Rooting Guide

A step-by-step guide to root your Courbet on our custom ROMs.

Disclaimer

Rooting your device and unlocking the bootloader will void your warranty and may carry risks. Proceed at your own risk. We are not responsible for any damage to your device. Always back up your data before proceeding.

Overview

All custom ROMs by melo have KernelSU support built directly into their kernel, which simplifies the rooting process: you only need to install the KernelSU Next manager app. For LineageOS (Omer), KernelSU Next is supported by flashing a custom boot image (KSU-NEXT_boot.img) before installing the manager app.

Step-by-Step Rooting Process

Flash Your Custom ROM

Flash your chosen custom ROM following the standard installation procedure.
Complete the initial setup and boot into the system.

Download the KernelSU Next Manager

All ROMs on this hub use KernelSU Next. Download the manager app from the official source below.

KernelSU Next Manager v1.1.1

Install and Enable Root

Install the downloaded APK file.
Open the KernelSU Next manager app.
The app should automatically detect kernel support and enable root access.
Grant root permissions to apps as needed.

Important Notes

Always back up your data before flashing any ROM.
Root access can void warranties and potentially compromise security.
Keep the manager app updated for optimal compatibility.

Troubleshooting

If root is not detected, ensure you have installed the correct KernelSU Next manager.
Ensure your ROM was downloaded from this Hub, as they are confirmed to have kernel support.
Try rebooting after installing the manager app.
If an installed module that uses WebUI-X doesn't open its interface, try downgrading the KernelSU Next manager app.

*This guide is specifically for MI 11 Lite 4G (Courbet) custom ROMs with built-in GKI kernel support.

APatch Root Guide (Kernel 4.14.356)

Important Warnings Before Starting

Risks: Rooting can brick your device, trip safety features, or cause bootloops. Proceed at your own risk.
Backup: Back up all important data + your original boot.img.
4.14 Kernel Note: Your kernel is supported, but older KernelPatch 0.7.x builds (or slightly older APatch versions) often work more reliably for module loading and stability on 4.14 kernels. Start with the latest, and downgrade if needed.
Prerequisites: Unlocked bootloader, ADB & Fastboot installed on your PC, Stock boot.img matching your current firmware (same build number).

Step 1: Check Kernel Compatibility (Recommended)

Run this command (via Termux or ADB shell — root not always required for basic check):

adb shell "zcat /proc/config.gz | grep CONFIG_KALLSYMS"

You need at least CONFIG_KALLSYMS=y. Ideally CONFIG_KALLSYMS_ALL=y.

Step 2: Extract the Correct boot.img

Download your device's ROM
Extract the boot.img
Copy the boot.img to your phone's internal storage (e.g., Downloads folder).

Step 3: Install APatch Manager

Go to the official GitHub: APatch Releases
Download the latest APatch Manager APK.
Install it (enable "Install from unknown sources" if needed). Do not install from untrusted sources.

Step 4: Patch the boot.img

Open the APatch Manager app.
Tap the Patch button (usually top right) → Select a boot image to patch.
Choose your extracted boot.img.
Set a strong SuperKey (8–63 characters, mix of numbers + letters — no special characters). Save this key securely
Tap Start and wait for patching to complete.
The patched image (e.g., apatch_patched_....img) will be saved (usually in Downloads).

If patching fails on latest version → Try an older APatch release or older KernelPatch tools.

Step 5: Flash the Patched Image

Recommended method (Fastboot):

Copy the patched image to your PC.
Reboot to bootloader:
```
adb reboot bootloader
```
Flash it:
```
fastboot flash boot patched_boot.img
```
(Rename the file to boot.img if needed.)
Reboot:
```
fastboot reboot
```

Step 6: Verify Root

Open Apatch Manager enter your SuperKey.
It should show as installed/active.
Use a root checker app or run su in a terminal.

Post-Installation Tips

Install APModules (Magisk-like) via the manager.
For kernel modules (KPM), explore options in the app.
After OTA updates, you usually need to re-patch and flash the new boot.img.
To unroot: Flash the original stock boot.img via fastboot.

Troubleshooting for 4.14 Kernels

Bootloop → Flash stock boot.img immediately.
Modules not loading → Try older APatch/KernelPatch version.
Patching errors → Ensure exact matching boot.img and strong SuperKey.

Official docs: apatch.dev/install.html

Magisk Alpha Root Guide

Important Notes

Risks: Rooting can cause bootloops. Proceed at your own risk.
Backup: Always back up your original boot.img before proceeding.
Source: Ensure you download Magisk Alpha from their official Telegram channel or trusted sources.

Step 1: Extract the Correct boot.img

Extract the boot.img from the ROM zip you are currently using.
Copy the boot.img to your phone's internal storage (e.g., Downloads folder).

Step 2: Install Magisk Alpha App

Download the latest Magisk Alpha APK from their official Telegram channel.
Install the APK on your device (enable "Install from unknown sources" if needed).

Step 3: Patch the boot.img

Open the Magisk Alpha app.
Tap Install next to Magisk.
Choose Select and Patch a File.
Select the extracted boot.img from your storage.
Wait for the patching process to complete. The patched file will be saved in your Downloads folder (usually named magisk_patched_...img).

Step 4: Flash the Patched Image

Connect your phone to your PC and copy the patched boot image to your computer.
Reboot your device to bootloader (Fastboot mode):
```
adb reboot bootloader
```
Flash the patched boot image:
```
fastboot flash boot magisk_patched_boot.img
```
(Make sure to match the exact filename).
Reboot your device:
```
fastboot reboot
```

Step 5: Verify Root

Open the Magisk Alpha app. It should now show that Magisk is installed.
If prompted with "Requires Additional Setup", proceed and let the device reboot.
Use a root checker app or run su in a terminal to confirm root access.