Hi!
My One "connects" to my PC when it's booting (that sound), but after that it stays disconnected. While booting it's being recognized as an MTP device. Recovery has the same problem: Until recovery starts it's kinda connected, but when TWRP is started, even sideload doesn't work. And in the booloader the "device enumeration failed". The ROM is ARHD GE 6.1
Does some1 know solutions to those probs?
Pwnie2012 said:
Hi!
My One "connects" to my PC when it's booting (that sound), but after that it stays disconnected. While booting it's being recognized as an MTP device. Recovery has the same problem: Until recovery starts it's kinda connected, but when TWRP is started, even sideload doesn't work. And in the booloader the "device enumeration failed". The ROM is ARHD GE 6.1
Does some1 know solutions to those probs?
Click to expand...
Click to collapse
You definitely have a driver problem. Install the drivers from this thread, that should solve your problems.
Make sure to uninstall all currently installed drivers for your HTC One. For this go to the device manager on your pc. (windows + x, -> device manager)
$tefanDroid said:
You definitely have a driver problem. Install the drivers from this thread, that should solve your problems.
Make sure to uninstall all currently installed drivers for your HTC One. For this go to the device manager on your pc. (windows + x, -> device manager)
Click to expand...
Click to collapse
any idea how i could list the drivers which i can uninstall?
Pwnie2012 said:
any idea how i could list the drivers which i can uninstall?
Click to expand...
Click to collapse
http://msdn.microsoft.com/en-us/library/windows/hardware/ff553572(v=vs.85).aspx
$tefanDroid said:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff553572(v=vs.85).aspx
Click to expand...
Click to collapse
uninstalled them, now it always get's recognized as an unknown device (searching drivers), but before it finds a driver it again disconnects
Pwnie2012 said:
uninstalled them, now it always get's recognized as an unknown device (searching drivers), but before it finds a driver it again disconnects
Click to expand...
Click to collapse
Hmm try this one http://forum.xda-developers.com/showthread.php?t=2588979
$tefanDroid said:
Hmm try this one http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
in fastboot i have a "failed device enumeration", the windows-update from the driver thread doesnt work, it says it isnt applicable for my OS
(8.1pro)
EDIT: was able to install the update now, after uninstalling another one. testing fastboot asap (after a reboot).
EDIT 2: Ok, doesnt work.
i now tested, if OTG works on it. doesnt even recognize that there was a usb cable inserted
Related
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
Hello
I really need help, my phone are not recognized by my pc
no adb no mtp no fastboot
even i use official charger it says "charging usb"
so it's something to do with the software
i just bought new charger, it's the same.
i didn't did anything important modification..
just flash custom multi rom, recovery,
i have s-off, unlocked bootloader rooted...
can anyone help me ?
Kigsuha said:
Hello
I really need help, my phone are not recognized by my pc
no adb no mtp no fastboot
even i use official charger it says "charging usb"
so it's something to do with the software
i just bought new charger, it's the same.
i didn't did anything important modification..
just flash custom multi rom, recovery,
i have s-off, unlocked bootloader rooted...
can anyone help me ?
Click to expand...
Click to collapse
Have you turned on ADB on the phone?
Jackering;Form:4290 said:
Have you turned on ADB on the phone?
Click to expand...
Click to collapse
Yes.
Maybe it's the firmware. I can't flash new firmware without fast boot..
Add : hboot 1.54
Firm : 3.22.154.......
I didn't relocked bootloader when flashing the new firmware
Mate what's the output from adb devices or fastboot devices command?
Guich said:
Mate what's the outputdevices"b devices or fastboot devices command?
Click to expand...
Click to collapse
Nothing
It's empty after "adb devices" or "fastboot devices"
Kigsuha said:
Nothing
It's empty after "adb devices" or "fastboot devices"
Click to expand...
Click to collapse
Umh, seems that the phone wasn't recognized by pc.
Which OS are you using?
If windows go to Device manager and check if you can see your one
Guic" said:
Umh, seems that the phone wasn't recognized by pc.
Which OS are you using?
If windows go to Device manager and check if you can see your one
Click to expand...
Click to collapse
W7 64
Only "unknown device"
No One
Can u tell me if it's bad that I flashed new firmware before relocking the bootloader ?
Kigsuha said:
W7 64
Only "unknown device"
No One
Can u tell me if it's bad that I flashed new firmware before relocking the bootloader ?
Click to expand...
Click to collapse
Are you on android right?
Have you tried to unistall the device from device manager and after re-connect the phone at the pc for the drivers?
Guich said:
Are you on android right?
Have you tried to unistall the device from device manager and after re-connect the phone at the pc for the drivers?
Click to expand...
Click to collapse
Yeah
Tried uninstall and usbdeview. Not work
On my other w7 pc windows say " drivers install failed"
Kigsuha said:
Yeah
Tried uninstall and usbdeview. Not work
On my other w7 pc windows say " drivers install failed"
Click to expand...
Click to collapse
Have you tried linux?
However, seems strange.
You're running 3.22 firmware and in android device isn't recognized...
Guich said:
Have you tried linux?
However, seems strange.
You're running 3.22 firmware and in android device isn't recognized...
Click to expand...
Click to collapse
Didn't try linux
Will do when I can
Kigsuha said:
Didn't try linux
Will do when I can
Click to expand...
Click to collapse
Tried on ubuntu.
Nothing. Phone only charges..
Do I have to retry? Installing adb/usb/fastboot drivers?
Kigsuha said:
Tried on ubuntu.
Nothing. Phone only charges..
Do I have to retry? Installing adb/usb/fastboot drivers?
Click to expand...
Click to collapse
So seems an hardware issue.
Maybe i can try to help you tomoz with teamviewer
Mobile Post
Guich said:
So seems an hardware issue.
Maybe i can try to help you tomoz with teamviewer
Mobile Post
Click to expand...
Click to collapse
Hardware really ?
So there's nothing I can do ?
I'm now with stock Rom stock recovery no root
I can do nothing without usb working..
Seems...
In fastboot, with all os you've tried, no answer by terminal?
Mobile Post
Guich said:
Seems...
In fastboot, with all os you've tried, no answer by terminal?
Mobile Post
Click to expand...
Click to collapse
No answer
I had the same problem a few weeks back. The phone was not recognised by any computer. If you fiddle around with the micro usb on the phone it would recognise the phone for a second. It took me nearly two weeks of trying, to flash a RUU and get the phone back to stock for a repair.
I asked in the shop if this was common and the lad said it has happened to others. It is dust that gets in the usb and people cleaning shorts the motherboard???? I didn't clean anything so I don't know if this is true.
Anyway I got a replacement phone. Maybe you should keep it at stock and get a replacement. If it happens once it will happen again.
Try uninstalling HTC Sync, if you haven't already, uninstall driver, reinstall HTC Sync and see if you can't get the PC to see it. And when the pop up on the phone comes, check always allow.
When I type lsusb : I don't see my One..
htc drivers and htc sync don't works everytime it say unknown device..
Got my phone about a week ago & got pretty bored of it so I wanted to root it and get a different ROM going. For some reason, I can't get the phone to connect to HTC Sync Manager though I updated the drivers. Any time the phone is switched into USB debugging, My HTC drivers fail to install. I have no idea how to solve this problem. Also when trying to get the Token ID using the command prompt, the device doesn't show up after using the command adb devices either. Need help please.
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
bigdaddy619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
HurtMeSole said:
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
Click to expand...
Click to collapse
Windows 8.1?
bigdaddy619 said:
Windows 8.1?
Click to expand...
Click to collapse
No, Windows 7, 64-bit.
HurtMeSole said:
No, Windows 7, 64-bit.
Click to expand...
Click to collapse
Check PM
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
HurtMeSole said:
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
Click to expand...
Click to collapse
Same problem here with an HTC One Mini. Its driving me mad!:silly:
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
Strangely enough, I literally just tried it on a different computer and everything worked exactly as it was supposed to. I had 3 computers in my home, none of which worked but got to work and the laptop they gave me worked just fine. Then I got on my gf's Mac and it went mostly smooth (even though it was difficult not being as familiar with the OS). My advice is do everything you're doing on a different computer until you see it without the ! in the device manager.
Boblud said:
Same problem here with an HTC One Mini. Its driving me mad!:silly:
Click to expand...
Click to collapse
Should try using a different computer. Worked for me after trying several computers.
BD619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
My experience may be helpful. I had no ADB driver, but Composite USB seemed to work. However, the driver install crashed. I needed to open my phone and answer the dialogs on my phone while the driver was installing. After that, everything is hunky-dorry (I know, showing my age).
I was having the same problem until I UNCHECKED the USB debugging mode and reconnected the phone to the computer. Drivers reinstalled and HTC Sync Manager (not HTC Sync--different program) recognized the phone. I had to answer dialogue on phone and then the USB debugging mode status changed itself to enabled. It's all working now, after hours of fiddling.
i have a problem with my htc one m7.
it as no os installed and no recovery option
the htc is unlocked with s-off and when i plug the usb cable to the pc it gets a windows error code 43 with an anknown device.
all the drivers that i downloaded did not done the work.
help me please.
roital said:
i have a problem with my htc one m7.
it as no os installed and no recovery option
the htc is unlocked with s-off and when i plug the usb cable to the pc it gets a windows error code 43 with an anknown device.
all the drivers that i downloaded did not done the work.
help me please.
Click to expand...
Click to collapse
is the phone in the bootloader or just a black screen ?
does fastboot work ? reflash custom recovery and a rom
clsA said:
is the phone in the bootloader or just a black screen ?
does fastboot work ? reflash custom recovery and a rom
Click to expand...
Click to collapse
it is in bootloader and can not get into recovery and if i select the fastboot option and connect it to the pc the error 43 pops up.
it started with the installing of a viper custom rom that the recovery gone bad.
but the driver error problem started earlier.
i have a backup on the phone but for restoring the backup i need the recovery to work but as i say the window7 7 64bit gives an unknown device error code 43.
can anyone help me please?
roital said:
can anyone help me please?
Click to expand...
Click to collapse
Fix your pc drivers
http://forum.xda-developers.com/showthread.php?t=2541082
Post 2 / FAQ 2
clsA said:
Fix your pc drivers
http://forum.xda-developers.com/showthread.php?t=2541082
Post 2 / FAQ 2
Click to expand...
Click to collapse
when i install the driver that is attached in the site i can not see it in the drivers list on windows.
if i select the folder where the windows 7 64bit driver is it gives me a massege that thare is no windows 64 bit drivers there.
can you please give me the inf file for the driver that workes on windows 7 ultimate 64bit for the htc one m7 ?
roital said:
when i install the driver that is attached in the site i can not see it in the drivers list on windows.
if i select the folder where the windows 7 64bit driver is it gives me a massege that thare is no windows 64 bit drivers there.
can you please give me the inf file for the driver that workes on windows 7 ultimate 64bit for the htc one m7 ?
Click to expand...
Click to collapse
You can find your drivers here.
Uninstall your present driver through the Control Panel then reboot your computer. Now install the new driver.
majmoz said:
You can find your drivers here.
Uninstall your present driver through the Control Panel then reboot your computer. Now install the new driver.
Click to expand...
Click to collapse
done that without any luck.
the defualt windows "unknown device" Standard USB Host Controller and the error 43 is there.
roital said:
done that without any luck.
the defualt windows "unknown device" Standard USB Host Controller and the error 43 is there.
Click to expand...
Click to collapse
error 43 is a windows error. no amount of reinstalling drivers will work.
if your using a laptop, remove all USB devices, uninstall the drivers you are trying to fix, shut down the computer and remove the battery for 10 mins min.
if its a desktop, do the same thing, but pull out the kettle lead from the back, hit the power button a few times to drain the PSU caps.
restart the computer and plug in usb devices one at a time making sure they work properly.
re-install phone drivers, I recommend downloading HTC sync manager for the drivers (never had a problem with them) and then remove HTC sync.
failing that a windows re-install or driver cache cleaner is required or try a different computer.
Use another comp dude
jdgreat4 said:
Use another comp dude
Click to expand...
Click to collapse
allredy tried another computer but still the same message.
I need a computer to recognize the device in a bootloader,adb fastboot mode to push the twrp into the device.
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app
Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.
This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?
MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.
Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?
okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?