The POCO M3 is among the few phones waiting for the Android 11 update. It is unclear if the new Android OS will arrive with MIUI 12.5, but hopefully, we will find out in the coming days/weeks. And perhaps, to fortify the device ahead of the planned upgrades, a new update was rolled out to the global models a couple of days ago. The update arrived with a version number – MIUI 12.0.10.0 QJFMIXM – based on Android 10. While it seems to be a safe build, it has bricked some phones.
It’s not the first time such a thing has happened, but it seems Xiaomi hasn’t found the cause of this problem. Perhaps, that’s why the issue has resurfaced, and this time it will let you download and decrypt the update. The first OTA that bricked some phones allowed 70 to 80% download before the device went off and refused to turn on. Going by the recent report, the phone died after pressing the reboot command. According to the affected user, he did everything correctly as he didn’t try to reboot the phone while it was decrypting the files. That means we are back to the same problem again.
Luckily, there are ways provided by the official POCO community on how to go about this. It seems you have to manually reboot the device to fix the problem, which is simple. You should press and hold the power button for 13s, and hopefully, the device turns on. Luckily, if this method works for you, there won’t be a need for a manual reboot next time.
Also, you can try the Fastboot method to try to revive the phone. Press and hold the power and volume down key for 5-7 seconds. Leave it in Fastboot for about 20 seconds and repeat the volume and power down button until the device exits the Fastboot mode. Another method is to plug the device in charging with the original USB cable. Leave it for some time and try pressing the power button. Check for more options here.
And the affected user is still exploring these fixes to see if anyone will work for him, none of them seem to be working. Hence, if you’re yet to upgrade, we recommend that you don’t. Although not everyone is reporting the issue, but we don’t know who will be next. The best thing will be to avoid the build.
