Troubleshooting
eSIM Not Working? US Carrier Fixes for iPhone & Android (2026)
Carrier-agnostic steps when eSIM activation, transfer, or data fails on US phones—before you open a ticket with your MVNO or national carrier.
- Updated
- 2026-05-08
- Reading time
- 14 min
TL;DR
Most eSIM failures are line-selection, provisioning cache, or SIM-manager settings—not broken hardware. Use a short checklist, then branch to carrier-specific guides when basics fail.
- Toggle airplane mode, confirm the intended line is default for data, and reboot before assuming the eSIM profile is bad.
- Dual-SIM phones often look “broken” when the wrong SIM owns mobile data or calls.
- QR and SM-DP+ errors usually need a clean Wi‑Fi attempt, profile removal, and a fresh activation—not a new phone.
- Escalate to carrier support with IMEI, error text, and whether the line is port-in or transfer.
Sixty-second sanity checks
| Check | iPhone | Android |
|---|---|---|
| Radio reset | Control Center → Airplane on 30s → off | Settings → Network → Airplane toggle |
| Data line | Settings → Cellular → Default Voice / Data | Settings → SIMs → default data SIM |
| Wi‑Fi for setup | Stay on Wi‑Fi during QR / SM-DP+ | Same—avoid captive portals |
| Unlock status | Settings → General → About → Carrier Lock | Settings → About / carrier unlock tools |
If calls work on one line but data does not, you usually have a default-data problem, not a dead tower. On dual‑eSIM setups, see Best MVNO iPhone dual eSIM (2026) for how people partition work vs personal lines.
Symptoms → Likely causes
| What you see | Common causes | Try this next |
|---|---|---|
| QR invalid / expired | One-time use, email delay, screenshot compression | Request a fresh QR from carrier; scan from original email |
| Stuck on “Activating…” | SM-DP+ backlog, iOS cache | Airplane toggle; reboot; retry once on Wi‑Fi |
| Profile installed, no signal | Wrong line selected, outage, incompatible IMEI | Confirm default line; check carrier status page |
| Transfer from old carrier hangs | Old carrier has not released number / eSIM | Finish release on old account; see porting guides |
For Google Fi provisioning quirks (Pixel vs iPhone), use Google Fi eSIM activation failed after the generic steps here.
iPhone-specific notes
Apple’s flow centers on Settings → Cellular: each eSIM is a plan with its own toggles for mobile data, default voice line, and data roaming. If you recently transferred from Verizon to a T‑Mobile‑based MVNO, iPhone 17 eSIM transfer Verizon to Mint covers transfer-friction patterns that masquerade as “eSIM broken.”
Android-specific notes
OEMs label SIM managers differently (Connections → SIM manager, Network & Internet → SIMs). Confirm mobile data, calls/SMS default, and roaming per SIM. Pixels integrating Google Fi should follow Fi’s official eSIM article in Sources—the Fi app and system settings must agree.
When to call carrier support
Escalate when you have repeated SM-DP+ failures, confirmed unlocked IMEI, and clean Wi‑Fi, or when a port is stuck beyond the carrier’s stated window. Have IMEI2 (eSIM), ICCID if shown, screenshots of errors, and whether the line is new vs port vs transfer.
Visible customers can pair this hub with Visible port number step-by-step if the failure happens mid-port.
Disclaimer
Carriers change provisioning flows without a public changelog. This article is educational, not a substitute for Apple, Google, or your carrier’s current support articles. Links can move—verify on the official domain before you rely on steps for billing decisions.
FAQ
Short answers; details are in the article above.
- Connect to stable Wi‑Fi, toggle airplane mode for ~30 seconds, confirm the device is unlocked for your target carrier, then retry activation from the carrier’s app or QR flow. If it still fails, remove the pending eSIM profile (when the carrier allows) and start once—not multiple rapid retries.
- Open SIM settings and verify that mobile data, roaming (if your carrier requires it), and the correct default data SIM are enabled. Some MVNOs also depend on automatic APN provisioning; a network settings reset may be needed after a failed first attempt.