Obtaining superuser rights, or root access, opens up limitless possibilities for the smartphone owner to customize the system. However, this often leads to unstable operation of the device, inability to launch banking applications and loss of warranty. A logical question arises about how to return the gadget to its original state and close security vulnerabilities.
The process de-rooting can vary from simple settings within the application to complex flashing of the device. The choice of method depends on how the privileges were obtained and whether the bootloader was flashed. In this material we will analyze all the current methods of returning to the stock system.
Preparing for the procedure for removing rights
Before taking any action, you must create a complete backup copy of all important data. Removing root access often involves full reset or flashing, which will inevitably lead to the loss of user information. Do not rely on cloud services to save everything, use local copying to your computer.
Be sure to make sure that the battery level is at least 70-80%. Interrupting the process of writing system partitions due to a low battery may result in the device turning into a “brick”. You will also need a stable USB connection and ADB drivers installed on your computer if you plan to use PC-related methods.
☑️ Checklist before you begin
It is important to understand the difference between simply hidden root access and its complete removal. Some methods only mask the presence of rights for specific applications, while others physically delete binary files su from the system partition. To fully restore the guarantee and operation of banking services, physical deletion is required.
Removal through the SuperSU application
If you used the classic application to obtain rights SuperSUthe return process will be as simple as possible. The developer of Chainfire has provided a built-in full rights removal function that automatically cleans system files and restores the stock bootloader if it has been modified by this application.
Go to the application settings and find the “Full Unroot” item. After pressing the button, the device will reboot and the rights will be revoked. This method is considered one of the safest, since the application itself controls the process of rolling back changes made to the file system.
Before using the Full Unroot function in SuperSU, make sure that you have not installed third-party recovery images manually, since the standard function may not restore the original bootloader in such cases.
It is worth noting that on modern versions of Android, especially starting from 10 and above, this method may not work correctly due to changes in the structure of system partitions and the introduction of the Project Treble mechanism. In such cases, it is better to consider alternative cleaning options.
Cleaning the system when using Magisk
Users of the utility Magisk are in a more advantageous position due to the modular structure of the app. There is no need for a complete flashing to remove rights; it is enough to use the built-in full uninstallation function. This allows you to restore system integrity without losing data if the bootloader has not been unlocked at the hardware level.
Open the Magisk application and select the "Remove Magisk" button in the main menu. The system will offer several options, among which you need to select “Complete removal”. After confirmation, the smartphone will automatically reboot and all traces of modification to the system partition will be deleted.
What is Zygisk and how does it affect deletion?
Zygisk is an implementation of Magisk in the Zygote process space. Uninstalling Magisk also removes Zygisk components, which may require you to reinstall applications that depend on that environment if you used them for other non-root purposes.
⚠️ Note: If you unlocked the bootloader before installing Magisk, simply deleting the application will not lock it back. To fully return to the factory state, you will need to re-lock via Fastboot, which is only possible on stock firmware.
An important advantage of Magisk is the ability to use the "Uninstall" function even if the system does not boot, by flashing a special script through custom recovery. This saves the device in situations where a system update has led to a conflict with superuser rights.
Resetting to factory settings as a cleaning method
On many devices, especially from Chinese manufacturers like Xiaomi or Meizu, obtaining root access is often done through the built-in developer tools. In such cases, going back to factory settings through the Recovery Mode can completely clear the data and cache partitions, removing root binaries.
To enter Recovery Mode, you usually use a combination of the Power and Volume keys. In the menu you need to select the item Wipe Data/Factory Reset. This process removes all user data and settings, returning the phone to its out-of-the-box state, with the exception of system updates received over the air.
However, this method is not always effective if root was injected directly into the system partition /system. In such situations, after a reset, rights may return automatically upon the first boot, since the modified system image remains intact.
| Method | Saving data | Efficiency | Complexity |
|---|---|---|---|
| Unroot function in the application | Yes | High | Low |
| Reset via Recovery | No | Medium | Low |
| Flashing with stock | No | Maximum | High |
| Manual removal files | Yes | Low | Very high |
Returning stock firmware via Fastboot
The most radical and reliable way to remove rooting is to completely flash the device in an official manner. This method guarantees the removal of any modifications, including custom kernels and modified bootloaders. You will need to find an official firmware image specifically for your model and device revision.
The process is carried out in Fastboot or Download Mode, depending on the manufacturer. For devices on Qualcomm chips, the command fastboot flash is used to write partitions. It is important to strictly follow the instructions for a specific model, since incorrectly recording partitions can disrupt the operation of the modem or camera.
fastboot flash boot boot.imgfastboot flash system system.img
fastboot reboot
After flashing the stock image, the bootloader will automatically return to a locked state (on devices where this is provided for by the manufacturer's policy). This will restore security features such as Google Pay and banking applications that require system integrity.
⚠️ Attention: When flashing via Fastboot, make sure you are using images that match the current regional firmware version. Incompatibility may lead to the loss of the VoLTE function or NFC inoperability.
Flashing with a stock image is the only way to guarantee the factory lock of the bootloader (Relock Bootloader), which is critical for the operation of some DRM services.
Manual deletion of files via ADB
For advanced For users who do not want to reflash the entire device, there is a method of manually deleting files through the ADB console. This method requires having root access at the time of starting the operation and understanding the structure of the Android file system.
You need to connect the smartphone to the computer, launch the command line and gain access to the shell. Then you should find and delete executable files su, which are usually located in directories /system/bin/, /system/xbin/ or /sbin/. You also need to remove control applications, such as Superuser.apk.
After deleting the files, you need to change the access rights to the system partitions back to read-only using the command mount -o remount,ro /system. An error at this stage can lead to a cyclic reboot of the device, since the system will not be able to mount the partitions correctly.
Why is manual removal dangerous?
When manually deleting, people often forget to clear the initialization files (init.d) or startup scripts that try to call a non-existent su binary at boot, which leads to a bootloop (looping on the logo).
Checking the result and security
After completing all procedures, you need to make sure that the rights are actually removed. To do this, you can use specialized applications from Google Play, for example, Root Checker. Launching such a utility will show the status of superuser access.
If the application reports that there is no root, check the operation of banking clients and contactless payment services. Sometimes additional data cleaning of the applications themselves is required so that they “forget” about the previous status of the device and allow entry.
⚠️ Attention: Even after removing root, if the bootloader remains unlocked, some applications may still refuse to work. In this case, the Relock Bootloader procedure is required, which is only available on stock firmware.
Regularly check for system security updates. Reverting to stock firmware allows you to receive official security patches from the manufacturer, closing vulnerabilities that could be opened if you have superuser rights.
After removing root, it is recommended to completely clear the application cache through the storage settings to remove remnants of configuration files related to access rights.
Frequently asked questions (FAQ)
Will the warranty be removed after removing root?
Physically removing root access and returning stock firmware can often hide the fact of tampering with the system. However, if the Knox counter (on Samsung) or a similar fuse was tripped, the hardware warranty may be permanently voided, regardless of the current state of the software.
Is it possible to unroot without losing data?
Yes, using the "Full Unroot" features in SuperSU or Magisk usually allows you to save user data. However, creating a backup copy before any manipulation is a mandatory security rule.
Why does the banking application not work after unrooting?
The application may cache information that the device has been compromised. Try clearing the cache and data of the banking application, and also make sure that the device's bootloader is locked.
Is it dangerous to leave an unlocked bootloader without root?
Yes, an unlocked bootloader reduces the security level of the device, allowing attackers with physical access to flash malware. For maximum protection, it is recommended to block the bootloader after removing root.