Falcon E79 Xbr

[4cc3ss]

I've just successfully got a falcon backup and working from error 79, the exploitable 6683 360 was brought forward to myself from a friend, has he couldn't get nandpro to recognize the nand.

After spending sometime goin over the wiring i was able to dump an image.. error free.. Ecc 100%
I extracted kv & config and then injected into xbr3 and flashed, when i powered up the 360 it gave E79
So i flashed the original back, which gave me E71 wtf, so i reflashed with xbr3 which gave me E79 again,
this time i dumped xbr image to see if it had gained any errors when the nand was flashed, but no errors occurred,
with the image.
I knew kv and config.bin wasn't corrupt, there was some confusion over drive key at one point,
this had nothing to do with the errors above.

My next solution was to check the diodes and jd2.2 diode had no continuity, after replacing the diode and E79
still giving me grief, i decided to reflash using Xell.
When i powered up, xell booted and efuses was displayed, from this point i knew if i did a reflash with xbr
the xbox would boot into 8955 dash.   
 
Sorry if i sounded mardy jay, it was my weekend off don't jump so deep next time

Enjoy m8

Before anyone mentions that i should read the nand 2 -3 times before flashing, i'm able to dump a working image 1st time round, using nandpro 2.0b, this would work for most, depending on hardware, i've explained how this is achieved in previous post, i was surprised this also worked for the falcon, after reading the issues this console is causing, i feel for the one's who are having issues with the falcon as it's not as straight forward as the xenon.

[cozmo]

great m8 thanks for all your help and you did'nt seem that mardy lol

thanks again

jay

[jelle2503]

Before anyone mentions that i should read the nand 2 -3 times before flashing, i'm able to dump a working image 1st time round, using nandpro 2.0b, this would work for most, depending on hardware, i've explained how this is achieved in previous post, i was surprised this also worked for the falcon, after reading the issues this console is causing, i feel for the one's who are having issues with the falcon as it's not as straight forward as the xenon.

have fun bricking your Xbox by doing only 1 dump.. i thought I had ubercompatible hardware coz I did 10 consoles without any mismatches.. 11th console would only give mismatched dumps

glad i wasn't being retarded and did only 1 dump and figured it would be OK.. wrong choice

[4cc3ss]

Before anyone mentions that i should read the nand 2 -3 times before flashing, i'm able to dump a working image 1st time round, using nandpro 2.0b, this would work for most, depending on hardware, i've explained how this is achieved in previous post, i was surprised this also worked for the falcon, after reading the issues this console is causing, i feel for the one's who are having issues with the falcon as it's not as straight forward as the xenon.

have fun bricking your Xbox by doing only 1 dump.. i thought I had ubercompatible hardware coz I did 10 consoles without any mismatches.. 11th console would only give mismatched dumps

glad i wasn't being retarded and did only 1 dump and figured it would be OK.. wrong choice

Your funny, i'm suprised that you was able to spell retarded, no bricks yet apart from the very 1st one i did lucky enough i grabbed 2 dumps with bad blocks but in the end i got it running, this lead me to seeing why these bad blocks
occured in the 1st place, i've done a good few now and been lucky, it's the case using the right tools to check the image, i already know there's nands out there with dead blocks and this would tell me to take more than the one reading.

[Arakon]

A dump with differences doesn't automatically have bad blocks. It's enough for someone to turn on a light on the same power line to cause a voltage peak that may corrupt the data read, without it ever showing as bad.

[4cc3ss]

A dump with differences doesn't automatically have bad blocks. It's enough for someone to turn on a light on the same power line to cause a voltage peak that may corrupt the data read, without it ever showing as bad.

I totally agree Arakon, i've sat back and thought the possibilities how the data can corrupt, mobile phone etc,
and it does seem to be a gamble and an expensive one at that, there's always the option to dump the 2 main
images which are needed for xbr several times and this gives less odds of having corrupted data.
 

[Arakon]

Yeah. If you want to dump less but still be safe, at least get one full dump and then 2-3x the keyvault and config.

[4cc3ss]

Yeah. If you want to dump less but still be safe, at least get one full dump and then 2-3x the keyvault and config.

Good advice, i'm sure some users only extract the kv & config from the nand image and not extract from the nand it self.