FolkPatch

English

简体中文

English

简体中文

Appearance

FAQ

About 838 wordsAbout 3 min

2026-02-01

Root Path & Authorization Quick Look

User

Why did my Root path become /system/bin/kp instead of su?

This is usually caused by conflicts with other ROOT solutions (KSU, Magisk) in the environment. FolkPatch automatically used an alternative path.

User

How do I change it back to su?

Clean up conflicting files in /data/adb, restart, then manually reset the su path in settings.

🎯 This document summarizes common issues and solutions encountered when using the FolkPatch Superuser (Root) feature.

1. Why is my Root path /system/bin/kp?

Some devices find that after patching and installation, the Root path defaults to /system/bin/kp instead of the traditional /system/bin/su.

Cause of the Issue

This usually happens because there is a conflict with another ROOT solution in your device environment. When FolkPatch detects residual or active environments like KSU or Magisk, it may use an alternative path to avoid direct conflicts.

Impact

Since the vast majority of Android apps only look for the /system/bin/su path to obtain Root privileges, most apps will report "Root not obtained". Currently, only a few apps (such as MT Manager) support manual configuration or automatic compatibility with the /system/bin/kp path.

2. How to Troubleshoot and Resolve Environment Conflicts?

If you want to restore the Root path to the standard su, please follow these steps to troubleshoot and clean up:

  1. Check for Conflicting Files Use a file manager (such as MT Manager) to go to the /data/adb directory and check for the following files or folders:

    /data/adb

    ksud# KSU daemon (conflict)

    susfs4ksu# KSU SusFS directory (conflict)

    magisk# Magisk-related (conflict)

  2. Environment Cleanup

    • If you find the above files, make sure you have uninstalled other Root management apps
    • Delete residual files related to conflicting solutions in the /data/adb directory
    • Restart the device

  3. Manually Reset su Path After the environment is cleaned up, you need to manually change the path back:

    • Open the FolkPatch app
    • Go to Settings -> General
    • Find the Reset su Path option
    • Manually change the path back to su
    • Save and restart the app (or device) for the changes to take effect

提示

Maintaining a clean system environment is a prerequisite for the stable operation of FolkPatch. It is recommended to completely clear other Root solutions before installing FolkPatch.

3. Normal su Path But Cannot Authorize Superuser

If your Root path shows as normal /system/bin/su, but apps still cannot obtain Root authorization, it may be caused by the following reasons:

Possible Causes and Solutions

Cause 1: Kernel Module Conflict

Certain kernel modules may be incompatible with your device, causing authorization mechanism issues. The most common case is installing Nohello KPM or other modules that don't适配 your device model.

Solution:

  1. Go to the Modules page in FolkPatch Manager
  2. Disable or uninstall recently installed kernel modules (KPM)
  3. Restart the device and test the authorization function again
  4. If the problem is resolved, it means the module is incompatible; avoid using it

注意

Modules like Nohello are developed for specific device models and may have compatibility issues on different devices. Please confirm whether the module is compatible with your device before installation.

Cause 2: System Module Conflict

Some system modules may affect FolkPatch's authorization process, causing authorization requests to fail to pop up or be rejected.

Solution:

  1. Go to the Modules page in FolkPatch Manager
  2. Disable system modules (non-KPM modules) one by one
  3. After disabling each module, restart the device and test authorization
  4. Once the problematic module is found, you can choose to uninstall it or contact the module developer for a fix

Troubleshooting Tip

If you're unsure which module is causing the problem, you can disable all modules first, then enable them one by one to locate the problematic module.

Cause 3: KernelPatch Version Incompatibility

The KernelPatch version you are using may have compatibility issues with your current device or system, causing the authorization mechanism to fail.

Solution:

  1. Use the FolkTool official tool to switch to another KernelPatch version
  2. Select a known stable version and re-flash
  3. After flashing, disable auto-update in FolkPatch Manager to avoid encountering compatibility issues again

Recommended Practice

  • When encountering version compatibility issues, prioritize using FolkTool for version switching
  • FolkTool supports selectable KernelPatch versions for quick downgrade to stable versions
  • After stabilization, it's recommended to disable auto-update in FolkPatch - General - Disable KernelPatch Update

Quick Diagnosis Flow

If you encounter authorization issues, it's recommended to troubleshoot in the following order:

  1. Check Path → Confirm it's /system/bin/su not /system/bin/kp
  2. Check KPMs → Disable all kernel modules and restart to test
  3. Check System Modules → Disable system modules one by one for troubleshooting
  4. Check Version → Use FolkTool to switch to a stable version

Copyright Ownership:FolkPatch Team

License under:Attribution 4.0 International (CC-BY-4.0)