Closed enragegit closed 3 years ago
I'll add the info I had wrongly posted as a separate issue.
-The cable has worked perfectly flashing a good number of custom ROMs on this device and a bunch of others. It is highly unlikely that either the cable (tried three of them, which had already worked flawlessly flashing TWRP and images for many devices), or my USB ports (now tried two different ones) are faulty.
-As a temporary way around, is there a way to install manually? I would have no qualms about proceeding manually from the recovery, trying to "adb push" the image and flash it from there. Even if the UT Recovery has adb connection issues, one could temporarily boot TWRP, "adb push" the zip with it, and go back to the UT Recovery and flash from there. UT Recovery makes it apparent that it expects a zip to flash, so I am assuming it could be done like flashing a ROM from TWRP, but please disregard this comment if that last assertion is off base.
Tried again with version 0.8.8, but got the same result. The installer begins pushing the Ubuntu files, but at about 75% it shows the "lost connection" message. This time I formatted and wiped repeatedly. Tried both, leaving the formatting and the wiping for last, following a tip in the forum: https://forums.ubports.com/topic/6023/installing-connection-to-device-lost to no avail.
Edit: made absolutely sure the /data and /system partitions were ext4.
Just checked the logs, and it seems to be a Heimdall thing. command: exec: {"cmd":["heimdall","detect"],"error":{"message":"Command failed: heimdall detect\nERROR: Failed to detect compatible download-mode device.","code":1},"stderr":"ERROR: Failed to detect compatible download-mode device."} I'm not familiar with the role Heimdall plays here (as opposed to adb and fastboot or TWRP, which I have used many times), but will keep looking into the issue to add any detail I find of use to pinpoint the issue (and if I can fix it myself, I'll happily do it).
Tried from the AppImage version on a Manjaro distro, on an entirely different computer, the result was the same. At about 75% the transmission breaks and I get the "Lost connection" message.
Tried on a different computer using the snap package under Ubuntu Mate, and found #2016. In this case it looked like the OS was not able to reach the device (the notification area popped up a "lost MTP connection" error), so I would not blame the UT installer on this disconnection. The installer still installed the UT recovery.
On a second try, I got to the "Unable to connect to device" message, though this happened with the progress bar having not reached 10%, as opposed as in all the previous attempts where it reached somewhere around 70%.
OK, It is somehow working now.
In order to get it working I:
Some side notes: -The installer version was 0.8.8-beta -Maybe newer twrp versions work as well -twrp 3.1.0 would not even load. -twrp 3.2.3-1 would return errors when trying to wipe and format (which prompted me to use a more recent one and not to use the one built in, which incidentally is in the 3.2's).
I will be trying it again, to make absolutely sure it is reproducible and a valid solution. Once I do that I will close the issue.
The defining factor seemed to be to NOT select "wipe user data" in the UT installer. Quoted from #2160, credit MoemUT, who hit the nail in the head.
The installer does something it should not when the "Factory reset : remove user data" is ticked.
Repeated the install twice and the install was successful both times, so I can now close the issue.
UBports Installer
0.8.7-beta
(deb) Environment:LinuxMint 19.2 Tina linux 4.15.0-129-generic x64 NodeJS v12.18.3
Device: oneplus3 Target OS: it was the stable version 16.04 arm64 hybris stable. Settings:undefined
OPEN-CUTS run: https://ubports.open-cuts.org/run/60726768ed021f0007109b1d Log: https://paste.ubuntu.com/p/Fv3wWYzW7J/Installed latest manufacturer firmware (OxygenOS 9.0.6). Formated as asked by the UBports installer using TWRP. The installer got the Ubuntu recovery working. From there, it attemted to push the files to the device, unsuccessfully ("lost contact with the phone"). adb was detecting the phone in recovery mode, so the cable is not likely bad. Furthermore, I used the same wire to install a good number of ROMs, so unless one needs a special cable for U Touch, I seriously doubt it went bad.