|Prepare your EnvironmentInstall the NAND-X drivers (info)Update your NAND-X to v3 if needed (info)Create a new folder on your C: drive called nandpro3Extract the following files/folder to C:\nandpro3
(Just so I don’t have to keep editing this guide so much, rename 360_Multi_Bulider_vX.X to 360_Multi_Builder)
**Note** Only the .xsvf files from coolrunner_xsvf_jed.rar are required for the TX Coolrunner. The .jed files are for other devices.
|Dump/Read the NANDBefore dumping your NAND, it’s probably a good idea to update your xbox to the latest dashboard version. You can do this via Xbox Live, USB key or CD. This is not needed, but it’s probably quicker to get it out of the way now, and will save you and extra step at the end of the guide.DO NOTupdate to any higher version than this guide is based on, just in case MS release and update that can disable this hack. Apparently, that isn’t something they can actually do with the Reset Glitch Hack (unlike the JTAG hack) But you never know.So, with that out of the way, on to the good stuff…Take the console apart and remove the motherboard from the metal cage (info)Connect your NAND-X to the 360 motherboard by soldering your QSB’s, Pin Headers, or direct cable connections to the correct points on your motherboard.NAND-X Install Guides
Once you have your NAND-X wires installed, connect it to your PC via the USB cable…
Make sure that the mains power is connected to the xbox, but do not turn the xbox on.
Now, on your computer, open a command prompt and navigate to…
Do that by hitting the start button, typing cmd and hitting Enter. Then type cd \nandpro3 and hit Enter.
Or.., hold the Shift key, and Right Click on a blank space inside the nandpro3 folder, then click “Open Command window here”
Now type (or Copy and Paste) the following commands, into the command window (same command for Phats or Slims, see Note)
nandpro usb: -r16 nanddump.bin
nandpro usb: -r64 nanddump.bin
(The full 256MB or 512MB is not required)
Now compare dumps by typing…
fc /b nanddump.bin nanddump2.bin
You should see…
FC: no differences found
If there are differences, check your soldering and try again until you have matching dumps.
|Bad Blocks?If bad blockswere found while dumping your NAND…Open one of your NAND dumps in 360 flash dump tool 0.97Don’t worry if it says BADKV all over the place, this is normal because you haven’t entered the CPU Keyyet. (We will get to that later).Check for a bad blocks tab, next to the file system tab.If there is no bad blocks tab, you have no bad blocks.
If there IS a bad blocks tab, click on the tab and verify that it looks like this:
Note: Bad Block ID 0x0349 [Offset: 0x00D8D200]
-> Block ID 0x0349 found @ 0x3FD [Offset: 01073A00]
You should see the above 2 lines of text, for each bad block you have.
The numbers may be different of course, depending on which blocks are bad, but the point is, for each bad block, you should see that the block was found @ another block.
This means that you did have bad blocks, but they have been corrected by the NANDs error correction, so they are legit bad blocks, and not just read errors due to dodgy soldering.
Example of 3 corrected bad blocks…
If the errors are at block 0x050 or above, no further action needs to be taken, because…
“Many user reports indicate that using Xell-Reloaded/Rawflash v3 to flash the Dashboard image, has a much better result over flashing with hardware flashers. This is because it helps to auto-remap the bad blocks in case they exist.”
As we will be booting into Xell-Reloaded, which will use Rawflash v3 to flash the NAND later on, the bad blocks will be auto remapped for us.
If you see:
But NO found @ location for the block, that means this bad block was the result of a read error with the NAND reader. Check your soldering and try again.
If you have Bad Blocks at 0x050 or below, check out Martin C’s guide on how to manually remap them. (Info)
If all checks out, you now have 2 good NAND dumps.
KEEP THEM SAFE. FOREVER.
|Create your XeLL/ECC Glitch imageCopy your nanddump.bin file from the nandpro3folder, to …360_Multi_Builder\Data\my360Launch Run.exe from the 360_Multi_BuilderfolderPress the number corresponding to your motherboard revision, and hit EnterYou will get a warning saying The file “cpukey.txt” is missing.
This is normal as we haven’t created it yet. Press any key to continue.
Sit back and watch 360 Multi Bulider do it’s stuff…
Press any key to close 360 Mulit Builder
Your Image_00000000.ecc file has now been created in 360_Multi_Builder\Data
|Flash the Reset Glitch Hack v1.1 .ecc file to the NANDMove the image_000000000.ecc file into the nandpro3folderEnter the following command for slim consoles and non BB Phatsnandpro usb: +w16 image_00000000.eccOr for BB Jaspers…nandpro usb: +w64 image_00000000.ecc*Note: it must be +w16 NOT –w16
|Programming the TX CoolRunnerDisconnect the cables from the NAND-X (not sure if that’s actually needed, but probably for the best) (the wires can stay soldered for now)Make sure the switch on the CoolRunner is set to PRG(program)Connect the CoolRunner to your NAND-X using the NAND-X to CoolRunner JTAG CableEnter one of the following commands (corresponding to your motherboard revision) (info) into the command prompt window, and hit Enter.
NandPro xsvf: Trinity.xsvf
Once the CoolRunner is programmed, it will say “Successfully executed file“, in the command prompt window, and the Green LED will turn off.
Now disconnect the CoolRunner from the NAND-X, and move switch to NOR (Normal)
Also make sure that the other switch is now set to the correct position for your console type (Phat or Slim)
|Install the TX CoolRunner
Now that you have good/matching NAND dumps, you have programmed the CoolRunner, and have created the Xell/ECC Glitch image, this is probably the best time to install the chip.Printer friendly, quick install guides (A4 paper, 300dpi) (LINK)Various other install methods and tips (LINK)
|Retrieve your CPU KeyNow that your CoolRunner is fully programmed/installed, it’s time to boot the console and retrieve the CPU Key.At this point you only need to connect…
Once you have the above items connected, turn on the console.
You should see a constant Red LED on the CoolRunner as soon as you connect power to the console, joined by a flashing Green LED when you turn it on.
The flashing Green LED indicates that Glitch attempts are taking place.
If you do not see this happening, turn the console off, and refer to the FAQ at the bottom of this guide.
Once the Glitch is successful, you will be greeted on screen with the awesomeness that is XeLL-Reloaded
You may now retrieve your CPU Key, either by copying it from the screen
Or by connecting the Xbox to your LAN via an Ethernet cable, and downloading the info from XeLL-Reloaded via it’s http web interface.
Using your web browser, connect to the IP address shown next to network config: For example: http://192.168.1.47
From XeLL-Reloaded’s web interface…
As you can see above, your CPU Key is made up of two fuseset lines, i.e 03 + 05, or 03 +06, ect.
Your LDV (Lock Down Value) starts on line 07, the amount of f’s = the value, so in the above image, the LDV value is 2
For more info regarding LDV, check out Martin C’s post (info)
|Create your NAND ImageMove cpukey.txtto…360_Multi_Builder\Data\my360Launch 360 Multi Builder again and press the number corresponding your motherboard revision.You may get a message informing you that “No fcrt.bin found in this nand.“
This is not uncommon, and is nothing to worry about, so just continue.Just for completeness, here is what it looks like if your NAND does contain fcrt.bin
Again, just press Enter to continue.
You are now given the option to create a Glitch image, or a stock NAND image (Retail MS). For the purpose of this guide, you want to choose 1
Press 1 again, choosing to build the image with DashLaunch patches included (highly recommended), and hit Enter
Now that Multi Builder has your NAND dump and CPU Key, it will use xeBuild to create your new “hacked” NAND image (nandflash.bin) and save it in 360_Multi_Builder\Data
(image – xeBuild Finished. Have a nice day)
(image – recommended flashing method)
|Flash your NANDCopy nandflash.bin and xenon.elf from 360_Multi_Builder\Datato a USB keyIf the console is still running, with XeLL on screen, insert the USB key now.XeLL-Reloaded will find xenon.elf and use it to flash nandflash.binto your NAND. (if not, turn the console off, and on again)(again, still no need to boot with the eject button at this time)Once you see “Image written, shut down now!” on your screen, turn off the console and remover the power for at least 30 seconds, and remove the USB key.
You can use this time to put the motherboard back in the cage, and reconnect your HDD, and DVD drive.
Replace the power, and boot the console. You are now running a hacked dash
If all is well, fully reassemble the console.
|Finishing UpDepending on the dashboard version you were on before you started, you may need to perform an update in order to get Avatars/Kinectworking correctly.If that is the case, put the USB key back in your PC, and delete the files from it.Now place the $systemupdate folder from the official 2.0.14699.0update, on the USB KeyIf you chose to create your NAND image with DashLaunch patches included (as you should have), then rename$systemupdate to $$ystemupdateotherwise the update wont install, because DashLaunch is configured to block updates by default.Make sure your xbox has some storage space for the update files, like a HDD or internal memory
Insert the USB key into the 360, and allow it to perform the update.
You are now ready to start installing all sorts of homebrew win, but before you do that, make backup copies of the following files, and put them somewhere safe.
Add them to a .zip/.rar file, and then email them to yourself, so that they are stored online, as well as locally.
After making your backup, delete the original files, so that you have clean working folders for any future Glitches you may do.
If your console is already Glitched and running a hacked Dashboard, and you just want to update to the latest, follow this guide, starting from the Create your NAND Image section.
HDD Folder List
Party Buffalo Drive Explorer
Thanks to blackwolf over at EMS for a large hunk of this guide, taken from here… http://www.elitemods…al-by-blackwolf and anybody else I may have nicked bits from, here and there And obviously a huge thanks to everybody involved in making all this even possible, not least of course, the legend that is gligli.
This was just compiled and edited to fit my own needs, but I thought If I padded it out a bit, it may be helpful to others who have the same TX based setup.
If there is anything I have left out, or something I have totally butchered (bad blocks section?), pull me on it, so I can fix it. Thanks.