THIS THREAD IS CURRENTLY BEING WRITTEN! I'm writing and saving in sections! That way i won't lose any work if something were to happen! Patience! Parts List (16 MB and 4 GB Trinity)Mandatory Parts: - DGX 1.0S or DGX 1.1S - Glitch chip. I will be using a Coolrunner REV. C in this tutorial. - NAND programmer. I will be using a J-R Programmer in this tutorial. - Patience!!!!!!!!! Optional Parts: - NAND-X Update Cable (COMMS cable) to monitor COMMS to get your keys faster and easier. **Requires this QSB** - Case of your favorite alcoholic beverage and a carton of smokes!! Parts List (16 MB Corona)Mandatory Parts: - DGX 1.0S or DGX 1.1S - Glitch chip. MUST have a 48.000Mhz Crystal on it (the little gold rectangle)! In this tutorial i'll be using the Coolrunner 3 Lite. - NAND programmer. I will be using a J-R Programmer in this tutorial. - Depending on your Corona type, you MAY need a POST Fix adapter! I'll explain this very soon. Optional Parts: - NAND-X Update Cable (COMMS cable) to monitor COMMS to get your keys faster and easier. Again, not mandatory. **Requires this QSB** Parts List (4GB Corona)Mandatory Parts: - DGX 1.0S or DGX 1.1S - Glitch Chip. MUST have a 48.000Mhz Crystal on it (the little gold rectangle)! In this tutorial i'll be using the Coolrunner 3 Lite. - Corona 4 GB Read/Write kit. I will be using TX's kit in this tutorial. - Depending on your Corona type, you MAY need a POST Fix adapter! I'll explain this very soon. Optional Parts: - NAND-X Update Cable (COMMS cable) to monitor COMMS to get your keys faster and easier. Again, not mandatory. **Requires this QSB Cannot be used to read or write to the NAND on a 4GB model! Only used for COMMS monitoring!** Identifying Your Motherboard (Externally) Identifying Corona NAND Version Identifying If Your Corona Requires the POST_OUT AdapterYou must remove the X-CLamp and CPU/GPU heatsink in order to find this info out. You can also refer to the picture above. However, i think it's always best to double check!! Remember, when you remove the heatsink, rule of thumb is to clean up the old thermal paste and replace it. Wiring Your NAND Programmer (Trinity)Here is an image for the Trinity's NAND Programmer wire points. Rather it's the J-R Programmer or the NAND-X, they use the same color code and points. Wiring Your Programmer (Corona 16 MB)Take a look at the picture above. Note the header numbers/letters. The short one is J2C1. The longer one is J2C3. Notice the square points? Those symbolize header pin number one. The point to the left is labled 2. So, you will read the header from top right to left. So, top right will be one, top left is two, second row right is 3 second row left is four, etc. Same for both headers. Wire your programmer like this: J2C1 Pin one Pin two Pin three Pin four Pin five (Can sometimes be a pain. You can solder this cable to ground since it's the ground cable.) J2C3 Pin five Pin six Installing Your Programmer (Corona 4 GB)You will install your QSB like the picture referenced below. You will then install the flat cable BLUE SIDE UP. The other end of that cable will be installed to the micro SD card looking adapter. Again, BLUE SIDE UP. You can then plug your adapter into the Micro SD to SD adapter. Then, you will plug it into your PC. Flip the switch to R/W for the next step. If you have one of those pesky v3 or v4 Coronas, you must bridge 3 empty resistor pads in order to enable the R/W function and to send the E and F signals to the header for use with the Coolrunner. Take a look at the image below on where to locate and which pads to bridge. ONLY BRIDGE IF THE RESISTORS ARE NOT PRESENT!!! DGX Install (NO POST_OUT ADAPTER)Follow this picture guide created by the guys on TX's forum. The same wiring method applies for both Trinity and Coronas that don't need the POST_OUT Adapter. Corona DGX Install That Need the POST_OUT AdapterYou must remove the GPU/CPU heatsink in order to install this adapter. Take reference to the image below on how to install the POST_OUT adapter. Take note. Once you solder this adapter in. Do NOT try to remove it. Now that you have your POST_OUT adapter installed, you can carry on with the DGX install as normal. When the guide comes to the POST_OUT (yellow or C wire) solder it to POST_1 on the POST fix adapter you just installed and the other end of it to the Coolrunner's C point. Reading your NAND (Non Corona 4GB)You will need a program Called J-Runner for this part. You can get it here. Boot the software you just downloaded (J-Runner). Take note, under the highlighted "Read Nand" button you will see "No. Reads" You can set that to what ever you'd like. MUST be AT LEAST 2. When you are done setting the number of times you want to dump the NAND, press "Read Nand" Another box will pop up that is labeled "Type" in the address bar. Select your console's motherboard type here. Then press OK. Your NAND should start dumping. You will hear a sound when your NAND is dumped. Remember, it will dump it more than once!!! Dumping the Corona 4GB NANDYou will also need the software J-Runner. You can find it here. Boot the software you just downloaded. You will see a toolbar at the top. We will be using the "Advanced" drop down menu for our 4GB Coronas. Once you press the "Advanced" button, click on "Corona 4GB Read/Write" Another window will pop up labeled "Drives" Here you will select your Corona's NAND. You're looking for something with the capacity of around 3.5GBs. Once you see it, you should double click that drive, then in the middle of the window select the ... button to select where to save the dumped image and what to name it. Remember, do two separate dumps! When you have your NAND location picked, press "Read." When the first dump is done, dump it one more time. Just remember to rename your NAND Dump in the middle box to something else so it doesn't write over the dump you just made. Writing the DGX.ecc to Your ConsoleUsing J-Runner, click on the "Advanced" tab and select "Write DGX." No, you are not programming the DGX. Until TX comes up with updated FW, you shouldn't try to write to the DGX. Non Corona 4GB consoles, click the "Write Nand" button. Corona 4GB consoles, when you press the "Write DGX" button, the Drives window will come up again. Select your Corona's NAND and press Write. Non 4GB Coronas will see something like this. Just press "Write Nand" that is highlighted in yellow. Highlighted in pinkish, make sure you have something like that in the source box. Just to make sure you're writing a DGX file and not your original NAND dump. If you have a 16MB Corona, it won't say Trinity of coarse. If you're using a Corona, there are two different DGX.ecc files to use. A dialog will come up asking if you want to use v2 DGX.ecc. Select YES. 4GB Corona consoles will see something like this. Check the "File" box and make sure you see something like that. If you do, press "Write." There are two different DGX.ecc files to use. A dialog will come up asking if you want to use v2 DGX.ecc. Select YES. Before You Boot!!Corona consoles (Doesn't matter the NAND size or motherboard version) DIP switch 8 MUST be flipped to the ON position Trinity consoles (Doesn't matter the NAND size) DIP switch 8 MUST be flipped to the OFF position. Power cycle your console. When the console is done being written to, unplug the power cable from the console, wait about 30 sec, then plug it back in. You man now boot your console. Take note! The DGX is a piece of **** to put it nicely. It only needs to boot ONE time to Xell to get your CPU key. So, the DGX will take FOREVER to finally glitch your console. With Trinity consoles, you will be there for a while tweaking wire lengths, etc JUST to boot one time. Trinity consoles will require patience. Having A Hard Time Booting?The wire lengths that come with the DGX (1.0S) are not really the right lengths. These will need to be tweaked. Out of the package, the CPU_RST (blue or D) wire is the standard slim length. 55cm. Use the CPU _RST wire for POST_OUT (yellow or C) to start with. Using the POST_OUT wire for CPU_RST. That will work for most Coronas. For Trinity consoles, you can try that config. However, i never had great success with it. The POST_OUT wire is the new troublesome wire on the DGX. Try using 120, 100, 70, 55, 50, 30 CM wires for POST_OUT. You can also try shorter or longer CPU_RST wires. I've had great success with the 12cm ground cable to the FT4R2 point (Picture of th FT4R2 point under the following spoiler). You can also try thicker core wire if the ground cable doesn't help. JUST NOT TOO BIG. You will rip your CPU_RST off the board that way. Also, don't forget about the DIP switches! Each one shapes the CPU_RST signal a different way! Just leave DIP 8 alone and set for your console type! Spoiler This is not my image. You only need ONE wire coming off that point. Image was taken off the TX site in a repair topic.