Database Info

[Hard bricked Pixel 2] qualcomm hs-usb qdloader 9008 in device manager

I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.

I found this for you: https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/page1

@misslebulletttttt did you fix your Pixel. If yes, how did you do that?

download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.

Tacis said:
@misslebulletttttt did you fix your Pixel. If yes, how did you do that?
Click to expand...
Click to collapse
sadly, the files that download tool asked was far proprietary, I'm not able to peek it a bit

I'm not saying these will fix or even do anything but I found them and maybe they can help you there Qualcomm usb drivers. I apologize if these are of no use.

I will just post here in case someone has the same issue and might contribute with the files...
Basically an Android device has a few steps of initialization
- power on
- initialize cpu and memory
- load bootloader
- bootloader selects boot mode
- having the boot selected, the kernel and device tree are loaded
- drivers are loaded
- system is loaded
- userdata is decrypted
Ok... So knowing that, when we want to write some partition on the device, we use fastboot. But first, the fastboot must have oem unlocked in settings. Well when unlocking in settings, this write in a protected partition (don't remember which one) which is checked if the fastboot can run some commands.
Well the next step is... Where is fastboot located?
Well, fastboot is located inside the bootloader. So, what?
Imagine that there isn't anything written in the memory... What would the processor do? It would think... Well nothing there... But must access the memory. So the cpu opens a port which is known as the emergency download mode (EDL).
EDL mode can be triggered with adb command or by shorting test points (there's another way, but I won't say it here)
Anyway when in edl mode, the processor talks a defined protocol, which is known as firehose.
So the first file you mentioned:
prog_emmc_firehose_xxxx.mbn
Is the programmer for the specific chipset, in order to make a handshake and allow to write.
Then after the handshake, you need to define how the memory will be partitioned (remember... It is considering a raw memory, with nothing on it). This lead us to the second file:
rawprogram_XXX.xml
This is basically how the memory is partitioned and where the image address is.
Besides those files, you need the img files (which will probably be only the system.img non sparsed i think...) And patch.xml too, probably.
But remember... The programmer needs to be signed and for the chipset... So if anyone has any contact with google... Maybe we can get those in order to unbrick devices... Anyway...
I just wanted to have those files, in case i run into a bad update...

I think we have to contact the carrier according to the bootloader files

misslebulletttttt said:
I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.
Click to expand...
Click to collapse
Hello friend! I have the same problem as you! (Hard bricked Pixel 2 and can't find firmware files for flashing device(via QFIL or QPST)). Do you have any progress on this issue ?
I don`t know where to go with this problem except for this forum

Hi, have you found a solution to this problem? I got a hard brick after the update (

Any update from anyone please?

bmw9651 said:
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
Click to expand...
Click to collapse
What does any of that mean? There is no download for a, tool all in one around here.

Can sb help me to unbrick my phone.

Hi, first off all i dont speak english very well.
I have a problem with phone i was stuck in bootloop and i tried to use twrp to restore sytem but i chose bad parition (boot, system and system image) those 3 and now i cant do anything. Only fastboot mode working. Pls guys can u help me. I was trying to use windows powershell to do sth but i cant run twrp image and now i dont know what to do. I have a nandroid backup on phone and on computer pls, can u help me???
I try to use qualcom brick tool but in device manager my device shows up us android bootloader interface

Possible solution
I had a problem where I softbricked my op6 by restoring an old system backup through twrp. My phone was stuck in fastboot mode. I was able to turn it off only when it wasn't connected to a pc or a charger.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It basically flashes everything you need onto your device. Your phone should be back to bone stock conditions software-wise after that

Download this
To unbrick your smartphone start the MSM Tool as Administrator. Turn off your phone and hold the volume up button and connect your phone to the computer. When you have done this, your phone should be recognized and flashed with the first ROM. Enclosed you find the Android P Rom as zip.
Download "https://1drv.ms/u/s!ApkcnumxOqfvhMBCFw0hvELIxADoNA"
Note: I accept no liability for failure and or possible damage

R4D0WS said:
To unbrick your smartphone start the MSM Tool as Administrator. Turn off your phone and hold the volume up button and connect your phone to the computer. When you have done this, your phone should be recognized and flashed with the first ROM. Enclosed you find the Android P Rom as zip.
Download "https://1drv.ms/u/s!ApkcnumxOqfvhMBCFw0hvELIxADoNA"
Note: I accept no liability for failure and or possible damage
Click to expand...
Click to collapse
I would recommend doing this operation, OP. For more reference, here's an XDA thread that talks all about recovering from Hard and Soft bricks using the MSM tool:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

HighOnLinux said:
I would recommend doing this operation, OP. For more reference, here's an XDA thread that talks all about recovering from Hard and Soft bricks using the MSM tool:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Click to expand...
Click to collapse
It´s the same one , but i have added the newest update in the .zip file.

Thanks for help guys, I used "MsmDownloadTool V4.0 International" and it solved my problem but i lost lots of data. There is a thread at xda forum, so if somebody have this problem too, you can use it but it's the last possible method to unbrick phone and you will lose everything what's was in your phone.

OPPO A3s - user password removal

I have OPPO A3s need to remove user password somehow, even in recovery mode phone asking for locks creen password to factory reset or flash, phone goes in Emergency Download Mode (EDL) if open recovery, connect USB cable to PC and click on Build number 3 times.
So far i can think of two solutions:
1. Mount Filesystem (this guide) with Qualcomm Flash Image Loader (QFIL), phone is detected in QFIL as HS-USB QDLoader 9008 once in EDL mode, but then what, i dont have MBN file required to mount filesystem can someone help?
2. Flash stock firmware, i can download two, from official website in CPH1853_11_A.31.qzip which i can extract, but then what?
Other firmware is unofficial in Oppo_A3S_CPH1853_11_A.21.ofp format this cannot be flashed by any tool i know of, there is info online that OFP file can be converted to proper format for QFIL (with scatter file and xml) by software+usb dongle (Miracle Box, UFI Box), but they are not free.
P.S. I am noob please help.

Hello

hello , does anyone have oppo a3s download certificate, that the only thing standing between me and unlocking it

oppo with new security needs to open the phone made jtag or isp connection direct to cpu to erase pattern

touji said:
oppo with new security needs to open the phone made jtag or isp connection direct to cpu to erase pattern
Click to expand...
Click to collapse
why here is no loader for oppo A3s Like other QUALCOMM devices

LG W41 (LM-K610IM) dead bricked by my stupidity. Could it be somehow revived?

Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.

Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient

Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore

The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers

you should be able to repair preloader from bootrom mode (BROM)

How to enter bootrom mode. I am sorry if it is a noob question

Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html

Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved

you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.

Hard Bricked oneplus 8t not starting EDL mode

Hi everybody,
I've Oneplus 8t kb2003 updated to the last ota firmware 13.1.
I tried to downgrade it to 13 by flashing full OTA payload.bin using fastboot enhance app but unfortunately the device is bricked.
Usually when such thing happen I boot the EDL mode and use msm tool to unbrick it which worked for me couple years before but for some reason the device is not detected at all on EDL mode!
The device manager not showing any thing called qualcomm even the msm tool not detecting any thing.
I tried to redownload the qualcomm driver and followed all instructions in this link , used 3rd party cables and the original cable and changed ports but nothing happens
It's like the phone is completely dead
any ideas how to get out of this mess ?

Reo0o said:
Hi everybody,
I've Oneplus 8t kb2003 updated to the last ota firmware 13.1.
I tried to downgrade it to 13 by flashing full OTA payload.bin using fastboot enhance app but unfortunately the device is bricked.
Usually when such thing happen I boot the EDL mode and use msm tool to unbrick it which worked for me couple years before but for some reason the device is not detected at all on EDL mode!
The device manager not showing any thing called qualcomm even the msm tool not detecting any thing.
I tried to redownload the qualcomm driver and followed all instructions in this link , used 3rd party cables and the original cable and changed ports but nothing happens
It's like the phone is completely dead
any ideas how to get out of this mess ?
Click to expand...
Click to collapse
Install all the necessary drivers and use MSM tool to restore your phone.
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
P.S: Don't use fastboot enhance app, as it wasn't updated for quite some time and was reason of bricking several phones after flashing.

If you used Fastboot Enhance it could have flashed the wrong xbl file for your RAM type. If is it so, the only thing you can try is a deep flash cable or shorting the test pins on the motherboard.