Obtaining superuser rights on devices with an operating system Android 9 Pie has become more complex, but at the same time a more controlled process compared to previous versions of the OS. In the era of Android 8.0, manufacturers have tightened security policies, making the classic “one-click” methods practically unworkable. Now the process requires a deep understanding of the system architecture, working with the bootloader and manipulating system partitions through the computer.
The main goal of rooting in 2026 has shifted from simply removing pre-installed software to fine-tuning performance, using specialized modules and full control over the hardware of the device. However, before you proceed, you must be aware that unlocking the bootloader often entails complete loss of warranty and irreversible erasure of all user data. This is not just a software setting, but an intervention in the fundamental mechanisms of the smartphone.
In this article we will analyze in detail the modern method of obtaining privileged access using a tool Magiskthat allows you to hide the fact of rooting from banking applications and services with a strict check of system integrity (SafetyNet/Play Integrity). We will look at the preparation, the image patching process and the final installation, paying special attention to the security of your data.
Device preparation and data backup
The first and most critical step is to create a complete backup of all information. Since the process of obtaining superuser rights on Android 9 requires unlocking the bootloader, the internal memory of the device will be completely cleared. This is a security requirement of the Android platform that cannot be bypassed using software methods without losing data.
Use cloud services or connect your smartphone to a PC to copy photos, contacts and documents. Pay special attention to saving encryption keys and two-factor authentication, as after a reset, access to them may be lost forever. It is also recommended to create a full partition dump EFS or Persistif your device model supports such operations through custom recovery or engineering menu.
⚠️ Attention: Unlocking the bootloader on some models (for example, devices with MediaTek processors or some versions of Verizon/Sprint) may not be possible or may result in to the “brickling” of the device. Always check the developer forums specifically for your model before starting work.
In addition to the data, you will need to prepare a software environment on your computer. Install ADB and Fastboot drivers, which are a standard communication tool between a PC and a smartphone. Without correctly installed drivers, the computer will not see the device in bootloader mode, which will make further instructions useless.
☑️ Preparing for rooting
Unlocking the bootloader
The bootloader is a app that runs before the operating system and verifies the digital signatures of all loaded components. By default, it is blocked by the manufacturer to prevent unsigned code from running. To obtain root access, we need to transfer it to the unlockedstate. Unlocking methods vary depending on the brand of the device.
For devices Xiaomi requires special permission through the official Mi Unlock utility and waiting from 3 to 168 hours. Devices Google Pixel i OnePlus allow you to unlock the bootloader with a simple command via Fastboot. Owners Samsung must use a combination of buttons and toggle a special flag in Download Mode, which also triggers the Knox counter.
The process usually looks like this: you put the smartphone into Fastboot mode (often this means holding down the volume down button when turning it on) and connect it to the computer. Then enter the command at the command line to release the lock. After confirming the action on the phone screen, the device will reboot and perform a factory reset.
fastboot flashing unlock
Keep in mind that on some Android 9 devices, unlocking the bootloader may result in the loss of the Widevine L1 feature, which reduces the quality of streaming video on services like Netflix to standard definition. This is a compromise that is made in order to gain complete control over the system.
Before unlocking the bootloader, be sure to unlink your Google account and remove the lock screen (PIN code, pattern), otherwise the device may be locked after a reset due to the FRP (Factory Reset Protection) function.
Extracting and patching the Boot image via Magisk
The modern rooting standard is to use a manager Magisk in systemless mode. This means that system files are not directly modified, but changes are loaded dynamically at boot. For Android 9 this method is the most stable. The first step is to download the official Magisk APK file and install it on your smartphone.
Next you will need an exact copy of the file boot.img from your current firmware. It can be extracted from a complete firmware archive (ROM) downloaded from the manufacturer’s website, or extracted from an already installed image using specialized utilities if you have access to the partitions. An incorrect boot.img image will cause the phone to stop booting.
Copy the file boot.img to the internal memory of the phone. Open the Magisk application, click the “Install” button in the Magisk block and select “Select and patch file”. Specify the path to your image. The application will create a new file with a name like magisk_patched_[random].img in the Download folder.
- 📂 Copy the patched file
magisk_patched.imgfrom the phone back to the computer in the folder with ADB tools. - 💻 Put your smartphone in Fastboot/Bootloader mode again times.
- 🚀 Execute the command to flash the modified image into the boot section.
After executing the flash command, the device is ready for the first boot with superuser rights. It is important not to interrupt this process and ensure a stable connection via the USB cable. The use of cheap or damaged cables often causes errors in writing to critical memory sections.
⚠️ Attention: Never use boot.img images from other firmware versions or from other phone models, even if they are similar. Differences in kernel memory addresses will lead to instant “bricking” of the device.
What to do if the phone goes into a cyclic reboot (Bootloop)?
If the phone does not boot after flashing the firmware, try going into Recovery mode and doing a wipe cache/dalvik. If this does not help, you need to flash the original (unpatched) boot.img via Fastboot with the command: fastboot flash boot original_boot.img. This will return the phone to a working state without root access.
Installing and configuring the superuser rights manager
After the system has successfully booted, you will see the Magisk application icon. When you first launch the application, you may request additional configuration or installation of additional components. At this stage, basic root access is already active, but for some applications to work correctly, additional configuration is required.
In the Magisk settings, it is recommended to enable the function Zygisk (if available for your version) and Enforce DenyList. This is necessary in order to hide the presence of root access from banking applications, games with anti-cheat and Google Pay services. Without this setting, many financial applications will refuse to start.
Also in this section you can activate support for init.d scripts, which allows you to run custom scripts when the system boots. This is a powerful tool for automating tasks such as changing the processor frequency, managing network parameters or fine-tuning the audio path.
| Magisk function | Purpose | Impact on the system |
|---|---|---|
| Zygisk | Injecting code into the process Zygote | Allows modules to work systemically |
| DenyList | List of exceptions for hiding Root | Necessary for banking applications to work |
| MagiskHide | Hide the fact of rooting (obsolete in new versions) | Replaced by DenyList in current builds |
| Superuser | Managing access rights requests | Control over which applications receive root |
The functionality check is carried out through the terminal or special checker applications. Enter the command su in the terminal: if the system asks for access confirmation and displays the symbol # instead of $, then the privileges have been granted successfully.
Managing modules and optimization systems
One of the main advantages of using Magisk is support for modules. Modules are archives that are installed like regular applications, but make changes to system files virtually. For Android 9, there are many optimizers that improve network performance, sound and battery life.
A popular solution is a module for managing daemons and services, which allows you to disable unnecessary system processes that consume battery power. There are also modules that change system fonts, emoji and visual interface elements without the need to rebuild the firmware.
However, installing too many modules can lead to conflicts and unstable system operation. Each installed module increases the boot time of the device. It is recommended to install only those add-ons that you really understand the need for and can justify.
⚠️ Warning: Modules that modify system libraries (for example, audio drivers or the display stack) may cause instability. Before installing such modules, make sure that you have access to your computer to restore the system via Fastboot in case of failure.
To manage modules, use the "Modules" tab in the Magisk application. Here you can enable, disable or remove installed add-ons. Some changes take effect only after the device is rebooted, which is standard behavior for system modifications.
Magisk modules allow you to customize Android 9 at a deep level, but their excess is a common cause of “bootloops” and rapid battery drain. Follow moderation.
Possible problems and methods of system recovery
Even if all instructions are followed, unforeseen situations may arise. The most common problem is a “soft brick”, when the phone turns on but gets stuck on the manufacturer’s logo. In 90% of cases, this is solved by returning to the original bootloader image.
If the device does not respond to button presses and does not enter Recovery mode, the recovery partition may be damaged. In this case, the only way out is the Download mode (for Samsung) or Fastboot (for others), through which you need to flash the full firmware or at least the critical sections. Also, users may experience a loss of security functions. After unlocking the bootloader, some payment applications may stop working permanently on a given device if the manufacturer has implemented a hardware check for bootloader status (as is the case with Samsung Knox). Software workarounds are often ineffective in such cases. boot And recovery.
Users may also experience loss of security features. After unlocking the bootloader, some payment applications may stop working permanently on a given device if the manufacturer has implemented a hardware check for bootloader status (as is the case with Samsung Knox). Software workarounds are often ineffective in such cases.
Always keep on hand the original firmware for your exact model and version of Android. The firmware version must match not only the phone model, but also the region and build version. Flashing incompatible software may lead to loss of IMEI function and inability to connect to a cellular network.
Will all information from the phone be erased when receiving Root?
Yes, at the stage of unlocking the bootloader, the memory will be completely cleared. This is a mandatory Android security requirement. After the rooting process itself (Magisk firmware), the data is not erased, but an initial reset is inevitable.
Is it possible to get system updates over the air (OTA) with root access?
Official updates over the air usually do not come to devices with an unlocked bootloader. If the update has arrived, its installation may remove root access or lead to an error. It is recommended to download full firmware images manually and update via a computer, saving the patched boot image for re-installing Magisk.
Is it safe to use banking applications after rooting?
Without additional configuration - no. Banking applications detect the presence of root and block the work. However, by using Magisk's hiding features (DenyList/Zygisk), you can successfully bypass these checks. However, security risks always remain higher than on a stock system.
What is "Systemless Root" and why is it important?
Systemless Root means that the files on the /system partition are not physically changed. Modifications are loaded into RAM upon boot. This is important for passing security checks (SafetyNet) and the ability to receive OTA updates without a complete flashing.