No users have reported such a behaviour yet:
Therefore I do not understand this . Is it because of your custom recovery or what?
P.S.: Topic renamed and moved to Q&A.
@Rey This is due to using modified upgrade zip that included twrp. The problem was with the modifications made and not the flyme firmware.
The user didn’t include this Information for some reason.
So if you’re installing modified zips just know that there is always risks, there was no problem with .22 release from meizu so if you’re installing the official one there is nothing to worry about.
@Rey -Joan Mena • 8 hours ago
Brick with 22.214.171.124. Install, wipe cache/dalvik and no reboot - Ivan Giorgi Joan Mena • 7 hours ago
Same to me, phone’s dead. How to Restore?
-aiden Mod Ivan Giorgi • 3 hours ago
i tested it before upload here. it just have very long install time. and there is nothing to make hard brick. try to hold volyme up + power buttons and hold it until meizu logo will appear on screen. i moved this build and i checked again. there is nothing to do full brick phone.
- zzhh5511 aiden • in an hour
Replaced the motherboard, the warranty period.
-Ivan Giorgi aiden • 2 hours ago
You haven’t uderstood. We are not talking of long install time or something software related. Right after installing your file and attempting to reboot, the phone dies. No chance to power on it again. No keys combination working. Nothing. The phone just dies. Now, three of us experienced this hard brick with your file: that file is the responsible and you did something extremely wrong.
is say such topics must be deleted for sure. because @Naphtha NOT told that he/she talking about some custom modified version of 126.96.36.199.
people can be confused and think this topic about Official 188.8.131.52 update and that official firmware can get your phone bricked (but that is not true).