Installing - connection to device lost
-
The installer offered to reinstall OxygenOS, and that worked! So at least the thing boots again. More experiments to follow soon.
-
@moem Original thread https://forums.ubports.com/topic/3253/oneplus-3-3t/616 very long and a bit of a ramble. Start at about 5th Nov.
-
@lakotaubp I don't see anything relevant in that thread... maybe I'm missing something?
-
@moem https://forums.ubports.com/topic/3253/oneplus-3-3t/59 fromm the 5th Nov 2019 is where the first mention of using TWRP starts down to about 19th it might give some hints on how to sort it.
-
@lakotaubp Ah, THAT fifth of November! Will check, thank you.
Edit: I see a lot of mentions of using TWRP for wiping cache/data/system partitions... which I have done at least five times today in different ways.
No success yet. -
@moem Just found this
libremax Just trying to think what I did with twrp. Wipe option, format data-select yes, then in advanced wipe repair change system and data to ext4 then reboot. Then just ran the installer with wipe and bootstrap, booted to fastboot then recovery for the rest. I do remember it took ages for the spinning circles to appear to say it was flashing the device. Remember thinking it had not worked at first. Maybe leave it a little longer rather than force reboot but bit confused I must admit.But that's about all. Will keep looking
-
@lakotaubp said in Installing - connection to device lost:
Then just ran the installer with wipe and bootstrap,
I know about the wipe, but what is the bootstrap?
It does not take long at all to tell me it's flashing. It always fails during the 'pushing files to the device' phase. And I never try to reboot at all... there is, after all, nothing to reboot.Thank you for your time!
-
@moem It was an option given in the installer is it not there now? Also found this from Flohack
FlohackFlohack 31 Jan 2021, 08:34
@sven Also delete system partition to be sure
- If there was encryption used for data before, it needs to be formatted, a simple wipe wont work.Might not help but explains why.
-
@lakotaubp said in Installing - connection to device lost:
It was an option given in the installer is it not there now?
I see two options: First Install (tick if the device was running Android before) and Wipe Data. Dalton advised me to tick them both.
I've wiped all the things.... so many times. And done a factory reset, and reinstalled Oxygen. All partitions show up as Ext4.
I don't by now even remember what I've tried.Is currently using an Op5t
Also owns an Op1, a BQ E4.5 and an Xperia X, as well as a BQ tablet and a Pinetab2. Please, someone... make it stop. -
@moem Sounds like time for a break and come back fresh. Packing in for today soon myself . Good luck and will keep thinking.
-
@lakotaubp said in Installing - connection to device lost:
Sounds like time for a break and come back fresh.
You are most likely right. Thank you, again, for your time!
-
@moem I found that it is better to tick "First Install" regardless, then the installer guides you through what you need to do in TWRP recovery to prep the partitions, I also found that if you untick "Wipe Data" the install completes to 100%, otherwise I get the connection lost dialog at around 75% if I tick "Wipe Data".
I can 100% complete the install every time now but my device freezes on the 2nd reboot after install.
I am using UBports installer version 0.8.6 beta on Endeavour OS. It might help if anyone has success to let everyone know which installer version they are using and on what OS.
I am thinking of getting access to a Windows machine to see if it makes a difference, I have tried different usb cables in both front and rear USB ports.
2x UBported Nexus 5 LG-D821
-
@cela said in Installing - connection to device lost:
I also found that if you untick "Wipe Data" the install completes to 100%
Holy macaroni.
You, kind sir/madam/other, are the hero of the day. This was the winning tip. My Op3 is now proudly running UT!my device freezes on the 2nd reboot after install.
I will report back once I know whether mine does that too. I used the 0.8.9 .deb on Linux Mint.
-
@moem Now that is something to remeber, and well done on sorting it.
-
@cela That no wipe thing is one to remember. Thanks.
-
@lakotaubp
That no wipe thing is one to report -
-
@lakotaubp Hi! Another one with the same problem. Can you explain how to do that using TWRP? Or share some place I can found the information?
I suppose first I have to go no Mount and mount both partitions, then go to Wipe -> Advanced Wipe (but there's nothing about file system (ext4))
And when it's done I will be able to install using UBports Installer or I will need to do it manually
Thanks!
-
@mpararols Here is what I would try, knowing what I know now:
Run the installer. Tick 'first install', untick 'wipe data'. Follow the guidance about TWRP that the installer gives you.If that doesn't do it, you can reflash OxygenOS from the installer (yes you can!), install TWRP on that again, and run it; first do the wipe as described above:
Wipe option, format data- select yes
And after that, the following:
then in advanced wipe repair change system and data to ext4 then reboot.
That repair/change system section is easy to overlook. But you may not need to do all that since TWRP is also invoked by the installer during installation, and the messages that I saw on the screen as it was doing its thing led me to believe it does in fact take care of the partitions and their file systems.
So I'd first try the Installer again.
-
Maybe half related to this topic, but just to share my experience with UBports installer 0.9.1 Beta (Ubuntu 20.04 snap)
I just test a re installation (no wipe) on Vollaphone and Redmi Note 7. Note that both devices were already equipped with Ubuntu Touch OTA-19 Stable.
If we follow carefully the instructions of the installer, we first have to connect the device to the computer, and Installer should detect it at first attempt.
Vollaphone: recognized without problem
Redmi Note 7: recognized as "Halium device arm64" not compatible.First on Vollaphone, I continue the installation, uncheck "Bootstrap partition", select "Ubuntu Touch", then "NEXT".
The installer displays "Download 12..13...14 on 14 files", then "Pushing files to device", then "Yikless, something wrong... Try again".
At this point, the device is still powered on.
So I turn off the device, turn it back on in recovery mode, and select "Try again".
The installer repeats the "Pushing files to device" operation, then "Succeed". The Vollaphone displays "Applying update", then restarts. Everything went well. I validate "Pass" in the installer to validate the success of the operation.I then do the same operation with the Redmi Note 7, and the result is identical. I have to restart it in recovery mode for the installation to be successful.(+ select manually the device)
I would suggest to add an instruction in the installer asking the user to restart it manually in recovery mode for the installation to continue. (or maybe there was and I didn't see it) Or enable the installer to reboot automatically the device in recovery (?)
I hope those clarifications would help users who fail to re-install Ubuntu Touch on their devices....
