Xbox 360:RGH/RGH1.2

The steps on this page are considered risky for your console, as there is a chance you can brick it. Please have someone else mod your console if you are not experienced in soldering!

RGH1.2 combines RGH1-like PLL slowdown with Glitch2 images to allow reliable glitching of Falcon/Jasper consoles with split CB (post 14699 kernel). RGH1.2 V2 ports this hack to Trinity/Corona consoles as well as fixing a few issues on Jaspers.

Equipment Needed

• A compatible glitch chip:
  • Coolrunner Rev A/B/C/D
  • CR3 Lite
  • Matrix Glitcher
  • Squirt BGA/Reloaded
  • X360ACE V1/V2/V3
  • X360ACE V3+/V4/V5 (Trinity/Corona only)
  • DGX
• A PC running Windows Vista or later
• A soldering iron, solder, flux, and Isopropyl alcohol with cotton swabs
  • Specific recommendatons can be found on this page
• A NAND and glitch chip programmer:
  • xFlasher 360
  • NAND-X
  • JR-Programmer
  • Modified Matrix Flasher
• A NAND Backup with XeLL written to the console
  • Standard NAND
  • 4GB Corona
• J-Runner with Extras (Includes RGH1.2 V2 Matrix/Coolrunner Timings)
• RGH1.2 V2 Timing Files (X360ACE/Squirt chips only)

Reading your NAND

4 GB Corona/Waitsburg/Stingray

4 GB Xbox 360 S/E SKUs made after mid 2011 use an MMC NAND (Corona) or eMMC chip (Waitsburg/Stingray/Winchester) and require different tools to dump and flash the NAND compared to the 16/64/256/512 MB NAND chips. These 4 GB consoles require that you use an xFlasher 360, PicoFlasher, Element18592's 4GB USB tool, or an SD card tool. Consider the pros and cons below and choose the method that’s right for you.

A guide on how to dump and write to a 4 GB NAND can be found here.

Device	Pros	Cons
xFlasher 360	Reads NAND fast in 40 seconds to 4 minutes Can also program glitch chips Actively supported USB-C	More expensive than other options
PicoFlasher	Reads NAND in 1-8 minutes Can also program glitch chips with DirtyJtag and the DirtyPico360 J-Runner Fork Super cheap Easy to find	Usually has inconsistent dumping behavior
4GB USB Tool	Reads NAND fast in 40 seconds to 4 minutes (same as xFlasher) Cheap Comes with a header for the NAND pads, making future NAND reading easier	You will need a programmer to flash glitch chips
SD Card Tool (any brand)	Super cheap Easy to find Easy to DIY	You will need a dedicated programmer to flash glitch chips Sometimes has inconsistent compatibility with SD card readers

All Other NAND Types

There are a few different tools for reading your NAND chip: xFlasher 360, Nand-X, JR Programmer, Matrix USB NAND Flasher, PicoFlasher, various SD card tools, or a LPT cable. Consider the pros and cons below and choose the method that’s right for you. An LPT cable is not recommended as it's extremely slow, requires more work than other options, and cannot be used to program glitch chips.

A guide on how to dump and write to a standard NAND can be found here.

Device	Pros	Cons
xFlasher 360	Reads NAND fast in 40 seconds to 4 minutes Can also program glitch chips One of four options for 4GB NANDs Actively supported USB-C	Most expensive flasher Not sold on common marketplaces like Amazon or AliExpress Can't be used for flashing Sonus Sounds
PicoFlasher	Reads NAND fast in 1-8 minutes One of four options for 4GB NANDs One of the two options for Sonus flashing Super cheap Easy to find Can flash glitch chips with this J-Runner Fork	Due to how the currently available PicoFlasher firmware is programmed, it often has many bugs with getting consistently good non-corrupt NAND dumps or being detected by J-Runner. Can sometimes have spotty reliability on Xbox 360 motherboards due to their SPI and eMMC logic being up to 5v, whereas the Pico uses 3.3v.
JR Programmer	Reads NAND in 3-10 minutes Can also program glitch chips One of the two options for Sonus flashing Cheap Easy to find	More expensive and less common than PicoFlasher Does not support 4GB NANDs
Nand-X	Reads NAND in 2-8 minutes Can also program RGH glitch chips	More expensive than most NAND flashers Does not support 4GB NANDs Can't be used for flashing Sonus Sounds
Matrix USB NAND Flasher	Cheap	Can’t be used for programming glitch chips unless you modify it Does not support 4GB NANDs Requires unsigned drivers Reads NAND in 7-26 minutes, which is quite a bit slower than most options Can't be used for flashing Sonus Sounds
LPT Cable	Cheap	Requires PC with a native parallel port and more equipment More difficult Does not support 4GB NANDs Can’t be used for programming glitch chips Can't be used for Sonus flashing Takes 30-150 minutes to read NANDs

Programming the Glitch Chip

1. Plug the cable from your programmer into the chip programmer.
   • If you are using an xFlasher, ensure the switch is set to SPI.
   • CoolRunner: Slide switch to "PRG".
2. Open J-Runner with Extras. Click "Program Timing File" in the upper left, select the RGH 1.2 tab, and the relevant radio button for RGH 1.2.
   • You can use the timing assistant in the bottom left to auto select a safe timing for your motherboard revision.
3. When complete, unplug the cable from the glitch chip.
   • Coolrunner: Set the switch back to "NOR".

X360ACE V3+/V4/V5

• xFlasher or other Gowin compatible programmer required in order to program these chips
• Programming Instructions

Waitsburg/Stingray Specific Instructions

On Waitsburg and Stingray motherboards, the trace connecting the CPU's POST to the POST pad on the bottom of the motherboard has been removed, so you need to use a postfix adapter to be able to attach a pogo pin to the POST connection underneath the CPU. You can use the following image to determine if you need the adapter or not by removing the heatsink:

You can also identify if you have a Waitsburg motherboard instead of a Corona by looking for the part number of X862605 on the bottom left of the PCB. Generally, Xbox 360 S consoles manufactured in 2012 will be Waitsburgs and need postfix adapters for RGH. Every Stingray will also need a postfix adapter with RGH.

As shown in following diagram, you can install it by carefully sliding the larger piece of the adapter onto the left side of the CPU (when looking at the CPU from a readable position). Gently press the PCB inward toward the CPU to depress the pogo pin, and slide the smaller PCB part over the other side of the CPU, interlocking the two PCBs together. Solder the four anchor points on the edges of the postfix adapter to prevent it from coming loose.

Glitch Chip Installation

Glitch Chip Pinouts

Note: RGH 1.2 on Corona consoles requires a glich chip with a built in oscillator. STBY_CLK will be unused when using a chip's oscillator.

Coolrunner Rev A/B/C/D

• B - STBY_CLK (only if not using oscillator on Phat or Trinity)
  • If you have a Rev D, the built in oscillator can be easily disabled if this resistor is removed instead of removing the entire oscillator.
• C - POST
• D - RST
• A - PLL (5-10K ohm resistor recommended on Slim)

CR3 Lite

• A - PLL (5-10K ohm resistor recommended on Slim)
• B - STBY_CLK (only if not using oscillator Phat or Trinity)
• C - POST
• D - RST

Matrix Glitcher

• A - RST
• B - POST
• C - STBY_CLK (only if not using oscillator Phat or Trinity)
  • If you have a Matrix that comes with an oscillator, it can be easily disabled if this resistor is removed instead of removing the entire oscillator.
• F - PLL (5-10K ohm resistor recommended on Slim)

Squirt

• (Phat) Squirt BGA 1.2: Disable the onboard 670pf and/or 480pf caps by removing R7 and R8
• (Phat) Squirt Reloaded 2.X: remove R2 and connect STBY_CLK
• (Slim) Squirt Reloaded 2.X: remove R2 and connect STBY_CLK or remove 100 MHz and add 48 MHz oscillator
• (Slim) Use SCL pad for PLL
• Pinout follows written labels
• Don't use POST or RST tuners

1.8v on an Ace V3

X360ACE (V1/V2/V3/V3+), DGX

• C - POST
• D - RST
• E - STBY_CLK (Only when using 48 MHz timings on Phat)
• F - PLL (5-10K ohm resistor recommended on Slim, 22K ohm resistor required on Phat)
• Remember to remove the diode and connect 1.8V on Phat

X360ACE V4/V5

• A - RST
• B - POST
• C1 - CPU_CLK_DP
• C2 - CPU_CLK_DN
• D - PLL (5-10K ohm resistor recommended on Slim)

Glitch Chip Diagrams

Phat

Coolrunner Rev A/B/C/D

CR3 Lite

Matrix Glitcher

Squirt

X360ACE (V1/V2/V3), DGX

Slim

Matrix Glitcher (Trinity)

Matrix Glitcher (Corona)

Testing the Console

Once you've finished soldering, clean up any flux with isopropyl alcohol and cotton swabs. Partially re-assemble your Xbox 360, ensuring that:

• Heatsinks are attached (If they were removed for some reason)
• Fan(s) are in place and plugged in (On a phat console, the fans can be angled on top of the heatsinks to cool them for testing)
• The RF board is plugged into the front of the console
• An A/V or HDMI cable is plugged into the Xbox 360 and into a TV or monitor
• A power brick is plugged in to both the wall and Xbox 360
• (Optional) An ethernet cable is plugged into the Xbox 360 and a LAN (e.g. a switch, router, or directly to a PC)

Turn on your console, and it should boot into XeLL RELOADED within a minute. If you don't have an ethernet cable connected, write down (and/or take a picture of) the "CPU Key" listed on screen. If the console doesn't boot into XeLL, check all previous steps and double check your wiring accuracy and quality.

Decrypting the NAND

Once you have successfully obtained your CPU key, we can build an XeBuild image, which is a modified NAND built specifically for your console.

• If you want to use J-Runner with the console connected to LAN to get the CPU key, enter the IP address XeLL gives you into the lower right of the app. You can then click Get CPU Key and XeLL will automatically decrypt the retail NAND dump you backed up earlier.
• If you want to use XeLL's web page to get the CPU key, enter the Xbox's IP address in your preferred web browser. You will see information about the console, and the CPU key can be easily copy and pasted from this web page.
• If you didn't have access to an ethernet cable to plug the Xbox into a PC or LAN, you can manually type the CPU key into J-Runner in order to decrypt your original NAND dump.

Writing New NAND Image (NAND Flasher)

1. Power down the console, and connect your programmer to the motherboard.
   • If you are using an xFlasher, ensure the switch is set to SPI.
2. Open J-Runner and select ... next to the Load Source field and select one of your original NAND dumps if not already selected. In the upper right of J-Runner, ensure the Glitch2 radio button is selected.
3. Click "Create XeBuild Image". This will take a few moments.
4. Click "Write NAND".
5. Disconnect your NAND programmer from the console's motherboard when the process completes.
6. Check if the console boots to the Microsoft dashboard. If it successfully boots to the dashboard, it is an indication that you've successfully hacked your console.
7. Boot the console several times and ensure it boots consistently. If not, make sure your wiring is clean and neat and avoids noisy areas. Run the wires near the X-Clamps for best results.
8. Tune boot times if necessary.
9. Continue in the Cleaning Up section.

Writing a New NAND Image (XeLL)

4 GB Corona varients do not support currently support NAND flashing through XeLL. If XeLL is the only thing flashed to the NAND, it is required to use a NAND flasher.

1. Open J-Runner and select ... next to the Load Source field and select your nanddump1.bin or nanddump2.bin if not already selected. In the upper right corner of the window, select the dashboard version you chose for the patched dump that you wrote to the motherboard and make sure that the Glitch2 radio button is selected.
2. Click "Create XeBuild Image". This will take a few moments.
3. Copy updflash.bin to a FAT32 formatted USB storage device and plug it into your powered-off console.
4. Turn on your console. It will boot into XeLL and begin flashing your NAND. Once it has finished, it will power off your console.
5. Turn it back on, and it should boot to the Microsoft dashboard, which is an indication that you've successfully hacked your console.
6. Boot the console several times and ensure it boots consistently. If not, make sure your wiring is clean and neat and avoids noisy areas. Run the wires near the X-Clamps for best results.
7. Tune boot times if necessary.
8. Continue in the Cleaning Up section.

Tuning Boot Times

Jasper Consoles

• If the console does not glitch reliably even after tuning the value, add a 68nf-100nf capacitor (ex: 683 cap or SMD cap) from PLL to GND.
• Onboard 100nf on Coolrunner Rev-C may be used by bridging CAP.
• Onboard 100nf on Squirt Reloaded 2.X may be used by bridging J5.
• If adding a cap, PLL will be more sensitive to noise. If you have strange blinking, be sure that your wire is routed away from clock signals.
• For X360ACE/DGX make sure the capacitor is after the 22K Ohm resistor.

Tuning Glitch Chip Timings (Phat)

Start at the top of the recommended range (noted in J-Runner's timing assistant and commented in the extra timings folders) and work down until you get good boots. On chips with crystals, the optimal timing will depend on the crystal (how close it is to its rated frequency)

• If the light stays on at the end of a cycle:
  • This means that the checks were passed, but the console failed to start
  • The timing is probably too low, or the pulse length is too large

• If the light goes off at the end of a cycle but doesn't boot:
  • This means that the checks failed
  • the timing is too high, or the pulse length is too small

Note: The debug light behavior may be slightly misleading due to using POST_OUT bit 0.

Tuning Glitch Chip Timings (Slim)

Start at the top of the recommended range (noted in J-Runner's timing assistant and commented in the extra timings folders) and work down until you get good boots

On chips with crystals, the optimal timing will depend on the crystal (how close it is to its rated frequency)

• 2 Short Blinks, then Short
  • .....##...##...................##............
  • This means that the checks were passed, but the console failed to start
  • The timing is probably too low

• 2 Short Blinks, then Long
  • .....##...##...................##############
  • If the light stays on at the end of a cycle:
    • This means that the checks failed
    • The timing is probably too high or far too low

Cleaning Up

Remove your NAND programmer wires and clean the points. Clean all flux off the board, allow it to dry, and test it once more before re-assembling.

You may want to leave your Xbox 360 disassembled so that you can disable the eFuse-blowing circuit so you can't accidentally install official updates on your console.

Installing XeXMenu

1. Plug a flash drive into your Xbox 360 and navigate to Console Settings > Storage. Select the flash drive and allow the console to format the flash drive.
2. Extract the CODE9999 folder from XeXMenu 1.2 rar to your Desktop.
3. Plug the flash drive into your PC. Create a new folder on the flash drive and name it 0000000000000000 (16 zeroes). Open the new folder, then drag the CODE9999 folder into it.
4. Select Drive > Close, then close Xplorer360. Safely eject your flash drive and plug it into your Xbox 360. Navigate to the Demos section of your dashboard, and it should list XeXMenu there. Select it to launch it.
   • You can install XeXMenu to your hard drive by going to Console Settings > Storage, and copying it from your flash drive to the hard drive.

From here, you can install any homebrew or mods that you want. See this page for a list of recommended modifications and applications to install.