Halium 9 / CI + OTA build

AntiDroid

@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 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. The current GSI is completely useless for me. I get a couple of seconds of screen time before it shuts off the screen. I can reboot UT as many times as I want and the results are the same. The only way I have ever been able to get it back is to reflash Oxygen then UT and a few times I had to repeat that. Once back it last for a couple of reboots maybe and comes back. Reflashing Oxygen obviously ruins my Postmarket build so I just don not use UT on it currently.

TotalRando

@rogier-oudshoorn ```
fastboot flash boot system.img
target reported max download size of 805306368 bytes
sending sparse 'boot_a' 1/4 (785285 KB)...
OKAY [ 26.708s]
writing 'boot_a' 1/4...
FAILED (remote: Error flashing partition : Volume Full)
finished. total time: 26.709s
root@mx:/home/computer/Downloads# fastboot getvar current-slot
current-slot: a
finished. total time: 0.002s

TotalRando

I sense this won't work as I don't have the LOS 16 build....

Hmm new feature. I've entered "Crashdump Mode". This gives me the impression I have done something wrong.

TotalRando

@totalrando Well, it's been fun. After a nightmare bootloop, I decided to start the process over. I downloaded OOS9 and am keeping it there... for now (apparently there's no download space on a 128 GB phone). If I do go back it will be to the GSI build or anything later. Still have UT on my Nexus 4, but I've had enough pain with this phone for now. Maybe I should have just left it as is. Maybe I'll go back to the GSI build if only to get my drive space back. I genuinely miss it. But for now, I'm just happy the thing places and receives calls.

rogier.oudshoorn

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

@rogier-oudshoorn
fastboot flash boot system.img

Yeah, you should flash system.img to system, boot.img goes to boot ...

AntiDroid

@rogier-oudshoorn So I decided to reflash my phone with Oxygen 9 to see if your CI build would work. It did not, it would just boot to the bootloader. But as you said it needs to be LOS 16 and as I said it is no longer available. So will you be providing a copy of LOS 16 for both the 6 and the 6T or will the installer provide everything needed to install regardless of the current OS?

sven

BTW: The same version problem of LineageOS 16 exists for the Xiaomi Pocophone. Any long term archives of LOS?

rogier.oudshoorn

@antidroid I found my copy of LOS 16 (for OP6) linked on XDA somewhere; i guess when we'll get to the installer stage i'll likely have fashboot or twrp flashable images for the installer to work with.

rogier.oudshoorn

@sven This at least claims it does: https://archive.org/details/lineage-16.0-20200325-nightly-beryllium-signed

When you do, please check https://wiki.lineageos.org/verifying-builds.html to see if they are in fact officially signed.

TotalRando

@rogier-oudshoorn Thanks for this. As my OOS9 build is virtually inoperable, I've moved my SIM back to my Nexus 4 but now I can start working on this wonderful phone again. Downloading LOS16 now.

AntiDroid

@totalrando Rogers link was to a LOS16 for pocophone not oneplus 6/6T

TotalRando

@antidroid If you click the zip files on the right (147) it lists all the builds. Enchilada and Fajita are somewhere in the middle. Installed with TWRP and I know I have to get to the next step to install UT but I am really liking this de-googled beast right now

EDIT: Maybe I can figure out how to do the dual boot thing

AntiDroid

@totalrando There is an app in the app store for dual boot and one for android as well. It sets the active slot for the next reboot.

Thanks for the tip to find the build.

TotalRando

@antidroid Oh, when I say de-Googled I mean I don't run Gapps either. If I combine the original instructions for the mixed build I can switch the sides, and maybe that will work. Will investigate

AntiDroid

@totalrando I don't think you understand. This has nothing to do with Google.

Install from the UT openstore https://open-store.io/app/switch-my-slot.shouko

The code for UT https://github.com/ubports-xiaomi-sdm660/Switch-My-Slot-Ubuntu-Touch

The above then links to

Side load for android https://github.com/shoukolate/Switch-My-Slot-Android/releases

The code for android https://github.com/shoukolate/Switch-My-Slot-Android

TotalRando

@antidroid Ah. I haven't actually put UT back yet.... I am still playing with LOS 16, and questioning if I can do this without making my phone sad again. I think I get the dual boot in concept, just nervous. Will let you know.

TotalRando

@totalrando Ok, so now that I am back to feeling adventurous, what is the first step to making sure that I install UBPorts on the correct (empty) slot, leaving LOS 16 in its place right now? Since I have the T-Mobile edition, I would think that it will pull the the SIM data from from the single SIM slot (It does still have A/B however.)

AntiDroid

@TotalRando
Start in fastboot mode and run fastboot getvar all from your host and look for current-slot. It will be either a or b

EDIT: fastboot getvar current-slot may be easier.

Then use fastboot --set-active=a or fastboot --set-active=b to set the active slot to the opposite slot as you found it currently was set. Then follow the instructions for installing UT and it will install to the slot you just set.

EDIT: The latest UBports Blog mentions that Lineage encrypts the home directory by default which means you will not be able to share data between OS's and it could cause other unknown issues.

TotalRando

@antidroid Thanks for your help. In perhaps the worst possible way for this story to end, I lost my beloved Fajita in a Walmart a week and a half ago. Despite attempts to call and leave information to get it back, I fear, sadly, that the phone is lost. But it's definitely worth the experience to give it a try!

ixsvf

Hi, there has been any progress in this port? Thank you!