Search the Community

** I did not write this tutorial nor do I take ANY repsonsibility for your 360 exploding if you follow it ** I want to go ahead and get this up for the folks needing help with xebuild. I will be adding more information to it later. ****DISCLAIMER: This information is to be used for educational purposes only and is not to be used for software piracy or anything that may violate the Microsoft Xbox360 terms and conditions. What you need. -Xebuild v1.00.f1 (xeBuild_1.00_f1.zip) -14699.zip (these are filesystem files, NOT the systemupdate from Microsoft) -Nand Dump (either original NAND or currently working freeboot dump from nand flasher 360 or xellous) -Cpu key (from Xell/Xellous/Xell reloaded) -1blkey (Google for this) -SMC.bin (for jtag only, and only if you are using orginal nand image to build, more on this later in the guide) -360 Flash Dump Tool 0.97 (Google to find this) Step 1 Preparing vital files. First you will need a nand dump. This can be obtained in any number of ways. You can use an original nand dump, or you can use a currently working freeboot dump (taken from nand flasher 360 or xellous) Name your nand dump nanddump.bin and place it in the mydata folder included with xebuild. Next, edit the cpukey.txt file inside the mydata folder, remove the dummy key and replace it with your CPU key (if you don’t have this you can obtain it by booting xell/xellous/xell reloaded) Save the file. Next open 1blkey.txt in the root of and replace the dummy key with the 1blkey (Google to find this) and save the file. Now, extract the contents of the 14699.zip file into the 14699 folder included with xebuild (xebuild\14699) FOR JTAG ONLY: If you are using an orginal nand dump, you will need to include a prehacked smc.bin that matches your console and wiring configuration (you can find smc packs on google). If you already have a working jtag setup and you have dumped your nand you do not need to provide this, xebuild will use the one from your nand dump. Step 2 Edit Options.ini: Below is an example from the options.ini ; console type ; valid values are: xenon, zephyr, falcon, jasper, jasper256, jasper512, trinity ; ie: type=falcon; type = trinity ; put hexidecimal 1BL key here, or on command line, or in 1blkey.txt 1blkey = 1blkeygoeshere ; put hexidecimal cpu key here, or on command line, or in cpukey.txt cpukey = cpukeygoeshere ; byte 0x21f of decrypted CF (also is the count of 0xF in fuse rows 7 and 8) ; if you provide a nanddump.bin with the correct ldv value, there is no reason to fill this in ; jtag images won't care what this value is set to, but glitch and retail images require this to match CPU fuses cfldv = 2 You will need to enter the 1blkey, cpukey, and console type to the appropriate fields. If you are doing a jtag, that is all the info you need to enter, you do not need to enter cfldv for jtag. FOR GLITCH: Make sure to set your CF LDV. (cfldv = ) You can obtain this by opening your orginal nand dump in 360 flash dump tool 0.97. Look for CF LDV and use the highest number that you see on the screen, as shown in the picture below. Please note, that it may not be the same box as shown in the screenshot, that shows the highest number LDV. Again, you want the highest number you see. If for some reason you cant get LDV from 360 flash dump tool, You can also get the LDV by booting up xell reloaded and counting the total number of the letter F in fuse like 7+8. The number of F you see will be the LDV. After you have entered the cfldv, now scroll down in the options.ini and look for this. patchsmc = false Change it to: patchsmc = true (This will automatically patch the smc taken from the original nand dump for glitch only!) Save the file once you have made the proper changes. Step 3 build: Open a command prompt in the xebuild folder (You can do so easily by holding down the shift button and right clicking on the folder containing xebuild. Then choose "open command window here".) We will be using the following command to build the image. Replace the parts of the command to match your type of console. xeBuild.exe -t glitch -c trinity -d mydata -f 14699 -t = type of hack, glitch, jtag, retail (remember you have to use the proper hack for your console!) -c = type of motherboard you have (xenon, falcon, zephyr, jasper, jasper256, jasper512, trinity) -d = the folder containing our vital files we prepared in step 1. -f = the version dash/kernel you wish to build. (at the time of writing this 14699 is latest) Once you have edited the command to fit your setup, copy and paste it into your open command window and press enter. If everything worked properly, it should look like the picture below. You may get a message about fcrt.bin missing. If you do its likely because your nand image didn't contain fcrt.bin (some boards do not) Just ignore the warning and move on. **Note: xebuild will automaticly remap any bad blocks you have if you provided a nand dump. Now you can flash the image via a nand flashing device like nandx, or you can use software to flash it such as nand flasher 360 (recommended) or xellous. (To do so with xellous name the image updflash.bin and place on root of fat32 formatted usb stick, and boot xellous) DO NOT FORGET You need to obtain the official Microsoft update matching the version of dash/kernel you built (in this case 14699)You can obtain it from here: http://www.xbox.com/system-update-usb To install, extract the $systemupdate folder into the root of a fat32 formatted usb stick. (if you already have dashlaunch installed, you may have to name it $$ystemupdate) Don’t worry, it will not damage your hacked system. Also, you will need to install the latest dashlaunch version (at time of writing this it is 2.27) You can do so by running the default.xex file from a dashboard such as freestyle dash and following the on screen instructions. Install in that order. systemupdate then dashlaunch