Related
I have the hardest time getting my computer to use the right driver for ADB. When I setup my wife's phone on a vista-64 operating system I first connected with USB enabled and it took me a week of trial-and-error to get the system to use the ADB driver (I don't know the steps that made it work - but it involved several attempts at uninstalling every USB device).
I just got another G1 for a Windows-7 laptop (64-bit) and I did the same thing (hooked up with the USB driver) and I fear another week of trial and error. I know that if I knew what I was doing I could do it in 10-minutes.
Can someone please provide the step-by-step instructions for having it use the ADB driver once it has already found, and is happy with, the regular USB driver? I'm not even sure how to tell which of my multiple installed USB [devices] is for the phone.
Step 1. Install a linux distribution.
cloverdale said:
Step 1. Install a linux distribution.
Click to expand...
Click to collapse
Step 2. Download the SDK and put it in a directory (I use "Android")
install the sdk from http://developer.android.com/sdk/download.html?v=android-sdk_r05-windows.zip
let it update (make sure that usb drivers are selected for download)
plug your phone in
if the drivers aren't automatically installed, point it to the drivers directory (<sdk>\usb_driver)
if your sdk is already installed, just download the drivers using the steps described here http://developer.android.com/sdk/win-usb.html
4.) Give me a huuuuuug!
I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it
TaeKwonDonkey said:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
Click to expand...
Click to collapse
Do you have the right drivers installed?
When your phone is on, plugged in, SD not mounted, and USB turned on, you should see "Android Phone" and "Android Composite ADB Interface" underneath that.
If you don't want to root (it's so easy and painless if you can follow instructions) then I don't know what to tell you other than:
1. Install "USB Deview" and remove all HTC/Google/Android related drivers.
2. Completely uninstall and wipe out the SDK stuff.
3. Rebooted, and reinstall Android SDK, and make sure that Windows7 installs the right drivers.
Installing the SDK is no more difficult than installing any other piece of software. If you've got Java installed, and you've plugged your phone in, and debugging is turned on, what *should* happen when you double-click ddms.bat is, the command prompt window opens, but then the Debug utility should open.
I had the screenshots stuff working before I ever rooted.
I followed the steps here: http://www.knowyourcell.com/google/...take_screenshots_on_the_google_nexus_one.html
Rooting is easy and painless. If you root, you don't have to flash a custom ROM or anything, but then you can install an app that you simply open, enable, then whenever you're doing something that you want to take a screenshot of, you shake the phone, and there it is.
First off sorry I'm sure flammage is coming but I've looked and looked through google and through xda my last ditch effort is to make a post.
I can not get windows 7 to recognize my I've downloaded the latest SDK with usb drivers but each time I try and update drivers I get "windows has determined he driver software for your device is update. Please help me
Go look for the PDANet drivers. You may have to actually install PDANet, but it's painless. Install those drivers, and adb will work for you.
This is mentioned in various stickies and other guides around the board.
This option didn't work please help pda install but didn't overwrite the driver
You need to reboot and hit f8 I believe, then choose the option to allow installation of unsigned drivers. Then try to reinstall the drivers when you boot
Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.
Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot
disgustip8ted said:
Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot
Click to expand...
Click to collapse
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.
codesplice said:
Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.
Click to expand...
Click to collapse
Thank you so much for this help all I had to do was download usbdeview the actual program it self told win 7 what to do so now my nexus one works on win 7, thank you!
No problem! Glad I could help
codesplice said:
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.
Click to expand...
Click to collapse
well played, i think youre correct.
ill have to grab that util for work...
disgustip8ted said:
well played, i think youre correct.
ill have to grab that util for work...
Click to expand...
Click to collapse
DSEO is a pretty nifty utility for sure. Provides easy one-click (okay, a few clicks, actually) access to disabling the driver signature enforcement - and even an easy way to eliminate the "Test Mode" watermark that would appear in the bottom-right of the desktop while operating in Test Mode.
There are other methods to bypass the signature enforcement without turning on Test Mode, but I've found that to be the best option. Other approaches use a boot-time hook to basically insert the F8 (and other keys as appropriate - down, down, enter or something like that) keystrokes to "automanually" disable driver signature enforcement for that boot. Any third-party application that accesses things that early in the boot process makes me a bit nervous!
Is there any way to install JUST the USB driver for 64-bit Windows (7) so I can use ADB to install and test apps on the phone, without having HTC Sync sink its hooks into Windows and try to endlessly sync things I don't want to have sync'ed (because I only use the Hero for testing apps to make sure they work on older phones)?
For future reference, does the Hero use the same USB drivers as newer phones (like the Evo3D), or did HTC switch chipsets somewhere along the line and change the driver used by newer phones?
Yes, I posted this yesterday but people didn't like... I wanted to do exactly this.So here is the way I proceeded:
I've done this for a desireHD but if HTCSync 3 is for your phone, it has to work.
Hi, here is an easy way to only install the drivers from the HTCSync package.
Double clic on setup_3.0.5579.exe (dwnld from HTC support site)
Choose the language and clic next (stop when it list the things to install: air,...)
Go to c:/user/yourname/AppData/Local/Temp
Order the files by date and choose the last folder created (so the temp folder were the files were extracted for the full package install)
Delete all *.prq except the ones for the drivers (3 files, 2 if you choose between x86 and x64)
Clic next in the HTCSync install box.
All deleted prq will be 'installed' but in fact no
Check... only drivers are installed
nb: do this if you don't have a sense ROM and don't need HTCSync of course.
Hope this will help
Edit: if you only use adb, you can dwnld the Android SDK, open it with 7zip and just extract ADB (and needed dll). No need to install the full SDK if you don't plan to make any dev. Personaly I'm only using ADB and Fastboot
Edit2: forget previous Edit... you develop apps... don't know regarding your last question but it seems there is only 2 drivers in the package x86 and x64. So I guess all device covered by HTCSync 3 share the same driver. This is just my idea, if someone knows for sure, add your comment.
update
Hey guys there's an updated version of HTC Sync.
When you go to install that, it tells you that it needs other stuff installed before it can continue (C++ redistributable, etc), two of these are the drivers you need.
Proceed with the pre-requisite installation then cancel the main installation and voila'! All is good.
pmatteucci said:
Hey guys there's an updated version of HTC Sync.
When you go to install that, it tells you that it needs other stuff installed before it can continue (C++ redistributable, etc), two of these are the drivers you need.
Proceed with the pre-requisite installation then cancel the main installation and voila'! All is good.
Click to expand...
Click to collapse
Try the SDK drivers:
https://developer.android.com/sdk/win-usb.html
You need to download the sdk, but when you launch it, just uncheck everything besides the USB Drivers.
truc007 said:
Yes, I posted this yesterday but people didn't like... I wanted to do exactly this.So here is the way I proceeded:
I've done this for a desireHD but if HTCSync 3 is for your phone, it has to work.
Hi, here is an easy way to only install the drivers from the HTCSync package.
Double clic on setup_3.0.5579.exe (dwnld from HTC support site)
Choose the language and clic next (stop when it list the things to install: air,...)
Go to c:/user/yourname/AppData/Local/Temp
Order the files by date and choose the last folder created (so the temp folder were the files were extracted for the full package install)
Delete all *.prq except the ones for the drivers (3 files, 2 if you choose between x86 and x64)
Clic next in the HTCSync install box.
All deleted prq will be 'installed' but in fact no
Check... only drivers are installed
nb: do this if you don't have a sense ROM and don't need HTCSync of course.
Hope this will help
Edit: if you only use adb, you can dwnld the Android SDK, open it with 7zip and just extract ADB (and needed dll). No need to install the full SDK if you don't plan to make any dev. Personaly I'm only using ADB and Fastboot
Edit2: forget previous Edit... you develop apps... don't know regarding your last question but it seems there is only 2 drivers in the package x86 and x64. So I guess all device covered by HTCSync 3 share the same driver. This is just my idea, if someone knows for sure, add your comment.
Click to expand...
Click to collapse
The deletion trick still works on newer versions of Sync, however, you should also edit config file (found in the same folder) and delete all the prerequisites except for BMP drivers and Driver installer. Click Next, wait for drivers to be installed and hit Cancel when it asks for confirmation to install Sync itself.
I managed to install it on both 32 and 64-bit windows 8
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.