Yesterday we inspected the Xbox 360 hypervisor, where Microsoft burned fuses so the console could remember history.

Today we inspect the successor:

the Xbox One.

For years, the Xbox One was the console scene’s locked palace.

The original Xbox was opened.

The Xbox 360 was negotiated with JTAG, DVD firmware, Reset Glitch Hack, and enough solder to qualify as urban planning.

The PlayStation 4 had WebKit and kernel surfaces.

The Switch fell to a boot ROM bug with a jig and a USB cable.

The Xbox One mostly sat there for over a decade like a concrete government building with no windows.

Then Bliss arrived.

Not a browser exploit.

Not a savegame bug.

Not “turn on Dev Mode and install RetroArch.”

A hardware fault attack against the earliest security path.

The palace did not fall to paperwork.

It fell to voltage.

I. Why Xbox One Was Different

Microsoft learned from the Xbox 360.

The Xbox 360 was not a joke, but it left enough electrical and boot-chain opportunities for attackers to build an industry out of timing, fuses, NAND dumps, and modchips.

The Xbox One was built with fewer romantic mistakes.

Layer	Xbox One strategy	Kim translation
secure boot	signed and verified boot stages	succession papers
security processor	ARM-based secure core on the AMD SoC	interior ministry
Hyper-V-style virtualization	separate host, system, and game worlds	prison blocks
key separation	secrets bound to layers and versions	passports expire
encrypted containers	XVD/XVC package discipline	sealed ration boxes
update model	old versions stop being useful	history is disposable

The key insight was disposability.

If you exploit one userland, one kernel, or one version, Microsoft does not want you to inherit the kingdom. It wants you to inherit a small room scheduled for demolition.

That is why Xbox One security lasted.

Not because there were no bugs.

Because the bugs lived in rooms with guards outside.

II. The Three-Government Console

The Xbox One did not run one simple operating system like a civilized appliance.

It ran a small federation.

Public Xbox One research describes a primary HostOS responsible for managing virtual machines, hardware drivers, and the console’s virtualization stack. The visible dashboard and Store applications run in SystemOS. Games run in a separate GameOS / ERA / GameCore world depending on generation and title model.

flowchart TB
    SP["Security Processor<br/>early trust and keys"]
    HV["Hypervisor / HostOS<br/>hardware and VM control"]
    SYS["SystemOS<br/>dashboard, apps, shell"]
    GAME["GameOS / ERA / GameCore<br/>game execution"]
    LIVE["Xbox services<br/>identity, licenses, policy"]

    SP --> HV
    HV --> SYS
    HV --> GAME
    SYS --> LIVE
    GAME --> LIVE

This is not accidental complexity.

It is a security doctrine.

If the dashboard breaks, the game partition should not automatically surrender.

If a game breaks, the host should not automatically kneel.

If an app breaks, the security processor should not even hear the noise.

The Xbox One was not “a PC under the TV.”

It was several Windows-like governments stacked inside a black plastic apartment block.

III. Dev Mode Was Not A Jailbreak

Microsoft did something clever:

it gave civilians a sanctioned basement.

Xbox Developer Mode allowed retail consoles to run UWP development applications. This was useful for hobbyists, small developers, and emulator people who wanted legal sideloading.

It also reduced pressure.

Why storm the palace when the state gives you a sandbox with paperwork?

But Dev Mode is not a jailbreak.

Thing	What it gives	What it does not give
Dev Mode	UWP app development and sideloading	full retail game control
UWP sandbox	limited app environment	arbitrary kernel ownership
Device Portal	deployment and debugging surface	keys, hypervisor, game decryption
Retail mode	normal console operation	unsigned native takeover

This distinction matters.

Running an emulator in Dev Mode is not the same as owning the console.

The state allowed a park.

It did not surrender the palace.

IV. Collateral Damage Was Real, But Not Bliss

Before Bliss, there were public Xbox One and Xbox Series research paths.

One important example was Collateral Damage, a 2024 SystemOS kernel exploit using CVE-2024-30088, with an entry path through the Game Script UWP application on vulnerable versions. The Xbox One Research Wiki lists it as code execution, patched in July 2024, with first patched system version 10.0.25398.4910.

That matters.

It proves “Xbox One had no bugs” was mythology.

But it was not the same class as a full boot-chain defeat.

Exploit class	What it means
UWP / app code execution	enter from a sandboxed app surface
SystemOS kernel exploit	compromise an OS partition layer
Hypervisor escape	attack the prison manager
boot ROM / security processor fault	attack the first clerk before the paperwork exists

Collateral Damage was a crack in a wall.

Bliss attacked the foundation.

V. The Boot Chain

Public Xbox One research describes a secure boot chain involving the southbridge, the AMD SoC security processor, streaming crypto machinery, x64 CPU boot stages, the hypervisor, HostOS, SystemOS, and game partitions.

In simplified form:

sequenceDiagram
    participant SMC as Southbridge / SMC
    participant SP as Security Processor
    participant CPU as x64 CPU
    participant SCP as Streaming Crypto Processor
    participant HV as Hypervisor
    participant Host as HostOS
    participant Sys as SystemOS
    participant Game as GameOS / ERA

    SMC->>SP: power up secure processor
    SP->>SP: run ROM and boot stages
    SP->>CPU: decrypt / load 2BL
    CPU->>SCP: load crypto firmware and key table
    CPU->>HV: load hypervisor
    CPU->>Host: load Host VBI / host.xvd
    Host->>Sys: start SystemOS VM
    Host->>Game: start game VM

The important part:

the earliest code is not the visible dashboard.

It is not SystemOS.

It is not even the x64 host.

It is the secure processor path and boot ROM logic.

Microsoft guarded the ordinary doors so well that attackers eventually had to attack the first heartbeat.

VI. Bliss: The Double Glitch

At RE//verse 2026, Markus “Doom” Gaasedelen presented Bliss, a voltage glitching attack against the Xbox One.

The public reporting describes it as a double glitch:

• one precisely timed voltage fault interferes with security-processor memory protection setup
• another hits a memory-copy/header-read path to divert execution into attacker-controlled data

This is not a casual mod menu.

This is not a teenager clicking “jailbreak.”

This is hardware fault injection.

flowchart TB
    BOOT["boot begins"]
    ROM["security processor BootROM"]
    MPU["memory protection setup"]
    GLITCH1["voltage glitch #1<br/>skip or corrupt protection setup"]
    COPY["header read / memcpy path"]
    GLITCH2["voltage glitch #2<br/>redirect execution"]
    PAYLOAD["attacker-controlled payload"]
    CONTROL["unsigned code below normal policy"]

    BOOT --> ROM --> MPU --> COPY --> CONTROL
    GLITCH1 --> MPU
    GLITCH2 --> COPY
    COPY --> PAYLOAD --> CONTROL

The joke writes itself:

the Xbox 360 had RGH, Reset Glitch Hack.

The Xbox One got VGH, Voltage Glitch Hacking.

The successor did not remove glitching.

It made the glitch need a better education.

VII. Why It Matters

Bliss matters because it attacks code in silicon.

Software updates can patch SystemOS.

Firmware updates can replace flash stages.

Hypervisor updates can change checks and mitigations.

But mask ROM is different.

If the vulnerable code is burned into the SoC, the real fix is a hardware revision or a mitigation outside the vulnerable moment.

Layer	Normal fix
app	Store update
SystemOS	system update
kernel	system update
hypervisor	system update
flash boot stage	firmware update
BootROM in silicon	new silicon, or pray around it

This is the same lesson as the Nintendo Switch BootROM, but with a higher entry fee.

Nintendo had a paperclip myth.

Microsoft required laboratory spite.

VIII. What Bliss Does Not Mean

The Ministry must prevent civilians from becoming stupid.

Bliss does not mean every Xbox One owner can now casually install Linux by breakfast.

Bliss does not mean Xbox Live is suddenly a pirate picnic.

Bliss does not mean every Xbox One S, One X, or Series console is automatically in the same state. Public reporting and research focus on original Xbox One hardware; later revisions and successors may differ.

Bliss does mean:

• the “unhackable” label is dead
• the security processor path has been publicly faulted
• boot ROM assumptions can now be studied with new access
• firmware and game preservation may improve
• Microsoft still deserves respect for making attackers wait twelve years and buy tools

This is not a weak console.

This is a strong console that eventually met physics.

IX. The Real Story (Suppressed)

Officially, Bliss is a pleasant word.

Suppressed expansion:

Bootrom Liberation by Inducing Silicon Seizure.

Microsoft called Xbox One secure.

The hackers agreed.

Then they asked:

“What if the secure processor gets dizzy?”

The first prototype reportedly used a hammer.

This was rejected because it lacked timing precision and produced too many Xbox One S-shaped political prisoners.

The second prototype used voltage.

This worked because silicon is like bureaucracy:

under normal conditions, it follows rules.

under stress, it signs the wrong document.

X. The Lesson

The Xbox One is the best kind of security story:

not a clown failure,

not a marketing lie,

but a serious architecture that forced attackers down to hardware physics.

Microsoft built layers:

• security processor
• signed boot chain
• streaming crypto
• hypervisor
• HostOS
• SystemOS
• GameOS
• disposable versions
• separated keys
• sanctioned Dev Mode sandbox

For twelve years, that was enough to keep full public compromise away.

Then Bliss attacked the place where the layers begin.

The decree:

• virtualization buys containment
• key separation buys time
• Dev Mode is not ownership
• software exploits are not boot-chain defeat
• BootROM bugs are constitutional defects
• voltage is also an API if you are sufficiently rude

The Xbox 360 taught Microsoft to fear timing.

The Xbox One taught hackers to respect Microsoft.

Then hackers taught Microsoft that even respect has a power rail.

— Kim Jong Rails, Supreme Leader of the Republic of Derails