Xbox 360:RGH: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Requirements: upd file name) |
||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category: | [[Category:Xbox 360]] | ||
{{Warning|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!}} | {{Warning|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!}} | ||
Reset Glitch Hack (RGH) is a hardware modification which allows you to run unsigned code, mods, game backups, and homebrew. The hack relies on a vulnerability in the hardware found by GliGli that is triggered by sending a reset pulse to the processor at a specific moment, resulting in a power glitch that causes a bootloader hash check to return "valid" no matter what you have flashed in place of the stock bootloader. The timing of when and how long the pulse should be sent is dependent on the console and it may take some tweaking until it "glitches" and boots. | Reset Glitch Hack (RGH) is a hardware modification which allows you to run unsigned code, mods, game backups, and homebrew. The hack relies on a vulnerability in the hardware found by GliGli that is triggered by sending a reset pulse to the processor at a specific moment, resulting in a power glitch that causes a bootloader hash check to return "valid" no matter what you have flashed in place of the stock bootloader. The timing of when and how long the pulse should be sent is dependent on the console and it may take some tweaking until it "glitches" and boots. | ||
| Line 5: | Line 5: | ||
The RGH variants are as follows: | The RGH variants are as follows: | ||
* RGH1 is | * RGH1 is compatible with Phat consoles on dashboard 14699 or lower. It uses CPU_PLL_BYPASS to slow down the CPU by 128x in order to precisely power glitch during a hash check on a bootloader. | ||
* RGH2 is for Slims (but also works for Non-Xenon | * RGH2 is for Slims (but also works for Non-Xenon Phats), which uses I2C slowdown instead of PLL slowdown, and works on any dashboard. However, it is considered more difficult to tune, and less consistent. | ||
** RGH2+ is the same as RGH2, except that the slowdown is sent by the southbridge, instead of the glitch chip. The glitch chip asserts a remapped GPIO pin to tell the southbridge when to send slowdown/speedup. It is exclusive to some Team Xecuter chips such as the CR4XL. | ** RGH2+ is the same as RGH2, except that the slowdown is sent by the southbridge, instead of the glitch chip. The glitch chip asserts a remapped GPIO pin to tell the southbridge when to send slowdown/speedup. It is exclusive to some Team Xecuter chips such as the CR4XL. | ||
* RGH1.2 combines RGH1-like PLL slowdown with | * RGH1.2 combines RGH1-like PLL slowdown with Glitch2 images to allow reliable glitching of Falcon/Jasper consoles with split CB (post 14699 kernel) and works on any dashboard. | ||
** RGH1.2 V2 ports this hack to Slim consoles as well as fixing a few issues on Jaspers. | ** RGH1.2 V2 ports this hack to Slim consoles as well as fixing a few issues on Jaspers. It is also tuned better than the original RGH 1, thus being preferrable. | ||
* S-RGH (Speeded-Up RGH) is a tweaked and better version of RGH2 which is far more consistent and quick. | * S-RGH (Speeded-Up RGH) is a tweaked and better version of RGH2 which is far more consistent and quick. | ||
** Muffin RGH is '''not recommended''' | ** Project Muffin is similar to S-RGH, but i2C slowdown is handled by the south bridge instead of the glitch chip. '''It is not recommended''', as it is essentially a less consistent method of glitching and does not boot as fast or consistently as S-RGH or Mufas. | ||
* EXT_CLK is similar to | ** Project Mufas is essentially a significantly tweaked and better version of Muffin to have more optimized and more reliable glitching. | ||
* RGH3 is the newest RGH variant, and the first to work without a glitch chip by using the SMC to do the glitching instead. | * EXT_CLK is similar to RGH 1.2, but uses the EXT_CLK_EN point instead of CPU_PLL_BYPASS to slow the CPU by roughly 10.6x. It is the best method for Xenon and Zephyr boards that have PLL-crash issues. | ||
* RGH3 is the newest RGH variant, and the first to work without a glitch chip by using the SMC in the south bridge to do the glitching instead. Works with Falcon/Jasper Phats and Slims, however it appears to be more reliable with Slims. | |||
==Requirements== | ==Requirements== | ||
Below are the requirements to RGH your Xbox 360. It’s recommended to read ahead and choose the NAND reading method and glitch chip specific wiring method that’s right for you, as you will need a NAND programmer and potentially more equipment depending on which methods you choose. | Below are the minimum requirements to RGH your Xbox 360. It’s recommended to read ahead and choose the NAND reading method and glitch chip specific wiring method that’s right for you, as you will need a NAND programmer and potentially more equipment depending on which methods you choose. | ||
# Be experienced in soldering. The Xbox 360 is not a good place to learn to solder. Regardless of which reading method you choose, you will need a soldering iron, solder, and | # Be experienced in soldering. The Xbox 360 is not a good place to learn to solder. Regardless of which reading method you choose, you will need a soldering iron, solder, flux, and 28 AWG or 30 AWG wire (Solid core preferred). [[Recommended Soldering Equipment|Specific recommendatons can be found on this page]]. | ||
# Determine your motherboard model. All models are compatible except the Winchester motherboard. You can use [https:// | # Determine your motherboard model. All models are compatible except the Winchester motherboard. You can use [https://octal450.github.io/identify/ Octal’s Identification Wizard] or use the methods mentioned on the [[Xbox 360:Getting Started|Getting Started]] page to determine your model . | ||
#* Corona: Determine if | #* Corona: Determine if 16 MB or 4 GB NAND model by turning on the console, navigating to System Settings > Storage, and checking whether the onboard storage unit is 16MB or 4GB. Also determine if you need to buy a postfix adapter using [[:File:Full Postfix Guide.png|this diagram]]. | ||
# Use [[Xbox_360:Exploit Chart|the recommended exploit chart]] to determine what RGH version is best for your console. | # Use [[Xbox_360:Exploit Chart|the recommended exploit chart]] to determine what RGH version is best for your console. | ||
==Reading your NAND== | ==Reading your NAND== | ||
===4 GB Corona/Waitsburg/Stingray=== | |||
{{Xbox 360 eMMC Flashers}} | |||
=== | ===All Other NAND Types=== | ||
{{Xbox 360 NAND Flashers}} | |||
== | ==RGH Methods== | ||
===[[Xbox 360:RGH/RGH1|RGH1]]=== | |||
==RGH | === [[Xbox 360:RGH/RGH1.2|RGH1.2]] === | ||
=== [[Xbox_360:RGH/ | ===[[Xbox_360:RGH/RGH2|RGH2]]=== | ||
=== [[Xbox_360:RGH/ | ===[[Xbox_360:RGH/S-RGH|S-RGH]]=== | ||
=== [[ | ===[[Xbox 360:RGH/Mufas|Project Mufas]]=== | ||
=== [[Xbox_360:RGH/ | ===[[Xbox_360:RGH/EXT_CLK|EXT_CLK]]=== | ||
===[[Xbox_360:RGH/RGH3|RGH3]]=== | |||
=== [[Xbox_360:RGH/RGH3|RGH3 | |||
Latest revision as of 19:00, 20 October 2024
 | 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! |
Reset Glitch Hack (RGH) is a hardware modification which allows you to run unsigned code, mods, game backups, and homebrew. The hack relies on a vulnerability in the hardware found by GliGli that is triggered by sending a reset pulse to the processor at a specific moment, resulting in a power glitch that causes a bootloader hash check to return "valid" no matter what you have flashed in place of the stock bootloader. The timing of when and how long the pulse should be sent is dependent on the console and it may take some tweaking until it "glitches" and boots.
The RGH variants are as follows:
- RGH1 is compatible with Phat consoles on dashboard 14699 or lower. It uses CPU_PLL_BYPASS to slow down the CPU by 128x in order to precisely power glitch during a hash check on a bootloader.
- RGH2 is for Slims (but also works for Non-Xenon Phats), which uses I2C slowdown instead of PLL slowdown, and works on any dashboard. However, it is considered more difficult to tune, and less consistent.
- RGH2+ is the same as RGH2, except that the slowdown is sent by the southbridge, instead of the glitch chip. The glitch chip asserts a remapped GPIO pin to tell the southbridge when to send slowdown/speedup. It is exclusive to some Team Xecuter chips such as the CR4XL.
- RGH1.2 combines RGH1-like PLL slowdown with Glitch2 images to allow reliable glitching of Falcon/Jasper consoles with split CB (post 14699 kernel) and works on any dashboard.
- RGH1.2 V2 ports this hack to Slim consoles as well as fixing a few issues on Jaspers. It is also tuned better than the original RGH 1, thus being preferrable.
- S-RGH (Speeded-Up RGH) is a tweaked and better version of RGH2 which is far more consistent and quick.
- Project Muffin is similar to S-RGH, but i2C slowdown is handled by the south bridge instead of the glitch chip. It is not recommended, as it is essentially a less consistent method of glitching and does not boot as fast or consistently as S-RGH or Mufas.
- Project Mufas is essentially a significantly tweaked and better version of Muffin to have more optimized and more reliable glitching.
- EXT_CLK is similar to RGH 1.2, but uses the EXT_CLK_EN point instead of CPU_PLL_BYPASS to slow the CPU by roughly 10.6x. It is the best method for Xenon and Zephyr boards that have PLL-crash issues.
- RGH3 is the newest RGH variant, and the first to work without a glitch chip by using the SMC in the south bridge to do the glitching instead. Works with Falcon/Jasper Phats and Slims, however it appears to be more reliable with Slims.
Requirements
Below are the minimum requirements to RGH your Xbox 360. It’s recommended to read ahead and choose the NAND reading method and glitch chip specific wiring method that’s right for you, as you will need a NAND programmer and potentially more equipment depending on which methods you choose.
- Be experienced in soldering. The Xbox 360 is not a good place to learn to solder. Regardless of which reading method you choose, you will need a soldering iron, solder, flux, and 28 AWG or 30 AWG wire (Solid core preferred). Specific recommendatons can be found on this page.
- Determine your motherboard model. All models are compatible except the Winchester motherboard. You can use Octal’s Identification Wizard or use the methods mentioned on the Getting Started page to determine your model .
- Corona: Determine if 16 MB or 4 GB NAND model by turning on the console, navigating to System Settings > Storage, and checking whether the onboard storage unit is 16MB or 4GB. Also determine if you need to buy a postfix adapter using this diagram.
- Use the recommended exploit chart to determine what RGH version is best for your console.
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 |
|
|
| PicoFlasher |
|
|
| 4GB USB Tool |
|
|
| SD Card Tool (any brand) |
|
|
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 |
|
|
| PicoFlasher |
|
|
| JR Programmer |
|
|
| Nand-X |
|
|
| Matrix USB NAND Flasher |
|
|
| LPT Cable |
|
|