The Ultimate Guide to Rooting: Magisk, KernelSU, and SafetyNet

Root access is the equivalent of Administrator privileges on Windows. It allows you to modify system files, remove bloatware, block ads system-wide, and install powerful kernels. In 2026, rooting has evolved beyond simple "SuperSU" zips. We now use systemless root methods like Magisk and KernelSU to maintain the integrity of the system partition and pass safety checks.

The Contenders: Magisk vs. KernelSU vs. APatch

The root landscape is more diverse than ever. Understanding which tool fits your needs is crucial before you start flashing files.

Why Choose Magisk?

Magisk remains the king because of its universality. It works on Android 6.0 all the way up to Android 15. It doesn't require a specific kernel version. If you have an older device or a non-GKI device (like most Samsungs before the S21), Magisk is your only option. Its "Zygisk" feature allows modules to inject code into apps, which is essential for detailed customization.

Why Choose KernelSU?

KernelSU is the future. By operating entirely within the kernel, it is invisible to userspace applications. Banking apps that detect "su" binaries or "magisk" package names simply cannot see KernelSU because it doesn't modify the system partition or the boot ramdisk in a detectable way. However, it requires a device that supports Generic Kernel Images (GKI), which mostly means devices launched with Android 12 or later.

Method 1: Rooting with Magisk (Universal)

This is the standard method for 99% of devices.

Step 1: Obtain Your Stock Boot Image

You need the boot.img file from your current firmware. You can get this by:

• Downloading the "Factory Image" zip for your device and extracting it.
• Using a payload dumper tool if the firmware is a payload.bin file (OnePlus/Xiaomi).

Step 2: Patch the Image

1. Install the Magisk app (APK) on your phone.
2. Copy the boot.img to your phone's storage.
3. Open Magisk > Install > Select and Patch a File.
4. Select your boot.img. Magisk will create a magisk_patched.img in your Downloads folder.
5. Copy this patched file back to your computer.

Step 3: Flash the Patched Image

Reboot your phone to Fastboot mode and run:

fastboot flash boot magisk_patched.img

Reboot your phone. Open the Magisk app. It may ask to complete additional setup (rebooting once more). You are now rooted.

Method 2: Rooting with KernelSU (Advanced)

If you have a modern device (Pixel 6+, Galaxy S23+, etc.) that uses a GKI (Generic Kernel Image), you can use KernelSU for superior stealth.

1. Download the KernelSU Manager app.
2. Download a GKI kernel compatible with your device that has KSU integrated.
3. Flash the kernel via Fastboot:

fastboot flash boot boot-gki-ksu.img

The beauty of KSU is that you grant root access to apps directly in the kernel. Apps that are not granted root cannot even "see" that su exists.

Passing SafetyNet / Play Integrity

Rooting often breaks banking apps (Google Wallet, Netflix, Pokémon GO). To fix this, you need to play a cat-and-mouse game with Google's Play Integrity API. This API checks if your device software is trustworthy. Unlocked bootloaders and root access cause this check to fail.

Understanding the Attestation Levels

There are three levels of integrity checks:

• MEETS_BASIC_INTEGRITY: The environment is not tampered with. Most rooted devices fail this without modules.
• MEETS_DEVICE_INTEGRITY: The software matches a certified Android version. This is what most banking apps require.
• MEETS_STRONG_INTEGRITY: The bootloader is locked and verified by hardware. This is nearly impossible to pass with root.

The Fix: Play Integrity Fix Module

To pass DEVICE_INTEGRITY, you must spoof your device fingerprint to match an older, certified device that didn't support hardware-backed attestation. The "Play Integrity Fix" module automates this.

1. Download the "Play Integrity Fix" module zip (by chiteroman or similar fork).
2. Open Magisk > Modules > Install from Storage.
3. Select the zip file and reboot.

Hiding Root (Zygisk & DenyList)

Even with the integrity fix, apps can detect root by looking for the Magisk app itself or open ports. To hide it:

1. Open Magisk Settings.
2. Tap "Hide the Magisk App" and give it a random name (e.g., "Settings").
3. Enable Zygisk (Zygote injection).
4. Enable Enforce DenyList.
5. Configure DenyList: Check Google Play Services (uncheck everything inside it except `com.google.android.gms` and `com.google.android.gms.unstable`), Google Play Store, and your target banking apps.
6. Clear data for the Play Store and Google Wallet, then reboot.

The Risks: Bricking and Bootloops

Rooting is safer than ever, but things can still go wrong. A "Bootloop" occurs when a bad module or incompatible patch prevents Android from starting. If this happens:

• Safe Mode: Boot into Safe Mode (usually hold Volume Down during the boot animation) to disable all Magisk modules temporarily. Then open Magisk and remove the bad module.
• ADB Wait-For-Device: If you have USB Debugging enabled, you can run adb wait-for-device shell magisk --remove-modules to clear all modules from your computer.
• Reflash Boot Image: If all else fails, reflash the stock boot.img via Fastboot to remove root entirely and restore the system to a bootable state.

Conclusion

Rooting gives you complete control. You can install AdAway for system-wide ad blocking, Viper4Android for superior audio, or countless customization modules. With Magisk and KernelSU, the risks are minimal, and the rewards are massive. Welcome to the true Android experience.

Need to go back? Check our Fastboot Guide to learn how to flash stock firmware.