If you have TWRP, you can fix su from recovery’s advanced terminal:
You flash the ZIP, your device reboots, and you open your root-required app, only to be greeted by the dreaded message: "No root access detected." Even more confusingly, the SuperSU app itself might open, yet claim there are "No SU binaries installed." supersu root undetected problem
If Step 3 fails, SELinux is likely blocking. Since you can’t run setenforce 0 without root, do it via: If you have TWRP, you can fix su
You open Root Checker. "Sorry, root access is not properly installed on this device." You open your banking app. "This device is compromised." You open Titanium Backup. "Root access failed." Yet, SuperSU is there, granting permissions, updating binaries, and looking functional. "This device is compromised
Check with: ps | grep daemonsu (via ADB or terminal if you have shell root).
The "SuperSU root undetected problem" refers to an issue where a device's root access, managed by SuperSU (a popular tool for managing root access on Android devices), is not being detected by certain applications or services that require root access. This can be frustrating for users who have successfully rooted their devices and installed SuperSU to manage root permissions. Here are several features or steps that can be considered to address this issue: