[FAQ] Magisk common issues

## Magisk stopped working When `su` works, but the Magisk app doesn't, something in `/data/adb` seemingly gets corrupted. `su -c 'rm -r /data/adb/magisk* && reboot'` seems to always fix it (at the expense of resetting Magisk's settings). This is a Magisk bug. Maybe some step is skipped when doing the "additional setup" versus the (unsafe in avbroot setups) direct install option? I'd suggest trying a couple things for troubleshooting: Grab the files from `/data/adb/magisk` and compare the checksums with the files inside Magisk's APK (in `assets/` and `lib/arm64-v8a/`). If they are different, then Magisk's "additional setup" didn't work properly. Deleting that directory, rebooting, and retrying the additional setup should fix it. If that doesn't fix it, try running `su -c 'sqlite /data/adb/magisk.db .dump'`, save the output, delete the file, reboot, set up Magisk's settings again, rerun sqlite, and compare the output. Perhaps there's a database migration that Magisk is meant to do, but doesn't? source: https://github.com/chenxiaolong/avbroot/issues/455#issuecomment-2955973508