Pixel XL seen as QUALCOMM HS-USB 9008 - Google Pixel XL Questions & Answers

Hey guys...
so i managed to connect my almost dead Pixel XL, to the PC
and its now know as QUALCOMM HS-USB at Device Manager...
the question is...
how to proceed now?
i found lots of guides to OnePlus, but cant find any to install Android Stock Rom...
any tips will be appreciatted!!!!!

tasty_boy said:
Hey guys...
so i managed to connect my almost dead Pixel XL, to the PC
and its now know as QUALCOMM HS-USB at Device Manager...
the question is...
how to proceed now?
i found lots of guides to OnePlus, but cant find any to install Android Stock Rom...
any tips will be appreciatted!!!!!
Click to expand...
Click to collapse
Just went through the same problem with my Pixel Xl.
To fix it i hold down the Volume Down + Power button until the phone boots in to the bootloader.
From there I just flashed the factory IMG.
Best of luck

hey my friend, i was thinking about It, but i have no screen...
how can i know that the phone booted in bootloader?
already tried...but the phone didnt connected to the computer...for sure wasnt in bootloader

Well it can be a hardware failure, but since i had the exact same problem with the black screen and my phone also showed up as QUALCOMM HS-USB 9008, i doubt it is a hardware failure. I can only suggest solutions that might work.
-Try holding in all the buttons for 14 seconds.
-Connect phone to the computer, then run "fastboot devices", if the phone is recognized(shows up in the list), flash factory img.
-Connect phone to the computer, then run "ADB devices", If the phone is recognized "ADB reboot bootloader". Then proceed as when you flash factory img.
Did you come from Android O btw ?

HALV0RS3N said:
Well it can be a hardware failure, but since i had the exact same problem with the black screen and my phone also showed up as QUALCOMM HS-USB 9008, i doubt it is a hardware failure. I can only suggest solutions that might work.
-Try holding in all the buttons for 14 seconds.
-Connect phone to the computer, then run "fastboot devices", if the phone is recognized(shows up in the list), flash factory img.
-Connect phone to the computer, then run "ADB devices", If the phone is recognized "ADB reboot bootloader". Then proceed as when you flash factory img.
Did you come from Android O btw ?
Click to expand...
Click to collapse
everything was fine with Nougat, then i received Android O update and it happened
i was browsing the web and listening to some music, then it rebooted itself and didnt come back again!

tasty_boy said:
everything was fine with Nougat, then i received Android O update and it happened
i was browsing the web and listening to some music, then it rebooted itself and didnt come back again!
Click to expand...
Click to collapse
Trie "Vol Up+Vol Down+Power for 30 sec"
I am sure you have already tried all the combinations in the world.
I would return it to google.
Best of luck.

tasty_boy said:
everything was fine with Nougat, then i received Android O update and it happened
i was browsing the web and listening to some music, then it rebooted itself and didnt come back again!
Click to expand...
Click to collapse
Hey man, have the same problem with my pixel. Did you fix it?

I had that issue to with mine. Ended up getting a RMA

Related

ADB and Fastboot Can't Detect My Hox - But Windows Device Manager Can...

Am trying to recover my phone from a bricked state (it's un-rooted, and entirely unmodified. It just overheated and won't boot).
(This is on Windows 7)
Running "adb devices", or "fastboot devices" gives me nothing at all, and yet my device is detected by Device Manager, as an APX device when I connect by USB.
Is there anything I can do to make one or the other of these programs recognise the device? Or another program?
It shoud be noted that the phone is entirely dead, aside from popping up in Device Manager. No charging, no LEDs, nothing, no matter what buttons are pressed.
Oh, and, if I connect my wife's phone (an old Desire), fastboot and adb both find this with the "devices" command.
JimBadger said:
Am trying to recover my phone from a bricked state (it's un-rooted, and entirely unmodified. It just overheated and won't boot).
(This is on Windows 7)
Running "adb devices", or "fastboot devices" gives me nothing at all, and yet my device is detected by Device Manager, as an APX device when I connect by USB.
Is there anything I can do to make one or the other of these programs recognise the device? Or another program?
It shoud be noted that the phone is entirely dead, aside from popping up in Device Manager. No charging, no LEDs, nothing, no matter what buttons are pressed.
Oh, and, if I connect my wife's phone (an old Desire), fastboot and adb both find this with the "devices" command.
Click to expand...
Click to collapse
my phone done something similar yesterday apart from i didn't get axp showing up. the s-off guys would be able to help with the apex i think since they think its the key to getting s-off. but if u just wont your phone back then hold power and vol- till soft buttons flash and it should boot. it worker for me
steveharris87 said:
my phone done something similar yesterday apart from i didn't get axp showing up. the s-off guys would be able to help with the apex i think since they think its the key to getting s-off. but if u just wont your phone back then hold power and vol- till soft buttons flash and it should boot. it worker for me
Click to expand...
Click to collapse
Cheers mate, but my phone's beyond that. No button combinations do anything
Who are the s-off guys? How do I contact them? Are they a bit like the A-Team? "If you have a problem, and if you can find them, maybe you can call...the S-OFF Team!" Dun-dun-dun da-da-da-daaaaa....
JimBadger said:
Cheers mate, but my phone's beyond that. No button combinations do anything
Who are the s-off guys? How do I contact them? Are they a bit like the A-Team? "If you have a problem, and if you can find them, maybe you can call...the S-OFF Team!" Dun-dun-dun da-da-da-daaaaa....
Click to expand...
Click to collapse
they are trying to get s-off on our phones so we can do more lol, loving the theme it should be official lol heres the link http://forum.xda-developers.com/showthread.php?t=1604300

Another Nexus 5X bricked

Hey!
I just got a bricked N5X from my friend. It doesn't show any sighs of life (download mode, recovery, etc.) except lovely Qualcomm HS-USB QDLoader 9008 when I connect phone to the PC.
I searched a lot of post across the Internet and there are couple of ways to (at least try to) fix ix, but I miss files to do that. BoardDiag doesn't support this chip and even if I want to try I cannot find .tot files for 5x.
So is there any way to fix it? To get img files needed or something else?
Thanks in advance!
Unfortunately, my Nexus 5X just got bricked as well. It was working fine until all of a sudden, it rebooted while using Google Maps & Bluetooth to stream the navigation and music. Then it got stuck on the Google boot screen and since then, it would not boot. I was able to get it to start in bootloader mode and recovery mode a few times. I was even able to clear cache once but that was it. Now, I can only get it to start in bootloader after pressing and holding the power + vol.down button for at least 20 secs.
I tried plugging into my computer and it shows the Qualcomm HS- USB QDLoader 9008 (COM5) under Ports (COM & LPT).
What can I do to recover from this?
If you are able to go to the download mode, then maybe you can try LGUP to flash original image. You can more info on other xda forums
konker said:
Unfortunately, my Nexus 5X just got bricked as well. It was working fine until all of a sudden, it rebooted while using Google Maps & Bluetooth to stream the navigation and music. Then it got stuck on the Google boot screen and since then, it would not boot. I was able to get it to start in bootloader mode and recovery mode a few times. I was even able to clear cache once but that was it. Now, I can only get it to start in bootloader after pressing and holding the power + vol.down button for at least 20 secs.
I tried plugging into my computer and it shows the Qualcomm HS- USB QDLoader 9008 (COM5) under Ports (COM & LPT).
What can I do to recover from this?
Click to expand...
Click to collapse
hardware issue, google and LG are apparently aware of this. Mine just crapped out and Im one month out of warrunty so I was able to get google to do a one time replacement. Thought who knows how long that one will last.
My Nexus 5X just crapped out about 5 minutes ago. I was using Chrome and it froze, so I held the power key. It is stuck in a boot loop. If I VolDn+Power I get the menu to go to go into recovery, but it doesn't succeed. Tonight when I get home if there's anything to try via ADB I'd appreciate a link, but I figure it's the hardware problem. Bootloader Version BHZ11h. I'm out of warranty but have an extended one from my credit card company.
Same here...I am really frustrated about that!Another bricked nexus out of nowhere..!!Don't know what to do!
Since i still have warranty is it better to go to the place i bought to ''fix'' it as they said or send an email to google if they can replace it..?
what do you think? is there any way to save our data?
My Nexus 5x froze up without warning earlier this week while listening to spotify and playing ingress.
I managed to reboot it but the same thing happened again so I booted it up in recovery mode and did a factory reset. Now the phone is dead other then the LED flashing red while connected to the charger.
I contacted the reseller and i'm gonna ship it of today to be repaired i hope.. unless the repairshop claim it's been water damaged or some other "#ยค"#%.
Here's another Nexus 5X bricked: it frozes playing War wings.
Sent in warranty to LG repair center they changed the mobo and sent me back in 4 weeks: how many time could work now?
link: https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg pin : g5cg
this rom test at my phone nexus 5 use firehose 8974 , no firehose 8994 ,your must find 8994

Phone bricked?

Hi, I was wondering if anyone has encountered this problem? The phone has been updated to the latest firmware as of the 8th of October 2017. I was using the facebook app and it was crashing repeatedly; after a few times of attempting to restart the app and crashing, the phone froze (black screen) and I tried to do a soft reset (30 secs on power button) but to no avail. I noticed that when the phone is put on the charger, the white LED flash for the front facing camera started blinking. I tried plugging it into the laptop and noticed that "Qualcomm HS-USB QDLoader 9008" driver is installed. Of course white LED flash was blinking too. A bit of digging seems to suggest that the bootloader has been corrupted. How is this possible and how can it be fixed (stopping short of contacting motorola)? Thank you for any advice in advance.
Flash stock firmware !?
Unfortunately I can't even get into the recovery mode (aka down + power button as per instructions here - https://motorola-global-en-aus.cust...ail/a_id/113698/p/30,6720,9837/kw/clear cache). Any other ideas?
Try this: https://forum.xda-developers.com/showpost.php?p=72813119&postcount=6
Oh no, black screen hard brick (to my face)
MP1_ said:
Try this: https://forum.xda-developers.com/showpost.php?p=72813119&postcount=6
Click to expand...
Click to collapse
I have the same issue. Z2 NASH is booting and showing the qualcomm usb qloader in windows however I have no response from the gui or screen whatsoever. This happened immediately after a factory reset so, not only can I not boot to TWRP, but I also cannot communicate thru ADB. Please help if you can. I am currently following your guide here for flashing from windows and installing / flashing stock firmwares. I will post back my results. Thanks for any help you can offer...
I have the same issue, have there been any fixes? My Moto z2 play randomly bricked one night, same "Qualcomm HS-USB QDLoader 9008" in my "other devices" tab, and i have no clue what to do. My phone wont do a single thing, it was flashing the led on the right side when it was charging, now it does nothing at all. Any help is appreciated

moto z2 on "press any key to shutdown" potential hardbrick

I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk
cgigate said:
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.
latadswapnil said:
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.
Click to expand...
Click to collapse
Have you tried holding vol up and pwr to boot into bootloader?
41rw4lk said:
Have you tried holding vol up and pwr to boot into bootloader?
Click to expand...
Click to collapse
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:
latadswapnil said:
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:
Click to expand...
Click to collapse
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash
41rw4lk said:
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash
Click to expand...
Click to collapse
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?
latadswapnil said:
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?
Click to expand...
Click to collapse
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.
41rw4lk said:
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.
Click to expand...
Click to collapse
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.
latadswapnil said:
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.
Click to expand...
Click to collapse
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.
41rw4lk said:
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.
Click to expand...
Click to collapse
While if the OP is correct, and the problem is that they replaced their bootloader, then that's exactly what edl mode is for. However, you're definitely right that there's no key combination. I've been trying to get my moto into edl for days. I even got the battery to die. It just makes other diagnostics more annoying when I need to charge. So far, from what I can tell, the MSM8998 in a Z2 force first of all plays by different rules, uses a different programmer, and is generally not going to respond to the stock "qualcomm unbrick" tutorials. If it gets into edl, then you might be able to blankflash. But I guess keep trying different things, from what I've read the drivers and usb ports are finicky even with phones where this is known to work. It is not known to work with TX1789, at least not with the ease it works in other snapdragon phones. It's actually a massive security vulnerability (if it works it allows arbitrary read/write from the lowest level of the chain of trust, bypassing most security by default. It's a total backdoor), it's just unfortunate we're on that side of the fence. It doesn't have to be that way, but it was designed to see all unsigned software as equally malicious.
latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
Does anybody have any new suggestion how I can get into EDL mode?
my phone is still stuck on to the screen where it says press any key to shutdown. It doesn't get detected at all on any USB port or with different cables.
Does anybody know if there are any EDL short points on motherboard or deep flashing cable?
although I tried cutting regular USB C cable for trying to short the two cables and force put it in edl mode but nothing worked yet.
If anybody has any suggestion please throw some light.

Question Bricked my Prixel 6 after flashing stock rom

Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Call whoever you bought the phone from and do warranty claim.
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?
cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits
ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....
Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears

Categories

Resources