I’ve upgraded my iodeOS firmware from the 6.8 to the lastest 6.9 release on my moto g32, and the touch screen doesn’t work anymore. I used the app installer to do the upgrade.
The side buttons (Power On/Off and sound volume) works well, but impossible to use the touche screen and then unlock my SIM card pin.
It seems that the problem has been raised in Lineage May 2025 delivery.
Solution exposed on this topic is, either make an OTA update (don’t know how to do that => Does anybody know ?), or flash a devon firmware with this issue fix.
Fortunately, plugging an USB mouse by OTG works, so I’m not totally stucked.
Just for my understanding: Did your smartphone tell you that there is a new version and you clicked “download” and “install”? Or did you install the new version through other means (cable, …)?
(OTA is over-the-air-update = your smartphone automatically downloads and installs the latest OS-version)
PS: Updated my Moto G32 to iodéOS 6.9 through the updater, booted and everything is back to normal.
Strange, but certainly not good! One team member has a g32 devon so I am checking with them if they have any similar issue. But as @MissPiggy doesn’t have problems it is a bit confusing.
Do both of you have the device relocked (or both unlocked)?
@MissPiggy Exactly, my smartphone (which was on the 6.8 release) notified me, through the iodéOS app, that a new version (6.9) was available. Then, I clicked “download” and “install”.
After reboot, the tactile screen didn’t work anymore (So, I was stucked on the smart card Pin code screen).
I manage to make it work with a mouse plug by OTG. But it’s not very convenient
My g32 is locked since I installed iodéOS for the first time (about 1 year ago).
I did all the upgrade only via the iodéOS installer app.
Ok, so, then I may consider to flash the firmware again.
What is the good way to flash a firmware, without erasing the user data ? I would like to keep the applications, and the datas. Is that possible, or must I wipe everything and install everyting from scratch ?
Since you still have access to your smartphone: Use a USB-stick and run a backup with Seedvault. I recommend doing this weekly and before every update.
Check, which apps have been successfully backupped. There are apps that do not support Seedvault backups, e. g. Threema you will need to backup seperately to your USB-stick. Copy the USB stick to your computer (as Seedvault might delete the backup after use and it could happen (did to me) that you need to run the flashing/restoring once more). Especially copy files to the stick, since they will not be saved by Seedvault. Check if your 12 passwords really match i. e. whether you will be able to decrypt the encrypted backup.
(edit: Seedvault has been integrated into the settings → backup.)
Write down a list with the apps you really do want to keep. Flash the system anew and let the system install the standard apps (skip the step that you want to restore data from backup). After the system is running, restore the apps that have data in them (like mail app, messenger, etc.) This way you will lose your system settings, but that should be restored quite easily.
Edit again: I do not know anything about purchased apps! (I use FOSS only) Had a photo-TAN-app from my bank which needed new registration after flashing, though.
@mad_matti since you already reflashed your device that means you had to reset it. If you haven’t spent too much time setting it all up again, would you be willing to reflash stock Moto firmware (newest build Android 15 or lower), then try again to use the iodé installer? We are trying to understand this better as we have multiple team members with the device and they don’t experience the issues. A possible theory is that updated Moto firmware exists on the working phones but the non-working ones had older underlying moto firmware that shows its incompatibility with the updates to iodé.
I don’t want to suggest to @FonkyKoala they do this since they are eager to not lose their userdata (but if your test succeeds, then they may need to or instead stay on the older iodé build… but getting them back to that older build is also a bit “iffy”).
the g32 is set up again. The backup with seedvault works fine. Only the closed apps like the Bank account need some manual action. I don’t want do start one more time. Sorry. I’m just a normal user with medium risc requirements. Lineage is OK for me.
No, sideload via adb in the recovery. To boot in recovery, go to fastboot mode, and select Boot to recovery. Or from the running system, ‘adb reboot recovery’. Then got to Apply update, apply from adb, and on computer type ‘adb sideload iode-6.9-20251107-devon-ota.zip’.
I was able to successfully update Moto G32 (devon), Moto G42 (hawao) and Moto G52 (rhode) to iodéOS 6.9 without any issues – including relocked bootloader.