Print

[DaddyJ]

XBOX ERRORS!
I'm only going to focus on Error 5,6,7,8,9,13,16, & 21. As these are the most common errors in softmodding. **v1.0 xbox's tend to not have error #'s, I cannot help you on that.

ERROR #5
 Def: HDD not locked

 Reason: A Retail Xbox BIOS cannot boot an Unlocked Hard Drive.

 Solution: Lock the Hard Drive or get a modchip.

ERROR #6
 Def: Cannot unlock HDD

 Reason: The Retail BIOS' Generated Unlock Key didnot unlock the Hard Drive.

 Solution: The Hard Drive should be locked with a unique key generated using the EEPROM & HD Serial. (LiveInfo Beta 3 & XboxHDM v1.9 both have the ability to generate these keys.) This drive is currently not locked with the correct key, unlock and relock with the correct key.

ERROR #7
 Def: HDD timeout

 Reason: The Hard Drive did not respond in the given time.

 Solution: Check the Drives Jumper, make sure its in CS (Cable Select) position. This can also happen if there is a loose connection on the IDE ribbon, or if the drive is physically failing.

ERROR #8
 Def: No HDD found

 Reason: Well this one is self explainatory.

 Solution: Hook a Hard Drive up, in CS (Cable Select) Position.

ERROR #9
 Def: HDD parameters (PIO/DMA/or size {debug}, certain size minimum is required for debug)

 Reason: All I could gather on this, was either the Jumper is in the wrong position, make sure its in CS (Cable Select). Or the Drive Has Phyisically Failed, or the drive has not been partitioned correctly.

 Solution: Make sure you have correctly partitioned your hard drive, and that the cable is tightly connected, trying a new IDE ribbon has also helped.

ERROR #13
 Def: Dashboard launch fail (due to missing/bad key, or anything else that would prevent it from running) and the dashboard didn't specify why it failed.

 Reason: Usually when the dashboard is missing, or a key file is missing. This can occur on new xboxs, when trying to run an old m$ dash.

 Solution: 80% of the time, a Error 13 will boot a retail game. (Usually have to boot, insert game, turn off, then boot again.) If it does, boot either your game & gamesave combo, or run a LIVE enabled game and update your dash to return to retail. If it does not, you will need to hotswap or use your EEPROM to gain entrance.

Dont let your system lose time or you will end up with

ERROR #16
 Def: Other files to do with dashboard / dashboard settings (specific dashboard error)

 Reason: A File that was required by the dashboard is missing, or the dash or dash file has been corrupted.

 Solution: Error 16 will rarely boot a retail game. you will need to hotswap or use your EEPROM to gain entrance.

Note: Error 16 usually seems to occur when the system clock has been lost, this is why it rarely boots orignals.

ERROR #21
 Def: This error says that the machine was booted to display a error, basically someone told the machine to reboot (or launch a xbe) with this flag, and the error code just means its been rebooted by the flag

 Reason: This is a hard error to pinpoint, as it can result from almost anything.

 Solution: Unsigned code is the biggest reason for this error. The rest of them are because of the Softmod using hacked fonts in c:\fonts, or c:\. A game, or menu that looks for the retail fonts, finds the hacked fonts, and ends up in an error 21. This is a safety feature if you will.
Some things to remember about error 21, is to track exactly where it is occuring.

Releated Errors

ERROR #11
This is normally caused by the user that is attempting to hotswap. It Is usually a result of the DVDROM's IDE cable being removed or the DVD drive is physically failing.
ERROR #12
This is normally caused by the user that is attempting to hotswap. It Is usually a result of the DVDROM's IDE cable being removed or the DVD drive is physically failing.

Some added notes about HD Locking.

In order to correctly lock the Hard drive for it to work with YOUR xbox, you will need that Xbox's EEPROM.BIN, this can be obtain using Evox's Backup function. XboxHDM v1.9 & LiveInfo Beta 3 both have the ability to correctly generate a valid locking password for the hard drive in question.

You CANNOT use any EEPROM to lock the Hard Drive for your xbox, it must be that Xbox's EEPROM, NO IF ANDs or BUTs.

[domesticman]

Hey daddyj, thanks for all the info.

I got error 16 on a 1.6 using Slayer's 2.5 for my c: and I was told that Slayer's 2.5 c: is too old for my 1.6 so that's why I got the error. Do you know if Slayer's 2.6 c: files will work? My error 16 was in the crappy 20% that won't boot.

Sorry to bug you but I saw you ask some guy with error 16 and Slayer's 2.5 if he had a 1.6...he didn't so you didn't explain the answer.

Thanks!

[krayzie]

Great job DaddyJ. The n00bz now really get loaded with info. Let's hope they really start lookin before they ask.

And yes you need the new slayer's dash for any kernel higher then 5530.

[Keo-Keo]

Really nice write up daddyj.. I might find myself using this already!.. Thanks!

[DaddyJ]

If your xbox will not boot a retail game, then hotswapping is a viable option, Check My Sig for some FAQ's about hotswapping.

[alaska2k3]

.
 Thanks
-=alaska2k3=-

[DaddyJ]

Updated main post with some more error codes, and updated a few solutions.

[Boooooommm]

Why would you need a friend for hotswapping? All you need is to unplug the DVD drive on your Xbox, Boot the Xbox to error 11 or 12, boot your PC with the XboxHDM disc (with whatever files you believe are corrupted in the C dir) and hot swap the hard drive on the option selection screen. That's as safe as you can actually do it. You'd be able to fix any files that are ruined that way. Just keep your Xbox on in the meantime if you didn't backup the EEPROM.bin to your PC (which you would place in the EEPROM dir on the /linux dir) before this happened. That's all you can probably do to fix your Box up.