Closed yesnomaybeyes closed 5 years ago
You are nuking data encryption by using the no-opt-verity zip. It is nothing that should be asked me for, please ask the dev created the zip :)
Hi @topjohnwu,
I get the same issue if I don't flash the no-opt-verify zip, i.e. just Magisk, I also tried again with a different kernel + Magisk (in that order), same results. :(
I tried from the start, locked bootloader. Unlocked it again, made sure I don't mount /system, formatted data, flashed Magisk, rebooted (boot took 5 minutes), completed initial setup (added Google account, set passcode, tried to sign into Samsung account it said "Processing failed"), and now I can "unlock" the phone by just swiping up and the passcode setting is broken.
To clarify, only the initial boot takes 5 mins
which causes lockscrem error and twrp, has nothing with the magisk, install the official rom puts only the twrp is going to continue with error in the lockscreen. sorry the english google translate
I experienced the same problem with my realme 5i smartphone, I tried to install the latest Magisk via the OrangeFox recovery because I had never rooted my smartphone before. but I have installed pixel 5 archipelago project. In this case, after installing magisk and successfully entering the lockscreen, here the problem occurs because I can't enter the lockscreen PIN and can't do anything, I can't even turn off my phone. But here I found a solution, namely using a google account and trying to wipe data via the Google Play application, namely find my devices and then delete it there and it worked for me
Hi!
This is likely not Magisk's fault but seems to be triggered by its installation, possibly MagiskHide needs adjusting but I've searched everywhere and I seem to be an outlier!
I am using Magisk 19. Root works and SN passes just... kinda would like a lockscreen :D
The TL;DR is if I install Magisk, the screen lock password fails to encrypt (based on the logs I read, provided below), but the db gets populated anyway, in a broken state(?), and after rebooting the screenlock activity(?) continually goes blank and opens again (crashlooping I guess), eventually causing a reboot. Trying to boot again yields the same sadly, the issue is "fixed" by using TWRP to delete
/data/system/locksettings.db*
On my Note9, I do the usual:
The boot takes about 4-5 minutes.
Once the boot is done I go through the steps of:
adb shell
,su
, andlogcat
https://files.zora.ws/log.txt (7MB logcat, I wasn't sure how to minify it or if I should, sorry...)
Output of
select * from locksetting
on the locksetting.db retrieved from TWRP:From the logs it appears some Samsung service doesn't want the key or whatever made.
Sorry if this isn't Magisk related, but I'm at my wits end! Would be great if you have any ideas at all.
Let me know if you need further details.