Hello.

Anyone knows what could be about? It just shows the Xecuter 2 text under the blue logo and then reboots. Happens when you try a boot DVD as well. Tried different HDs and different DVD-players. Still the same thing. Sounds like a "Clock Loop" but thats not possible with a modchip and a boot DVD is it?

Anyone got ideas or have experienced this before?

Regards

Aladdin

awfull bump, but this is what happens to me aswell actually, i have even rebuilt the HD with xboxHDM and the problem persists

What does it do with the modchip disabled?

with the modchip disabled it boots wit the normal green X, however an error pops up, but this is probably because my harddrive is unlocked ( so i do need the chip)

2 possibilities i can think of....

• bad flash (wrong .bin(ary) image size, or corrupt .bin(ary) image.
• shtty install

i'm leaning towards bad flash from a bad download, or a 512KB image squeezed down to 256KB. checksums are your friend. get a second opinion on that bios image (get it somewhere else that you can do a checksum).

I strongly doubt it has anything to do with the chip, since this has remained untouched since it was first time installed. It has worked fine for a very long time, with a 120gb harddrive.

At some point the drive was taken out, wiped and used in a windows pc, the xbox has been lying safely in a box until recently. I tried putting the same harddrive back ( formatted it, even made it RAW using some software, and when all that failed i tried this xboxHDM thingy)

So far no good.


My guess would be then that these installs would be corrupted, but i also seriously doubt this one because i have downloaded several versions of slayers, severeal times, downloaded xboxhdm twice, put at least 4 kinds of different software in the C folders ( varying from original xbox dash to evox to avalaunch)

So far no succes

did you format the drive again with fatx? based on what you have said, the xbox is booting to a hard drive with no partitions.

not likely a HD issue. if it was, xecuter would spit a service code out.
when you have a chip, you can put any HD in it, even unpartitioned and unlocked or locked to a different xbox.
you should still be getting an error code.

i still think it's a bad bios image or faulty chip or faulty install.

what happens using the other bios bank on the chip?