How to confirm root rights on Xiaomi: from applications to applications ADB-team

Getting root rights on Xiaomi smartphones gives you access to hidden system settings, allows you to remove embedded applications and optimize performance. However, after installing a custom recover or firmware with Magisk, it is not always clear whether superuser rights are successfully activated. This article will help you unequivocally confirm the presence of root on your device – from simple methods with applications to advanced verification through ADB and Terminal.

It’s important to understand that Xiaomi is actively blocking the ability to get root on new models (such as the Redmi Note 12 or POCO F5) through standard methods. If you used informal firmware or patches like Magisk, checking becomes a mandatory step before installing modules or changing system files, otherwise you risk getting a brick or losing your warranty.

We will cover methods for different scenarios, from visual verification via Root Checker to deep diagnostics via fastboot. We will pay special attention to the nuances for devices with a locked bootloader and MIUI of different versions (including MIUI 14 and HyperOS).

1. Root verification through specialized applications

The easiest way to validate a superuser's rights is to use Google Play utilities, which analyze system files and try to execute commands that require increased privileges.

• 📱 Root Checker (from joeykrim) is a classic application with support for Magisk and SuperSU. Shows the version of the binary su file and access status.
• 🛡️ Magisk Manager (official) – if you have Magisk installed, the app will show the status of modules and the patch version. On devices with HyperOS, you may need to adjust root hiding from banking applications.
• 🔍 Root Validator – checks not only the presence of rights, but also the integrity of system partitions (useful after firmware).

How to use Root Checker:

1. Download and install the app from Google Play.
2. Launch and press the Verify Root (or similar button).
3. Confirm the request for rights (if a pop-up from Magisk or SuperSU appears).
4. Wait for the result: green tick - root confirmed, red cross - no rights.

⚠️ Attention: On some firmware MIUI applications may show false positives due to built-in "fake root" for system processes. ADB (see section 3).

2. visual signs of root rights

Even without apps, you might suspect root for indirect reasons.

• 🔧 Developer settings: If in the menu Settings → The phone. → Version. MIUI (Click 7 times, Root access appears – rights are most likely active.
• 📁 File Manager: Try to open system folders (for example, /system or /data) Mi File Explorer or Solid Explorer, without root, no access will be allowed.
• 🚫 Banking applications: If SberBank Online or Tinkoff refuse to work with the error "device is rooted" - this is an indirect confirmation.
• 🔄 Updates MIUI: On rooted devices OTA-Updates are usually blocked with the message "Update is impossible due to changes in the system".

On new Xiaomi models (such as the Xiaomi 13T or Redmi K60), visual features may be absent even with root due to improved Magisk concealment.

Verification through ADB (for experienced users)

The Android Debug Bridge (ADB) tool allows you to perform low-level root-rights checks directly from your computer, which works even if there are no visual signs.

What you need:

• 🖥️ Computer with Windows/Linux/macOS and installed Xiaomi drivers.
• 🔌 USB-cable (preferably original).
• 📦 ADB Fastboot Tools by Google.

Instructions:

1. Enable USB debugging on your smartphone: Settings → About Phone → MIUI version (click 7 times), then Additional settings → For developers → Debugging over USB.
2. Connect your phone to your PC and confirm your request for trust in the device.
3. Open the command prompt (or Terminal) in the ADB folder and type:

adb shell


su

If after the su command:

• 🔹 The course has changed to # - root confirmed.
• 🔹 The message was “Permission denied” – no rights.
• 🔹 The phone requested confirmation in the window Magisk/SuperSU — rights but require manual permission.

⚠️ Note: On HyperOS devices, the su command may not work even if there is root due to a modified security architecture. In this case, use the alternative command: adb shell "magisk" --version" If the Magisk version is displayed, the rights are active.

USB debugging enabled

Installed drivers Xiaomi on PC

ADB added to the environment variables (or the folder is open in Terminal)

The phone is connected in the file transfer mode (MTP).

-->

4. Manual check of system files

If apps and ADBs don’t give a definitive answer, you can manually check for key root files, which you’ll need any root-enabled file manager (like FX File Explorer or Root Browser).

What files are we looking for?

If none of these files are available, but you are sure you have been flashing Magisk, try:

1. Reboot to the recavator (e.g. TWRP) and check the /data/adb folder.
2. Execute the command in ADB:

adb shell "ls -la /data/adb/"

On some firmware (for example, MIUI EU) If you use Xiaomi.eu, check the path as well. /system/addon.d/99-magisk.sh — This is a script to save root after OTA-update.

💡

If the file manager does not show hidden folders (starting from a dot), turn them on in the application settings. In Mi File Explorer, this is done through Settings → Show hidden files.

Verification via Terminal Emulator (no PC)

If you don't have access to a computer, you can check root directly on your phone via Terminal Emulator (download from Google Play), which works on all versions of MIUI and HyperOS.

Instructions:

1. Install and open Terminal Emulator (e.g. from Jack Palevich).
2. Enter the commands one by one:

su


whoami

Results:

• 🔹 If the cursor changed to # after su and the whoami team returned root, the rights are confirmed.
• 🔹 If there is a "su: not found" binary, there is no.
• 🔹 If nothing has happened after su, manual confirmation may be required in Magisk.

To check the Magisk version (if installed):

magisk -v

On HyperOS devices, you may need to allow access in Magisk settings first: open the Magisk app, go to Settings → Superuser, and enable the Allow for Terminal option.

💡

If the su command works but whoami returns your username (not root), it means that root access is restricted, as is the case on partial root firmware (e.g. some modifications of MIUI for POCO).

6. Diagnostics via Fastboot (for blocked downloaders)

On new Xiaomi devices (such as Xiaomi 14 or Redmi Note 13) with a locked bootloader, even successful Magisk firmware may not give a full root.

What to do:

1. Turn off the phone and press Volume Down + Power to log into fastboot.
2. Connect the device to the PC and execute the command:

fastboot getvar all

Look for the following parameters in the output:

• unlocked: yes – the bootloader is unlocked (a prerequisite for root).
• secure: no – the firmware signature check is disabled (allows modifications).
• verity: disabled – System integrity check disabled (required for Magisk)

If at least one of these options is missing or has a no/yes value (e.g. secure: yes), your root may be defective. This is typical for devices that are embroidered through Mi Flash without first unlocking the bootloader.

⚠️ Note: Some models (e.g. Xiaomi) 12S Ultra) even after unlocking the bootloader, the secure: yes parameter may remain due to hardware protection, in which case full root requires custom kernel firmware with the check disabled. AVB 2.0.

7. Frequent errors and their solutions

Even if you follow the instructions, there can be problems, and let's look at the typical scenarios and how to fix them:

If none of the methods worked, but you are sure you have been flashing Magisk, try:

1. Delete all Magisk data via Settings → Complete uninstallation.
2. Download the latest version of Magisk from the official GitHub.
3. Switch boot.img manually through fastboot:

fastboot flash boot magisk_patched.img


fastboot reboot

For devices with dynamic partitions (e.g. Xiaomi) 11T) Instead of boot, you may need to flash init_boot:

fastboot flash init_boot magisk_patched.img

FAQ: Answers to Frequent Questions