Verifying the presence of root rights on Xiaomi smartphones is a challenge that both beginners and experienced users face after buying a used device or installing custom firmware. The absence of visual features (for example, the SU icon in the notification panel) does not guarantee that superuser rights are disabled: they could be hidden through Magisk Hide or rolled back to factory state while maintaining root access. In this article, we will discuss 5 reliable verification methods, including analyzing system files and ADB commands, which work even on the latest versions of MIUI 14/15 and HyperOS.
It is important to understand that the presence of root rights affects the security of the device: banking applications (for example, SberBank Online or Tinkoff) can block work, and some system updates MIUI refuse to install on rooted devices without first removing the rights of the superuser.
1. Verification through specialized applications
The easiest way is to install a utility that scans the system for root access, which analyzes the presence of su binary files, checks the rights to write to system partitions, and tests execution of commands on behalf of the superuser.
Among the reliable solutions:
- π Root Checker (from joeykrim) is a classic open source application that supports verification through Magisk and SuperSU.
- π‘οΈ Root Validator β additionally tests the integrity of system partitions and detects traces of rooting even after they are hidden.
- π± MIUI Hidden Settings β a utility for Xiaomi that shows hidden system parameters, including the status of root rights.
How to check:
- Download one of the apps from Google Play or APKMirror (if Play Market blocks installation on a rooted device).
- Launch the program and press the Verify Root button (or similar).
- Wait for the result: a green checkmark or the inscription Root access: Yes will confirm the rights.
β οΈ Note: Some applications (such as Magisk Manager) may mask root status for individual programs. If the check shows no rights but you suspect them, use the methods in the following sections.
2. Manual verification through file manager
If you have a file manager with root folder access (such as Solid Explorer, FX File Explorer, or MiXplorer), you can manually look for rooting signs. This method does not require installing additional applications, but requires care.
What to look for:
- π File. /system/bin/su or /system/xbin/su β main marker of classical rue.
- π folder /magisk or /data/adb/magisk β Points to Magisk installation (popular root rights manager).
- π Files busybox or supolicy in /system β auxiliary utilities, often installed with root access.
Instructions:
- Open the file manager and enable the display of hidden files (the option is usually in the settings).
- Go to the root directory (/) and check the paths from the list above.
- If files are found, but access to them is blocked - this is an indirect confirmation of root rights (the system restricts access for non-rooted users).
Enable the display of hidden files
Check the folder /system/bin/
Check the /magisk/ folder
Try to open the file /system/xbin/su
-->
On some firmware (e.g. HyperOS), system files can be encrypted, in which case only checking through ADB or terminal will help.
Verification through ADB (for experienced users)
Android Debug Bridge (ADB) is a debugging tool that allows you to execute system-level commands, and it can help you determine exactly whether your device has root rights, even if they are hidden.
What you need:
- π₯οΈ Computer with installed ADB Tools (part of Android) SDK).
- π± Included debugging by USB on a smartphone (Settings) β The phone. β Version. MIUI β 7 times press to activate the developer mode, then Settings β Additionally. β For developers β Debugging by USB).
- π Cable USB (preferably original).
Teams to check:
adb shell
suIf, after entering su:
- πΉ The course has changed to # (instead of #) $) β root-rights.
- πΉ A message from Permission Denied β No rights.
- πΉ The device requested confirmation in the app (e.g., Magisk) β root is there but hidden.
β οΈ Note: On some Xiaomi bootloader-locked devices, the su command may not work even if you have root rights:
adb shell "echo 'test' > /data/local/tmp/test.txt && echo 'Root confirmed'"If a test.txt file is created, the superuser rights are active.
What if the ADB canβt see the device?
4. Verification through the terminal on the device
If you don't have access to a computer, you can use the terminal directly on your smartphone, and applications like Termux (without root rights) or MT Manager (with root access support) will do this.
Steps for Termux:
- Install Termux from F-Droid (the version from Google Play may be outdated).
- Enter the command: pkg install tsu tsu
- If the cursor has changed to # after tsu, the root rights are confirmed.
For a deeper check, do:
ls -l /system/bin/su
ls -l /system/xbin/suIf files exist and the answer has a string with rwsr-xr-x, it is a confirmation of root access.
In MT Manager, the process is even simpler:
- Open the app and go to the Terminal section.
- Enter su and press Enter.
- If you have a request for rights, you have root, and if you don't have a request and the command doesn't work, you don't have rights.
π‘
If the terminal produces a command not found error, update the PATH variables with the command export PATH=/system/bin:$PATH before checking.
5. Indirect signs of root rights in MIUI/HyperOS
Even without technical checks, you can suspect root rights to the behavior of the system. Xiaomi has integrated several mechanisms into MIUI and HyperOS that respond to rooting:
| Sign. | What does it mean? | How to check |
|---|---|---|
| Lack of OTA updates | MIUI blocks updates "over the air" on rooted devices. | Go to Settings β About Phone β System Update. If the Check Update button is inactive or gives an error, it may be root. |
| SafetyNet reset | Banking apps and Google Pay are no longer working. | Install SafetyNet Test from Play Market and run the check. FAIL status on CTS Profile Match indirectly indicates root. |
| Availability of unknown applications | Applications like Magisk Manager, SuperSU or BusyBox. | Check the list of installed programs in Settings β Applications β Application Management. |
| Modified system fonts/icons | Root allows you to modify theme system files. | Compare the appearance of the interface with stock screenshots of your model on the official Xiaomi website. |
Please note that some of these features may also be present for other reasons (such as custom firmware without a root or an error in Google Services) and should therefore be considered only in conjunction with other verification methods.
Verification through the engineering menu (hidden method)
Xiaomi devices have a hidden engineering menu that can provide information about bootloader status and system modifications, a technique that doesnβt work on all models, but could be useful for Qualcomm-based devices.
How to open the engineering menu:
- Open the Phone app.
- Enter the code ##4636##
- Go to the phone information section.
- Scroll down and find the Bootloader or Root Status strings.
What to look for:
- π Bootloader: Unlocked β the bootloader is unlocked (not necessarily a root, but increases its probability).
- π οΈ Root Status: Yes or Modified: True is a clear confirmation of the root rights.
- π System Status: Custom β custom firmware installed, which often implies root.
β οΈ Note: On new HyperOS devices, the engineering menu may be blocked or not displaying root status information.
π‘
If the engineering menu is not available but you suspect root rights, the combination of ADB verification and system file analysis gives 99% accuracy.
Frequent errors and myths about root rights verification
When diagnosing root access, users often experience false positives or miss obvious signs.
Myth 1: βIf there is no SuperSU badge, there is no root.β
In fact: Apps like Magisk can hide icons and processes from displaying in the launcher. Check for files manually or through ADB.
Myth 2: βSafetyNet passes, so there is no root.β
In fact: Modern cloaking techniques (like MagiskHide or Universal SafetyNet Fix modules) allow you to bypass Google checks while maintaining root access.
Myth 3: βIf MIUI updates are installed, there is no root.β
In fact: Some custom firmware (e.g. xiaomi.eu) support OTA-Update even with root rights. Check the status of the bootloader and system files.
Mistake 1: Using outdated applications
Apps like Root Checker Basic (not to be confused with joeykrim's Root Checker) may not recognize Magisk or new rooting methods. Always use current versions of the utilities.
Error 2: Ignoring the unlocked bootloader
An unlocked bootloader does not itself give root rights, but it makes it much easier to get them. If the bootloader is unlocked, there is a high probability that the previous owner installed the root.