Repository navigation
Replies: 20 comments 17 replies
|
this is samsung A14 phone show success but ksud not load kernelsu manager still show jailbreak and phone permessive |
|
Update for SM-A146U (Galaxy A14 5G, MT6833, In addition to the
Two notes from debugging this:
How to build (DDK — override the two generated files via bind-mount, then build as usual): sed -i 's@^#define CONFIG_SHADOW_CALL_STACK 1@/* disabled: a14xm SCS=n */@' $KDIR/include/generated/autoconf.h
sed -i 's@^CONFIG_SHADOW_CALL_STACK=y$@# disabled for a14xm@' $KDIR/include/config/auto.conf
sed -i 's@^#define CONFIG_CFI_CLANG 1@/* disabled: a14xm CFI=n */@' $KDIR/include/generated/autoconf.h
sed -i 's@^CONFIG_CFI_CLANG=y$@# disabled for a14xm@' $KDIR/include/config/auto.conf(keep Pre-flash sanity checks (all green on our build):
Status: rebuilt a new ksud ( TL;DR — on this device the module must be built with SCS=n + CFI=n, on top of the KDP/DEFEX switches. Quick note on the
|
|
Full write-up is above; TL;DR: this device needs SCS=n + CFI=n build overrides, and the rebuilt ksud is attached (ksud-a14xm.zip). @PixelFuck — if you can give it a retry on your A14, that'd help a lot. @diabl0w — a look whenever you get a chance. Thanks! |
|
@diabl0w regarding to this #65 (comment) I finally found out why it's not working it's kinda dumb and funny. It happens to be my ksud's hash and manager are not the same. It's a noob mistake I really forgot about these hashes and I created a huge fuss about this issue. Anyways it's working now, I just have to create a keystore in my github to prevent hash mismatches again. |
07-10-2026_22-37-36.mp4 |
|
=== setup === === exploit (patching files) === === init === === cleanup === patched 16 bytes to /system/lib64/libc++.so+0xb30a0 |
|
Samsung Galaxy A05 SM-A055F Android 15 DFRoot: But KernelSU Manager still shows "Not installed". What KernelSU changes/build are required for this device? |
|
Version No. RMX3867_16.0.5.702(EX01) Baseband version M_V3_P10,M_V3_P10 Kernel version 6.6.89-android15-8-o-g59160d8212a5- 4k realme Ul Version 7.0 Hardware version RMX3867_11 Android version 16 Android security update 1 June 2026. Didn't work on it , with Kernelsu next . When I ran it my device freezed for like 5 mins then auto restarted , i thought device got fucked . Any solution? |
|
I was able to exploit my Galaxy S23 after many attempts, my phone restarts and then shows a rooted phone, but when entering the manager, jailbreak appears but without the error. |
|
Dear Devloper Bro, |
|
S731U === XFRM setup === === exploit === === cleanup ===
=== teardown === [!] DFRoot failed to acquire root [!] Failed |
|
Hello DFRoot developers! I urgently need help fixing a problem with DFRoot. Device information:
Problem: Whenever I press "LAUNCH ROOT", DFRoot displays "SUCCESS", but my phone reboots normally. After rebooting, KernelSU still shows "Not installed", and root access is not available. The Auto Soft Reboot option is already disabled. Could you please investigate this issue and provide a fix or specific instructions for my device? Please help me get DFRoot working on my device. Thank you! |
|
A065f kernel 6.6.82 android 16 not working I used kernelsu v1.0 samsung dfroot says rooted but manager shows not installed if I use other manager version device keeps rebooting even with disable module and soft reboot on/off I used one manager v2.0.0 shows gki mode but no superuser tab works VID_20261105_183151_663.mp4 |
|
I have galaxy s23, Oneui 9, Android 17, kernel 5.15.197, Dirtyfrag app (DFRoot fork) sais Rooted, KernelSU said Working Jailbreak mode but I don't have root, the Kernel su build is https://github.com/diabl0w/KernelSU/ |
|
Data point that answers the original question for a MediaTek/vivo device, since most reports here are Samsung: DirtyFrag works, official KernelSU does not, KernelSU-Next does. Device: iQOO Neo7 DirtyFrag 1.17 (CVE-2026-43284) completes on every run — all patches applied and re-read verified, log ends with The failure is entirely on the manager side, exactly as described in the opening post:
App-level For anyone rebuilding the LKM for this target, the kernel config is Two runs, no panic, no reboot, SELinux stayed Enforcing throughout. Full device report with logs: fynks/awesome-temporary-root#12 |
|
[SUCCESS] Temporary root on Galaxy A15 5G SM-S156V (Straight Talk) — Android 16, DFRoot + KernelSU Finally managed to get KernelSU working on my bootloader-locked Galaxy A15 5G (SM-S156V) running Android 16, using DFRoot 4.7 and a patched Samsung KernelSU v2.2 build. Device info:
At first, everything looked like it was working. DFRoot reported "ksud start: SUCCESS" and KernelSU showed "Working [Jailbreak mode]". The problem was that the Superuser tab just sat there saying "Refreshing…" forever, and apps weren't actually getting root access. After digging into it, I found two separate issues:
Both issues have now been fixed in the patched build. I rebuilt KernelSU, tested it on my phone, and can confirm that the Superuser tab works and apps can actually request and receive root access. There's already a PR with the changes here: Just to be clear, this is temporary root, not a bootloader unlock. I've only tested it on my own SM-S156V, so I can't say whether it'll work on other Samsung models or firmware versions. I also haven't verified what effect, if any, this has on Knox. Big thanks to diabl0w and everyone behind KernelSU and DFRoot. I was stuck on the "Refreshing…" issue for a while, so I figured I'd post this in case anyone else runs into the same thing. |


















Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This space is dedicated to discussing KernelSU (and derivative) based issues. How do you know if its KernelSU specific issue? In 99% of cases, if DFRoot says "SUCCESS" or "FAILED: ksud exited with error" and you get permissive Selinux but don't have root, then you should be here and not in the Issues section of DFRoot, as DFRoot did its job as intended at that point.
As of v3.0 DFRoot is intentionally independent of KernelSU. Different manufacturers have different kernel exploit mitigations that may require specific changes to official KernelSU for it to work on that device. Aside from starting up the su daemon, DFRoot has zero involvement in that process and zero capability to do anything about that. Those things can be discussed here
All reactions