How to check the firmware version of Xiaomi through ADB: all manner

You can find out the firmware version on Xiaomi devices in a dozen ways, through your smartphone settings, the Updater app, or even through the phone box. But what if the phone doesn't turn on, the screen crashes, and access to the system is limited? ADB (Android Debug Bridge – a universal tool for interacting with Android devices via the command line.

This method is especially relevant for Redmi owners, POCO Mi, which faced a “brick” after a failed update, for developers testing custom firmware, or just for those who want to get the most accurate information about the version MIUI Android without a graphical interface, unlike the standard methods, ADB allows you to pull data even from a locked screen (when debugging is enabled on) USB) or devices in fastboot mode.

In this article, we will analyze not only the basic commands for checking the firmware version, but also the nuances of their operation on different Xiaomi models, possible errors, as well as alternative methods for obtaining information through fastboot and recovery. ADB — Don’t worry, we’ll start by installing tools and connecting the device.

What is it? ADB Why do you need it to check the firmware?

ADB (Android Debug Bridge is a bridge between your computer and your Android device that allows you to execute commands directly on the system:

• 🔧 The device does not turn on or hangs on the logo Mi/Redmi — through ADB Data can be obtained even in the "semi-bricked" state.
• 🔒 The screen is broken or does not respond to touch, but USB-debugging was included earlier.
• 🛠️ Custom firmware testing – checking the current version before installing a new one.
• 📱 Get advanced information that standard settings don’t show (such as bootloader or modem version).

It is important to understand that ADB It only works when the debugging is enabled. USB If this mode has not been activated in advance, connect to the device via ADB You will not be able to use fastboot (we will talk about it later).

⚠️ Attention: Teams ADB They require superuser rights (root) to retrieve some data (such as the bootloader version). On Xiaomi stock firmware, without unlocking the bootloader, these commands may not work.

Advantage ADB You can see the same thing before other methods, exactly the data. For example, if you use the settings on your smartphone, you'll only see the general version. MIUI (for example, MIUI 14.0.5), then ADB Can give you a full build number (V14.0.5.0.TKUMIXM), Android (13 TKQ1.220829.002), and information about the region of the firmware (Global/Russia/China).

Preparation for work: installation ADB and drivers

Before you check the firmware version, you need to configure the work environment.

1. A computer running Windows, macOS or Linux.
2. USB-cable (preferably original from Xiaomi to avoid connection issues).
3. Drivers for your model (for Windows – Mi) PC Suite or Universal Google Suite USB Drivers).
4. Package ADB Fastboot (can be downloaded from the official Google website or via the SDK Platform Tools).

The easiest way to install ADB:

1. Download. SDK Platform Tools from Google.
2. Unpack the archive in any folder (for example, C:\platform-tools).
3. Add a path to the folder to the environment variable PATH (For Windows, use the terminal with a full path (for Windows) macOS/Linux).

To check the installation, open the command line (Win) + R → cmd and enter:

adb version

If the output contains a version number (e.g. 1.0.41), the tool is ready to go.

⚠️ Attention: On Windows 10/11 You may need to disable driver signature verification for Xiaomi devices to work correctly, via gpedit.msc (for Pro versions) or special utilities like Driver Signature Enforcement Overrider.

How to enable debugging by USB on Xiaomi

Without activated debugging by USB connect to the device through ADB It's impossible. Here's how to turn it on:

1. Go to Settings. → The phone.
2. Click on MIUI Version 7 times until the notification “You are a developer!” appears.
3. Return to the main settings menu and open Additional settings → For developers.
4. Activate the debugging switch over USB.
5. Confirm the inclusion by pressing OK in the window that appears.

On some models (e.g. POCO F5 or Redmi Note 12), the path may be different:

• 📱 Settings → Memory. → (three-point) → Special facilities → For developers
• 📱 Settings → System system → Advanced settings → For developers

Once turned on, connect the device to your computer. On the smartphone screen, you'll see a request for debugging permission -- tick "Always allow from this computer" and click "Allow."

💡

If the device is not detected, try using another device. USB-port (preferably) USB 2.0) or disable all other USB-Sometimes it helps to reboot the phone with the cable connected.

Teams. ADB To check the firmware version of Xiaomi

Now, to the most important of all, the commands to get firmware information, all of which run on the command line (cmd for Windows or Terminal for Windows). macOS/Linux) after-connection.

Basic information on the system

A command to get general information about the device, including the Android version and MIUI:

adb shell getprop ro.build.version.incremental


adb shell getprop ro.miui.ui.version.name




adb shell getprop ro.build.version.release

Example of conclusion:

V14.0.5.0.TKUMIXM # MIUI version


13 # Android Version

2. Complete firmware build number

To find out the exact build (for example, to search for custom firmware):

adb shell getprop ro.build.display.id

The conclusion might look like this: TKQ1.220829.002.V14.0.5.0.TKUMIXM, where:

• TKQ1.220829.002 — Android version 13)
• V14.0.5.0.TKUMIXM — version MIUI (14.0.5 for Redmi Note 11, Global Region)

3. Region and device model

It is useful for determining the compatibility of firmware:

adb shell getprop ro.product.model # Model (e.g. "2201116TI")


adb shell getprop ro.product.brand # Brand ("Xiaomi", "Redmi", "POCO")




adb shell getprop ro.miui.region # Region ("ru" for Russia, "cn" for China)

4. Loader and kernel information

For advanced users:

adb shell getprop ro.boot.bootloader #Bootloader version


adb shell uname -a # Linux kernel version

Critical information: If the adb shell getprop ro.miui.region command returns cn, it means that the device has Chinese firmware installed. Installing the global or European (eea) version on top of it without unlocking the bootloader can lead to a “brick”.

Install ADB and drivers|Enable debugging on USB Xiaomi|Connect your phone to your PC with the original cable|Check the connection of the adb device team|Start the command line on behalf of the administrator-->

Alternative methods: Fastboot and Recovery

If debugging is on USB has not been enabled, and the device does not boot into the system, you can try to get information through other modes:

1.Through Fastboot

Transfer the device to fastboot mode (clip the power supply) + Volume down when the phone is turned off) and perform:

fastboot getvar all

Look for the lines:

• version-bootloader - version of the loader
• version-baseband - version of the modem
• product - device model

2. Through Recovery (TWRP/Stock)

If established TWRP, You can see the firmware version on the main menu. In the stock recovery (Mi Recovery), the information is displayed at the top of the screen:

• 📱 MIUI Global 14.0.5 | Android 13
• 📱 Redmi Note 11 (ginkgo)

For TWRP You can also connect through ADB even without a working system:

adb shell


cat /default.prop

⚠️ Note: Some Xiaomi models (e.g. Redmi) are fastboot mode 9A or POCO M3) They may not be able to display the version. MIUI. In this case, only unlocking the bootloader and installation will help. TWRP.

Common mistakes and their solutions

When working with ADB Users often encounter problems, and here are the most common ones and how to fix them:

1. Device not defined (no) devices/emulators found)

Causes and solutions:

• 🔌 Cable or port: Try another one USB-cable or port (preferably) USB 2.0).
• 🖥️ Drivers: Install the Mi PC Suite or manually update the driver through Device Manager (select Android) ADB Interface).
• 📱 Debugging: Make sure that the debugging is done USB enabled and enabled on the phone screen.
• 🔄 Reboot: Reboot your phone and computer.

2. Unauthorized Error (Unauthorized Device)

So that means that the computer has no debugging rights.

• 🔑 A request for permission will appear on the phone - confirm it.
• 📝 Delete the adbkey.pub file in the.android folder (for Windows: C:\Users\Your name android and reconnect.
• 🔄 Reinstall the drivers ADB.

3.The teams return an empty withdrawal

If after entering a command (e.g. getprop) there is no response:

• 🛠️ Make sure the device is unlocked (screens don’t lock while running). ADB).
• 🔧 Check if root is required for the command (e.g. su before getprop).
• 📱 Reset the phone to mode ADB fastboot:

adb reboot adb

Practical examples for different Xiaomi models

Some Xiaomi models have special features when working with the ADB. Let us consider a few examples:

1. Redmi Note 10 Pro (sweet)

In this model, getprop ro.miui.ui.version.name can return an outdated version due to the firmware features.

adb shell cmd miui_version miui_version

The output will be in the format of:

miui_version_code=14


miui_version_name=V14.0.5.0.TKFMIXM

2. POCO F3 / Xiaomi Mi 11X (alioth)

For these devices, it is useful to check the vendor version (firmware provider):

adb shell getprop ro.vendor.build.fingerprint

Example of conclusion:

Xiaomi/alioth_global/alioth:12/SKQ1.211006.001/V13.0.4.0.SJKMIXM:user/release-keys

3. Xiaomi 12/12 Pro (cupid/zeus)

On flagships with HyperOS (new shell instead of the new one) MIUI) teams are a little different:

adb shell getprop ro.vndk.version


adb shell getprop ro.hyperos.version

For devices with HyperOS, it is also useful to check the version. dynamic_partitions (If you're planning to stitch up a caste):

adb shell ls -l /dev/block/by-name/dynamic_partitions_*

💡

On HyperOS models (e.g. Xiaomi 13 or Xiaomi Pad 6), the standard getprop ro.miui.* commands may not work. Use ro.hyperos.version or ro.build.hyperos.version.

FAQ: Frequent questions about checking firmware through ADB