XBtool - XBOX BIOS Mangler

!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!

XBtool is under ongoing developement. Bugs can and will happen. If you plan to use XBtool to modifiy a BIOS then be fully aware that you are responsible for what happens. It is entirely possible that a bug in some patch code, a bug in your flashing software, a power outage, a random gamma ray, or the detonation of an electromagnetic pulse weapon could render your Xbox dead. If you have no way to recover from a bad flash then seriously consider whether the risk is acceptable to you.

Use this software at your own risk!

!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!


Contents

About XBtool
About the DVD Drive Check Option
About the Boot Options
About the BFM Packer
About the BFM Flag Option
About File Sizing
About the " Config\More Configs" Folder
Things to Do
Things to Watch Out For
Bug Reports

Thanks
History


About XBtool

XBtool Unpacks, Packs, and Patches XBOX BIOS/Kernel Files.

You'll need to supply your own RC4 key for encrypted BIOSes. If you are working with a BIOS which works with both the original xbox and the newer revisions then you don't need an RC4 key--use the included "Multi.ini" as-is.


About the DVD Drive Check Option

Unchecking this box will disable the DVD drive check so that the Xbox will boot with no DVD drive installed. This might be useful if your DVD drive is dead. This patch is built-in to later x2 kernels.


About the Boot Options

Back-slashes can be used for dashes in subfolders.

X2 BIOSes have 3 partion options and XBtool pools the space for the dash strings. The kernel will try to laod the xbe's in top to bottom order. The total space available for dash names depends on how many dash options are used. There are a total 129 bytes available. However, each dash option needs 29 bytes for the partition info plus a null terminator. If you make one option blank you'll gain that extra 30 bytes for the total dash name pool. There is, of course, a minimum requirement of one boot partition/dash, so the longest dash name available would be 99 characters. The first dash option must not be blank.

Evox has two boot partition/dash choices. The second dash name can be 18 characters long. Dash strings cannot be pooled in Evox because the strings are not in contigous space.


About the BFM Packer

If you plan to use this feature, please read the following section in its entirety.

Packs kernels so that they can be used with the Phoenix loader. I believe they should work using the debug BFM function also, but I haven't tested this. This option is only for conversion of a non-BFM BIOS. You should leave the box unchecked if the BIOS is already BFM.

Conversion may not work with all BIOSes. I have tested x2 4977, Evox D.6, and TATX successfully. Complex 4627 Debug 1.03 failed to load using the Phoenix loader. It might simply be a matter of finding the correct reainder and 2bl images.

In order to enable this feature you'll need to place a config file and two image files named "bfm_remainder.img" and "bfm_2bl.img" in the "Config\BFM\" folder. You can get the image files by unpacking a BFM BIOS and renaming its 2bl and remainder images. The config file should be a debug config named bfm.ini and should contain an RC4 key--preferably a debug RC4 key. The remainder image used should be big enough to accomodate your kernel. Debugs are natively 512k, for example.

The BFM option is only for packing/saving BIOS files. It has no effect when opening or unpacking. If the BFM packing option is selected then the config file chosen under BIOS Type is ignored (when saving/packing).


About the BFM Flag Option

This toggles the boot from media flag in the kernel. Checking the box means the saved kernel will not display the Xbox logo screen when booting from media. Don't set the BFM flag for BIOS files intended for flashing to a modchip or the TSOP. The BFM flag option is intended for toggling the flag in kernels already packed in a BFM package. The Convert to BFM function ignores this setting and will instead ask if you'd like to set the flag before packing the BIOS.


About File Sizing

When saving a file the resulting BIOS file will be saved to the size selected in the XBtool dialog or to the minimum size for the currently opened BIOS, whichever is larger. When using the size button, BIOS files are not opened but blindly cut or mirrored to the selected size. No minimum size checking is done when the size button is used. All debugs that I am aware of must not be sized to smaller than 512k. Some BFMs must be 1MB.


About the " Config\More Configs" Folder

This folder contains some useful config files. You will need to enter the proper RC4 key and copy them to the Config folder to use them.

The format for the RC4 key line in the config file is like so:
RC4_key=0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F


Things to Do


Things to Watch Out For


Send Bug Reports to: xbtool@alltel.net

I need good feedback if anyone suspects a bug. Bug reports like, "Sometimes xbtool makes bad bioses," are not helpful. If you suspect XBtool made a bad BIOS, reload that BIOS into XBtool and see if it reads ok. Then note the settings and include them in your report. If possible, try to see if the bug is repeatable. I may ask to see a bad BIOS file, but please don't send any unless I ask.


Thank You

(in no particular order)

XBtool is very much a collaborative effort. Without these people, it would, at best, be much less functional than it is, and, at worst, nonexistent.


History

1.0.8b4

1.0.8b3

1.0.8b2

1.0.8b1

1.0.5

1.0.4b1

1.0.2

1.0.1

1.0.1b5

1.0.1b4

1.0.1b3

1.0.1b2

1.0.1b1