Ошибка 21 xbox original
Original Xbox Error Codes
Tutorial Name: Original Xbox Error Codes
Date Added: Wed. Sep 22, 2010
Description:
When you attempt to boot, a 'you need service' message comes up, and has a LED style number on the top left hand corner. Here is what they mean.
Disclaimer:
This information is a believed to be correct, should be as close as it gets;
Also:
Bootloader stuff you should never see, since if it fails kernel doesn't boot. (thus you see no message)
Code Who sets it - Description
0 - any - No error (duh)
1 - bootldr - Unknown exactly, something to do with checking the motherboard
2 - bootldr - Eeprom check failed
3 - bootldr - ??/not used
4 - bootldr - Ram check failed
5 - kernel - HDD not locked (retail bioses require the hd to be locked)
6 - kernel - Cannot unlock HDD
7 - kernel - HDD timeout
8 - kernel - No HDD found
9 - kernel - HDD parameters (PIO/DMA/or size , certain size minimum is required for debug)
10 - kernel - DVD timeout
11 - kernel - No DVD Founnd
12 - kernel - DVD parameters (PIO/DMA)
13 - kernel - 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.
14 - dashboard - Error loading dashboard (dashboard generic error)
16 - dashboard - Other files to do with dashboard / dashboard settings (specific dashboard error)
20 - kernel - The dashboard was attempted to load and failed; It was a cold boot, and the dashboard didn't specify why it failed, but it (for some reason) needed to be noted that the dvd passed the challenge/response authentication
21 - anywhere - 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
21 was the highest number I could find, I dont think anynthing is past that. And for the unknown ones, I couldn't find anyreference to them at all, I don't believe they are used.
Acquired an ORIGINAL xbox. When I turn it on, there is a different language with a number at top left, (21). After minor investigation, this is an error code, apparently meaning it's modded. is that right?
If so, what can I do? I am not that savvy with software tools, but I can follow directions. How can I fix this issue? Please Help! Thanks in advanced.
Error 21 is a dashboard error. Supposedly you can load an Xbox Live game and tell it to connect and it will update the original dashboard which will get you back to the stock working state, but that won’t save any softmod that is on there. You’re going to have to get the original dash back on there before you can reapply a softmod to it (just because you need to make sure the exploit save is on the drive and you need to know which one is on there). If there’s a hardmod (which would usually show an extra bit on the splash screen) you can just run Hirens (I think, for some reason I want to say Hexen Boot Disk but I think that’s wrong and I’m on my phone) and it’ll give you the option to reinstall the dashboard.
Also, were at the age when the hard drives are going to start dying of natural causes, so this may be a symptom of that. It’s unlikely, but considering that error 21 is basically “can’t read the dashboard” it’s something worthy of note.
It means something is wrong with the dashboard on your Xbox when it tries to boot. Most likely, somebody tried to softmod it and screwed it up, so it can't boot from the HDD. From what I understand, it may still be able to boot from the DVD drive though (not always). If your lucky, download and burn Hexen 2018 to a DVDR using a utility like ImgBurn. Here's a link. You'll want it anyway, as its a good utility to have on hand for modded systems. Do a slow burn at the slowest speed, to give the drive the best chance at reading it. Also do a verify operation, just to rule out any obvious errors.
If that boots, this should be fairly easy. There is a utility on there for installing a new dashboard (I'd suggest leaving it modded), which should fix the problem. I'll give you more info if you get this far. Don't give up hope if it doesn't work the first time. The drive may have read it incorrectly or you have a bad burn/disc. Reburn it, possibly with different brand DVD R media if possible (some are more crap than others). These DVD drives are pretty old, and don't always work right with official media, let alone modern burned discs. I've had to turn the Xbox on and off when it was midway through copying and restart the process.
Another option is to try and boot an XBL compatible game like Halo 2 and try to update the dashboard. That should at least get you back to stock.
If it still doesn't work, you got your work cut out for you. Best of my knowledge, you will need to hot swap the drive into a PC and reinstall the files that way. Trick is, you'll need a PC with IDE-PATA support. But let's worry about that when we get to that point.
I bought an Xbox from a . "dishonest" person who said it worked perfectly. Surprise!! It doesn't. It immediately gave me an error 21.
I've used XboxHDM and the hard drive is recognized. I can rebuild the hard drive and using xbrowser see that all the files are there. Upon reattaching the hard drive to the Xbox and rebooting, I get error 21 again.
ALSO, the disc drive continuously pops out and won't stay closed.
If it matters, I believe it is a 1.0 Xbox, due to the controller daughterboards.
Any help or thoughts would be appreciated!
Check the clock cap to see if it's removed or it's leaking if it's still there.
Corrosion of the traces near the clock cap can cause the issue your facing regarding the DVD drive tray.
As for error 21 that's an xbe issue usually but maybe the trace damage is causing issue?
good call on the clock cap. it was leaking. cleaned the top of the MB with some vinegar, but haven't checked the underside of the board. Tried booting up, but still got the error and the disc drive still popped in & out. Next step, I'll check the underside of the board and clean that up too. I'll check the traces but honestly I've never seen a corroded trace.
You did make sure to straight up take the cap off, right? Not doubting you. Just want to make sure you get it off so it doesn't leak any more and cause more trouble.
Still giving error 21 after cap removal and cleaning. disc drive still popping out on its own as well. Getting frustrated with it so I'm taking a step away! May start to cannibalize this unit. Like I said, DVD & controller ports to another unit. Can I take the hard drive, rebuild it (again) and put it in a unit that has no hard drive?
Is the Xbox hard-modded with a modchip or a TSOP? Try booting it by holding the power button for 1 second. Some xboxes are modded so that the modchip only activates if you hold the power button.
The disc popping out is a sign the clock capacitor has burst.
another update: I took the daughter board out and plugged it into another 1.0 xbox. Fixed the issues I was having with that. I also plugged the disc drive in and it's still doing the open/close routine. I have already pulled the clock cap on this 2nd xbox, so maybe there's an issue with the drive itself? I had previously soft modded this 2nd xbox, so I know a disc drive has been attached and functioning. Anyways, I've given up on the donor xbox and not sure if I want to keep it for parts or just sell it for parts. Still thinking of rebuilding the hard drive and trying that in another xbox I bought that had no hard drive.
Disclaimer:
This information is a believed to be correct, should be as close as it gets;
Also:
Bootloader stuff you should never see, since if it fails kernel doesn't boot. (thus you see no message)
Error Code 02
Problem: EEPROM check failed. This error is triggered by the bootloader and as a result does not display an error code on screen. You will see the Xbox rebooting and flashing red and green lights (FRAG).
Cause/Solution: You flashed something wrong or caused a short somewhere on your motherboard (possibly while soldering). If you're using a modchip and you just flashed it, try again using a different BIOS. If you recently did some soldering to your Xbox, check for any stray solder balls that may be present and carefully remove them.
Error Code 04
Problem: RAM check failed. This error is triggered by the bootloader and as a result does not display an error code on screen. You will see the Xbox rebooting and flashing red and green lights (FRAG).
Cause/Solution: RAM chip failure. This could be from pins on the RAM chip(s) becoming bridged, possibly from an accidental splash of solder or a failed 128MB RAM upgrade. Remember, electrostatic shock can sometimes damage integrated circuit chips like RAM chips, so even if you can't see a problem, the RAM could still be fried. Replacing the RAM chips could be a solution but is risky and time consuming.
Error Code 05
Problem: Hard disk drive (HDD) not locked.
Cause/Solution: If you have not replaced your Xbox's BIOS via a modchip/TSOP flash, then your HDD needs to be locked using a special password that is generated based on your Xbox's EEPROM, which is unique per each individual Xbox. Microsoft designed it this way to prevent people from being able to plug the drive into a computer and have access to its contents and thus hacking it. Virtually all non-retail BIOSes (including modchip/TSOP) will not require the hard drive to be locked in order to start. If you're seeing this error on a non-retail BIOS, then chances are your modchip/TSOP flash process had issues and for some reason you are now using a stock BIOS which is now requiring a password-locked hard drive again. If you're seeing this error and your Xbox has been softmodded (through gamesave/font/audio expoits), then you just need to lock your drive again. Hopefully you have your EEPROM backed up at this point because if not, things get a lot more complicated. If you unlocked your HDD on the Xbox itself (using ConfigMagic for example), chances are the app you used made a backup of your EEPROM for you and it's now sitting on your E:\ drive called "eeprom.bin" or something similar. You can plug the HDD into a computer at this point and use an Xbox hard drive explorer program like "Xplorer360" (Windows only) to view its files to copy your EEPROM backup. There are multiple ways to lock a HDD, one of which is by using XboxHDM by author ldotsfan. XboxHDM runs on a PC and one of its features is the ability to lock hard drives if you have an EEPROM backup. Choose option "3" from XboxHDM and follow the on-screen instructions to lock the HDD.
Error Code 06
Problem: Incorrect hard drive password.
Cause/Solution: The hard disk drive (HDD) is locked but it is locked with a password that belongs to a different Xbox. You will need to unlock the HDD and then re-lock it using the correct password. As stated above, each Xbox is locked using a password that is generated based on each Xbox's unique EEPROM. Assuming you have the EEPROM of your Xbox backed up, you will just need to unlock the drive and re-lock it using your EEPROM backup. See the solution for error 05 for more info.
Error Code 07
Problem: Hard drive timeout / HDD took too long to become ready.
Cause/Solution: The Xbox seems to know the HDD is present but it times-out waiting for the drive to become ready and respond to commands. This is probably due to a loose connection or faulty wire. See the solution for code 08. Note: If you're using a SATA to IDE adapter, it's possible that the adapter you're using is not compatible with the drive you're using or isn't compatible with the Xbox at all. Try another SATA to IDE adapter / HDD combination. Some "green" drives are temperamental with certain SATA adapters.
- Make sure the IDE ribbon cable (flat grey cable) is securely connected to the HDD, the DVD drive, AND the motherboard itself.
- Check the IDE cable for signs of damage. If the cable looks like it has been scraped or has evidence of any damage then replace it.
- Check the HDD's power cable and make sure it's securely plugged in.
- If you can wiggle the HDD power cable around and make the Xbox work at certain times, then the leads coming from the power supply are loose and the power supply should be replaced.
- Take the HDD out and make sure the jumper is set correctly. There should be a diagram printed on the drive's label that shows how the jumper should be connected. Make sure its set to Cable Select (CS), Master, or isn't present at all. If the drive is set to Slave then you will run into issues!
- If all other cables are in fact securely connected and not damaged, you can try replacing the IDE cable any way. It's possible that it is damaged in a way that isn't visible and IDE cables are cheap to come by.
- If all else fails, your hard drive is probably to blame and is faulty and needs to be replaced.
Error Code 10
Problem: DVD drive timeout.
Cause/Solution: Similar to error codes 07 and 08, this is usually caused by a loose/faulty cable. The Xbox seems to know the DVD drive is present but it times-out waiting for the drive to become ready and respond to commands. Check the yellow DVD cable running from the motherboard to the DVD drive. If all else fails, replace the DVD drive.
Error Code 11
Problem: No DVD drive found.
Cause/Solution: The Xbox cannot find the DVD drive. Similar to error 10, this is usually from a loose/faulty cable. See solutions for error 10. Note: many non-retail BIOSes can configured to skip using a DVD drive entirely.
Error Code 12
Problem: DVD drive parameters are missing or incorrect.
Cause/Solution: Not very common. Try solutions for error 10.
Error Code 13
Problem: Dashboard failed to launch due to missing/bad key, or anything else that would prevent it from running and the dashboard didn't specify why it failed.
Cause/Solution: This can be caused by a kernel version issue but is a lot less common in recent years. Make sure you're running the latest kernel. If you're using a softmod, make sure your dashboard and softmod files are installed correctly. You might have luck using SID5 as your softmod installer if you're using something else currently.
Error Code 14
Problem: Dashboard failed to launch (generic error).
Cause/Solution: Same as error 12 basically. This can also result from changing names of files or messing with files on the HDD without knowing the repercussions. A common cause is from changing the boot orders or names of startup files on the HDD. It can also happen when you are rebuilding your HDD with a Slayer CD and the power was cut.
Error Code 16
Problem: Internal clock cannot be set.
Cause/Solution: This happens when the Xbox tries to boot to the stock dashboard in order to have you set the current date/time but fails to load the menu. This happens people that erase their HDD or stock dashboard files and afterwards don't immediately install the HDD but instead leave the Xbox without power for longer than 5 hours. The Xbox has capacitors in it that allow it to keep its clock set but it only has enough charge for about 3-5 hours before the clock clears and it asks you to set it again. This used to be a more common problem before people figured out how to get around it in later years. Virtually all modern (made after 2005) softmods and non-retail BIOSes will account for the clock reset problem. To fix this, try putting the stock dashboard back on your HDD's C:\ partition. After the Xbox boots up and is able to set the clock successfully, then you can continue on. If you DON'T have an eeprom backup and can't access the hard drive from a PC to put the stock dashboard back on it, then you can do a hotswap to gain access to the drive and continue with copying the stock dashboard over. Once you fix the issue, update your BIOS or softmod to a more recent version to avoid this in the future.
Error Code 20
Problem: Dashboard failed to launch.
Cause/Solution: It was a cold boot, and the dashboard didn't specify why it failed, but it needed to be noted that the DVD passed the challenge/response authentication during boot.
Error Code 21
Problem: Unspecific/generic error.
Cause/Solution: The Xbox was instructed (possibly by an XBE you launched) to reboot the Xbox and display this error. This occurs frequently when the Xbox is unable to boot due to dashboard changes being made (i.e. an XBE hasn't been signed correctly OR parts of the stock dashboard (C:\) are missing. Also, if you're using XbeShortcutMaker and seeing this error code then you might try regenerating the shortcut XBE file as it could be corrupted.
Credit: OCnewB [Xbox-Scene forums] & Superfro [Xbox-Scene forums] for compiling the list. deezp1 [Afterdawn forums] for more compiling and organization. GoTeamScotch [xbmc4xbox forums] for clean-up.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
PneumaticFrog
New member
What's happening here? Original Xbox with Exexutr2 on it. Won't boot games or load the MSdashboard.
PneumaticFrog
New member
Well-known member
HDD going bad maybe? I think bad sectors/read errors aren't covered by 5 through 9. Try a replacement if you have one, or at least a rebuild though even if that works it'll only be temporary.
Should go without saying but backup your shit asap.
PneumaticFrog
New member
HDD going bad maybe? I think bad sectors/read errors aren't covered by 5 through 9. Try a replacement if you have one, or at least a rebuild though even if that works it'll only be temporary.
Should go without saying but backup your shit asap.
Okay thanks a ton. I'll get it backed up tomorrow at my friend's place. Cheers for the help man
Though, how long is temporary do you reckon?
Thanks again ?
PneumaticFrog
New member
HDD going bad maybe? I think bad sectors/read errors aren't covered by 5 through 9. Try a replacement if you have one, or at least a rebuild though even if that works it'll only be temporary.
Should go without saying but backup your shit asap.
Well-known member
Remake the HDD contents from scratch, i.e. recreate the partitions, then put on a fresh copy of all the files. In hopes of any bad parts of the drive being recognized and marked/skipped throughout that process.
Seeing how you apparently can't boot anything, your best bets are a) putting the drive into another Xbox and doing it there (with e.g. the Hexen disc), or b) do it in a PC (with XboxHDM).
Honestly, if your time is worth anything to you, don't bother and just try it with a replacement. (Also, if the HDD turns out not to be the issue, you can just swap the old, untouched drive back in.)
NeC5552
Member
The easiest way out of this is a new IDE (or SATA w/ SATA-to-IDE adapter) drive prepared with Hexen. You already have a Xecuter 2 chip which enables you to boot the Hexen disc, so just pop it in the DVD drive and set your Xbox up the way you like it.
cta - bad sectors aren't covered by any error. E5 and 6 are unlocked (5) and locked (6, locked to wrong Xbox), 7 is HDD timeout, while 9 is DVD timeout. 13 means bad dash files, 16 is can't set clock, and 21 means it couldn't launch the dash properly and showed this error as a result. (it's similar to 20, more or less)
Tutorials Navigation
Tutorials: 18,244 Categories: 12
Total Tutorial Views: 38,573,663
Читайте также: