@MrT10001 thank u sooo much

I've been using UT 20.04 on my OnePlus 6 without issues, including Waydroid with MicroG. However, today I noticed there's no audio from the headphone jack to my stereo system. Bluetooth audio works fine with a Bluetooth speaker.

Hi @wurmphlegm Have you tried to force the fastboot mode? I remember having to do it manually as the installer wasn't able to make my device comply. So I used the volume buttons and power button to make it happen.

@ginggs You cannot flash that through fastboot like that. With a .bat file it has to be Windows and run through the Windows terminal. Linux would use the .sh and run through a CLI. To manually flash you need to extract the images.zip file and then flash manually in this order: fastboot flash aop_a aop.img fastboot flash aop_b aop.img fastboot flash bluetooth_a bluetooth.img fastboot flash bluetooth_b bluetooth.img fastboot flash boot_a boot.img fastboot flash boot_b boot.img fastboot flash dsp_a dsp.img fastboot flash dsp_b dsp.img fastboot flash dtbo_a dtbo.img fastboot flash dtbo_b dtbo.img fastboot flash fw_4j1ed_a fw_4j1ed.img fastboot flash fw_4j1ed_b fw_4j1ed.img fastboot flash fw_4u1ea_a fw_4u1ea.img fastboot flash fw_4u1ea_b fw_4u1ea.img fastboot flash modem_a modem.img fastboot flash modem_b modem.img fastboot flash oem_stanvbk oem_stanvbk.img fastboot flash qupfw_a qupfw.img fastboot flash qupfw_b qupfw.img fastboot flash storsec_a storsec.img fastboot flash storsec_b storsec.img fastboot flash system_a system.img fastboot flash system_b system.img fastboot flash vbmeta_a vbmeta.img fastboot flash vbmeta_b vbmeta.img fastboot flash vendor_a vendor.img fastboot flash vendor_b vendor.img fastboot flash LOGO_a LOGO.img fastboot flash LOGO_b LOGO.img Thanks to the XDA-developers forum @mauronofrio here.

@MrT10001 thanks guys I knew something was not normal here. I hope someone figures this out as I think ubuntu touch on this device is amazing.

@ezst036 Wow, I found the OP6T one of the easiest phones to install! I'll put the next bit in bold to help others: If the device is at the bootloader (fastboot mode) and connected and you start the installer, the installer will pick it up as example "sdm845". If you know which device you have manually select it from the drop down list in the installer and follow the on screen instructions. The bootloader must be unlocked to install Ubuntu Touch and if the instructions indicate a specific version of Android must installed before, install that version, boot into it and set it up, enable developer mode and ADB/USB debugging before starting the installer. The reasons for the specific version of Android has to be installed is for things like Vendor BLOBS, specific bootloader, specific kernel. To install UT on the OP6T I have always had to downgrade the Android version to Android 9 using this file Fulldowngrade_wipe_18801_181024_2027_user_MP2_release.zip This can be obtained from here. The link is still active at this date (11th February 2024). Download it to the root of the device i.e. connect the device to the PC and set the USB connection to file transfer and copy the zip (STILL zipped) file to the device - NOT in a folder (i.e. the root of the device). Once done then go to Settings, System, System updates and with the cog symbol on the top right, choose Local Install and let it do it's thing. It will take about 15 minutes, reboot and leave you at the Android set up screen. Set up Android again, and enable Developer options and ADB?USB debugging. Reboot to the bootloader. Unlock the bootloader using fastboot oem unlock. Reboot the device and set Android up again, enabling ADB/USB debugging. Connect it to the PC and run the Installer. The installer will then reboot the device and do most of the work for you. You will at one stage have to boot into recovery, the installer will do the rest. @ezst036 You may have had issues due to the device being T-Mobile, but I have had many locked devices that I have installed UT to and it was only SIM locked, the UT install always went through. If the device reboots and you get a message saying "Qualcomm Crash Dump", power off the device, charge the battery for a bit and boot it up again. The stability of the device is not quite there yet, mainly due to the issue across devices with UT draining the battery. There is an app called BatterySaver for 20.04 by Lionel Duboeuf that will help. I have no bricked devices due to installing UT (yet)!

@tomsome Yes, the developer mode think is for Android users. If you already have Ubuntu Touch, then this is already done as well as unlocking the bootloader (expect if you locked it back despite it being deprecated).

@ijiki30 Use this build to roll back: OnePlus6Oxygen_22_OTA_054_all_1908302047_fulldowngrade_f019784c78234a67.zip Download it from here. There is a reason why Android 9 is used, something to do with Vendor BLOBs I believe (but don't quote me on that).

@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: )