How to Manually Select Partner Carrier Networks on Travel eSIM (Fix No Service Abroad in 2026)

---

The Telecom Mechanics of Roaming: Why Travel eSIMs Get Stuck on 'No Service'

To understand why your device suddenly drops off the grid in a foreign airport, you have to look past the user interface and into the cellular baseband stack. An international travel eSIM does not connect directly to local infrastructure as a native subscriber; it operates through an intricate web of wholesale routing protocols, roaming agreements, and over-the-air cryptographic handshakes.

When any step in this authentication pipeline desynchronizes, your smartphone’s baseband processor defaults to a state of radio paralysis—manifesting as No Service, Emergency Calls Only, or an unusable EDGE/3G connection.

`` [Device Baseband] │ (Scans RF Spectrum) ▼ [Local Cell Tower (VPLMN)] ──(RSRP Signal OK)──► [Authentication Request] │ │ ├── Has Wholesale Agreement? ──► YES ──► [Attach Success / 5G Data] │ └── NO / Stale SoR Profile ──► REJECT (Cause #11 / #15) │ ▼ [Stuck: "No Service"] ``

---

1. PLMN Discovery vs. Physical Radio Power (RSRP)

Every cellular operator broadcasts a unique Public Land Mobile Network (PLMN) identity, consisting of a Mobile Country Code (MCC) and a Mobile Network Code (MNC)—for example, 208-01 for Orange France or 440-20 for SoftBank Japan.

Your smartphone’s internal modem is hardwired by standard 3GPP specifications to seek the highest physical radio energy—specifically the Reference Signal Received Power (RSRP) and Received Signal Strength Indicator (RSSI).

• The Problem: The tower emitting the strongest RF signal into an airport arrival lounge or across a land border is often not the carrier with which your travel eSIM provider holds an active wholesale roaming agreement.
• The Failure Mode: Your phone attempts an initial ATTACH REQUEST to the dominant local tower (the Visited Public Land Mobile Network, or VPLMN). The tower queries your eSIM's International Mobile Subscriber Identity (IMSI) against its visitor database, fails to validate a roaming clearinghouse path back to your eSIM’s Home PLMN (HPLMN), and returns an error:
• 3GPP Cause #11: PLMN Not Allowed
• 3GPP Cause #15: No Suitable Cells in Tracking Area

Instead of instantly switching to a secondary carrier, the baseband modem frequently enters a temporary back-off timer (T3245/T3212), locking the connection into No Service until forced to re-scan.

---

2. Steering of Roaming (SoR) Algorithms and Border Collisions

Travel eSIM providers deploy Steering of Roaming (SoR) protocols to maximize margin and routing performance. SoR updates the internal Preferred PLMN (PPLMN) list on your eSIM via Over-The-Air (OTA) binary SMS payloads, forcing your phone to prioritize partner networks that offer lower wholesale IPX (IP eXchange) transit costs.

When crossing international borders or landing at high-density hubs (such as London Heathrow, Singapore Changi, or Frankfurt), your device receives overlapping carrier signals from multiple PLMNs simultaneously.

If the eSIM’s SoR table has not updated over the local cell layer—or if the profile contains a stale multi-IMSI map—the baseband continuously retries access on forbidden or deprioritized frequencies, refusing to drop down to the secondary functional carrier.

---

3. Avoiding the Wholesale Roaming Handshake Trap

Modern architectures mitigate these handshake bottlenecks by deploying dynamic multi-IMSI profiles and premium IPX routing. Tier-1 providers like MollySIM engineer their eSIM profiles to negotiate direct local interconnects with low-latency breakout gateways, reducing handshake rejection rates during international cell transfers.

Furthermore, even under extreme network congestion or Fair Use Policy (FUP) thresholds, premium roaming infrastructures maintain a functional baseline. While generic travel eSIMs drop speeds to an unusable 128kbps (or cut packet routing entirely during PLMN misalignments), MollySIM sustains a 384kbps FUP floor—three times the industry average. This ensures that real-time cryptographic handshakes (like Apple Pay tokens and Google Maps vector tile rendering) complete successfully even while operating on congested roaming nodes.

When automatic carrier selection fails to resolve these routing conflicts, the only reliable solution is executing a manual PLMN override directly in your operating system settings.

Step-by-Step Guide: Overriding Automatic Carrier Selection on iPhone (iOS 18 & iOS 19)

Apple’s baseband management engine in iOS 18 and iOS 19 aggressively automates roaming handshakes, frequently trapping the device in an infinite loop with a non-responsive partner network. Forcing a direct Public Land Mobile Network (PLMN) override breaks this cycle by forcing the modem to bypass stored Steering of Roaming (SoR) lists and lock onto an operational local radio access network (RAN).

Follow these exact steps to execute a manual override on modern iOS architectures:

`` Settings ➔ Cellular (or Mobile Data) ➔ [Your Travel eSIM Profile] ➔ Network Selection ➔ Toggle Off "Automatic" ``

---

1. Navigating the iOS Core Modem Settings

1. Open Settings and tap Cellular (labeled Mobile Data in British English locales).
2. Scroll to the SIMs section and select your active international profile (e.g., labeled Travel, Secondary, or MollySIM).
3. Verify that Data Roaming is toggled ON. Without this enabled at the profile layer, manual network assignment will still fail to route IP packets.
4. Tap Network Selection.
5. Toggle the Automatic switch to OFF.

---

2. Managing the Baseband Scan Delay (The 60–120 Second Rule)

When you disable Automatic, the baseband modem suspends cached SIM profiles and initiates an over-the-air Broadcast Control Channel (BCCH) scan across all supported frequency bands (sub-6 GHz 5G NR and LTE).

• Do not leave the screen: Navigating away from the Network Selection menu causes iOS to terminate the active modem query, resetting the scan timer.
• Expect latency: A comprehensive spectrum sweep across local towers takes anywhere from 60 to 120 seconds. A persistent spinning activity indicator is normal behavior while the device compiles the available PLMN list.

---

3. Deciphering Duplicate Network Identifiers and Phantom Carriers

Once the scan concludes, iOS renders a list of available carriers broadcasting in your immediate sector. You may encounter identical carrier names or generic numeric strings (MCC-MNC pairs such as 440-10 or 208-01).

• Duplicate Names (e.g., two "Vodafone" or "Orange" entries): This occurs when a carrier broadcasts distinct Core Network nodes for legacy LTE versus 5G Standalone (5G SA), or operates shared RAN infrastructure (e.g., MOCN architectures). Select the first entry; if your data pipeline fails to initialize within 30 seconds, tap the second entry.
• Numeric Strings: These represent networks whose alphanumeric network names are unmapped in Apple's local carrier bundle database. Avoid selecting numeric strings unless confirmed as an authorized partner.

---

4. Selecting Tier-1 Partner Networks for Travel Profiles

Select the verified Tier-1 infrastructure partner for your destination. Premium providers engineer direct wholesale interconnects to guarantee maximum bandwidth allocation and low-latency packet routing.

If you are using a high-throughput provider like MollySIM, manually locking onto these Tier-1 carriers routes your device directly through low-latency local IPX tunnels. Furthermore, even if you exceed standard data caps during heavy roaming sessions, MollySIM preserves an industry-leading 384kbps Fair Use Policy (FUP) baseline—triple the standard 128kbps throttle enforced by legacy providers. This ensures mission-critical services like Google Maps navigation, Apple Pay authentication, and VoIP messaging remain fully functional without dropped packets on your selected network.

Once selected, wait 15 seconds. The signal bars in the iOS status bar will refresh, displaying the chosen carrier name alongside the active 5G or LTE data indicator.

Step-by-Step Guide: Manual Network Selection on Android (Samsung One UI & Google Pixel)

Unlike iOS, which abstracts the Radio Interface Layer (RIL) behind simplified toggles, modern Android environments (Android 15 and Android 16) expose granular cellular controls. However, OEM skins split these settings across divergent menus.

Because Android handles Dual SIM Dual Standby (DSDS) by assigning separate baseband hardware instances to each SIM slot, you must ensure you are strictly modifying the radio parameters of your Travel eSIM slot—leaving your primary home SIM voice and SMS channels uninterrupted.

---

1. Samsung Galaxy Devices (One UI 6.x / One UI 7.x)

Samsung isolates carrier routing within the "Mobile networks" sub-layer rather than the primary SIM Manager.

`` Settings ➔ Connections ➔ Mobile networks ➔ Network operators ``

`` ┌────────────────────────────────────────────────────────┐ │ 1. Open Settings ➔ Connections │ │ 2. Tap "Mobile networks" │ │ 3. Tap "Network operators" │ │ 4. Select your Travel eSIM tab at the top/bottom │ │ 5. Toggle OFF "Select automatically" │ │ 6. Wait 30–90 seconds for the PLMN broadcast scan │ │ 7. Choose your verified Tier-1 roaming partner │ └────────────────────────────────────────────────────────┘ ``

1. Open Settings and tap Connections.
2. Tap Mobile networks (do not enter SIM manager for this specific step).
3. Tap Network operators. If prompted, select your designated Travel eSIM from the profile selector at the top.
4. Toggle off Select automatically.
5. A confirmation dialog will warn you that searching for networks may take several minutes. Tap OK.
6. The modem will execute a full passive radio scan across local cell towers. Once the list populates, select the authorized Tier-1 partner carrier (e.g., NTT Docomo, EE, or T-Mobile).

---

2. Google Pixel & Stock Android (Android 15 & 16)

Google Pixel UI assigns network search parameters directly within the individual SIM profile pane.

`` Settings ➔ Network & internet ➔ SIMs ➔ [Select Travel eSIM] ➔ Automatically select network (Disable) ``

1. Navigate to Settings > Network & internet > SIMs.
2. Tap on your active Travel eSIM profile.
3. Scroll down past the roaming data toggles to the Network configuration sub-header.
4. Toggle off Automatically select network.
5. A modal prompt stating "Scanning for available networks..." will appear. Allow your Pixel’s modem to poll local cell towers (this process takes between 45 and 120 seconds).
6. A dynamic list of visible terrestrial networks will display. Tap your provider's designated local partner to initiate the radio handshake.

---

3. Resolving Android-Specific Baseband Quirks

During the manual registration process, modern Android basebands frequently encounter edge-case behaviors that require targeted troubleshooting:

``` MANUAL SELECTION SEQUENCE

[ Auto Select: OFF ] ──► [ 60s PLMN Scan ] ──► [ Select Partner Carrier ] │ ┌────────────────────┴────────────────────┐ ▼ ▼ [ Handshake Success ] [ MCC-MNC Numeric Code ] │ │ Status: 5G / LTE Active Verify Partner Database │ [ Connect Manually ] ```

When traveling with high-performance profiles such as MollySIM, multi-IMSI firmware natively directs the modem toward pre-authenticated Tier-1 radio channels, minimizing registration rejection loops. Even during periods of localized cell tower congestion or after crossing standard high-speed allocations, MollySIM maintains an industry-leading 384kbps Fair Use Policy (FUP) baseline. This provides three times the throughput of typical 128kbps legacy roaming caps, guaranteeing that data-sensitive applications—including Google Maps routing, Apple Pay and Google Wallet token handshakes, and encrypted banking authentications—remain active while your Android device locks onto the partner network.

Comprehensive Troubleshooting Matrix: Manual Carrier Override vs. APN & Hardware Errors

While manually overriding the carrier selection forces the device baseband to latch onto a specific Public Land Mobile Network (PLMN), connectivity failures abroad often stem from a misalignment between radio-layer registration and packet-data gateway negotiation. A successful handshake with a local cell tower only completes layer-1 and layer-2 radio authentication; your eSIM still requires an active Packet Data Protocol (PDP) context and valid routing rules to pass IP traffic.

The troubleshooting matrix below isolates common international data failures, diagnosing whether your issue requires a manual PLMN override, Access Point Name (APN) reconfiguration, or a baseband radio flush.

---

Step-by-Step APN & Protocol Alignment

If manual carrier selection succeeds (showing active signal bars) but web pages fail to resolve, your operating system has likely assigned an incorrect APN profile or locked the PDP context to an incompatible IP protocol.

`` [ Baseband Connected (PLMN) ] ──► [ APN Negotiation ] ──► [ PDP Context: IPv4/IPv6 ] ──► [ Data Flow ] ▲ │ │ │ ▼ ▼ Carrier Override Verify APN String Set Dual-Stack Mode ``

1. Verifying and Adding the APN

• iOS: Go to Settings > Cellular (or Mobile Data) > Select your eSIM profile > Cellular Data Network. Enter the APN string provided by your eSIM carrier into both the Cellular Data and LTE Setup fields. Leave Username and Password blank unless explicitly required.
• Android: Go to Settings > Network & Internet > SIMs > Select your eSIM > Access Point Names > Tap + (Add). Input the required APN string, name the profile, and tap the three dots to select Save. Ensure the radio button next to the newly created APN is active.

2. APN Roaming Protocol (IPv4 vs. IPv6)

Many modern Android devices default their APN roaming protocol strictly to IPv6. However, numerous foreign partner networks and legacy roaming inter-exchange (IPX) proxies still rely exclusively on IPv4 addressing for inbound roaming sessions.

• Under your APN settings on Android, locate APN Protocol and APN Roaming Protocol.
• Change both values from IPv6 to IPv4/IPv6 (or purely IPv4 if data fails to initialize). This prevents silent PDP drops and DNS resolution failures while traveling.

Baseband Radio Reset (Cold Power-Cycle)

When switching across international borders, your device’s baseband processor caches tower identifiers in its non-volatile memory (NVRAM). If manual carrier selection and APN updates fail to establish a link:

1. Turn Airplane Mode ON.
2. Wait 20 to 30 seconds—this duration forces the modem's baseband subsystem to completely de-register from the active cell stack and flush stale PLMN metadata.
3. Turn Airplane Mode OFF and allow the device to initiate a fresh handshake with your manually selected partner carrier.

MollySIM's Multi-Carrier Redundancy Architecture & Zero-Downtime Guarantee

Most budget travel eSIM providers cut wholesale costs by routing traffic through a single low-tier mobile virtual network operator (MVNO) or locking your profile to a single local Public Land Mobile Network (PLMN). If that single partner carrier experiences localized cell tower maintenance, core routing congestion, or regional dead zones, your connection drops entirely—rendering manual network switching useless because your eSIM lacks authentication keys for alternative towers.

To resolve this single point of failure, MollySIM engineers its travel profiles on an enterprise-grade Multi-IMSI and Tier-1 multi-carrier roaming architecture. This technical infrastructure guarantees that travelers maintain continuous data redundancy across multiple competing national networks within every destination.

``` Traditional Budget eSIM: [User Device] ---> [Single MVNO Roaming Profile] ---> [Single Local Carrier] (Fails = Dead Zone)

MollySIM Redundant Core: ┌──> [Local Tier-1 Carrier A (e.g., SoftBank / AT&T)] [User Device] ─── Multi-IMSI Profile ──┼──> [Local Tier-1 Carrier B (e.g., KDDI / T-Mobile)] └──> [Local Tier-1 Carrier C (e.g., NTT Docomo / Verizon)] ```

Multi-IMSI Dynamic Provisioning vs. Single-Network Lock-In

When you install a MollySIM profile, the underlying eUICC (Embedded Universal Integrated Circuit Card) downloads dynamic International Mobile Subscriber Identity (IMSI) sets backed by direct roaming inter-exchange (IPX) agreements with major national operators.

Because MollySIM authorizes access to multiple Tier-1 carriers per country, the Manual Network Selection techniques outlined in this guide function as a reliable hardware failover mechanism. If high-density pedestrian congestion saturates local 5G bands in metropolitan hubs (such as downtown Tokyo or central London), you can open your device settings, disable automatic network selection, and instantly swap to a competing local carrier's underutilized cell towers.

High-Fidelity Fallback: Why the 384kbps Standard Matters

Carrier outages are not the only risk abroad; data depletion mid-transit can sever access to critical navigation and communication apps. Standard market eSIMs frequently enforce aggressive throttling mechanisms, capping speeds at 64kbps to 128kbps once a high-speed allowance is consumed. At 128kbps, modern TLS/SSL cryptographic handshakes often time out, effectively breaking ride-share applications, secure payment authorization, and dynamic vector mapping.

MollySIM mitigates this risk by deploying an industry-leading 384kbps Fair Use Policy (FUP) fallback floor—delivering 3x the throughput of conventional travel eSIMs.

``` 128kbps (Standard Competitor FUP): [TLS Handshake] ── Timeout ──> [Google Maps/Apple Pay Failure]

384kbps (MollySIM Guaranteed Floor): [TLS Handshake] ── Success ──> [Real-Time GPS Vectors, WhatsApp VoIP, Apple Pay Active] ```

At a sustained 384kbps:

• Vector-based turn-by-turn navigation (Google Maps, Apple Maps) loads route modifications and terrain layers without gateway timeouts.
• Biometric payment tokens (Apple Pay, Google Wallet) process payment authentication handshakes smoothly at transit turnstiles and POS terminals.
• Essential transport platforms (Uber, Grab, Bolt) successfully dispatch driver locations and load dispatch telemetry.
• Compressed voice packets (WhatsApp, FaceTime Audio) sustain two-way communication without dropped voice frames.

Combined with automated Remote SIM Provisioning (SM-DP+) that dynamically updates carrier roaming tables over-the-air, MollySIM's architecture guarantees that manual partner carrier selection remains fully operational, low-latency, and redundant wherever you travel.

Pre-Flight & Transit Checklist: Maintaining Flawless Connectivity Across Borders

Achieving instant data access when the wheels touch down requires setting baseband configurations before entering foreign airspace. Mobile operating systems frequently mishandle international handshakes if the primary SIM and travel eSIM transmit competing registration requests upon disembarkation.

Follow this chronological checklist to prevent provisioning errors, eliminate accidental domestic roaming fees, and preserve device battery life.

---

Phase 1: Departure Gate Protocol (T-Minus 2 Hours)

Execute these steps prior to boarding your international flight:

• [ ] Label Profiles Clearly: Rename your cellular profiles in Settings > Cellular / Mobile Data. Label your domestic line Home/Primary and your travel line MollySIM [Destination]. This eliminates destructive configuration mistakes during transit.
• [ ] Enforce Roaming Segregation:
• Turn Data Roaming OFF on your Primary SIM to prevent pay-per-megabyte domestic carrier billing traps.
• Turn Data Roaming ON exclusively on your MollySIM profile.
• [ ] Disable "Allow Cellular Data Switching": Both iOS and Android feature automatic fallback switches. If left active, your phone will quietly switch data consumption back to your primary SIM when the foreign network signal wavers, generating massive roaming invoices.
• [ ] Cache Partner Carrier Matrices Locally: Take a screenshot of the approved partner networks and APN values provided in your MollySIM confirmation. Storing this offline in your camera roll ensures you can execute manual PLMN selection even inside subterranean transit terminals without Wi-Fi.
• [ ] Verify Frequency Band Compatibility: Check that your handset supports local spectrum allocations at your destination. Key baseline bands include:
• Europe: LTE Bands 3, 7, 20 (800MHz coverage layer) and 5G Band n78.
• North America: LTE Bands 2, 4, 12, 17, 66 and 5G Bands n41, n71, n77.
• Asia-Pacific: LTE Bands 1, 3, 8, 28 (700MHz long-range) and 5G Bands n77, n78, n79.

---

Phase 2: Landing & Baseband Power Management

When an operating system transitions from Airplane Mode in a new country, the baseband processor initiates wide-spectrum Radio Frequency (RF) sweeps. In crowded airport environments or fringe coverage terminals, continuous cell-searching drains the battery up to 25% faster while the modem cycles through rejected PLMN handshakes.

``` Modem Hunting Loop (High Battery Drain): [Search All Bands] ──> [Attempt Incompatible PLMN] ──> [Reject] ──> [Repeat RF Sweep]

Manual Carrier Lock (Optimized Baseband State): [Direct Lock to Partner Network] ──> [Instant Handshake] ──> [Low-Power RRC Connected] ```

1. Wait for Ramp-Up: Disable Airplane Mode only after the aircraft has cleared the active runway. Terminal buildings present dense Faraday shielding; allow the modem 60 seconds to scan nearby Macro Cell towers.
2. Halt Hunting Loops via Manual Selection: If your device remains stuck on "Searching..." or shows 3G/E speeds, immediately disable Automatic Network Selection and lock onto the top-tier local partner listed in your setup guide. Locking the modem directly to an authorized IMSI/PLMN pairing terminates the battery-intensive wideband search loop.

---

Phase 3: The 60-Second Field Recovery Diagnostic

If you experience zero data throughput, an invalid IP allocation, or "No Service" after landing, run this deterministic troubleshooting sequence:

Even if high-speed bucket thresholds are exceeded during transit, MollySIM keeps mission-critical tools alive with a guaranteed 384kbps FUP floor—preventing data timeouts on Apple Pay authentication, real-time Google Maps vector rendering, and encrypted transport messaging when you need them most.