Flashing a Moto G32

[misterdan]

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

[iodysseus]

@iodysseus

(re)locking the bootloader with iodè OS works perfectly for me with my three Motorola G32, G42, G52.

@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.

[MissPiggy]

@misterdan

if I’m safe to try flashing a Motorola G32

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).

[Pierce]

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

[MissPiggy]

@Pierce

why did u flash iodeOS again? just lock 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).

[misterdan]

Thanks for your replies.

These are the two threads detailing the problems:

Installed iode on Motorola G32, but unable to lock bootloader

Hi, I used the installer flash iode on my G32 which ended successfully and asked whether I wanted to lock the bootloader. I guess I was a bit slow in answering so it defaulted to No and ended. The phone boots successfully into iode. I went back into fastboot mode and used the command 'fastboot flashing lock, which seemed to succeed as it flashed a message ‘Bootloader is now locked’. However when I reboot the phone it immediately shows a message saying ‘No valid operating system can be found on…

Bricked Motorola G32 after trying to lock bootloader?

Hi, I have another post on here about being unable to lock the bootloader after installation but it now looks like the phone might be bricked. I updated the firmware before flashing to android 13 and then installed with the installer software. All seemed to go well but I was too slow when asked to lock bootloader so the phone rebooted in an unlocked state. I went back into fastboot mode and used the command 'fastboot flashing lock, which seemed to succeed as it flashed a message ‘Bootloader is …

I’ve successfully flashed 4 or 5 phones before, mainly lineageOS.

First step is to unlock the bootloader…

[rik]

@misterdan

These are the two threads detailing the problems:

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).

[iodysseus]

@rik

,… and also make sure the firmware on the device is not newer than the iodéOS build …

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  )

[misterdan]

Thanks, not got round to doing anything yet but I’ll be sure to check the Google accounts and the firmware before I do.

[rik]

@iodysseus

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  )

How did you obtain this info?

[iodysseus]

@rik

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.

[rik]

@iodysseus

navigate to > META-INF > com > android and open metadata with an editor.

Thank you.