Database Users

Bricked Elife E7, Human Interface Device (HID) Detection Help

Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:

Steps Parku said:
Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Click to expand...
Click to collapse
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck

Still Not Helpful.
andresplata94 said:
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Click to expand...
Click to collapse
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks

did u fix it??

U can fix ? I have the same problem since three weeks and nothing... this a a sh*t... only recognized by HID... In other ocassion before of this, i can flash my Gionee but now i cant:crying:

Another one here who saw how the phone bricked after being flashed with GnQc, now when I plug the Usb on the Pc or with wall charger, the red light keep lit and it seems like it will like this forever. I am thinking of trying to get out the screen and disconnect the battery, seems like the phone is stuck on some strange mode.
Thanks.

This feel that not have solution....

Can any one fix it ?

i also got stuck . have given to gionee care they are unable to figure what was the actuall problem

Steps Parku said:
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
Click to expand...
Click to collapse
the problem for me is that it have recovery stock english(e3) and i can't do anything...
anyone fixed the problem? i have my gionee bricked....

Bricked G2, more information is in the post

Hello guys,
I need help to unbrick my Lg G2 d802 32GB. First of all i rooted the phone and then flashed TWRP on it, because i wanted to install Cyanogenmod. The install instructions told me to go into recovery mode. As i wanted to do that, my phone needed a restart and it didnt start anymore.
I cant go into recovery mode or download mode, nor can i do anything with it. I have already tried many solutions, but none of them worked.
It would be really nice if you can give me some answers on what i could have done wrong and help me get my phone back to normal. It doesnt matter if it gets fully wiped, because i backupped everything before i wanted to install cm.
Here is a list of the links i have already tried:
http://forum.xda-developers.com/showthread.php?t=2582142 The problem with this is, that the phone connects and disconnects over and over again and you dont have time to switch out the broken things. Im using Ubuntu 15.10 if that helps. Is there any way to make Ubuntus drivers act like Windows drivers, because on Windows its connected all the time and doesnt disconnect?
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 The problem with this is, that the phone doesnt get shown under the name "Qualcomm HS-USB QDLoader 9008" mode but under the name "Qualcomm hs-usb diagnostics 9006" . How can i get it into this mode?
The other methods are requiring recovery or download mode in which i cant go.
Thanks in advance for you help!!

Gundeltraud said:
Hello guys,
I need help to unbrick my Lg G2 d802 32GB. First of all i rooted the phone and then flashed TWRP on it, because i wanted to install Cyanogenmod. The install instructions told me to go into recovery mode. As i wanted to do that, my phone needed a restart and it didnt start anymore.
I cant go into recovery mode or download mode, nor can i do anything with it. I have already tried many solutions, but none of them worked.
It would be really nice if you can give me some answers on what i could have done wrong and help me get my phone back to normal. It doesnt matter if it gets fully wiped, because i backupped everything before i wanted to install cm.
Here is a list of the links i have already tried:
http://forum.xda-developers.com/showthread.php?t=2582142 The problem with this is, that the phone connects and disconnects over and over again and you dont have time to switch out the broken things. Im using Ubuntu 15.10 if that helps. Is there any way to make Ubuntus drivers act like Windows drivers, because on Windows its connected all the time and doesnt disconnect?
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 The problem with this is, that the phone doesnt get shown under the name "Qualcomm HS-USB QDLoader 9008" mode but under the name "Qualcomm hs-usb diagnostics 9006" . How can i get it into this mode?
The other methods are requiring recovery or download mode in which i cant go.
Thanks in advance for you help!!
Click to expand...
Click to collapse
some went bad when you flashed your custom recovery..
you can try 2 things srk tools and do the nuke download..
maybe you need to short ciscuit your motheboard to get download mode.. seach for it.

Bricked phone but can still get into EDL mode

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

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

unbrick "dead" tablet Lenovo TB 4 10.1 (X304F/L)

I managed to identify the test point on the motherboard.
This allows the tablet to switch from Qualcomm HS-USB Diagnostics 900E driver mode to Qualcom HS-USB QDLoader 9008 mode.
My tablet could not be booted into bootloader, recovery or system.
Button vibration did not work.
The tablet only logged on to a PC with the Qualcomm HS-USB Diagnostics 900E driver.
The EDL cable did not help and the buttons of the 900E driver only restarted.
Photos and brief instructions I posted on the Russian forum here:
http://4pda.ru/forum/index.php?s=&showtopic=849554&view=findpost&p=90398828
I attach the photo here.
Only one hidden test point is connected to the metal frame (needle).

My tutorial on the Russian forum has been updated, missing the source file for MiFlash.
Today it was added.

Downgrade from Android 8.1 to 7.1.1 is possible!
Applies to tablets with unlocked bootloader.
The entire factory clean version must be reinstalled.
Use the same installation and tools as in the introductory link.
It is necessary to install in EDL mode.
To start EDL mode (driver 9008) from a working tablet, follow these steps:
1) Turn off the tablet
2) run the device manager in windows - ports
3) run and set up MiFlash (firmware path,option "save user data")
4) connect tablet to computer (USB)
5) hold all three buttons on the tablet (power+volumeUP+volumeDown) until the 9008 driver loads in the windows manager
6) run "refresh" in MiFlash without delay and immediately afterwards "flash"
It is important to start recording as soon as the driver is loaded, otherwise the input will close even if the driver remains loaded!
If there is a delay in recording, the EDL mode may close and the recording will not work.
In this case, you must start by disconnecting the tablet and turning it off.
The restored tablet remains unlocked (if you have unlocked it previously) while Lenovo updates work.

Hello i want to contact you are you still alive
I want to unbrixk my tab i accidentally deleted aboot.img

Hello i want to contact you
I want to unbrick my tab are you available???

Just to clarify, the test points on the board are the points you see on the board labeled "FORCE, VDD, TX, RX" and can be different sizes.
One such point was hidden under a folded out frame and that is the correct one. Connect this point with a needle to the metal frame and follow the order of operations in the instructions.
MiFlash - recommended:
Download in progress... | Xiaomi Tips
Thank you for downloading. Your download should start automatically in a few seconds.. Download FAQs Broken download link? Let us know. Is the file safe
xiaomitips.com
System:
TB-X304L_S000035_170703_ROW_QFIL.rar | by yulianto adikragil for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Follow the procedure.
After loading 9008, release the checkpoint as soon as possible.
I used XiaoMiFlash (beta).
You need to prepare XiaoMiFlash before taking action.
"Refresh" and "flash" should start immediately after disconnecting the breakpoints.
The path to the XiaoMiFlash firmware should only be "bat" files, not "images".
The fact that the 9008 driver loads in Windows indicates a functional boot.
You "only" need to complete the remaining steps correctly and on time.
If unsuccessful, repeat the procedure by disconnecting the battery.
If you changed the drivers manually, uninstall them first.
Let them download automatically.
There is a risk that this is not the 9008 driver.

You'll still need this:

The files contained in the image folder TB-X304L_S000035_170703_ROW_QFIL.rar need to be put into the inage folder X304L and then use this folder for MiFlash.

I have to thank You a lot. You saved my good old Lenovo. First when I read Your tutorial, I thought that could never ever work. I was exactly same problem as You were. I tried everything, even raindance. Nothing not helped. Two weeks with drivers, softwares, thousand tutorials...etc. But that did the trick! Now when I know How to unbrick totally dead Lenovo, it is actually only 10 minutes and lenovo fired up again.
Actually it is really easy do with linux by using QDL. No driver hassles or timing when connect or similar. I've linux installed, so if someone gonna try this, Live linux from USB stick working as well. User friendly could be for example Linux Mint Mate, Ubuntu...
1. Install Linux Your USB device and boot it by using Your PC.
2. Get QDL flash tool for Your PC (free and very easy to use).
3. Install QDL depencies: libxml2 and libudev (fastboot is optional, if unlocking bootloader same time).
sudo apt-get install libxml2 libudev fastboot
4. Stop modem manager: sudo systemctl stop ModemManager
5. Start flashing : ./qdl --storage emmc --include <Your Whole Stock firmware path> <Firehose path> <RAW program path (xml format)> <patch0 path (xml format)>
Enter and QDL start waiting for EDL device....
Next open second terminal for monitoring: dmesg and as You can see it is coursed 900e mode.
Next disconnect battery and leave it disconnected whole process time. Now it is time to short testpoint. reconnect device to PC when testpoint is shorted and check dmesg . When You'll see it changing 9008 mode. You're ready to start flashing. At this moment QDL still waiting EDL device > Ctrl+C and start over again ./qdl ...etc and flashing starting.
This is how easily You can hard unbrick Lenovo X304F Tab4 10 or X304L.
In my case I accidently Flashed X704 firmware to my device. It went just fine. But when booting, You know. I tought that's it! But It wasn't. Thanks again @StaryMuz.

I'm glad you found my advice helpful. The Linux tutorial is useful and it's good that you posted it.

i ended up bootlooping on the lenovo logo (tbx304L) and locked bootloader
and is it necessary to be on stock 8.1 to downgrade? @StaryMuz
the recovery shows 7.1.1 but still bootlooping

StaryMuz said:
I managed to identify the test point on the motherboard.
This allows the tablet to switch from Qualcomm HS-USB Diagnostics 900E driver mode to Qualcom HS-USB QDLoader 9008 mode.
My tablet could not be booted into bootloader, recovery or system.
Button vibration did not work.
The tablet only logged on to a PC with the Qualcomm HS-USB Diagnostics 900E driver.
The EDL cable did not help and the buttons of the 900E driver only restarted.
Photos and brief instructions I posted on the Russian forum here:
http://4pda.ru/forum/index.php?s=&showtopic=849554&view=findpost&p=90398828
I attach the photo here.
Only one hidden test point is connected to the metal frame (needle).
Click to expand...
Click to collapse
Many of the links for the rescue files are now missing but I will share how I rescued my TB-X304F in 2023. I followed your photo indicating the test point location/ trick along with the Lenovo Rescue and Smart Assistant program.
Rescue and Smart Assistant (RSA) - Lenovo Support US
support.lenovo.com
1) open the tablet
2) Remove the metal cover
3) Carefully Peel/bend the metal frame around the chip on the right in order to find the hidden test point. It is right under the frame. (the frame should gently move away from the chip, the frame is not difficult)
Now be sure to install the Lenovo Rescue and Smart Assistant program on your PC. Launch it, and look up the tablet's firmware by either S/N or manually looking it up. Download the necessary firmware files within the program until you get to the point of start rescue. Click Proceed, ok, ok, until you get to the screen that says: Find QDLoader COM Port which is asking you to hold the volume +&- but we have already tried that and didn't work so at this point then do the following:
- disconnect the battery
- connect the USB cable to the phone and computer
- Connect the test point with a needle (touch) to the frame and hold
- connect the battery and watch the driver in the windows manager
- as the 9008 driver loads, disconnect the point and let the Lenovo Rescue and Smart Assistant do its thing.
Tablet rescued!