Print

[sl_stealth]

Hi guys,

I bought an xbox yesterday and soldered it so i could use the 007 exploit.
That all worked fine. I flashed the bios to M7 with the TSOP flashkit.
Today I used eepromagic to flash the evox m7 bios with ejectfix because I
needed the fix.
Both the bios-files (with and without fix) are from the same .rar-file.
But anyway, i flashed the tsop and restarted.
All i get is 1 green blink, than a orange blink, and than it keeps blinking red.
My eject-button and power-button still work but i get no image on my tv.
Any advice?
I saw a tutorial about using 1/4 of the bios because i thought maybe that was
the problem but my mobo layout differs.

Thanx in advance

Stefan

This post has been edited by sl_stealth: Sep 28 2003, 11:17 AM

[lordvader129]

hmm, thats odd, i never heard of an error blink like that....do you know what version xbox you have?

edit: reread your pos, ok, so you flashed with the EF M7, then REFLASHED without EF? im confused as to why

This post has been edited by lordvader129: Sep 27 2003, 05:56 PM

[dddooo]

I'm a noob but here's some stuff to dblcheck.

did you use xbtool to verify that your bios was not corrupted?
you verify that bios is pal or ntsc?
did you verify the size of your bios? (256kb for v1.2 and up)  (1024kb for v1.0 and v1.1)
have you tried to boot xbox with a normal xbox game or slayer's install disc?

When I did my tsop flash I remember having something similar happen but  I think it was 1 green blink and then flashing orange.  I think it was that my dash was screwed up.  It was still able to boot off dvd drive.

[Nimrod3]

i think your best bet is to go and install a chip at this time...

[sl_stealth]

The first bios I flashed was the M7 without EjectFix. I did this with the 007 exploit.
I wanted to update the bios to M7 with EjectFix. The 2 bios files are both from the
same .rar-file. The first one worked great so assume that the other one is also PAL
and the same size.
Is it possible that Raincoat writes the 256kB file 4 times to the bios and Eepromagic 1 time?

Antoher question:
Does a(ny) chipmod work with an empty or corrupt onboard TSOP?
They told me that a modchip needed the onboard bios too, but I think that's odd
because I thought a mopdchip totally replaces the original one.

[sl_stealth]

Some info of my Xbox:

It's a v1.2 or v1.3

Bios: Winbond - W49F020

Manufacturing date 2003-03-25 (int.)

This post has been edited by sl_stealth: Sep 28 2003, 11:18 AM

[F-TIMMER]

"Does a(ny) chipmod work with an empty or corrupt onboard TSOP?"

you can use the homebrew mod (32 wires) . follow the tutorial on wiring start your box go into evox . cut ground and vcc on chip then flash with evox.  

[sl_stealth]

QUOTE (F-TIMMER @ Sep 28 2003, 02:26 PM)

"Does a(ny) chipmod work with an empty or corrupt onboard TSOP?" you can use the homebrew mod (32 wires) . follow the tutorial on wiring start your box go into evox . cut ground and vcc on chip then flash with evox.

If I could get into evox I did'nt have to post this topic.

[Scan-C]

he meant after you installed the homebrew mod which actually uses 29 wires to the mobo.

[Perplexer]

QUOTE (sl_stealth @ Sep 28 2003, 07:03 AM)

Does a(ny) chipmod work with an empty or corrupt onboard TSOP? They told me that a modchip needed the onboard bios too, but I think that's odd because I thought a mopdchip totally replaces the original one.

First-generation modchips like the Enigmah and Xtender "patched" the original BIOS on the TSOP, so they will not work with a corrupt TSOP.

But LPC mods and homebrew mods bypass the TSOP and you will be able to boot from your modchip.  If you want to reflash your TSOP, use the homebrew chip, and if you don't care, then go with the easier LPC mod.

[sl_stealth]

I can buy a x2lite from a guy 15 km ahead for 35 euros.

Can I use my Xbox again with this chip?

According to xbox-scene.com it bust me a non-

• 
  chip and my xbox must be a v1.2.
  According to the s/n it is.
  
  I hope this will work.