eced8bae82
* Fix typos in README.md * Fix various translation error in README-en.md * Update links in README-en.md
4.8 KiB
4.8 KiB
SukiSU
Enlish | 简体中文
Android device root solution based on KernelSU
Experimental! Use at your own risk! This solution is based on KernelSU and is experimental!
This is an unofficial fork. All rights are reserved to @tiann
- Fully adapted for non-GKI devices (susfs-dev and unsusfs-patched dev branches only)
How to add
Use the susfs-stable or susfs-dev branch (integrated susfs with support for non-GKI devices)
curl -LSs "https://raw.githubusercontent.com/ShirkNeko/SukiSU-Ultra/main/kernel/setup.sh" | bash -s susfs-dev
Use the main branch
curl -LSs "https://raw.githubusercontent.com/ShirkNeko/KernelSU/main/kernel/setup.sh" | bash -s main
Use dev branch（With support for non-GKI devices）
curl -LSs "https://raw.githubusercontent.com/ShirkNeko/KernelSU/main/kernel/setup.sh" | bash -s dev
How to use integrated susfs
- Use the susfs-dev branch directly without any patching
More links
Projects compiled based on Sukisu and susfs
Hook method
- This method references the hook method from (https://github.com/rsuntk/KernelSU)
- KPROBES hook:
- This method only supports GKI (5.10 - 6.x) kernels, and all non-GKI kernels must use manual hooks.
- For Loadable Kernel Modules (LKM)
- Default hooking method for GKI kernels
- Requires
CONFIG_KPROBES=y.
- Manual hooks:
- For GKI (5.10 - 6.x) kernels, add
CONFIG_KSU_MANUAL_HOOK=yto the kernel defconfig and make sure to protect KernelSU hooks by using#ifdef CONFIG_KSU_MANUAL_HOOKinstead of#ifdef CONFIG_KSU. - Standard KernelSU hooks: https://kernelsu.org/guide/how-to-integrate-for-non-gki.html#manually-modify-the-kernel-source
- backslashxx syscall hooks: https://github.com/backslashxx/KernelSU/issues/5
- Some non-GKI devices that manually integrate KPROBES do not require the manual VFS hook
new_hook.patchpatch
- For GKI (5.10 - 6.x) kernels, add
Usage
[GKI]
- such as Xiaomi, Redmi, Samsung, and other devices (does not include manufacturers that modified the kernel like Meizu, OnePlus, RealMe, and OPPO)
- Use the prebuilt GKI kernel, the ones with their name ending with AnyKernel3, mentioned in the 'More Links' section, and then flash it with recoveries like TWRP
- Generally, packages with a plain .zip suffix are universal. However, if your device has a MediaTek processor, you should use the ones with .gz suffix, and packages with .lz4 suffix are dedicated to Google devices.
[OnePlus]
- Use the link mentioned in the 'More Links' section to create a customized build with your device information, and then flash the zip file with the AnyKernel3 suffix. Note: You only need to fill in the first two parts of kernel versions, such as 5.10, 5.15, 6.1, or 6.6.
- Please search for the processor codename by yourself, usually it is all English without numbers.
- You can find the branch and configuration files from the OnePlus open-source kernel repository.
Features
- Kernel-based
suand root access management. - Not based on OverlayFS module system, but based on Magic Mount from 5ec1cff
- App Profile: Lock root privileges in a cage.
- Bringing back non-GKI/GKI 1.0 support
- More customization
License
- The file in the “kernel” directory is under GPL-2.0-only license.
- All other parts except the “kernel” directory are under GPL-3.0 or later license.
Sponsorship list
- Ktouls Thanks so much for bringing me support
- zaoqi123 It's not a bad idea to buy me a milk tea
- wswzgdg Many thanks for supporting this project
- yspbwx2010 Many thanks
If the above list does not have your name, I will update it as soon as possible, and thanks again for your support!
Contributions
- KernelSU: original project
- MKSU: Used project
- RKSU: Reintroduced the support of non-GKI devices using the kernel of this project
- susfs：Used susfs file system
- KernelSU: KernelSU conceptualization
- Magisk: Powerful root utility
- genuine: APK v2 Signature Verification
- Diamorphine: Some rootkit utilities.