Can't set Lock Screen Password and Fingerprint - Xiaomi Poco F1 Questions & Answers

Hi,
I have a Pocophone F1 that recently upgraded to MIUI 12 (Global stock ROM). The password and fingerprint functioned normally until removing the password. Now when I try to set a password (pattern, PIN or password) a fingerprint is requested, the sensor doesn't recognize my finger and gets stuck on this screen.
I have already cleared all data from the applications below and restarted the device:
- POCO Laucher
- FingerprintExtensionService
- Fingerprint test
I also tried to create a Second Space, but the password is requested and I can't move forward.
In the Fingerprint input test option, the finger is not recognized. The sensor works normally, it vibrates (except on the screen to set the fingerprint) and I can take pictures with the sensor. I don't believe it's hardware because the problem started at the moment when I removed the password and fingerprint.
Any ideas what I can do to resolve without restoring the device?

Bro, Don't worry about your hardware.
It's a software bug and many MIUI 12 users are facing it.
I faced issue in setting up fingerprint in MIUI 12 too.
So I downgraded to MIUI 9 and it works like a charm.
You have two ways, either wait for next update to fix the issue or downgrade to lower MIUI version.

To set password etc boot in twrp and select advance, then file manager, in file manager select data, in data select system and in system delete lock setting files (3 files or may be one only).
Reboot and set your password.

Related

[Q] Android 4.4.2 S5 Mini: Where is file with Fingerprint data

In which file is the fingerprint data stored on 4.4.2 on S5 Mini 800F?
In case one forgets the password or pattern on Android, the phone can be unlocked by deleting the password/gesture file in data/system.
After reboot one can access the phone with any password or pattern and set a new one.
Several methods are described here at XDA and YouTube.
Samsung came up with the S5 Mini that has the fingerprint scanner.
Fingerpritn scanner does not recognise anymore, no alternative password to use, no google related account.
In order to get access back I assume I need to delete the file that stores the fingerprint data - just like the approach as described with the password and pattern.
Is it correct to assume that after deletion of the file containing the fingerprint data and after a reboot ANY fingerprint swipe will give access to the phone and that a one can set again the fingerprint security?
Many thanks to your help in this matter which will also interst others as more and more fingerprint accessed devices are expected to hit the market.

[FIX] Can't Unlock your Phone after full restore from TWRP.!!!!

HAD A FULL BACKUP OF YOUR CURRENT ROM!?
BRICKED YOUR PHONE AND TRIED TO RESTORE.?
SOMEHOW WENT TO RECOVERY AND RESTORED EVERYTHING.!?
HOPED EVERYTHING TO BE FINE BUT BOOM. WHATthe**** CANT UNLOCK YOUR PHONE. SAYS WRONG PIN EVERY TIME. CANT USE FINGERPRINT ALSO. HARD LUCK.!?
Generally this problems occurs because you had done your backup after setting up the pin or fingerprint or pattern.
TWRP otherwise restores everything superfine with every app and data and settings restored but sometimes when rebooted users can't unlock there phone with pin or pattern and can't even use their fingerprints. Common bug of restoring pattern of TWRP.
THOUGH its recommended that do your backup whithout any screen lock. And while restoring uncheck 'cache' and recovery.
BUT THERE'S A 100% WORKING FIX FOR THIS ::
1. TRY 3 TO 4 TIMES THE PIN AND FINGERPRINT. IF DOESNT UNLOCKS REBOOT ONCE AND THEN TRY.
2. IF THAT FAILS. 'POWER OFF' YOUR PHONE.
BOOT TO TWRP RECOVERY. (Pressing power button and volume up button at once)
3. IF PROMPTED ALLOW MODIFICATIONS.
DONT DO ANYTHING. GO STRAIGHT TO ADVANCED.
4. NOW HEAD TO FILE MANAGER.
(normally opened in the main folder '/', if not select storage internal). HEAD TO '/data/system' folder. Scroll down.
5. FIND FILES WITH .key EXTENSIONS AND CLICK ON THEN (generally two files). AND 'DELETE' THEM.
6. NOW FIND AND DELETE ALL FILES WITH KEYWORD 'locksettings'
AFTER DELETING. JUST REBOOT TO SYSTEM.
NOW YOU COULD BE ABLE TO UNLOCK YOUR PHONE WITHOUT any PIN or PATTERN or FINGERPRINT.
just SWIPE UP. Phone got restored to original state.
NOW SET UP FINGERPRINT AND NEW PIN IN THE SETTINGS.
* for me while setting up new pin and FINGERPRINT. The settings apps stopped closed suddenly. I opened it again and i found fingerprint and lock already set up.
Locked the screen and unlocked with my old pin and fingerprint.
DO GIVE A THUMBS UP IF YOU FOUND THE POST HELPFUL...!!!!!!!
Thanks
Or flash AgniToolbox from Recovery and select the option to reset the lock.
or, flash mandatory firmware depends on rom you've restored (cm13 or cm14 firmware)
this tricks worked for me, whenever im restoring my full backup of RR MM and then i flash CM 13 firmware
locksettings.db is the only file you need to delete.
This happens to me with every backup, even i set up the pin a long time before backup.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Thanks brother , you saved my day (Y)
[email protected] said:
HAD A FULL BACKUP OF YOUR CURRENT ROM!?
BRICKED YOUR PHONE AND TRIED TO RESTORE.?
SOMEHOW WENT TO RECOVERY AND RESTORED EVERYTHING.!?
HOPED EVERYTHING TO BE FINE BUT BOOM. WHATthe**** CANT UNLOCK YOUR PHONE. SAYS WRONG PIN EVERY TIME. CANT USE FINGERPRINT ALSO. HARD LUCK.!?
Generally this problems occurs because you had done your backup after setting up the pin or fingerprint or pattern.
TWRP otherwise restores everything superfine with every app and data and settings restored but sometimes when rebooted users can't unlock there phone with pin or pattern and can't even use their fingerprints. Common bug of restoring pattern of TWRP.
THOUGH its recommended that do your backup whithout any screen lock. And while restoring uncheck 'cache' and recovery.
BUT THERE'S A 100% WORKING FIX FOR THIS ::
1. TRY 3 TO 4 TIMES THE PIN AND FINGERPRINT. IF DOESNT UNLOCKS REBOOT ONCE AND THEN TRY.
2. IF THAT FAILS. 'POWER OFF' YOUR PHONE.
BOOT TO TWRP RECOVERY. (Pressing power button and volume up button at once)
3. IF PROMPTED ALLOW MODIFICATIONS.
DONT DO ANYTHING. GO STRAIGHT TO ADVANCED.
4. NOW HEAD TO FILE MANAGER.
(normally opened in the main folder '/', if not select storage internal). HEAD TO '/data/system' folder. Scroll down.
5. FIND FILES WITH .key EXTENSIONS AND CLICK ON THEN (generally two files). AND 'DELETE' THEM.
6. NOW FIND AND DELETE ALL FILES WITH KEYWORD 'locksettings'
AFTER DELETING. JUST REBOOT TO SYSTEM.
NOW YOU COULD BE ABLE TO UNLOCK YOUR PHONE WITHOUT any PIN or PATTERN or FINGERPRINT.
just SWIPE UP. Phone got restored to original state.
NOW SET UP FINGERPRINT AND NEW PIN IN THE SETTINGS.
* for me while setting up new pin and FINGERPRINT. The settings apps stopped closed suddenly. I opened it again and i found fingerprint and lock already set up.
Locked the screen and unlocked with my old pin and fingerprint.
DO GIVE A THUMBS UP IF YOU FOUND THE POST HELPFUL...!!!!!!!
Click to expand...
Click to collapse
Saved me from installing freshly again
I was using latest aosip...then i decided to change to Nitrogen os...
I wiped everything needed and then flashed Nitrogen os...
I was using a pattern lock in the aosip and when the Nitrogen os starts..it asks for pattern..but the previous pattern doesn't work...
when i again flash the aosip the same pattern works..but it doesn't work in nitrogen os
I tried to delete the keys from data/system but there are no keys there(in nitrogen os)
what shall i do? help guys....i can only use
ME TOO
biratlama said:
I was using latest aosip...then i decided to change to Nitrogen os...
I wiped everything needed and then flashed Nitrogen os...
I was using a pattern lock in the aosip and when the Nitrogen os starts..it asks for pattern..but the previous pattern doesn't work...
when i again flash the aosip the same pattern works..but it doesn't work in nitrogen os
I tried to delete the keys from data/system but there are no keys there(in nitrogen os)
what shall i do? help guys....i can only use
Click to expand...
Click to collapse
I myself also have this problem kindly tell a fix guys
thank dude...... worked like a charm..... u saved some grey hairs...bless
Thanks thanks thanks a lot my friend, you saved me from losing every precious data from my locked phone. Thanks once again
only delete locksettings.db worked for me
no need to delete other files
I erased *.key and locksettings... but now I enter but can't insert new finger or pin.
I restored with TWRP /system and /data (no error), cleared devlick/art and cache, reboot and now I can't enter in "Security settings". What can I do?
simona70 said:
I restored with TWRP /system and /data (no error), cleared devlick/art and cache, reboot and now I can't enter in "Security settings". What can I do?
Click to expand...
Click to collapse
Flash the same ROM without wiping anything.
If you had.
Noor9933 said:
Flash the same ROM without wiping anything.
If you had.
Click to expand...
Click to collapse
Yes... I have not thinked the more obvious thing!!!! Thanks!!!!! Install exact rom (I have) and reinstall xposed and supersu and all shoud be lilke before.
---------- Post added at 05:37 PM ---------- Previous post was at 04:42 PM ----------
MMM all ok but... /modem damaded (no sim read)... anymore twrp and /modem restore solved this second derivated problem.
None... again I can't enter in security settings
biratlama said:
I was using latest aosip...then i decided to change to Nitrogen os...
I wiped everything needed and then flashed Nitrogen os...
I was using a pattern lock in the aosip and when the Nitrogen os starts..it asks for pattern..but the previous pattern doesn't work...
when i again flash the aosip the same pattern works..but it doesn't work in nitrogen os
I tried to delete the keys from data/system but there are no keys there(in nitrogen os)
what shall i do? help guys....i can only use
Click to expand...
Click to collapse
@sarabeshsab i think your phone is encrypted (MIUI encrypt by defaul /DATA and /internalSD) . NitrogenOS not support encryption (maybe in lasted build yes), you need to format data button on TWRP, this erase all DATA and Internal SD and disable partition encryption, (make backup to PC first, pictures and docs, etc). Now you be able to install NOS 8.
thank you works 10000000000000%
I followed this guide 'cause when I've restored a twrp backup my fingerprints didn't work (PIN did).
Removed them, added again, but not working.
Following this guide, deleting all these files didn't work.
Removing instead locksettings.db only*worked!

Encrypted Android no longer asks for desencryption password...

Hi everyone,
A month ago, I encrypted my phone (Galaxy S5 Plus - kccat6) currently under LineageOS 15.1 (Android 8.1.0) and TWRP 3.2.3-0.
Normally, after the encryption, when I started my phone, I would get a password request to decrypt my phone before launching Android. Access to TWRP was also password protected.
However, for a week now, for no apparent reason, I no longer have any password requests at startup and TWRP no longer asks for a password either.
In the "Security and Confidentiality" section, under "Encryption and identifiers", the phone is always indicated as encrypted... so it's impossible to request the encryption of my data again. At the same time, when I use Trust (integrated with LineageOS), it says "Encryption : Disabled".
I don't understand it. I did nothing in particular to have the encryption deleted.
Do you have any idea what to do to recover the encryption on my phone? And eventually why I may have lost the encryption?
Thank you in advance
OK I found a solution. It seems that it's a bug well known since many versions of Android. Strange that it has not been corrected...
Here's what helped me to fix the problem (found here : https://issuetracker.google.com/issues/37010136 )
How to reproduce:
1. Go to Settings -> Accessibility -> Switch Access
2. Enable Switch Access service
3. Go to Security -> Screen lock
4. Incorrect warning text appears under Pattern, PIN, and Password options
How to fix
1. Go to Security -> Screen lock
2. Select one of Pattern, PIN, and Password options
3. Select "Require pattern to start device" on the next UI
4. Finish setup
5. Go to Settings -> Accessibility -> Switch Access
6. Enable Switch Access service
7. Incorrect text ("If you turn on Switch Access, your device won't use your screen lock to enhance data encryption") on the prompt. It's incorrect and misleading because "Require pattern to start device" is already set and screen lock will apear on start up.
Click to expand...
Click to collapse

Removing device password on mido

Hi,
After accidentally setting up password on startup (Settings -> Security -> ScreenLock -> Password -> Require password on startup), I can't for the love of Pete remove it. I restarted number of times, set screenlock to none, set different password, set PIN and the confirming 'No Thanks'. The device password never gets replaced by anything I set up there.
The phone is encrypted by default. TWRP is installed, the system is otherwise fully accessible.
Running RR 5.8.5 on Nougat 7.1.2
Anyone have an idea how to remove this password?

Restore cloud backup asks for a 3x3 pattern, but is encrypted with 6x6

Hi all,
I have a Poco F1 with the latest LineageOS rom found elsewhere on XDA. I had to do a factory reset because of some weird problem, assuming that my backup to Google Drive could be restored during the setup wizard.
The backup turns out to be encrypted with my lock screen pattern, a policy introduced last year. Unfortunately, I was using a 6x6 unlock pattern, but the setup wizard only allows me to enter a 3x3 pattern. Unlike other pattern screens, there is no 3x3/4x4/5x5/6x6 selector on the bottom of the screen. In other words: I cannot unlock mt backup.
Things I tried:
- Skip the restore process in the setup wizard, go to the system settings first to configure the exact same 6x6 lock pattern, and then return to the restore process. This did not help.
- Running adb shell bmgr restore also failed:
Code:
$ adb shell bmgr restore TOKEN
Scheduling restore: POCO F1
restoreStarting: 82 packages
restoreFinished: -1000
done
(I know, it says "done", but nothing changed and this happened much faster than I would expect a restore process to be.)
What can try next? All help is appreciated.
i think we are out of luck
pretty much the same thing happened to me with 4x4 pattern yesterday.
in my opinion this is a big no-no for the pattern size feature in the lineageos and there should be warning about all of this in big bold letters when you are changing pattern size
if there is anyone with an idea how to fix it, please share but for now i think the only theoretical chance of ever retrieving the data is for google to add "forgot my pattern" functionality into the backup restore procedure.
also, i found out that the pattern i set up originally still unlocks the phone during boot when it restarts.
once the system runs i have now just plain 3x3 pattern but somehow the old one is stored somewhere even though i did full wipe of the phone in twrp
Agree.
zivel said:
in my opinion this is a big no-no for the pattern size feature in the lineageos and there should be warning about all of this in big bold letters when you are changing pattern size
Click to expand...
Click to collapse
Exactly, I completely agree. The grid size feature was probably added to LineageOS before backups started to be encrypted with the pattern, but still I am surprised that this feature is still present in the code base while it cripples the backup restore process. A big fat warning is the bare minimum I would expect.
There isn't much information about this problem on the web, so I gave up on the thought of restoring my backup and built up my phone from scratch. Needless to say, I am using a 3x3 pattern now... Fortunately contacts and calendar have their own storage so the most important data (for me) is still safe.
Issue
I created an issue in the LineageOS issue tracker: https://gitlab.com/LineageOS/issues/android/issues/937.
same :crying::crying::crying::crying: the situation here, there isn't even an option to postpone the restore, all things gone....
This makes me cry. No warning anywhere. All that stuff gone now. Thought I was being a good boy by making a backup. Nope, screwed anyway. So many hours lost.

Categories

Resources