Getting root rights on Xiaomi smartphones opens up access to hidden system functions, but users often forget whether they have unlocked them before β especially after flashing or resetting settings. You can check for root in several ways: from installing specialized applications to executing commands through ADB or built-in terminal. It is important to understand that even if you did not install the root yourself, it could appear after using some custom firmware or βsingβ utilities to unlock the bootloader.
In this article, we will discuss 5 reliable methods of verification, including visual features in the MIUI interface, system file analysis and testing through Fastboot. We will pay special attention to the nuances for different models - from Redmi Note 12 to flagship Xiaomi 14 - as the manufacturer regularly tightens protection. If you plan to get a root or just want to make sure that the device is safe (for example, after buying a used phone), these instructions will help to avoid errors.
1. Visual signs of root rights in MIUI
Before you get into the technical details, check the interface of the smartphone, some changes appear automatically after obtaining the root rights and can serve as indirect confirmation:
- πΉ Superuser icon in the notification panel (most often a shield with an exclamation point or an inscription) SU).
- πΉ Magisk Manager or SuperSU app in the app menu (even if it is hidden, it can be found through a search system).
- πΉ Warning about modified firmware when running banking applications (for example, Sberbank Online or Tinkoff can block the entrance).
- πΉ Absence OTA-Updates: After the root, the system often stops offering updates over the air".
If one of these features is present, the probability of root is 80-90%, but visual methods do not provide a 100% guarantee - some firmware can mask the root, and icons can be hidden through the launcher settings.
2. Checking through applications (without technical skills)
The easiest way is to use Google Play's specialized tools, which analyze system files and give a clear answer about root rights status, and we recommend three proven tools:
| Annex | precision | Features | Reference |
|---|---|---|---|
| Root Checker | 95% | Shows a version of su-binary, supports Magisk | Google Play |
| Root Validator | 90% | Tests access to system folders, works without the Internet | Google Play |
| MIUI Hidden Settings | 85% | Shows hidden firmware parameters, including bootloader status | APKMirror |
Instructions for using Root Checker:
- Download and install the application from the official store.
- Open it and press Verify Root Access.
- Wait for the result: green tick - rue is, red cross - no.
- If you receive a request for granting superuser rights, confirm it (this is normal).
β οΈ Note: Some applications (such as Titanium Backup) can also check the root, but their main function is to back up. Use them only if you trust the download source.
Make sure your phone is over 30% charged
Disable VPNs and proxy (they can block access to system files)
Close all background applications (especially antiviruses)
Allow installation from unknown sources (if downloaded) APK)-->
Verification through ADB (for experienced users)
If apps donβt give a definitive answer or you donβt trust them, use Android Debug Bridge (ADB), a debugging tool that is part of the Android SDK. This method works even if the root is hidden from standard checks.
You'll need:
- π₯οΈ Computer with Windows/Linux/macOS.
- π USB-cable (preferably original).li>
- π± Included debugging by USB on a smartphone (Settings) β The phone. β Version. MIUI (click 7 times) β Additionally. β For developers β Debugging by USB).
Steps of verification:
- Download ADB Tools and unpack the archive.
- Connect your phone to your PC and go to the command line (terminal) folder with adb.exe.
- If you enter su, the cursor moves to a new line with the #-root symbol. If you see a message Permission denied, no rights.
On Xiaomi smartphones with MIUI 14+, the su command may not work even if there are root due to additional protection.
adb shell"echo'id' | su"π‘
If ADB Does not recognize the device, try reinstalling Xiaomi drivers USB Drivers or using other drivers USB-port (preferably) USB 2.0).
4. Manual check of system files
Root rights leave traces in Android system folders. If you have a file manager with access to the root directory (such as Solid Explorer or FX File Manager), check for the following files and folders:
- π /system/bin/su or /system/xbin/su β primary binary.
- π /system/app/SuperSU or /system/priv-app/SuperSU β SuperSU application folders.
- π /data/adb/magisk β Magisk directory (if the root is obtained through it).
- π /data/local/tmp/rooted β a temporary file created by some utilities to unlock.
How to check:
- Open the file manager and enable the display of hidden files.
- Go to the root directory (/) and manually check the paths from the list above.
- If files are found, the root is installed. If there are no folders or access is denied, there are no superuser rights.
β οΈ Note: Do not delete or edit the files you find without understanding the consequences! This can lead to data loss or device blink (especially if you are talking about files in the file file file). /system).
What if there are files but apps canβt see root?
5. Check through the terminal on the smartphone itself
If you donβt have access to a PC but have a terminal application (like Termux or MIUI Terminal), you can do a check on the device.This method is suitable for Xiaomi with an unlocked bootloader, even if the root is hidden.
Instructions for Termux:
- Install Termux from F-Droid (the version from Google Play may be outdated).
- Start the application and enter alternately the commands: pkg update & & pkg upgrade pkg install tsu tsu tsu
- If you change the cursor to # after tsu, the root is active. If you get tsu: not found, no rights.
For the built-in MIUI terminal (available on some models via Settings β Additional β Terminal):
su
idIf you see uid=0(root) in the id response, the rights of the superuser are confirmed.
π‘
Terminal methods are most reliable, as they address the system kernel directly, bypassing the limitations of MIUI.
6. Check the status of the bootloader (bootloader)
On Xiaomi smartphones, the presence of an unlocked bootloader often correlates with root rights, although this is not always interrelated.
- Turn off the phone.
- Press the Power button + Volume down before the Fastboot logo appears.
- Connect the device to the PC and enter in the terminal: fastboot oem device-info
- Find the Device unlocked: true string. If you have one, the bootloader is unlocked, which increases the likelihood of having root.
On newer models (Xiaomi 13/14, Redmi Note 12) instead of fastboot oem device-info use:
fastboot getvar unlockedβ οΈ Note: An unlocked bootloader does not mean root by itself, but it is unwarranted and may block some features (e.g. Google Pay or Widevine). L1 for Netflix HD).
7. Frequent errors and their solutions
When root-rights are checked, users often encounter false results, and let's look at the typical problems and ways to fix them:
| Problem. | Possible cause | Decision |
|---|---|---|
| The app shows the root, but the su commands don't work. | Root is installed but not activated in Magisk or SuperSU | Open Magisk Manager β Install β Direct Install |
| ADB does not see the device | No drivers or only charging mode enabled | Install Mi PC Suite or switch USB mode to File Transfer |
| The terminal gives Permission denied when entering su | SELinux in Enforcing mode blocks access | Try setenforce 0 (temporary shutdown of protection) |
| The /system/bin/su file is available, but the root is not working. | Binary is damaged or blocked by MIUI | Reinstall the root via Magisk or TWRP |
If none of the methods gave a definite result, but you suspect the presence of root (for example, after buying a used phone), try:
- π Install 3C Toolbox and check the Root Management section.
- π Run adb shell getprop ro.boot.verifiedbootstate β if the answer is orange, the bootloader is modified.
- π Check for a custom recavΓ©rie (TWRP) Adb Reboot Recovery Command.