"SIM Not Provisioned" After a Reset: The Cause (Almost) No One Explains, and How to Recover Your eSIM
You just reset your phone — maybe to free up space, fix some lag, or move to a new device — and when it restarts you see "SIM not provisioned" where your connection used to be. No calls, no data, no network. If you've already tried restarting, removing and reinserting the SIM, or toggling airplane mode on and off with no luck, you're not alone: this is one of the most frequently reported errors in Samsung and eSIM user communities after a reset, and the real cause often has nothing to do with your carrier. In this guide we'll look at what this message actually means, why a simple reset can "wipe out" a perfectly working eSIM, and how to get back online step by step.
"Provisioning" refers to the process by which your carrier formally authorizes a SIM card — physical or eSIM — to use its network for calls, texts, and data. It's essentially the official permission that links your number and data profile to your specific device.
When your phone shows "SIM not provisioned," it's saying that link doesn't exist, or no longer exists: the network doesn't recognize the SIM as authorized, so it blocks every service. It doesn't necessarily mean the SIM is broken or the plan has expired — it just means the active authorization is missing at that moment.
What it meansYes, and telling them apart helps you know where to look for a fix. "No network available" usually points to a coverage or signal issue in your area: the SIM is fine, but the signal is missing. "SIM not valid" more often points to a physical problem with the card (damaged, incorrectly inserted, incompatible) or a lock set by the phone itself.
"SIM not provisioned," on the other hand, is a "system-level" error: the phone and the SIM communicate normally, but the carrier's database doesn't recognize that SIM as active on its network. That's why restarting the phone or cleaning the SIM contacts — while a sensible first step — often doesn't fix it on its own.
Telling the errors apartIt affects both. "SIM not provisioned" is a generic message that the operating system shows regardless of the type of card involved: it can appear with a physical SIM you just inserted, or with an eSIM profile that's been installed for weeks.
The important difference lies upstream, in the cause: a physical SIM rarely "disappears" on its own, while an eSIM profile can be removed by a phone reset, a software update gone wrong, or a failed device transfer — exactly the scenario at the heart of this guide.
Physical SIM vs. eSIMOn some Android devices, instead of the plain "SIM not provisioned" message, you may see the more technical code MMCC_IMSI_UNKNOWN_IN_HLR. Don't worry — it's the exact same issue, just described in the system's internal language.
The IMSI is the code that uniquely identifies your phone line; the HLR (Home Location Register) is the carrier's registry where that code should show up as active. When the message says the IMSI is "unknown in the HLR," it's flagging exactly the same missing authorization described by "SIM not provisioned" — just with a more technical name.
HLR technical errorA physical SIM sits on a card that stays in the phone even during a reset: the reset wipes apps and settings, but doesn't touch the piece of plastic in the tray. An eSIM profile, by contrast, isn't a physical object — it's a set of encrypted data stored in the phone's internal memory, in the exact same "space" a factory reset is designed to wipe clean.
For this reason, if the reset doesn't specifically handle eSIM profiles before proceeding, the most common outcome is that the eSIM gets deleted along with everything else — and on restart, finding no authorized profile left, the phone shows exactly "SIM not provisioned."
Why the eSIM disappearsThese are two very different operations, often confused because their names sound similar. "Reset network settings" (or "Reset Wi-Fi, mobile data & Bluetooth") only clears connectivity configurations — saved Wi-Fi networks, paired Bluetooth devices, some APN settings — but normally leaves installed eSIM profiles untouched.
A full factory reset, on the other hand, wipes the phone's entire memory to bring it back to a "first boot" state: apps, photos, accounts, and — unless specific protection features are used — eSIM profiles too. If the connection is still missing after a network reset, the problem is likely elsewhere; if the error appears after a full reset, a deleted eSIM profile is the prime suspect.
Network reset vs. full resetOn more recent models — iPhones on iOS 17 and later, and the latest Samsung and Pixel devices — a factory reset actually offers an option to keep eSIM profiles during the process. When available and selected correctly, it's the simplest and most effective protection against this problem.
The catch is that this option only appears when the reset happens "normally," from the settings menu with the phone powered on and working. If the reset is instead performed in recovery mode, through a PC/Mac restore (such as a DFU restore), on a locked device that's no longer responding, or remotely through an enterprise device management system (MDM) or an anti-theft feature like "Find My Device," the phone has no way to ask you anything: it wipes everything, eSIM included, with no choice offered.
The limits of "keep eSIM"Almost never — and this is probably the most common misunderstanding for anyone facing this issue for the first time. Standard cloud backups are built for photos, contacts, apps, messages, and general settings: for security reasons, eSIM profiles — which contain sensitive network credentials tied to a specific device — are normally not included in these backups.
This means that even after restoring a phone from a full backup, it's completely normal to still find the eSIM missing, with "SIM not provisioned" appearing on restart: the backup did its job on everything else, but the eSIM needs to be reinstalled separately, as explained further in this guide.
Cloud backups and eSIMBefore assuming the worst, it's worth ruling out the simplest causes: restart the phone, then toggle airplane mode on and off to force a new attempt at connecting to the network. Also make sure you have a stable Wi-Fi connection available, since you'll need it for any eSIM reinstallation.
If you have a dual-SIM device and the message specifies "SIM 2 not provisioned" (or an equivalent number), it's simply indicating which of the two cards is affected — useful for quickly understanding whether the issue involves your travel eSIM or your primary line.
First things to tryIf you kept the screenshot, email, or PDF with the QR code you received at purchase, you can try reinstalling the eSIM exactly as you did the first time: on Android, go to Settings → Connections → SIM Manager → Add eSIM (the exact path varies slightly by manufacturer); on iPhone, Settings → Cellular → Add eSIM, then scan the code with the camera.
There's one important detail to know before trying: many eSIM QR codes are designed for single use. If the code has already been scanned successfully once, the attempt may fail with an invalid code message — this isn't a phone problem, it's simply a carrier safeguard against the same profile being duplicated across multiple devices.
Reinstalling with the original QR codeAt this point, the correct request to make to customer support is specific: ask for an eSIM reissue (sometimes also called a "replacement QR code"), explaining that the profile was lost following a device reset. Keep your order or original activation email handy, along with your phone model and, if available, the device's EID code — these speed up verification on the support side considerably.
Most carriers and travel eSIM providers handle this request at no extra cost as long as the data plan hasn't expired yet, sending a new QR code to scan in place of the original one.
Requesting a new QR codeIn most cases, reactivation is nearly immediate: once a valid QR code is scanned and installation is complete, the phone registers on the network within minutes. In some situations — especially if the profile was just reissued on the carrier's side — it may take up to a few hours for the systems to fully sync.
If the error persists after a reasonable wait, another restart of the phone is often enough to trigger a new attempt to connect to the network using the newly installed profile.
Reactivation timing• Avoid unnecessary factory resets while traveling: if your phone slows down or acts up, try a simple restart or clearing the cache first before resorting to a full reset.
• If a reset is truly necessary, always check, before confirming, whether the phone offers the option to keep eSIM profiles during the process.
• Always keep a backup copy of the QR code and activation email for every eSIM you purchase, saved in the cloud or on a second device — not only on the phone you might need to reset.
• Don't wait until the last minute to activate a travel eSIM: installing it a few days before departure lets you catch any activation issues while you're still at home, calmly, with access to customer support in your own time zone.
How to prevent the problemLike any eSIM profile, BLIVALE eSIMs follow the same rules set by the phone's operating system: if the reset deletes the eSIM data, reactivation requires the same steps described in this guide. The difference lies in the support: by keeping your order confirmation email, the BLIVALE team can quickly verify the purchase and, if needed, reissue the profile.
For anyone traveling with multiple devices to keep connected at the same time — families, work groups, or anyone carrying a tablet or laptop too — it's worth choosing an eSIM with hotspot included from the start, so you have a single reliable connection to manage instead of multiple profiles to reinstall if something goes wrong.
BLIVALE eSIM and resetsMost of the remaining BLIVALE eSIMs also offer hotspot as an available feature; however, if you're planning to use it intensively, the Unlimited Premium eSIMs remain the best choice, thanks to their design built specifically for shared, sustained use.
Conclusion
The "SIM not provisioned" error is frightening because it shows up as a blunt, technical message that seems to offer no solution — and that's exactly why so many people, after resetting their phone, end up assuming a serious fault or an unfixable carrier issue. The reality, in most cases tied to a reset, is much simpler: an eSIM profile that lived as software data was deleted along with the rest of the phone's memory, and it simply needs to be reinstalled.
Knowing this completely changes how you approach the problem: instead of chasing generic fixes from unreliable forums, the right path is to check whether the original QR code is still usable and, if not, ask your carrier or provider directly for a profile reissue. In the vast majority of cases, this process takes just a few minutes and costs nothing extra.
The most useful lesson to take away, though, is about prevention: always keep a backup copy of every eSIM's QR code, check for the "keep eSIM" option before any reset, and activate travel eSIMs a few days ahead of departure. These are three simple habits that will save you from discovering this error at the worst possible moment — right after landing, with no network and no maps to find your way.
- "SIM not provisioned" means the network doesn't recognize the SIM as authorized — it doesn't necessarily mean the card is faulty.
- A factory reset can delete an eSIM profile because it lives as software data, not as a physical object in the phone.
- The "keep eSIM" option only protects you during resets started normally from a powered-on phone: DFU, recovery mode, and remote resets delete it anyway.
- Standard cloud backups (Google, Samsung, iCloud) usually don't include eSIM profiles — these need to be reinstalled separately.
- If the original QR code no longer works (often because it's single-use), simply ask your carrier or eSIM provider for a profile reissue.
- Keeping a copy of the QR code outside the phone and activating eSIMs in advance keeps you from getting stuck exactly while traveling.
The best BLIVALE eSIMs if you use multiple devices at once: