@advocatux thanks for the link , I joined and will ask a bit later when I have more time to concentrate.

I have this issue too. Is there a workaround? N5. 16.04dev

full dmesg : https://pastebin.com/raw/TGeyuyW6

I had Meizu Pro 5 Ubuntu Edition but run into the https://forums.ubports.com/assets/uploads/files/1528013524195-8a15d567-ca4b-44ca-a1ce-84fdb7e0aec7-image.png screen when first trying to update it to Ubports 16.04/stable channel. Somehow now later I managed to flash - with ubuntu-device-flash - from within 16.04 ubuntu installation (actually, 16.04 lxd container with usb vendor specific passthrough). I did that by booting to Ubuntu's recovery installation with power button + volume up - this is where you might need the recovery-turbo.img but I had it flashed already. I verified that from within my lxc container (where I had added lxc config device add CONTAINERNAME meizu usb vendorid=18d1) I was able to see the device with 'adb devices'. Then I ran ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=ubports-touch/15.04/stable - I thought it got stuck after downloads, but actually then it started the "Pushing" phase. And even more to my surprise, it rebooted to flashing phase with Ubuntu prorgress bar going back and forth, and then booted into working Ubports installation! Even though I specified "15.04/stable", it seems it too pointed to 16.04 already, ie OTA-5. The greatest thing was that since I didn't need to specify --bootstrap or --wipe, it was even the same installation I used as my main phone back in the days, so I had all my apps and photos intact.

@freedman Ok thanks,anyway.

@antony1455 hi, have you finished the Halium porting part already? If the answer is 'yes', can you complete the info here https://github.com/Halium/projectmanagement/issues/57? Thank you

Hi, If your sources have the file init.qcom.rc, with this line: export LD_SHIM_LIBS /system/lib/libril.so|libril_shim.so:/system/lib/libcrypto.so|libboringssl-compat.so try change this to export LD_SHIM_LIBS /system/lib/libril.so|libril_shim.so build system.img and install again. regards

@azimoto9 show your manifest please

@faith you're welcome!

Really!? More crossposting? Also it seems everytime you crosspost in a new place you give less information. If this is meant as a followup it needs a summary and references to what has happened earlier. But you give nothing.

Hey, i write this to become the notification Hope we find a solution for this wonderfull phone

@synnyg_r If you flashed via script halium-install-standalone.sh dont forget to add argument with -p ut halium-install-standalone.sh -p ut path/to/rootfs.tar.gz path/to/system.img

@advocatux said in Install Fail with Installer: @batteryjuice4 it's better to start the installer first and then plug the device. Yes, I followed instructions.

@stefano No worries, we cannot just focus on the Librem, we want to be as broad as possible, as our users might not be happy if just locked into one hardware. There are many porters doing Halium ports right now, see https://github.com/Halium/projectmanagement/issues and WOW there are many good starting points for new devices already. Hopefully some of them will be great UT devices one day!

@qusay said in Halium sources ,Porting UT on Note 3 N9008: Hi,i'm trying to port ubuntu touch to note 3 n9008 the chinese version ,we all know that you must first get halium sources but my internet connection is bad ...real bad,so how many GBs is the sources tree? I think I heard people say 20 GB. the device doesn't have an official cm or lineage will it affect the process of porting? Well, if there is an inofficial port that works well, it won't have much effect. But if nobody has ported any rom then you are facing a very big challenge!

@4cc501 this is the list of supported devices http://ubuntu-touch.io/devices Go for the most potent one (depending on your budget). Anyway, OPO is a good phone. If you have the knowledge and patience, you can try to port a different phone model yourself https://docs.ubports.com/en/latest/porting/introduction.html