I installed UBPorts Ubuntu Touch on my mobile on 2021-06-11.
(love Ubuntu Touch in its own right - and have had a huge sense of relief ever since)

I installed and configured Dekko 2 for a my_email@gmail.com - the only reference in the mobile to my gmail account - and I have been receiving emails just fine and didn't receive any security notifications from Google (though I only connect to the Internet very seldomly).

Yesterday, I connected the smartphone to a Wi-Fi, Decko downloaded my new emails immediately and I received 2 security emails (in the same minute) from Google warning me that «someone had used my password to login into my account and Google blocked the login»
(^ translated from the language I received it in).

Why would Dekko have triggered such a block/warning from Google?

I usually severely distrust such security warnings from the likes of Microsoft email servers, since they appear to have a strong tendency to «judge» any non-Microsoft clients as untrustworthy and worthy of being «security» blocked (with "security" probably meaning the security of MS' revenue).

However, I have used the smartphone to access my emails some 10(?) times already, without ever triggering any such warnings. Further, the Dekko client did get to download the emails, including the security warning emails themselves.

I had a slight issue with the OnePlus 5, though - it didn't recognize the SIM card.

I rebooted <- nothing
Took the SIM card off, put it on again and rebooted <- nothing
| The mobile is Dual-SIM, so: |
Took the SIM card off from the outermost slot and changed it to the innermost slot <- recognized <- rebooted and now everything ok.

(the SIM card is Lycamobile Portugal and I'm currently residing in Finland, though I suspect that doesn't affect anything, but still FYI)

I tried again, with a new cable, without the "-f" option, and without checking the "Update Firmware" or "Wipe user data".

Everything ran perfectly smoothly this time and I now have Ubuntu Touch UBports-version running. Can't say for sure, but I suspect the cause of the issues was the checkboxes I was ticking before. This time I left them unticked, since Lakotaubp mentioned that's how s/he was doing it successfully. (looking back, don't know why I didn't try that before - a couple of good night's sleep are good advisors)

Alas I'm finally free from the unbelievable level of T&C abuse and Orwellian level of spying and am now free again to turn on mobile data, location, have maps, etc. Finally, ffs! Been waiting years since Canonical unfortunately (though understandably) dropped Ubuntu Phone.

What a marvelous feeling of renewed freedom.
Thank you for the help.

In the UBports menu I saw it mentions 2 log files:

So I downloaded them with the Fastboot command:
I cannot paste files into here, it tells me I'm not authorized...

It is still failing for me and I don't think it is the cable. This is a screengrab sequence of everything I did on my latest attempt:

There's a slight mistake with the instructions - to invoke the special boot menu it is holding Power + VolumeDown. The combo Power + VolumeUp does nothing on my OnePlus 5:

Then finally in Fastboot mode:

Started ub-ports as root + sspecifying the OnePlus5 config file, Justin Case,

# ubports-installer -f /home/paulo/Desktop/cheeseburger.yml

Installer automatically detects the mobile, I check all checkboxes:

Installer asks me to continue (and gives me the wrong? instruction to Power+VolumeUp):

After reboot the mobile just hangs:

I notice that the mobile is still responsive and is in "fastboot" (whatever that means), so I make is boot up the latest TWRP:

root@paulo-B450-AORUS-ELITE:~/.cache/ubports# fastboot devices
957ec7db	fastboot
root@paulo-B450-AORUS-ELITE:~/.cache/ubports# fastboot flash recovery /home/paulo/Desktop/twrp-3.4.0-1-cheeseburger.img
target reported max download size of 536870912 bytes
sending 'recovery' (33412 KB)...
OKAY [  0.792s]
writing 'recovery'...
OKAY [  0.314s]
finished. total time: 1.106s
root@paulo-B450-AORUS-ELITE:~/.cache/ubports# fastboot boot /home/paulo/Desktop/twrp-3.4.0-1-cheeseburger.img
downloading 'boot.img'...
OKAY [  0.797s]
booting...
OKAY [ 10.094s]
finished. total time: 10.891s

Once TWRP boots up, the installer recognizes it and reacts:

Following the instructions:

Instead of following directly the instructions, I pressed back, back, then Reboot, then Bootloader:

Installer recognizes the mobile in the Boot menu and issues a reboot:

However, once again the mobile doesn't progress from the Bootup image:

Once again I detect that the mobile is recognized by Fastboot, so I reboot it to boot loader then start in Recovery Mode:

root@paulo-B450-AORUS-ELITE:~/.cache/ubports# fastboot devices
957ec7db	fastboot
root@paulo-B450-AORUS-ELITE:~/.cache/ubports# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [  0.000s]
finished. total time: 0.050s
root@paulo-B450-AORUS-ELITE:~/.cache/ubports#

Installer recognizes the mobile after restarting in Recovery Mode:

However now it always fails with something which I'm suspecting is not the cable (and UBports is now loaded):

When the installer was waiting for the mobile to reboot but is actually frozen, I tried:

• Forcefully stop the mobile;
• Restarted it into the «regular» Android/Oxygen;
• Restarted to bootloader;
• Used fastboot to inject twrp-3.4.0-1-cheeseburger.img
• The issued a fastboot boot twrp-3.4.0-1-cheeseburger.img

It then fired up TWRP and the ubports-installer then reacted, it recognized it - that must be what the installer was waiting on.
Once it recognized the mobile / that the mobile was in the desired state, it started trying to upload something,
However, it is now failing to upload. When I retry the upload progress goes close to the beginning (though not entirely) and then fails again at about 3/4 of the progress, always:

@pauloaugusto said in Booting twrp freezes:

@pauloaugusto Try looking here https://forums.ubports.com/topic/6227/installer-configs-beta-test if you have not already.

Nope, mostly the same. The only thing different in those instructions was to specify the config file with the "-f" flag. I tried it anyway, just in case, even though I suspected the installer was already using that same config file.

There was 1 thing different this time, though - ubports-installer downloaded some files. I haven't yet quite figured out when the installer downloads files and when it doesn't... Finding it a bit strange.

The start screen after detecting the OnePlus 5 mobile:

The "More..." links don't link nor open anything. Are they missing?

@lakotaubp said in Booting twrp freezes:

Not sure from your post if you are just trying the installer (0.8.8), which I don't think is ready yet.

Indeed I am using "ubports-installer_0.8.8-beta_linux_amd64.deb", which is the version I downloaded this morning from UBports - it is the latest, I think?

@lakotaubp said in Booting twrp freezes:

@pauloaugusto Try looking here https://forums.ubports.com/topic/6227/installer-configs-beta-test if you have not already.

(thanks for the quick reply and mega kudos for UBports overall)

I hope someone can help me - I bought 1 of the original Ubuntu Phones, Aquaris 4.5, and I loved it.

I eventually bought a new phone 3~4 years later but there were no longer any Ubuntu phones on sale, so I thought I was doomed and relegated myself to a OnePlus 5.

One of my long time regrets was not having purchased a better model which came out some time later (Meizu?). I miss my trusted Ubuntu Touch so much...

I have been accompanying the UBports project and Librem phone for a long time and now finally decided to try out something. I considered trying to buy a mobile coming pre-instaled with Ubuntu Touch but there aren't many options (.. any options at all except Volla, whose website-checkout is entirely in German o_O?), so I thought of repurposing my old but still just-fine OnePlus 5 riddled with malware...

From other sources online, I downloaded the img twrp-3.4.0-1-cheeseburger.img and used fastboot to flash that img into the phone:

• fastboot flash recovery twrp-3.4.0-1-cheeseburger.img
• Boot into recovery mode,
• TWRP opens then I followed manually the instructions that ubports-installer was telling me:
• I navigated to "Advanced", "ADB Sideload", checked "Wipe Dalvik Cache" and checked "Wipe Cache" and then "Swipe to Start Sideload".

Once that was completed, I went to check the partitions and /data and /system were already ext4 (even though /system is almost full <- is this a problem?).

So, I tried to manually do the TWRP actions that I am assuming would be done as part of the ubports-installer installation.
However, upon re-attempting installation with ubports-installer still tries to boot up TWRP and freezes in the same place.

Is there a way for me to complete the installation manually instead of relying on ubports-installer, which is apparently attempting to boot up TWRP and freezing the mobile?

I tried to install Ubuntu Touch from UBports with the ubports-installer tool,
However it freezes when it tries to boot up twrp.

I started by preparing everything (there's actually a lot of stuff which I had to figure out outside of UBports...):

• I am using Ubuntu 20.04.2 LTS,
• I am attempting to install into OnePlus 5,
• I've enabled developer mode on the mobile,
• Enabled the unlock bootloader config on the mobile,
• Enabled the USB debugging config on the mobile,
• Rebooted to bootloader and, with the command-line command "fastboot" I unlocked the bootloader,

Now finally ready to start trying to use UBports' ubports-installer tool,
I used ubports-installer and followed these steps:

• When ubports-installer starts, it recognizes the mobile,
• Then tells me: "you will have to install TWRP and format to ext4 /data and /system before... ",
• When I click to advance, ubports-installer manages to issue a reboot into the mobile which starts to boot,
• And ubports-installer now tells me to operate the upcoming TWRP to "Wipe Dalvik Cache", "Wipe Cache" and ""Start Sideload",
• However, the mobile enters the boot-screen with white letters "1+ something" and never progresses.

Is there any way to work around this?