Obtaining superuser rights, or root accesson modern versions of the Android operating system has become much more difficult than a few years ago. If on older versions it was enough to launch one application, then Android 10 requires deep intervention in the system partitions. Google tightened security policies by introducing mandatory encryption and bootloader verification, which makes the process more labor-intensive, but still doable.
The main reason, The reason why users strive to unlock their devices is the desire to gain full control over the hardware software. The ability to remove system software, change the processor frequency, or install specialized modules outweighs the fear of losing the warranty for many enthusiasts. However, before starting the procedure, you must be aware that any manipulations with the bootloader will void the warranty manufacturer.
In this article we will analyze the current method of obtaining root access through the utility Magisk, which is currently the industry standard for system modification. We will look at preparing the device, the unlocking process and the final installation of the patch. Be careful: following the steps incorrectly can turn your smartphone into a “brick.”
⚠️ Attention: You perform all actions at your own peril and risk. The author of the article is not responsible for damage to the software or hardware of your device during the modification process.
Preparing the device and backing up data
The first and most critical step is to save all important information. The process of unlocking the bootloader, which is a prerequisite for obtaining root completely deletes all data from the internal storage of a smartphone. This is done by manufacturers for security purposes so that attackers cannot access your files when you reset the protection.
You need to create a complete backup of your contacts, photos, documents and application settings. It is best to use cloud services, such as Google Drive, or copy the files to your computer via a USB cable. It is also recommended to make a backup of the partition EFS or persistif your device supports such operations through custom recovery, since the loss of IMEI can make the phone unusable for communication.
In addition to saving data, you need to prepare a software environment on the computer. You will need to install drivers ADB and Fastbootthat allow the computer to communicate with the phone in a special mode. Without these tools, interaction with the bootloader is impossible.
☑️ Preparing for rooting
Make sure that it is turned on on your smartphone USB debugging. To do this, go to settings, find the “About phone” item and quickly click on the build number until a notification appears that you have become a developer. After that, in the “For Developers” menu, activate the desired switch.
Unlocking the bootloader
The bootloader is a app that runs in front of the operating system and verifies the integrity of its signature. On most devices it is blocked by default, which prevents the installation of modified images. The unlocking procedure is radically different depending on the brand of your smartphone.
For devices based on chips MediaTek or Qualcomm often you need to obtain a special unlock token through the manufacturer's official website. For example, owners Xiaomi must wait 168 hours after linking an account, and users Samsung may lose access to Knox security features forever. There is no universal “Unlock” button.
- 🔓 Xiaomi / Redmi: Requires the Mi Unlock Tool and waiting for a week.
- 🔓 Google Pixel / OnePlus: The command
fastboot flashing unlockis performed directly without tokens. - 🔓 Huawei: Official unlocking is almost impossible for new models after 2018.
- 🔓 Samsung: Requires switching to Download Mode and confirming the action with the volume buttons.
⚠️ Attention: On Samsung devices, unlocking the bootloader physically blows the Knox electronic fuse (0x1). This permanently disables Samsung Pay, Secure Folder, and some banking apps, even if you reset the bootloader.
Once successfully unlocked, the phone will reboot and erase all data. The next time you turn it on, you will see a warning that the device is not certified or the bootloader is unlocked. This is normal system behavior.
What to do if the fastboot command is not visible?
If the computer does not see the phone in fastboot mode, try another USB cable (preferably original), another USB 2.0 port, or reinstall the drivers manually through the device manager, selecting the Android Bootloader Interface model.
Installing a custom recovery and image patch
The modern method of obtaining root access does not require flashing entire custom recoveries like TWRP, although they are still useful for creating full backups. The main tool is Magisk Manager. You need to download the official APK file from GitHub and install it on your smartphone as a regular application.
The essence of the method is to patch the boot image (boot.img). You need to extract this file from the stock firmware that exactly matches the software version currently installed on your phone. Using an image from a different firmware version will lead to bootloop (an endless reboot).
The algorithm of actions is as follows: copy the file boot.img to your phone, open the Magisk application, click “Install” next to Magisk and select “Patch boot image”. The application will create a new file magisk_patched.img in the downloads folder.
fastboot flash boot magisk_patched.imgThis command must be executed from the platform tools folder on the computer, having first switched the phone to fastbootmode. After flashing the patched image, the device is ready for the first launch with superuser rights.
Never try to patch the recovery image if your goal is only root. It is boot.img that needs to be patched, since Magisk is embedded in the boot partition, and not in the recovery partition.
Final setup and checking rights
After entering the firmware command, enter the command fastboot reboot to reboot the device. The first launch may take longer than usual as the system checks the integrity of changed files. If the phone has successfully booted, open the Magisk application.
In the application interface you should see the version of the installed app and the “Installed” status. If it says “Not Installed,” it means the patch was not applied correctly or was discarded during boot. In this case, you will need to repeat the procedure or check the compatibility of the Magisk version with your version of Android 10.
For a final check, download any application from Google Play that requires root access, for example Root Checker. Launch it, grant superuser rights through the Magisk pop-up window, and the application will confirm the privileges.
| Option | Before modification | After obtaining Root |
|---|---|---|
| Access to system files | Read only | Full access (Read/Write) |
| Deleting system applications | Impossible | Possible through a terminal or special device. software |
| Operation of banking applications | Full | Often blocked (hiding required) |
| OTA system updates | Automatic | Root is blocked or broken |
The presence of the Magisk icon and a successful test in Root Checker guarantee that the process is completed correctly and the system kernel is modified.
Hiding root access from banks and games
One of the main problems after obtaining root access is the operation of applications, which check the integrity of the system. Banking clients, Google Pay (now Google Wallet) and many online games block launching on rooted devices. Fortunately, Magisk has built-in mechanisms to bypass these checks.
In the settings of the Magisk application, you need to activate the function Zygisk. This technology allows Magisk code to be injected into the Zygote process, making hiding more effective. Also enable the “Observe exclusion list” (DenyList) option.
In the DenyList, you need to check off all applications that should “think” that there are no root access. This includes banks, payment processors, and sometimes Google Play Services itself. After changing the settings, be sure to restart your device.
⚠️ Attention: Banking application developers are constantly updating detection methods. What worked yesterday may no longer work after an app update. Follow the XDA Developers community for the latest hiding modules.
If standard tools are not enough, you can install the module MagiskHide Props Config or use third-party solutions like Shamikothat improve masking algorithms. However, remember that this is an arms race between modders and security services.
Possible problems and ways to solve them
Despite careful preparation, errors may occur during the process. The most common problem is when the phone gets stuck on the manufacturer's logo. In most cases, this occurs due to the incompatibility of the patched image bootloopwhen the phone gets stuck on the manufacturer's logo. In most cases this happens due to incompatibility of the patched image boot.img with the current version of the kernel or damage to the partition during writing.
To get out of this situation, you will need to put the phone back into fastboot mode and flash the original, stock image boot.imgthat you saved before starting all the manipulations. This will return the phone to its original state without root access, but will keep it working.
Another common problem is the lack of Internet after unlocking the bootloader on some MediaTek models. This is due to partition corruption persist. You can restore it only by having a dump of this partition from exactly the same device or through a service center.
- 🔥 Overheating: A modified kernel may incorrectly manage thermal control.
- 🔥 Decreased autonomy: Background processes with root access may consume more energy.
- 🔥 Communication instability: Changing modem frequencies can lead to network loss.
If you encounter a critical error, do not panic. The enthusiast community is large and restoration kits are available for most popular models. The main thing is not to try to flash random files from unverified sources.
Is it possible to return the warranty after rooting?
Technically, you can lock the bootloader back and flash the stock firmware through official utilities (MiFlash, Odin, SP Flash Tool). However, the Knox counter on Samsung and traces of flashing in the service logs often indicate the fact of interference, so the warranty may not be restored.
Is it safe to root Android 10 in 2026?
The process has become safer thanks to Magisk, which does not directly modify the system partition (systemless root). However, the risks of data loss and device damage due to inept actions remain high. This is not recommended for the average user.
Will the warranty expire after unlocking the bootloader?
In 99% of cases, the manufacturer will void the warranty on software, and often on hardware, if it proves that the breakdown is caused by a software modification. On Samsung devices, the Knox counter is irrefutable evidence.
Is it possible to get root without unlocking the bootloader?
On Android 10 this is almost impossible using legal methods. Old kernel exploits (like KingRoot) are covered by Google security patches. The only working method is to officially or semi-officially unlock the bootloader.
Will the system be updated over the air (OTA) after getting root?
Usually no. Modifying the boot image violates the digital signature of the system, and the update server will refuse to install the patch. You will have to download the full firmware and install it manually, re-patching the boot image.
Which smartphone models are easiest to root?
The leaders in simplicity are Google Pixel, OnePlus and Xiaomi (after waiting). The most difficult thing is with devices from Huawei, Honor and some Motorola models, where there are no official unlocking tools.