Print

[hangover]

I have a 1.1/1.2 xbox that is booting to an 16 error code, i know its the clock setting problem but this xbox i have just bought and is possibly softmodded and all the tut's i've read to fix the 16 error is for chipped box's.
 Not sure how to fix this without doing a hdd rebuild using xboxhdm if that is possible  ?

[Heimdall]

As you suggested, you need to hotswap, then use either xboxhdm or Xplorer360 beta 6 to replace the softmod with Kingroach NDURE 3.1.

[hangover]

QUOTE(Heimdall @ May 24 2010, 10:22 PM)

As you suggested, you need to hotswap, then use either xboxhdm or Xplorer360 beta 6 to replace the softmod with Kingroach NDURE 3.1.

 Yeah i was just being lazy, i had a crappy pc with xboxhdm disc already in the cdrom so i just rebuilt the c partition and its all good- softmodded it and will tsop flash it tomorrow.

[Bomb Bloke]

Never been entirely sure whether error 16 overides faulty-HDD-type errors. I assume it does, but I've never been sure (the easy way to test would be to attach a locked drive from another console - I'd be interested to know what error that caused). The system relocks the drive once it throws that error screen, so there's a bit of timing involved when hotswapping...

[Heimdall]

Error 5 means your chip almost certainly isn't working, and your Xbox is booting the MS BIOS.

You are correct - error 16 is generally a failed softmod, with no MS dash, and left unpowered for a few hours.

Soldering the chip or building an eeprom reader are both viable alternatives if you can't get hotswapping to work.

[lordvader129]

QUOTE(Bomb Bloke @ Jun 1 2010, 06:38 PM)

Never been entirely sure whether error 16 overides faulty-HDD-type errors. I assume it does, but I've never been sure (the easy way to test would be to attach a locked drive from another console - I'd be interested to know what error that caused)

it depends on the bios, an xecuter bios will give 16 in that case instead of 06, and IIRC an evox bios will give the correct error 06

[xboxmods2977]

QUOTE(Bomb Bloke @ Jun 2 2010, 03:38 AM)

Never been entirely sure whether error 16 overides faulty-HDD-type errors. I assume it does

I second this, and will also assume it does. It would seem to me that most xbox bios' shouldn't be able to tell if the clock is set wrong without first running HD checks (error 7) and then checking lock status (error 5 and 6) on the drive, and in fact, accessing contents on a non-unlockable drive isn't possible so why would anyone code a bios to try it?

In conclusion, I say for sure, error 6 overrides error 16 and possibly, error 5. Not sure about error 7.

EDIT:

QUOTE(lordvader129 @ Jun 2 2010, 10:36 PM)

it depends on the bios, an xecuter bios will give 16 in that case instead of 06

This doesn't seem possible to me. How can any xbox bios check the clock on a locked (and non-unlockable) HD?

@spectrumx Check the D0 wire on your solderless adapter to make sure it is making good contact with the DO pad (or it could be touching the wrong pad for your version). Your symptom could indicate this simple fix, and in regards to the hotswap, is sounds to me like the retail kernel is re-locking the drive once error 16 is thrown. If this is the case, you can try the swap before error 16 comes up but that may not work either. The modchip should be your focus.

[Bomb Bloke]

QUOTE(xboxmods2977 @ Jun 3 2010, 07:43 AM)

This doesn't seem possible to me. How can any xbox bios check the clock on a locked (and non-unlockable) HD?

Simple: It can't. But not because the drive is locked, it's because the time isn't stored there to begin with. Otherwise, how on earth would the console keep track of the time while the HDD is powered down?

It might be worth identifying that "old" modchip. Some really old ones only allow booting unsigned code (as opposed to say, skipping clock or locking checks), if memory serves.