HoldMyBeer Hi, I'm new to this forum and I've got a question to the experts. I set a Duress PIN some month ago and my approx. 3 years old Pixel 6a is up2date. For the duress PIN I've set 4 numeric digits (example 1234) and the unlock PIN is a combination of 8 letters and 6 numbers (example abcdefgh987654). And to unlock the private profile I use the same PIN. As said I work with that settings for almost 3 years. Today my GOS was screenlocked and I entered the unlock PIN as usual but I made a mistake and pressed enter already after the abcdefgh <return> and the device rebooted immediately and came up to the recovery mode and remains now there. I tried the option TRY AGAIN many times, same problem. Looks like the incomplete unlock PIN has the same functionality as the Duress PIN. Can anyone confirm that or what could happen? Is it possible to recover it? Switching totally off is not possible. A factory data reset would be bad because my eSIM became deleted and inaccessible. I'd like to provide a photo of the screen but I cannot attach it. What service is working here? Thanks for any help. HMB
Probably9857 HoldMyBeer A factory data reset would be bad because my eSIM became deleted and inaccessible Also, a factory reset doesn't delete eSIMs.
gristle-cause HoldMyBeer Looks like the incomplete unlock PIN has the same functionality as the Duress PIN This is not expected behavior. The only think that should trigger the duress encryption keys wipe is the duress pin exactly Here is a video of duress wipe in action
phospmph HoldMyBeer When you set up duress PIN you should have set up a duress password as well. Do you remember what was the password set to?
Probably9857 FWIW, if the duress pin was triggered, I think you should see a message about the device being corrupt. If you don't see that, then there is some other issue. (That's good, because there is no way to recover data after a duress wipe.)
HoldMyBeer Probably9857 Thanks for reply. I made a pic but cannot post it here. Do I need an online service to host it?
HoldMyBeer Probably9857 LOL {"data":{"error":"Imgur is temporarily over capacity. Please try again later."},"success":false,"status":403} I have to find another service
HoldMyBeer gristle-cause Thanks, I knew this video before I set the Duress PIN. My screen now is exactly the same screen as in this video at 1:34. Any idea why?
Probably9857 HoldMyBeer If you already have a cloud storage service, you can also share a public link from there.
EverettHitch HoldMyBeer I have not seen an imgur image in ages. Either their users haven't parted their ways with Google or they're not using a VPN or both. It's hard to feel sorry for that folk that don't know what's good for them, I hope they'll get there. But I mean, who are you trying to trick? You can't escape Google by using it.
gristle-cause HoldMyBeer If you've indeed triggered a duress wipe without entering the duress pin, this is a bug you should report
Probably9857 HoldMyBeer Well, that's not good, but it's still very unlikely that the cause was accidentally triggering the duress pin.
userofgos userofgos This was back almost two years ago when wired Android Auto was crashing my Pixel 8a a lot, and overheating it and would turn black and be completely unresponsive while I was navigating with Google Maps. Had to force shutdown by holding the power button for 30 seconds. Iirc, it repeated a few times before I received this screen (HoldMyBeer ).
Probably9857 HoldMyBeer I'm sure I unlocked the screen exactly the way I described it. I am assuming that. If that did trigger the duress pin, that would be a severe bug. But there are probably other ways to reach that state. The obvious one that comes to mind is a hardware failure in the secure element.
Probably9857 HoldMyBeer Does that mean it is impossible to boot without a factory reset? I don't know. I would first wait for others to give some advice before you do anything irreversible.
userofgos HoldMyBeer Does that mean it is impossible to boot without a factory reset? I would try sideloading the latest OTA GrapheneOS image for your device. Sometimes there's a hardware issue that leads to seeing this screen. I've had it happen only once and sideloading resolved it without wiping any data, your experience may differ. See here for steps: https://grapheneos.org/usage#updates-sideloading
HoldMyBeer Probably9857 Any idea how I could identify that the device has such problem? But exactly after entering the incomplete PIN and OK getting a hardware failure? Not too much coincidence?