A Kernel based root solution for Android
KernelSU now supports installation through kernel modules (LKM) (GKI Only), you can use it with official kernels or third-party kernels; at the same time, the manager has also added installation functionality, you can choose to patch files, install directly, or install after OTA. Regarding the new LKM installation method, there are some tips:
init_boot partition exists, you should choose to patch init_boot; otherwise, patch boot;init_boot partition, you can directly flash back to the stock boot;Have fun!
For a long time, the module functionality of Magisk / KernelSU was limited to executing boot scripts and modifying system files. Now, we are exploring the possibility of endowing modules with the capability to display UI interfaces!
Previously, after installing some modules, users needed to configure them either through the command line or by directly modifying configuration files in specific locations. Clearly, this process was quite inconvenient for users. At times, in order to configure settings, it was even necessary to write a separate app. With the ability for modules to display interfaces, these issues could become a thing of the past.
Moreover, the display interface can be used for more than just configurations. You have the freedom to present anything you'd like to showcase and interact with the user.
The current interface is implemented through WebUI. You can create HTML pages using any web technology and place them in the module's webroot directory. After the module is installed, users can access this page through the KernelSU manager's list of modules. KernelSU also provides a JavaScript library to facilitate interaction with the system.
However, these trials are still in their infancy, and the jsapi is not yet stable. We welcome your feedback!
Changelog:
For a long time, the module functionality of Magisk / KernelSU was limited to executing boot scripts and modifying system files. Now, we are exploring the possibility of endowing modules with the capability to display UI interfaces!
Previously, after installing some modules, users needed to configure them either through the command line or by directly modifying configuration files in specific locations. Clearly, this process was quite inconvenient for users. At times, in order to configure settings, it was even necessary to write a separate app. With the ability for modules to display interfaces, these issues could become a thing of the past.
Moreover, the display interface can be used for more than just configurations. You have the freedom to present anything you'd like to showcase and interact with the user.
The current interface is implemented through WebUI. You can create HTML pages using any web technology and place them in the module's webroot directory. After the module is installed, users can access this page through the KernelSU manager's list of modules. KernelSU also provides a JavaScript library to facilitate interaction with the system.
However, these trials are still in their infancy, and the jsapi is not yet stable. We welcome your feedback!
Changelog:
Fix memory leak
module.prop causing module directory confusion./debug_ramdisk as temporary directory.We’re excited to report that we’ve delivered on the App Profile feature we promised 5 months ago! In this release, we have added an important feature to App Profile: Templates. You can create templates by yourself, import templates created by others, or directly use online templates. Templates can be directly applied to App Profile, without having to manually set each configuration! Therefore, even if you don’t understand the complex concepts in App Profile, you can easily restrict ROOT permissions through templates. In addition, welcome to contribute rules to online templates!
Changelog: