残页

Possibly you can try adb... Power off your phone, connect your phone to a PC (which has installed ADB), execute this cmd command: ``` adb logcat > boot.log ``` then...

Okay, found the crash: ``` 01-17 19:29:20.285 1668 1668 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 01-17 19:29:20.285...

Try this build? https://github.com/canyie/Magisk/actions/runs/3950168775

Try this? https://github.com/canyie/Magisk/actions/runs/3955118267

The Zygisk fix is just a simple workaround for now so it won't be published soon... I'm still thinking how to properly fix it... Maybe a huge code refactor... >...

Did you move `/vendor/etc/hosts` to `/system/etc/hosts`? Magisk seems working well, maybe you can file a issue on Adaway that Adaway didn't detect `/vendor/etc/hosts`

It looks like the problematic logic does not exist before commit 4e14dab60ab2cc3c6ff72e268038b5ad914e3cfd, so this is actually a regression

Please upload a log saved from Magisk App and a bugreport file https://developer.android.com/studio/debug/bug-report

Hmm, nothing about Magisk can be found in your log, it behaves like boot is not patched. And I found something interesting, someone successfully rooted a Pixel 6 by patching...

I can confirm the same issue also happens on Doogee T10 and Teclast P40HD which use Unisoc T606/616 instead of MTK SoCs 🤔