Qualcomm Qdloader 9008 Error - Galaxy Note 4 Q&A, Help & Troubleshooting

Can anyone help or atleast explain what is this state i do know that it is some sort of emergency mode for smartphones but the phone is stuck in this state for 2 weeks with no detection in odin software only i see this in the device manager.
I have seen some unbrick threads that suggests me to use the sd card method to unbrick the phone but no matter what i try with button combinations or even putting in the freezer the phone would not go into download mode or even boot up.
So my main question is the SOC of this phone is dead p.s this is what i suppose
Or i am dumb or missing something
p.s The phone does turn on at some point if i leave it overnight but for the past 2 weeks even this is not happening even after removing the battery.
Your help would be apprieciated

Related

[HELP] Bricked Samsung S8 (US T-MO version) with Qualcomm HS-USB QDloader 9008

Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Anyone?! There has to be someone who can help me out here....
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.
Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Display is in like new condition, not even a blemish. No image upon power or on the wireless charging pad, the battery does get a bit warm when charging for few hours.
Yes, I have tried that exact combo for a good 60 seconds but nothing.
Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk
whoamanwtf said:
Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.
Click to expand...
Click to collapse
The reason I commented about root was then someone can get a backup of the eMMC or a backup of the bootloader, so I can flash that, if that possibly fixes it. From what I can understand, something got corrupted and for that reason the device will not boot at all (nothing on the screen), so Odin is out of the question, since the device has to be in the Download mode for Odin to recognize it.
What I have found from further reading is that I can use QFIL (Qualcomm Flash Image Loader) to flash stock firmware since it recognized the S8 on COM port 3 when connected and QFIL recognized "Qualcomm HS-USB Qloader 9008" message, but what I have seen is people using MBN files (firehose.MBN) and an XML file to revive the phones. I've tried looking for those files even within the S8's stock firmware (AP, BL, CSC) but nothing.
Is there anyone who has experience working with QFIL who can guide me or provide with the files I need to flash this device back to stock.
Bisquit-02 said:
Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Appreciate your input but it does charge
taj786 said:
Appreciate your input but it does charge
Click to expand...
Click to collapse
If u can return it go do it, thats not a issue that can be solved here im guessing is a hardware conection/display issue. If u cant reach download mode then i think u cant get help here
This is not hardware issue or anything like it. What youve done, same as I have, is wiped the download and recovery partitions of the phone. QFIL can fix this, but same as you I have not found the required files. I did find the programmer firehose but its an efl. I can not find the meta file it apparently needs. Did you ever fix this
taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises
partcyborg said:
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises
Click to expand...
Click to collapse
Looks like I've done the same thing with S8+ G955F. I was trying to fix an FRP issue and flashed a mixture of Nougat 7.0, combination and CRED BL and now it just shows black screen, can't get to download mode. This was all done with Odin.
Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
Good morning, my S8 and the same happened to me, to downgrade the oreo to the nougat; I did a JIG with resistors; When you download the keys, the JIG does not work on time, then after; I do not know how to say why.
then it means im doomed.. im experiencing the same shiiit
\

Lenovo k6 Power Hard Bricked.

No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
ImSSin said:
I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
Click to expand...
Click to collapse
Thank You ?
I am also trying my best to recover the phone and i will write here so that anyone who is facing this issue can recover his/her Phone.
No Solution found for this.
...
You have to send your Lenovo K6 Power to Lenovo Service Centre and get your Motherboard replaced.
If your phone is in guarantee then you will get free replacement no matter if your phone is rooted but please don't tell about root to them otherwise they will charge money for your small mistake.
what happened?
Do a new install
faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Boss it seems that you have hard bricked your phone so it means it's first boot has been corrupted there is no chance as first boot is mandatory to flash any file, there are some tools like octopus, or Medusa box, they can repair your boot then the phone can be used its just an outside chance 5o get it in workable condition look for some person or Repairing person have this boot repairing gadget,
If this fails too or you have messed up very badly then, last option is mother board replacement, there is no software option to repair by yourself
Help please..!!!!
:crying:
Even I face the same problem...
How do I go to download mode..???
It's stuck at Lenovo screen .... It just turn off on low battery and reboots on long press of power button.. Is it compulsory to have 80% of charge to get into download mode..???
i did the same. it switches on with lenovo logo , shows the os logo animation and its stuck there. when i tried connecting it to phone it showing unspecified device.
i could get into a fastboot mode . but nothing ahead to that. please find me a solution
Help me same issue
faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Did you find any solution for this, present i'm facing same issue, please tell me if you have any solution for this...

SM-950F Hard bricked, JTAG?

Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me
Thanks, I'll give it a shot
ok let me know then
Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??
Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?
Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.

Bricked phone

Hello, i think my phone is completely dead. Here's what happened : i wanted to go back to a stock ROM so i used MiFlash, but it gave me an error really early after a couple seconds (modem flash error i think) and now it doesn't respond. When i connect it to my PC nothing happens (nothing in device manager). The only sign of "life" is that when the battery is low (i think that's the case), the LED starts flashing RED until the phone runs out of juice. Any ideas? I already tried charging the phone all the way up and then discharging it completely(those are the only things that seem to work as they should) but the phone seems completely dead. I had a similar thing happen to me before on my older Xiaomi phone but that time my PC at least managed to detect it in device manager as qdloader 9008 (EDL mode) but that just doesn't seem to work now. Would shorting the test points work to make it go into EDL mode or is it a lost call? The bootloader was unlocked before flashing and i chose the option in MiFlash that doesn't lock it again. Thanks for anything. EDIT: Phone sent to a repair centre.

assistance needed

i attempted to root my zte maven 3 with zpst for at&t and when the device went to restart the screen stayed black and no matter what key combinations i try i cannot get the screen to turn on. The only thing the phone does is connect to the pc and makes that connection noise. it connects as Qualcomm HS-USB QDLoader 9008. does anyone have any advice or suggestions that might help
Did you make any partition backups in QFIL by any chance? If not, I have no idea how one would go about fixing it. What's your bootloader version? I can try to give you my partition backups and you can try flashing it and seeing if it'll boot.
Tbh I should write my own rooting guide, because the existing methods are, quite frankly, ****ty and dangerous. To anyone reading this, please open QFIL and make a backup of all of your device partitions before messing with anything; this is basically creating a bit-for-bit backup of the storage itself, such as the persist partition, userdata, system, etc. I had to buy a for-parts Maven 3 from eBay because I bricked my Maven 3 using the same guide...
And don't use ZPST from now on. You don't need it. Everything can literally be flashed as a partition in QFIL easily. This is how I safely flashed a Magisk boot image (partition) and half-working TWRP recovery partition.
maxwelldad90 said:
i attempted to root my zte maven 3 with zpst for at&t and when the device went to restart the screen stayed black and no matter what key combinations i try i cannot get the screen to turn on. The only thing the phone does is connect to the pc and makes that connection noise. it connects as Qualcomm HS-USB QDLoader 9008. does anyone have any advice or suggestions that might help
Click to expand...
Click to collapse
Your device is in EDL mode. It's the only mode that connects as Qualcomm HS-USB QDLoader 9008, and EDL mode doesn't display anything on your device screen. Just take the battery out for a second and you should be able to boot normally.
I'm going to post a new thread in this forum as soon as I send this, where I'll run down the steps I took to achieve root on my Maven 3 just this morning. I've powered off and booted up about 5 times since rooting and it's still rooted.
I have edl mode no boot no screen no lights, what do do next. I tried removing battery no luck
xecutionkrk said:
I have edl mode no boot no screen no lights, what do do next. I tried removing battery no luck
Click to expand...
Click to collapse
I am unsure of what you can do because iirc i faced the same issue. I have full partition dumps for my current maven 3, some of which (except for example persist) I can send and you can try flashing it using QFIL since your device sounds like it's in EDL mode

Categories

Resources