Help..Pixel XL in HS-USB QDloader 9008 mode.
- Thread starter droidan
- Start date
Hey... 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...
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...
Hey... 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.
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://xdaforums.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?
Last edited:
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://xdaforums.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
Last edited:
What does that mean? Were you rooted, unlocked? If so return the device, no?Bad Flash on OTA update
Sent from my Pixel using XDA-Developers Legacy app
Hi guys,
I've opened a similar thread on google forum - related to pixel 128gb being bricked and in chipset download mode.
If there are enough bricked pixels out there perhaps google will (hopefully) share those files?
Cheers,
Dan
I've opened a similar thread on google forum - related to pixel 128gb being bricked and in chipset download mode.
If there are enough bricked pixels out there perhaps google will (hopefully) share those files?
Cheers,
Dan
The deluge of bricked Pixels resulting from the Oreo update continues...
I did, however, find these pages posted in the last couple weeks, and wondering if they're the answer to the Q's posted earlier ITT (sry I'm too new to post live links, so you'll have to paste these):
- androidauthority.com/download-android-8-0-oreo-794622/
- androidauthority.com/install-android-oreo-758342/
- developers.google.com/android/ota
Earlier ITT, posters were saying that they couldn't find the firmware or other files that would allow someone to recover from the hard-bricked state...but are those 'official' factory images and OTAs what they were saying they needed, but which they couldn't find at the time? In short, might we now actually have the files necessary to save our bricked Pixels without engaging in Macguyvering that would void the warranty?
I did, however, find these pages posted in the last couple weeks, and wondering if they're the answer to the Q's posted earlier ITT (sry I'm too new to post live links, so you'll have to paste these):
- androidauthority.com/download-android-8-0-oreo-794622/
- androidauthority.com/install-android-oreo-758342/
- developers.google.com/android/ota
Earlier ITT, posters were saying that they couldn't find the firmware or other files that would allow someone to recover from the hard-bricked state...but are those 'official' factory images and OTAs what they were saying they needed, but which they couldn't find at the time? In short, might we now actually have the files necessary to save our bricked Pixels without engaging in Macguyvering that would void the warranty?
I assume so...I bought the Pixel directly from Google, so assumed I was getting the purest Android installation possible / no provider bloatware etc...if i'm not mistaken, the bootloader would have been Locked when I initially received the phone, right?...if so, then yes it would still have been locked when it bricked, as I didn't take any actions to unlock it (nor would i know how)
G
GuestK00254
Guest
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
G
GuestK00254
Guest
Maybe that's why they aren't giving the filesI wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
This happened to mine as well
Went from 8.0 to 8.1 - wiped data and re-locked bootloader. Ran fine for two days then powered down and now I'm in this qualcomm mode. Thankfully I purchased the 2-year through Google. Unfortunately their support is dogsh**.
Update: Ok Google's support rep was actually pretty solid but their system is awful. I'm already on a refurb and it doesn't have the IMEI printed on the sim tray. Either way they worked it out and I'm down $80 for the deductible.
Went from 8.0 to 8.1 - wiped data and re-locked bootloader. Ran fine for two days then powered down and now I'm in this qualcomm mode. Thankfully I purchased the 2-year through Google. Unfortunately their support is dogsh**.
Update: Ok Google's support rep was actually pretty solid but their system is awful. I'm already on a refurb and it doesn't have the IMEI printed on the sim tray. Either way they worked it out and I'm down $80 for the deductible.
Last edited:
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://xdaforums.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://xdaforums.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
