I purchased a modded Xbox a while ago (to be honest, I don't remember if it was soft modded or hard modded). Anyways, I want to change the green slime boot logo to how it is on an unmodded Xbox. Currently when my Xbox boots, it still has the green slime startup but there's an "evo x" logo on the top left and the Xbox logo is red.
Is there anyway I can change it back?
It looks like this, but the Xbox logo is red.
Your box is not softmodded, it's using Evox m8 BIOS so either has a modchip or the TSOP is flashed.
To remove the Evox triangle, you can either flash a customised m8, or a bios which doesn't have it, such as X2.4981 (what I use most often).
But you must try to identify the type of hardmod and the version of Xbox motherboard you have before you change your BIOS because some BIOSes are unsuitable for some modchips/TSOPs motherboard combinations.
spicemuseum wrote:Your box is not softmodded, it's using Evox m8 BIOS so either has a modchip or the TSOP is flashed.
To remove the Evox triangle, you can either flash a customised m8, or a bios which doesn't have it, such as X2.4981 (what I use most often).
But you must try to identify the type of hardmod and the version of Xbox motherboard you have before you change your BIOS because some BIOSes are unsuitable for some modchips/TSOPs motherboard combinations.
is there anyway to identify the type of hardmod/xbox motherboard I have without opening the console?
There are software ways to identify the flash chip from which your BIOS was loaded. raincoat and probably a custom version of EvolutionX Dashboard with a shitload of chip ID definition in its config.ini file might help you out (hexen's disk has one I think). This is all neat but it would be easier for everyone that you just snap a picture of your motherboard. you only need to remove the top case, HDD and finally DVD drive.
It's important. You need to know what's the size of your flash chip (whether it be a modchip or your onboard TSOP).
In order to flash a new BIOS, you need to completely overwrite the old one already in place.
So for example you wish to flash a customized version of EvoX M8+ (no logo and other cool stuff). This BIOS comes in 256KB size by default. If you have a modchip that takes 512KB BIOSes and you only flash the first 256KB, the Xbox will end up loading a 512KB BIOS essentially composed of 2 different 256KB BIOSes and return a redundancy checksum error (probably FRAG). Now you'll regret not taking the time to check your flash chip size.
You need to access Xenium OS and flash a bank from there. I read Xenium OS 1.0 boots into OS mode by holding the white button on boot while OS 2.0 boots into OS when powering console from the eject button.
Xbox 1.6 don't have much choice of BIOS. EvoX M8+ and X2 5035 are the two retail hacked BIOSes available. there is also a hacked X3 bios but I wouldn't use it.
psyko_chewbacca wrote:Xbox 1.6 don't have much choice of BIOS. EvoX M8+ and X2 5035 are the two retail hacked BIOSes available.
Note, on a v1.6 you'll need the M8+16 verison of the Evox BIOS.
If you want fast start-up then you'll need to stick with M8+16 and hand-modify it using EVTool (search the forum) to remove the flubber.
If you're not worried about fast start-up then go for the X2.5035 (although that has the annoying XecuterRoxMyBox image at the end of the flubber which I can't remember whether you can remove or change in the config on the hard disc). It's slower to start-up because it gets a config file from hard disc at start-up, so it needs to wait for hard disc to initialise, whereas M8+16 does not.
psyko_chewbacca wrote:Xbox 1.6 don't have much choice of BIOS. EvoX M8+ and X2 5035 are the two retail hacked BIOSes available.
Note, on a v1.6 you'll need the M8+16 verison of the Evox BIOS.
If you want fast start-up then you'll need to stick with M8+16 and hand-modify it using EVTool (search the forum) to remove the flubber.
If you're not worried about fast start-up then go for the X2.5035 (although that has the annoying XecuterRoxMyBox image at the end of the flubber which I can't remember whether you can remove or change in the config on the hard disc). It's slower to start-up because it gets a config file from hard disc at start-up, so it needs to wait for hard disc to initialise, whereas M8+16 does not.
You can change the Xecuter logo by placing a file called x2logo.bmp in the root of your E:\ drive. I think it needs to be of a precise resolution but I can't tell you what it is.
spicemuseum wrote:
If you're not worried about fast start-up then go for the X2.5035 (although that has the annoying XecuterRoxMyBox image at the end of the flubber which I can't remember whether you can remove or change in the config on the hard disc). It's slower to start-up because it gets a config file from hard disc at start-up, so it needs to wait for hard disc to initialise, whereas M8+16 does not.
You can change the Xecuter logo by placing a file called x2logo.bmp in the root of your E:\ drive. I think it needs to be of a precise resolution but I can't tell you what it is.
Yep, that's it! From memory, I think the default config file contains a comment giving the dimensions.
xman wrote:If your going to mod an M8 bios how about something like this?...
The settings are something like these.....
Screenshot custom bios.JPG
that evtool looks like exactly what I need. does it just read my bios via FTP? and if so, where is my bios located? sorry for the general newbiness, I just want to make sure I don't brick my Xbox hahaah
What you need to do is tell me exactly what modchip you are using and then I can send the size bios you need. Get this right and you won't brick it. It won't damage your Xbox itself, only the chip if this is wrong and it won't brick the modchip if you accidentally load the wrong sized bios but you'll need another modchip to re-flash the one that has been loaded with the wrong sized bios but we won't get that error will we. You'll need a copy of EvoXDash and FTP that into your apps folder. Just make sure it is the "Full" version of EvoXDash, not the short version as used on the 2.7 Slayer's disc as you need the "Utilities" feature in EvoXDash and the Slayer's version doesn't have it.
Hi ....i found on the net this program: Xflash for SST49lf020 v2 that seems to be perfect for my modchip ( strange i have console version v.1.6 or v.1.6b) and seems that modchip is from model 1.0 to 1.5).
So i've read on the net that before flashing is correct to disable protected mode?? what is?
Another thing i've noticed is that changing options with evtool after saved when open again changes also MD5 numbers and letters is normal??
What do you think about Xflash for SST49lf020 v2 program? I would use the hacked bios made with evtool with Xflash for SST49lf020 v2.Is risky?
i would notice that originally my xbox was pal but i used enigmah to change region to NTSC and i've replaced original hard disc with another with 160 GB.Should i chamge some setting before attempt to flashing?