I was recently FTPing files from my xbox to my pc, and midway through one of the transfers my xbox made a noise, and incedently the transfer stopped. I rebooted my xbox and was alarmed to see the error #13 on my TV. I havent been on xbox live in ages, and my dash was loading fine before this transfer; I also had never changed any of my firmware/software. Any suggestions?
Hard; its been running fine now for a year or so... i dont see how a file transfer could screw it up. I was importing a file from my xbox to my PC if that makes any difference.
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
yes that is what you do, assuming you can launch games with your error, you will have to cold boot, put the game in turn the console off and then turn it back on with the power button not the eject button
You should be able to boot slayers,(get 2.7 if possible or any other installer..whatever you do DO NOT use a softmod instaler) then reinstall just M$ dash. Get the new version..If that doesn't work with your hardware..very early 1.0 and debug boxes have a few issues you will need to find slayers 2.5 which has the older version, then upgrade with halo2 (no internet connection) The kernal including the bootloader is in the bios chip (hynix or sharp, near the pinheader, also an eeprom, but not referred to as such).. not the eeprom,(little 8 legged bug between the kernal rom and bios chip) which holds the HDD key and certain xbox unique details related to live id. What you describe sounds a bit like a full drive error.. It happens when dash files are on F: for a stealth install, and get overwritten by a large file via ftp. Teach and Learn.. thanks ddp
