I didn't FTP the bios to C: on the XBOX and haven't had a problem. I just run it from the save though. Got Mame to run and a few homebrew demos. Now I just transfer the save to whoever's XBOX that wants it and just FTP and sign the applications or emus that they want to use. I'll probably try to get it to boot with EVOX this week.
you have to put in the game every time you wanna play it. Also this tut is very old and there are much better alternatives
http://forums.xbox-s...howtopic=243341
ANY1 WHO GETS THIS COMPLETELY IM ME PLEASE AT Dem0nicCrunk ILL LOVE YOU FOREVER.
I used the double dash tutorial, which works perfectly.
the UDE is superior to the double dash.
HELP!
I tried everything the tutorial said,and when i load up my MA and choose the Run Linux,nothing happens,it sais it wont run "<Run Linux>". What should i do?
Ive got the same problem as cflare, ive tried ltools, on the suggestion of those in the #xbox room on efnet, but i get the same message: Unable to load <Run Linux>. Can anyone offer advice other than, "try it again"?
I'm going to pm tutu and see if he can reply in this thread again.
you guys are probably using a patched up version of the game. you need the opriginal game.
My UDATA is too large for my mem card, can i delete the trainers in my evox file to get it to work, and also, what is the serial number for the correct version of mech assault??
1) I downloaded 007_with_evox_intaller_plus.rar
2) created a UDATA directory and extracted file to it
3) deleted the readme.txt because action replay wouldnt recognize it as a game save unless i deleted this file
4) used winzip to zip up the UDATA folder
5) put the zip file on my memory card using action replay
6) from the ms dash, copied the file from the memory card to the hard drive
7) put 007 in the drive, started a new mission
8) exited out, then loaded mission from hard drive
9) and voila! evox loaded right before my eyes, i couldnt believe it
My xbox is version 1.0 with k: 5101 and D: 4034
Good luck with it and let me know how it turns out for anyone who tries it. 
-Ryan
can u still get onto Live with this?
QUOTE(blakemanf @ Jun 21 2005, 05:57 PM)
can u still get onto Live with this?
y?
i just wanted to know, cause i was gonna do a UXE mod, and i wanted to know which is better.....
right..... did you ever think to look at the dates on top of the threads?
no, lol.
Should i use waffletools or this?
cause i have this all setup and ready to run!
man.....don't you get tired of yourself?
i have a Mechassault disc, its not platinum and i bought it for 30 dollars Retail
its version: ms02301L L0 02
it doesnt work with either save, waffle or this.
HELP!
QUOTE(bacchus21 @ Dec 1 2005, 03:05 PM)

What have I done wrong.

You are not following up to date guides....
warning: i am a noob at this, i usually do case mods
i have a few questions
1. do i need a modchip to do this because i saw "X2"?
2. will this bios allow me to run my xbox without a dvd drive? (that is my main focus)
3. what features does this bios have?
QUOTE(lastcrime @ Jun 15 2007, 04:53 PM)

I really dont understand how to sign the files anyone help or recomend a better tutorial
this guide is 4 years old, and seriously outdated.
look for Krayzies NDURE exploit instead.
MA/007 with Phoenix BIOS loader Tutorial - Revision: 1.34
------------------------------------------------------------------------------
The purpose of this tutorial is to show you how to integrate Phoenix BIOS loader into the 007/MA hacked game save so you can load an X2 BIOS and then a dashboard of your choice.
This hack is only ran when you need it, so should be more "safer" in Xbox live, unlike the font hack. It also does not have a problem with the clock!
This hack should be:
(1) compatible with any BIOS
(2) no xbes need to be signed!!
(3) lots of other stuff..
I have done this with MechAssault so it should work with 007:AUF.
Step 1
--------
You will need the following:
(1) MechAssault or 007: Agent Under Fire games
(2) Mega X Key/Action Replay or other
The following files from Xbins:
(1) Signed_Phoenix_Bios_Loader_V1.3.rar
(2) MechassaultwithEvox.rar or 007_With_Evox_Installer.zip
and Evox or any dashboard:
(1) EvolutionX_V1_8_3752.rar
and XBEdump
(1) xbedump.zip
and (optionally)
(1) XBtool_1.0.5.zip
Step 2
--------
(a) Create a UDATA directory
(b1) Extract MechassaultwithEvox or 007_With_Evox_Loader into UDATA
(b2) Delete DEFAULT.XBE, Evox.ini and Items.txt (and Skins directory) (this was the old hack)
(d) Extract Signed_Phoenix_Bios_Loader_V1.3 into a temporary directory
(e) Copy these files into the same place as your MA/007 save game
(ie UDATA\4d530017\62D648EBF155 for MA and
UDATA\4541000d\000000000000 for 007).
(f) Delete evoxdash.xbe, evox.ini (and Skins directory if there is one)
Step 3
--------
Extract EvolutionX_V1_8_3752.rar
It is up to you where you would like Evolution X to be installed.
You have two choices, you can either:
* Option A - Put it on your Xbox hard drive - C (easiest), E or F or
* Option B - integrate into your game save.
Now by default the X2 4977 BIOS will look for Evoluton-X on your C drive, so if you do not put Evolution-X on your C drive an additional step is required.
Option A - Installing Evolution-X to your Xbox hard drive
Use MechassaultwithEvox.rar or 007_With_Evox_Installer.zip which will allow you to boot Evox and thus allow FTP access to your Xbox. Follow the instructions contained in those zip files.
Upload Evolution-X to your C, E or F drive.
Option B - Installing Evolution-X to your gamesave
Copy Evolution-X to your game save.
(ie UDATA\4d530017\62D648EBF155 for MA and
UDATA\4541000d\000000000000 for 007).
Step 4 (if you haven't put Evolution-X on C)
--------
If you have decided that you wish to use EvolutionX on a drive other than C or in your gamesave then it is necessary to follow this step. If you have put Evox on C then skip this step and goto Step 5.
We need to modify the X2 BIOS so that it will look for EvoX on another drive and/or directory.
This is quite easy and can be done using XBtool
(1a) Extract XBtool_1.0.5.zip to a temporary directory.
(1b) Goto the Config folder of XBtool.
(1c) Move Multi.ini to "More Configs" sub-folder
(1d) Go into More Configs
(1e) Move Debug.ini to Config folder of XBtool (one directory up)
(2) Goto your Pheonix boot loader directory
(2a) Open boot.cfg
(2b) Copy the stuff after RC4Key into your clipboard (Ctrl-c)
(3) Open Debug.ini in your XBtool/Config directory
(3a) Go down to RC4_key=, and copy the RC4 key into it (Ctrl-v). Save and close it
(4) Load up XBtool.
(4a) Select open, and select the BIOS - xboxrom.bin (in your BIOS loader directory)
(4b) Go down to Boot Partitions and Executables.
Change the drive and/or directory to what you require:
Option A - Specify the drive, i.e. C, E, or F where Evox resides:
Use the slider and simply change the drive.
Option B - Specify the drive and/or directory where Evox resides:
You have to remove the 3rd boot option or there wont be enough room for the path
in the first (the paths are pooled in 1.0.2). So simply wipe the text in the third.
As a safety precaution, change the 2nd to:
Partition C: xboxdash.xbe
Now, Click Save As and save the BIOS, overwriting the old one. Now Re-open
the BIOS again. You will now notice that the 3rd boot option is greyed out! Wahoo! now the space is available for the 1st one 
Now enter whatever you like into the 1st boot option.
If you integrated Evox into your gamesave, then specify Evolution-X as:
For 007:
Partition E: UDATA\4541000d\000000000000\evoxdash.xbe
For MechAssault:
Partition E: UDATA\4d530017\62D648EBF155\evoxdash.xbe
(4c) Click Save As and save it. Overwrite your old one (making sure you backed it up first - Shouldn't be a problem tho!!).
You may wan't to open it up again in XBtool to confirm the changes have been made.
All done, X2 BIOS should now look for Evox or whatever dash on the drive and/or directory you specified.
Step 5
--------
Next we need to sign the BIOS loader with the habibi key so it will load from 007/MA.
Extract xbedump.zip to a temporary directory, or put it somewhere in your path, like C:\Windows\System32 for Windows XP.
Open up a command prompt and goto to your gamesave:
xbedump default.xbe -habibi (signs it)
del default.xbe (deletes the old one)
ren out.xbe default.xbe (renames the new one to default)
Step 6
--------
Zip up the game save, and use the Mega X Key software to copy the save
to the memory card.
Step 7
--------
Boot your xbox with nothing in the drive.
Copy the game save from the memory card to the hard drive.
Next we boot the game:
007
Insert 007 into the drive
Enter in normal level, back to main menu and LOAD SAVEGAME
Mechassault
Insert MA into the drive
Load a campaign, select load linux, and voila
Phoenix BIOS loads.. then Evox.
The intro that you get will only run the first time
Your xbox is now free to do anything you wan't... and you won't have to sign any XBEs or have to worry about the clock problem.
and it only takes a few seconds to launch MA 
oh and IGR works too.
I am quite new to this, but I installed XBMP, UAE-X and DGens on my F drive and they work. A lot of testing still has to be done!! 
Upgrading to Phoenix BIOS loader 1.3
-------------------------------------------
If you used Signed_Phoenix_Bios_Loader_V1.3 or later then you are already
running the latest version. If not, you can upgrade following these instructions:
Copy the RC4 key out of boot.cfg in your original gamesave.
Extract PhoenixBiosLoaderV1.3.rar, and overwrite your original files in the game save.
Insert the RC4 key into boot.cfg
Insert the appropiate EEPROM key into boot.cfg for your xbox model
EEPROMKey1_0 (1.0 Xbox)
EEPROMKey1_1 (1.1 and higher Xbox)
See this thread on how to get the correct EEPROM key:
http://forums.xbox-s...ST&f=45&t=84574
Sign the default.xbe:
xbedump default.xbe -habibi
del default.xbe
ren old.xbe default.xbe
Zip up your save game, and upload it to the xbox!
UPDATE: Known Issues
-----------------------------
Reset on eject fix does not work. If you press the eject button, the tray will open half way and the xbox will reboot.
This isn't a problem if you are loading stuff off the hard drive or play originalls.
If anyone has a solution please let me know.
THANKS
-----------
Artifex, Wonderdog, Cain, NeoS, Wooger and anyone else who have all contributed to the tutorial via forum or IRC
Thanx for the info, guess i have something new to add now
and this should be ok to play live with if not in use?
hey man..
i did everything like you said, but as soon as the phoenix screen disappears, it's just a black screen.. nothing happens.
I had that problem when I was figuring this out.
Did you put Evox onto C of your Xbox?
This post has been edited by tutu: Jul 19 2003, 09:16 PM
yessah
There is a step that I did miss that is now in the tutorial.
When you sign the default.xbe it creates a new one called out.xbe.
You need to delete the default.xbe, and rename out.xbe to default.xbe
Sorry about that!!
Working from memory
great tutorial tutu, can you add the steps needed to have evox automaticly come up, so have it installed on the xbox!!
So there is no need to re-run 007/MA! So a permanent solution!!! Or could you point me in the right direction to one already done!!
Cheers mate,
Johno
quick question, when i want to use phoenix do i boot up ma/007 and load the save file?
--PooN
| QUOTE (Johno @ Jul 19 2003, 10:45 PM) |
great tutorial tutu, can you add the steps needed to have evox automaticly come up, so have it installed on the xbox!! So there is no need to re-run 007/MA! So a permanent solution!!! Or could you point me in the right direction to one already done!!
Cheers mate,
Johno |
There are a couple of tutorials for this in the Dashboard Exploit forum. I will tell you quickly
but you should read the other forum for this.
You need to FTP into your xbox and rename two font files (Xbox Book.xtf and Xbox.xtf), and upload two hacked font files (bert and ernie reloaded, or bigfonts). These are run when your switch on your xbox so be careful if you use Xbox live..
Then you just need to extract Complete_Signed_Phoenix_Bios_Loader.rar onto your computer. Sign the default.xbe with:
xbedump default.xbe -font, delete the default.xbe and rename the new one (out.xbe to default.xbe).
Upload the files to your C drive on your XBOX.
Reboot.. hopefully it should work, but read the other forum please 
| QUOTE (PooN @ Jul 19 2003, 10:49 PM) |
quick question, when i want to use phoenix do i boot up ma/007 and load the save file?
--PooN |
Exactly. The hack is only run when you load the game save from ma/007. This may/may not fit your requirements but it is good enough for me while everyone else messes with fonts and that ironing out the bugs 
The only problem I have is that the xbox reboots when I eject the tray - it opens half way, reboots and closes (no reset on eject fix) 
I am using K: 4817, D: 4920 - anyone else have that problem? Not a big problem mind you
do you have to solder anything with this exploit?
tutu, get reloaded as opposed to bert is cheating on ernie, will fix the eject problem
This post has been edited by vintage_guitar: Jul 19 2003, 10:40 PM
Wow, great tutorial...
I finally understand how to do this
! Before I was lost sitting there going 'duh?' wondering how the hell these loaders were being run, all the confusing talk about bert and ernie hacks...
Well now I just need the hardware!
Edit: Loading a new BIOS loads all features in the new BIOS right? Not just a crappy half-patch? I mean, this does fix the DVD eject problem?
| QUOTE (XBox_Master_King4469 @ Jul 19 2003, 11:31 PM) |
| do you have to solder anything with this exploit? |
not unless you wan't to lol
| QUOTE (vintage_guitar @ Jul 19 2003, 11:40 PM) |
| tutu, get reloaded as opposed to bert is cheating on ernie, will fix the eject problem |
thanks for the suggestion but this hack does not use the "font hack". It uses the habibi 007/MA hacked save game boot method
Wish it was that simple? 
RiceCake: this loads the full X2 bios but it still has the eject bug.. dunno whats up with it, going to bed
hehe
instead of soldering anything couldnt you just put electrical tape on each ends of a wire and connect that to the box w/o soldering?
Alright I have been trying this a couple times now....
If you don't put evox on the C drive of the xbox and try to boot the pheonixbiosloader the screen goes blank.
Any way around this? I want to leave the contents of c alone and simply boot the new bios. I dont want the evox dash nor any other dash other than the M$ dash.
You said you had this problem. Any idea's why?
Wooger
I have a virgin xbox k:4034 d:4034 and installed the bigfontz.tgz files (latest green-led-fix updated files) into the C: directory of my 1.0 box. Along with the complete_signed_loader.rar from xbins onto the c:
When evox boots up I press any button on remote control and xbox switches off... but if in EvoX I insert a DVDMovie disc and then press the MS Dashboard button with the controlpad the xbox will flick off to reboot and start up any dvdmovie instantly.
with full dvd remote control. I'm using a PAL region 4 playback kit with a PAL xbox.
with full functionality and then after movie is over I just reset to go back to evox.
| QUOTE (Wooger @ Jul 20 2003, 04:23 AM) |
Alright I have been trying this a couple times now.... If you don't put evox on the C drive of the xbox and try to boot the pheonixbiosloader the screen goes blank.
Any way around this? I want to leave the contents of c alone and simply boot the new bios. I dont want the evox dash nor any other dash other than the M$ dash.
You said you had this problem. Any idea's why?
Wooger |
You could try what bernienoel suggested. However, I would find it rather tight
of MS to ban you from XBL just because you had evoxdash on your C drive 
I will do some further testing.
I haven't decided whether to make this change permanent to my xbox, or get the audio exploit working, or just use the MA/007 boot method
Wooger and anyone else? when you have it running using this MA/007 boot method, do you have the eject/reboot problem?
does this tutorial give me access to the F drive as well? Using the load from 007 everytime tricK??? And also if I wish to use the always boot evox option?
So if i'll boot loader with 007 without any changes on my C, can i play Live ?
| QUOTE (Johno @ Jul 20 2003, 09:27 AM) |
| does this tutorial give me access to the F drive as well? Using the load from 007 everytime tricK??? And also if I wish to use the always boot evox option? |
Yes it does!! I have just followed the F drive tutorial on xbox-scene and I have my F drive 
http://www.xbox-scen...les/formatf.php
It already boots straight into Evox
The only changes to your C drive is to put Evoxdash on there.
It is the X2 BIOS itself that looks for Evox on C. Perhaps it could be modified to look on F or in the gamesave.
F is not detected by MS Dash, so it would not detect evox or any homebrew you put on their.
bernienoel has a suggestion for this by using xbtool. I will look at it, but I need the RC4 key?
| QUOTE (Napek @ Jul 20 2003, 10:17 AM) |
| So if i'll boot loader with 007 without any changes on my C, can i play Live ? |
Loader is only executed when you choose to run it from 007/MA.
So as long as you use Xbox live normally i.e. original in DVD drive, then why would they ban you?
Update ->
I have used the RC4 key supplied within the boot.cfg of Complete_Signed_Phoenix_Bios_Loader.
I have copied this into ini file of XBtool, using the same format (RC4_key=blah). Will this work?
I have used XBtool to open the BIOS. It says unknown bios, and clicking on extract does nothing?
I will have to read a tutorial on XBtool me thinks. But now, time for sunday dinner
i must be missing something ..
I tried to run the phoenix code from 007.
i signed it renamed it then ftped it to my udata folder
i get all the way to the load screen the it goes black.
i have removed the font hacks to test this out.
i do have a modded box and i did turn off the mod and boot
from the original bios.
now i have evox on the save and on c: i have configured the evox ini files on both directorys to match the one on c: so i dont know .
i also tryed puttin an 007 evox installer with a evox ini that pointed to e:appzphoenixdefault.xbe
and i tried it habibi signed as well as the original xbe in this folder to no avail and i got the same results.... stops after the aniamation at the black screen... tried turning off auto start for games as im sure this would be a bad setting with bond in the drive...what gives am i missing something btw ive had no probs with the remote when i had the fonts installed
Yes i have the same problem with the dvd remote, when i press Fast Forward and Skip, then it reboots the xbox
I can now boot to Phoenix then EVOX and can jump to M$ Dash.
(LIVE does not work though. Get a black screen and hang up on it. But, I dont want to get banned so it doesn't matter. I can use the alternatives for now.
Heres my sucess story;
After trying all the dashboard exploits that have came up in the past 2 weeks none would allow me to see the DVD drive. Kept getting the diplicate C: drive. or just the video tracks. I was ready to forget it and install a chip.
Then I stumbled across this thread. MANY MANY THANKS TUTU!!!
I have used this on 3 different units and it works perfectly on all 3.
1 - 4817 dash / 4920 K
1 - 5101 dash / 4920 K
The other I didn't get the specs on.
I made these modifications though.
The 4817 I used the habibi 007 game save.
The 5101 I used the Free Evox 007 game save.
(Note) I have concluded that the game save has no effect other than to let you ftp the info to the drive at first.
First thing I did for both units, was use the Kraken Tut to run M$ Dash.
Second, trip to xbins, grabbed Complete_Signed_Phoenix_Bios_Loader.
Dumped complete contents to c:root, less .nfo file.
Third, Modified Evox.ini to go to new M$ Dash created with Kraken tut.
example; MSDashBoard = "c:newdash.xbe"
(Note) I had problems running some CD backups and HD backups untill I changed all instances of IGR to = NO in EVOX.INI file. Now they all run fine. And can still use IGR from pad.
Fourth, Rebooted, got Phoenix Intro, Logo, then EVOX! YEAH!
Hit M$ Dashboard, up comes ol Greenie. YEAH!
Poped in backup. Hit, Launch DVD from Evox, up comes game. YEAH!
MANY THANKS TUTU
I wish to thank all who have helped to make this all a possibility.
In the news it linked to this post. I have the dvd remote reset problem, its a pain. Kernel 3944, Dash: 4920. Hacked dash: Freevox. Bert and ernie reloaded. When I load a dvd it does it without even loading the fonts. So I beleive the reset is due to the fact it can't find the fonts it needs to display the info associated with the remote button. Someone might have already said this, I didnt have time to read through the post.
| QUOTE |
no..it is not yet complete there are a few bugs to iron out.. as in a remote during DVD playback resetting issue-reported by artifex-
and i fixed the resetting issue using the reloaded fonts |
i have the dvd remote bug too, expect mine is with EvoX w/ B&E Reloaded (BigFonts) and i still get the dvd remote bug......someone fix it now!!!!
thanx!!!!
Hi
Nice tutorial TUTU
I was thinking if its possible to make a permanent solution to an unmodded xbox by:
1) ftp the evox.xbe and evox.ini to the C: drive
2) then rename the xboxdash.xbe (original MS dashboard) to msdash.xbe
3) rename evox.xbe to xboxdash.xbe
4) and make a link in evox.ini to look for the msdash.xbe
This is assuming that the xbox bios can load the evoxdash.xbe (now called xboxdash.xbe).
Can it be possible? or the evoxdash.xbe needs to have a key or be sign with MS code in order for the bios to load it?
How can the evoxdash be sign so the original xbox bios will load it?
Thanks a lot
alagares
E&B Reloaded>Phoenix BIOS loaded w/x2 4977>evox
IF you use a hex editor and do the x.t.f trick then if you point evox to new Dash then the DVD remote will work great.But you have to insert DVD after evox is loaded/after M$ dash tried to read it.
I found it on eMule/eDonkey.
Succes!
) has to have its original Phoenix Evox skin and the aforementioned files intact.
Hi, I'm really new to all this Xbox Hacking but I have a few questions.
I have a moded Xbox, with a homebrewn chip. I was thinking of getting a chip so I could switch between modded xbox and the debug xbox.
With this new Loader, I think that I dont need to buy this chip anymore.
Could someone tell me if I'm getting this wrong.
I can have my xbox boot evox like it is actually, and I can have a tab that will execute the Loader, making my xbox reboot into the debug bios ?
Then once done having fun debugging stuff, all I need to do is on/off the box and evox will come up naturally ?
If this is possible, could someone tell me how I can do this ?
my screens goes black.
ok, I copy evox to my C: drive so in addition to my original files, I have evox.ini and evoxdash.xbe along with a Skin folder
Then I do all that jazz with 007withevox and the phonix files.
then I use xbedump I signed, del, and rename.
zipped it up, loaded to HD, then loaded thru oo7
I see a cool looking phoenix, then i see eternal darkness.....
what am I doing wrong?
--PooN
| QUOTE (PooN @ Jul 21 2003, 04:23 PM) |
my screens goes black.
ok, I copy evox to my C: drive so in addition to my original files, I have evox.ini and evoxdash.xbe along with a Skin folder
Then I do all that jazz with 007withevox and the phonix files.
then I use xbedump I signed, del, and rename.
zipped it up, loaded to HD, then loaded thru oo7
I see a cool looking phoenix, then i see eternal darkness.....
what am I doing wrong?
--PooN |
Exactly the same problem that I am having. My Xbox is a 4034 - has anyone gotten this working that has the same kernel version? Can't remember the Dash version off the top of my head (at work rite now..).
Is it more likely a problem with the BIOS+RC4 key or a problem with the Evox that is on the Xbox's C-drive? The fact that the Phoenix intro plays means the default.xbe has been properly signed with -habibi, right?
Any ideas?
My kernal is 4034 and dashboard is 4920
and im thinkng the same as you, GQ, cant be the .xbe since the red does show up.
anyone else?
--PooN
BT
| QUOTE (DeadJB @ Jul 22 2003, 05:35 AM) |
Okay, so this is my problem, which will hopefully be solved easily (this is my first time at ever trying to do an Xbox mod, so I'm an extreme greenhorn with all this).
I had no idea what step 2 meant, because I didn't know how to use the hacked MA save game if it weren't set up yet already. So I ignored step 2 (knowing this would probably be a problem). I know that was stupid, but I had no idea how to use the hacked save game. Am I supposed to take the contents of the rar file, spit them into a UDATA folder, put that on my mem card (without altering any of the files or doing the whole command line stuff), and load that file first in Mechassault? Will evox just load from the memory card so that I can ftp to the box after that?
This is what happened for me:
I skipped step 2.
I went and did the other steps. Copied the new save game file (after doing the whole dumping and altering of the file etc etc) to the HD. Loaded MA, then loaded the run linux save. From there it booted the Phoenix logo, went black temporarily, then just showed the big green X logo. It hung, then the LED blinked red/green, then an error 21 occured.
So was I supposed to initially just take that save game file as is, and load that first? Will that load a barebones evox dash for me to ftp to my xbox with? If someone could explain this one thing to me, I would be in your debt.
Thanks. |
If you skipped Step 2 or even 1 it will obviously not work - you have to follow them in order. Step 1 is just taking the Mech w/ Evox save game and using that to be able to FTP into ur XBox. Step 2 is where you copy the actually BIOS to the c:/ drive of the XBox and Step 3 is altering the Mech w/ Evox save game to actually load the new BIOS you copied to the c:/ of the Xbox... so if you skipped Step 2 and went to Step 3 it is trying to find the EvolutionX BIOS on the c:/ of the XBox that you didn't copy in Step 2....therefore the problem you are having. If you follow each step as tutu laid it out you shouldn't have any problems. The only problem I am having is the dreaded Reset on Eject bug that has plagued several people. This appears to be solved by the Bert & Ernie Reloaded Font files, but I am not sure how to intergrate those into this particular hack - anybody care to explain? Anyhow - everything else works, I copied KOTOR to the e:/ drive last night and it came right up.... hope this helps.
BT
That's just it. I don't understand step 2. How do I ftp into my box? Do I just take the gamesave exploit, without doing anything to it at all except throwing its folder into a UDATA directory and zipping that, then loading it in MA?
| QUOTE (wonderdog @ Jul 22 2003, 01:27 PM) |
I edited the x2 4977 bios with xbetool 1.0 RC5 to boot evox from the e:, (cant seem to work out how to format my f:, shows as having space on xftp, buit wont format... any ideas?)
Works a treat!
stuck evox in the e:, so there should be few probs with xbox-live. only way it could be safer would be of f: (my prob = see above).
Only "real" issue (apart from my cant get F: drive working stupidity) is the reset on eject problem. I thought about loading complex loader, to tackle this, but that kind of defeats the whole purpose, and I'd be as well going back to trying to sign it to work with MA directly...
#Wonderdog |
I've managed to modify it using XBtool this morning with a little help off on IRC.
I've updated my tutorial with an optional step for using XBtool, and added a known issues bit at the bottom.
Reset on eject is still a problem, and I have switched to the audio exploit until it is fixed!!
As for drive F problem, have you read the format F tutorial on xbox-scene? Perhaps you don't have the 10 gig hdd? but the 8 gig one? (and thus no F)
where can i see these updates to the tutorial.
--PooN

If you wan't to use the audio exploit then get hold of Audio_Signed_Phoenix_Bios_Loader.zip on Xbins as it comes with everything ready. I would however, install your own Evox to E or F and edit the BIOS in XBtool so to keep C as clean as possible.
I'm having the same problem as Poon and GQinfinity. It just loads the phoenix animation, then goes black.
I'm using 007 on a 4034 kernel.
I think it might be some difference between MA and 007 that is causing this... just speculating though.

Used the MechAssault/Phoenix Bios Loader on my Xbox with k:4817 d:4920. Everything working except the boot-on-eject.
K:4034
D:4920
Using the 007 save i load the save, i see the phenoix movie, then just a blank screen.
Seems like im not the only one with the problem, anyone got any idea as to what is causing it?
Phoenix Bios Loader ver 1.1 released. One of the fixes includes:
- Properly fixed rest-on-eject issues
I am going to test it now, let you all know if it fixes the reboot on eject problem

#Wonderdog
But reset on eject fix doesn't.. 
IMPORTANT: If you modified the bios using XBtool and changed the DVD filename from "restore.xbe" to "default.xbe", the hack will work but it will automatically load MechAssault or whatever is in the drive.
So leave it as "restore.xbe"!!
| QUOTE (tutu @ Jul 23 2003, 02:58 PM) |
| Now there is one problem, it doesn't work!! It loads the intro, but It will not boot evox. I am totally puzzled. |
Yeah.. that's as far as 1.0 of the phoenix bios loader went with the 007 save game exploit (intro and then nothing...)
Getting the phoenix bios loader working to load evox of e-drive using the audio exploit worked fine on the first try.. so I'm thinking that the save game exploit just isn't compatible with the phoenix bios reloader.. odd that it worked at all with the mechassault save game, but maybe that was a fluke - it also didn't work fully (reboots on eject).
Oh well, the audio exploit is just as safe (no changes to C:) so I'm happy with that. 

So if you have modified the BIOS, put it back to "restore.xbe". I have updated my post to reflect this finding.
The reset on eject issue is still there.
It works fine however with audio exploit
| QUOTE (DeadJB @ Jul 23 2003, 04:23 PM) |
| Did you use the audio exploit and phoenix bios loader zip file from xbins? |
Yes...and if you have already loaded up the MA Hack you don't even have to put the contents of the "c stuff" folder onto your Xbox C drive since it is the same BIOS. Just load up the "e stuff" folder onto your Xbox E drive and you are ready to go - took me 2 mins last night to do it and worked perfectly and like Tutu says the Reset on Eject issue is not present in the Audio Exploit. Works great and I am in no hurry to implement the 1.1 release of the Phoenix Loader since everything is working fine with what I have...
BT

#Wonderdog
I have tried the ejecttray and loadtray and they do the same thing as pressing the eject button (Tray comes half way out and the xbox resets adn loads the tray back) Good idea it was but it does not fix the problem.
Using the Audio exploit is the only way I have be able to get it to work (Other than the font exploit but I don't want to do it that way)
Here is hoping that Phoenix Bios Loader 1.2 fixes the problem!
Definitely a difference between oo7 and ma. Fortunately, I have both games. I never wanted to try MA, cuz of XBL.... Can i still use MA to go on XBL? But first i did this with 007 and it froze, then i tried with MA and it worked the first try.
--PooN
Booting EvoX from the gamesave (after copied to the hard drive) works fine. I downloaded XBtool 1.0.1b1 and used it to edit the BIOS image. In XBtool I configured it as follows:
Boot Partitions and Executables
1st E:\UDATA\4d530017\62D648EBF155\evoXdash.xbe
2nd <blank>
3rd <blank>
Note: You'll have to delete the text in the 2nd and 3rd text boxes before being able to copy that string into the 1st text box. Once you've saved the new file, copy the new xboxrom.bin and EvoX into the gamesave folder and you're set. Now if I can just get the reset on eject not to happen, I'd be so happy with this solution.
Exact same situation as me mate.
Seems to be an issue with the phoenix bios loader itself, seems that a register or something doesnt get properly changed/intercepted regarding the eject instruction unless evo-x is the first dash loaded (which is why it would work with fonts but not gamesave). Could be something the M$ dash passes to the kernel that doesnt get passed by EVO-X regarding reset on eject...
Thats conjecture of couse, but seems reasonable.
#Wonderdog
| QUOTE |
Eject and Close Tray >> From Dgege... This is Two XBE's (with sources included) to eject and close your tray.
Official Site: n/a (By Dgege) Download: Sources News-Source: http://www.xbins.org
update by XanTium: I guess this could be interesting for the gamesave exploit. It could probably allow to load a DVD and bypass the reset-on-eject problem.
|
Anyone tried using the above to fix the reset-on-eject? Keen to find out.
Yip, and nope. It doesnt work. See my post above.
#Wonderdog
Well, this 'method' has screwed up my chances of ever using another exploit ever. On my 1.3, after going through the steps of this tutorial, when you try to use a gamesave exploit, it starts and then decides to crash the XBox to the GSOD... WHATEVER savegame exploit you use. So I can't even go into one of the conventional exploits to take the files off the xbox, and I can't even send the xbox back because of the files on there
Anybody got a suggestion of a fix???
all I want to do is access the harddrive. any fix, perhaps changiing some of the contents of the MECHWARRIOR gamesave exploit file package?
| QUOTE (juleskitten @ Jul 25 2003, 07:16 PM) |
| all I want to do is access the harddrive. any fix, perhaps changiing some of the contents of the MECHWARRIOR gamesave exploit file package? |
Did you screw with the fonts or the st.db audio file? If not, just boot into the MS dashboard without a game in the DVD drive and delete your MechAssault savegame. Grab MechassaultwithEvoX.zip, put that onto a memory card, copy it onto the hard drive, and load it. It should get you to EvoX where you can use FTP to clean up/install whatever you like.
No, I didn't screw with the fonts or the audio thing. The whole thing with this bios loader exploit is that it automatically loads itself, doesn't it? So, the phoenix bios loader on the harddrive is making it go to the GSOD, and with any savegame exploit, even the unmodified Mechwarrior one, it trips it off and so goes to the GSOD. Deleting the savegame and putting another clean copy of the exploit on the harddrive won't work.
| QUOTE (juleskitten @ Jul 25 2003, 07:26 PM) |
| No, I didn't screw with the fonts or the audio thing. The whole thing with this bios loader exploit is that it automatically loads itself, doesn't it? So, the phoenix bios loader on the harddrive is making it go to the GSOD, and with any savegame exploit, even the unmodified Mechwarrior one, it trips it off and so goes to the GSOD. Deleting the savegame and putting another clean copy of the exploit on the harddrive won't work. |
Mine doesn't automatically load. I boot MA and load the savegame whenever I want to boot Phoenix and then EvoX. What exactly did you do? List the steps you took to get it in this state.

I think the step in the tutorial I didn't complete was to load the fonts, but I didn't see it in the tutorial, and if the fonts were loaded, several of the tutorial steps would not work...
As a side note, I always found in the past that I could get the evox to load. Then if I tried to load any hard drive games, or any software, it would go to the GSOD. Is this because I have the newest 1.3 Xbox?
| QUOTE |
The whole thing with this bios loader exploit is that it automatically loads itself, doesn't it? So, the phoenix bios loader on the harddrive is making it go to the GSOD, and with any savegame exploit, even the unmodified Mechwarrior one, it trips it off and so goes to the GSOD |
No, it doesn't automatically load itself.. there's nothing magical about the phoenix bios exploit. If you use the evox installer save game exploit, then the evox installer will run. If you use the phoenix bios loader save game then the phoenix bios loader will run, trying to replace your bios in memory which causes a "reboot" using the new bios. The new bios (the x2 one anyways) tries to load a dash (c:evoxdash.xbe). The buffer overflow (or whatever) in the save game will run whatever exploit is in the save game you are using - if you delete the current mech save game and copy the evox installer one onto the hd from the MS dash, that is what will run when you load the save game - e.g. you should be able to get back to evox. At no point does any phoenix bios loader code 'automatically' run.. it's only initiated if you use the save game including the phoenix bios loader exploit.
| QUOTE |
| As a side note, I always found in the past that I could get the evox to load. Then if I tried to load any hard drive games, or any software, it would go to the GSOD. Is this because I have the newest 1.3 Xbox? |
Did you sign the HD apps? With savegame + evox the programs on the HD need to all be signed to run...
thanks for tryng to help though, I hope there is a solution.
I believe it has something to do with 007 auf.
I have both, MA and AUF, when i did the exploit with 007 nothing but lock ups.
I gave it a try with MA, it works fine.
--PooN
Ok, to summarise:
1. I followed all the details of this tutorial minutely.
2. After the phoenix video it went to the GSOD.
3. It did this every time I used the modified MechAssault exploit (without the video loading).
4. I took the modified exploit off the hard drive and replaced it with the normal exploit and it did the SAME thing, going straight to the GSOD.
5. This means that I can't get onto my xbox harddrive via ftp at all.
6. Would a solution be to rent Agent Under Fire and use an exploit that doesn't involve Evox? (the new version of evox on the xbox harddrive is obviously causing the problem).
7. Or is there a way to stop the evox on the hard drive from automatically loading?
or is there some way to load the mech assault exploit file with something that will format the C drive?
or some way to modify something in the evox.ini so that it doesn't load the one on the hard drive?
Thanks for any help in advance
Lets see what we can do here.
If you have any mechasasult downloaded content, that can muck up the operation of the exploit, so use the MS dash (boot with no disk in) to remove ALL mechassault savegames, including the linux one. Infact, do this anyway.
Then get the original mechassault_with_EVOX savegame from "the usual places" and get that on your HD using your memorycard and run that.
That should run a basic version of evox from the savegame folder, not the bios loader or anything on the HD.
Then you can FTP in and remove all the crazy stuff from the HD and start again.
I take it you havent fannied about with any font files or audio files, if so, good. The whole point of this savegame method is to avoid having to do that.
Also, on which HD (c: e: etc) and directory did you put Evox? are you sure you correctly modified and saved the bios to point to this? If not, when the bios loader loads, it'll crash as you said.
What you have to do is get the bastard cleaned up, so we can get it working correctly from scratch.
Dammit, I'm gonna make up a pre-setup download tonight for this exploit, cause so many people are having probs with all the setup stages...
#Wonderdog
Hello Wonderdog, thank you for your reply.
Okay, I put evox on C, without the fonts, therefore when I turn on the xbox, it boots to msdash. However, as I have been saying all along, getting rid of all mechassault savegames and then putting a fresh mech w/evox exploit doesn't work. The exploit crashes the xbox, but then goes to the GSOD. This never ever happened before doing this tutorial, so I am sure it is booting to the one on the harddrive which obviously doesn't like my xbox. Do you seeeee now? So I can't go into ftp... I know what you are saying and it would have been the first thing I would have done, but I can't for the above reasons.
Any solution for this
*EDIT*
I Saved my xbox and let me tell you how maybe this is the solution for the black screen ppl.
I use the 007 Auf exploit + the pheonix bios loader but like i sayed i get a black screen after i see the phoenix....
Try completing the first lvl after that do save ON THE HDD with me ( this saved my box ) the evolutionX came up and it booted my backups like a charm 
Only thing is the default.xbe of the EVOX on my C has to be named as evoxdash.xbe only then it gets loaded.
But is this a Boot disc solution ( phoenix bios loader ) or can it be auto runned?
*edit*
and for the part that you need to load the phoenix trought 007 is bullshit...
Get it in a dir on your E or F or whatever make sure evox sees it and voila when you load it up the same thing happents only much much faster....
Only problem now is that it needs and evoxdash.xbe and the xbox needs to be started with an default.xbe so any eynsteins that know how to change the file you'll need load for phoenix FROM evoxdash.xbe to default.xbe
Use xbetool (latest verison) to edit the bios to point to whatever dashboard xbe you want. Remember thought this thread is for discussion of the GAMESAVE exploit implementation of the phoenix loader, anyone wanting to make it permanent should go look at the dashboard modification forum. You'll get better help/advice there.
NOW.
Regarding the reset on eject problem related to the 007/MA method of launching phoenix... I just realised we could have acted like total retards about this one...
Does the 4977 Boot from media bios even SUPPORT the reset on eject fix? It doesnt specifiy...
I believe I'll try the EVOXD6 with eject fix bios (which phoenix 1.2 supports) and some others later this evening. I will feel so stoopid if this is the only problem though... but I'd still be ecstatic! I'll let you all know about 5 ish (GMT).
#Wonderdog
Hi,
just as others have reported they have receive problems loading this through the 007 exploit they get a black screen after the Phoenix Logo, same thing happens to me I haven't found anything that tells me how to over come this. This still happens when using the fonts exploit, I'm using
K 4817 (something like that)
D 4790 (something like that too)
Thanks for any help or even a reply!

Hey Wonderdog, how did you get on with Evox D6 BIOS? I would like to try it too, but I'm at work
So with my problem... I can try to change the xbe on the savegame to ONLY point to the one in the savegame? the thing is that xbetool says that the default.xbe in the savegame exploit is invalid.... so not quite sure what to do about it
I must say though that I have got the 'official' MechassaultwithEvox file from 4 sources including 'the usual places' and tried all of them and all of them now make the xbox crash
hopefully your version will fix it though!
Have you gone on LIVE with this game?
If so have you removed all downloaded content before trying this?
| QUOTE (Mordenkainen @ Jul 28 2003, 01:49 PM) |
Have you gone on LIVE with this game?
If so have you removed all downloaded content before trying this? |
I believe this was suggested a page or two back...didn't seem to be the problem...
BT
Yep, sure will.
The only problem left to be fixed is reset on eject. Worked out how to put everything in one distributable save quite a while back... Work out ROE and I'll give you a cookie.
Still to try EVOXD6 btw, broadband connection went mental earlier on, and now I'm off to bed. cya!
#Wonderdog
.
i can't seem to load the original msdash for some reason i think its because i had 2 sets of xbox.xtf and xbox_book.xtf 1 in the fonts and 1 in the main.
But who wants to use xbox live
give me ( loading backups ) over xbox live anytime 
Hope this is for some use.
Hey tutu, our wish has been answered... complex just released a version of EVOX D6 that is BFM as part of thier complex BFM collection.
lol!
Just testing it now...
#Wonderdog
hmmmm. evox_D6_BFM doesnt seem to work... It crashes xbtool (latest and prior versions) when I go to open it, and the xbox goes black after the phoenix loader art.
And yes, I have renamed it correctly and put evoxdash etc in the right places!
Think I'll try some other dashes from the pack, might just be this one.
#Wonderdog
According to the PBL .nfo it says:
"If you specify the key to be all 0x00's, it will assume the 2BL is decrypted already in the rom you are providing."
debug command lol, why didn't I think of that?
Remember that XBTool's info said that with an Evox BIOS you can only use something like 18 characters for the path to the dash. Perhaps the path you are pointing to is longer than that?
Morden.

and C: drive followed by "xboxdash.xbe"

Updated with info from within this thread on how to integrate EvolutionX into the save game, and how to make 007 work (hopefully?).
Goto the first post to see it lol
XBTool still won't let me type all that in, even if i blank out the text fields for 2 and 3. (although i don't know how to make them greyed-out-disabled like they are b4 i open the xboxrom.bin. What am i doing wrong? how can i get the full "UDATA4541000d 0000000000evoxdash.xbe" in?
| QUOTE (S@nto @ Jul 29 2003, 06:31 PM) |
| XBTool still won't let me type all that in, even if i blank out the text fields for 2 and 3. (although i don't know how to make them greyed-out-disabled like they are b4 i open the xboxrom.bin. What am i doing wrong? how can i get the full "UDATA4541000d0000000000evoxdash.xbe" in? |
Are you using the latest XBtool beta? (XBtool 1.0.1b3)
I just checked, I opened up XBtool and loaded up the BIOS, and I pasted the exact string from my tutorial into XBtool and it accepted it, and then I saved my BIOS.
Opened it up again, and it kept the string.
I haven't tried the BIOS itself yet as I'm faffing around with getting the other BFM BIOS to work lol but it should work as reported in this thread.
I've been trying to figure out why evox wasn't loading...i signed habibi the default pbl, i pointed it at the E: location...
ok, no long stories...I cut and pasted your address tutu, and you're missing a 0 !!
I'd quote you, but hopefully it gets edited and then the -0 string won't appear anywhere.
the correct loc should b UDATA4541000d 00000000000 for the save game i had (it's universal isn't it?)
then, it still didn't work...so i read Neos post again...i wasn't going into level then out. so i did...AND IT WORKED.
Anyone know why u have 2 do that? and how far into the game do you have to go?
Grrrrr, no solution for the reboot on eject problem yet?
In case anyone is wondering there should be 12 "0" for 007



#Phil
well the tutorial DID say to copy EVERYTHING after the code 
for the people that still can't get it to work, you have to PASTE the destination directory address, it won't let you type it in, if you try to type it in manually it will still only let you type in 12 characters
oh and sorry for using more than one post a couple of times, I only just got the edit function for my posts and i'll always use that instead now promise!
*EDIT*
guess what? after all that, and following the new tutorial, after loading mechassault and selecting the savegame, it STILL goes to the GSOD!!!
( is it because I have an XBOX 1.3??
Hey!
Great tutorial you have here. There seems to be a new version of Phoenix out (1.3). I was just wondering if upgrading to it works the same way as upgrading to 1.2? Do I need to have those bios keys or is it okay without those?
Thanks again for the tutorial!

I will make a couple of changes to the tutorial later to bring the new xbtool 1.0.1 into it, and I will follow my own tutorial again to make sure all the steps work (I keep altering it etc.). Better make sure it works lol
virtahepo and others ->
For the new PBL 1.3 you need to enter the EEPROM key for your xbox. I haven't had a chance to test this new release yet as I am at work
| QUOTE (juleskitten @ Jul 31 2003, 05:03 PM) |
I've removed it but would it matter if I was banned? nobody seems to know how to help me or can be bothered to help me?  |
People have to work lol 
Now that I am back I can help you.
Perhaps you should try Evolution-X on your C drive and just work on getting it to work first. Skip the step about editing the BIOS. When you have it all working, then do that step.
Read the tutorial from the start (just start all over again). There is something you may have missed or not done correctly.
I have updated my tutorial to 1.3. It now includes the correct information for using XBtool to edit the BIOS so you can load Evolution-X from your gamesave.
I have verified the latest tutorial myself.
| QUOTE (tutu @ Jul 31 2003, 06:43 PM) |
[Perhaps you should try Evolution-X on your C drive and just work on getting it to work first. Skip the step about editing the BIOS. When you have it all working, then do that step.
Read the tutorial from the start (just start all over again). There is something you may have missed or not done correctly. |
I did the tutorial correctly the first time and it screwed up my harddrive for whenever I try to even use a fresh exploit, so I cannnn't try evox on my c: drive because I can't ftp to it, as i've said twice
i'm looking for a simple exploit that can be loaded from memory card that only points to itself that can give me ftp so i can clear up the c: drive and start again

Remember to use the debug RC4 key for ALL boot from media bioses (even the D6 which is normally decrypted) as this is a requirement to run them.
Still, because the Evox D6 has to have the drive ejected to be loaded, it aint much use
cause the bios (which stops reset on eject) hasnt been installed 
still, maybe a bios which supports reject on eject and doesnt have this problem when configured for BFM might still work!
#Wonderdog
PS, going away for the weekend, wont be able to post/try this to I return, good luck if you do!
| QUOTE (juleskitten @ Jul 31 2003, 07:14 PM) |
| QUOTE (tutu @ Jul 31 2003, 06:43 PM) | [Perhaps you should try Evolution-X on your C drive and just work on getting it to work first. Skip the step about editing the BIOS. When you have it all working, then do that step.
Read the tutorial from the start (just start all over again). There is something you may have missed or not done correctly. |
I did the tutorial correctly the first time and it screwed up my harddrive for whenever I try to even use a fresh exploit, so I cannnn't try evox on my c: drive because I can't ftp to it, as i've said twice i'm looking for a simple exploit that can be loaded from memory card that only points to itself that can give me ftp so i can clear up the c: drive and start again |
Depending on the game you are using its MechassaultwithEvox.rar or 007_With_Evox_Installer.zip....
They simply have Evox and allow you to FTP into it.
As for screwing up your harddrive? Are you sure you was reading the right tutorial?
2 hours of work and just after phoenix logo black screen. And one more why after this
copy "temp" "c:"
nothing is copied ?
ill try this too: copy "E:UDATA4541000d 00000000000temp" "c:" and still nothing is copied
anyone can help ?
| QUOTE (juleskitten @ Jul 31 2003, 11:14 PM) |
| QUOTE (tutu @ Jul 31 2003, 10:30 PM) | Depending on the game you are using its MechassaultwithEvox.rar or 007_With_Evox_Installer.zip....
They simply have Evox and allow you to FTP into it.
As for screwing up your harddrive? Are you sure you was reading the right tutorial? |
Oh god, i've got to repeat myself for the third if not forth time......
Yes, I KNOW the savegames USUALLY do but following THIS tutorial I got a version of evox stuck on the hard drive that makes my hard-drive GSOD any time evox starts. ANY time. So if I try loading the normal exploits even, it decides to load to the evox on the harddrive and GSOD. Hence, I can't use FTP. See pages 6,7,8 and 9 of this tutorial for details. That's also what I meant by screwing the harddrive up, I have no access to it. |
The savegame exploits DO NOT BOOT EVOX OFF THE HARD DRIVE.
evoxdash.xbe is in the savegame and signed for the exploit. So I don't know what the deal is...the savegame exploits have always booted fine for me.
| QUOTE (oracle2 @ Jul 31 2003, 11:38 PM) |
The savegame exploits DO NOT BOOT EVOX OFF THE HARD DRIVE. evoxdash.xbe is in the savegame and signed for the exploit. So I don't know what the deal is...the savegame exploits have always booted fine for me. |
Umm, where do you think the savegames are in your Xbox? The freakin' harddrive! You couldn't be anymore wrong!
J.
| QUOTE (oracle2 @ Jul 31 2003, 11:38 PM) |
The savegame exploits DO NOT BOOT EVOX OFF THE HARD DRIVE. evoxdash.xbe is in the savegame and signed for the exploit. So I don't know what the deal is...the savegame exploits have always booted fine for me. |
yes, plus this tutorial is about putting evox w/phoenix on the main hard drive too (if you decide to), that's what I did in the first place, it GSOD'd, I tried to ftp to get the files off but the unchanged savegame exploit GSODs too ever since carrying out this tutorial (hard drive version). That is why I think it has to be the evox+phoenix n the main hard-drive (not the savegame directory). THATS ALL IT COULD BE, otherwise I would happily use the unmodified savegame exploit to use ftp, BELIEVE ME. Can anybody suggest a fix? a modified self contained savegame exploit? (hmm I asked this 5 pages ago)
| QUOTE (juleskitten @ Aug 1 2003, 01:45 AM) |
| QUOTE (oracle2 @ Jul 31 2003, 11:38 PM) | The savegame exploits DO NOT BOOT EVOX OFF THE HARD DRIVE. evoxdash.xbe is in the savegame and signed for the exploit. So I don't know what the deal is...the savegame exploits have always booted fine for me. |
yes, plus this tutorial is about putting evox w/phoenix on the main hard drive too (if you decide to), that's what I did in the first place, it GSOD'd, I tried to ftp to get the files off but the unchanged savegame exploit GSODs too ever since carrying out this tutorial (hard drive version). That is why I think it has to be the evox+phoenix n the main hard-drive (not the savegame directory). THATS ALL IT COULD BE, otherwise I would happily use the unmodified savegame exploit to use ftp, BELIEVE ME. Can anybody suggest a fix? a modified self contained savegame exploit? (hmm I asked this 5 pages ago) |
Oookay. Let me clarify. MechassaultwithEvoX.rar, once copied from your memory card to your hard drive, looks for evoxdash.xbe in E:UDATA......etc. NOT in C: or E:. So if you have a corrupted dash in the root of an partition, that's not the problem. I have a self-contained savegame with the MechAssault exploit, Phoenix and EvoX...that's what I use.
so why is it going to GSOD since the tutorial then, even with a fresh mechassault exploit gotten from the usual places? Why then, if that's the case?
| QUOTE (Jefe1 @ Aug 1 2003, 12:11 AM) |
| QUOTE (oracle2 @ Jul 31 2003, 11:38 PM) | The savegame exploits DO NOT BOOT EVOX OFF THE HARD DRIVE. evoxdash.xbe is in the savegame and signed for the exploit. So I don't know what the deal is...the savegame exploits have always booted fine for me. |
Umm, where do you think the savegames are in your Xbox? The freakin' harddrive! You couldn't be anymore wrong!
J. |
When tutu's talking about the HD he's talking about the C: muppet!
Anyhow.
Jules, sorry I havent had time to make you up a savegame, but I suggest making up a mechassault/007 savegame which loads ANOTHER dash with FTP (not EVOX, but avalaunch maybe? check the nfo first) and signing it with xbedump. Try loading this through the savegame exploit.
If it loads avalaunch, you know something is screwed with the way you've been using the evox saves. otherwise, we'll try something else!
Good luck.
#Wonderdog
I have updated the tutorial to now use Signed_Phoenix_Bios_Loader_V1.3.rar instead of Complete_Signed_Phoenix_Bios_Loader.rar (1.0) as it is no longer available from #xbins
It should make it easier as it now is the 1.3 version. I have kept the upgrade instructions for 1.3 in case anyone is still running the 1.0/1.1 or 1.2 version of Phoenix BIOS loader.
Hi, can i use this to play backups? ive looked but im not sure, sorry, i presume so seen as the X2 BIOS is loaded allowing the use of unsigned code? Also could i set up the bios to load 1st D:xboxdash.xbe 2nd C:xboxdash.xbe? with font hacks, so if i insert the disc with all my evo-x stuff on it'load that, if not then it'll load normal xbox dash so ill be fine for xbox live? i dont own either Mechassault or 007AUF i just intend on renting them. Any help would be much appreciated.
hi tutu
i have the eject prob with phoenix and evox ,dam its anoying !!!
i guess it s because the font exploit are not in plce !
but u re trying not to use them right ?
i tried to load avalunch and not evox but i get a black screen after phoenix image !
any idea ???

Reset on eject is a problem I know, and it will continue to be a problem. So little time..
More info on the audio exploit can be found here:
http://forums.xbox-s...&t=73731&st=120
Basically you just need to download audio_track_exploit.zip, modify the ST.DB file with a hex editor, upload it to your Xbox, and put Phoenix Bios loader on E drive and call it linux.xbe.
I haven't tried any other dashes apart from EvolutionX yet, might get round to it one day
ok so i got the last XBtool_1.0.4b1 so u can really modify bfm bios !
so i did run to evox with the EvoXD6_EjectFix_bfm works fine but the eject still reboots the box !

Hopefully this will be an easy one for someone 
The problem with the tutorial that I'm running into is this section:
(4a) Select open, and select the BIOS - xboxrom.bin (in your BIOS loader directory)
I don't have an xboxrom.bin bios anywhere, or a bios loader directory. I assume then that I have to download the X2 4977 bios separately? This isn't mentioned anywhere in the files required, so maybe not. Cheers for any help on this one.
u need to download pheonix bios loader at www.pheonix.maxconsole.com anyways you have to do the stuff with xbtool with the rc4 key etc and if your bios is called x24977 or x24978.bin u need to rename it xboxrom.bin thats where that file comes from.
But my own question now if u integrate into the game save and u keep your original dash on the c drive turn off your xbox after using this hack then go into xbox dash and go to live it will not ban u since it looks for the dash on the c drive right?
I've gone thru the thread, and there seems to be a difference of opinion.
If I use the MA save + Phoenix 1.3 + Reloaded (to run evox on bootup without MA), will the roe still be a problem?
Sorry if it hasn't been too clear.
couldnt u use the evox d6 eject fix bios to fix it?
is there anywere i could download phoenix bios loader intergrated with the game save.
Theres no reason to do this as u wont be able to play backup cd or dvds or homebrewn games ud need to ftp em to the hard drive and hope it doesnt try and eject the tray. So you would either have to do it the normal pheonix loader way or the audio exploit.
But being that your probably a very famous r kelly impersonator couldnt u pretend to be rkelly and ask someone to chip a system for u
But I have a action replay
Everytime I try to intergrade phoenix bios loader with the ma save myself I get a error 21 when I try to load it.
thats a problem with the linux shit or u did something wrong like with the habibi sign delete rename part. if u really wanna do this use 007 auf go into new game go to main menu then load a saved game and bang evox comes up. youd have a better time not integrating and doing the pheonix loader tutorials around and using the big fonts hack in addition to 007.
When i use XBTool and open up xboxrom.bin it says "Error reading config file"
please help!
i have the file when i run MA where is load campaign!!!? how do i use the save!!?
i JUST got action replay, and i did step 1-5, now im at step 6 or whatever where it says to zip, so i zip the files, and then i try to drag the zipped filed over onto the memory card part of the window, and guess what, its not a valid xbox game save file, i need help
| QUOTE (Cornwallace @ Sep 20 2003, 04:36 AM) |
| i JUST got action replay, and i did step 1-5, now im at step 6 or whatever where it says to zip, so i zip the files, and then i try to drag the zipped filed over onto the memory card part of the window, and guess what, its not a valid xbox game save file, i need help |
CornWallice: did you delete the readme.txt in the Udata folder before tou ziped Udata and draged it to AR.
Is there any way to get the reset on eject bug out. I integrated Pheonix and Evox in my savegame. If the bug does get fixed will this allow me to execute xbes off of a CD-RW?
http://us.codejunkie...=1&g=1297285143
Download the Run Linux save from here. Then sign the default.xbe with habibi. There are a lot of Run Linux downloads there, but I don't remember the exact one with the Pheonix Bios loader in it. But the right save is there.
Hi, I have the same problem that robwish had. I downloaded everything from xbins, all the steps worked accordingly but I get the service error screen after i load the game save from the hd.
i have an original xbox purchased at release date so i'm not sure if it's because i'm using a 4977 bios. Any ideas?
also, how big should the game save be? mine fluctuated from 4 to 6 megs. i had to delete the temp directory to fit it into my action replay.
Same here ...error 21.....I used mordens audio hack also.....and gouki's....still error 21....Can someon make it a little more clearer for us n00bs ...cause ive been doing this for a week ...and beleive me ...i read before i ask......And this isn working....Thx for the help n the info....
SoP
Also i jus resigned the deafault.xbe in mordens using xbedump.... too -habib and then tryed too load in AR wouldnt work .....So i put in xbox save manager V.4 and loaded in AR then too HD then run linux then good ole error 21......
u have to resign default.xbe it makes a out.xbe then u delete default.xbe and rename out.xbe to default.xbe thats usually the problem they didnt follow that part right. i guess tell me if u did exactly that. if u keep it named old.xbe your screwed.
I tried the gouki way of signing and the habibi way of signing. both methods were successful in creating a new default.xbe (out.xbe) which i renamed. The problem from my research thus far appears to be either a bad AR mem card or incompatible bios.
Has anyone been successful with a 3944 bios and AR for 007?
Also, how big should the exploit zipped file be?
Flick... I have 3944 Kernal/Bios whatever you want to call it, and yes the action replay with the 007 hack works perfectly fine for me. I still haven't figured out what mostly perminant way of loading stuff is though. And that's why I'm looking through. Apparently Bert is Cheating on Ernie wont work with my BIOS, so I'm kind of stuck. If anyone has any ideas for me let me know. I want to be able to play backups, and have it load to EVOX even when a game is in... if this is possible. Thanks
i have 4034 bios and Dashboard
i am using the 007 Exploit
Phoinex Loads and then it goes black ...... what the hell should i do
hey can anyone e-mail their save game file for mech assult somehow i can not get this thing to work. thanks.
Hey, Does this hack make any changes in my EEPROM, or some other Live needed file ???????
lol if u do the hack u can't use live at all.best chance is a modchip with a on off switch
plus to everyone getting the black screens if your using the platinum hits version of 007 u cant if your choosing load game u cant u need to enter a new mission go back to the main menu then load the game.
if it freezes it might be becouse evox.ini has IGR=Yes that will make pbl freese everytime IGR is implimented in the x2 bios anyway so dont worry just edit your evox ini so all the IGR=Yes are changed to IGR=No.
hope it helps someone.
| QUOTE (stanneh @ Oct 8 2003, 09:19 PM) |
if it freezes it might be becouse evox.ini has IGR=Yes that will make pbl freese everytime IGR is implimented in the x2 bios anyway so dont worry just edit your evox ini so all the IGR=Yes are changed to IGR=No.
|
Did not work for me (007 savegame). Got the red-light just after the Phoenix logo. Seems like some of the skin for Evox get painted to the screens before it crash.
What does IGR means ?
And is it possible to download a 007 savegame with Phoenix integrated/signed default.xbe ?
I followed the tut and when i load mission i see the phoenixthen screen goes black and then i see some artifacts then the big MS x pops up and it just stays there
What did i do wrong?
, will this method work on a non-modded Xbox making the evoX screen work? And if so, is this change perminant? (I'm not sure if this is important but I will use the MA exploit method using a memory card).
If you reply, you make me a very happy person!
Bump,
please reply, I can't use this method if it's gonna perminantly do something to my xbox.
I think I am following everything in this tutorial but I just can not get the save game zip onto my ActionReplay memory card. If I drag it into the middle window it shows up fine as a MechAssult save. It says "Run Linux" as the save name. But when I try and drag it into the memory card window the progress bar goes up a bit and then says there was an error with the save. After this it will show up in the memory card window as Unamed Save. At this point I can not delete it. Trying to delete it with ActionReplay just crashes the program. I have to take th memory card to the Xbox and delete it there. In the XBox it shows up as a corrupted save file.
I thought it might be a problem with the card itself but I loaded it up wih a bunch of other saves and it seems to work fine.
Can something in the file itself cause it to not copy properly? I figured if it showed up in the middle windows it must be valid so I can not figure out why I can not copy it over.
Any help would be appreciated.
It's quite a large save, so I would suggest taking most other stuff off the card, because you may not have enough room, that's all I can think of.
Well, I've been at this for a couple days strait, poured over the tutorial countless times, and no matter what I try, I allways get the black screen.
I dont suppose that makes much of a difference though... after reading through some of the posts on this thread it seems that this method still cant avoid eject on reset, even when using an eject-fix bios? Im kind of wondering at this point what exactly you would do with an exploit that's only advantage is the ability to avoid altering or adding files to the hard drive, when you cant load anything off a disc..
In any event.. Im curious.. instead of using the bios loader, would it be posible to simply make a copy of the MSdash that has the font exploit applied to it, then sign it with the habibi key, and hide the whole shabang in the game save file? Is something like that what people mean when they talk about using the font exploit on this thread?
-Orochi
erased
Is there a way to stop the Xbox returning to dashboard when opening the CD drive???
Also, is there a way to install EvoX and create an icon on the MS Dashboard (like you can with the linux exploit).
For all the newbies trying to install the font exploit, use the tutorial from this thread.
http://forums.xbox-s...ST&f=45&t=79558
When you get to the section about the phoenix loader, you will have to edit the evox.ini file that comes with the loader to point to the drive you have your xboxdash.xbe file. From what I remember, the evox.ini file that comes with pbl does not specify the right place. I ended up using pbl 1.3 and all I did was replace the xboxrom.bin file with the evoxd6_ejectfix_bfm.bin file. You do have to rename it to xboxrom.bin though. Just make sure where it says to extract the pbl files that you have to replace the xboxrom.bin file accordingly.
| QUOTE (kickson @ Dec 2 2003, 11:56 PM) |
| evoxd6_ejectfix_bfm.bin file. You do have to rename it to xboxrom.bin though. Just make sure where it says to extract the pbl files that you have to replace the xboxrom.bin file accordingly. |
Did the eject fix work with that ?
i followed all these instructions but when i try to load it with mechassault it says that it cannot load (run linux)