Rep: 255
3
3
Its been a long time since I have worked on an original XBOX. As soon it tries tto boot up, we get an error 13. The system appears to never have been opened and therefore it has not been modded. Is there a way to fix it?
Is this a good question?
Rep: 782.4k
1.1k
893
2.3k
Kevin Wells, check this first "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.
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? You can use the dashupdate found on most new xbox games! Be sure to 1st unplug your ethernet cable before you do so!!!
Besides that, just use a good installation disc and all is fine. Use a 2.6 slayer or something similar" from here. Let us know if this works, or what you tried besides this. Good Luck.
Was this answer helpful?
Just as an FYI, I haven't spent any time on this unit but the Slayer CD won't do anything on this XBOX. It is stuck in a clock loop where you can't boot anything without first adjusting the clock but you can't get to the clock without getting past the error. I beleive the only way to fix it would be to plop the hard drive into an xbox that has the clock information saved on it and get it up and running there. Once the drive has been restored and functional then I should be able to switch it back to the first xbox and be good to go.
Past 24 Hours: 0
Past 7 Days: 0
Past 30 Days: 0
All Time: 2,034
