I thought my pixel was bricked after a bad flash of a custom rom... I ended up with no os. I could still boot into recovery tho and eventually, after hrs of banging my head against the wall got it to accept a flash all command. I believe thats what saved me honestly. But i really dk i actually woke up the next day after staying up the whole night trying to fix the no os problem to my pixel working perfectly. Super crazy. But i understand your pain... It doesnt boot into recovery at all??
Help..Pixel XL in HS-USB QDloader 9008 mode.
- Thread starter droidan
- Start date
Nop, when connected to PC I can hear the usb connected windows sound and device manager picks it up as Qualcomm HS-USB QDLoader 9008.
ADB fails to list device also, so shell fails too.
C:\WINDOWS\system32>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\WINDOWS\system32>adb devices
List of devices attached
C:\WINDOWS\system32>adb shell cat proc/partitions
error: no devices/emulators found
ADB fails to list device also, so shell fails too.
C:\WINDOWS\system32>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\WINDOWS\system32>adb devices
List of devices attached
C:\WINDOWS\system32>adb shell cat proc/partitions
error: no devices/emulators found
Hi all,
I happened to run to the exact problem as @wingman021280. I've been following this thread and try to revive my bricked Pixel XL 128gb.
No luck adb try to read the device when I plug my bricked pixel xl onto my PC. Try to power it on and off for holding the power button and getting into fastboot mode, no luck.
I got QFIL handy here and ready to fire up once someone willing to share that with me (mbn + 2 xml file).
I am more than happy to PayPal whoever that help me and @wingman021280 getting this issue to resolve a beer or 2.
Thanks in advance!
I happened to run to the exact problem as @wingman021280. I've been following this thread and try to revive my bricked Pixel XL 128gb.
No luck adb try to read the device when I plug my bricked pixel xl onto my PC. Try to power it on and off for holding the power button and getting into fastboot mode, no luck.
I got QFIL handy here and ready to fire up once someone willing to share that with me (mbn + 2 xml file).
I am more than happy to PayPal whoever that help me and @wingman021280 getting this issue to resolve a beer or 2.
Thanks in advance!
@petiolarissean - So this needs to be done on a working device in order to pull the files needed for unbricking, is that correct? Also it looks like root is needed on the healthy device to access this? And these blocks contain the .xml/firehose files we might be seeking?
How can I pull the IMG from a working phone?Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
Hello,
I'm sorry, but I am not skilled enough to help you to do this. I would if I could...
I know I have already seen threads on XDA or Google how to do it. If you dig enough I'm sure you'll find it! :good:
Good luck...
Hi,
I have 2 identical Pixel XL phones. One is working fine while the other is not working and when I connected it to the computer it's identified it as 'Qualcomm HS-USB QDLoader 9008'.
Is it possible to extract the needed files for QFIL from the working Pixel? How I can do it?
Thank you so much!
I have 2 identical Pixel XL phones. One is working fine while the other is not working and when I connected it to the computer it's identified it as 'Qualcomm HS-USB QDLoader 9008'.
Is it possible to extract the needed files for QFIL from the working Pixel? How I can do it?
Thank you so much!
Have a look at any Xiaomi fastboot ROM. I firmly believe that the programmer and xml files cannot be extracted rom a working phone but are external tools only used when programming the phone at the factory or when repairing. It's a shame that Xiaomi does provide these essential files thus allowing users to debrick their phones but Google chose not to for whatever (IMO dubious) reason.
Hi there! I got bricked tomorrow too. Just used my phone as always and got reboot with black screen after. PC detects Qulcomm 9008 loader.
So I need loader image too. As I can see there are no images for Pixel XL.
My friend has a Pixel XL, mabe he will help me with image then I share it for you all.
P.S. My GF has a Pixel (not XL) may be this image will be compatible who knows? (the specs of devices are same)
So I need loader image too. As I can see there are no images for Pixel XL.
My friend has a Pixel XL, mabe he will help me with image then I share it for you all.
P.S. My GF has a Pixel (not XL) may be this image will be compatible who knows? (the specs of devices are same)
Hey guys,
Anyone with a rooted working Pixel ever tried this possibility?
https://forum.hovatek.com/thread-1405.html to create the xxx.img
https://forum.hovatek.com/thread-19721.html to create the bootable SD from xxx.img
Anyone out there with a working rooted Pixel willing to try this option please?
Cheers,
Dan
Anyone with a rooted working Pixel ever tried this possibility?
https://forum.hovatek.com/thread-1405.html to create the xxx.img
https://forum.hovatek.com/thread-19721.html to create the bootable SD from xxx.img
Anyone out there with a working rooted Pixel willing to try this option please?
Cheers,
Dan
Add another one to the list...this is so frustrating... used my pixel xl before the holidays (it's my backup phone), then came back to it in early January to retrieve some data from it and it won't turn on....same thing as you guys. Should I loose all hope in retrieving my data ? I don't need the phone to actually booth I'd just need to be able to read the data partition when connected to a PC.
I had that issue on my phone last year and I gave up, Just found it and tried to contact Google in order to get those files with no luck.
Did anyone solve the issue?
Did anyone solve the issue?
Me too...
My OG Pixel XL just entered this state yesterday. I am also willing to pay someone for the chipset files from their working Pixel XL to revive mine.
My OG Pixel XL just entered this state yesterday. I am also willing to pay someone for the chipset files from their working Pixel XL to revive mine.
Just got this HS-USB QDLoader issue after 3 years of use. Sudden death. No fixes, right? Looks like I'm going to wait for the iPhone 12 Max to release next month. Using my HTC One M7 from 2013 until then. I've been using Google phones since the Nexus One in 2010 but got unlucky hardware/software failures with my last two Google phones, the Huawei Nexus 6p and now this Pixel XL.
I guess Pixel phones, given their poor reliability, are OK for people who use their phones during manufacturer warranty periods (i.e. keep them for 2 years)?
I guess Pixel phones, given their poor reliability, are OK for people who use their phones during manufacturer warranty periods (i.e. keep them for 2 years)?
AOA
flash twrp wrong then pixel restar in qualcom mode
i try more methods to solve but till not
using emmcdl commands all flash tools but still not alive
waitng for Help
Can help me expert
sorry for bad english
Dead Pixel -
google pixel 3a on qualcom port show.flash twrp wrong then pixel restar in qualcom mode
detect only as Qualcomm HS-USB QDLoader 9008
i try more methods to solve but till not
using emmcdl commands all flash tools but still not alive
waitng for Help
Can help me expert
sorry for bad english
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2be back bit dude.We will tackle this together and hopefully solve situation at hand!1Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...1Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.1
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?1
Thank you for your reply and information.Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
