Opened bootloader, have installed custom SyberiaOS with sleppy kernel. After trying to join a discord stream, the phone turned off and now it doesn't react on buttons, light indicator doesn't work too. After connecting to PC, device manager showed "QUSB_BULK". I've installed drivers and now it is Qualcomm HS-USB Diagnostics 900E (COM3). Fastboot\adb\edl dont see the phone. Has anyone ever encountered such a thing? What should I do?
Related
I wanted to port MIUI on the Robin, found Xiaomi mi4c, which were good enough to port miui from. downloaded, edited boot, and pushed to phone. then i flashed it, clicked "reboot to system" and then it turnes off. It is not reacting on buttons or that sort of thing. When i connected to pc i had qhsusb.. but after flashing drivers it is qualcomm hs-usb dloader 9008 (COM9). I found nothing about unbricking, not found needed files for QFIL unbrick? Please help with smth
Dear friends
I have a Wileyfox Swift phone bricked after trying to fastboot flash another OS.
Unfortunately It's completely dead now: It doesn't turn on, Its doesn't blink or shows no sign of connecting or recharging... In fact it is the pure meaning of a hard bricked phone
I tried many procedure and none of them worked. The phone is recognized by PC and is shown as "Qualcomm HS-USB QDLoader 9008" in Device Manager (I installed driver).
It would be appreciated soooo much if you could help me with this situation... Please...
I am trying to use the EDL methods that require qualcomm hs-usb qdloader 9008 drivers.
I had 0 luck so far to get the device show up as qualcomm hs-usb qdloader 9008.
I tried several versions of the driver install package I could find, tinkered with LG, xiaomi and others.
My device is Windows x64, 1903.
It's an UEFI device, so secure boot is enabled
Some instructions require you to disable driver signing - which doesn't work with secure boot, I disabled it...
I disabled driver signing...
I installed the certificate...
still nothing.
When booting the device shows up under "Universal Serial Bus devices" as "QUSB_BULK"... when trying to update the drivers, I get "The best drivers for your device are already installed" - Care Suite Emergency Connectivity, which is a Microsoft driver. Uninstalling that one also results in nothing really.
Are there no qdloader drivers for a current OS? Which steps do you take to get the driver working?
My phones do not even seem show up when in EDL mode a this point.
Any help is appreciated.
My first "thing" is to do is to reflash the Alcatel Idol 4s open market properly as the WDRT tool only would allow the T-Mobile firmware to be flashed.
What I eventually would want is a European language supporting firmware with a US based modem/cellular configuration.
My first step is however to be able to flash things at all.
Any guidance is appreciated.
unstall all nokia/microsoft software,driver on pc and install qcom driver again
During the last software update around 2 years back the phone suddenly turned off and it never turned on. Now i want to get this up and running. I have connected it to charger and there are no notification or any changes on the screen. It does not turn on also. When i connect it to the laptop, it gets connected and under the ports option on device manager it shows as qualcomm hs-usb qdloader 9008.
please let me know if there can be anythingdone.
Can i flash the ROM somehow?
Hello,
My device randomly shut down the other day and won't come back to life at all.
It doesn't go into fastboot or recovery mode, it just shows up in windows as Qualcomm HS-USB QDLoader 9008. From what I understand, this means the phone is in "EDL Mode"?
I have tried:
- Letting the battery completely drain and attempt to turn it on
- Using the recovery tools Google provides
- Using android platform tools to trigger fastboot/recovery
Nothing seems to be working at the moment. I am a bit noob-ish, so maybe there's a troubleshooting step I missed?
I'd like to get this device recovered. Has anyone run into this issue and solved it? Any advice is appreciated!
Thanks in advance!
Unfortunately there is no way to recover the device, as the software and files required are not publicly available. You could have it repaired but they will just replace the main board.