XeBuild 1.10

[cory1492 30]

xeBuild 1.10============Introduction:=============    xeBuild is a command line system image builder for JTAG, glitch, and clean images.    Run the xeBuild program with no (or incorrect) arguments to see it's usage info.What's New:===========    - minor bug fixes    - add 16547Current 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 -?', 'xebuild client -?' or 'xebuild update -?' for command line infoUpdate and Client modes:========================    Both modes require the supported updsvr running on the xbox, full functionality may require    updating console patches with the included hv patches. Both the PC and the xbox need to be on    the same subnet/LAN router.   	 Client mode is a simple way to read, write and patch flash as well as few other simple commands    such as the patch updater. The patch updater will look in the folders beside the exe for    {version#}binpatches_{type}.bin    which are full patches for whichever console and hack type, it will load and strip the patches    if needed and send them to the console. Note that only xebuild images are truly supported for this.    Most of the client mode commands should be available on any console, even unhacked devkits. See output    from 'xebuild client -?' for more information on the options available.    Update mode attempts to retain as much data about the console as possible, without having to    provide any info on the command line aside from optional/addon patches if required. After you    copy the $SystemUpdate folder into (in this example) the folder 16203 it is capable of taking    a simple command line like:    xebuild update -f 16203 -a nohdmiwait    It will fetch all the info from the console, and use the updater to update both the system flash    and avatar data on the console (provided you have an 360 formatted HDD internally in the console.)    It has some more advanced options to allow one to build the update image as well as dump the data    from the console as it's acquired, while even leaving the console data untouched. See output    from 'xebuild update -?' for more information on the options available.   	 Neither update or client image writes are able to affect bad blocks, but are able to write new ones.    If this happens mistakenly, an erase block command has been provided in client that will attempt to    clear the bad block - use with caution though, blocks get marked as bad for good reasons and is a normal    occurrence on NAND when a block becomes unreliable.   	 With big block machines, the server will attempt to retain any NAND mu data in the system area, provided    there is no system data to write in the image being sent. It's not foolproof, but update mode should not    corrupt NAND mu.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    nolan	  - disables wired LAN to prevent E75/76/77 on machines with a damaged PHY    nointmu    - disables jasper NANDmu, trinity 4G internal USB and corona 4G MMC memory unitsblmod.bin:==========    Changing the patches to the BL that follows the BL that is executing during glitch attempts    has a direct effect on whether a machine will glitch. The provided patches are generic    and work well on most machines, but this per machine build addon can now be supplied without    modifying the base patches to CBB or CD via a file in the perbuild folder, they will simply be    tacked onto the end of CBB or CD, and the BL size adjusted to include this new data in the hash.    Keep in mind, it can take multiple attempts and re-flashing with different binary data to find    something that will boot at all, let alone be more effective for your console.   	 blmod is currently not supported by update mode.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 dirsDevkit image building:======================    This feature is currently considered Beta/Work In Progress.    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.10 - 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 ..-----//2014-----Changes:========1.10- add 16547- fix a bug with build mode mobile*.dat extraction when multiples of the same settings are stored in the same block but version number does not increase- minor fixes

xeBuild_1.10.zip

[moses_373 151]

Fantastic!  I've been waiting for this!  I got really excited about the devkit image building option for recovering software bricked consoles, but then I realized upon a closer read that it was for devkits only.  Still, It's always exciting to get a new release!

[The Cowboy 28]

---------------------------------------------------------------     xeBuild v1.10.646------------------------------------------------------------------- { Update Mode } ----data directory set from command line to '16547'started, watching network for xbox...success, found xbox beacon at 192.168.2.120attempting to connect...success!Getting console info...success!connected to Jasper with updsvr version 2 (peek version 2)NAND image size: 0x4200000 Block size: 0x21000 Spare Data: Yes------ parsing console info response ------Console Current Info:running kernel  : 2.0.16537.0bootstrap type  : Jasperhardware type   : Jasperhardware flags  : 0x30000207internal HDD    : not presentImage Type      : Jasperbb (GlitchCPU key         : 8F722E433C6649A6BDE70129A751C177 (weight:0x35 valid; ecd: valid)DVD key         : 02E0F04CE974A043FD8352CFA6ECD4CD1BL key         : DD88AD0C9ED669E7B56794FB68563EFA (good)Virtual Fuses   : not present1BL RSA pub     : goodPIRS RSA pub    : goodMASTER RSA pub  : goodCPU Key set to  : 8F722E433C6649A6BDE70129A751C177 (weight:0x35 valid; ecd: valid)1BL Key set to  : 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)xex Key set to  : 0x20B185A59D28FDC340583FBB0896BF91 sum: 0x800 (expects: 0x800)Xell Reason     : console eject buttonCF LDV          : 8Pairing Value   : 0x000000 ------ parsing ini at '16547_glitch.ini' ------ini version 16547ini: label [jasperbl] foundfound (1) 'cb_6750.bin' crc: 0xf7afa8ccfound (2) 'none' crc: 0x00000000found (3) 'cd_8453.bin' crc: 0x25e0acd0found (4) 'ce_1888.bin' crc: 0xff9b60dffound (5) 'cf_16547.bin' crc: 0xa54f9efcfound (6) 'cg_16547.bin' crc: 0xc34c06edini: label [flashfs] foundfound (1) 'aac.xexp' crc: 0xf2808dc5found (2) 'bootanim.xex' crc: 0xd5c63122found (3) 'createprofile.xex' crc: 0xf7e474effound (4) 'dash.xex' crc: 0x2a153493found (5) 'deviceselector.xex' crc: 0x09e04596found (6) 'gamerprofile.xex' crc: 0x4647565dfound (7) 'hud.xex' crc: 0xa6f9c197found (8) 'huduiskin.xex' crc: 0x1d296f10found (9) 'mfgbootlauncher.xex' crc: 0x33d5771bfound (10) 'minimediaplayer.xex' crc: 0x4de56d9cfound (11) 'nomni.xexp' crc: 0x97cadcecfound (12) 'nomnifwk.xexp' crc: 0xc7ab2e5bfound (13) 'nomnifwm.xexp' crc: 0x22253a42found (14) 'SegoeXbox-Light.xtt' crc: 0xe0ee6049found (15) 'signin.xex' crc: 0xaffe7f78found (16) 'updater.xex' crc: 0xf6e1cdd5found (17) 'vk.xex' crc: 0xb916846bfound (18) 'xam.xex' crc: 0x027463e8found (19) 'xenonclatin.xtt' crc: 0xd5d17ff5found (20) 'xenonclatin.xttp' crc: 0x7a507ad1found (21) 'xenonjklatin.xtt' crc: 0xdde4a14cfound (22) 'xenonjklatin.xttp' crc: 0xe2adddfbfound (23) 'ximecore.xex' crc: 0xa86f3ef4found (24) 'ximedic.xex' crc: 0x1d992bfbfound (25) 'ximedic.xexp' crc: 0x186d8df9found (26) '..launch.xex' crc: 0x00000000found (27) '..lhelper.xex' crc: 0x00000000found (28) '..launch.ini' crc: 0x00000000ini: label [security] foundfound (1) 'crl.bin' crc: 0x00000000found (2) 'dae.bin' crc: 0x00000000found (3) 'extended.bin' crc: 0x00000000found (4) 'fcrt.bin' crc: 0x00000000found (5) 'secdata.bin' crc: 0x00000000------ ini parsing completed ------------ getting bad blocks ------processing 1 bad blocks on devicemarking bad block at 0xb5cleaning up stray remapsblock 0xb5 had no remap, assigning remap block 0x1ffdone!mounting SystemRoot to usv:...success!------ getting security files ------retrieving USVRcrl.bin...OK, received 0xa00 bytes        verified! Will use if external file not found.retrieving USVRdae.bin...OK, received 0xad30 bytes        verified! Will use if external file not found.retrieving USVRextended.bin...OK, received 0x4000 bytes        verified! Will use if external file not found.retrieving USVRfcrt.bin...not availableretrieving USVRsecdata.bin...OK, received 0x400 bytes        verified! Will use if external file not found.retrieving USVRkv_enc...OK, received 0x4000 bytes        decrypt and verify...keyvault is good!retrieving USVRsmc_enc...OK, received 0x3000 bytes        decrypt and verify...smc is good!------ getting mobile settings ------retrieving USVRMobileB.dat...OK, received 0x800 bytesretrieving USVRMobileC.dat...OK, received 0x200 bytesretrieving USVRMobileD.dat...OK, received 0x800 bytesretrieving USVRMobileE.dat...OK, received 0x800 bytesretrieving USVRMobileF.dat...not availableretrieving USVRMobileG.dat...not availableretrieving USVRMobileH.dat...not availableretrieving USVRMobileI.dat...not availableretrieving USVRMobileJ.dat...not availableretrieving USVRStatistics.settings...OK, received 0x400 bytesretrieving USVRManufacturing.data...OK, received 0x80 bytesconsole has no available blmodconsole has no available addonsretrieving USVRStatic.settings (smc_config.bin)...OK, received 0x20000 bytes        verifying...smc_config is good!Writing initial header to flash image------ loading system update container ------system update container not found at 16547su20076000_00000000, trying altsystem update container not found at 16547$SystemUpdatesu20076000_00000000, skipping load------ Loading bootloaders and required security files ------reading smc.bin failed, using smc.bin from nand dumpreset smc load address to 0x1000 size 0x3000reading kv.bin failed, using kv.bin from nand dump**** could not read cb_6750.bin (-1) *********** ERROR: critical bootloader files are missing, cannot proceed!***** FATAL UPDATE ERROR: -1 unable to complete NAND image---------------------------------------------------------------    xeBuild Finished. Have a nice day.--------------------------------------------------------------- 

First time i'm updating.What is the problem ?

[hansolo77 17]

Does the remote update feature as laid out in this post still work?

http://www.realmodscene.com/index.php?/topic/2227-dashlaunch-308-xebuild-108-released-with-amazing-new-features/

I'm in the need to update but haven't because I wasn't sure.  I really loved how quick and easy the remote update worked.

[JPizzle 0]

Does the remote update feature as laid out in this post still work?

http://www.realmodscene.com/index.php?/topic/2227-dashlaunch-308-xebuild-108-released-with-amazing-new-features/

I'm in the need to update but haven't because I wasn't sure.  I really loved how quick and easy the remote update worked.

Yes

 

---------------------------------------------------------------     xeBuild v1.10.646------------------------------------------------------------------- { Update Mode } ----data directory set from command line to '16547'started, watching network for xbox...success, found xbox beacon at 192.168.2.120attempting to connect...success!Getting console info...success!connected to Jasper with updsvr version 2 (peek version 2)NAND image size: 0x4200000 Block size: 0x21000 Spare Data: Yes------ parsing console info response ------Console Current Info:running kernel  : 2.0.16537.0bootstrap type  : Jasperhardware type   : Jasperhardware flags  : 0x30000207internal HDD    : not presentImage Type      : Jasperbb (GlitchCPU key         : 8F722E433C6649A6BDE70129A751C177 (weight:0x35 valid; ecd: valid)DVD key         : 02E0F04CE974A043FD8352CFA6ECD4CD1BL key         : DD88AD0C9ED669E7B56794FB68563EFA (good)Virtual Fuses   : not present1BL RSA pub     : goodPIRS RSA pub    : goodMASTER RSA pub  : goodCPU Key set to  : 8F722E433C6649A6BDE70129A751C177 (weight:0x35 valid; ecd: valid)1BL Key set to  : 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)xex Key set to  : 0x20B185A59D28FDC340583FBB0896BF91 sum: 0x800 (expects: 0x800)Xell Reason     : console eject buttonCF LDV          : 8Pairing Value   : 0x000000 ------ parsing ini at '16547_glitch.ini' ------ini version 16547ini: label [jasperbl] foundfound (1) 'cb_6750.bin' crc: 0xf7afa8ccfound (2) 'none' crc: 0x00000000found (3) 'cd_8453.bin' crc: 0x25e0acd0found (4) 'ce_1888.bin' crc: 0xff9b60dffound (5) 'cf_16547.bin' crc: 0xa54f9efcfound (6) 'cg_16547.bin' crc: 0xc34c06edini: label [flashfs] foundfound (1) 'aac.xexp' crc: 0xf2808dc5found (2) 'bootanim.xex' crc: 0xd5c63122found (3) 'createprofile.xex' crc: 0xf7e474effound (4) 'dash.xex' crc: 0x2a153493found (5) 'deviceselector.xex' crc: 0x09e04596found (6) 'gamerprofile.xex' crc: 0x4647565dfound (7) 'hud.xex' crc: 0xa6f9c197found (8) 'huduiskin.xex' crc: 0x1d296f10found (9) 'mfgbootlauncher.xex' crc: 0x33d5771bfound (10) 'minimediaplayer.xex' crc: 0x4de56d9cfound (11) 'nomni.xexp' crc: 0x97cadcecfound (12) 'nomnifwk.xexp' crc: 0xc7ab2e5bfound (13) 'nomnifwm.xexp' crc: 0x22253a42found (14) 'SegoeXbox-Light.xtt' crc: 0xe0ee6049found (15) 'signin.xex' crc: 0xaffe7f78found (16) 'updater.xex' crc: 0xf6e1cdd5found (17) 'vk.xex' crc: 0xb916846bfound (18) 'xam.xex' crc: 0x027463e8found (19) 'xenonclatin.xtt' crc: 0xd5d17ff5found (20) 'xenonclatin.xttp' crc: 0x7a507ad1found (21) 'xenonjklatin.xtt' crc: 0xdde4a14cfound (22) 'xenonjklatin.xttp' crc: 0xe2adddfbfound (23) 'ximecore.xex' crc: 0xa86f3ef4found (24) 'ximedic.xex' crc: 0x1d992bfbfound (25) 'ximedic.xexp' crc: 0x186d8df9found (26) '..launch.xex' crc: 0x00000000found (27) '..lhelper.xex' crc: 0x00000000found (28) '..launch.ini' crc: 0x00000000ini: label [security] foundfound (1) 'crl.bin' crc: 0x00000000found (2) 'dae.bin' crc: 0x00000000found (3) 'extended.bin' crc: 0x00000000found (4) 'fcrt.bin' crc: 0x00000000found (5) 'secdata.bin' crc: 0x00000000------ ini parsing completed ------------ getting bad blocks ------processing 1 bad blocks on devicemarking bad block at 0xb5cleaning up stray remapsblock 0xb5 had no remap, assigning remap block 0x1ffdone!mounting SystemRoot to usv:...success!------ getting security files ------retrieving USVRcrl.bin...OK, received 0xa00 bytes        verified! Will use if external file not found.retrieving USVRdae.bin...OK, received 0xad30 bytes        verified! Will use if external file not found.retrieving USVRextended.bin...OK, received 0x4000 bytes        verified! Will use if external file not found.retrieving USVRfcrt.bin...not availableretrieving USVRsecdata.bin...OK, received 0x400 bytes        verified! Will use if external file not found.retrieving USVRkv_enc...OK, received 0x4000 bytes        decrypt and verify...keyvault is good!retrieving USVRsmc_enc...OK, received 0x3000 bytes        decrypt and verify...smc is good!------ getting mobile settings ------retrieving USVRMobileB.dat...OK, received 0x800 bytesretrieving USVRMobileC.dat...OK, received 0x200 bytesretrieving USVRMobileD.dat...OK, received 0x800 bytesretrieving USVRMobileE.dat...OK, received 0x800 bytesretrieving USVRMobileF.dat...not availableretrieving USVRMobileG.dat...not availableretrieving USVRMobileH.dat...not availableretrieving USVRMobileI.dat...not availableretrieving USVRMobileJ.dat...not availableretrieving USVRStatistics.settings...OK, received 0x400 bytesretrieving USVRManufacturing.data...OK, received 0x80 bytesconsole has no available blmodconsole has no available addonsretrieving USVRStatic.settings (smc_config.bin)...OK, received 0x20000 bytes        verifying...smc_config is good!Writing initial header to flash image------ loading system update container ------system update container not found at 16547su20076000_00000000, trying altsystem update container not found at 16547$SystemUpdatesu20076000_00000000, skipping load------ Loading bootloaders and required security files ------reading smc.bin failed, using smc.bin from nand dumpreset smc load address to 0x1000 size 0x3000reading kv.bin failed, using kv.bin from nand dump**** could not read cb_6750.bin (-1) *********** ERROR: critical bootloader files are missing, cannot proceed!***** FATAL UPDATE ERROR: -1 unable to complete NAND image---------------------------------------------------------------    xeBuild Finished. Have a nice day.--------------------------------------------------------------- 

First time i'm updating.What is the problem ?

 

Follow the tutorial in the tutorials section 

[GameLov3r 1]

Thanks a lot.

[Swizzy 2077]

Fantastic!  I've been waiting for this!  I got really excited about the devkit image building option for recovering software bricked consoles, but then I realized upon a closer read that it was for devkits only.  Still, It's always exciting to get a new release!

This feature has been there for a VERY long time... nothing new...

[moses_373 151]

This feature has been there for a VERY long time... nothing new...

Schooled by Swizzy... I am now ashamed...

[Raruke 0]

Thanks for the update, waiting for the GUI version. I hope it gets released as well .. Anyway thanks for the effort guys, but please don't forget about GUI version

[Swizzy 2077]

It will be released soon, a friend of mine found a bug we missed during tests, might have a new xebuild release which is what i'm waiting to hear about... been to busy prior to this release to make a updated package, got the notification seconds before i was about to release GUI 2.092...

Sent from my GT-I9300 using Tapatalk

[dominus 1]

Second that. Swizzy - waiting on you.

[Swizzy 2077]

http://www.realmodscene.com/index.php?/topic/2928-xebuild-111/ <--- fixed

** edit: **

http://www.homebrew-connection.org/xebuild-gui-2-092-16547-kernel-support-added/ <--- released the new GUI package now

Edited January 19, 2014 by Swizzy

[dominus 1]

You're the king!