Every iPhone performs a security check before it shows you anything at all. Before the Apple logo finishes drawing, before the lock screen appears, the phone has already verified a chain of signed code, stage by stage, from silicon to operating system. If any link in that chain fails, the phone refuses to boot. That chain is why Calif’s October 16 demo mattered so much: the jailbreak did not just reach the kernel, it came back after a full reboot, which means it survived the very checks designed to stop exactly that.
Understanding the chain is the key to understanding why an untethered jailbreak is rare, why most jailbreaks are not, and why iOS 27.2, expected October 26, is the update that decides whether Calif’s chain still works. We explained the tethered, semi-tethered, and untethered distinction when the demo happened. This is the machinery underneath it.
The chain starts in silicon that cannot be rewritten
The first link is the Boot ROM, code burned into the chip during manufacturing. It cannot be updated, patched, or replaced, which is precisely the point. The Boot ROM holds Apple’s root cryptographic key, and its only job is to verify the signature of the next stage before running it. A flaw here would be unpatchable, which is why Boot ROM exploits, when they appear, are so prized and so rare. There is no public evidence Calif used one.
Each stage then verifies the next. The Boot ROM checks the Low-Level Bootloader, which checks iBoot, which checks the kernel and the device tree. At every step, the code must carry a valid Apple signature, or the boot stops. This is called the chain of trust, and it is enforced in hardware at the start and in software after that. Breaking one link is not enough. To own the boot process, an attacker needs a flaw that lets unsigned or modified code pass a check, or a way to skip a check entirely.
A second guardian watches from a separate chip
Alongside the main chain sits the Secure Enclave, a separate processor with its own boot ROM and its own signed firmware. It guards encryption keys, biometric data, and payment credentials, and it refuses to release them to code it does not trust. Even a jailbreak that reaches the main kernel does not automatically get the Secure Enclave’s secrets. That separation is why a rooted phone is not the same as a fully compromised phone, and why Apple can keep some protections intact even when the main system is owned.
Two more defenses sit on top. Pointer Authentication Codes, or PAC, use cryptographic signatures on pointers in memory, so corrupting a pointer to hijack control flow fails unless the attacker can forge a valid signature. The Secure Page Table Monitor, SPTM, guards the kernel’s own page tables, making it harder for an exploit to quietly rewrite kernel memory. A modern jailbreak chain typically needs several bugs working together: one to escape the app sandbox, one to reach the kernel, and others to defeat PAC, SPTM, and the boot checks.
Why most jailbreaks die at reboot, and this one did not
Here is the difference that makes “untethered” special. A kernel exploit lives in memory. Turn the phone off, and it is gone. Tethered and semi-tethered jailbreaks accept that: after every restart, the user must re-run the exploit, usually from a computer or an app, to restore the jailbroken state. The phone’s boot chain is never beaten. It is simply bypassed after boot, again and again.
An untethered jailbreak survives because something persists across the reboot. That usually means the chain found a flaw in a boot stage that runs before the kernel, or a way to make the boot process load modified code it trusts. In the Paris demo, the sequence was public and specific: the iPhone 18 Pro rebooted, reached the lock screen, was unlocked with the passcode, and the jailbreak returned on its own, followed by a root shell over SSH. That reboot is what made the demo historic, the first publicly shown untethered jailbreak since the iOS 9 era.
Why a software update can kill a chain, but not always
Every boot stage except the Boot ROM is software Apple can update. When Apple patches a flaw in iBoot or the kernel, the next iOS version closes that hole, and the old chain stops working on updated phones. That is the normal life cycle of a jailbreak, and it is why Calif researcher Stefan Esser’s comment matters: he said most of the Hexacon bugs are fixed in iOS 27.2. If those bugs live in updatable stages, 27.2 ends the chain for anyone who installs it.
The exception proves the rule. A Boot ROM flaw cannot be patched, so a chain built on one survives every update. So does a flaw in a component Apple does not update through iOS. Neither has been shown for Calif’s chain, and the smart assumption is that 27.2 closes most or all of it. Researchers will confirm that by diffing the update against iOS 27.0.1 in the days after release, a process we will be watching closely.
There is a second way around the chain, and it already died
October produced a useful contrast. A separate iOS 27 jailbreak effort, CryptSn0w, did not attack the boot chain at all. It exploited Apple’s TSS signing server, the service that signs firmware tickets and cryptexes, to get the phone to accept a privileged component it would normally reject. That code has since been open-sourced, and its fate explains the difference. Because the flaw lived on Apple’s servers, Apple fixed it for every device at once, on October 9, without shipping an iOS update. The on-device chain Calif showed cannot be killed that way. It needs a software update, which is exactly what 27.2 is.
What this means for your phone
For nearly everyone, the practical conclusion is unchanged. Install iOS 27.2 when it arrives, keep Automatic Updates on, and treat any website offering an iOS 27 jailbreak download as a scam, because no tool exists. Calif has said it will not release an end-user tool, and its six second iPhone Duo clip from launch day, which we covered on October 24, shows even less than the Paris demo did.
For readers in genuinely high risk categories, journalists, activists, and executives handling sensitive material, Lockdown Mode under Settings, Privacy and Security remains the strongest built-in defense Apple ships. It shuts down several of the message-based attack surfaces that chains like this one depend on, including the Signal and iMessage routes Calif demonstrated separately.
The boot chain is Apple’s deepest defense, and for a decade it held against every public untethered attempt. Paris showed it can still be beaten, at least on iOS 27.0.1. This week we learn whether the fix holds.
