5 ms·
KernelSU: A kernel-based root solution for Android
- ManuLinares 4y ago"And also, please check your stock boot.img's format, you should use the right format, such as lz4、gz." How do I find out my boot.img format? I have a "Google Pixel 6a"
- nubinetwork 4y agoWhy, just use lineageOS.
- c4mpute 4y agoLineageOS hasn't supported root for several major releases. The last official su addon is for version 16.0, https://download.lineageos.org/extras https://download.lineageos.org/extras , we are now at 19.1 or 20.0. Magisk used to work, but is getting more and more of a hassle to install and update. I fear root is becoming rarer and harder, even on alternative Android distributions.
- nubinetwork 4y agoSorry I didn't see this reply... I'm on 18.1 at the moment, but I'm pretty sure I had su installed at one point. I reflashed my phone a few months ago because my nand/SD are starting to go... Time to ditch the S5 and buy a S23 :)
- RealStickman_ 4y agoThis has nothing to do with LineageOS.
- nubinetwork 4y agoYou're right, it doesn't. But why go through the hassle of hacking the kernel when you can replace the whole OS with something better?
- RealStickman_ 4y agoBecause, last I checked, LineageOS doesn't expose root privileges to the user.
- nubinetwork 4y agoThe install goes something like this... - install new recovery and reboot - install new OS image - install google apps - install su package - reboot and wait half an hour because androids first boot always takes forever :) Installing su is often skipped because its not recommended.
- RealStickman_ 4y agoThe latest officially avaiable su package is for 16.0. My phone's on 18.1 and the latest version is 20. If you want SU on a supported LineageOS, you have to use Magisk or potentially this project.
- lauriewired 4y agoKernelSU is pretty interesting in certain circumstances compared to say, Magisk, which is a systemless root. KernelSU cannot be prevented by SELinux—the kernel can even disable SELinux if it wants to. It's quite useful for gaining root on "weird" and or/old android devices such as lesser-known smartwatches, often that have no support for Magisk at all. In terms of bypassing SafetyNet, both KernelSU and Magisk have their own strengths and limitations. For those utilizing an Android smartphone in a conventional manner, Magisk may be the preferred choice due to its extensive module support and strong community support.
- weishu 4y agoKernelSU need to be integrated to kernel source and compile kernel, for "wired" and/or old android devices, maybe it is difficult to do that.
- worldsavior 4y agoNice, but using root generally is very insecure. The whole concept of superuser is broken and bad. Such privileges shouldn't be given to any user.
- alex7734 4y agoBypassing "security" when you as the owner of the device want to is the whole point of root.
- worldsavior 4y agoThis project allows root by default, like it's part of the user experience, which is bad for security.
- summm 4y agoIt does not grant root by default, quote: "Whitelist access control Only App that is granted root permission can access `su`, other apps cannot perceive su."
- worldsavior 4y agoIn this context I meant that it allows root where Android never allows.
- summm 4y agoBut that's the whole point? That you can user your own device as a general-purpose computing device, not only as a media-consumption device limited by arbitrary restrictions the vendor of the device can pose on you?
- worldsavior 4y agoThis kernel is for day to day use. Using insecure features such as root, can potentially cause harm. Do whatever you want, just pointed a fact.
- yellowapple 4y agoGPLv3 licensed, despite almost certainly being a derivative work of Linux, which is GPLv2 licensed (with no "or later" provision). Now, I ain't no lawyer or nothin', but I reckon that's a legal paddlin'.
- c4mpute 4y agoMost probably not. Kernel devs are tame even with closed-source device and software vendors pirating the Linux kernel. I doubt any kernel copyright holder will bat an eye over GPLv3 vs. GPLv2. Not to mention the very relevant question of "is it really a derivative work?", which very much depends on the depth and complexity of integration, provided interfaces, GPLONLY symbols and other minutiae.
- yellowapple 4y ago> Kernel devs are tame even with closed-source device and software vendors pirating the Linux kernel. It's more complicated than that: https://lwn.net/Articles/698452/ https://lwn.net/Articles/698452/ > I doubt any kernel copyright holder will bat an eye over GPLv3 vs. GPLv2. Probably not, but why risk it? The only meaningful difference between the two is the anti-TiVoization clause, and considering how thoroughly Android is already TiVoized, that seems pretty pointless anyway. > Not to mention the very relevant question of "is it really a derivative work?", which very much depends on the depth and complexity of integration, provided interfaces, GPLONLY symbols and other minutiae. It's a kernel module, the build process for which entailing pulling the KernelSU code into a cloned Linux repo. It's pretty unambiguously a derivative work.