I already have a Pixel 6 with iodé.
I had instaled it manually.
Today I tried to install iodé with the official Iodé installer for a pixel 7a.
The installer was stuck during the installation and now the pixel 7a seems to be bricked :
It is stuck on black screen, even when I push Power + vol down, or Power + vol up, or even just power for 30 seconds and more, nothing hapend.
I had charged it for 30min in case of .
Is there an other way to unlock the phone ? Or can we say good bye to the phone ?
How long was it stuck? If you removed the phone mid-flash it could very well cause a hard brick. Sending it to Google at least with these, is a option, you should take advantage of
For the phones I own the 'force power off` functionality comes from holding Power plus vol down, (or Power plus vol up) for 30 seconds or more: after 10 seconds it will vibrate once; a bit later it will vibrate three times and power off.
You should be able to get it to show something if you hold power for a long time. After you get some response from it, I suggest going to flash.android.com using a Chrome(ium) based browser and flash it to Android 15, then again using the iodé installer.
Did you flash stock Android 15.x before installing iodé as I note above? If not this is likely the issue.
There doesn’t seem to be any issue with the factory reset, the error is just indicating there is no pending OTA update to erase. But again if it is getting stuck at fastboot I suspect it is due to incompatible firmware / drivers due to the incorrect underlying base.
To encourage you, I don’t think either of these are actually “bricked”, they may just have a problem with the install and need reflashing. My only understanding of a true “hard brick” is if after install you go into Developer Options and disable ‘Allow OEM Unlocking’ and then after that your system becomes corrupted (and then also can’t get back to the previous good system which it should revert to if a simple update was corrupted). So it is hard to to.
It should be possible with a long long power press while holding down volume down for it to enter the bootloader again. Even in the case of the hard brick above I mention, it would still be able to enter the bootloader and be detected by the installers (but in that case it is locked and not unlockable).
To your issue: How long are you waiting when it says waiting for any device this can take a bit as it reboots into fastbootd mode (orange header at top saying fastbootd)? Give this some time! If it really is getting stuck there, what about your USB cable, is it usb-c-c or usb-a-c? I previously had issues with c-c cables in the same place where it wouldn’t get into fastbootd mode and got confused, whereas traditional a-c cables were more reliable. But recently on a few other pixels the same c-c cable has been fine. Just wondering what you situation is.
I’ve seen “Waiting for Any Device” many times in my installations with Iode. I install on Windows.
And it’s always the same reason, when the device goes into fast boot mode, the wrong driver is installed in Windows, after the device starts in fastboot mode.
Check this in the device manager and assign the correct driver, then it will finish the installation correctly.
Go to device manager,
find your device,
right click, update driver,
“Search on my device for driver”
“Driver from a list on my computer” and select Filemanager,
(select the path of your zip extracted folder) and find “android_winusb.inf” and select - Click ok.
It shows you: “Android Bootloader Interface”
Click Next -click Finish.
Check:
When your device is in fastboot mode:
Open a CMD - Write:
fastboot devices
(it should show you a device id)
