January Update
- Thread starter johnny8910
- Start date
Anyone else finding face unlock is now broken after the January update?
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
Hasn't happened for me but if you're having issues go back to December update with a clean flash. Then take the January update before you root. Once it's downloaded and installed then root.
I've tried all sorts of things to get it fixed, including what you mentioned. But it remains broken.
I've tried...
1) Clean flashing the January image again
2) Clean flashing the December image (which previously worked perfectly)
3) Clean flash December and let it auto-update to the January update before attempting to set up face Unlock
None of the above have solved the issue and now, no matter what image I clean flash, I get an error telling me a new face can't be added because there is old face data already uploaded. It gives me no way to remove the old face data in any clean flash I install. This has truly become a serious problem, at least in my case.
My only hope at this point is for Google to roll out an update/fix to correct it. Otherwise, the only other option I can think of is to RMA, which would suck because the phone has been flawless until now. Extremely annoying.
Are you making sure you're using the right build number? Mess ups like yours can be a result of flashing the wrong build.I've tried all sorts of things to get it fixed, including what you mentioned. But it remains broken.
I've tried...
1) Clean flashing the January image again
2) Clean flashing the December image (which previously worked perfectly)
3) Clean flash December and let it auto-update to the January update before attempting to set up face Unlock
None of the above have solved the issue and now, no matter what image I clean flash, I get an error telling me a new face can't be added because there is old face data already uploaded. It gives me no way to remove the old face data in any clean flash I install. This has truly become a serious problem, at least in my case.
My only hope at this point is for Google to roll out an update/fix to correct it. Otherwise, the only other option I can think of is to RMA, which would suck because the phone has been flawless until now. Extremely annoying.
Also try going back to stock unrooted with the bootloader relocked. Then try again. Other than that you may have to contact Google.
I have a carrier unlocked US Pixel 4 and used the top factory image in this screenshot:
Also, the December image I tried re-flashing was the proper image that had face unlock working perfectly up until moving to the January image.
It would be amazing if I simply flashed the wrong January image. However, even going back to the previously working December image (which was saved on my PC) didn't solve it. So I'm not confident that this is the case.
Also, I want to reiterate that face unlock WAS working for the first few days after flashing the top January image in the above screenshot. It only stopped working a few days after flashing when I got a random notification to re-enroll my face. After that, it was broken and there is seemingly no fix. I also haven't rooted my Pixel 4. Looks like I need to contact google.
Last edited:
That's my main concern. I'm thinking about just testing one of the other January factory images to see if I can get lucky. I really have nothing to lose, at this point.
regardless, it does look like this issue is a bit more wide spread than just me...
https://www.androidpolice.com/2020/...ken-for-some-may-be-caused-by-recent-patches/
https://www.androidcentral.com/pixel-4s-face-unlock-inexplicably-broken-some
https://bgr.com/2020/01/10/pixel-4-face-unlock-not-working-authentication-failure-and-fixes/
https://9to5google.com/2020/01/09/pixel-4-face-not-available/
Can someone explain what "NTT DOCOMO" means in the bottom factory image from my above screenshot? I'm thinking about giving that a try. I know the "TW & JP" version is "Taiwan and Japan", so I'm not going to bother with that one.
On another note... when did Google start resorting to confusing factory image labels? I've had all the Pixel phones since the Pixel 1 and I have to say, the naming conventions Google is now using for factory images is the most confusing I've ever seen. They aren't even consistent, month to month.
---------- Post added at 12:35 PM ---------- Previous post was at 11:57 AM ----------
UPDATE: Face Unlock fixed!! :highfive:
I should have paid this more mind. I was digging around and saw someone on the Google support forum report that simply relocking and unlocking the bootloader solved the problem as relocking and/or unlocking the bootloader is the only way to do a 100% true wipe, which erases previously stored face data.
So I relocked the bootloader, immediately unlocked it again before even booting up. Then booted, went back through setup an VOILA! Face unlock working again. Extremely relieved right now.
QQ1B is the correct build.
You may have hardware failure.
---------- Post added at 05:34 AM ---------- Previous post was at 05:32 AM ----------
That's why I was thinking it was hardware failure. Because if relocking the bootloader didn't fix it then it had to be hardware related. Because without twrp to do a full wipe the only way to completely wipe the phone is by relocking the bootloader.
Glad it's fixed!
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone