Cops Can Bypass iPhone's Automatic Reboot to Get into Locked Phones
Police forensics tools like GrayKey can reportedly bypass Apple’s automatic “inactivity reboot” safeguard, allowing investigators to preserve a seized iPhone’s unlocked state and later extract data that should have been protected after a reboot. Commenters debate the technical angles (Secure Enclave, clock manipulation, USB-based exploits) and compare iOS with hardened Android variants like GrapheneOS, while noting that such capabilities are generally too expensive for ordinary thieves but accessible to governments. The thread broadens into concerns about border searches, duress passwords, and the limits of legal protections such as the Fifth Amendment, highlighting the gap between theoretical device security and what can happen in practice when states have both legal and technical leverage.
How the bypass may work
- Some speculate the inactivity reboot is implemented in the Secure Enclave and not driven by NTP, but may rely on a manipulable time source or other oversight (e.g., “wall clock” vs monotonic timers).
- Others think GrayKey doesn’t really “stop” the reboot, but exploits the AFU state to extract key material (“keybags”) and later re-use it even after power loss.
- There’s discussion that USB/port-level tricks or clock spoofing could be involved; details are unclear from the leak.
Forensics tools, access, and costs
- GrayKey and similar tools are described as expensive, licensed primarily to government agencies; quoted figures are in the tens of thousands per year, sometimes five-figure per‑device unlocks.
- Some argue this keeps them out of ordinary thieves’ hands, others note that insider abuse or leak of tools/keys is plausible.
User security strategies and limitations
- Several recommend:
- Using long passphrases instead of short PINs.
- Relying on auto‑reboot/“inactivity” features where available.
- Shutting devices down yourself in “high snatch risk” situations.
- Disabling Control Center / airplane mode on the lock screen.
- Keeping sensitive data in separate encrypted containers or E2EE cloud, or on offline/secondary devices, not daily phones.
- Skeptics warn that flawed “safety” features can create false confidence, and OS‑level duress/wipe functions may be defeatable or create new legal risks.
Legal and civil liberties concerns
- Lengthy debate over border searches:
- Some say you “must unlock” and can be detained or have devices seized if you refuse.
- Others counter that constitutional protections (e.g., against self‑incrimination) apply, but note you can still face contempt/obstruction or long pre‑trial detention.
- People distinguish rare but serious risks from everyday likelihood, and note the chilling effect of overbroad powers.
Debate over Apple, backdoors, and responsibility
- Some suspect modem or Secure Enclave backdoors or NOBUS‑style weaknesses; others point to public Apple–FBI conflicts as evidence against deliberate backdoors.
- Apple’s control over devices (remote code execution via updates, compliance with local regimes) leads to claims that users never fully “own” their phones.
GrapheneOS and duress features
- Thread contrasts iOS/Pixels’ fixed 72‑hour auto‑reboot with GrapheneOS’s configurable timer and two‑factor unlock (passphrase + biometric+PIN).
- Some praise GrapheneOS duress codes; others note recent cases where using destructive duress codes led to charges for evidence destruction, and that such features depend on hardware limits to be trustworthy.
Ethics of forensics vendors and power balance
- Concern that “evidence preservation” modes effectively pre‑search devices before warrants, similar to bulk data collection, while vendors and police claim they’re only freezing state.
- Some argue for treating such vendors as engaging in tortious interference with device makers, but note that law enforcement and corporations tend to be favored over individual privacy.