UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Installing - connection to device lost

    Scheduled Pinned Locked Moved Oneplus 3/3T
    69 Posts 16 Posters 18.1k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • ? Offline
        A Former User @geekyneo
        last edited by

        @geekyneo You don't need to install Oxygen OS. Just try it again.
        From which distribution are you installing? Some failed with Linux Mint.

        1 Reply Last reply Reply Quote 0
        • ? Offline
          A Former User @geekyneo
          last edited by

          @geekyneo Oh, you are using Windows.... Please try Ubuntu. No installation is necessary. A live system is enough.

          G 1 Reply Last reply Reply Quote 0
          • G Offline
            geekyneo @Guest
            last edited by

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

            Device : OnePlus 3T

            ? 1 Reply Last reply Reply Quote 0
            • ? Offline
              A Former User @geekyneo
              last edited by A Former User

              @geekyneo yeah, as I wrote before - some failed with Mint. Try Ubuntu. There is an open issue on Github.

              G 3 Replies Last reply Reply Quote 0
              • G Offline
                geekyneo @Guest
                last edited by

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

                Device : OnePlus 3T

                1 Reply Last reply Reply Quote 0
                • LakotaubpL Offline
                  Lakotaubp
                  last edited by

                  Just as a thought is that version of Oxygen ok for the OP3/3T or would an older version be better. Can't think why but are the partions off in some way? Probably nothing to do with it and the answer is easy but lost for now on this.

                  G 1 Reply Last reply Reply Quote 0
                  • G Offline
                    geekyneo @Guest
                    last edited by

                    @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 
                    

                    Device : OnePlus 3T

                    1 Reply Last reply Reply Quote 0
                    • G Offline
                      geekyneo @Lakotaubp
                      last edited by

                      Hi @lakotaubp

                      Actually the installer mentions the version to be 9.0.6 :smiling_face_with_smiling_eyes:

                      Device : OnePlus 3T

                      LakotaubpL 1 Reply Last reply Reply Quote 0
                      • LakotaubpL Offline
                        Lakotaubp @geekyneo
                        last edited by

                        @geekyneo Wasn't sure it's been some time since I installed OP3. I know thw OP5 does as that was the last one I did. Have you tried with and without the bootstrap option? This is odd very similar to issues with a OPO to.

                        G 1 Reply Last reply Reply Quote 0
                        • G Offline
                          geekyneo @Lakotaubp
                          last edited by

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

                          Device : OnePlus 3T

                          1 Reply Last reply Reply Quote 0
                          • G Offline
                            geekyneo @Guest
                            last edited by

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

                            https://pastebin.com/9xBp4y1L

                            Device : OnePlus 3T

                            LakotaubpL 1 Reply Last reply Reply Quote 0
                            • ? Offline
                              A Former User
                              last edited by

                              Sorry, but I can't help you any further. :man_shrugging_medium_skin_tone:

                              1 Reply Last reply Reply Quote 0
                              • LakotaubpL Offline
                                Lakotaubp @geekyneo
                                last edited by

                                @geekyneo All I can think off for now and you might not like it 🙂 is to flash the OP3 with the OS version it shipped with and go from there. That should put everything back to where it should be. You can then do all the dev mode stuff, mtp transfer usb debugging, adb permissions and try again.
                                That or try a much older version of the installer with the OP3 on it. Lost as to why it will not flash after clearing, formatting and so on.

                                1 Reply Last reply Reply Quote 0
                                • R Offline
                                  RapidRotator
                                  last edited by

                                  I had the same problem and decided to try and solve it by formatting both /data and /system. TWRP provides buttons to change the filesystem type for any partition, but afaik not to format any partition except /data. So using the UI I changed the filesystem of /data to ext4 and formatted it.

                                  Then I went into a shell ($ adb shell on my PC but TWRP has an internal shell too) and unmounted /system to format it:

                                  ~ # mount
                                  

                                  Note the block device /system is mounted on, then:

                                  ~ # umount /system/
                                  ~ # mkfs.ext2 /dev/block/<device>
                                  

                                  (Yes, that's ext2, not 4, but it won't matter)

                                  You can of course use the shell to format /data (and /cache) the same way if you want.

                                  After that, I could install UT by not ticking the boxes for first install and wipe device.

                                  I would be interested if others also succeed using this solution.

                                  K C MoemM 3 Replies Last reply Reply Quote 0
                                  • K Offline
                                    kriszie @RapidRotator
                                    last edited by

                                    @rapidrotator
                                    This worked for me! I only had to alter the commands, as 'mount' would not show /system and the adb shell did not recognize the mkfs.extX -invocation of mke2fs :

                                    OnePlus3:/ # cat /etc/fstab
                                    

                                    Get the block device...

                                    OnePlus3:/ # mke2fs -t ext4 /dev/block/<device>
                                    

                                    As the /system-partition was already ext4, I wonder whether wiping the partitions will be enough and the trick is not ticking the 'first install' and 'wipe device' boxes....

                                    Thanks a lot, anyways!

                                    R 1 Reply Last reply Reply Quote 1
                                    • R Offline
                                      RapidRotator @kriszie
                                      last edited by RapidRotator

                                      @kriszie mount without arguments will show anything that is mounted, and where. So if it doesn't show /system than it means that partition isn't mounted, so you don't have to unmount it. Sadly, UT doesn't have lsblk, my usual go-to for finding out what devices there are, mounted or otherwise.

                                      1 Reply Last reply Reply Quote 0
                                      • C Offline
                                        cela @RapidRotator
                                        last edited by cela

                                        @rapidrotator said in Installing - connection to device lost:

                                        I had the same problem and decided to try and solve it by formatting both /data and /system. TWRP provides buttons to change the filesystem type for any partition, but afaik not to format any partition except /data. So using the UI I changed the filesystem of /data to ext4 and formatted it.

                                        Then I went into a shell ($ adb shell on my PC but TWRP has an internal shell too) and unmounted /system to format it:

                                        ~ # mount
                                        

                                        Note the block device /system is mounted on, then:

                                        ~ # umount /system/
                                        ~ # mkfs.ext2 /dev/block/<device>
                                        

                                        (Yes, that's ext2, not 4, but it won't matter)

                                        You can of course use the shell to format /data (and /cache) the same way if you want.

                                        After that, I could install UT by not ticking the boxes for first install and wipe device.

                                        I would be interested if others also succeed using this solution.

                                        Isn't there a manual install instruction somewhere?, I thought it was on the devices page, i'd like to try installing
                                        manually, without the installer.
                                        None of these solutions worked me, been messing around for hours, wiped and formatted all partitions except USB-OTG.Even formatted
                                        SYSTEM using twrp terminal, still freezes on reboot, after installing. Even reinstalled Oxygen 9.0.6 using the installer and started over again.
                                        I can install Lineage OS from TWRP no problem.

                                        I can easily install, if I untick first install and wipe boxes, reboots, get the rotating
                                        ring on first boot, then on 2nd reboot stuck on "Powered by Android" splash screen.

                                        using ubports-installer_0.8.6-beta_linux_x86_64.AppImage and twrp-3.3.0-0-oneplus3.img newer versions of both
                                        freeze up.

                                        2x UBported Nexus 5 LG-D821

                                        1 Reply Last reply Reply Quote 0
                                        • MoemM Offline
                                          Moem @RapidRotator
                                          last edited by Moem

                                          @rapidrotator said in Installing - connection to device lost:

                                          I had the same problem and decided to try and solve it by formatting both /data and /system. TWRP provides buttons to change the filesystem type for any partition, but afaik not to format any partition except /data.

                                          This is the problem I seem to be running into today. The installer said something about needing to format both of these partitions, but I could not find where to do it in TWRP so I skipped it. This appears to have been a mistake. The phone can now not boot into any OS. (Not a drama as it was very cheap)

                                          Is there any way to fix this without terminal use? If not, is there any link or information that explains how precisely this is done through the terminal? The instructions as given here make my head spin, I'm afraid.
                                          Any sentence that starts with 'You can use the shell...' makes my inner technophobe shout 'No I &%$ well cannot'. 😵

                                          LakotaubpL 1 Reply Last reply Reply Quote 0
                                          • LakotaubpL Offline
                                            Lakotaubp @Moem
                                            last edited by

                                            @moem you can just boot back to twrp and you need to look under advanced wipe otptions. Clear format to ext4 cache and data. Then try again. You might need to do system as well.

                                            MoemM M 3 Replies Last reply Reply Quote 0
                                            • MoemM Offline
                                              Moem @Lakotaubp
                                              last edited by Moem

                                              This post is deleted!
                                              1 Reply Last reply Reply Quote 0
                                              • First post
                                                Last post