Database Develop

Stuck at Bootlogo

Hello all,
I have a friends sprint hero cdma that was rooted with z4root. He was flashing a mod that changed the text from green to orange and the phone froze. He waited quite a while then decided to hard reset. When he put the battery back in and rebooted the phone and the phone would not boot past white HTC bootlogo. The phone will not boot into recovery and the PC will recognize the phone, but the system will not mount so the ruu will not detect the phone either. HTC sync does not detect the phone being connected either. I am using a program called USBDeview and it shows the driver is there and says it is connected but none of the programs detect its connection. Any ideas?
Thanks in advance. Again this is not my phone and I am not familiar with rooting procedures with this phone, but I see a great learning experience in front of me and love these challenges.

this should be in QnA.
Hold power + vol down. will get you into HBOOT. if you flashed the eng-spl that unlocks fastboot you can erase and flash new. Tutorials are somewhere in this forum.

Sorry for the wrong forum. The phone will not hboot or boot into recovery

If it gets that far, you should be able to run the RUU. It'll restore everything to stock ;-)
Sent from my Epic using XDA App

The phone does not connect all the way for some reason. The RUU does not see device and neither does ADB. In device manger, when the device is connected it is assigned a drive letter and I can right click and go to properties and details and the description says android phone. I am out of ideas. Even when the device is connected and assigned a drive letter I can open file explorer and click on the device and the directory is blank. The SD card does not even show up, but if I take sd and put it in an adapter the sd card is still in tact with everything on it.

Sounds like a driver went haywire try searching the dev section for my thread on how to install adb. I know you have it already but try the diffrent drivers. I would post a link but I'm mobile. Hope it helps
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.

Power off
hold vol up and power on
should be in fast boot mode
plug in your USB cable
should now be in fast boot usb mode
run RUU from the computer
RUU should recognise the phone and start installing

I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.

What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.

nordy420 said:
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
Click to expand...
Click to collapse
Yes this is basically true. But if you get the HTC screen, chances are that it is not bricked. I have to ask, did you flash anything like a radio for GSM? If not, then you might need to just let it sit there for an exstended period of time and see if it boots. When I do certain things to my phone, it might take up to 15 minutes to get by the HTC logo screen.

nordy420 said:
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
Click to expand...
Click to collapse
I wish I could take a screen shot and show you but the phone is not recognised at that point except by the RUU when it is waiting for bootloader. Bootloader is another name for fastboot.
It would be a white screen with green letters and it will say fastboot near the top under the green letters. At the bottom of the screen there will be 3 android characters on skate boards.
This is what you should see. Try again
Important: Make sure the USB is not conected at this time
Power off
Hold volume up, then press the red key (power on)
Fastboot screen comes up
At this point plug in the USB. It will change from Fastboot to Fastboot USB
Run RUU .5 or .6 from the computer
It will get to a point where the install says waiting for bootloader
from there it should start installing
If you can't get to the bootloader screen (fastboot) then I am not sure how to help you
Let me know if it works for you.
Edit: If you are not using ENG SPL or have S-Off read this post. You will need a working knowledge of how to use ADB.
http://forum.xda-developers.com/showthread.php?t=958968

Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.

Thank you for the help by the way. I am not the owner of the phone, I am just more patient than the owner and have nothing to lose if it is screwed lol. http://androidforums.com/sprint-hero-all-things-root/259735-bricked.html. Here is his desperate cry for help after it happened. I own a Droid x and have no idea what he was actually trying to do, but maybe after you read what he did then maybe we can come up with a fix. I agree with you supporters that the phone is not bricked but it is sure being stubborn. Please let me know what ya think. Thanks.

unCoRrUpTeD said:
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Click to expand...
Click to collapse
I will try this when I get home. I did do a battery pull but I did not leave it out very long, but the screen never changed for me, just stayed white with HTC logo in the middle.

Be very sure to disconnect the USB. That was the step I was missing and I could not get it to boot to recovery when it was stuck at the logo. Once the USB was disconnected, took the battery out, put it back in, and held down the home button while pushing the power. That worked! Woot!
Lynne

No luck. The phone will not boot into anything to where a PC will recognize it.

nordy420 said:
No luck. The phone will not boot into anything to where a PC will recognize it.
Click to expand...
Click to collapse
Have you downloaded android commander and gave that a shot? androidcommander.com
android commander recognises the phone when it is at the logo screen. it will see all but the sdcard.
within android commander menu, there is a reboot to bootloader command

Ill try it, and report back

So I messed with android commander a little and could not get it to detect the device. I really think that it is a driver issue. I cannot get the HTC driver to install for the phone. A different driver has been installed for the device and windows will not let me manually install one. I can use the install legacy and the HTC driver is there but it will not correlate with the phone when connected.

[Q] Help! - Bricked Incredible S, S-ON, unable to boot past HTC logo

Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!

expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
You better wait till january and claim the warranty!

hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .

If the above doesn't work send it to any htc repair center. You have to pay but whatever.

hassanhm said:
hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .
Click to expand...
Click to collapse
Hey hassanhm,
thanks for the reply. I've tried searching the HTC official website for the stock rom, however it is not available for download due to the fact that firmware upgrades are now over the air ..
i've downloaded the RUU rom by optus (RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned
http://www.filefactory.com/file/cfdd...028_signed.exe) found here - http://forum.xda-developers.com/showthread.php?t=1033922 - however it just gets stuck on the booting to bootloader step ...
if there a different stock rom exe file i should be using?
Thanks!

I'm a singaporean. Its uncommon to see this kinda stuff :/

looks like dead motherboard i saw thing like that already

I'm from Singapore. I had this issue, spent a day flashing and rebooting to try and fix it. Then I have up and just flashed an official ROM, I think any one will do, then sent it to HTC. It was still s-off but they didn't care. Took just 3 days and they sent it back, fixed and like brand new. I suggest you don't waste time and just sent to HTC. it will come back s-on but you can just root it again.
Hope this helps!
Sent from my HTC Incredible S using XDA App

There's one but when they put latest Hboot (1.16.0000)then it's harder to flash ROM than 1.13.0000. Hope you get your phone back and it's working

expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
If you claim warranty : YOU LOSS A CHANCE TO HAVE BIG FUN I'm exactly on your situation (may be worse), but probably we feel different. I can only boot into fastboot and hboot ... LOL

expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
Click to expand...
Click to collapse
You must be able to revive, since you did not do anything related to s-off, rooting etc. rooting, s-offing are for modding addict fellow
[/QUOTE]
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
[/QUOTE]
Revolutionary only work on phone with NORMAL BOOTING (Android booting). If you did on fastboot then (I Think) you start create big trouble
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
Click to expand...
Click to collapse
This will only work for UPDATE, mean you must use higher version of ROM than in the phone (if you are s-on) -CMIIW-
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
Click to expand...
Click to collapse
can you post your mainver : FYI, I could NOT resolve my vivo since my situation is worse than you, but probably my experience with unsuccesfull result will give different output ... who knows.
on fastboot (I'm sure You know how to do) fastboot getvar all (windows command) and post the output for our analysing together and help each other.
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
You will loss a big FUN on your life !!! by choosing easy way.

i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard.

ice_pick88 said:
i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard
Click to expand...
Click to collapse
.
what did you do before stuck. Can you boot into bootloader (?) are you S-ON or S-OFF (?) what is Hboot version do you have. To have bootloader state : press power and volume down button SIMULTANEOUSLY if within TEN MINUTES you do not have bootloader status you should stop and let us know here

Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.

ice_pick88 said:
Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.
Click to expand...
Click to collapse
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.

x1123 said:
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.
Click to expand...
Click to collapse
Thanks again for the reply. when i choose the factory reset the phone hangs but when i select recovery it goes to the red triangle logo. Where and how can i know whats RUU of my phone? Sorry im literally a noob.

3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R

programci_84 said:
3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R
Click to expand...
Click to collapse
Just for additional info. If you can not find another android/windows phone to get sdcard CID (you have only one phone and now in trouble). You can use any laptop with Built In card reader at PCI slot and NOT USB STORAGE if you were not have BOTH ... it's time to ask help your neighbour or your friends

Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done

fallenwout said:
Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done
Click to expand...
Click to collapse
Good day,
Thanks for the replies. Im having problem with this step. Im doing the unlocking the bootloader of the phone but when im in the process of inputting the cmd command "fastboot oem get_identifier_token" it gets me the " <waiting for device>
I have installed the latest htc sync version and updated all the drivers but it looks like my pc doesnt detect the incredible s.
Need suggestion guys.
Ill try the Gold card step later maybe it will work.
Thanks again.

[Q] Possibly Bricked HTC One M7... HELP!

Hi,
This is my first time to create an account and or post on XDA, so I appolagize if my question is somewhere else, or if this is the wrong section...
I have a T-Mobile HTC One M7. I flashed the Google Edition RUU to try it out. I then flashed just the firmware back and was going to restore a TWRP Backup. After I issued the command fastboot flash zip firmware.zip twice, I entered the command fastboot reboot-bootloader. The screen then turned black and won't turn on. The phone seems completely unresponsive. It won't boot to an OS, or Bootloader. No HTC logo on the screen. If I plug the phone in, nothing happens. No charging light or anything. I surrely thought I actually Bricked it, but it appears to be reconized by Windows. If I hold down the power button for so long, the light won't blink, but the computer makes a device disconnected sound shortly followed by a connect sound. I went ahead and connected it to a Linux machine, and the OS sees 6 different partitions / removable media. I am able to browse what appears to be the root, system, recovery...
It is S-OFF via firewater and the firmware I flashed has hboot 1.57.0000. The bootloader is unlocked. The device is not seen by adb nor fastboot.
Does anyone think I have any chance of recoverying it?

Yes it's dead, try this http://forum.xda-developers.com/showthread.php?t=2770684
[UNBRICK][BETA] HTC Unbricking Project
If not, then JTAG.

That worked. Thank you very much SaHiLzZ.

AndroidBrick said:
That worked. Thank you very much SaHiLzZ.
Click to expand...
Click to collapse
Excellent

[Q] bootloop and no access

HTC M7 unlocked
s-off
hboot-1.57.000
android 4.4
i think 'twrp-2.8.6.4-m7univ'
usb debugging on
adb on pc win 8.1
all driver incl. fastboot
tried till now
° 'power' 15sec pressed
° 'power+volume up' 15sec pressed, ( htc logo, immediately after black screen jumped from volume up and pressed 'power+volume down' - short vibration, htc loge ( beep from windows - but recognizes only a blank CD drive), than stuck in google bootanimation
° 'power+volume down' same result like before that - if i continuing to press both there is the vibration, htc logo, beep from pc, black screen, vibration, htc logo,.....
tried all with or without usb-connection, also after one our pause - always the same result.
i.e., can't enter neither fastboot nor recovery so i haven't access to my M7 to flash anything
is there any possibility to reactivate the phone ???
thx a lot in advance

cla1966 said:
HTC M7 unlocked
s-off
hboot-1.57.000
android 4.4
i think 'twrp-2.8.6.4-m7univ'
usb debugging on
adb on pc win 8.1
all driver incl. fastboot
tried till now
° 'power' 15sec pressed
° 'power+volume up' 15sec pressed, ( htc logo, immediately after black screen jumped from volume up and pressed 'power+volume down' - short vibration, htc loge ( beep from windows - but recognizes only a blank CD drive), than stuck in google bootanimation
° 'power+volume down' same result like before that - if i continuing to press both there is the vibration, htc logo, beep from pc, black screen, vibration, htc logo,.....
tried all with or without usb-connection, also after one our pause - always the same result.
i.e., can't enter neither fastboot nor recovery so i haven't access to my M7 to flash anything
is there any possibility to reactivate the phone ???
thx a lot in advance
Click to expand...
Click to collapse
Try putting the phone's proximity sensor under a very bright light then try again.

The Android Manual said:
Try putting the phone's proximity sensor under a very bright light then try again.
Click to expand...
Click to collapse
tried - same result - first the htc logo and than the balls from the google boot animation.................

cla1966 said:
tried - same result - first the htc logo and than the balls from the google boot animation.................
Click to expand...
Click to collapse
Mmm... I think it's good that you can still get to the boot animation. What happened before this one by the way? Did you flash a ROM or something? Was your phone converted to a different variant?

The Android Manual said:
Mmm... I think it's good that you can still get to the boot animation. What happened before this one by the way? Did you flash a ROM or something? Was your phone converted to a different variant?
Click to expand...
Click to collapse
oups........sorry - forgott
had android 4.4.4 and would reflash lollipop -> Google-Plus-Edition-LP_m7_v2.06_030615
doing 5 things the same time forgott to wipe and reboot....
fine, that you're thinking, that's good that i had my bootloop.......................................... but i won't to have back my fastboot or my recovery................................. :crying:

cla1966 said:
oups........sorry - forgott
had android 4.4.4 and would reflash lollipop -> Google-Plus-Edition-LP_m7_v2.06_030615
doing 5 things the same time forgott to wipe and reboot....
fine, that you're thinking, that's good that i had my bootloop.......................................... but i won't to have back my fastboot or my recovery................................. :crying:
Click to expand...
Click to collapse
Mmm... You said that when you plug it in, Windows 8 detects it. What does Windows 8 say it is? Go ahead and open device manager in windows 8 by going to the start screen and simply typing "Device Manager". Lastly, what variant is your M7? International, AT&T, T-Mobile, sprint or verizon? If it's from Sprint or Verizon you may have flashed a ROM that is NOT for your phone.

it's an international
Unknown USB device
Google-Plus-Edition-LP_m7_v2.06_030615 - the rom is for my phone
edit: now it is shown as HTC MTP device

i faced like this problem ,,, try this solution
http://forum.xda-developers.com/htc-one/help/htc-m7-802w-stuck-lock-screen-t3137812

thaaaa-haaaaa...... IF i COULD enter in fastboot....... i just wrote that i can't do nothing - no fastboot, no recovery

nobody un' altra idea ?????

Google Pixel QUSB_BULK_CID:xxxx SN:xxxxxxxx

Something happened to my Google Pixel this morning. Everything was fine last night, woke up this morning and the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx SN:xxxxxxxx.
I did some searching around, and it sounds like the phone might be stuck in Emergency Download Mode (EDL)? Anyone has a solution on how to fix this issue?
(I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.)
BTW mine is Google Pixel 3,
Anyone has the solution !! Please help !!!​

Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.

mindyabiznis said:
Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.
Click to expand...
Click to collapse
Yeah, but nothing happened! Its EDL mode.

From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.

mindyabiznis said:
From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.
Click to expand...
Click to collapse
Thanks for the reply...
I already did all of this but couldn't get the phone out of Emergency Mode,
and I already said (I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide and I'm not able to locate the QSPT Flashable Firmware File for my device Pixel 3.
It's very frustrating to saw that even a pixel phone has to go through this...
It was not rooted / not Bootloader unlocked / or any kind of modification wasn't done with it only an OTA update from Google was installed last wk.

Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.

mindyabiznis said:
Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.
Click to expand...
Click to collapse
Yeah, thinking of battery disconnect..

sifatrhmn said:
Yeah, thinking of battery disconnect..
Click to expand...
Click to collapse
Can you disconnect the cable and just let it run out of juice?

Give your information to this proposed lawsuit this office may pursue.
Google Pixel 3 Class Action Investigation - Chimicles Schwartz Kriner & Donaldson-Smith LLP
chimicles.com

When your device appears like this on your PC, it means it's stuck in QPST mode - Qualcomm Product Support Tool. The software is not freely available from Qualcomm, nor are the necessary files that would be required to reprogram the PROM.
Some users have had success leaving their phone to run out of battery. Failing that, there is unfortunately no way to recover the device beyond seeking repair.