So this happens almost in any rom I try like lineage A10 and dot os A11 and havoc and all. When I install the Google app from playstore and if the device hapens to reboot after that it's basicaly soft bricked if u have a pin, patern or password setup. The lockscreen after reboot doesn't allow to use biometrics and after I put the pattern the screen goes black and the lock screen comes up again. The only fix I've found is deleting the locksettings.db file from twrp. Does it happen only to me or fr others too?
poornarao211 said:
So this happens almost in any rom I try like lineage A10 and dot os A11 and havoc and all. When I install the Google app from playstore and if the device hapens to reboot after that it's basicaly soft bricked if u have a pin, patern or password setup. The lockscreen after reboot doesn't allow to use biometrics and after I put the pattern the screen goes black and the lock screen comes up again. The only fix I've found is deleting the locksettings.db file from twrp. Does it happen only to me or fr others too?
Click to expand...
Click to collapse
that screen lock is a common bug in a10-a11 is random , does not have a permanent fix rn...
Oh ok
Related
hello friends. pattern lock is a cool thing in android smartphone. but sometimes it becomes a big problem to us. if we draw wrong pattern several times then our devices gets locked. we need to unlock then using our gmail account. but the problem arises if we don't have enabled data network or added a Google account in our phone. so the only solution left is to hard reset our phones and loosing all the data. but now u can remove your pattern lock without loosing data. the only condition is that u must have a custom recovery installed on your device like clockworkmod recovery or TWRP recovery. i have made a flashable zip file to remove pattern lock or password lock. download the file from attachment and flash in recovery mode and enjoy. post reply if i helped you.
I have an HTC One S running Candy ROM 4.4.4
When I run the encryption process it asks for my pin, reboots and goes through the encryption process,
but when it boots up it asks for a password that i didn't set.
When I try to set a password and encrypt my phone it doesn't let me,
it just goes through a normal reboot.
Could there be a built in password that it is looking at and if so is there a way to change it?
ogre55 said:
I have an HTC One S running Candy ROM 4.4.4
When I run the encryption process it asks for my pin, reboots and goes through the encryption process,
but when it boots up it asks for a password that i didn't set.
When I try to set a password and encrypt my phone it doesn't let me,
it just goes through a normal reboot.
Could there be a built in password that it is looking at and if so is there a way to change it?
Click to expand...
Click to collapse
The password is your PIN. The android system uses the lock screen pin for the encryption process.
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
BluGuy said:
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
Click to expand...
Click to collapse
You need to re-enable the pin from lockscreen options
Sent from my A0001 using Tapatalk
cloudx720 said:
You need to re-enable the pin from lockscreen options
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I think you misunderstood. The lockscreen still ask for a pin. When the phone has encryption turned on, when you either restart or turn the phone on you will receive a prompt on a grey screen to enter you pin. At this point Android hasn't fully booted yet. It then checks the pin and then boots Android. My phone is no longer brining me to this grey screen, it flashes grey but seems to just skip that screen. It is just fully loading android all the way.
BluGuy said:
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
Click to expand...
Click to collapse
If you set up pin code again will ask if you want pin to boot.
You have two option
One is pin to boot
Other pin after boot
I do not use screenwise for related issues
But i am familiar with encryption
Encryption will exist unless do factory reset
geowolf1000 said:
If you set up pin code again will ask if you want pin to boot.
You have two option
One is pin to boot
Other pin after boot
I do not use screenwise for related issues
But i am familiar with encryption
Encryption will exist unless do factory reset
Click to expand...
Click to collapse
I didn't even know it had the other option in it to ask for the pin during boot up. I would have thought if there was an option for that it would be in the Security menu with encryption rather than the lockscreen menu. Thanks.
Hi,
I've got ZTE Nubia Z9 mini with a stock rom of Android 5.0.2. Today I have clicked power on button and I saw the clock is on a wrong place. I've restarted the phone and get powered off few times. I've also tried some custom screen locks and launchers without any success. because while using custom screen lock I have to disable default lock screen but I cannot do that because I have my certificates on the device and when I do that android deletes my certificate and to upload them again I have to enable PIN etc. How can I bring it back. I have already clean personal data from nubia launcher but this didn't help. Factory reset of course is an option but it is as a lat position on my list. Getting xposed framework is not an option for me because I don't have custom bootloader. Please help ....
I'm having a odd issue. I just restarted my phone to fix some slow performance issue.s When I reboot I was presented with my lock screen on the "enter pin" screen that pops up after a reboot. But after that screen pops up, I am unable to enter in any lock screen inputs as my lock screen appears to be frozen. I can lock and unlock the phone and use lock screen gestures however, the phone unlocks to the frozen lock screen and there nothing I can do from there. I did not make any edits to any files before this issue popped up.
I can still access fastboot and twrp just fine but I'm unsure what to do as this is a brand new issue.
Any help is greatly appreciated.
Thanks,
Do you have any magisk modules?
@soka said:
Do you have any magisk modules?
Click to expand...
Click to collapse
I'm on XXX but I've diabled that with magisk manager through twrp
Possibly xXx removed something you required for the phone to operate normally, installing your current OOS version on both slots could help.