I have a feeling I know the answer but wanted to double-check.
Successfully installed pin-head 2.6 (don't think this is a CE, bought from system-mods) to a previously modified v1.0 XBox. Got the flashBIOS screens on both banks.
So the trick now was to load up EvoX M8 so that it would reference the dashboard already on the drive. No big issue.... Following various instructions found in this forum, I used the network option to upload FlashBIOS 3.0.3 to Bank 1 and Evox M8 to bank 2 using X2DM to create the appropriate bin file.
Unfortunately, we had little info on how the hard drive was configured, we were guessing at what drive to have Evox M8 reference for the dashboard. Being methodical, I started with the C: drive (default). Launched the Evox BIOS off of bank 2, but no dashboard. Okay, no problem, start up again on bank 1 and do a network flash, this time with a modified to look in the E: drive (using EVTool). Still no good.
Switched back to bank 1... and I get frag-ed. So now I have a working Evox M8 BIOS in bank 2 (but no dashboard), and what seems to be a bad flashBIOS in bank 1. After searching through this forum, it seems to me that my only option is to use a flash programmer. Is this in fact the case? Or is there some other way that I can re-flash the chip without having to loose everything on the hard drive?
Am I safe in assuming that this was just a bad flash? I'm thinking that since Evox M8 launches from Bank 2 that the chip mod is sound.
Also, do I need to use the Xecuter Programmer, or will any programmer do?
I'm open to other options, but my experience with XBox modification is a bit limited... but I did okay with soldering the pins in so I'm not afraid of a little work.
However, we would like to keep the contents of the drive if at all possible.
Thanks very much.
Successfully installed pin-head 2.6 (don't think this is a CE, bought from system-mods) to a previously modified v1.0 XBox. Got the flashBIOS screens on both banks.
So the trick now was to load up EvoX M8 so that it would reference the dashboard already on the drive. No big issue.... Following various instructions found in this forum, I used the network option to upload FlashBIOS 3.0.3 to Bank 1 and Evox M8 to bank 2 using X2DM to create the appropriate bin file.
Unfortunately, we had little info on how the hard drive was configured, we were guessing at what drive to have Evox M8 reference for the dashboard. Being methodical, I started with the C: drive (default). Launched the Evox BIOS off of bank 2, but no dashboard. Okay, no problem, start up again on bank 1 and do a network flash, this time with a modified to look in the E: drive (using EVTool). Still no good.
Switched back to bank 1... and I get frag-ed. So now I have a working Evox M8 BIOS in bank 2 (but no dashboard), and what seems to be a bad flashBIOS in bank 1. After searching through this forum, it seems to me that my only option is to use a flash programmer. Is this in fact the case? Or is there some other way that I can re-flash the chip without having to loose everything on the hard drive?
Am I safe in assuming that this was just a bad flash? I'm thinking that since Evox M8 launches from Bank 2 that the chip mod is sound.
Also, do I need to use the Xecuter Programmer, or will any programmer do?
I'm open to other options, but my experience with XBox modification is a bit limited... but I did okay with soldering the pins in so I'm not afraid of a little work.
However, we would like to keep the contents of the drive if at all possible.Thanks very much.
Last edited: