Obtaining superuser rights (Root) on a device under control Android opens up unlimited possibilities for the smartphone owner to customize and manage the system. This allows you to remove software pre-installed by the manufacturer that cannot be uninstalled using standard methods, as well as install specialized applications to deeply optimize processor and battery performance.
However, the process of granting privileges requires careful preparation and understanding of the risks associated with violation of warranty and potential loss of data. Many users are wondering how to give root access to an Android app safely, without turning your gadget into a “brick”. Modern methods, such as using Magisk or KSU, provide hidden access to rights, which is critical for the operation of banking applications and services with a high degree of security.
In this article we will analyze in detail all stages of the procedure: from unlocking the bootloader to the final configuration of the superuser manager. You will learn what tools are needed, how to create a backup copy of the system and what to do if errors occur at different stages of the firmware.
Preparation of the device and necessary tools
Before starting any manipulations with the system partition, you must perform a number of mandatory actions that minimize risks. The first step is to create a complete backup copy of all important data, since the process of unlocking the bootloader in 99% of cases leads to complete removal of information from the internal drive.
You will need a computer with drivers installed ADB and Fastboot, as well as an original USB cable to ensure a stable connection. You should not use cheap "charge only" cables, as they may not support data transfer, which will lead to failures during the firmware process.
⚠️ Warning: Unlocking the bootloader will officially void your device's warranty in most regions. Manufacturers may refuse free repairs if they find traces of tampering with the software.
You also need to enable developer mode and USB debugging in the smartphone settings. To do this, go to Settings → About phone and click on the build number seven times, after which a new item “For Developers” will appear in the menu.
☑️ Preparing for rooting
Unlocking the bootloader
The bootloader is a special app that runs before the operating system and verifies the integrity of the software signature. By default, it is locked by the manufacturer, which does not allow the installation of modified Recovery or kernel images.
The unlocking procedure differs for different brands. For example, on devices Xiaomi you need to wait from 7 to 16 days after linking your account, but on Samsung it is enough to simply switch the toggle switch in bootloader mode. For Pixel i OnePlus the process is as simplified as possible and is performed through the command line.
After enabling USB debugging, connect the smartphone to the PC and enter the command to put the device into Fastboot mode:
adb reboot bootloaderNext, depending on the model, enter the unlock command. For most devices it looks like fastboot oem unlock or fastboot flashing unlock. A warning about data loss will appear on the phone screen, confirmation of which will initiate formatting of the userdata section.
What to do if the command is not executed?
If the console displays the error "device not found" or "waiting for device", check the installed drivers. Try using a different USB port, preferably USB 2.0, and the original cable. Also make sure that permission to debug from this computer appears on the phone screen.
Choosing a method for obtaining Root: Magisk versus old utilities
The era of universal applications like KingRoot or Framaroot, which received rights in one click, is irrevocably gone. On modern versions Android 10, 11, 12 and higher these methods do not work due to the enhanced SELinux security system and complex partition structure.
The gold standard of the industry at the moment is Magisk. This solution implements a systemless modification, that is, it does not directly modify the system partition, but is loaded when the system boots. This allows you to use the function Zygisk to hide root access from banking applications and anti-cheats in games.
- 🔒 Systemless Root: The system partition remains untouched, which allows you to pass the Integrity Play Store integrity check.
- 🛡️ Magisk Hide: The ability to selectively hide the presence of root access from specific applications.
- 🧩 Modules: Installation support modules for changing fonts, emoji, sound settings and other parameters without flashing.
- 🔄 OTA updates: Ability to receive official system updates while maintaining root access (if installed correctly).
An alternative may be KernelSU, which works at the kernel level and is only suitable for devices with certain kernel versions (usually 5.10+). This method is more advanced, but less universal for older devices.
Step-by-step guide for installing Magisk
To install superuser rights, you will need an exact copy of the bootloader image (boot.img or init_boot.img) from your current firmware version. This file can be extracted from the official firmware image (ROM) downloaded from the manufacturer’s website, or obtained through the utility payload_dumper.
Copy the resulting image file to the internal memory of the smartphone. Then install the application Magisk Manager (download only from the official GitHub repository to avoid malicious modifications). Launch the application and click the “Install” button in the Magisk block.
In the menu that appears, select the “Select and Patch a File” method and specify the path to the copied bootloader image. The application will process the file and save the patched version in a folder Download with the name of the type magisk_patched_[random].img.
⚠️ Attention: It is strictly forbidden to flash an image from a different firmware version or from a different phone model. This is guaranteed to lead to a bootloop (cyclic reboot) and the need for flashing via EDL or Odin mode.
Return the file with the name magisk_patched... to the computer. Switch your smartphone to Fastboot mode and run the firmware command:
fastboot flash boot magisk_patched.imgFor devices with a partition init_boot (for example, Pixel 7/8, Xiaomi 13/14) the command will be:
fastboot flash init_boot magisk_patched.imgAfter successful recording, enter the command fastboot reboot. When you first boot, the process may take up to 5-10 minutes. If the device has booted, open Magisk Manager - if the version number is displayed in the “Version” line and not “N/A”, it means that root access have been successfully obtained.
Before flashing the firmware, be sure to check the partition name. On new Android 13+ devices, the kernel image is often located in the init_boot section, rather than in the usual boot. Selecting the wrong partition will make the phone unable to boot.
Configuring application access to Root
After successfully installing Magisk, access to superuser rights is not automatically granted to all applications. This is done for security purposes: each application must explicitly request access, and the user must confirm it.
When you launch an application that requires root access (for example Titanium Backup, Root Explorer or terminal), a pop-up window from Magisk will appear on the screen asking for permission. You can choose the option “Grant forever”, “Grant only once” or “Refuse”.
You can manage the list of allowed applications in the settings of Magisk Manager itself. Go to the “Superuser” section (shield icon), where you will see a list of all requests. Here you can revoke the rights of any application at any time by simply switching the toggle switch opposite its name.
| Application | UID | Access | Notifications |
|---|---|---|---|
| Termux | u0_a123 | Allowed | Enabled |
| Root Explorer | u0_a145 | Allowed | Disabled |
| Doubtful application | u0_a201 | Forbidden | Enabled |
| SystemUI Tuner | android | Allowed | Disabled |
Some applications may not explicitly request rights, but try to obtain them in the background. Check your Magisk log regularly to monitor for suspicious activity.
Root access is the key to the entire system. Never provide it to applications from untrusted sources or those whose functionality does not require deep file system access.
Solving problems and hiding Root from banks
One of the main problems after obtaining root access is the refusal of banking applications (Sberbank, Tinkoff, Google Pay) to work on a rooted device. They use the service to check the security of the environment. To bypass this protection, you must enable the feature in Magisk settings. After turning it on and rebooting, go to the settings and select “Configure exclusion list” (DenyList). Check the boxes for all banking applications, Google Play Services and the Google Play Market itself. Google Play Integrity API to check the security of the environment.
To bypass this protection, you must enable the feature Zygisk in Magisk settings. After turning it on and rebooting, go to the settings and select “Configure exclusion list” (DenyList). Check the boxes for all banking applications, Google Play Services and the Google Play Store itself.
It is also recommended to install a module Play Integrity Fix (developed by chiteroman), which replaces the device’s fingerprints with certified ones. This allows you to return the “Certified” status in the Play Market settings and restore contactless payment functionality.
⚠️ Attention: Banking application interfaces and root detection methods are constantly updated. What worked yesterday may no longer work after an app update. Always check the latest bypass methods on specialized forums (for example, w3bsit3-dns.com or XDA).
If the application still does not start, try clearing its data and cache after setting up DenyList. In extreme cases, using an isolated space helps, for example, through an application Shelter or Insular, which creates a working profile where root access is not visible.
Return to its original state (Unroot)
If you needed to return the phone for warranty repair or you simply decided to refuse from superuser rights, the return procedure is simple. Magisk allows you to completely remove yourself from the system without having to manually flash the stock image.
Open the Magisk Manager app and click the “Remove Magisk” button in the center of the screen. Select "Complete removal". The device will automatically reboot and the process will take a few minutes. After booting, you will have a clean system with a locked (or unlocked but stock) bootloader.
Remember that uninstalling Magisk does not lock the bootloader back. If a locked BL is required for warranty, you will have to run the command fastboot oem lock, but this will again delete all data from the phone, so make a backup in advance.
What to do if the phone does not boot after flashing the firmware?
If the device is stuck on the logo (bootloop), try going into Recovery mode (usually volume up + power) and make wipe cache/dalvik. If it doesn’t help, you need to flash the stock boot.img via Fastboot or use emergency recovery mode (EDL for Xiaomi, Odin for Samsung).
Is it safe to obtain root access on modern Android?
If you follow all instructions and use current methods (Magisk/KSU), the risk is minimal. The main danger is the human factor: inserting the wrong file or interrupting the recording process. The smartphone will not be physically damaged, but it can be disabled programmatically, which will require flashing.
Will the warranty expire after receiving Root?
Formally, yes, most manufacturers indicate this in the warranty terms. However, if you completely remove Magisk and return to the stock image of the system (Unroot), there will be no software traces left behind. Service centers rarely physically check for signs of tampering unless the problem is related to overheating or power supply.
Is it possible to get system updates over the air (OTA) from Root?
A standard OTA update will not be installed on a modified boot partition. However, by using the "Install to inactive slot" method in Magisk before rebooting, you can retain root privileges after the update. Or you can download the full firmware image, patch it and install it manually.
What applications are required for the Root owner?
It is recommended to install: Swift Backup (for backing up applications and data), Titanium Backup (classic for freezing the system software), Root Explorer (file manager) and Termux (terminal emulator for advanced scripts).
Why does the KingRoot application not work on Android 13?
KingRoot uses vulnerabilities in the kernel that were closed back in Android 6-7. On modern versions of Android, the security architecture (SELinux, Verified Boot) does not allow KingRoot exploits to gain access to the system partition. The only working method is manual flashing of a modified bootloader.