xeBuild 1.00 & dash launch v2.27 | JTAG & Glitch - 14699

[Jim_Jones]

Spoiler: 

xeBuild 1.00
============


Introduction:
=============
After a lot of work, xeBuild brings together ggbuild and fbbuild into
a single application for building glitch, jtag and clean retail images.


What's New:
===========
- builds jtag/glitch/retail images
- image type specifyer changed, specify -t on command line
- all ini options are now available on the command line (no spaces allowed!)
- patch append option, -o [patchname] via command line, see NOMU/NOFCRT below
or about_patches.S for further info. Up to 16 files can be specified.
- NOMU and NOFCRT patches are provided as optional patches, please use the
-a flag on the command line (ie: -a nomu and/or -a nofcrt) if you want
to use them, nomu disables jasper NAND memory unit, nofcrt will attempt
to disable FCRT file (not needed if yours isn't corrupt)
- nonandmu has been changed to nandmu so it's behavior is inverted
- virtual fuses is no longer being pursued for glitch images as correct
cpu key is already required to build working trinity images. They remain
for JTAG images.


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.


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


Credits:
========
Without ikari this would not have been possible, thanks!
__ ____ ___ ___ _____
/ _|_ __ ___ ___| __ ) / _ \ / _ \_ _|
| |_| '__/ _ \/ _ \ _ \| | | | | | || |
| _| | | __/ __/ |_) | |_| | |_| || |
|_| |_| \___|\___|____/ \___/ \___/ |_|
[v0.07 - 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 to Free60 and Redline99 for providing usable xell builds [3

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 ..

-----
//2011
-----

Changes:
========
1.00
- gets security files from nanddump.bin and verifies them (odd.bin is currently not processed)
- option added to disable extracting security files from nanddump.bin
- decrypts perbuild security files for verification (crl/dae only currently, updater files work too)
- zero nonce data in bls before checking crc (inlcuded file lists updated with new crc and explanation)
- fixed a bug with mobile extraction
- fixed a bug with fsroot processing
- (glitch) dynamic SMC patcher, no longer limited to hard coded hash/offsets
- added more SMC hashes to verify known clean SMCs
- will attempt to decrypt external encrypted smc.bin if needed
- whitelist more chars in the file list parser
- altered so that pairing value will be retreived from nanddump.bin even if ldv is set in ini
- dual CB is dictated by ini, "none" filename indicates single CB (jtag does not use dual CB)
- increased logged info when adding files to flashfs
- odd.bin in encrypted (only!) form is now handled (from file or nanddump.bin)
- ini options are now available as -o options on command line
- added -t command line flag for glitch/retail/jtag selection
- JTAG image creation merged
- separate retail/glitch/jtag into individual per-firmware ini lists
- added -noenter command line option to suppres application asking to press enter on completion
- added proper errorlevel exiting, 1=usage/commandline error, 2=file write err, 3=image build error
- add 'cygnos' and 'xellbutton' options for glitch images with appropriate bl patches (either may affect fat glitch boot rate!)
- non-critical spare data fix to the way smc config is added to image
- update freeboot core and glitch base patches to accept a secondary xell poweron reason
- rewrote extended.bin handler, given an invalid/undecryptable file it will create a empty extended.bin
- rewrote keyvault handler, can decrypt and verify kv.bin when it's provided encrypted
- added patch append -a command, and converted nomu and nofcrt to optional patches
- added simple explanation of patch file formats in about_patches.S
- changed nonandmu option to nandmu so it can default to false
- added corona and winchester console types, currently not supported but there if needed
- add 14699

0.33
- corrected bug with ini parsing and dvd region (and others) left blank
- add 13604

0.32
- slim/fat glitch image building (based on fbbuild 0.32)
- builds retail images with -retail command line option
- added autopatch smc option in per box ini file
- extracts pairing value and highest LDV from nanddump.bin
(ini cfldv setting overrides nanddump ldv)

Spoiler: 

Dash Launch 2.27
----------------

****
at time of this writing, this is ONLY compatible with:
"freeBOOT": 9199, 12611, 12625, 13146, 13599, 13604, 14699
"ggBuild" : 13599, 13604, 14699

read info_launch.ini for info on options and setting launch parameters.
****
================================================================================
important note about the new keyswitcher
================================================================================
Retail encrypted xex that are not validly signed will not load due
to the way the new keyswitcher works.

================================================================================
Overview - what it does
================================================================================
- It will launch a XeX or CON file from the path you specified in launch.ini
as long as it's valid
- Depending on the button you hold when the xbox is trying to load the NXE, it
will divert to the xex/con tied to that button or return to default as
defined in launch.ini
- At boot time it is possible to subvert default item and/or NXE loading, but
you must wait until the controller syncs to do so, and the controller must
sync to the top left quadrant (player 1.)
- Depending which button is held when closing miniblade in NXE (use Y button to
close, release then hold a QL button) it will quick launch a CON or XEX
from your ini file
- allows one to patch kernel/xam at bootup with a freeBOOT patch style bin file
from usb or hdd (in that order) must be in root of the device and be named
"kxam.patch" and be no larger than 0x4000 bytes. Again, kxam.patch binary
format is the same as a compiled freeboot patch bin, but uses real virtual
addresses rather than offsets - see 1.0 release for a windows patch builder
- with the included patch set, launch.xex acts as a helper to detect when
xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator
to function together

================================================================================
Installation
================================================================================
- have the required freeboot version installed on the console

- get the installer to a place where you can run it, and do so. Follow onscreen
instructions. The installer will prompt you if it needs to update the
freeboot patches and will give you an opportunity to configure the new
options

- edit and place launch.ini where you would like it, see note below as well
**See inlcuded sample and the info ini which describes the options allowed**

note: the installer includes upgrade paths for dash launch 1.0 users, it will
optionally update launch.ini files wherever found to use the new path names

================================================================================
Updaters and Avatars
================================================================================
- this version of dash launch contains an update blocker that is enabled by
default. There are two ways around this if you wish to install the bits and
pieces used by the dash for kinect and avatars
1 - place the updater that matches this version on removable media, and
rename the folder from $SystemUpdate to $$ystemUpdate
----OR----
2 - place an ini where dash launch can find it and set the noupdater option
to false - noupdater = false
****
NOTE that some games WILL prompt you to update the console if avatars are
not installed, this doesn't mean they have an update to actually put in, it
just means it needs avatar/kinect bins/resources to run
****

================================================================================
LIVEblocker
================================================================================
- if you are like me, and keep your consoles off the net then this option is
for you. It's capable of blocking the resolution of the LIVE specific
servers and does so by default, with an additional option in the ini file
it will attempt to block access to all MS servers. The default option is
set up to block only LIVE servers, which still allows programs like FSD to
access covers and such.

================================================================================
Important - going to NXE
================================================================================
- if you need to go back to NXE and have default item set in ini, HOLD RB while
exiting game via miniblade or exit using one of the miniblade options like
family settings or system settings

================================================================================
INI notes
================================================================================
-it's possible to have multiple ini files, priority is: USB, HDD, BB MU, FLASH
(** it is NOT recommended to launch USB con/xex from hdd ini **)
the first one found on the devices in that order will be the one used.
-see http://code.jellycan.com/simpleini/ for more info on the ini parser

-if you find your ini file is not working, open it in a hex editor and ensure
that windows didn't convert it to a non-ASCII format by putting identifyer
bytes at the beginning of the file. The first charater in a hex editor
should be whatever the first character you have in the ini file, not
non-character codes like 0xFF or similar

================================================================================
Caveats
================================================================================
The work herein is presented as-is, any risk is solely the end users
responsibility. While all of us are sorry when unforseen things happen, not
every situation or mistake can be accounted for before they have been
spotted. Please use responsibly.

================================================================================
Thanks
================================================================================
-Big thanks to those who opened the way and those who made it even more usable.
-Thanks to Tux, Arbiter, stk, the2000, Corrupted, tk_saturn and Toddler for all
the bugs you caught trying to sneak by!
-Thanks AmyGrrl for passing along the glitch and new ideas
-Thanks to Tux, Ironman, JPizzle and Dionis Fernandez for helping procure a
Jasper big block console to extend testing and fix NAND MU corruption bug
Dionis - you went above and beyond!
-Thanks to vgcrepairs for providing the cygnos, dash launch likely wouldn't
exist without one.
-Thanks to FBDev and mojobojo for the data used for the patch options
-Thanks to sm32
-Thanks to unknown, you know why
-Extra Special thanks to SpkLeader, Boflc, and LordXBig!
-Big thanks to Swizzy, the least bit for debugging readmes!
-Thanks to fbbuild, keeping us on our toes and up to date!
-Thanks to xbox-scene for always putting up a release thread announce!
-Greetz to XeDev
-shouts out to E Nellie and D33per, this a sourceless release!

~brought to you by cOz~
07/12/2011

================================================================================
Known Bugs
================================================================================
- Thanks to excellent testers, none were corned by the time of this writing. If
you find any during use, find the release thread at xbox-scene and please
report them there.
- in freestyle 1.7 and earlier, there was a minor glitch that caused console
crashing for some people under rare circumstances, if you haven't updated
to RC1.8 or newer please do so.
- corrupt games when launched return to NXE to display the corrupt game UI

================================================================================
ChangeLog
================================================================================
v2.27
- removed FCRT patch (was not compatible with 1175 drives)
- installer: revise patch checks to only check base patches
- installer: conform to xebuild's base+patch extension method, copies addon patches to
base as needed
- add 14699

Spoiler: 

Swizzy's xeBuild GUI Version 1.0
---------------------------------

****** If you find a bug, let me know! you can reach me on: admin@swizzy.se ******

****** NOTE: I did NOT create xeBuild! i merely made a frontend/gui for it! ******

======================================================================
   Requirements - What you need to do have in order for this to work!
======================================================================
- Microsoft .NET Framework 3.5 or later
- Your CPUKey
- A dump of your nand

======================================================================
   Overview - What it does
======================================================================

- This is a frontend/GUI for xeBuild, what it does is make it easy
for you to select most options that you might need, such as Motherboard,
SMC hack for freeboot, image type etc. etc.

- It is able to check what SMC hack you have previously used for JTAG
it's also able to tell you what SMC version you have, and if it's a
JTAG, Clean/Retail, Glitch or Cygnos patched SMC :)

- If you put any of these files next to the executable it'll use them
automaticly:
SMC.bin - Custom SMC of your choice; ONLY USE THIS OF YOU KNOW WHAT
YOU ARE DOING!!!!
Xell.bin - Custom Xell of your choice; ONLY USE THIS OF YOU KNOW WHAT
YOU ARE DOING!!!!
cpukey.txt - It'll read the first line of this file as CPUKey
flashdmp.bin - It'll load this as source nand ;)
Default.xml - It'll load any preset settings from this file ;)
options.ini - It'll load any custom settings from this (for xeBuild)
launch.ini - Settings for Dashlaunch, if you choose to use this setting
it'll include this file in the built image ;)

======================================================================
    Notes about building retail images
======================================================================

Retail images can be built using this gui, it includes common retail
SMC's i've extracted myself, i make no form of garantuee that these
are safe to use for your console, some machines might not like the
bootloaders etc. which are used by default...

======================================================================
     Notes about LDV
======================================================================

There are 3 ways you can get your LDV value:

1. Use Xell and manually count the ammount of "f" on fusesets
07 and 08, the total here is your LDV value.
2. Use Xell and a network connection, doing this the app can
read fusesets for you and read cpukey aswell as check what ldv your
Xbox 360 should have automaticly for you (this option also sets both)
3. Use 360 Flash Dump Tool and check which value is the highest, this
is the one you will want to be using

Normally (if you have a good dump that does NOT include data from
.ECC file created using RGH python script) xeBuild should be able
to extract this value on it's own, if it can't just follow the
instructions above... if you don't understand these instructions,
ask google!

======================================================================
     Notes about FCRT patches
======================================================================

This patch removes the need for FCRT.bin in nand, however, it will
NOT work for everyone, it's been enabled in the default configuration,
but should be disabled if you are using a machine with a Liteon DG16-D5S
FW: 1175, it's been confirmed by me that it doesn't work on these drives
all others i've tested has worked just fine, however it can still be a 
problem for you to have this activated, disable it if games don't work
from discs (if you use this feature!)

======================================================================
    Changelog - New features and bug fixes
======================================================================

**************
* KNOWN BUGS *
**************
- Whiles checking SMC the app may sometimes crash if using a bad dumped
image, or an image with badblocks in it...

*******
* 1.0 *
*******
- Initial release
- Dashlaunch 2.27 is the version included with this release
- xeBuild 1.0_Hot Fix is the version used with this release
- This version supports building the following Dashboard versions:
   - 2.0.7371.0 - Retail images ONLY
   - 2.0.9199.0 - JTAG images ONLY
   - 2.0.12611.0 - JTAG images ONLY
   - 2.0.12625.0 - JTAG images ONLY
   - 2.0.13146.0 - JTAG images ONLY
   - 2.0.13599.0 - JTAG, Retail and Glitch images
   - 2.0.13604.0 - JTAG, Retail and Glitch images
   - 2.0.14699.0 - JTAG, Retail and Glitch images 
   * Files for 2.0.14699.0 are included *

======================================================================
     Credits - Thanks to:
======================================================================

- cOz - Maker of Dashlaunch, been talking ALOT to him asking for advice
- Razkar - Helping me find bugs and giving me general advice/ideas, along with 
releasing this app on logic-sunrise! :D
- Jack Nepacha - Making my new icons, thanks mate ;)
- Anyone else that has helped me with anything such as tests, bug finding
and such that is not mentioned above, THANK YOU! without testers this app
would be pretty much useless compared to the other GUI versions out there ;)

Download:
http://tinyurl.com/xeBuild-1-00
http://tinyurl.com/dash-launch-2-27
http://tinyurl.com/xeBuild-GUI-v1-0
http://tinyurl.com/SystemUpdate-14699 (BITTE ERST NACH ERFOLGREICHEM UPDATE INSTALLIEREN! entweder den ordner $systemupdate oder $$ystemupdate benennen)

[fxone]

xeBuild 1.00 Hotfix1

Spoiler: 

1.00
- hotfix - jtag images were being created with incorrect patch file number (xexp1 instead of xexp2)

xeBuild Hotfix 1

[Pady]

wird das 14er denn schon benötigt ????

[fxone]

wird das 14er denn schon benötigt ????

soweit mir bekannt ist nein. ist halt nur das neue metro design. und sky und das gelumpse ist glaub ich eh an den live account gebunden. und da live mit jtag eh schlecht ist. kann man sich denk ich zeit laßen

[andy.macht]

wow, das ging mal schnell. wird heute gleich mal richtig ausprobiert

trinity und jasper werd ich heute mal testen.

[Jim_Jones]

xeBuild-GUI-v1.0 hinzugefügt...

[Herrgoettle]

danke,geht alles

[Hocico2010]

Hallo,

ich habe den Glitch Hack erst seit 2 Wochen. Kann mir jemand bitte helfen und erklären (gern über Skype und Teamviewer) was ich machen muss um das XEBuild 1.00 und Dash Launch v 2.27 zu installieren. Einfach eine PM.

Danke im vorraus.

[Jim_Jones]

einfach mal zuerst die readme lesen...

[andy.macht]

danke,geht alles

hast du es mit der gui gemacht? welche version also glitch/JTAG und board-version?

[Pady]

Wie sieht es aus mit xgd 3
Wegen dae.bin???? Gehn die per Disk ?

[Jim_Jones]

bei einer jtag/glitch gibt ein keine kopierschutzmechanismen...

[Herrgoettle]

hast du es mit der gui gemacht? welche version also glitch/JTAG und board-version?

ja ich habs mit der gui gemacht,glitch jasper bb(512).

[iglitare]

Wie sieht es aus mit xgd 3
Wegen dae.bin???? Gehn die per Disk ?

schon ewig...

[esunny4711]

Danke fürs Bereitstellen der files - hat bestens funktioniert,

habs noch die Nacht ohne GUI erstellt, für SLIM
als source die nanddump.bin vom 13604 ggBuild genommen

danach DashLaunch v2.27 und das SystemUpdate 14699 noch für Avatare, etc.

hmm, Begeisterung fürs neue Dash: zu viel LIVE für RGH und immer ähnlicher PS3

[CeeJay1337]

hmm hab nen prob bei ner cygnos v2 falcon. bootlogo ja dann aus.

vorher nie nen prob gehabt, mit 13599 oder 13604 bootet sie auch

[Quiggy]

Danke fürs Bereitstellen der files - hat bestens funktioniert,

habs noch die Nacht ohne GUI erstellt, für SLIM
als source die nanddump.bin vom 13604 ggBuild genommen

danach DashLaunch v2.27 und das SystemUpdate 14699 noch für Avatare, etc.

hmm, Begeisterung fürs neue Dash: zu viel LIVE für RGH und immer ähnlicher PS3

Hab den selben Weg genutzt. Funktioniert auch bei mir super! Hoffentlich kommen die Apps usw. bald ohne Xbox Live aus

[Pady]

lasst es besser zuviele bugs in 14699
zb
guide taste geht net
manchmal gehn xgd3 games net
installiert das update nicht
festplatte kann man nicht formatieren
kinect games auch nur ab und an ja ich habs an mehreren getestet

[andy.macht]

gut zu wissen, ich teste jetzt mal alles mit ner falcon. dann sehen wir weiter...

[Herrgoettle]

lasst es besser zuviele bugs in 14699
zb
guide taste geht net
manchmal gehn xgd3 games net
installiert das update nicht
festplatte kann man nicht formatieren
kinect games auch nur ab und an ja ich habs an mehreren getestet

meine guide taste geht,xgd3 geht von festplatte und dvd,das avatarupdate geht auch(muss man nur umbennenen).
festplatte formatieren und kinect habe ich nicht getestet.

ps hab schon die zweite jasper damit gemacht und habe bisher keine probleme.