Skip to content
How to Fix Bootloop without Data Loss on iPhone 11: Complete Diagnostic ManualMappleCare Community ↗

How to Fix Bootloop without Data Loss on iPhone 11: Complete Diagnostic Manual

By • • 8 min read

1. Issue Overview & Symptoms on iPhone 11

The iPhone 11 (N104AP, D22) bootloop manifests as an infinite restart cycle where the device powers on, displays the Apple logo (with or without the progress bar), remains static for 10–180 seconds, then abruptly cuts power to the display and PMIC rails before restarting. Critically, the device never reaches the launchd userspace initialization phase, preventing SpringBoard load and APFS volume mount of the /private/var (Data) volume. Users report the device enumerates in DFU mode (USB PID 0x1281) but fails to enumerate in Recovery Mode (USB PID 0x1283) consistently, indicating a failure during the iBoot stage 2 handoff to the kernel. Visual indicators include a static Apple logo (no progress bar = early iBoot/SEC failure; progress bar stall = kernel/kext/driver load failure). Thermals remain nominal (PMIC die temp < 45°C), ruling out thermal throttling shutdowns. Diagnostic state via idevicediagnostics or Apple Configurator 2 shows BootProgress stuck at 0x0 or 0x1, with LastPanics.plist inaccessible due to the Data volume remaining encrypted (Class D keys not unsealed by Secure Enclave). This specific failure vector on A13 Bionic typically correlates with APFS transaction log corruption in the Preboot volume, a corrupted kernelcache signature verification failure (AMFI), or a baseband firmware (BBUP) mismatch causing a watchdog reset (WDT) via the Always-On Processor (AOP).

2. Subsystem Architecture & Failure Mechanics

The iPhone 11 boot sequence relies on a strict Chain of Trust: Secure ROM (Boot ROM) → LLB (Low Level Bootloader) → iBoot → Kernelcache (XNU) → launchd. A bootloop indicates a break in this chain post-iBoot execution but pre-userspace. On the A13 SoC, the PMIC (PMU_GRAPE / PMU_CHESTNUT) manages 12+ power rails (VDD_MAIN, VDD_CPU, VDD_SOC, VDD_RAM). A bootloop often stems from the watchdog timer in the AOP (Always-On Processor) expiring because the XNU kernel failed to pet the watchdog via the IOWatchDogTimer IOKit driver within the 180-second timeout window. This occurs when the kernel panics during early init—specifically during APFS volume mount (apfs_mountfs) or kext injection (OSKext::load).

APFS on iPhone 11 utilizes a Copy-on-Write (CoW) B-tree structure with a dedicated Preboot volume (role: APFS_VOL_ROLE_PREBOOT) storing the kernelcache, iBoot payloads, and dyld_shared_cache. If the APFS transaction tree (checkpoint region) is corrupted—often due to an interrupted OTA update (iOS 16→17/18) where the fsck_apfs -y snapshot rollback failed—the kernel cannot validate the kernelcache hash against the Trust Cache (AMFI). The Secure Enclave (SEP) refuses to unseal the Class D (NSFileProtectionComplete) keys for the Data volume because the boot manifest hash (measured into PCR 0-7) does not match the expected policy. Consequently, the kernel enters a panic loop: panic(cpu 0 caller 0x...): "APFS: invalid checkpoint" or "AMFI: code signature validation failed". The AOP WDT triggers a global reset (PMIC GLOBAL_RESET line), restarting the cycle. Baseband (BBUP) firmware mismatch (Modem: Qualcomm XMM7560 / Intel PMB9955) can also trigger a baseband_watchdog_timeout panic if the Baseband IOKit driver fails to handshake with the AP over the HSIC/PCIe control plane during IOServiceMatch.

3. Pre-Flight Diagnostic Checklist

  • Host Machine: macOS 13.0+ (Ventura) or 14.0+ (Sonoma) with Apple Configurator 2.15+ and libimobiledevice (brew install libimobiledevice) installed. Disable SIP (csrutil disable) only if using idevicerestore custom IPSW workflows.
  • Cable Verification: Use Apple OEM USB-C to Lightning (or USB-A to Lightning) cable. Verify USB 2.0 High Speed (480 Mbps) enumeration via system_profiler SPUSBDataType; ensure device appears as “Apple Mobile Device (DFU Mode)” or “Apple Mobile Device (Recovery Mode)”.
  • Power Source: Connect to 20W+ USB-PD charger. Verify charging current > 500mA via ioreg -r -k "AppleUSBHostPort" | grep "CurrentAvailable". A depleted battery (< 3.6V) causes brownouts during NAND write ops in Recovery.
  • Backup Status: Confirm last iCloud Backup timestamp (Settings > [Name] > iCloud > iCloud Backup) or local Finder/iTunes backup manifest (~/Library/Application Support/MobileSync/Backup/).
  • Hardware History: Screen/battery replacement history? Non-genuine displays (missing ALS/Proximity calibration data in display.icl) trigger IODisplay kernel panics on iOS 17+. Battery BMS gas gauge (BQ27546) cycle count > 800 or MaxCapacity < 80% indicates voltage sag under boot load.
  • OS Version Target: Identify current installed version via Recovery Mode ideviceinfo -k ProductVersion. Target restore IPSW must be signed by Apple (check api.ipsw.me) or use Futurerestore with SHSH2 blobs (APTicket) for downgrade/upgrade to specific iOS 16/17/18 versions.

4. Terminal & Diagnostic Commands

Execute these on the macOS host machine with the iPhone 11 connected in DFU or Recovery Mode.

4.1. Device Enumeration & Mode Verification

# List all connected USB devices; confirm iPhone 11 (ID 05ac:1281 DFU / 05ac:1283 Recovery)
system_profiler SPUSBDataType | grep -A 11 "iPhone"

# libimobiledevice: Get device UDID and current mode (Normal, Recovery, DFU)
idevice_id -l
ideviceinfo -k DeviceClass -k ProductType -k ProductVersion -k BuildVersion -k UniqueDeviceID

4.2. Panic Log Extraction (If device boots to Recovery/Diagnostics)

# Pair device (trust prompt appears on screen if booted far enough)
idevicepair pair

# Pull diagnostic logs (requires device in Normal mode or Recovery with ramdisk)
# Note: In bootloop, this usually fails until a ramdisk is booted.
idevicediagnostics diagnostics 2>&1 | head -n 50

# Attempt to read panic logs via AFC (if Data volume mounted - rare in bootloop)
# Requires custom ramdisk (e.g., checkra1n/palera1n ramdisk) for filesystem access
# idevicecrashreport copy .

4.3. AOP / SEP Firmware & Boot Manifest Inspection (via idevicerestore / ipwndfu)

# Check if device is in DFU mode and probe AOP/SEP versions
# Requires ipwndfu (checkm8 exploit) for iPhone 11 (A13 - checkm8 vulnerable)
git clone https://github.com/axi0mX/ipwndfu
cd ipwndfu
./ipwndfu -p  # Probe mode: prints AOP, SEP, iBoot versions without exploit

# Sample Output Interpretation:
# AOP: 1.0.0 (release) / SEP: 5.0.0 / iBoot: 6723.100.12
# Mismatch between SEP OS version and iOS version on NAND causes bootloop.

4.4. NAND / APFS Health Check via Custom Ramdisk (Advanced)

# Boot a custom ramdisk (e.g., from palera1n or checkra1n) to access shell
# Once shell accessed via iproxy (port 22/44) or netcat:
# ssh -p 2222 root@localhost  (alpine)

# Check APFS Container integrity on /dev/disk0s1s1 (Data) / disk0s1s2 (Preboot)
fsck_apfs -n /dev/disk0s1s1  # Read-only check
fsck_apfs -n /dev/disk0s1s2

# List APFS Volumes
diskutil apfs list /dev/disk0s1

# Check Kernelcache existence in Preboot
ls -la /mnt/preboot/*/System/Library/Caches/com.apple.kernelcaches/

# Verify AMFI Trust Cache
amfid_dump -t /mnt/preboot/*/System/Library/Caches/com.apple.kernelcaches/trustcache

5. Step-by-Step Remediation Protocols

Protocol A: Non-Destructive Forced Recovery Entry & Update (Preserves Data)

Applicability: Bootloop caused by transient kernel panic, minor APFS journal inconsistency, or stalled OTA delta update. Success rate: ~65% on iOS 16-18.2.

  1. Force Enter Recovery Mode (iPhone 11 Specific):
    1. Connect to Mac via Lightning.
    2. Press and release Volume Up.
    3. Press and release Volume Down.
    4. Press and HOLD Side Button (Power).
    5. Ignore “Slide to Power Off”. Continue holding Side Button.
    6. Screen goes black → Keep holding.
    7. Apple Logo appears → Keep holding.
    8. Recovery Mode Screen appears (Lightning cable + Computer icon) → Release Side Button.
  2. macOS Finder / Apple Configurator 2 Action:
    1. Finder: Select iPhone in Sidebar → “Update” (NOT Restore). Downloads latest signed IPSW (iOS 18.x) and attempts in-place upgrade. Preserves /var (Data) and /private/var/root.
    2. Apple Configurator 2: Right-click device → “Update” → Select specific IPSW if downgrading/upgrading to specific version (requires signed IPSW).
  3. Monitor Logs: Open Console.app → Select Mac → Search “MobileDeviceUpdater” or “AMDRestore”. Look for ASR: Starting restore → ASR: Verifying kernelcache → Mounting /private/var.
  4. Post-Update: Device reboots to Setup Assistant (if successful) or back to Recovery. If stuck at “Waiting for iPhone” > 15 mins, proceed to Protocol B.

Protocol B: APFS Snapshot Rollback & fsck_apfs Repair via checkm8 Ramdisk (Data Preservation)

Applicability: “Update” fails with Error 4013, 4005, 9, or 14. Indicates APFS metadata corruption on Preboot/Data volumes. Requires checkm8 exploit (A13 vulnerable).

  1. Prepare Environment:
    brew install libimobiledevice libirecovery idevicerestore
    git clone --recursive https://github.com/palera1n/palera1n
    cd palera1n
    make setup
    make
  2. Enter DFU Mode: Same button combo as Recovery, but release Side Button when screen stays **BLACK** (no Apple logo). Device shows “Apple Mobile Device (DFU Mode)” in System Report.
  3. Boot Palera1n Ramdisk (Rootful/Rootless):
    # Boot the ramdisk (provides SSH shell over USB)
    ./palera1n_macos_universal --dfu --ramdisk
  4. SSH into Ramdisk & Repair APFS:
    # On host: iproxy 2222 22  (forwards local 2222 to device 22)
    # Connect:
    ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@localhost -p 2222
    # Password: alpine (default)
    
    # Identify APFS Container (usually disk0s1)
    diskutil list
    
    # 1. Verify Container
    fsck_apfs -n /dev/disk0s1
    
    # 2. If errors found, attempt repair (READ ONLY FIRST)
    fsck_apfs -y /dev/disk0s1  # DANGER: Can destroy data if container map is trashed. Backup via AFC first if possible.
    
    # 3. Snapshot Rollback (Preboot Volume)
    # Mount Preboot
    mkdir -p /mnt/preboot
    mount_apfs /dev/disk0s1s2 /mnt/preboot  # s2 usually Preboot
    
    # List Snapshots
    diskutil apfs listSnapshots /dev/disk0s1s2
    
    # Revert to last known good snapshot (UUID from list)
    # diskutil apfs revertSnapshot /dev/disk0s1s2 -snapshot 
    
    # 4. Verify Kernelcache & TrustCache integrity
    ls -l /mnt/preboot/*/System/Library/Caches/com.apple.kernelcaches/kernelcache.release.iphone12
    # If missing or 0 bytes, copy from a known good IPSW extracted kernelcache (matching BuildVersion)
    # Use 'ipsw' tool: ipsw download kernelcache --device iPhone12,1 --version 18.2 --build 22C152
  5. Exit Ramdisk & Test Boot: Type reboot in SSH. Device attempts normal boot.

Protocol C: Futurerestore with SHSH2 Blobs (Targeted Firmware Restore – Data Preservation via Custom IPSW)

Applicability: Protocols A/B failed. SEP/Baseband firmware compatible with target iOS version. Requires saved SHSH2 blobs (APTicket) for target version. Warning: iPhone 11 requires SEP/Baseband compatibility. iOS 16 SEP != iOS 18 SEP. You can only restore to versions where SEP/Baseband are compatible with current installed versions (usually current signed window + 1 version back).

  1. Verify SHSH2 Blobs: Check ~/shsh/ or TSSSaver output. Must have BuildManifest.plist, APTicket.der, IM4M blobs for iBoot, Kernelcache, SEP, Baseband.
  2. Build Custom IPS
Still running into this issue on your iPhone or Mac?

Share your OS version, device model, and exact error code in our independent peer Q&A rooms.

Ask in Community Forum →