Does an eSIM Work on a Jailbroken or Rooted Phone?

Usually, yes — jailbreaking or rooting doesn't disable the eUICC (the physical chip that stores eSIM profiles), so many modified phones can still install one through the phone's own Settings app. But it's genuinely unsupported: some eSIM providers detect root or jailbreak and block their own apps outright, and the modification itself can cause unrelated data and connection problems.

#What actually determines whether a modified phone can still use an eSIM?

Jailbreaking (iOS) and rooting (Android) both remove manufacturer-imposed software restrictions to gain deeper system access, which is the "modification" this question is really about. An eSIM (embedded SIM) lives on the eUICC, a certified chip soldered to the device's motherboard.

Under the GSMA's SGP.22 remote-provisioning standard, a phone's Local Profile Assistant downloads a profile from the carrier's server over an authenticated connection. The GSMA's own eSIM overview describes this as a secure download process, not a check on the phone's OS build. That's why the native "Add eSIM" flow in iOS or Android Settings often still completes on a modified phone.

What actually gets in the way is added on top, not built in: some providers' own apps run root/jailbreak detection and refuse to launch. Airalo's help center states plainly that "as a security measure, the Airalo app does not work on devices it recognizes as jailbroken or rooted."

co:sim, like most eSIM resellers, instead emails a QR code and lets the phone's own Settings complete the install, a path that generally survives root or jailbreak, unlike an app gated by Google's Play Integrity API, which flags rooted or modified devices for any app that checks it. Custom ROMs that strip carrier certificates, or a bootloader unlock that breaks the modem interface, are the cases where installation genuinely fails at the hardware level.

#Does jailbreaking void my eSIM warranty?

No — an eSIM profile is a data plan, not hardware, so it has no warranty to void. What jailbreaking does void is Apple's hardware warranty for damage the modification caused, and it can forfeit support from a provider whose terms exclude troubleshooting an unsupported, modified device.

Apple's own support documentation warns that unauthorized modifications "can cause dropped calls, slow or unreliable data connections, and delayed or inaccurate location data" — exactly the symptoms a traveler might blame on a bad eSIM. A co:sim eSIM that fails to install on a jailbroken phone was never actually installed, so it typically still falls under the standard policy: uninstalled eSIMs can be refunded within 30 days of purchase (some plans that bill immediately are excluded; check the plan page).

#Can I un-root my phone to fix eSIM installation problems?

Yes, usually. Restoring stock firmware removes whatever tripped the check, so the device again reports as unmodified to a carrier's app and to Play Integrity or Apple's own attestation, and most eSIM failures caused specifically by root access resolve immediately once the phone is back on an unmodified build.

This is different from a jailbroken iPhone with genuinely broken cellular behavior: reflashing stock iOS fixes both the detection problem and the instability Apple warns about, since both trace back to the same removed security layer. If a co:sim Japan eSIM won't scan on a rooted Android phone, restoring the stock ROM before reinstalling is the reliable fix; a root-hiding module that fools one check today isn't worth risking a plan you've already paid for, since it can stop working the next time the check it exploits gets patched.

#FAQ

#Will jailbreaking delete an eSIM I've already installed?

Jailbreaking itself doesn't automatically delete an installed eSIM profile, but many jailbreak methods require a full device reset or firmware restore first, and that reset does wipe eSIM profiles the same way it wipes everything else on the phone. If you jailbreak without a full restore, the profile typically survives the process intact, since eUICC storage sits outside the file system the jailbreak modifies. The real risk is indirect: Apple warns that unauthorized modifications can cause unreliable data connections and dropped sessions, so a jailbroken phone might show a working eSIM profile that still fails to hold a stable connection. If your eSIM disappears right after jailbreaking, it was almost certainly the reset step, not the jailbreak itself, that removed it.

#Does rooting an Android phone remove eSIM support entirely?

No. Rooting an Android phone leaves the eUICC chip and its stored eSIM profiles untouched: rooting only grants elevated software access, it doesn't unsolder hardware. What changes is which apps will run. Google's Play Integrity API gives developers a way to detect a rooted device, and some carriers build their eSIM-activation apps to check it and refuse to proceed on a device that fails. The phone's native Settings app, which handles most QR-code-based eSIM installs, generally isn't gated by that same check, so installation through Settings often still works. Custom ROMs are a separate risk: some strip out carrier certificate files the eSIM stack needs, which can break installation even though the phone is technically still capable of holding a profile.

#Can I still buy and install a co:sim eSIM if my phone is rooted?

In most cases, yes. co:sim delivers every plan as a QR code by email, and installation happens through the phone's own Settings app rather than a co:sim app that might run root-detection checks. A rooted Android phone that hasn't been stripped of its carrier certificates, or a jailbroken iPhone that's otherwise stable, will usually scan and install the code the same way an unmodified device does. What co:sim can't guarantee is the device's own reliability afterward: a rooted or jailbroken phone that drops data connections intermittently will show that same instability on any eSIM, not co:sim's alone. If installation fails outright and the eSIM was never activated, it's covered by the same uninstalled-eSIM refund window as any other plan; buying on a modified phone doesn't change that policy.

#Why do some eSIM apps specifically check for root or jailbreak?

Root and jailbreak detection exists because a modified OS can bypass protections an app relies on to trust the device it's running on. On Android, Google's Play Integrity API gives developers a verdict on whether a device is a genuine, unmodified build, and apps handling account credentials, payment details, or carrier activation often refuse to proceed below a certain trust tier. On iOS, jailbreaking removes the same sandboxing and code-signing protections Apple's security model depends on. For an eSIM provider, the concern usually isn't the eSIM chip itself; it's that a compromised OS could expose the account session used to manage the subscription, or make it harder to trust that the app displaying an activation status is telling the truth.

#Is there a way to hide root or jailbreak status from an eSIM provider's check?

Various modules and tweaks claim to spoof integrity checks so a rooted or jailbroken phone reports as unmodified, but this is worth avoiding for a travel eSIM specifically. These tools hide the detection signal, not the underlying issue: the same modification Apple and Android's own security documentation warn causes unreliable data connections is still present, so a successful spoof doesn't fix the instability risk. They're also a moving target, since Google and device makers regularly patch the detection methods these modules rely on, so a workaround that lets an eSIM app install today can stop working with the next security update, sometimes mid-trip. If an eSIM genuinely won't install because of root or jailbreak detection, restoring the stock, unmodified build is the more reliable fix.

#What should I do if my eSIM won't activate on a modified phone?

First, confirm the failure is actually root- or jailbreak-related and not something more common, like an incompatible device, a carrier-locked phone, or a QR code that's already been scanned once. If the phone is rooted or jailbroken, try installing through the native Settings app rather than a provider's dedicated app, since Settings is less likely to run an integrity check of its own. If that still fails, restoring the phone to stock firmware resolves most root- or jailbreak-related activation problems immediately. On a co:sim plan, the account dashboard shows whether a profile was ever successfully installed; if it wasn't, the standard uninstalled-eSIM refund policy applies (within 30 days of purchase, excluding plans that bill immediately). Contact support with the device model and OS version if the problem persists after restoring stock firmware.

Ready to travel with a plan that installs the moment you land?