[deleted]
How bypass the SIM unlock screens without introduce a PIN?
GOS Phone Unusable After Forgetting eSIM PIN due to Google eSIM management.
other8026 I can't open the Settings because i have to enter the PUK of the eSIM. I never got any PUK from my carrier. I will get one in 2 weeks but until then i can't use my phone. Im stuck on the "Enter PUK screen". There is a button to disable the eSIM but pressing it results in an error message. Probably due missing Google eSIM management on my device. Is there a way to get into the settings and bypass the PUK screen until i have my PUK code?
On stock google android you could deactivate the eSIM until you get the PUK to use your phone till then. But GrapheneOS can't disable the eSIM at the moment because of missing Google eSIM management.
I can press on "emergency call" resulting in an telephone input field. From there i can access the control center but i can't change anything there. I can't go to settings. If i want to it shows me the PUK input screen again. Same for WIFI or bluetooth or other settings which needs user authentication.
[deleted] I got into this problem by adding an PIN to my eSIM in the settings to add an extra layer of security after the phone reboots. This results in an error message. After pressing OK on this message i got into the "enter PUK" screen. I don't have a PUK at the moment and i will get one in a few weeks but i have to use my phone until then. Is there a way to disable the eSIM or bypass it temporally to enter the PUK when i have got it?
There is a button which shows "disable eSIM" which is a normal function to bypass the screen until you have the PUK but in GOS it results in an error because "Google eSIM management" is not permanent enabled. So this function is general bricked on GOS devices.
domnru I see. Sorry, I don't have an eSIM so I'm not too familiar with the whole process.
What happens if you try safe mode? Can you remove the eSIM then? https://support.google.com/pixelphone/answer/2852139?hl=en
other8026 No problem. Its my first time too.
Rebooting into the safe mode results in the same "enter PUK" screen. Is there a way to enter ADB commands to set system properties to disable eSIM completely? Like in the sideload mode? or other rescue modes?
A GOS update could fix that too by adding a button to enable "Google eSIM management" in this screen or enable Google eSIM management if you have to enter the PUK but thats in the far future, if its a relevant topic for the devs.
If Google eSIM management is the only way to disable or manage an eSIM, im asking myself the question, what will happen if i enter the PUK 10 times wrong, resulting in a locked eSIM. But the system can't disable the eSIM or delete it because it requires "Google eSIM management". Worse case would be an error loop. But if im honest, i don't want to try that on my personal phone.
domnru asking around, I don't know of a way to get past that prompt. What happens if you enable airplane mode via the quick settings tile and restart? Can you do that?
Any way you can get your carrier to rush that code for you?
By the way, there is an open issue where others have run into this issue: https://github.com/GrapheneOS/os-issue-tracker/issues/2162
other8026 I wasn't able to activate the airplane mode via the control panel. By entering the safe mode the airplane mode will be activated what i did but sadly this does not help. To get the PUK i have to open the App of my carrier but i can't access that because my phone is locked because of the missing PUK. What a funny paradox. The carrier answered that they can only get me the PUK if i send an picture of my ID and then i have to wait until mid January... The PUK is shown in the App on my phone. I just need to disable the eSIM temporally, get the code and activate the eSIM again...
But still thank you very much for trying to help.
domnru I can't open the Settings because i have to enter the PUK of the eSIM.
Whenever I have something in fullscreen blocking me from interacting with the phone (for example I receive an unknown call, but i want to search the number before I answer). The only way to get past that is to double click the lock button (to open the camera) and then swipe up from the bottom to open the home screen. Have you tried this? Does this work before phone unlock?
treequell The problem is the PUK is stored on the phone in the carrier app. I could access the PUK easily if the button "deaktivate eSIM" in the "enter PUK" screen works. Pressing the button results in an error. Typing the PUK 10 times wrong it will result in an error loop.
https://github.com/GrapheneOS/os-issue-tracker/issues/2162
At the moment I am locked out of my phone because i can't access the PUK because of the missing implementation or wrong architecture of the "disable eSIM" button. The button can't be used because "Google eSIM management" is disabled after every reboot. The system can't disable the eSIM and can't lock the eSIM after 10 times failed attempts with the PUK.
a year later
Hello, I was wondering if you found a solution for this. I'm encountering the same issue but I'm not using graphene OS, just stock pixel OS. I did install the beta version of android 16 which may be the underlying issue. Thank you already :)
- Edited
de0u I contacted Google support as well around the time I posted the previous question, to be honest I just want my phone to work again as soon as possible. I've read through this thread and every problem the original poster encountered, I've been encountering as well. It's the only thread I've found thats remotely close to what I experienced.
Pieter This thread was related to the state of the GrapheneOS code base a year ago. I believe code changes were made in GrapheneOS that should make this situation unreachable in GrapheneOS today. Despite potentially having some similar symptoms, it is vastly unlikely that the problem is the same...
I would be surprised if Google has a toggle for disabling their trusted eSIM management code.
If the eSIM requires the PUK and the PUK is not known, that is a big issue. Perhaps somebody on the Google forum can talk you through wiping the device (I don't know if Google's Recovery factory-reset code can wipe eSIMs).
- Edited
I'm assuming that the SIM PIN entry screen is implemented identically for physical SIMs and for eSIMs. I tried the SIM PIN feature with my physical SIM, and it seems that the SIM PIN entry screen was implemented such that it blocks usage of the lockscreen and Quick Tiles area completely, and the only things usable are the emergency dialer linked to from the SIM PIN entry screen and the power menu. Entering Safe Mode automatically enables Airplane Mode but it seems that even Airplane Mode doesn't prevent the OS from asking for the SIM PIN. Assuming I'm right that the SIM PIN entry screen works the same for SIMs and eSIMs, why was it implemented this way?? The way it currently works is as if the SIM PIN is meant to lock usage of the entire phone, but it can be easily physically ejected, then the phone could be unlocked. Perhaps the SIM PIN feature was implemented long time ago where the Android developers thought the user could easily eject the SIM, but didn't consider the case of eSIMs? Why not just make the SIM PIN entry screen less obnoxious, if it's (hopefully) possible? Then users that are already locked out with an eSIM on GrapheneOS could easily sideload the OTA update from recovery and dismiss the SIM PIN entry screen and use their device.
- Edited
Not sure if its helpful, but I'm reminded of this story:
https://bugs.xdavidhu.me/google/2022/11/10/accidental-70k-google-pixel-lock-screen-bypass/
- Edited
Watermelon Perhaps the SIM PIN feature was implemented long time ago where the Android developers thought the user could easily eject the SIM, but didn't consider the case of eSIMs?
I expect so.
Watermelon Why not just make the SIM PIN entry screen less obnoxious, if it's (hopefully) possible?
I suspect it's a mixture of:
- It is messy code that is delicate to change because of security implications
- Most users don't set SIM PINs
- Many users with a SIM PIN know the PUK
- ...plus maybe other factors.