Cannot install iode on Motorola G52 (rhode)

Installation Help
1

Hello,

I’m struggling to install iode on a Motorola G52 phone. The phone had Calyx OS previously but I decided to replace it with iode. I tried running the GUI installer on Windows but it kept failing. I managed to reach the screen on the phone where I choose whether to lock the bootloader. I chose to not lock it (as I assumed iode allows for both locked and unlocked bl on this phone) and I got an “Installation aborted” screen. I then tried with the .bat script and got exactly the same result.

At the end the phone is in the bootloader screen and doesn’t feel bricked (fastboot in Powershell does detect it) but I did not try to reboot it to system to avoid problems.

I have scoured the internet for solutions and did following things (which did not work):

  • update adb drivers and usb drivers of my computer
  • update adb itself
  • try different usb socket
  • change usb cable
  • run installer/command line as administrator
  • try windows 10 and 11
  • try on Linux - this actually also failed but with a different result (which I also paste below).

Final lines of the log from Windows:

	Warning: skip copying fsg image avb footer (fsg partition size: 0, fsg image size: 16801792).
	Sending 'fsg' (16408 KB)                           OKAY [  0.379s]
	Writing 'fsg'                                      FAILED (remote: 'No such file or directory')
	fastboot: error: Command failed
	Sending 'hyp_b' (507 KB)                           OKAY [  0.012s]
	Writing 'hyp_b'                                    OKAY [  0.012s]
	Finished. Total time: 0.042s
	Sending 'keymaster_b' (507 KB)                     OKAY [  0.013s]
	Writing 'keymaster_b'                              OKAY [  0.008s]
	Finished. Total time: 0.039s
	Sending 'logo_b' (10544 KB)                        OKAY [  0.240s]
	Writing 'logo_b'                                   OKAY [  0.032s]
	Finished. Total time: 0.305s
	Sending 'prov_b' (251 KB)                          OKAY [  0.007s]
	Writing 'prov_b'                                   OKAY [  0.007s]
	Finished. Total time: 0.031s
	Sending 'qupfw_b' (75 KB)                          OKAY [  0.002s]
	Writing 'qupfw_b'                                  OKAY [  0.006s]
	Finished. Total time: 0.026s
	Sending 'rpm_b' (507 KB)                           OKAY [  0.013s]
	Writing 'rpm_b'                                    OKAY [  0.008s]
	Finished. Total time: 0.041s
	Sending 'storsec_b' (123 KB)                       OKAY [  0.004s]
	Writing 'storsec_b'                                OKAY [  0.006s]
	Finished. Total time: 0.028s
	Sending 'tz_b' (4091 KB)                           OKAY [  0.095s]
	Writing 'tz_b'                                     OKAY [  0.023s]
	Finished. Total time: 0.143s
	Sending 'uefisecapp_b' (2043 KB)                   OKAY [  0.054s]
	Writing 'uefisecapp_b'                             OKAY [  0.017s]
	Finished. Total time: 0.092s
	Sending 'xbl_config_b' (251 KB)                    OKAY [  0.007s]
	Writing 'xbl_config_b'                             OKAY [  0.014s]
	Finished. Total time: 0.038s
	Sending 'xbl_b' (5115 KB)                          OKAY [  0.122s]
	Writing 'xbl_b'                                    OKAY [  0.051s]
	Finished. Total time: 0.197s
	Rebooting into bootloader                          OKAY [  0.000s]
	Finished. Total time: 0.001s
	FAILED (remote: '')
	fastboot: error: Command failed
	Press any key to exit...

Final lines of the log from Linux:

Sending 'storsec_b' (123 KB)                       OKAY [  0.004s]
	Writing 'storsec_b'                                OKAY [  0.006s]
	Finished. Total time: 0.028s
	Sending 'tz_b' (4091 KB)                           OKAY [  0.095s]
	Writing 'tz_b'                                     OKAY [  0.023s]
	Finished. Total time: 0.143s
	Sending 'uefisecapp_b' (2043 KB)                   OKAY [  0.054s]
	Writing 'uefisecapp_b'                             OKAY [  0.017s]
	Finished. Total time: 0.092s
	Sending 'xbl_config_b' (251 KB)                    OKAY [  0.007s]
	Writing 'xbl_config_b'                             OKAY [  0.014s]
	Finished. Total time: 0.038s
	Sending 'xbl_b' (5115 KB)                          OKAY [  0.122s]
	Writing 'xbl_b'                                    OKAY [  0.051s]
	Finished. Total time: 0.199s
	Rebooting into bootloader                          OKAY [  0.000s]
	Finished. Total time: 0.051s
	FAILED (Status read failed (No such device))

Do you have any tips how to install without these errors?

2

If you were direct installing over Calyx, it may be that a return to stock would be needed first. You do not need to login to google, or even activate wifi, etc. but there are occasional issues when not starting from stock.

3

I changed from CalyxOS zu iodéOS four weeks ago. (Motorola G32)

Did not need any adb stuff.
BUT: CalyxOS automatically relocks the bootloader after the installation. Therefore, you will first need to unlock it (again).

If you run Installation - iodé the installer (download, unzip), you will need to activate USB-Debugging. The unlock code is still the same like in the mail obtained from Motorola back when you flashed CalyxOS in the first place. Click on “unlock”, then confirm unlocking the bootloader on your Motorola (by toggling with the volume button and confirming with start button).

You should now see a picture of a little space shuttle and below
“flashing unlocked” on your Motorola. Flashing starts and you should resist to do anything on the smartphone!
(reboot system now or reboot to bootloader - keep your hands off it)

Only when your Motorola asks whether you want to lock the bootloader, you can confirm to lock it. The installation will be complete by this time.
BTW: I did all this on Win 10 pro.

4

Thank you for the reply! I tried to do what you suggested - I successfully reverted to stock Android with use of the Motorola/Lenovo repair program and then didn’t set it up beyond getting to the settings to enable USB debugging (skipped wifi, login, pin etc). The bootloader was already unlocked. Iode installer did recognize the phone and ran the procedure but the result was identical - the phone displayed the bootloader lock choice prompt, I chose not locking and the log said fastboot error: Command failed. Then I tried again: ran the installer but this time I chose to lock the bootloader. Installer exited without errors, phone booted to iode start screen. I’m not sure if the revert to stock was important or the bootloader choice - is it expected to fail when bootloader isn’t locked at the end?

1 Like
5

Also the installer didn’t close despite what it says in the log.

obraz
obraz1901×985 48.4 KB

6

No, it should not error to not lock the bootloader, that is strange. The messages seem to me like ones I got when trying with a USB C-C cable that I don’t know why there was the problem, but that were solved by using a USB C-A cable, so not certain if maybe there was some level of issue with cable, PC port, Phone port, etc. that could be acting up?

If you unlock (you should be able to do this after allowing in Developer Options, then using fastboot flashing unlock) it should be possible, but any change from lock to unlock or vice versa will wipe your userdata partition so you will have to setup your data and apps, etc. again.