The presence of root access (superuser rights) on the device Android opens up wide opportunities for customization, removing system garbage and fine-tuning performance. However, in some cases there is an urgent need to return the smartphone to its original, “clean” state. Banking applications stop working due to SafetyNet protection, online games block access, and warranty service becomes impossible.
The process of removing administrator rights, often called “unroot,” is not simply removing one icon from the desktop. This is a complex procedure that affects the system partition boot.img and configuration files. Incorrect intervention can lead to a software failure or complete inoperability of the device (bootloop).
In this guide, we will examine in detail all the current methods for relinquishing superuser rights. We will consider both the standard functions of access managers and more radical methods of flashing stock images, which are guaranteed to clear the system of any traces of modification.
Preparation of the device and risk assessment
Before proceeding with the removal root access, you need to make sure that the device is ready for the procedure. The first step is to create a complete backup of all important data. Even if the method seems safe, the risk of losing personal files, contacts and messages always exists.
Use built-in tools Google or third-party utilities for backup. Pay special attention to application data that may be lost during a factory reset. It is also recommended to charge the smartphone battery to at least 70-80% to avoid a power outage at the critical moment of writing system partitions.
⚠️ Attention: Removing root access on devices with an unlocked Bootloader does not always return the device's security status. Some banks and applications may still show signs of tampering.
Check your current bootloader lock status. If it was unlocked specifically to gain administrator rights, simply deleting Magnitude or SuperSU will not close it back. To fully return to the factory state, you may need to re-lock, which on some models (for example Sony or old Moto) can lead to the loss of DRM keys and deterioration in the quality of the camera.
☑️ Checklist before deleting root
Removal method through the app Magisk
Today Magisk is the de facto standard for obtaining and managing superuser rights. The developer has provided a built-in function for completely removing root access without the need to manually flash the device. This method is considered the most secure and preferred by most users.
Open the application Magisk Manager on your device. In the main menu, in the block displaying the current installation version, you will find a button labeled “Uninstall”. Clicking this button launches a cleanup script that automatically restores the original boot image and removes the binaries. su.
The process may take several minutes, during which the screen may turn off and on. Do not interrupt the application. Once the procedure is complete, the device will prompt you to reboot. It is after the first restart that the changes take full effect and the administrator's rights disappear.
What to do if the delete button is inactive?
If the "Delete" button is gray or cannot be pressed, check whether the "Zygisk" mode is enabled or whether modules are installed that block the work of the manager. Try putting the device into safe mode and try again.
It is important to understand that this method is only effective if the system has not been subjected to deep modifications beyond standard rooting. If you have modified system files manually or installed modified kernels, using the standard uninstall function may not return the device to a completely stock state.
ℹ️ Please note: The interface and button layout of applications may change with updates. Always check the official Magisk developer guide if the standard path does not work.
Clearing rights using SuperSU
For owners of older devices or those who use the classic manager SuperSU**, the procedure is also as simplified as possible. This application has been a market leader for a long time and contains a reliable mechanism for completely renouncing privileges.
Launch the application SuperSU** and go to the "Settings" section. Scroll down the list of options to the Cleanup block. Here you are interested in the option “Full Unroot”. Selecting this item initiates the process of restoring stock launch files.
After confirming the action, the application will delete the binary file su, application SuperSU and restore the original boot.img. The device will automatically reboot. Upon completion of the process, it is recommended to delete the apk file of the application itself SuperSU manually through the file manager, since it is no longer needed.
If after removing SuperSU there are traces left in the system, use a file manager with rights (before deleting the root) to check the /system/xbin/ and /system/bin/ folders for the presence of su files.
It is worth noting that support for SuperSU** has been officially discontinued, and on new versions Android (starting from 10 and higher) this method may not work correctly or be completely unavailable. In such cases, using Magisk is the only correct solution.
Manual removal via ADB and Fastboot
If automatic methods did not work or the manager application was removed earlier, you will have to resort to manual intervention using a computer. This method requires the package to be installed ADB and Fastboot on the PC and USB debugging enabled on the smartphone.
The essence of the method is to directly flash the stock image of the boot partition. You need to find the official firmware image (factory image) specifically for your device model and version Android. You need to extract the file from the archive with the firmware boot.img.
Connect the phone to the computer in bootloader mode (Fastboot mode). This is usually done using a key combination Volume Down + Power with the device turned off. In the command line on your PC, enter the following command to record the original image:
fastboot flash boot boot.imgAfter successful recording, enter the command fastboot reboot to reboot the device. This method is guaranteed to remove any kernel modifications associated with obtaining root access, since it replaces the modified partition with the factory one.
| ADB/Fastboot command | Purpose | Error risk |
|---|---|---|
adb devices |
Checking device connection | Low |
fastboot devices |
Checking bootloader mode | Low |
fastboot flash boot boot.img |
Write stock kernel | High (if the file is incorrect) |
fastboot reboot |
Reboot to system | Low |
Using the wrong boot.img file from a different model or version of Android can turn your smartphone into a “brick”. Always check the compatibility of the image.
Return to factory settings (Factory Reset)
The most radical, but often the most effective way to get rid of traces of root access is a complete data reset (Wipe Data/Factory Reset). However, it is important to understand the nuance: a simple reset through the settings menu does not delete root access if the system partition is modified.
To achieve the result, you must perform a reset through the Recovery mode, after making sure that you are not using a custom recovery (for example, TWRP). If a custom recovery is installed, it must also be replaced with a stock one via Fastboot, otherwise the reset will not affect system privileges.
After replacing the recovery with a factory one, enter recovery mode (usually Volume Up + Power) and select Wipe data/factory reset. Confirm the action. This will delete all user data and applications, returning system settings to their original values, as far as the current firmware allows.
⚠️ Attention: A complete data reset destroys all information in the internal memory. Photos, documents and correspondence will be lost forever if a backup is not made.
This method is often used in conjunction with flashing the stock image. It provides a "clean slate" by removing cache, temporary files and remnants of settings that could conflict with the operation of applications after root removal.
Checking the result and troubleshooting
After completing all procedures, you need to verify the success of removing administrator rights. There are several ways to check if your smartphone is still “clean”. The simplest is to try to open an application that requires root, or specialized software for verification.
Install the application Root Checker from the store Google Play. Launch it and click the test button. If the rights are successfully removed, the app will display a message stating that the device does not have root access. You can also try launching a terminal and entering the command su. If access is denied or the command is not found, the goal has been achieved.
If banking applications still refuse to work, the problem may lie not in the rights themselves, but in the unlocked bootloader or residual files. In such cases, clearing the application cache through the settings menu or re-locking the bootloader (if the device model allows it) helps.
Sometimes after removing root, errors may occur in the operation of system functions that were previously modified. In this case, the only solution is to completely flash the device with official software via a computer (for example, via Odin for Samsung or SP Flash Tool for MediaTek).
Frequently asked questions (FAQ)
Will the warranty be removed after removal root access?
Physical removal of superuser rights does not automatically restore the warranty. Many service centers have technical means to detect the fact of previous interference in the software (triggering of the Knox counter on Samsung, changing bootloader flags) The decision on warranty repair is made individually.
Is it possible to remove root without losing data?
Yes, when using methods through applications Magisk or SuperSU** user data is saved. However, methods using Fastboot and flashing stock images, as well as a full reset (Factory Reset), lead to the complete deletion of all data from the internal memory.
Why does the bank application write? "root detected" after uninstallation?
Modern banking application security systems check not only the presence of a binary file subut also the status of the bootloader, the presence of custom recovery and the integrity of system partitions. If the bootloader remains unlocked, the application can block the operation.
Is it safe to block. bootloader after removing root?
It is safe to block the bootloader only on completely stock firmware. An attempt to block the bootloader with a custom recovery or a modified kernel will result in the device stopping booting (hard brick). Always return all partitions to the factory state before blocking.
Is it necessary to remove the Magisk application after the procedure? Unroot?
When using the "Full Uninstall" function inside the Magisk application, it removes itself automatically during the reboot process. If you used manual methods, the application must be uninstalled manually as a regular app.