Related
Hi,
I bought the Samsung Galaxy S5 and the fingerprint reader works reasonably well (as in it works, nothing in comparison to apple though, so don't buy it for the fingerprint reader ) for unlocking the screen...
However its a work requirement that my phone has full device encryption, as phones are regularly stolen where I travel.... it seems when I enable encryption I lose the ability to use the fingerprint reader to unlock the phone .... I bought this hoping that I could avoid having to type in my complex password just to unlock the screen, as I got so tired of doing that with my S2
Is there any mods to enable finger print reader screen unlock + full device encryption at boot time for the Galaxy S5 yet? ... I saw some references to pattern unlock / pin with device encryption... but I would think the fingerprint reader is different...
Thanks!
S5 Full disk encryption with fingerprint unlock
I also have this question. I believe on the Nexus 5 it at leasts lets you use face unlock with full device encryption. And I read on one article that you should be able to do this but i do not think the author actually tried this. I will say from my own personal experience that you can infact decrypt the device after encrypting it without doing a complete wipe of the device and you can restore the use of fingerprints to unlock your phone. It seems like for security minded people this would be a great feature but if it is unable to be used with full device encryption it seems a little pointless to me. Being forced to use a PIN or password to use encryption is a big pain point for android users who want some type of security.
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
androidpleb said:
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
Click to expand...
Click to collapse
I am having the same pain, as I use my S5 for BYOD.
It makes no sense when you can use fingerprint to make payments with paypal but not unlocking the phone when it is encrypted.
Hope Samsung can enable this feature in next update.
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
sorphin said:
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
Click to expand...
Click to collapse
I can't believe that the fingerprint sensor can't be used if encryption is enabled whatsoever. I could understand the iPhone model, requiring a pin before a fingerprint can be used, but by disabling fingerprint lockscreen, boot unlock, and SD unlock, the fingerprint sensor is now wholly useless for convenience.
It's too trivial to extract data from an unencrypted Android. By not supporting encryption with a measure of covenieve, I don't see the point in including a fingerprint sensor whatsoever given the current software limitations.
Please, someone, figure out what sqlite/settings need to be changed so we can make decent use of our phones fingerprint sensor.
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Boot Loop
fabiokino said:
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Click to expand...
Click to collapse
I get samsung boot loop using the above instructions
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
Hi guys! Did someone try this solution? I unfortunately have the same issue and unlock my device each time make me crazy!
Thanks in advance.
Same problem
I purchased a Galaxy S5 and I have the same problem, unfortunately I cannot root my phone due to security policies in my company. :crying:
I hope Samsung will solve the issue. :fingers-crossed:
Have anyone contacted to Samsung Support Center?
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
What is the consequence of boot loop if you are using stock boot loader? Odin mode required to recover? Something less drastic? What device model are you using?
I found a possible solution that involves deactivating SuperSU and running encryption from there. Still investigating. I am thinking that the solution from @fabiokino will work in this case too.
I'm curious about this aswell.
Doesn't anyone know a working solution?...
It is really frustrating the very least. I can't believe there isn't a way (or if there is, a guide) to do this (with or without root access).
I have also heard it is doable on the Note 4. See this post for example http://forum.xda-developers.com/showpost.php?p=57103664&postcount=7.
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
How?
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Nice to see this, hope it will work on my Galaxy tab S too
Did you see this?
https://www.jethrocarr.com/2013/12/29/encrypting-disk-on-android-4/
GermanDoerksen said:
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
Click to expand...
Click to collapse
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Joker87 said:
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Click to expand...
Click to collapse
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
GermanDoerksen said:
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
Click to expand...
Click to collapse
You could root then unroot it after you have encrypted it
Joker87 said:
You could root then unroot it after you have encrypted it
Click to expand...
Click to collapse
you're right... plus it's not really the "rooting" process that makes it slow, it's installing another ROM. Having a rooted phone doesn't necessarily have any performance impact... just opens up a few things for me. Interesting. Thanks! Unfortunately I've already encrypted so now I have to find that thread about how to decrypt lol.
Thanks!
Dear guys. I setup a fingerprint (F1) and a backup code. After, I have set up another fingerprint (F2) while the other one was active. I have deleted F1, but the unlocking screen requires it. To deactivate this unlocking way, I have to insert the deleted F1.
What can I do?
Gotlaub said:
Dear guys. I setup a fingerprint (F1) and a backup code. After, I have set up another fingerprint (F2) while the other one was active. I have deleted F1, but the unlocking screen requires it. To deactivate this unlocking way, I have to insert the deleted F1.
What can I do?
Click to expand...
Click to collapse
this thread belongs to qa and help section
but heres your fix. didnt try. this thread might solve ur issue without resetting ur phone.
http://forum.xda-developers.com/note-4/help/bad-suprise-fingerprint-scanner-twrp-t2933878/page5
So I fell victim to googles new FRP Security feature that requires you to log in using the same gmail account associated with the phone before it was reset. Short of it was I decided to flash a 6.0 ROM after using the 5.1.1 ROM to get my Project Fi account activated correctly.
After flashing 6.0 and I began going through the setup wizard where I was eventually prompted to enter the credentials for the account that I had used previously. I entered my credentials and was then sent to another screen asking me to reset my Gmail password (Turns out google decided my login attempt was suspicious...). So i reluctantly reset the password not knowing I had just screwed myself(for 72 hours at least). There is a 72 hour reset time from the time you changed your account password until you're able to use it to authenticate during the setup process and until you authenticate you cant use the phone.
Not having a backup phone I took to google and found that the only way around this problem involved a USB OTG storage device loaded with an apk that causes the settings app to launch allowing you to do a real factory reset(complete wipe of all credentials and data). Resetting the phone this way removes any account associations allowing you to setup the phone as if it were new once you've re-flashed it.
Not having the tools needed to do it that way I thought about it and decided to try a few things out and eventually found my solution.
Disclaimer: I am not responsible for any damage or loss of data that may result from the following procedure.
Solution
Requirements
A computer with adb installed
USB cable
Rom with Persistent ADB Enabled (I used the 5.1.1 Stock, Rooted Project Fi ROM)
Phone booted and at the Setup Wizard
Procedure
Have the phone turned on and sitting at the startup wizard
Connect the USB to you computer and then plugin your phone ( I assume you've already setup ADB)
The phone may then prompt you and ask to verify the device fingerprint which you will say yes to
open a terminal and type:
Code:
adb shell
Code:
am start -S com.android.settings -c android.intent.category.LAUNCHER 1
This will launch the Settings.apk
***NOTE: This will completely wipe your phone!*** (Edit: The Reset program claims to wipe all internal storage but for whatever reason my SDcard data was not touched. Would still recommend pulling any wanted data from the device prior to resetting)
Go to the Backup & Reset menu and perform a factory reset
After the phone finishes resetting, proceed to boot back into Recovery mode and re-flash your ROM
The Setup Wizard will now go through the steps without the FRP authentication steps.
Again, I have only tested this on my T-Mobile Nexus 6 (using Project Fi) running 5.1.1 so your mileage may vary depending on your setup. If you find this worked or didn't work for your particular setup/situation then post your results here.
Hope this helps!
EDIT: The original solution using the USB OTG storage can be found here.
Just to clarify a bit. The problem that these two methods try and fix stems from a new feature introduced in Lollipop called FRP(Factory Reset Protection). It is meant to keep someone that has stolen a phone from being able to use it by simply doing a factory reset and reinstalling the OS. To counter this, google requires the user to verify they're the owner of the device that was reset by giving the credentials of the google account associated with the phone before it was reset. The issue arises when the password to this account is changed after the device was reset but before verifying ownership of the device during the setup process. When this happens, you have to wait 72 hours before you will be able to verify ownership using the new password.
Edit 2: Specified having a ROM with Persistent ADB Enabled as a requirement for this to work.
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
...snip...
Click to expand...
Click to collapse
Ah, a workaround, nice!!! Tahnks for sharing!
Keep "OEM unlocking" enabled in the future. It will disable "Device protection"
---------- Post added at 02:27 PM ---------- Previous post was at 02:27 PM ----------
ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This is not about 2 way auth i'm affraid
ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No, this isn't an issue with 2FA. From Google's standpoint this isn't an issue at all actually. This verification is, to my understanding, only required when the device is factory reset in recovery mode.
The purpose of 72 hour lock period seems to be there to protect user in the event someone is trying to gain access to their phone/account.
This normally isn't an issue since most people won't change their password in that small timeframe. In order to not require the verification, you have to disassociate the account from the phone before resetting it. This is done for you when you do a reset from the settings app on the phone. That's the reason for using these methods, it does a full reset including account removal.
Sent from my Nexus 6 using Tapatalk
@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!
Droidphilev said:
@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!
Click to expand...
Click to collapse
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
perfect, thanks!
Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.
player911 said:
Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.
Click to expand...
Click to collapse
That was my thoughts exactly as it was happening to me, I initially was trying to figure out if there was an alternate authentication method and was a little surprised not to find one.
I really like the direction they're moving with thus security feature but I think it was thrown out a bit early. Nexus users are more likely to be doing factory resets and locking them with no way of fixing it (aside from waiting 3 days) out because they did so on a custom recovery isn't very cool on their part lol.
Sent from my Nexus 6 using Tapatalk
sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, that will work just fine.
yossijoe said:
So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.
Click to expand...
Click to collapse
It worked for me. Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
Edit: It could be that the project fi ROM has USB debugging enabled by default(just a guess, haven't looked at the source to verify).
Edit 2: Confirmed that the Stock, Rooted, decrypted 5.1.1 ROM for Project Fi has persistent ADB enabled. Adding this as a requirement to the original post.
Sent from my Nexus 6 using Tapatalk
sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
He's wrong, that absolutely will not be fine.
You need to make sure to remove any screen locking you've setup, sync your Google account, and then remove your Google account before resetting.
http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504
My nexus 6 doesn't have custom recovery installed,It has only stock one,the phone is on stock rom,and it is stuck in setup screen asking for 1st used gmail !
I have OTG usb cable but it is useless ,not working, seems motorola improved security in nexus 6,to be specific the phone has OEM lock ,so i can't install cust.recovery
is there any trick to apply those adb commands ?
any help friends ? im still stuck ,any way to disable OEM lock or to flash custom rom on frp locked nexus6 ?
joyrida12 said:
Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
...
.... the project fi ROM has USB debugging enabled by default
Click to expand...
Click to collapse
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5
W60 said:
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5
Click to expand...
Click to collapse
Hey, first time poster, long time lurker. This is the first thing I have not been able to find a solution for.
In order to connect to ADB in recovery, does one need a custom recovery? My Nexus 6 bootloader is locked, running 5.1.0 LMY47D. I have fastboot access but can't pull up an ADB shell.:crying::crying:
I bought a Nexus 6 on eBay that was reset and I do not have the original users info. (I thought I was getting a pretty sweet deal because I'm so good at phones and blah blah)
Thanks in advance for any assistance!
- Beej
Beej4real said:
In order to connect to ADB in recovery, does one need a custom recovery?
Click to expand...
Click to collapse
As far as I know, yes, you need a newer version of a custom recovery. Anyway, if ADB doesn't connect, you certainly need another recovery, and you can't install that if you have a locked bootloader.
....
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?
W60 said:
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?
Click to expand...
Click to collapse
I did give it a shot. No dice. I also tried entering lots of numbers in as the emergency number. No response from the phone.
Hi guys can you help to frp bypass on Samsung SM-G530H Galaxy Grand Prime without otg function, can i use this tut or need another rom for sm-g530h? where i can find Rom with Persistent ADB Enabled? Thanks
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
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