Print

[ftothe3]

no. it cant really get corrupt unless u touch the chip and kill it with static electricity. whats the exact error you get? how do you know the bios is the problem in the first place?

[ArcticWolf]

I've heard of two incidences.
In one incidence, the Xbox fragged after one week.  I assume that fragging is due to corrupt BIOS.
In another incidence, after one day, the Xbox powers on, but the video is black and white, and the screen scrolls up, so it's hard to see the screen.  You can see the EvoX menu, and also able to launch apps and games, but the screen is black and white, and the frames scroll up constantly.  Almost like a bad reception using the classic rabbit ears antenna.

[kman308]

QUOTE

the screen is black and white, and the frames scroll up constantly

That could be a PAL/NTSC eeprom setting issue.

[ArcticWolf]

Hey kman308, but this guy says that he never touched that setting.  It happened while he was playing Ninja Gaiden.  Could something like tha occur spontaneously during a game play?

[ArcticWolf]

Hey kman308, you're the man!  Yeh, it was the NTSC/PAL setting.
I'm just wondering how it could've spontaneously switched while playing Ninja Gaiden,...

[DaShiZNiT]

[ArcticWolf]

Yes, I agree with you all.  A defective TSOP flash is evident immediately.  If the Xbox works right after the TSOP flash, then the flash was good.  If something goes wrong days or weeks later, then they were mucking around with it.
The problem arises from the customization of the BIOS with personal preferences to alter the flubber animation, or to make the Xbox logo red, or something like that.  If you don't do it properly, then you can end up with a $150 paper weight.
A bit off topic,... but I had one guy who wanted the TSOP flashed, and he told me that the Xbox suddenly stopped working; it kept rebooting repeatedly.  He *swore* to me that he didn't do any modifications with it.  He first gave me only the Xbox and a bigger HD, but not the original stock HD.  When I asked him more about the repeated rebooting, it sounded very much like the infinit clock loop, but he swore that he didn't muck with the Xbox.  I told him that I will need the original stock HD anyway, because of the locking code.  When I unlocked the HD and looked inside, there was the familiar Phoenix file and the font exploit.  The Xbox was in the infinit clock loop, after the black out due to the thunder storm.  After I flashed the TSOP and revived his Xbox, I called him up to confront him, but he has no idea how the Phoenix file got there.  He has no roommates, only a dog.  He made a joke that the dog may have been screwing around with the Xbox.  What's surprising is that even with an irrefutable solid evidence, they will continue to deny everything.  Is it because of embarrassment, pride, guilt, or what?  Since this guy is paying me for a service, who cares?!  Am I naive for trying to find logic in human nature?

[hawgman]

some of early tsop I had people screw them up like that, but now I try to
make them idiot proof. I disable the flash points after the flash and
I dont leave any apps that they could screw anything up with like
enigma videoswitcher .. and in some cases i have even
passworded all apps and only allowed games to be played..

and since ive taken those preacutions not one has come back for
problems...

[zipo1200]

i do the same. but i leave the soldier points on there just in case they want to come back for an update.

i just disable the command line in the EvoX.ini.

and the tsop would be corrupted imediatly.

[zipo1200]

sorry i should refrase what i wrote. the tsop that was flashed with a bad rom. would be corrupted imediatly after  being flashed. its good just to open the *bin file in XBtool just to make sure the setting ias good. also a good idea your flashing the right rom into the right size tsop

[pepsik]

Yeah they always muck something up and bring it back for me to fix. About the fragging box, you should take a look at all the IDE connectors, I've had a few that where not in place properly, and that solved it.