Print

[phasic]

I installed Nand-X and read my nand 3 times.
Using Coolshrimp's jtag tool I wrote the xell and when I started my xbox I got E79.
Then I removed Xell and tried turning the xbox back on, now I get a black screen and 3 flashing red lights.

Any ideas?

[MadBoxer]

QUOTE(phasic @ Nov 13 2010, 02:10 PM)

I installed Nand-X and read my nand 3 times.
Using Coolshrimp's jtag tool I wrote the xell and when I started my xbox I got E79.
Then I removed Xell and tried turning the xbox back on, now I get a black screen and 3 flashing red lights.

Any ideas?

Sounds to me like it is a bad nand flash dump or write. A bad solder connection would cause e79 with xell, but it should have booted again when dumping the nand back. Did you compare the 3 nand dumps and make sure at least two of them match? If they don't match, you didn't get a clean dump. Also, what is the secondary error code? The 3red lights can be many different things. If you are not familiar with how to get your secondary error code, do the following:

•   Turn the xbox 360 on, and wait untill the 3 red lights are flashing.
•   Press and hold the sync up button, while holding that button press the eject button.
•   The LEDs will now blink the first number in the code.
•   Release the eject button and press it again.
•   The LEDs will now blink the second number of the code.
•   Release the eject button and press it again.
•   The LEDs will now blink the third number of the code.
•   Release the eject button and press it again.
•   The LEDs will now blink the forth number of the code.
•   Release the eject button and press it again.
•   The LEDs will go back to the 3 red flashing lights.

If you let me know what the secondary 4 digit error code is, I can narrow it down.

[phasic]

QUOTE(MadBoxer @ Nov 13 2010, 05:47 PM)

Sounds to me like it is a bad nand flash dump or write. A bad solder connection would cause e79 with xell, but it should have booted again when dumping the nand back. Did you compare the 3 nand dumps and make sure at least two of them match? If they don't match, you didn't get a clean dump. Also, what is the secondary error code? The 3red lights can be many different things. If you are not familiar with how to get your secondary error code, do the following:

•   Turn the xbox 360 on, and wait untill the 3 red lights are flashing.
•   Press and hold the sync up button, while holding that button press the eject button.
•   The LEDs will now blink the first number in the code.
•   Release the eject button and press it again.
•   The LEDs will now blink the second number of the code.
•   Release the eject button and press it again.
•   The LEDs will now blink the third number of the code.
•   Release the eject button and press it again.
•   The LEDs will now blink the forth number of the code.
•   Release the eject button and press it again.
•   The LEDs will go back to the 3 red flashing lights.

If you let me know what the secondary 4 digit error code is, I can narrow it down.

Thanks for your reply 0020

[MadBoxer]

QUOTE(phasic @ Nov 13 2010, 03:56 PM)

Thanks for your reply 0020

That error code is an unconfirmed error, but the description of the possible problems is:

"Unconfirmed: General I/O Malfunction, could be caused by an error with any of the I/O devies such as A/V port, USB, Hard drive, DVD drive, etc. over torquing of the AV or heatsync bolts can cause this error."

You could try unplugging all HD/USB devices or adjust the tightness of the heatsink bolts, but It could very well be a problem with that nand. Did you verify that the original dumps are identical? You can use the freeware program "Total Commander" to compare the dumps. If they match, try re-dumping the original back one more time and see if it boots.

[brandogg]

If you have the JTAG wiring installed, remove it. 0020 is a common error with JTAG systems upon quick power cycles and stuff like that, due to the way that the wiring is. 0020 is also the error code (like 0102) for a cold solder joint under the GPU, so if you get that error with the original NAND image and no JTAG wiring installed, then you've got a typical RROD system.

[phasic]

Ive dumped a total of 6 nand reads and they all match with 0 bad blocks. I tried to write xell again with nandpro20e, the write was successful but I am still getting e79 when trying to boot with the eject button.

[kipper2k]

QUOTE(phasic @ Nov 15 2010, 03:30 PM)

Ive dumped a total of 6 nand reads and they all match with 0 bad blocks. I tried to write xell again with nandpro20e, the write was successful but I am still getting e79 when trying to boot with the eject button.

silly question, gotta ask.  have you installed the jtag wiring as well as the wiring for reading the nand.

 - What wiring did you use, did you use resistors, diodes or the diode/transistor wiring ?
 - try restoring your original nand file and start from scratch

[phasic]

QUOTE(kipper2k @ Nov 15 2010, 08:34 AM)

silly question, gotta ask.  have you installed the jtag wiring as well as the wiring for reading the nand.

 - What wiring did you use, did you use resistors, diodes or the diode/transistor wiring ?
 - try restoring your original nand file and start from scratch

All wiring has been installed. I used the Nand-x Kit with the quick solder boards. I have tried that several times now.

[kipper2k]

QUOTE(phasic @ Nov 15 2010, 03:47 PM)

All wiring has been installed. I used the Nand-x Kit with the quick solder boards. I have tried that several times now.

K, you need to ensure the CB of your motherboard is a jtaggable one, use degraded and load your original bin file into it to find out what the CB value is.

 Restore the original bin file back onto your motherboard and verify it will boot up once restored.

[phasic]

QUOTE(kipper2k @ Nov 15 2010, 09:06 AM)

K, you need to ensure the CB of your motherboard is a jtaggable one, use degraded and load your original bin file into it to find out what the CB value is.

 Restore the original bin file back onto your motherboard and verify it will boot up once restored.

CB Version 5761, will trying original bin now but it hasnt worked before, maybe I messed up this point?

(IMG:http://coxercise.com/images/IMG_1401.JPG)

[kipper2k]

Messing up that point will only affect booting in jtagged mode and not regular bootup. If you restore the original nand and it doesnt boot up normally, then you have little choice except to remove the nand-x to see if that is interfering.

[phasic]

QUOTE(kipper2k @ Nov 15 2010, 09:28 AM)

Messing up that point will only affect booting in jtagged mode and not regular bootup. If you restore the original nand and it doesnt boot up normally, then you have little choice except to remove the nand-x to see if that is interfering.

Do I need to have all the internal component plugged in (aka dvd drive) once I install the original nand?

[kipper2k]

heres a list of exploitable CB's...

Exploitable CBs:
Xenon: 1921 or lower is Exploitable (exception: 8192 IS EXPLOITABLE)
Zephyr: 4558 or lower is Exploitable (exception: 4580 IS EXPLOITABLE this needs falcon version of Free60)
Falcon: 5770 or lower is Exploitable
Jasper 16mb: 6712 or lower is Exploitable
Jasper Arcade (256/512): 6723 or lower is Exploitable

 so it looks like your CB is at least in the correct range to jtag. I looked at the nand-x and i am not familiar with it,  from what i seen on the website it only hooks up the nand read/write points and not the jtag connections. Also you have to make sure that your jtag wiring agrees with the version of xell that you are using otherwise you will get the E79 error

... DVD doesnt need to be plugged in to actually get xell , xellous or your 360 to begin the bootup process, i'm assuming that once you wrecked that pad, you wired the alternate point underneath the board

 Always use flux when trying to solder onto a pad, dont rely on the flux  in the solder... apply flux to the pad, then place soldering iron tip on edge of pad and push the solder onto the pad, it will blob up. If the pad is dirty/oxidised then use an asbestos pencil to clean it up

This post has been edited by kipper2k: Nov 15 2010, 04:38 PM

[phasic]

QUOTE(kipper2k @ Nov 15 2010, 09:32 AM)

heres a list of exploitable CB's...

Exploitable CBs:
Xenon: 1921 or lower is Exploitable (exception: 8192 IS EXPLOITABLE)
Zephyr: 4558 or lower is Exploitable (exception: 4580 IS EXPLOITABLE this needs falcon version of Free60)
Falcon: 5770 or lower is Exploitable
Jasper 16mb: 6712 or lower is Exploitable
Jasper Arcade (256/512): 6723 or lower is Exploitable

 so it looks like your CB is at least in the correct range to jtag. I looked at the nand-x and i am not familiar with it,  from what i seen on the website it only hooks up the nand read/write points and not the jtag connections. Also you have to make sure that your jtag wiring agrees with the version of xell that you are using otherwise you will get the E79 error

... DVD doesnt need to be plugged in to actually get xell , xellous or your 360 to begin the bootup process, i'm assuming that once you wrecked that pad, you wired the alternate point underneath the board

 Always use flux when trying to solder onto a pad, dont rely on the flux  in the solder... apply flux to the pad, then place soldering iron tip on edge of pad and push the solder onto the pad, it will blob up. If the pad is dirty/oxidised then use an asbestos pencil to clwean it up

I havent wired the alternate point, I wanted to make sure you agree theres no way for me to solder to that point.

[kipper2k]

QUOTE(phasic @ Nov 15 2010, 04:39 PM)

I havent wired the alternate point, I wanted to make sure you agree theres no way for me to solder to that point.

that point is toast, move on to the alternate point, if you arent sure of your soldering capabilities, stop, and get help... if you follow my tip to blob up the pad you should be fine, use fine 26 - 30 awg kynar solid core wire, don't use stranded wire