Phat512 , restored to stock nand , 3rrod-0022

TimboZero

Full Member
Oct 26, 2004
57
0
Floating in Space
Hi all,

Another 3rrod-0022 thread.

Phat512 , dumped 16MB (doh) and wrote ecc , wasnt behaving so figured my error and back tracked. Read 64MB and injected the original 16MB read into it and flashed the stock 64MB back to the 360.
I get a 3rrod-0022 and even after removing and cleaning up the RGH install it does the same. I can also hear the fans slow for just a second every 4-5 seconds as if the 360 is power-cycling internally or similar. I can only guess I have cooked something ?
Apologies for the bypass pic quality , there's a bit of flux there and its hard to clean properly without risking damage.

Thanks

Timbo
 
Last edited:

SOloNon

Full Member
Oct 2, 2011
62
0
same problem . soldering point's have no issue . but when backing to orig nand got rrod .
 

TimboZero

Full Member
Oct 26, 2004
57
0
Floating in Space
Yes , it does sound as if the ECC file is still there but that is entirely impossible.

As for what I did (exactly) , from start to end.

1) installed nandx qsbs for write/read and coolrunner
2) read nand 2 times and compared (only read 16MB by mistake with nandpro usb: -r16 dump.bin)
3) built ecc file with multibuilder 0.3
4) injected to 16MB backup and flashed with nandpro usb: +w16 image.ecc
5) installed coolrunner (flashed with jasper timing file)

It had refused to boot several times , the coolrunner was red led only , I rerouted the wiring as per the revised install guide (ie avoiding the coils)

6) booted to xell and read the cpukey manually (due to no network connection)

This is where it got 'iffy' , the 360 powered itself down and refused to reboot. It also refused to see the nand when it was returned to my work area.

7) removed the coolrunner , checked around all my install for lifted traces , cleaned up where the coolrunner had been installed. Nandx started to see the nand again.

8) read the full nand with nandpro usb: -r64 dump64.bin

9) added the original 16MB dump back into the new 64MB dump with nandpro dump64.bin: -r64 dump.bin

10) erased the entire nand and then flashed the revised dump64.bin from step 9 to nand with nandpro usb: -w64 dump64.bin and read it back to verify a clean write

and that is basically the path to where i am now