| QUOTE (xafloc @ Jun 7 2004, 07:36 PM) |
I have a saved game exploit, that I acquired from a friend (MA), with PBL 1.3 on it.
I am running Kernel 5101 and DB 5969.
I've placed the saved game on the Xbox HD, then I run the 1.3 exploit, and FTP over to the Xbox. I then replace the boot.cfg and the default.xbe from within the UDATA directory. I also take the eVoxM7.bin file and replace the xboxrom.bin file.
However, when I reboot the xbox and run MA, and load the saved game, it pops me into an Error 21 screen.
Did I miss a crucial step here? |
When you transfered it to the Xbox, did you use an AR card? If so, that unsigned/corrupted it. If not, did you sign PBL with -habibi, if needed? I know not all of the releases of PBL were signed.
Ok, I did some reading, correct me where I may be wrong.
I go and grab a tool called xbedump, and somehow transfer that to the Xbox (via FTP I presume). Now, how the heck to I run this thing?
| QUOTE (xafloc @ Jun 7 2004, 09:41 PM) |
Ok, I did some reading, correct me where I may be wrong.
I go and grab a tool called xbedump, and somehow transfer that to the Xbox (via FTP I presume). Now, how the heck to I run this thing? |
You don't run it on your Xbox--you run it from the command prompt on your computer.
Here is the latest update.
I've signed the default.xbe, and re-created by MA saved game. I included hte boot.cfg, default.xbe and I renamed the evox*.bin file to be xboxrom.bin, and placed it in the same directory as the boot.cfg. I also placed it in a folder called bioses in that same directory.
When I fire it up, I now see the 1.4.1 text based interface. However, I can't use the controller (A to select a bios, etc). So, I sit there and wait for the default timeout.
At this point, for a fraction of a second I see:
| CODE |
| Loading :/Bioses/xboxrom.bin |
And then it reboots into the MA game.
What did I miss?
| QUOTE (xafloc @ Jun 8 2004, 10:25 AM) |
Here is the latest update.
I've signed the default.xbe, and re-created by MA saved game. I included hte boot.cfg, default.xbe and I renamed the evox*.bin file to be xboxrom.bin, and placed it in the same directory as the boot.cfg. I also placed it in a folder called bioses in that same directory.
When I fire it up, I now see the 1.4.1 text based interface. However, I can't use the controller (A to select a bios, etc). So, I sit there and wait for the default timeout.
At this point, for a fraction of a second I see:
| CODE | | Loading :/Bioses/xboxrom.bin |
And then it reboots into the MA game.
What did I miss?
|
What kind of controller are you using with PBL? Do you have 4 in the ports? Did you remember the RC4 & eeprom keys in the boot.cfg file? Is the bios you used BFM? Did you make sure the bios you are booting from doesn't look for D:\default.xbe first?
| QUOTE (xafloc @ Jun 8 2004, 01:36 AM) |
| I also take the eVoxM7.bin file and replace the xboxrom.bin file. |
The bios file you replaced the default one with was a BFM bios right? It nees to be Bootable From Media to work with PBL.
Edit : You beat me to it Blank

. Yup, could be the RC4 key in boot.cfg also.
Ok, here is the latest.
I grabbed a different copy of PBL 1.4.1, and I have made it slightly further.
I know for a fact now, that PBL is coming up, and that it is using the xboxrom.bin, EvoxM7.bin. However, the minute it loads it, it jsut restarts the MA game.
The buttons are working in this version, so I can hit A and then select the eVox bin file. But, it still does the same restart.
Any ideas?
That's expected. What's happening is that the BIOS is being loaded, and it's going through the boot sequence (as if you rebooted). Since there's a disc in the drive, it runs it. To get rid of this problem, you'll need to use XBtool to edit the BIOS boot sequence so that it doesn't load D:\default.xbe. We usually change it to D:\restore.xbe.
To use XBtool, just take your RC4 key from your boot.cfg, place it in debug.ini (found in "More Configs"), and then place debug.ini in your Config folder. When you run XBtool, be sure to select "debug" in the dropdown list box.
| QUOTE (Grospolina @ Jun 8 2004, 03:21 PM) |
That's expected. What's happening is that the BIOS is being loaded, and it's going through the boot sequence (as if you rebooted). Since there's a disc in the drive, it runs it. To get rid of this problem, you'll need to use XBtool to edit the BIOS boot sequence so that it doesn't load D:\default.xbe. We usually change it to D:\restore.xbe.
To use XBtool, just take your RC4 key from your boot.cfg, place it in debug.ini (found in "More Configs"), and then place debug.ini in your Config folder. When you run XBtool, be sure to select "debug" in the dropdown list box. |
| QUOTE |
Did you make sure the bios you are booting from doesn't look for D:\default.xbe first?
|
| QUOTE (xafloc @ Jun 8 2004, 04:08 PM) |
Thanks for hte prompt reply. I've at least got it to do something different now.
I've done as you said, and what it ends up doing now, is rebooting to the Green and black Xbox logo, and just sits there.
thoughts? |
Do you have EvoX installed where it points to?
| QUOTE (xafloc @ Jun 8 2004, 04:16 PM) |
I acctually started checking that right after my post. It was indeed wrong (XBtool showed me that).
I'm in the process of updating, but need to find the latest evox XBE file.
Thanks |
Hop on #xbins and pick up version 3935.
| QUOTE (xafloc @ Jun 8 2004, 10:27 PM) |
| Hopefully this isn't a stupid question, but all the releases I can find, do not include the XBE, only the .bin? |
Nevermind...downloaded oen of many releases...didn't have it. But I found the right one.
Update:
I have been able to sucessfully boot into eVox, after using XBtool to update the boot order. I had to hard-code the location to the savegame evoxdash.xbe file, but I am assuming, until I do a system mod, that that is the way to do it.
Here are my next steps:
1) Get FTP/telnet working (probably just an evox.ini problem)
2) Downgrade the dashboard to 4920 (using Slayers?)
3) Install the permanent mod
Let me know if I missed anything.
Thanks everyone for the help thus far!
| QUOTE (xafloc @ Jun 9 2004, 02:41 AM) |
Here are my next steps: 1) Get FTP/telnet working (probably just an evox.ini problem) 2) Downgrade the dashboard to 4920 (using Slayers?) 3) Install the permanent mod |
Sounds right

Just make sure you're using the UDE mod