Xiaomi Error: Try Connect in Normal Mode First

Users of Xiaomi, Redmi and Poco smartphones often face an unpleasant situation when the device stops loading into the usual interface. Instead of the MIUI or HyperOS logo, the logo of the rabbit repairing the android appears on the screen, or the inscription "Fastboot". When trying to perform any actions through the computer, such as reflashing the device or unlocking the bootloader, the console gives a mysterious message: "try in normal first mode switch then connect xiaomi what to do."

This error means that the firmware tool or driver cannot properly interact with the device in its current state. Fastboot mode is designed for low-level operations, but to transition to it or execute certain commands, the system requires prior confirmation or change of state. Often the problem lies in stuck buttons, incorrect drivers or a software failure of Bootloader. Understanding the causes of this state is the first step to successfully recover the gadget without contacting the service center.

In this guide, we will discuss in detail the algorithms for exiting Fastboot mode, how to switch between boot modes and how to fix connection errors. It is important to act consistently, since incorrect interference with the boot process can lead to complete failure of the smartphone. We will look at both software methods through the PC and physical manipulation of the device buttons.

Causes of connection error

An error message that requires a normal connection before switching rarely occurs from scratch, most often due to an interrupted upgrade process or a bootloader failure. If you tried to update the system through the Mi Flash Tool or unlock the bootloader through Mi Unlock, and the process was interrupted (the cable went off, the battery went down, the program window closed), the device could be stuck in an intermediate state.

Another common cause is physical damage to the control buttons. Volume Down is responsible for entering Fastboot mode. If it is stuck, slammed into the case or has a damaged plume, the smartphone will constantly try to go into this mode every time it is turned on, ignoring normal booting.

⚠️ Note: If your smartphone has recently fallen or been in contact with moisture, a connection error may be a sign of a short circuit in the button chain.

Also, consider the driver conflict in the computer operating system. Windows may not correctly detect the device when it goes from Normal to Fastboot or EDL. If the Qualcomm or MediaTek drivers are installed incorrectly, the mode switch command simply will not reach the destination, and you will see a requirement to connect in normal mode.

Diagnostics of device status

Before you start to take action, you need to determine exactly what condition your Xiaomi smartphone is in. It depends on the choice of recovery method. Primary diagnostics are performed visually and through the computer Device Manager. Connect your phone to the PC using the original device. USB-cable and follow the system's response.

If the smartphone displays a Fastboot logo or an orange or blue FASTBOOT sign, the device is in bootloader mode. If the screen is black but the computer is making the device connect, it may be in EDL (Emergency Download Mode) or deep sleep mode, and in Device Manager, it will be reflected as a Qualcomm HS-USB QDLoader 9008 or an unknown device.

For a deeper diagnosis, you can use specialized ulites such as Mi ADB/Fastboot Tools or Xiaomi ADB/Fastboot Tools. They allow you to see the bootloader lock status and current mode of operation. However, if the system requires "normal mode", these tools may not start the scan until you perform a forced reboot.

💡

Use it. USB-Hub without external power or connect the phone directly to the PC motherboard. front ports of the case often do not provide enough voltage for stable operation in recovery modes.

How to exit Fastboot mode

The easiest and most common way to solve the problem of "try connect in normal mode first" is to force the device to restart. Since the smartphone is in Fastboot mode, a simple press of the power button may not work or simply reboot the phone back to Fastboot if the volume button is pinched.

To do this, press and hold the Power button for 10-15 seconds. The screen should go out and the device vibrates. As soon as you feel the vibration or see the MI logo, immediately release the button. If the phone starts to boot into the system, the problem is solved. If it goes back into hare mode, perhaps the volume button is physically pinched.

If standard retention doesn't work, try a button combination. Press Volume Down and Power for 15-20 seconds at the same time. This emulates the battery pull and should completely de-energize the device's logic, after which, when you release the buttons, the phone will try to start normally.

Switching loading modes through ADB

If the buttons do not respond or the smartphone cyclically reboots, you can try to control the boot modes programmatically using the ADB debugging bridge. For this method, it is critical that the smartphone has at least a partially working system or Recovery mode with ADB support. If the phone is hanging on the Fastboot logo, this method may not work without first accessing Recovery.

First, make sure that your computer has Google USB Driver drivers and SDK Platform-Tools installed. Open the Command Prompt (CMD) or PowerShell in the tool folder. Enter the command to check the connection: adb devices. If the device appears in the list, you can send a command to reboot.

To go to normal mode, use the command: adb reboot. If you need to get into Recovery mode to reset settings, type: adb reboot recovery. In some cases, when the system writes "try connect in normal mode", the command helps force the transfer to bootloader mode for subsequent flashing: adb reboot bootloader.

adb reboot # Reboot to normal mode


adb reboot recovery #Reboot in Recovery




adb reboot bootloader #Reboot in Fastboot




adb reboot edl # Reboot to EDL mode (requires rights)

⚠️ Attention: Adb reboot edl will put the phone into emergency boot mode, only by keeping the power buttons and volume up for a long time (about 30 seconds) or by using a special cable.

Using Recovery Mode to Reset

Recovery is an Android diagnostic environment that allows you to reset data and clear cache. If the "try connect in normal mode" error is caused by a software conflict or damage to system files, resetting to factory settings (Wipe Data) may be the only solution that preserves the functionality of the device.

To get to Recovery on Xiaomi, turn off the phone completely. Then press the Volume Up and Power buttons at the same time. Hold them until the MI logo appears, then release the power, but keep the volume up until the Recovery menu appears. Navigation is done with volume buttons, the power button selects.

From the menu, select Wipe Data, then Wipe All Data, and confirm the action. This process will delete all user data, but restore the system to work. Once complete, select Reboot -> Reboot to System.

💡

Recovery reset is a radical method that deletes all data, and only use it if the forced reboot doesn't work and you're ready to lose information on the device.

Table of error and action codes

When you use firmware tools, you may not only encounter text messages, but also numerical error codes. Understanding their meaning helps you choose the right smartphone treatment strategy. Below is a table of the main statuses encountered when trying to connect to Xiaomi devices.

Analyzing the error code saves time, for example, if you see a server error, it's useless to reconnect the cable, the problem is on the Mi Account or network side, and if the error indicates mode, the focus shifts to manipulating buttons and ports.

Prevention and work with drivers

The stability of the recovery tools depends on the quality of the installed drivers. In the Windows operating system, universal drivers are often automatically installed, which conflict with specific Xiaomi commands. ADB Original drivers are required.

It is recommended to install the Xiaomi USB Drivers package or Universal ADB Driver package. After installing the drivers, be sure to check them in the Device Manager. In the "Android Devices" or "Ports (COM and LPT)" section, there should be no unknown devices with a yellow exclamation mark. If there is a sign, right click, select "Update driver" and specify the path to the driver folder.

It’s also worth disabling the digital signature check for drivers in Windows if you’re in forced mode, especially for older versions of Windows 10 and Windows 11, which can block low-level bootloader drivers.

⚠️ Warning: Never interrupt the process of installing drivers or firmware by pulling out the cable. This can lead to the "bricking" of the device, after which only a paid service will help through the cable. EDL-account.

Frequently Asked Questions (FAQ)