eSIM on LineageOS and other AOSP builds

Your phone almost certainly has the chip. Any handset sold with eSIM has a physical eUICC wired to the modem, and flashing a different Android over the top does not remove it. You can prove it in seconds by dialling *#06# and reading off the EID, a 32-digit number that identifies the chip rather than the phone. People see that EID, conclude the device supports eSIM, and then cannot understand why nothing in Settings lets them add one.

The EID is telling you about silicon. The missing menu is telling you about software. Both statements are true at once: the hardware is eSIM-capable and the operating system cannot use it. No provider can sell you around this, no activation code is special enough to fix it, and no support ticket will help, because the limitation lives in the image you flashed rather than in the profile. That is why the check further down this page exists, and why it costs nothing to run.

There is an open-source answer. OpenEUICC is a free software local profile assistant for Android, and it is what several de-Googled ROMs use in place of Google's implementation. iodeOS adopted it, and the now-discontinued DivestOS shipped it before that. The catch is in the project's own one-line description: system privilege or ARA-M allowlisting is required. OpenEUICC has to be installed as a system application, which means it must be built into the ROM image or injected as a Magisk module. It is not something you install like a normal app and expect to work.

The project also publishes EasyEUICC, an unprivileged variant that does install like a normal app, and this is where people get their hopes up wrongly. EasyEUICC cannot manage a phone's internal eSIM. It works with removable eSIM chips and USB readers, and only where the chip proactively grants it access through its ARA-M field. Built-in eUICCs do not do that. So downloading EasyEUICC onto stock LineageOS and expecting to add a profile to the handset's embedded chip will not work, and no amount of retrying changes it.

If your build has no assistant, you have three realistic options and one dead end. You can move to a ROM that ships one, which in practice means a build that has integrated OpenEUICC or a de-Googled OS that carries Google's implementation in a disabled-by-default state. You can look for an unofficial build of your device that includes OpenEUICC as a system app, remembering that unofficial builds vary enormously in quality and that you are trusting whoever compiled it. Or you can add OpenEUICC via Magisk if your device is already rooted and you accept the risk that entails.

The dead end is buying an eSIM first and hoping. A physical SIM is the honest answer for an unsupported build, and we do not sell physical SIMs, so this is advice with nothing behind it. If you do change ROMs specifically to get eSIM working, do the change and confirm the download screen appears before you pay anyone for a profile. Build support also moves: some device builds have gained eSIM screens over time, so a two-year-old forum post about your model may simply be stale in either direction. Check the build in front of you.

We supply a standard GSMA activation code. Whether your operating system can consume it is determined entirely by your build, and we have no visibility into and no control over that. We sell the eSIM profile, we do not control whether a given ROM can install it, and on this page more than any other that distinction decides whether you should buy at all. Test first. If the add-a-SIM screen is not there, do not pay us.

Concretely: the UK number QR is single use and is never reissued, and the purchase is not refundable if your ROM turns out to be unable to download it. Ask us before paying if you are unsure, and we will tell you plainly whether we have seen your combination work. On verification generally, the line receives ordinary SMS and voice calls, but no provider can guarantee that any particular app or service will accept any particular number.