Unable to install UBports on MX4 Ubuntu edition

[UKPhil]

When I was trying to install on my device I tried different cables and ports and nothing seemed to work. Know how frustrating it can be, but you will get there.

[Lakotaubp]

Guess you have but have you tried using the SP flash tool. I used it to put flyme on ut mx4 might work for you.

[halucigenia]

@UKPhil Thanks for the encouragement

[halucigenia]

@Lakota I will look into the SP flash tool. Thanks for the advice.

[Marathon2422]

@halucigenia Just curious,coming from flyme,did you go into dev mode,and permit OEM unlock.
Or from UT,switch to dev mode while unplugged then connect and watch that dev page,you should get a window asking to Allow PC to connect,(maybe !!)

[UKPhil]

@halucigenia have a gowith the process that I mentioned and see how you get on. This was the only thing that worked for me after being ready to throw it all in and go down the andriod route.

[halucigenia]

@UKPhil I can't get the devmode version of MDT to run
I ran
sudo apt update
sudo apt install snapd

I ran sudo snap install magic-device-tool --devmode

snap list
Name Version Rev Developer Notes
core 16-2.28.1 3017 canonical core
magic-device-tool 1.0 289 marius-quabeck devmode

When I run magic-device-tool as my normal user
I get the message "snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks"

When I run sudo magic-device-tool
I get the message "cannot change profile for the next exec call: No such file or directory"

Looks like snap is incompatible with my kernel
snap --version
snap 2.28.1
snapd 2.28.1
series 16
ubuntu 17.04
kernel 4.11.12-041112-lowlatency

I think snap needs an "Ubuntu supported" kernel.
I will try again when I can reboot into another kernel.

[halucigenia]

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?

[UniSuperBox]

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?

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

[UniSuperBox]

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.

[halucigenia]

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