Xbox 360:RGH/RGH2

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!

RGH 2 is an outdated method of the Reset Glitch Hack. RGH 1.2, RGH 3, and S-RGH are much quicker and are thus recommended over RGH 2. EXT_CLK is recommended for Xenon and Zephyr consoles.

RGH2 was designed for Slims, but it also works for non-Xenon Phats. It uses I2C slowdown instead of PLL slowdown, and works on any dashboard. However, it is considered more difficult to tune and less consistent than the more improved S-RGH.

• RGH2+ is on Team Xecuter’s later chip firmwares (such as CR4XL) which uses I2C slowdown from the southbridge to glitch. It is not considered to be optimal.

Equipment Needed

• A compatible glitch chip:
  • Coolrunner Rev A/B/C/D
  • CR3 Lite
  • Matrix Glitcher
  • DGX v1.0S
  • X360ACE V1/V2/V3
• 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
• J-Runner with Extras
• RGH 2 Timing files if using a Zephyr

File:5lY3TID.png

Postfix adapter diagram

(Corona Only) Postfix Adapter

On later Corona motherboards, the POST pad and trace has been hidden, 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 diagram to determine if you need the adapter or not. As shown in the 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.

Reading your NAND

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. However, the 4GB Corona requires 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. The LPT cable method is not recommended, as it's extremely slow, requires more work than other options, and cannot be used to program glitch chips.

4GB Corona

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 SD Card tools or PicoFlasher
PicoFlasher	Reads NAND in 1-8 minutes Super cheap Easy to find	You will need a programmer to program glitch chips
4GB USB Tool	Cheap	You will need a programmer to program glitch chips
SD Card Tool	*Super cheap Easy to find	You will need a programmer to program glitch chips

All Other Motherboards

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 Corona Actively supported USB-C Uses signed drivers	Most expensive flasher Can't be used for flashing Sonus Sounds
Nand-X	Reads NAND fast in 1-8 minutes One of four options for 4GB Corona One of the two options for Sonus or Slim sound programming Super cheap Easy to find Uses signed drivers	Can't easily be used to flash glitch chips
JR Programmer	*Reads NAND in 2-8 minutes Can also program RGH glitch chips	More expensive than most NAND flashers Not much cheaper than the xFlasher Does not support 4GB Coronas Requires unsigned drivers
PicoFlasher	Reads NAND in 3-10 minutes Can also program glitch chips One of the two options for Sonus or Slim sound programming Cheap Easy to find	More expensive than PicoFlasher or Matrix Does not support 4GB Coronas Requires unsigned drivers
Matrix USB NAND Flasher	Reads NAND in 7-26 minutes Super cheap	Can’t be used for programming glitch chips unless you modify it Does not support 4GB Coronas Requires unsigned drivers
LPT Cable	Cheap Doesn't require unsigned drivers	Requires PC with a native parallel port and more equipment More difficult Can’t be used for programming glitch chips Takes 30-150 minutes to read NANDs

Glitch Chip Installation

Glitch Chip Pinouts

Coolrunner Rev C/D

• B - STBY_CLK (only if not using oscillator)
• C - POST
• D - RST
• E - i2C_SCL
• F - i2C_SDA

CR3 Lite

• B - STBY_CLK (only if not using oscillator)
• C - POST
• D - RST
• E - i2C_SCL
• F - i2C_SDA

Matrix

• A - RST
• B - POST
• C - STBY_CLK (only if not using oscillator)
  • 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 (10K ohm resistor recommended on Slim)

1.8v on an Ace V3

X360ACE (V1/V2/V3), DGX

• C - POST
• D - RST
• E - i2C_SCL
• F - i2C_SDA
• Remember to remove the diode and connect 1.8V on Phat

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 and select the click the arrow next to the "Program" button, then click "Select File" to flash your selected RGH 2 timing file.
3. When complete, unplug the cable from the glitch chip.
   • Coolrunner: Set the switch back to "NOR".

Decrypting the NAND

1. Connect Ethernet and power on the console. The glitch chip should blink once or more times, and then the console should start into XeLL RELOADED.
2. Once XeLL finishes, it will display your CPU key and some other info. There is also an IP address.
3. Enter the IP address into the box on the lower right of J-Runner and click "Get CPU Key". J-Runner will pull the info from the box, and decrypt the NANDs automatically.

Writing New NAND Image

1. Power down the console, and connect your programmer to the motherboard.
   • If you are using an xFlasher, ensure the switch is set to eMMC (for 4GB Corona) or SPI (for all other motherboards).
2. 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 programmer when the process completes.
6. Boot the console several times and ensure it boots consistently. If not, make sure your wiring is clean and neat and avoids noisy area. Run the wires near the X-Clamps for best results.
7. Tune boot times if neccessary.
8. Continue in the Cleaning Up section.

Tuning Boot Times

As the glitch chip pulses, a green debug light will flash a pattern. Using this pattern, we can know roughly how to adjust the tuning. Let's start with some examples. The ideal is slightly "below" the edge of Long/Short, closer to Short. You want to see more Short than Long cycles.

If you get good light behavior, mostly Short but also Long sometimes, but the console still does not boot well, try to recreate this scenerio with other timing/pulse length. If using Corona with Xecuter Postfix V2, try moving wire to a bigger number pad. This will adjust for you the length of POST.

• 2 Short Blinks, then Short
  • .....##...##...................##............
  • This means that the checks were passed, but the console failed to start.
  • Probably the timing is too low, or the pulse length is too large.

• 2 Short Blinks, then Long
  • .....##...##...................##############
  • This means that the checks failed.
  • Probably the timing is too high, or the pulse length is too small.

• 4 Short Blinks, then Long
  • .....##...##...................##...##...................##############
  • This means there is a problem with RST wiring problem causing pulse length to be very big. Try to use alternate points or longer wire.

• No Light Blinks or Always On
  • .............................................
  • #############################################
  • This means your wiring is bad, or the timing file was not written sucessfully.

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.

Installing XeXMenu

1. Plug a flash drive into your Xbox 360 and navigate to Console Settings > Storage. Select the flash drive and allow it to format the flash drive as a system drive.
2. Extract the CODE9999 folder from the XeXMenu 1.2 rar to your Desktop.
3. Plug the flash drive into your PC. Open Xplorer360 and select Drive > Open > Harddrive or Memcard. On the left-hand side, select Partition 3, then right-click the Content folder, select "New Folder", 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.