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

[solved] Mx4 - Installer blocked at "waiting for recovery mode"

Scheduled Pinned Locked Moved Support
40 Posts 8 Posters 7.8k Views 2 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.
    • A Offline
      advocatux @arubislander
      last edited by advocatux 20 Aug 2018, 15:44

      @arubislander yes, probably, but I really don't know. Maybe that tool is exactly the same as in Canonical times or maybe it has been adapted for UBports like other tools?

      Just in case, the full command adapted for MX4, 16.04 RC, and UBports scenario is:
      ubuntu-device-flash --server=https://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/rc --bootstrap

      and then, once again without the --bootstrap option

      1 Reply Last reply Reply Quote 0
      • A Offline
        advocatux
        last edited by 20 Aug 2018, 15:49

        Ah, this point is also important before doing anything else:

        Warning: If your device is encrypted you must perform a full factory reset before installing ubuntu. This also will delete all data from the device, including apps and other data. You may want to create a backup first

        1 Reply Last reply Reply Quote 0
        • S Offline
          Slayne
          last edited by Slayne 20 Aug 2018, 17:08

          Thanks for your time.

          Once again, whatever i do, all commands made by terminal on my labtop finish with :
          "2018/08/20 19:05:37 Can't flash recovery image"

          Sooooo frustrating.

          Edit - I follow with interest this conversation about installing UBports without cable but with terminal and then i realise that on my all-new Ubuntu touch legacy installation, i dont have access to the ubuntu store and then i have no terminal...

          A 1 Reply Last reply 20 Aug 2018, 18:03 Reply Quote 0
          • A Offline
            advocatux @Slayne
            last edited by 20 Aug 2018, 18:03

            @slayne have you tried to install the Terminal app (vivid version) from here https://open-store.io/app/com.ubuntu.terminal?

            S H 2 Replies Last reply 21 Aug 2018, 08:29 Reply Quote 0
            • S Offline
              Slayne @advocatux
              last edited by Slayne 21 Aug 2018, 08:29

              @advocatux It doesnt work.

              But is doesnt matter because I UPGRADED MY MX4 TO UBPORTS !!! Finally !

              As i thought, the main problem was the buggy recovery mode.
              I tried :
              sudo adb devices
              75HABLM26VFN no permissions (verify udev rules); see [http://developer.android.com/tools/device.html]

              (note : all these commands were made while phone on "recovery mode")

              This "no permissions" was the key.

              Then i did :
              slayne@slayne-PcAsus:~$ sudo adb kill-server
              slayne@slayne-PcAsus:~$ sudo adb start-server

              • daemon not running. starting it now on port 5037 *
              • daemon started successfully *
                slayne@slayne-PcAsus:~$ adb devices
                List of devices attached
                75HABLM26VFN recovery

              That "recovery" instead of "no permissions" seemed pretty good.

              I retried one of the last commands i did yesterday :
              slayne@slayne-PcAsus:~$ sudo ubuntu-device-flash --server=https://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/rc

              2018/08/21 09:56:51 Device is |arale|
              2018/08/21 09:56:51 Flashing version 9 from ubports-touch/16.04/rc channel and server https://system-image.ubports.com to device arale
              2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
              2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/ubports-touch/16.04/rc/arale/version-9.tar.xz to device
              2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
              2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/gpg/image-master.tar.xz to device
              2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/ubports-touch/16.04/rc/arale/version-9.tar.xz to device
              2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
              2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/gpg/image-master.tar.xz to device
              2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
              2018/08/21 09:57:03 Start pushing /home/slayne/.cache/ubuntuimages/pool/device-c746103f205781974a7b89aff29cdf3dd450879f119f672d3a6f62b67ed783c5.tar.xz to device
              2018/08/21 09:57:03 Start pushing /home/slayne/.cache/ubuntuimages/pool/ubports-dfcbe0416dc5dddaa398eff83a60d883c0d693dd1b1958e2fd9b61a02771e4ee.tar.xz to device
              2018/08/21 09:57:35 Done pushing /home/slayne/.cache/ubuntuimages/pool/device-c746103f205781974a7b89aff29cdf3dd450879f119f672d3a6f62b67ed783c5.tar.xz to device
              2018/08/21 09:59:27 Done pushing /home/slayne/.cache/ubuntuimages/pool/ubports-dfcbe0416dc5dddaa398eff83a60d883c0d693dd1b1958e2fd9b61a02771e4ee.tar.xz to device
              2018/08/21 09:59:27 Created ubuntu_command: /home/slayne/.cache/ubuntuimages/ubuntu_commands324087129
              2018/08/21 09:59:27 Rebooting into recovery to flash

              AND IT WORKED !!

              Thanks everydoby for your time and your help. Now im in.

              A L 2 Replies Last reply 21 Aug 2018, 11:22 Reply Quote 2
              • A Offline
                advocatux @Slayne
                last edited by 21 Aug 2018, 11:22

                @slayne yay kudos!! Enjoy your new UT phone!!

                1 Reply Last reply Reply Quote 0
                • L Offline
                  Lakotaubp @Slayne
                  last edited by 21 Aug 2018, 11:48

                  @slayne double yey well done

                  1 Reply Last reply Reply Quote 0
                  • H Offline
                    halucigenia @advocatux
                    last edited by 21 Aug 2018, 13:21

                    @advocatux How would I go about installing terminal app from there on my MX4 Ubuntu Touch without functional USB?

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

                    A 1 Reply Last reply 21 Aug 2018, 14:54 Reply Quote 0
                    • A Offline
                      advocatux @halucigenia
                      last edited by 21 Aug 2018, 14:54

                      @halucigenia if you're using UT (UBports) you just need to use the OpenStore app.

                      If you're using the "old" Canonical's one, then it depends on what you have installed in your phone already. For example, do you have WifiTransfer? Do you have UT Tweak tools? Do you have ssh available over wifi?

                      You can go to https://open-store.io/app/com.ubuntu.terminal with the browser and download the vivid version to your phone, of course, but the problem is how to install that click package if you don't have at least one of the necessary tools to do it.

                      H 1 Reply Last reply 21 Aug 2018, 15:45 Reply Quote 0
                      • S Offline
                        Slayne
                        last edited by 21 Aug 2018, 15:02

                        Here is the tip, if somebody has the same issue (waiting for recovery mode) :

                        Phone on "recovery mode".

                        Terminal :
                        sudo adb devices

                        If ‘no permission’ :
                        sudo adb kill-server
                        sudo adb start-server

                        S H 2 Replies Last reply 21 Aug 2018, 15:32 Reply Quote 3
                        • S Offline
                          Stefano @Slayne
                          last edited by Stefano 21 Aug 2018, 15:32

                          @slayne also unplugging from a PC then
                          adb kill-server
                          then plugging in again
                          and start adb start-server again

                          1 Reply Last reply Reply Quote 0
                          • H Offline
                            halucigenia @advocatux
                            last edited by 21 Aug 2018, 15:45

                            @advocatux It's still on the old Canonical Ubuntu Touch reset to base build without any extra installed apps (sorry that was not clear). I will see what I can do with ssh when I get back home.

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

                            A 1 Reply Last reply 21 Aug 2018, 15:49 Reply Quote 0
                            • A Offline
                              advocatux @halucigenia
                              last edited by 21 Aug 2018, 15:49

                              @halucigenia hmm you'll need adb to set & config ssh

                              H 1 Reply Last reply 22 Aug 2018, 06:25 Reply Quote 0
                              • H Offline
                                hummlbach @Slayne
                                last edited by 21 Aug 2018, 17:27

                                @slayne And it didn't work with the latest installer for you? I'm asking because I had the same issue with the nexus 4 and it seems to be fixed for the nexus 4 with the latest version of the installer... Perhaps the fix (if there was one... :)) was in a device specific part of the installer... @NeoTheThird can you tell anything about that?

                                S 1 Reply Last reply 21 Aug 2018, 18:56 Reply Quote 0
                                • S Offline
                                  Slayne @hummlbach
                                  last edited by 21 Aug 2018, 18:56

                                  @hummlbach No, even with the latest installer (*.21) it didn't work. The installer couldnt debug my recovery mode.

                                  But i read several posts about the Mx4 and this phone seems a bit specific (many versions ?).
                                  And i read several posts of people having the same problem as i had.

                                  At least i hope this can help some people, or maybe help to improve the installer.

                                  1 Reply Last reply Reply Quote 0
                                  • H Offline
                                    halucigenia @advocatux
                                    last edited by 22 Aug 2018, 06:25

                                    @advocatux Catch 22. even adb connect [IP address] returns Connection refused.

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

                                    A 1 Reply Last reply 22 Aug 2018, 07:01 Reply Quote 0
                                    • A Offline
                                      advocatux @halucigenia
                                      last edited by advocatux 22 Aug 2018, 07:01

                                      @halucigenia if you really want to use that phone, probably it's better to fix the usb issue before trying anything else. Maybe it's an easy repair, like dirty connections.

                                      Have you tried to use other usb cables? Have you tried to gently wiggle the usb cable connector?

                                      H 1 Reply Last reply 22 Aug 2018, 10:56 Reply Quote 0
                                      • H Offline
                                        halucigenia @advocatux
                                        last edited by halucigenia 22 Aug 2018, 10:56

                                        @advocatux Yes, I have tried everything that I can think of to get USB working again.
                                        The Ubuntu device now has the USB module from another flyme MX4 and the flyme MX4 has the Ubuntu devices USB module, USB still works fine on the flyme device with the same cables that I use in the Ubuntu device. It must be hardware other than the USB module or a software related problem.

                                        I have been here before - See https://forums.ubports.com/post/4741

                                        I just thought that this thread might have something that I have not yet tried.

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

                                        A 1 Reply Last reply 22 Aug 2018, 11:39 Reply Quote 0
                                        • A Offline
                                          advocatux @halucigenia
                                          last edited by 22 Aug 2018, 11:39

                                          @halucigenia ah, I see 🙂

                                          1 Reply Last reply Reply Quote 0
                                          • Josele13J Offline
                                            Josele13
                                            last edited by 30 Aug 2018, 14:16

                                            This post is deleted!
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post