Hi, I own a BS2 Pro Global and it suddenly froze and shutdown, it happened several times and now it's completely dead. It won't charge and boot up. When I connect it to a PC my PC detects it but no signs of power from the device.
In my 'device manager' it says "Qualcomm HS-USB QDLoader 9008 (COM#)"
it's also detected by Mi Flash tool but I don't have anything to boot from.
*If you guys know where I can download a fastboot file or if you have can you please share it with me T_T
did
jlrivera1125 said:
Hi, I own a BS2 Pro Global and it suddenly froze and shutdown, it happened several times and now it's completely dead. It won't charge and boot up. When I connect it to a PC my PC detects it but no signs of power from the device.
In my 'device manager' it says "Qualcomm HS-USB QDLoader 9008 (COM#)"
it's also detected by Mi Flash tool but I don't have anything to boot from.
*If you guys know where I can download a fastboot file or if you have can you please share it with me T_T
Click to expand...
Click to collapse
did you solve your problem?
Related
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit
daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible
i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!
A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted
The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.
i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
Hi,
I was using my Xiamoi Mi A1 as usual, and suddenly everything became laggy and the phone finally shut down.
The problem is that it may have rebooted in a special mode as far as the LED blinks when I plug the battery charger. Moreover when I connect the phone to my PC it reads: "qualcomm hs-usb qdloader 9008".
I don't know how to get out of this...
Oh! and I did not modify anything: no root, no custom ROM, nothing...
thank you for reading my boring request
Toryuu.
Toryuu said:
Hi,
I was using my Xiamoi Mi A1 as usual, and suddenly everything became laggy and the phone finally shut down.
The problem is that it may have rebooted in a special mode as far as the LED blinks when I plug the battery charger. Moreover when I connect the phone to my PC it reads: "qualcomm hs-usb qdloader 9008".
I don't know how to get out of this...
Oh! and I did not modify anything: no root, no custom ROM, nothing...
thank you for reading my boring request
Toryuu.
Click to expand...
Click to collapse
Have a look here: https://forum.xda-developers.com/mi-a1/help/bricked-xiaomi-mi-a1-stuck-edl-9008-t3782688
kudos1uk said:
Have a look here: https://forum.xda-developers.com/mi-a1/help/bricked-xiaomi-mi-a1-stuck-edl-9008-t3782688
Click to expand...
Click to collapse
So I tried to flash it many times, but there is an error : "cannot recieve hello packet". I even disabled driver signature enforcement, but it does not help.
If flash with disabled driver signature enforcement did not work you will need to try some of the more radical suggestions in that thread unless you can get it to a service center under guarantee.
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
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.
Hello,
I messed up the phone and I don't know how to solve..initially it was stuck at logo screen and I tried some solution found online and now it's in EDL mode (I think).
I connected it to PC and Win10 recognized it as Qualcomm hs usb qdloader 9008..
Someone can help me please?
thank you