Why does iodé support pixel 3 but not 3xl, 4 but not 4xl, 5 but neither 4a5g nor 5a, unlike how grapheneos, calyxos, divestos and /e/ do? Why does iodé abandon people owning these models?
I only follow Usage and Skipping root patches with --clear-vbmeta-flags option to remove the flag disabling full avb in the vbmeta, but as the vbmeta is signed the only way to modify it is to resign it with own key.
Because
the challenges of maintaining such a project as a one-person effort.
Like many open source custom ROMs, IodéOS support for older or less common devices happens because of the associated community of volunteers with an interest in specific devices (e.g. me with Sony devices, @rik with Google Pixel devices, and @ronnz98 with a very wide range of devices). Iodé are - and always have been - very helpful to such volunteers. But they are a commercial organistion (though a small one) which needs to make decisions that allow it to stay in business and - with luck - to eventually make some money to justify the effort they put in.
It is not ‘abandoning’ them, since the project never supported them.
Are the any plans for an unofficial build for the Pixel 9a (tegu)?
There’s no official LineageOS support yet - see here.
It’s being worked on (see here) but it’s not ready yet
As Pete notes, it is being worked on. As it had no Android 15.x release, that is the main reason for the delay. As LOS 23 / A16 was just announced it will be a bit more before the LOS builds for it are stable. Then I will need to wait for iodé 7.x, and then after all of that dust settles I can add it to my build list 
Thank you, rik!
I’m sorry to ask what may be a silly question: would I be installing LineageOS onto the Pixel Tablet first, and then flashing iodéOS? When clicking on the link on the left (Pixel Tablet tangorpro), I see a detailed document on installing LineageOS for the Tablet; when I select the right-hand link (6.8 under the latest iodéOS build), I’m taken to a folder with lots of files. I’m assuming I would download the .zip file (1.5 GB in size); but as to what would come next, I do not know. Is there a guide somewhere?
Basically, my goal is to remove GrapheneOS from first my Tablet, and then my Pixel 8a, and finally flash iodéOS onto both. To that end, I’d like to experiment with the unofficial build of the Tablet first, since that is less important than the 8a, which is my daily driver.
Final question: do you think it would be beneficial to load the stock OS back onto each device before flashing iodéOS? Or is it possible to go from Graphene to iodé without reverting to stock?
Thank you so much!
I could probably be a bit more clear on the download post, but the reason for the link to the Lineage documentation is that you follow it but when it comes to the actual images to flash, you use the files from my builds instead of the Lineage ones. iodéOS is built on top of LineageOS, so a lot of the prep is the same.
This is where the Lineage install steps are helpful: they are explicit that you need to first return to stock Android 15: installing on top of GrapheneOS won’t work as they modify the underlying base that Lineage and iodé expect.
Note that the Pixel 8a is now and officially supported device meaning you can use the graphical installer for it, and it will give the chance to re-lock the bootloader (my unofficial builds don’t have this ability). As noted above, you will want to revert to a stock Android 15 install first, using https://flash.android.com (with a Chromium-based browser).
After you flash stock, you may not even need to set it up, but if you do for some reason there should be no need to connect to the internet.
Thank you again, rik…I appreciate you!
I’ve read through the steps on installing LineageOS a couple of times, but I’m not seeing instances of where your iodeOS files would go for quite a few of the files (specifically, the “init_boot.img,” “super_empty.img,” “vbmeta.img,” and all of their corresponding sha256sum files). Would I just skip those?
After this major tinkering project (major for me, that is ) on the Tablet, I’ll be glad to use the official graphical installer for the 8a.
Question pertaining to the phone once iodeOS has been flashed (and I apologize that it’s a silly one): would I need to bring the phone to the store (AT&T is my carrier) to have them activate the eSIM? Surely that does not remain after reverting to stock and then flashing iodeOS…?
Thank you so much again for your time!
Note I am moving these posts to the Unofficial Google Pixel Build thread
The build process produces extra partitions that are often not necessary, you can ignore those if the install instructions don’t reference them (the main ones you want are the main ...zip and the ...boot.img but again sometimes a few others may be needed.
All of the .sha256sum are the checksums so that you can confirm your download is not corrupt. With a <filename> and the corresponding <filename>.sha256sum in the same directory, for example, on linux you can run sha256sum -c <filename>.sha256sum and it will output OK if all is good.
I have not used eSIMs before, but others report they do register just fine using the included OpenEUICC app. I don’t know about transferring one, however. Do you have a registration link for it you can re-use, or do you maybe “export it” from the phone and then re-import? Sorry this may be good to make a new post on with a title something like “How to transfer an eSIM” or something like that so we can get broader input from the community that may be more familiar with them.
Hey rik I have a question. Lineage 23.0 was released not too long ago but they didn’t have android 16 builds for newer pixel devices. I was wondering if this is a road block for iode os developers in releasing version 7.x for these newer pixels or if there is a work around. Thanks in advance.
If there is no Lineage 23 build available for Pixels it will also prevent making iodé 7.x builds. It is still early though: I see that the Lineage team hasn’t given up on working toward Lineage 23 builds for Pixels even though they aren’t there yet.
Thank you again, good sir! Your time and input is greatly appreciated!
Sorry, I should have mentioned that I was aware of the sha256 files’ functions. I’m pretty sure that I did not see the three .img files that I mentioned above when studying the LineageOS instructions, so I’ll ignore those during the flash process on the Tablet.
Great tip on starting a new thread on transferring the eSIM to a newly-flashed phone; I will do that. I had the luxury of using the 8a as a wifi device for a while after flashing GrapheneOS onto it almost immediately after purchasing it, so this is a new situation for me. I’m guessing that a new one will be needed after flashing iodeOS and that AT&T will probably charge me around $25 for the privilege… Thanks also for the tip on the OpenEUICC app. I’d seen that mentioned here on the forums a couple times.
Last (I hope!) question: I run Pop!_OS. Do you think that the flatpak version of Chromium from the Pop!_Shop would be alright to use when flashing the stock OS, or do you think I should assume that an official Google Chrome build would be necessary?
Thank you!
LOS23 is released for Pixel 9a today LineageOS Downloads
Stable in a month ??
I also use the Chromium flatpak version, it works fine for flashing stock 
Great to see it! That will trickle down to us when iodé 7 is ready, stay tuned!
Thanks, @rik ! I flashed the unofficial build to my Pixel Tablet last night (and used the flatpak version of Chromium to revert to stock easily) and was shocked at how easy and seamless the process was (and quick, too)! Thank you for your excellent work for the whole community! I’ll be playing with iodeOS on the Tablet for a while before I make the switch on my 8a.
Great to hear!
I have completed v6.9 Unofficial Pixel builds and have uploaded them to the download server (same link as listed in the table above as those links are only to the device folder).
I have confirmed a successful update on a Pixel 3a XL bonito using the “Updater app > 3 dots > Local update” option.
Yet again, I didn’t get a chance to look at enabling an OTA update server for these builds, and also didn’t look into possible bootloader relocking. Some day!
Hi all,
Now that I am getting used to iodeOS on my Pixel Tablet (tangorpro) – again, great job and thank you, @rik —I have a couple follow-up questions:
; and (2) when I select check for updates, it always states “check your internet connection,” even though I have no issues there (I’ve tried both with and without ProtonVPN running, and it is the same).
) and the update fails. I have one other user profile set up, and I have not logged into a Google account (nor do I plan to).Other than that, things are going well and I am really enjoying iodeOS. Thanks again to all the developers and the community!
Aurorastore is confused. It thinks MicroG is playservices (GMS). You can click Ignore. MicroG is updated via Fdroid.