Halium 9 / CI + OTA build
-
@totalrando said in Halium 9 / CI + OTA build:
@antidroid @rogier-oudshoorn I'm down to begin this process. Is there a quickstart process or is it basically starting by cloning this and doing the steps? https://gitlab.com/ubports/community-ports/android9/oneplus-6/oneplus-enchilada-fajita
I've never done this before, but I feel comfortable enough to start figuring it out. That, and my only other phone is a Nexus 4 (3G) and I am not going back to Android on this. If I have to help build this up, I will. Those issues are not insurmountable. (Curious about the camera though... worth investigating.)I am fairly sure you do not need to build anything. The last link Roger posted was a link to compiled images. A boot.img and a system.img
But again no instructions on how to flash other than Rogers comment on using fastboot. I would have thought you use the same technique as the GSI but since he says this is not a GSI I am not sure.I would simply try flashing them as if they were a GSI but I am currently dual booting to postmarket on a custom Gnome build I am working on and do not want to risk losing the changes until I have my install-able version matching the changes I have made on the phone directly. You can always reflash the phone back to stock and start over.
OnePlus One with UT OTA-15 daily driver. I would be testing the Halium 7.1 port if I could roll back to OTA-15
OnePlus 6T PostmarketOS Custom Gnome on Mainline Kernel -
@antidroid It's not a GSI. It's a Continuous Integration system (CI). Kind of like a pseudo-central base to withdraw from.
Like an artificial speed force.
-
@totalrando said in Halium 9 / CI + OTA build:
@antidroid It's not a GSI. It's a Continuous Integration system (CI). Kind of like a pseudo-central base to withdraw from.
Like an artificial speed force.
I get that but the two files the Roger linked to in the last link of his post are the same types of images as used for a GSI (system image and boot image). As to how they are flashed I was guessing it is like flashing a GSI but again the lack of documentation leaves us to guess.
I think the difference is that is more like an edge build. The continuous integration means it gets patches and updates pushed to it and are built to test for problems but does not create actual files so they are not installed on devices. The files he linked to were created 6 days ago but if you look through the jobs you can see it is simply the last successful build from a month ago being made into actual downloadable files.
-
@antidroid said in Halium 9 / CI + OTA build:
@rogier-oudshoorn said in Halium 9 / CI + OTA build:
you have to flash on top of LOS 16, it won't boot on any other base.
I would just like to confirm you actually mean it has to be Lineage 16 and not any other Android 9 version that Lineage is based off of? Or do you just mean the equivalent version to LOS 16? If it has to be LOS 16 can you explain why? If it has to be LOS 16 does it matter which point release?
You'll need to run exactly LineageOS 16, not just any Android 9 version. I presume this is because LOS changed some of the partitions, and we need it to load their drivers, but i'm not sure. I'm running on the latest LOS16, and i suggest everyone does the same.
-
I am fairly sure you do not need to build anything. The last link Roger posted was a link to compiled images. A boot.img and a system.img
But again no instructions on how to flash other than Rogers comment on using fastboot. I would have thought you use the same technique as the GSI but since he says this is not a GSI I am not sure.I would simply try flashing them as if they were a GSI but I am currently dual booting to postmarket on a custom Gnome build I am working on and do not want to risk losing the changes until I have my install-able version matching the changes I have made on the phone directly. You can always reflash the phone back to stock and start over.
Yeah, exactly! Please download the system.img and boot.img artefacts from the CI job - CI will do the building for us.
It's not a GSI, and you need to flash with fastboot instead of twrp. IF you're on the right slot ( you can check with fastboot getvar current-slot ), the steps are:
-
fastboot flash boot boot.img (flashes the boot.img to the boot partition of your current slot)
-
fastboot flash system system.img (flashes system.img to the system partition of your current slot)
-
fastboot reboot (reboots your phone on the current slot)
-
-
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.
OnePlus One with UT OTA-15 daily driver. I would be testing the Halium 7.1 port if I could roll back to OTA-15
OnePlus 6T PostmarketOS Custom Gnome on Mainline Kernel -
@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
Nerd with UT on a OnePlus One. OnePlus 6T waiting in the wings for VoLTE.
-
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 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.
-
@totalrando said in Halium 9 / CI + OTA build:
@rogier-oudshoorn
fastboot flash boot system.imgYeah, you should flash system.img to system, boot.img goes to boot ...
-
@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?
-
BTW: The same version problem of LineageOS 16 exists for the Xiaomi Pocophone. Any long term archives of LOS?
-
@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.
-
@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.
-
@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.
-
@totalrando Rogers link was to a LOS16 for pocophone not oneplus 6/6T
-
@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
-
@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.
-
@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
-
@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
OnePlus One with UT OTA-15 daily driver. I would be testing the Halium 7.1 port if I could roll back to OTA-15
OnePlus 6T PostmarketOS Custom Gnome on Mainline Kernel
