Obtaining superuser rights, or root accessopens up almost limitless opportunities for the smartphone owner to customize and manage the system. This allows you to remove pre-installed software, block ads at the system level, make full backups and fine-tune the processor. However, this function is not provided by standard Android tools, and its activation requires the use of specialized tools that work in tandem with a computer.
One of the most reliable and universal methods is to use the bundle ADB (Android Debug Bridge) i Fastboot. This approach requires the user to be attentive and understand the processes that occur when interacting with the device bootloader. Unlike “one-click” applications from the Play Market, which often contain malicious code or simply do not work on modern versions of the OS, the ADB method gives complete control over the procedure.
Before starting any manipulations, it is critical to understand the risks. Any tampering with the system partition may lead to loss of warranty or turning the device into a “brick.” The bootloader unlocking procedure will inevitably lead to the complete deletion of all user data from the internal memory. Therefore, the first and most important step should be to create a backup copy of all important files, contacts and photos to an external drive or to cloud storage.
Preparation of the working environment and necessary tools
The success of the operation depends 90% on the correct preparation of software on a personal computer. You will need to install a minimum set of tools, which includes device drivers, the Android SDK Platform-Tools, and a boot image specific to your model. Without correctly installed drivers, the computer simply will not see the smartphone in debug mode.
You should download Platform-Tools exclusively from the official Android developers website to avoid modified versions that may contain vulnerabilities. After downloading the archive, it must be unpacked to the root of the disk or to any folder with a short path, avoiding Cyrillic characters in the directory name, since the console may interpret such paths incorrectly.
On the smartphone itself, you must activate the hidden menu for developers. To do this, go to Settings → About phone and quickly click on the item Build numberseven times. After a message appears stating that you have become a developer, return to the main settings menu and find the new section For developers. You need to enable two key parameters in it:
- 📱 USB debugging —allows the computer to send commands to the device.
- 🔓 Factory unlocking (OEM Unlocking) - allows changing the bootloader state.
- 💾 File transfer - default connection mode when connected with a cable.
Also make sure that the device's battery charge is at least 60-70%. Interruption of the firmware process due to battery discharge is one of the most common causes of irreversible system damage. Use only an original or high-quality certified cable, since cheap analogues can only support charging mode, but not data transfer.
☑️ Ready for root
Unlocking the bootloader
Most modern smartphones come with a locked bootloader, which is a safety measure of the manufacturer. To be able to write changes to system partitions, this lock must be removed. The procedure varies greatly depending on the brand: if Xiaomi requires waiting for 7 days and using the proprietary Mi Unlock utility, then for Pixel or OnePlus the process takes a few minutes.
Connect your smartphone to the computer and put it in Fastboot mode. This is usually done with a key combination when the device is turned off (most often Volume down + Power) or through the command adb reboot bootloader, if debugging is already active. In the command line window or PowerShell, opened in the tools folder, check the connection:
fastboot devicesIf you see the device serial number in response, then the connection is established. Now you can send the unlock command. For many devices, it looks standard, but be careful: on some models (for example, Sony or Huawei), this procedure may not be possible without obtaining a special code from the manufacturer, which is no longer issued.
fastboot flashing unlockor for older devices:
fastboot oem unlockA data loss warning will appear on the smartphone screen. Confirm the action with the volume buttons. After rebooting, the device will be completely cleaned and ready for modification. If the command returns an error or the device freezes, it means that your carrier or manufacturer has imposed a hardware ban on unlocking.
⚠️ Attention: Unlocking the bootloader on Samsung devices with a Snapdragon processor often triggers the Knox fuse, which physically burns out the fuse element. This permanently disables Samsung Pay, Secure Folder and reduces the liquidity of the device on the secondary market.
Why are some phones not unlockable?
Carriers in the US and some other countries require manufacturers to lock the bootloader to prevent users from changing network settings or uninstalling pre-installed carrier apps. It is impossible to bypass this programmatically.
Installing a custom recovery or patching an image
There are two main ways to obtain superuser rights on modern versions of Android. The first is classic, through the installation of a modified recovery (for example, TWRP), into which an archive with access rights is then sewn. The second, more relevant for Android 11-14, is the method of directly patching the boot image using an application Magisk.
Let's consider the method with Magisk, since it is less invasive and makes it easier to hide the fact of obtaining root access from banking applications. You'll need to download the official Magisk APK, transfer it to your phone, and install it like a regular app. Inside the application, select the “Install” item and the “Patch Boot Image” method.
To do this, you will need the source file boot.img, which must exactly match the firmware version installed on your device now. It can be extracted from a full firmware image (ROM) downloaded from the manufacturer's website, or pulled from an already installed update through special utilities on the phone itself.
After Magisk creates the patched file (usually it is saved in the Download folder with a name like magisk_patched_[random].img), copy it back to the computer in the folder with Platform-Tools. Switch the phone back to Fastboot mode and run the firmware command:
fastboot flash boot magisk_patched.imgIt is important not to mix up the partitions. On devices with A/B architecture (seamless updates), it is sometimes necessary to flash both slots using the flag --slot allalthough in most cases, flashing the active slot is sufficient for the first boot.
| Device type | Unlock command | Features firmware | Risk of loss of warranty |
|---|---|---|---|
| Google Pixel | fastboot flashing unlock |
Simple, A/B support | High (status changes) |
| Xiaomi / Redmi | Mi Unlock utility | Requires account and waiting | The warranty is preserved (often) |
| Samsung | Button combination | Knox works, you need Odin | Lost the warranty forever |
| OnePlus | fastboot oem unlock |
Quickly, without waiting | Depends on the region |
Using a patched boot image via Magisk is the safest method, since it does not require replacing the entire recovery and is easier to disguise as the original system.
Completing the installation and checking rights
After executing the flash command, enter fastboot reboot to reboot the device. The first launch may take longer than usual as the system optimizes applications and checks the integrity of changed partitions. Don't panic if the boot process gets stuck on the logo for more than 5-7 minutes - this may indicate an error in the boot image version.
If the phone has booted successfully, look for the Magisk icon in the application menu. Launch it. If the version number is displayed at the top of the screen, and the “Magisk” line has a checkmark or the “Installed” status, then the rights have been obtained successfully. For a final check, you can install the Root Checker app from the store.
You can now grant apps root access. The first time you launch a app that requires elevated privileges (for example, the Solid Explorer file manager or the AFWall+ firewall), the system will ask for confirmation. You can choose "Only once" or "Forever" to avoid receiving notifications all the time.
It is worth noting that having root access changes the behavior of the system when updating over the air (OTA). Trying to install an official update directly on top of a modified bootloader will most often result in an error or a cyclic reboot. Before updating the firmware, you will need to temporarily restore the original boot image.
Possible problems and ways to solve them
The process of obtaining superuser rights rarely goes perfectly smoothly for all users. The most common problem is an error FAILED (remote: device is locked) when trying to flash the firmware. This means that the bootloader was not unlocked correctly or the command was entered in the wrong mode (for example, you are in S-OFF instead of Fastboot).
Another common situation is "Bootloop" (cyclic reboot). If, after flashing the firmware, the phone constantly reboots without reaching the desktop, you need to go into Fastboot mode again and flash the original, unpatched boot.img. This will return the device to a working state, but without root access, after which you can try to find a different image or version of Magisk.
⚠️ Attention: If your device uses data encryption (which is standard for Android 6.0+), then unlocking the bootloader will reset the encryption keys. Without complete formatting of the data (wipe data), it will be impossible to boot into the system, even with the original image.
Also, users often encounter the fact that banking applications stop working and display security errors. This occurs because the system integrity check (SafetyNet or Play Integrity API) detects modifications. To solve this problem, in the Magisk settings you need to activate the "Zygisk" function and configure the exclusion list (DenyList), hiding the Magisk store itself from scanning applications.
If the phone is not detected in Fastboot mode, try installing generic Google USB Drivers or drivers from the manufacturer (for example, Motorola USB Drivers) manually through Windows Device Manager.
Security and hiding root access
Having superuser rights in itself is not a vulnerability, but it removes many layers of Android sandbox protection. Malware that gains root access can cause irreparable damage to the system, delete system files, or steal data from protected storage. Therefore, install applications that require root only from trusted sources.
For everyday use, it is important to maintain a balance between functionality and security. Modern methods allow you to completely hide the fact of having root access from most applications. The use of Magisk modules, such as Shamiko or Universal SafetyNet Fix, helps bypass checks of banks and payment systems, making the device almost indistinguishable from stock for regular software.
However, remember that the arms race between developers of bypass methods and creators of security systems continues constantly. What worked yesterday may no longer work after you update your banking app. Always have the original firmware image on hand so that, in case of a critical need, you can quickly return the device to its factory state.
Will rooting erase the warranty on the phone?
Formally, yes, most manufacturers indicate obtaining root access as a reason for refusing warranty service. However, if you can return the device to stock state (lock the bootloader and restore the original image), it will be extremely difficult to visually and programmatically determine the fact of interference, unless the physical Knox fuse has blown.
Is it possible to receive bank transfers with a rooted phone?
Yes, it is possible. Banking applications are blocked when superuser rights are detected, but using the hide settings in Magisk (Zygisk + DenyList) and hiding the Magisk application itself (renaming the package), you can make banking applications work correctly.
What to do if you forgot the pattern key after unlocking the bootloader?
Unlocking the bootloader automatically resets to factory settings (Wipe Data). Therefore, the old pattern or password will no longer be on the device - you will have to set up the phone as new and enter the Google account that was synchronized earlier.
Do you need a computer to get Root?
In most cases - yes, especially to unlock the bootloader. There are methods for installing root without a PC (through system vulnerabilities), but they only work on very old versions of Android or specific models and are extremely unstable and dangerous.
How to remove root access if they are no longer needed?
The cleanest way is to open the Magisk application, click the "Uninstall" button and select "Full removal". After this, the phone will reboot. If the bootloader remains unlocked, you can lock it back via Fastboot with the command fastboot flashing lock, but this will erase all data again.