# Installation feedback **URL:** \ **Category:** Installation Help\ **Tags:** MotorolaG32\ **Created:** [15 April 2026 21:03 UTC](https://community.iode.tech/t/installation-feedback/8044 "2026-04-15T21:03:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![dsilva](https://community.iode.tech/user_avatar/community.iode.tech/dsilva/32/2527_2.png) [@dsilva](https://community.iode.tech/u/dsilva)\ **Post date:** [15 April 2026 21:03 UTC](https://community.iode.tech/t/installation-feedback/8044/1 "2026-04-15T21:03:52Z")
I’ve used the installer v0.3.0 on Linux to flash IodéOS 7.4-20260401 on my Moto G32 (devon). * * * As I’m coming from LineageOS, I came across the [“OEM unlocking” issue](https://community.iode.tech/t/is-it-possible-to-install-manually-on-moto-g32/5147), for which I’ve documented the workaround in [this comment](https://community.iode.tech/t/is-it-possible-to-install-manually-on-moto-g32/5147/9). Do you recommend always starting from the stock ROM to install Iodé? Because Lineage makes that requirement explicit in its installation docs. * * * If I don’t quickly respond to the bootloader lock prompt, installation ends with an error, even though the system was successfully installed (with an unlocked bootloader) at that point. > **Logs** > > ```auto > Setting current slot to 'a' OKAY [0.378s] > Finished. Total time: 0.378s > Erasing 'avb_custom_key' OKAY [0.015s] > Finished. Total time: 0.018s > 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.017s > 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: not exist /proc/version! > 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 > "6.19.11-200.fc43.x86_64" > [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.619s] > Writing 'modem_a' OKAY [0.344s] > Finished. Total time: 1.968s > -------------------------------------------- > Bootloader Version...: MBM-3.0-devon_g-8847829342a-250806 > Baseband Version.....: HAK11_15.154.01.90R DEVON_LATAMDSDS_CUST > Serial Number........: ZF523ZDDH7 > -------------------------------------------- > extracting android-info.txt (0 MB) to RAM... > Checking 'product' OKAY [0.000s] > Setting current slot to 'a' OKAY [0.228s] > 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.205s > archive does not contain 'boot.sig' > extracting super_empty.img (0 MB) to RAM... > Sending 'boot_a' (98304 KB) OKAY [2.063s] > Writing 'boot_a' OKAY [1.296s] > extracting super_empty.img (0 MB) to RAM... > extracting dtbo.img (24 MB) to disk... took 0.049s > archive does not contain 'dtbo.sig' > extracting super_empty.img (0 MB) to RAM... > Sending 'dtbo_a' (24576 KB) OKAY [0.515s] > Writing 'dtbo_a' OKAY [0.126s] > extracting super_empty.img (0 MB) to RAM... > extracting vendor_boot.img (96 MB) to disk... took 0.166s > archive does not contain 'vendor_boot.sig' > extracting super_empty.img (0 MB) to RAM... > Sending 'vendor_boot_a' (98304 KB) OKAY [2.052s] > Writing 'vendor_boot_a' OKAY [0.506s] > 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.008s] > 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.008s] > Rebooting into fastboot OKAY [0.001s] > < 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.035s] > Resizing 'system_a' OKAY [0.007s] > Resizing 'system_ext_a' OKAY [0.007s] > Resizing 'product_a' OKAY [0.007s] > Resizing 'vendor_a' OKAY [0.007s] > extracting super_empty.img (0 MB) to RAM... > extracting system.img (965 MB) to disk... took 2.856s > archive does not contain 'system.sig' > Resizing 'system_a' OKAY [0.007s] > Invalid sparse file format at header magic > Sending sparse 'system_a' 1/4 (262100 KB) OKAY [5.722s] > Writing 'system_a' OKAY [0.657s] > Sending sparse 'system_a' 2/4 (262048 KB) OKAY [5.703s] > Writing 'system_a' OKAY [0.667s] > Sending sparse 'system_a' 3/4 (261940 KB) OKAY [5.713s] > Writing 'system_a' OKAY [0.760s] > Sending sparse 'system_a' 4/4 (199356 KB) OKAY [4.358s] > Writing 'system_a' OKAY [0.678s] > extracting super_empty.img (0 MB) to RAM... > extracting system_ext.img (483 MB) to disk... took 1.490s > archive does not contain 'system_ext.sig' > Resizing 'system_ext_a' OKAY [0.006s] > Invalid sparse file format at header magic > Sending sparse 'system_ext_a' 1/2 (262028 KB) OKAY [5.719s] > Writing 'system_ext_a' OKAY [0.716s] > Sending sparse 'system_ext_a' 2/2 (231464 KB) OKAY [5.035s] > Writing 'system_ext_a' OKAY [0.631s] > extracting super_empty.img (0 MB) to RAM... > extracting product.img (1152 MB) to disk... took 3.751s > archive does not contain 'product.sig' > Resizing 'product_a' OKAY [0.007s] > Invalid sparse file format at header magic > Sending sparse 'product_a' 1/5 (261960 KB) OKAY [5.737s] > Writing 'product_a' OKAY [0.741s] > Sending sparse 'product_a' 2/5 (262044 KB) OKAY [5.739s] > Writing 'product_a' OKAY [0.708s] > Sending sparse 'product_a' 3/5 (262052 KB) OKAY [5.721s] > Writing 'product_a' OKAY [0.701s] > Sending sparse 'product_a' 4/5 (261845 KB) OKAY [5.713s] > Writing 'product_a' OKAY [0.762s] > Sending sparse 'product_a' 5/5 (127928 KB) OKAY [2.799s] > Writing 'product_a' OKAY [0.397s] > extracting super_empty.img (0 MB) to RAM... > extracting vendor.img (500 MB) to disk... took 1.484s > 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 (261841 KB) OKAY [5.722s] > Writing 'vendor_a' OKAY [0.771s] > Sending sparse 'vendor_a' 2/2 (247684 KB) OKAY [5.409s] > Writing 'vendor_a' OKAY [0.687s] > Finished. Total time: 121.314s > Erasing 'userdata' OKAY [5.027s] > Finished. Total time: 5.035s > Sending 'abl_a' (332 KB) OKAY [0.008s] > Writing 'abl_a' OKAY [0.006s] > Finished. Total time: 0.030s > Warning: skip copying bluetooth_a image avb footer due to sparse image. > Sending 'bluetooth_a' (792 KB) OKAY [0.020s] > Writing 'bluetooth_a' OKAY [0.008s] > Finished. Total time: 0.402s > Sending 'devcfg_a' (123 KB) OKAY [0.004s] > Writing 'devcfg_a' OKAY [0.006s] > Finished. Total time: 1.659s > Sending 'dsp_a' (32768 KB) OKAY [0.726s] > Writing 'dsp_a' OKAY [0.087s] > Finished. Total time: 0.881s > Warning: skip copying fsg image avb footer (fsg partition size: 0, fsg image size: 18472960). > Sending 'fsg' (18040 KB) OKAY [0.403s] > Writing 'fsg' FAILED (remote: 'No such file or directory') > fastboot: error: Command failed > Sending 'hyp_a' (507 KB) OKAY [0.012s] > Writing 'hyp_a' OKAY [0.012s] > Finished. Total time: 0.044s > Sending 'keymaster_a' (507 KB) OKAY [0.013s] > Writing 'keymaster_a' OKAY [0.008s] > Finished. Total time: 0.041s > Sending 'logo_a' (10544 KB) OKAY [0.236s] > Writing 'logo_a' OKAY [0.051s] > Finished. Total time: 0.337s > Sending 'prov_a' (251 KB) OKAY [0.007s] > Writing 'prov_a' OKAY [0.007s] > Finished. Total time: 0.031s > Sending 'qupfw_a' (75 KB) OKAY [0.002s] > Writing 'qupfw_a' OKAY [0.006s] > Finished. Total time: 0.024s > Sending 'rpm_a' (507 KB) OKAY [0.013s] > Writing 'rpm_a' OKAY [0.009s] > Finished. Total time: 0.038s > Sending 'storsec_a' (123 KB) OKAY [0.004s] > Writing 'storsec_a' OKAY [0.009s] > Finished. Total time: 0.029s > Sending 'tz_a' (4091 KB) OKAY [0.094s] > Writing 'tz_a' OKAY [0.021s] > Finished. Total time: 0.134s > Sending 'uefisecapp_a' (2043 KB) OKAY [0.053s] > Writing 'uefisecapp_a' OKAY [0.018s] > Finished. Total time: 0.096s > Sending 'xbl_config_a' (251 KB) OKAY [0.007s] > Writing 'xbl_config_a' OKAY [0.018s] > Finished. Total time: 0.044s > Sending 'xbl_a' (5115 KB) OKAY [0.120s] > Writing 'xbl_a' OKAY [0.054s] > Finished. Total time: 0.193s > Rebooting into bootloader OKAY [0.000s] > Finished. Total time: 0.050s > < waiting for any device > > FAILED (remote: '') > fastboot: error: Command failed > > ``` * * * A question about the Iodé (network blocking) app: does it impact system performance in any noticeable way? For instance, I’ve noticed some extreme stutters and freezes while downloading a few torrents with LibreTorrent, which didn’t ever happen on LineageOS. I’m disabling blocking while torrenting for now on. * * * IodéOS is also affected by this [LineageOS issue](https://gitlab.com/LineageOS/issues/android/-/work_items/9896), which makes recent apps constantly have to reload and lose their state while multitasking, and eventually leading to a system reboot. A few other Motorola users have confirmed it, but the maintainers haven’t replied yet. An Iodé devon user [reported no such issues](https://community.iode.tech/t/iodeos-7-4-released/7990/4), though. If you’re a devon user, please leave your feedback. My guess is that this is the work of an overly aggressive out-of-memory killer that closes any apps that haven’t been focused for a minute or more. It only starts happening after some uptime and moderate multitasking — never in the first few hours following a reboot. RAM usage reported by the system show a decent amount of free memory. All I know is that the last version of CalyxOS (based on Android 15) is unaffected, because I’ve used it for almost a year, running the same apps I do now. So far, every Android 16 build I’ve tried has this issue. ---
**Author:** ![petefoth](https://community.iode.tech/letter_avatar_proxy/v4/letter/p/2acd7d/32.png) [@petefoth](https://community.iode.tech/u/petefoth)\ **Post date:** [16 April 2026 17:45 UTC](https://community.iode.tech/t/installation-feedback/8044/2 "2026-04-16T17:45:04Z")
> [@dsilva](#): > > Do you recommend always starting from the stock ROM to install Iodé? Because Lineage makes that requirement explicit in its installation docs. They say that because they don’t want to provide any support for users installing LineageOS over some random custom ROM. In practice, I have switched installations between LineageOS, LineageOS for microG, /e/OS, and iodéOS - in both directions - with no problems, art from having to factory reset and lose user-installed apps and data. I would recommend trying to flash IodéOS over whatever ROM is currently installed on your device, but be prepared to return to the stock ROM if you hit any nasty problems. ---
**Author:** ![rik](https://community.iode.tech/user_avatar/community.iode.tech/rik/32/1437_2.png) [@rik](https://community.iode.tech/u/rik)\ **Post date:** [16 April 2026 18:29 UTC](https://community.iode.tech/t/installation-feedback/8044/3 "2026-04-16T18:29:07Z")
> [@dsilva](#): > > …which makes recent apps constantly have to reload and lose their state while multitasking, and eventually leading to a system reboot. A few other Motorola users have confirmed it, but the maintainers haven’t replied yet. An Iodé devon user [reported no such issues](https://community.iode.tech/t/iodeos-7-4-released/7990/4), though. If you’re a devon user, please leave your feedback. @devonuser are you running iodéOS 7.x? If so can you comment on this? @MissPiggy seems happy, and I think there are other `devon` users that don’t have the issue? ---
**Author:** ![MissPiggy](https://community.iode.tech/user_avatar/community.iode.tech/misspiggy/32/2158_2.png) [@MissPiggy](https://community.iode.tech/u/MissPiggy)\ **Post date:** [16 April 2026 21:36 UTC](https://community.iode.tech/t/installation-feedback/8044/4 "2026-04-16T21:36:59Z")
> [@petefoth](#): > > In practice, I have switched installations between LineageOS, LineageOS for microG, /e/OS, and iodéOS - in both directions - with no problems I went from CalyxOS directly to iodéOS with my G32, too, without any show stopper. ---
**Author:** ![devonuser](https://community.iode.tech/user_avatar/community.iode.tech/devonuser/32/2557_2.png) [@devonuser](https://community.iode.tech/u/devonuser)\ **Post date:** [17 April 2026 17:42 UTC](https://community.iode.tech/t/installation-feedback/8044/5 "2026-04-17T17:42:11Z")
Yeah sure, it is anti-rollback or verified boot issue or something. My advice is if you come from CalyxOS try install first LineageOS then from LineageOS to iodeOS works for me. And regarding Regression Issue no I haven’t encounter the bug ---
**Author:** ![dsilva](https://community.iode.tech/user_avatar/community.iode.tech/dsilva/32/2527_2.png) [@dsilva](https://community.iode.tech/u/dsilva)\ **Post date:** [23 April 2026 13:23 UTC](https://community.iode.tech/t/installation-feedback/8044/6 "2026-04-23T13:23:51Z")
Thanks for replying! I’m now running the stock ROM (Android 13), and it doesn’t have the issues I described, which I think rules out hardware failure. It’s got the very same apps, except microG, DAVx5 and all the other default LineageOS and Iodé apps. * * * By the way, this is what I see when I don’t interact with the phone in time to respond to the bootloader lock prompt. See screenshot below. > If I don’t quickly respond to the bootloader lock prompt, installation ends with an error, even though the system was successfully installed (with an unlocked bootloader) at that point. ![Screenshot_20260414_100153](https://community.iode.tech/uploads/default/original/2X/f/ff9e45897f57ad975e11536c5f9eb161110148bd.png) Maybe the installer could say that “installation has finished, but the bootloader was not locked”. ---
**Author:** ![rik](https://community.iode.tech/user_avatar/community.iode.tech/rik/32/1437_2.png) [@rik](https://community.iode.tech/u/rik)\ **Post date:** [23 April 2026 15:28 UTC](https://community.iode.tech/t/installation-feedback/8044/7 "2026-04-23T15:28:21Z")
> [@dsilva](#): > > Maybe the installer could say that “installation has finished, but the bootloader was not locked”. Well explained, I created this issue: > **[Installer: don't give "failed" message if not relocked (#82) · Issues · ota /...](https://gitlab.iode.tech/ota/issue-tracker/-/work_items/82)** > > Using the installer, if the user doesn't interact with the device when the relock command is sent to the device and it then times out, they get a... ---
**Author:** ![dsilva](https://community.iode.tech/user_avatar/community.iode.tech/dsilva/32/2527_2.png) [@dsilva](https://community.iode.tech/u/dsilva)\ **Post date:** [27 May 2026 16:46 UTC](https://community.iode.tech/t/installation-feedback/8044/8 "2026-05-27T16:46:02Z")
Hey. Just to let you know, the [performance issue](https://gitlab.com/LineageOS/issues/android/-/work_items/10191) I had was [fixed and merged](https://review.lineageos.org/c/LineageOS/android_kernel_motorola_sm6225/+/486862) into LineageOS today. Commit message is “Disable CONFIG\_LRU\_GEN”. 🥹 ---
**Author:** ![MissPiggy](https://community.iode.tech/user_avatar/community.iode.tech/misspiggy/32/2158_2.png) [@MissPiggy](https://community.iode.tech/u/MissPiggy)\ **Post date:** [28 May 2026 16:09 UTC](https://community.iode.tech/t/installation-feedback/8044/9 "2026-05-28T16:09:17Z")
Thanks for reporting back!