I'm one of the lucky people with a mostly dead 128gb pixel in HS-USB qdloader 9008 mode. There have been hints at a way of possibly reloading the chipset firmware to revive the phone enough to get to the bootloader.
There is a list of needed files needed for this: a device firehose file + some .xml files, plus some qualcomm software. Apparently someone has been able to pull these off a Pixel XL, but I'm curious if anyone has succeeded for the Pixel.
I have the same problem. Hundreds of people from Russia are watching this. We have the same trouble!
someone has been able to pull these off a Pixel XL ? i read the thread but i can't found who has get these files (MBN or XML)
MBN and XML files are not stored on device after flashing. This is exactly why they need to be sent by QFIL in order to start any flash (emmc, ufs) programming at all. Before Google or whoever produced a particular Pixel phone for them releases these or they're leaked we're out of luck.
Are there any news on this?
Related
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.
Hello all,
I'm new here, and I searching since many time a solution for my issue.
I'm technician for a company in France, that import professional PDA's from Korean. These devices are strong, and a little "expensive"... So when a customer send me a device for RMA, I need to found the best way for solve the issue, without change parts.
At this time, I'm facing to the issue below :
Lot of devices come in RMA because they can't boot. When I plug the device to my computer, I see Qualcomm HS-USB QDloader 9008 in port COM list.
For the manufacturer (we work direclty with him, no "intermediary"), the only way is to change the main board. OK but I'm not stupid, and I konw that they want sold main boards
I know that the main board is bricked and the device boot in EDL mode, no command can't be send (ex adb), and no screen boot.
Impossible to acces to the bootlader with touch combination.
I have the OS files on my computer (boot.img, emmc_appsboot.mbm, rpm.mbn, NON-HLOS.bin etc...)
The CPu is MSM8916, so I tested with QFIL and Miflash to send send files but nothing good :/ MiFlash told me that the "device is busy", and QFIL told me that there is a Sahara fail error".
So my question is : Can I save the main boards ? I think that there is some people here with more competent than me
For information, I have try 1 year ago with Miflash, and I saved only ONE board with Miflash and Xiaomi OS (I try the OS of the redmi because this phone work with the same CPU) ............. Only one file of the OS was sent by Miflash (before a crash of Miflash), but the main baord was save ^^ So I think that it is really a little problem, maybe an only one partition corrupt ....
I can take pictures of the board if needed.
I downloaded a stock Pixel 4a 5G ROM instead of the Pixel 4a stock ROM and flashed it. Now I'm stuck with a black screen with no ability to get into recovery. My device manager shows "Qualcomm HS-USB QDLoader 9008 (COM6) when connected to my computer. I've been following this thread https://forum.xda-developers.com/t/flashed-pixel-4a-with-pixel-5-image-by-mistake.4267097/page-2 and downloaded the Pixel 4a mbn someone linked but I'm still stuck. Any help would be very much appreciated
I am still amazed in this day of tech that the flasher doesn't compare the signature of the device to the intended device signature of the image file and at least warn if the two don't match!
SmegmaDong said:
I downloaded a stock Pixel 4a 5G ROM instead of the Pixel 4a stock ROM and flashed it. Now I'm stuck with a black screen with no ability to get into recovery. My device manager shows "Qualcomm HS-USB QDLoader 9008 (COM6) when connected to my computer. I've been following this thread https://forum.xda-developers.com/t/flashed-pixel-4a-with-pixel-5-image-by-mistake.4267097/page-2 and downloaded the Pixel 4a mbn someone linked but I'm still stuck. Any help would be very much appreciated
Click to expand...
Click to collapse
were you able to fix it?
My Tab S7 FE wifi somehow got stuck in EDL mode and cannot be booted into android, recovery or fastboot.
It shows as QUSB_BULK_CID on device manager, After installing the qualcomm usb drivers with Driver Signature Enforcement disabled, it now shows as Qualcomm HS-USB QDLoader 9008.
The device is stock, no root or custom rom and only less than 5 months old. Samsung service center, gave an expensive price to repair it claiming that it is display damage and replacing the device it would only get me back like 1/6 of its original value. The device was only dropped twice and Samsung won't cover the warranty (the problem came up long after it was dropped.) Service guy told me that once I dropped the device, the device can still die suddenly afterwards. (totally believable /s). The screen wasn't cracked, only the aluminium frame got dented.
Anyways I assume:
I would need the firehose programmer for the SM7325 chipset. (and for specifically this model I think?, I also don't think anyone have the firehose programmer, please let me know if there is a way to get it)
Download the Samsung stock firmware using something like Frija, extract it then decompress the lz4 files to get the .elf and .mbn files.
Download QPST and then flash those files.
For point 1, is it possible to get the firehose programmer file with another Tab S7 FE? Or is it only obtainable through qualcomm/samsung? I'm clueless when it comes to android stuff.
I don't know what else to do now.
Super unlucky
So I tried to download some of the files from the recent Samsung leak. I found what seems to be the source code for the FE's bootloader, but I'm too noob to understand anything from it.
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
UP. Any thoughts? Any suggestions? Please!
Svobodniy_ said:
UP. Any thoughts? Any suggestions? Please!
Click to expand...
Click to collapse
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
BillGoss said:
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
Click to expand...
Click to collapse
It's complicated, because I tried a lot of ROMs from this forum and from other sources... The main problems, that MSM doesn't see my phone if I want to install ROM through MSM, and Fastboot give a lot of errors, if I want to install ROM through Fastboot...
How I brick my phone? I used file from OnePlus to unlock the bootloader (before it I unlock my phone from T-Mobile). After that all my data was wiped and I decided to change ROM from T-Mobile's to Global. I tried one of the ROM's (I don't remember which, but one from this forum). And my phone became a brick. (previously in my life I reinstalled a lot of ROMs on my Samsung Galaxy S2, Samsung Galaxy S4 - and have no issues, but this time...)
Use EDL to recover. You can get to fastboot, so you are not hard bricked. Make sure drivers are installed properly, try a different computer/cable
Svobodniy_ said:
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
Click to expand...
Click to collapse
It seems, on PC side of things you don't have drivers properly installed, otherwise you wouldn't have
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager.
For the same reason, i presume MSM doesn't see your phone.