Jump to content


Photo

Update Failed Pv:2.0.7371.0 Cv:2.0.8955.0


  • Please log in to reply
5 replies to this topic

#1 syntaxerror329

syntaxerror329

    X-S Hacker

  • Members
  • PipPipPipPipPipPip
  • 2,330 posts
  • Location:Niagara Falls
  • Interests:Mountain Biking, Downhill Skiing, Xbox Mod Chips, Xbox Repair, Wiikey, ARGON, D2pro, XBOX360,
  • Xbox Version:v1.6
  • 360 version:v3.1 (opus)

Posted 09 February 2010 - 08:46 PM

First off here is the complete error message.

Update Failed

Couldn't find you Xbox 360 Hard Drive. If the hard drive is attached, contact Xbox Customer Support or go to www.xbox.com/support.

PV:2.0.7371.0 CV:2.0.8955.0

-----------------------------

So here is where i am at with this.
A customer brought this to me for repair.
I have no idea what they did to get to this point.

Hard drive works fine on other consoles. Hard drive connector on motherboard looks fine.
Tried the power on while holding sync to remove bad updates fix but that doesn't help.

I assume PV: means previous version and CV: must then mean Current Version.

Last one of these i had with similar problem had CV of 7371 so i installed xbreboot on it and got it going that way.

Is there anything the jtag hack can do to help me fix this?

Has anyone ever fixed this error?


#2 BUZYAHAZZ

BUZYAHAZZ

    X-S Enthusiast

  • Members
  • 4 posts

Posted 09 February 2010 - 09:05 PM

you will need to either use a newer game with the 8955 update on it... or download it from the xbox website and either burn it to disc or transfer it to a usb drive... this has worked for me every time with the same error

#3 syntaxerror329

syntaxerror329

    X-S Hacker

  • Members
  • PipPipPipPipPipPip
  • 2,330 posts
  • Location:Niagara Falls
  • Interests:Mountain Biking, Downhill Skiing, Xbox Mod Chips, Xbox Repair, Wiikey, ARGON, D2pro, XBOX360,
  • Xbox Version:v1.6
  • 360 version:v3.1 (opus)

Posted 11 February 2010 - 01:41 AM

I just plugged my hard drive in with 8955 and it was fixed. LOL
Simplest repair ever. I feel silly for even making a thread But I really didn't expect it to work.

The last one i had with almost the exact same error (differnt version #'s) could not be fixed that way and now its running xbreboot and that is just fine with me.

Thanks for the reply.













#4 TingedAce

TingedAce

    X-S Senior Member

  • Dev/Contributor
  • PipPip
  • 179 posts
  • Location:Scotland
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 01 April 2010 - 11:25 PM

LOL, it's interesting nonetheless. I have a question though....

The string PV:2.0.7371.0 CV:2.0.8955.0

This means the previous version was 7371, and it's trying to update to 8955 but it's not completed, is that correct? Do we know if the eFuse is already blown at this point or not?

Even if it were, is it possible to fix using some sort of fancy KV swapping and patching into a donor 8955 NAND? I just know the answer's going to be no, due to something to do with pairing or something that I haven't quite grasped yet wink.gif

Cheers

Edited by TingedAce, 01 April 2010 - 11:25 PM.


#5 PaganOne

PaganOne

    X-S Member

  • Members
  • Pip
  • 76 posts
  • Location:Colorado, US
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 04 April 2010 - 05:16 AM

Have you tried powering up the console while holding the sync button? I was under the impression that this combination was specifically for failed updates and will clear the update.

#6 radoman

radoman

    X-S Member

  • Members
  • Pip
  • 149 posts

Posted 04 April 2010 - 07:52 PM

QUOTE(TingedAce @ Apr 1 2010, 11:25 PM) View Post

This means the previous version was 7371, and it's trying to update to 8955 but it's not completed, is that correct? Do we know if the eFuse is already blown at this point or not?


I would also like to know this as I just bought a PV:2.0.6717.0 CV:2.0.8498.0 xbox as a possible jtag candidate.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users