I create unofficial iodéOS builds approximately monthly for these devices and host them on the LineageOS for microG download server, with OTA update support included:
To install, download all the files for the newest iodéOS version and follow the linked Installation Guide, but use the downloaded .img and .zip files.
Note: Bootloader re-locking is not possible with these unofficial builds. As with all modern Android systems, your userdata is encrypted and safe unless your unlock pattern / pin is compromised.
The main motivation for the Moto G 5G (2024) fogo build is that this device is one of the few newer Moto devices available in the USA that also have official LineageOS support, so it is a very good candidate to sell at my personal business, https://openmobile.us. Here is a direct link to the product page if you would like to recommend this device to a friend (I am assuming if you are reading this you probably would prefer installing yourself instead of buying from me).
As the Moto G34/45build is a very similar device for the European market and I have the build environment already setup for fogo it is easy to produce the fogos build as well.
I have just updated both fogo and fogos to v7.3. Users with my older builds for these devices will receive the updates “OTA” from the Updater app. Let me know if there are any issues!
I have just updated both fogo and fogos to v7.4. Users with my older builds for these devices will receive the updates “OTA” from the Updater app. Let me know if there are any issues!
Hey Rik, I’m just starting out on my Moto G32, and I want to help my partner do the same. I have a question: would a used Moto G34 be a good choice right now? I I’ve checked that our banking app works, but I haven’t tested it with the Moto G32’s bootloader unlocked. Do you know if there is a good chance that Iode will support the relock process?
I haven’t heard any discussion of adding an official G34 build from the iodé developers. IF they do, THEN I suspect it would be able to be re-locked. But my unofficial builds do not support bootloader re-locking (I just haven’t had the time to dig into it, it may be possible but I don’t have any timeline for that).
Regarding banking apps working or not working in iodéOS based on it being locked or unlocked, I think that microG reports the device is locked to apps regardless of actual state. Put another way, I don’t know of any cases where the actual lock has enabled a non-working app to work… meaning that if your bank app works on iodéOS with a locked bootloader I would fully expect it to work with an unlocked bootloader, and vice-versa if it doesn’t work unlocked then it likely will not work locked either.
Regarding banking apps working or not working in iodéOS based on it being locked or unlocked, I think that microG reports the device is locked to apps regardless of actual state. Put another way, I don’t know of any cases where the actual lock has enabled a non-working app to work… meaning that if your bank app works on iodéOS with a locked bootloader I would fully expect it to work with an unlocked bootloader, and vice-versa if it doesn’t work unlocked then it likely will not work locked either.
Interesting. I think this isn’t the first time I’ve read about this. Fun fact: So far, the only app that doesn’t work for me has been tested with unlocked and locked bootloader…
About the Moto G34: I managed to buy a used one here in Portugal and I’m waiting for it to arrive. Do you think that will work as daily driver solidly? By the way, I’m trying to prepare for the installation, which will probably be more difficult, and I’m a bit limited in this matters. I tried clicking the link you provided, but it’s not working. Could you share some good tips on things to keep in mind? I know this device is still receiving official updates so I have to try hard to not mess up.
I see the G34/45 come with either 4 or 8 GB of RAM, certainly the 8GB will be better for long term, but even now I personally find 4GB sufficient, and this is with a slower / older processor (with a Pixel 3a XL bonito). For reference, here is a NanoReview overall benchmark comparison:
Thank you, I’ve already checked. So for the installation of the iodeOSversion 7.4 it’s just following the lineage OS guide using your files like you mention, right? Since we are talking about a motorola phone which still has official updates, do I have to be careful with something besides Security Patches “thing”?
My question was more related to your unnofficial build. Is there any bugs/problems? Performance-wise I don’t worry too much.
I have installed it on a customer phone and done a lot of testing on it, I didn’t see any issues.
To make sure and avoid any security update “anti-rollback prevention” risks, you can find the date from “About phone” for your existing install and make sure it is from earlier in 2026 at the newest.
Also make sure any logged in Google account in your existing install is removed before installing iodé or you could trigger “Factory Reset Protection” which could also effectively brick the device.
Nice. Did you tested the VoLTE function just out of curiosity?
Thanks. I’m aware of the FRP trigger situation and it’s never enough to remind it. My main doubt is more about receiving the Phone with pendent official updates and I am bit anxious about the best way to proceed since I read this could cause the impossibility to unlock the bootloader for e.g.. May I ask you what is your reccomendation in this case? Should one do all run all official updates first or never this way?
Yes, no issues with VoLTE / 5G calls or data, etc.
I would NOT apply any pending updates. “The older the build on the device the better” just to make sure to prevent ARB (“Anti RollBack”) Protection. The iodéOS builds should include the required manufacturer blobs for hardware support (they are included in the build process so if there are published updates for them then they get updated as well with newer builds).
I have to read more about this because I’ve stepped on this a few times studying the iodeOS installation. I did run all official updates on my moto g32 so I hope that doesnt bite me back… I received the phone with pending updates already.
But even for phones that are not officially supported by iodeOS?
Yes, the vendor proprietary bits are pulled in by the repositories maintained by the TheMuppets project. Here is a link to the manifests for that, you can find “fogos” in this list and then follow that to the repo with the Motorola binaries: manifests/muppets.xml at lineage-23.2 · TheMuppets/manifests · GitHub
Here is a bit more of an explanation on the process I and others use for making Unofficial builds:
