Skip to content

Installation Guide ​

This guide provides comprehensive instructions for installing SukiSU-Ultra on your Android device. Please follow the steps carefully.

Prerequisites ​

Before you begin, ensure you have the following:

Installation Methods ​

There are several ways to install SukiSU-Ultra, depending on your device and preference.

LKM mode installs SukiSU-Ultra as a Loadable Kernel Module. The Manager patches your boot image with a prebuilt module that matches your device’s KMI, so you do not need to build a kernel.

Steps: ​

  1. Install the Manager: Download the latest SukiSU_*.apk from the GitHub releases and install it.
  2. Start the installer: On the home screen, tap the install card (Tap to install).
  3. Choose how to provide the boot image:
    • Direct install (Recommended).
    • Select a file and patch: pick a boot image. The Manager recommends the image of the partition that applies to your device (boot, init_boot or vendor_boot). If you enable Backup as stock image, make sure the image you picked is a stock image.
    • Download a file and patch: enter the URL of a full OTA image or a factory image. The Manager looks for a boot, init_boot or vendor_boot partition inside it.
    • Use local LKM file: use your own module instead of the bundled one. Only .ko files are supported.
  4. Select the KMI: the Manager shows the KMI of your device (KMI version of this device). Pick the matching one if you are asked.
  5. Flash and reboot.

Prebuilt LKM images

Release builds ship prebuilt modules for these KMIs (each for aarch64 and x86_64): android12-5.10, android13-5.10, android13-5.15, android14-5.15, android14-6.1, android15-6.6, android16-6.12 and android17-6.18. See the latest release for the current list.

Jailbreak mode

In Jailbreak mode, flashing a partition on a device with a locked bootloader breaks AVB (Android Verified Boot) and may leave the device unable to boot.

Method 2: Using Pre-built GKI Packages ​

This is the recommended method for devices with Generic Kernel Image (GKI) 2.0, such as many Xiaomi, Redmi, and Samsung models.[1]

Steps: ​

  1. Download GKI Build: Visit our resources section to find the appropriate GKI build for your device’s kernel version. Download the .zip file that includes AnyKernel3 in its name.
  2. Flash via Recovery:
  3. Verify Installation:
File Format Guide

The .zip archive without a suffix is uncompressed. The .gz suffix indicates compression used for specific models.

Method 3: Custom Build for OnePlus Devices ​

For OnePlus devices, you’ll need to create a custom build.

Steps: ​

  1. Gather Device Information: You will need:
    • Your kernel version (e.g., 5.10, 5.15).
    • Your processor’s codename.
    • The branch and configuration files from the OnePlus open-source kernel repository.
  2. Create Custom Build: Use the link in our resources section to generate a custom build with your device’s information.
  3. Flash the Build:

Method 4: Manual Kernel Integration (Advanced) ​

This method is for advanced users who are building a kernel from source.

Integration Scripts: ​

  • Main Branch (LKM):
    bash
    bash
    sh
    curl -LSs "https://raw.githubusercontent.com/SukiSU-Ultra/SukiSU-Ultra/main/kernel/setup.sh" | bash -s main
  • Builtin Branch:
    bash
    bash
    sh
    curl -LSs "https://raw.githubusercontent.com/SukiSU-Ultra/SukiSU-Ultra/main/kernel/setup.sh" | bash -s builtin

Required Kernel Configs

For KPM support, you must enable CONFIG_KPM=y. For non-GKI devices, you also need to enable CONFIG_KALLSYMS=y and CONFIG_KALLSYMS_ALL=y.

Post-Installation ​

Maintaining Root After OTA Updates ​

To keep root access after an Over-the-Air (OTA) update, follow these steps ==before rebooting==.

  1. Flash to Inactive Slot:
  2. LKM mode (recommended): after the OTA has been installed and before you reboot, start the Manager’s installer from Method 1 and choose Install to inactive slot (After OTA).

TIP

For non-GKI devices, the safest method to retain root after an OTA is to use TWRP to flash the kernel again.

Verification Checklist ​

After installation, please verify the following:

Troubleshooting ​

If you encounter any issues:

  1. Double-check the Compatibility Guide.
  2. Visit our GitHub repository for issues and solutions.
  3. Join our Telegram community for live support.

Safety Reminder

⚠️ Always have a backup! Keep a copy of your original boot.img and be prepared to restore your device if something goes wrong.


  1. This method is not suitable for devices from manufacturers that heavily modify the kernel, like Meizu, OnePlus, Realme, and Oppo. ↩︎