A Challenge for YU's officials - YU Yureka Q&A, Help & Troubleshooting

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

Related

[Guide] No Boot - No Recovery - No Download Mode Unbrick Guide

No Boot - No Recovery - No Download Mode Unbrick Guide​
Qualcomm HS-USB QDLoader 9008 or Secure booting error (No Boot - No Recovery - No Download Mode) or "QHSUSB_BULK"​
Hi team, if you have come here I'm sorry you are having this problem! But my friend and I have been to hell and back trying to fix this problem and we wanted to share our method of success for any poor soul who is experiencing the same thing! For our situation the USB was unplugged half way through flashing a KDZ or going back to stock firmware and created the No Boot - No Recovery - No Download Mode problem.
This has only been tested on the D855.. Just so you know.​
First off, here are some links which you may need to have a look at if you have not done so already. Most of the bricking problems have already been extensively talked about by people here on XDA. For the method that works, we had to pull information from everywhere and spent a long time looking for the solution.
How to go back to stock - http://forum.xda-developers.com/showthread.php?t=2785089
Link for TOTs and KDZ's from the above thread - http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
The Main Fix for the problem - http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
The G2 version of the fix (for reference if you still have problems 55+ pages) http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
This is your last stop shop if everything is broken and nothing works, involves hardware fix - http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
The problem we encountered several times with all of the described methods above, is that many do not describe important things. While the main fix thread for the Qualcomm HS-USB QDLoader 9008 mode, which is shown in device manager, is very well written and detailed, the programs which are linked in this thread are questionable and haven't worked for many users with some offering to fix for money. We searched the internet and located a working version of the program which worked without giving a "Device was not found in dload trying to flash programmer" like the one provided on the XDA page. Use the links below for a working version from this thread http://androidforums.com/threads/lg-g2-not-turning-on-help.916865/
My first point is if you are having problems with any of the things, CHANGE YOUR USB CABLE or use the stock cable (I know most experienced users know this). The reason for this problem has something to do with different USB cables being made for different purposes and are of different qualities. Having an error on the USB ports gave us only qhsusb_bulk on windows device manager, without Qualcomm HS-USB QDLoader 9008 as well.
If you are still having problems, check your USB ports. It is really important to make sure this isn't the problem or you will be trying to fix this problem endlessly.
First attach the USB cable to the computer. When you plug your phone in, make sure you attempt to enter download mode by holding the volume up button when you plug the USB into your phone. Even though the phone will not enter "Download Mode" It will allow the phone to be detected by your computer (at which point you can release the buttons, it should then show "Qualcomm HS-USB QDLoader 9008" under ports. If this is not displayed you have a problem with the USB cable or port, or your phone is hard bricked and you need to head to the above guide for the hardware fix. If you have followed so far and are wondering what to do from here, once the "Main Fix" guide ends, head over to the "How to go back to Stock" thread above. Your phone should be showing "firmware upgrade" and you can proceed to flash a new updated KDZ on your device then everything will work and your nightmare should be over!
Working Boarddiag - https://drive.google.com/file/d/0BzkqP9M0LLWQUkEyRkZrVHlEbDg/view
Qualcomm USB Drivers (Essential for the aforementioned "Main Fix" above) - https://drive.google.com/file/d/0BzkqP9M0LLWQblF6Vl9OcUkwUDA/view
LG United Drivers (Phone Drivers) - https://drive.google.com/file/d/0BzkqP9M0LLWQUURDTHlYOW5YRms/view
If this helped you to fix your nightmare don't forget to hit the thanks button!
The "Wroking Boarddiag" asks for PW. aside from that, very good find, thanks
detected as qdloader hs usb 9008
board diag- ap check failed device not in downld mode
For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64
Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?
MrMuli said:
Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?
Click to expand...
Click to collapse
I just fixed my Lg g3 with this method. Not sure if it will work with AndroidNetUSB
Would like to help for any difficulties. (e.g. Not able to find TOT file) etc.
Thanks to @Orcam & @kryptonite
This did not work. Here's what I tried:
1. Without battery
2. Changed drivers as @shawe_ewahs says
3. With battery
4. Admin and non-admin
5. Changing COM ports
But, every time, I get:
"Device was not found in dload trying flash programmer
TEST Aborted!!"
My LG G3 D851 is in Qualcomm HS_USB QDLoader 9008 (COM 41) so I know it is in the correct mode! Agh, it is very frustrating. Any help is appreciated. Thanks.
Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*
furiify said:
Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*
Click to expand...
Click to collapse
No problem. Hope it didn't take you as long as it took us to find all the right stuff
I'm having this problem, but when I plug in without a battery all that shows up in device manager is "Unknown USB Device (Device Descriptor Request Failed)". I tried to do the hardware fix and was able to force the device to reboot by touching the pins. But all that happens is it disconnects and reconnects from USB without being detected properly.
I should note that when I turn the phone on right now, it stays stuck in the initial LG G3 splash screen. When I plug in without a battery, it shows an empty battery icon with a wire and a triangle question mark.
Any idea what I'm doing wrong? I think if I can just figure out how to get my machine to detect my phone as the qdloader hs usb 9008 I can figure out the rest.
The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.
Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.
Dr1t3r said:
The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.
Click to expand...
Click to collapse
phaim said:
Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.
Click to expand...
Click to collapse
Sounds like it may be a problem with windows from what you two have said. Perhaps compatibility mode is the way to go. They did release a pretty major windows 10 update since I posted this guide.

s4 i9506 - Relink HS-USB QDLoader 9008, No Download Mode/No Recovery Mode, why?

Hi there,
Well, I am a samsung s4 i9506 owner. This weekend, I actually hard brick my phone and now it doesn't respond. It doesn't even start, No screen flash, No led flash. When I try to connect it to PC, it says Windows cannot recognize this device. However, I figured it out how to connect my phone to pc, its by holding the power button for one minute and then plug in the usb cable, which is connected to the pc on the other end. Now it shows, RELINK HS-USB QDLoader 9008 (Com 6). I tried everything whichever I could found after google search but nothing pls help
I think the people in the below thread have the same problem.
http://forum.xda-developers.com/galaxy-s4/help/samsung-s4-fullbrick-t3284237

Qualcomm 9008 bricking recovery error

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.

S7 SM-G935P (Sprint) Hardbricked "Qualcomm HS-USB QDLoader 9008"

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)

Nokia 6.1 TA-1045: Bricked, recognized in Qualcomm mode when plugged in

So my Nokia 6.1 (TA-1045) randomly bricked and now the phone does not boot up at all. No screen, no sounds, no charging noise.
When I plug it into my Windows PC, the PC does recognize that it is plugged in. However it shows up as "Qualcomm HS-USB QDLoader 9008".
The best resource I could find with a similar issue was this thread, but for the LG 70+ devices. Is there any way for me to fix my bricked phone? Or am i out of luck?
abc617 said:
So my Nokia 6.1 (TA-1045) randomly bricked and now the phone does not boot up at all. No screen, no sounds, no charging noise.
When I plug it into my Windows PC, the PC does recognize that it is plugged in. However it shows up as "Qualcomm HS-USB QDLoader 9008".
The best resource I could find with a similar issue was this thread, but for the LG 70+ devices. Is there any way for me to fix my bricked phone? Or am i out of luck?
Click to expand...
Click to collapse
So if it's showing as qc 9008 mode than it's a good sign.. it means it's going to edl mode.
What you need to do is find a qfil flashable firmware (just google) and flash it on your device through qfil flash software.

Categories

Resources