03-28-2024 12:52 PM
Hi, I am trying to get to EDL mode on my pixel 5. On windows, it always shows up as "Android Bootloader Interface" in Device Manager - which works fine with ADB and Fastboot commands , as well as normal file transfer for the phone. But right now, I have a phone stuck in a Fastboot loop - where Recovery mode doesn't work, or rescue mode, just fastboot only - and the device state says "error" in red. What seems to be happening is the boot file is corrupt, so it can't even determine if the bootloader is locked or not - but the bootloader is unlocked. I can run fastboot commands from the computer but nothing else. I was trying to force to EDL mode where the phone whould show up as Qualcomm 9008 serial device instead of Android phone, so I could then run Qualcomm tools (QPST, QFIL, QDLoader), but can't get the phone into this mode. I even tried to make my own EDL USB cable using the merge green and black wires technique. Anyway, looking for anyone who's been through this before. I don't want to take it to a repair shop, I already have many phones, I can either throw it away or learn some more skills with it. I've tried using fastboot to boot from the other slot "b", and I've tried booting from a recovery file on my computer but it can't access the bootloader to check if its unlocked (device state) so it fails. Also, I've tried flashing a new recovery from fastboot, but it gives an error, can't get device unlock state. I've also tried the Google online rescue site to reload stock ROM. BTW, I believe they call this soft-bricked, not hard-bricked also.
03-30-2024 03:00 PM
yeah, I tried unsticking all 3 buttons, because they all work correctly in Fastboot, I don't think they're stuck.
03-28-2024 11:46 PM
@ByteFragment - Another person said the volume down button is stuck.
03-28-2024 11:36 PM
thanks....I saw that one before - I actually tried it - just in case my button was stuck - didn't work 🙂 but the fact that my power button still works on the fastboot screen I know its not stuck.
03-28-2024 09:22 PM
@ByteFragment - What may be the best is to contact Google Support and see what they will say.
One person suggested on Google's forum to "Slam your phones power button against a corner of a table" 🤣
03-28-2024 12:54 PM
Here's the results of my attempt using the Android Flash tool (see attached). One is for VZW phones and one is for the generic Android build for Pixels. I think this shows its partially bricked. But I can still do things on Fastboot, but can't think of anything that would help.
The phone has been running Lineageos 20 just fine for the last 3 months.
These didn't work:
fastboot reboot > back to fastboot mode
fastbook flashing get_unlock_ability > FAILED (remote: 'Error getting unlock ability No Response')
fastboot flashing unlock > FAILED (remote: 'Error getting device locked state No Response')
fastboot boot boot.img > FAILED (remote: 'error getting device locked state No Response')
fastboot boot vendor_boot.img > FAILED (remote: 'error getting device locked state No Response')
fastboot flash boot boot.img > FAILED (remote: 'error getting device locked state No Response')
fastboot flash vendor_boot vendor_boot.img > FAILED (remote: 'error getting device locked state No Response')