Your iPhone shows “SOS only” when it can reach a cellular tower that belongs to some carrier — enough to place an emergency call over another provider’s network — but cannot complete a normal registration with your own carrier’s network for voice, data, or SMS. The condition is a partial radio link, not a dead phone: the modem hears a signal, fails the identity and authorization handshake, and falls back to emergency-only service. That single distinction explains nearly every cause, from a dead battery in a distant cell site to a carrier settings file that no longer matches the network.
This fallback is deliberate. Emergency calling is treated as a safety function in most countries, so phones are built to attach to any compatible tower for 911 even when no commercial service is authorized. Apple documents this behavior in its support material: when you see “SOS” or “SOS only” in the status bar, your device can still call emergency services if cellular coverage is available, and the wording differs because the feature’s availability varies by country. What follows is the mechanism, the numbers that matter, the edge cases, and the checks that actually resolve it.
The registration handshake behind the status bar
A phone does not simply “connect” to a tower. It performs an attach procedure: it reads the tower’s broadcast identity, negotiates radio-level parameters, then authenticates cryptographically with the core network using credentials stored in the SIM or eSIM. Only after authentication does the network authorize services and assign an IP path for data. “SOS only” means the first steps succeeded — the tower is physically reachable and compatible — while authentication, authorization, or service provisioning failed, or the home network simply is not present.
The status-bar logic reflects that split. Apple states that “SOS” appears when your cellular carrier’s network is unavailable but other networks are available for emergency calls, while “SOS only” appears when cellular service is unavailable but emergency calls are possible over another carrier. In both cases the modem is doing exactly what it was designed to do: keep the emergency path open while withholding commercial service.
Two mechanisms drive most real-world cases. The first is radio-frequency mismatch: a tower broadcasts on bands your modem supports, but the specific carrier identity it announces is not one your SIM is authorized to use. The second is core-network rejection: the tower is yours, the radio link is fine, but the authentication server rejects the attach — often because the SIM’s subscription state, the carrier settings bundle, or the device’s provisioning is out of date. A third, subtler mechanism is the emergency-only attach itself: once a device latches onto a foreign network for emergency service, it may stay there until it re-scans, which is why toggling airplane mode so often “fixes” the display.
Quantified context: how partial coverage actually looks
Signal strength alone does not predict the status bar. On LTE, a usable reference signal can sit anywhere from roughly −80 dBm (strong) to −110 dBm (marginal), and calls often hold below −105 dBm while data stalls. The status bar is a service-state indicator, not a signal meter, so a phone can show four bars and “SOS only” simultaneously — the bars describe the radio link, the text describes authorization.
Timing matters too. After you leave a coverage area, a phone typically holds its last registration for tens of seconds before declaring service lost, then begins scanning on the order of every 10 to 60 seconds depending on idle-mode settings. That is why the banner sometimes appears minutes after you enter a basement or a rural dead zone rather than instantly. Re-selection to a stronger or home network can take similar time, and airplane mode forces an immediate re-scan rather than waiting for the timer.
Apple’s own troubleshooting guidance frames the fix around three levers: toggling cellular data and airplane mode, restarting the device, and checking with the carrier about outages and account status. Those map directly onto the mechanisms above — re-scan, re-attach, re-authorize.
A timeline of what the phone is doing
| Elapsed time after coverage loss | Modem behavior | What you may see |
|---|---|---|
| 0–10 seconds | Holds last registration, measures neighbor cells | Bars may persist, no banner |
| 10–60 seconds | Declares out-of-service, begins periodic scans | “No Service” or “SOS only” appears |
| 1–5 minutes | Attempts attach to any permitted network | “SOS” if a foreign network is usable |
| 5–30 minutes | Repeats scans at idle-mode intervals | Banner flickers as cells are found and lost |
| After airplane-mode toggle | Immediate full re-scan and re-attach | Service returns if a permitted network exists |
| After restart | Fresh SIM read and carrier-settings load | Clears stale provisioning states |
| After carrier-settings update | New APN and identity parameters loaded | Resolves mismatches with the home network |
Edge cases that mimic a network failure
Several conditions produce “SOS only” with nothing wrong with the tower. A SIM that has been removed and reinserted, or an eSIM transfer that did not complete, leaves the device without valid credentials — the attach fails at authentication every time. A carrier settings update that arrived but was not installed can leave access-point parameters stale, so data authorization fails while voice registration still works, or vice versa. Account-level suspension, whether for billing or a reported loss, produces a network-side rejection that looks identical to a coverage problem.
International roaming adds its own layer. A phone abroad may attach to a visited network for emergency calls while roaming authorization is pending or blocked, showing “SOS only” even though local towers are strong. Physical obstructions behave differently from distance: dense construction materials can attenuate signals by 20 to 30 dB, enough to drop a marginal link below the attach threshold while a nearby window still works. Finally, a device that has been in a low-signal area for hours may be camped on a distant cell it can barely hear rather than re-scanning for a closer one — a behavior that resolves with a forced re-scan.
Misconceptions worth retiring
The most common error is treating “SOS only” as proof of a dead network. It is proof of a partial link. The second is assuming a restart is superstition; it forces a fresh SIM read and carrier-settings load, which genuinely clears stale provisioning states. The third is believing bars equal service — they measure radio quality, not authorization.
A counterintuitive professional caveat: a phone can show “SOS only” precisely because emergency service is working. The device has found a usable tower and is holding it for 911 calls; commercial service is the part that failed. That is why the banner often appears in places where a call to emergency services would actually connect.
Do not assume a battery or hardware fault before checking carrier status and outages. Do not repeatedly eject a SIM; reinsertion can corrupt the credential read. Do not ignore a carrier-settings update prompt; install it before troubleshooting further. Do not conclude the phone is broken if emergency calls work — that is expected behavior. Do not factory-reset as a first step; it erases data without addressing authorization.
Practical actions with thresholds
Work from least disruptive to most. First, toggle airplane mode for 10 seconds and back; this forces an immediate re-scan and re-attach. Second, restart the device, which reloads SIM credentials and carrier settings. Third, check the carrier’s outage page and your account status, since a network-side rejection is invisible on the handset. Fourth, install any pending carrier-settings update. Fifth, re-seat the SIM only if it was recently moved, and verify eSIM activation status. If “SOS only” persists across multiple locations for more than 30 minutes while emergency calls work, the problem is almost certainly authorization or provisioning, not coverage — contact the carrier with the exact banner text and the locations where it appears.
Limits of what the handset can tell you
The status bar cannot distinguish a rejected authentication from an absent home network, and it cannot report why a rejection occurred. Those details live in the carrier’s core network, not on your screen. That is why the practical sequence above ends with a carrier contact rather than a device setting: the handset can re-scan and reload credentials, but it cannot re-authorize a subscription or repair a network-side provisioning error. Apple’s guidance and your carrier’s outage tools are the authoritative references; anything beyond them is inference from behavior.
This article is general educational information about how cellular registration and emergency fallback work, not a diagnosis of your device or account. It does not promise that any step will restore service. For account, billing, or provisioning problems, contact your carrier; for device hardware concerns, consult Apple or an authorized service provider. If you are in immediate danger, use the emergency call function your phone is preserving and contact local emergency services.