Hello, I’m not an expert but installed successfully CalyxOS and Lineage with MicroG but wanted to go with iodeOS. I know how to enter fastboot and switched between ROMs just to ensure I had the right cable and processes. Right before trying to install iodeOS I flashed the Pixel with stock Android 15 from flash.android.com successfully.
Then, I followed the instructions on iode.tech/installation/, downloaded the installer and followed the straightforward instructions up until the “waiting for any device” where the phone was stuck on a screen with the lineageOS logo and 3 or 4 options. I awaited over 1 hr then eventually I selected the “Restart” option on the phone. Then it went blank and it’s not responsive.
Any suggestions?
“Waiting for any device”
is almost always a driver problem.
The device was recognized cleanly in normal operation and then suddenly no longer when it went into download mode.
It is for Windows specifically here to check the device manager and change the driver manually.
I’ve had this several times now.
If you connect the device to the computer, is it accessible via ADB?
1 Like
Thank you @volker01
Indeed the computer is a Windows 10 machine but I did not have any issue when flashing any other ROMs (same machine and cable). I also did download the USB driver from Google and device manager did not show any warning.
To clarify a bit more, once the process was at “Waiting for any device”, the device was “stuck” at the Lineage menu and I clicked on Reboot (or Restart) which led for few seconds to the red triangle warning after which the device (I guess) rebooted again and the screen went blank.
Unfortunately no, ADB does not recognize the device. When I plug it in any laptop via USB there is no sign or activity. The screen is blank and I could not perform hard reset (power + down volume).
If I could get into the bootloader, I may be able to reset it to stock Android and try one more time; however, I do not know how to get the device to power on (or wake up).
Thank you for any help
Are you using a usb c-a cable instead of c-c? I have had issues with c-c cables getting stuck at that same spot. The phone is trying to get into fastbootd mode (different than normal fastboot). I do see this same cable worked for other builds, but something about the fastbootd part (at least in my limited understanding) is different that I would normally do when installing a custom ROM.
If this isn’t the case, you can also try to download the full fastboot image and use the flash-all.bat script (instead of using the graphical installer). I assume you have a fastboot connection, even though adb isn’t avaiable at that lower level stage.
Hey @rik thanks for the reply!
As it stands, the device is no longer turning on (I am not sure 100% but adb devices shows no list. And fastboot still hangs at “waiting for any device”). I’ve tried several cables (c-c, a-c and OEM) but the device is just dead. I have another pixel that, when plugged into the computer, “activates” Windows USB response (choose what you want to do when Pixel is plugged in). But when I plug in the dead Pixel I get no response; nothing changes in Device Manager or elsewhere.
Even when unplugged, the power+down volume for 60 seconds to enter bootloader does nothing; the device just remains off.
So, I guess any work FROM the computer is futile as the phone is not seen any longer. Anything I can do with the phone itself? Any special, secret operations I can do to force it into the “normal” boot?
I wonder if it was stuck “powered on but at a black screen” and was completely drained? Put it on a good charger for some time to see if you can get it back to life?
@rik thanks!
The phone was tethered to the laptop during all those ROM flashing work so I assumed the device was charging/charged. Yet, it’s so weird that I’m not able to get the phone to turn on the screen or even flicker for a short time to signal it’s “alive”.
That’s why I’m hoping to find a way to revive the phone…
Do give a check on a proper charger, a USB port on a computer will only give approx. 5v x 500ma = 2.5W, and a phone that is somewhat “hung” can be pulling more power than this (meaning even if it is on a black screen the cpu etc may be drawing more than it is receiving, thus draining down still).
A good charger will be 5v x 3a (15W), or with “quick charging” will jump up to 12v x 2.5a = 30W (or higher).
Thanks @rik - I’ve also contacted Google support and all they asked was to press Volume Up+Power and when that did not work, they referred me to a store for technician support. Maybe I can get some help there. I’ll report back if anything comes up. Not very optimistic but appreciate your help!
I don’t see your exact Pixel model listed by the way, but yes it doesn’t seem good if there is no response at boot + volume keys.
I had the same issue. I allowed the phone to fully discharge because it was stuck at the G icon. Next day I plugged it in using the charger into the wall and it showed some life of charging. Once it got to an acceptable level it actually showed the fastboot screen. I plugged it back into the windows computer and low and behold it actually saw it!!! I preceeded to use the installer again and it went thru the proper steps and I allowed it to do its magic and this time everything worked as planned. The mistake I made was instead of watching the display on the software screen I looked at the phone for messages and saw the “Reboot Now” on the phone and pressed it. Needless to say it wasn’t actually ready to reboot and this screwed up my installation. Hopefully this will help someone in the future. I have a Pixel 9 XL and I was waiting for the developers to drop the update for that phone. I guess I got too excited!!