adb detects the phone : adb devices

• daemon not running; starting now at tcp:5037
• daemon started successfully
  List of devices attached
  75HABM3QVHRX device
  but the installer doesn't detect it ,have to do it manually and after running the installer got same problem,like always
  phone will be not detected in recovery mode.

Try this, phone not connected to PC, boot it in recovery mode, then plug to PC and do the "adb device" command.
If device not listed, this is an ADB driver issue.

On windows (see my own mx4 issue topic link i gave you above) i had an issue with ADB driver, i had to "attach" the driver for MX4 on each boot mode, normal mode, recovery mode, and fastboot mode.

@stefwe Maybe you should create your own topic in order to not interfer with OP problem as it's not the same.

@stefwe
Quick tip, have you tried to switch to Devel or RC channel then revert back to stable ?

Switch to another channel don't work.

@AppLee said in can't reinstall Ubuntu touch on MX4 Meizu-Ubuntu edition:

The file not found error might indicate a data corruption on your phone and no other attempt to download it again.
I don't know how to check the eMMC memory integrity but the "FILE SYSTEM ERROR" made me think that it's likely a data corruption or FS corruption.

It looks like a bigger problem

• daemon not running; starting now at tcp:5037
• daemon started successfully
  List of devices attached
  75HABM3QVHRX device
  but the installer doesn't detect it ,have to do it manually and after running the installer got same problem,like always
  phone will be not detected in recovery mode.

Then you have to run the installer on your desktop.
From your previous post I'd say that the installer is OK, now you just need to be able to connect your phone using ADB.
If you already have an older version of Ubuntu Touch I'd say that you have the bootloader unlocked.

Now what does adb tells you when you run adb devices ?

The file not found error might indicate a data corruption on your phone and no other attempt to download it again.
I don't know how to check the eMMC memory integrity but the "FILE SYSTEM ERROR" made me think that it's likely a data corruption or FS corruption.

I'm running ubports ota11 on my mx4. But it is impossible to install ota12 on the device.

If you're already running UBports on your device, you don't need UBports installer to upgrade from OTA11 to OTA12, you just need a good 3G or 4G or WIFI connection and then only go to the phone settings and do the update with Over The Air method...

With the installer i get the following error:

error: Error: adb:format: Error: {"error":{"killed":false,"code":1,"signal":null,"cmd":"/opt/ubports-installer/resources/app.asar.unpacked/platform-tools/linux/adb -P 5037 shell echo ."},"stdout":"","stderr":"error: insufficient permissions for device: user in plugdev group; are your udev rules wrong?\nSee [http://developer.android.com/tools/device.html] for more information"}
stack trace: Error: {"error":{"killed":false,"code":1,"signal":null,"cmd":"/opt/ubports-installer/resources/app.asar.unpacked/platform-tools/linux/adb -P 5037 shell echo ."},"stdout":"","stderr":"error: insufficient permissions for device: user in plugdev group; are your udev rules wrong?\nSee [http://developer.android.com/tools/device.html] for more information"}
    at /opt/ubports-installer/resources/app.asar/node_modules/promise-android-tools/src/adb.js:66:13
    at /opt/ubports-installer/resources/app.asar/src/utils.js:282:7
    at ChildProcess.exithandler (child_process.js:319:5)
    at ChildProcess.emit (events.js:194:13)
    at maybeClose (internal/child_process.js:998:16)
    at Socket.<anonymous> (internal/child_process.js:403:11)
    at Socket.emit (events.js:194:13)
    at Pipe.<anonymous> (net.js:593:12)

If your running on a windows PC, see this : https://forums.ubports.com/topic/4026/solved-problem-upgrading-mx4-from-ota15-to-ubport/13

Has this been fixed already: https://github.com/ubports/ubports-installer/issues?page=1&q=mx4
I mean the numerous Fastboot errors? Never worked for me because the device can't reboot itself to recovery from Fastboot - user has to do that manually and the installer breaks not expecting that :(. But I haven't tried that recently so maybe that's fixed now - but was not for a long while.

I'm very glad installation on the N5 went well.

Regarding your MX4, most issues occurs out of the installer.
From what I read here in the forum people sometimes struggle to unlock the bootloader or to connect their phone to the computer.

Just so you know, that is not something an update of the installer could solve.