Xbox 360:RGH/RGH1.2: Difference between revisions

From ConsoleMods Wiki
Jump to navigation Jump to search
mNo edit summary
Line 152: Line 152:
Start at the top of the recommended range (noted in J-Runner's timing assistant) 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)
Start at the top of the recommended range (noted in J-Runner's timing assistant) 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:
* If the light stays on at the end of a cycle:
* This means that the checks were passed, but the console failed to start
** 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
** Probably the timing is too low, or the pulse length is too large


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


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

Revision as of 05:11, 14 September 2023

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

Glitch Chip Installation

PLL Repair on a Phat motherboard (required if bottom pad is damaged). Image credit to TheLazyITGuy.
1.8v on an Ace V3

Motherboard Points

Phat

Slim (Trinity)

Slim or E (Corona/Waitsburg/Stingray)

Glitch Chip Pinouts

Coolrunner Rev A/B/C/D

  • A - PLL
  • B - STBY_CLK (only if not using oscillator)
  • C - POST
  • D - RST

CR3 Lite

  • A - PLL
  • B - STBY_CLK (only if not using oscillator)
  • C - POST
  • D - RST

Matrix Glitcher

  • A - RST
  • B - POST
  • C - STBY_CLK (only if not using oscillator)
  • F - PLL (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

Coolrunner Rev A/B/C/D

  • B - STBY_CLK (only if not using oscillator)
  • C - POST
  • D - RST
  • E - PLL (10K ohm resistor recommended on Slim)

CR3 Lite

  • B - STBY_CLK (only if not using oscillator)
  • C - POST
  • D - RST
  • E - PLL (10K ohm resistor recommended on Slim)

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

  • C - POST
  • D - RST
  • E - STBY_CLK (only if not using oscillator version)
  • F - PLL (22K ohm resistor required on Phat, 10K ohm resistor recommended on Slim)
  • 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 (10K ohm resistor required 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 (Corona)

Matrix Glitcher (Trinity)

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 your console’s 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. Click "Program". When complete, unplug the cable from the glitch chip.
    • Coolrunner: Set the switch back to "NOR".

X360ACE V3+/V4/V5

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 SPI.
  2. In the upper right of J-Runner, ensure the Glitch2 radio button is selected.
    • Enable SMC+ for better boot times.
  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 glitch chip timings if necessary.
  8. Return to the RGH main page and continue in the Cleaning Up section.

Tuning Boot Times

Jasper Consoles

  • If the console does not glitch reliably even after tuning the value, add 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

Start at the top of the recommended range (noted in J-Runner's timing assistant) 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
    • Probably the timing is 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
    • Probably 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.