Update failure error codes.

nubleet

Senior Member
Apr 5, 2012
129
0
I have a console that was sent to me that is in update loop with the Factory seal in place. Used swizzy's update toolbox to get the proper update to a flash drive. Console began to update, but stopped at around 55% then threw 351f-397f-2600-2515-c000-007f. The update toolbox doesn't know what the error code is but the NTStatus states: STATUS_DISK_FULL. Is this worth getting a nand read to attempt a fix?
 

RhoTrux64

VIP Member
Jun 22, 2004
591
0
I have a console that was sent to me that is in update loop with the Factory seal in place. Used swizzy's update toolbox to get the proper update to a flash drive. Console began to update, but stopped at around 55% then threw 351f-397f-2600-2515-c000-007f. The update toolbox doesn't know what the error code is but the NTStatus states: STATUS_DISK_FULL. Is this worth getting a nand read to attempt a fix?
Put the second set of numbers in a hex converter for the update needed.

Sent from my ASUS Transformer Pad TF700T using Tapatalk
 

alexander_1333

VIP Member
Jan 10, 2012
980
0
Slovakia
In short, you need to convert the error code from hexadecimal to decimal.In your case 351f = 13599, you had this dashboard version when you try to update.397f = 14719 this is the dashboard version that need to be applied.
 

nubleet

Senior Member
Apr 5, 2012
129
0
ya. I have placed dash 14719 on the thumb drive and it tries to update, but fails and throws this error code. Looking like the nand has gone bad? attempting to get a nand read as i write this and it has had SEVERAL errors.
 

alexander_1333

VIP Member
Jan 10, 2012
980
0
Slovakia
Nand can't go bad.What you see are probably bad blocks.Is the correct drive model in this xbox?Is the drive flashed or stock?Have you tried with another HDD?
 

nubleet

Senior Member
Apr 5, 2012
129
0
Xbox had factory seal intact. Drive is stock. Tried with and without HDD. It is a 512 jasper. Here is my J-Runner log: http://pastebay.net/1355888 (won't let me post seeing as it is too long)

I have re-soldered a few times, tried with nand-x and with jrp. I didn't think NAND's could go bad either, but this is changing my mind on it.
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Your consoles nand hasnt gone bad. If it had the system wouldnt even turn on. My advice install rgh to retrieve keys, then build a new retail nand and flash that back to the console.
 
Last edited:

nubleet

Senior Member
Apr 5, 2012
129
0
I would love to. But I cannot get a proper read of the nand. What you have suggested is what I am trying to do.
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
By proper read, do you mean it has bad blocks, or your nand-x/jrp isnt finding the nand at all. because there are guides for both issues. The easier fix is to install the demon, as that connects directly to the chip. Unfortunatly not as easy to remove, so if you do install one you might as well leave your glitch chip installed.
 

nubleet

Senior Member
Apr 5, 2012
129
0
If you look at my j-runner log, it shows that it reads several blocks. It does howevever have SEVERAL read errors. I don't have a demon anymore sadly, and this console is going to be staying stock so I don't feel that a demon is necessary. I can post install pics if needed. Would this be caused by a southbridge issue?
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Microsoft says with that error code the console needs to be returned for service. Also read Martin C's nand-x troubleshooting guide. also post your logs from j-runner.
 

socalbill

VIP Member
Nov 30, 2011
356
0
Valhalla
another thing you can try is to remove the hdd, and format the memory, then try to update it with either the hdd or memory, as it's a hardware fault
 

alexander_1333

VIP Member
Jan 10, 2012
980
0
Slovakia
Another thing you can try is to occupy xbox int. mem. format a USB pen so xbox can see it and update to 14719 from another USB pen.

I know it sounds stupid but on a jasper BB I can't update avatars on the int.mem. only on external USB.
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
sorry i missed the log. it says you had to manually select the nand type. if this is correct check nand-x points with multimeter. if everything checks out with your nand-x points try the resistor shorting method. there are guides on here which explain this method.