IPhone 11 Panic Log and 3-Minute Reboot: Common Causes and Fixes

🔒 This article is maintained by PhoneRepair.biz's automated research assistant and checked against public sources. Last reviewed: 2026-07-01. Spotted a mistake? Report an error on the talk page — or just edit the article. Suggestions from readers are reviewed before going live.

Recovery at a glance
Difficulty	Intermediate
Risk to data	Low to stored data (board-level repair; NAND is not touched)
Time estimate	30–90 minutes
Storage type	NVMe NAND (64 / 128 / 256 GB), soldered
Device state	Boots to SpringBoard, then kernel/userspace panic-reboots at ~180 s
Key tools	Precision opening kit, quality OEM-pull charge-port flex and power/volume button flex, USB analytics access or 3uTools/iMazing, microscope + multimeter (optional)

The iPhone 11 (A2111) is one of the most frequent devices to land on a repair bench with a "restarts every three minutes" complaint. The device powers on normally, reaches the lock screen or Home Screen, runs for roughly 180 seconds, then reboots — and repeats indefinitely. On this model the cause is almost always a userspace watchdog panic from `thermalmonitord` caused by a missing, damaged, or aftermarket component that fails to report a required sensor. This article documents the panic-string tokens seen on the iPhone 11 specifically, the board-level components most often implicated, and the diagnosis-to-repair path. For the general method see How to Read an iPhone Panic-Full Log, and cross-reference tokens against the iPhone Panic-String Signature Database. The model hub is iPhone Panic Logs and Boot Diagnostics.

Overview

iOS runs a daemon called `thermalmonitord` that continuously polls the device's thermal and environmental sensor array. A userspace watchdog expects `thermalmonitord` to "check in" successfully. If the daemon cannot enumerate every sensor iOS considers mandatory for that hardware model, it never posts a successful check-in. After the watchdog interval elapses — about three minutes from load — the kernel force-panics the device to attempt self-recovery, and the phone reboots. Because the missing sensor is still missing after the reboot, the loop is permanent until the hardware is corrected.

The signature panic-string on the iPhone 11 reads approximately:

"userspace watchdog timeout: no successful checkins from thermalmonitord since load"
... Missing sensor(s): Prs0 ...
SD: 1 BC: 1 RC: 0 BS: 1

The critical text is the `Missing sensor(s):` token — that string names the exact sensor iOS could not read, which points directly at the board component to inspect or replace. The `SD/BC/RC/BS` flags are internal watchdog state and are not, on their own, a reliable diagnostic; treat them as secondary.

Why this model is special: sensor enforcement is not uniform across the lineup. The iPhone 11 enforces a thermal sensor carried on the power/volume button flex that later models (e.g. iPhone 12) do not require, in addition to the barometric pressure sensor and bottom microphone carried on the charge-port (Lightning) flex. This is why a "good enough" aftermarket charge port or a button flex omitted during a screen/frame swap will boot-loop an iPhone 11 while the same part might pass on a different model.

Applies to

Brand / model: Apple iPhone 11 (model A2111; global variants A2221 / A2223 share the board family). The same failure pattern and workflow apply to iPhone 11 Pro (A2160) and 11 Pro Max (A2161), though enforced-sensor sets differ slightly per model.
SoC: Apple A13 Bionic (T8030) with a discrete SEP (Secure Enclave Processor).
Storage: Soldered NVMe NAND (64 / 128 / 256 GB). Not eMMC/UFS; there is no removable card.
OS & encryption: iOS 13 through current iOS 18/26 builds. Data is protected by hardware File-Based Encryption (FBE / Data Protection) rooted in the SEP and a per-device UID; class keys are wrapped to the user passcode.
Required device state for this procedure: the device must power on and reach at least SpringBoard for the diagnostic window. A device that never boots, panics instantly (<10 s), or shows a "kernel data abort" is a different fault class (CPU/NAND/PMIC) — see Common pitfalls.

Risk to data

This is a board-level repair. When the fault is genuinely a missing sensor, correcting it does not touch the encrypted NAND and carries low data risk — the user's data becomes usable again simply because the device stops rebooting.

Be explicit with the customer about what this repair does not do:

It does not decrypt anything and does not bypass the passcode. If the device is in a BFU (Before First Unlock) state or the passcode is unknown, fixing the panic loop only gives you a working-but-locked phone. FBE keys remain sealed in the SEP. There is no lawful data-recovery shortcut around iPhone 11 Data Protection.
Point of no return / irreversible risk: if you misdiagnose a sensor panic as something else and jump to NAND reball, CPU reflow, or "tristar/tigris" rework, excessive heat or a slipped reball can corrupt the NVMe or crack the underfilled A13 package — that can destroy data permanently. Do not apply hot air to the CPU/NAND stack to "fix" a `thermalmonitord`/`Missing sensor` panic; that panic is not a CPU fault.
Always take (or confirm the owner has) a backup before opening, if the device is unlocked and stays up long enough to sync.

Tools and materials required

Precision screwdriver / opening kit (P2 Pentalobe, tri-point Y000, Phillips #000), suction handle, plastic spudgers, tweezers.
Adhesive-remedy and reseal supplies (display and back-glass gaskets as needed); the iPhone 11 is IP68 — reseal properly.
Known-good replacement flexes: a high-quality OEM-pull charge-port (Lightning) flex and a power/volume button flex for the A2111. Low-grade aftermarket flexes are a leading cause of this fault, not a fix — insist on OEM/OEM-pull for parts that carry sensors.
A way to read panic-full logs off the device: on-device (Settings) or via 3uTools / iMazing / libimobiledevice over USB.
Optional but recommended: stereo microscope, multimeter/diode-mode, and a boardview + schematic for the A2111 to trace a suspect sensor line to its connector when a swap alone does not resolve it.

Prerequisites and safety

Obtain documented owner authorization before opening the device or exporting logs (see Legal and consent note).
Disconnect the battery FPC before removing or reseating any board flex. Discharge and work ESD-safe.
Read the panic log before you open anything — the log tells you which flex to buy. Opening blind wastes an adhesive set.
Confirm the panic cadence: a true `thermalmonitord` sensor loop reboots at roughly the same uptime (~3 min) every cycle. Random-interval reboots suggest a different problem.
Handle the A13 area with care; never park hot air over the SoC/NAND for a sensor-class fault.

Step-by-step procedure

Reproduce and time the loop. Power the device and note uptime at reboot. Consistent ~180 s cycles strongly indicate a userspace watchdog / sensor panic rather than a power or NAND fault.
Retrieve the panic-full log. On-device: Settings → Privacy & Security → Analytics & Improvements → Analytics Data, scroll to the newest `panic-full…` entry (alphabetical; timestamped). Alternatively pull logs over USB with 3uTools / iMazing / `idevicecrashreport`. Because the device only stays up ~3 minutes, be quick or use USB export.
Locate the panic string. Read the top of the JSON/`panicString`. Confirm the phrase `no successful checkins from thermalmonitord` (userspace watchdog). Then find the `Missing sensor(s):` token and record the exact sensor name(s).
Map the token to a component (iPhone 11). Use the table in Verifying the result below. On the iPhone 11 the overwhelmingly common tokens are `Prs0` and `Mic1` (charge-port flex) and a power/volume button flex sensor.
Inspect and reseat first — swap second. Open the device (battery FPC off first). Reseat the named flex on its board connector; inspect for a bent pin, torn pad, corrosion, or an aftermarket flex missing the sensor die. A poor connection alone can produce the "missing" reading.
Replace the implicated flex with OEM/OEM-pull. If the token is `Prs0` or `Mic1`, replace the charge-port flex. If the log implicates the button-flex thermal/mic sensor, replace the power/volume button flex. If both are named, address both. Test-point / connector locations vary by board revision — verify against an A2111 boardview/service schematic; do not rely on generic pinouts.
If a swap does not clear it, trace the line. A persistently "missing" sensor after a known-good flex swap points to a broken board-side trace, a bad connector (FPC socket), or an upstream sensor-array/PMIC fault. Use a boardview to follow the specific sensor net from its connector to the SoC/PMU, and diode-check the connector pins. This is micro-soldering territory — proceed only with the schematic.
Reassemble and reseal. Restore adhesives/gaskets to preserve water resistance; torque screws to spec.

Verifying the result

After the repair, boot the device and let it run past 5 minutes — well beyond the ~3-minute watchdog window — without a reboot. Then pull a fresh panic-full log and confirm no new `thermalmonitord` "Missing sensor(s)" entries are being generated. Optionally verify the previously-missing subsystem works end-to-end (e.g. bottom microphone records in Voice Memos; barometer reads in a sensor-log app).

iPhone 11 panic-string token → likely component (community-observed):

Token in `Missing sensor(s):`	Most-likely component on iPhone 11	Notes
`Prs0`	Barometric pressure sensor on the charge-port (Lightning) flex	Single most common iPhone 11 cause; aftermarket ports frequently omit it
`Mic1`	Bottom microphone (with its temp sensor) on the charge-port flex	Often appears alongside `Prs0`
`Mic2` / `REARMIC2`	Microphone/thermal sensor on the power/volume button flex	Source naming varies (some maps place Mic2 near the flash); verify against your log and boardview
`TG0V`	Battery voltage sense (gas-gauge / battery FPC)	Points to battery or its FPC/fuel-gauge, not the charge port
`TG0B`	Battery temperature sense (gas-gauge)	Battery / charging circuit

Treat this table as a starting hypothesis, not a guarantee — the same token can have several root causes (flex, connector, board trace, or the sensor's upstream IC). The log is a clue, not a verdict.

Required / enforced sensors & components for this model

Based on community bench data (iFixit, ipadRehab, board-repair shops), the iPhone 11 typically enforces reporting from the following before `thermalmonitord` will check in successfully:

`Prs0` — barometric pressure sensor — charge-port flex.
`Mic1` — bottom microphone + associated temp sensor — charge-port flex.
A thermal sensor on the power/volume button flex — this is the iPhone-11-specific requirement that iPhone 12 dropped, and it is easy to overlook after a housing/frame transfer.
Battery gas-gauge sensors (`TG0V` / `TG0B`) — battery FPC / fuel gauge.

Honesty note: the exact enforced set can change with iOS version — Apple has altered which sensors are mandatory across releases, so a device that was stable on one iOS build can begin looping after an update, and vice-versa. Community documentation of the precise iPhone 11 list is good but not exhaustive, and specific silicon part numbers for each sensor die are not reliably published — do not quote fabricated component IDs to a customer. Verify against a current A2111 boardview and the actual `panicString` on the bench.

Success rate and limitations

When the panic string clearly names `Prs0`/`Mic1` and the fault is a bad or missing charge-port flex, replacing it with an OEM/OEM-pull part resolves the loop in the large majority of cases — this is a high-yield, well-understood repair. Button-flex sensor cases resolve similarly once the correct flex is fitted.

What this does NOT recover or fix:

Encrypted user data on a locked device. Fixing the reboot loop does not decrypt the NAND. iPhone 11 uses SEP-backed FBE; without the passcode (or an existing trusted backup) the data stays sealed. There is no legitimate bypass of Data Protection or Activation Lock (FRP) via this repair, and this article does not provide one.
Activation Lock / iCloud state. A repaired, working phone that is iCloud-locked remains locked; that is an ownership question, not a hardware one.
Genuine CPU/NAND panics. If the log shows `kernel data abort`, `ANS/ANS2`, `Nvme`, or instant (<10 s) panics, that is a storage/CPU fault — a different, lower-success, higher-data-risk repair, not a sensor swap.

Common pitfalls and troubleshooting

Fitting another cheap aftermarket flex. The root cause is frequently an aftermarket part that omits the sensor. Replacing it with another low-grade flex reproduces the fault. Use OEM/OEM-pull for sensor-bearing parts.
Forgetting the button flex after a frame transfer. On iPhone 11, an unseated or damaged power/volume flex sensor will loop the phone even when the charge port is perfect. If the log doesn't name `Prs0`/`Mic1`, check the button flex.
Chasing `SD/BC/RC/BS` numbers. These watchdog flags are not a component map. Anchor your diagnosis on the `Missing sensor(s):` token.
Assuming it's software. A restore/DFU can clear a corrupted-log false alarm, so try a clean restore first if you're unsure — but a truly missing hardware sensor will loop again immediately after restore. Don't reflow the CPU to "fix" a sensor panic.
Liquid damage. Corrosion on the charge-port connector or its board pads can present identically. Inspect under magnification; clean and re-verify before condemning the flex.
Post-update onset. If the loop started right after an iOS update, the update may have begun enforcing a sensor the prior build ignored — the hardware fault was latent. Read the new log; the token will still point you to the part.

Legal and consent note

Only service devices you own or are explicitly authorized to repair. Retrieving panic-full logs and analytics data exposes device identifiers and usage information — obtain the owner's documented consent before exporting logs off the device, and handle that data per applicable privacy law. This procedure restores hardware function; it must not be used to circumvent Activation Lock, passcode Data Protection, or any anti-theft mechanism on a device you do not own or lawfully control. If ownership cannot be established, stop and refer the device.

Sources

PhoneRepair.biz is a free community knowledge base. Data recovery and board-level repair carry a real risk of permanent data loss — when the data matters, back up any raw dump before modifying a device and consider a professional lab. Only work on devices you own or have documented authorization to service. See PhoneRepair:Legal notice.