After the first day of panic, due to the new update released by Microsoft, that brings the console to the new dashboard / kernel 2.0.14171.0 appear on the scene here is a new version of XeBuild, The command line tool that allows you to create an image Glitch / JTAG / Retail of your console, that supports the very latest version of the kernel 14171.

 

Come together right now to see who can’ perform this update, juicy news and what is contained in this release!

Here's the changelog, and after that the warnings and instructions on using.

What’s New:
===========
- adds 14717
- trinity CB_B patches updated to allow glitch image booting on official 14717 updated slims,
requires having CPU key before building image. Updated fats will likely require new CPLD
timing, if you wish to continue to glitch a fat for the time being it’s advised to not apply
any update ] 14699.
- included xells updated to xell reloaded v0.991 built 2012-02-19. See xell_info folder for
usage info and changelog, or find newer builds at libxenon.org
-note that for xebuild, jtag images use xell-2f not xell-1f
- added devkit image building (WIP, see info below)
- added bigffs jasper type (see info below)
- added a small helper app, ini_creator.exe that will create a basic .ini file with crcs
for xebuild when batches of files are dropped onto it, ready for sorting
- bug fixes

 

XeBuild is the heart of the project RGH / JTAG-day: born from the merger of GGBuild FBBuild and manages to create images from NAND flash on your console for both RGH for JTAG.

This means that those who already know your CPU-Key and has a dump of your NAND is affixed: it can launch the program and create everything you need for your console; If you do not have the CPU-Key joined a working dump of your console, the road splits.

In fact, this program generates only the starting NAND dump and CPU-Key Nand, if you have upgraded to the latest official kernel (just, the 14171) you can not glitchare your console because of the new CB inserted by Microsoft, however if you have a kernel below you can proceed calmly to the glitch!

 

The use is via the command line, and if you are still not as proficient in this method advise everyone to wait for the release of “XeBuild GUI”, a version with GUI very much’ friendly towards newbies.

Here is an excerpt from the README file that explains very well XeBuild its operation:

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 = use falcon falcon bl and patch seen
-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

 

 

And here below, instead of the

DOWNLOAD A XEBUILD 1.01

and

DOWNLOAD THE FILES NEEDED TO MAKE THE KERNEL 14171