GENERAL NAND of a console stuck in an update loop.

[Dosk3n]

Hey guys and gals just want your thoughts on this situation.

I have a stock console that I have had laying around for about a year now that is stuck in an update loop. I have taken about 20 consoles out of an update loop so I know the procedure here however this was a stock console that from what I can tell must have RROD'd mid update and got stuck that way. I reflowed the GPU so fixed the RROD issue but just cant get it out of the update loop with no matter what dashboard update I use. Still keeps saying reattach hard drive that was used when updating. Obviously I dont have that so I am attempting USB and CD.

Anyway thats just the background so not that important.

My real questions is could I read the NAND of this console with it being stuck in an update loop and then build a Freeboot NAND of the latest dash. Would the fact that its stuck in a loop make any difference to the NAND such as corruption?

I will still be attempting a few other things for the update loop in the mean time but obviously if this was a possibility then I could just skip that part and go straight to installing Freeboot.

-Dean.

 

[Martin C]

Aside from rebuilding the NAND, ALL consoles can be taken out of an update loop. MS made it that way for a purpose.

1. Install the stock drive with stock firmware (unless you know what it was on previously, it will be either pre or post 13146 firmware. You may need to try them both).

2. Insert a USB stick with the version of dashboard which was present - you can dump the NAND to find this out as it records the current and previous dashboard versions.

That's it. You should get it out of the update loop.

If you want to go the rebuild route, get the CPU key / NAND dump from the console and build a retail NAND for it. Flash this to the console and you should be ok.

 

[Dosk3n]

Ah well at least I know the option is there to work from the nand. Its got the original drive still in it. But with a dead laser (shouldnt matter I know).

I have tried it with 13146 onwards. Just with it being a year ago I have no idea what dash was on when it RROD'd.

I will dump the nand and get the dash version that way then update it and if I get nowhere I will go the nand route. Got a few cool runners laying about so will be installing that anyway which was why I mentioned Freeboot.

Thanks for your insight!

 

[Martin C]

Well dump the NAND and you'll know what the previous one is. A hint is 13146 wasn't out a year ago. The Kinect came out last year with 12*** dashboard, so the reason it's not working is you've not gone back far enough. Flash the drive with a pre-13146 stock firmware and go BACKWARDS from 13146.