I need a bit of help installing my Android G1 USB drivers included in the Android SDK.
When I attach my Android G1 to my pc, it doesn't ask to search for drivers to install. I believe it automatically installs the drivers, as I see "HTC Android Phone USB Device" in device manager. Though that shows up, when I check for attached devices via ADB "adb.exe included in sdk ( SDK\Tools\adb,exe )", it doesn't list my device.
What should I do from there?
PS: Is there any other application that I need? Is eclipse required.
Note: My Android G1 is unactivated ( I am trying to activate without Sim or data plan [ Via Wi-Fi I guess? ])
You need to go to the development option and check on USB Debugging, but I think you your problem is you have to download the android_usb_windows.zip for adb to see your device.
I have the USB Drivers, the issue is probably the fact that I don't have eclipse.
Maybe I should download it, yes?
{{ What ver. of Eclipse? Java EE or Java? }}
Eclipse is not required. Heck, the full sdk is not even required. There is a zip file floating around that is just adb.exe and adbwin.dll. Works fine.
In that case, how do I enable Device debugging.
I downloaded the SDK (includes adb)
where should I set the usb drivers and how do I enable them?
settings->Applications->Development->USB debugging
JesusFreke said:
settings->Applications->Development->USB debugging
Click to expand...
Click to collapse
i have done it
but still cant setup usb driver correctly.
rddhome said:
i have done it
but still cant setup usb driver correctly.
Click to expand...
Click to collapse
what instructions are you following?
go under device manager and check under universal serial bus controllers...its prolly listed under usb mass storage device. you gotta go find the correct one and install the drivers manually. also you gotta type in that setprop.blah blah nonsense on your g1 and the computer will recognize it. check the ADB setup for dummies thread
rddhome said:
i have done it
but still cant setup usb driver correctly.
Click to expand...
Click to collapse
i have code 10 error for adb interface/htc dream composite adb interface in device manager.
volcomnator999 said:
go under device manager and check under universal serial bus controllers...its prolly listed under usb mass storage device. you gotta go find the correct one and install the drivers manually. also you gotta type in that setprop.blah blah nonsense on your g1 and the computer will recognize it. check the ADB setup for dummies thread
Click to expand...
Click to collapse
thankful.
i finish it following as u said.
but what reason?
Ok i made a post and it was moved to trash and it says i dont have permission to post there so ill just move it here.....
Ok well i have been trying for like 2 hours now to get ADB to work. I followed all the guides, installed the 1.5 SDK and everything even did the Enviroment Variable thing as well. When i plug in my G1 i dont get any popup of a new device or anything. In device manager there is not ADB as well just Android Phone and when i uninstall it, it installs again on its own when i plug the phone in again. I went to cmd and typed in adb shell but i get "device not found".
Anyone know whats wrong? Btw im using Windows Vista SP1
I went into fastboot and that gave me the new driver notification so i have fastboot working but when i go to ADB i get device not found and device manager finds my phone as a universal usb device or w/e. Why wont this work?!?!?!?
It sounds like you didn't install the drivers.
Read this (I wrote it). You should have adb working in no time.
http://androidcommunity.com/forums/f28/what-is-adb-made-easy-17732/
Did you update the driver for the phone (should currently be showing as one of the USB Composite Device, IIRC) with the ADB driver included in the SDK (android_usb.inf in <sdk root directory>\usb_driver\)?
If you are using a 64-bit edition of Vista, alternatively, you can try the 64-bit signed driver found here. Also, you can try the updated driver I have attached.
Well, if you used your phone as a card reader at any point before you enabled USB debugging, then you'll have to uninstall the USB Mass Storage Device associated with your phone first. After that, unplug and plug the USB cord back in and it'll install the USB Mass Storage Device and then it'll ask about the ADB interface. That's your chance to install the driver that everyone is talking about but didn't spend the time to explain how to get there if you were in this situation...
never mind i got it. I used a program to uninstall all the Android USB drivers then i plugged it back in and it worked. Thanks for the help guys!
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.
I just upgraded my computer with Windows 10. Everything seemed to work fine with upgrading but when I put my phone into fastboot,the prompt doesn't detect my device anymore (like it did with Windows 7)
Used :
http://forum.xda-developers.com/showthread.php?t=2588979
this...
http://developer.sonymobile.com/downloads/drivers/xperia-z1-c6902-c6903-c6906-c6943-driver/
and the Google USB driver from SDK tools but my PC still can't find my phone.
Flashing kernels won't help either.
Looked online but I can't seem to find an answer...any ideas to fix this?
you probably need to reinstall the drivers, you can use Flashtool-drivers.exe found in the flashtool/drivers folder.
but you also need to probably disable driver signature enforcement to install it, instructions can be found here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Hey guys, a fellow flasher here. I've tried everything ( really everyhting i know ) but still i cant get my op3t to get recognized in adb or in fastboot.
It's just shows nothing under the list of adb device. Also in drivers section i cant make that exclamation go which means that drivers arent installed properly, but i've tried every driver and toolkit but none of them are of any help as when i go to update driver and select the option to browse to update the driver i cant find the google one. And when i connect my phone with debugging on it shows( in the right bottom corner ) drivers for adb installing but after about 5 seconds it shows failed-no driver found.
P.S-windows 7 is being used and driver enforcing is off also ive used the same pc to flash and unlock my oneplus one many times.
Help!!!
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
redukt said:
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
Click to expand...
Click to collapse
Thank you but I've tried all this but no luck.
But I've got it working now.
Things I did-
Download android SDK manager, run it as admin, while connected to internet download the Google drivers under extras section, connected op3t with debugging on, go to drivers section, update that driver manually by selecting the google folder in the android SDK folder under extras and now it's good to go!..
BTW do you suggest that should I unlock bootloader and flash twrp the traditional way or use that unified toolkit?