@yuu-ä3 System settings offered the upgrade and unwisely I applied it only to find the phone more-or-less bricked. After a few false starts (see my posts) I was able to restore 20.04.

My advice:
DON'T TOUCH 24.04 on OP6 or 6T until there is an announcement about the port (Unless you are able to contribute to the porting work)

Managed to do it -- there's an option below "Erase user data", to enable/disable flashing the system (sorry, I wasn't careful enough to note exactly what it said) disabling that allowed the install to proceed and the system to reboot. It all looks the same as it was before the ill-advised foray int0 24.0.1.

@MrT10001 Thanks for that reminder I have had issues with Ubports install from certain ports in the past, I'll try a different one.

Just hope that charging works without a working OS since it's now saying the battery is too low

On attempting to downgrade (installer V0.11.2, binary install from AUR) , booted to fastboot mode then:

info: Welcome to the UBports Installer version 0.11.2!
info: device detected: sdm845
warn: The device sdm845 is not supported!
info: device selected: enchilada
info: Installing Ubuntu Touch on your OnePlus 6/6T (enchilada)
info: configuring...
info: settings: {"bootstrap":true,"channel":"20.04/arm64/android9plus/stable"}
error: Error: fastboot:flash: Error: Flashing failed: {"error":{"code":1},"stderr":"fastboot: error: Failed to find AVB_MAGIC at offset: 0"}
stack trace: Error: Flashing failed: {"error":{"code":1},"stderr":"fastboot: error: Failed to find AVB_MAGIC at offset: 0"}
    at /usr/lib/ubports-installer/app.asar.unpacked/node_modules/promise-android-tools/lib/module.cjs:1121:15
    at /usr/lib/ubports-installer/app.asar.unpacked/node_modules/promise-android-tools/node_modules/cancelable-promise/dist/CancelablePromise.js:27:18
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Any pointers please.

@Vlad-Nirky I don't think so.
I have WiFi enabled/connected and Bluetooth off whenever I'm at home.
There's not normally any apps running (at least not visible ones).
I've not installed waydroid on this phone (I know it can get into odd states where the waydroid window isn't visible but it's not in the start menu either).

When I plug my 6T into charge from a low state (same USB-A port on the computer, same cable each time), there seem to be two different rates of charging:

• Sometimes the indication is that it will take about 1.5 - 2 hours.
• Other times about 4-5 hours.

I've not been able to spot any obvious factor controlling this.
While it's not a problem, I'm just curious whether anyone has any idea what drives this. (Or indeed whether anyone else has seen it).

@vince.vs Definitely working again now.

I've been setting up a 1+ 6T to replace my 5T which has a cracked screen.

After installing and setting everything up, I shut down the 6T and the 5T and moved the SIM card to the 6T. But when I tried to power up the 6T nothing happened (even holding the power button for well over 15s).
Remove SIM, boots OK, replace it no boot.

Then I powered down and left it for a few hours. then put the SIM in and it booted no problem.

Since it seems to be behaving OK now, I don't think there is anything wrong with the system. The only thing I can think is that the actual shutdown takes longer than it appears so effectively I was installing a SIM in a running system.

Just thought I'd bring it up in case anyone else encounters a similar issue.

I am seeing somewhat the same issue on Manjaro.

When I plug the phone in is starts charging (in the appropriate mode according to its on/off state at the time).
But if plugged in while the device is on, it does not appear in the USB devices menu in the KDE toolbar.

It does however appear to be recognized by the OS as the dmesg output is sensible:

[489387.766340] usb 2-1.3: new high-speed USB device number 10 using ehci-pci
[489387.865961] usb 2-1.3: New USB device found, idVendor=1209, idProduct=0002, bcdDevice= 4.04
[489387.865971] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[489387.865974] usb 2-1.3: Product: 5T
[489387.865976] usb 2-1.3: Manufacturer: OnePlus
[489387.865978] usb 2-1.3: SerialNumber: d7dfe97c

and it shows up in the list of USB devices in the system info tool. It also appears in the dolphin "Places" sidebar, but when I try to access it via that, I get an error:

Could not access device. Make sure it is unlocked, and tap "Allow" on the popup on its screen. If that does not work, make sure MTP is enabled in its USB connection settings.

I do not see (and never have seen) an allow popup on the screen, but according to the UT tweaks tool MTP is enabled (and it does not allow me to disable it).

FWIW, on the PC:

$ pacman -Qs android
local/android-tools 35.0.2-7
    Android platform tools
local/android-udev 20241109-1
    Udev rules to connect Android devices to your linux box
local/gvfs-mtp 1.56.1-1 (gnome)
    Virtual filesystem implementation for GIO - MTP backend (Android, media
    player)

(Omitting a few libcamera related matches)

@arubislander Reinstalled Waydroid + Fortitoken, and got new key from our IT folks and now it connects again.

Not clear though whether a glitch with the server (resulting in an unacceptable level of failed logins) or an OTA-5/Waydroid problem was the root cause.

Is it possible to revert a stable-branch phone from OTA-5 to OTA-4? And if so how?

Why? See this post, so I would like to be able to test if it is an issue between Waydroid & OTA-5, or a problem at the server end.

To connect to my work VPN, I use the FortiToken Client (from Playstore) running in Waydroid to authorize connections. However since the OTA-5 update, I've not been able to get an authorization prompt, not sure if it's a problem with OTA-5/Waydroid or at the lab.
Any ideas for how to test?

@MrT10001 Thanks,
I've been using the OnePlus 5T, only issue is that the USB socket has had to be replaced, so it seemed sensible to have a backup in case of hardware problems (I'm not young). I have ordered a 6T and returned the Xiaomi; even with secondhand things I don't like supporting systems that make you jump through hoops to do what you need.

To be absolutely honest, if it was supported on the current version, I'd be quite happy with the Nexus 5 (or even 4).

I was able to get the USB-C socket replaced and it works again.

@Eric-H
I'm not exactly a heavy or sophisticated phone user, so I don't need many of those features, just something that can call, text and play music and NOT deliver an endless stream of ads.

@MrT10001 Thanks, but I think it's time to return it and try a oneplus 6t instead.

I've been trying to unlock the bootloader on this phone in order to install UBPORTS.

The only unlocker that the installer offers to download is for Windows. And while I can run the miflash-unlock.exe file using wine with the phone booted in fastboot mode and connected to a USB port, the program complains that the phone is not connected.

I have tried the suggestion on Winehq of adding the line:

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", MODE="0666"

to a high-numbered file in /etc/udev/rules, and restarting udev using

sudo udevadm control --reload-rules
sudo udevadm trigger

but to no avail.

Does anybody have any workarounds/solutions? I do NOT have a Windows machine available.
I am running Manjaro on the PC.

@MrT10001 said in Hardware dying? Or software issue?:

usually usb c port on its way out.

@wally said in Hardware dieing? Or software issue?:

Sounds like hardware, in my inexpert opinion.

Thanks both, that's rather what I thought. Taking a look at the internet I suspect that trying to replace it myself is probably asking for trouble. There is a mobile phone repair shop in town so I think I'll see what they might be able to do.

I've a feeling that the USB-C port on my oneplus 5T may be wearing out,

Symptoms:

• If I plug it into my charging brick (when turned off) it boots up and the battery level appears, flashes a couple of times but then the phone appears to shut down.
• Similarly when plugged into a USB port on my PC. N.B. I've been using different USB-C cables in the two cases.
• When booted up, it (usually) fails to charge from the brick. It does charge sometimes (but not always) from the USB ports on the PC [I've not done a detailed enough investigation to be sure whether it's really sometimes or some ports, though I suspect the latter].
• There is never a message in dmesg on the PC (Manjaro / KDE) and nothing appears in the USB devices list.

Since my old Nexus 5 was still lying around I was able to verify that that is detected as expected (though as was always the case accessing it from the PC is tricky).

It seems unlikely that there is a software issue that could cause this, but has anyone seen anything similar?

Also I've forgotten which protocol is used by the 5T when accessing on a Linux box, can someone remind me please, so that I can go onto the Manjaro forums to see if there are any issues with that protocol and Plasma 6?

I'm not sure if this is the best place to raise this, but there's no obvious place for discussing the main web page.

It seems a good idea to remove devices not supported under 20.04 from the "promoted devices" page. It doesn't look so good when you click on the Nexus 5 only to get a page that says it's not supported by the current versions.