Hi, just wondered if I’m safe to try flashing a Motorola G32 as I saw someone recently managed to brick their G32 trying to lock the bootloader. Maybe leave it unlocked?
Thanks
1 Like
@misterdan
If you use the iode-7.x-devon-fastboot.zip variant for the iodéOS installation, iodé will be installed correctly and securely and the bootloader will be locked.
I have a Motorola G32 (devon) and did flash iodéOS onto it (directly coming from CalyxOS) in August 25. No problem whatsover (luckily, since I am an absolute n00b).
Where did you read about a G32 brick?
Is this your first time flashing a custom ROM to a smartphone? Motorola made it quite hard for me to get to OEM unlock. I even protocolled the adventure on a German forum. But the flashing of the custom ROM itself was not hard at all. Even did it twice 
since I was too slow for locking the bootloader again at the end. It is highly recommended to save all the passwords/codes/IDs etc. received in this process in case you need to do the flashing all over again one day (like me, going from CalyxOS to iodéOS after one year).
2 Likes
why did u flash iodeOS again? just lock the bootloader.
i did flash iodeOS two times on a g32 and had no problem with relocking the bootloader
a) By that time, I did not know that there are other possibilities to lock the bootloader after the flashing.
b) I just ran the installation again right after the first attempt, and this time I was prepared to answer the question about locking in time. Was easy to do, so why not?
c) Even learned something on the second attempt about the right time to restore data (did it too soon the first time).
Thanks for your replies.
These are the two threads detailing the problems:
I’ve successfully flashed 4 or 5 phones before, mainly lineageOS.
First step is to unlock the bootloader…
I think there is possibility both of those prior issues were related to one or both of these issues:
-
FRP (“Factory Reset Protection”) triggered: this occurs if you have a registered Google account on a device and don’t remove it before reflashing to iodéOS. If triggered, it would prevent unlocking the device again, and will prevent things like installation of apps from Aurora (“Google Play”).
-
SPL (“Security Patch Level”) anti-rollback prevention: This occurs if the patch level (can be seen from “About phone”) is higher on the previous ROM before flashing. If you flash and lock immediately and don’t realize that your new install has an older SPL, then it will not boot. If you also don’t have “Allow OEM Unlocking” enabled in Developer Options before flashing, it could be a hard brick (won’t boot, can’t unlock again to reinstall).
FRP reset is now part of the installation process for FP and Pixels, I am not certain about Motorola but can check. But best to make sure you wipe out any Google Accounts as part of the “pre-install” process, and also make sure the firmware on the device is not newer than the iodéOS build (to prevent SPL rollback protection).
2 Likes
Example: Motorola Moto G32 (devon)
Firmware: XT2235-2_DEVON_RETEU_13_T2SNS33.73-22-3-19_subsidy-DEFAULT_regulatory
CustomROM: iode-7.1-20251225-devon-ota ( metadata: T2SNS33.73-22-3-19 )
1 Like
Thanks, not got round to doing anything yet but I’ll be sure to check the Google accounts and the firmware before I do.
How did you obtain this info?
Unpack iode-7.1-20251225-devon-ota.zip and navigate to > META-INF > com > android and open metadata with an editor.
1 Like
Thank you.
Hi! I didn’t want to create a new post, so I’ll ask my question here.
I discovered IodeOS a few months ago and have been trying to catch up ever since. It’s been hard. Nevertheless, I managed to buy a used Moto G32 and install the 7.4 version on it. I am thinking of sharing my experience due to the problems I encountered.
During the installation process, I did not relock the bootloader as I was afraid it would cause more problems. It’s been a few days, and now I want to relock it. Can someone recommend the best way to do this? Is it as simple as executing one ADB command?
Thanks!
Congratulations for successfully installing a custom ROM!
The G32 is - in my personal opinion - a very uncomplicated device. Not reading much problems about it here in the forum. I am still grateful that I chose this device - being an absolute beginner at that time.
As far as I know (never did it myself) it is as simple as executing the adb command and data should not be erased on locking (but will be deleted on unlocking the bootloader). Maybe you don’t have valuable data on the device yet, since you are still in test mode.
Did you shut off the phone and restart it to check if it boots properly into iodéOS? This is important before manually relocking.
1 Like
The problem I encountered was due to a malfunctioning Windows driver. I followed every step and recommendation from the Windows installer, but since my Windows setup is unusual, it’s possible that this interfered.
Yes, I have been using it for a while and have restarted it a few times. I want to use it as my primary phone, hence the need to relock it.
Do you know the best ADB command for relocking? I have seen two different commands. Thanks for your input.
Hi, I’m getting ready to flash Iode on my G32 and was trying to check the Security Patch Level in “About Phone”. I can’t see SPL mentioned there, is it called something else? Thanks
There are no vendor updates anymore, G32 is “end of life”. So: No worries on that topic!
Edit: Sorry, SPL is Android’s security patch level, not the vendor update. Mixed that up.
But: As far as I know, there is no problem with antirollback for the G32. I think it is a big problem for Fairphone devices, but not Motorola.
Another Edit: Which OS are you currently running? Check at settings → about the phone.
Thanks, its on stock android 13. Can’t see any reference to SPL in “About phone”.
Is it called something else maybe?
So no worries with that: iodéOS 7.4 is Android 16. When did you update the stock OS last?
Thanks, it’s fully up to date