Source: It took me nine years to hack my Xbox 360, by Kennedn
The Xbox 360 checks a Microsoft signature before it boots. The reset glitch does not break the check; it makes the CPU run one instruction wrong at the right moment. Kennedn bought the chip for it in 2017 and finished the job in 2026.
Microsoft learned from the original Xbox. Software attacks that try to run unsigned code on the 360 mostly don’t work.
The first boot stage cannot be rewritten. It is the root of trust.
1BL reads the next bootloader stage, called CB.
CB must be signed by Microsoft. Without Microsoft’s keys there is no real way to take over the boot.
The lock is sound, so the attack goes after something more basic: a CPU behaves predictably only under stable energy conditions.
A reset pulse during the check turns “refuse” into “run”.
Researchers toggled the CPU reset line very briefly. Instead of resetting, the CPU executed its current instruction incorrectly. Timed to the signature check, the mr (move register) instruction ignores the value it should move and writes a 0 into its destination register. That gives arbitrary code execution.
| Case | Lesson | Rule now |
|---|---|---|
| Xbox 360 | A correct signature check fell to a timed reset pulse. | A secure-boot chain is only as strong as its power and timing. |
| ESP32 v3, 2024 | A single electromagnetic glitch bypassed Secure Boot and Flash Encryption on a chip with fault-injection countermeasures. | Countermeasures need testing against real glitches; hardware flaws cannot be patched. |
| Raspberry Pi Pico | PIO blocks at 133 MHz time to about 7.5 ns. | Assume attackers own cheap, precise glitch tooling. |
Kennedn: It took me nine years to hack my Xbox 360.
Free60: Xbox 360 boot process.
Rodrigo Copetti: Xbox 360 architecture, the glitcher.
Delvaux, Mune, Romero, Timmers: Breaking Espressif’s ESP32 V3 (USENIX WOOT 2024).
Sources: pulse length, the mr glitch, 1BL/CB, 2017 and 2026 dates, Pico timing from Kennedn’s post; ESP32 v3 from the USENIX WOOT 2024 paper page.