This is mostly common knowlegde by many users and already explained in another topic but in the last couple of days i needed to help some guys with a lockscreen problem like wrong PIN, pattern or password for whatever reason it started.
Instead of deleting some files I made a small flashable zip which can be held on your extSD in case something might go wrong in future
Normally with deleting in twrp file manager : /data/system/locksettings.db you would be good to go.
In other cases you might need to delete :
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
Anyway, just flash this zip : A2017X_remove _all_ locksettings NEW VERSION due to typo - thnx @dnlilas
......and password, pattern and pin will be removed :good:
Btw, if you have FP + pin, pattern or password and apply this zip, only the FP remain. Pin, pattern or password are gone.
Tested on G version. Should work on U/CN too although in some cases it had no effect. Just try and see
Thanks. It worked on a Note 3 SM-N900P i was unlocking for a customer. Lucky me i was able to install TWRP and it didn't force me to do a factory reset so i could avoid resetting it from recovery menu thus triggering on the Samsung lock status. I guess security on those days was none to zero. I feel confident that the route i took to remove the pattern is not available on newer phones/ android versions.
THX!
Does it also work if TWRP can 't mount the system partition due to password protection?
@raystef66
Just for information: there is a typo in updater-script:
delete("/data/system/gatekeeper.patern.key");
instead of:
delete("/data/system/gatekeeper.pattern.key");
dnlilas said:
@raystef66
Just for information: there is a typo in updater-script:
delete("/data/system/gatekeeper.patern.key");
instead of:
delete("/data/system/gatekeeper.pattern.key");
Click to expand...
Click to collapse
Good find ! Indeed there is
A2017X_remove+_all_+locksettings
hello community ,
Do I need Twrp in phone ?When I want use the script ?
How to use this script ? I must rebulid fota and paste script ?
best regards .
My phone is stuck in "phone is starting" screen, i can open settings app from the quick settings but i cant open any apps from the settings
Nokia 7.1
Havoc-OS Android 10
Removed PIN
Related
I need to recover screen lock password and it doesn't give me the "forgot your password?" option that allow me to recover it with google account
adb shell replies with error: device not found
but I still can go to ADB sideload
can we Use sideload to get rid of the screen lock ?
NOTE: its password not pattern or pin
HELP
heeeeeeeeeeeeeeeeeeeeeeeeeeeeeeelp
@me1mon Dunno mate, maybe you should ask on the Samsung threads, or use google, I found this... http://everydaylife.globalpost.com/unlock-galaxy-s-forgot-password-22140.html but I don't know if it works with your phone
oscarblue48 said:
@me1mon Dunno mate, maybe you should ask on the Samsung threads, or use google, I found this... http://everydaylife.globalpost.com/unlock-galaxy-s-forgot-password-22140.html but I don't know if it works with your phone
Click to expand...
Click to collapse
thanks for your reply but I already know that and I don't want to lose my data
[SOLVED]
I solved that by myself
I used CWM to mount all the partitions and used (Aroma file manager) App inside recovery to get access to the system files and removed (gesture.key, password.key & other password related files that are located at "/data/system/gesture.key")
after I came across many amendments on my phone (j7p)
twrp ,root, xsposed, Nonencrypt kernel,deleting systemapps.....
i found that my phone doesnot remeber my wifi paswword /ssid
after each reboot , also after disconnect & connect to wifi ....
I could not determine the cause of the problem.
I restored my efs via twrp, but the problem still present
so i came to a temporary solution, and i posted here in order to be helpfull to others
or if someone have a better solution... so he can guid us
first off all backup your efs and keep it in safe place
now open your phone buildprop it is in your root/system ( you should have root access,afaik) via (buildprop edditor or totalcommander..or other
then scroll down to that string
ro.securestorage.support=true
change the value into false
ro.securestorage.support=false
save it and enter your wifi info...again
try to reboot your phone.. if the problem Disappeared, then it is secure storage issue
here i donot have a specific solution ,since i use a moded kernel
but maybe you can get ride of it by deleting ss-data in efs folder (via total-commander .apk or es file explorer.apk ...)
this file contains decryption of your wifi passwords..., and other
the problem will disappear untill you flash new thing from recovery
here you can take another backup of your efs beside the original one, and give it ashot from recovery after you make Major modification
at last I hope some of Veteran members give us better idea
Thanks a lot. By the way, can you use your front flash with the modded kernel?
It's not working for me.
I don't use it but i want to know if it's an issue with the kernel or i messed up a step somewhere.
Zhiro90 said:
Thanks a lot. By the way, can you use your front flash with the modded kernel?
It's not working for me.
I don't use it but i want to know if it's an issue with the kernel or i messed up a step somewhere.
Click to expand...
Click to collapse
sorry for my late reply
j7P doesn't have separate front flash (led) ....afaik
the screen only turn into white when you are using front flash cam
as for me I updated my J7p firmware ...so I am using stock kernel at now
BTW there is no need to modded kernel if U use USBotg pendrive
in clear steps from stock firmware u install twrp via odin
then U can root your phone , put supersu *zip in USBotg pendrive
attach it to your phone, mount this USB in twrp then flash any *zip file... such as SuperSU,,, and then you can install xposed ....
so there is no need to modded kernel , unless you need to get backups for your phone
Regards
Bootup password
I cant change ro.securestorage.support value to false... triggers bootup password then it rejects all password, cant get through... I then have to restore my build.prop and give up
nazgul67 said:
I cant change ro.securestorage.support value to true... triggers bootup password then it rejects all password, cant get through... I then have to restore my build.prop and give up
Click to expand...
Click to collapse
you should set it to false
not true
My bad, i mean setting it false. Then some bootup password is required.
nazgul67 said:
My bad, i mean setting it false. Then some bootup password is required.
Click to expand...
Click to collapse
NM
since the problem still presnet , so i think it is not secure storage issue
any how there is a new domed kernel without this issue (remembering wifi password)
give it a shot
https://forum.xda-developers.com/ga...el-theflash-kernel-v1-0-t3616374#post72618392
Regards
xcorona said:
NM
since the problem still presnet , so i think it is not secure storage issue
any how there is a new domed kernel without this issue (remembering wifi password)
give it a shot
https://forum.xda-developers.com/ga...el-theflash-kernel-v1-0-t3616374#post72618392
Regards
Click to expand...
Click to collapse
Im using default ROM and Kernel. I can see wifi passwords now. One of my apps is setting my selinux to permissive I dont know which is it. Maybe its because of my root, im just thankful for it ?
Hi all,
I have a question about encryption on Android 9. I recently fixed up my old Nexus 5 to use as a test device and set it up with the newest Unlegacy Android (Pie) ROM (OpenGAPPS Mini, Magisk 17.1) and enabled encryption on it. So far so good and everything works perfectly without any Problem.
As I was always curious about changing the encryption password on my current daily driver (Nexus 6) because I use a fairly short passcode to not make it annoying to get into the phone, I searched a little and came across the App SnooperStopper, which would do everything I wanted: Make it able to use different passwords for encryption and the lock screen, but also secure the lock screen in a way that after some failed unlock attempts the phone would reboot, requiring the full encryption password again.
After testing on my Nexus 5 I found out that the way the app changes the password does not work on the newer Android OSes anymore. (I also tested the method mentioned on this XDA Blog post without success)
So my question is if there is an updated way to change encryption password or if there is any other way to achieve my goal of having different passwords for encryption and lock screen as well as making the phone reboot on too many retries.
Thanks a bunch!
~Joe
Maybe a bit late, but it might help someone else, as I was looking for a way in Oreo or later the last 2 days too.
bastei said:
As a workaround on Android Pie, you can do the following (on your own risk):
set the desired password for the screen lock
backup lockscreen files:
all files under /data/system_de/0/spblob/
files containing "_synthetic_password_" in /data/misc/keystore/user_0/
/data/system/locksettings.db
set the desired password for the device encryption
restore / replace all lockscreen files
If something went wrong, sqlite into /data/system/locksettings.db and set the values of sp-handle and lockscreen.password_type to 0 to reset the screen lock.
Click to expand...
Click to collapse
For me this did not work and just made the phone hang for a while and then reboot after entering the encryption password.
An alternative way I found was to set a password normally (the one you want for the disk encryption) and then just delete all these files and restart the process of setting a new lockscreen password while denying to turn on the boot protection. This might work on some devices, but according to the following link, this doesn't work for example on LineageOS 16.
Also it seems like LineageOS 17 and possibly other Roms reenabled the old way of changing the password in the Terminal. See: https://github.com/nelenkov/cryptfs-password-manager/issues/25
I wished I could do it without installing any apps, but I am not knowledgeable enough to proceed further. For me the only solution was this modified version of the cryptfs App. The normal install process is explained there as well: https://github.com/thedroidgeek/cryptfs-password-manager/releases
Here is how I installed it:
1) Install the App
2) Get the 'App Systemizer' module through the Magisk Manager (https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851)
3) Install Cryptfs App normally
4) Run 'systemize' as root in a Terminal app (I got a busybox error and ignored it)
5) Choose 'Systemize Installed Apps (Listed)' and find 'Cryptfs Password'
6) install into '/system/priv-app'
7) For me it errored out saying that the app already exists, ignore it.
8) reboot
9) Start Cryptfs App. If the process of making it a system app failed, then the app shuts down with an error message about needing to be systemized.
10) set your encryption password in the app.
11) Reboot, check if it works
12) Disable cryptfs App and the App systemizer module, no need to keep them running until next use.
The difference to snooper Stopper is that you can't set any actions to take if the password is entered incorrectly a few times. However if that functionality is needed, you can install snooper Stopper afterwards and just ignore the password change options and just set the behaviors.
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
Found it to be ineffective against the latest lockscreen bugs.
Code:
I have made an attempt to fix the lockscreen bug that happens randomly on the kenzo (ie when you go to enter the pin number, the lock screen will keep appearing no matter if you input the correct value.) eventually you will have to delete the locksettings.db file to reset it so you can boot into the phone.
I have made a Magisk module that sets the locksettings.db file read-only meaning nothing can modify the file ('something' causes it to corrupt and develop the bug), unfortunately just setting it read-only will cause the OS not to boot so I had to set it read-write on boot then set it read-only after boot finishes., this is a quick 'fix' , I had several people test including myself and so far the bug has not appeared again, so it might just be luck or it's a effective fix, I put a 20 second delay on before setting it read-only so it might be possible for the bug to develop within this timeframe, but unlikely unless the system crashes on boot. so please make sure the system is stable before using the module.
Preliminary checks.
First make sure you currently don't have the 'bug' if you do flash a lock screen reset or delete locksettings.db, then setup a working lock screen., after you are satisfied, you can flash this module.
Bugs that might come from this module.
1. since it sets the file read-only, changing the lockscreen type or password might not work, you must disable the module, and either delete locksettings.db (from twrp), or change the permissions back to 660, then make your changes, then re-enable the module and reboot. - so I suggest using this module if you don't frequently change the lockscreen type or password/pattern/pin. I intended this to be a set and forget kinda fix.
2. I suspect a softreboot or systemui crash might cause the system to get stuck in a loop (untested) but I figure if it's the same as a normal reboot with it set readonly it will get stuck, if that happens then a force reboot might be necessary (power buttons pressed for 10 sec). again I am unsure if this will happen but there is a possibility.
3. Unknown, let me know.
Uninstall.
I had made this module for myself initially but figured more people might benefit from it (if it works), so uninstall / disable the module might require some manual fix-ups, so if you have problems here are the steps you should follow.
first reboot to twrp, go to /data/adb/modules/rn3plsf/ and delete the folder (this effectively disables the module, or you can use the orangefox magisk manager to disable / remove) , then go /data/system/locksettings.db and set permissions to 660 (you can also delete the locksettings.db file if you want to start new), reboot & everything should be as it was before.
I have only tested this on Android 10 (msm xtended), I am unsure if it will work on lower android versions, don't try it on selinux builds or miui. (well you can but it probably won't work)
-
This work is ALPHA, I expect the user to know how to use twrp and modify / delete files and are ok with experimenting, I may fix-up the module or make a uninstaller at a later date if it has good results, but for now I am just testing this. [B]use at own risk[/B],. I hope I have found a fix, but results are still to early to tell. please test and report back.
I don't check xda everyday, sometimes it can be weeks before I check I am pretty busy .
Thank you, this bug is the only thing that holded me from using Q roms.
Sir, I had installed this module but the bug still appeared the next time I booted after updating the orange fox recovery..
But after a forced reboot things went fine.
Will inform here next time I face the bug...thanks for the module anyways..
uploaded v2 and a uninstaller.
I lowered the wait time to 8 seconds, I am hoping this is not too quick, on my system it is fine, but I am not sure how it will work on other systems.
sometimes, If I reboot the device fingerprint is not working and If I tried to unlock with pattern it just hangs .. I have to Force reboot it (sometimes more than once) to enter the Home screen. will this module fix this also ?