Obtaining superuser rights on devices under control Android 10 has ceased to be a simple formality, turning into a multi-step process that requires a deep understanding of the architecture of the operating system. Unlike earlier versions, where there were single-file patchers, modern Google security algorithms require an individual approach to each device. root access open access to the system partition, allowing you to remove pre-installed software, modify the kernel and run specialized applications.
However, the procedure is associated with serious risks, including the possibility of turning a smartphone into a “brick” or disrupting banking services. You need to be clearly aware that any manipulations with the bootloader and system files will void the device's warranty. Below we will examine in detail the technical side of the issue, methods of bypassing protection and ways to minimize potential damage.
Preparation of the device and diagnostics of the model
The first and critically important step is to accurately determine the model of your gadget and the firmware version. There is no universal tablet in the world, so you will need to know the exact code name of the device, which often differs from the marketing name. Go to Android There is no universal tablet, so you will need to know the exact code name of the device, which is often different from the marketing name. Go to Settings → About phone and tap on the build number several times to activate the developer menu.
Then enable USB debugging, which will allow the computer to exchange commands with the smartphone's operating system. Without this step, further actions are impossible, since the standard interface does not provide access to low-level functions. You also need to activate the "Factory Unlocking" (OEM Unlocking) item, if it is available in your region and by your telecom operator.
⚠️ Attention: On some devices from American operators or Chinese versions of Xiaomi, the OEM Unlocking item may be missing or blocked by software. In this case, obtaining superuser rights without opening the case and using programmers is impossible.
Make a complete backup copy of all important data, since the process of unlocking the bootloader will inevitably lead to the complete deletion of information from the internal drive. Use cloud services or connect the device to a PC to copy photos and documents. Make sure that the battery charge is at least 60% to avoid sudden shutdown at a critical moment.
- 📱 Exact device model and Android version
- 🔌 USB cable with support for data transfer (not only charging)
- 💻 Computer or laptop with ADB drivers installed
- 🔋 Battery charge is above 60%
Bootloader Unlock
The foundation for implementing superuser rights is an unlocked bootloader, which is locked by default by the manufacturer for security reasons. This is a gateway that verifies the digital signatures of all running system components. To start the procedure, put your smartphone into Fastboot mode, usually this is done by using a combination of the volume and power buttons when the device is turned off.
Having connected the phone to the computer, open the command line and enter the command to check the status: fastboot oem device-info. If you see the value Device unlocked: false, it means the blocking is active. Xiaomi devices require obtaining a special token through the official Mi Unlock application, which may take from 3 to 7 days of waiting.
fastboot flashing unlockAfter entering the unlock command, a risk warning will appear on the smartphone screen. Confirm the action using the volume buttons. The process will take a few minutes, after which the device will reboot and perform a factory reset. Bootloader Now open to changes, making it possible to install a modified recovery or direct kernel patch.
⚠️ Attention: Unlocking the bootloader on Samsung devices activates the Knox counter, which irreversibly changes the security status eFuse. This permanently disables Samsung Pay, Secure Folder and some banking applications, even if you return the stock.
Toolkit: Magisk versus old methods
The era of the SuperSU superuser is irrevocably gone, and the de facto standard for Android 10 and became higher Magisk. The main advantage of this solution is the systemless root system, which does not directly make changes to the system partition. This allows you to hide the presence of rights from banking applications and Google Play services, which was not possible with older methods.
Magisk works by modifying the boot image (boot.img), injecting its code into RAM when the system boots. This means that system files remain unchanged, making it easier to unroot or update the operating system over the air (OTA). You will need to download the latest version of the APK file from the official GitHub repository.
| Features | Magisk (Modern) | SuperSU (Legacy) |
|---|---|---|
| Deployment method | Systemless (without system changes) | Modification of the system partition |
| Hide from banks | Built-in function (MagiskHide/Zygisk) | Ineffective or impossible |
| Support for Android 10+ | Full | Absent |
| Modules | Supported | Not supported |
Except manager itself, you may need a custom recovery such as TWRPif the patch method through the app does not work. However, for most modern Android 10 devices, the method of directly patching the boot image is preferable, since it is less prone to compatibility errors. Zygisk This is a new technology inside Magisk that allows you to inject code into the Zygote process, which is necessary for the operation of many modern modules.
Boot image patching process
The most reliable way to get rights to Android 10 is to modify the original boot image of your firmware. You need to find and download the complete stock firmware archive that exactly matches the version installed on your smartphone. A version mismatch can lead to a bootlap (cyclic reboot).
Extract the file boot.img from the firmware archive and transfer it to your smartphone. Launch the Magisk application, select "Install" and then "Select and patch file". Specify the previously extracted image, and the application will create a modified version in the Download folder with the prefix patched_.
fastboot flash boot patched_boot.imgAfter patching is complete, return the file to your computer and flash it through Fastboot mode using the command above. For devices with A/B separation (slot system), the command may be different, requiring a specific slot to be specified. After successful flashing, run the command fastboot reboot to reboot.
⚠️ Attention: Never try to flash a boot image from another model or another version of Android. This is guaranteed to lead to inoperability of the device, the restoration of which will require paid service tools.
Installing custom Recovery (TWRP)
An alternative, but more risky way is to install a modified recovery menu, such as TWRP. This method is often necessary if the standard bootloader does not allow you to patch the image directly or if a complete wipe of partitions is required. Find the file twrp.imgcreated specifically for your device model.
Firmware is carried out by command fastboot flash recovery twrp.img. However, on devices with Android 10, protection has been introduced that can overwrite the custom recovery with the stock one on the first boot. To avoid this, after flashing TWRP, you need to immediately, without booting the system, go to Recovery mode and install a Magisk ZIP archive or patchboot.
Using custom recovery provides additional features, such as creating full system backups (Nandroid backup) and clearing the Dalvik cache. It's a powerful tool in the hands of an experienced user, but it requires care when navigating the menus. An error in choosing a partition for formatting (for example, Data instead of Cache) will lead to data loss.
- 🔄 Ability to create full copies of the system
- 🗑️ Deep cleaning of partitions before installing mods
- 📦 Installing ZIP modules without loading into Android
- 🛡️ Risk of overwriting with stock recovery if done incorrectly
Checking rights and setting up Magisk
After the system has successfully booted, find the Magisk icon in the application menu. If it appears and the version is displayed in the application status, it means that root access is active. To check, you can use specialized applications from the Play Market, such as Root Checker, which will confirm the presence of superuser access.
However, simply obtaining root access is not enough - you need to configure their hiding. Go to Magisk settings and enable Zygisk feature. Then, in the “Customize exclusion list” (DenyList) section, mark banking applications, Google Pay and games with anti-cheat. This will force Magisk to hide root access from the processes of these applications.
It is also recommended to enable "Isolated Storage" for Magisk to hide the fact that the root access manager is installed. After making all changes, be sure to restart your device. Now your Android 10 has expanded functionality, while remaining compatible with most everyday services.
Possible problems and their solutions
When modifying the system to Android 10, users often encounter cyclic reboots or lack of Internet access. If your device is stuck on the logo, try booting into Recovery mode and running wipe cache/dalvik. In more complex cases, you will need to flash the stock boot image via Fastboot.
Internet problems may be associated with changes in hosts files or module conflicts. Disable all installed modules in safe mode (boot with the volume down button held down) and check the network. If the problem disappears, turn on the modules one by one to find the culprit.
What to do if the sound disappears after getting root?
Often modifying system files or installing audio modules leads to a driver conflict. Try removing recently installed audio-related Magisk modules. If this does not help, reflash the original boot.img. In rare cases, it is necessary to reset the sound settings in the engineering menu.
Is it safe to update the system over the air (OTA) with root access?
A regular OTA update on a rooted device will most likely not install or reset root access. Magisk allows you to save the root after OTA if you use the "Install in inactive slot" function. However, the safest thing to do is download the full firmware and update manually, saving the patched boot image.
Is it possible to remove Magisk and return everything as it was?
Yes, there is a "Full removal" button inside the Magisk application. It will restore the original boot image and delete all manager files. If access to the system is lost, it is enough to flash the stock boot.img via Fastboot, which will return the device to its factory state without losing the warranty on the hardware (but not on the software).