Methods compared
Each homebrew method targets different console revisions and asks for different hardware. Use this table to narrow down which approach fits the console on your bench, then read that method's dedicated page before starting.
| Method | Type | Glitch chip? | Best for |
|---|---|---|---|
| JTAG | Software / NAND exploit | No | Older phat consoles with the unpatched vulnerability |
| RGH 1.2 | Reset-glitch | Yes | A broad range of supported boards |
| RGH 2 | Reset-glitch | Yes | Boards where faster, more reliable glitching is wanted |
| RGH 3 | Reset-glitch | No, wiring only | Supported consoles where a simpler parts list is preferred |
| R-JTAG | Hybrid glitch + JTAG boot | Yes | Consoles needing extra boot reliability |
How to choose
- Start with the console. Identify your motherboard revision first; it rules most options in or out before any other consideration.
- Weigh the hardware. Glitch-based methods need a chip and soldering, while JTAG and RGH 3 avoid a dedicated chip.
- Value reliability. If a basic glitch is slow on your board, R-JTAG or a newer RGH revision may boot more consistently.
Whichever you pick, the overall flow is the same: identify the console, read the NAND, install the glitch or exploit, build and write the modified image, boot XeLL, and set up a dashboard.