got a 360 elite falcon v3 in from customer, has had a glass of water spilled on it whilst on (whoops!!)
console booted up at first but froze on the bootup animation and went into to RLOD error code E71 sec code 1013 problem with dash files
first assumption is that NAND has been shorted and corrupted.
hooked up SPI LPT wiring and dumped flash to see if nand is functioning and to try to get cpu key etc to make a new nand image fingers crossed!!
dumped it 3 times with a few differences (my setup gives 100% matches on all previous consoles)
assumed differences are due to corrupted/bad blocks
got this for dump in 360 flash dump tool
yay its exploitable might be light at end of tunnel!!
and this in degraded
decided to try XBR_8955_3 first, hooked up JTAG wiring and extracted kv and config block from orig with no issues patched into XBR and moved bad blocks manually
flashed XBR to get cpu key and test the nand to see if it even worked
success!! XBR and xell loaded pertfectly.
obtained cpu key ok which decrypted my kv with an odd string for OSIG (keep at end?)
rang the customer and he wants the xbox for live so i gotta rebuild a retail NAND image for the console
coffe time and lots of searching found me this post in x-h forumshttp://www.xboxhacker.org/index.php?topic=12265.40
i was delighted to see that it was possible to rebuild a good image so i grabbed all the files required and started it.
created 1888 bin ok, kv details the same, patched LDV values to max and matched pairing info, as tut says which gives me shown below
erased nand and flashed, removed JTAG wiring and booted 360 to be met with black screen and RROD 0022 after 20 secs, pointing to incorrect LDV values or something?
moved the bad blocks in the clean 1888 image also.
where have i gone wrong? is the 1888 for xenon only? should i use a diff kernal for falcon?
i have a donor falcon.bin but do not have the cpu key for it to decrypt the kv to insert my own.
any pointers on how i can get this xbox back to original dash?
any help much appreciated