Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?
PriyanPhoenix said:
Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?
Click to expand...
Click to collapse
In this case, even a factory reset might not help.
Just to confirm, should anyone else have the same issue, a factory reset did solve the problem and the error has not returned. Still no idea what could have caused it though.
Solution
I had this problem also just hold the power button down for like a minute.
I'm having the same problem, was working fine a few hours ago then not recognizing the pattern. I've tried holding the power button but that just powers it off. When I turn it back on it asks for my pattern to power the device back on and it recognizes the pattern then just fine but once it power's up and I try to put the same pattern in to unlock the screen it says wrong pattern!! What the hell is going on here? Any help please?
This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.
NJ72 said:
This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.
Click to expand...
Click to collapse
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.
1barlog17 said:
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.
Click to expand...
Click to collapse
Yes, Google sent me a new unit. They didn't advise to do a factory reset, they just advised to return the unit. Part of their RMA process is that they recommend you wipe data (for data protection) so I ended up doing both.
I imagine that there are other apps which would offer access to your device data without unlocking, I just have experience with Airdroid.
I also had this problem, but I was using a pin instead of a pattern. Very concerning to be locked out of your own tablet. Had the tablet for about 3 months before it happened. Factory reset fixed it, hasn't returned since but only time will tell. Doesn't inspire a lot of confidence in the device knowing that maybe you could get locked out at any moment.
The same problem has been found on the Nexus 6p. Lockscreen not unlocking with the correct pin/password, appears to be a problem with the lockscreen as the phone can be booted or decrypted with the correct password.
The suggested fix was to ensure you have prey or another similar program installed. Changing your unlock password remotly via prey fixes the problem allowing you access to your phone.
Just had this problem today. Went to login with the same pattern I've been using for the past 3+ months, and it said "Wrong Pattern" over & over again. I tried to reboot and try again, same story. I used Android Device Manager to lock it & entered a password. Then my Pixel C confirmed that it was locked via the Android Device Manager, but when I went to log in, it asked me for a pattern, not a password! (Bad sign!) And, of course, I entered the right pattern and it told me it was the wrong pattern.
The Google support rep said I had to do a factory data reset. It is indeed disconcerting and frustrating. Next time I'll use Backup!
are you guys rooted? I had this problem on my N5X during rooting and trying to install ROMs. wiping data helped but I simply reset the device anyway. I noticed this also happened on some devices when an incompatible version of SuperSU was installed. If not rooted then you got me.
I am not rooted. I haven't done anything to the tablet except install & use apps and install a p12 certificate (which, I believe, unfortunately, requires you to use some kind of lock screen).
So, I used Android Device Manager to erase my tablet & the problem went away. Yay! I changed to using a PIN instead of a pattern. Now, today, just over a week later, the problem has recurred. <sob!> It says "Wrong PIN" when I try to login, even after powering off & on again, and I am facing the prospect of having to go through all that again.
Just had the same issue, tablet not rooted no developer options unlocked/used just left as factory with apps installed from play store.
Factory reset in progress...
Just happened to me (on the official beta ROM)
This just happened to me today on my Pixel C. I found threads on Google Forums that this has been happening for over a year without a fix.
If your bootloader is unlocked, you can always boot TWRP, Advanced > File Explorer, change to /data/system and delete locksettings.db, locksettings.db-wal and locksettings.db-shm.
Does anybody has an idea here? I'm confronted with this issue: Wrong PIN. No matter how many times i give the correct PIN
restarting Pixel C does not help. Is there any other way to fix this issue?
Shame on Google for this!
farsiray said:
Shame on Google for this!
Click to expand...
Click to collapse
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.
bornheim2 said:
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.
Click to expand...
Click to collapse
Looks you have no clue what you're talking about. Do some more reading before you give a useless comment.
This is an issue with Pixel C since 2016, Google still hasn't fixed it.
https://issuetracker.google.com/issues/62404336
https://productforums.google.com/fo...ce=footer#!msg/nexus/ImQsmQ8-8JA/n-1kqOv9AwAJ
Related
I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.
I'm also interested in this. So bump for a more knowledgeable member to comment.
I think this thread proved pretty conclusively that there is no real world performance benefit in decrypting.
I activated file encryption on my N5X, specifically to allow for direct boot. I had N with full disk encryption on my N5X for about 72 hours before switching. I see no performance difference -- it was smooth before, and it is smooth now.
rockhardy said:
I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.
Click to expand...
Click to collapse
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Thanks for your comment.
In that case i think i will be switching to File-based encryption to enjoy direct boot feature.
sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced
ABSathe said:
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced
Click to expand...
Click to collapse
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try. If it does help, it will probably be coincidence because you had to format user partition to decrypt your phone which is equivalent of factory reset.
sfhub said:
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try.
Click to expand...
Click to collapse
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks
ABSathe said:
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks
Click to expand...
Click to collapse
Before you do factory reset, I suggest you get rid of any pin/pattern/password you might have configured. This will disable the factory reset protection, just to be on safe side.
You can do it from android.
If you say this problem was there from beginning, then it probably migrated over from existing account restoration of apps. You might want to try installing onto a new google account to test that theory out. The install a couple of apps at a time while verifying everything remains stable.
Hi,
Do folks think that switching to File Based Encryption might help avoid this issue - a decryption failure on reboot with Factory Reset the only solution? My phone is 13 months old and now out of warranty and this has happened 5 times to date - once about 6 months ago, once about 3 months ago and then worryingly 3 times in the last month. Stock unmodified on 7.1.1
Hey, When will TWRP support this? I've been waiting for ages.....
So I gave my mother my note 4 rooted Ultimate Note7 Hybrid SM-N930P and I wiped everything before I gave it to her. But when setting up her phone it asks for pin number for screen lock so I make one. Then when trying to unlock it it won't allow it. It looks to go to the next screen but flashes then goes back to lock screen.
Any help would be appreciated.
Thank you
Willyb211 said:
So I gave my mother my note 4 rooted Ultimate Note7 Hybrid SM-N930P and I wiped everything before I gave it to her. But when setting up her phone it asks for pin number for screen lock so I make one. Then when trying to unlock it it won't allow it. It looks to go to the next screen but flashes then goes back to lock screen.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
Maybe a little late to reply but what did you wipe?
Recommended way to turn phone over to another user is to remove fingerprint(s) and accounts while booted. And make sure the reactivation lock isn't enabled.
You can factory reset after the above.
Maybe you can still factory reset but if that doesn't work, I don't know why it wouldn't unless reactivation lock is enabled.
Did you try the factory reset? Did that work or no?
Edit: if it's just a persistent fingerprint issue, try this but read the whole thread.
https://forum.xda-developers.com/showpost.php?p=63327098&postcount=1
Sent from my SM-N920P using Tapatalk
Willyb211 said:
So I gave my mother my note 4 rooted Ultimate Note7 Hybrid SM-N930P and I wiped everything before I gave it to her. But when setting up her phone it asks for pin number for screen lock so I make one. Then when trying to unlock it it won't allow it. It looks to go to the next screen but flashes then goes back to lock screen.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
Flash this zip file from twrp or any custom recovery and it will bypass any lockscreen security lock. pin/pattern/password/fingerprint.
https://mega.nz/#!fQ03xarS!Rmik-8KQSxvnZ9AYFsU_t03RdmjZeqwF-ahnXLQi41s
samep said:
Maybe a little late to reply but what did you wipe?
Recommended way to turn phone over to another user is to remove fingerprint(s) and accounts while booted. And make sure the reactivation lock isn't enabled.
You can factory reset after the above.
Maybe you can still factory reset but if that doesn't work, I don't know why it wouldn't unless reactivation lock is enabled.
Did you try the factory reset? Did that work or no?
Edit: if it's just a persistent fingerprint issue, try this but read the whole thread.
https://forum.xda-developers.com/showpost.php?p=63327098&postcount=1
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I wiped it from recovery mode with the TWRP
It isn't a finger print issue. It's the 4-12 digit pin number
Willyb211 said:
I wiped it from recovery mode with the TWRP
It isn't a finger print issue. It's the 4-12 digit pin number
Click to expand...
Click to collapse
Trying to help so I won't debate the issue. It's important to recall if you went back through setup wizard and were prompted for original user and account password.
I still don't know what partitions you wiped. You likely need to root again if you wiped data or factory reset. I thought a factory reset would remove fingerprints.
The reason I think it's a fingerprint issue is the prompt for pin after reboot. I think that still applies since it asks for one and won't unlock. On initial prompt after you wiped it, did you input your personal backup pin to unlock and set another pin? Original pin should be wiped but if not your accounts and likely prints still exist.
I may be wrong but you may have to restore a stock backup or go back to stock tar in Odin if the two suggestions given aren't helping. I'd suggest the same stock tar as before in case it is factory reset protection causing the issue. You may have use your original Google or Samsung account user and password to unlock it.
But before following through with Odin, one important thing to look for in phone's display is reactivation lock while phone is booted to download mode (for Odin). If enabled, factory reset protection is applied. I wouldn't flash but pull battery and factory reset and sign in with original user and password. The prompts should direct just that. After setup wizard, remove anything of yours like fingerprints and accounts and factory reset within system Settings app.
As I said in my initial reply, you need to remove your accounts and check for fingerprints and remove those if applicable. Then factory reset. I didn't mention it before but factory reset in system Settings app is recommended to avoid issues handing phone to another user. Not sure but it may be a more sanity check to ensure you've removed accounts and fingerprints and encrypted data. I forgot to mention encrypted earlier.
Sent from my SM-N920P using Tapatalk
Last night my phone got freeze and I decided to restart it, now when I turn it on the phone ask for a pattern before fully start, the problem is that when I put the pattern it doesn't work anymore, I'm not able to start the phone, when I put the pattern it stays for a long time in "cheeking" and finally fails, I have 3 more tries before it wipe everything.
What can I do?
Jerber said:
Last night my phone got freeze and I decided to restart it, now when I turn it on the phone ask for a pattern before fully start, the problem is that when I put the pattern it doesn't work anymore, I'm not able to start the phone, when I put the pattern it stays for a long time in "cheeking" and finally fails, I have 3 more tries before it wipe everything.
What can I do?
Click to expand...
Click to collapse
Assuming you have twrp, flash lock screen reset from here:
https://potterroms.me/Mods/
Cupcake 1.5 said:
Assuming you have twrp, flash lock screen reset from here:
https://potterroms.me/Mods/
Click to expand...
Click to collapse
Sadly not, the only way is just doing a factory reset?
I can't understand why the pattern doesn't work, I use it always.
Jerber said:
Sadly not, the only way is just doing a factory reset?
I can't understand why the pattern doesn't work, I use it always.
Click to expand...
Click to collapse
I have no answer, never heard of a phone locking you out when you know the pattern. The only cause I have heard is some android viruses can do this.
Cupcake 1.5 said:
I have no answer, never heard of a phone locking you out when you know the pattern. The only cause I have heard is some android viruses can do this.
Click to expand...
Click to collapse
The phone was on WhatsApp, in that moment it freezes and was like that for about a minute, then I decided to reboot it, I was reading about a similar case on Lenovo forums that pattern just stop working, I was able to use the fingerprint but when the startup is locked I can only use pattern, pass out PIN... Anyways I'll try a factory reset and pray to God to see if there is a backup of all my data.
Is frustrating because viruses can't be the problem, I don't use the phone to explore the web or download things, just the classic, WhatsApp, maps, Facebook etc.
Jerber said:
The phone was on WhatsApp, in that moment it freezes and was like that for about a minute, then I decided to reboot it, I was reading about a similar case on Lenovo forums that pattern just stop working, I was able to use the fingerprint but when the startup is locked I can only use pattern, pass out PIN... Anyways I'll try a factory reset and pray to God to see if there is a backup of all my data.
Is frustrating because viruses can't be the problem, I don't use the phone to explore the web or download things, just the classic, WhatsApp, maps, Facebook etc.
Click to expand...
Click to collapse
That's because of encryption, if twrp is installed wipe data, again reboot to recovery and wipe data, this will remove encryption
Hey there,
let me start off by saying that I don't own an XL, but a non-XL 3a. Since my question seems to apply to both devices (similar/same components), I'll try my luck here.
Recently, my 3a got stuck in SystemUI crashes and I tried every solution that came to mind and others suggested over at the 3a section (check my profile if curious, basically locked BL, fully stock, no ADB), but nothing solved the issue.
However, I didn't factory reset yet, but I'm confident that it would fix it. On the other hand, It'll also wipe my storage.
----
Long story short, the only option I can think of is to recover my files with a data recovery app/program after I have wiped/factory reset my phone.
Did anybody ever successfully used such an app on a Pixel or similar (A/B) partition layout? Is it even possible/viable? Are there special prerequisites to consider?
It goes without saying I'll make sure to overwrite as few sectors as possible, if any. I can accept some files getting lost in the process, but want to keep whatever I can recover.
Thank you for reading.
Your biggest issue is going to be the fact that the storage is encrypted. So even if you do wipe the phone, I don't think anything will be recoverable since it won't be readable.
Your data will not be recoverable after the factory reset... because it was encrypted. Part of the factory reset will wipe the encryption key (that will not be recoverable since it will be regenerated on the first boot) so your data is surely lost. You are in the worst possible scenario for data recover, honestly your best bet is probably just factory reset and accept that the data is gone forever.
xnifex said:
Your biggest issue is going to be the fact that the storage is encrypted. So even if you do wipe the phone, I don't think anything will be recoverable since it won't be readable.
Click to expand...
Click to collapse
acejavelin said:
Your data will not be recoverable after the factory reset... because it was encrypted. Part of the factory reset will wipe the encryption key (that will not be recoverable since it will be regenerated on the first boot) so your data is surely lost. You are in the worst possible scenario for data recover, honestly your best bet is probably just factory reset and accept that the data is gone forever.
Click to expand...
Click to collapse
Well, damn. Thanks nonetheless, I didn't even think about that.
I'll try to fiddle with the phone one last time, maybe I'll get it unlocked somehow (I can only get 7 or 8 dots
of my pattern connected before the UI crash kicks in...). This is literally the only thing that separates me from the storage.
This has to be the most infuriating small obstacle with the biggest effect for me.
Since you're stock, might get lucky if your software is good on your second slot. You'll have boot into fastboot mode abs try the command "fastboot continue" from command line on a computer. Plenty of fastboot guides online if you've never used it.
Credit to this thread: https://www.reddit.com/r/GooglePixel/comments/5cbc9m/bricked_pixel_xl/
brandontowey said:
Since you're stock, might get lucky if your software is good on your second slot. You'll have boot into fastboot mode abs try the command "fastboot continue" from command line on a computer. Plenty of fastboot guides online if you've never used it.
Credit to this thread: https://www.reddit.com/r/GooglePixel/comments/5cbc9m/bricked_pixel_xl/
Click to expand...
Click to collapse
Man, if that works out, I'd be insanely glad. Have to get my hands on my friend's laptop first though.
I mean, the UI just started crashing after I checked for an OTA without downloading, then changing the wallpaper. That was literally it. Hadn't I rebooted, I would have been able to still unlock with my fingerprint between each crash.
Here's hoping that ADB sideloading OTAs left that slot option intact.
Will definitely update this post; at the very least, thank you for your suggestion.
Update: "fastboot continue" as well as switching boot slot parameters aren't allowed on this locked bootloader.
ADB sideloading caused slots to switch anyway, and both slots seemed to be affected from the SystemUI crashing. Will edit my original thread with a conclusion now.
I am not sure if I am asking this on the correct forum but I have the following issue:
A few weeks ago I made a backup of my P6P (Google Backup). I have a temporary phone, where I restored my P6P backup on, while I still had my P6P. I downgraded and resetted my P6P, and sold the device. As I had issues with the temporary phone, I resetted it again. Now I am trying to restore the P6P backup on the temporary phone, but it only says ''Incorrect PIN'', but its the PIN I have used for years, and its also the PIN I have restored the backup with before. I have tried it on multiple phones, on A12 and A13 but the Incorrect PIN message won't go away. I have tried 8 times now, and after 10 failed attempts Google will delete the backup.
Relevant(?) information:
- I was running the P6P A13 Beta, downgrading to A12 was not successful, but worked after doing it through ADB
- Restoring the backup worked with the same pin code before the P6P reset and downgrade
I don't understand with what PIN the backup is locked with, as I have always used the same PIN.
I just want to check and make sure - you don't have a newer backup from your temporary phone?
I'm afraid I don't know the solution to the PIN issue. I have the feeling that there is no solution. Question: When you reset your P6P before you sold it, did you manually remove the PIN from it first?
If you did remove the PIN before resetting the phone, did you perform another backup after removing it?
I'm guessing that you did remove the PIN, because from memory, I think the buyer of your phone would've been prompted for your PIN even after a reset, as a security feature for stolen phones - this has happened to some other users who buy a used phone.
roirraW edor ehT said:
I just want to check and make sure - you don't have a newer backup from your temporary phone?
I'm afraid I don't know the solution to the PIN issue. I have the feeling that there is no solution. Question: When you reset your P6P before you sold it, did you manually remove the PIN from it first?
If you did remove the PIN before resetting the phone, did you perform another backup after removing it?
I'm guessing that you did remove the PIN, because from memory, I think the buyer of your phone would've been prompted for your PIN even after a reset, as a security feature for stolen phones - this has happened to some other users who buy a used phone.
Click to expand...
Click to collapse
Thank you for replying!
I just want to check and make sure - you don't have a newer backup from your temporary phone?
Unfortunately not, as my temporary phone had issues I had reset it after just a day, so I didn't check if it made a backup as I thought I could restore the P6P backup.
When you reset your P6P before you sold it, did you manually remove the PIN from it first?
No and yes. I tried downgrading through the official Google way first (A13 Beta->A12), but got stuck in a bootloop. So I flashed the downgrade through ADB. The phone was reset after the downgrade, as far as I can remember there was no PIN set after I performed the downgrade. To make sure the P6P was really reset, I did a reset once more.
If the buyer did have to fill in a PIN code, he would have contacted me right away. So there was no PIN. But there was a PIN set before the downgrade. But that PIN is incorrect.
It's just a weird issue that I have never encountered after switching phones every few months.
Jordytjes said:
Thank you for replying!
Click to expand...
Click to collapse
You're welcome!
Jordytjes said:
When you reset your P6P before you sold it, did you manually remove the PIN from it first?
No and yes. I tried downgrading through the official Google way first (A13 Beta->A12), but got stuck in a bootloop. So I flashed the downgrade through ADB. The phone was reset after the downgrade, as far as I can remember there was no PIN set after I performed the downgrade. To make sure the P6P was really reset, I did a reset once more.
If the buyer did have to fill in a PIN code, he would have contacted me right away. So there was no PIN. But there was a PIN set before the downgrade. But that PIN is incorrect.
Click to expand...
Click to collapse
That's surprising. Normally, yes, you have to manually remove all lockscreen security from a phone before factory resetting it to be assured the buyer of the used phone won't have trouble, but it's possible the Android 12 downgrade caused it to act differently. I don't know if the behavior is also affected by who manufacturers a phone, although my impression is that it's a Google requirement, so it wouldn't matter who makes the old or new Android phone. I don't remember what year this security was built into Android (to require the phone's last PIN after a factory reset). I feel that I'm not remembering all the details of this.
Jordytjes said:
It's just a weird issue that I have never encountered after switching phones every few months.
Click to expand...
Click to collapse
My only guess, then, is that this too was caused by the combination of not manually removing your PIN (and making another backup after, with no lockscreen security), and the downgrade to Android 12.
I wish I had more solid information for you. Unfortunately, I suspect there's nothing you can do about it.