No service after a phone update: what actually broke

An update touches four separate things, not one

Every repair-tool page treats "the update" as a single event. It isn’t. Four separate things decide whether your phone gets service, each on its own schedule, and the failures you are seeing are almost always a mismatch between two of them. Only the first is the thing you tapped Install on.

Layer 1 — the OS build. The part you consented to. It is also the least likely culprit on its own, because the same build ships to a very large number of identical handsets, so a fault that killed cell service outright for everyone would be a mass event rather than your event. When the OS itself is the problem, the problem is usually that it moved and something else didn’t.

Layer 2 — the carrier settings. On an iPhone this is a discrete file written by your carrier, not by Apple. Apple describes carrier settings updates as letting your carrier update network and settings information to improve cellular connectivity and performance, and gives Settings > General > About as the place to check for one. Two details from that page matter here. First, if your carrier issues a mandatory update, you see an OK button instead of an Update button, because the system already downloaded and installed it — so the absence of an Update prompt does not prove you are current. Second, setting up a new eSIM or inserting a new SIM can itself require downloading that carrier’s settings; the phone does not automatically already have every carrier’s bundle.

Android does the same job with a different mechanism. Carrier configuration is resolved through CarrierConfigManager in priority order — the carrier app first, then the platform configuration app, then framework defaults — and the first value found for a given key wins. The configuration is matched to your SIM using MCC, MNC, SPN, IMSI, GID1, GID2 and the Carrier ID. What it controls is exactly the set of things that break after an update: roaming and non-roaming network behavior, visual voicemail, SMS and MMS parameters, VoLTE and IMS configuration, and whether the subscription is treated as capable of voice, messaging and data at all.

The scheduling detail is the useful one. Android rebuilds that key-value list only when the SIM is loaded — at boot, or on a SIM hot swap — when the carrier app manually triggers a reload, or when the carrier app itself is updated. That is the mechanical reason a plain restart fixes a post-update phone often enough to have become folk wisdom. You are not "clearing something out." You are forcing the one event that rebuilds the carrier configuration.

Layer 3 — the modem firmware. Your phone’s cellular radio is a separate subsystem with its own software, and on a normal phone that software ships as part of the system image rather than as something you install or select. There is no ordinary Settings control that lets you pick a version of it. This layer matters less as something you can act on and more as something to stop chasing: if your symptom survives everything below and your carrier confirms the account and the network are fine, you have hit a layer that only a later OS release can move.

Layer 4 — the carrier’s record of your device. This one is not on your phone at all, which is why the entire repair-tool SERP misses it. VoLTE, Wi-Fi calling and SMS over IP are not simply toggles; they are switched on after an entitlement check defined by the GSMA TS.43 specification, which Android documents as the entitlement verification step for activating those services, plus on-device activation of eSIM companion devices and data plan information. The phone queries your carrier’s entitlement server using EAP-AKA authentication, with no credentials typed by you. When that handshake produces the wrong answer — because the carrier’s record still describes your old device build, or the record was never refreshed — voice service does not come back no matter what you reset locally.

Why a voice-only failure is the loudest signal

If your data works and your calls don’t, stop resetting things. US voice runs over VoLTE. Vermont’s Department of Public Service put it plainly when the 3G networks were retired: the transition requires the use of VoLTE, a form of voice over IP, and handsets more than a few years old that lack VoLTE support stopped working when 3G was shut down. Google warns in the same terms that devices without VoLTE or VoLTE roaming support may lose voice calling services, including calls to 911.

So a broken VoLTE state after an update is not a degraded call experience. It is no voice at all, on a phone whose data icon looks perfectly healthy. That combination is diagnostic, and it points up the stack at layers 2 and 4, not at the radio.

Which layer your symptom points at

The recovery, ordered by what it costs you to undo

Menu names vary by phone maker and OS version; the iPhone paths below are Apple’s own wording, and the Android ones are described generically because the labels differ across Samsung, Pixel, Motorola and the rest.

1. Give the carrier settings time to land. They are a separate download on the carrier’s schedule, not part of the OS image. Leave the phone on Wi-Fi and on for a while before doing anything drastic.
2. Airplane mode, properly. Apple’s own first step is airplane mode on for at least 15 seconds, then off. The 15 seconds is not superstition; it gives the radio time to fully detach before it re-attaches.
3. Restart. Apple lists it second, and on Android it is the event that rebuilds carrier configuration from the SIM.
4. Check for a carrier settings update deliberately. Settings > General > About on an iPhone. If an update is available, you see an option to update your carrier settings; give the screen a moment to check. Remember that a mandatory update appears as an OK button, not an Update button.
5. Confirm the line is on. Open cellular settings and check that the line you actually use is enabled — updates that touch dual-SIM or eSIM configuration can leave one switched off.
6. On Android, check network mode and the VoLTE toggle. Set the preferred network type to LTE or 5G, and turn on the VoLTE calling option; on a Pixel you can reach it by searching volte in Settings.
7. Reset network settings. This is where it belongs — after the free steps, before anything destructive. It rebuilds the phone’s locally cached network and telephony state and forces a clean re-attach, which is exactly the fault class layer 2 produces. It costs you saved Wi-Fi passwords, VPN profiles and Bluetooth pairings, so write those down first. It will do nothing for a layer 4 entitlement problem, which is why people repeat it and get the same result.
8. Call your carrier from a different phone. Apple puts carrier contact alongside the on-device steps, not after a reset: confirm the account is active and in good standing, that there is no outage where you are, and that the device is not blocked or barred from cellular service. Say this: "My phone lost service right after an OS update. Can you confirm the line is provisioned, and re-push the IMS entitlement and carrier settings for this device?" That sentence names the thing they can actually change.

Where the internet’s favorite advice goes wrong

Every result on page one ends the same way: factory reset, or run the vendor’s repair tool. The reset is nearly always the wrong move — it costs you an hour and your app state, and it does not touch the carrier settings bundle your carrier controls or the entitlement record on their server.

It can also strand you. On an iPhone, the erase flow at Settings > General > Transfer or Reset > Erase All Content and Settings asks you to choose between "Keep eSIM and Erase Data" and "Delete eSIM and Erase Data," and Apple states that if you erase your eSIM you need to contact your carrier to reactivate your cellular plan. Apple is blunter on the dedicated page: if you erase an eSIM, you will need to contact your carrier to get a new one, and you should not erase an eSIM for troubleshooting unless your carrier tells you to. On a phone with no service, "contact your carrier" is not a step you can take from that phone.

If you ever do reach that screen, choose to keep the eSIM.

What this page cannot tell you

It cannot tell you which layer failed on your specific handset, because none of them expose a clean error. The phone shows the same two words — No Service — whether the carrier settings are stale, the entitlement record is wrong, or the account was suspended for an unrelated billing reason on the same day you happened to update. The symptom table narrows it; only your carrier can confirm layers 2 and 4 from their side.

It also cannot promise that the mismatch is fixable today. When a new OS build is genuinely ahead of a carrier’s bundle, the fix is the carrier shipping an updated bundle, and that is on their schedule. And if the trouble did not actually start with an update — if you are reconstructing the timeline after the fact — you are probably in a different problem entirely, and the generic ordered checklist is the better starting point.