-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KernelSU Not Granting Full Root Privileges on Samsung M14 (One UI 6.1 - Android 14 June security patch) (GKI Kernel 5.15.123 #2095
Comments
I was able to dump the log files related to this incident using Magisk (from /data/adb/ksu/log: edit : I was not able to find anything important in these logs. Maybe these issues are related to the manager itself? edit 2: even with SE Linux permissive mode, the problem still exists which means this is related to manager or One UI itself : |
Quick update: After wasting over 5-10 hours in the debugging process, I finally managed to identify why this happens and found a workaround to fix the issue. I always thought there was something wrong with my device, but all of my efforts were in vain after I realized the issue is with KernelSU itself. According to the issues created in this repo, I found the exact same issue as mine, stating that this problem started occurring after v0.9.2. So, I downgraded my KSU version to v0.9.2 and tested it again. Voila, it worked! Hope you guys fix this issue ASAP. |
Is your terminal a 32-bit application? |
maybe. btw this issue happened with half of my root related apps, even with the root explorer. Only shizuku and log fox worked in my scene :( |
32 bit apps can't use |
okay, lemme check |
I did everything correctly. But, the problem still exists 😢 |
bootloop with those CI builds |
Even I can't execute 'su' in ADB shell 🥲 |
Your KMI is android13-5.15 while tiann provided android14-5.15. Try this https://github.com/tiann/KernelSU/actions/runs/10977394263?pr=2084 |
Root Explorer downloaded from https://rootexplorer.co/ cannot reproduce your problem |
It booted, but it didn't fix any of my issues. 01. su in any terminal application is always broken : 02. Still 32 bit applications unable to get root access + flashing an upstreamed kernel broke some features in my phone like graphics and battery statistics |
Run |
Mmm. I locked the BL. I can only test this again after 2 months due to my exams. Hope someone will provide the necessary logs reguarding this issue, or don't close this issue as completed :) |
Please check before submitting an issue
Describe the bug
I'm creating this issue after trying everything I can.
Our family recently bought a new phone (Samsung M14 4G - shipped with Android 14), and I noticed it has a GKI kernel (5.15.123)
Since I had never compiled GKI kernels before, I spent three days practicing by compiling the OEM kernel (GKI).
Source : https://github.com/ravindu644/a05s_stock
Today, after managing to configure custom defconfigs and menuconfig, I decided to try KernelSU.
After spending several hours adding and fixing various components, I successfully built a KSU-enabled kernel from the OEM source, and it booted on the first attempt!
The KernelSU Manager also shows the kernel version with the
Working <GKI>
message.However, the problem is that
su
is not functioning properly. KernelSU Manager itself has minimal permissions, similar to ADB. I can only use the KernelSU Manager to perform basic actions like rebooting to download mode, etc.When I grant root permissions to Root Checker, it shows that the device is rooted.
Shizuku also works since it requires minimal permissions.
However, apps that require higher privileges, like Root Explorer, report that my device isn't rooted.
Additionally, in terminal apps, it indicates that root is not functioning.
I thought this might be an issue with my kernel, so I disabled security features like Defex (this phone doesn’t have RKP, KDP, or UH since it lacks Knox).
The issue persists.
I also tried modifying
selinux hooks.c
—no luck.Installed LKM—no luck.
Installed the
boot.img
from the official KSU releases—no luck.I'm not sure what’s going on :(
I've collected some logs from
logcat
since KernelSU Manager provides a log file with 0 bytes.Thank you!
To Reproduce
??
Expected behavior
Normally, any rooting solution should work fine on a security disabled Samsung device.
Screenshots
No response
Logs
Device info
Additional context
No response
The text was updated successfully, but these errors were encountered: