Hi All,
I was trying to enable the ADB with PAC ROM when my evita is switched on as we do on sense roms.
But my Windows 7 PC is unable to detect the phone as android and It was searching for drivers online and at last failing to find the drivers.
I have HTC Android drivers installed on my PC and android debugging enabled on my evita.
Is this is the known behaviour of KK 4.4.2 AOSP ROM's ??
Not that I know of, I've had no problems using adb on any of the KitKat ROMs I've tried. How have you installed the drivers?
Sent from my Evita
Scozzar said:
I've had this issue quite a lot as well. ADB won't ever work when booted into the ROM, but if you boot into fastboot, no problems at all. What happens is that it searched for drivers, then can't find them.
Click to expand...
Click to collapse
Are you talking about adb commands working in fastboot? Or fastboot commands working in fastboot?
Sent from my Evita
Ok. It can be a huge hassle, I had the opposite problem. My adb was working beautifully on my new laptop but I couldn't get fastboot working with official HTC drivers. Ended up using the drivers from pdanet to get it to work, but they ended up not being compatible with RUUs. So tried with the official HTC drivers again, plugged in my fiance's Evita instead of mine, and bam! Perfect driver setup. Go figure. The amount of times I've helped people on XDA get their drivers working and it took me like three friggin days.
Sent from my Evita
No, only one set of drivers. When the official HTC drivers didn't work with fastboot I uninstalled them and used the pdanet drivers. When the pdanet drivers didn't work with the RUU I uninstalled them and installed the HTC drivers again.
Sent from my Evita
timmaaa said:
No, only one set of drivers. When the official HTC drivers didn't work with fastboot I uninstalled them and used the pdanet drivers. When the pdanet drivers didn't work with the RUU I uninstalled them and installed the HTC drivers again.
Sent from my Evita
Click to expand...
Click to collapse
PDANet drivers worked for me as well. But my device is showing as Offline, what could be the reason for this?
sathish804 said:
PDANet drivers worked for me as well. But my device is showing as Offline, what could be the reason for this?
Click to expand...
Click to collapse
You need to have your screen on and accept the prompt that pops up.
Sent from my Evita
I have experience similar problem after flash to KK4.2.2: adb never connect and no authorization confirmation pop up will show. I found that in my device manager there is a device called "One X" without driver. I get all my htc driver from http://forum.xda-developers.com/showthread.php?t=2217396 never installed htc sync. I searched around, everyone was talking about disable and re-enablle adb debug and "allow" its access from the popup and no one was having the "no driver" problem. I solved this problem by editing one inf file in the installed driver.
SOLUTION
If you have installed the driver from the link above, under:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
there will be a file named androidusb.inf. Depending on your windows installation path and bitness, this path may be slightly different. Edit it with notepad, find a line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF2&MI_01
insert the following line just below that line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF9&MI_01
save the file and use "update driver" in device manager to install driver. manually select the search directory and windows should find the driver. After the driver is installed, adb works like a charm.
sippey said:
I have experience similar problem after flash to KK4.2.2: adb never connect and no authorization confirmation pop up will show. I found that in my device manager there is a device called "One X" without driver. I get all my htc driver from http://forum.xda-developers.com/showthread.php?t=2217396 never installed htc sync. I searched around, everyone was talking about disable and re-enablle adb debug and "allow" its access from the popup and no one was having the "no driver" problem. I solved this problem by editing one inf file in the installed driver.
SOLUTION
If you have installed the driver from the link above, under:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
there will be a file named androidusb.inf. Depending on your windows installation path and bitness, this path may be slightly different. Edit it with notepad, find a line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF2&MI_01
insert the following line just below that line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF9&MI_01
save the file and use "update driver" in device manager to install driver. manually select the search directory and windows should find the driver. After the driver is installed, adb works like a charm.
Click to expand...
Click to collapse
Thank You.. This is worked for me!!
Related
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!
haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!
bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.
I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid
I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!
Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!
Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work
matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!
thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!
I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box
I have scoured the internet and xda and have not found a solution. I am trying to unlock my bootloader, so I can install ROMs and whatnot, on my HTC One S. However, the device is not recognized by adb, even though the normal drivers are installed through HTC sync. I cannot install any additional driver through any other way.
Basically, I just need to know if anyone has a solution to getting the HTC One S to recognize with adb on Windows 8, or any alternate way to get a token.
I have done this many times before on windows 7, and even used adb for other devices on Windows 8, but cannot get the One S to read.
..and unfortunately my Windows 7 machine is in need of repair.
Any suggestions would be appreciated.
Adb still worked after I went from 7 to 8. Uninstall drivers and install android sdk which has required drivers. I've never used HTC sync due to its suckness. You can also google the download for just the drivers without any extra software. There are multiple devices that have adb drivers for download here on xda aswell.
Good hunting
But as far as driver compatibility nothing has changed since the update
Sent from my HTC VLE_U using xda app-developers app
the drivers wont work until htc/Microsoft updates them. doesn't work on my windows 8 pro, I had to installed a virtual machine to get it to work with windows 7.
Definitely nofun that the htc drivers seem to be the big issues. Whendid not have trouble with the kindle orsamsung. Did update as much through the sdk, and tried manually installing the win 7 drivers, and more andno luck. So guess Ill be waiting.
Works for me on windows 8 pro....don't know what you are talking about
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
Works for me on windows 8 pro....don't know what you are talking about
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Thats good to hear that there is a way to get it working. What drivers did you install?
Are you looking for a driver that will work for when you are in bootloader? I used a Samsung driver and it worked fine.
mbh87 said:
Are you looking for a driver that will work for when you are in bootloader? I used a Samsung driver and it worked fine.
Click to expand...
Click to collapse
I just installed the latest htc sync and all the drivers were good
Sent from my HTC VLE_U using xda premium
mikeyinid said:
I just installed the latest htc sync and all the drivers were good
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Did this allow detect in adb? not just for windows recognizing the device?
Ive come to find that adb will recognize the device, but not in fastboot mode. Which is the killer, cause thats the only mode I really need it to be recognized in.
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Ruwin said:
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Click to expand...
Click to collapse
Already tried Used both windows 7 and windows vista drivers.
Oh well.
I installed the SDK and some hacked HBOOT drivers. Doesn't work. I'll have to try new methods
phoenixbennu said:
Ive come to find that adb will recognize the device, but not in fastboot mode. Which is the killer, cause thats the only mode I really need it to be recognized in.
Click to expand...
Click to collapse
I've found in some pages that HTC has already uploaded their HTC Sync and that is now compatible with Windows 8. However, still not working for me in 8 Pro.
---------- Post added at 02:02 AM ---------- Previous post was at 01:55 AM ----------
Ruwin said:
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Click to expand...
Click to collapse
I've uploaded from W7 to W8 pro and my now I'm not able to find a driver that fits my computer. It's a very strange situation.
I have tried pretty much everything lol, its not worth it if you are installing a RUU then windows 8 suddenly stopped detecting your phone then you have a brick. I would just wait till htc releases drivers for windows 8. or installed windows 7 through VMware, like I did.
Just have the device for 1 day and had some issues. Is there any working solution for this? I've spend some time searching and reading, I tried alot of drivers (HTC, from android-sdk and so on)...with all the same issue. Windows 8 recognizes the device as My HTC BUT...adb doesn't. When issuing "adb devices" command, returned list is blank.
Finally I've installed recovery and unlocked on a Windows 7 machine but I don't want to do that each time I flash a ROM (and I flash alot).
Also short question... I didn't saw anywhere clearly stated but from what I've read, I understood there's no S-Off for One S right? I'm comming from Desire S and everything there was flawless.
It is working on my Windows 8 Pro without an issue. I installed the driver which comes together with the android sdk.
1. Open device manager
2. Select the android device with yellow sign
3. right click and select "Update Driver Software ..."
4. select browse my computer for driver software
5. select "Let me pick from a list of device drivers on my computer"
6. select have disc and browse for the "android_winusb.inf" in the android sdk folder
7. select Android ADB Interface and press next
8. select yes, ...
-> adb driver is installed and device should now work with adb.
Best regards,
dexi
dexi00 said:
It is working on my Windows 8 Pro without an issue. I installed the driver which comes together with the android sdk.
1. Open device manager
2. Select the android device with yellow sign
3. right click and select "Update Driver Software ..."
4. select browse my computer for driver software
5. select "Let me pick from a list of device drivers on my computer"
6. select have disc and browse for the "android_winusb.inf" in the android sdk folder
7. select Android ADB Interface and press next
8. select yes, ...
-> adb driver is installed and device should now work with adb.
Best regards,
dexi
Click to expand...
Click to collapse
wbut i can't find android-winusb.inf in my sdk,
can you mention the folder's path?
I'm having same issue but on Win7 also tried many installs and uninstall of HTC drivers, still not recognized plus have my own thread which 2 members tried all they know also tried on my Dad's Vista with a no go? I found my computer recognized my device if u do this, power down ur device than restart ur computer while booting up plug in ur device and sometimes it recognizes it but not always staying connected
Sent from my HTC One S using xda premium
I have Windows 8 Pro Media Center, install drive from htc sync manager from htc site, flashing fastboot, oem lock, etc seem to work in cmd. But odd was if i do adb devices, it just say something like "list device" i don't see my device number.. or i should use fastboot devices instead
Try this:
[Solution]Windows 8 - ADB/fastboot driver problem solved!!
NOTE: This is an older version of the driver, a newer version is available here.
This was pulled directly from the HTC Sync Manager 2.0.61.0 installer.
HTCDriver.exe.part1.rar and HTCDriver.exe.part2.rar are the executable driver installer. The other files are the drivers for the individual platforms.
Note: The last zip is labeled Win2k, but I suspect it is also intended for use with Windows XP.
Note 2: An earlier version of the Windows 7 driver was reported to work with Windows 8, so I suspect that is also the case with this version.
NOTE: This is an older version of the driver, a newer version is available here.
I never seem to see the driver in HTC Sync Manager temp folder, I only see the driver in HTC Sync temp folder which contains HTCDriver_4.0.1.001_20121107.exe which hasn't been updated.
DvineLord said:
I never seem to see the driver in HTC Sync Manager temp folder, I only see the driver in HTC Sync temp folder which contains HTCDriver_4.0.1.001_20121107.exe which hasn't been updated.
Click to expand...
Click to collapse
Like the HTC Sync installer, the HTC Sync Manager installer creates temporary folders for the individual components as it installs them, but, unlike the Sync installer, there is no pause after installing the "prerequisite" components before deleting all of the individual installers and starting the Sync Manager install. Also unlike the Sync installer, it there will be a second temporary folder containing "HTC Sync Manager.msi" and other files. This is not the folder where the other components will be extracted.
The trick is to wait until the Sync Manager installer says "Installing HTC Driver Installer" and click Cancel, but don't actually cancel the installation. Just leave it at the "Are you sure...?" dialog. This isn't absolutely necessary, but it will give you time to sift through the %TEMP% folder to find the installer. Also, be sure that you uninstall HTC Driver Installer, if it is already installed, before starting the HTC Sync Manager installer, or this step won't happen, and the HTC Driver installer won't be extracted to a temporary folder during setup. Simply uninstalling HTC Sync Manager will not uninstall HTC Driver Installer.
Also note that the HTC Driver installer will be running during this time, so there will also be a temp folder with HTCDriver.msi and other files. This is not the folder where HTCDriver.exe will be extracted.
This just unbrick my phone....
Am so happy,
Thanks thanks thanks
Any new drivers in latest HTC Sync Manager? setup_2.1.55.0_htc.exe
Thanks for this, the Windows 7 x64 worked perfect. :good:
Ive never had a problem on my previous 2 computers running Win7 but now Ive upgraded to Win8 x64. Since then adb.exe window opens and closes. I can see my phone in the device manager whether Im in the bootloader or fully booted up. Ive followed a few guides to install sdk, jdk, adb but still not able to get adb to fully work. Installed the Win7 x64 usb drivers and google USB drivers manually thru the device manager and they are are all up to date. Ive moved the file folders for everything to the c:\program files directory before I started opening everything up and installing. Ive looked thru other forums for Win8 adb problems and followed those guides and looked on Youtube and done a search on XDA. Most are all the same but I tried them as well.
Im really out of options regarding this problem. Asking for help now. Thanks
platform-tools_r18.0.1-windows.zip
CRC32: c5df9dec
MD5: f94f493c3c998c07c7a2037b830636ab
SHA-1: b40fea3ed72296dd42dd616a7abf536b8dace20d
Do these drivers work with Desire HD? I'm trying to get fastboot to work, but I'm unable to do so without the proper drivers.
DvineLord said:
Any new drivers in latest HTC Sync Manager? setup_2.1.55.0_htc.exe
Click to expand...
Click to collapse
Sorry for the delay in replying. Yes, there is a new version of the driver, at least in the 2.4.11.0 installer. You can find it here.
Scozzar said:
What does this do?
Click to expand...
Click to collapse
It's a newer version of the installer from which the drivers are pulled.
raczyk said:
Do these drivers work with Desire HD? I'm trying to get fastboot to work, but I'm unable to do so without the proper drivers.
Click to expand...
Click to collapse
Yes, my backup phone is an Inspire 4g, and these work with it.
Please take your time to read this.I will keep it quite short, but try to understand my problem.
Ok so I am trying to enable USB debugging for my Nexus 5.But everytime I try to install the ADB driver, it says parameter is incorrect (I'm using windows vista).
At first, I didn't have the SDK installed, so I downloaded the 70 MB SDK Manager, and from there I downloaded the platform tools & google drivers, then I tried installing the drivers manually using the Device manager using both methods of locating the file manually using the have disk method and the locate the directory and include sub folders method..but both have failed to install the driver and it keeps saying the parameter is incorrect.
Suggestions?
Use a different driver from the one included in the SDK. Either use the USB driver package provided by lg(I did this and it went flawlessly) or use the "naked adb driver" which is a simple adb driver that should just work.(I used the former because the naked driver is third party and not properly signed, so it's a pain to install on windows 8)
Find either through a Google search.
Edit: nvm this guide includes the links required: http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
biro2200 said:
Please take your time to read this.I will keep it quite short, but try to understand my problem.
Ok so I am trying to enable USB debugging for my Nexus 5.But everytime I try to install the ADB driver, it says parameter is incorrect (I'm using windows vista).
At first, I didn't have the SDK installed, so I downloaded the 70 MB SDK Manager, and from there I downloaded the platform tools & google drivers, then I tried installing the drivers manually using the Device manager using both methods of locating the file manually using the have disk method and the locate the directory and include sub folders method..but both have failed to install the driver and it keeps saying the parameter is incorrect.
Suggestions?
Click to expand...
Click to collapse
uninstall driver and use this tool.
samersh72 said:
uninstall driver and use this tool.
Click to expand...
Click to collapse
Tried it, still doesn't recognise my nexus 5 as ADB device, and windows still wants to install the driver for it & fails as well
biro2200 said:
Tried it, still doesn't recognise my nexus 5 as ADB device, and windows still wants to install the driver for it & fails as well
Click to expand...
Click to collapse
i am sorry to ask this but are you having problem enabling usb debugging? did you activate developer option by tapping build number seven times?
Man this stuff gave me such a headache same issue here. But with fastboot. I had to manually update the drivers while the phone was plugged in. That's what messed me up.
First uninstall all drivers
While phone is on.
Update drivers with USB debugging enabled
While phone is in boatloader
Update again.
Adb and fastboot should work fine after that. Use one of the exe type drivers. Like LGS driver .exe than go into the device manager and update. Let the computer find the drivers.
Sent from my Nexus 5 using xda app-developers app
Have Windows 7 64-bit, and had no issues using adb commands with my M7 HTC One. No matter what, I cannot get the same laptop to recognize my M8 to issue ADB commands. adb devices shows no device. Made sure HTC Sync/Samsung Keis/etc. wasn't installed. Update Android SDK to latest versions. Tried to install the HTC One M8 "Toolkit" and update drivers there.
Any ideas? Not sure if I should be getting the security popup on my phone to trust the PC connection, but that's not happening even though USB Debugging is enabled on the phone. I can provide more information if needed.
WorldOfJohnboy said:
Have Windows 7 64-bit, and had no issues using adb commands with my M7 HTC One. No matter what, I cannot get the same laptop to recognize my M8 to issue ADB commands. adb devices shows no device. Made sure HTC Sync/Samsung Keis/etc. wasn't installed. Update Android SDK to latest versions. Tried to install the HTC One M8 "Toolkit" and update drivers there.
Any ideas? Not sure if I should be getting the security popup on my phone to trust the PC connection, but that's not happening even though USB Debugging is enabled on the phone. I can provide more information if needed.
Click to expand...
Click to collapse
I too had trouble getting my M8 drivers to install correctly. When the adb devices command returns nothing that means your drivers aren't installed. Open your device manager in Windows (open start menu then search device manager) and see if under your devices it shows a yellow triangle next to your device. If it does then drivers aren't installed correctly. What I ended up doing was actually installing HTC Sync and HTC Sync manager and allowing it to install drivers for me. Then once it was done uninstalling them. Or you could also manually update the drivers with the Universal adb drivers (they come with the Android SDK). I would install HTC Sync and let it do it's thing though first.That HTC Driver installer program you see in the screenshot below came with the HTC Sync program.
nicholi2789 said:
I too had trouble getting my M8 drivers to install correctly. When the adb devices command returns nothing that means your drivers aren't installed. Open your device manager in Windows (open start menu then search device manager) and see if under your devices it shows a yellow triangle next to your device. If it does then drivers aren't installed correctly. What I ended up doing was actually installing HTC Sync and HTC Sync manager and allowing it to install drivers for me. Then once it was done uninstalling them. Or you could also manually update the drivers with the Universal adb drivers (they come with the Android SDK). I would install HTC Sync and let it do it's thing though first.That HTC Driver installer program you see in the screenshot below came with the HTC Sync program.
Click to expand...
Click to collapse
OK, I decided to all out attack this and uninstalled a bunch of stuff from my PC. Plug the phone in and it installed the drivers, prompted (on my phone) to allow debugging and I am all set. Strangest thing as my M7 was working perfectly fine last week. Thanks!