I’m trying to flash iode 7.4 into Moto G32. All good, is just that now I have this message and no further progress.
[…]
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 >
On my phone i have the fastboot interface with 4 options: Reboot system now, Enter Recovery, Reboot to bootloader and Power off.
How should I move one? I don’t want to take any action that could damage my phone as this is also explicitly mentioned in the auto-installer of Iode, to not unplug, power off etc.
It looks like the installer can’t “see” your phone in fastboot-mode. My guess would be a missing driver. You can check that in the device manager (on windows). Devices with issues are flagged there.
I think the installer wants to relock the bootloader at this point, which is optional BUT it means it is less secure and if you decide relock it later, it might wipe your personal data. But it should boot into iodeOS without problems at this point.
Okay, I checked the installer-script, installation isn’t done at this point. It tries to flash more partitions at this point but it really seems like it can’t see the phone after the first reboot.
Can you open another terminal/cmd window and execute fastboot devices from within the windows folder from iode’s ZIP (with the fastboot-exe in it)? If nothing is shown, the PC doesn’t “see” the phone in fastboot mode.
The weird thing is, initially the device is recognized in fastboot mode and fastboot-commands run fine. but after the first reboot it suddenly doesn’t get recognized. That doesn’t make sense really, since if you restart the script, it gets recognized.
If you have the option to try it on linux, I would do so, maybe it works there right away, saving you some time
I did a bit of digging and it seems like it is rebooting into a different kind of fastboot-mode, when your script gets stuck. There is a chance it uses a different driver for this mode. So can you double check in the device manager if the device is working properly when the script gets stuck!?
Windows is often getting “stuck” at this same place in fastbootD not detecting the device. Users report it works after they get various device manager updates / USB drivers updated. But there are still several that complain. I don’t use Windows but do have a spare laptop with a W10 install for various tests that I need to dust off to see if I can recreate the issues.
Hello everyone. I had intended to share some feedback on my installation process, but then I came across this discussion and decided to post here instead.
Disclaimer: I’m a bit limited in these matters as this journey began a few weeks ago.
Well, during my first attempts to use the Windows installer, the process kept crashing and the output was always the same – ‘waiting for any device’. After a few failed attempts, some frustration and a bit of luck, I found this video, followed the same steps, and the installation started straight away without crashing, then phone booted successfully into iodeOS. Maybe the problem is due to the motorola official driver first interaction with Windows. My computer setup is Windows 10 LTSC IoT on a 2013 macbook air.
If anyone else experiences a similar problem, perhaps they can resolve it this way, I hope.
I think the installer wants to relock the bootloader at this point, which is optional BUT it means it is less secure and if you decide relock it later, it might wipe your personal data. But it should boot into iodeOS without problems at this point.
