Vietnam eSIM Not Working? A Non-Destructive Setup and Network Checklist

If a Vietnam eSIM is not working, do not delete it first. Record the exact error, confirm that the profile and line are still present, then check the selected data line, mobile data, roaming instruction, and network registration in that order. Restarting, toggling Airplane Mode, or briefly turning a line off and on are reversible checks; QR reissue, deletion, and factory reset are escalation steps.

First: Preserve evidence and the installed profile

Before changing settings, capture:

• the exact error message and a screenshot;
• phone model, OS version, and country/region of purchase;
• whether the eSIM is visible under Cellular/SIM settings;
• whether the home SIM is still visible;
• the time and location of the test, with Wi-Fi on or off;
• the order/reference identifier, without posting the QR code or activation credential.

Do not scan the same QR repeatedly, delete the line, reset the entire phone, or erase network settings while you are still collecting evidence. Whether a QR can be reused, whether a deleted profile can be reinstalled, and whether a provider can reissue credentials are provider policies. This page does not infer those policies.

Identify the failure stage

What you see	Likely stage	Safe next check
No eSIM/profile appears	Download or installation	Confirm the device supports eSIM and that the install flow completed; keep the credential private
Profile appears but line is off	Enablement	Turn on that line once, then recheck the status bar
Line is on but “No Service”/“SOS”/“Searching” appears	Network registration	Airplane Mode, restart, then check provider/account and local availability
Signal appears but webpages fail	Data path	Select the travel line for mobile data; check the provider’s roaming/APN instructions
Some apps work and others fail	App or account path	Test a browser, check app mobile-data permission, and distinguish app login/OTP from connectivity
It worked, then stopped	Allowance, validity, setting, or network change	Check the provider’s current plan status and phone data counter before changing the profile

Step 1: check line and data selection

On iPhone, open Settings > Cellular and confirm the travel line is listed and Turn On This Line is enabled. Under Cellular Data, select the travel line and turn off Allow Cellular Data Switching while troubleshooting. On Pixel, open Settings > Network & internet > SIMs, confirm the travel line is present, Use SIM is enabled, and Mobile data is assigned to it. Samsung and other Android devices use equivalent controls under SIM manager; labels vary.

With Wi-Fi off, look for a cellular data indicator and load a small webpage. If the home line’s data counter increases instead, the problem is line selection, not necessarily the eSIM profile. Re-enable Wi-Fi after the small test to avoid unnecessary data use.

Step 2: try reversible reconnection checks

Do one check at a time and record the result:

1. Turn Airplane Mode on for at least 15 seconds, then turn it off. Apple recommends this for “No Service” or “Searching.”
2. Restart the phone.
3. Move outdoors or to a different location and wait briefly for registration.
4. On iPhone, open Settings > General > About and accept a network-provider settings update if one is offered.
5. On supported Pixel devices, use the built-in mobile-data diagnostic if available.

These steps reconnect radios or refresh settings; they do not prove that a provider plan is active or that a location is covered. Apple’s eSIM troubleshooting guide and Apple’s “SOS, No Service, or Searching” guide are the primary iPhone references. Google’s Android connection checklist documents restart, Wi-Fi/mobile-data comparison, and Airplane Mode checks.

Step 3: check roaming and APN without guessing

Some travel plans require data roaming; other plans do not. Follow the provider’s current written instructions for the travel line only. Do not enable roaming on the home line as a generic fix. Apple explains where Dual SIM roaming is configured in About cellular data roaming.

If the provider gives an APN, compare the displayed APN with that exact value and save only the documented value. An APN is not universal: Google describes it as a setting that helps an operator provide the correct IP address and connection. Do not copy a Viettel, home-carrier, or internet-forum APN into a different service. If no controlling APN instruction exists, leave the field unchanged and escalate rather than inventing one.

Likewise, do not force a manual network selection unless the provider or device manufacturer specifically instructs it. Automatic selection is the safer baseline while the cause is unknown.

Step 4: separate service, app, and account problems

Run three small tests:

1. A browser page with Wi-Fi off.
2. A second app that does not require a login.
3. The affected app after confirming its mobile-data permission.

If the browser works but a bank, messaging, employer, or social app does not, the issue may be the app account, regional policy, verification method, or server—not the eSIM’s internet path. An eSIM does not by itself guarantee a phone number, cellular voice, SMS, OTP, banking access, VPN/SSO access, or any particular app’s behavior. Do not claim that a data connection will receive an OTP.

Step 5: check allowance and validity using provider evidence

Use the provider’s current order page, app, or terms to check remaining allowance, validity dates, activation trigger, throttling/post-cap rules, and any outage notice. The phone’s usage counter is useful for a local estimate but may not match the provider’s accounting; Google notes that carriers can measure usage differently. No Kovitel quota, reset time, post-cap behavior, activation trigger, APN, manual-network rule, QR reuse/reissue policy, or support response time is stated in this draft because those fields remain product-verification gates.

Escalation packet

Escalate only after the reversible checks above. Send the provider:

• order/reference identifier;
• device model and OS version;
• country/region of purchase;
• screenshot of the error and SIM settings (redact QR credentials);
• exact time, location, Wi-Fi state, and whether the line had signal;
• steps already tried and their outcomes;
• EID/IMEI only through the provider’s secure channel when requested.

Ask a precise question: “Is this profile active, and what is the approved recovery path for this exact error?” Do not ask for or publish a support SLA unless the provider has documented one. If the provider says a reissue is required, follow that written policy; do not delete an installed profile before understanding what will happen to the original.

Last-resort actions and their consequences

Network-settings reset can remove saved Wi-Fi, Bluetooth, VPN, or cellular preferences depending on the phone. It is not the first step and should be used only when the manufacturer or provider recommends it. A factory reset erases device data and is outside ordinary eSIM troubleshooting. Deleting an eSIM can make reinstall or reissue dependent on the provider’s policy. Document consent and a backup before any destructive action.

For a complete clean install, use the install and activate guide. For data planning after service is restored, use the reproducible data calculator. The Internet in Vietnam pillar compares eSIM, local SIM, roaming, and Wi-Fi neutrally.

Sources, method, and limitations

Reviewed 3 September 2026 against Apple—If you can’t set up an eSIM, Apple—SOS, No Service, or Searching, Apple—Cellular data roaming, Google—Fix internet connection problems, Google Pixel—Mobile network settings, and Google Pixel—Fix mobile connectivity. Manufacturer instructions control device UI; provider documentation controls plan, QR, APN, registration, allowance, and escalation behavior.

Menu names and available diagnostics vary by model, OS version, region, and carrier. Network registration can also change with location, congestion, outages, and radio compatibility. This checklist is designed to preserve the profile and evidence; it cannot guarantee service or diagnose a provider-side account issue without provider access.