Introduction: Why has the smartphone become a brick?
Xiaomi Redmi Note 5A firmware (codenamed ugglite) is a procedure that usually goes smoothly but sometimes ends in complete failure of the device. If after updating or manually installing the software, the screen remains black, the Mi logo appears with infinite download, or the phone does not respond to buttons at all, you have encountered a software βbrickβ, the reasons range from an incompatible version of the firmware to failures during the recording of the boot or system partition.
Itβs important to understand that the Redmi Note 5A, based on the Qualcomm Snapdragon 425/435 processor, has anti-rollback protection that blocks the device when you try to roll back on an older version of MIUI. Even if you downloaded the βofficialβ firmware from the Xiaomi forum, the risk of turning the phone into a βbrickβ remains β especially when using the wrong tools like MiFlash with the wrong settings. In this article, we will analyze all possible recovery scenarios, from the simplest to the most complex.
Before you start repairing, answer two questions: 1. Does the phone respond to charging (light indicator, vibrates when you connect the cable)? 2. Can I enter Fastboot (Loudness down + Power) or Recovery (Loud up + Power) modes?
The answers depend on which recovery method is suitable.
Diagnostics of the problem: determine the type of βbrickβ
Not all bricks are the same. The Redmi Note 5A can be in one of four states, and the algorithm of actions depends on this:
- π Soft-brick: The phone turns on but gets stuck on the Mi logo, reboots cyclically, or hits the bootloop.
- π₯οΈ Fastboot-mode brick: The device only responds to the combination Volume down + Power by entering Fastboot mode. The screen can show the inscription FASTBOOT or the rabbit-cap.
- π EDL-mode brick (Qualcomm 9008): Phone not turned on, but defined by computer as Qualcomm HS-USB QDLoader 9008 (requires special cable or contact closure).
- β οΈ Hard-brick: The device shows no signs of life β it doesn't warm, it doesn't vibrate, it doesn't detect the PC. It's often caused by damage to the bootloader or EMMC-memory.
To determine the condition accurately, follow the following steps:
- Connect the Redmi Note 5A to charge for 30 minutes. If the charging indicator lights up, it's a software problem.
- Try logging into Fastboot: Press Volume Down + Power for 10-15 seconds. If the screen reacts, you have a Fastboot-mode brick.
- Install Qualcomm drivers and check the device in Windows Device Manager. If you have a QDLoader 9008, it's a EDL-regime.
What if the phone is not detected in any mode?
Method 1: Recovery via Fastboot (MiFlash)
If the phone is coming into Fastboot, the chances of recovery are maximum.
- π» Windows computer 7/10/11 (on macOS/Linux MiFlash is not working).
- π Original. USB-cable (better from the set).
- π Fastboot-ROM for Redmi Note 5A (Download only from the official Xiaomi website).
- π οΈ MiFlash (last version).
Step-by-step:
- Unpack the firmware archive in a folder without Cyrillic characters (for example, C:\ROM\ugglite).
- Install Qualcomm and Xiaomi drivers (you can use MiFlash in Driver Install mode).
- Launch MiFlash, press Select and point the path to the firmware folder.
- Connect the phone off in Fastboot mode (clip Volume Down + Power).
- In MiFlash, select the firmware method: Clean all β complete cleaning (recommended when changing the region or versions of MIUI); Clean all and lock β cleaning + lock the bootloader (only if the phone was unlocked!); Save user data β saving user data (not always working).
Refresh
Flash
Firmware time: 5-15 minutes. If the process is stuck on waiting for a device, check:
- USB Cable and Port (try USB 2.0 on the back of your PC).
- Drivers (there should be no exclamation points in the Device Manager).
- Antivirus (disable it β it can block MiFlash)
βοΈ Checking before firmware through MiFlash
Method 2: Recovery through EDL (Qualcomm 9008)
If the phone does not enter Fastboot, but is defined as Qualcomm HS-USB QDLoader 9008, you will need it. EDL-It's a more complicated method because it requires:
- π§ Specialist EDL-cable (or the ability to close test points on the board).
- π Firmware in.mbn or firehose format (for example, prog_emmc_firehose_8917.mbn for Snapdragon 425/435).
- π οΈ QFil or MiFlash with support EDL.
Attention! The firmware through EDL will reset all data, including the IMEI and serial number, and if you had the bootloader unlocked, it will lock again after the procedure.
Instructions for QFil:
- Download and install QFil + Qualcomm drivers.
- Connect the phone in mode EDL: Method 1: Use EDL-cable (closes the contacts D)+ and D- on the connector USB). Method 2: Disassemble the phone and close the test points (for Redmi Note) 5A These are the contacts near the battery, marked EDL or TP).
QFil
- Flat Build β point the way to the file prog_emmc_firehose_8917.mbn.
- Load XML β select rawprogram0.xml and patch0.xml from the firmware folder.
- Press Download and wait until it is finished (10-20 minutes).
β οΈ Note: If after the scaling of the EDL The phone does not turn on, and a Qualcomm error appears in Device Manager HS-USB Diagnostics 900E, So the firmware is not suitable for your Redmi Note modification. 5A (For example, you've flashed the ugg version instead of ugglite.
1. Connect the charger.
2.Put the Volume up. + Loud down and insert USB-phone-in.
3. Without releasing the buttons, connect the cable to the PC.
Sometimes it's forcing the device into mode. EDL pieceless.-->
Method 3: Manual recovery via TWRP (if installed)
If it's a Redmi Note 5A custom Recovery was installed TWRP, The phone is in Recovery mode (Loudness up). + Power, you can restore your performance without completely flashing it:
- π Firmware in.zip format (for example, MIUI or LineageOS).
- πΎ File. Disable_Dm-Verity_ForceEncrypt.zip (Avoid bootloop after installation).
- π OTG-cable SD-file-transfer.
Algorithm of action:
- Download the firmware and Disable_Dm-Verity on OTG-storage SD-map.
- Enter TWRP (Loudness Up + Nutrition).
- Select Wipe β Advanced Wipe and mark: Dalvik / ART Cache System Data (if you are not afraid to lose files)
Install
Disable_Dm-Verity_ForceEncrypt.zip
Reboot β System
Important: If the phone gets back into the bootloop after the reboot, then the firmware is not compatible with your version of the bootloader. Try a different build or go back to the Fastboot method.
Table: Comparison of recovery methods
| Method | Conditions required | Difficulty | Time. | Data retention | Risks. |
|---|---|---|---|---|---|
| Fastboot (MiFlash) | Phone enters Fastboot | Medium | 5-15 minutes | β No (except for Save user data) | Firmware errors, loader lock |
| EDL (QFil) | The phone is defined as 9008. | Tall. | 10-20 minutes | β No. | IMEI loss, hardware failure |
| TWRP | Custom recaveri installed | Low. | 3-10 minutes | β Partially (with selective vape) | Bootloop with incompatible firmware |
| Recoil through MiAssistant | The phone is switched on but is not working smoothly. | Low. | 20-40 minutes | β Yes. | Does not work in severe failures |
Method 4: Recovery of IMEI and serial number after EDL
If the phone is turned on after running through EDL, but does not catch the network (writes No Services or Invalid IMEI), then the IMEI and the serial number have been erased.
- Find out the original IMEI (look at the box or sticker under the battery).
- Download QCN Rebuilder or Maui META.
- Connect the phone in Diag mode (you need to flash Diag-enabled firmware or use the engineering menu).
- Maui. META Select a port and enter IMEI format AA-BBBBBB-CCCCCC-D.
- Press Write and restart the phone.
To know for sure:
- Check the sticker under the battery (if the phone is unpacked).
- Check the box (it is indicated modification).
- If the phone is turned on, use the CPU-Z or AIDA64 app.
Important: The firmware for ugglite and ugg is incompatible! Installing the wrong version will lead to hard-brick.