xboxscene.org forums

Author Topic: I Think I Might Have Nuked My System  (Read 33 times)

dogbert

  • Archived User
  • Newbie
  • *
  • Posts: 16
I Think I Might Have Nuked My System
« on: July 29, 2003, 08:28:00 AM »

if the xbox resets three times and starts then with a flashing green/red light, the tsop doesn't contain a valid bios. the only way to restore the onboard tsop is to apply the homebrew/matrix mod. if u've got an xbox v1.0/v1.1/v1.2, u could revive it with a cheap and flashed lpc mod (but u won't be able to reflash your onboard tsop with an lpc modchip unless ur xbox is a v1.0 model).
Logged

[)eacon]ndigo

  • Archived User
  • Newbie
  • *
  • Posts: 32
I Think I Might Have Nuked My System
« Reply #1 on: July 29, 2003, 10:43:00 PM »

QUOTE (RacerX2k2 @ Jul 29 2003, 12:19 PM)
I flashed my tsop with an evox d6 bios. I just tryed xbtool to change the colors and the led color. I copied over the modified bios file to the xbox and updated it. Now when I reboot my xbox all I have is a plain black screen but I have the red led, which was one of the options that I chose in xbtool. Now my question is: is my bios fried? is there anyway I can get back or copy over my old bios file so I can get the xbox working again? somebody please help!!

There seems to be a problem with LED color patching and the Evox BIOSes. I don't know why, but I never saw it happen before. I'll look into this further and see if I can figure out what's causing it.

Meanwhile, I find (and have seen a couple of other reports) that pressing the eject butting after the screen goes black allows the boot to complete. Strange.

SantMat did the LED color patch, so I'll see if he has any ideas (if I can find him smile.gif. I've looked at them, myself and see no difference between the way it works on Evox and the way it works on X2.
Logged

[)eacon]ndigo

  • Archived User
  • Newbie
  • *
  • Posts: 32
I Think I Might Have Nuked My System
« Reply #2 on: July 30, 2003, 07:52:00 AM »

Ok, this issue should be fixed in the 1.0.1 final release. I'm not sure when this bug crept in but get 1.0.1 if you use D.6 firmware.
Logged