Does restarting actually help?

Often yes, because a restart forces a full re-registration on the network. Try airplane mode for 15 seconds first, then one full restart if needed. Repeated restarts rarely add anything.

Restarting the phone is usually the first suggestion the team offers when an eSIM profile refuses to connect, and it sounds too simple for many people to believe it genuinely helps. This page explains why a restart works in many cases, which type to try first, which cases a restart cannot fix at all, and what to check both before and after every restart.

It suits anyone currently facing a connection problem mid-trip who wants to try fixing it themselves before contacting the team, as well as anyone who wants to understand the reasoning ahead of time, so as not to waste time trial-and-erroring once already abroad.

Why restarting genuinely helps

When a phone connects to a mobile network, it holds the registration state in the modem's temporary memory. If that state gets stuck in an incorrect way for any reason — switching lines too quickly, or travelling across coverage areas fast enough to confuse the modem — a restart clears that state entirely and forces the phone to re-register with the network completely from scratch.

That is why a restart so often fixes a 'no service' problem even when the profile is installed correctly and the plan has not expired, because in many cases the fault is not the profile at all, but a temporary connection state stuck in the phone at that moment.

Fifteen seconds of airplane mode before a full restart

Switching airplane mode on and off again within roughly fifteen seconds is a lighter step than a full restart, but works on the same principle: it cuts all network connections briefly, then makes the phone re-register the instant airplane mode is switched off, without powering the whole phone down and back up.

Always try this first, since it is faster and does not disturb other apps left open. If the symptom persists, move on to one full restart instead. A full restart clears state at a deeper level, since it restarts the whole operating system rather than just the networking component.

How to restart properly

1. 1Try airplane mode firstSwitch airplane mode on, wait about fifteen seconds, then switch it off again. Check whether the destination network name reappears with signal bars.
2. 2If it persists, do one full restartPower the phone down completely and switch it back on using that model's own method. The button and hold duration vary by manufacturer and model, so check the phone's manual if unsure.
3. 3Wait for registration to finishAfter switching on, give it a moment to search for and complete registration with the network. Do not conclude it failed if only a few seconds have passed since it powered back on.
4. 4Check the network name and data statusCheck that a destination network name shows with signal bars, and that data roaming for that line is still switched on. If both are in order and it still does not work, consider a cause other than the restart itself.

Cases where restarting genuinely fixes it

A restart usually works when the phone has just travelled across coverage areas, such as landing off a flight while the phone is still stuck trying to find the network from the home country, or when the eSIM line has just been switched on for the first time and the phone has not automatically moved to connect it. It also helps when the primary line has been toggled back and forth between the physical SIM and the eSIM several times, leaving the modem stuck on an old state.

In every one of these cases, the profile and the plan itself have no problem at all. What went wrong is only the temporary state on the phone at that moment, so a restart genuinely fixes the right thing without touching the profile in any way.

Cases where restarting cannot help at all

If the phone does not support eSIM at all, or is carrier-locked, no number of restarts will help, since the restriction sits at the hardware level or in the original operator's own setting, not in a temporary state a restart can clear. The same applies when the plan's data allowance has run out or the plan has expired, which is a plan-condition issue, not a connection issue.

If data roaming on the eSIM line was left switched off, or a different line was accidentally set as the primary line for data, a restart will not help either, since that is a setting that needs fixing directly in the phone's own menu. Restarting only confirms the same incorrect setting all over again.

Checking settings before restarting saves time

Before restarting, it is worth opening the mobile network menu briefly to check whether data roaming for the eSIM line you want is switched on, and whether it has been set as the primary line for data. The menu's exact position varies by manufacturer and operating system version, but it generally sits under the mobile network or SIM settings section.

Checking these two things first takes under a minute and immediately tells you whether the problem is a setting you can fix right there, or a connection state that genuinely needs a restart, saving you from restarting first only to discover data roaming was simply switched off.

If the problem remains after restarting

If both airplane mode and a full restart have been tried and the symptom is unchanged, the next step is to check whether the phone is genuinely in an area where the destination network has coverage at all, since some areas still have dead spots. Try moving to a more open location first.

If moving location does not fix it, save a screenshot showing the network name, the data roaming status, and the time the problem occurred, then contact the team with your order number, so they can check the system-side status against what the phone is showing.

Before you restart, check these

• Whether data roaming on the eSIM line is switched on
• Whether the correct line is set as the primary line for data
• Remaining data allowance and the plan's expiry date
• Whether the current location genuinely has coverage
• Whether lines or SIMs have been toggled frequently in the last few minutes

Restarting is not the same as resetting network settings

A restart merely switches the operating system off and back on, without touching any saved settings. Resetting network settings is a far heavier step, since it erases every saved Wi-Fi password, forgets every paired Bluetooth device, and clears any custom APN configuration set beforehand. It is not a step to take simply because an eSIM profile is not connecting.

Always try airplane mode and a full restart in full first, and treat resetting network settings as a genuine last resort only, after every other cause has been checked and none found. It is worth consulting the team before taking this step, since the original settings cannot be recovered once it is done.

Crossing several countries in one trip, do you need to restart at every border

Not necessarily. Most phones register with the new network automatically once they cross into a country the plan covers, especially with a regional plan that uses one profile across several countries. But when crossing borders quickly by car or train, the phone can sometimes stay stuck on the previous network a little longer than usual.

If the network name still shows the previous country for an unusually long time after crossing the border, try fifteen seconds of airplane mode first, then a full restart if it still has not changed — the same approach used for every other connection issue on this page.

Does a restart fix a specific app, or only the overall connection

A restart primarily fixes problems at the network-connection level, not a problem specific to one particular app. If one app fails to work while other apps connect to the internet normally, that problem more likely sits with the app itself rather than the eSIM line's network connection, which is a separate matter from what this page covers.

A simple way to tell the difference is to open a web browser or another app and see whether it loads normally. If it loads fine and only one particular app has trouble, try closing and reopening that app, or checking its own specific settings, rather than restarting the whole phone.

Does a low battery affect the connection

Some phones automatically switch on a battery-saving mode once charge runs low, which can limit background activity for certain apps or turn off automatic data refresh, but it generally does not directly cut the mobile network connection itself. If you notice no signal alongside a very low battery, try charging the phone for a short while first and see whether the symptom changes, to rule out battery-saving mode as the cause.

If the battery returns to a normal level after charging and the no-signal symptom remains exactly the same, go back to the airplane-mode and restart steps recommended above, since that confirms the cause was never the battery in the first place.

See the step-by-step eSIM install guide

Contact the team if it is still not fixed

What a restart touches, and what it leaves alone

Most people treat a restart as a universal remedy: data stops flowing, so they power the phone off and on and hope the problem sorts itself out. In reality a restart has a very specific scope. It clears the temporary state held in the modem and in the operating system, then forces the device to search for a network and register from scratch. It is genuinely good at fixing stuck-state symptoms, such as a handset still clinging to the network of the country you have just flown out of, or a modem that has registered but never opened the data channel. What it cannot do is change a setting you configured incorrectly. If you set the Thai SIM as your data line and left the eSIM line's data switched off, a restart will faithfully restore that same wrong configuration every single time.

Separating the two matters, because it tells you when a restart is worth doing and when you should stop restarting and start reading menus. If the symptom appeared right after you changed location, crossed a border, or came out of airplane mode, stuck state is very likely and one restart is well spent. If instead the symptom has been there since the second the profile finished installing, and the device has never once had data from this plan, a restart is rarely the answer, because there is no good state to return to. Something is either configured wrong or the plan is not yet ready on the supplier's side.

How long to wait after boot before judging the result

A mistake more common than not restarting is judging the restart too quickly. The screen coming back does not mean the modem is ready. After boot the system still has to wake the radio, scan the bands available in that spot, choose a network the profile is entitled to use, and then negotiate data rights. Where signal is strong this can finish in tens of seconds. In a crowded airport terminal, on an underground train, or anywhere the signal is weak, it can take considerably longer. Many people see an empty signal bar for thirty seconds, conclude the restart failed, and press restart again, which throws away a process that was about to succeed and starts it over.

A workable approach is to give the device at least two to three minutes after boot, leaving the screen on and not toggling anything in the meantime. While you wait, watch two things. First, the network name in the status bar: if a local network name appears, registration succeeded and only data rights remain in question. Second, the data connection type indicator: a network name with no data indicator points at the data-side configuration rather than at registration. Those are different symptoms with different fixes.

A sequence that actually works on landing

The minutes after the wheels touch down are when people restart most often and most chaotically: everyone is in a hurry, everyone wants to message whoever is meeting them, and everyone is inside a building where thousands of handsets are competing for the same masts. The sequence below is designed to be done once, without cycling back and forth, and to give each step enough time to produce a real result.

1. 1Turn off airplane mode as usual and wait quietly for a minuteDo not open any app and do not press anything. Let the handset scan and choose a network by itself. Many devices connect at this stage without any restart at all. If a local network name appears and data works, you are done and the remaining steps are unnecessary.
2. 2Confirm the line selected for data is the travel plan's lineBefore restarting, open the device's network or SIM menu and check which line is set as the data line. Menu locations differ by manufacturer and OS version, but every device has somewhere to choose the data line. This takes under twenty seconds and rules out the single most common cause.
3. 3If nothing arrives, cycle airplane mode once for fifteen secondsSwitch airplane mode on, count a genuine fifteen seconds rather than tapping off and on in one motion, then switch it back off and wait another minute. This step is lighter and faster than a full restart and resolves most stuck-state symptoms just as well.
4. 4Do one full restart, then allow three minutesPower the device fully off, wait a couple of seconds, then power it on. Once you reach the home screen, do not rush to test. Give the modem time to register, and walk somewhere more open if you are in a part of the building with poor coverage.
5. 5Test with something that does not rely on cacheDo not use a chat app that loads old messages from local storage as your indicator. Open a website you have not visited on this trip, or run a fresh search in the browser. If it loads, the connection is real. If it fails while the chat app looks alive, you are reading cached content.
6. 6If it still fails, stop pressing and collect evidenceOnce one restart has failed, a second rarely improves the odds. Take screenshots of the status bar, the data line menu, and the network selection screen, then send them to us on LINE at https://lin.ee/skDPoNx or by email to esimonline.asia@gmail.com along with your order number.

Toggling the line instead of restarting the whole device

There is a middle option people overlook: switching the travel plan's line off and on without powering down the whole device. Every operating system's SIM or network management menu has a per-line on/off switch. Turning that line off and back on forces only that profile to re-register while the other line and the rest of the system keep running. The benefit is that you do not lose the connection on your Thai line, which may be receiving verification messages, and you do not wait through a full boot.

In practice the most time-efficient order is: cycle airplane mode first, then toggle the individual line, and only then do one full restart. The three steps run from light to heavy and each covers a different group of symptoms. Jumping straight to a full restart is not wrong, but it costs more time and makes the result harder to read, because after a reboot everything changes at once and you cannot tell what actually helped.

Dual-SIM handsets and the settings that revert after a restart

On handsets running two lines at once, restarting has a side effect people rarely anticipate: some defaults may revert to what the system has stored rather than what you just selected. A common example is choosing the eSIM line for data at the airport, restarting, and finding after reboot that data has gone back to the Thai SIM because that was the saved default, or that an automatic data-switching feature has picked the line it believes is better. The result is that you restarted to fix a problem and recreated the original one.

The fix is not to avoid restarting but to re-check afterwards, every time. It takes ten seconds: open the SIM or network menu and confirm the data line is still the one you want. If your device offers automatic data switching, turn it off while travelling, because that logic is designed for two lines in one country, not for a situation where one line is abroad and the other should not be used at all.

• After a restart, confirm the data line is still the travel plan's line
• Confirm that line's enable switch is still on and was not turned off while you were in the menus
• Confirm data roaming for that line is still on if the plan requires it
• Confirm the device is on a local network rather than stuck on the previous country's network name
• Confirm a low-battery power saving mode has not switched on and started limiting background connectivity
• Test with a fresh web page, not an app that can load old content from local storage

Restarting after an operating system update

An operating system update is one of the few situations where an extra restart is genuinely justified. After a major update, menu locations may move, option names may change, and settings related to lines and data are sometimes reset to that version's defaults. If you update mid-trip and lose data, the answer is not repeated restarts but walking through the menus again as though setting the device up for the first time, because what changed is software, not temporary state.

The most direct advice is not to update your operating system mid-trip unless you must, and especially not on a travel day or the night before a flight. If you are going to update, do it at home while wifi and your main SIM still work normally, so that if something goes wrong you have a fallback connection for looking up fixes and contacting us. Abroad, with data already down, an update adds complication you do not need.

Restarting while a hotspot is running

If you are sharing data with other devices and restart the host phone, the hotspot goes down with it, and on many handsets it does not come back automatically after boot. The devices that were connected, whether a tablet, a laptop, or someone else's phone in your group, will keep looking for a network name that is no longer there, and some will automatically fall back to whatever public wifi is nearby. The result is that after the restart you may believe data is still down when the real issue is that the hotspot has not been re-enabled.

Before restarting the phone acting as the hotspot, tell the others in your group and switch the hotspot off yourself so their devices stop trying to reconnect. Then restart. Once the host has booted and you have confirmed it genuinely has data, turn the hotspot back on. This order lets you test one thing at a time instead of guessing whether the problem lies with the plan or with the sharing.

Places where the result cannot be read

The outcome of a restart depends on the signal conditions exactly where you are standing, more than most people expect. Restarting where the signal cannot reach produces nothing, and you then wrongly conclude the plan does not work. The table below collects situations that come up often while travelling, with what to do instead of pressing restart again.

Devices other than your main phone

If you installed the plan on a tablet, a spare phone, or another eSIM-capable device, the restart principle is the same but the details differ. Devices not designed primarily for telephony often have simpler network menus, and some models lack options a phone has, such as manual network selection. A restart on such a device therefore does less, and if it does not work the remaining options are usually limited to checking settings and asking for help.

Another point of confusion: if your main phone has data but the tablet does not, the problem is almost never the plan, because one plan is tied to the profile installed on one device. If you want the tablet online too, the direct route is to share a hotspot from the main phone rather than restarting the tablet repeatedly. Before buying a plan for a secondary device, check that the device genuinely supports eSIM.

Check whether your device supports eSIM before buying

What to record before and after a restart so we can help faster

When someone messages us saying a restart did not help, the thing that slows our reply most is not knowing what state the device is in. The phrase no internet covers several different symptoms, from no network name at all to a full network name with a data indicator that still will not load a page. Those two need completely different fixes, so a single screenshot saves several rounds of questions.

Send us your order number, the country and city you are in right now, a picture of the status bar showing the network name, a picture of the menu showing which line is set for data, and a picture showing that line's roaming status. If data was working and then stopped, tell us when it stopped and what happened just before, such as crossing a border, updating the device, or changing a setting. That set of details is usually enough for us to point at the cause in one message.

Send us the details and we will look

When restarting turns into a loop

There is a behaviour pattern we see constantly: five restarts in ten minutes, each with under a minute of waiting, followed by the conclusion that the plan does not work. The problem is not only the wasted time. It destroys the information needed for a diagnosis, because the device is never left alone long enough to show how far it gets, and when you message us you cannot say what appeared after each restart.

A rule that works is one full restart per change. If you altered a setting and then restarted, see that change through before altering anything else. If you changed nothing, a second restart is nearly identical to the first because every condition is the same. What should change is where you test, or which setting you have not yet checked, not how many times you press the button.

A restart and the state of your plan are different things

One last point people miss: a restart tells you nothing about the state of your plan. If the data allowance is used up, or the validity period has ended, the device may still register on a network normally and display a full network name while no page will load. That symptom looks so much like a connectivity fault that people restart repeatedly without realising the cause lies elsewhere.

Before the next restart, ask yourself how much data you have used and when this plan's validity started. How you check the remaining allowance depends on the supplier behind that plan: some provide a status page, others require us to check on the back end. If you are unsure, message us with your order number rather than restarting endlessly to fix a problem that may not exist.