Database Info

Nexus 5 QPST/QDLoader Mode

So, messing around with kernels and stuff, I wound up with a bricked device (wouldn't turn on, no response to anything, etc [I did eventually manage to get it functional again through a combination of button mashing and praying])
However, when plugging it into my computer, it showed up as "Qualcomm HS-USB QDLoader" which seemed interesting.
Searching the internet, I found several things. The QPST (Qualcomm Product Support Tool) Software suite, as well as other less useful links about the LGFlash tool, etc.
The programs also makes reference to debug and other modes, but there isn't a lot of documentation on the internet.
What I want to know is, is there a way to put the device back into the QDLoader or other QPST related modes so as to either update the firmware again, or just make backups for future use?
If there is, this seems like it would be a great tool for undoing any damage to the phone that isn't hardware related (the documentation says this part resides on a read only chip[which it seems fastboot doesn't])

It looked like you borked your phone to the point where there was nothing recognizable as Android left on it. I don't know anything about this loader but based on my past experiences dealing with proprietary OEM tools (Samsung KIES), I hope I never find myself in a situation where I'd need to learn. :crying:

Turn off your phone. Press all the keys if nothing happens your phone bricked. If you end up qualcomm 9008 mode we cant do much, because we dont have a working flash programmer and a working bootloader which would be flashed to the phone with the flash programmer. You can do 2 things. Replace your motherboard, or find the emmc pins on the motherboard to get direct acces to the storage then with a modified sdcard reader you could have access to the storage content then you could restore the bootloader. This is pretty hard method almost impossible.
If you have qualcomm 9006 mode then you can restore the bootloader with any kind of linux, because in 9006 mode the phone acts like a external hdd.

May I ask how exactly you messed around with the kernels to get this? Did you flash an incompatible kernel or something?

It sounded like he resolved his issue and wanted to know if this hidden mode can be used.

Wakamatsu said:
It sounded like he resolved his issue and wanted to know if this hidden mode can be used.
Click to expand...
Click to collapse
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off

It works!
bitdomo said:
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off
Click to expand...
Click to collapse
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...

caffeinatedangel said:
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...
Click to expand...
Click to collapse
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.

Well darn
bitdomo said:
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.
Click to expand...
Click to collapse
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!

I've never bricked my phones that bad man when I was a noob I installed safestrap on a device with an unlocked boot loader and tried to flash a ROM it didn't work out to well,man that was about two years ago

caffeinatedangel said:
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!
Click to expand...
Click to collapse
There were two placed where qualcomm documentatiosn could be found. One was a chinese forum where you have to be veteran or admin to get access to the files. This forum not exist anymore. The other is a chinese ebay like website where they are selling qualcomm documents for 3000 usd.
If you search for msm8974 boot flow or sahara protocol you will find file names for qualcomm pdf documents. Sadly just file names no download possibilty.

Flashed wrong bootstack/modem, Pls HELP unbrick m8

Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!

HTC m8
danielr324 said:
Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!
Click to expand...
Click to collapse
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0

ok_then_so said:
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0
Click to expand...
Click to collapse
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk

beaups said:
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,

danielr324 said:
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,
Click to expand...
Click to collapse
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk

dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I got it to be recognized on a computer again, and windows installs a driver. The name of the device is forge hs-usb qdloader 9008.
I tried the all in one 2.0 kit, adb sideload, etc but anything I try I get a "device not found".
I think I am giving up unless someone finds a way to unbrick this kind of severe problem in the future. I also researched a bit on google, and there's a way to unbrick the LG G2 when it's seen as forge hs-usb qdloader 9008, which is known as a board unbrick. I found nothing for the HTC m8 though.
We tried all we could Thanks all for the help, it's very much appreciated! You guys are the best and this forum is awesome. I also ordered a new phone...and I will root it too

dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.

BadUsername said:
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.
Click to expand...
Click to collapse
Not likely with the nand used on this device.
Sent from my HTC6535LVW using Tapatalk

Samsung Galaxy Tab 2 10.1 SGH-I497 AT&T Bricked!

Hi all,
I own a Samsung Galaxy Tab 2 10.1 SGH-I497 (don't forget, its that specific model) that I recently tried to flash a Kernel through CWM recovery. Unfortunately, by the time I realized I shouldn't do such a thing, it was too late and I pressed the wrong button to select "go back". Now my device is stuck in what I would assume is a boot loop, without any screen output. However, I can turn the tab off and my computer will make the "disconnect" noise, alike when a flash drive/USB is unplugged. It also makes a "connect" noise when the tab turns itself back on less than 5 seconds later. Since I need an IMEI number for the KIES firmware reset, I cannot fix this with KIES, as I have no access to my android OS and it is not written on the back plate (for some ungodly reason, thanks Samsung!) I do have an SD card and a cable, and also have ODIN installed, so any suggestions would be great Honestly I don't think it can get any more F*cked right now, so if you guys have a clue on what to start with, shoot!
Also, if ANYONE has a way to find the IMEI number, It would be VERY, VERY appreciated!~
Thanks!
-Tekk

Anyone? I have found out it is connecting/disconnecting to my PC as a "Qualcomm HS-USB QDLoader 9008 (COM3)", so I am going to attempt to use a qualcomm flash tool.

BUMP!
TheTekkitBoss said:
Anyone? I have found out it is connecting/disconnecting to my PC as a "Qualcomm HS-USB QDLoader 9008 (COM3)", so I am going to attempt to use a qualcomm flash tool.
Click to expand...
Click to collapse
I'm having this exact issue. Did you figure it out? Anyone? :silly:

I don't have this specific model but have you tried flashing the factory image using odin? Boot into download mode and connect it to your PC then odin should display "Added!" Then locate your firmware package and flash it
Sent from my espresso3g using XDA Labs

erasmosis said:
I'm having this exact issue. Did you figure it out? Anyone? :silly:
Click to expand...
Click to collapse
flashing a custom kernel that is not meant for the same device, is fatal in most of the cases. still if your device can get into either recovery or download mode. praise the lord.
there is a detailed guide in my signature below, where I had tried explaining most of the parts.

billysam said:
flashing a custom kernel that is not meant for the same device, is fatal in most of the cases. still if your device can get into either recovery or download mode. praise the lord.
there is a detailed guide in my signature below, where I had tried explaining most of the parts.
Click to expand...
Click to collapse
Thats exactly it... no download mode, no recovery mode.

erasmosis said:
Thats exactly it... no download mode, no recovery mode.
Click to expand...
Click to collapse
If none of those two modes work, then I'm sorry because now you have a pretty expensive paperweight now Only a JTAG can save it now
Sent from my espresso3g using XDA Labs

Do you have adb installed? You could try spamming adb reboot recovery when it connects for that brief moment.
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Sprint Samsung S8+ qualcomm mode

Hi my name is Miguel and im new to xda and i have a serious problem so i bought my phone and i was using it a mp3 and stuff since i live over seas i tried to region unlock it and in the process bam phone restarted and nothing but a black screen i plug in my phone to my charger nothing happens i plug it in to my pc something happens but not on the phone but on the pc it started downloading drivers i can tell you what the bubble said because i came to europe for vacation and im staying here for a while but a friend of mine said your phone lost his boot-up and it wont do anything unless you buy a medusabox and get all the files im buying the medusabox or whatever but where can i get the files from he told me you need 4 files with ones are they any ideas?

What were you doing to region unlock it?
If you hold down the bixby, power, and volume down buttons, can you get into download mode?

I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.

ragarcia87 said:
I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.
Click to expand...
Click to collapse
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+

The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
huawei asker/fixer said:
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+
Click to expand...
Click to collapse

Brittanyporter said:
The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
Click to expand...
Click to collapse
This is very old but no all bricks dont leave in edl the devices also have groind points. All of us that tested the edl repair use qfil or the recovery script which i use on mine. You need a bit more than just the bootloader for repair. A whole barrage of sperate partitions as well as the programmer xml

https://drive.google.com/file/d/1CFRc7RljFHX1oN4WdDLUR3b3BmaGnNAc/view?usp=drivesdk

help !. Bricked OP8 t-mobile unlocked

Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks

kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks

kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !

solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF

JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.

Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.

JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......

kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha

JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/

kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you

kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.

kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol

JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.

kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!

JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol

I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] 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