Meizu Pro5 fastboot mode locked
-
@halucigenia You did not installed the correct Terminal app and/busybox app, therefore the changes are only temp and after reboot it rolls back to chinese.
-
I have just retried from scratch again and made sure that Flyme OS 5.1.3.0A was installed first, which I may have missed last time.
I now have an un-locked bootloader in the flyme version downloaded from xda.I am just starting to follow the procedures here:-
https://forums.ubports.com/post/4929
as neither Ubports installer or MDT seemed to allow a Pro5 install and phablet-tools seems to be unavailable on Kubuntu 17.10.@Stefano Please let me know if those instructions should now work for me.
-
@halucigenia did you downgraded the Flyme to that version mentioned in that post? Newer versions of Flyme were patched by Meizu to prevent the unlocking of bootloader and chnging ID to Global/International.
-
@halucigenia oh yes, that's correct. That is my backup of Ubuntu-touch/15.04/stable/r1(ota-1).
Just follow the steps and it should work. -
@Stefano OK I tried, but each time I installed the zip file it returned errors:-
"Could not find 'META-INF/com/google/android/update-binary' in the zip file"What do I do now?
-
@halucigenia You need to unpack/unzip it and then to restore the backup. I had to compress it when I uplodaed it.
-
@Stefano OK, I now have the folder Ubports_ota1 in /sdcard/TWRP/BACKUPS
and can navigate to it but it won't let me proceed - there is no option to install after selecting the folder. -
@halucigenia Restore backup, not install
Rebbot recovery first -
@Stefano said in Meizu Pro5 fastboot mode locked:
@halucigenia Restore backup, not install
Rebbot recovery firstAh, OK, got it. But it had to be copied to the /sdcard/TWRP/BACKUPS/M86 directory before the restore function could see it.
-
@halucigenia As I said, follow the steps provided.
Once you've done it, there is an update available, but it only will be installed after you flash the ubuntu recovery. fastboot flash recovery recovery-turbo.imgLet me know if you succeeded.
-
@Stefano installed and updated to UBports v2.
Thank you so much for your help.
-
@halucigenia Enjoy the Ubuntu Touch on your Pro 5
-
If I get the chance I will see if I can compile an instruction set for a step by step how-to.
-
I am glad for you!
Congratulations for not giving up! It took me about three days to do it a year ago... Welcome! -
Hi,
thanks for ubuntu touch, I had same problems with a meizu pro 5 with flyme 6.0.0G firmware installed. I solved installing previous flyme firmware from here:then I installed beta firmware from xda developer site and I unloked the bootloader.
-
Hi all.
I read with interest this thread. I got a Meizu Pro 5 just one week ago and since then I'm struggling to make it eligible for UT installation.I guess it's a chinese version, since it is coming from China and when I first booted it up, it showed up a lot of chinese app. The main problem I'm facing is that the OS arrived locked and when I go into fastboot mode the device is not detected by the Desktop terminal and I cannot unlock it.
Therefore, I followed all the useful threads indicated here but without any luck up to now. Here following the steps I made:- To double check the version I typed the following:
As you can see I got a [none] which sounds very strange to me.
- I then tried to change the region:
- I installed the chinese Flyme OS 5.1.3.0A and then, to get root, I installed KingRoot, which does pretty well the job to gain the root access;
- then I installed SuperSu 2.76 (by Chainfire) and BusyBox v1.24.1-meefik. The installation from apk went smoothly but if I open each app by tapping on it, it states it cannot install the binary.
- BTW if I enter the root mode, I can follow the next step without any issue:
The "machine_type=M576_intl_official" specification to make the phone international seems properly set. However, If I reboot the phone, and I type again "su", "id" and "cat /dev/block/platform/15570000.ufs/by-name/proinfo" I don't see anymore the specification above. It seems like if the "busybox cp -f" doesn't take effect at all and the modification is only temporary. Can you give me some advice on that, please? Any hint would be highly appreciated.
Thanks,
Matteo
- To double check the version I typed the following:
-
@matteo I think there might be a problem with root privileges. On Meizu phones you need to go FLyme account and register there, or if registered then just log in. There is option to ROOT the phone. Only this rooting actually works. ( The FLyme log in onFlyme OS 5.1.3.0A) Then install the Bysybox and SuperSU, exactly those mentioned here: https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-change-region-id-to-t3323883
Then just follow the instructions there and here: https://askubuntu.com/questions/767323/how-to-install-ubuntu-on-meizu-pro-5-that-was-originally-with-androidAny other rooting method or different Busybox or SupeSu , will cause only the temporary changes. I have experienced the same issue.
-
Grazie Stefano! You have been very helpful!
I'll try as per your suggestion. I'll report here as soon as possibleMatteo
-
Apparently it seems I made some progress.
Finally, I succeeded to create a Flyme account (it was not a straightforward process indeed) and I gained the root permission. I realized that BusyBox wasn't actually working before because it couldn't install the binary; now, set it properly, I proceeded with the root permission and after that I finally was able to save the "machine_type=M576_intl_official" name to the Pro 5 phone. I double checked it by rebooting with "cat /dev/block/platform/15570000.ufs/by-name/proinfo" and this time that name was already shown. Yay
I thought the worst part was just behind the back, and I passed to follow the instructions on the page https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-unlock-bootloader-meizu-pro-5-t3303127. I installed the version Flyme OS 5.6.1.19, as suggested, and rebooted in fastboot mode.....nothing.....my device isn't recognized at all.....
Any clue?Thanks.
Matteo
-
@matteo have you enabled developer menu, usb debugging?
