xenon help

Jun 4, 2010
3,080
0
The CPU key has to be correct, else it would have not decrypted your KV files.

So far we tried:

1. Remapping original NAND then compiling Freeboot (Failed)
2. Compiling Freeboot from original NAND the remapping (Failed)
3. Compiling Freeboot from original NAND without remapping (Failed)
4. Use another NAND source but with your KV (the freeboot I sent you) (Failed)

It's time to construct Freeboot block by block.
 
Last edited:

big_ted

VIP Member
Dec 31, 2003
766
48
Midlands UK
some ideas to try, i've been thinking (never good)

Have a go at zeroing or ff'ing the bad blocks on the nand after writing.

flash with fash360 or xellous these should auto remap the bad blocks.

Try extracting the kv and config, from you dump(a) and inject them to another xenon dump(b) with no bad blocks using 360 flash tool.

This will still be encrypted by the (b) cpu key so will need that cpu key to decrypt in ibuild,

use this guide, from the "free boot part"
http://team-xecuter.com/forums/showthread.php?t=54531

1. Extract your original image

Extract your original 7371 [recommended but not necessary] image with the following command:

ibuild.exe x -d temp\ -p [cpu key] -b [1bl key] dump.bin (dont include the square brakets)

"the cpu key is from the donor nand"

then when you rebuild it use the cpu key (a) your problematic console, then try as above xellous and flash360 if that doesn't work try moving the bad blocks manual and dump the new image.

"fingers crossed"

Ted
 

craigj172

Junior Member
Mar 13, 2009
19
0
Well after trying every option i have come to believe that freeboot just cant work on a xenon with bad blocks in the first 50 so have found someone who wanted a standard xbox and swaped mine for his. dumped flash and had 3 bad blocks but all above first 50 made freeboot image same as with other xbox remapped to match orig bad blocks and worked perfect 1st time. thanks all for you time and effort sorry we couldnt crack it but its been a lesson lol.