Related
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.
Hi guys,
I have installed Android 10 Beta 1 on my op6, all the sensors stop working after the phone rooted.
I tried uninstall magisk,and all the sensors go back normal after a reboot.
Both magisk V19.4 and V20.0 had been tried.
Any idea?
Thank you very much.
You should reboot twice or a factory reset if the First solution doesnt work.
Q has sensors off feature, it might have been turned on by some mistake,
Go to developer options, quick settings developer tiles, tick "Sensors off" option, you'll see new unremovable tile, change it's status several times & see.
Good luck
Thank you all guys.
I reseted everything in twrp.
Root and sensors are all working now.
Thank you.
For me, also all sensors are not working after updating to Android 10 open beta 1, even without root.
I already tried flashing it again and cleared cache, but it didn't help.
Is there anything else I can try to get sensors working again without resetting everything?
Bleuzen said:
For me, also all sensors are not working after updating to Android 10 open beta 1, even without root.
I already tried flashing it again and cleared cache, but it didn't help.
Is there anything else I can try to get sensors working again without resetting everything?
Click to expand...
Click to collapse
For me, I have to reboot few times ( lost count of how many times I have rebooted ) until the sensor is working again.
It's not permanent fix though, another reboot could make the sensors stop working.
I've another problem that a smiley in the Notification only appears as "?". Is happens also in Chrome with some symbols
I fixed it by uninstalling Magisk via TWRP (there's now an easy guide to install it in Android 10), rebooting to system, check if the sensors are working again, and then reinstalling Magisk through TWRP again. If this happens again just re-do the procedure, an update will probably fix this.
How weird ô.O
Magisk v20, rebooted multiple times, nothing worked :|
I just reboot one more time while reading this post ... it works ...
Martuzki said:
I've another problem that a smiley in the Notification only appears as "?". Is happens also in Chrome with some symbols
Click to expand...
Click to collapse
The fonts problem.
The size of some fonts became 0 byte.
Try to reinstall the fonts or reinstall the rom .
stormPremier said:
How weird ô.O
Magisk v20, rebooted multiple times, nothing worked :|
I just reboot one more time while reading this post ... it works ...
Click to expand...
Click to collapse
It seems that the V20 is not compatible with android 10.
I installed v19.4 instead.
Kluxe Nobody said:
I fixed it by uninstalling Magisk via TWRP (there's now an easy guide to install it in Android 10), rebooting to system, check if the sensors are working again, and then reinstalling Magisk through TWRP again. If this happens again just re-do the procedure, an update will probably fix this.
Click to expand...
Click to collapse
Yes,after uninstall magisk all sensors are working again.
I need both root and sensor. So I try to reset the phone .
For all you people with the sensors issue. Install magisk 20.1 that'll fix this issue
thewhitehathacker said:
For all you people with the sensors issue. Install magisk 20.1 that'll fix this issue
Click to expand...
Click to collapse
Updated but not working here...
marcioafoliveira said:
Updated but not working here...
Click to expand...
Click to collapse
Try installing the rom again and try
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.
Hi,
I bought an X3 pro with a global rom, but as I really need a call recorder I have installed the xiaomi 12.5.1 rom. I'm really not an expert on phones but somehow I managed to do it. Also for whatever reasons I had the magisk manager installed as well which I have never really wanted to use.
I was pretty happy with the phone when on one day (ironically a day after I have just checked if my phone is rooted) my phone said I can't use NFC payments anymore. So I have decided to try some magic and fix the problem myself. Again, I'm not an expert but as far as I understood I have a problem with safety-net which I have managed to solve by installing magisk and setting up modules as I have seen on youtube.
Now my phone passes the safety-net check and my phone in the play app says its certified but I still can't pay with NFC and some of the banking apps are not working anymore which is pretty bad for me.
So the question I have in escence: how can I really restore my phone to the factory default 12.5.1 eu rom? I mean I dont need TWRP or anything unlocked, I'd just like to be a regular joe without superuser rights.
Thanks a lot for your help.
ps: not sure if that matters, but if I hit the update button or I'd like to perform a factory reset on my phone then it boots into TWRP.
Uninstall Magisk or Use Magiskhide also your Banking app hide it on the Magiskhide and playstore,
Just MiFlash stock ROM.
Thanks for responding. I have tried hiding Magisk, but that didnt help me with my banking apps. Then I have uninstalled it which made things even worse cause some other programs started to complain. As the phone was not rooted anymore (I guess) I thought it can't be anything except the unlocked bootloader so I had the genius idea to type something like 'adb oem lock' which immediately bricked my phone saying 'the system is destroyed'.
I was very lucky that I remembered that xiaomi unlocker tool which opened the bootloader and that magically still worked and my phone booted to TWRP. From there I just installed an EU ROM and now everything works perfectly fine.
So overall I spent about 20h with unlocking, intalling a new ROM, rooting etc and then another 10 with reinstalling the original ROM plus reinstalling my apps again! Kudos to me going back to square one