Post by: EXCURSION-CRUSHER on January 11, 2004, 04:55:00 PM
Post by: maxsee on January 12, 2004, 12:42:00 AM
| QUOTE |
| Your Evox file which comes as default.xbe - you rename as evoxdash.xbe |
Copy over the files "default.xbe" and "evoX.ini" to your HDD. If there is a skin and bios folder, you can copy those as well, but they aren't needed.
After you copied them, rename the "default.xbe", thats on your Hard-drive, to "xboxdash.xbe".
After renaming, go up one so you can see the xbox drives.
Click and go into the "C" drive. The file on your Hard-drive that you will be changing is the "xboxdash.xbe". DO NOT DELETE OR OVERWRITE THIS FILE. Rename it to "MSxboxdash.xbe" instead.
Then when you renamed it, copy over the evoX "xboxdash.xbe" and the "evoX.ini" to your Xbox HDD.
Post by: NeoKast on January 12, 2004, 04:04:00 AM
Post by: Auximines on January 12, 2004, 06:46:00 AM
Everything was fine until I put the top back on.
Thanks for your posts, though.
Post by: esc1 on January 12, 2004, 06:58:00 AM
Post by: 82ross on January 12, 2004, 02:00:00 PM
When the big green x comes up with XBOX written underneath in green. Underneath that should be some white letters.
If it says MS, your chip isnt connected properly or i switches off. If it says xecuter2 the chip is fine.
When you get it back, rename the origional xboxdash.xbe now called msxboxdash.xbe to its origional name.
Rename the current xboxdash.xbe to evoxdah.xbe aswell. This means that if you chip ever failed again or when it is switched off (when it says MS) your xbox will boot normally to the normal green dashboard and you wont get the service eror. And when it is working it will boot nicely to evolutionX.
Get back to us when you know what comes up in white under the green xbox letters.
Post by: maxsee on January 13, 2004, 11:03:00 PM
| QUOTE |
| The logo that appears after the flubber animation said XECUTOR2 when it worked, now it says nothing. Just gives me the FRAG lights and hits the error screen. |
This what you should do for Xecuter Bios. It has 1 MB Bank!
FLASH ONLY one of the two banks! That way if you mess it up you can reboot to cromwell and try again. Here's how:
FIRE UP X2BE. Choose 512k bios. Yes, 512k, not 1mb! Fill in the first two banks with your X2 hacked bios that you downloaded. Then save the results as bios.bin (the default file.)
BURN IT. Get Nero and a blank CDRW. Take a 100mb random file on your HDD. Rename it to 0dummy.bin. Add this file and your bios.bin file to your compilation. Burn at 2x, DAO/96, FINISH CD. This is your BIOS CD.
FLASH IT. Turn off your XBOX. Set the external switches to "ENABLED, BANK 2, UNPROTECTED." Turn it on and get cromwell. When it prompts, drop in your newly minted bios CD. Wait for it to do its thing. When its done, it will turn off the XBOX.
USE IT. With the power still off, set the external switches to "ENABLED, BANK 1, PROTECTED." Say a quick prayer and turn on your XBOX. You should get a flubber with the Xecutor 2 message. Congrats!
IF YOU EVER NEED TO REFLASH, just set the external switches, with the power off, to "ENABLED, BANK 2, UNPROTECTED" . Then turn on your XBOX. It should boot into Cromwell and you can then reflash your bios.
Credit To U2mir
maxsee
singapore
Post by: PolarBearWY on January 13, 2004, 11:43:00 PM
| QUOTE (Auximines @ Jan 12 2004, 04:46 PM) |
| It just says "connecting" and hangs |
I just installed an AppleX V and the chip works great. When I booted to an Evox CD, I could not connect via FTP. I found that CuteFTP defaults to HTTP when I used "quick connect" instead of FTP protocols. I switched the setting, and was connected to my XBox within milliseconds. Do you possibly have a similar problem?
Post by: moddedoutxbox on January 14, 2004, 02:06:00 PM
you say it does not boot your Evox CD???
when you got that EvoX file was it in ISO of did you see the files in it?
if you saw the files in it did you just write it as a data CD or as an Xiso CD useing an Xiso program to make the Iso?
Post by: Auximines on January 14, 2004, 06:03:00 PM
Even if the filenames on the HDD are wrong, shouldn't I get the XECUTOR2 logo if the chip and BIOS are good? I don't get any logo at all.
Post by: maxsee on January 15, 2004, 12:52:00 AM
| QUOTE |
| Are you sure it's the BIOS? I have a 2.3b Pro so I flash the BIOS with the LTP port, which works fine. I created a 1Meg file and flahed it that way, it worked great, came up "XECUTOR2" and everything. It's only after I put the top back on that it didn't work. Would it still say XECUTOR2 at the flubber animation if the BIOS was good? And my FTP settings are good. I used FlashFXP and it worked just fine. That's how I renamed the dashboard files. Now when I try to connect it won't work, I'm pretty sure it's because there's no dashboard loaded. I'm beginning to think maybe the chip itself is bad somehow. Anyone know a way to test it to find out? |
Okay here is what you should do
Go back when it first started..
1.Recheck the modchip - check any loose end wire
2.Recheck whether the modchip is on - enable
3.Reboot - recheck and see the xecuter2 logo at the bottom
4.If No - next option - FTP and see your xbox HD at C drive - see any missing files
5.Next get Slayers Boot Disk - boot with Slayers Disk - under Identify Your Bios/Mod Chip
What it does is it will load a program to ID your bios and modchip inside your Xbox. If is able to ID then there is nothing wrong with both of them. Next if your MS dashboard is corrupted then it will not load
Good Luck!