Thank you team Xecuter for being so ****ING BRILLIANT and including a backup bios! That is all. Good day.
Just Need To Make One Comment
- Thread starter ryawn
- Start date
yeah it's sure nice but only thing i dont like about it is... if people fail to read/know what to do on a 1.6b xbox and they happen to erase the flashbios v3.03 on the modchip... there pretty much screwed since all the modchips now ship with flashbios v3.01 on banks 1-4 and flashbios v3.03 on banks 5-8 ... and if u mess up banks 5-8 u have no traces of flashbios v3.03 left on the modchip at all since the backup bios im pretty sure ships with flashbios v3.01 on it which wont work with 1.6b xbox's.
but if u got a 1.6 ( not 1.6b )xbox or older u have nothing to worry about
if im wrong someone correct me
but if u got a 1.6 ( not 1.6b )xbox or older u have nothing to worry about
if im wrong someone correct me
Last edited:
Martin C
VIP Member
The problem, once again, is *not* the chip - it's pure ignorance.ThaCrip said:yeah it's sure nice but only thing i dont like about it is... if people fail to read/know what to do on a 1.6b xbox and they happen to erase the flashbios v3.03 on the modchip... there pretty much screwed since all the modchips now ship with flashbios v3.01 on banks 1-4 and flashbios v3.03 on banks 5-8 ... and if u mess up banks 5-8 u have no traces of flashbios v3.03 left on the modchip at all since the backup bios im pretty sure ships with flashbios v3.01 on it which wont work with 1.6b xbox's.
but if u got a 1.6 ( not 1.6b )xbox or older u have nothing to worry about
if im wrong someone correct me
You cannot blame the chip for user error. It's like saying "Windows XP sucks because I deleted a load of crap from the registry and now it won't boot".
If you've managed to boot banks 5678 for FlashBIOS 3.0.3, then you should have the common sense to read the flashbios guides and / or the X3 noob guides.
The user has to take some responsibility in all of this! If you're going to jump in with both feet then more fool you.
Martin
i aint really blameing the chip for the most part... cause like u said it's pretty much the users fault... but it would be nice if they could make it so no matter what u do to the bios's on the chip, there would always be a way to revive it, since the X3 was made NOT to need a programmer if a bios got messed up on it u know, unlike the Xecuter 2.6 modchip.
but for the most part i agree with you martin
but for the most part i agree with you martin
Last edited:
Martin C
VIP Member
Now *that* I do agree with.
There should be a way to get the chip working on a 2.x programmer - after all, the voltages and programming lines are the same! It's something I'm still working on and I believe that I'm about 80% there. I waiting for another X3 to come in - when it does, I'll try and nail this.
Martin