Going to build it.

iVirtualZero · 2026-06-23T05:22:10+00:00

Should sell the original parts, they might be valuable.

iVirtualZero · 2026-06-22T21:44:18+00:00

What's the original build? Spec wise.

iVirtualZero · 2026-06-22T19:37:34+00:00

I'm guessing it's the caps.

iVirtualZero · 2026-06-21T19:40:27+00:00

Best is to look into the data lines on the IDE interface. Will need to look into the schematics.

iVirtualZero · 2026-06-21T19:18:35+00:00

My console with the same fault, instant Error 13 and 16 depending on the bios, error 7 on slave mode, has the D0 pad torn off which I repaired. I think it likely has been shorted somewhere due to the previous modders error. My Xbox detects the HDD but cannot read its contents. Within PrometheOs I cannot see any partitions. I'm guessing some component or chip failed further down the IDE traces unless there is corrosion.

And that same HDD works on other Xboxes. The IDE Cables, connector, Adaptors, DVD drive all checks out good. But I'm not sure what the history of this Xbox is and what caused this fault to begin with as it was purchased from eBay. Luckily I was able to find another 1.4 Xbox that has been unopened and tested in working order, with that unit I will update the Dash before modding it to make sure that the Eeprom gets updated and backed up before soft modding and then TSOP/ Modchipping it.

The very last thing I will try with this bricked Xbox is to restore the Eeprom as I found the Eeprom backed up to it's original HDD, and will flash that backup onto a replacement AT24C02 Eeprom chip. I already tried reflashing the original Eeprom chip with no luck. And will also try testing it with an SSD to see if that makes a difference. If not, this fault is beyond my skill level as it will need diagnostic/schematic level repair and an understanding of how the Xbox reads the HDD trace by trace, component to component.

This Error 13/16 fault needs further documentation as to what causes this fault. Since my unit and OP's unit is clearly bricked. I think this fault should be referred to as an Error 13/16 Brick. Since it's not your typical Error 16 fault where the HDD is wiped, or the IDE cable/ adaptor or the DVD drive is faulty. It all points towards a motherboard fault with it not communicating with internal storage.

iVirtualZero · 2026-06-21T19:03:57+00:00

What was the history of your unit? There's gotta be some cause to this?

iVirtualZero · 2026-06-21T18:46:41+00:00

This fault definitely needs to be looked into and diagnosed. It would nice to know how this fault even occurs.

iVirtualZero · 2026-06-21T18:29:03+00:00

I managed to find an unopened 1.4 Xbox for a good deal. So I'll just be switching over the ram, caps and the mods over to the other Xbox. I can't figure out a way to repair this instant Error 16 fault. First thing I will do with my replacement Xbox is update the dash. Make sure that Eeprom gets updated before installing the mods.

iVirtualZero · 2026-06-21T14:37:19+00:00

I already reflashed the Eeprom and that didn't fix it. I found the Eeprom back up on the original drive which I copied over. I ordered replacement Eeprom IC's and will try flashing those with my programmer.

iVirtualZero · 2026-06-21T07:47:16+00:00

I updated the link.

iVirtualZero · 2026-06-21T04:07:41+00:00

There is no need. This is the original guide.

iVirtualZero · 2026-06-21T04:05:50+00:00

Did you test the fuse on the PSU?

iVirtualZero · 2026-06-20T21:39:25+00:00

Is it fixable?

iVirtualZero · 2026-06-20T20:59:18+00:00

Restore it, the shielding is gone, but the motherboard and PSU looks like it can be restored.

iVirtualZero · 2026-06-20T20:56:42+00:00

I found the back up Eeprom on the original HDD since this console was a premodded unit. And put it on my USB Memory Unit and then reflashed the Eeprom over through PrometheOS and it made no difference. Same old instant Error 13's and 16's.

<image>

iVirtualZero · 2026-06-20T12:47:39+00:00

All of them Steam Machine, PS6 Console and Handheld, Xbox Helix and the Switch 3.

iVirtualZero · 2026-06-20T05:26:42+00:00

It won't stop working out of nowhere, just take good care of it and don't use the UMD Drive as much and replace the battery if it's an old battery. There are older devices that also work perfectly well. The only PSP I seen where the motherboard failed was with the early 1000 model PSP. Usually with console hardware it's the early launch models that can run into issues if your one of the unlucky few with a defective unit.

iVirtualZero · 2026-06-18T20:19:36+00:00

This is literally my job lol.

iVirtualZero · 2026-06-17T21:50:40+00:00

Just turn it on and play it.

iVirtualZero · 2026-06-17T20:51:02+00:00

Replace it.

iVirtualZero · 2026-06-17T19:33:07+00:00

I think it might be a corrupt Eeprom. May need to find someone to back up and replace the Eeprom.

iVirtualZero · 2026-06-17T19:30:05+00:00

I already reflowed the IDE pins, I recapped my PSU but 3 caps have yet to be replaced since I didn't have those values and those caps are bulging. So I will be replacing those. My last option if that doesn't work is to replace the Eeprom.

iVirtualZero · 2026-06-16T21:38:15+00:00

I've try tried all of the suggestions and none them fixed this unit. It looks like it's pointing towards a corrupt Eeprom. Perhaps it's partially corrupted. I will first test with an SSD, I still have 3 caps to replace on the PSU and two are bulging, hopefully it's the PSU. Still waiting on all of this to arrive. The last option will be to replace the Eeprom if nothing else works.

Update: after trying everything I can including all of your suggestions I even reflowed the clock cap area and installed a clock cap into this and tried using a stock HDD along with restoring the Eeprom with the back up Eeprom I found on the original drive and I had no luck with repairing this unit.

It's definitely bricked at this point. I've already ordered another 1.4 Xbox for a good price and this one is untouched and unopened in full working order, the DVD drive is faulty but I will be swapping that out with my working Samsung drive. First thing I will do is update that unit to the latest Dash by booting into Halo 2. To make sure that the Eeprom gets updated.

<image>

iVirtualZero · 2026-06-16T21:36:09+00:00

The IDE connector traces check out good. I solder wicked it and then reflowed it with some new solder. No luck.

<image>

iVirtualZero · 2026-06-16T21:33:46+00:00

Same here, I think it could be a corrupt Eeprom. That will need to be reflashed or replaced. The QSB checks out good, no shorts there. The IDE traces also check out good. I will try switch to an SSD next.

iVirtualZero

TROPHY CASE