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.

@User100 Hey I realize this is old, but if you have not gotten it out of Qaulcomm Crash Dump mode yet the way to do it is getting the MSM tool. You can get the tool with Android 9.0 so that you can boot right into it. Here is the link to the MSM tool. Follow the guide you will find in there it works like a charm. I got the crash dump error twice trying to get it to 9.0. If your phone is as finicky as mine when you start the process it will give you the sahara error... This is where you have to not listen to the instructions. Keep the phone plugged in and reboot with power + volume up, Then restart the phone with power volume up and you will see that the MSM tool will start the download again once it boots. You can let got of the buttons then and let it do its thing. If you have any questions feel free to reach out and I'll do what I can to help. Side note.... Rollback option does not work with T-Mobile OnePlus phones.

@spaceman_spiff Not my fix, read about it on the forum or TELEports, but if it works, good. It is one of the tricks to remember for any sort of connectivity issue on UT, try switching airplane mode on and off first

@randomuser Sometimes it is what it is and works and your never sure exactly why, main thing is your up and running.

@kodybear18 when you install UT to the device it gives you the option in a drop down box. If you have installed UT to the device you can switch channel in the system updates, cog on top right of the screen.

@joel_1 This is a common problem we usually handle in the (North American Issues) Ubuntu Touch Telegram group as it is easier to solve with live support. Please join the UT welcome group and ask for the North American Issues group

@mw4jet Thanks I'll try it

@xga3xga3 Hi, can you be a bit more specific. If the device is not responding, and you are at the Ubuntu Touch home screen, do a hard power off, i.e. press the power button till it switches off. If the device is not responsive at all and wont power on or show it is charging, leave the device plugged in to a charger or PC and leave it for a couple of hours. It should power on after that.

I had the same thing on OP6T, rocket2infinity answered in Telegram, Welcome and Install page on Sep 13th, but here it is in a nutshell : "No need to install it. Just boot into TWRP after unlocking bootloader and setting USB permissions under developer settings in Android. Then wipe cache and data. Reboot to fastboot, then run installer without rebooting back to Android" It worked for me.

@rocket2nfinity US Mobile is a good deal. Really customizable for a strict budget situation, plus 2G service. Just want to let everybody know...

@mrt10001 When the device is unplugged, after holding volume- and power for long enough, it eventually boots into Ubuntu. Sometimes it takes 20 seconds sometimes it takes 60. It never loads the bootloader any more. EDIT: ok I got it to show up with bootloader for about a second by holding power for 10 seconds as if I was turning it on as usual, then releasing when it vibrates, then volume down and repressing for another 10 seconds. Going to experiment some more. EDIT 2: for anyone else who ends up with their device in the same state as mine: the trick was to continue holding down both buttons and click on the touch screen while still holding them down, and then I was able to release once it started the bootloader. Thanks very much for the help! Hopefully I'll be good from here.

Don't want to do the Android test yet. Living with the weird power on issues. I always hold vol up and power, takes 5-7 seconds it vibrates, I let go and it boots. Shutdown is normal, hold power button and the 4 choices show up. I have found it won't boot if the usb is connected, like charging. Got phone and text working with cell data. The only thing I don't have working is pictures in text messages in or out. I expect other things will surface when I begin to carry it, but we'll see.

@rocket2nfinity said in OP6T failed ubports installer: @mw4jet MSMdownloadTool if wiping data and cache in the installer or with TWRP did not work This is definitely the fix. Boot into TWRP without installing, UBPorts installer works well then.

@shadowcastiel I do not think you hard bricked your phone. I saw the dame behavior with an almost empty battery. The screen was shortly blue (light blue) and than it gone dark. You just need to charge your battery a bit more before trying again. In my case it first showed a "battery is too low" screen. Then I charged a bit and it then showed the behavior you described. (with shortly light blue screen) . Then after charging even more it could successfully boot again. In my case all these problems are related to a strange behavior when powering off the phone. Take look here . Unfortunately the software issue still doesn't seem to be fixed.