Bestpig update.bin Question

[hawk3y3]

Using Nand-x I dropped 5 copies of the on-board nand to PC

I checked and verified the 5 copies as the same using hex workshop

Degraded confirm the Xenon CB to be 1921 and as the dash was 6717 the console was exploitable

I installed Xellous and connected to the console via Firefox and downloading a 3 further nand copies all of which were the same (8 backups in total)

So far so good .........

My problem was that on installing xbr3 for Xenon from the Xellous screen (Xellous showed if flashing a number locations) it would still not boot into anything but Xellous (USB Controller in rear, using eject button etc)

So I took the plunge and re-flashed one of the original nands and the console reverted to its original state.

I then repeated the install and the console was again locked into booting only Xellous.

No matter what I did it would not boot into a "console" dash.

I then decided to use try BESTPIG 0.26 to create an update.bin file (autodetect based on CB 1921), which created an update.bin which I flashed via USB stick to the console.

The console now boots into a 12611 dash, however it will not run Xex loader from CD, it says the disk is not recognised.

The CB from the nand download of the new dash has been upgraded to 1923 and if I flash the original nand I just get a singe green light on the front of the console.

Have I screw up the jtag (the new 12611 works normally) or as I have my CPU key and original nand dump can I reflash it into a state that will run xex files.

I am asking at this stage as I don't want to do something that renders the console no functional.

TIA

 

[Xmods]

make sure you nand open in 360 flash tool if you get bad k/v on the right side then you have entered the wrong cpu key

 

[hawk3y3]

I attach screenshots of 360 Flash Tool and Degraded

If I download the onboard nand and put that in degraded the CB is 1923 LDV0??

If I look at the original updflash.bin on the memory stick it shows a CB of 1921 LDV0

I hope this helps

Thanks for looking at this

 

[tony1160]

have you put your cpu key in before making freeboot??

and might of been better updateing your dash to 7371

 

[hawk3y3]

This is a text dump of the web page created by Xellous

XeLLous v1.0 By Redline99
Taking back your console
Based on XeLL - Xenon Linux Loader
Keys
SECRET KEY
CPU 6A0...........................E2
DVD ...................................
Downloads
FILE

DESCRIPTION

DOWNLOAD
Fuses The jewels that keep you honest. Fuse line 3 and 5 makeup your CPU key.

Download
Raw Flash This is the file needed for any flash modifications.
Download
Key Vault This is your Decrypted Key Vault and is part of what makes your console unique.
Download
Key Vault (RAW) This is your Encrypted Key Vault and is part of what makes your console unique. (equivalent to nandpro -r switch)
Download
Config Blocks (RAW) Contains the unique console MAC address and other configuration data. (equivalent to nandpro -r switch)
Download
Tools
Set DVD Key
This has limited use and is kept here in case someone finds a need for it. *It only SETS the DVD key and does not FLASH and does not modify the Key Vault's OSIG.

I have also attached a screenshot of the bestpig freeboot generator used to create the updflash.bin

I just pasted the CPU key from the Xellous web page into the Bestpig 2.6 package it detected a Xenon mobo and CB1921 and created an updflash.bin which I copied to the root of a usb stick which I then used to update the console.

Degraded shows that the updflash.bin created is based on the correct CB1921.

Can I try to create a new updflash.bin and reflash, if so what did I do wrong the first time?

The 12611 dash is fully functional works with ACB and NFS but will not run .xex files from CD / USB?

 

[hawk3y3]

Apologies for double posting, however I have been at this for most of the evening as its driving me crazy.

I read on one forum that if you format a USB stick with the console (which is what I have been doing) that it stops the USB autoboot working and so I tried formatting my USB stick under windows XP - FAT32.

I then copied the content of my XEX Loader 0.26 CD onto the stick and booted the console with the USB in the slot and guess what, I get an E71 error.

Now its my understanding that this error relates to either a corrupted flash or bad blocks.

More importantly the error does not show if the USB stick is NOT in the console. This leads me to believe that the console is trying to execute the default.xex in the root of the stick.

I took the stick to my mates house who also has a JTAG and that console also shows an e71 error if I insert my USB stick into his console.

So if I'm right then I need to build a suitable booting USB stick. I will look for a tut on this, if anyone can suggest a working file structure from a USB stick that boots their JTAG I would be grateful for a copy to try on my console.

Might be getting there......................

 

[hawk3y3]

I found a good tutorial on making a bootable USB stick to run XeXMenu and build it using XexTaf and XexMenu.

It boots in my friends JTAG (CD and USB) and shows an XEXMenu screen, however on my console the XeXMenu just flashed briefly into view on the library screen, (CD Does not boot) which I think means that mine is not executing the XeX file, i.e. is not a JTAG

Any suggestions on reflashing the console as the wiring is correct?