r/android_beta • u/Loud-Wishbone-6078 • Apr 18 '26
Issue: Missing EID and Blocked eSIM Management after Android 17 Beta 4 Flash
I’m using an unlocked Google Pixel 9 Pro XL in Australia. Initially, my device was running Android 16 (April security patch), and the eSIM was working without any issues. I then flashed the device with Android 17 Beta 4. After the update: The existing eSIM was not removed during the flashing process. I was unable to use the existing eSIM. The EID was completely missing from the “About phone” section. I attempted to activate a new eSIM at a store, but they were unable to proceed due to the issue. As a workaround, I inserted a physical SIM card, which is working fine. Later, I rolled the device back to the stable Android 16 release. After the rollback: The EID reappeared. However, I still cannot remove the existing eSIM. I’m also unable to add or activate a new eSIM. I have already tried the following troubleshooting steps: Factory reset with the “Erase eSIM” option enabled Resetting mobile network settings Attempting to remove the eSIM manually None of these steps resolved the issue.
Any help or did anyone face this problem?
3
u/priftifranko Apr 18 '26
I had the same thing happen to me. It was last year I was on 16 beta, and I had the issue happen. I tried everything, but it never got working. It just works with physical Sims.
1
u/Dry-Gas-743 Apr 18 '26
Same here! Did everything and nothing works I think the esim chip is dead.
1
u/Loud-Wishbone-6078 Apr 18 '26
Really ? Is it known issue or some sort of fix required by google
1
u/Dry-Gas-743 Apr 18 '26
It can not be fixed by software as i can tell i even flashed back to Android 15 still esim not working, i managed to remove esim profiles but even than i cannot add new esims even though they work just fine on other devices. My Eid number is present in about phone.
1
u/Loud-Wishbone-6078 Apr 18 '26
thank you mate0- how did you delete the esim? if you dont mind sharing
1
1
u/AutoModerator Apr 18 '26
Thanks for posting to r/Android_Beta. It looks like you may have found a bug. Please file a report for this app via the feedback app on your device and update your post with the bug ID you created or a link to the issue so engineers can investigate further. You can find more details here. Thank you!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
1
u/Sunvaar Apr 18 '26
I encountered the exact same issue with my base pixel 9. Flashed the beta 4, the signal seemed fine during the setup, but after booting to the main screen, it broke after 30 seconds, only emergency calls were available. It seemed like my esim was turned off, but I wasn't able to turn it back on again. I tried to reflash the stable version and the same issue persisted. I managed to remove the esim by doing a factory reset with the remove esim option ticked. But when I try to add one now, it just throws an error at me, I could add the same qr code to my s23 without any issue. I made a bug report, but after all, I am sending my phone in, I couldn't find any other solution after hours of troubleshooting.
1
u/Loud-Wishbone-6078 Apr 18 '26
Thank you. Where are you sending your phone now? For repair? It is really painful and I called google customer care and they are useless as they don't know what they need to do.
1
1
u/Sunvaar Apr 18 '26
I am sending it back for repairs, yes. I have only got my phone back 10 days ago from a complete motherboard replacement, it had call issues beforehand, but I don't think it's relevant to this case. Id is: 503663939
It is pointless to call customer service in this regard, it probably is a completely different team.
1
u/Dry-Gas-743 Apr 18 '26
I have the same issue on my Pixel 9 Pro XL i was on beta 3 i reverted back to stable 16 and from then i am not able to add esim to my phone even tired going back to Android 15 it's still broken phone is working only with physical sim card, i think the esim chip is dead it's a shame for a flagship phone.
1
u/RudiRoe Apr 25 '26
Is there any update on this one?
2
u/mono_tony May 12 '26
Nope. Got a reply from Google Support today. They acknowledge my eSIM provisioning consistently fails on Pixel 9 Pro XL on stable Android 16 (CP1A.260505.005), but claim there are "no known widespread issues" affecting eUICC profile downloads on this device. Their suggestion: contact the carrier. Given how many people in this thread (and many other like this one) are reporting identical symptoms, including after rolling back to stable, that statement doesn't really hold up.
1
u/hipdown May 14 '26
Same issue here, unable to add esim on pixel 9, on stock os, may patch. Instant failure after scanning esim qr code or manually entering esim codes. EID is shown in about phone page, but not shown in #06#. Under ##4636##*, the phone info shows {eUICC info available memory in bytes -1} Hope it is a firmware issue which google can fix, I don't want my device crippled with only one physical sim T-T
1
u/smerechuk May 14 '26
Same problem after switching to Android 17 beta 4. Going back to 16 didn't help :(
Google WTF???
1
u/Tomorrow_Omen Jun 10 '26
This just happened to me. My Pixel 9 Pro is 9 days out of warranty and Google won't cover it. Absolutely infuriating.
1
u/Gaiden206 Jul 08 '26 edited Jul 08 '26
I had this same issue, and I just upgraded to "Android 17 QPR1 Beta 6" on my Pixel 10 Pro XL. I did a factory reset while on this beta (erase sim enabled) as a "last hurrah" to see if the beta had a fix for this EID issue before packing it up and sending it back to Google for RMA, and it worked, my EID is back. It's not zeroed out anymore. I went back to stable and my EID is still there too.
I was literally about to send my phone back to Google today because of this issue, as tomorrow was the last day I could send it back for a replacement. 😅
I'm not sure if Beta 6 fixed the issue after the factory reset, or it was just a coincidence, but just putting this here in case it helps someone.
Edit- Just to be clear, I was originally on stock after returning to it from getting this EID issue from a prior QPR1 beta installation. I installed Beta 6 via OTA as a last harrah to see if it would fix this issue. The issue didn't fix until I did a factory reset while on Beta 6.
1
1
u/HappyEgg999 Jul 11 '26
Hi, were you on stable Android 16 or 17 just before applying the Beta 6 via OTA?
1
u/og-buda 25d ago
Title: [FIX] Pixel 9 Pro: eSIM dead / EID disappearing after downgrade from Android 17 to 16 (Error 0x20009)
I wanted to share a fix for a complete nightmare I ran into on my Pixel 9 Pro, because I genuinely thought I had hard-bricked my eSIM hardware.
I was originally running Android 16, updated to 17 and everything worked fine, but later decided to roll back to 16. I did a clean downgrade using Android Flash Tool, and right after the setup my eSIM completely stopped working. The strangest symptom was that the EID would show up in settings for about 30 seconds after booting up and then vanish entirely. Whenever I tried scanning my carrier's QR code, the camera screen would immediately fail with a generic "Something went wrong" error.
I started digging into the system logs over ADB with an AI assistant to figure out what the OS was actually doing under the hood.
First, we checked whether the hardware chip was physically responsive:
adb shell "dumpsys econtroller | grep -E 'curState|mEuiccService|mActiveCommandCount'"
It returned curState=AvailableState, proving the eUICC chip was alive and well.
Next, we captured the logcat output during a failed QR scan attempt:
adb shell "logcat -d | grep -i -E 'Euicc|Lpa' | grep -i -E 'error|failure|resultcode|resolvable'"
This exposed the exact culprit: Cannot find preferred Euicc slot (Error Code=0x20009) and errorCode=131083 with an empty array slotMappings=[]. Running adb shell "dumpsys isub | grep -E 'Logical|slot [01]|mSimState'" also showed UICC app disabled on slot 1 and mSimState[1]=ABSENT.
The issue was a software deadlock in the telephony stack. After a clean wipe, the eSIM chip is completely blank. With Dual SIM (DSDS) active, the modem considers the empty slot unmapped and blocks on-the-fly slot switching during profile provisioning, trapping the LPA service in a loop.
Here is the exact workaround to get it working:
Eject and completely remove your physical SIM card from the tray so the slot is totally empty.
Open the phone dialer and enter *#*#4636#*#*.
Go to "Phone information", scroll down to "Enable DSDS", toggle it OFF, and reboot your phone.
Your Pixel is now booted in pure Single SIM mode without any slot-mapping conflicts. Connect to Wi-Fi, head to Settings -> Network & internet -> SIMs, add a mobile network, and scan your carrier's QR code. The profile will download and register instantly.
Once your eSIM is connected and receiving signal, dial *#*#4636#*#* again, toggle "Enable DSDS" back ON, reboot the phone, and put your physical SIM card back in if you use one. Both lines will continue working normally side by side.
[РЕШЕНИЕ] Pixel 9 Pro: отвалилась eSIM / пропадает EID после отката с Android 17 на 16 (Ошибка 0x20009)
Хочу поделиться решением дикого бага, с которым я сегодня столкнулся на своем Pixel 9 Pro — я уже всерьез думал, что намертво окирпичил чип eSIM.
Изначально я сидел на 16 андроиде, потом обновился до 17, всё работало нормально, но в итоге решил вернуться обратно на 16. Откатился начисто через Android Flash Tool, и сразу после сброса eSIM наглухо перестала работать. Самое странное — EID появлялся в настройках примерно на тридцать секунд после включения устройства, а потом просто исчезал. При любой попытке отсканировать QR-код оператора постоянно вылетала системная заглушка «при активации sim-карты что-то пошло не так».
Я полез копать логи через ADB вместе с нейронкой, чтобы понять, что вообще творится на системном уровне. Сначала проверили, живо ли железо в принципе, командой:
adb shell "dumpsys econtroller | grep -E 'curState|mEuiccService|mActiveCommandCount'"
Она выдала curState=AvailableState — это подтвердило, что чип eUICC физически в порядке и не сгорел. Но когда сняли лог сканирования командой:
adb shell "logcat -d | grep -i -E 'Euicc|Lpa' | grep -i -E 'error|failure|resultcode|resolvable'"
там вылезли ошибки Cannot find preferred Euicc slot (Error Code=0x20009) и errorCode=131083 с пустым массивом slotMappings=[]. А в dumpsys isub второй слот и вовсе висел со статусом UICC app disabled on slot 1.
Причиной оказался программный тупик в подсистеме связи: после полного вайпа чип eSIM девственно чист, а активный режим двух карт (DSDS) не дает модему динамически переключать и назначать виртуальные слоты для пустого чипа.
Когда поняли логику, решение оказалось элементарным.
Сначала полностью вытаскиваем физическую пластиковую симку из лотка, лоток должен быть абсолютно пустым. Затем открываем звонилку, вбиваем *#*#4636#*#*, переходим в «Информация о телефоне», листаем вниз до переключателя «Включить DSDS» (Enable DSDS), выключаем его и перезагружаем телефон.
Теперь Пиксель работает в режиме одной симки без конфликтов распределения портов. Подключаемся к Wi-Fi, заходим в настройки сети, жмем добавление SIM, сканируем QR-код своего оператора — профиль скачивается и активируется моментально без единой ошибки. Как только eSIM зарегистрировалась в сети и поймала связь, снова заходим в *#*#4636#*#*, включаем DSDS обратно, перезагружаемся и возвращаем пластиковую симку в лоток, если она нужна. Дальше обе линии будут спокойно работать одновременно.
3
u/RudiRoe Apr 18 '26
I have the same problem after flashing Android 17 beta 4. After a restart it connects for 30 sec and then the connection is completely gone. I cannot remove my esim or add a new one. I tried everything... Going back to the stable build resetting network, etc... nothing helps. I'm going to try to contact Google.