Print Page - The Real Fix For "update Failed" Dashboard Installs

Congratulations,but you don't fell a bit sorry to loose the jtag ability of the console?

The damage was done before I received the console. Since it had been partially updated to 8498 before it failed, I could essentially only continue the install of 8498- no other version would load. It's a shame too because it was an hdmi pre nxe console with no history of RROD.

QUOTE(capcomguru @ Sep 12 2010, 10:35 AM)

Hi everyone-

I was fixing a console today for a friend that tried to connect to xbox live and get the NXE dashboard update. He was going from version 6717 to 8498. Midway through the update, his console froze, and when rebooted, all it would show was "Updated failed, please insert the update disc". I tried getting the latest 9199 firmware from microsoft, as I read online, and it wouldn't take the update. I tried putting a Hard Drive on the console that had 9199 installed, and no luck there.

I read online to download the latest update, burn it to a disc and go from there (or USB key or HardDrive). What all of the guides DO NOT tell you is you have to update to the failed dashboard before you can upgrade further. I realized the error code was pretty self explanatory, and is used to determine exactly which update you need. All the "fixes" I found say it needs to be the newest update, which is incorrect.

On the error screen, you'll see two (seemingly random) error codes. In my example, I was getting:
PV:2.0.6717.0 CV:2.0.8498.0

The PV error string represents the dashboard prior to the failed update, in my case 6717.
The CV error string represents the dashboard that failed to update, in my case 8498.

In order to redo the update, you MUST update to the one that failed (for me 8498). Once I realized what the error code was, I googled for the 8498 offline install. Extract the zip archive to a CD-r (using the build-in windows cd burning software), put the disc in your 360, boot it up and go.

I all but gave up on fixing it because I was using version 9199 provided from Microsoft. Once 8498 successfully instaled, I updated to 9199 and everything is fine!

I hope this helps other people.
Bill

Did you know how luckey you were, if the system failed to update the CB properly, u could have a bricked retail xD

Damn, I would have tried to JTAG it first. That error means it had 6717 and failed trying to update to 8498, so I'd say it would be 50/50 if it were still exploitable. If the eFuses were already burned, I don't think the system would even boot at all, or would give E80.

xboxscene.org forums

Xbox360 Forums => Xbox360 Software Forums => General Software Discussion => Topic started by: JuliVerHJ on September 12, 2010, 12:06:00 PM