I have a PRA-LX1 with unlocked and rooted Magisk. I tried to set a fingerprint screen lock but can not. I will enter the PIN code and then again. After that, I want to set the fingerprint authentication, ask for the PIN code, and the PIN you entered previously says it's wrong, there are only 4 attempts left.
What could be the problem?
No fingerprint authentication was set before opening and rooting.
Magisk can cause truble fot the FPS, so try uninstalling it and root it with SuperSU
Try clearing cache and dalvik cache.
Related
Hi,
I have for the first time rooted my HTC Desire. And for the first time also just installed a ROM, LeeDroid 3.0.6-R2. Everything works fine, so I think, but one thing.
I've set up my Exchange account to my work and entered a new pin code. The pin code works every time when the phone locks and I need to enter the pin to unlock it. But as soon as I go into Clockwork Recovery mode and then do nothing but restart the phone, it doesn't accept my pin code. After 8 failed attempts it wipes my phone automatically.
When it happened the first time I thought I messed up with the pin code. So I wiped the phone and started over (not reflashing the ROM), setting up Exchange with the same pin code. But it didn't accept the one I used previously. So I choose a new one, simple, 0000. Tried several times to unlock with the pin after the phone had locked. Then just now I rebooted again with Clockwork Recovery and just restarted the phone and it again won't accept my pin code.
I don't want to disable the policy and not have a pin code via some app.
Has anyone had this issue before? It's like my pin code isn't saved once I go into Recovery mode. But it still enforced the policy.
This will be the 4th time I have to wipe my phone and start over -.-
TIA
Ok, so I tried after my last wipe last night to not configure Activesync and just go into security and set a regular pin. Let the phone lock, worked. Restart phone into recovery, restart again. Doesn't work.
So I think I've managed to solve the issue. Reboot the phone completely (not into recovery) after I've set the pin code. Try to see if it works, which it did, then boot into recovery and again reboot to normal. Pin code still works. Odd....
Sigh.....nope. Still the same problem when I rebooted the phone. I still need help :'(
Someone must have some ideas?
Bumping. Halp!
Hi!
I have a very frustrating problem with the backup password on my galaxy note 4.
The fingerprint scanner is no longer accepting any of my fingerprints, but I can unlock the phone using my backup password.
However, the same backup password is not accepted for turning off the fingerprint lock, or resetting it/configuring new fingerprints.
Ive tried very carefully entering every letter/number, the password just doesnt work after the initial screen lock.
This means every time I want to use my phone I have to manually enter a 16-character password.
Any ideas?
OP reposted in the correct section:
http://forum.xda-developers.com/general/xda-assist/fingerprint-backup-password-error-t3420441
Thread closed.
Hi,
I had full disk encryption on my Moto G 3rd Gen (osprey), running stock Android 6.0, stock and locked bootloader.
Initially I had it with a PIN lock. It worked fine.
Then I removed PIN lock and I had "naked" full disk encryption, it didn't ask for any PIN on boot. Worked fine.
Now I added a PIN lock again. After rebooting my phone it is stuck with the "Decryption unsuccessful" message. The thing is it doesn't ask me for my PIN, but says "The password you entered is correct, but unfortunately your data is corrupt".
Might this be a bug with this Moto ROM that after entering a PIN it still tries to unlock with "default_password"?
Since I have a locked bootloader, do I have any way to run vdc and try do decrypt it manually with my PIN?
There is really no reason to think the decryption key is lost or corrupted, so I believe this is ROM bug triggered by adding a PIN lock.
Thanks!
Can't find a solution for this anywhere. I have an encrypted rooted moto g with unlocked bootloader and latest harp recovery. I installed an app that needed accessibility services which turned off unlock screen at bootup. I downloaded am closed app that was supposed to allow me to use accessibility services without turning off encryption at bootup but it didn't appear to do anything. I then went into security settings and re-entered unlock gesture and when asked if I wanted to be prompted for unlock at boot I said yes. Looked at accessibility settings and the permissions for the app were still turned on. I revolted the phone and now after moto logo boot screen, without asking me for a password, it goes straight to a screen saying that my password is correct but that decryption failed and to please factory reset phone. However I can boot into harp recovery and enter my unlock gesture and it works fine. So how can I turn off accessibility services for that app or otherwise fix this problem through recovery or adb? Please help.
Ok Masters, so I am having the same issue that this guy here:
https://forum.xda-developers.com/ga...mand-error-samsung-galaxy-j7-prime-s-t3929850
I can install any rom. However, the pin to register either face or fingerprint, does not work. So I cannot even get to the fingerprint screen because it returns me to enter pin, and when I re-enter it, it says is wrong. I guess it has something to do, the fingerprint so far, had just worked on Cerberus AOSP rom, but neither on one UI nor 8.1 based roms work. on 8.1 I get setting had stopped.
So, flash stock over odin was already tried and it gets stuck there. Already flashed no verity, no luck, flashed, bbos, godness, venom, no luck.
Any other advice? Seems that somehow I messed up with the encryption and that is making not registering the pin or pattern.
I managed to pass the screen with Magisk, but as soon as system boots and I try to set fingerprint, it says settings stopped. I am really frustrated now.
Thanks,
This was already solved. If anyone is interested in getting more details he they are:
The no command was because someway somehow, the system partition was "busy " or non-writteable, at least that was the message that I was able to read. I don't know how it got to that state, but my solution was the following:
- Select system partition in twrp and tapped on repair file system. I got an error immediately that twrp could not read system block. I changed file system to ext2 and rebooted twrp.
- once again I clicked on repair file system. No errors this time. Rebooted twrp. Changed file system to ext4. Rebooted twrp. Repaired file system again and rebooted twrp once again. Downloaded an aosp 8.1 rom and setted screen lock after the set up, it worked. Then, installed apollo v1. Screen got frozen for a second when setting pin, but it let me pass to set my fingerprints.
Then I knew that it was already working. Installed a One Ui rom to try and it worked again my screen lock with finger print.
Hopefully this helps someone as I found no solution whatsoever in any part of forums or internet, this was pure trial an error over 4 days.