Topic: Ma/007 With Phoenix Bios Loader Tutorial (Read 1096 times)

wonderdog · « **Reply #120 on:** July 24, 2003, 03:58:00 AM »

#Wonderdog

Vitrious · « **Reply #121 on:** July 24, 2003, 08:12:00 AM »

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!

PooN · « **Reply #122 on:** July 24, 2003, 10:06:00 AM »

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

oracle2 · « **Reply #123 on:** July 24, 2003, 02:45:00 PM »

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.

wonderdog · « **Reply #124 on:** July 25, 2003, 02:37:00 AM »

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

kahn2k · « **Reply #125 on:** July 25, 2003, 02:48:00 AM »

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.

wonderdog · « **Reply #126 on:** July 25, 2003, 07:26:00 AM »

Yip, and nope. It doesnt work. See my post above.

#Wonderdog

juleskitten · « **Reply #127 on:** July 25, 2003, 09:58:00 AM »

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???

juleskitten · « **Reply #128 on:** July 25, 2003, 10:16:00 AM »

all I want to do is access the harddrive. any fix, perhaps changiing some of the contents of the MECHWARRIOR gamesave exploit file package?

oracle2 · « **Reply #129 on:** July 25, 2003, 10:18:00 AM »

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.

juleskitten · « **Reply #130 on:** July 25, 2003, 10:26:00 AM »

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.

oracle2 · « **Reply #131 on:** July 25, 2003, 10:39:00 AM »

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.

juleskitten · « **Reply #132 on:** July 25, 2003, 10:55:00 AM »

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?

GQinfinity · « **Reply #133 on:** July 25, 2003, 11:43:00 AM »

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...

juleskitten · « **Reply #134 on:** July 25, 2003, 01:00:00 PM »

thanks for tryng to help though, I hope there is a solution.

Author Topic: Ma/007 With Phoenix Bios Loader Tutorial (Read 1096 times)