Related
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....
Helloeveryone
I got my yu 2weeks ago and since iam trying to unlock bootloader and root yu yurrka
?but i failes to root and unlock device a hundred of timess i tried almost everything
(All in one tool.minimal adb.oneclickroot apps.etc)
When i tried to unlock phone the adb commands are working fine and i used koushik dutta universal adb drivers (fitst time)
Then i triee naked usb drivers annd every drivers in internet that is available for yureka
Thus in every drivers the commands work fine in adb but ehen we connect phone in via fastboost mode it shows waiying for device
I dont know what to do
Pls share a working link of drivers
Adb and fastboot commands
And how to ise it in right way????
Sent from my AO5510 using XDA mobile app
I have had my Axon 7 for about 48 hours. I was super excited to get into as it has a great price/feature ratio.
As I usually do with a new handset, I set about unlocking, rooting, etc. This turned out to be massively annoying and not nearly as easy as I would have liked. After a couple of hours, I managed to get the bootloader unlocked, TWRP installed, and the stock firmware up to B25. When I couldn't get root to work properly (after another few hours), I decided to throw in the towel. I set about reverting everything back to factory so I could reevaluate. There is where my problems started...
In the middle of rolling back everything, somehow I am no longer able to boot the phone at all.
All the guides I have read online say to enter EDL mode but it never seems to work? I have tried using MiFlash as well as the Axon7Toolkit and both do not see the device. I have installed the Qualcomm USB drivers and I see the COM port in device manager, but it says the device isn't connected.
I get the blue ZTE logo then a split-second flash of the open chest android with the red triangle before the screen goes black. The phone is still powered on however.
BUT 'adb devices' command yields: d69520e recovery
So, I know the phone has some degree of communication with the computer.
Is all hope lost for me at this point? Or is there something else I'm missing?
Please let me know if there is any additional information needed to help figure out what's going; I will do my best to provide it.
Thanks in advance for any assistance!!
This is similar to what has happened to me. Have a look here. There are some advises, but I couldn't get it to work anymore.
https://forum.xda-developers.com/showthread.php?p=72223036
Gesendet von meinem Lenovo K3 Note mit Tapatalk
@frustratedaxon7user
You said :
> I see the COM port in device manager, but it says the device isn't connected.
> BUT 'adb devices' command yields: d69520e recovery
It looks like that the recovery is broken (open check Android screen).
Do you mean that the phone is detected as "Qualcomm HS-USB QDLoader 9008 (COM10) in device manager?
And you got response to "adb devices" command?
I think there is a conflict here. If you got "adb devices" answer as "d69520e recovery" then the phone is in recovery
mode, not EDL mode. You must try to get in EDL by entering "adb reboot edl" command. Keep the Windows Device manager always on,
it should emit beep sound and refresh display to show the phone as "Qualcomm HS-USB QDLoader 9008" (or "QUSB_BULK") depending on your installed driver.
and if the phone is really in EDL mode, "adb devices" should no longer work (empty attached devices in answer to command). Note that in EDL mode there is nothing on the screen
so you must rely on the Device manager to deduce the status of the phone (In item USB devices), and to issue "adb devices" comand to check.
If Qualcomm HS-USB QDLoader 9008, you can flash TWRP 3.1.0-0 with MiFlash : https://forum.xda-developers.com/showpost.php?p=72313753&postcount=44
and https://forum.xda-developers.com/showpost.php?p=72316949&postcount=52 . You may havy to refresh several times in MiFlash for connection with the phone.
If QUSB_BULK, you can flash TWRP (tenfar signed TWRP 3.0.2) using axon7tool https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 (section A).
My wife´s Z1 (which is on original 5.1.1) has been noughty recently. Phone calls (incoming or outgoing) can not be made because incoming voice sounds are not heard. It does not depend on what phone app is used, also the problem exists on WhatsApp calls as well. The problem is intermittent, comes and goes at random and is active far more often than not. Anyone has a clue to what the cause may be?
Anyway, I decided to try and wipe and upgrade the phone, hoping it is not a hardware fault and will disappear after upgrade. Then came next problem. The PC first reports that the attached USB device is not recognised, then, after repeated connections, the Z1 is just ignored by the Win10 PC. The PC has an old ADB-driver and Lenovo bridge installed since a previous operation on another Lenovo phone. I tried to connect to another Win10 PC without any ADB or Lenovo software, hoping to at least see it in the Explorer, but with eaxactly same result. Anyone has a clue to how I can make the Z1 recognizable again?
Every guide to flashing, be it TWRP or a rom, assumes that the phone is connected to a PC. But I have checked the internal recovery option, and it looks like you should be able to browse to an external SD-card to find a rom zip to upgrade from. Since this option is never mentioned in guides, why ca´nt you use it?
bjorni said:
My wife´s Z1 (which is on original 5.1.1) has been noughty recently. Phone calls (incoming or outgoing) can not be made because incoming voice sounds are not heard. It does not depend on what phone app is used, also the problem exists on WhatsApp calls as well. The problem is intermittent, comes and goes at random and is active far more often than not. Anyone has a clue to what the cause may be?
Anyway, I decided to try and wipe and upgrade the phone, hoping it is not a hardware fault and will disappear after upgrade. Then came next problem. The PC first reports that the attached USB device is not recognised, then, after repeated connections, the Z1 is just ignored by the Win10 PC. The PC has an old ADB-driver and Lenovo bridge installed since a previous operation on another Lenovo phone. I tried to connect to another Win10 PC without any ADB or Lenovo software, hoping to at least see it in the Explorer, but with eaxactly same result. Anyone has a clue to how I can make the Z1 recognizable again?
Every guide to flashing, be it TWRP or a rom, assumes that the phone is connected to a PC. But I have checked the internal recovery option, and it looks like you should be able to browse to an external SD-card to find a rom zip to upgrade from. Since this option is never mentioned in guides, why ca´nt you use it?
Click to expand...
Click to collapse
i also came across the same problem with my zuk z1 and windows 10 laptop. my phone also remained unrecognized till i found proper drivers for lenovo zuk z1 : LenovoUsbDriver_v1.0.12.zip, you can google for it as i am new so cant post url till xda allows me to post.
this worked for me. you also can try it.
a0879 said:
i also came across the same problem with my zuk z1 and windows 10 laptop. my phone also remained unrecognized till i found proper drivers for lenovo zuk z1 : LenovoUsbDriver_v1.0.12.zip, you can google for it as i am new so cant post url till xda allows me to post.
this worked for me. you also can try it.
Click to expand...
Click to collapse
Thanks for the tip. When googling for the driver, I actually found a newer one, v1.1.16.0, which also seems to work. But then a new problem appeared. When I activate Fastboot from the PC, the connection to the Z1 is immediately lost. Z1 will not connect again until I restart both the PC and the Z1. Actually, I found out, that you can set Z1 into Fastboot mode by itself. There is a setting in Developer Options that can do that. When I first connect Z1 to the PC and then enable Fastboot mode from the Z1, the result is the same, the connection to PC drops immediately. So, I cannot proceed to the next step to flash TWRP.
Does anyone have a solution?
Edit: I decided to uninstall the new Lenovo ADB driver and then found that the PC still responds to adb commands. Before I started to work on the Z1, I had another adb driver installed, which I used when working on another mobile phone. I had uninstalled it, before installing the new driver, but either that uninstallation left some remains or the uninstallation I just made left some remains. Now it seems I have some adb driver still in the PC and I have to find out how to locate it.
bjorni said:
Thanks for the tip. When googling for the driver, I actually found a newer one, v1.1.16.0, which also seems to work. But then a new problem appeared. When I activate Fastboot from the PC, the connection to the Z1 is immediately lost. Z1 will not connect again until I restart both the PC and the Z1. Actually, I found out, that you can set Z1 into Fastboot mode by itself. There is a setting in Developer Options that can do that. When I first connect Z1 to the PC and then enable Fastboot mode from the Z1, the result is the same, the connection to PC drops immediately. So, I cannot proceed to the next step to flash TWRP.
Does anyone have a solution?
Click to expand...
Click to collapse
you are right, you can set z1 into fastboot mode but then also it is not recognized by your pc. i suggest you to once again install the driver version which i specified . atleast i can say it worked for me !!, secondly there is a twrp version with min. adb tools in a zip file who's link i found when i was searching on youtube for installing twrp on zuk z1 (by: D Tech Terminal).
i did exactly what was asked to do in it and to my surprise my Z1 got twrp installed on it !!
now again same problem
i can't share the link.
you just search how to install twrp zuk z1 on you tube (by D Tech Terminal)
and you will get it.
hit thanks if it helps !!!
bro connect with old computer it work
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
sujan smash said:
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
zgfg said:
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
Click to expand...
Click to collapse
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
sujan smash said:
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
Click to expand...
Click to collapse
Everything looks correctly set but you could still try another PC and USB cable
zgfg said:
Everything looks correctly set but you could still try another PC and USB cable
Click to expand...
Click to collapse
Well i did that too, tried it on my laptop too no luck there also,
As ive mentioned in the first thread ,
It is detecting redmi note 10 in fastboot mode on the same pc with same cable and everything, but not redmi k20, so its not abt PC drivers its something to do with my phone
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
zgfg said:
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
Click to expand...
Click to collapse
Yep it sucks, Thanks Anyways