@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.

It could have gone into EDL mode. Hold power + vol up for ten second then release. Then press just power again. Hopefully it reboots. If not use MSMdownloadtool as described in the post several above this one.

@totalrando Bootloader can be unlocked using MSMDownloadTool at XDA-Developers. You appear to have a T-mobile model. It has two functioning sim slots, just buy a dual sim tray. Don't know why T-mobile used a single sim tray.

The OP6T image works for all OP6T models

It has been fixed by: https://gitlab.com/ubports/porting/community-ports/android9/oneplus-6/oneplus-enchilada-fajita/-/commit/0dd442c516facd70c25dd2c2e8cebce2c3106aac

@shadowcastiel Good to know. Could you please mark as solved https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved Thanks

@stanwood

Thanks for your info!

This helps me a lot, I will completely erase my phone and try again for roaming,
and hopefully mark this issue as solved..... if its not an OP6 issue...

@toughcaddy No matter how unhappy I am with possible problems in the current release candidate, I am planning on forgoing all updates for at least 1 year.

@manesec
Sorry, I never used Libertine, only once to test it out with my BQ M10 while Canonical was still in charge.
🤷♂ I have no clue if it will work.

Best of luck and hopefully someone with more knowledge will help you out.

@bielsnohr

Just checked on my OP6 with OTA-22:
I am able to connect to Bluetooth headphones (MusicMan BT-X42) and listen to music.
Make sure that in

/etc/bluetooth/main.conf

the last line says:

AutoEnable=true

About bluetoothctl, its sometimes a bitch, but you can try:

sudo bluetoothctl

then you get a inside the terminal something like:

[bluetooth]#

there you enter, always followed by an 'enter':

power on agent on default-agent scan on

wait a moment... until you see $yourheadphones device.
You first need to trust your headphones:

trust $yourheadphones

then when its trusted, you should be able to pair:

pair $yourheadphones

and finally connect:

connect $yourheadphones

Not sure if you have to turn scan off or not:

scan off

Hope that helped... I did not test this procedure on my phone, but on a rpi 😉

@mardy
Just tried again after updating to OTA-22.

Everything works, I do have running GPS !!!
Thank you very much for updating, this is a great help for me to not get lost in the woods 😉