Citation
Le fonctionnement du nand builder est toujour le même, il faut mettre votre nand d'origine renommé "nanddump.bin et votre clé cpu dans le dossier mydata et utiliser la commande suivante :
Par exemple pour une console glitch et faire une nand en kernel 14699 :
xebuild -t glitch -f 14699 -d maslim nandflash.bin
-t : pour le type de hack utilisé (-t glitch ou -t retail)
-f : version du kernel
-d : nom du dossier contenant vos données
Changelog V2.05
Swizzy's xeBuild GUI Version 2.05
---------------------------------
****** 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!
NOTE: This is the official frontend/GUI for xeBuild, i have contacts with the team, but i cannot give you details about future features or how everything works.
NOTE: I take NO responsibility for damage to your console/files caused by your use of my program!
NOTE: If the program say something about "Unkown" when you check the nand this ussually means it is NOT supported! If you encounter a problem with a NAND that the GUI can't identify that's probably NOT a bug in the program, but rather unsupported versions...
======================================================================
Requirements - What you need to do have in order for this to work!
======================================================================
- Microsoft .NET Framework 2.0 or later
- Your CPUKey or network connection with your console (when creating images other then ECC)
- A dump of your nand OR donor files OR a motherboard and a device that can dump the nand using nandpro
======================================================================
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 IF YOU KNOW WHAT YOU ARE DOING!!!!
kv.bin - donor keyvault; ONLY USE THIS IF YOU KNOW WHAT YOU ARE DOING!!!!
smc_config.bin - donor smc_config; ONLY USE THIS IF YOU KNOW WHAT YOU ARE DOING!!!!
Xell.bin - Custom Xell of your choice; ONLY USE THIS IF YOU KNOW WHAT YOU ARE DOING!!!!
cpukey.txt - It'll read first line of this file, if it starts with "cpukey" it'll read the last 32 characters from that line (removing any extra spaces) otherwise it'll read the first 32 characters of that line (removing any extra spaces)
FUSE.txt - It'll parse it as if it was saved from Xell using network...
flashdmp.bin - It'll load this as source nand
Default.xml - It'll load any preset settings from this file
nandpro.xml - It'll load any nandpro 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 generated image
======================================================================
Notes about build types/image types
======================================================================
First of all, there are 3 types of hacks, first one is called "JTAG"
or "SMC-JTAG" it's the first version of the JTAG hack for Xbox 360
the requirements to use this type of hack is:
- Dashboard may NOT be higher then 2.0.7371.0
- The console may NOT be manufactured or have been to a repaircenter
after 2009-06-xx~ there are some exceptions to this, but most of the
consoles after this has new CB versions which have "fixed" the hack
Valid CB versions for JTAG includes:
* Xenon: 1888, 1902, 1903, 1920, 1921
* Zephyr: 4558, 4571, 4580
* Falcon: 5761, 5766, 5770
* Jasper: 6712, 6723
Second hack is called "RGH" or "Reset Glitch Hack" it was made by GliGli
and Tiros, This hack works for almost all versions of consoles, however
phat consoles have had this "fixed" by getting split CB versions, the
requirements here are quite simple:
- If you have a "phatt" console (non-slim) it may NOT have a dashboard above
2.0.14699.0 because after this it'll have the new CB versions and require the
new RGH 2.0 hack
Valid CB versions for RGH includes:
* Xenon: 1923, 1940, 7375
* Zephyr: 4578, 4579
* Falcon: 5771
* Jasper: 6750, 6751
* Trinity: 9188, 9230
Third and last hack is called "RGH 2.0", it was made by Team-Xecuter and
stolen/leaked to Team Squirt360 and released, it works something similar
to RGH but still a little different, this supports updated phatt consoles
and will probably support any newer dashboard, there is no restrictions to
this type of hack at the time of writing (apart from not beeing meant for
slims)
Valid CB versions for RGH 2.0 includes:
* Zephyr: 4575, 4577
* Falcon: 5772, 5773
* Jasper: 6752, 6753
Changelog V1.1
- Added: Function to prepare a USB memory stick for updating your console with the AVATAR support (Update downloader)
- Fixed: Copying of Cygnos360 V2 SMC now works...
- Fixed: Some Xenon SMC's didn't show previous hack properly... works now
- Fixed: Sometimes the app will recognise your SMC as Cygnos whiles it's JTAG, the app will now show you it's JTAG if it can see that it's JTAG patched aswell instead of fooling you by saying it's a cygnos 360 patch...
- Changed: The app no longer asks if you want to clear the log after autosaving, instead it asks if you want to Close the app, Clear the log or just leave the way it is
- Added: Reading cpukey/ldv from fuse.txt or downloading it from xell now also saves both CPUKey and DVDKey (if available) to keys.txt
Changelog : 1.00
- hotfix - jtag images were being created with incorrect patch file number (xexp1 instead of xexp2)
- 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
Changelog version GUI:
- la recupération directement depuis la Xell via le réseau (un fichier fuse.txt sera alors créer)
- l'intégration des patch dashlaunch,
- la possibilité d'utiliser un xell custom
- la possibilité d'utiliser le patch ôtant la necessité d'utiliser le fichier FCRT.bin pour les slims (sauf lecteur 1175)
Voici une vidéo du metro dashboard, (le kernel dans la video est 14696, mais xebuild apporte bien le support du kernel 14699)
Ancienne version:
xeBuild-GUI-2.0
xeBuild-GUI-2.01
xeBuild-GUI-2.01 FR
xeBuild-GUI-2.02
Nouvelle version:
xeBuild-GUI-2.05
Source: LS by Razkar.

Connexion »
Inscrivez-vous !
Aide























