TimelessNL
Enthusiast
Hi People,
Question:
Could it be that a corrupt NAND causes e79? but still boots Xell just fine?
Answer:
Yes, after flashing a donor NAND image and unplugging it for 20sec to reset the SMC ram. This Xbox360 came back to life .
(See post #8 for detailed information)
Full story:
I recently acquired a Falcon motherboard that suffered severe damage by the previous owner, seems like he(or she) attempted all known hardmod methods that ever existed the Xbox360 galaxy. I can see soldering attempts pointing to JTaG and RGH1 and also see some sticky residue on the AV port suggesting that some modchip was present at a given time, it even had some (broken)remains of the Nand-X J2B1 near the H-ANA chip.
Ok, so what is the problem you asked? Glad you asked , Originally the Xbox gave me a 0022 error (immediately after boot). I successfully re-routed some of the traces (namely PLL_CPU_BYPASS) and some resistors the previous owner burned to death. After which I tried to boot the thing with whatever was left on the NAND by the previous owner. This gave me 0022 again but this time took like 30 sec's and also continuously ramped-up the fans, which by my experience could either mean a reflow(reball) was needed (not worth the effort) or the NAND is corrupt.
After I dumped the NAND it seams clear that it was indeed corrupt:
Full updflash creation log: link
Since this was the first time I had to deal with a corrupt NAND, I continued as usual and flashed Xell and installed an ACE360v3 based on RGH1.2. I chose RGH1.2 because I had no idea which dash it had. After turning it on to my surprise it booted straight into Xell (took 4 glitches with the [Click here to view this link] on a cold boot and 1 glitch on warm boot). But my luck did not end there, I wrote the CPU key and created my self a FreeBoot(updflash.bin) image which I flashed with a USB stick in Xell (much faster than J-Runner). The hacked dash also booted just fine presenting me with a "overheat" message which was most likely caused by the previous owner. But since I did not expect it to boot at all I did not have the FAN's installed yet, so I powered the thing off, installed the FAN's and booted it a 2nd time. This time I browsed the menu's a but to see if it was stable which it was . Unfortunately my luck ends there, I once again turned it down took some pictures of my victory install, removed NAND programming wires and put it all back into its plastic case (without HDD).
Troubles:
once it was fully assembled I turned it on but to my alarm it gave me 1 RRoD with secondary error code (1033) e79 (no display output). But strangely it still boots to Xell every time. Also I see it doing its cold boot 4 glitches (warm boot 1 glitch) then 5 sec's later bam.. e79. So it's not immediately e79 but only after the glitch is successful.
Things I tried:
-Run it without FANs for a while which should most likely temporally solve a broken solder joint but to no avail. Even if it booted after applying the "GPU overheat fix" I would plan to trow it away anyway because of previously given reasons.
-Rebuild dummy NAND based on this tutorial but still no luck, boots Xell but not to Dash. Calculated LDV to be 17 based on fuses.
-Looked around for solder bridges but couldn't find any.
-Flashed NAND though Xell multiple times.
Question:
I also noticed CF and CG from the NAND dump showed 4532, do these numbers represent the dashboard version it came with or it's current version? Because the previous owner attempted a JTaG mod. Maybe that's why the RGH1.2 does not work. Also during the ECC xell boot it had trouble decrypting the KV but after flashing FreeBoot it had no issue and gave my a DVD key, Don't know if the key is valid or not. Since I have not checked the DVD drive yet.
Here are some pictures of the e-fuses and J-Runner stats:
Initial ECC write:
After writing FreeBoot (updflash.bin) through Xell:
Initial state of the PCB below the CPU (before me doing anything):
PLL_CPU_BYPASS fix
RGH v1.2 wiring:
Question:
Could it be that a corrupt NAND causes e79? but still boots Xell just fine?
Answer:
Yes, after flashing a donor NAND image and unplugging it for 20sec to reset the SMC ram. This Xbox360 came back to life .
(See post #8 for detailed information)
Full story:
I recently acquired a Falcon motherboard that suffered severe damage by the previous owner, seems like he(or she) attempted all known hardmod methods that ever existed the Xbox360 galaxy. I can see soldering attempts pointing to JTaG and RGH1 and also see some sticky residue on the AV port suggesting that some modchip was present at a given time, it even had some (broken)remains of the Nand-X J2B1 near the H-ANA chip.
Ok, so what is the problem you asked? Glad you asked , Originally the Xbox gave me a 0022 error (immediately after boot). I successfully re-routed some of the traces (namely PLL_CPU_BYPASS) and some resistors the previous owner burned to death. After which I tried to boot the thing with whatever was left on the NAND by the previous owner. This gave me 0022 again but this time took like 30 sec's and also continuously ramped-up the fans, which by my experience could either mean a reflow(reball) was needed (not worth the effort) or the NAND is corrupt.
After I dumped the NAND it seams clear that it was indeed corrupt:
Code:
Initializing nanddump1.bin..
Comparing...
Header is wrong..
Since this was the first time I had to deal with a corrupt NAND, I continued as usual and flashed Xell and installed an ACE360v3 based on RGH1.2. I chose RGH1.2 because I had no idea which dash it had. After turning it on to my surprise it booted straight into Xell (took 4 glitches with the [Click here to view this link] on a cold boot and 1 glitch on warm boot). But my luck did not end there, I wrote the CPU key and created my self a FreeBoot(updflash.bin) image which I flashed with a USB stick in Xell (much faster than J-Runner). The hacked dash also booted just fine presenting me with a "overheat" message which was most likely caused by the previous owner. But since I did not expect it to boot at all I did not have the FAN's installed yet, so I powered the thing off, installed the FAN's and booted it a 2nd time. This time I browsed the menu's a but to see if it was stable which it was . Unfortunately my luck ends there, I once again turned it down took some pictures of my victory install, removed NAND programming wires and put it all back into its plastic case (without HDD).
Troubles:
once it was fully assembled I turned it on but to my alarm it gave me 1 RRoD with secondary error code (1033) e79 (no display output). But strangely it still boots to Xell every time. Also I see it doing its cold boot 4 glitches (warm boot 1 glitch) then 5 sec's later bam.. e79. So it's not immediately e79 but only after the glitch is successful.
Things I tried:
-Run it without FANs for a while which should most likely temporally solve a broken solder joint but to no avail. Even if it booted after applying the "GPU overheat fix" I would plan to trow it away anyway because of previously given reasons.
-Rebuild dummy NAND based on this tutorial but still no luck, boots Xell but not to Dash. Calculated LDV to be 17 based on fuses.
-Looked around for solder bridges but couldn't find any.
-Flashed NAND though Xell multiple times.
Question:
I also noticed CF and CG from the NAND dump showed 4532, do these numbers represent the dashboard version it came with or it's current version? Because the previous owner attempted a JTaG mod. Maybe that's why the RGH1.2 does not work. Also during the ECC xell boot it had trouble decrypting the KV but after flashing FreeBoot it had no issue and gave my a DVD key, Don't know if the key is valid or not. Since I have not checked the DVD drive yet.
Here are some pictures of the e-fuses and J-Runner stats:
Initial ECC write:
After writing FreeBoot (updflash.bin) through Xell:
Initial state of the PCB below the CPU (before me doing anything):
PLL_CPU_BYPASS fix
RGH v1.2 wiring:
Last edited: