Modern operating system Android provides users with enormous opportunities, but with each new version Google developers are increasingly tightening the security screws, limiting access to system files. For many enthusiasts and advanced users, obtaining (superuser rights) on root access (superuser rights) to Android 11 remains a critical step to complete control over the device. This allows you to remove system garbage, install powerful modifications and fine-tune the operation of the kernel.
However, the rooting process in 2026 is radically different from what we saw a couple of years ago. Old methods using KingRoot or OneClickRoot no longer work and can be dangerous. Now the de facto standard is Magisk and its forks, which allow you to gain rights, modify the system without changing the system partition (systemless) and bypass security checks. You will have to deal with unlocking the bootloader, working with ADB i Fastboot, as well as the risk of losing the warranty.
Before you begin, it is important to realize that any intervention in the smartphone’s software code is a risk. You can turn your gadget into a brick if you don't follow the instructions. In this article we will analyze in detail all the stages: from checking compatibility to installing a rights manager. We will also discuss how to hide the fact of rooting from banking applications, which has become especially important with the introduction of strict security protocols.
Preparing the device and the necessary tools
The first step is thorough preparation. You need to create a complete backup of all important data, since unlocking the bootloader, which is a prerequisite for obtaining superuser rights, is completely clears the device memory. All photos, contacts and applications will be deleted. Make sure that the battery charge is at least 60% so that the phone does not turn off at the most inopportune moment.
You will need a computer (preferably with an operating system Windowsas drivers are easier to install there) and a high-quality USB cable. You must install Platform Tools (ADB and Fastboot) on your PC. It is also critically important to download the original firmware (Stock ROM) specifically for your model and version of Android. The firmware must match the build number, otherwise restoring the boot image boot.img will be impossible.
⚠️ Attention: Unlocking the bootloader on Samsung smartphones often triggers the flag Knox, which irreversibly disables Samsung Pay, Secure Folder and some banking functions, even if you will return everything back.
For work you will need the following components:
- 📱 Smartphone with USB debugging enabled (in the developer menu).
- 💻 PC with ADB and Fastboot drivers installed.
- 💾 Firmware file (Stock ROM) corresponding to the current OS version.
- 📲 APK file of the latest version Magisk.
Bootloader Unlock
Without an unlocked bootloader (Bootloader), not a single method of obtaining superuser rights will work. Manufacturers block it to prevent modified software from running. The procedure varies greatly depending on the brand. On devices Xiaomi you must wait 7 days (168 hours) after linking your account in the application Mi Unlock. On Motorola i OnePlus the unlock code can be obtained on the manufacturer's official website.
The process usually looks like this: you put the phone in Fastboot mode (usually by holding down the volume down button when turning it on) and connect it to the PC. An unlock request is sent via the command line. After confirmation (often with the volume buttons on the phone itself), the device will reboot and perform a factory reset.
☑️ Check before unlocking
It is important to understand that after this procedure some security functions will no longer work, for example, payment via NFC in some banks. You may also receive a warning when the system boots that the bootloader is unlocked. This is normal for a rooted device, but for ordinary users it may come as a surprise.
Installing and setting up Magisk Manager
The most effective tool for Android 11 and newer is Magisk. It injects itself into the boot partition, leaving the system partition untouched. This allows you to pass system integrity checks. First, install the Magisk APK file as a regular application. Without opening it, find the file boot.img from your stock firmware on your computer.
If you have a phone Samsung, you will need the file AP.tar or boot.imgextracted from the firmware archive. For other brands, it is enough to simply copy boot.img to the smartphone’s memory. Open the Magisk app, click "Install" next to the Magisk version and select "Select and patch file." Specify the path to your boot.img.
What to do if Magisk does not see boot.img?
Make sure that the file has the .img extension and is not damaged. On some devices (for example, Samsung) you need to patch the entire AP firmware file, and not just boot.img. Also check that the application has permission to access files.
After the patching process is completed, a file with a name like magisk_patched_xxxxx.imgwill appear in the Download folder. Copy it back to your computer. This file now contains a modified bootloader with superuser rights. This is what we will write to the phone’s memory at the next stage.
Firmware of the modified bootloader via Fastboot
Now it’s time to write the patched image to the device’s memory. Switch your smartphone to Fastboot (or Download Mode for Samsung, although Odin is used there). Connect your phone to the PC and open the command line in the folder with Platform Tools.
For most devices (Xiaomi, Pixel, OnePlus, Motorola) the command will look like this:
fastboot flash boot magisk_patched.imgIf you have a device with dynamic partitions (many modern smartphones), the command may differ:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
⚠️ Attention: Make sure that you are flashing exactly
boot, and notrecoveryorsystem. Writing the boot image to the recovery partition will make it impossible to boot the system.
After successful recording, enter the command fastboot reboot. If everything went well, the phone will boot and you will see the Magisk welcome screen. Open the application - the version should be in the "Magisk" line, and the status "Installed" below. This means that you have successfully obtained Root access.
Comparison of methods for obtaining root access: Magisk vs KernelSU
In 2026, the rooting ecosystem is not limited to Magisk. New solutions have emerged, such as KernelSUthat work at the kernel level and provide an even higher degree of secrecy. The choice of method depends on your goals and device model.
| Characteristics | Magisk | KernelSU | RootFS (Old method) |
|---|---|---|---|
| Working level | User space | Kernel space (kernel level) | System partition |
| Stealth | High (requires Zygisk configuration) | Very high (default) | None |
| Installation complexity | Medium | High (custom kernel required) | Low (but outdated) |
| Modules support | Full | Partial / Through modules | Limited |
Magisk remains the most universal solution, supported by a huge community. KernelSU requires that the kernel of your device already has KSU support built-in, or you need to rebuild the kernel, which only experienced developers can do. For most Android 11 users, Magisk with enabled Zygisk (replacing Riru) will be the optimal choice.
Hide Root from banking applications and games
Obtaining superuser rights is only half the battle. The second half is to trick applications into thinking there are no rights. Banking applications Google Pay (now Google Wallet) and games with anti-cheat (for example, Pokemon GO) actively scan the device.
In the Magisk settings, you need to activate the switch Zygisk (previously called MagiskHide in older versions, but now the functionality has been changed). After enabling Zygisk and rebooting, go to Settings (gear) and enable DenyList. This list should include all banking apps and games. This will hide the presence of root access and the Magisk process from them.
Use the "Universal SafetyNet Fix" module (or its current forks) if Google Pay stops working after rooting. It replaces the device certification data.
It is also recommended to hide the Magisk application itself. In the manager settings there is a function "Hide the Magisk application". When activated, the application will be renamed (for example, to “Settings” or “File Manager”) and will receive a random batch identifier, which will make it difficult for simple scripts to detect.
⚠️ Attention: Banking application interfaces and detection methods are constantly changing. What worked yesterday may no longer work today after updating your banking app. Always check the functionality of payments after updates.
Possible problems and ways to solve them
The rooting process does not always go smoothly. The most common problem is Bootloop (infinite reboot). If after flashing the firmware magisk_patched.img the phone is stuck on the logo, try booting into Recovery mode (if there is a custom one) and doing a Wipe Data. If this does not help, you will have to return the original boot.img via Fastboot to bring the device back to life.
Another problem is Wi-Fi or Bluetooth not working after rooting. This often happens if you took boot.img from a different firmware version. Always use files strictly from the build that is installed on the device. You can check the build number in Settings → About phone.
The most common reason for failure is the use of a boot image from a different firmware version or a damaged file during download. Always double-check file hashes.
If you encounter the "Magisk not installed" error after rebooting, your antivirus or cleaning system may have removed Magisk files. Try reinstalling the application and re-patching