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

                      @stefano yes exacly, the "Unlocked_bootloader_pro5_update.zip ". If I try to flash it, it gives me the "Firmware corrupt" message.
                      I already flashed back Flyme OS 5.1.3.0A (before reading your warning though). I gained root mode again by accessing the Flyme account and then I wanted to check again the international name and it seems all good so far:

                      0_1527184442341_69425564-320d-4400-999d-967d53cded63-image.png

                      It should work! I'm out of ideas...

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

                        @matteo just to be sure,type in:
                        sudo fastboot oem unlock

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

                          @matteo download this recovery:

                          move to your Home folder on PC

                          Start terminal and type in with phone rebooted to bootloader mode:

                          sudo fastboot flash recovery TWRP_3.0_m86.img

                          it should flash you phone with custom TWRP recovery, then you reboot to recovery and flash International version of FLyme, boot in the FLYME and enable developer mode, usb debugging.

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

                            @matteo SORRY man, I probably forgot to mention that you need to rename the Unlocked bootloader zip to " update.zip "
                            And flash it, I only renamed it for recognition while downloading, the FLYME recovery won't flash any other zip. While selecting to update it, you need to select the WIPE option as well ,on original FLYME recovery. Otherwise you might loose IMEI. ( But you probably know that, as I hope you read tutorials on Flyme forum ,how to upgrade the FLYME )

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

                              @stefano thanks, I already renamed that, you mentioned to do so already in this post when you attached the file. Anyhow, I'm still getting the "Corrupt" message....I try out your other tips and see what happens...in the meantime...thank you very much, you are sooooo kind to help me!

                              P.S. what's the numbering of your firmware? Is it by the chance the Flyme OS 5.6.1.19? I'm telling you, because that's the one I downloaded according to this post, from the MediaFire or Mega servers and this version worked so far for me, but not enough to get the device be recognized in fastboot mode.

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

                                @matteo Yes, that's the version I uploaded as well.
                                Maybe the file itself be corrupted by downloading.
                                Anyway, if you have trouble to have detected phone in fastboot, try:
                                sudo fastboot devices
                                or try to plug it to a different usb port, reboot the PC, update it...

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

                                  @stefano ok, then there is a problem with your file, maybe as you said I got it corrupted during the download. Anyhow, I again downloaded the version of Flyme OS 5.6.1.19 daily (I expected a suffix like G but it says only "daily"), and tried again to plug it to the PC to be detected....nothing......it stays put with the message <waiting for device>, forever displayed.
                                  I also tried an other version, this time from the official Flyme site (ver. Flyme 5.1.12.0G because "G" stands for the global device) but again no detection in fastboot mode...nothing seems to work.
                                  I tried different usb ports but it always ends with no detection. I enabled the "USB debugging", I have the doubt that I missed something else to be accomplished before going in fastboot mode.

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

                                    @matteo sorry to ask again ,but have you used : sudo fastboot devices

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

                                      @stefano you mean if I tried typing that when the Pro 5 is in fastboot mode? Yes, and the output is nothing, the device isn't recognized. I tried with all the usb ports my laptop has got but no change. I would like just to mention that on my laptop I installed the Ubuntu 16.04 OS.

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

                                        @matteo That's strange. Try to reinstall fastboot and adb on your laptop.

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

                                          @matteo Maybe try this:

                                          Create a bootable usb disk (at least 6gb usb key)
                                          from your laptop. ( Usb startup disk creator)
                                          Boot from that usb,
                                          In terminal install adb tools, install fastboot and try if it list your Pro 5. If yes, then you can try installation of UT.

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

                                            @stefano I know for sure that fastboot detection works with my Ubuntu 16.04 desktop because I tried it with my other phone BQ Aquaris E5 UBports edition, which is detected without any issue. The difference between the BQ E5 and the Meizu Pro 5 is that the E5 is unlocked while the Pro 5 isn't yet.

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

                                              @stefano I will try also this way, thank you for not giving up....

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