Getting root access on Android gives the user full control over the operating system, removing software restrictions imposed by the manufacturer. This allows you to remove pre-installed system applications, modify the kernel, install custom firmware and, what is most often of interest to ordinary users, provide applications with access to critical system functions. However, before you start the process, you need to be aware that interfering with system partitions carries certain risks for the stability of the device.
The rooting procedure is radically different depending on the smartphone model, Android version and the bootloader used. Modern versions of Android, such as Android 13 or Android 14have enhanced security, which makes older methods like KingRoot or OneClickRoot practically ineffective. Today, the de facto standard is to use a tool Magiskthat provides system access without changing the system partition (systemless root), which allows you to bypass many security checks of banking applications.
⚠️ Attention: Obtaining superuser rights will automatically void the manufacturer's warranty. You will correct any physical or software damage that occurs during the process at your own expense.
Preparing the device for the rooting procedure
The first and most important step is to save all personal data. The process of unlocking the bootloader, which is a mandatory step to get root, completely erases the internal memory of the device. You need to back up your contacts, photos and documents to cloud storage or to your computer. Ignoring this step will result in irretrievable loss of information.
Next, you should activate developer mode. To do this, go to Settings → About phone and quickly click 7 times on the item Build number. After a notification appears that you have become a developer, go to the new menu System → For developers. Here you need to find and enable the option USB debugging. Without this permission, the computer will not be able to send commands to the device through the interface ADB.
It is also critical to know the exact model processor and bootloader version. Different chipsets, such as Snapdragon, MediaTek or Exynos, require different approaches to modifying the boot image. There are no universal solutions, and trying to flash an incompatible file can turn your smartphone into a brick. Check the availability of drivers for your device on your computer so that the system correctly recognizes the phone in fastboot mode.
Unlocking the bootloader
The bootloader is a app that runs before the operating system and verifies the digital signature of the loaded software. It is locked by default to prevent unauthorized modifications from being installed. Unlocking is the first technical step to rooting. For devices Xiaomi requires the official Mi Unlock utility and a wait of 3 to 7 days after linking the account. For Google Pixel and OnePlus the process is much faster through the command line.
To unlock the bootloader manually, connect the switched off phone to the computer by holding down the combination of buttons (usually Volume down + Power) to enter Fastboot mode. In the PC command line, enter the command to check the connection:
fastboot devicesIf the device is detected, enter the unlock command. Please note that the commands may vary on different devices. For most models, the following is used:
fastboot flashing unlockA warning about data loss will appear on the smartphone screen. Confirm the action with the volume buttons. After rebooting, the device will be completely cleaned. Some manufacturers, for example Huawei or American telecom operators, may completely block this feature by not providing unlock codes.
Installing Magisk to manage root access
The modern standard for gaining superuser privileges is to use Magisk. Unlike older methods that modified the system partition, Magisk operates in a "systemless" mode, making changes to memory at boot. This allows you to hide the fact of rooting from applications that check security, such as banking software or Google Pay.
The installation process begins by obtaining a file boot.img from the official firmware of your model. This file can be extracted from the archive with the factory software (ROM), downloaded from the manufacturer’s website. Copy the file boot.img to the internal memory of the phone. Then install the application Magisk Manager (The APK file is downloaded from the official GitHub repository).
Open Magisk Manager, click the button Install next to Magisk and select the option Select and patch the file. Indicate the previously copied boot.img. The application will create a modified file with a name like magisk_patched.img in the downloads folder. This file must be returned to the computer.
Before flashing the patched image, be sure to check the checksum of the file to ensure the integrity of the data and avoid write errors.
The final stage occurs again in Fastboot mode. Enter the command to flash the modified image:
fastboot flash boot magisk_patched.imgAfter successful recording, enter fastboot reboot. The first time you boot, the process may take longer than usual. If the device has booted, open Magisk Manager - if you see the version number instead of the "Install" button, then root access have been successfully obtained.
Granting rights to specific applications
After installing Magisk, root access is not automatically granted to all apps. This is done for security reasons. When an app first requests root permissions, a pop-up from Magisk will appear on your screen asking for confirmation. You can select the option “Grant”, “Refuse” or “Grant forever”.
You can manage the list of permissions in the Magisk application itself by going to the section with the shield icon (Superuser). All apps that have requested access are displayed here. You can revoke rights from any application at any time by toggling the appropriate toggle switch. This is useful if you suspect that a utility is using privileges for malicious purposes.
- 🛡️ File Administrators: Applications like Root Explorer or Solid Explorer require root to access system folders
/systemand/data. - 🔋 System tweakers: Utilities like Kernel Adiutor or Franco Kernel Manager use root to change processor frequencies and power management.
- 🧹 Junk cleaning: Advanced cleaners use root to remove system application caches that are not accessible by the usual method.
Some applications require settings via Magisk modules. For example, to work LSPosed (framework for Xposed modules), you need to activate the "Zygisk" option in the Magisk settings and reboot the device. Without this, deep modification of the behavior of other applications will be impossible.
☑️ Checking successful rooting
Security risks and working with banking applications
Having root access significantly reduces the level of security of the device. Malware that gains root access can steal any data, intercept keystrokes, or encrypt the device. By default, banking applications and contactless payment services refuse to work on rooted devices, detecting a modified bootloader or the presence of a binary file su.
To bypass these restrictions, Magisk has a function DenyList (Refuse List). In the settings, enable "Enforce DenyList" and "Zygisk". Then, in the list itself, check the boxes for banking applications, Google Play Services and Google Pay. This will force Magisk to hide root access for these specific apps. However, if the bootloader is unlocked, some apps (such as Google Wallet) may still not work due to system integrity verification (SafetyNet or Play Integrity API).
⚠️ Warning: Hiding root access is an arms race. Banks are constantly updating detection methods, and what worked yesterday may stop working after updating the application.
The table below shows common problems and methods for solving them when working with banking software on a rooted device:
| Problem | Cause | Solution method |
|---|---|---|
| Application does not start | Magisk detected | Add application to DenyList, enable Zygisk |
| Security error | Unlocked Bootloader | Use the Universal SafetyNet Fix module |
| Blocking by certificate | Presence of suspicious modules | Temporarily disable all modules in safe mode |
| Google Pay does not work | Failed Play Integrity | Clear Google Play Services data, reflash patch |
What is Zygisk?
Zygisk is an implementation of Magisk in the Zygote process that allows modules to be injected into any Android process. This is a more advanced and secretive replacement for the old MagiskHide mechanism.
Returning to its original state (Unroot)
If you decide to give up root access, sell the phone or send it to a service center, you need to return the device to its stock state. Simply deleting the Magisk app will not remove the modified boot image, and the phone may stop turning on or continue to be detected as rooted.
The easiest way is to open the Magisk app, click on the button Delete and select the option Full uninstall. The device will automatically reboot and restore the original boot.img from the backup created during installation. This method works in 95% of cases if manual changes have not been made to other sections of memory.
In more complex cases, when automatic removal does not work or the system is damaged, you will need to manually flash the stock image. Download the official firmware for your model, extract the original one boot.img and flash it via Fastboot using the command fastboot flash boot boot.img. This is guaranteed to return the bootloader to its original state, although unlocking the bootloader itself (the unlocked flag) will remain until you lock it back with the command fastboot flashing lock.
Always keep the original boot.img of your firmware - this is the only reliable way to quickly restore the device if the experiment fails.
Is it possible to get root without unlocking bootloader?
On modern devices with Android 9 and higher, this is almost impossible. Methods that use kernel vulnerabilities (exploits) are rare, unstable and often lead to unstable system operation. Unlocking the bootloader is the only reliable way.
Will root delete my data?
Installing Magisk itself does not delete the data. However, the bootloader unlocking step, which is required before installation, completely clears the internal memory of the device. A backup is required.
Why doesn't fingerprint work after rooting?
On some devices (especially Sony and Samsung), modifying the boot partition breaks the security key store (TEE). In such cases, biometrics may stop working forever until the stock image is flashed.
Are root apps from the Play Market dangerous?
Applications that require root are not dangerous in themselves if downloaded from trusted sources. The very presence of superuser rights poses a danger: if you give access to a virus, it can do whatever it wants to your phone. Trust only well-known developers.
⚠️ Attention: Menu interfaces and item names may differ depending on the manufacturer’s shell (MIUI, OneUI, ColorOS). Always check the documentation for your specific model before entering commands.