We use cookies on our website to provide you with the best possible service and to further improve our website. By clicking the "Accept All" button, you agree to the use of all cookies. You can limit the cookies used by clicking on "Accept selection". Further information and an option to revoke your selection can be found in our privacy policy.
These cookies are necessary for basic functionality. This allows you to register on our website and forum or order products with our online shop.
With these cookies, we collect anonymized usage data for our website. For example, we can see which content is interesting for our visitors and which resolutions are used. We use the information to optimize our website to provide you with the best possible user experience.
show more
If you stubbornly stick with SuperSU (again, not recommended for daily drivers), follow these rules:
-rwsr-sr-x (4755) owned by root:root . If permissions are 644 or 755 without setuid, root fails.
SuperSU walked so Magisk could run. Honor its legacy by letting it go. supersu root undetected problem
Open SuperSU > Settings > Scroll to “Cleanup” > Reinstallation > “Reinstall” (not full unroot). Reboot. This sometimes re-links the binary.
This fixes binary path and permission issues: If you stubbornly stick with SuperSU (again, not
When you encounter an "undetected" problem, it usually means one of three things has happened:
Magisk works systemlessly, passes SafetyNet/Play Integrity (with modules), and never suffers from the “undetected” problem because its su lives in a separate, secure location ( /sbin/.magisk/ ) and is injected into the boot image — not vulnerable to SELinux enforcing or partition overwrites. Honor its legacy by letting it go
In SuperSU app: Settings > Full Unroot. Then reboot, re-flash SuperSU ZIP in TWRP. This often resolves namespace or daemon conflicts.
SuperSU acts as a gatekeeper for root permissions. For it to work, two components must be present and correctly linked:
Deutsch
English
Français
Chinese 中文
Korean