@Keneda
thanks for doing that, I'll do that in the future. My first post here ...

And to answer @mark1250 Yes I do have adb and fastboot installed.

Update: I've created a PPA with the installer:
https://launchpad.net/~mardy/+archive/ubuntu/ubports-tools

Now I'll slowly add more devices 🙂

Problem has been resolved -- phone is now running UT OTA-19 stable.

Details about the fix in the device-specific post (see URL in previous post). I'll now mark this one as resolved as well.

Many thanks to all those who helped.

@bouleerbil : You're welcome! Hope it works for you too.

@alter The other thing to keep in mind is that not all devices seem to be affected. Quite a few I admit but not all. Then there are the problems some users had with 0.8.8/.9 on a completley different set of devices. So not quite as straight forward as it first seems. This is not ideal I will be the first to admit but as soon as there are answers we will let you know.
Also the offer is still there to anyone who wants to help with the installer or for that matter anything else. Let us know and we can direct you to the right people.

@reynald : Congratulations! Hope you will be as pleased with the system as I am 🙂

@reynald Files correctly dowloaded with installer 0.9.1beta.

Now it hangs at adb stage :

info: device detected: enchilada info: Installing Ubuntu Touch on your OnePlus 6/6T (enchilada) info: configuring... info: settings: {"bootstrap":true,"channel":"16.04/arm64/android9/stable"} info: Downloading 10 files info: Downloaded file 1 of 10 info: Downloaded file 2 of 10 info: Downloaded file 3 of 10 info: Downloaded file 4 of 10 info: Downloaded file 5 of 10 info: Downloaded file 6 of 10 info: Downloaded file 7 of 10 info: Downloaded file 8 of 10 info: Downloaded file 9 of 10 info: Downloaded file 10 of 10 error: Error: adb:preparesystemimage: Error: {"error":{"code":1,"cmd":"adb -P 5037 shell mkdir -p /cache/recovery"},"stderr":"mkdir: '/cache/recovery': Required key not available"} stack trace: Error: {"error":{"code":1,"cmd":"adb -P 5037 shell mkdir -p /cache/recovery"},"stderr":"mkdir: '/cache/recovery': Required key not available"} at /opt/ubports-installer/resources/app.asar.unpacked/node_modules/promise-android-tools/lib/module.cjs:117:20 at ChildProcess.exithandler (node:child_process:413:5) at ChildProcess.emit (node:events:394:28) at maybeClose (node:internal/child_process:1067:16) at Socket.<anonymous> (node:internal/child_process:453:11) at Socket.emit (node:events:394:28) at Pipe.<anonymous> (node:net:672:12)

I have moved this thread to sutopic

@tera yes confirmed: https://github.com/ubports/ubports-installer/issues/1990

@johhnycash maybe @NeoTheThird might be able to help.

Tested this with Oneplus2

When in bootloader, device is not recognized, error: "The device msm8994 is not supported"

In release 0.7.4, same situation, device is properly recognized as oneplus2.

@sahirul That sounds either like the unlock of the phone did not work properly, or your flash eMMC has some troubles.

From which Android are you coming from? I suggest you try to flash stock Android 5.1: https://dl.google.com/dl/android/aosp/hammerhead-lmy48m-factory-e01ca3b7.zip - and see if that works.

@poVoq Sure, i'm open to including any and all operating systems! I opened an issue about it a while back, happy to hear your input on weather pmbootstrap should be wrapped or re-implemented: https://github.com/ubports/ubports-installer/issues/1396

Sorry for the quick iterations, here's yet another one:

https://github.com/ubports/ubports-installer/releases/tag/0.7.4-beta https://ubports.open-cuts.org/build/5fb3f18b9702a600079dcfe8

Due to time constraints, we had to squeeze another minor thing in.

@NeoTheThird thank you, I will give it a try as soon as I am in front of my PC

Might be. The snap package handles udev rules (required for device access) that might cause issues when adding new devices. Could you check if another installer package, AppImage for example, sees the device?

@thilov
I tried the snap version ，same problem.