Print

[TurnX]

I know this is a fairly common error but I have tried a handful of the common fixes with no luck, so I was hoping that someone here would be kind enough to give me a little direction. First off here are the things I have tried:

1) Hold the sync button while powering up to clear failed updates. (Didn't do anything)
2) Downloaded the 20 or so updates, burned them to CDR, and ran each of them. (Didn't work with any of them)
3) Tried each of the above with/without a HDD attached and with a wired and wireless controller.

This system was given to me by a friend who didn't have the time to try and fix this. According to him his brother was playing some game, doesn't know which one, that error out during play and when he booted the console back up he encountered the "Can't find update, please insert update disk" error message. At this point I am just curious what my remaining options are to try and fix it:

1) Is there something I can run, either a disk or through my pc, that can clear out or flash the failed update so I can start fresh?
2) Would setting it up with a mod chip allow me to bypass the failed update?
3) Is there something else I haven't tried yet that might clear out this error?

If anyone can answer any of the above questions or give me any suggestions I would really appreciate it.

[MadMaxGR]

Did you try to update thru USB flash drive?

[TurnX]

QUOTE(MadMaxGR @ May 23 2011, 04:56 AM)

Did you try to update thru USB flash drive?

I have tried that as well with no luck. Anyone else have any new suggestions?

[kkdd]

QUOTE(TurnX @ Jun 14 2011, 02:29 PM)

I have tried that as well with no luck. Anyone else have any new suggestions?

I have had this problem several times, and like you have tried many update discs with no luck.. but that's only because I didn't find the right update!
What I did was read the NAND (using nand-x), open it up in 360 flash tool, checked the bootloader sections, and whichever was the highest value, that's the update that hasn't been completed. When you know which one it is, just download and burn it to a disc, and reboot the console with the disc inside. It's worked for me a few times now after struggling to find the right update by guessing.

Also just to make sure, are you burning it right? The $SystemUpdate folder should be in the root directory (i.e. d:\$SystemUpdate)

There are 14 "blades" updates, 7 NXE versions and 3 kinect versions. If you know whether you're on a blades, nxe or kinect dash, it might help you narrow it down.

Hope this helps!

*by the way, I've tried it with a USB stick several times, but it just doesn't work with some older dashboards, so using a CDR is your best bet.

This post has been edited by kkdd: Jun 17 2011, 09:15 PM

[TurnX]

QUOTE(kkdd @ Jun 17 2011, 04:14 PM)

I have had this problem several times, and like you have tried many update discs with no luck.. but that's only because I didn't find the right update!
What I did was read the NAND (using nand-x), open it up in 360 flash tool, checked the bootloader sections, and whichever was the highest value, that's the update that hasn't been completed. When you know which one it is, just download and burn it to a disc, and reboot the console with the disc inside. It's worked for me a few times now after struggling to find the right update by guessing.

Also just to make sure, are you burning it right? The $SystemUpdate folder should be in the root directory (i.e. d:\$SystemUpdate)

There are 14 "blades" updates, 7 NXE versions and 3 kinect versions. If you know whether you're on a blades, nxe or kinect dash, it might help you narrow it down.

Hope this helps!

*by the way, I've tried it with a USB stick several times, but it just doesn't work with some older dashboards, so using a CDR is your best bet.

Thanks for the suggestion, I will definitely be giving this a try. Just quick questions:

1) Does the highest value in the bootloader sections directly tie to the number of the update? For example would the value be 2.0.13146.0 or a number that corresponds to an update number?

2) Is there any other device or method for reading the bootloader sections? Reason I ask is the 360 in question is an older unit and I am trying to spend as little as possible to fix it, so while $50 for a Nand-X is doable if there is a cheaper route that would be better.

[kkdd]

QUOTE(TurnX @ Jun 18 2011, 01:42 PM)

Thanks for the suggestion, I will definitely be giving this a try. Just quick questions:

1) Does the highest value in the bootloader sections directly tie to the number of the update? For example would the value be 2.0.13146.0 or a number that corresponds to an update number?

2) Is there any other device or method for reading the bootloader sections? Reason I ask is the 360 in question is an older unit and I am trying to spend as little as possible to fix it, so while $50 for a Nand-X is doable if there is a cheaper route that would be better.

1. yes the highest value is always the failed, or incomplete update, at least in my experience.

2. The cheapest way would be to burn every update to disc, and try each disc several times using different methods (i.e. put in cd, then restart, or put in cd, restart and hold sync button etc). You can only see the boatloader sections by reading the nand. You could try to find a used nand-x online, try ebay or the BST section of this forum or team xecuter. Or maybe someone here will be kind enough to lend you theirs (IMG:style_emoticons/default/smile.gif)

[TurnX]

QUOTE(kkdd @ Jun 18 2011, 12:17 PM)

1. yes the highest value is always the failed, or incomplete update, at least in my experience.

2. The cheapest way would be to burn every update to disc, and try each disc several times using different methods (i.e. put in cd, then restart, or put in cd, restart and hold sync button etc). You can only see the boatloader sections by reading the nand. You could try to find a used nand-x online, try ebay or the BST section of this forum or team xecuter. Or maybe someone here will be kind enough to lend you theirs (IMG:style_emoticons/default/smile.gif)

Since I do have a large spool of CDRs sitting around I think I will give burning the updates one more try and see what I end up with. One final question, aside from the 24 updates you mentioned (14 "blades" updates, 7 NXE versions and 3 kinect versions) are there any other updates I should be looking for? I only ask ebcause I know some games did come with updates, and I wasn't sure if those updates are the same as the general released ones.

[kkdd]

QUOTE(TurnX @ Jun 18 2011, 06:13 PM)

Since I do have a large spool of CDRs sitting around I think I will give burning the updates one more try and see what I end up with. One final question, aside from the 24 updates you mentioned (14 "blades" updates, 7 NXE versions and 3 kinect versions) are there any other updates I should be looking for? I only ask ebcause I know some games did come with updates, and I wasn't sure if those updates are the same as the general released ones.

As far as I know they are the same.. but you'll know for sure once you've tried all the update CD's and it hasn't fixed the problem. It has worked for me every time, and I'm pretty sure the bad updates were caused by game discs in those cases. Good luck!