@Alain Oh wait, so you haven't unlocked the bootloader yet earlier? I assume only the toggle in Android?

@Alain said in What is my Halium version?: UBPorts Installer is built upon Halium, I think. No it is not. Halium is related to installing a "not android system" on an android system native device. Trivially it is a software that Iinks android hardware device drivers and Linux kernel ("extracted" from an android rom) with GNU/Linux operating system ported to that device. https://halium.org/ I see no "halium" anywhere on my computer. That's perfectly normal. You, as simple user installing UT on a device, don't have to deal with halium. You only have to unlock bootloader and install the required android rom on that device. have Android 11, but how do I check my halium version? Again, you don't have to, you "only" need to install the required android rom. If it's android 10 then android 10 it is... No halium stuff for you. To summarize, what you need to know, is the android version installed on your device. And if needed you have to install the exact one required before installing Ubuntu Touch.

@lenkhulu I'm glad to hear that!

It is currently hard-coded. https://github.com/ubports/ubports-installer/blob/master/src/core/helpers/api.js#L25

The last step installs the rootfs usually in system partition, see the install section of the porting documention. Basically flash the latest xenial image from the CI to system. Alternatively push the image with adb to /data/system.img when booted to recovery. Otherwise you could try ubports installer with only the systemimage:install command. You can also see the halium-install source code, particularly these lines. Be sure to check if this partition exists as partition schemes can vary.

@stanwood It's not me, its @rubencarneiro . He told me in a PM the other day he was putting them forward for the installer and here they are! My interest was the Lenovo Tab. I am working on the coding bit, time is against me at the moment with other things in life! I didn't see this mentioned in the forum so I thought it was worth promoting.

@Dave I just had the same problem. When I tried to open https://ubports.open-cuts.org/ in Firefox, it gives a certificate error as well.

@TheVancedGamer Thank you, that is what I thought. I wonder why recently the devices would hang and UT would not be pushed over ADB. This issue stopped when I upgraded Android Studio to the latest version ("Giraffe"), on Windows and Ubuntu.

I just found out that my ISP doesn't support IPv6. Anyway around that?

The device page says that it is under development but is currently only on xenial not focal. You could try contacting the porter for more details.

@klh Thats what I thought.

@arubislander said in Postmarketos on the Ubports installer: @carrabelloy said in Postmarketos on the Ubports installer: I tried it and I can tell you that it does not work, That is unfortunate. Did you contact the postmarketOS community? I am assuming they test and maintain the installer configuration. I must say my morpf browser and a deepl goes very well here. So that I can answer here well better as on my first the onplus on. Which I have in cardboard and everything here. But are probably my Händy and finger too big. now it runs after erbelichen difficulties on my FP4.

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