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

    Unable to install UBports on MX4 Ubuntu edition

    Scheduled Pinned Locked Moved Support
    mx4install
    25 Posts 6 Posters 7.9k 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

        The devmode version of MDT doesn't connect to the phone either.

        There must be something wrong in that adb / fastboot are not running on the phone.
        Time to give up and just keep on using Cannonical UT until I get a fairphone 2 or something?

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

        1 Reply Last reply Reply Quote 0
        • U Offline
          UniSuperBox
          last edited by

          The problem seems to be that USB isn't connecting at all. The MX4 has a notoriously bad USB connector.

          You might need to try different ports or cables until you're able to find one that works. Run dmesg -w and plug in the phone. Does anything appear indicating that *hci found a new device?

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

            @UniSuperBox
            ran dmesg -w
            Plugged in MX4 UT device
            Got
            [253965.539781] usb 1-10: new high-speed USB device number 65 using xhci_hcd
            [253965.703835] usb 1-10: device descriptor read/64, error -71
            [253965.976791] usb 1-10: device descriptor read/64, error -71
            [253966.240752] usb 1-10: new high-speed USB device number 66 using xhci_hcd
            [253966.404820] usb 1-10: device descriptor read/64, error -71
            [253966.672783] usb 1-10: device descriptor read/64, error -71
            [253966.936735] usb 1-10: new high-speed USB device number 67 using xhci_hcd
            [253971.737477] usb 1-10: Device not responding to setup address.
            [253976.741015] usb 1-10: Device not responding to setup address.
            [253976.948675] usb 1-10: device not accepting address 67, error -71
            [253977.104558] usb 1-10: new high-speed USB device number 68 using xhci_hcd
            [253981.904552] usb 1-10: Device not responding to setup address.
            [253986.909068] usb 1-10: Device not responding to setup address.
            [253987.116359] usb 1-10: device not accepting address 68, error -71
            [253987.116387] usb usb1-port10: unable to enumerate USB device

            Plugged in MX4 Flyme device
            got
            [254161.429876] usb 1-10: new high-speed USB device number 69 using xhci_hcd
            [254161.628575] usb 1-10: New USB device found, idVendor=2a45, idProduct=2008
            [254161.628579] usb 1-10: New USB device strings: Mfr=2, Product=3, SerialNumber=4
            [254161.628581] usb 1-10: Product: MX4
            [254161.628583] usb 1-10: Manufacturer: Meizu
            [254161.628584] usb 1-10: SerialNumber: 75UBBKN22FQP

            Same port same cable (MX4 Flyme device now with USB module that was in MX4 UT device)

            Now what?

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

            1 Reply Last reply Reply Quote 0
            • U Offline
              UniSuperBox
              last edited by

              The device with Ubuntu Touch doesn't seem to be working correctly. See if you can plug it in to a USB 2.0-only port. You can also check if there's anything obstructing the pins in the port.

              The goal is to have an output like your Flyme device.

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

                @UniSuperBox I have tried it in a USB2 port and it was in a USB2 only port when I ran dmesg -w

                The fact that I have switched the USB modules between the devices rules out an obstruction.

                It must be a hardware issue past the USB port, or a software issue on the UT device.

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

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