残页

`FragmentActivity.onCreate()` recreates `ModuleFragment` which creates `ModuleViewModel`. At this time `RootService` is not yet ready, `RootUtils.fs == FileSystems.LOCAL` which have no permission to access `MAGISKTMP`. So `ModuleViewModel` thinks the device is...

~~Another user reports the bootloop also happens while the SAR kernel patch is not applied, probably the kernel patch is not the reason of bootloops. Can you try this build?...

Can you execute this command in a root shell and upload the output? `readlink -f /proc/$(pidof zygote64)/exe`

Upload `/system/etc/init/hw/init.zygote64_32.rc`?

Try to capture a bootlog? Connect your phone to a PC, `adb logcat > boot.log`, start your phone, then upload `boot.log`

Looks like your ROM starts Zygote64 before the actual post-fs-data phase: ``` 01-03 21:14:28.112 0 0 I init : starting service 'exec 15 (/system/bin/vdc --wait cryptfs init_user0)'... 01-03 21:14:28.114 0...

Please follow this to capture kernel log? https://github.com/topjohnwu/Magisk/issues/5607#issuecomment-1072347395 and https://github.com/topjohnwu/Magisk/issues/5607#issuecomment-1072389939

I have tried to patch this image on my side, just noticed the SAR patch is applied to your kernel while your device uses rootfs, not SAR: ``` Loading dtbs...

Well, just noticed your device uses MediaTek Helio P23 (MT6763V), and Oppo F5 Youth uses MT6763T 😄 If this build works, this is the same issue as #5124. [app-debug.zip](https://github.com/topjohnwu/Magisk/files/9417317/app-debug.zip) Found...

Try this build first? https://github.com/topjohnwu/Magisk/files/9417317/app-debug.zip