An Xbox issue I've never seen

Maybe someone can help me out , I have plenty of experience just never had this particular issue before

Xbox fires up normally , I can navigate through the menus but when I try to play a game , the game spins like it should and the xbox logo comes on like the game is starting , then goes back to dash with this error message




I've tried 3 drives , I know they are good , tried changing IDE and power cable , and multiple games , same error

Thanks for any advice

 

Have you tried tinkering with the eeprom? Try to load a backup.

If not I would advise clearing the cache partitions. Also, how much space you got left on each drive?

 

It's a stock xbox I got off ebay , hard drive is empty except SID5 and Splinter Cell gamesave , I cant get the eeprom which is the problem

I meant I tried 3 different DVD drives if that wasn't clear

 

If you can't get a game to load I have no idea how you're going to go about getting the EEPROM atleast short of getting a modchip and installing that. That's a very odd issue to be having. I'd figure something is either bugged with the EEPROM or just xboxdash.xbe

 

Yeah I figured this would be the place to ask , I've probably gone through 100 xbox consoles over the past 10 years , softmodding , and etc , never seen this error happen like that. Maybe Ill get a chip for it because its in such good condition , Thanks for the replies and keep them coming if anyone has any input

 

That's fake. I never see a Xbox showing this message

 

Is it a NTSC retail unit?

 

Best suggestion is if it's a 1.0 - 1.5 then do the softmod via hotswap (I did it for my Xbox that way),solder the TSOP points and flash a BIOS using HeXEn. After you flash it,to make it brickproof from BIOS flashes just unsolder the TSOP points (one thing I failed to do) and be happy with the BIOS you've chose.

Here's what BIOSes you should use:

1.0 - 1.1 Xbox - X2 5035 - this is for 512KB/1MB TSOP chips.
1.2 - 1.5 Xbox - hard to say,but X2 5035 for 512KB TSOP and X2 4981/iND BIOS 5003 for 256KB chips including W49F020T chips.

I chose those to know that you're on the safe side. NEVER try flashing any other BIOS than the one HeXEn unzips if you have a Winbond TSOP because Winbond TSOP flashing involves Gentoox and not EvoX like other chips.(EvoX detects the chip but won't flash it. Anybody know why?)

I accidentally did that with a X2 4983.06 BIOS and now my box FRAGS even without the video cable .

Modchip is good to but it involves soldering D0 to a via in order to disable the chip. TSOP is easier IMO,just practice on a dead board and you'll be able to do the TSOP in a few minutes. (soldering+flashing)

 

No, it's not. I've seen a couple of Xbox consoles do this, usually involving a messed up chipping attempt. The strangest one I've seen is a console that displays the Xbox Live service is currently down and keeps looping that message even if you've got an ethernet cable plugged in.

 

Thanks for the info NeC5552

yes

 

Winbond TSOP (W49F020) does not support block erase command. My guess is that Evox Dashboard only uses block erase command to erase the flash which yields no result on the W49F020 chip.
Gentoox loader will try to erase by block erase command first and fallback to chip erase command if necessary.

I know this because I've been toying with my Xbox TSOP during development of the OS. Nasty chip if you ask me...

 

Nasty indeed! In fact I feel stupid for killing my 1.0 accidentally (traces burnt underside while trying Llama's Coma Console Fix) because it had a Hyundai TSOP (anybody heard about a Hyundai TSOP?) and it was 1MB too,which would have made my life a LOT easier.

Anyways,found a strange thing in the HeXEn disc. The files to TSOP 1.0/1.1 Xboxes with 1MB TSOP are X3 3294! IIRC X3 couldn't be flashed but I must be wrong.

Also,is it good that I use a Philips DVD drive in my 1.4? Or should I replace it with a Samsung drive?
The Philips drive is the original 1.4 drive and the Samsung comes from a dead 1.1 Xbox.

And one final question: why did Gentoox say Flash Failed and made my Xbox FRAG when I tried to flash X2 4983?

 

Yoshihiro released a hacked version of the X3 Config Live to flash on any modchip. The downside is that you cannot change any "Live" settings. You're stuck with default boot paths, fan speed and such, I haven't look too much on this, I have a real X3.

Maybe it's this hacked BIOS that you find on the HeXen disc?

For your second question, I'd go with the Samsung drive. They are supposed to be of much better quality, reads media faster and last longer especially if you use recordable medias.

For your final question, Gentoox Loader flashes stuff without retrying in the event of a failure. It'll verify what's been wrote on the flash but will only throw you a verify error(you don't see it because the Xbox is instructed to reboot instead) without retrying to flash it.
I'm currently working on this annoyance. Maybe I will release an unofficial version of Gentoox Loader with this feature but it'll be in the OS of my modchip for sure.

 

Safe to say, it's EEPROM related... Probably a region issue, as it's throwing the xboxdash back up.

Get or build an EEPROM reader, then come back and share your results.

 

Yeah as hex said build a eeprom reader or buy on on ebay, dump your eeprom and keys and see if you can find a stock eeprom dump somewhere and flash back or find a copy of the xbox refreash disk (iirc that only touches the HDD)

 

Try holding down the power button and/or eject button. I picked up an Xbox once upon a time without knowing it had been modded, gave me this exact same error but booted into unleashx once I held down the button.

 

Guys I have exactly the same issiue these days with a unit a got. I replaced the ide cable, the cd-r and even installed 2 different modchips but nothing worked. It gives the same error on games and plays only music cds. It is a PAL v1.4 motherboard. If find a solution please let me know! Thank you!

 

I have only seen this issue with some retail kiosks a few years after the system launched. I am guessing the systems overheated in those enclosed systems and had problems.

 

Did you try manually formatting the cache partitions?

 

Kiosks have two fans, they barely overheat.