I have finally convinced two of my friends to mod their xboxes, so they go and order up 2 of the Xecuter2.2 Pro chips, and we get them all installed. I got the xecuter2 bios manager, and a copy of 4977 bios. I connected the programmer to the pc (At first using a 6 ft. DB25 cable, then trying a direct connection between the xbox and the pc w/ no cable (we hadn't stickied down that piece on the back yet)) and i do 'info', which is retreiving the correct values (Manufacturer 0x01 Device Code 0xD5), so I proceed to select 'write'. This takes just under 2 minutes, and then the verify consistently fails w/ reading from 0x03 got 0xFF expected 0x00 or something very close to that. I would go into more detail if i could, but this is an after the fact post. We are going to 'hopefully' start round 2 tomorrow

Oh and also, while flashing I have the dip switches as follows

Modchip disabled, 1-2-3 off, 4 on

I have rerun the 'write' multiple times, both using the 6 ft cable, and the direct connect, still the verify always fails.

Any help would be greatly appreciated.

Have you tried to see it if works i get the same error but it does flash .

I was just assuming that the flash had failed because of the verification errors.

Sweet, thx alot, it turns out that the write did actually succeed. Xbox boots w/ Xecuter2 logo now, then to msdashboard (EVOX not yet installed).

Thanks again

i had the same problem with my X2.2pro just last week when i tried to install it. Just to be safe, I only flashed it with the newest Cromwell BIOS, then used a boot CD to flash it with Xecuter, and that worked without a hitch.

BTW - having a failed verification is a common issue with this program. From everything I read when I was going through the process I drew the conclusion that it seemed as if cable length and connection affects this factor first and then only later the ability to find the chip. When people went with shorter cables or port-to-port the verification improved greatly - it also improved finding the chip itself but some people just had bad installs or hardware quirks to begin with as port-to-port didn't always resolve this problem.