File Name: xeBuild File Submitter: EyesOnly File Submitted: 12 Apr 2013 File Category: Xbox360 Modding Tools Introduction: ============= xeBuild is a command line system image builder for JTAG, glitch, and clean images. Run the xeBuild program with no (or incorrect) args to see it's useage info. What's New: =========== - added corona4g build target, nanddump.bin minimum size (without ecc) is 0x3000000 - minor bug fixes - add 16197 Current Limitations: ==================== - STAY THE HELL OFF LIVE! Nuff said, we're not you're mum. How To Use: =========== - See individual folders for lists of files to provide - if desired provide replacement cpu and 1bl keys in text files - open a command window in the xeBuild directory - on the command line type, for example: example - if you provided keys in appropriate text files xeBuild.exe -t glitch -c falcon -d myfalcon myfalconout.bin -t glitch = build a glitch type image -c falcon = use falcon bl and patch set -d myfalcon = a folder is present called "myfalcon" with per machine files, this uses it myfalconout.bin = the file that will be produced - type xeBuild.exe -? for command line info Example: ======== -take original console dump, put it in mytrinity folder as nanddump.bin -set CPU key and 1BL key in ini file, verify LDV from nanddump.bin matches console fuses if not set cfldv in ini file -build (xeBuild.exe -t glitch -d mytrinity -f 13599), flash and hopefully life is good .ini files: =========== Just a word on the format... the ini parser is not very robust, the files need to be plain ASCII, everything after a ; on a line is ignored, and spaces are not acceptable (they get removed). Things like CPU key and 1BL key, if present in the per box ini file need not be placed anywhere else. Optional Patches: ================= Various optional patches are included for use with the -a option, they are: nofcrt - removes fcrt.bin requirement on some drives nohdd - disables detection of internal SATA HDD nohdmiwait - HDMI consoles will no longer wait or EXX screen when video is not ready nomu - disables detection of jasper big block NAND mu notrinmu - disables detection of trinity 4G internal USB module Note: ===== - DON'T USE THIS UNLESS YOU KNOW FOR SURE THAT YOU NEED IT! Using an incorrect controller config can result in problems remapping bad blocks (even manually.) If you have a 16M jasper, an additional build type has been added 'jaspersb', by default the image will be built for jasper with big block controller (config 00023010), use this alternate switch to build for small block controller (config 01198010.) Multi build/options example: ============================ when you specify -f 13599 on the command line: 13599\filelist.ini is parsed instead of data\filelist.ini Also the bin directory is used from 13599\bin\ instead of bin\ allowing anyone to create multiple builds without multiple instances or rebuilds/hex edits/hacks of the main app. The example provided is the last version of 13599 patch set from dash launch and other files to build freeboot 13599 example use: ------------ xeBuild -f 13599 -d myfalcon x13599out.bin -f 13599 : use .\13599\filelist.ini, and .\13599\ for firmware files, .\13599\bin\ for patches -d myfalcon : use .\myfalcon for per build files (cpu key, keyvault, security files, ini etc.) x13599out.bin: override auto generated name and produce .\x13599out.bin as the final NAND image note, if -d ***** is not specified it will still use the original /data and /bin dirs Devkit image building: ====================== This feature is currently considered Beta/Work In Progess. A new image target type was added, "-t devkit" which builds 64M flash images for devkits. Currently untested, building with a 00 filled CPU key will create a zeropaired devkit image that may allow one to boot a software bricked devkit that one does not know the CPU key for and recover it to an operational state. By powering on the console with such an image present, with a recovery DVD in the drive, the recovery software should be able to create a new keyvault, re-pair the DVD drive to the new keyvault, and allow normal operation once complete. Normal devkit image building when one does know their CPU key and thus has security files and keyvault should work as expected. Building devkit for glitch/jtag is also possible using the standard -t glitch/jtag methods. Sample ini have been provided with this release, but will not work unless patches and files are supplied. Note that devkit is not our focus, but was relatively easy and straight forward option to supply for those that wish to make use of it. jasperbigffs: ============= Those who use large block NAND are now able to nearly double the size of the system file area with this option with no apparent ill effects. Normally this option wouldn't be needed, but if one wanted to experiment with more files in flash, or one was building a devkit image for a devkit with a big block flash, this option is required. support: ======== If you've found a bug or have a suggestion, please comment at realmodscene.com/index.php?/forum/15-xebuild/ (english) homebrew-connection.org/forum/in...?board=8.0 (english/french) Credits: ======== Without ikari this would not have been possible, thanks! Hidden Content: You must reply before you can see the hidden data contained here.