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.
      • 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
                              • S Offline
                                Stefano @matteo
                                last edited by

                                @matteo have you enabled developer menu, usb debugging?

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

                                  @stefano Yes I did but it doesn't change anything. This is what I got (as you can see I tried many times to wake up the phone in fastboot)

                                  0_1527099268777_185825fb-16cc-47de-a30a-ab15b79ab25d-image.png

                                  P.S. the international name is there this time, so it shouldn't be recognized as a Chinese device anymore...

                                  1 Reply Last reply Reply Quote 0
                                  • M Offline
                                    Marathon2422 @halucigenia
                                    last edited by

                                    @halucigenia I thought you had to flash old ubuntu touch,to get partitions sized correcly,then flash ubports, ( updates by flyme,put on the root of internal drive ,and flyme recovery can find them and go to work). Recovery install from fastboot= sudo fastboot flash recovery ~then your recovery location,drag n drop or or

                                    S halucigeniaH 2 Replies Last reply Reply Quote 0
                                    • S Offline
                                      Stefano @Marathon2422
                                      last edited by Stefano

                                      @matteo try to flash recovery again,: sudo fastboot flash recovery recovery-turbo.img

                                      And if it won't work, unplug the phone and :
                                      sudo adb kill-server

                                      sudo adb start-server

                                      plug in the phone and try again

                                      M M 2 Replies Last reply Reply Quote 0
                                      • M Offline
                                        Marathon2422 @Stefano
                                        last edited by

                                        @stefano thanks ,i was trying to throw some ideas in.
                                        i am waiting for 16.04 to be released for my pro 5.
                                        my sim no good for ubuntu/ubports.
                                        most likley need help then ,cant remember my flyme login ,and on a different cell number,should be fun

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

                                          @marathon2422 No, I did not have to re-partition, although I did think that I might have to. However, it looks like for 16.04 it needs more room on your cache partition than 15.04, see https://forums.ubports.com/post/8931

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

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

                                            @stefano you know what Stefano? Reading again this post from the beginning, I found out something that I missed before, i.e. you sent a link to an update.zip file. I downloaded that and saved in the phone in order to upgrade the phone. Once started the process, it came out the "Firmware corrupt" issue. Why is so? My phone is now supposed to be fixed as international, weird....

                                            Going to your suggestion regarding the flash recovery thing, I didn't do any flash recovery before nor I know how to proceed with this procedure. Should I exploit the Ubports installer to do so?

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

                                              @matteo did you mean the "Unlocked_bootloader_pro5_update.zip "

                                              This is the one which you are suppose to flash after you change the ID to I (global or international)
                                              This version can have the bootloader unlocked, no other firmware version of Flyme is known to work.
                                              Be careful, if you flash again any A firmware ( Chinese ) you will need to unlock the bootloader again.

                                              So, If you flashed firmware Flyme OS 5.1.3.0A first, then changed the ID and followed the steps, you should have now International (global)version of FLYME and the next thing is to flash that Unlocked_bootloader_pro5_update.zip, start the phone, enable developer options, usb debugging, then rebooting to FASTBOOT and unlock the bootloader.
                                              After that reboot to fastboot and check the screen down, is small print and shoud say "FASTBOOT MODE (unlocked, rooted )

                                              If this is true, you can then flash UT, otherwise it won't do nothing.

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