OG Xbox - EEPROM error (flashing red) no matter what modchip I use.

[Lina_Inverse_]

Hi, I have a 1.4 revision Xbox which is modchipped with a generic Aladdin XT Plus2, it was modified many years back and was working normally when put away, Now when I turn it on, I get 1 green flash followed by red flashing of the LED. It does not matter the modchip I use which are all Aladdins, and have been proven tested/working in other consoles.

The power LED initially flashes green once and then red. No video/audio on TV.

I should add, it is only the left half of the LED that is flashing. I suspected it was due to the trace rot repair, but reversing this did not help. It was working normally when put away.
The console powers up without even the front panel buttons connected.

No solder splashes that I can see.

Attempting to reverse the mod entirely (removing D0 point grounding and chip) I get FRAG.

[KaosEngineer]

The configuration EEPROM on the motherboard died, is no longer accessible or the data stored inside is corrupt.  No Xbox BIOS that allows you to run XBE files (play games) will boot with a bad EEPROM.  Some of the modchip OS's will boot without a good EEPROM or access to it.  IIRC, FlashBIOS and other Cromwell-based BIOSes will too but you cannot do much with them other than boot Linux or flash a different BIOS to the modchip.

Use a Raspberry PI, Arduino or serial EEPROM reader/writer cable to read the contents from the chip.  Load it into LiveInfo v1.6. It will probably show that the content is corrupt is all which you already know from the RED flashing Eject ring.

Do you have a backup of the EEPROM's content. An eeprom.bin file on your PC?

If the chip is dead, remove and replace it with a new one and write the eeprom.bin file's content back to it.

[KaosEngineer]

Powering on when plugged in  - trace rot on the bottom side of the motherboard along the front edge.

[Bowlsnapper]

18 minutes ago, KaosEngineer said:

The configuration EEPROM on the motherboard died, is no longer accessible or the data stored inside is corrupt.  No Xbox BIOS that allows you to run XBE files (play games) will boot with a bad EEPROM.  Some of the modchip OS's will boot without a good EEPROM or access to it.  IIRC, FlashBIOS and other Cromwell-based BIOSes will too but you cannot do much with them other than boot Linux or flash a different BIOS to the modchip.

Use a Raspberry PI, Arduino or serial EEPROM reader/writer cable to read the contents from the chip.  Load it into LiveInfo v1.6. It will probably show that the content is corrupt is all which you already know from the RED flashing Eject ring.

Do you have a backup of the EEPROM's content. An eeprom.bin file on your PC?

If the chip is dead, remove and replace it with a new one and write the eeprom.bin file's content back to it.

The PicoProm would be perfect for this