Unable to activate eSIM

Foyer9054

I did a fresh install of GrapheneOS, enabled "eSIM support", and rebooted.
Went to Settings > Network & Internet > SIMs > Setup an eSIM.
Scanned the eSIM QR code, and then a screen popped up saying "SIM not activated. Something went wrong while trying to activate your SIM.".
The same thing happens if I try to enter the eSIM activation code manually.
If I go to Reset options > Reset mobile network settings, check "Erase eSIMs", and then click reset, a dialog appears saying "Can't erase eSIMs".

I then enabled developer options and checked the log when trying to activate (output at end of post).

So I installed Google Play Services and Play Store via the Graphene OS app store.
Logged in, tried activating eSIM again, same error.
I then enabled all permissions for Play Services & Store and tried activating again. Same error.

I've tried with multiple different eSIM activation codes on two different carriers, and used different WiFI networks during setup.
DSDS is enabled in the *#*#4636#*#* menu.

Any advice is appreciated.

2026-03-13 16:41:52.140 16779-16779 ProxyAndro...gerBackend com.google.android.euicc             W  Too many Flogger logs received before configuration. Dropping old logs.
2026-03-13 16:41:52.140 16779-16779 EuiccGoogle             com.google.android.euicc             I  [2] GetAcFromQrScannerFragment.onActivityResult: onActivityResult: request code = 1, result code = -1.
2026-03-13 16:41:52.142  2405-2735  EuiccController         com.android.phone                    D   getDownloadableSubscriptionMetadata callingPackage: com.google.android.euicc
2026-03-13 16:41:52.143  2477-11375 SudConfigProvider       com.android.settings                 D  method: isEnhancedSetupDesignMetricsEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.143  2405-2668  EuiccConnector          com.android.phone                    D  handleMessage: E msg.what=101
2026-03-13 16:41:52.143  2405-2668  EuiccConnector          com.android.phone                    D  processMsg: ConnectedState
2026-03-13 16:41:52.144  2477-11375 SudConfigProvider       com.android.settings                 D  method: isEnhancedSetupDesignMetricsEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.145  2405-2668  EuiccConnector          com.android.phone                    D  handleMessage: X
2026-03-13 16:41:52.146  2477-11375 SudConfigProvider       com.android.settings                 D  method: isGlifExpressiveEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.146 16779-16779 PartnerConfigHelper     com.google.android.euicc             I  isGlifExpressiveStyleEnabled is false
2026-03-13 16:41:52.147 16779-26304 EuiccGoogle             com.google.android.euicc             I  [287] EuiccServiceImpl.ensureSlotIsEuiccAndActive$ar$ds: ensureSlotIsEuiccAndActive: slotId = 0, forceDeactivateSim = false
2026-03-13 16:41:52.147  2477-11375 SudConfigProvider       com.android.settings                 D  method: isForceTwoPaneEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.149 16779-26304 EuiccGoogle             com.google.android.euicc             I  [287] EuiccServiceImpl.ensureSlotIsEuiccAndActive$ar$ds: Passed in slotId=0; euiccIsActive=false; targetSlotIsRemovable=false; forceDeactivateSim=false, multiSimEnabled=true, euiccSlotPresent=true, allowSlotSwitchInMultiPsimEsimMode=false.
2026-03-13 16:41:52.149 16779-26304 EuiccGoogle             com.google.android.euicc             E  [287] EuiccServiceImpl.ensureSlotIsEuiccAndActive$ar$ds: Slot switch is not allowed in multiSim mode, ignore switch request
2026-03-13 16:41:52.149 16779-26304 EuiccGoogle             com.google.android.euicc             I  [287] EuiccServiceImpl.onGetDownloadableSubscriptionMetadata: onGetDownloadableSubscriptionMetadataInternal: slotId = 0, forceDeactivateSim = false, ensureSlotIsEuiccAndActive = EuiccOperationResult{errorCode=131083, switchedToEsim=false, slotMappings=[]}.
2026-03-13 16:41:52.149 16779-26304 EuiccGoogle             com.google.android.euicc             I  [287] EuiccErrorMapper.mapErrorCode: Mapping for error code: 131083
2026-03-13 16:41:52.149 16779-26304 EuiccGoogle             com.google.android.euicc             I  [287] EuiccErrorMapper.mapErrorCode: Mapping error code: 131083 to: 33554432
2026-03-13 16:41:52.149 16779-26304 EuiccGoogle             com.google.android.euicc             I  [287] EuiccServiceImpl.onGetDownloadableSubscriptionMetadata: onGetDownloadableSubscriptionMetadata errorCode: 33554432
2026-03-13 16:41:52.150  2405-2668  EuiccConnector          com.android.phone                    D  handleMessage: E msg.what=6
2026-03-13 16:41:52.150  2405-2668  EuiccConnector          com.android.phone                    D  processMsg: ConnectedState
2026-03-13 16:41:52.152  2405-2668  EuiccConnector          com.android.phone                    D  handleMessage: X
2026-03-13 16:41:52.152  2477-11375 SudConfigProvider       com.android.settings                 D  method: isGlifExpressiveEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.153 16779-16779 PartnerConfigHelper     com.google.android.euicc             I  isGlifExpressiveStyleEnabled is false
2026-03-13 16:41:52.153 16779-26176 EuiccGoogle             com.google.android.euicc             I  [281] WindowInsetsCompat$TypeImpl30.isEsimOnlyDevice: Device Hardware SKU: GZC4K
2026-03-13 16:41:52.153  2477-11375 SudConfigProvider       com.android.settings                 D  method: isGlifExpressiveEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.153 16779-16779 PartnerConfigHelper     com.google.android.euicc             I  isGlifExpressiveStyleEnabled is false
2026-03-13 16:41:52.154  2477-11375 SudConfigProvider       com.android.settings                 D  method: isGlifExpressiveEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.154 16779-16779 PartnerConfigHelper     com.google.android.euicc             I  isGlifExpressiveStyleEnabled is false
2026-03-13 16:41:52.154  2477-11375 SudConfigProvider       com.android.settings                 D  method: isKeyboardFocusEnhancementEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.155  2477-11375 SudConfigProvider       com.android.settings                 D  method: isGlifExpressiveEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.155 16779-16779 PartnerConfigHelper     com.google.android.euicc             I  isGlifExpressiveStyleEnabled is false
2026-03-13 16:41:52.156  2477-11375 SudConfigProvider       com.android.settings                 D  method: isGlifExpressiveEnabled, caller: com.google.android.euicc
2026-03-13 16:41:52.156 16779-16779 PartnerConfigHelper     com.google.android.euicc             I  isGlifExpressiveStyleEnabled is false
2026-03-13 16:41:52.156 16779-16779 SetupLibrary            com.google.android.euicc             I  [GlifLayout] Using setup design GlifLoadingLayout to init for QrDownloadActivity
2026-03-13 16:41:52.156 16779-26176 EuiccGoogle             com.google.android.euicc             I  [281] ClearcutServerLog$$ExternalSyntheticLambda15.call: NetworkUtil
2026-03-13 16:41:52.156 16779-16824 GEuiccLpa               com.google.android.euicc             D  replaced getText() with empty string: %1$s is having trouble with Google Play services. Please try again.
2026-03-13 16:41:52.156 16779-16824 GooglePlayServicesUtil  com.google.android.euicc             W  com.google.android.euicc requires the Google Play Store, but it is missing.
2026-03-13 16:41:52.156 16779-16824 GoogleApiManager        com.google.android.euicc             W  The service for com.google.android.gms.usagereporting.internal.UsageReportingClientImpl is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null}
2026-03-13 16:41:52.156 16779-16824 GEuiccLpa               com.google.android.euicc             D  replaced getText() with empty string: %1$s is having trouble with Google Play services. Please try again.
2026-03-13 16:41:52.157 16779-16824 GooglePlayServicesUtil  com.google.android.euicc             W  com.google.android.euicc requires the Google Play Store, but it is missing.
2026-03-13 16:41:52.157 16779-16824 GoogleApiManager        com.google.android.euicc             W  The service for com.google.android.gms.usagereporting.internal.UsageReportingClientImpl is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null}
2026-03-13 16:41:52.157 16779-26176 EuiccGoogle             com.google.android.euicc             E  [281] ClearcutServerLog$$ExternalSyntheticLambda15.call: Cannot connect to GMS API client. (Fix with AI)
                                                                                                    com.google.android.gms.common.api.ApiException: 17: API: UsageReporting.API is not available on this device. Connection failed with: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null}
                                                                                                    	at com.google.android.gms.clearcut.internal.batcher.DropLargestEventBatchReductionAlgorithm.fromStatus(PG:13)
                                                                                                    	at com.google.android.gms.common.api.internal.ApiCallRunner$TaskRunner.reportFailure(PG:3)
                                                                                                    	at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.failEnqueuedMethods(PG:48)
                                                                                                    	at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.failAllEnqueuedMethods(PG:10)
                                                                                                    	at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.onConnectionFailed(PG:164)
                                                                                                    	at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.onConnectionFailed(PG:174)
                                                                                                    	at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.connect(PG:163)
                                                                                                    	at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.enqueue(PG:51)
                                                                                                    	at com.google.android.gms.common.api.internal.GoogleApiManager.handleMessage(PG:844)
                                                                                                    	at android.os.Handler.dispatchMessage(Handler.java:128)
                                                                                                    	at android.os.Looper.dispatchMessage(Looper.java:333)
                                                                                                    	at android.os.Looper.loopOnce(Looper.java:263)
                                                                                                    	at android.os.Looper.loop(Looper.java:367)
                                                                                                    	at android.os.HandlerThread.run(HandlerThread.java:139)
2026-03-13 16:41:52.157 16779-16779 SetupLibrary            com.google.android.euicc             W  [GlifLoadingLayout] Can not find the resource entry for loading_animation_custom_default
2026-03-13 16:41:52.157 16779-16824 GEuiccLpa               com.google.android.euicc             D  replaced getText() with empty string: %1$s is having trouble with Google Play services. Please try again.
2026-03-13 16:41:52.157 16779-16824 GooglePlayServicesUtil  com.google.android.euicc             W  com.google.android.euicc requires the Google Play Store, but it is missing.
2026-03-13 16:41:52.157 16779-16824 GoogleApiManager        com.google.android.euicc             W  The service for com.google.android.gms.clearcut.internal.ClearcutLoggerClientImpl is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null}

Johnnyloans

Foyer9054

Dial this number to enter a secret menu
*#*#4636#*#*
Under phone information > enable DSDS

Use a good internet connection. Do this in the owner profile.

Try another reboot possibly.

More info:
https://grapheneos.org/usage#esim-support

Novalissoide

Foyer9054 enabled developer options

This was the culprit for the user. You should not run your main phone with these enabled. And no Adb either.

Foyer9054

Update on my situation. I sent my Pixel 9 Pro XL to Google for repair, but they weren't able to fix the eSIM issue (cant activate, and errors when erasing eSIMs via reset menu).
I didn't get any explanation as to why, and since they didn't fix it I contacted them again and it seems the next step is for them to issue a replacement.

Foyer9054

Johnnyloans

DSDS was enabled when I tried the steps in my post. I just edited it to add that.
Everything done in the owner profile.

Johnnyloans

Foyer9054

bump.

Another option is to activate the esim on stock then come back to GOS.

Sorry mate, I don't know. I just did a GOS esim yesterday for someone.

DeletedUser683

Any chance it's a russians mobile provider esim and you try to register it with a roaming tower cell? Because now it's not possible to register esim with roaming cell tower with them.

Foyer9054

DeletedUser683

I'm in the UK. It doesn't look like the eSIM activation request ever actually leaves the phone based on the log, and the error screen pops up pretty much instantly.

Novalissoide

Foyer9054
This similar thread from yesterday

https://discuss.grapheneos.org/d/33097-sim-manager-crashes-when-trying-to-add-an-esim

Foyer9054

Novalissoide

Looks like a different issue, thanks for linking it though. Dev options were off for the steps I performed above (including turning it off again after attempting with Play services/store installed).

In case anyone else has the same issue, I've since reflashed stock Android and the same issue occurs "SIM not activated" (but there were no error logs like above).
I believe now it is a carrier/hardware issue, unrelated to GrapheneOS.

Google support and my carrier were unable to find a solution. I'm giving it a few more days as they each said they would investigate more and get back to me. Not expecting anything though.
I'll probably send the phone back and get a replacement.

SolarSciencePup

Same here. Installed last Saturday, the activation kept failing, tried on Boost Mobile, airalo, and the eSIM test profiles, all of them failed. After re flashing stock it still errors "SIM not activated". Dev options off, tried with and without DSDS. On GrapheneOS it wouldn't let me turn on the eSIM or delete the eSIM in addition to not letting me install one. Can't say for stock android if deletion and/or toggling eSIMs works. Also Pixel 9 Pro XL.

aceblack

SolarSciencePup
hey same problem here, when i try to activate an esim it says “sim not activated”. whent back to stock and still the same. I actually bought another one today and tested it in stock first and worked, but when i got graphene on it it gives me the same problem. Now I have 2 9 pro XL’s ahhaha. Help!!

SolarSciencePup

If anyone still has the a Pixel 9 Pro XL with this issue that has GrapheneOS installed and has not been factory reset or reflashed and is comfortable searching a bugreport, it could potentially be possible to find the command that bricked the eUICC (eSIM chip) during setup.
If you find anything you should submit it to the GitHub issue here
https://github.com/GrapheneOS/os-issue-tracker/issues/7415

Never share a bugreport unless you are sure that the information being shared does not contain personally identifiable information (PII) and never trust the raw output of a LLM without checking it for PII first, even if it claims it is sure that the output contains no PII, double check it.

aceblack

SolarSciencePup
yes that would be very helpful, have you found a solution yet?

SolarSciencePup

Not yet, later tonight I will try and reflash various radio and modem firmware and see if that fixes it.
Also, if people could respond with if the March Pixel drop was installed on the stock os before flashing GrapheneOS that would be of great help, it is possible that Google modified firmware on one of the chips that has broken support for GrapheneOS, possibly some kind of anti rollback protection that means that GOS can't communicate with it as it is on a future firmware version.
The eUICC system seems unable to properly pull profiles and data from GSMA, however the EID, IMEIs and satellite SOS eSIM can all be read so they aren't corrupted and the eUICC is not bricked so there is a chance that this bug is recoverable.
Additional info(to avoid confusion):
eUICC: the chip used to host and store the eSIM
eSIM: profiles installed onto the eUICC
Satellite SOS eSIM: a profile preinstalled onto Google Pixels supporting the satellite SOS feature, contains a subscription to Skylo which provides connectivity when the satellite SOS feature is activated, this eSIM is believed to be locked so that it cannot be removed by the user but possibly may be removed by Google&Skylo through remote SIM provisioning.

Foyer9054

SolarSciencePup

I don't know the exact build version of the stock OS before I installed GrapheneOS, but it was fully up to date around March 12, so it was likely running the most recent build: CP1A.260305.018 (14887507).

I never tried installing an eSIM on the stock OS so don't know if it was broken there before installing GrapheneOS, or if the GrapheneOS install caused it. But your suggestions of the cause of the issue sound plausible.

aceblack

SolarSciencePup
yes very likely something with the software form gos

Johnnyloans

SolarSciencePup Foyer9054

Physical sims are problem free except for hardware failure.
Activating the sim on stock OS then flashing GOS is an option (i think 1 or both of you did this then it stopped working. You might need your carrier's app like googleFi )

aceblack

Foyer9054
I don’t know if you have read my post on the forum but to be sure the problem was not hardware related. I bought a brand new 9 pro xl and installed on stock an esim. everything worked perfectly fine. After gos installation it failed, then I flashes back to stock and it did not work either. So i do not think it is hardware related.

littlerack

Rather for search purposes. If someone experiences issues with esim activation, remember it requires access to few domains (even Google ones may be involved).

If you're doing it while being on restrictive network environment (like with DNS filtering, be it WiFi router or private DNS with "no Google"-like blacklists), you will face expected issues.

shawnsc

Same exact problem, same exact Pixel 9 Pro XL. I tried two different carriers/esim providers, with/without google play services, DSDS activated and updating the os. Only thing I have not tried is reverting to stock android or changing phone. I am operating on unrestricted home wifi. Has anyone come up with a solution or workaround?