I just replaced my phone after I cracked the screen I was stock rooted and had done a nandroid backup prior to running Odin to get the broken phone back to stock. I had a hard time getting safestrap installed and working on the new phone. Finally after several attempts, I got it up and running but there were no backupslisted under recovery. I checked in ES file explorer and they were still on the SD card where they were supposed to be in the TWRP directory. I figured that was possibly a folder issue so I tried creating a nandroid backup of the new phone and it made a new folder in the TWRP/Backups directory. So I copied my newest nandroid I created from the old phone into the new directory. It worked. It came up when I went to recovery in safestrap. I did the recovery of it and when the phone started up, it came to the lockscreen I have always used so I tried entering my pin. I got an "incorrect pin" message. I absolutely know that I used the right pin. I tried every pin I could think of that I though might work and nothing would unlock the phone. After doing some research, I found that if I get back into safestrap, I could use the file manager to get into /data/system and either delete or rename the gesture.key file along with all 3 of the the locksettings files. Once I restarted the phone, I only had to swipe to get it open. At least I was in. I then went back into settings and then into lockscreen, selected screen lock and clicked on PIN. A full keyboard came up which had never happened on the old phone. I again set the PIN that I have always used and restarted the phone. The lock screen came up after rebooting and again, my PIN did not work. I had to go back into safestrap's file manager and those 4 files had been recreated. I renamed them again and was able to get back into the phone.
I don't like not being able to lock the phone. Does anyone have any suggestions on how to fix this?
Somehow I was able to fix this. i don't quite remember all the steps but I got it done. I had originally just renamed gesture.key extensions to and all the locksettings files in /data/system to .bak or .old. When trying to add a PIN under sttings/lockscreen and checking the locksettings.db through sq lite editor that would be created , it would only have 5 entries under locksettings. I would then get the incorrect PIN message upon rebooting and have to go back to safestrap and rename those files. After rebooting this last time I went and deleted the gesture.key and all 3 locksettings files. I then went and selected the password option. I created a password and upon rebooting, IT WORKED!!!! I then checked the locksettings.db in sqlite and found that there were several more entries for it. I then went and changed the lockscreen from password to my regular PIN. I rebooted the phone and this time the PIN worked!!! I don't know why but I am happy agan.
mikeyk101 said:
Somehow I was able to fix this. i don't quite remember all the steps but I got it done. I had originally just renamed gesture.key extensions to and all the locksettings files in /data/system to .bak or .old. When trying to add a PIN under sttings/lockscreen and checking the locksettings.db through sq lite editor that would be created , it would only have 5 entries under locksettings. I would then get the incorrect PIN message upon rebooting and have to go back to safestrap and rename those files. After rebooting this last time I went and deleted the gesture.key and all 3 locksettings files. I then went and selected the password option. I created a password and upon rebooting, IT WORKED!!!! I then checked the locksettings.db in sqlite and found that there were several more entries for it. I then went and changed the lockscreen from password to my regular PIN. I rebooted the phone and this time the PIN worked!!! I don't know why but I am happy agan.
Click to expand...
Click to collapse
I know this is old, but thank you! You saved me from having to reinstall all my apps after getting my phone back from Samsung with a new motherboard (essentially new phone).
Related
Since rooting my phone I have been unable to change my lock screen wallpaper, it never sticks. Any ideas? Could I push the image to the proper folder?
DRACONIANDRAGON said:
Since rooting my phone I have been unable to change my lock screen wallpaper, it never sticks. Any ideas? Could I push the image to the proper folder?
Click to expand...
Click to collapse
did you freeze or remove any LG apks? I can change the background on mine after root.
Clear data and cache on lockscreen apk, should work then.
Sent from my Nexus 7
Worked for me
(First ever post, so hope this helps someone)
I had this exact same issue, prompted by the above I guessed that it was something to do with permissions or corruption of the files for the lock screen wallpaper.
I found that deleting the wallpaper.png file in data/data/com.lge.lockscreensettings, and also deleting the contents of the cache directory worked for me, it reset the phone to the initial stock lock wallpaper, and the next time I set it, it finally worked again.
Unfortunately I did not take a full note of the permissions on the wallpaper.png file before I started, however I strongly believe that they were different from what they are now, which is rw-rw-rw- so if someone else has the same issue they might like to try simply changing the permissions on the file as a first step.
Rooted LG G2 - stock ROM - TWRP installed.
juststarted said:
(First ever post, so hope this helps someone)
I had this exact same issue, prompted by the above I guessed that it was something to do with permissions or corruption of the files for the lock screen wallpaper.
I found that deleting the wallpaper.png file in data/data/com.lge.lockscreensettings, and also deleting the contents of the cache directory worked for me, it reset the phone to the initial stock lock wallpaper, and the next time I set it, it finally worked again.
Unfortunately I did not take a full note of the permissions on the wallpaper.png file before I started, however I strongly believe that they were different from what they are now, which is rw-rw-rw- so if someone else has the same issue they might like to try simply changing the permissions on the file as a first step.
Rooted LG G2 - stock ROM - TWRP installed.
Click to expand...
Click to collapse
Worked for me, on a LG G2, thanks bud
I just changed the permissions of wallpaper.png
in Data/Data/com.lgelockscreensettings/files and VIOLA! I was able to change my lockscreen background again.
Hi people!
I somehow seem to have corrupted the filesystem of /system somehow. I was replacing a background image file for my rom x-note inside the folder /system/script/images. No big deal, I renamed a present file and injected a new one in its place. Selected it in the x-note settings and things were great. Day after this I decided it was time for a TWRP backup. It starts, 3 seconds and BAM, phone reboots. I grab my root explorer (ES) and go to the folder in question again. My injected file is gone. I attempt renaming the backup of the old file thinking I'd injecting my own file again. BAM, reboot. Trying it again, this time I can't even go INTO the images folder before the phone reboots.
I go into recovery, twrp, trying to use the filemanager there to do the operation. Same result, reboot on trying to enter the folder. How the hell did this happen?? and what can I do? Can I just flash the system partition of the rom again to fix this (so I don't have to set everything up again although I have titanium backups of course).
EDIT: I mean dirty flash by system only
EDIT2: I think I may have renamed the original file ".bak " note the space, maybe that's what f**king it all up.
For others finding themselves in this situation: there's little to do to save the system-partition. There must've been an error sneaked into the partition table or something like that. I dirty-flashed the rom again BUT also had to restore the data partition after that. Then everything was back to normal. This time around I injected the modified background file using the file manager of TWRP. This worked.
Case closed. If anybody cares to explain how it could happen, feel free.
I'm on the stock rom and I tried following this guy but I'm too dumb to figure out how do anything passed installing a ROM. So instead of following that guy, I tried doing the Nexus 4 method in the link. I probably made a stupid mistake so that's on me. I copied the just the generic.kl file using ES File Explorer and pasted it into a folder outside the system files. I made another copy of the file and started editing one. I pasted the edited generic.kl file back into the root location and restarted my phone. Nothing happened except now my power button doesn't operate correctly. It doesn't wake or put my phone to sleep. What makes this worse is my Knock-On is sorta broken because I dropped my phone so I have to tap about 30~ times to get it to function once. I tried copying the backup I made back into the folder but it didn't change anything. What can I do that isn't a factory reset? Would a factory reset even work? I'm only rooted, no unlocked bootloader.
This is weird.
I bought a T95 box and have been using it with an external keyboard almost flawlessly for months. The only issue was that the Enter key was incorrectly mapped.
I found a guide to fix this, which involved using a root browser to edit a single word in a keyboard mapping file. I installed two root browsers, made the change to the file and then found it wouldn't save due to a "read only file system". I thought I'd change the permissions of the file and then the folder just to make this tiny change, but nothing would do it. Then I looked at the folder, and the file i had been trying to save had been completely blanked - 0kilobytes. Which is weird, as I thought this was a read only file system?
I found another copy of the file and tried to paste it into the folder, but exactly the same problem again -read only file system.
My keyboard is now useless as none of the keys are recognised and I have no way of restoring it to functionality as I can't restore the file that was overwritten on the allegedly "read only file system".
Any suggestions? I guess a factory reset might possibly help, but I've spent the best part of a year setting this device up just right so that has to be a very last resort. Tearing my hair out here...
I managed to delete the 0kb file and paste a replacement in its place, but it too instantly became 0kb. This is surreal.
I have a S6 lite 2022 LTE version SM-P619. It's rooted and works great but I tried to change to boot screen qmg and shut down qmg's with ones that have a bit more animation. They work once but next reboot or shut down the original boring qmg's are back and the ones I inserted into the media folder have gone poof. Start up ones are that important but my shutdown one is of a tv shutting down that look really nice on the tablet. once...
edit: after doing a few things on this tablen I begin to wonder, is there some sort of security on the root partion? When I delete a file from the system/app it comes back after rebooting. When I rename that file, it comes back to original after rebooting.
Most puzzled... never seen this happen before.
*Bump* because I would really like to know how to really delete an app without it returning after a reboot. Rooted and using Root Explorer. I go to Root/system/app and delete a file such as DailyBoard. When I reboot the tablet it is back in the app folder like it was never deleted. As well, the issue of overwriting the shutdown.qmg is same, reboot and original is back. Am I only one with this or is anyone else seeing this?
Okay, I finally found out why this happens. Samsung has made all dynamic partitions (odm, product, system, vendor) READ ONLY! So even if you are rooted, you won't be able to debloat or change files on anything in the tablet (S6 Lite LTE 2022 P619)
So after searching around for an answer, I stumble upon a solution that worked for me. But you have to be able re-build the AP-P619XXXXX.tar file. Reason is that you will have a new super.img that is Read Write and allows you to delete files and push files to your tablet without the changes being undone. And rebuilding the ap-tar file is because the tablet doesn't have a working fastboot in it.
Go to: https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/ and follow all instructions carefully. You DO need to be rooted and do need Magisk install to be able to use this method. Good Luck