Installing - connection to device lost

Keneda · 2 Oct 2021, 18:33

@lakotaubp
That no wipe thing is one to report

Lakotaubp · 2 Oct 2021, 18:35

@keneda @Moem has already done that and it will be looked into. If anyone else has a similar issue please let us know device and installer version.

mpararols · 6 Oct 2021, 08:26

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

Moem · 6 Oct 2021, 09:26

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

stanwood · 6 Oct 2021, 11:45

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

Lakotaubp · 6 Oct 2021, 13:00

@mpararols Appologise for the late reply but @Moem has given you all the info you should need and @stanwood has added a few more hints if needed. Give them a go and if you have any issues just pop back and we will do our very best to get it sorted.

mpararols · 6 Oct 2021, 18:42

@moem Thank you very much. I have to do it twice, installing Android 9 but finally I get my Ubuntu Touch working!

Thanks

Lakotaubp · 6 Oct 2021, 18:52

@mpararols Good news and well done.Enjoy

Moem · 6 Oct 2021, 20:02

@mpararols Hurray! That is very nice to hear! Congratulations.

wusa · 22 Apr 2022, 07:56

Hello,
I was on a custom ROM and tried to install UT according to instructions.
It is an OP3 in my case.

First I installed Oxygen OS, booted and enabled USB debugging, etc..
Ubports recognizes the phone when plugged in and also through the whole tutorial the phone was always recognized. Also Fastboot or then in TWRP no problems. but it does not go on pushing files. It always comes up with the message connection lost.

I tested it with Ubports-installer 0.9.5 on Ubuntu, also with xubuntu. Then also with an older version 0.8.6.

I have really tried a lot with the Telegram group, but unfortunately it did not work so far.

I have already tried Repair System. Then formatted to EXT4.
Device is unlocked.
Can someone maybe give me a hint how it could work?

Thank you

Lakotaubp · 22 Apr 2022, 10:52

@wusa Have you read through all the thread above including about the not ticking wipe data and what to wipe in TWRP.

MrT10001 · 22 Apr 2022, 11:12

@wusa When you unlocked the device did you boot back into Android and set it up again?

wusa · 22 Apr 2022, 11:16

@lakotaubp said in Installing - connection to device lost:

@wusa Have you read through all the thread above including about the not ticking wipe data and what to wipe in TWRP.

If you mean the installer, yes i tried both versions.
First install and wipe data and
First install without wipe data.
Both runs into the same error.

@mrt10001 said in Installing - connection to device lost:

@wusa When you unlocked the device did you boot back into Android and set it up again?

No, first i installed OOS and set everything up.
Than i tried to flash UT. In Fastboot the message tells me the device is unlocked.
I unlocked the device years ago.

MrT10001 · 22 Apr 2022, 11:21

@wusa I found that devices would lose connection if I did not boot back into Android directly after unlocking and went straight into the UT install (trial and error).

I had an issue on a Oneplu3 where it would not load any ROM. I ended up re downloading the last ROM and installing it piece by piece in fastboot. This worked and then allowed UT to be installed.

wusa · 22 Apr 2022, 11:27

@mrt10001 said in Installing - connection to device lost:

@wusa I found that devices would lose connection if I did not boot back into Android directly after unlocking and went straight into the UT install (trial and error).

I had an issue on a Oneplu3 where it would not load any ROM. I ended up re downloading the last ROM and installing it piece by piece in fastboot. This worked and then allowed UT to be installed.

I dont know which ROM was my last ROM i tried so many different custom ROMs my whole time i used the phone.
But i also tried to install TWRP through fastboot and i installed OOS again through the console in ubuntu.
Then i did the developer settings and connected my device.
Than i tried the installer again. Everything failed.

I dont know how to proceed now.

Maybe someone can tell me an order how to proceed step by step again.
What I should delete, how and where I should delete, etc.

Lakotaubp · 22 Apr 2022, 12:04

@wusa Not just that. You might have to install TWRP and wipe and format cache, data and system to ext4.

wusa · 22 Apr 2022, 12:56

@lakotaubp said in Installing - connection to device lost:

@wusa Not just that. You might have to install TWRP and wipe and format cache, data and system to ext4.

Data and System are ext4.
Cache i have to check

pranishres · 17 Jun 2022, 11:29

Follow this video. I also had the same issue but this video saved me.
https://www.youtube.com/watch?v=b4WkjUkHUzw

ut · 23 Sept 2022, 09:04

@pranishres Great video. Successful install on OP3T A3003 (Europe model) with ubports-installer 0.9.7-beta. Had to switch Cellular Connectiontype to 2G/3G to receive calls. On T-Mobile in The Netherlands.