Xbox Dead? Xecuter 2 Pro Code 16 Options

[shanebuss]

I have an xecuter 2 pro mod chip, i think v1.0 (not sure how to checK)
it has worked fine for a year or two, but now i get a code 16 when i boot my xbox. I understand this is a bios clock problem. I try setting my dip switches to all settings (including off), no avail. So i assume my bios is corrupt. I connect LPT cable to try to flash and get code FFFF on every setting. Also, im not getting a light on the modchip, but im not sure if the v1.0 even has a light on it?

Did the modchip just die? What is the next step from here?

Thanks
Shane

[atomiX]

try disabling the chip and letting the MS dash boot so you can set the clock. after that is done, reboot with chip on. if it still does it, then reflashing might be a good idea, just get the newest X2 bios (either with X2CL or 4983). your chip needs to be disabled and the xbox powered on before you can flash. also make sure flash protection is off and that your dip switches are set correctly.

[shanebuss]

thanks for the reply.

Even when i disable the chip i still get error 16. For whatever reason when i connect my external programmer it gets code FFFF and cannot read/write the bios.

I see some posts where error code 16 is a corrupt dash. I am thinking about trying to hot swap the drive and rebuild the C partition.

Should there be a LED on the Xecuter 2 pro V2.0? There isnt one lighting up if there is.

[(((XYU)))]

is it possible for you to reflash the chip...if it is try that and see if things work

[shanebuss]

is it possible for you to reflash the chip...if it is try that and see if things work

does anyone even read my posts?

I just get error FFFF when i tried to read the chip, it cannot detect it for some reason. I think the modchip might just be bad.

Is there a LED indicator on the xecuter2 pro v2.0 chips? If so, mine isnt coming on

thanks

[shanebuss]

to the top.. it would be very helpful to know about the LED.. then i would know its either the connection or the chip is dead

[atomiX]

thanks for the reply.

Even when i disable the chip i still get error 16.  For whatever reason when i connect my external programmer it gets code FFFF and cannot read/write the bios.

I see some posts where error code 16 is a corrupt dash. I am thinking about trying to hot swap the drive and rebuild the C partition.

Should there be a LED on the Xecuter 2 pro V2.0? There isnt one lighting up if there is.

yes, corrupted dash could also be the problem. From my experience, error 16 is mostly rare. It happens when the clock looses it's setting (power unpluged for a while) and the dash cannot be loaded to reset it. As soon as the kernel detects an invalid clock, it tried to load the dash. When it can't, it outputs error 16. This means that your dash is either completely missing or corrupt. Either way, it can't be booted.

This problem usually doesn't happen when you have a chip installed since almost every recent hacked bios bypasses the clock problem and allows a boot no matter what.

I assume your only possibilities would be to flash your chip (if you can get your PC to recognize the chip) or to hotswap and restore the MS dash. (make sure it's xboxdash.xbe and not something else).