Lock Screen Frozen When Phone restarts - OnePlus 7 Pro Questions & Answers

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.

Related

[Q] Enabled Encryption - unable to boot

Unfortunately my OnePlus is no longer able to function and would like some assistance/suggestion from the community.
OnePlus has TWRP installed
- installed Paranoid Android rom = no issues
- enabled encryption
Now here is where the issue occurs.
When I start the phone I am able to see the PA bootup screen, it prompts me to enter the password. Once the password is entered "bugdroid" appears on the screen for a quick flash and then disappears. The screen continue to stay blank/black with no further progress, I have left the phone in this state for at least 20mins but it still doesn't proceed further. It should also be noted the the soft keys STAYS lit once the password has been entered for decryption.
I am still able to boot into recovery, enter my password to decrypt and use the standard TWRP functions. It should be noted that unfortunately I haven't done a backup on the phone at all {something that I totally regret right now), plus there is no rom left on the phone for me to attempt a install.
Any help is appreciated
note: the phone as able to complete its bootup process when I initially activated encryption but has failed ever since the first reboot
There are multiple threads discussing this in the very section you posted this thread in. Have a look, you'll find what you need.
Transmitted via Bacon

[Q] Lock Screen not working on Android 5.0 with Root

Hi,
I'm using an unlocked Nexus 5, and flashed as soon as the factory image was released. I used CF-Autoroot to gain root access.
The problem that I'm having is that the lock screen does not work. This means that when I lock the phone (power button), it just fades to black, but when I hit the button again (either immediately, or after a wait), I go straight to where I was, the lock screen does not activate no matter what I do. I've tried letting it time out, still no luck.
When I restart the phone, it shows the lock screen, but sounds like something is trying to unlock the phone, and the phone then unlocks and doesn't lock again. I've tried disabling all Device Administrators, with no luck. I tried a factory reset and then a re-flash followed by another factory reset, and the problem still persists. I've also tried toggling Smart Lock on and off, still no change.
If I go to the security settings and re-select a Screen Lock mode, then the lock screen shows up again, but after I unlock, it goes away never to return.
This has been extremely frustrating, since Smart Lock was one of the features I was most looking forward to. Does anyone know what could be causing this?
The current Root apps that I use are:
1. SuperSU (obviously) 2.23 BETA
2. BusyBox Free
3. AutomateIt Pro
4. Greenify
5. Power Toggles
6. AdAway
7. Titanium Backup
Another note: After the factory-reset, wipe, flash, factory-reset that I did, I restored all non-system Apps and data with Titanium Backup. Just putting this here in case you guys know of any app that causes this problem.
Ekitrak said:
Hi,
I'm using an unlocked Nexus 5, and flashed as soon as the factory image was released. I used CF-Autoroot to gain root access.
The problem that I'm having is that the lock screen does not work. This means that when I lock the phone (power button), it just fades to black, but when I hit the button again (either immediately, or after a wait), I go straight to where I was, the lock screen does not activate no matter what I do. I've tried letting it time out, still no luck.
When I restart the phone, it shows the lock screen, but sounds like something is trying to unlock the phone, and the phone then unlocks and doesn't lock again. I've tried disabling all Device Administrators, with no luck. I tried a factory reset and then a re-flash followed by another factory reset, and the problem still persists. I've also tried toggling Smart Lock on and off, still no change.
If I go to the security settings and re-select a Screen Lock mode, then the lock screen shows up again, but after I unlock, it goes away never to return.
This has been extremely frustrating, since Smart Lock was one of the features I was most looking forward to. Does anyone know what could be causing this?
The current Root apps that I use are:
1. SuperSU (obviously) 2.23 BETA
2. BusyBox Free
3. AutomateIt Pro
4. Greenify
5. Power Toggles
6. AdAway
7. Titanium Backup
Another note: After the factory-reset, wipe, flash, factory-reset that I did, I restored all non-system Apps and data with Titanium Backup. Just putting this here in case you guys know of any app that causes this problem.
Click to expand...
Click to collapse
I'm facing the same issue with my NON-rooted Nexus 4.
Anybody having any ideas?
Arijit
arijitmaniac said:
I'm facing the same issue with my NON-rooted Nexus 4.
Anybody having any ideas?
Arijit
Click to expand...
Click to collapse
Mine fixed itself after I manually installed the latest Google Play Services apk. Maybe try that and see if it works for you...

Encryption problem

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.

Decryption fails at boot but works fine in recovery

Can't find a solution for this anywhere. I have an encrypted rooted moto g with unlocked bootloader and latest harp recovery. I installed an app that needed accessibility services which turned off unlock screen at bootup. I downloaded am closed app that was supposed to allow me to use accessibility services without turning off encryption at bootup but it didn't appear to do anything. I then went into security settings and re-entered unlock gesture and when asked if I wanted to be prompted for unlock at boot I said yes. Looked at accessibility settings and the permissions for the app were still turned on. I revolted the phone and now after moto logo boot screen, without asking me for a password, it goes straight to a screen saying that my password is correct but that decryption failed and to please factory reset phone. However I can boot into harp recovery and enter my unlock gesture and it works fine. So how can I turn off accessibility services for that app or otherwise fix this problem through recovery or adb? Please help.

ODIN No command and PIN not registered

Ok Masters, so I am having the same issue that this guy here:
https://forum.xda-developers.com/ga...mand-error-samsung-galaxy-j7-prime-s-t3929850
I can install any rom. However, the pin to register either face or fingerprint, does not work. So I cannot even get to the fingerprint screen because it returns me to enter pin, and when I re-enter it, it says is wrong. I guess it has something to do, the fingerprint so far, had just worked on Cerberus AOSP rom, but neither on one UI nor 8.1 based roms work. on 8.1 I get setting had stopped.
So, flash stock over odin was already tried and it gets stuck there. Already flashed no verity, no luck, flashed, bbos, godness, venom, no luck.
Any other advice? Seems that somehow I messed up with the encryption and that is making not registering the pin or pattern.
I managed to pass the screen with Magisk, but as soon as system boots and I try to set fingerprint, it says settings stopped. I am really frustrated now.
Thanks,
This was already solved. If anyone is interested in getting more details he they are:
The no command was because someway somehow, the system partition was "busy " or non-writteable, at least that was the message that I was able to read. I don't know how it got to that state, but my solution was the following:
- Select system partition in twrp and tapped on repair file system. I got an error immediately that twrp could not read system block. I changed file system to ext2 and rebooted twrp.
- once again I clicked on repair file system. No errors this time. Rebooted twrp. Changed file system to ext4. Rebooted twrp. Repaired file system again and rebooted twrp once again. Downloaded an aosp 8.1 rom and setted screen lock after the set up, it worked. Then, installed apollo v1. Screen got frozen for a second when setting pin, but it let me pass to set my fingerprints.
Then I knew that it was already working. Installed a One Ui rom to try and it worked again my screen lock with finger print.
Hopefully this helps someone as I found no solution whatsoever in any part of forums or internet, this was pure trial an error over 4 days.

Categories

Resources