Database Users

Lumia 520 DLoad 9008

When I was updating to Windows 10 with registry trick,Lumia 520 bricked.After the gears my phone doesnt open.I am connected phone to usb and pc recognized it as Qualcomm HS-USB Dload 9008.What should I do ?

LeonR30 said:
When I was updating to Windows 10 with registry trick,Lumia 520 bricked.After the gears my phone doesnt open.I am connected phone to usb and pc recognized it as Qualcomm HS-USB Dload 9008.What should I do ?
Click to expand...
Click to collapse
https://sujitintel.wordpress.com/2015/05/08/lumia-520-bricked-here-is-100-working-fix-for-all/. Had same problem as yours and i got mine solved with this tuto. You have to be patient to make it work.

Tried this method after finish this method device recognized as QHSUSB_ARMPRG and I try to boot it now it recognized as HS-USB 9008.Any solution?

LeonR30 said:
Tried this method after finish this method device recognized as QHSUSB_ARMPRG and I try to boot it now it recognized as HS-USB 9008.Any solution?
Click to expand...
Click to collapse
Just keep on trying, bro. Had everything you're saying here... Unplug and plug again till it can be recognized as qhsusb-dload

I tried this method a lot.Nothing change.

I have tried WPInternals Restore Bootloader I have selected hex and ffu click continue and Error - Parsing FFU file failed.

Ok I tried another ffu it restored bootloader but Pc recognized phone as USB Input Device(HID) I looked propertries on Usbdeview vendorid:05c6,productid:f006.

Ok I will try again with another battery thanks for the help.

When I was get phone the 9008 mode I flashed original bootloader from WPInternals.After flash done connection lost and WPInternals stuck at Rebooting phone.

I have 9006, how to get 9008?

A2017U completely stock on b32, miflash won't read it for downgrade

As the title says, I can't get miflash to see my device so I can downgrade and unlock. I've been through every guide most likely and have tried every possible combination I can think of. So my question is, is there anyway I can root and unlock on b32 without edl?
The device works fine, adb, Qualcomm drivers all work as they are supposed to and again, many different approaches to try and get it to work but have had no success getting miflash to see my device in edl.
If it makes a difference I downgraded to b19
I'm still a rookie but far from a newb, is there anyway around me having to hunt down another computer that might make miflash see my device?
Desperate

There's no way man cause u need to unlock your bootloader and bootloader is disabled in b32, so u'll need edl mode in order to flash b19 booltloader to root, if your pc does not recognize your device you might want to try in a different pc or maybe change the usb cable you using that might help

Thanks man. The crazy thing is one of the tool kits can see the device in edl as it checks for the just before it prompts miflash to open but then miflash doesn't see it.

Does your phone show in Device Manager when you put it in EDL mode? If so, what does it say? QUSB_BULK or Qualcomm HS-USB QLoader 9008 (COMn)

I do recall it saying Qualcomm hs-usb qloader once or twice before, one of the times I uninstalled and reinstalled everything. Other than that I recall it saying qusb_bulk. Is that what's killing it for me?
BTW I finally got it to downgrade to b19 through SD card upgrade in the stock recovery but still no luck with miflash recognizing it.

Also I just tried to reboot to bootloader from stock recovery and it still boots me into the ROM :/

I had the "QUSB_BULK" message instead of the Qualcomm Qloader thing a while back.
Took a while to realise I didn't have .NET Framework 3.5 installed. The moment I installed it, MiFlash detected and everything was fine. I would also advice you to make those Qualcomm driver and MiFlash installations in Driver-Enforcing mode.
Also, the bootloader doesn't work as they disabled it on B19 upwards. You can fix it with the FASTBOOT_UNLOCK zip from this thread: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514

Solved!!! I had to install miflash on the D; hard drive not the C; for some odd reason.. Hit refresh and it immediately recognized the device. Happy days people. Happy days

Lol, that's a new one. Glad you got it solved.

Lol me too, literally days... I was beginning to question myself.

A1 Completely dead

Hi, I have (or used to) the GSI Android P Rom on my A1, I saw that an update was avalible for it on the official Telegram group so I decided to download and install it, I wiped vendor as it said and flash the zip files, but I forgot to flash the vendor image again, I rebooted and now the screen is completely black, the phone is dead, the led is not making anything aswell, not even blinking, I'm trying to reboot into fastboot or TWRP with the volume keys but doesn't make anything, I tried to connect it to the PC and it recognizes it as Qualcomm HS-USB Diagnostics 900E (COM10).
I don't know what to do, I'm so worried about this, any idea?

Try to flash stock rom via miflash

If it says Qualcomm HS-USB Diagnostics 900E its not even dead. Lol
What to do next? Stop panicking & use that thing on top of your neck. It'll be fine. (& Use search button in xda, everything is here?)

https://forum.xda-developers.com/mi-a1/help/bricked-mi-a1-qualcom-hs-usb-t3784681

.:Addicted:. said:
If it says Qualcomm HS-USB Diagnostics 900E its not even dead. Lol
What to do next? Stop panicking & use that thing on top of your neck. It'll be fine. (& Use search button in xda, everything is here)
Click to expand...
Click to collapse
Hi, what if now the PC recognize it as an unknown device?
Before your reply I tried to use Qualcomm emmc studio to fix it because MiFlash wasn't recognizing it, Qualcomm did, so I tried to flash the stock ROM but it gave me an error (something about couldn't found ram), I disconected it and it appeared as an unkown device, now not even Qualcomm can recognize the phone, help

Use edl method and you should be good

Flashing with QFIL without opening phone?

Hello everyone, so, unfortunately, my three month old Note 7 got bricked after an unsuccesful ROM flashing.
I have read this guide and set up everythin accordingly before the part where the phone needs to be opened: https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543 ,
I noticed that when I plug in my phone without opening it, it's already in QDLoader 9008 mode so I installed the Qualcomm drivers and all was good. However, I always get a sahara error when flashing the rom using QFIL
Is it necessary that I open my phone to short the test points or should I just keep trying with the different USB ports of my laptop?

My (bricked) Xiaomi MI A1 won't connect to pc

Almost a month ago, my phone ran out of battery so I charged it. When I got back, there was a warning sign and below it said: "the system has been destroyed"
I tried everything I could to flash it, included the official Xiaomi flash tool, but the problem isn't the method itself, but the phone, which it's not being recognized by my pc at all.
When I connect it (In fastboot mode), a notification shows up saying: "The USB device is not recognized", I tried commands, updating the drives, cleaning up the USB port, another USB cable, but nothing worked.
Does anyone know any possible solution for this? Thanks in advance : D

faulty usb cable may be the reason and try edl mode

MrHarveen said:
faulty usb cable may be the reason and try edl mode
Click to expand...
Click to collapse
I have already tried with other cables (and all of them are working for everything except this, so it's the device's fault), and edl mode can only be activated with a computer, so i guess i'll keep trying

Drivers must have been installed multiple times.Delete them and reinstall.
Cheers.

Same problem bro

Hi!
There is a way to enable EDL mode without computer but you'll have to open your phone.
Once opened, you must short two specific test points while connecting USB.
That's how I got out of a bootloop with a locked bootloader.
For the procedure just search for "edl test point mi a1", there are many videos.