Topic: Help! Error Code 13 And Now Error Code 16 (Read 260 times)

barrel123 · « **on:** April 04, 2009, 03:26:00 PM »

I haven't touched my xbox for over an year. I use the matrix chip with EvoX (as far as I can remember)
Today I turned it on and everything is ok, but when i start a game, the screen suddenly went black so I decided to restart the xbox.
Afterwards, I get error code 13. I tried to boot it a few times but to no avail and I unplugged the xbox (which I found out afterwards that I should NOT have done).
And now I get error code 16.
I tried the hotswap method (unplug DVD IDE cable, hotswap HDD to PC), but Xplorer360 keeps saying 'FatX drive not found' whenever I try the read the harddisks. Windows Device Manager can see the harddisk ok, but disk management can't.
I have lost the matrix programmer and also my original XBOX HDD.

Is there anything I can do to 'rescue' my xbox now??

Any help will be much appreciated!

Bomb Bloke · « **Reply #1 on:** April 04, 2009, 08:16:00 PM »

Odd, I'm pretty sure Drive Management should be able to see the thing whether you hotswapped correctly or otherwise. Though I do get the impression you didn't quite pull it off.

I don't really recommend repeated attempts. The more times you do it with a given drive, the more likely it is you'll toast that drive completely.

When you say you're using EvoX with the chip, do you mean the dashboard or the BIOS? If not the BIOS, then do you know which BIOS you are using? Or is the matrix one of those ones that doesn't really have a BIOS in it?

lordvader129 · « **Reply #2 on:** April 04, 2009, 07:58:00 PM »

QUOTE(Bomb Bloke @ Apr 4 2009, 06:16 PM)

Or is the matrix one of those ones that doesn't really have a BIOS in it?

matrix is flashable, generally an evox bios would be used because of the way you had to disable the chip for Live, you hit eject and it would reset into stock mode, so an x2 bios with the no-reset-on-eject hack wouldnt work

although if you didnt use Live or added a hardware switch it didnt matter what bios you used, lol

barrel123 · « **Reply #3 on:** April 05, 2009, 05:14:00 AM »

I used both EvoX BIOS and dashboard.

barrel123 · « **Reply #4 on:** April 05, 2009, 05:01:00 AM »

QUOTE(Bomb Bloke @ Apr 5 2009, 02:16 AM)

Odd, I'm pretty sure Drive Management should be able to see the thing whether you hotswapped correctly or otherwise. Though I do get the impression you didn't quite pull it off.

One slight difference is that when hotswapping the xbox HDD with the CD/DVD drive when Windows is running, Windows cannot detect the drive. I have to restart the PC in order for the drive to be detected. The drive does not show up in Disk Management at all either way.

BTW, for hotswap, do I have to disable the modchip bios for it to unlock the drive?

Bomb Bloke · « **Reply #5 on:** April 05, 2009, 08:35:00 AM »

If the console didn't unlock the drive then it wouldn't be able to read the thing. It HAS to do it, whether the chip is running or not.

Again, don't bother with the hotswapping aspect of things until you've made sure you're out of other options.

First off, does the console boot game discs? What about burnt discs? Slayers? Auto Installer Deluxe?

What backups do you have? EEPROM data?

Do you have a spare HDD, at least 8gb in size?

barrel123 · « **Reply #6 on:** April 05, 2009, 11:36:00 AM »

I backed up all the drive data before. I tried burning AIM, Slayers etc with CD-R, DVD+R, DVD-RW and none of them loaded. I have misplaced the original HDD and my games (seeing that I havent touched the xbox for over an year).

lordvader129 · « **Reply #7 on:** February 02, 2020, 04:23:00 PM »

its possible the hard drive just died on you, it happens sometimes when you dont use it in a long time

Heimdall · « **Reply #8 on:** February 02, 2020, 05:28:00 PM »

Sounds like the chip is dead/broken, or the D0 connection has come loose ...... and then the disk doesn't sound too healthy either. Try reseating the chip to ground D0, then booting the Xbox, because if you can get the chip working then you should be able to boot with Slayers and rebuild the disk, or build a new one. Also try the switches on the chip, to see it works in any of the modes.

If none of that works, and hotswapping isn't working, you'll have to fit a new chip or build an eeprom reader.

lordvader129 · « **Reply #9 on:** April 05, 2009, 06:21:00 PM »

QUOTE(Heimdall @ Apr 5 2009, 04:28 PM)

Sounds like the chip is dead/broken, or the D0 connection has come loose

i doubt that, since its a matrix chip its probably using an evox bios, and those dont have the clock fix and thus are susceptible to error 16

i would suggest getting another HD, building it with xhdm so it has the MS dash on it, and try booting that

Heimdall · « **Reply #10 on:** February 02, 2020, 06:14:00 PM »

Ah. Got it. The disk failed, the error 13 was from the Evox BIOS because it couldn't find a dash on the broken disk, and unplugging the box resulted in an unset clock and error 16 that the Evox BIOS doesn't fix.

Bomb Bloke · « **Reply #11 on:** April 05, 2009, 07:50:00 PM »

So EvoX doesn't throw error 07s?

lordvader129 · « **Reply #12 on:** April 05, 2009, 09:14:00 PM »

QUOTE(Bomb Bloke @ Apr 5 2009, 06:26 PM)

So EvoX doesn't throw error 07s?

ive had some strange things happen with dead/dying hard drives, sometimes it seems like the bios cant decide what error to throw when there are multiple

for example an x2 bios will give error 13 instead of 06, lol

barrel123 · « **Reply #13 on:** February 03, 2020, 01:50:00 AM »

yeah, i guess its best for me to get a new HDD and start anew again, or find my old original xbox HDD.

barrel123 · « **Reply #14 on:** February 03, 2020, 02:22:00 AM »

i just checked my backups and found that i am using X2 4973 as the bios, which does not have the skip clock check feature.
one thing i realised is that when i did the hotswap, i didn't plug in the AV cable, is it possible that it will not 'unlock' the HDD that way?

Author Topic: Help! Error Code 13 And Now Error Code 16 (Read 260 times)