I was able to install Ubuntu Touch on Aquaris M10 HD with pre-installed Android 8.1.0. I am not experienced in flashing mobile devices therefore some things shown in the video were unclear for me but still very useful. I don't know what was important so I'm posting these steps combined from the video and official instructions that were lucky for me. If there is something wrong with it, please, correct me. Hope that it will help other unexperienced users in the future.

1. Start pre-installed Android 8.1.0 on the tablet (hold "Power" button) and enable developer mode and USB debugging there.

2. Power off the device by holding "Power" button.

3. Start the tablet by holding "Power" button and "Volume Up" button to select device's boot mode.

4. Choose "Fastboot mode" by "Volume Up" button and then press "Volume Down".

5. Device doesn't reboot automatically. Power off the device by holding "Power" button for a few seconds and then start it again by "Power" + "Volume Up" buttons and select "Recovery Mode".

6. In recovery menu select "Reboot to bootloader" item using "Volume Up"/"Volume Down" buttons and press "Power" button. => FASTBOOT mode... text will be shown at the left bottom corner of the blank screen.

7. I guess it's time to flash the firmware, but it was unclear from the video whether I should power off the device or not. So according to these instructions I decided to power off the device (hold "Power" button for a few seconds).

8. Download recent version of Smartphone Flash Tool and extract it's files from the archive. I used version 5.1916 for Linux 64-bit. To be exact, I'm on Kubuntu 18.04.1.

9. Install missing library for SP Flash Tool:

   $ wget -q -O /tmp/libpng12.deb http://mirrors.kernel.org/ubuntu/pool/main/libp/libpng/libpng12-0_1.2.54-1ubuntu1_amd64.deb \
   && sudo dpkg -i /tmp/libpng12.deb \
   && rm /tmp/libpng12.deb
   

10. Go to directory with SP Flash Tool and make it executable:

    $ cd ~/Downloads/ubports/SP_Flash_Tool-5.1916_Linux
    $ chmod +x ./flash_tool.sh
    

11. Start SP Flash Tool with root privileges:

    $ sudo ./flash_tool.sh
    

12. Download old Canonical UT image called cooler for M10 HD, unpack it and select Android_scatter.txt file from there in SP Flash Tool ("Download" tab => "Scatter-loading File").

13. Choose "Firmware Upgrade" from dropdown list.

14. Press "Download" button at the top left corner of "Download" tab.

15. Connect powered-off tablet to USB 2.0 port of the computer. "Magic happens" — old UT image will be downloaded into device and installed.

    I saw BQ logo with "Powered by Ubuntu" label at the end but unfortunatelly further UT loading was stuck. Nothing happened for a long time.

16. Download recent version of UBports Installer. It was deb of version 0.4.5-beta for me.

17. Start UBports with root privileges:

    $ sudo ubports-installer
    

    and follow it's instructions.

    When I ran "Reboot to bootloader" and saw => FASTBOOT mode like it was in 6, I didn't power off the tablet before connecting to computer. Everything was fine, I got rotating Ubuntu logo on the screen first, and working fresh Ubuntu Touch image three minutes later.

@Flohack I didn't find any proxy related tickets there so created a new one.

@Emmelyne, thanks for your answer.

Probably, there were some issues related to my Internet provider. I just reconnected right now and everything seems to work again.

@AppLee, no, I didn't check privacy settings yet but other users including maintener of the app have also confirmed the issue. Probably, it has been occurred due to recent refactoring.

@dobey, you are right about 4.0 version, it doesn't exist according to the provided specs. Seller mixed up the info. Finally, I purchased two items. One with Android 6.0.0 and unlocked bootloader, and another with Android 6.0.1 but locked bootloader. So I don't need to flash Android firmware first.

Installation to 6.0.0 was smooth and done in five minutes! This is awesome!

Installation to 6.0.1 took an half of an hour due to locked bootloader, and Ubuntu didn't start after the first attempt of flashing. It was Google logo on the screen and nothing happened. Fortunately, the second attempt was successful and also done in five minutes! Thanks to all of you, guys, all developers and ubports-installer-0.4.11-beta that also helped to unlock a bootloader in easy way!

@advocatux, thanks for the reply. And for firmware reference!

Relying on your answer I can update to 6.0.1 but not to 5.1. Ok, will purchase the item and do it then.

Hi, guys!

I'm interested in purchasing LG Nexus 5 device to use it with Ubuntu Touch and found it somewhere on eBay. A seller tells me that it's shipped with Android 4.0 (Ice Cream Sandwich) but can be upgraded to 6.0 (Marshmallow). Here is the reference:

https://www.gsmarena.com/lg_nexus_5-5705.php

I saw that devices with Android 5.1 and Android 7.1 only are supported to install Ubuntu Touch on (unfortunatelly, I unable to recognize where). Could you, guys, please, clarify these things?

• Is it possible to upgrade Android 4.0 to Android 5.1 (Lollipop) on this phone while Android 6.0 is mentioned for upgrade?
• Do I really need to upgrade Android 4.0 to Android 5.1 (Lollipop) before installing Ubuntu Touch?

Thanks in advance!

@Flohack, could you please merge Russian translations for TELEports from Weblate? I updated these translations in November fixing many issues such as this date formatting one. My wife, like me, uses Nexus 5 with UT as daily driver so this app is really important for us, and I'm ready for further contribution!

Hi, guys! I'm trying to build TELEports from sources in order to take a part in delevopment but unable to launch it on my Nexus 5. I followed simple guide from README.md:

git submodule update --init
clickable build-libs tdlib-prepare --arch amd64
clickable build-libs tdlib --arch armhf
clickable

Everything's got complied and installed on the device but it seems that the app crashes on startup — a logo is shown for a moment and then it closes.

These are last lines of output:

Successfully built package in './teleports.ubports_0.6.0.200209214823_armhf.click'.
/home/ezze/Development/ubports/teleports/build/arm-linux-gnueabihf/app...9214823_armhf.click: 1 file pushed. 4.9 MB/s (7490770 bytes in 1.460s)
Installing files              [=========================]         
Finished                      [=========================]         
Installing files              [=========================]         
Starting                      [=========================]         
Finished                      [=========================]         
Installed   	teleports.ubports-0.6.0.200209214823.armhf (installed:click,removable=1,app_name=push,app_name=teleports)	summary goes here

I tried to build from both master and latest v0.6.1...

How can I understard what's going wrong? Are any logs or debug information available? Sorry for these (probably) dumb questions. I'm not a C++ developer but JavaScript/Node.js one and would be happy to get some feedback.

@Flohack I didn't find any proxy related tickets there so created a new one.

I still have the issue. Sometimes it works but most of the time — doesn't. If you, guys, don't experience the same issue I believe it's the Telegram blocking in Russia.

@Flohack, keeping it in mind, could we add support for MTProxy in TELEports? Native desktop application unlike web application has such option.

@Flohack, I got it. And see that some translations for other languages are already merged. But still can't figure out the reason why Russian translations are not merged yet. There were some changes in translation strings and I believe that I fixed them yesterday. Could you, please, clarify a little bit how it works? Is there something missing in translations preventing them from being merged?

@Emmelyne, thanks for your answer.

Probably, there were some issues related to my Internet provider. I just reconnected right now and everything seems to work again.

Connected to device with adb shell and removed ~/.local/share/teleports.ubports. Now I'm singed out, and the app hangs when I enter my phone number on login. So it's a connection issue, as I guess.

Another observation — when I go to menu and select "Settings" the application becomes non-responsive. Uninstalling application and installing it again doesn't help. It still recognizes my account. Probably, I have to remove some files from file system manually.

The most dissapointing moment here is that the app behave the same on all of my devices so, I guess, it's not a device specific issue.

@Lakotaubp still the issue for me. First, I thought that it could be probably some kind of blocking Telegram in Russia but I had no problems with it for months... And official applications are working.

I'm out of idea.

Hi, guys!

I have three UT devices (two Nexus 5 and BQ Aquaris M10 HD), and TELEports stopped to work on all of them today. Seems it's unable to connect to Telegram server and get updates (chat list and messages) — loading indicator runs from left to right and vice versa forever. Push notifications still come but I have no luck to read or write something in the app.

I tried to run official desktop and web Telegram applications in the same home network and they are running fine for me!

Any thoughts?

@Flohack, could you please merge Russian translations for TELEports from Weblate? I updated these translations in November fixing many issues such as this date formatting one. My wife, like me, uses Nexus 5 with UT as daily driver so this app is really important for us, and I'm ready for further contribution!