Here is how to resolve the "a su binary not from magisk has been detected" error, from simplest to most thorough.
option. This should remove its binaries and allow Magisk to take over cleanly. 3. Toggle System Root (For Custom ROMs) On some ROMs, you can disable the built-in root: Developer Options Root Access and set it to 4. Reinstall Magisk a su binary not from magisk has been detected
Sometimes, the binary itself is fine, but SELinux (Security-Enhanced Linux) labels are incorrect, or the Magisk daemon ( magiskd ) fails to respond properly. When an app queries for root, the system falls back to scanning paths and finds an older binary. Here is how to resolve the "a su