Post by: OcnewB on February 04, 2004, 05:18:00 AM
because it is getting more and more annoying to explain over and over again
what the most common errors mean.
Thanks to Superfro for the 1st (much too basic) list.
I thought the list was sort off too basic and to short to be newbie friendly so lets try and see what I can make of it.
Beware, you wont see the bootldr error's because (thanks to: Lordvader129) : "when you see this" is not entirely accurate, you never see the bootloader errors, as they are one that cause the reboot/FRAGs
2 - bootldr - Eeprom check failed
[Details]
When you see this error most of the times you have flashed something wrong. Or you dropped solder on your eeprom chips.
[/Details]
4 - bootldr - Ram check failed
[Details]
Your Xbox ram chips are wasted.
Maybe you dropped a little solder on it (try to remove it CAREFULLY!). Note, if they are fried, removing solder won't fix them). Maybe you were static when you touched the ram chips. They are kind off sensitive. If they are, they are fried, sell your xbox for spare parts to me
[/Details]
5 - kernel - HDD not locked (The retail xbox bioses require the hd to be locked)
[Details]
When you upgrade your hard disk drive for one that is larger, you most of the times use a new hard drive that you bought in the shop. Now, when you put this hdd in your xbox and you try to boot up with your chip off. It gives you error 5. Why you ask? Well i will try to explain it simple.
The original (also called "Retail") hard drive is locked by MS. Why did they lock the harddrive?
Well if it wasn't it wouldve been more than easy (in the start of xbox hacking)
for hackers to change content on it. Thats why MS locks it. It is just a security measure.
This locking proces uses information thats on the motherboard. The "Lock" on a xbox hard drive contains information that is based on the harddrive itself and the motherboard it came with.
One thing that makes this clear: You can not change a retail harddrive with another one from an other not modded xbox. With every xbox there is only ONE i repeat ONE compatible harddisk drive. That is, if they are locked.
If you don't mod your xbox (tsop or modchips) you can not change harddrives. Not even from another xbox. However when your xbox IS modified you can change your harddisk for almost every other harddisk (thats UNLOCKED). This means that even when your xbox is modified, you can not just put another (retail) XBOX harddisk in your xbox. However some smart people made programs that can lock or unlock your xbox harddisk on the fly.
So when does the error occur? The only time this error should occur is when you boot up your xbox in original mode AND you have a harddisk in your xbox that is not yet locked. So now you ask what do i have to do to make your xbox work again?
Well the answer is pretty easy. Boot up your xbox with the chip on. Preferably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"
When it is "Done" just turn off your xbox. Disable your chip and try to boot in original mode. Now there should be no more error 5.
[/Details]
6 - kernel - Cannot unlock HDD
[Details]
If you understand the above, you should be able to understand what this means. It means you are trying to boot up the xbox with an harddisk that is locked in combination with ANOTHER motherboard than you are using it with right now.
What can i do about it, you ask? Well place the harddisk back in the xbox where it came from. After that, UNLOCK the harddisk with the same procedure i explained above (see error 5). Now when the harddisk is UNLOCKED, put it in the xbox which gave you the error. Now when you boot up with the chip ON it should not give you an error anymore.
However when you put the xbox on with the chip OFF your xbox will give you an error. (error 5) So to make sure you can boot original and boot with the chip ON. Next do the same as above: "Boot up your xbox with the chip on. Preferrably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"
When it is ready just turn off your xbox. Disable your chip and try to boot original. Now there should be no more error.
[/Details]
7 - kernel - HDD timeout
[Details]
Most of the times, the IDE cable is not properly connected when you see this error. Please reattach the ide cable. Not only to the harddisk drive but also to the dvd drive. ALso try to reconnect the ide cable to the motherboard.
Press pretty hard so it goes all the way in. Make sure it is seated straight and proper in the drives and the motherboard. If you still have an error 7. Try another ide cable. If that won't work try another harddisk. If there is still no go, try to set the jumpers on the rearside of the harddisk drive. Set it to master or cable select. If still no succes, good luck and sell your xbox to me
[/Details]
8 - kernel - No HDD found
[Details]
Please make sure your xbox hdd is attached properly. Most of the times the Ide cable came loose, or isn't seated properly in the IDE port of your harddisk. ALso make sure the power supply cables are intact and working.
Make sure the ide cable is also connected properly to the rest of the hardware (dvd and motherboard).
[/Details]
9 - kernel - HDD parameters (PIO/DMA/or size {debug}, certain size minimum is required for debug)
[Details]
Not very common error, please try another harddisk.
[/Details]
10 - kernel - DVD timeout
[Details]
Actually its almost the same as error 6/7/8. But also make sure the yellow cables are properly connected to the motherboard and the dvd drive.
1. Make sure ide cables are connected good.
2. Make sure the yellow cables are good and properly connected.
3. Still no succes? Try another dvd drive of which you are sure it is working.
[/Details]
11 - kernel - No DVD Founnd
[Details]
Same as #10 So read up please!
[/Details]
12 - kernel - DVD parameters (PIO/DMA)
[Details]
Same as #10, only not very common.
[/Details]
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.
[Details]
This is an error thats most common when you have changed something on your xbox harddisk drive for whatever reason you had, but did not do it properly.
So what to solve it? Well, try to rebuild you xbox harddisk (retail or upgraded/large)
with a slayer 2.6 cd.
(BUT WATCH OUT READ MORE ABOUT THIS ERROR 13 BEFORE YOU DO THAT!) .
The thing you should understand is that error 13 is only because something is wrong with the files on your xbox harddisk.
UPDATE: Recently more and more xbox's that i started modding were giving me an error 13 when i booted in original mode. So what the hell was going on. Solder work was great, the slayer cd was also working great.
However i started doing some research and i finally figured it out. The error it gives is because of the incompatibility between the (older) dashboard (4920) that older slayer cd installs and the new dashboard/kernel versions found in some new xbox's and found in xbox's that have been connected to xbox live (when you go on xbox-live, it'll upgrade your dashboard file to i believe it is now 5659.03. This dasboard is incompatible with the dash that (old) slayer cd installs (for example 2.5 or lower) for you.
(In detail, in the eeprom chip there is a kernel which is incompatible with the dashboard (4920) that slayer installs.)
So what do you do to fix it? Well, it's easy. Someone may know how to do this more easy but this is how i did it. I got myself an xbox of a friend that has xbox live. His xbox is modified and runs a executor chip. I checked his dashboard version and i saw it was the latest 5659.03 dashboard. So i connected his xbox to my computer and i transferred his complete c:\ partition to my computer. Than i connected the xbox that gave me an error 13 when booting original, to my computer. AFter that i transferred "his" c:\ partition to my own c:\ partition, when it asked me to overwrite i chose all. After transfer was done, i rebooted the xbox. And voila no more error 13. The incompatibility was gone.
I think you have to transfer all the xboxdash files and also the xboxdashdata (or something like that) folder. In case you hate to experiment, just transfer the complete c:\ partition of a fairly new or upgraded xbox to your c:\ partition and overwrite all.
Ah well, hope it helps someone.
*UPDATE*
It seems there is an easier solution. You can use the dashupdate found on most new xbox games! Be sure to 1st unplug your ethernet cable before you do so!!!
Also see this post:
http://forums.xbox-s...0
*UPDATE2*
Besides that, just use a good installation disc and all is fine. Use a 2.6 slayer or something similar
[/details]
14 - dashboard - Error loading dashboard (dashboard generic error)
[Details]
Same thing as above (error 13). This time it is also a little mistake from you on changing names or having played around with files on the xbox harddisk. Error 14 is most often because you changed boot orders or names of startup files on the harddisk. It can also happen when you are rebuilding your xbox harddisk with a slayer cd and the power was cut.
[/Details]
16 - dashboard - Clock cannot be set. Well i wrote earlier another tutorial about this specific error so here it is:
[Details]
Basically it comes down to this. Error 16 has to do with not finding the menu setting with which you can set the clock of the hdd. This happens to a lot of people that erase their hdd (original/upgraded) or MS dashboard files and after that they don't immediatly install the hdd but leave the xbox without power longer than 5 hours.
It's all about the hdd can't find the menu with which it can set the clock. This is mostly because the xbox hdd is empty (you removed dashboard or fux0red it via ftp). The problem arises when xbox searches for menu to set clock with, can't find it and voila: error 16. Well read on please!
So you have an error 16 huh? Don't worry "nothing" is broken!
You have an xbox hdd that is locked. And normally you can boot in original and modded mode. Retail or upgraded doesn't matter. You start playing around with xboxdash.xbe etc. using ftp programs. While doing this you "accidently" remove your MS dashboard and also your alternate dashboard (Evox, etc.) so there is no dash anymore on the xbox hdd.
You end the ftp session and after that you shut off your xbox. Normally when you would start up again it gives you an error 13/14 ( no dashboard found). No worries with a slayer Evox cd (and a hardmod), all is ok. BUT this is only WITHIN 3 hours or so.
This is because the internal clock of the xbox will only be kept alive by the capacitors for only 3 or 4 hours. So when you leave your xbox unplugged from electricity for over 5 hours after you have played with the .xbe's AND you have removed your (ms and evo-x) dash from your xbox than you are fux0red. Why do you ask?
Why can't I boot from disc?
Its as follows Xbox starts booting==> (almost 1st thing a xbox does is) searches for internal clock==> doesnt find internal clock because there hasn't been any electricity on the xbox for 5 hours so battery that kept clock alive is empty and clock is gone==> searches for the proper dashboard menu to set clock with ==> doesnt find msdashboard or evo-x dashboard menu becuz you have removed it from the hdd for whatever reasons you had==> xbox gives error 16: cannot set clock.
So what do you do about it? Two options!
1. There are some bios'es around that allow the chip to boot past the clocksetting. (do a search!). So how do you get that bios on your chip because you cant boot to a flash program or something? Well you need to have an external flasher.
It seems the m8 bios will take care for you of booting past the clocksetting. Or use the latest Xecutor bios
2. This is the more easy and newbie friendly strategy
-Get a friend with a modded xbox.
-Unlock his hdd with eeprom management from a slayer evo-x cd.
-Than, place his hdd in your xbox.
-Boot with your chip on.
-Now the xbox DOES find a dashboard when you boot in original mode and you can set the time in the msdashboard clock settings.
-Shut off xbox and remove your friends hdd
-PLace his hdd back in his xbox and lock it again
-Install your hdd
-(clock has been set) So boot up with slayer cd.
-Install normally whatever you wanna install
-lock hdd
If you get an error 13 after this, please read up on the error 13 explanation!
[/Details]
20 - kernel - The dashboard was attempted to load and failed
[Details]
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
[/Details]
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
[Details] With thanks to "bleugh"
This occurs frequently when the xbox is unable to boot due to dashboard changes being made (ie Gcue true blue hasnt been resigned, parts of the stock dash are missing - incomplete FTP backups copied to a new HDD for example).
See also this topic:
http://forums.xbox-s...howtopic=287760
[/Details]
I am not responsible for whatever happens to your xbox when following my advice. It's just what i found to be working so don't blame me when you kill your xbox.
Without this your xbox would also be dead so... Have fun and good luck
I Hope this is helpfull and it will end the endless error this error that topics.
Cheers
OcnewB
Post by: SheepshanK on February 05, 2004, 04:27:00 AM
Words like fucked dont iritate me but sticky's normally dont have em ?
Good job tho
Post by: SKllZ on February 05, 2004, 04:33:00 AM
Post by: OcnewB on February 05, 2004, 04:53:00 AM
Thats what i mean. People dont search or do some work , they expect simple ready answers to any question they throw at you. I won't spare my time for them if they won't even take the time to do some work themselves.
Post by: SKllZ on February 05, 2004, 04:57:00 AM
Post by: bleugh on February 05, 2004, 11:09:00 PM
the language needs to be revised a little, otherwise its excellent,
a good suggestion for Error 21
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
this occurs frequently when the xbox is unable to boot due to dashboard changes being made (ie Gcue true blue hasnt been resigned, parts of the stock dash are missing - incomplete FTP backups copied to a new HDD for example)
some common occurances of the faults would be usefull!, everone post in when you got the errors, what you did before the error and how you cured it!
OCnewb why not post this as a tutorial?
Post by: OcnewB on February 05, 2004, 11:52:00 PM
Thanks for you suggestion, i will add it.
Post by: Renthal on February 06, 2004, 10:52:00 AM
If you are getting one of these errors and cannot fix it, please don't try to sell your Xbox as a working Xbox. Sell it for parts.
Post by: nobodyimportant on February 06, 2004, 11:05:00 PM
Post by: lordvader129 on February 06, 2004, 11:16:00 PM
| QUOTE (OcnewB @ Feb 4 2004, 09:18 AM) |
| 2 - bootldr - Eeprom check failed [Details] When you see this error most of the times you have flashed something wrong. Or you dropped solder on your eeprom chips. [/Details] 4 - bootldr - Ram check failed [Details] Your XboX ram chips are wasted. Maybe you dropped a little solder on it (try to remove it CAREFULLY!), or maybe you were kinda static when you touch the ram chips. They are kind off sensitive. If they are, they are fried. Sell your xbox [/Details] |
"when you see this" is not entirely accurate, you never see the bootloader errors, as they are one that cause the reboot/FRAGs
Post by: munificent on February 07, 2004, 02:56:00 AM
I think this topic deserves to be pinned - it would have saved me a lot of hunting around.
Post by: OcnewB on February 09, 2004, 06:16:00 AM
Post by: Revolg on February 09, 2004, 07:04:00 AM
Post by: perry2175 on February 10, 2004, 08:37:00 AM
Post by: Exobex on February 10, 2004, 09:24:00 AM
| QUOTE (perry2175 @ Feb 10 2004, 05:37 PM) |
| Error seven you say try another HDD.. how would you do this if the point of the error is you're drive won't work ? |
Easy. You remove the drive that's not working. Then you fit a drive that IS working.
The key word here is try another HDD. Not the same one.
Post by: perry2175 on February 10, 2004, 01:12:00 PM
| QUOTE (Exobex @ Feb 10 2004, 07:24 PM) | ||
Easy. You remove the drive that's not working. Then you fit a drive that IS working. The key word here is try another HDD. Not the same one. |
Yeah but that's providing you saved a copy of the eeprom.
Post by: OcnewB on February 11, 2004, 01:04:00 AM
| QUOTE (perry2175 @ Feb 10 2004, 11:12 PM) | ||||
Yeah but that's providing you saved a copy of the eeprom. |
Ehm, no. you just hook up an empty new harddrive and boot up with slayer cd. Point is that you just have to make sure it is not your harddrive that is dead.
Post by: bleugh on February 11, 2004, 02:53:00 AM
Post by: OcnewB on February 11, 2004, 03:49:00 AM
| QUOTE (bleugh @ Feb 11 2004, 12:53 PM) |
| keep bumping this, it's a MUCH better description set than the one thats i the tutorials |
Thank you, it did cost me some time to write but if i can make people happy.
I'll have a go on it :-)
I wrote it because i hate to answer the same question (error code X!?) over and over again and it has to stop!
Post by: OcnewB on February 12, 2004, 01:12:00 AM
Every day i see 5 or more new: "error X please help me " posts. PIN THIS PLEASE, because i refuse to help people that wont use a search or something!
Post by: OcnewB on February 15, 2004, 02:27:00 AM
Post by: networkBoy on February 15, 2004, 08:35:00 AM
I've got a box that with the OEM drive gives an error 7 (drive dead?) but when swapped with a 60 gig maxtor (which runs fine in any other box I have) it gives an error 9.
Any thoughts (beyond try another drive)?
-nB
Post by: ole_gab on February 26, 2004, 04:40:00 AM
XBMediaplayer started giving me "Error Code 21" every time I played Audio CD og DVD. Uppgraded to XBMplayer 2.4, still same problem. Uppgraded with Slayers EvoX 2.5 and still have the same problem. (MS Dashboard also bootes to Error 21).
Anny good ideas???
Post by: bleugh on February 27, 2004, 12:53:00 AM
what mod chip do you have?
how is evox installed (if at all?)
could be that your xboxdash is renamed to something else,
you need to have a bios that boots a different name other than msxboxdash first and leave the stock dash well alone!
Post by: enginenerd on March 07, 2004, 06:41:00 PM
However, no error codes are displayed.
Any advice? I don't think it's error 16 because i can still boot to evox with the chip on and it gives me a clock readout.
Is it possible that the M$ dash should be named xboxdash.xbe rather than msxboxdash.xbe and the evox dash should be evoxdash.xbe in lieu of xboxdash.xbe.
Is this a function of the latest version of evox and it's possible that I used an old tutorial which indicated changing the the file names?
If I do need to change the file names as shown above, can it be done directly in FlashFXP? That would be a great easy fix.
Thanks all for the great posts.
Post by: cap269 on March 07, 2004, 07:35:00 PM
Post by: enginenerd on March 08, 2004, 01:08:00 AM
I'll give it a look.
Post by: dark_shadow on March 08, 2004, 02:00:00 AM
| QUOTE |
| 12 - kernel - DVD parameters (PIO/DMA) [Details] Same as #10, only not very common. [/Details] |
Not very common... And now I'm the one with the error
I can only boot from retail bios and can't open the drive...
I'll check the cables or swap the drive when I'm back from school. Hope I can get it fixed.
Post by: SEPHZAI on March 08, 2004, 09:35:00 AM
Post by: seriouslysilly on March 08, 2004, 04:58:00 PM
Will save hundreds of people many hours in trying to search in the forums for explanations
Post by: OcnewB on March 18, 2004, 04:03:00 AM
Post by: Boomhower on April 10, 2004, 12:47:00 AM
Post by: lookformeb on April 10, 2004, 10:22:00 AM
Post by: gen2_rx7 on April 18, 2004, 11:55:00 AM
New to xbox modding, not computers. very similar stuff.
xecuter 2.3b lite+
Xbox ver 1.1 (bought it a month ago is that weird that i got a 1.1?)
samsung dvd drive and retail HDD
Post by: EZYESS57 on April 18, 2004, 07:29:00 PM
Post by: OcnewB on April 25, 2004, 10:47:00 AM
Maybe it'll help someone. It has been bugging me now for a while and i finally fixed it.
So, read up!
Post by: OcnewB on May 07, 2004, 03:24:00 AM
Post by: Jake Reef on July 08, 2004, 11:12:00 AM
Call M$ screen without an error number. The box has never been modded, the idecable is tite, i even replaced the cable...nothing.
Post by: aquiesce on July 15, 2004, 08:18:00 AM
Thanks
Post by: jokker on July 16, 2004, 06:49:00 PM
| QUOTE (networkBoy @ Feb 15 2004, 06:35 PM) |
| so what would you make of an error 9 on a known good drive? (put the drive in another box and it boots fine). Just curious 'cause you don't say much about it. I've got a box that with the OEM drive gives an error 7 (drive dead?) but when swapped with a 60 gig maxtor (which runs fine in any other box I have) it gives an error 9. Any thoughts (beyond try another drive)? -nB |
Yeah i have a very similar problem....
I had put in a 20gig Maxtor in my xbox (1.3, x2.3mod) and it all worked fine then all of the sudden (after couple days) it started giving me Error 9 everytime. If i put the original seagate in it not a single problom.
And you cant boot from the DVD drive if you get this error 9 so I cant test the drive in the Xbox anymore.
Hooked up to a pc the Maxtor works perfectly fine, full format and bad sector scan reveals no problems...but in an xbox i got nothing...
anyone else have thoughts or this problem?
-jokker
Post by: Hitmanfq on September 07, 2004, 08:14:00 PM
Post by: S1lenT_X on September 07, 2004, 10:03:00 PM
Post by: OcnewB on September 08, 2004, 04:39:00 AM
| QUOTE (S1lenT_X @ Sep 8 2004, 06:06 AM) |
| Yay! Added under the general hardware faq pin!! Great job Ocnewb. I was especially grateful for the error 16 explanation. Very nice, and easy to understand!! Thanks *thumbs up.* |
Welcome :-) Always glad to help some ppl.
This forum has helped me also a lot of times :-)
Post by: darkplayer on September 26, 2004, 01:05:00 AM
First box frags red/green with no error #, with and with out the IDE connected. Can you guys give me a hint. I read that the eeprom may be bad?
Second box, frags red/green with an error 7. I managed to trouble shoot it to the hard drive with a known working pc HDD that gave me a different error #. I think I read that I have to burn a slayer disk and boot the box up with a modchip? I just downloaded slayer v2.6, will burn a disk and install matrix and see if it works out.
Also, did my first dvd (SD616T) mod. Powers up nicely and the ejects perfect. Can't wait to see if it works. Not bad for my first soldering job.
Post by: darkplayer on October 01, 2004, 03:27:00 AM
| QUOTE (darkplayer @ Sep 26 2004, 09:08 AM) |
| Second box, frags red/green with an error 7. I managed to trouble shoot it to the hard drive with a known working pc HDD that gave me a different error #. I think I read that I have to burn a slayer disk and boot the box up with a modchip? I just downloaded slayer v2.6, will burn a disk and install matrix and see if it works out. Also, did my first dvd (SD616T) mod. Powers up nicely and the ejects perfect. Can't wait to see if it works. Not bad for my first soldering job. |
Got the second drive working
Modchip & slayer 2.6 took care of my fragging problems.Having trouble with the modded sd616. The soldering went fairly easy. Might have to open her right up and expect my soldering.
Post by: darkplayer on October 03, 2004, 09:13:00 PM
| QUOTE (darkplayer @ Oct 1 2004, 11:30 AM) |
| Got the second drive working Modchip & slayer 2.6 took care of my fragging problems. Having trouble with the modded sd616. The soldering went fairly easy. Might have to open her right up and expect my soldering. |
Easy fix for my dvd drive, HDD must be set as a mster & DVD selected as slave. How sweet it is.
New delima, dvd was working just fine then, stopped ejecting. Everything works fine, even the games wil load up but the tray just doesn't want to eject. Found out a number of people are getting the same problem.
what to do
Post by: OcnewB on October 04, 2004, 12:48:00 AM
| QUOTE (MatthewDavidson @ Oct 1 2004, 10:46 PM) |
| I have done an incredible job at trashing my XBox. My problem as it stands now is that I can't get any hard drives to work in my Xbox. I was stupid and started by reformatting my hard drives, but then I decided to flash a new BIOs. So then, of course, when I try to boot the system up I get nothing. I can't boot with my chip on at all; it just frags. But if I put in my friends hard drive from his modded XBox, I still get Error message 5 or 6, depending on which lock/unlock operation I just did. So I can't get far enough to fix my Error 16 message. Can anyone offer me any help? |
If his drive is unlocked it should boot in your xbox when you have your modchip enabled. Then you should be able to solve error 16. After that you can install every hdd in your xbox.
It seems your chip isnt working. If it gives you error 5 or 6 it means the chip is not working. Cuz every modded xbox will boot past a not locked (unlocked) drive.
Post by: OcnewB on October 04, 2004, 12:13:00 PM
| QUOTE (TB2ZI @ Oct 4 2004, 09:24 AM) |
This thread got a place in my Sig, Good work  |
Your welcome!!
Post by: westrick on October 05, 2004, 08:22:00 PM
Post by: bleugh on October 09, 2004, 02:45:00 AM
WTF is going on?
Post by: OcnewB on October 11, 2004, 05:09:00 AM
| QUOTE (bleugh @ Oct 9 2004, 10:48 AM) |
| ............Mods, is this ever going to be pinned or linked to?, what kind of arsey policics is going on here, its a far superior description than any other crap out there WTF is going on? |
Thx bleugh, however this topic is already pinned in the general hardware section a while ago, But somehow people just do'n't seem to find it and keep on asking the same questions over and over.
If you wanna know the link here it is to the pinned topic:
http://forums.xbox-s...howtopic=241773
But thx for your support.
Post by: OcnewB on October 21, 2004, 05:32:00 AM
| QUOTE (soulrebel @ Oct 21 2004, 02:12 AM) |
| Im in desparate need of help. Im always playing games from my hd and dvds with no problem what so ever. Today I copied Def Jam to my hdd(hdd retail) and played it for about 3 hours. I wanted to play again but when I start up my xbox I get the "xbox needs serviced" screen with the 09 error on the left of the screen. I unplugged the xbox from the power and re-plugged it and the message dissapeard and went straight to evox. So i went on and started up Def Jam 2 from my hdd. but before the "enter start" screen I got an DD error. Restarted my xbox and again I get the 09 error. So I tried to delete the def jam game from my hd (via FTP) but it cant be deleted, like its in use or something, all the subfolders and files are deleted but the main file not. Now my dvd drive isnt working either and I get the 09 error and sometimes the 21. Im stil using th retail hdd and everything was working perfectly before I backed up Def Jam 2. I think the problem is that i went to dvd2xbox (without a cd in the tray) and pressed A-button( coppy dvd to hdd with the tray empty) instead of the B-button(browse hdd). My xbox froze and Im gettin al this mess since then. |
Id try to reinstall the haddrive with slayer 2.6
so it will reformat your hdd.
Goodluck
Post by: soulrebel on October 21, 2004, 09:48:00 AM
But I decided to put a new hdd (seagate 80 gb). But the problems is when I ver I try to boot with evox cd and the new hdd I get the 05 error, but im not booting with the modchipp off.
I tried hotswapping but after the formating procedure i still get the error 5.
Post by: spare72 on November 01, 2004, 09:36:00 AM
Check your power supply and the power wires running to the pack. I have a instance where the power pack had a loose wire suppling power to the HD and it would work sometimes. Normally I would take it apart it would work and once back together it would die.
Post by: SxualVnilla on November 16, 2004, 02:03:00 AM
Post by: Tipster on December 25, 2004, 10:05:00 PM
Post by: Mohnsy on January 01, 2005, 11:48:00 PM
xbox=253$
modchip instaled=40$
hard drive=140$
not paying for a game for the rest of my xbox life=priceless
Post by: blah101 on January 28, 2005, 06:35:00 PM
Post by: raven_xbe on February 20, 2005, 05:17:00 PM
Post by: kneehighspy on March 06, 2005, 11:58:00 AM
//kneehighspy
Post by: nickels on March 22, 2005, 02:02:00 AM
Post by: seriouslysilly on March 22, 2005, 06:10:00 AM
QUOTE(OcnewB @ Feb 4 2004, 07:24 AM)
Ok there we go. I hope this WILL get PINNED on most (all?) of the forum sections
-
Title: A Lot Of Errors Explained In Detail!
Post by: EAgle_47 on March 28, 2005, 11:08:00 PM
-
So.. what is error 13??
just kidding, great tut thx to u eh! and the other who participated to this tut (if there are any) for error 13 im going to try another way to get past through and I'll tell ya if it works 
-
Title: A Lot Of Errors Explained In Detail!
Post by: Jintao on March 30, 2005, 04:24:00 AM
-
ok...just so i got this straight...the only way to fix an error 9 is to get a new HD ? or is it being locked the problem ?
-
Title: A Lot Of Errors Explained In Detail!
Post by: OcnewB on April 01, 2005, 05:16:00 AM
-
Post by: EAgle_47 on March 28, 2005, 11:08:00 PM
just kidding, great tut thx to u eh! and the other who participated to this tut (if there are any) for error 13 im going to try another way to get past through and I'll tell ya if it works
Post by: Jintao on March 30, 2005, 04:24:00 AM
Post by: OcnewB on April 01, 2005, 05:16:00 AM
QUOTE(Jintao @ Mar 30 2005, 11:30 AM)
ok...just so i got this straight...the only way to fix an error 9 is to get a new HD ? or is it being locked the problem ?
-
Title: A Lot Of Errors Explained In Detail!
Post by: Jintao on April 02, 2005, 03:15:00 PM
-
ok, so error 9 means there's something wrong with the HD itself ? yer explanation says something about size. would that be the size of the HD ? wouldn't make sense to me since the retail hd is only 10gb (i think/heard). any chance it could just be the model of HD i have ? it's a 40gb AT Maxtor D740X-6L. it's also several years old. might that have something to do with it ? basically, can i do anything with this HD or do i need a whole new one ? thanks.
-
Title: A Lot Of Errors Explained In Detail!
Post by: Jintao on April 04, 2005, 07:44:00 PM
-
just a little bump. this thread's foundation is eroding away. eroooding, eeeerrrroooddddiiiinnnggg...
-
Title: A Lot Of Errors Explained In Detail!
Post by: Jintao on April 07, 2005, 04:12:00 PM
-
bump again. seriously, this answer depends whether i spend $40, or $240
. i'd really appreciate an answer...thanks
-
Title: A Lot Of Errors Explained In Detail!
Post by: garyopa on April 07, 2005, 06:02:00 PM
-
Error Code 9 - Can be only one of the three problems below:
1: Bad Hard Drive
2: Bad IDE Cable
3: Low 12volt Power
-----------------
Very Simple Solutions:
Install a new hard drive.
Try a replacement IDE cable.
Check for only 10volts on the 12volt (Yellow) cable going to the hard drive.
(If so, adjust the small pot at the front of the power supply unit, just a hair)
-
Title: A Lot Of Errors Explained In Detail!
Post by: phatspade on May 05, 2005, 09:21:00 PM
-
i just had a code 9 and i found out it was caused by where the jumper was placed. make sure u have ur HD as cable select or master otherwise u get a hardware conflict since ur dvd drive is set as a slave.
-
Title: A Lot Of Errors Explained In Detail!
Post by: Lvskapunk on May 19, 2005, 04:13:00 PM
-
For the error number 5, you said to boot it up with a Slayer Evox CD. Are you referring to a SlaYer's EvoX Auto-Installer? I want to make sure I turn the system on with the correct CD in as to avoid any problems.
-
Title: A Lot Of Errors Explained In Detail!
Post by: thesideinguy on June 08, 2005, 09:52:00 PM
-
bump.
-
Title: A Lot Of Errors Explained In Detail!
Post by: Reptile007 on July 08, 2005, 11:10:00 AM
-
I am getting a error 16, I have tryed booting off a unlocked hdd out of another xbox and still getting error 16.
I then put the harddrive from the non-working xbox into the working xbox and it booted up the the evo-x the was on the drive out of the xbox giving me the error 16.
Any ideas guys?
Thanks
-
Title: A Lot Of Errors Explained In Detail!
Post by: thesideinguy on July 13, 2005, 06:33:00 PM
-
woops..
-
Title: A Lot Of Errors Explained In Detail!
Post by: garyopa on July 13, 2005, 07:07:00 PM
-
-
Title: A Lot Of Errors Explained In Detail!
Post by: OcnewB on August 18, 2005, 04:15:00 AM
-
Post by: Jintao on April 02, 2005, 03:15:00 PM
Post by: Jintao on April 04, 2005, 07:44:00 PM
Post by: Jintao on April 07, 2005, 04:12:00 PM
. i'd really appreciate an answer...thanks
Post by: garyopa on April 07, 2005, 06:02:00 PM
1: Bad Hard Drive
2: Bad IDE Cable
3: Low 12volt Power
-----------------
Very Simple Solutions:
Install a new hard drive.
Try a replacement IDE cable.
Check for only 10volts on the 12volt (Yellow) cable going to the hard drive.
(If so, adjust the small pot at the front of the power supply unit, just a hair)
Post by: phatspade on May 05, 2005, 09:21:00 PM
Post by: Lvskapunk on May 19, 2005, 04:13:00 PM
Post by: thesideinguy on June 08, 2005, 09:52:00 PM
Post by: Reptile007 on July 08, 2005, 11:10:00 AM
I then put the harddrive from the non-working xbox into the working xbox and it booted up the the evo-x the was on the drive out of the xbox giving me the error 16.
Any ideas guys?
Thanks
Post by: thesideinguy on July 13, 2005, 06:33:00 PM
Post by: garyopa on July 13, 2005, 07:07:00 PM
QUOTE(jerunh @ Jul 6 2005, 07:30 PM)
Post by: OcnewB on August 18, 2005, 04:15:00 AM
QUOTE(Alucard7 @ Aug 15 2005, 03:02 AM)
Alright sorry for this question but I've searched far and wide and haven't been able to get an answer. Anway I have a v 1.6 xbox (not modded ) and the original hdd from my old v 1.4 xbox(which I messed up). I don't have the hdd to the v 1.6 xbox either. But the problem is that when I try to boot it up normally I get error 6. So I tried putting my old hdd from my computer in there and got error 16. I understand what both the error codes mean I just don't know what to do because I don't have the xbox modded and I don't have a eeprom backup on my computer either. But I do have an X3ce modchip on the way, that I wanted to mod it with. I was just going to mod the xbox and see what I could do from there but if someone could explain to me what I should do, that would be awesome, because I've already messed up once before(with my 1.4 xbox).
-
Title: A Lot Of Errors Explained In Detail!
Post by: knoxrox on September 09, 2005, 02:17:00 PM
-
could somebody please tell me what i have to do to get this working i have MA. The Save.I put it in and do as instructed to go to campain and once i click on that it goes into error 21 screen i do not have a mod chip im kinda new at doing this too
-
Title: A Lot Of Errors Explained In Detail!
Post by: OcnewB on September 12, 2005, 03:48:00 AM
-
Post by: knoxrox on September 09, 2005, 02:17:00 PM
Post by: OcnewB on September 12, 2005, 03:48:00 AM
QUOTE(knoxrox @ Sep 9 2005, 10:28 PM)
could somebody please tell me what i have to do to get this working i have MA. The Save.I put it in and do as instructed to go to campain and once i click on that it goes into error 21 screen i do not have a mod chip im kinda new at doing this too
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on September 12, 2005, 04:04:00 AM
-
Post by: ferrari_rulz_02 on September 12, 2005, 04:04:00 AM
QUOTE(OcnewB @ Sep 12 2005, 08:59 PM)
I don'nt know what the hell youre talking about:
-
Title: A Lot Of Errors Explained In Detail!
Post by: OcnewB on September 13, 2005, 06:07:00 AM
-
Post by: OcnewB on September 13, 2005, 06:07:00 AM
QUOTE(ferrari_rulz_02 @ Sep 12 2005, 12:15 PM)
neither do i.
-
Title: A Lot Of Errors Explained In Detail!
Post by: OcnewB on September 13, 2005, 08:18:00 AM
-
Sorry for bumping but i just noticed this topic has been viewed more than 25.000 times!
Thats quite nice for something i wrote in an hour or two.
It's a shame I can't edit the startpost anymore though... (mods?)
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on September 14, 2005, 03:57:00 AM
-
Post by: OcnewB on September 13, 2005, 08:18:00 AM
Thats quite nice for something i wrote in an hour or two.
It's a shame I can't edit the startpost anymore though... (mods?)
Post by: ferrari_rulz_02 on September 14, 2005, 03:57:00 AM
QUOTE(OcnewB @ Sep 14 2005, 01:29 AM)
Sorry for bumping but i just noticed this topic has been viewed more than 25.000 times!
-
Title: A Lot Of Errors Explained In Detail!
Post by: OcnewB on September 14, 2005, 07:15:00 AM
-
Post by: OcnewB on September 14, 2005, 07:15:00 AM
QUOTE(ferrari_rulz_02 @ Sep 14 2005, 12:08 PM)
but its very old
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on September 19, 2005, 02:19:00 AM
-
Post by: ferrari_rulz_02 on September 19, 2005, 02:19:00 AM
QUOTE(Pepper 139 @ Sep 19 2005, 02:36 PM)
It installed just fine then ran slayer to format it for me but i still get the same problem.
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on September 19, 2005, 06:58:00 AM
-
Post by: ferrari_rulz_02 on September 19, 2005, 06:58:00 AM
QUOTE(Pepper 139 @ Sep 19 2005, 10:05 PM)
is there anything i can do to establish that it is the mobo?
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on September 21, 2005, 10:18:00 PM
-
Post by: ferrari_rulz_02 on September 21, 2005, 10:18:00 PM
QUOTE(Pepper 139 @ Sep 22 2005, 12:31 PM)
Anyone got any ideas what it could be?
-
Title: A Lot Of Errors Explained In Detail!
Post by: kyle2738 on September 24, 2005, 03:17:00 PM
-
i took the hard drive, dvd drive and modchip (and all related parts) out and also resoldered the ata plug on the mother board and it still gives me a error code 7. it was working fine until i drove 10 min. away to show a friend how cool my box is and tell him i could do the same for him, and then this happened. ive ran across many other problems and fixed them ( and also learned from them ) but i cant SEE any physical reason why its not working and im out of ideas.PLEASE HELP!!!!
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on September 24, 2005, 05:07:00 PM
-
well this is a pain. not really sure what else you could do
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on October 07, 2005, 07:29:00 PM
-
Post by: kyle2738 on September 24, 2005, 03:17:00 PM
Post by: ferrari_rulz_02 on September 24, 2005, 05:07:00 PM
Post by: ferrari_rulz_02 on October 07, 2005, 07:29:00 PM
QUOTE(Master Russ @ Oct 8 2005, 11:33 AM)
Can someone help me with error code 3
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on October 18, 2005, 02:10:00 AM
-
Post by: ferrari_rulz_02 on October 18, 2005, 02:10:00 AM
QUOTE(wewe6 @ Oct 17 2005, 06:25 PM)
I have got error 13, after I insert the slayer 2.6, it gives me error 14, what's that mean ? HDD need to replace ? Pls. help.
-
Title: A Lot Of Errors Explained In Detail!
Post by: doodle_9008 on October 18, 2005, 09:26:00 PM
-
hi i have error 7 i think it was because i touched the hdd on metal what should i do do i have to get a new hdd? please respond here or at [email protected] thanks
-
Title: A Lot Of Errors Explained In Detail!
Post by: ferrari_rulz_02 on October 19, 2005, 03:31:00 AM
-
Post by: doodle_9008 on October 18, 2005, 09:26:00 PM
Post by: ferrari_rulz_02 on October 19, 2005, 03:31:00 AM
QUOTE(doodle_9008 @ Oct 19 2005, 02:37 PM)
hi i have error 7 i think it was because i touched the hdd on metal what should i do do i have to get a new hdd? please respond here or at [email protected] thanks
-
Title: A Lot Of Errors Explained In Detail!
Post by: lmb03 on January 06, 2006, 07:12:00 PM
-
Is there a way fix ERROR CODE 06 on my softmodded xbox?
-
Title: A Lot Of Errors Explained In Detail!
Post by: klipschfan4life on February 16, 2006, 03:39:00 PM
-
I got a used xbox never been opened for $8! WOW!!! But, I have some bad news....... It's not boting up to the dashboard. When I get the error message saing that I need to get my xbox serviced by MS, theres no number at the top left corner of the screen. Whats that mean? How do I fix it? How do I know if I have a bad HDD?
Any help would be apppriciated. Thanks!
-
Title: A Lot Of Errors Explained In Detail!
Post by: Cappi on February 16, 2006, 04:18:00 PM
-
I got a used xbox never been opened for $8! WOW!!! But, I have some bad news....... It's not boting up to the dashboard. When I get the error message saing that I need to get my xbox serviced by MS, theres no number at the top left corner of the screen. Whats that mean? How do I fix it? How do I know if I have a bad HDD?
Any help would be apppriciated. Thanks!
No error number means you have a 1.0 xbox with 3944 kernel. kernel 3944 does not have error codes in the bios. Your hard drive probably went out.
-
Title: A Lot Of Errors Explained In Detail!
Post by: klipschfan4life on February 16, 2006, 04:56:00 PM
-
[quote name='Cappi' date='Feb 16 2006, 05:25 PM' post='3253356']
-
Title: A Lot Of Errors Explained In Detail!
Post by: JrracinFan8 on February 16, 2006, 05:23:00 PM
-
Is there a way fix ERROR CODE 06 on my softmodded xbox?
Error 6 is that the drive is locked and Xbox eeprom doesnt match the key to unlock the drive, most you could do is try a different IDE cable or unlock it and use a modchip and try relocking it.
-
Title: A Lot Of Errors Explained In Detail!
Post by: OcnewB on March 16, 2006, 09:51:00 AM
-
Is anyone actually READING the starting post?
-
Title: A Lot Of Errors Explained In Detail!
Post by: llcccc on May 05, 2006, 05:32:00 AM
-
Hi !
I have Xbox V1.6 with error 16 I try to do Exactly like this in step 2 but it not working nothing change
2. This is the more easy and newbie friendly strategy
-Get a friend with a modded xbox.
-Unlock his hdd with eeprom management from a slayer evo-x cd.
-Than, place his hdd in your xbox.
-Boot with your chip on.
Anything can help will be appreciate
Thanks alot
llcccc
-
Title: A Lot Of Errors Explained In Detail!
Post by: Zebes on July 20, 2006, 01:52:00 AM
-
Error Code 9 - Can be only one of the three problems below:
1: Bad Hard Drive
2: Bad IDE Cable
3: Low 12volt Power
-----------------
Very Simple Solutions:
Install a new hard drive.
Try a replacement IDE cable.
Check for only 10volts on the 12volt (Yellow) cable going to the hard drive.
(If so, adjust the small pot at the front of the power supply unit, just a hair)
Not always true, on mine something is screwed up on the mobo
-
Title: A Lot Of Errors Explained In Detail!
Post by: Zebes on July 25, 2006, 12:56:00 PM
-
the error 9 can also be casue by a bad ata controller on the mobo or broken traces, thanks to llamma
-
Title: A Lot Of Errors Explained In Detail!
Post by: xboxgamer733 on July 25, 2006, 02:45:00 PM
-
-
Title: A Lot Of Errors Explained In Detail!
Post by: raymond24 on October 27, 2007, 12:57:00 AM
-
Ok there we go. I hope this WILL get PINNED on most (all?) of the forum sections
because it is getting more and more annoying to explain over and over again
what the most common errors mean.
Thanks to Superfro for the 1st (much too basic) list.
I thought the list was sort off too basic and to short to be newbie friendly so lets try and see what I can make of it.
Beware, you wont see the bootldr error's because (thanks to: Lordvader129) : "when you see this" is not entirely accurate, you never see the bootloader errors, as they are one that cause the reboot/FRAGs
2 - bootldr - Eeprom check failed
[Details]
When you see this error most of the times you have flashed something wrong. Or you dropped solder on your eeprom chips.
[/Details]
4 - bootldr - Ram check failed
[Details]
Your Xbox ram chips are wasted.
Maybe you dropped a little solder on it (try to remove it CAREFULLY!). Note, if they are fried, removing solder won't fix them). Maybe you were static when you touched the ram chips. They are kind off sensitive. If they are, they are fried, sell your xbox for spare parts to me
[/Details]
5 - kernel - HDD not locked (The retail xbox bioses require the hd to be locked)
[Details]
When you upgrade your hard disk drive for one that is larger, you most of the times use a new hard drive that you bought in the shop. Now, when you put this hdd in your xbox and you try to boot up with your chip off. It gives you error 5. Why you ask? Well i will try to explain it simple.
The original (also called "Retail") hard drive is locked by MS. Why did they lock the harddrive?
Well if it wasn't it wouldve been more than easy (in the start of xbox hacking)
for hackers to change content on it. Thats why MS locks it. It is just a security measure.
This locking proces uses information thats on the motherboard. The "Lock" on a xbox hard drive contains information that is based on the harddrive itself and the motherboard it came with.
One thing that makes this clear: You can not change a retail harddrive with another one from an other not modded xbox. With every xbox there is only ONE i repeat ONE compatible harddisk drive. That is, if they are locked.
If you don't mod your xbox (tsop or modchips) you can not change harddrives. Not even from another xbox. However when your xbox IS modified you can change your harddisk for almost every other harddisk (thats UNLOCKED). This means that even when your xbox is modified, you can not just put another (retail) XBOX harddisk in your xbox. However some smart people made programs that can lock or unlock your xbox harddisk on the fly.
So when does the error occur? The only time this error should occur is when you boot up your xbox in original mode AND you have a harddisk in your xbox that is not yet locked. So now you ask what do i have to do to make your xbox work again?
Well the answer is pretty easy. Boot up your xbox with the chip on. Preferably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"
When it is "Done" just turn off your xbox. Disable your chip and try to boot in original mode. Now there should be no more error 5.
[/Details]
6 - kernel - Cannot unlock HDD
[Details]
If you understand the above, you should be able to understand what this means. It means you are trying to boot up the xbox with an harddisk that is locked in combination with ANOTHER motherboard than you are using it with right now.
What can i do about it, you ask? Well place the harddisk back in the xbox where it came from. After that, UNLOCK the harddisk with the same procedure i explained above (see error 5). Now when the harddisk is UNLOCKED, put it in the xbox which gave you the error. Now when you boot up with the chip ON it should not give you an error anymore.
However when you put the xbox on with the chip OFF your xbox will give you an error. (error 5) So to make sure you can boot original and boot with the chip ON. Next do the same as above: "Boot up your xbox with the chip on. Preferrably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"
When it is ready just turn off your xbox. Disable your chip and try to boot original. Now there should be no more error.
[/Details]
7 - kernel - HDD timeout
[Details]
Most of the times, the IDE cable is not properly connected when you see this error. Please reattach the ide cable. Not only to the harddisk drive but also to the dvd drive. ALso try to reconnect the ide cable to the motherboard.
Press pretty hard so it goes all the way in. Make sure it is seated straight and proper in the drives and the motherboard. If you still have an error 7. Try another ide cable. If that won't work try another harddisk. If there is still no go, try to set the jumpers on the rearside of the harddisk drive. Set it to master or cable select. If still no succes, good luck and sell your xbox to me
[/Details]
8 - kernel - No HDD found
[Details]
Please make sure your xbox hdd is attached properly. Most of the times the Ide cable came loose, or isn't seated properly in the IDE port of your harddisk. ALso make sure the power supply cables are intact and working.
Make sure the ide cable is also connected properly to the rest of the hardware (dvd and motherboard).
[/Details]
9 - kernel - HDD parameters (PIO/DMA/or size {debug}, certain size minimum is required for debug)
[Details]
Not very common error, please try another harddisk.
[/Details]
10 - kernel - DVD timeout
[Details]
Actually its almost the same as error 6/7/8. But also make sure the yellow cables are properly connected to the motherboard and the dvd drive.
1. Make sure ide cables are connected good.
2. Make sure the yellow cables are good and properly connected.
3. Still no succes? Try another dvd drive of which you are sure it is working.
[/Details]
11 - kernel - No DVD Founnd
[Details]
Same as #10 So read up please!
[/Details]
12 - kernel - DVD parameters (PIO/DMA)
[Details]
Same as #10, only not very common.
[/Details]
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.
[Details]
This is an error thats most common when you have changed something on your xbox harddisk drive for whatever reason you had, but did not do it properly.
So what to solve it? Well, try to rebuild you xbox harddisk (retail or upgraded/large)
with a slayer 2.6 cd.
(BUT WATCH OUT READ MORE ABOUT THIS ERROR 13 BEFORE YOU DO THAT!) .
The thing you should understand is that error 13 is only because something is wrong with the files on your xbox harddisk.
UPDATE: Recently more and more xbox's that i started modding were giving me an error 13 when i booted in original mode. So what the hell was going on. Solder work was great, the slayer cd was also working great.
However i started doing some research and i finally figured it out. The error it gives is because of the incompatibility between the (older) dashboard (4920) that older slayer cd installs and the new dashboard/kernel versions found in some new xbox's and found in xbox's that have been connected to xbox live (when you go on xbox-live, it'll upgrade your dashboard file to i believe it is now 5659.03. This dasboard is incompatible with the dash that (old) slayer cd installs (for example 2.5 or lower) for you.
(In detail, in the eeprom chip there is a kernel which is incompatible with the dashboard (4920) that slayer installs.)
So what do you do to fix it? Well, it's easy. Someone may know how to do this more easy but this is how i did it. I got myself an xbox of a friend that has xbox live. His xbox is modified and runs a executor chip. I checked his dashboard version and i saw it was the latest 5659.03 dashboard. So i connected his xbox to my computer and i transferred his complete c:\ partition to my computer. Than i connected the xbox that gave me an error 13 when booting original, to my computer. AFter that i transferred "his" c:\ partition to my own c:\ partition, when it asked me to overwrite i chose all. After transfer was done, i rebooted the xbox. And voila no more error 13. The incompatibility was gone.
I think you have to transfer all the xboxdash files and also the xboxdashdata (or something like that) folder. In case you hate to experiment, just transfer the complete c:\ partition of a fairly new or upgraded xbox to your c:\ partition and overwrite all.
Ah well, hope it helps someone.
*UPDATE*
It seems there is an easier solution. You can use the dashupdate found on most new xbox games! Be sure to 1st unplug your ethernet cable before you do so!!!
Also see this post:
http://forums.xbox-s...p;#entry1700179
*UPDATE2*
Besides that, just use a good installation disc and all is fine. Use a 2.6 slayer or something similar
[/details]
14 - dashboard - Error loading dashboard (dashboard generic error)
[Details]
Same thing as above (error 13). This time it is also a little mistake from you on changing names or having played around with files on the xbox harddisk. Error 14 is most often because you changed boot orders or names of startup files on the harddisk. It can also happen when you are rebuilding your xbox harddisk with a slayer cd and the power was cut.
[/Details]
16 - dashboard - Clock cannot be set. Well i wrote earlier another tutorial about this specific error so here it is:
[Details]
Basically it comes down to this. Error 16 has to do with not finding the menu setting with which you can set the clock of the hdd. This happens to a lot of people that erase their hdd (original/upgraded) or MS dashboard files and after that they don't immediatly install the hdd but leave the xbox without power longer than 5 hours.
It's all about the hdd can't find the menu with which it can set the clock. This is mostly because the xbox hdd is empty (you removed dashboard or fux0red it via ftp). The problem arises when xbox searches for menu to set clock with, can't find it and voila: error 16. Well read on please!
So you have an error 16 huh? Don't worry "nothing" is broken!
You have an xbox hdd that is locked. And normally you can boot in original and modded mode. Retail or upgraded doesn't matter. You start playing around with xboxdash.xbe etc. using ftp programs. While doing this you "accidently" remove your MS dashboard and also your alternate dashboard (Evox, etc.) so there is no dash anymore on the xbox hdd.
You end the ftp session and after that you shut off your xbox. Normally when you would start up again it gives you an error 13/14 ( no dashboard found). No worries with a slayer Evox cd (and a hardmod), all is ok. BUT this is only WITHIN 3 hours or so.
This is because the internal clock of the xbox will only be kept alive by the capacitors for only 3 or 4 hours. So when you leave your xbox unplugged from electricity for over 5 hours after you have played with the .xbe's AND you have removed your (ms and evo-x) dash from your xbox than you are fux0red. Why do you ask?
Why can't I boot from disc?
Its as follows Xbox starts booting==> (almost 1st thing a xbox does is) searches for internal clock==> doesnt find internal clock because there hasn't been any electricity on the xbox for 5 hours so battery that kept clock alive is empty and clock is gone==> searches for the proper dashboard menu to set clock with ==> doesnt find msdashboard or evo-x dashboard menu becuz you have removed it from the hdd for whatever reasons you had==> xbox gives error 16: cannot set clock.
So what do you do about it? Two options!
1. There are some bios'es around that allow the chip to boot past the clocksetting. (do a search!). So how do you get that bios on your chip because you cant boot to a flash program or something? Well you need to have an external flasher.
It seems the m8 bios will take care for you of booting past the clocksetting. Or use the latest Xecutor bios
2. This is the more easy and newbie friendly strategy
-Get a friend with a modded xbox.
-Unlock his hdd with eeprom management from a slayer evo-x cd.
-Than, place his hdd in your xbox.
-Boot with your chip on.
-Now the xbox DOES find a dashboard when you boot in original mode and you can set the time in the msdashboard clock settings.
-Shut off xbox and remove your friends hdd
-PLace his hdd back in his xbox and lock it again
-Install your hdd
-(clock has been set) So boot up with slayer cd.
-Install normally whatever you wanna install
-lock hdd
If you get an error 13 after this, please read up on the error 13 explanation!
[/Details]
20 - kernel - The dashboard was attempted to load and failed
[Details]
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
[/Details]
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
[Details] With thanks to "bleugh"
This occurs frequently when the xbox is unable to boot due to dashboard changes being made (ie Gcue true blue hasnt been resigned, parts of the stock dash are missing - incomplete FTP backups copied to a new HDD for example).
See also this topic:
http://forums.xbox-s...howtopic=287760
[/Details]
I am not responsible for whatever happens to your xbox when following my advice. It's just what i found to be working so don't blame me when you kill your xbox.
Without this your xbox would also be dead so... Have fun and good luck
I Hope this is helpfull and it will end the endless error this error that topics.
Cheers
OcnewB
-
Title: A Lot Of Errors Explained In Detail!
Post by: Brick17 on June 11, 2008, 05:40:00 PM
-
Wonder if anyone can help me out , new to all this but are trying to find out what to do to fix my boys X Box.
It's not a X box 360 but it's the first version. Error code on screen is 09 which as far as I can work out the HDD( Hard Disk ) has had it and It needs a new one.
Is that right and can I repair it myself, as I have a spare not working X Box?
Cheers
-
Title: A Lot Of Errors Explained In Detail!
Post by: Who_U on April 03, 2009, 03:02:00 AM
-
hay guys,
i have recently stuffed up(i think
) my xbox. i have error 7. i also have another UNMODDED xbox. can i use this to fix it?? or can i use the slayers disc?? if so, HOW???????
ta
-
Title: A Lot Of Errors Explained In Detail!
Post by: Bomb Bloke on April 03, 2009, 04:45:00 AM
-
Error 07 means the HDD is busted. Install a different HDD to verify you don't get the same code (it might be an issue with the motherboard), and once you're sure the drive is at fault, replace it.
If you need further assitance, create a new thread detailing such things as how your problem console is modified, what backups you have, and so forth.
-
Title: A Lot Of Errors Explained In Detail!
Post by: The_Zig on August 11, 2011, 01:50:00 AM
-
[/quote]
5 - kernel - HDD not locked (The retail xbox bioses require the hd to be locked)
[/quote]
Basically i got my 1st xbox in 2002 (i think it is a 1.1) got it chipped. I got it modded at the MOD shop, got 250 gig hdd, new DVD drive and what i though (was sold a shit sandwhich) a xecuter 2 mod chip. I had probably 50 games over the years i backed up, and emulators XBMC. was awesome.
I moved house and the next time i turned it on i got the red and green flashing lights, error 5
The chip is hard wired and therefore cannot be turned off
so does this mean the chip is stuffed or has the HDD had it?
Post by: lmb03 on January 06, 2006, 07:12:00 PM
Post by: klipschfan4life on February 16, 2006, 03:39:00 PM
Any help would be apppriciated. Thanks!
Post by: Cappi on February 16, 2006, 04:18:00 PM
QUOTE(klipschfan4life @ Feb 16 2006, 03:46 PM) 
I got a used xbox never been opened for $8! WOW!!! But, I have some bad news....... It's not boting up to the dashboard. When I get the error message saing that I need to get my xbox serviced by MS, theres no number at the top left corner of the screen. Whats that mean? How do I fix it? How do I know if I have a bad HDD?
Any help would be apppriciated. Thanks!
No error number means you have a 1.0 xbox with 3944 kernel. kernel 3944 does not have error codes in the bios. Your hard drive probably went out.
Post by: klipschfan4life on February 16, 2006, 04:56:00 PM
Post by: JrracinFan8 on February 16, 2006, 05:23:00 PM
QUOTE(lmb03 @ Jan 6 2006, 09:19 PM)
Is there a way fix ERROR CODE 06 on my softmodded xbox?
Error 6 is that the drive is locked and Xbox eeprom doesnt match the key to unlock the drive, most you could do is try a different IDE cable or unlock it and use a modchip and try relocking it.
Post by: OcnewB on March 16, 2006, 09:51:00 AM
Post by: llcccc on May 05, 2006, 05:32:00 AM
I have Xbox V1.6 with error 16 I try to do Exactly like this in step 2 but it not working nothing change
2. This is the more easy and newbie friendly strategy
-Get a friend with a modded xbox.
-Unlock his hdd with eeprom management from a slayer evo-x cd.
-Than, place his hdd in your xbox.
-Boot with your chip on.
Anything can help will be appreciate
Thanks alot
llcccc
Post by: Zebes on July 20, 2006, 01:52:00 AM
QUOTE(garyopa @ Apr 7 2005, 05:09 PM)
Error Code 9 - Can be only one of the three problems below:
1: Bad Hard Drive
2: Bad IDE Cable
3: Low 12volt Power
-----------------
Very Simple Solutions:
Install a new hard drive.
Try a replacement IDE cable.
Check for only 10volts on the 12volt (Yellow) cable going to the hard drive.
(If so, adjust the small pot at the front of the power supply unit, just a hair)
Not always true, on mine something is screwed up on the mobo
Post by: Zebes on July 25, 2006, 12:56:00 PM
Post by: xboxgamer733 on July 25, 2006, 02:45:00 PM
QUOTE(p5ycho0 @ Jul 25 2006, 08:13 AM)
Error 16 woes. I've followed the instructions ( all I could find ) on fixing error 16 and nothing has helps, I'm down to the assumption that there's a motherboard issue. I've swapped in an unlocked working drive from a working X-Box and still get the error, I can use the failed X-Box drive unlocked in the working X-Box and it runs fine. I've tried BIOS that supposedly by-pass the clock check but still get error 16. Anyone run into a failed IDE interface or the like? I've tried swapping cables as well.
Have you tried formatting the Xbox's hard drive to stock, and including the full MS dashboard on the drive?Post by: raymond24 on October 27, 2007, 12:57:00 AM
QUOTE(OcnewB @ Feb 4 2004, 01:54 PM)
Ok there we go. I hope this WILL get PINNED on most (all?) of the forum sections
because it is getting more and more annoying to explain over and over again
what the most common errors mean.
Thanks to Superfro for the 1st (much too basic) list.
I thought the list was sort off too basic and to short to be newbie friendly so lets try and see what I can make of it.
Beware, you wont see the bootldr error's because (thanks to: Lordvader129) : "when you see this" is not entirely accurate, you never see the bootloader errors, as they are one that cause the reboot/FRAGs
2 - bootldr - Eeprom check failed
[Details]
When you see this error most of the times you have flashed something wrong. Or you dropped solder on your eeprom chips.
[/Details]
4 - bootldr - Ram check failed
[Details]
Your Xbox ram chips are wasted.
Maybe you dropped a little solder on it (try to remove it CAREFULLY!). Note, if they are fried, removing solder won't fix them). Maybe you were static when you touched the ram chips. They are kind off sensitive. If they are, they are fried, sell your xbox for spare parts to me
[/Details]
5 - kernel - HDD not locked (The retail xbox bioses require the hd to be locked)
[Details]
When you upgrade your hard disk drive for one that is larger, you most of the times use a new hard drive that you bought in the shop. Now, when you put this hdd in your xbox and you try to boot up with your chip off. It gives you error 5. Why you ask? Well i will try to explain it simple.
The original (also called "Retail") hard drive is locked by MS. Why did they lock the harddrive?
Well if it wasn't it wouldve been more than easy (in the start of xbox hacking)
for hackers to change content on it. Thats why MS locks it. It is just a security measure.
This locking proces uses information thats on the motherboard. The "Lock" on a xbox hard drive contains information that is based on the harddrive itself and the motherboard it came with.
One thing that makes this clear: You can not change a retail harddrive with another one from an other not modded xbox. With every xbox there is only ONE i repeat ONE compatible harddisk drive. That is, if they are locked.
If you don't mod your xbox (tsop or modchips) you can not change harddrives. Not even from another xbox. However when your xbox IS modified you can change your harddisk for almost every other harddisk (thats UNLOCKED). This means that even when your xbox is modified, you can not just put another (retail) XBOX harddisk in your xbox. However some smart people made programs that can lock or unlock your xbox harddisk on the fly.
So when does the error occur? The only time this error should occur is when you boot up your xbox in original mode AND you have a harddisk in your xbox that is not yet locked. So now you ask what do i have to do to make your xbox work again?
Well the answer is pretty easy. Boot up your xbox with the chip on. Preferably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"
When it is "Done" just turn off your xbox. Disable your chip and try to boot in original mode. Now there should be no more error 5.
[/Details]
6 - kernel - Cannot unlock HDD
[Details]
If you understand the above, you should be able to understand what this means. It means you are trying to boot up the xbox with an harddisk that is locked in combination with ANOTHER motherboard than you are using it with right now.
What can i do about it, you ask? Well place the harddisk back in the xbox where it came from. After that, UNLOCK the harddisk with the same procedure i explained above (see error 5). Now when the harddisk is UNLOCKED, put it in the xbox which gave you the error. Now when you boot up with the chip ON it should not give you an error anymore.
However when you put the xbox on with the chip OFF your xbox will give you an error. (error 5) So to make sure you can boot original and boot with the chip ON. Next do the same as above: "Boot up your xbox with the chip on. Preferrably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"
When it is ready just turn off your xbox. Disable your chip and try to boot original. Now there should be no more error.
[/Details]
7 - kernel - HDD timeout
[Details]
Most of the times, the IDE cable is not properly connected when you see this error. Please reattach the ide cable. Not only to the harddisk drive but also to the dvd drive. ALso try to reconnect the ide cable to the motherboard.
Press pretty hard so it goes all the way in. Make sure it is seated straight and proper in the drives and the motherboard. If you still have an error 7. Try another ide cable. If that won't work try another harddisk. If there is still no go, try to set the jumpers on the rearside of the harddisk drive. Set it to master or cable select. If still no succes, good luck and sell your xbox to me
[/Details]
8 - kernel - No HDD found
[Details]
Please make sure your xbox hdd is attached properly. Most of the times the Ide cable came loose, or isn't seated properly in the IDE port of your harddisk. ALso make sure the power supply cables are intact and working.
Make sure the ide cable is also connected properly to the rest of the hardware (dvd and motherboard).
[/Details]
9 - kernel - HDD parameters (PIO/DMA/or size {debug}, certain size minimum is required for debug)
[Details]
Not very common error, please try another harddisk.
[/Details]
10 - kernel - DVD timeout
[Details]
Actually its almost the same as error 6/7/8. But also make sure the yellow cables are properly connected to the motherboard and the dvd drive.
1. Make sure ide cables are connected good.
2. Make sure the yellow cables are good and properly connected.
3. Still no succes? Try another dvd drive of which you are sure it is working.
[/Details]
11 - kernel - No DVD Founnd
[Details]
Same as #10 So read up please!
[/Details]
12 - kernel - DVD parameters (PIO/DMA)
[Details]
Same as #10, only not very common.
[/Details]
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.
[Details]
This is an error thats most common when you have changed something on your xbox harddisk drive for whatever reason you had, but did not do it properly.
So what to solve it? Well, try to rebuild you xbox harddisk (retail or upgraded/large)
with a slayer 2.6 cd.
(BUT WATCH OUT READ MORE ABOUT THIS ERROR 13 BEFORE YOU DO THAT!) .
The thing you should understand is that error 13 is only because something is wrong with the files on your xbox harddisk.
UPDATE: Recently more and more xbox's that i started modding were giving me an error 13 when i booted in original mode. So what the hell was going on. Solder work was great, the slayer cd was also working great.
However i started doing some research and i finally figured it out. The error it gives is because of the incompatibility between the (older) dashboard (4920) that older slayer cd installs and the new dashboard/kernel versions found in some new xbox's and found in xbox's that have been connected to xbox live (when you go on xbox-live, it'll upgrade your dashboard file to i believe it is now 5659.03. This dasboard is incompatible with the dash that (old) slayer cd installs (for example 2.5 or lower) for you.
(In detail, in the eeprom chip there is a kernel which is incompatible with the dashboard (4920) that slayer installs.)
So what do you do to fix it? Well, it's easy. Someone may know how to do this more easy but this is how i did it. I got myself an xbox of a friend that has xbox live. His xbox is modified and runs a executor chip. I checked his dashboard version and i saw it was the latest 5659.03 dashboard. So i connected his xbox to my computer and i transferred his complete c:\ partition to my computer. Than i connected the xbox that gave me an error 13 when booting original, to my computer. AFter that i transferred "his" c:\ partition to my own c:\ partition, when it asked me to overwrite i chose all. After transfer was done, i rebooted the xbox. And voila no more error 13. The incompatibility was gone.
I think you have to transfer all the xboxdash files and also the xboxdashdata (or something like that) folder. In case you hate to experiment, just transfer the complete c:\ partition of a fairly new or upgraded xbox to your c:\ partition and overwrite all.
Ah well, hope it helps someone.
*UPDATE*
It seems there is an easier solution. You can use the dashupdate found on most new xbox games! Be sure to 1st unplug your ethernet cable before you do so!!!
Also see this post:
http://forums.xbox-s...p;#entry1700179
*UPDATE2*
Besides that, just use a good installation disc and all is fine. Use a 2.6 slayer or something similar
[/details]
14 - dashboard - Error loading dashboard (dashboard generic error)
[Details]
Same thing as above (error 13). This time it is also a little mistake from you on changing names or having played around with files on the xbox harddisk. Error 14 is most often because you changed boot orders or names of startup files on the harddisk. It can also happen when you are rebuilding your xbox harddisk with a slayer cd and the power was cut.
[/Details]
16 - dashboard - Clock cannot be set. Well i wrote earlier another tutorial about this specific error so here it is:
[Details]
Basically it comes down to this. Error 16 has to do with not finding the menu setting with which you can set the clock of the hdd. This happens to a lot of people that erase their hdd (original/upgraded) or MS dashboard files and after that they don't immediatly install the hdd but leave the xbox without power longer than 5 hours.
It's all about the hdd can't find the menu with which it can set the clock. This is mostly because the xbox hdd is empty (you removed dashboard or fux0red it via ftp). The problem arises when xbox searches for menu to set clock with, can't find it and voila: error 16. Well read on please!
So you have an error 16 huh? Don't worry "nothing" is broken!
You have an xbox hdd that is locked. And normally you can boot in original and modded mode. Retail or upgraded doesn't matter. You start playing around with xboxdash.xbe etc. using ftp programs. While doing this you "accidently" remove your MS dashboard and also your alternate dashboard (Evox, etc.) so there is no dash anymore on the xbox hdd.
You end the ftp session and after that you shut off your xbox. Normally when you would start up again it gives you an error 13/14 ( no dashboard found). No worries with a slayer Evox cd (and a hardmod), all is ok. BUT this is only WITHIN 3 hours or so.
This is because the internal clock of the xbox will only be kept alive by the capacitors for only 3 or 4 hours. So when you leave your xbox unplugged from electricity for over 5 hours after you have played with the .xbe's AND you have removed your (ms and evo-x) dash from your xbox than you are fux0red. Why do you ask?
Why can't I boot from disc?
Its as follows Xbox starts booting==> (almost 1st thing a xbox does is) searches for internal clock==> doesnt find internal clock because there hasn't been any electricity on the xbox for 5 hours so battery that kept clock alive is empty and clock is gone==> searches for the proper dashboard menu to set clock with ==> doesnt find msdashboard or evo-x dashboard menu becuz you have removed it from the hdd for whatever reasons you had==> xbox gives error 16: cannot set clock.
So what do you do about it? Two options!
1. There are some bios'es around that allow the chip to boot past the clocksetting. (do a search!). So how do you get that bios on your chip because you cant boot to a flash program or something? Well you need to have an external flasher.
It seems the m8 bios will take care for you of booting past the clocksetting. Or use the latest Xecutor bios
2. This is the more easy and newbie friendly strategy
-Get a friend with a modded xbox.
-Unlock his hdd with eeprom management from a slayer evo-x cd.
-Than, place his hdd in your xbox.
-Boot with your chip on.
-Now the xbox DOES find a dashboard when you boot in original mode and you can set the time in the msdashboard clock settings.
-Shut off xbox and remove your friends hdd
-PLace his hdd back in his xbox and lock it again
-Install your hdd
-(clock has been set) So boot up with slayer cd.
-Install normally whatever you wanna install
-lock hdd
If you get an error 13 after this, please read up on the error 13 explanation!
[/Details]
20 - kernel - The dashboard was attempted to load and failed
[Details]
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
[/Details]
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
[Details] With thanks to "bleugh"
This occurs frequently when the xbox is unable to boot due to dashboard changes being made (ie Gcue true blue hasnt been resigned, parts of the stock dash are missing - incomplete FTP backups copied to a new HDD for example).
See also this topic:
http://forums.xbox-s...howtopic=287760
[/Details]
I am not responsible for whatever happens to your xbox when following my advice. It's just what i found to be working so don't blame me when you kill your xbox.
Without this your xbox would also be dead so... Have fun and good luck
I Hope this is helpfull and it will end the endless error this error that topics.
Cheers
OcnewB
Post by: Brick17 on June 11, 2008, 05:40:00 PM
It's not a X box 360 but it's the first version. Error code on screen is 09 which as far as I can work out the HDD( Hard Disk ) has had it and It needs a new one.
Is that right and can I repair it myself, as I have a spare not working X Box?
Cheers
Post by: Who_U on April 03, 2009, 03:02:00 AM
i have recently stuffed up(i think
) my xbox. i have error 7. i also have another UNMODDED xbox. can i use this to fix it?? or can i use the slayers disc?? if so, HOW???????ta
Post by: Bomb Bloke on April 03, 2009, 04:45:00 AM
If you need further assitance, create a new thread detailing such things as how your problem console is modified, what backups you have, and so forth.
Post by: The_Zig on August 11, 2011, 01:50:00 AM
5 - kernel - HDD not locked (The retail xbox bioses require the hd to be locked)
[/quote]
Basically i got my 1st xbox in 2002 (i think it is a 1.1) got it chipped. I got it modded at the MOD shop, got 250 gig hdd, new DVD drive and what i though (was sold a shit sandwhich) a xecuter 2 mod chip. I had probably 50 games over the years i backed up, and emulators XBMC. was awesome.
I moved house and the next time i turned it on i got the red and green flashing lights, error 5
The chip is hard wired and therefore cannot be turned off
so does this mean the chip is stuffed or has the HDD had it?