POCO claims to be an independent brand, but current facts show the company still depends on Xiaomi. They’re still on the parent company’s supply change and still use their design, Android skin (MIUI), and others. Meanwhile, the POCO M3 remains one of the few non-rebadged Redmi phones. It was launched in Q2 of last year with great value for money features. The device runs Android 10 on top of MIUI 12 outside-of-the-box. It is waiting for the MIUI 12.5 and Android 11, of which the former has started seeding. However, we don’t have any information at the moment when POCO M3 will receive it.
Meanwhile, the device has continued to receive maximum software support, but the latest version that brought the March security patch left a bug. It’s one of Xiaomi buggy update. Initially, the phone was thought to be dead because it won’t turn on no matter what you try. Issues like this one are triggered when an update is interrupted on Installation. That’s why you’re always reminded no to reboot during update Installation. However, it wasn’t anything like rebooting that caused the issue, as according to some users, their device went off when the update reached 70-80%. It is more like the build that bricked the Mi A3 a couple of months ago, but this time it’s different.
Luckily, you won’t visit the Xiaomi service center to fix their buggy update this time. According to a Moderator in the Mi Community forum, you should hold down the power button for 13s to manually reboot the device. Also, you can reboot the device when you enter fastboot mode. Hold down the power and volume down buttons at the same time for about 5-7 seconds. After about 20 seconds on fastboot, repeat holding the power and volume down button to exit, and your device will start.
Hopefully, the two alternative fixes the Xiaomi buggy update this time. Meanwhile, here are affected version; MIUI 12.0.7.0 QJQEUXM, MIUI 12.0.6.0 QJFMIXM, MIUI 12.0.8.0 QJFEUXM, MIUi 12.0.7.0 QJQMIXM, MIUI 12.0.5.0 QJFRUXM, MIUI 12.0.4.0 QJQIDXM. Looking at the version of these builds, Redmi 9T users seem affected. Of course, you should reboot your device using the above method.
