So I am trying to use Naman's recovery tool from the oneplus forums (I am sorry but I cannot link it) but when I get to checking my phone in the device manager, it says it is Android HS-USB QDLoader 9008 (COM9) as opposed to what it should be, Qualcomm HS-USB QDLoader 9008 (COM10). Does anyone know why this is happening and how to fix it? in its current state, I cannot run the recovery software.
I remember that in device manager you can change the coms but com9 might be taken so you need to change that first.
It's been long time since I don't do that
Sent from my ONE A2005 using Tapatalk
1439soccerdude said:
So I am trying to use Naman's recovery tool from the oneplus forums (I am sorry but I cannot link it) but when I get to checking my phone in the device manager, it says it is Android HS-USB QDLoader 9008 (COM9) as opposed to what it should be, Qualcomm HS-USB QDLoader 9008 (COM10). Does anyone know why this is happening and how to fix it? in its current state, I cannot run the recovery software.
Click to expand...
Click to collapse
I believe, you have installed the Qualcomm Drivers. If you haven't follow the procedure in my thread on how to install it the correct way.
Now considering, you have installed it, First restart your machine into Test Mode (Driver Signature Enforcement must be off). Then head over to Device Manager and right click Android HS-USB QDLoader 9008 (COM9) -> Update Driver -> Manually Select from list the correct Qualcomm driver. You needn't worry about the COM port as it changes depending on machine and the plugged USB port.
Follow my guide from scratch if required as it is the procedure followed by OnePlus L2 Support Team themselves.
Related
I am the OP of this project thread, but it seems that only I who managed to revive my YU from "Qualcomm HS-USB QDLoader 9008" mode. I don't know how your business works, but I know that the guide, if it really works, would extremely helps your business because you don't have to send new replacement each time YU Yureka's owners brick their phone. However, it would be a different story if you just send back those brick phone to Coolpad (Yulong), by saying that they are defective goods.
But if it really helps, I'm challanging YU's official to join the above mentioned project thread, by conducting a Controlled Brick. The word "controlled' here means we control the brick to know what "9008" mode the phone are experiencing, include the symptoms, etc. This would be useful to complete project thread that managed by me, where eventually will helps other YU's member debricking their own phone without asking your company for new replacement.
All you need is two good healthy phone (we named it YU-A and YU-B), and do this:
Download all the attached zip files
Flash the DDR.bin found in DDR.zip via fastboot to YU-A, and reboot. PLEASE REBOOT THE PHONE WHILE STILL CONNECTED TO PC RUNNING WINDOWS.
Run BrickToOld9008.bat found in BrickToOld9008.zip to YU-B. PLEASE REBOOT THE PHONE WHILE STILL CONNECTED TO PC RUNNING WINDOWS.
Please post all the symptoms experience by both phone here.
If my hypothesis in my project thread are true, YU-A, upon reboot while connected to PC, would vibrate endlessly and Windows would detect its as "Qualcomm HS-USB QDLoader 9008" and also detect its eMMC as "Qualcomm MMC Storage USB Device". Whereas YU-B, Windows would only detect it as "Qualcomm HS-USB QDLoader 9008", without "Qualcomm MMC Storage USB Device".
@tirta.agung Can I know what's the use of DDR.bin ??
And, how did you create that custom DDR.bin, or is it from some other device's firmware?
Thanks
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
The site listed above is all the information I currently have on my problem. I know enough to understand a bit of what's going on but I'm no coder or hacker. I've dabled (meaning rooting S3 Straight Talk, Nexus 7, and S7 Edge).
So my phone is black screen, cannot boot/won't boot. It's an S7 Edge so I'm not pulling the battery out since it won't be water-proof then.
+ I cannot boot into bootloader
+ I cannot boot into recovery
+ Nothing lights up, the LED indicator, the screen, buttons, all unresponsive.
+ ADB won't recognize my phone currently so I can't use that
+ Odin won't recognize the phone so I can't use that
My S7 Edge *plugged into my pc* comes up as "RELINK HS-USB QDLoader 9008 (COM 7)" under 'Ports (COM & LPT)' in DEVMGMT.MSC (Device Manager).
I installed the drivers for Qualcomm following the tutorial from the site above. My phone is now recognized as "Qualcomm HS-USB QDLoader 9008 (COM 7)". I cannot find a BACKUP.IMG of my device since I don't know if that's what I'm supposed to be looking for ("BACKUP.IMG") or if it's just a "compiled" version of the five Odin-flashable images I downloaded.
So, copied from their website;
"Guide, if you are NEW “Qualcomm HS-USB QDLoader 9008” MODE
If you are that lucky person, (I'm not) who is stuck in the NEW “Qualcomm HS-USB QDLoader 9008” mode, to be honest, the steps to be taken are a lot easier. However, you need somebody having the same phone as yours to upload your device’s complete eMMC image for you."
So I guess what I'm posting this for is to find out
1.) if anyone else is having similar issues
2.) if there have been any successful attempts at using this method to recover from hard brick
3.) if someone could go waaaaay out of their way to give me their eMMC file
^ I don't think it has to be a Sprint phone, I just need it to boot into bootloader (I THINK)
I'll update with my progress below!
So I contacted JTag repairs and my response is as follows:
"Hello ------ and thank you for contacting me.
No problem for the questions ...but unfortunately I have a short answer :
The S7 Edge uses UFS Memory instead of Emmc memory, there are no JTAG tools that can communicate this UFS memory...this means it cannot be unbricked with JTAG or similar tools."
So here's the information for anyone else. You'll need a program that can communicate to a hard bricked S7 Edge and you'll need a UFS image backup of a functioning device.
Special thanks to @godpowerrr for trying to help me out with it.
Notes: don't hard brick your S7 yet! Lol.
Have you found any solution? I'm also stuck in the same situation with G935A S7 Edge (AT&T variant)
Edit*** I fixed it****
no bootloader, recovery or system, its also listed as unkown device on device manager.
i had it unlocked bootloader. and had magisk installed. but i made error of relocking.... i used the axon 7 tool.
Please i really need help maybe even remote desktop. and ill even pay i can't lose this phone i paid way too much for it
okay i have fast boot
WADE13x said:
no bootloader, recovery or system, its also listed as unkown device on device manager.
i had it unlocked bootloader. and had magisk installed. but i made error of relocking.... i used the axon 7 tool.
Please i really need help maybe even remote desktop. and ill even pay i can't lose this phone i paid way too much for it
Click to expand...
Click to collapse
Why did you lock it? There are a bunch of warnings everywhere. you couldn't have missed all of them...
Well try to get into EDL, maybe you can use MiFlash to fix it. But I can't help you more if you don't tell me what model it is...
Choose an username... said:
Why did you lock it? There are a bunch of warnings everywhere. you couldn't have missed all of them...
Well try to get into EDL, maybe you can use MiFlash to fix it. But I can't help you more if you don't tell me what model it is...
Click to expand...
Click to collapse
its a A2017U
miflash doesnt work
WADE13x said:
its a A2017U
miflash doesnt work
Click to expand...
Click to collapse
But what mode is the phone in when you put it in EDL?
Put the phone in EDL and go to Device manager, open the 'Ports (Com & LPT) tab', it should appear either as "Qualcomm HS-USB QDLoader 9008" or as "ZTE DFU interface". If the latter, you have to follow the 4th categ brick repair manual. And if it appears below 'USB devices' as 'QUSB_BULK', you should uninstall the driver (and tick 'delete driver software too') and restart EDL (hold the 3 buttons until the Device Manager spazzes
Choose an username... said:
But what mode is the phone in when you put it in EDL?
Put the phone in EDL and go to Device manager, open the 'Ports (Com & LPT) tab', it should appear either as "Qualcomm HS-USB QDLoader 9008" or as "ZTE DFU interface". If the latter, you have to follow the 4th categ brick repair manual. And if it appears below 'USB devices' as 'QUSB_BULK', you should uninstall the driver (and tick 'delete driver software too') and restart EDL (hold the 3 buttons until the Device Manager spazzes
Click to expand...
Click to collapse
i can't even see it showing up
https://photos.app.goo.gl/SdqJGWGkBE9TYxfE3
What do you make of this?
Turn off your phone. Connect to PC your device. Press volume up+down+power button for a while. You'll hear a sound from PC and check notification light. It should blink for one time. Then release buttons and let us know what do you see on device manager.
WADE13x said:
https://photos.app.goo.gl/SdqJGWGkBE9TYxfE3
What do you make of this?
Click to expand...
Click to collapse
What do I make of that? That's fastboot. I asked you to get to EDL. so nothing
If you want help you need to post more then once an hour and give us the info requested.
lafester said:
If you want help you need to post more then once an hour and give us the info requested.
Click to expand...
Click to collapse
sorry a friend needed me, setting up edl now
it says: unknown usb device (device descriptor request failed)
i got the right driver
Choose an username... said:
But what mode is the phone in when you put it in EDL?
Put the phone in EDL and go to Device manager, open the 'Ports (Com & LPT) tab', it should appear either as "Qualcomm HS-USB QDLoader 9008" or as "ZTE DFU interface". If the latter, you have to follow the 4th categ brick repair manual. And if it appears below 'USB devices' as 'QUSB_BULK', you should uninstall the driver (and tick 'delete driver software too') and restart EDL (hold the 3 buttons until the Device Manager spazzes
Click to expand...
Click to collapse
i have it in Qualcomm HS-USB QDLoader 9008
whats the next step?
WADE13x said:
i have it in Qualcomm HS-USB QDLoader 9008
whats the next step?
Click to expand...
Click to collapse
Run MiFlash and flash a FULL_EDL package
You have to find one for the A2017U, you can't use packages for the A2017 kr the A2017G or you'll mess up even more
Hello everyone.
I bought a oppo a37 i looked for the root, i did not find a good frimeware for my phone, then i downloaded Qualcomm Premium Tool.exe, after opening the program i got go to the GENERAL section and I clicked [reboot option 9008 to 9006] then my phone no longer lights up. and when I mount it via usb on my pc it detects it as ( Qualcomm hs-usb qdloader diagnostic 9006 ) ,not (Qualcomm hs-usb qdloader 9008), i do not know what to do how to flash it, I only fond frimeware of MSM8936 While my phone is an MSM 8916 ... please help me, I am staying without Cell Phone.
PS: when my pc detects it as an Qualcomm hs-usb qdloader 9006 when I hold the power key it becomes an Qualcomm hs-usb qdloader 9008.
Firstly, my phone don't boot in any mode(hardbricked), no display, no vibration, no fastboot, no recovery (even tried shorting 2 - 6 pins), just showing red light when connecting to pc/charger. Earlier, it was showing as "Qualcomm HS-USB QDLoader 9008" in device manager, so after researching on it, I found that I can flash stock rom using qfil tool (used files provided here). Then I tried flashing it using qfil, the process stopped at dowloading firehorse file. "Qualcomm HS-USB QDLoader 9008" in device manager, automatically, disappeared and after then its showing "Unknown USB Device (Device Descriptor Request Failed)" in device manager.
Now, I tired connecting phone with all key combinations, shorting pins, reconnecting battery, updating drivers, changing ports, but nothing worked. I am not able to connect phone in "Qualcomm HS-USB QDLoader 9008" mode, instead it always shows as "Unknown USB Device (Device Descriptor Request Failed)".
Observations: After flashing, even if phone doesn't boot any mode, it heats up when connecting to usb. (earlier it was not same)
It all happened after interrupted flashing, is there any possible solutions to fix it, making phone detectable as qdloader and also unbrick it?
Your help will be highly appreciated.