confusion about xell and kv...

[bluemimmos]

ok, i have a litle confusion regarding kv and xell.

to my knowledge:

Xell= Xenon linux loader, it is the 1st stage loader for linux which is trigerred via smc hack...
KV= KeyVault, each is unique and consists of unique data for each consoles like dvd key, osig, region, console mfgr date, serial no. etc.

to dump KV from original nand file.

we give this command.

nandpro backup.bin: -r16 kv.bin 1 1

this means kv is located in the 1st block and its length is 1 block...  (correct me if i am wrong)

and
my question  is that ,

Can i first write xell to the nand without backing it up.... and run gentoo and use xbrflash from trancy to dump the nand and flash xbr to it...


doesn't xell overwrite the kv area??

please reply soon...

[Arakon]

Xell overwrites the kv.

[bluemimmos]

Code:

livecd Desktop # .[b]/a.out b1.bin xbr.bin -i[/b]  (means dump nand as b1 and flash xbr.bin file)

XBR-Flash for Linux v0.2 beta by trancy
Thanks goes to tmbinc and Redline99

Nandsize: 512 MB detected
Read and write: 64 MB

Dumping to b1.bin...
0x200 block's to dump...
Bad block found (index: 0x16)                 
Reading block: 0x200 of 0x200
Reading done in 41.00 sec.
Speed: 1.56 MB/s

Verifying flash with b1.bin...
0x200 block's to verify...
Detected RAW nand file, verifying in raw mode.
Bad block found (index: 0x16)                 
Ignoring bad block @ 0x16         
Verifying block: 0x200 of 0x200             
Verify done in 41.00 sec.
Speed: 1.56 MB/s.
Verify ok.

[b]Injecting KV and Config from b1.bin to xbr.bin...
Injecting done.[/b] (see, injecting kv from b1 to xbr, kv is already gone away because xell is written to it..)

Flashing from xbr.bin...
0x200 block's to write...
Detected RAW Nand file, flashing in raw mode.
Relocating/moving bad block from position 0x16 to 0xfff
Writing block: 0x200 of 0x200
Write done in 31.00 sec.
Speed: 2.06 MB/s

Verifying flash with xbr.bin...
0x200 block's to verify...
Detected RAW nand file, verifying in raw mode.
Bad block found (index: 0x16)                 
Ignoring bad block @ 0x16         
Verifying block: 0x200 of 0x200             
Verify done in 41.00 sec.
Speed: 1.56 MB/s.
Verified 67108864 bytes ok :)
livecd Desktop #
 

still confused,, how is that possible.......

look the code in bold and my comments in braces....