Hello friends

[jadersilva1]

Device information

• Device: Samsung Galaxy A16 (SM-A165M)
• Android version: 16
• One UI version: [add exact version]
• Security patch: 2026-08-05
• Build / firmware: A165MUBSBDZH6
• Kernel: 6.12.38-android16-5-abA165MUBSBDZH6-4k
• DFRoot version: 4.7
• Bootloader: locked / OEM unlocking not available on this device

Issue

DFRoot reaches the === init === stage, but Triggering hook... times out:

=== init ===
Triggering hook... timeout: ERROR - check logcat & dmesg

The tool then completes the cleanup stage and restores the modified files.

Logs

I can provide logcat and dmesg captured immediately after the failure. Please let me know which sections or filters you need.

Question

Is DFRoot 4.7 expected to support this exact firmware/build? If not, could you confirm whether a newer version or a different supported build is required?

[braydon9-svg]

Working: Samsung SM-A075F, Android 16 / One UI 8.5 — ksud error fixed by reinstalling original KernelSU APK

Reporting a working DFRoot setup:

Device: Samsung SM-A075F
Android: 16
One UI: 8.5
Kernel: 6.12.38-android16-5-abA075FXXS7CZI1-4k
Security patch: 5 August 2026
DFRoot version: DFRoot_4.5.apk is the only one i can get to work with
KernelSU version/fork: KernelSU_samsung-v2.2_32687-release.apk

DFRoot originally worked, but later started failing with a
ksud non-zero exit error.

I fixed it by uninstalling KernelSU and reinstalling the
original KernelSU APK I downloaded when root first worked.

Root now works again, and I tested it using the su command
in Termux.

I can't confirm whether the problem was the KernelSU version
or the previous installation's app state.

We have the same kernel type so try thoes kernalsu and dfroot versions

[braydon9-svg]

Let me know if it works for you

[jadersilva1]

Hi, I tried those versions you recommended, and I'm still getting the same error. I hope there's a solution or that the developer can help me.

[braydon9-svg]

That sucks, try making sure ur log buffer size is set to 4M or higher in developer options
Use termux or wichever you use

/system/bin/logcat -b all -d -v threadtime -f /sdcard/Download/dfroot-logcat.txt you will find the log in downloads folder
My Files → Internal storage → Download → dfroot-logcat.txt
Then youll probally want to use RAR file compressin from google play to upload it cause i cant upload any bigger than 25mb lol my log is 70mb
If you dont know how to get the logs developer is probally gonna want it

[braydon9-svg]

Or u can just get termux download a proot distrobution then type

proot-distro login debian

It will drop you in a root shell