I get error code 16, matrix chip, xecuter 4977 bios, xbox v 1.1, latest evox, need help--xbox died.......

Make sure your xbox clock is set. I had an error 16 when i swapped new hard drives for the 2nd time because the clock became reset. I put in the original HD and set the clock, reswapped with no problems.

The clock was already set up correctly, error 16 is a dashboard problem, but I can't figure it out. That goofy error message comes up with the red and green blinking lights, has anyone ever fixed this?

what order is the ide cable?

i think i got an error 17 when i connected the cable in the wrong order

Cables are in the right order, still getting error 16.

If the xbox boots and gives me error 16, is it then possible to use the evox boot disc and transfer the original files over?

Ok, lets make it simple---Has anyone fixed error 16 that has a v1.1 xbox,xecuter 4977 bios and a matrix chip? I've read that using the evox d6 bios bypasses the clock but does it matter if I have the eject fix version? Also is it ok to unlock my original harddrive?

I take it you didn't peruse the general hardware faq?

I linked a big thread on error 16...don't know if it will help, but give this a read:
http://forums.xbox-scene.com/index.php?act...=ST&f=3&t=53268

Error 16... EXPLAINED...
Yes, it is a DASH ERROR, but it is due to the TIME
-----------------------------------------------------------------------------

NORMAL BOOT PROCESS:

1.Xbox turns on
2. several checks are done for hardware, incuding RAM, HD, and DVD-DRIVE, just to test if they are present
3.Xbox checks SYSTEM TIME -> if no time is found -> boot dash off hard drive to set time
4. Xbox looks for default.xbe on DISC, if it is not found, goto 5
5. Xbox boots dash off of Hard drive

What is happening in your case:
1.Xbox turns on
2. several checks are done for hardware, incuding RAM, HD, and DVD-DRIVE, just to test if they are present
3.Xbox checks SYSTEM TIME ->TIME NOT FOUND -> Xbox tries to launch dash off of hard drive -> DASH NOT FOUND-> ERROR 16 - DASH ERROR

The fix:
Put back in your OLD drive (the one with the dash's still on it)
Set the time
Swap the drives without physically unplugging the xbox.

I reflashed with evox d6 red eject fix because I found my old external programmer that came with the matrix chip. It actually works, it bypasses the system clock check and boots normal. The only problem is that I don't want to use the evox bios because it does'nt patch all of the games. NCAA 2k4 won't boot with the d6 bios neither will WSB2k3, it will only boot with the xecuter 4977 bios. I'm afraid that if I reflash back to 4977 I'll have the same error 16 problem again.

QUOTE (Dr.Banes @ Sep 7 2003, 02:14 PM)

I reflashed with evox d6 red eject fix because I found my old external programmer that came with the matrix chip. It actually works, it bypasses the system clock check and boots normal. The only problem is that I don't want to use the evox bios because it does'nt patch all of the games. NCAA 2k4 won't boot with the d6 bios neither will WSB2k3, it will only boot with the xecuter 4977 bios. I'm afraid that if I reflash back to 4977 I'll have the same error 16 problem again.

As long as there is a dash on the hard drive, you wont get error 16. Or did you completely ignore my post?

heinrich, I added your error 16 fix to the pinned hardware faq

hopefully it will get some attention there

"As long as there is a dash on the hard drive, you wont get error 16. Or did you completely ignore my post?"

There has always been a dashboard, both evox and the original dashboard, why are you talking about putting my old drive in? I never took out the original drive to begin with,I just asked a question about unlocking it, nowhere did I mention anything about swapping drives but aerofan897 did. Did you ignore my post and assumed that I swapped drives? Like I said I fixed it with the evox d6 bios like OcnewB posted instead of using slayer and all that other stuff I simply reflashed with it with the external programmer. The only thing I want to know is if this is an ongoing problem with the 4977 bios and is there a fix for this.