Skip to content
How to Fix SOS Only and No Service Modem Recovery on iPhone 15: Complete Diagnostic ManualMappleCare Community ↗

How to Fix SOS Only and No Service Modem Recovery on iPhone 15: Complete Diagnostic Manual

By • • 7 min read

1. Issue Overview & Symptoms on iPhone 15

The iPhone 15 series (D84/D84A/D84B/D84C) exhibits a distinct “SOS Only” or “No Service” failure mode characterized by a complete loss of registration on the Home PLMN (Public Land Mobile Network) and all available PLMNs, restricting the device to emergency calling services (112/911) via the EmergencyCall.app pathway. Users observe a persistent “SOS” or “SOS Only” badge in the Dynamic Island and Control Center status bar, replacing the carrier name and signal strength RSSI bars. Critically, the Settings > Cellular pane often displays “No SIM” or “Searching…” indefinitely, despite a physically seated nano-SIM or active eSIM profile (SM-DP+). The CommCenter daemon logs reveal repeated CTCarrier state transitions: kCTCarrierRadioAccessTechnologyDidChangeNotification firing with NULL RAT, followed by kCTRadioAccessTechnologyGPRS fallback attempts that stall at MM_STATE_REGISTERING. Baseband firmware (Qualcomm Snapdragon X70 / SDX70M, firmware branch MPSS.TH.4.0) crashes manifest as modem_stall watchdog timeouts in syslog (kernel: (AppleBCMWLANCore) modem_watchdog_timeout), often correlated with PMIC (PM8019/PM8020) rail brownouts on VPH_PWR (1.8V) or VCC_RF (3.3V) during high-throughput CA (Carrier Aggregation) or ENDC (E-UTRA-NR Dual Connectivity) negotiation. This is not a SIM failure; ICCID reads succeed via MobileEquipmentIdentity IOService, confirming UICC electrical connectivity. The failure isolates to the Baseband Processor (BP) / Application Processor (AP) IPC handshake over the high-speed UART (HS-UART) / Shared Memory (SMEM) transport layer.

2. Subsystem Architecture & Failure Mechanics

The iPhone 15 cellular subsystem centers on the discrete Qualcomm SDX70M 5G Modem-RF System, interfacing with the A16 Bionic (AP) via a dedicated PCIe Gen 3 x1 lane (tunneled over MIPI M-PHY/UniPro) for high-throughput data plane traffic and a high-speed UART (4.6 Mbps) for control plane (AT commands, QMI, DIAG). The PMIC (Qualcomm PM8019/PM8020) manages 12+ dedicated Low-Dropout Regulators (LDOs) and Buck converters for the modem: VCC_MODEM_CORE (0.75V), VCC_MODEM_MEM (0.9V), VCC_RF_TX (3.3V), and VCC_ANT_TUNER (1.8V). Failure mechanics initiate when the Modem Power Manager (MPM) firmware requests a power state transition (e.g., PM_MODEM_STATE_ONLINE to PM_MODEM_STATE_DATA_CALL). If the PMIC detects an over-current event (OCP) on VCC_RF_TX during a 256-QAM uplink burst (n77/n78 FR1), it triggers a PMIC_WDOG_BARK, asserting MODEM_RESET_N to the SDX70M. The AP-side driver (AppleQualcommModem.kext / IOKit personality com.apple.driver.AppleQualcommModem) receives a kIOMessageServiceIsTerminated via the IOService matching dictionary. However, the CommCenter userspace daemon (PID 1 child, launched via launchd.plist com.apple.CommCenter) fails to reconcile the CTModem object state machine, leaving the CTTelephonyNetworkInfo cache stale. Simultaneously, the Secure Enclave Processor (SEP) blocks keybag decryption for the eSIM profile (stored in EF_IMPI/EF_DOMAIN files) because the SEP firmware attestation of the Modem Firmware hash (measured at boot via IBoot trustcache) mismatches the post-crash recovered firmware version. This creates a deadlock: AP requests SIM auth -> SEP refuses (modem measurement mismatch) -> Modem cannot authenticate -> Network rejects REGISTER REQUEST -> SOS Only. Thermal sensors (TS_MODEM, TS_PA) reporting > 105°C exacerbate PMIC throttling, collapsing VCC_MODEM_CORE voltage below 0.70V, inducing instruction fetch errors in the modem’s Hexagon DSP.

3. Pre-Flight Diagnostic Checklist

  • Carrier Account Status: Verify provisioning status via carrier portal; confirm IMEI (Settings > General > About) is not blocked/blacklisted (GSMA IMEI Database).
  • SIM/eSIM Integrity: Eject nano-SIM; inspect gold contacts for oxidation (clean with 99% IPA). For eSIM: Settings > Cellular > [Plan] > Remove Cellular Plan, then re-add via SM-DP+ QR code (Settings > Cellular > Add eSIM > Use QR Code).
  • RF Exposure / Physical Damage: Inspect chassis for bend points near lower antenna flex (Lightning/USB-C flex assembly) and upper mmWave antenna module (if applicable). Check Liquid Contact Indicators (LCIs) in SIM tray slot and USB-C port (white = dry, red = triggered).
  • iOS Version & Carrier Settings: Confirm iOS 17.4.1 – 18.2. Check Settings > General > About > Carrier version (e.g., 5G_56.0). Force update: Settings > General > About (wait 15s for popup).
  • Mac/PC Host Diagnostics: Connect via USB-C (USB 3.2 Gen 2). Launch Console.app (macOS) > Select Device > Filter CommCenter, baseband, modem. Observe for ModemManager: Modem reset detected or QMI_ERR_INTERNAL.
  • Field Test Mode: Dial *3001#12345#* > LTE > Serving Cell Meas. Verify rsrp > -110 dBm and rsrq > -15 dB. If rsrp = 0 or PLMN = 000-00, RF front-end is non-functional.
  • Backup Integrity: Execute encrypted Finder/iTunes backup. Verify Manifest.plist IsEncrypted = true. Confirm KeychainDomain and WirelessDomain (contains carrier.plist, preferences.plist) are present.

4. Terminal & Diagnostic Commands

Execute the following on a macOS host (Apple Silicon/Intel) with libimobiledevice (brew install libimobiledevice ideviceinstaller) and Apple Configurator 2 CLI (cfgutil) installed. Device must be in Normal Mode (not DFU/Recovery) and trusted.

# 1. Extract real-time syslog stream (requires paired device)
idevicesyslog -u  | grep -E -i "commcenter|baseband|modem|qmi|pmic|thermal|sos|no service|sim|carrier|rat|plmn|registration"
# 2. Dump Baseband Firmware Version & Hardware Revision
ideviceinfo -u  -k BasebandFirmwareVersion
ideviceinfo -u  -k BasebandHardwareVersion
ideviceinfo -u  -k IntegratedCircuitCardIdentity
# 3. Trigger Modem Diagnostic Log Collection (persists to /var/logs on device)
# Requires Developer Mode enabled (Settings > Privacy & Security > Developer Mode)
idevicediagnostic -u  diagnostics -o /tmp/device_diag_$(date +%s).zip
# 4. Query Modem Power State via MobileGestalt (requires libmobilegestalt.dylib on device or remote query)
# On macOS host using cfgutil (Apple Configurator 2)
cfgutil get ModemFirmwareVersion
cfgutil get CellularPlanCount
cfgutil get ICCID
# 5. Analyze Panic Logs (Kernel/Baseband) from last boot
# Pull panic logs via idevicecrashreport
idevicecrashreport -u  copy /tmp/panic_logs/
# Parse for Modem Watchdog
grep -r "modem_watchdog_timeout\|PMIC_WDOG\|MODEM_RESET_N" /tmp/panic_logs/
# 6. Force Carrier Settings Update Profile Installation (Enterprise/Supervised only)
# cfgutil install-profile /path/to/carrier_settings.mobileconfig

5. Step-by-Step Remediation Protocols

Protocol Alpha: Non-Destructive State Reset (Software Layer)

  1. Toggle Airplane Mode with Timing: Control Center > Airplane Mode ON. Wait 30 seconds (allows CommCenter to tear down QMI sockets and release PMIC rails). Airplane Mode OFF. Wait 60s for CTModem power-up sequence.
  2. Reset Network Settings (Preserves UICC/eSIM): Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. Enter Passcode. Device reboots. This flushes /var/preferences/SystemConfiguration/preferences.plist (Wi-Fi/VPN/APN) and /var/wireless/Library/Preferences/com.apple.commcenter.plist, forcing CommCenter to rebuild CTCarrier objects from SIM EFs.
  3. Carrier Settings Re-fetch: Post-reboot, connect to Wi-Fi. Settings > General > About. Tap “Carrier” version row if update prompt appears. If not, dial *#5005*7672# (SMSC reset) then *#5005*7672# again to trigger OMA-DM session.
  4. Validate: Field Test Mode (*3001#12345#*) > NR5G SA / LTE > Serving Cell Info. Confirm PLMN matches Home Network (e.g., 310-260 T-Mobile US).

Protocol Beta: Deep Modem Firmware Re-flash via IPSW Restore (Firmware Layer)

Warning: Erases all data. Requires recent Finder/iTunes encrypted backup.

  1. Enter Recovery Mode (iPhone 15): Connect USB-C to Mac. Press Volume Up, release. Press Volume Down, release. Press and Hold Side Button. Do not release at Apple logo. Continue holding until “Connect to Computer” screen (Recovery Mode DFU-like state with iBoot active).
  2. Fetch Signed IPSW: On Mac, Terminal: mkdir -p ~/IPSW && cd ~/IPSW && curl -O "https://updates-http.cdn-apple.com/2024FallFCS/fullrestores/042-XXXXX/XXXX/Restore_iPhone15_18.2_22C152_Restore.ipsw" (Verify SHA256 via shasum -a 256 *.ipsw against ipsw.me).
  3. Restore via Finder (macOS 10.15+) or idevicerestore (Linux/CLI):
    # Finder: Select iPhone > Hold Option (Alt) > Click Restore iPhone > Select IPSW.
    # CLI (libirecovery/idevicerestore):
    idevicerestore -u  -e -d ~/IPSW/Restore_iPhone15_18.2_22C152_Restore.ipsw

    The -e flag erases (updates baseband firmware MPSS.TH.4.0.cX and PMIC firmware PM8019_FW_vXX via AppleMultiFunctionManager.kext).

  4. Setup as New: Do not restore backup immediately. Test cellular activation on Setup Assistant “Cellular” screen. If “SOS Only” persists here, hardware failure is confirmed (Protocol Gamma).
  5. Restore Backup: Only if Protocol Beta succeeds. Finder > Restore Backup > Select Encrypted Backup.

Protocol Gamma: Hardware-Level PMIC / RF Front-End Intervention (Physical Layer)

Requires Apple Authorized Service Provider (AASP) or Self Service Repair (SSR) kit. Voids warranty if not AASP/SSR.

  1. Diagnose PMIC Rails: Using SSR Thermal Camera / Multimeter on Logic Board Test Points (requires Display/Logic Board separation).
    • Measure VCC_MODEM_CORE (TP_MPM_CORE): Target 0.75V ± 20mV (Active), 0.0V (Off).
    • Measure VCC_RF_TX (TP_PA_VCC): Target 3.3V ± 100mV (TX Burst).
    • Measure VCC_ANT_TUNER (TP_TUNER_VCC): Target 1.8V ± 50mV.
  2. Inspect RF Flex Assemblies: iPhone 15 uses distinct Lower Component Flex (USB-C, Mic, Lower Antenna, mmWave if Pro) and Upper Antenna Flex (UWB, Upper Antenna, mmWave). Check for:
    J4800 (Lower Flex to Logic Board) connector pins 12, 14, 16 (HB/LB/MB Antenna) for bent pins/corrosion.
    J4801 (Upper Flex) for UWB/High

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 →