xboxscene.org forums

Pages: 1 ... 5 6 [7] 8

Author Topic: A Lot Of Errors Explained In Detail!  (Read 3726 times)

doodle_9008

  • Archived User
  • Newbie
  • *
  • Posts: 1
A Lot Of Errors Explained In Detail!
« Reply #90 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
Logged

ferrari_rulz_02

  • Archived User
  • Hero Member
  • *
  • Posts: 2661
A Lot Of Errors Explained In Detail!
« Reply #91 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
Logged

lmb03

  • Archived User
  • Newbie
  • *
  • Posts: 2
A Lot Of Errors Explained In Detail!
« Reply #92 on: January 06, 2006, 07:12:00 PM »

Is there a way fix ERROR CODE 06 on my softmodded xbox?
Logged

klipschfan4life

  • Archived User
  • Newbie
  • *
  • Posts: 5
A Lot Of Errors Explained In Detail!
« Reply #93 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!
Logged

Cappi

  • Archived User
  • Full Member
  • *
  • Posts: 115
A Lot Of Errors Explained In Detail!
« Reply #94 on: February 16, 2006, 04:18:00 PM »

QUOTE(klipschfan4life @ Feb 16 2006, 03:46 PM) View Post

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.
Logged

klipschfan4life

  • Archived User
  • Newbie
  • *
  • Posts: 5
A Lot Of Errors Explained In Detail!
« Reply #95 on: February 16, 2006, 04:56:00 PM »

[quote name='Cappi' date='Feb 16 2006, 05:25 PM' post='3253356']
Logged

JrracinFan8

  • Archived User
  • Sr. Member
  • *
  • Posts: 278
A Lot Of Errors Explained In Detail!
« Reply #96 on: February 16, 2006, 05:23:00 PM »

QUOTE(lmb03 @ Jan 6 2006, 09:19 PM) View Post

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.
Logged

OcnewB

  • Archived User
  • Full Member
  • *
  • Posts: 209
A Lot Of Errors Explained In Detail!
« Reply #97 on: March 16, 2006, 09:51:00 AM »

Is anyone actually READING the starting post?

Logged

llcccc

  • Archived User
  • Newbie
  • *
  • Posts: 1
A Lot Of Errors Explained In Detail!
« Reply #98 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
Logged

Zebes

  • Archived User
  • Full Member
  • *
  • Posts: 133
A Lot Of Errors Explained In Detail!
« Reply #99 on: July 20, 2006, 01:52:00 AM »

QUOTE(garyopa @ Apr 7 2005, 05:09 PM) View Post

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
Logged

Zebes

  • Archived User
  • Full Member
  • *
  • Posts: 133
A Lot Of Errors Explained In Detail!
« Reply #100 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 happy.gif

Logged

xboxgamer733

  • Archived User
  • Hero Member
  • *
  • Posts: 670
A Lot Of Errors Explained In Detail!
« Reply #101 on: July 25, 2006, 02:45:00 PM »

QUOTE(p5ycho0 @ Jul 25 2006, 08:13 AM) View Post
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?
Logged

raymond24

  • Archived User
  • Newbie
  • *
  • Posts: 1
A Lot Of Errors Explained In Detail!
« Reply #102 on: October 27, 2007, 12:57:00 AM »

QUOTE(OcnewB @ Feb 4 2004, 01:54 PM) View Post

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  rolleyes.gif

[/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  rolleyes.gif

[/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

Logged

Brick17

  • Archived User
  • Newbie
  • *
  • Posts: 1
A Lot Of Errors Explained In Detail!
« Reply #103 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
Logged

Who_U

  • Archived User
  • Newbie
  • *
  • Posts: 2
A Lot Of Errors Explained In Detail!
« Reply #104 on: April 03, 2009, 03:02:00 AM »

hay guys,

i have recently stuffed up(i think sad.gif  ) 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
Logged
Pages: 1 ... 5 6 [7] 8