UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Meizu Pro5 fastboot mode locked

    Scheduled Pinned Locked Moved Support
    133 Posts 9 Posters 80.1k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • halucigeniaH Offline
        halucigenia
        last edited by

        Well, it turns out that I do have a Chinese version Pro5.
        I thought that since I did have an English GUI that it was international.
        I even reset to factory settings again and went through choosing English language again to confirm this.
        Trying to install the update.zip returns a "Firmware Corrupt" message.

        Once I managed to root and install the android term app
        I saw that using
        cat /dev/block/platform/15570000.ufs/by-name/proinfo from the androidterm app
        it listed
        machine_type=M576_mobile_public
        Which according to the xda tutorial means Chinese

        after following the instructions from
        https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-change-region-id-to-t3323883
        this changed to
        machine_type=M576_intl_official

        However, even after following those instructions I still can't get the update.zip from xda to install.
        Trying to install the update.zip still returns a "Firmware Corrupt" message.
        The update.zip from Stefano also results in a "Firmware Corrupt" message.

        Nexus4, Meizu MX4, Meizu Pro5, PinePhone UBPorts edition, PineTab, Pixel 3a XL

        S miousernameM 3 Replies Last reply Reply Quote 0
        • S Offline
          Stefano @halucigenia
          last edited by Stefano

          @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.

          1 Reply Last reply Reply Quote 0
          • halucigeniaH Offline
            halucigenia
            last edited by

            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.

            Nexus4, Meizu MX4, Meizu Pro5, PinePhone UBPorts edition, PineTab, Pixel 3a XL

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              Stefano @halucigenia
              last edited by

              @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.

              1 Reply Last reply Reply Quote 0
              • S Offline
                Stefano @halucigenia
                last edited by

                @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.

                halucigeniaH 1 Reply Last reply Reply Quote 0
                • halucigeniaH Offline
                  halucigenia @Stefano
                  last edited by

                  @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?

                  Nexus4, Meizu MX4, Meizu Pro5, PinePhone UBPorts edition, PineTab, Pixel 3a XL

                  S 1 Reply Last reply Reply Quote 0
                  • S Offline
                    Stefano @halucigenia
                    last edited by

                    @halucigenia You need to unpack/unzip it and then to restore the backup. I had to compress it when I uplodaed it.

                    halucigeniaH 1 Reply Last reply Reply Quote 0
                    • halucigeniaH Offline
                      halucigenia @Stefano
                      last edited by

                      @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.

                      Nexus4, Meizu MX4, Meizu Pro5, PinePhone UBPorts edition, PineTab, Pixel 3a XL

                      S 1 Reply Last reply Reply Quote 0
                      • S Offline
                        Stefano @halucigenia
                        last edited by Stefano

                        @halucigenia Restore backup, not install
                        Rebbot recovery first

                        halucigeniaH 1 Reply Last reply Reply Quote 0
                        • halucigeniaH Offline
                          halucigenia @Stefano
                          last edited by

                          @Stefano said in Meizu Pro5 fastboot mode locked:

                          @halucigenia Restore backup, not install
                          Rebbot recovery first

                          Ah, OK, got it. But it had to be copied to the /sdcard/TWRP/BACKUPS/M86 directory before the restore function could see it.

                          Nexus4, Meizu MX4, Meizu Pro5, PinePhone UBPorts edition, PineTab, Pixel 3a XL

                          S 1 Reply Last reply Reply Quote 0
                          • S Offline
                            Stefano @halucigenia
                            last edited by

                            @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.img

                            Let me know if you succeeded.

                            halucigeniaH 1 Reply Last reply Reply Quote 0
                            • halucigeniaH Offline
                              halucigenia @Stefano
                              last edited by

                              @Stefano installed and updated to UBports v2.

                              Thank you so much for your help.

                              Nexus4, Meizu MX4, Meizu Pro5, PinePhone UBPorts edition, PineTab, Pixel 3a XL

                              S 1 Reply Last reply Reply Quote 0
                              • S Offline
                                Stefano @halucigenia
                                last edited by

                                @halucigenia Enjoy the Ubuntu Touch on your Pro 5 🙂

                                1 Reply Last reply Reply Quote 0
                                • halucigeniaH Offline
                                  halucigenia
                                  last edited by

                                  If I get the chance I will see if I can compile an instruction set for a step by step how-to.

                                  Nexus4, Meizu MX4, Meizu Pro5, PinePhone UBPorts edition, PineTab, Pixel 3a XL

                                  1 Reply Last reply Reply Quote 1
                                  • mihaelM Offline
                                    mihael
                                    last edited by

                                    I am glad for you! 🙂 Congratulations for not giving up! It took me about three days to do it a year ago... Welcome! 🙂

                                    1 Reply Last reply Reply Quote 0
                                    • miousernameM Offline
                                      miousername @halucigenia
                                      last edited by

                                      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:

                                      http://dl-res.flymeos.com/Firmware/Flyme/PRO_5/5.1.11.0G/intl_stable/20161028020453/22a9e4dc/update.zip

                                      then I installed beta firmware from xda developer site and I unloked the bootloader.

                                      1 Reply Last reply Reply Quote 0
                                      • M Offline
                                        matteo
                                        last edited by

                                        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:

                                        1. To double check the version I typed the following:
                                          0_1526921218326_cff85a8d-aabd-456d-b30b-732f1adc00f1-image.png

                                        As you can see I got a [none] which sounds very strange to me.

                                        1. 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:
                                            0_1526920854109_0c2e9f20-9a4f-4bd8-8d83-6ce7da939eaa-image.png

                                        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

                                        S 1 Reply Last reply Reply Quote 0
                                        • S Offline
                                          Stefano @matteo
                                          last edited by Stefano

                                          @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-android

                                          Any other rooting method or different Busybox or SupeSu , will cause only the temporary changes. I have experienced the same issue.

                                          1 Reply Last reply Reply Quote 0
                                          • M Offline
                                            matteo
                                            last edited by

                                            Grazie Stefano! You have been very helpful!
                                            I'll try as per your suggestion. I'll report here as soon as possible 🙂

                                            Matteo

                                            1 Reply Last reply Reply Quote 1
                                            • M Offline
                                              matteo
                                              last edited by

                                              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

                                              S 1 Reply Last reply Reply Quote 0
                                              • First post
                                                Last post