I'm trying to setup a new unlock pattern but the phone still uses the old one for twrp and system startup. My old unlock pattern was a 4x4 grid, but i'm trying to install Xiaomi.eu which uses a 3x3 grid in the installation. I'm currently using LineageOS.
luceris said:
I'm trying to setup a new unlock pattern but the phone still uses the old one for twrp and system startup. My old unlock pattern was a 4x4 grid, but i'm trying to install Xiaomi.eu which uses a 3x3 grid in the installation. I'm currently using LineageOS.
Click to expand...
Click to collapse
Delete all the lock files (there will be three or four) and then reboot and set your unlock pin/pattern afresh. Search XDA for the names of the lock files.
Related
Hi Everyone!
I am running latest version of Resurrection Remix (7.1.2) on my HTC One M8 and somehow, the Pattern unlock Sequence i have set during Boot (using it since Months!) has changed to a Password entry Box without any reasons.
I have never set any Password or PIN for the Device, so i have been locked out.
Just to make sure, i have also tried any PIN and Password that i could remember.
Disc Encryption is active , but i can access System and SD Partitions in TWRP without entering a Pattern/PIN.
I have read some Guides wich describe how to delete pass and pattern key-files to bypass the Boot Security, but without success yet. Any Ideas, what might have changed the Pattern Protection and how to revert it?
Thanks in advance!
br
Qudo
qudo said:
Hi Everyone!
I am running latest version of Resurrection Remix (7.1.2) on my HTC One M8 and somehow, the Pattern unlock Sequence i have set during Boot (using it since Months!) has changed to a Password entry Box without any reasons.
I have never set any Password or PIN for the Device, so i have been locked out.
Just to make sure, i have also tried any PIN and Password that i could remember.
Disc Encryption is active , but i can access System and SD Partitions in TWRP without entering a Pattern/PIN.
I have read some Guides wich describe how to delete pass and pattern key-files to bypass the Boot Security, but without success yet. Any Ideas, what might have changed the Pattern Protection and how to revert it?
Thanks in advance!
br
Qudo
Click to expand...
Click to collapse
Deleting a Few Files In /Data Will Unlock Deactivate any Password.Try Finding the Locksettings.db in /Data/system or Somewhere.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
Deleting a Few Files In /Data Will Unlock Deactivate any Password.Try Finding the Locksettings.db in /Data/system or Somewhere.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Atifbaig786,
already did this.
files i have removed:
password.key
pattern.key
locksettings-db-shm
locksettings-db.wal
locksettings.db
no effect. still requests a password.
qudo said:
Atifbaig786,
already did this.
files i have removed:
password.key
pattern.key
locksettings-db-shm
locksettings-db.wal
locksettings.db
no effect. still requests a password.
Click to expand...
Click to collapse
I can't say For Sure But.There are more Files Than That In Version Above MarshMellow.Those Guides were for Android 4.4.4 and low.
Or Someone Just Took your Gmail Account and Locked It.
It's The Most Possible Reason For Auto-Locking Devices That Someone Accessed your Device and Did Some Bad S,H,I,T to you.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
I can't say For Sure But.There are more Files Than That In Version Above MarshMellow.Those Guides were for Android 4.4.4 and low.
Or Someone Just Took your Gmail Account and Locked It.
It's The Most Possible Reason For Auto-Locking Devices That Someone Accessed your Device and Did Some Bad S,H,I,T to you.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Google Account is safe and definitely not hacked.
Secured by 2-step-authentication and i still have access to it. there is also nothing wrong in phone management there. already checked this.
And to get this straight, the device is not auto locked as you may from device management in your google account.
Disc has been encrypted and a pattern has been set for decryption. this pattern has changed to Password entry.
same password entry that you have when encrypting with a password.
i had this behaviour before on some older cm versions on my samsung i9305...
i have started creating a current backup and will restart everything from scratch.
seems more like an error in android, than <<s,h,i,t>>
all hail to titanium backup!
thanks anyways.
Qudo
OK, this bug is reproducable.
i have tested it twice.
- clean install from scratch
- disc encryption
- creating a nandroid backup
- reboot afterwards
-> pattern set before is not available, but a password prompt asking for a password that i had never set.
System details:
Phone 1:
HTC One M8
resurrection remix ROM 5.8.5
TWRP Recovery Version 3.1.1-0
Phone 2:
Google Nexus 5
resurrection remix ROM 5.8.5
TWRP Recovery Version 3.1.1-0
Anyone else? :/
EDIT:
This does ot happen, if i don't create a nandroid backup. seems linked somehow ...
Hello,
just today I updated to the new MIUI Version.
After reboot the device asked me for the lockscreen PIN.
Due to that I justed use the facetime unlock I forgot the PIN.
Is there any possibility to avoit the PIN Code of the lock screen ?
The way with the google account is not working with the pocophone ;-(
Please help.
Best
Eggi
Use twrp
Go in file manager then data then system then delete file locksetting.db
It will remove lock
Hey,
I just had to reset my phone, and now the google recovery wizard wants my lock pattern I had on the old install. It presents a 3x3 grid to enter it. My Pattern had 4x4 dots. How can I recover my Settings and SMS now?
Thanks
Werdck
I also want to know...
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.
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.