@thilov , the same installer works perfectly fine for OnePlus One and installation was a success.

https://pastebin.com/9xBp4y1L

@lakotaubp the installer doesn't show oprion of bootstrapping like in OPO.

Hi @lakotaubp

Actually the installer mentions the version to be 9.0.6

@thilov it's failing for Ubuntu 20.04 installed on a system.
Installer versions tried are 0.8.4 & 0.8.8.

{"level":"info","message":"Downloaded file 1 of 12"}
{"level":"info","message":"Downloaded file 2 of 12"}
{"level":"info","message":"Downloaded file 3 of 12"}
{"level":"info","message":"Downloaded file 4 of 12"}
{"level":"info","message":"Downloaded file 5 of 12"}
{"level":"info","message":"Downloaded file 6 of 12"}
{"level":"info","message":"Downloaded file 7 of 12"}
{"level":"info","message":"Downloaded file 8 of 12"}
{"level":"info","message":"Downloaded file 9 of 12"}
{"level":"info","message":"Downloaded file 10 of 12"}
{"level":"info","message":"Downloaded file 11 of 12"}
{"level":"info","message":"Downloaded file 12 of 12"}
{"level":"verbose","message":"running core action write"}
{"level":"verbose","message":"running adb action wait"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"wait-for-any-any\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"get-state\"],\"stdout\":\"recovery\"}"}
{"level":"verbose","message":"running adb action preparesystemimage"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"mount -a\"],\"error\":{\"message\":\"Command failed: adb -P 5037 shell mount -a\\nmount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument\",\"code\":1},\"stderr\":\"mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"cat /etc/recovery.fstab\"],\"stdout\":\"# Android fstab file.\\n# The filesystem that contains the filesystem checker binary (typically /system) cannot\\n# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK\\n\\n#TODO: Add 'check' as fs_mgr_flags with data partition.\\n# Currently we dont have e2fsck compiled. So fs check would failed.\\n\\n#<src>                                                       <mnt_point>       <type>  <mnt_flags and options>                                                                                         <fs_mgr_flags>\\n/dev/block/bootdevice/by-name/boot                           /boot             emmc    defaults                                                                                                        defaults\\n/dev/block/bootdevice/by-name/recovery                       /recovery         emmc    defaults                                                                                                        defaults\\n/dev/block/bootdevice/by-name/system                         /system           ext4    rw,barrier=1,discard                                                                                            wait\\n/dev/block/bootdevice/by-name/userdata                       /data             ext4    nosuid,nodev,noatime,barrier=1,noauto_da_alloc                                                                  wait,check,encryptable=footer,formattable,length=-16384\\n/dev/block/bootdevice/by-name/persist                        /persist          ext4    nosuid,nodev,barrier=1                                                                                          wait\\n/dev/block/bootdevice/by-name/dsp                            /dsp              ext4    ro,nosuid,nodev,barrier=1                                                                                       wait\\n/dev/block/bootdevice/by-name/modem                          /firmware         vfat    ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337                                                        wait\\n/dev/block/bootdevice/by-name/bluetooth                      /bt_firmware      vfat    ro,shortname=lower,uid=1002,gid=3002,dmask=222,fmask=333                                                        wait\\n/dev/block/bootdevice/by-name/misc                           /misc             emmc    defaults                                                                                                        defaults\\n/dev/block/bootdevice/by-name/logo                           /logo             emmc    defaults                                                                                                        defaults\\n\\n/devices/soc/6a00000.ssusb/6a00000.dwc3/xhci-hcd.0.auto/usb* auto              auto    defaults                                                                                                        voldmanaged=usbdisk:auto\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"rm -rf /cache/*\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"mkdir -p /cache/recovery\"]}"}
{"level":"debug","message":"adb created /cache/recovery directory"}
{"level":"verbose","message":"running adb action push"}
{"level":"command","message":"spawn:start: {\"cmd\":[\"adb\",\"-P\",5037,\"push\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/ubports-b338720c09678eb1ab6ce28b4c8e6ea5be08911b7c65e743d770eebd1521c5e4.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/ubports-b338720c09678eb1ab6ce28b4c8e6ea5be08911b7c65e743d770eebd1521c5e4.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/device-762c2b584c58b5d2ff8f89917b0e4599cd054f74cbdfa37441bc6c9575112870.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/device-762c2b584c58b5d2ff8f89917b0e4599cd054f74cbdfa37441bc6c9575112870.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/version-6.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/version-6.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-signing.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-signing.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-master.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-master.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/ubuntu_command\",\"/cache/recovery/\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"mount\"],\"stdout\":\"rootfs on / type rootfs (rw,size=2838236k,nr_inodes=709559)\\ntmpfs on /dev type tmpfs (rw,nosuid,relatime,size=2918868k,nr_inodes=729717,mode=755)\\ndevpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)\\nproc on /proc type proc (rw,relatime,gid=3009,hidepid=2)\\nsysfs on /sys type sysfs (rw,relatime)\\ntmpfs on /tmp type tmpfs (rw,relatime,size=2918868k,nr_inodes=729717)\\ntmpfs on /storage type tmpfs (rw,relatime,size=2918868k,nr_inodes=729717,mode=050,gid=1028)\\npstore on /sys/fs/pstore type pstore (rw,relatime)\\nadb on /dev/usb-ffs/adb type functionfs (rw,relatime)\\n/dev/block/bootdevice/by-name/system on /system type ext4 (rw,relatime,discard,data=ordered)\\n/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,nosuid,nodev,relatime,data=ordered)\\n/dev/block/bootdevice/by-name/dsp on /dsp type ext4 (ro,nosuid,nodev,relatime,data=ordered)\\n/dev/block/bootdevice/by-name/modem on /firmware type vfat (ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)\\n/dev/block/bootdevice/by-name/bluetooth on /bt_firmware type vfat (ro,relatime,uid=1002,gid=3002,fmask=0333,dmask=0222,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)\\ntmpfs on /cache type tmpfs (rw,nosuid,nodev,noatime,size=262144k,nr_inodes=729717,mode=771,uid=1000,gid=1000)\"}"}
{"level":"warn"}
{"level":"command","message":"spawn:exit: {\"cmd\":[\"adb\",\"-P\",5037,\"push\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/ubports-b338720c09678eb1ab6ce28b4c8e6ea5be08911b7c65e743d770eebd1521c5e4.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/ubports-b338720c09678eb1ab6ce28b4c8e6ea5be08911b7c65e743d770eebd1521c5e4.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/device-762c2b584c58b5d2ff8f89917b0e4599cd054f74cbdfa37441bc6c9575112870.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/device-762c2b584c58b5d2ff8f89917b0e4599cd054f74cbdfa37441bc6c9575112870.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/version-6.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/version-6.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-signing.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-signing.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-master.tar.xz\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/image-master.tar.xz.asc\",\"/home/neo/.cache/ubports/oneplus3/Ubuntu Touch/ubuntu_command\",\"/cache/recovery/\"],\"code\":1}"}
{"level":"debug","message":"attempting to handle Error: no device"}
{"level":"warn","message":"lost connection to device"}
"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"wait-for-any-any\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"get-state\"],\"stdout\":\"recovery\"}"}
{"level":"verbose","message":"running adb action preparesystemimage"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"mount -a\"],\"error\":{\"message\":\"Command failed: adb -P 5037 shell mount -a\\nmount: mounting 

@thilov , I can confirm that it's failing for UBports snap installer 8.8.0 on Ubuntu 20.04 live machine, with device on Oxygen OS 9.0.6.
I've followed all the wipe/format step as instructed by you.

@thilov It's linux Mint(based on Ubuntu). It's not windows...

@thilov

Request you to please check logs : https://pastebin.com/E7DXEktC

@thilov what about the OS ?
I mean if a previous installation failed, do I need to install Oxygen OS and then follow your steps or can continue directly after failure ?

Thanks @thilov

Trying it now.

Hi @thilov, @mikeglover

Would request you to kindly the steps and the sequence in which the Format/Advance Wipe should be used to successfully install UT on OnePlus 3T.

I've tried every sequence possible and those mentioned on the page.

I have the same observation as @En-Ragegit .

Also do mention the installer version, TWRP version etc.

The installer is able to successfully install the Oxygen OS but not UT using the same cable. On installing UT the process ends up saying "Connection to device lost".

Also if there is any manual step to perform the installation ?

Best Regards