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)
Related
Hello,
I think my Samsung Galaxy S4 - GT-9506 is Hard Bricked. Screen is black - regardless if i press the power-button, home and Volume-Down or Up. Odin didn't recognize the Phone. But i installed OPST cause the phone was recognized as Qualcom HS-USB QDLoader 9008. When i start the QPST Software Download Program it tells me that there is a phone connected to COM6 in Download Mode. I think this is a good sign but i don't know how to use QPST and I also have no recovery Image for QPST and my GT-9506. Can somebody help me?
Nobody here who can help me?
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
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.
Hi,
My phone got bricked while installing and update. The phone i hard bricked it shows no signs of life and does not go to Download or recovery mode. Not by button combination or USB Jig.
When I connect the phone to the laptop it shows qualcomm hs-usb qdloader 9008. Is there any way to rescue the phone and debrick it?
Thanks :crying:
Come on people there should be a solution to this crap
Just assuming my phone got an update last night and decided to brick itself. From my side, restarts won't work but I got a USB to recognize Qualcomm HS-USB QDLoader 9008 (COM5). I've tried the software (here) but it doesn't seem to run on the phone, what would be my next step?
Thanks!