@snail_phablet ... Before lunch you need to sync Device trees, kernel and vendor from GitHub.com/ubports-oneplus6. Example of path: device/oneplus/fajita

Ubuntu Touch hasn't USB Tethering. Yes, there is RNDIS option in UT Tweak Tool but it used for USB debugging when ADB was unavailable.

It is poor adb drivers in Windows 11. My main Windows 11 setup, works fine, but my other always puts an exclamation mark over the device in device manager and tells me the drivers aren't installed. My usual resolution to this is to update or install Android studio, but this hasn't resolved it recently. This is really irritating as I need to test USB 2.0 to unlock an Xiaomi phone to discount USB 3 as an issue (my main Win 11 setup is all USB 3.0) and this setup won't see the device correctly - you need windows tu unlock the bootloader on an Xiaomi device.

I know this thread is old by now but I really need to ask :

How is it possible that his provider refuses to support the more expensive and advanced OnePlus 7 Pro and instead only supports the cheaper OnePlus 7T and also the older 6T model ?!

That makes no sense when we talk refusing/cutting 3G phones from their network : The can all use 4G/4G+ and with Android installed probably VoLTE too ?! 😳

@rocket2nfinity said in Oneplus 6T hard bricked to g.co/abh:

MSMdownloadtool uses EDL mode to overwrite the partitions on the drive directly. It doesn't need TWRP.

If this phone still supports EDL Mode then maybe he should try to get into EDL Mode via the cable trick or by holding down the power button for a very long time ??

My ZUK Z2 Pro works like that but has a much older SoC : SD820 instead of the SD821/835 or something like that in the OnePlus 6T I think ?!

...the downloaded rollback file has to be renamed...you need to delete the ".jar" then update local.

screenshot20220107_165450751.png

@carrabelloy Then you'd rather use the UBports installer to install Ubuntu Touch on your device.

@antidroid said in Halium 9 / CI + OTA build:

@rogier-oudshoorn

So the XDA page for the official LOS 16 Oneplus 6T build release points to the files on the Official Lineage OS sites download page for the Fajita which only has Lineage 17.1 builds.

On their FAQ it says this

We don’t keep building, or keep builds around for any version older than 2 Android versions (e.g. when 18.1 builds started, 16.0 builds stopped and the builds were slowly removed,

So we need an OS that you can no longer get unless you build it yourself or trust some shady download portal someone has uploaded the files to before they were scrubbed from the official server. Just to flash it before flashing a test build of UT.

I feel your pain and it's indeed VERY ANNOYING when you are messing around with ROM's that need the LineageOS 16.x version as base! 😞

I had to wait weeks before someone uploaded LineageOS 16.x for the Xiaomi 9T (Davinci) for example...

I may try flashing it over Oxygen just to see and if it fails I will run Postmarket until there is a proper install-able version of UT.

Often the latest Android 9 Stock ROM of the same phone works too, but with some glitches/bugs so that's a good idea! 🙂

Anyways...

Could you please tell me more about your PostmarketOS experience on the OnePlus 6T ?
That sounds VERY interesting! 😃

@reynald
here you go (its from OP6 running 2021-W45):

screenshot20211210_002856026.png

Thank you all, I went through the source code and the installer log.
All it does is flash boot.img and vbmeta.img to the current slot and does not touch the other. the recovery image does not work so I fastboot boot a working recovery and continue from adb shell.
Then it downloads the xz.tar files with their keys and push them to the device /cache/recovery once it's in recovery mode, then it adds recovery.fstab to /etc/

The downloaded files come with ubuntu_command file that is executed in recovery using system-image-upgrader script.
the script formats system_b partition and load keyrings then extracts the xz.tar files in cache, and strangely tries to move cache/data/* to /data when the first one doesn't exist, because the extraction results in system folder not data. (I guess I will change the path)
Anyway now that I'm sure the main slotA does not get touched I will keep testing until I come up with something that works. (I already got it to the boot splash but it keep loading and does not go past it)

@reynald
Try using ubports-installer 0.8.9_beta1
It worked for me with OP6 and OP6T.
Newer versions 0.9.0_beta1 and 0.9.1_beta1 doesn't work either.

@gortbrown - phones running UT will NOT work with CDMA carriers like Verizon or Sprint - you need GSM. T-mobile is your best bet, works great on my 6t

@jpb

Check this out:
https://github.com/ubports-oneplus6/documentation/issues/14
to get Android 9,

then you can use the ubports installer.

Also check this thread

@applee said in Disable Bluetooth from autostart:

But that's good to know it IS device related (or maybe Halium related )

That's the intend of my post.

@reynald Had the same issue with my Xiaomi Mi A2 yesterday on dev channel. Switching to stable did the trick...for now...

@magdesign The fix will be in the next RC update which IIRC is Wednesday. Other than that yes Dev is the answer.

I don't know if it matters, but the McLaren edition differs slightly from the OnePlus 6T. I never understood why I bricked the McLaren one (following these steps: https://github.com/Intrinsically-Sublime/fajita-factory-flash-bash-scripts ).