ANSWERED Issue with updating to new dash

walapu

Junior Member
Jan 6, 2012
10
0
Alright, so I updated 13604 successfully. After about three minutes of testing out the new dash, my screen glitched and froze up. I could no longer boot the xbox up, so I decided to pull up nandpro (lpt) and reflash. Now I can't write any of the blocks, nor read. Any ideas as to why this may happen?:(

Thanks for the help
 

walapu

Junior Member
Jan 6, 2012
10
0
Small correction, I can turn it on but will not boot up. After about 2 minutes I get 3 rings.
 

walapu

Junior Member
Jan 6, 2012
10
0
Sorry for not being clear, I plugged the lpt cord into my computers lpt port to reflash with the upgraded nand, a second time. This was after I successfully updated with 360flash, but 3 minutes into running the new dash it froze. Now I can longer boot or access the nand, I also get 3 rings after about 2 minutes of the xbox sitting on.
 

walapu

Junior Member
Jan 6, 2012
10
0
Hmmm, that did come to mind. I had just repaired the console about three weeks ago, I tried overheating it to see if I could bring it back to life but no luck. Doesnt rrod appear immediately when the xbox is turned on? The red rings show up about two minutes later. It would make sense that rrod would prevent you from accessing the nand, correct?
 

alexhore

BANNED
Sep 16, 2011
60
0
Manchester, UK
I just found someone with the same issue, take a look http://www.se7ensins.com/forums/top...-flash-dead-360/page__p__3369367#entry3369367 I do not believe this is rrod, and may I correct myself once more it is about 30 seconds to 1 minute until the rings appear!
Be very carefull trying that shorting trick you can do more damage. If you had it booting then I would concentrate on checking your wireing for both the RGH/JTAG and the nand-x.

Did you get that secondary error code? this will indicate RROD or dead nand....
 

walapu

Junior Member
Jan 6, 2012
10
0
0022

0022
See Error E10

E10: Unconfirmed: CPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints). This can also be triggered by an error with the TSOP.

Looks like rrod.
 

walapu

Junior Member
Jan 6, 2012
10
0
Actually, the TSOP is where the nand is stored correct? I should still be able to read the nand if I have RRoD, but in this case I cannot. This seems nand related and not RRoD.
 

RavenPhoenix

Senior Member
Mar 25, 2011
135
0
Sydney OZ
www.consoleme.webs.com
From what you are explaining it sounds like your JTAG either has had a bad flash or it may as well have a real deal RROD.

I recommend trying to solder on a SPI nand flasher like the Nand-X and see if you can read or write to the NAND at all. I mean unless something went terribly wrong during the upgrade flash that you done there shouldn't be a physical problem with the TSOP. Only short out the NAND as a very very last resort if nothing will work. Failing that you may want to seek assistance from a local pro if you feel that you not getting anywhere.