Many of you know how to fix this issue.
I created a simple zip to do it faster. The TWRP file manager can be very useful but it's not as confortable as a file manager like MiXplorer, Amaze, Solid...
From now on, instead of going to the TWRP file manager to remove the files one by one, just flash one of these zips and reboot.
- To remove the 5 files > DOWNLOAD LINK
- As suggested, here is another flashable zip to only remove the LOCKSETTINGS files > DOWNLOAD LINK
- Final version, to only remove locksettings.db => DOWNLOAD LINK (recommended)
Here are below the list of files it removes:
Code:
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Does this only apply to PIN errors?
I recentrly restored a backup and it didn't recognize my password. I gave up and deleted everything.
carlosh2k4 said:
Does this only apply to PIN errors?
I recentrly restored a backup and it didn't recognize my password. I gave up and deleted everything.
Click to expand...
Click to collapse
The zip only removes the lockscreen protection where you have to enter your PIN/patter/password to reach your homescreen.
It doesn't apply to the boot protection while you are encrypted.
Thanks for this flashable zip,
I've got the same files on my NEXUS 6P , it should work... :good:
Lol
I made the same for another device some time ago..
https://forum.xda-developers.com/g4/development/tool-lock-screen-fix-encrypted-devices-t3499478
#
Sent from my LG-H815 using XDA Labs
I had this issue and had to clean install.
I have deleted only those locksetting files and it works fine.
TurboStrutsi said:
I have deleted only those locksetting files and it works fine.
Click to expand...
Click to collapse
Yep, I only ever delete the 3 locksetting files and it works great. Preserves fingerprints too, so only need to set up the PIN again.
New zip to only remove the LOCKSETTINGS files.
Thanks for this. Saves a lot of people from nuking their ROM ?
honestly all I've ever deleted was locksettings.db and that was enough...
dimm0k said:
honestly all I've ever deleted was locksettings.db and that was enough...
Click to expand...
Click to collapse
Fingerprint enabler xposed module also works for the times i restore and forget to erase that file in twrp.
Thanks so much. Solved my problems on my rooted HTC U11. You are awesome. Do I need to flash it everytime I leave TWRP?
Cdneyes said:
Thanks so much. Solved my problems on my rooted HTC U11. You are awesome. Do I need to flash it everytime I leave TWRP?
Click to expand...
Click to collapse
no
this is only used once - when you restore your TWRP backup and lockscreen security fails to log you in
Does my phone have to be rooted and have twrp to use this? If not, how do i flash the zip file?
kingslash said:
Does my phone have to be rooted and have twrp to use this? If not, how do i flash the zip file?
Click to expand...
Click to collapse
That's a convenient solution for a specific issue, I suggest to read the OP, if you don't have TWRP you cannot be locked out due to restoring a backup by TWRP in first place, it only applies to TWRP users in a certain usage scenario... It's flashed from recovery, root has nothing to do with this...
Sent from my OnePlus3T using XDA Labs
Is it applicable to op3?
prasant737 said:
Is it applicable to op3?
Click to expand...
Click to collapse
Of course. Many devices are compatible.
Primokorn said:
Of course. Many devices are compatible.
Click to expand...
Click to collapse
Hey!
I'm an HTC U11+ user and this doesn't work for me, im facing the same issue either i restock via OTA or TWRP backup, any thing you consider sharing that could help me?
1 thing though, i manually flashed 1.24.401.2 images, while my bootloader shows the actual version to be 1.24.401.12 .
Could this be in anyway be causing my problems?
If I do not set up any boot password/pattern etc but just a swipe on lockscreen then,
after restoring the back up and then flashing the given zips for five files immediately,
Will I be able to set up the PIN/Password/pattern on the restored ROM?
Related
READ AT THE END OF THIS POST FOR THE SOLUTION
I accidentally used Titanium Backup's widget to frost all system and user apps, leaving mi phone in a infinite boot animation loop. I dont have aNandroid Backup and I would really love to solve this issue without flashing.
I found at Titanium Backup's troubleshooting webpage that I could use this command with adb to solve my issue:
Code:
Type the following command (replace with /dbdata/system/packages.xml if you have a Samsung phone):
busybox sed -n 's/<package name="\([^"]\+\)".*enabled="false".*/\1/p' /data/system/packages.xml | while read PKG; do pm enable "$PKG"; done
but it just says: No such file or directory (yes, I changed /data to /dbdata as stated in the webpage)
Any idea on how to solve this issue?
Thank you!
**EDIT:
This is the way I managed to get my phone working again without having to flash or wipe:
1. Boot in recovery mode and used adb pull command to extract "packages.xml" and "packages-more-backup.xml" from /data/system/
2. Open both files with Wordpad and replaced all protection="2" or "3" lines to protection="1".
3. Also, and very important, replaced all enabled="false" lines to enabled="true"
4. Boot in recovery again and used adb to delete old "packages.xml" and "packages-more-backup.xml" files and push the new ones.
5. Reboot and Voila!
6. Boot once again in recovery mode and fix permissions to avoid any problem.
Hope that this could be usefull to someone else having this horrible problem.
Thank you all!
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
nitox.n2o said:
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
Click to expand...
Click to collapse
I tried with /data too but same result.
shadow65781 said:
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I know I could do that but I would really like to restore my system as it was
Help please
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Simba501 said:
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
Click to expand...
Click to collapse
Pretty sure that's not gonna work because the frozen apps settings are at packages.xml file, but I can't access it I don't know why
jhermit said:
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Click to expand...
Click to collapse
I tried doing that right now but it didn't worked
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
shokuchi said:
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
Click to expand...
Click to collapse
Wrong forum dude
Sent from my Zanpakuto using Getsuga Tensho!
<deleted>
ZIP for unfreezing apps
For those, who accidentally frozen important system app: here quick solution without factory reset, reflashing and ADB
It automatically edits files as described in first post.
You should have unlocked bootloader. If no, ZIP useless because unlocking wipes all data.
Download both ZIP's and just flash them via custom recovery (TWRP / CWM)
If first throws error try second and vice versa. 2nd with mark "New" contains newer updater-binary that must be compatible with recent TWRP.
Then all apps will be unfrozen, so phone will boot.
Fix compatible with all Android versions.
Note: also you can somehow (ADB or filemanager in TWRP) delete file /data/system/0/package-restrictions.xml
More correct to edit that file which ZIP actually do, but deleting not harmful too.
tags: unfroze apps, auto-unfroze, defrost apps, unfreeze apps, 5596
Bonoboo said:
For those, who accidentally frozen system app there is quicker solution without factory reset and ADB.
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen.
Compatible with all Android versions.
Click to expand...
Click to collapse
THANKS MAN!! i just signed up to say thanks! you just saved my life :highfive:
Bonoboo said:
For those, who accidentally frozen system app here quicker solution without factory reset and ADB
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen, so phone will boot.
Compatible with all Android versions.
tags: unfroze apps, auto-unfroze
Click to expand...
Click to collapse
Thanks very much for the zip. It worked great
Same Problem
Does anyone have an updated version of that zip? I also froze an app linked to the device and it won't boot, even after factory resetting it. Tried running the zip on my t-mobile GS4 (probably newer than that zip) from the SD card in recovery mode, however it didn't unfreeze it.
Any help greatly appreciated!
pianoplayer55 said:
Does anyone have an updated version of that zip?
I also froze an app linked to the device and it won't boot, even after factory resetting it.
Click to expand...
Click to collapse
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Bonoboo said:
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Click to expand...
Click to collapse
Yup, unfortunately I did select wipe data on the recovery screen. I am also stuck in an infinite boot up loop and cannot access the phone to install any apps. How can I use a custom recovery to run the zip file if i cannot access the phone? Instructions much appreciated. Thanks again.
pianoplayer55 said:
How can I use a custom recovery to run the zip file if i cannot access the phone?
Click to expand...
Click to collapse
ZIP – it's not app.
Again, you need to install custom recovery.
Here link to TWRP and how install it via Odin on PC.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Bonoboo said:
ZIP – it's not app.
Again, you need to install custom recovery.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Click to expand...
Click to collapse
Downloaded TWRP with Odin and ran custom recovery without a change after the zip (this must have been a deeper-rooted problem in the OS itself), however in the meantime I formatted the system partition, removing the operating system. Installed Kies and ran the update. It reinstalled the OS and I'm good now. Most stuff was backed up anyways. Thanks guys for your time :good::good:
Which apk is the culprit?
Man, I wish I'd found this thread before restoring my phones internal ROM. Had it rooted and set up in every way I like except removing bloatware.
Using TB, I froze a system apk that shut down my System UI and sent the phone bootlooping. What I'm trying to determine is WHICH apk(s) I froze that caused this. I thought I had researched each one that didn't seem obvious, but I musta missed one or one of the 'obvious' ones wasn't so obvious.
Using XtreSoLite ROM on a Galaxy S5. When I do a TWRP backup (default settings) and I target my external SD card (64GB SanDisk microSD), the backup succeeds and I can go back to the main TWRP menu and verify that the backup was created in a new folder called 'TWRP' on the SD card. However, once I boot into the system and get past the unlock screen, that TWRP folder is deleted from the SD card along with the backup.
All of the other files on the SD card are untouched, just anything to do with TWRP is removed.
Any idea what could cause this? I searched the thread for my specific ROM with no luck regarding this issue.
I have this issue as well running the stock rom. I also have the 64 gb card. Near as I can tell something about the way TWRP is writing the files to the file system (exfat) android doesnt like and corrects which removes the files. If I pull the card out of the phone before booting android I can see the files on the PC. The work around I'm currently using is to mount an external USB storage to do my backup, then copying the backup to the SD card in android.
..
Hey there guys...its happening to me as well and its annoying because you cant rely in your backups!
Any solution or just that SD take out workaround? Its kinda dangerous because you can corrupt the SD by doing this often!
What version of twrp are you using?
Sent from my SM-G900T using Tapatalk
tonyevo52 said:
What version of twrp are you using?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
I'm using the 2.8.2.0.
I noticed this happened when I updated to 2.8. I went back to 2.7.1 and its works fine again.
Yea, same problem, using 2.8.1, going to go back to 2.7.1
Sent from my SM-G900T using Tapatalk
Quickvic30 said:
I noticed this happened when I updated to 2.8. I went back to 2.7.1 and its works fine again.
Click to expand...
Click to collapse
I noticed it has started when I did format /data to F2FS back on 2810.
RazrHD, CM11 Nightly, ART, F2FS /data, Marvel boot animation
Quickvic30 said:
I noticed this happened when I updated to 2.8. I went back to 2.7.1 and its works fine again.
Click to expand...
Click to collapse
Whats the main differences between 271 ans 2810? Would you mind sharing the 271 link?
Thanks man!
RMarques said:
Whats the main differences between 271 ans 2810? Would you mind sharing the 271 link?
Thanks man!
Click to expand...
Click to collapse
I didn't notice any difference between the two. I only have the tar file you have to flash via odin, here ya go!
Quickvic30 said:
I didn't notice any difference between the two. I only have the tar file you have to flash via odin, here ya go!
Click to expand...
Click to collapse
Thanks man...dont use Odin though!
RMarques said:
Thanks man...dont use Odin though!
Click to expand...
Click to collapse
What!!!! Odin is the bestest! well you could zip it up and flash it in recovery.
Quickvic30 said:
What!!!! Odin is the bestest! well you could zip it up and flash it in recovery.
Click to expand...
Click to collapse
Ive heard but it happen that I never came across a situation where I needed it...due to that, Ive never even saw it! However, Ive heard about it and I know its such a powerful tool!
Ill take a loo at it as soon as I have some spare time! Would you mind telling me what are its main uses? Im kinda advances user-mod-wanna-be. So far, Ive just needed to use Fastboot, RSD and custom recoveries!
Cheers man!
RMarques said:
Ive heard but it happen that I never came across a situation where I needed it...due to that, Ive never even saw it! However, Ive heard about it and I know its such a powerful tool!
Ill take a loo at it as soon as I have some spare time! Would you mind telling me what are its main uses? Im kinda advances user-mod-wanna-be. So far, Ive just needed to use Fastboot, RSD and custom recoveries!
Cheers man!
Click to expand...
Click to collapse
I would say odins main use is for flashing stock tars after you get your phone stuck in brickloop after flashing something you shouldn't have :laugh:.......very useful tool I must say.
Quickvic30 said:
I would say odins main use is for flashing stock tars after you get your phone stuck in brickloop after flashing something you shouldn't have :laugh:.......very useful tool I must say.
Click to expand...
Click to collapse
Thanks man! Now I understand why I never needed it...never been into this kind of situation!
TWRP Backups being deleted at boot
Click to expand...
Click to collapse
My solution for this error:
--Device S5 mini G800F
--TWRP 2.8.1
--MicroSD 64Gb
--TotalCommander for android instaled.
Step by Step:
1. Boot in recovery mode.
2. Create and save your backup into extSDCard (TWRP/backups folder).
* Example: extSDCard\TWRP\BACKUPS\14001308b6ffd4cc\2016-01-01--01-01-01 XXXXX.YYYYYYYYYYYYY
-- 2016-01-01--01-01-01 XXXXX.YYYYYYYYYYYYY = my last backup folder name created automatically by TWRP.
-- 2016-01-01--01-01-01 = backup date and time
-- XXXXX.YYYYYYYYYYYYY = phone and rom model/version
3. Open File Manager in TWRP and copy your backup folder (2016-01-01--01-01-01 XXXXX.YYYYYYYYYYYYY) from extSDCard to internal memory.
4. Restart your phone (system restart in twrp).
5. Open TotalCommander and navigate to extSDCard/backup folder (extSDCard\TWRP\BACKUPS\14001308b6ffd4cc)
6. Create new folder and rename it with your backup name folder. *Example: extSDCard\TWRP\BACKUPS\14001308b6ffd4cc\2016-01-01--01-01-01 XXXXX.YYYYYYYYYYYYY
7. Go to internal memory (copied backup folder) and copy all files to created folder in step 6.
8. Restart in recovery mode, run file manager in TWRP and delete backup folder from internal memory.
9. Restart your phone (system restart in twrp).
10. Finish.
Hello,
After much time and effort I was able to restore my watch to stock to get the newest OTA. Here is everything for those of you who have TWRP and are rooted, so you don't have to bother restoring to stock just to re-root and replace the recovery!
https://drive.google.com/open?id=0B1My3ELWb01vM29HbTZvQ3ZaTU0
Thanks to other users and posts who helped point me in the right direction to get this. Pulling the stock recovery was the hardest part for a n00b like me!!
slothdabski said:
Hello,
After much time and effort I was able to restore my watch to stock to get the newest OTA. Here is everything for those of you who have TWRP and are rooted, so you don't have to bother restoring to stock just to re-root and replace the recovery!
https://drive.google.com/open?id=0B1My3ELWb01vM29HbTZvQ3ZaTU0
Thanks to other users and posts who helped point me in the right direction to get this. Pulling the stock recovery was the hardest part for a n00b like me!!
Click to expand...
Click to collapse
Thanks :good:
did you read this post to pull the stock recovery?
Yeah but I wasn't knowledgeable enough to figure it out from that post, I had to Google for a most basic step by step lol. But that post got me started!
Sent from my Nexus 6 using Tapatalk
is this for big zenwatch 2?
Yes :good:
Sent from my ASUS_T00F using XDA-Developers mobile app
Nice post :laugh:
r0tati0n said:
is this for big zenwatch 2?
Click to expand...
Click to collapse
Yes, big zenwatch 2 with speaker
Sent from my Nexus 6 using Tapatalk
Can you please help me with the installation process?
instantdetox said:
Can you please help me with the installation process?
Click to expand...
Click to collapse
Do you have twrp on your watch or know how to sideload it?
Sent from my Nexus 6 using Tapatalk
slothdabski said:
Do you have twrp on your watch or know how to sideload it?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I want to know how to sideload it.
This thread is for people with twrp who can't take the OTA.
Sent from my Nexus 6 using Tapatalk
instantdetox said:
I want to know how to sideload it.
Click to expand...
Click to collapse
Find the OTA link in another thread and download it. The using adb issue the command:
adb sideload (location of OTA zip)
While in the stock recovery
Sent from my Nexus 6 using Tapatalk
slothdabski said:
Do you have twrp on your watch or know how to sideload it?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I also don't know how to update the system using your images. I know how to sideload and I also have twrp working. Never flashed an img to a wearable so if you don't mind explain how to would be great.
metuskale said:
I also don't know how to update the system using your images. I know how to sideload and I also have twrp working. Never flashed an img to a wearable so if you don't mind explain how to would be great.
Click to expand...
Click to collapse
You flash the stock recovery using fastboot.
Fastboot flash recovery /location/of/stock_recovery.img
This isn't necessary unless you want stock recovery flashed or to be able to take future official OTAs directly from Google/asus
The system and boot are in twrpon backup format. Make a small backup on your watch of the cache partition, just so the twrp backuo folder gets created (which is unique to your device). Then adb push the folder you downloaded from this thread (with the build number and date I backed it up, not the parent folder that contains the stock recovery) to /sdcard/TWRP/<your_serial_number>/
Then, on your watch, use to to restore the system and boot. Wipe the cache on your watch and restart. You will not be updated without have to factory reset/wiping data partition.
If you try to flash stock recovery and get error BC your bootloader is locked. You will have to wipe data partition when you unlock bootloader by issuing command
fastboot oem unlock
Please let me know if you have any other questions
Sent from my Nexus 6 using Tapatalk
metuskale said:
I also don't know how to update the system using your images. I know how to sideload and I also have twrp working. Never flashed an img to a wearable so if you don't mind explain how to would be great.
Click to expand...
Click to collapse
Download the files, place them in the TWRP/Backups/(RandomHASH) directory using the directory name he has in his Drive folder, remount System RW (that one threw me off for a few), then run a TWRP restore. You don't have to sideload anything, since TWRP will let you see the watch as a drive (at least under WIN7, haven't tried anything else).
---------- Post added at 07:23 AM ---------- Previous post was at 07:06 AM ----------
I'm glad you were able to pull this.
I woke up this morning to find my watch sitting in TWRP because it had tried to update. I just flashed this, and so far, so good.
Fair warning to everyone: TWRP will restore the boot in the recovery, even if you tell it not to(TWRP bug?)! If you use a different kernel just reflash it after you restore this backup.
do i just put everything on a folder named 2016-06-22--20-06-49_mwd59 and then just flash via twrp?
Jairsantana said:
do i just put everything on a folder named 2016-06-22--20-06-49_mwd59 and then just flash via twrp?
Click to expand...
Click to collapse
You have to make a twrp backup just so a backup folder with your unique hash has been created (just backup cache partition to do this). Then push the 2016-06-22--20-06-49_mwd59 folder into /sdcard/TWRP//
(You'll see a similarly named folder in that directory from the backup you did yourself)
Then use the restore function of twrp to restore the system and boot from the backup folder you got from this thread.
Then wipe your cache partition and you should be good to go!
Sent from my Nexus 6 using Tapatalk
I can confirm that this steps are working:
Backup anything from TWRP (just to create the folder).
Inside the newly created folder (sdcard/TWRP/BACKUP/XXXXXXXXXXXXX --> XXXXXXX folder is one created by TWRP ) place the folder from Drive (the folder itself, no need to change the name).
Then from TWRP perform a Restore and select the one with the name from Drive.
Also note that I lose root, and dunno how to recover it. With this update UI is way faster and connects to BT and WIFI better too.
metuskale said:
I can confirm that this steps are working:
Backup anything from TWRP (just to create the folder).
Inside the newly created folder (sdcard/TWRP/BACKUP/XXXXXXXXXXXXX --> XXXXXXX folder is one created by TWRP ) place the folder from Drive (the folder itself, no need to change the name).
Then from TWRP perform a Restore and select the one with the name from Drive.
Also note that I lose root, and dunno how to recover it. With this update UI is way faster and connects to BT and WIFI better too.
Click to expand...
Click to collapse
You'll have to reflash SuperSU wear BC its overwritten when your restore the boot partition. Busybox will also have to be reinstalled if you need it BC that is overwritten when you restore the system partition
Sent from my Nexus 6 using Tapatalk
I forgot to restore boot, now my battery life is being sucked dry! I'm guessing it's stock recovery, though, even though I unticked that option. Someone in here said it was a bug in TWRP. So I guess I could just fastboot flash twrp, then push the zip and flash it?
Sent from Toastmade 6P using TAPATAPA
I have a silly problem, I had freshly installed the unofficial CM14.x and between all the new settings forgot the Lockscreen pattern. Since i didn't want to try factory reset and other solutions without data loss didn't wird, I searched a bit and erasted the /data/system/gatekeeper.pattern.key via ADB ! It actually helped passing through lockscreen, but now I can't set any new lock (none of the options tough) / I can't go to the option… I get dropped out with an error…
What can I do??
roshak said:
What can I do??
Click to expand...
Click to collapse
Open thread in right section.
CheckYourScreen said:
Open thread in right section.
Click to expand...
Click to collapse
Well, I guessed that users in the Q&A/Troubleshoot section wouldn't have much clue about manipulating Android's /data/system/. . . files and apparently I was true! No reply since 3-4 days
roshak said:
Well, I guessed that users in the Q&A/Troubleshoot section wouldn't have much clue about manipulating Android's /data/system/. . . files and apparently I was true! No reply since 3-4 days
Click to expand...
Click to collapse
Chill.
You able to access your files and data?
Just open settings and change the screen lock to "none" or "swipe", then select pin/password and set your own.
It should fix it.
If it doesnt then make a backup of your data and clean flash stock rom by wiping system,cache and data (not internal sd).
CheckYourScreen said:
Chill.
You able to access your files and data?
Just open settings and change the screen lock to "none" or "swipe", then select pin/password and set your own.
It should fix it.
If it doesnt then make a backup of your data and clean flash stock rom by wiping system,cache and data (not internal sd).
Click to expand...
Click to collapse
Says right in the in original post that he can't set any new lock with any of the options, it just crashes. I think he's got not choice but a re-flash.
As @Tanner1294 noticed. I can't change the locksreen options anymore and that's the problem (I can't use the device without lock! But I wouldn't)
backing up data may work or maybe not, because the missing files could be under data… But I'll give it a try.
I don't know why I couldn't replace the screen password via Google Device Manager… The device was recognised and the pass and message has been sent to it, but i couldn't interact with it at all! only "emergency call" was touchable If it's an issue in Android 7.x or CM14.x dunnow
Maybe dirty flashing the ROM again will help
mcmarius said:
Maybe dirty flashing the ROM again will help
Click to expand...
Click to collapse
didn't work!
roshak said:
As @Tanner1294 noticed. I can't change the locksreen options anymore and that's the problem (I can't use the device without lock! But I wouldn't)
backing up data may work or maybe not, because the missing files could be under data… But I'll give it a try.
I don't know why I couldn't replace the screen password via Google Device Manager… The device was recognised and the pass and message has been sent to it, but i couldn't interact with it at all! only "emergency call" was touchable If it's an issue in Android 7.x or CM14.x dunnow
Click to expand...
Click to collapse
Make a backup of contacts,sms, apps(or just download from playstore) or use titanium backup if you want app data also.
And clean flash rom.
Forget everything and clean flash after making backup.
That file is related to system and has to be present in /data/system/ so will remain excluded from backups you make.
Make sure you clean flash rom.
CheckYourScreen said:
Make a backup of contacts,sms, apps(or just download from playstore) or use titanium backup if you want app data also.
And clean flash rom. . .
Click to expand...
Click to collapse
If I only knew how I can re-install my selection of apps straightforward, I wouldn't hesitate about clean flash; I don't worry about my files, contacts etc.
I'll try to figure out, how Titanium Backup works… Thanks for advice
The problem is now solved without reflashing etc.
I just had to know which other files need to be removed in addition to /data/system/gatekeeper.pattern.key
they were locksettings.db locksettings.db-wal locksettings.db-shm from the same directory!
So i removed them, whatever they may contain
then rebooted to system and everything was on the rail, i could pick a lockscreen method again.
PS: I haven't imagined that havong debugging mode enabled could make an Android system so unsecure though!
roshak said:
If I only knew how I can re-install my selection of apps straightforward, I wouldn't hesitate about clean flash; I don't worry about my files, contacts etc.
I'll try to figure out, how Titanium Backup works… Thanks for advice
Click to expand...
Click to collapse
Titanium backup is godly makes transitioning between ROMs a breeze like you never left your setup. In TB app top right corner is a blank page with check mark on it. In there you can backup/restore large chunks of apps and data. After a fresh install rooted first thing install is TB and got to that section restore and choose what you want from backup. System apps can be backup also but will find some won't work on other ROMs. Regular apps will have no such issues. There is also TB sms backup. To use that you must set TB as default sms app. Restore sms then revert back to regular sms app and open. There all your messages will be restored.
roshak said:
The problem is now solved without reflashing etc.
I just had to know which other files need to be removed in addition to /data/system/gatekeeper.pattern.key
they were locksettings.db locksettings.db-wal locksettings.db-shm from the same directory!
So i removed them, whatever they may contain
then rebooted to system and everything was on the rail, i could pick a lockscreen method again.
PS: I haven't imagined that havong debugging mode enabled could make an Android system so unsecure though!
Click to expand...
Click to collapse
You shouldn't delete " /data/system/gatekeeper.pattern.key" as "locksettings.db locksettings.db-wal locksettings.db-shm" contain your lock screen pattern. So to remove pattern just delete these files. Android device manager won't work if it reads that your device has already a pattern/PIN enabled. I guess it worked a while ago on password protected devices as well but not anymore.
EDIT: Sry for the trouble, i just reinstalled it again. this time using Format Data in TWRP and it worked.
so i have the snapdragon xiaomi Redmi note 3, and i did the offical bootlocker.
after that worked, i installed twrp using this guide https://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
so far so good.
i chose this ROM https://forum.xda-developers.com/redmi-note-3/development/rom-aospextended-rom-v1-2-t3506955
and installed it using the GApps(ARM64) for 7.1 ofcourse.
but when i reboot my phone it says To start Android, enter your password.
i read about it online and it says either it was your password(my phone wasnt locked, only swipe to unlock) OR use your Google account to open, but i didn't have Google accounts logged in the device(it is brand new, only MI account but that password didn't work).
So i tried to perform factory reset using TWRP (Wipe->Data), that didn't work.
SO i re-installed the new ROM+GApps thinking it will fix it, still same error.
anyone got a solution?
PIC:
http://imgur.com/a/tiKnJ
ty for everyone that helps
555satan said:
anyone got a solution?
Click to expand...
Click to collapse
Boot into TWRP. Mount /system, then go to filemanager and delete the following files inside /data/system (just delete the ones that are there, I think all 5):
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Then reboot, it should work, let me know (or thank me if it works)
I can really help you.
Now you conform me that your device is working or not
Boot into Twrp and under Wipe you`ll find FORMAT DATA, not wipe data.. Format the data and the rom will boot . Note that you`ll lose everything from you phone, so it`s good to save files on pc before, if you have something important..
Robin>Hood said:
Boot into TWRP. Mount /system, then go to filemanager and delete the following files inside /data/system (just delete the ones that are there, I think all 5):
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Then reboot, it should work, let me know (or thank me if it works)
Click to expand...
Click to collapse
Sadly it doesn't work :crying:
Did you have password/pin protection enabled? I had a similar issue, and I entered TWRP, and used the in-app file explorer. I went to the data/system folder and deleted all the *.key files. Then I rebooted my phone and everything was there! Hope it helps you!
PS: I was having a hard time, after having formatted my system, in order to install AOSP 8.0.0, and trying to restore my MIUI backup ....
Guys, sorry to hijack the post, but can this be solved by using LazyFlasher? Hope someone can help. Thanks.
Op_Flashpoint said:
Guys, sorry to hijack the post, but can this be solved by using LazyFlasher? Hope someone can help. Thanks.
Click to expand...
Click to collapse
didn't help
Yes Formatting Data under wipe section works
Robin>Hood said:
Boot into TWRP. Mount /system, then go to filemanager and delete the following files inside /data/system (just delete the ones that are there, I think all 5):
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Then reboot, it should work, let me know (or thank me if it works)
Click to expand...
Click to collapse
Is it inside of any other folder or in system
cristiandiaconu6 said:
Boot into Twrp and under Wipe you`ll find FORMAT DATA, not wipe data.. Format the data and the rom will boot . Note that you`ll lose everything from you phone, so it`s good to save files on pc before, if you have something important..
Click to expand...
Click to collapse
thanks, it was work on my vince when i tried install AOSP Ext
Hitagi End said:
thanks, it was work on my vince when i tried install AOSP Ext
Click to expand...
Click to collapse
did you format data after installing the rom or before that?
mona356 said:
did you format data after installing the rom or before that?
Click to expand...
Click to collapse
after installing AEX, if your TWRP said No OS installed just flash the rom again and the rest will be fine
Hitagi End said:
after installing AEX, if your TWRP said No OS installed just flash the rom again and the rest will be fine
Click to expand...
Click to collapse
are you using pie or Oreo?
mona356 said:
are you using pie or Oreo?
Click to expand...
Click to collapse
Pie
cristiandiaconu6 said:
boot into twrp and under wipe you`ll find format data, not wipe data.. Format the data and the rom will boot . Note that you`ll lose everything from you phone, so it`s good to save files on pc before, if you have something important..
Click to expand...
Click to collapse
thanks dude!!!!!!!!!! It worked!!!!!!!!!!!!!!!!!!!!!11 :d:d:d
i cannot find always on display ? is it not available on pixel rom s8+?