JPizzle 0 Posted February 20, 2013 xeBuild 1.07 ============ 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: 13599filelist.ini is parsed instead of datafilelist.ini Also the bin directory is used from 13599bin 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 .13599filelist.ini, and .13599 for firmware files, .13599bin 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 http://www.realmodscene.com/index.php?/forum/15-xebuild/ (english) http://homebrew-connection.org/forum/index.php?board=8.0 (english/french) Credits: ======== Without ikari this would not have been possible, thanks! [v0.08 - inspired by ikari] R.I.P. No this isn't freeboot, it is a clone and has always been since the last release of ibuild. Thanks and greetz to everyone who has contributed to hacking this wonderful machine. Thanks to the engineers and countless others who made the machine what it is... we only wish they had listened and RROD was not a problem. If we were to list everyone here, there would be no time left to play on the machine! Thanks Team Xecuter for the Corona 4G! Thanks to JuggaHax, dayton360mods, glitch360team and all other contributors for helping find a way to make Corona 4G golden! Thanks to Free60, LibXenon.org, Redline99 and Tuxuser for providing xell builds <3 Thanks to Swizzy for making the official GUI front end for xeBuild, for always adding the new stuff we shovel at him and never once complaining. Big thanks to the folks at #freeboot on efnet for the tireless hours of help you all give freely. Thanks to the testers who tirelessly made sure stuff worked. Thanks to rgloader for doing the work yourselves, there *is* no spoon, just a glitch in the matrix. Don't believe what random people *cough* write on forums .. ----- //2012 ----- Changes: ======== 1.07 - trinitybigffs added (big block devkit sized file system for trinity) - -s option added to create a .sha1 file along with the final image if no arg is provided, the final image name will be used with .sha1 appended as extension - change behavior of patchsmc - add 16203 xeBuild_1.07.zip 16203.zip Quote Share this post Link to post Share on other sites
nghia26 0 Posted February 23, 2013 i dont no how to use this Quote Share this post Link to post Share on other sites
JPizzle 0 Posted February 23, 2013 try reading the documentation Quote Share this post Link to post Share on other sites
nghia26 0 Posted February 23, 2013 try reading the documentationthanks but i just use j runner Quote Share this post Link to post Share on other sites
JPizzle 0 Posted February 23, 2013 this is what j runner uses Quote Share this post Link to post Share on other sites
ESTE 6 Posted February 23, 2013 So where can I find 16203 dashfiles for xebuild to make nand image? I don't mean the USB Official Update. I need those Hacked dash filesytem files. Quote Share this post Link to post Share on other sites
JPizzle 0 Posted February 23, 2013 Sorry about that, FS added. Quote Share this post Link to post Share on other sites
Aut0botKilla 4 Posted February 24, 2013 Thanks JP Quote Share this post Link to post Share on other sites
Tyrant 0 Posted March 3, 2013 They should make a gui for people that are just not well experienced "me" and can't use this stuff. Me and command don't really get a long. And I really wish to update. Quote Share this post Link to post Share on other sites
tonymarraffa 2 Posted March 9, 2013 They should make a gui for people that are just not well experienced "me" and can't use this stuff. Me and command don't really get a long. And I really wish to update. I second this! Quote Share this post Link to post Share on other sites
JPizzle 0 Posted March 9, 2013 XeBuild GUI by swizzy Quote Share this post Link to post Share on other sites
TudorBlue 19 Posted March 13, 2013 I definately need a gui I can use on my pc, Im lost with this. Would the older version work with 16203? Quote Share this post Link to post Share on other sites
bfds89 0 Posted March 14, 2013 Newbie question. In J-Runner in XeBuild folder can I copy the folder with dash 16203 from the link in this topic and put it there? And the 16203.zip file do I extract it to bin folder inside 16203 folder or do I place it somewhere else? Sorry if this is kinda obvious, but I dont wanna mess up my console, so I better ask before attempt something stupid. Thanks Quote Share this post Link to post Share on other sites
BL4K3Y 96 Posted March 14, 2013 In J-Runner in XeBuild folder can I copy the folder with dash 16203 from the link in this topic and put it there? And the 16203.zip file do I extract it to bin folder inside 16203 folder or do I place it somewhere else? Do you realise that J-Runner gives you the option to download dashboard/kernel files? Use "Add Dash" from the dashboard version drop-down list in J-Runner. Quote Share this post Link to post Share on other sites
joutain 0 Posted June 9, 2013 hi, when i tried to create an image of 16203 for my trinity xbox, it always goes to the failure like the following, and when i use the 360 FLASH tool to sca't knn the nand dump, it shows that there are some bad block. i don't know whether the failure is related with the bad block or not? and how to fix it? thanks! bad block: Note: Bad Block ID 0x0058 [Offset: 0x0016B000] -> Block ID 0x0058 found @0x3FD [Offset: 0x01073A00] -> Block ID 0x0022 found @0x3FE [Offset: 0x01077C00] Failure: --------------------------------------------------------------- xeBuild v1.07.561 --------------------------------------------------------------- building glitch image An unhandled exception 0xC0000005 has occured, exiting... xeBuild ERROR: Unkown exitcode (4)! ERROR: There was one or more fatal errors: 1 errors during the build process Cleaning data and temporary directories... Done! ****** The app has now finished! ****** Quote Share this post Link to post Share on other sites
