Installer failed Motorola G32 - Boot loop

maxito · September 20, 2026, 4:02am

Hi Community,

I am new to this. First time I do any installation on a mobile phone. I followed the installer instructions on windows 11 and the phone is now stuck in a boot loop.

Any suggestions?

See installer log here:

When I start the phone it says Your device is loading a different operating system contact support.motorola.com OS Fingerprint: 0xC4F18977

Setting current slot to ‘a’ OKAY [ 0.203s]
Finished. Total time: 0.203s
Erasing ‘avb_custom_key’ OKAY [ 0.014s]
Finished. Total time: 0.015s
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending ‘avb_custom_key’ (1 KB) OKAY [ 0.001s]
Writing ‘avb_custom_key’ OKAY [ 0.014s]
Finished. Total time: 0.018s
Warning: userdata type is raw, but f2fs was requested for formatting.

F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11)

Info: Debug level = 1

Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 230928344 (112757 MB)
Info: block size = 4096
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
“”
[f2fs_init_sit_area: 743] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 777] Filling nat area at offset 0x01200000
[f2fs_add_default_dentry_root:1393] Writing default dentry root, at offset 0x1d800
[f2fs_write_root_inode:1439] Writing root inode (hot node), offset 0x1d200
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d801 (1/2)
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d802 (2/2)
[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d201
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d803 (1/2)
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d804 (2/2)
[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d202
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d805 (1/2)
[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d806 (2/2)
[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d203
[f2fs_update_nat_default:1620] Writing nat root, at offset 0x00001200
Info: Overprovision ratio = 0.430%
Info: Overprovision segments = 246 (GC reserved = 239)
[f2fs_write_check_point_pack: 969] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack:1056] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1070] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1082] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1096] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1104] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1146] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1165] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1198] Writing super block, at offset 0x00000000
Info: format successful
Warning: skip copying userdata image avb footer due to sparse image.
Sending ‘userdata’ (89 KB) OKAY [ 0.003s]
Writing ‘userdata’ (bootloader) flash permission denied
FAILED (remote: ‘’)
fastboot: error: Command failed
Warning: skip copying modem_a image avb footer due to sparse image.
Sending ‘modem_a’ (75520 KB) OKAY [ 1.917s]
Writing ‘modem_a’ OKAY [ 0.363s]
Finished. Total time: 2.282s

Bootloader Version…: MBM-3.0-devon_g-8847829342a-250806

Baseband Version…: HAK11_15.154.01.90R DEVON_APEMDSDS_CUST
Serial Number…: ZY22G23PWS

extracting android-info.txt (0 MB) to RAM…
Checking ‘product’ OKAY [ 0.000s]
Setting current slot to ‘a’ OKAY [ 0.224s]
extracting fastboot-info.txt (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to disk… took 0.000s
(bootloader) super-partition-name: not found
Writable partitions are not supported
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting super_empty.img (0 MB) to RAM…
extracting boot.img (96 MB) to disk… took 0.216s
archive does not contain ‘boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘boot_a’ (98304 KB) OKAY [ 2.482s]
Writing ‘boot_a’ OKAY [ 1.366s]
extracting super_empty.img (0 MB) to RAM…
extracting dtbo.img (24 MB) to disk… took 0.045s
archive does not contain ‘dtbo.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘dtbo_a’ (24576 KB) OKAY [ 0.621s]
Writing ‘dtbo_a’ OKAY [ 0.154s]
extracting super_empty.img (0 MB) to RAM…
extracting vendor_boot.img (96 MB) to disk… took 0.183s
archive does not contain ‘vendor_boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vendor_boot_a’ (98304 KB) OKAY [ 2.479s]
Writing ‘vendor_boot_a’ OKAY [ 0.602s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_a’ (8 KB) OKAY [ 0.001s]
Writing ‘vbmeta_a’ OKAY [ 0.009s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta_system.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta_system.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_system_a’ (4 KB) OKAY [ 0.001s]
Writing ‘vbmeta_system_a’ OKAY [ 0.009s]
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Erasing ‘userdata’ OKAY [ 0.368s]
Finished. Total time: 0.393s
Rebooting into fastboot OKAY [ 0.021s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.051s]
Finished. Total time: 0.051s
< waiting for any device >
(bootloader) Bootloader is now locked

OPress any key to exit…
KAY [ 24.340s]
Finished. Total time: 24.341s

That’s all I can see in the log.

Many thanks for your help,

Max

maxito · September 20, 2026, 9:33pm

Also, I went to recovery mode and did a factory reset, but I do not know what should I do next. Shall I try and restore stock ROM and try the installer again? Any pointers on how to restore the stock ROM? I am stuck in the fastboot screen.

maxito · September 22, 2026, 8:12am

Hi all,

Does anyone know why the installer failed. It seems to me that this log section shows the installer did was not able to write data “Writing ‘userdata’ (bootloader) flash permission denied“:

Info: format successful
Warning: skip copying userdata image avb footer due to sparse image.
Sending ‘userdata’ (89 KB) OKAY [ 0.003s]
Writing ‘userdata’ (bootloader) flash permission denied
FAILED (remote: ‘’)
fastboot: error: Command failed
Warning: skip copying modem_a image avb footer due to sparse image.
Sending ‘modem_a’ (75520 KB) OKAY [ 1.917s]
Writing ‘modem_a’ OKAY [ 0.363s]
Finished. Total time: 2.282s

What could have gone wrong? Because I did enable the developer options OEM unlocking before running the installer and the installer screen showed a successful unlock …

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

On a separate note, this is what I managed to do to recover the phone and re-install the stock rom.

go to rescue mode and did a factory reset. not sure this is 100% needed, but that is what I do first.
downloaded the minimal fastboot/adb : https://xdaforums.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790
I unlocked the bootloader like shown in this video:

https://xdaforums.com/t/motorola-g-stylus-2021-xt2115-1-minsk-soft-brick-fix.4633071/

How To FIX Your Device Is Corrupt,It cant be trusted and will not BOOT on All Motorola Phones Easily - YouTub

4. then after the boot loader was unlocked I recovered the phone using the motorola Software Fix. However, this software would say the phone is no longer supported, in order to get this software to work I used the search option where you can find the ROM by entering your phone’s IMEI.

maxito · September 22, 2026, 11:21am

An update on progress. After restoring the stock rom as described above, I run again the windows installer. The installer screen completed with a message saying the installer failed.

However, even though the error “Writing ‘userdata’ (bootloader) flash permission denied“ continues to be in the log. The system booted iode and it seems to work ok. The next step for me is to try and lock the bootloader tomorrow.

See full log here:

Setting current slot to ‘a’ OKAY [ 0.182s]

Finished. Total time: 0.182s

Erasing ‘avb_custom_key’ OKAY [ 0.014s]

Finished. Total time: 0.015s

Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).

Sending ‘avb_custom_key’ (1 KB) OKAY [ 0.001s]

Writing ‘avb_custom_key’ OKAY [ 0.014s]

Finished. Total time: 0.022s

Warning: userdata type is raw, but f2fs was requested for formatting.

F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11)

Info: Debug level = 1

Info: Trim is disabled

Info: Set conf for android

Info: Enable Project quota

Info: Segments per section = 1

Info: Sections per zone = 1

Info: sector size = 512

Info: total sectors = 230928344 (112757 MB)

Info: block size = 4096

Info: zone aligned segment0 blkaddr: 512

Info: add quota type = 0 => 4

Info: add quota type = 1 => 5

Info: add quota type = 2 => 6

Info: format version with

“”

[f2fs_init_sit_area: 743] Filling sit area at offset 0x00600000

[f2fs_init_nat_area: 777] Filling nat area at offset 0x01200000

[f2fs_add_default_dentry_root:1393] Writing default dentry root, at offset 0x1d800

[f2fs_write_root_inode:1439] Writing root inode (hot node), offset 0x1d200

[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d801 (1/2)

[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d802 (2/2)

[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d201

[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d803 (1/2)

[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d804 (2/2)

[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d202

[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d805 (1/2)

[f2fs_write_default_quota:1531] Writing quota data, at offset 0001d806 (2/2)

[f2fs_write_qf_inode:1582] Writing quota inode (hot node), offset 0x1d203

[f2fs_update_nat_default:1620] Writing nat root, at offset 0x00001200

Info: Overprovision ratio = 0.430%

Info: Overprovision segments = 246 (GC reserved = 239)

[f2fs_write_check_point_pack: 969] Writing main segments, cp at offset 0x00000200

[f2fs_write_check_point_pack:1056] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201

[f2fs_write_check_point_pack:1070] Writing Segment summary for HOT_NODE, at offset 0x00000202

[f2fs_write_check_point_pack:1082] Writing Segment summary for WARM_NODE, at offset 0x00000203

[f2fs_write_check_point_pack:1096] Writing Segment summary for COLD_NODE, at offset 0x00000204

[f2fs_write_check_point_pack:1104] Writing cp page2, at offset 0x00000205

[f2fs_write_check_point_pack:1146] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400

[f2fs_write_check_point_pack:1165] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405

[f2fs_write_super_block:1198] Writing super block, at offset 0x00000000

Info: format successful

Warning: skip copying userdata image avb footer due to sparse image.

Sending ‘userdata’ (89 KB) OKAY [ 0.003s]

Writing ‘userdata’ (bootloader) flash permission denied

FAILED (remote: ‘’)

fastboot: error: Command failed

Warning: skip copying modem_a image avb footer due to sparse image.

Sending ‘modem_a’ (75520 KB) OKAY [ 1.959s]

Writing ‘modem_a’ OKAY [ 0.237s]

Finished. Total time: 2.203s

--------------------------------------------

Bootloader Version…: MBM-3.0-devon_g-8847829342a-250806

Baseband Version…: HAK11_15.154.01.90R DEVON_APEMDSDS_CUST

Serial Number…: ZY22G23PWS

--------------------------------------------

extracting android-info.txt (0 MB) to RAM…

Checking ‘product’ OKAY [ 0.000s]

Setting current slot to ‘a’ OKAY [ 0.206s]

extracting fastboot-info.txt (0 MB) to RAM…

extracting super_empty.img (0 MB) to RAM…

extracting super_empty.img (0 MB) to disk… took 0.001s

(bootloader) super-partition-name: not found

Writable partitions are not supported

extracting super_empty.img (0 MB) to RAM…

extracting boot.img (96 MB) to disk… took 0.216s

archive does not contain ‘boot.sig’

extracting super_empty.img (0 MB) to RAM…

Sending ‘boot_a’ (98304 KB) OKAY [ 2.495s]

Writing ‘boot_a’ OKAY [ 1.513s]

extracting super_empty.img (0 MB) to RAM…

extracting dtbo.img (24 MB) to disk… took 0.045s

archive does not contain ‘dtbo.sig’

extracting super_empty.img (0 MB) to RAM…

Sending ‘dtbo_a’ (24576 KB) OKAY [ 0.622s]

Writing ‘dtbo_a’ OKAY [ 0.094s]

extracting super_empty.img (0 MB) to RAM…

extracting vendor_boot.img (96 MB) to disk… took 0.182s

archive does not contain ‘vendor_boot.sig’

extracting super_empty.img (0 MB) to RAM…

Sending ‘vendor_boot_a’ (98304 KB) OKAY [ 2.484s]

Writing ‘vendor_boot_a’ OKAY [ 0.379s]

extracting super_empty.img (0 MB) to RAM…

extracting vbmeta.img (0 MB) to disk… took 0.000s

archive does not contain ‘vbmeta.sig’

extracting super_empty.img (0 MB) to RAM…

Sending ‘vbmeta_a’ (8 KB) OKAY [ 0.001s]

Writing ‘vbmeta_a’ OKAY [ 0.010s]

extracting super_empty.img (0 MB) to RAM…

extracting vbmeta_system.img (0 MB) to disk… took 0.000s

archive does not contain ‘vbmeta_system.sig’

extracting super_empty.img (0 MB) to RAM…

Sending ‘vbmeta_system_a’ (4 KB) OKAY [ 0.001s]

Writing ‘vbmeta_system_a’ OKAY [ 0.011s]

Rebooting into fastboot OKAY [ 0.000s]

< waiting for any device >

extracting super_empty.img (0 MB) to disk… took 0.000s

Sending ‘super’ (4 KB) OKAY [ 0.001s]

Updating super partition OKAY [ 0.028s]

Resizing ‘system_a’ OKAY [ 0.005s]

Resizing ‘system_ext_a’ OKAY [ 0.005s]

Resizing ‘product_a’ OKAY [ 0.005s]

Resizing ‘vendor_a’ OKAY [ 0.005s]

extracting super_empty.img (0 MB) to RAM…

extracting system.img (966 MB) to disk… took 2.421s

archive does not contain ‘system.sig’

Resizing ‘system_a’ OKAY [ 0.006s]

Invalid sparse file format at header magic

Sending sparse ‘system_a’ 1/4 (262100 KB) OKAY [ 6.879s]

Writing ‘system_a’ OKAY [ 0.693s]

Sending sparse ‘system_a’ 2/4 (262044 KB) OKAY [ 6.855s]

Writing ‘system_a’ OKAY [ 0.704s]

Sending sparse ‘system_a’ 3/4 (261940 KB) OKAY [ 6.809s]

Writing ‘system_a’ OKAY [ 0.669s]

Sending sparse ‘system_a’ 4/4 (199428 KB) OKAY [ 5.182s]

Writing ‘system_a’ OKAY [ 0.565s]

extracting super_empty.img (0 MB) to RAM…

extracting system_ext.img (526 MB) to disk… took 1.418s

archive does not contain ‘system_ext.sig’

Resizing ‘system_ext_a’ OKAY [ 0.005s]

Invalid sparse file format at header magic

Sending sparse ‘system_ext_a’ 1/3 (262028 KB) OKAY [ 6.797s]

Writing ‘system_ext_a’ OKAY [ 0.748s]

Sending sparse ‘system_ext_a’ 2/3 (243224 KB) OKAY [ 6.364s]

Writing ‘system_ext_a’ OKAY [ 0.625s]

Sending sparse ‘system_ext_a’ 3/3 (31788 KB) OKAY [ 0.821s]

Writing ‘system_ext_a’ OKAY [ 0.135s]

extracting super_empty.img (0 MB) to RAM…

extracting product.img (1187 MB) to disk… took 4.152s

archive does not contain ‘product.sig’

Resizing ‘product_a’ OKAY [ 0.006s]

Invalid sparse file format at header magic

Sending sparse ‘product_a’ 1/5 (261956 KB) OKAY [ 6.865s]

Writing ‘product_a’ OKAY [ 0.670s]

Sending sparse ‘product_a’ 2/5 (261980 KB) OKAY [ 6.857s]

Writing ‘product_a’ OKAY [ 0.715s]

Sending sparse ‘product_a’ 3/5 (262104 KB) OKAY [ 6.833s]

Writing ‘product_a’ OKAY [ 0.697s]

Sending sparse ‘product_a’ 4/5 (261713 KB) OKAY [ 6.797s]

Writing ‘product_a’ OKAY [ 0.715s]

Sending sparse ‘product_a’ 5/5 (163152 KB) OKAY [ 4.252s]

Writing ‘product_a’ OKAY [ 0.431s]

extracting super_empty.img (0 MB) to RAM…

extracting vendor.img (502 MB) to disk… took 1.365s

archive does not contain ‘vendor.sig’

Resizing ‘vendor_a’ OKAY [ 0.006s]

Invalid sparse file format at header magic

Sending sparse ‘vendor_a’ 1/2 (261837 KB) OKAY [ 6.871s]

Writing ‘vendor_a’ OKAY [ 0.669s]

Sending sparse ‘vendor_a’ 2/2 (250424 KB) OKAY [ 6.553s]

Writing ‘vendor_a’ OKAY [ 0.680s]

Finished. Total time: 135.754s

Erasing ‘userdata’ OKAY [ 0.042s]

Finished. Total time: 0.051s

is-userspace: yes

Sending ‘abl_a’ (332 KB) OKAY [ 0.009s]

Writing ‘abl_a’ OKAY [ 0.005s]

Finished. Total time: 0.037s

Warning: skip copying bluetooth_a image avb footer due to sparse image.

Sending ‘bluetooth_a’ (792 KB) OKAY [ 0.022s]

Writing ‘bluetooth_a’ OKAY [ 0.007s]

Finished. Total time: 0.042s

Sending ‘devcfg_a’ (123 KB) OKAY [ 0.004s]

Writing ‘devcfg_a’ OKAY [ 0.006s]

Finished. Total time: 0.036s

Sending ‘dsp_a’ (32768 KB) OKAY [ 0.860s]

Writing ‘dsp_a’ OKAY [ 0.079s]

Finished. Total time: 0.987s

Warning: skip copying fsg image avb footer (fsg partition size: 0, fsg image size: 18472960).

Sending ‘fsg’ (18040 KB) OKAY [ 0.482s]

Writing ‘fsg’ FAILED (remote: ‘No such file or directory’)

fastboot: error: Command failed

Sending ‘hyp_a’ (507 KB) OKAY [ 0.014s]

Writing ‘hyp_a’ OKAY [ 0.014s]

Finished. Total time: 0.047s

Sending ‘keymaster_a’ (507 KB) OKAY [ 0.014s]

Writing ‘keymaster_a’ OKAY [ 0.011s]

Finished. Total time: 0.043s

Sending ‘logo_a’ (10544 KB) OKAY [ 0.278s]

Writing ‘logo_a’ OKAY [ 0.036s]

Finished. Total time: 0.343s

Sending ‘prov_a’ (251 KB) OKAY [ 0.007s]

Writing ‘prov_a’ OKAY [ 0.007s]

Finished. Total time: 0.033s

Sending ‘qupfw_a’ (75 KB) OKAY [ 0.002s]

Writing ‘qupfw_a’ OKAY [ 0.005s]

Finished. Total time: 0.025s

Sending ‘rpm_a’ (507 KB) OKAY [ 0.014s]

Writing ‘rpm_a’ OKAY [ 0.008s]

Finished. Total time: 0.041s

Sending ‘storsec_a’ (123 KB) OKAY [ 0.004s]

Writing ‘storsec_a’ OKAY [ 0.006s]

Finished. Total time: 0.027s

Sending ‘tz_a’ (4091 KB) OKAY [ 0.110s]

Writing ‘tz_a’ OKAY [ 0.028s]

Finished. Total time: 0.171s

Sending ‘uefisecapp_a’ (2043 KB) OKAY [ 0.058s]

Writing ‘uefisecapp_a’ OKAY [ 0.025s]

Finished. Total time: 0.105s

Sending ‘xbl_config_a’ (251 KB) OKAY [ 0.007s]

Writing ‘xbl_config_a’ OKAY [ 0.011s]

Finished. Total time: 0.036s

Sending ‘xbl_a’ (5115 KB) OKAY [ 0.139s]

Writing ‘xbl_a’ OKAY [ 0.070s]

Finished. Total time: 0.239s

Rebooting into bootloader OKAY [ 0.000s]

Finished. Total time: 0.000s

< waiting for any device >

FAILED (remote: ‘’)

fastboot: error: Command failed

Press any key to exit…

maxito · September 22, 2026, 11:24am

If you are completely new to this and never done any mobile flashing.

See this video:

rik · September 22, 2026, 5:22pm

I see you marked it as the “solution” does that mean that you now succeeded? If so can you give a very brief explanation of what step(s) solved the problem you faced?

maxito · September 26, 2026, 6:32am

Hi,

Find here a summary of the problem/solution.

Problem:

I run the installer on Windows 11 on a Moto G32. It failed as per log details shown above post 1 on Sep 20. The phone was left in Fastboot mode and locked. But Iode was not installed.

Solution:

Then I did a factory reset. Followed by unlocking the boot loader using the minimal adb fastboot windows software. When the phone was unlocked I restored the standard rom using the motorola Software fix program as per details Post #3 Sep 22, 6:12 PM.
Finally, with a working stock rom, I went and tried again the Iode installer from Windows 11 and it worked better than before, still showing an error in the log “Writing ‘userdata’ (bootloader) flash permission denied“ but the phone boots Iode and it works normally. See log in Post #4 Sep 22, 9:21 PM

I still did not have time to re-lock the bootloader. Will do that later.

rik · September 26, 2026, 7:38pm

Note that this will erase your userdata… effectively performing a “factory reset” so make sure you have your data backed up before doing this.

maxito · September 26, 2026, 11:12pm

Many thanks for your prompt response. I am new to this, could you elaborate on what is included in userdata that will be erased by re-locking? Is it data in the internal memory filesystem or it is also the apps I already installed, etc?

rik · September 28, 2026, 4:31pm

All apps, settings, data, everything! It will greet you as a brand new install after userdata is reset.

You can use “System Settings > System > Backup” to make a Seedvault backup of your apps, settings, and data and then restore after resetting (but some apps do not allow backups and restores, such as secure messaging apps, thunderbird, iodé browser, etc. so all important things you should have your own backups in addition for extra security to not lose important things).

maxito · October 6, 2026, 6:58am

Many thanks for the response.

I tried re-locking using ‘fastbook oem lock’ with NO success.

I followed these steps:

Enable developer options.
Enable USB Debugging
Enable OEM unlocking
Switch off phone, plug it to computer.
Press power/Volume down until I see the fastboot screen
go to the windows cmd.exe screen and type the lock command:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
…
(bootloader) Bootloader is now locked
OKAY [ 6.284s]
finished. total time: 6.284s

I can see the fastboot screen now shows “flashing_locked”. Then I power off the phone from the fastboot menu and unplug usb cable.

The issue is I still get the mobile error message “your device is loading a different operating system” OS Fingerprint 0xC4F18977 screen.

Does anyone know how to troubleshoot and fix this issue and get a clean boot without the above error message screen?

Many thanks in advance, I appreciate your help with this issue.

MissPiggy · October 6, 2026, 7:22am

This is not an issue, it is a feature! Your device is reporting that you are using a different OS - which is what you want. And you would want to know it if someone got hold of your device and did secretly install another system …

maxito · October 7, 2026, 6:18am

I thought the message would go away after relocking.

Would this message show in all devices even after they are relocked; for example, a Google Pixel?

MissPiggy · October 7, 2026, 6:45pm

Yes.