Unable to activate eSIM

DoneDimmaDome

xxx my pixel 9a model is the GXQ96 for reference and MP1.0 hardware model

ZooBuZZ

Did anyone ever figure out a solution for this? I should have looked into this before trying to port from one carrier to another...now I seem to be stuck without being able to delete the old esim, can't add a new esim. No ability to text or call. Pixel 9. Just get the 'sim not activated' line every time.

Johnnyloans

ZooBuZZ without being able to delete the old esim,

What steps are you doing to delete the esim?

nackelnick RCS stop working
@"ZooBuZZ" exact same situation

The newest update has the fix for RCS. It is in stable for every phone it looks like so as long as you haven't disabled system updates, you should get it.

After updating, RCS should show connected within a few minutes, if no you could try:

turn the phone off for 5 minutes, then turn on

And/or

delete the storage and cache of Google mesages
- you will keep all messages
- you will have to re-add permissions to Google messages.

RocketWolf696

First thing you could try is make sure you don't have an ad blocker, DNS, vpn onto phone or router blocking anything (even if it's just setting your dns server to adguard's ad blocker ip address for example)

After that, I'd do this:

backup everything on my phone
2.ask an LLM what should I back up on my phone incase it breaks?
Then backup more things I forgot
Flash Google stockOS onto the phone and add the esim there. https://flash.android.com
- similar steps to flashing GOS. It'll erase your data.
If successful, flash GOS back onto the phone kf you wish (the esim stays)

[is this a P10 issue?]

This could just be a software issue.
Any phone could have hardware like the esim break.

I recently added an esim to 2 GOS phones and it worked. A low number of people have to add on Google stockOS or warranty their phone. (Take pictures of all sides and down the usb port incase google says you trashed the phone so no warranty.)

nackelnick

Pixel 9. I randomly had RCS stop working this morning after 3 months on GOS. I tried to toggle my eSIM and had issues connecting to mobile data services. I deleted the eSIM and tried to reinstall with a fresh from my carrier. My logs look similar to what has been attached

ZooBuZZ

nackelnick Yeah, exact same situation for me. Mine was working no problem until late last night. Then it stopped working. I was considering switching carriers anway, so I thought that would help. But that has only made the situation significantly worse... It's odd though that this hit two of us on a Pixel 9 at the same time without it ever being an issue before.

RocketWolf696

Hi everyone!
I have a new Google Pixel 10 Pro XL with GrapheneOS installed with similar error with eSIM (tested with three carries).

The error:
"Cannot initiate a profile download due to an SM-DP+ error"
fires before any actual TLS handshake with the carrier's SM-DP+ server, suggesting the problem is in the local requestEuiccChallenge call to the eUICC chip itself. Given that:

eUICC info returns a valid (non-−1) value
EID is readable
No profiles have ever been on this chip

Is there a known issue with SKU G45RY eUICC initialisation, or is the SERVICE_INVALID response from sandboxed GMS blocking the challenge generation? Any guidance on next diagnostic steps would be very helpful.

Device

Device: Google Pixel 10 Pro XL!<
Hardware SKU: G45RY
GrapheneOS build: 2026061600 (Android 16)
eUICC chip: alive, eUICC info shows a valid number (not −1)
EID: readable, consistent across all log sessions (cardId 1794Si9Mz2dXohL0gDgcm5tXuZ0)

Settings at time of activation attempts

eSIM support: enabled
DSDS: enabled
Developer options: disabled
Sandboxed Google Play: installed and active
VPN: off
Secure DNS: off
Profile used: Owner (main) profile

History

This is a new device. eSIM has never been successfully activated on it — neither on stock Android nor on GrapheneOS. No eSIM profiles have ever been written to the chip.

Three carries tested. All three attempts failed within ₁ second of QR scan or code entry - before any server negotiation could complete.

UI error message:
"Can't set up eSIM. Something went wrong with your SIM. To fix the issue, contact your carrier."
Appears instantly (₁ second after scan/code entry), suggesting the error occurs at the local LPA/eUICC challenge stage, not at the remote SM-DP+ server.

Full logs for three carries:

https://1drv.ms/f/c/5bc623291eb89da3/IgDa6wDQJkv-Q5PfmctWTumbAYyeRyIcHVOt991rmrZz424?e=FtaFiK

Log analysis — key errors (same pattern in all 3 log files):

E EuiccGoogle  ProfileDownloadTransaction.initiate Cannot initiate a profile download due to an SM-DP+ error.
E EuiccGoogle  EuiccServiceImpl.onGetDefaultDownloadableSubscriptionList Failed to get downloadable subscriptions from SM-DS lpa.live.esimdiscovery.com
E EuiccGoogle  EuiccServiceImpl.onGetDefaultDownloadableSubscriptionList Failed to get downloadable subscriptions from SM-DS lpa.ds.gsma.com
I EuiccGoogle  EuiccServiceImpl.onGetDownloadableSubscriptionList onGetDefaultDownloadableSubscriptionList errorCode 262152

For carrier №2, the error is slightly different — occurs at metadata stage:

E EuiccGoogle  ProfileDownloadTransaction.initiate Cannot initiate a profile download due to an SM-DP+ error.
I EuiccGoogle  EuiccErrorMapper.mapErrorCode Mapping error code 655362 to 151004958
I EuiccGoogle  EuiccServiceImpl.onGetDownloadableSubscriptionMetadata onGetDownloadableSubscriptionMetadata errorCode 151004958

Persistent GMS warnings throughout all sessions (may or may not be related because Google Play Store IS installed as sandboxed):

W GooglePlayServicesUtil  com.google.android.euicc requires the Google Play Store, but it is missing.
E EuiccGoogle  PhenotypeSyncSidecarLogic.onFailure Failed to registerSync
E EuiccGoogle  ClearcutServerLogExternalSyntheticLambda15 Cannot connect to GMS API client
  ApiException 17: API UsageReporting.API is not available on this device
  ConnectionResult: statusCode=SERVICE_INVALID

ZooBuZZ

Johnnyloans I did turn of all adblockers, custom dns settings, etc. That did not help any. I also was on the latest build. I deleted cache, unistalled and resintalled google messages, did all of those tricks. Did all the network reset tricks. Toggled airplane mode as well as turning off developer settings. None of those tricks did anything.

I really did not want to factory reset or even flash stock back (and many others have reported stock flashing does not help.). I waited it out for a Sim card to arrive. Popped in the physical sim and was working within 30 seconds.

So no, I never figured out a real solution for the esim situation. I still am unable to even delete the old esim. I am able to toggle it off (disable it) and that seems to be work fine. But adding a new esim or deleting one? Forget about it. ha. So if you have the option of buying a physical sim card, and you do not need to run more than than 1 sim, this will work as a backup plan. But proper esim function seems to be gone for good.

Cia

I had the same issue and couldn't figure it out. So I got a sim card.

gowowa1659

Pixel 10a user here. I'm currently using physical SIM, and never inserted eSIM both before and after flashing GOS. My phone info also says eUICC available memory in bytes:-1.
Does this mean I can't use eSIM? (I immediately flashed GOS after buying this new phone)

gowowa1659

gowowa1659 Edit) When I turned on eSIM functionality, it changed to a valid(non -1) value.
Haven't tested whether eSIM functions properly since I don't have any..

_dex

I've gotten the same issue on my device. The EID still shows in About Phone, but the eUICC size is reporting as -1. I have partially managed to get some life out of the eUICC by toggling DSDS off, restart, toggle on, restart in the *#*#4636#*# Phone Info menu. That at least gets me to have the eUICC to report a non-negative memory size. But trying to enroll a new eSIM reverts back to -1.

Been looking around and it seems it might have to do with the latest Pixel update causing the eUICC to wipe data on bootloader unlock/lock which is unfortunate because that's kinda what's needed to install Graphene :/

So install Graphene on a Pixel 9 device = wiped out eSIM.

I've also reverted to full stock OS + relocked bootloader; nothing. Can't get eUICC to come back to life. I would've said this might be intentional on Google's part to discourage installing Graphene, but seeing as it seems contained to Pixel 9... something something Hanlon's Razor.

Might try OpenEUICC later on a rooted device, but might also just try sending it off to a third-party warranty service and see what they make of it.

de0u

_dex Been looking around and it seems it might have to do with the latest Pixel update causing the eUICC to wipe data on bootloader unlock/lock [...]

There are many reports online of eUICC failures from users of Google's stock OS: https://www.androidauthority.com/google-pixel-esim-bug-3664010/

It doesn't seem clear yet to what extent flashing an OS is causal.

skully373

What device do you have? My main phone is a Pixel 9 Pro XL with a Verizon physical SIM but I just activated my Pixel 7 with a Voidmob eSIM and it was an incredibly easy and painless process. I'm actually planning on ditching the 9 for the 7 just because of the form factor and the fact that I haven't noticed any difference in performance in my day to day use... and since the activation was so easy, and less that half the price for the service, I'm 99% sure the 9 Pro XL is going in a drawer.

sammumm

Recently bought another 'refurbished" 9 Pro, this time the XL model. I did this:

activate stock rom
register with new google account
activate eSim (same one as above in june on my 9 Pro NoXL), absolute frictionless
prepare pixel for flashing
reboot & flash GOS
reboot & activate GOS
settings > aktivate eSim
reboot
check: eSim is active & online instantly, without any further action

some extra points:

NOXL contained an active phySim all the time, XL not at all
NoXL battery manufacturing date nov 16, 2024
XL battery manufacturing date may 28, 2024
both came refurbished with unknown history
NoXL came with somewhat 80 battery cycles
XL had only 2 battery cycles - probably was never activated before

One thing i don't understand: the eSim is not PIN protected (neither was under short term stock rom nor under GOS), but survived the OS flash procedure.
So, it is not secured when the phone is lost? or is this anyhow integrated permanently within the devic PIN, which was/is intentionally identically on stock and GOS?

de0u

sammumm One thing i don't understand: the eSim is not PIN protected (neither was under short term stock rom nor under GOS), but survived the OS flash procedure.

So, it is not secured when the phone is lost?

Correct, if a SIM PIN is not set, though the carrier can cancel it.

_dex

Just messed with OpenEUICC on stock Android 17. I toggled DSDS on/off to get the eUICC to start talking again and it got picked up by OpenEUICC. Looks like there's a permanent, but disabled profile for Skylo (satellite comms) on the EUICC that doesn't get cleared with a normal eSIM wipe.

I did get a little more information by doing the eSIM provisioning with OpenEUICC which provides more debug info. Connection to the provisioning server succeeded with an HTTP 200. The process crashes at "Authenticating your device with server". The secure element seems to just completely disappear during the process. Seems to indicate a deeper firmware issue with the element itself.

07-06 22:09:12.236  7187  7276 D HttpInterfaceImpl: transmit(url = [SANITIZED])
07-06 22:09:12.237  7187  7276 D HttpInterfaceImpl: HTTP tx = {"smdpAddress":"[SANITIZED]","euiccChallenge":"[SANITIZED]","euiccInfo1":"[SANITIZED]"}
07-06 22:09:12.717  7187  7276 D HttpInterfaceImpl: transmit responseCode = 200
07-06 22:09:12.718  7187  7276 D HttpInterfaceImpl: HTTP response body = {"header":{"functionExecutionStatus":{"status":"Executed-Success"}},"transactionId":"[SANITIZED]","serverSigned1":"[SANITIZED]","serverSignature1":"[SANITIZED]","euiccCiPKIdToBeUsed":"[SANITIZED]","serverCertificate":"[SANITIZED]"}
07-06 22:09:12.719  7187  7276 I app_process64: es9p_initiate_authentication 0
07-06 22:09:12.720  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21100[SANITIZED]
07-06 22:09:12.787  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.789  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21101[SANITIZED]
07-06 22:09:12.802  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.804  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21102[SANITIZED]
07-06 22:09:12.817  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.819  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21103[SANITIZED]
07-06 22:09:12.832  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.838  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21104[SANITIZED]
07-06 22:09:12.850  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.852  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21105[SANITIZED]
07-06 22:09:12.864  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.866  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21106[SANITIZED]
07-06 22:09:12.879  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.880  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21107[SANITIZED]
07-06 22:09:12.892  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.894  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21108[SANITIZED]
07-06 22:09:12.908  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.909  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E21109[SANITIZED]
07-06 22:09:12.920  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.921  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E2110A[SANITIZED]
07-06 22:09:12.933  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.938  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E2110B[SANITIZED]
07-06 22:09:12.951  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.953  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E2110C[SANITIZED]
07-06 22:09:12.966  7187  7276 D OmapiApduInterface: OMAPI APDU response: 9000
07-06 22:09:12.967  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E2910D[SANITIZED]
07-06 22:09:31.205  7187  7276 D OmapiApduInterface: OMAPI APDU response: 0000
07-06 22:09:31.206  7187  7276 I app_process64: es10b_authenticate_server -1
07-06 22:09:31.208  7187  7187 E EuiccChannelManagerService: Foreground task encountered an error
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: ProfileDownloadException(lpaErrorReason=ES10B_ERROR_REASON_UNDEFINED, lastHttpResponse=HttpResponse(rcode=200, data=[[SANITIZED]
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at net.typeblog.lpac_jni.impl.LocalProfileAssistantImpl.downloadProfile(LocalProfileAssistantImpl.kt:231)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.core.LocalProfileAssistantWrapper.downloadProfile(LocalProfileAssistantWrapper.kt:45)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.service.EuiccChannelManagerService$launchProfileDownloadTask$2$1$1.invokeSuspend(EuiccChannelManagerService.kt:404)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.service.EuiccChannelManagerService$launchProfileDownloadTask$2$1$1.invoke(EuiccChannelManagerService.kt:8)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.service.EuiccChannelManagerService$launchProfileDownloadTask$2$1$1.invoke(EuiccChannelManagerService.kt:4)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager$withEuiccChannel$2.invokeSuspend(DefaultEuiccChannelManager.kt:259)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager$withEuiccChannel$2.invoke(DefaultEuiccChannelManager.kt:8)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager$withEuiccChannel$2.invoke(DefaultEuiccChannelManager.kt:4)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:89)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:169)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.BuildersKt.withContext(dex-id-550c44cb79fe776cc932dbb5557682d990345207:1)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager.withEuiccChannel$suspendImpl(DefaultEuiccChannelManager.kt:258)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager.withEuiccChannel(DefaultEuiccChannelManager.kt:0)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.service.EuiccChannelManagerService$launchProfileDownloadTask$2.invokeSuspend(EuiccChannelManagerService.kt:403)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.service.EuiccChannelManagerService$launchProfileDownloadTask$2.invoke(EuiccChannelManagerService.kt:8)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.service.EuiccChannelManagerService$launchProfileDownloadTask$2.invoke(EuiccChannelManagerService.kt:4)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at im.angry.openeuicc.service.EuiccChannelManagerService$launchForegroundTask$2$1.invokeSuspend(EuiccChannelManagerService.kt:296)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
07-06 22:09:31.211  7187  7187 E EuiccChannelManagerService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
07-06 22:09:33.002  7187  7276 D OmapiApduInterface: OMAPI APDU: 81E29100[SANITIZED]
07-06 22:09:33.002  7187  7276 E OmapiApduInterface: OMAPI APDU exception
07-06 22:09:33.003  7187  7276 W System.err: java.io.IOException: Secure Element is not connected
07-06 22:09:33.003  7187  7276 W System.err: 	at android.se.omapi.Channel.transmit(Channel.java:174)
07-06 22:09:33.003  7187  7276 W System.err: 	at im.angry.openeuicc.core.OmapiApduInterface.transmit(OmapiApduInterface.kt:66)
07-06 22:09:33.003  7187  7276 W System.err: 	at net.typeblog.lpac_jni.impl.LocalProfileAssistantImpl$ApduInterfaceWrapper.transmit(LocalProfileAssistantImpl.kt:38)
07-06 22:09:33.003  7187  7276 W System.err: 	at net.typeblog.lpac_jni.LpacJni.es10cGetEid(Native Method)
07-06 22:09:33.003  7187  7276 W System.err: 	at net.typeblog.lpac_jni.impl.LocalProfileAssistantImpl.getEID(LocalProfileAssistantImpl.kt:170)
07-06 22:09:33.003  7187  7187 I Surface : Creating surface for consumer unnamed-7187-20 with slotExpansion=1 for 64 slots
07-06 22:09:33.003  7187  7276 W System.err: 	at net.typeblog.lpac_jni.impl.LocalProfileAssistantImpl.getValid(LocalProfileAssistantImpl.kt:108)
07-06 22:09:33.003  7187  7276 W System.err: 	at im.angry.openeuicc.core.EuiccChannelImpl.getValid(EuiccChannelImpl.kt:40)
07-06 22:09:33.003  7187  7276 W System.err: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager.tryOpenEuiccChannel(DefaultEuiccChannelManager.kt:133)
07-06 22:09:33.003  7187  7276 W System.err: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager.access$tryOpenEuiccChannel(DefaultEuiccChannelManager.kt:25)
07-06 22:09:33.003  7187  7276 W System.err: 	at im.angry.openeuicc.core.DefaultEuiccChannelManager$findEuiccChannelsByPort$2.invokeSuspend(DefaultEuiccChannelManager.kt:225)
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
07-06 22:09:33.003  7187  7187 I Surface : Creating surface for consumer VRI[PrivilegedMainActivity]#20(BLAST Consumer)20 with slotExpansion=1 for 64 slots
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
07-06 22:09:33.003  7187  7276 W System.err: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

WhiteBear

Hi,
I got the same problem. However when I updated to 2026070501, first boot after update enabled the eUICC (I didn't get the - 1 byte error, it showed the real size). Since a replacement is approved from Google, I restarted to make sure. It is again - 1 byte and eSIM is not working.

quaternion

Exactly the same problem occurs with both of the refurbished Pixel 9 Pro XL devices I bought recently:

Device 1: Flashed using the 'Web Installer' on 27 June.
Device 2: Flashed using the 'Web Installer' on 13 July.

Having read through all the official issue tracker tickets mentioned on this topic (as well as this one: https://issuetracker.google.com/issues/504073878), it seems to boil down to the following two options:

Accept the error and use physical SIM cards for the time being (hoping that a software fix for the bricked eSIM feature will become available in the future).
Ask the seller to replace the devices (ignoring the high likelihood that the replacement units will exhibit the exact same problem).

Any recommendations on what to do?

Johnnyloans

quaternion Accept the error and use physical SIM cards for the time being (hoping that a software fix for the bricked eSIM feature will become available in the future).

Maybe but probably not. Ive seen a few people with a pixel 9 (pro or XL as well) send their phone to the Google repair center and get back a new (or refurbished?) device because they couldn't fix it.

If you want to return it. A 2nd SIM could be useful for traveling internationally or work. Many P9 owners don't have this issue. It's a common issue on P9 and not unheard of on other models.

quaternion

Maybe but probably not.

This comment gives me reason for hope: https://www.reddit.com/r/android_beta/comments/1sonjlg/comment/ow7jzoy/

Many P9 owners don't have this issue.

The issue is aparrently triggered by unlocking & locking the bootloader while updating to 260305 or later.

« Previous Page Next Page »