Installation on G52 failed, twice

Installation Help
1

Hello,
new to IodeOS.
Flashed some phones in the past, LineageOS and Calyx. Calyx on G52, three phones, flawless.

Last week I got a used G52, updated, unlocked and tried with Linux to install: failed.
Unable to go back to stock rom, the phone boots and reboots and reboots endlessly…

Today I got another used G52, this time I tried Windows10 installer. Same problem and same behaviour.

I find a couple of these msg during the installation process:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Also I see:
Writing ‘userdata’ (bootloader) flash permission denied
FAILED (remote: ‘’)
fastboot: error: Command failed
Warning: skip copying modem_a image avb footer due to sparse image.

Looks as if the installer cannot write. I am not able to interpret these msgs, I am just a user.

For Windows I tried two different computers (both W10) and different cables, one new out of the box.
Should be good cable quality.

When the phone gets rebooted it does not get back into fastboot but goes in adb menu as far as I can tell - from here I go to reboot into fastboot manually and when the fastboot comes up installation continues.
Don’t know if this should be like this, when flashing CalyxOS the reboot goes back into fastboot, never seen the adb menu before.

Iodeos installer on windows tried to install latest 6.6.

Any other ideas, what else can I try?
Thanks a lot for your help.
Kind regards, panmeri

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.026s
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: 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: 714] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 748] Filling nat area at offset 0x01200000
[f2fs_add_default_dentry_root:1364] Writing default dentry root, at offset 0x1d800
[f2fs_write_root_inode:1410] Writing root inode (hot node), offset 0x1d200
[f2fs_write_default_quota:1502] Writing quota data, at offset 0001d801 (1/2)
[f2fs_write_default_quota:1502] Writing quota data, at offset 0001d802 (2/2)
[f2fs_write_qf_inode:1553] Writing quota inode (hot node), offset 0x1d201
[f2fs_write_default_quota:1502] Writing quota data, at offset 0001d803 (1/2)
[f2fs_write_default_quota:1502] Writing quota data, at offset 0001d804 (2/2)
[f2fs_write_qf_inode:1553] Writing quota inode (hot node), offset 0x1d202
[f2fs_write_default_quota:1502] Writing quota data, at offset 0001d805 (1/2)
[f2fs_write_default_quota:1502] Writing quota data, at offset 0001d806 (2/2)
[f2fs_write_qf_inode:1553] Writing quota inode (hot node), offset 0x1d203
[f2fs_update_nat_default:1591] Writing nat root, at offset 0x00001200
Info: Overprovision ratio = 0.430%
Info: Overprovision segments = 246 (GC reserved = 239)
[f2fs_write_check_point_pack: 939] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack:1027] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1041] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1053] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1067] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1075] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1095] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1117] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1136] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1169] Writing super block, at offset 0x00000000
Info: format successful
Warning: skip copying userdata image avb footer due to sparse image.
Sending ‘userdata’ (97 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’ (77196 KB) OKAY [ 1.789s]
Writing ‘modem_a’ OKAY [ 0.314s]
Finished. Total time: 2.114s

Bootloader Version…: MBM-3.0-rhode_g-8847829342a-250320
Baseband Version…: HA11_15.154.01.89R RHODE_EUAPEMDSDS_CUST
Serial Number…: ZY22FP6WLC

extracting android-info.txt (0 MB) to RAM…
Checking ‘product’ OKAY [ 0.000s]
Setting current slot to ‘a’ OKAY [ 0.179s]
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.250s
archive does not contain ‘boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘boot_a’ (98304 KB) OKAY [ 2.266s]
Writing ‘boot_a’ OKAY [ 1.157s]
extracting super_empty.img (0 MB) to RAM…
extracting dtbo.img (24 MB) to disk… took 0.054s
archive does not contain ‘dtbo.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘dtbo_a’ (24576 KB) OKAY [ 0.567s]
Writing ‘dtbo_a’ OKAY [ 0.109s]
extracting super_empty.img (0 MB) to RAM…
extracting vendor_boot.img (96 MB) to disk… took 0.214s
archive does not contain ‘vendor_boot.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vendor_boot_a’ (98304 KB) OKAY [ 2.266s]
Writing ‘vendor_boot_a’ OKAY [ 0.404s]
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.007s]
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.007s]
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.369s]
Finished. Total time: 0.370s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending ‘abl_a’ (332 KB) OKAY [ 0.009s]
Writing ‘abl_a’ OKAY [ 0.009s]
Finished. Total time: 0.030s
Warning: skip copying bluetooth_a image avb footer due to sparse image.
Sending ‘bluetooth_a’ (792 KB) OKAY [ 0.019s]
Writing ‘bluetooth_a’ OKAY [ 0.016s]
Finished. Total time: 0.047s
Sending ‘devcfg_a’ (123 KB) OKAY [ 0.004s]
Writing ‘devcfg_a’ OKAY [ 0.006s]
Finished. Total time: 0.021s
Sending ‘dsp_a’ (32768 KB) OKAY [ 0.758s]
Writing ‘dsp_a’ OKAY [ 0.121s]
Finished. Total time: 0.919s
Sending ‘fsg_a’ (16408 KB) OKAY [ 0.382s]
Writing ‘fsg_a’ OKAY [ 0.090s]
Finished. Total time: 0.497s
Sending ‘hyp_a’ (507 KB) OKAY [ 0.013s]
Writing ‘hyp_a’ OKAY [ 0.012s]
Finished. Total time: 0.037s
Sending ‘keymaster_a’ (507 KB) OKAY [ 0.013s]
Writing ‘keymaster_a’ OKAY [ 0.011s]
Finished. Total time: 0.038s
Sending ‘logo_a’ (10544 KB) OKAY [ 0.244s]
Writing ‘logo_a’ OKAY [ 0.041s]
Finished. Total time: 0.305s
Sending ‘prov_a’ (251 KB) OKAY [ 0.007s]
Writing ‘prov_a’ OKAY [ 0.007s]
Finished. Total time: 0.025s
Sending ‘qupfw_a’ (75 KB) OKAY [ 0.003s]
Writing ‘qupfw_a’ OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending ‘rpm_a’ (507 KB) OKAY [ 0.013s]
Writing ‘rpm_a’ OKAY [ 0.012s]
Finished. Total time: 0.037s
Sending ‘storsec_a’ (123 KB) OKAY [ 0.004s]
Writing ‘storsec_a’ OKAY [ 0.005s]
Finished. Total time: 0.019s
Sending ‘tz_a’ (4091 KB) OKAY [ 0.097s]
Writing ‘tz_a’ OKAY [ 0.021s]
Finished. Total time: 0.138s
Sending ‘uefisecapp_a’ (2043 KB) OKAY [ 0.052s]
Writing ‘uefisecapp_a’ OKAY [ 0.013s]
Finished. Total time: 0.078s
Sending ‘xbl_config_a’ (251 KB) OKAY [ 0.007s]
Writing ‘xbl_config_a’ OKAY [ 0.022s]
Finished. Total time: 0.039s
Sending ‘xbl_a’ (5115 KB) OKAY [ 0.122s]
Writing ‘xbl_a’ OKAY [ 0.022s]
Finished. Total time: 0.165s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
(bootloader) Bootloader is now locked

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

2

It is trying to get to fastbootd, which isn’t the same as good old fastboot. If Linux is your preference, can you try again with the iodéOS installer there, not using a usbc-c cable, but a usbc-a cable? Maybe this was the case before for you, but for me that is where it has trouble automatically getting to fastbootd is when I am using a usbc-c cable.

3

Hi rik,
thank you for the feedback.
I read something about this cable trick, a-c and not c-c. But in my case I use a-c cable.

By the way, I used command line or better the shell script, as I didn’t understand how to start the installer (which has a GUI I suppose?)

4

What about the fastbootd - fastboot?
Does my phone/phones in general nowadays have fastbootd in addition to fastboot?

So “old” fastboot is the menu with the android mascot at the bottom and fastbootd the menu top of screen?

So what happens after the phone gets into fastbootd - if that was the case, just sit and wait …? Because it didn’t look to be doing anything and as I did bot see that menu before I thought that was wrong.

So is the phone supposed to boot into fastboot mascot or into fastbootd? I do not understand this… sorry

5

I may need to defer to some others more knowledgeable to explain, but yes the phone has both. I have noticed when using the graphical installer it does the bulk of the flashing in fastbootd. (Note for Linux the GUI should already be executable but you can launch from a terminal to ensure it is starting).

You can also see this when you start fastboot from within recovery it will clearly say fastbootd at the top. If you use the flash-all.sh or flash-all.bat it will do the install but I forget what fastboot will show on the phone. But I do know I have only been successful in flashing if I use the flash-all.sh or the graphical installer. I need to look into this more.

6

I will give it another try, hopefully the phone(s) aren’t bricked already.
Thanks

So the installer does not run on my Debian 12 installation.

./iodeOS-installer: symbol lookup error: ./iodeOS-installer: undefined symbol: g_once_init_enter_pointer

… and I don’t know what’s that about …

7

So I see the device on usb hooked up (lsusb) but fastboot / adb will not detect it.
Looks like I cannot unlock it to re-flash.
Bricked?

8

Tried RSDLite to get back to stock rom …
The device is on usb, but RSDLite does not see it (Windows).
Also tried Lenovo Software Fix - says that the firmware is not correct (that’s correct, ahem, shouldn’t that be the idea of FIXing things? :wink:

The bootloader is flashing_locked - so I guess end of story.

9

? I am confused why fastboot doesn’t detect it ? This happened after attempting to manually get it into fastboot when the installer or script was just stuck “waiting for fastboot” or whatever?

I don’t know what to say about your Debian 12 issue with the installer, but if you do have that Windows machine sitting around, could you try the iodé installer on it again?

10

Which Moto stock firmware did you update to?

Perhaps you fell victim to anti-rollback protection

11

Hi, thanks for the comment.
I guess I can see fw on the fastboot screen? Have to check that.
As for the note the G52 is not listed…

The first G52 I tried has received Moto updates, before I tried installing IodeOS.
With the second I did not do any updates, although as far as I recall it suggested some.

In essence might not be my case … or maybe yes, but not detected yet.

Thanks

12

Try out different versions of platform-tools ADB Fastboot

Avoid version 36.0.0 (Apr 2025); older versions from 35.0.2, 34.04 to 31.0.3 are preferable.

1 Like
13

Pardon me, but this information is not very precise. iode-6.6-20250729-rhode is based on firmware version 13_T2SR33.72-22-4-13

I’ve skipped all Moto 5.2025 updates so far and was able to install all iodéOS ROMs, e.g Moto G84 (bangkk)

14

Hi,
Yes, I beg you pardon, I just don’t know much about where ro look at or what to report. Thank you for your patience.

What I see from the recovery log is
13/T2SR33.72-22-4-13
That’s the G52 phone I tried yesterday.

Thanks

15

Good news, guys.
I used the windows installer again as rik suggested.
The installer got the phone unlocked and started the installation.
In my humble opinion, the collaboration between installer and device has something to improve, as when finishing it does not tell the user to lock again - it’s something the user decides. And after locking the installer although saying Finished still has the spinning wheel running and the msg on top to not kill the app or disconnect the phone.

But besides that, I did the installation two times in a row, as first time I saw some err msg go by.
Second run was different, I saw many things happen amd looked overall less error msg.
In the end IodeOS started after locking.

So, in the end, looks good.

1 Like