I got my X2.2 Lite + to install fine, the green LED comes on with chip disabled. I got the Cromwell to update with the Xecuter2 4977.

Now when I go to install Evox 3752 the XBOX just turns on, powers off, turns on, powers off then turns on again and hangs with the eject LED blinking. I can't open the tray or anything from there, it just hangs. What is wrong? Did I flash the BIOS bad?

I don't think I did the BIOS update wrong because it said it updated the BIOS on the screen then automatically shut off. So I went and I burned the Evox 3752 ISO and put it in but now it does the 3 times reboot.

What did I do wrong? The original M$ BIOS loads with the chip disabled so that is OK. I think the Xecuter 4977 is bad. Thanks.

How would I go about re-flashing the Xecuter 4977 onto the chip? Will starting over fix the 3-reboot problem?

Thanks

This is a fairly typical case of "that damn Cromwell bios licks ass". Appearantly there is some sort of a flaw in it. This happens about 50% of the time it looks like (from the posts here).

QUOTE

I think the Xecuter 4977 is bad.

The bios image that you have is probably ok, you will just need to find another way to flash it. Since this is a lite you will need to either buy a programmer or find a working modded box and do the swap and flash method.

Dammit. Where can I get a programmer for cheap? How much does it cost?

Thanks for the perfect reply though. I guess I gotta do some shopping.

i had that problem just keep turning ur box on and off while messing with the switches and u'll get it soon.......

QUOTE (WodMan @ Aug 2 2003, 08:41 PM)

This is a fairly typical case of "that damn Cromwell bios licks ass". Appearantly there is some sort of a flaw in it. This happens about 50% of the time it looks like (from the posts here).

I have flashed clean from the FlashBIOS about 20 times to this day and I have never had any issues. No offense, but you just have to do it right. It's picky how it wants things done.

QUOTE

I don't think I did the BIOS update wrong because it said it updated the BIOS on the screen then automatically shut off. So I went and I burned the Evox 3752 ISO and put it in but now it does the 3 times reboot.

Bad BIOS flash, you sure you created a 1MB BIOS image file properly using x2bm? You could've loaded 4 256k x2_4977 BIOS files into the one image file via x2bm; but if you only tried to flash a 256k BIOS image that's your problem. Either way, the BIOS flash is fubar'ed, so chances are you will need to get a hold of an X2 Lite programmer - system-mods.com usually has them in-stock and they run about $15 each.

QUOTE

Dammit. Where can I get a programmer for cheap? How much does it cost?

http://shop.system-mods.com/product.asp?3=95

You can get the programmer there, it is $15.

QUOTE

QUOTE (WodMan @ Aug 2 2003, 08:41 PM) This is a fairly typical case of "that damn Cromwell bios licks ass". Appearantly there is some sort of a flaw in it. This happens about 50% of the time it looks like (from the posts here).  I have flashed clean from the FlashBIOS about 20 times to this day and I have never had any issues. No offense, but you just have to do it right. It's picky how it wants things done.

I haven't done it even once personally, but I see lots of posts about it.

When I loaded the BIOS into the BIOS manager program it said it was a 1024KB bios so it said it would place it through all four of the banks. I thought this was right.

Anyway I have played with the switches ALOT while turning the XBOX on and off. What do you reccommed I try with the switches and powering on and off? Any particular method of switch flipping? Thanks for all the replies guys.

Make sure all your hardware is connected inside your xbox. (hd, dvd, etc.) also test your xbox using the standard rca cable.

All the hardware is cool because I can still run the XBOX without the chip in. Play music and play games so that is all good. Plus when I initially flashed the BIOS from Cromwell the Xecuter it worked perfectly. It updated the BIOS and then shut off automatically. I know I have done everything right but I guess the BIOS to begin with was bad.

NM