@christianBorg the 6t rebooting is a win, i think devs should replicate the process for rebooting mechanism, i use that to reboot tbh

@anon Sometimes leaving it for a few minutes resolves it. Glad it is resolved.

@danfro Hello, If the led notification discussion on OPT5 still interests you, would you like to find the continuation in https://forums.ubports.com/topic/9592/notification-lights-not-working-topic-8775/4 Best regards

Is USB HDMI working?

@bable3 if you do a hard reset (power off) it should go past the crash dump on starting it up again. Possible sign of a weak battery.

@arubislander Thank you. I was trying that several times, and getting rather anxious about it not rebooting, but then finally it did reboot and all is now well again. But I shan't be trying to use the Wireless Display again very soon ...

@kugiigi YES! That fixes it. Very many thanks! Now I will disturb those around me less, and save battery

@hunter616 For both Focal (Pixel 3a XL) and Xenial (BQ E4.5) it recognizes the pendrives. Recognizing meens the envelope on the topbar lights up green, and I hear a sound. In Focal I can not eject the drives, so when I remove it from the phone and put another pendrive in, it does not react to the new drive anymore. In Xenial I don't see this behavior. After a reboot it works again. Ejecting in Focal does work in the Terminal app ($ umount /media/phablet/name-off-pendrive) Can you try after a reboot? So you do not get the message the drive was attached. But have you also checked the filebrowser app if it shows up there? In the filebrowser you should tab on the hamburger menu. Can you try the filebrowser app? The drives are formated as isofs (Ubuntu install drive), msdos (Windows install drive :astonished_face: )

The device needs the stock version of Android for UT to install and it has to be the version stated in the installer page which is the last version of OxygenOS 9. Here is the useful resource page.

@FK_nero You need this ROM: Fulldowngrade_wipe_18801_181024_2027_user_MP2_release.zip Download from here. Information here.

Hi @Hugehead , See: https://gitlab.com/ubports/porting/community-ports/android9/oneplus-6/oneplus-enchilada-fajita/-/issues/12 Thank you!

@MrT10001 ahh that would make sense. For now I can do that.

@Pingu https://forum.xda-developers.com/t/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.3792244/ I just download a version for here and flashed it with TWRP adb sideload also change your slot

@MrT10001 Thanks for the instructions! I was afraid I needed to mess with Msm from Windows or something but I wasn't aware of the flashable zips in that thread. I was running LineageOS 20 with F2FS unencrypted data and needed something to really work to revert all that fun to stock I rebooted to bootloader, fastboot booted TWRP, formatted data and everything except vendor partition, rebooted back to bootloader and fastbooted TWRP again, adb pushed OnePlus6Oxygen_22_OTA_054_all_1908302047_fulldowngrade_f019784c78234a67.zip to /sdcard, flashed it from TWRP, rebooted to System, and was greeted with the stock boot animation and OxygenOS 9. My host OS is Ubuntu 23.04 so I got the UBports .deb and installed it with apt, opened it up from the launcher, and chose 20.04/devel. Some stuff downloaded, I followed the UBports prompt to go to Recovery, and eventually Ubuntu Touch booted up!

@MrT10001 Thanks

Sorry have been away for a couple of months and only now finally got back to my OP6. Using the UB touch installer, I got Focul up and running. A couple of minor issues, the date and time (despite been set as automatic) seems to revert to manual on reboot. I get the Qualcom Crash Dump screen whenever I leave it charging....and on reboot get the Boot Loader is unlocked screen. I have not had time to explore much more than this at the moment.

@Lepotototor Ok start from step one: boot into android. enable developer mode system>settings>about phone. Hit Build number a few times to enable developer mode. Enter developer mode, enable USB/ADB debugging and OEM unlock 4)boot to the bootloader and in fastboot unlock the bootloader 5)boot back into Android and set it up again 6)enable developer options and USB debugging again copy the downgrade ROM to the root of the device, ie, NOT in a folder go to system updates and do a local update. It will reboot and you will be on Android 9.04. enable developer options and USB/ADB debugging again Unplug and plug the device back in again Reboot to the bootloader and run TWRP recovery. In Wipe and advanced wipe, ensure the DATA partition is EXT4 reboot to Android 14)USB/ADB debugging should be enabled Start the UT installer and follow the instructions. You have to install Android 9 IF you have installed LineageOS or any other version of Android it will fail to install, it has to be on Android 9 USE the Installer, the fastboot commands are only required to get the device ready for installing UT. If the device boot loops, usually it is because your DATA partition is not EXT4 or your bootloader is the wrong version (one of the many reasons why you use Android 9). So you need to get back to Android stock ROM and make sure it is Android 9. I lack a lot of the understanding of whys and wherefores with the need to set it up in a certain way before installing UT as I am not a software engineer/coder or genius, but if you follow the instructions it should and usually works. One rule for all of this is keep it simple (KIS), don't complicate things by overusing the command line.

Try the latest hotfix for OTA-25.