Pixel 4 - FAce Unlock issue - Not working - Google Pixel 4 Questions & Answers

Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
I haven't seen this issue and face unlock works properly even with sun glasses on. Contact Google(chat/call) see what they say.
https://store.google.com/repaircenter

I don't have much issues with Face Unlock, but please keep us informed what the Google Repair Center says about that issue you have, pdash79.
But I have questions about this Face Unlock:
- How much of the face needs to be visible (means, unmasked due to Corona infection preventing rules) to make that thing work?
- Can a second "Face pattern" (one with masked face) be learned so the unlock works even with mask up?

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
Yeah I just did a warranty claim over this issue. Curious did u flash a rom ? Anyway it just stopped working out of the blue

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
I have had the same problem, and I have flashed several times until I realize that the problem is in the update of April 5, flash an old ROM and it is solved

gaseoso said:
I have had the same problem, and I have flashed several times until I realize that the problem is in the update of April 5, flash an old ROM and it is solved
Click to expand...
Click to collapse
Hey. Thanks a lot man. I did flash a rom from Jan and it did solve the issue.
Thanks a lot for your advice.
Saved me hell lot of trouble.
Was troublesome to use pin or pattern.
Hope google resolves it in future updates.
But they have not even acknowledged it seems.
Stll hope then fix.
Thanks again.

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
Had this also and the problem was that I installed a custom kernel.
Flashed a new firmware on the phone and it works again.

I had same issue, so i did flash older rom to fix it, just want to know if the may 2020 update solve the problem before i download the update

I had issues with the face unlock twice already while having the phone.
I wasn't able to re-enroll my face and got error messages.
Since my bootloader is unlocked I figured that locking it will wipe it completly (factory reset did not help by itself)
Indeed, after locking, and unlocking the bootloader, the issue resolved. twice.

Just curious is anyone has had this problem with a locked bootloader (never unlocked) and only did OTA updates?

bobby janow said:
Just curious is anyone has had this problem with a locked bootloader (never unlocked) and only did OTA updates?
Click to expand...
Click to collapse
Not me, as I unlocked the bootloader since day one.
But, it did happen to me once after OTA (sideloaded).
Try to unlock and re-lock your bootloader, it should resolve it but all content of the phone will be erased.
The reason I think it works is that the biometric is saved somewhere not reachable but since unlock/lock operations are so data destructive so it is probably erasing old/corrupted bio info.

thehartk said:
Not me, as I unlocked the bootloader since day one.
But, it did happen to me once after OTA (sideloaded).
Try to unlock and re-lock your bootloader, it should resolve it but all content of the phone will be erased.
The reason I think it works is that the biometric is saved somewhere not reachable but since unlock/lock operations are so data destructive so it is probably erasing old/corrupted bio info.
Click to expand...
Click to collapse
So you're not having any issues at all? If I go to the March build it works again but as soon as the phone updates it's broke again! If I use the Android 11 preview it works but they're too many bugs I've tried several times to wipe and lock and unlock the bootloader but nothing will get it working!

The guys from Russian 4pda, made a magick module that fixes face unlock, for whom it does not work on April and May firmware.

OK, I made a module for for Magisk to fix Face Unlock
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP

How to add a link?
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
Displax said:
OK, I made a module for for Magisk to fix Face Unlock
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
я не успел?

DanDroidOS said:
So you're not having any issues at all? If I go to the March build it works again but as soon as the phone updates it's broke again! If I use the Android 11 preview it works but they're too many bugs I've tried several times to wipe and lock and unlock the bootloader but nothing will get it working!
Click to expand...
Click to collapse
I'm on April build and it works.
I had the issue when updating from March to April, did my routine and all is good now.

Displax said:
OK, I made a module for for Magisk to fix Face Unlock
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Worked perfect, thank you! :good: How did Google manage to break FU with the update and why are only some affected?

Guys, anyone tried May update and see if the problem solved from who's getting the issue before on April update?
I'm still using an old update till someone try and till us

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
go into your camera app settings and disable frequent faces. restart your phone and try out the face unlock

jalado said:
go into your camera app settings and disable frequent faces. restart your phone and try out the face unlock
Click to expand...
Click to collapse
I updated to May 2020 Security update.
Then tried out disabling frequent faces, restarted and tried the face unlock.
Bow it is giving the message that Hardware not found.
I thought of removing face data and re-adding it and then trying.
It does not even let me delete my face data.
Please advise what i can do to fix it.
Thanks,
Pdash

Related

Issue with fingerprint scanner and back up password

For some reason it is now saying my finger print is not recognised and won't accept it so when I try to change it using my back up password it also says that is incorrect. I have not changed it or anything. Is there a way of fixing this I am hoping I don't have to do a complete restore on my phone.
Babychan said:
For some reason it is now saying my finger print is not recognised and won't accept it so when I try to change it using my back up password it also says that is incorrect. I have not changed it or anything. Is there a way of fixing this I am hoping I don't have to do a complete restore on my phone.
Click to expand...
Click to collapse
There is a guide on the forum for bypassing the fingerprint scanner without wiping the phone. I havent accessed the thread nor using the guide as I never needed it though.
NickVXD said:
There is a guide on the forum for bypassing the fingerprint scanner without wiping the phone. I havent accessed the thread nor using the guide as I never needed it though.
Click to expand...
Click to collapse
I can unlock my phone as I managed to change it to using a pattern lock. But I want to change it back to o fingerprint but it won't allow me.
Babychan said:
I can unlock my phone as I managed to change it to using a pattern lock. But I want to change it back to o fingerprint but it won't allow me.
Click to expand...
Click to collapse
Maybe a defective fingerprint scanner?
i have the same pproblem, worked all fine, then i wanted to chance my fingerprints, did the first 10 swipes, then it said, there is a problem, couldnt do the 2. 10 swipes.. after that i deleted data and all, now it says i have a fingerprint on it, but it wont detect it, nor will the password work, i didnt factory restore yet, since im waiting for 5.1.1. to do so, hope it fixes it, but id love to know what the problem is.. cheers
I have the same problem with the backup password, I wiped everything no cure without root .
oMaRcO said:
I have the same problem with the backup password, I wiped everything no cure without root .
Click to expand...
Click to collapse
So you did a restore and it didn't fix it?
Wip data via recovery, and don't use finger print in 5.1.1. I restored my data via Samsung smart switch.
---------- Post added at 10:06 PM ---------- Previous post was at 09:55 PM ----------
Check this thread
http://forum.xda-developers.com/showthread.php?t=2958069

S7 Edge Fingerprint sensor not working ! HELP

hello everyone ! I'm facing some serious issue with my s7 edge with fingerprint not working. it gives this' An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device.
It's NZ model G935F. So far I have done this but no luck:
1) restarted device
2) wiped cache and data resest
3)flashed stock rom with odin
4) rooted phone with chain fire, Installed titanium backup and from fingerprint app delete data and restart phone! No luck.
5) When i run *#0*# test fingerprint sensor test it says ' Fingerprint initializing Fail '
What else I can do ? I'm currently in India and can't access warranty as it was bought in New Zealand.
indergill said:
hello everyone ! I'm facing some serious issue with my s7 edge with fingerprint not working. it gives this' An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device.
It's NZ model G935F. So far I have done this but no luck:
1) restarted device
2) wiped cache and data resest
3)flashed stock rom with odin
4) rooted phone with chain fire, Installed titanium backup and from fingerprint app delete data and restart phone! No luck.
5) When i run *#0*# test fingerprint sensor test it says ' Fingerprint initializing Fail '
What else I can do ? I'm currently in India and can't access warranty as it was bought in New Zealand.
Click to expand...
Click to collapse
I"LL provide DONATION to whosoever can help me !
Id be reflashing a stock rom if all else has failed. If that doesnt work then its a hardware fault. Have you flashed any custom kernels or mods? Have you wet the phone at all?
indergill said:
hello everyone ! I'm facing some serious issue with my s7 edge with fingerprint not working. it gives this' An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device.
It's NZ model G935F. So far I have done this but no luck:
1) restarted device
2) wiped cache and data resest
3)flashed stock rom with odin
4) rooted phone with chain fire, Installed titanium backup and from fingerprint app delete data and restart phone! No luck.
5) When i run *#0*# test fingerprint sensor test it says ' Fingerprint initializing Fail '
What else I can do ? I'm currently in India and can't access warranty as it was bought in New Zealand.
Click to expand...
Click to collapse
Ausboy 2011 said:
Id be reflashing a stock rom if all else has failed. If that doesnt work then its a hardware fault. Have you flashed any custom kernels or mods? Have you wet the phone at all?
Click to expand...
Click to collapse
As I said in 3) I have already flashed stock rom and no luck. I just got it from someone so not aware of mods or custom kernels.
Hardware fault then best take it to samsung or refund it
Ausboy 2011 said:
Hardware fault then best take it to samsung or refund it
Click to expand...
Click to collapse
I wish I could ! I bought it from New Zealand but I'm in India now so need a solution!
indergill said:
I wish I could ! I bought it from New Zealand but I'm in India now so need a solution!
Click to expand...
Click to collapse
Hey, Did you fix it? if so, please let me know ..I have the same problem.
This happens to me when I downgrade to Marshmallow from Nougat. Reverting back to Nougat resolves the issue but I wish to downgrade, is there a solution to this?
i23u8 said:
This happens to me when I downgrade to Marshmallow from Nougat. Reverting back to Nougat resolves the issue but I wish to downgrade, is there a solution to this?
Click to expand...
Click to collapse
Yep same thing here. Appears to be an issue with newer hardware releases though the sensor firmware is the same. I wish someone could figure this out.

phone crashed - Fingerprint deleted - 120 Minutes lock after wrong

Hi,
yesterday evening my redmi 3s (http://www.gearbest.com/cell-phones/pp_487801.html) crashed while I used facebook App.
it restarted
i gave in sim-Pin
but normally i use fingerprnt to unlock the phone - this does not work any longer - I tried to unlock the phone with my formerly used pattern but it does not work. perhaps i don't remember. perhaps it is erased, too?
now i can try a pattern each 120 Minutes - then phone is locked if pattern is wrong.
Do you have any ideas how to fix this? this is really important because i do not want to make new rom to the phone.
thank you in andvance
qwerqw said:
Hi,
yesterday evening my redmi 3s (http://www.gearbest.com/cell-phones/pp_487801.html) crashed while I used facebook App.
it restarted
i gave in sim-Pin
but normally i use fingerprnt to unlock the phone - this does not work any longer - I tried to unlock the phone with my formerly used pattern but it does not work. perhaps i don't remember. perhaps it is erased, too?
now i can try a pattern each 120 Minutes - then phone is locked if pattern is wrong.
Do you have any ideas how to fix this? this is really important because i do not want to make new rom to the phone.
thank you in andvance
Click to expand...
Click to collapse
Always you Turn ON or reboot the phone, you must (Yes or Yes) get Unlocked with the Pattern or Pin, the Fingerprint do not work until the phone is unlocked at leat one time.
If you do not remember the Pattern or Pin, you sould to do a factory reset from recovery or flash MIUI rom via fastboot.
kukuteku said:
Always you Turn ON or reboot the phone, you must (Yes or Yes) get Unlocked with the Pattern or Pin, the Fingerprint do not work until the phone is unlocked at leat one time.
If you do not remember the Pattern or Pin, you sould to do a factory reset from recovery or flash MIUI rom via fastboot.
Click to expand...
Click to collapse
that's what i did not want to hear
thank you
i remember a thread on xda about bypassing lockscreen but i can't find it anymore. i think it was on hacking forum. maybe google will help you
merlin.berlin said:
i remember a thread on xda about bypassing lockscreen but i can't find it anymore. i think it was on hacking forum. maybe google will help you
Click to expand...
Click to collapse
ok - thank you.
might work:
https://www.google.de/search?q=bypa...en&aqs=chrome..69i57&sourceid=chrome&ie=UTF-8

Screen lock was already changed. Please try again with the new screen lock.

On android 10 nov update.
I didn't set any security because I was testing/setting up the phone till I liked it first.
However when I try to set one now, I get said error from the thread title.
Googled it, returned 2 results with no solution other than 'just factory reset it', which I'm guessing is probably the only 'fix', but hoping someone would know what to do.
anonxlg said:
On android 10 nov update.
I didn't set any security because I was testing/setting up the phone till I liked it first.
However when I try to set one now, I get said error from the thread title.
Googled it, returned 2 results with no solution other than 'just factory reset it', which I'm guessing is probably the only 'fix', but hoping someone would know what to do.
Click to expand...
Click to collapse
Do This It will Work Tried and Tested
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
Do This It will Work Tried and Tested
for video reference -https://www.youtube.com/watch?v=WOsUbcTQhrY
Above link is not my video so

Help? Fingerprint Reader Stops Working ONLY After Bootloader Re-lock?!?

Hey guys...I know I posted this in the persist thread, but I figured it might deserve a dedicated post here just in case there's a bigger issue at play or is something that's relatively unknown.
So long story short, unlike many on here I wanted to go back to a stock, locked, unrooted state after being unlocked & rooted (otherwise stock OOS) for a couple months. Unfortunately, upon doing this my fingerprint scanner stopped working (instantly errors with "enrollment was not completed - fingerprint registration error, please try again" when trying to enroll a fingerprint).
So when the guide came out the other day to repair the fingerprint scanner I tried it. I started off by re-unlocking my bootloader (from full stock, locked, unrooted) so that I could grab the persist partition backup that I hadn't done before. After rebooting suddenly, magically my fp scanner started working again. Then after verifying I could enroll several fingerprints, I booted to TWRP (didn't flash it, just booted) and flashed the magisk zip.
After this, I rebooted and backed up my now-working persist.img partition.
I then did a factory reset from the settings menu, which should return the device to 100% stock. After the reset, I verified during initial setup that the fp scanner was still working properly. I then rebooted to fastboot, and upon re-locking the bootloader received a g.co/ABH message in red saying the device was corrupt and that it would not boot.
I then used the latest 10.5.10 MSM tool to re-flash back to full stock again, which caused it to then boot up as expected. At this point, I tested the fp scanner again during initial device setup and it was once again back to not working.
I then re-enabled OEM unlocking in settings and rebooted to fastboot again. Another bootloader unlock. After reboot I tested the fp scanner again during initial device setup. Lo and behold, it's back to working again.
So I stopped midway through the fp enrollment (just hit back, didn't complete) and rebooted back into fastboot mode. Re-locked bootloader again and booted back up. FP scanner again back to not working with the same "enrollment was not completed - fingerprint registration error, please try again" error.
And once again I re-unlocked the bootloader, enrolled a FP during setup, and then used the MSM tool again. After MSM it again produced the same results - FP scanner wouldn't work upon reboot.
And before anyone asks - I am in contact with OP support for either a warranty replacement or a repair...but this whole situation just doesn't make even the slightest bit of sense to me. Basically my FP scanner works perfectly fine with an unlocked bootloader, but any attempt at re-locking it renders it useless. I do have a working persist backup, but obviously can't flash it from a locked state. Anyone else have any suggestions on something to try, or at least have any sort of theory as to why this behavior would be happening? I have never had a phone where attempting to RE-lock the bootloader has been such a freaking pain.
No one has any idea on this, or theories as to what could be taking place and causing this? OP support has been a total trainwreck so far.
Hi, Did you get a solution for this ? I am facing the same issue of fingerprint sensor not working after relocking the bootloader, although in my case I did not have to reflash the persist img. It works when unlocked and stops working when locked. As usual OP after sales are not really helpful. Thanks
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
shakathesaint said:
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
Click to expand...
Click to collapse
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
AarSyl said:
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
Click to expand...
Click to collapse
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Related, on 11.0.2.2 magisk and unlocked, my fingerprint sometimes won't recognize at all and forces password unlocks. No corrupt persist or delete and re register a finger solved it.
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
Oh, thank you! I will certainly try!
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
I'm writing just to update about the tests above: unfortunately neither of them is working, so I'm starting to think there's no other solution than sending the phone to RMA.
Has any one found a solution for this? Im facing exactly the same problem.

Categories

Resources