@rik
I’d like to install your unofficial iodéOS on my Google Pixel 9 Pro (caiman). But before I’ll do this I’ve to questions:
No, as I understand it is not available publicly, it is “baked in” to Google’s builds. BUT, you can obtain .apks from GCam Hub, which I don’t fully understand but am testing with myself. It is some sort of mashup of the proprietary Google apks with mods to make it work for non-Pixel devices and / or devices without Google Play Services (like iodé or other microG builds). There is more discussion in this topic.
Since the “build keys” will be different, you won’t be able to update using the “Updater” app. But I would assume a “dirty flash” will work from recovery, meaning you should not need to wipe the device. So all your user data should be fine, installed apps still installed, etc.
Note that after installing the iodé version (when it becomes available), if you would choose to then re-lock your device it would then wipe your userdata (pretty sure about that).
Hello everyone
I have recently installed iodeOS on a Pixel 4a. In the table it says tested: ‘no’. Is there something which needs to be tested which changes it to ‘yes’? Will that eventually make it switch to supported?
No. It is marked as not tested because the team who make these unofficial builds (for Pixel and Sony devices) do not have
The good news is that the code in these builds has been tested
So you are unlikely to see any problems which do not occur (and which will nt be fixed eventually) in either the LineageOS, LineageOS for microG, or IodéOS ROMs for these devices.
Unlikely. As far as I know, the Iodé team are not looking to add devices to their list of supported devices. And if they did, they would probably focus in more recent devices rather than the five year old 4a.
Thank you for your detailed and transparent explanation.
So I’m looking at the instructions for installing iode on Linux, and I’m running into the issue of which <iode…boot.img> to download. there are so many and the only one that seems to work is the vendor kernel, however it doesn’t reboot me into recovery- I get the G, then bootloop. Any ideas?
Thanks,
I moved your post from “installation” to this thread, as the installation tag is for officially supported devices. With the move, I lost your message title, but I think you are asking about a P9P, “caiman”, is this correct?
You should only need the base boot image, this one: https://download.lineage.microg.org/IodeOS/caiman/iode-6.4-20250527-UNOFFICIAL-caiman-boot.img
And then of course the actual image, this one: https://download.lineage.microg.org/IodeOS/caiman/iode-6.4-20250527-caiman.zip
The build process makes all those extra artifacts but shouldn’t be needed. So use these commands:
fastboot flashing unlock
fastboot flash boot iode-6.4-20250527-UNOFFICIAL-caiman-boot.img
Then start recovery… go to adb update screen and run the following command:
adb sideload iode-6.4-20250527-caiman.zip
Keep us posted!
Just back from traveling for the past few weeks, I’ll try to get the v6.5 builds made in the next few days.
I have uploaded the v6.5 builds, with again only bonito having been tested. I am giving walleye and taiman another try as well, I’ll update the table if they succeed.
Hello rik,
I installed your iodéOS 6.5 port on my Google Pixel 9 Pro (“caiman”). It runs great – thanks for your work 
However, I have had the following experiences:
After installing “…boot.img,” my 9 Pro would no longer start, and I had to install the individual “.IMG” files one after the other according to these LineageOS instructions: Install LineageOS on caiman | LineageOS Wiki
I cannot lock the bootloader again after installation
I cannot install the original Google Pixel camera app (this is the answer to my question above 
)
I found a few Google system components (see screenshot). Is this intentional and what data is transmitted to Google? I’m asking because I assumed that iodéOS was completely de-googled…
And I noticed the following annoying little things, which are apparently also present in the official ports:
The lock screen clock does not switch to analog when the corresponding setting is selected – not even after a restart
The sound when unlocking the smartphone is not turned off, even if the corresponding setting is disabled – not even after a restart.
It would be great if these inconveniences could be fixed…
Otherwise, I’m looking forward to the next release
Thanks for the explanation, and glad you succeeded. I haven’t attempted to install an unofficial build on anything newer than a Pixel 3a XL, and I honestly haven’t known when (or IF) the extra build artifacts would be needed. I will try to adjust the top post to note that these extra partitions may need to be applied, noting the LOS instructions should be followed in that case.
Yes that is correct. The LOS 4 microG build process doesn’t have the ability to re-lock the bootloader. I would like to dig into this, but it may not be coming for some time. Note that, in my understanding, an unlocked bootloader is only a risk to an “evil maid attack”, your data is encrypted and safe unless your unlock code is compromised.
When iodé officially supports the Pixel 9 series, it will give the ability to relock the bootloader.
Yes, as noted above please see the GCam Hub ports for Pixel Camera.
I believe the installed versions of these apps are NOT Google versions, but are spoofed components coming from microG. Attempting to install the updates may indicate it succeeds, but in reality I think it doesn’t actually install them. You can long-press on them and add to “blacklist” not have them show in the Aurora Store updates.
Not certain though, it may be better to post an inquiry on these to the general “Apps and Core Settings” category for broader input.
By “official port” do you mean the Google builds? I haven’t noticed these issues, but could test. Again this may be better to comment on to the “Apps and Core Settings” category (please keep to 1 issue per thread so we can keep it on track and mark solved when it is indeed solved).
No, I meant the iodèOS builds for the officially supported devices. Last year I tried iodéOS on a Fairphone 5 and there were the same issues:
@ronnz98 - I’m very glad for the taimen update. It already landed on my phone yesterday. Local update didn’t work for me but flashing from recovery did the job.
@ronnz98 I second that, thanks for the taimen and walleye updates. My attempted builds for those continue to fail with various partition sizing problems (running out of space). There may possibly be a bit of a bug in the lineageOS 4 microG build process because attempting to pass larger partition size settings is not taking effect as I expect. Or maybe the problem is between my keyboard and chair 
. Regardless, could you share more on your build environment? I don’t think I will look at it closely this week but would like to resolve why my builds are failing for those 2 devices.
The solution is easy if you know how. Sorry for not explaining it earlier.
I’m not fully sure since it is different in the several AOSP but you need to look where the prebuilt apps are for iode (vendor/extra I think?). There you find a file which is called common.mk and you need to comment out or delete some apps that are not mandatory for the system (eg. Thunderbird, Aurora App etc). I do not remember how many prebuilt apps I removed, but you can see how many space / partition size is the maximum for this devices and count the difference
Sorry everyone, I didn’t start the 6.6 builds yet, I have been quite busy helping out with the release of the brax3 phone. But will get these builds rolling in the next day or so.
OK, all 6.6 builds I make have completed, and bonito has successfully installed via Updater App > Local update. Others are untested, let me know if you find any issues!
This might be a dumb question. I alrwady have lineage on my 9 pro fold, then i found out about this. Do i just do a full install like i did for lineage but replace the .zip file, or do i onoy have to install a certain file ?
Im okay with erasing the data to do a proper install if thats needed
Thanks
I am not sure of your recovery, but you would need to install from recovery using adb sideload of the .zip. Cleanest would be to just install the iodé recovery with fastboot, then boot the new recovery, then adb sideload the .zip. The bottom of the top post walks you through this. Good luck!
You can try to not wipe your userdata (that is what we mean by “dirty flash”), but if there are issues you may need to do the “factory reset” which will wipe userdata.
Im using the lineage recovery i believe. The process is what i assumed but wanted to verify. I will do tge full install as i have not used the device enough to care about wiping it.
Thank you.
