Modern Xiaomi smartphones offer users a lot of customization, but sometimes standard methods of updating through the settings menu are not enough: situations when the device “bricks”, gets into an endless reboot cycle or requires installing a specific version of software for the region, require deeper intervention in the system. This is where Platform Tools comes to the rescue, which is the official set of tools from Google for interacting with Android devices at a low level.
Using ADB (Android Debug Bridge) and Fastboot mode allows you to not only update the software, but also to completely clean partitions, unlock the bootloader or even restore the system after critical failures. Unlike graphical shells like the Mi Flash Tool, working through the command line gives you complete control over the process, eliminating interface errors and allowing you to see real-world operation logs. This is the choice of professionals and enthusiasts who want to understand every step of interaction with the file system of their gadget.
This guide details how to prepare, install the necessary components and execute the basic firmware commands. We will examine the nuances of working with drivers, the specifics of switching between boot modes and how to solve typical errors that users encounter when trying to modify the software of their devices. Readiness to follow instructions and attention to detail are key factors for successful firmware reflashing.
Tools preparation and installation of Platform Tools
The first and most important step is to get the latest version of the software from Google. Platform Tools is distributed separately from Android Studio, which allows you to download the minimum necessary package weighing about 10-15 MB. Download the archive should only be from the official repository of Android Developers, as third-party builds can contain modified binary files that can disrupt the stability of the connection or, in the worst case, damage the bootloader of the device.
Once the archive is uploaded, it must be unpacked into the root directory of the disk, such as C:\platform-tools. Using space paths or Cyrillic characters in the folder name often leads to errors in executing commands, so avoid paths like "C:\My Documents\Firmware." Inside the folder, you will find executables adb.exe, fastboot.exe and systrace.exe, which will be used for all subsequent operations.
For ease of use, many users add a path to utilities in the Windows operating system environment variables. This will allow you to run adb and fastboot commands from any directory through the command line, without going to the tool folder each time. However, for a one-time firmware procedure, it is enough to simply open the console directly in the tool folder, holding the Shift key and right clicking on the empty place, selecting “Open PowerShell window here” or “Open in the terminal”.
⚠️ Warning: Windows antivirus software or firewall can block script execution ADB, For the duration of the work, it is recommended to temporarily disable the protection or add an exception to the platform-tools folder.
Quality. USB-The cable plays a critical role in the data transfer process: Cheap cables designed only for charging do not have the necessary contacts to transmit data, which will lead to the fact that the computer simply does not see the device. Use the original cable or certified high-speed data-enabled analogue, avoiding cheap Chinese wires without labeling.
☑️ Firmware readiness
Installation of drivers and debugging configuration
In order for a computer to correctly identify a Xiaomi smartphone, the right drivers are needed. Unlike other manufacturers, Xiaomi does not always automatically install all the necessary components when you first connect in debugging mode. USB Driver or specialized Xiaomi ADB/Fastboot Drivers, which can be found on developer forums or as part of the Minimal utility ADB and Fastboot.
The debugging mode is activated in the hidden developer menu. To enable it, you need to go to Settings → About Phone and quickly click on the MIUI Version (or HyperOS Version) field seven times. After the notification “You became a developer”, you need to go back to the main settings menu, find the option → For developers and activate the Debugging switch over USB.
When you first connect your smartphone to a PC with debugging enabled, you will see a request on the device screen for debugging permission from that computer. You must tick "Always allow from this computer" and press OK. Without confirmation of this action, the adb devices command will show the status of unauthorized, and any operations will be impossible to perform.
If the smartphone display is broken or does not respond to touch, and debugging over USB has not been previously enabled, you will not be able to flash the device through ADB. In such cases, the only option is EDL (Emergency Download Mode), which requires an authorized Mi Account or the use of special test points on the board, which is a more complex hardware procedure.
Modes of operation: ADB and Fastboot
Understanding the difference between ADB and Fastboot modes is fundamental to proper firmware. ADB mode works when the Android operating system is already loaded (or in Recovery mode), it allows you to transfer files, install applications, take screenshots and execute shell commands, but does not give full access to the partitions of the bootloader.
Fastboot (or Bootloader) mode starts before the operating system boots, in which the device waits for commands to directly write partition images (.img) to memory. This is the mode in which the bootloader is unlocked, the custom recover (TWRP) is installed, or the complete flashing of all partitions of the device, usually transitioning to this mode by a combination of buttons (volume down + Power) when the phone is turned off.
There's also Recovery mode, which is an intermediate. In the standard Xiaomi drain recavator, functionality is limited, but through ADB you can send a command to reboot to Fastboot mode or start installing an update from the internal drive. The adb reboot bootloader command transfers the device from the running system or recavator directly to Fastboot mode.
| Parameter | ADB mode | Fastboot mode | EDL mode |
|---|---|---|---|
| Status of the OS | Downloaded or Recovery | Not loaded (Pre-loader) | Hardware mode |
| Access to files | Full (via push/pull) | Section images only | Full (Flash Programming) |
| Principal application | Debugging, logging | Firmware, unlock. | Rebuilding the bricks |
| Indication | Robot badge/key | Hare in an ooschank hat | Black screen + indicator on fire |
⚠️ Warning: Staying in Fastboot mode for more than 30 minutes without giving commands can lead to automatic restart of the device to normal mode or battery discharge, which will interrupt the firmware process.
To check the connection in any mode, use the appropriate commands. In the terminal, while in the tool folder, enter adb devices to check the normal connection or fastboot devices if the phone is transferred to bootloader mode. Successful connection displays the serial number of the device.
Firmware process through Fastboot
The Fastboot firmware process itself requires an unpacked firmware image in either.tgz (for global versions) or.zip (for Chinese ones that require renaming). Fastboot requires the archive version of the firmware, not the.exe installer or the.zip (Recovery) update file. flash_all.bat (for Windows) and the image folder.
Before running the script, make sure that the smartphone is connected in Fastboot mode and the fastboot device team issues a serial number. flash_all.bat It initiates a sequential recording of all partitions, from bootloader and system to user data (userdata). 3 before 10 minutes depending on speed USB-port and firmware.
There's a modified script. flash_all_except_data_storage.bat, This allows you to update the system by saving photos, contacts and installed applications, however, if you move from one version of Android to another (for example, from Android). 13 on 14) or change the location of the scaling (C) CN Global, it is strongly recommended to use full cleanup to avoid file conflicts and cyclic reboots.
What to do if a script ends in an error?
During firmware, the console will display progress for each partition. Don't interrupt the process or turn off the cable, even if it seems that the process is stalled. Current data protocols can pause the transfer of large files, which is normal.
Unlocking the bootloader and customization
One of the main reasons for using Platform Tools is to unlock the bootloader (Unlock Bootloader). Xiaomi's official method requires submitting an application through the Mi Unlock Tool application and waiting for 7 to 30 days. However, the unlock procedure itself is performed via the Fastboot command fastboot oem unlock (for older devices) or fastboot flashing unlock (for new ones), after which the confirmation will appear on the smartphone screen.
An unlocked bootloader opens the doors to install a custom Recovery, such as TWRP. This allows you to do full backups of the system (Nandroid backup), install third-party firmware (LineageOS, Pixel Experience) and get root rights. twrp_image_name.img, After that, you must immediately reboot to the recovery mode so that the stock system does not overwrite the changed partition back.
It’s worth remembering that unlocking the bootloader on Xiaomi devices results in a complete reset of user data (Wipe Data) for security purposes.In addition, some features, such as Google Pay (now Wallet) or banking applications, can stop working without additional manipulations to hide root rights and the state of the bootloader.
💡
Unlocking the bootloader is an irreversible security and data security action, and all files on the device will be deleted the moment you first unlock, so backup is mandatory.
For users engaged in deep modification, also available mode FastbootD (Dynamic Partitions), introduced in Android 11. It allows you to manage dynamic partitions that were previously part of the image of the system. Working with them requires special care, as the partition structure on the new Snapdragon and MediaTek processors is significantly different from legacy devices.
Diagnostics and Solving Typical Errors
The most common error is waiting for a device, which means that the computer is not seeing the phone in the right mode. Check Windows Device Manager if there is a device with a yellow exclamation mark or name "QHSUSB_BULK" (for EDL) Or Android, which means the drivers are not installed correctly, and you need to manually update the driver through Device Manager, indicating the path to the folder with the drivers of Google or Xiaomi.
The FAILED (remote: device is locked) error occurs when you try to flash partitions without the bootloader unlocked. It is not possible to officially flash global firmware to the Chinese version of the device (or vice versa) without unlocking. Some service centers use workarounds through Mi Auth accounts, but for the average user of Platform Tools in conjunction with the blocked BL, it is useless to change the region.
If the firmware process is stuck at a specific percentage (e.g., 48% or 99%) for more than 5 minutes, it may indicate power problems or flash memory failure, in which cases it sometimes helps to retrieve and re-install the battery (if the design permits) before retrying.
⚠️ Warning: Firmware of the device with a discharged battery (less than) 30-40%) The power surges at the end of the process can cause the phone to shut down when critical partition tables are written, turning it into a brick that requires a programmer to restore.
For advanced users, process logging is available. Adding keys to the command line or using sniffering utilities USB-This allows you to see which data packets are not reaching the device, and this is true when using unoriginal cables or ports. USB 3.0 that sometimes conflict with old Fastboot protocols.
💡
Use it. USB-a personal powered hub if you're flashing a Xiaomi tablet or a device with a large battery. USB 2.0 may not provide enough current (500 mA) to run in Fastboot mode while actively recording, causing failures.
Recovery after a failed firmware
If after firmware the phone went into cyclic restart (bootloop), first of all try to enter Recovery mode (Loudness up). + Power) and run Wipe Data / Factory Reset. Often the remnants of the old settings conflict with the new system. If this does not help, repeat the firmware procedure, making sure that the firmware file is intact.
If the device does not respond to the buttons and only the charging indicator is on, it may have fallen into EDL mode. To exit it without service software, you can try the "two finger method": connect the phone off to the PC, pinch both volume buttons and, holding them, connect the USB cable. If you are lucky, the device will be determined as a Qualcomm HS-USB QDLoader 9008, and it can be revived through specialized software (Mi Flash in Clean All or QFIL mode).
Remember that firmware is a powerful tool, but it requires responsibility. Always check the codename, such as the gauguin for the Redmi Note 10 Pro, before downloading the firmware. Installing an image from another model through the Fastboot can cause permanent damage to the hardware.