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
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.