Topics

It works with Pro1, however, a bit more complicated to replace as it does not come together with a frame. However, as far as I have found, these displays (at Aliexpress) are not perfect, so you should expect some (mostly minor) problems like smaller or bigger blank (black surface) area at one or two corners. I have even received a display which has a relatively large black spot in a very wrong place. So, generally they are useable, but some minor problems (mostly acceptable) are exists, so it is unlikely you will receive an absolutely perfect one. I have replaced my display bought at Aliexpress twice, the first one has developed a whiter and whiter screen in every colours temporarily, then it became its only way to "work" after a few months of use. So I am on my second replacement which also has some colour temperature problem (the first one was the same like original one) at lower brightness (it is blueish instead of greenish like original display).

I will try [email protected] Both of mine went to [email protected] Thanks. And an update, I read some old posts where someone confirmed that the elephone u/u pro screen is what the Pro1 uses. Found one here and it is several times cheaper than what F(x)tec charged me: https://www.aliexpress.com/item/1005002314744127.html?spm=a2g0s.9042311.0.0.64fe4c4dJvkrmj There is a month delivery time, but I have already waited much longer for a screen from F(x)tec that I have no idea if it has/ever will ship.

Yes I have very bad call quality... it's very muffled. I'm currently on LOS 18.1 If AICP performs better I may move to that :(

Congratulations Zahkc for getting it done and a very big Thank You for writing this up! Excellent work, I was about to share the notes I have made while dressing up my Pro1 to get famous, but that were already some meters to scroll (thats how it felt 😉 ) ... and you nailed it down.  My way to get to dual booting was slightly different in details. But all in all the same. Still I want to paste some additional notes here. ****************************************************************************************************************** Basic things I learned, that might enlight the guide from above a bit: - Always use a proper USB cable to connect your phone. There are lost of cheap ones around that are only capable of charging. Check before you start if you can transfer data (i.e. a picture) from the phone. - All fastboot commands have to be fired on a pc and with the phone connected via USB and beeing in "Bootloader Mode" - The adb sideload commands on pc need to have the phone connected via USB and  in "Recovery Mode" - AND sideloading needs to be supported by the phone's installed recovery image. Pro1 Bootloader Mode:       see "pro1_bootloader.jpg" attached While the phone beeing switched off  - press and hold "volume DOWN" and "power" simultaneously until you see a green START in the phones display. --> I recommend to unplug USB cable (when switching off) because phone "wakes up" while charging after a while (this ) --> I recommend concentrate on the finger on the power and only release that in the moment the START appears. That might save you from unwanted system starts ...     The other finger might than trigger other menu items, but you still beeing in "Bootloader Mode" .     Then play with the volume buttons to cycle the available menu items. The one currently to be seen can executed with power switch. But thats not needed here. Unfortunately there is no menu item offering to switch the slot, so you need to do that with other tools: During setup (and whenever you want) from your pc (with fastboot commands) and finally with apps from within the OSes. The Bootloader Mode is provided by the phones "hardware". So it is always accessable, even when you did something wrong while flashing or sideloading. So don't be afraid, you can always start from here. Pro1 Recovery Mode:   see "pro1_ubuntu_touch_recovery.jpg" and "pro1_lineageos_recovery.jpg" attached While the phone beeing switched off  - press and hold "volume UP" and "power" simultanously until you see something in the phones display.    Within 30 secs (longest wait) the recovery mode should be reached, otherwise the recovery image is broken --> goto Bootloader Mode and flash a working one. To get into recovery mode there needs to be a proper recovery image flashed. So this can possibly fail if something went worng before, but then you still have the bootloader mode for flashing the right recovery image. There are different recovery images available, I have seen one for Ubuntu touch, stock android, LineageOS and TWRP. As a thumb rule: The image files are between 24MB and 67Mb in size and even though they are sometimes named "boot...img", they usually bring data for the boot partition AND recovery mode  ... For setting up dual boot Ubuntu Touch and LineageOS we only need recovery mode for the adb sideload for LineageOS...zip. All the rest is done in bootloader mode or while booted in one of the OSes. Befor sideloading files check with command "adb devices" if there is something like   List of devices attached   b7****08    sideload <--- With these recovery images the slot-story comes into play. For me it was sufficient to know that either slot keeps some of the partitions important for the boot process. So each slot can have its own recovery mode. Other partitions (and there are more than 50) are not separated by the slots. For example, there aren't two different partitions keeping the boot splash image ... (so that we can not have different early boot logos [a.k.a. "splash.img"] for the two OSes 😞 ) . Usually, when installing a single OS on the phone, both slots (more correct: the separate partitions for each slot) are getting written equally. It doesn't matter which slot is active and used for booting up. I and possibly most of us never even noticed, that during an system update/upgrade the slots (precise: the other slot) become filled with different data and the curently active slot changes. From then on you boot with the other slot, until the next upgrade ... Here we manually decide to write the slots differently so that each OS can boot up with the data from its slot partition(s) to a stage where it is able to find and load everything needed from the other partitions. In the consequence we have to say good bye to convinient ways of do system upgrades. I am preety sure that more experienced users will find out how to do that anyway ... Helpfull command: How to check for current active slot (with fastboot and phone in Bootloader Mode) fastboot getvar all 2>&1 | grep slot #(--> current-slot:X) Ubuntu Touch has a lot of mountpoints to subdirs below /userdata (the userdata-image/-partition for android), see /etc/fstab . As the subdirs are different from Android default dirs, they can coexist.   All this above might be more or less incorrect description, but it's not needed to know better for setting up dual boot. ****************************************************************************************************************** Okay, MY installation process differs from the Zahkc's way in the point, that I "started" with Ubuntu Touch installed as a/the single OS. I wonder if the procedure to flash stock android with ext4_QX1000_user_20200825231445_dd49dd0dd1.7z is really needed. Maybe stock android has to bring a basic partition structure to the phone. If I had to start again, I would try without. The stock android file is hard to handle, it is 1GB big itself, it extracts 3GB of files additionally and forces you to have 7zip capable software ... Helpful command if you only want to extract single files from that 7z (example splash.img): 7z e '/path/to/ext4_QX1000_user_20200825231445_dd49dd0dd1.7z' -o/which/dir/the/file/should/be/extracted/to/ splash.img -r Actually I had Ubuntu Touch installed as single OS AFTER my tries with stock android ... and then startet with sideloading LineageOS ... In case you are looking for the boot/recovery-image for Ubuntu Touch, get it from here: https://cdimage.ubports.com/devices/pro1/boot.img The link ist taken from the UBports installer config file for pro1: https://github.com/ubports/installer-configs/raw/master/v2/devices/pro1.yml (look for the lines with "url:") The recovery mode of Ubuntu Touch does not have the functionality to receive/install sideloads. So I flashed the LineageOS-recovery into slot A , set A active , then booted into slot A recovery (LineageOS recovery) , sideload the LOS...nightly...zip, just the same commands as Zahkc did. Remember: The command "fastboot erase userdata" allways includes the removal of all individual/personal data you had on the phone. Maybe even for both OSes! As I already had Ubuntu Touch installed before, I did not need to install it again. But, the original Ubuntu Touch boot/recovery partitions (in slot A) where overwritten/flashed with the LOS-recovery by me before, so this had to be corrected: Just fastboot flash boot_a /path/to/downloaded/ubuntu-touch/boot.img. Before booting into LineageOS the very first time I decided to integrate GoogleApps via this instruction https://wiki.lineageos.org/devices/pro1/install#installing-lineageos-from-recovery (I took MindTheGapps arm64) I never used Magisk before, but it is needed for root access (for app "switch my slot") in LineageOS. I installed MagisK after I had used my new LineageOS already for some time. So installation can, but has not to be done during dual boot setup ... I downloaded version 21.4 zip (last version available as zip)   see https://github.com/topjohnwu/Magisk/releases   Direct link https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip Magisk installation - boot again into LinageOS recovery (yes, this is slot b 😉 ) - --> Advanced --> Enable ADB and   --> Apply Update --> Apply from ADB - then sideload Magisk zip file   adb sideload /path/to/Magisk-v21.4.zip After booting into full LineageOS there will Magisk appear between the installed apps. The app "Switch My Slot" now can get root access but still needs the bootctl module for Magisk. See https://github.com/roihershberg/bootctl-binary/releases Direct link v2.0: https://github.com/roihershberg/bootctl-binary/releases/download/v2.0/bootctl-binary-v2.0.zip Download or copy it to the phone (into LineageOS). Im Magisk tap on the "jigsaw"-icon in the lower area and then "install from storage", then install bootctl...zip. Reboot. Done!   Cheers, order#10148  

This is an assumption but I presume you need to side load the updates each time to the correct slot instead of using auto updates.  (Also assume auto update needs to be turned off)