I unlocked the bootloader today without any noticable averse effects. When I was setting up the phone I restored from Google's cloud backup. While I was going through setting up the lock screen and it wouldn't let me. I would go through the motions to add a fingerprint but every time I would add a pattern I would be asked to add the pattern again. No matter what I do, setting up the lock screen will not stick! I also performed a factory reset and didn't restore anything from the cloud backup and no luck. Does anyone else have this problem? If you know how to fix it I would really appreciate it. Here's a couple screen shots, but I don't think they'll help. Here's to trying
I just got Magisk installed after flashing a patched boot image through fastboot and I still can't add the fingerprint or lock screen. Any suggestions are welcome
I was unable to lock my screen with my bootloader unlocked and i need it locked for some of my apps to work so i relocked my bootloader.
Marco0070 said:
I was unable to lock my screen with my bootloader unlocked and i need it locked for some of my apps to work so i relocked my bootloader.
Click to expand...
Click to collapse
Does magisk still work with a locked bootloader?
Mustachetic said:
Does magisk still work with a locked bootloader?
Click to expand...
Click to collapse
I didn't install magisk sorry I don't know
Sent from my moto z4 using Tapatalk
Marco0070 said:
I didn't install magisk sorry I don't know
Click to expand...
Click to collapse
I updated to 105-75 and reinstalled magisk. I am able to add a lock screen. My device passes safety net also
Mustachetic said:
I updated to 105-75 and reinstalled magisk. I am able to add a lock screen. My device passes safety net also
Click to expand...
Click to collapse
Thanks for the update
Sent from my moto z4 using Tapatalk
I ran into this problem as well. It would not let me set any kind of lock screen. I was trying to install the Verizon software in order to get WiFi calling, per the thread elsewhere here in the Z4 forums.
I had thought the issue was related to either Magisk, copying from my old phone, or when I was trying to set the lock screen during the setup process, so I ended up doing the following (going from having bootloader unlock and running on Verizon rom but not being able to add a screen lock)
-Wipe data
-Flash initial Verizon ROM
-Do initial setup but skip trying to set screen lock in the setup process
-After setup, then set screen lock
-Update to latest Verizon ROM
-Flash patched boot image corresponding to the updated ROM
I'm not sure if the problem was Magisk related or if it got screwed up setting the lock screen during the initial setup process and skipping that and doing it later fixed the issue, but those were my two guesses. Eventually it all worked, and I now have lock screen and root via Magisk working along with WiFi calling. It passes Safety Net.
I had the same thing happen when I first got my phone. What ended up resolving the issue for me was that I flashed the image as root in Linux.
Related
Hi All,
I just rooted with chainfire .img via fastboot and updated supersu to latest from google play. I unlocked the bootloader the second I bought the phone, decided to root now, so no wipe was involved (this is why I can compare with no root boot times). No custom rom installed. Stock rom, rooted and bootloader locked.
What I noticed is that all desktop widgets take 10-15 seconds to load after boot. Widgets are in a blank state for that period of time, like freezing.
Anyone else noticed this ? Is expected to see this after rooting ? Maybe supersu checking entire device after boot and slowing the device ?
Thanks in advance
I also noticed this on stock rom but also on custom rom.
I have to wait before using Power Toggles widget (but not with Poweramp). The same for some apps that should start at boot as Headset Control, Clipper, Tasker, LMT Launcher...
BTW if you used CF Auto Root your BL is unlocked.
Glad I an not the only one seeing this.
I have locked my bootloader after root using bootunlocker. This is why I said bootloader is locked. I would unroot and wipe to see if this is a root problem or not, but I am still not clear if I can backup and restore to EXACT same state I am now (apps, data, settings, widgets, etc.)
LE: apparently slow widgets after boot are caused in my case by sim pin check. If I disable the sim pin check on boot, all widgets load instantly first time after boot. Can anyone else test and confirm ?
Anyone else notice this?
Sent from my SPH-L900 using xda premium
I also noticed this problem, not sure if after root or not, as I rooted my phone immediately. Tested against Nex4 and although Nex5 lock-screen comes up 2 seconds earlier, the Nex4 widgets immediately loads, whereas my Nex5 take 30 seconds for widgets to load.
Ladduro said:
LE: apparently slow widgets after boot are caused in my case by sim pin check. If I disable the sim pin check on boot, all widgets load instantly first time after boot. Can anyone else test and confirm ?
Click to expand...
Click to collapse
Can you explain in more detail where this option is?
Settings > Security > Set Up SIM card lock > Lock SIM card on or off.
Put it to off and try again.
I flashed factory images and the widgets do the same thing, so I dont think it is root related.
I have the same problem
The widgets were running perfectly when the Nexus 5 was stock (unrooted, locked, stock rom). As soon as I unlocked, rooted but stock rom still, the widgets were slow to load -- 30 seconds. I then insalled DroidKang, and still -- Widgets are slow to load;
I did not, however, check if putting in ART runtime has anything to do with it (it could as I did this after unrooting my phone.)
Anybody has ideas ?
(I have tried to lock/unlock SIM card, and still same effect)
I also have this issue and I've never used a pin code on my device , It was working perfectly fine before I rooted it :crying:
So I have a Google Pixel 2 and I installed the android P preview via sideload but I had my bootloader locked now I can try to toggle OEM unlock and put in my pattern but after I put my password in it still says it's off idk what to do I haven't tried to flash the 8.1 factory image or unlocking yet but idk if I'll be able too there's I'm almost 100,% sure it's not a Verizon model I don't have any Verizon apps and on 8.1 I could toggle this on and it's not greyed out
I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.
EnormoDerClown said:
I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.
Click to expand...
Click to collapse
That wouldn't brick my phone?
Before you attempt anything extreme, I suggest factory reset your phone and do the minimal setup to get into the settings and try toggling
I did still no luck
To be fair: i can not guarantee that, but i can just imagine 3 scenarios:
1. Update fails, OTA install fails
2. OTA installs but a lot of FC´s with apps (factory reset afterwards shoudl get rid of that)
3. Everything installs and is functional without doing anything (i don´t think so).
i would expect, that option 2 would occure
Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out
AaronGavin said:
Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out
Click to expand...
Click to collapse
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.
March update could just be to old, April update could work because of newer data. OTA checks whether the update is older/newer.
quakeaz said:
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.
Click to expand...
Click to collapse
That actually worked xD thank you
AaronGavin said:
That actually worked xD thank you
Click to expand...
Click to collapse
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
It was never greyed out just after I put my password in it wouldn't turn on the slider and at first I just thought maybe it is on but bugged out but after I removed my password it just turned on properly I'm about to test it as soon as the factory image downloads again
quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
Back on 8.1 ?
Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....
Would this one work?
GitManMatt said:
Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
Thanks for this, I'll give it a go now
Working again
Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
yep, that's awesome, fully up and running now. Just for anyone else experiencing this problem, I downloaded the TWRP version listed above, then flashed it via ADB (unlock USB debugging on your phone, connect it, open a powershell window where you keep your adb files, 'adb reboot bootloader' then 'ffastboot flash recovery [NAME].img' and it will reinstall TWRP with the new version).
Bit of a moment when I rebooted to recovery, as faced with the same decryption unlock window, but this time the decryption worked and was able to access TWRP fully.
Nice one.
Hi,
After unlocking the bootloader with the latest official app, I cannot change the screen lock method of my Zenfone 6 with a message saying "Screen lock was already changed, try again with the new screen lock" and I can only choose "None" or "Swipe". The fingerprint breaks as a consequence because it relies on PIN/password/Gesture.
The phone comes with a fingerprint + password authentication before the unlocking, which seems to cause my issue due to mess-up of the TEE. Factory reset / Reflashing the whole image doesn't work.
Anyone experiencing similar issues? Is there any way to re-enable other unlocking methods?
Thanks!
Same happened to me,
I got back the pin option only when I relock the bootloader.
I used the official asus application, I'm gonna try the adb unlock option
Same thing here. Unlocking the bootloader breaks it. I fixed mine by flashing the downgrade to P zip, setting my phone all back up and then updating to Q. You might be able to just reflash Q and have it work, but if that fails go to P and then upgrade. Haven't had an issue since.
Did you downgrade to P being bootloader unlocked? If so , did you use the official asus method with their apk, or did you unlock with adb?
Thanks for your response !!!
[Removed]
DaConcho said:
Same thing here. Unlocking the bootloader breaks it. I fixed mine by flashing the downgrade to P zip, setting my phone all back up and then updating to Q. You might be able to just reflash Q and have it work, but if that fails go to P and then upgrade. Haven't had an issue since.
Click to expand...
Click to collapse
I can confirm that reflashing stock Q image doesn't work.
joesa said:
Did you downgrade to P being bootloader unlocked? If so , did you use the official asus method with their apk, or did you unlock with adb?
Thanks for your response !!!
Click to expand...
Click to collapse
I could never get the adb unlock method to work at all. I used the app to unlock, stayed unlocked and flashed back to Pie, then updated to Q
DaConcho said:
I could never get the adb unlock method to work at all. I used the app to unlock, stayed unlocked and flashed back to Pie, then updated to Q
Click to expand...
Click to collapse
Thanks,. A will try your method this weekend and let you know :good:
DaConcho said:
I could never get the adb unlock method to work at all. I used the app to unlock, stayed unlocked and flashed back to Pie, then updated to Q
Click to expand...
Click to collapse
It worked !!!!
Did exactly what you did and now I got back the screen lock options,
Thanks !!!!
So, I am on a custom ROM, but I understand that you solved this on stock. Does anyone have experience how this can be solved on a custom ROM? Thanks!
Hey, I was having the same problem and tried doing several things without success (Like deleting files in the /data/misc/keystore, changing different ROMS, etc). What fixed it for me was restoring the vendor partition, the problem was that I removed the enforced encryption flag and that was causing problems with the GSIs I was installing.
Xanderco said:
Hey, I was having the same problem and tried doing several things without success (Like deleting files in the /data/misc/keystore, changing different ROMS, etc). What fixed it for me was restoring the vendor partition, the problem was that I removed the enforced encryption flag and that was causing problems with the GSIs I was installing.
Click to expand...
Click to collapse
how did you restore the vendor partition? did you use the backup on twrp or something? is there a flashable zip?
also did this happen after you unlocked or after you installed a custom ROM with encryption disabled?
Did you guys manage to fix it? I actually have the same problem with my Redmi 8A after flashing Magisk on Havoc and Stock ROM. I tried to delete the locksettings. db and .key files but i still can't set a pattern or PIN
redm4227 said:
Did you guys manage to fix it? I actually have the same problem with my Redmi 8A after flashing Magisk on Havoc and Stock ROM. I tried to delete the locksettings. db and .key files but i still can't set a pattern or PIN
Click to expand...
Click to collapse
Do This It will Work Tried and Tested
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
Do This It will Work Tried and Tested
for video reference -https://www.youtube.com/watch?v=WOsUbcTQhrY
Above link is not my video so
What worked for me was re-locking the phone with fastboot. I didn't have to mess with any files.
drish malhotra said:
Do This It will Work Tried and Tested
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
Do This It will Work Tried and Tested
for video reference -https://www.youtube.com/watch?v=WOsUbcTQhrY
Above link is not my video so
Click to expand...
Click to collapse
Spot on !
Removing the .key and lockfiles from /data/system works !
I can set PIN again
....
Swipe TWRP on your phone, enter the system, and delete 2 locksettings....file in the DATA\ SYSTEM\ folder directory.. The file at the beginning can be successfully protected by restarting and setting a password or fingerprint.
abprie said:
So, I am on a custom ROM, but I understand that you solved this on stock. Does anyone have experience how this can be solved on a custom ROM? Thanks!
Click to expand...
Click to collapse
just aslo wipe vendor before flashing the rom it will help u. If doesnt work just ping me.
I'm thinking of trying out Android 12 Beta soon. Anybody try it out? Any bad bugs?
better wait , my phone is stuck in setup process "keep date from old phone" > "enter pin" > keep data from..." blabla
Seems great to me. No issues whatsoever!
I cleaned flashed to it from DP3 yesterday. Loving it so far! And I wasn't sure about some of the UI changes from the leaked photos.
The bugs I'm getting are:
Bubbles work, but there's a messages 'screen' that opens for each one that you see in recents.
The new conversation widgets still only shows the person. No message or anything. It does launch either messages or whatever bubble.
There's still a pill on the top of the screen when it's locked. Looks like the navigation pill. It started for me on DP3.
That's all I've seen so far. No crashes. Root works but safety net fails, Viper4Android works, GPay works.
Go get it!
Beta 1 works well so far. There were some minor issues that disappeared, so not even sure if it was the Beta causing it.
Magisk/root works
EdExposed doesn't work yet -- or at least, I couldn't get it to work
So far it's been perfect. No issues whatsoever. Been using it since yesterday when it released. I did perform a factory reset as always. It's really nice I think.
gettinwicked said:
I cleaned flashed to it from DP3 yesterday. Loving it so far! And I wasn't sure about some of the UI changes from the leaked photos.
The bugs I'm getting are:
Bubbles work, but there's a messages 'screen' that opens for each one that you see in recents.
The new conversation widgets still only shows the person. No message or anything. It does launch either messages or whatever bubble.
There's still a pill on the top of the screen when it's locked. Looks like the navigation pill. It started for me on DP3.
That's all I've seen so far. No crashes. Root works but safety net fails, Viper4Android works, GPay works.
Go get it!
Click to expand...
Click to collapse
I've had the same issue (having the pill on the lock screen) since android 11... Otherwise, seems to be relatively usable
Anyone able to get safetynet passing?
emkay5775 said:
I've had the same issue (having the pill on the lock screen) since android 11... Otherwise, seems to be relatively usable
Click to expand...
Click to collapse
With A11? Weird! It only started doing it for me on DP3. I even reset my phone on it to try to fix that and a couple other issues. Clean flashed into beta 1 and it's still there...
Go for it. But be sure about how you follow the installation instructions. Don't forget, the Android 12 beta is still a beta release with some known issues and can brick your device. Be cautious.
sw6n21 said:
Anyone able to get safetynet passing?
Click to expand...
Click to collapse
As far as Google pay working? It works for me
I'm keen to install but does anybody know if Barclays and Natwest apps work with 12 Beta?
StrangerWeather said:
I'm keen to install but does anybody know if Barclays and Natwest apps work with 12 Beta?
Click to expand...
Click to collapse
Replying to my own question: yes, they work.
is there anyway to swap backbutton? tried magisk modules that worked with android 11. but bootloops
I'm currently using beta, some bug available, it's ok for me using for daily driver. I don't care bug
I'm currently using beta, some bug available, it's ok for me using for daily driver. I don't care bug
Well, just flashed Android 12 beta today and I'm love it so far. I'm really like the Samsung style AOD clock.
I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?
I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?
Chris PL said:
I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?
Click to expand...
Click to collapse
You need to unlock it and flash again.