[Q] Can't Install Google ADB Drivers - Nexus 7 Q&A, Help & Troubleshooting

I recently downloaded the Carbon backup app so I could back up my Nexus 7 before I root it. However, when I installed it, it needed to connect to my computer before I could use the app. When I connected to my computer, it said I needed to install the Google ADB drivers. So, I downloaded the drivers from Carbon's website, but when I tried to install them in Windows 8's device manager, it said that no drivers could be found in the directory I specified. I do have the drivers unzipped, and I had it check for subdirectories. I tried doing the same process with the Nexus Root Toolkit, but it ran into the same problem. Even when I tried to run the backup utility, it was unable to reboot my device to start the backup process. What should I do to get these drivers installed? I am running Windows 8 64-bit and my Wi-Fi 32 GB Nexus 7 is running 4.2.2. Every time I try to install a driver, I get the error "Windows was unable to install your Nexus 7." I have tried various Google and Asus USB drivers, and none were able to install.

http://bit.ly/10aCleQ

Pirateghost said:
http://bit.ly/10aCleQ
Click to expand...
Click to collapse
That pretty much summarized how I spent my free time today.

lisalover1 said:
That pretty much summarized how I spent my free time today.
Click to expand...
Click to collapse
so basically you didnt bother to try turning off the driver signature as instructed in the FIRST link?

Related

Google Maps, Facebook and ADB

Hello All.
I've had my UK, T-Mobile G1 for quite a while now. I have rooted it and it is running the latest CyanogenMod recovery image and ROM. I also have Apps2SD set up on my 8GB SD card, on a 512MB ext partition. This was all working fine until the problems below occurred...
I'm having some problems with several apps and ADB.
My PC runs Windows 7, 64 bit, and I can't seem to find a driver for the G1's ADB. I'm probably being incredibly stupid, but I just can't find one. I have used one before on Vista, where I had to set some boot options, but I'm not too sure / happy about doing that on my nicely functioning Windows 7. And as my friend once said; "You mess around with windows, then windows will mess around with you"...
But, anyway, I can't seem to get ADB working, if someone could either send me a link to the drivers or guide me through it, I'd be grateful...
Also, it may be due to me running CyanogenMod, but if I try to update the Facebook app, it downloads the app, and then when it tries to install, gives me the error "Installation Unsuccessful - Incompatible Update".
And with the Google Maps app, it says "Installation unsuccessful - Package file was not signed correctly". This may be due to me trying to get the hacked version of the app to get the Google Maps Navigation working in the UK, but I couldn't get that to work, so I uninstalled it and Nav Launcher, and now when I try to update from the Market it gives me that error.
I've seen a guide online with ADB commands, but as I have no access to ADB, I'm a tad screwed. I've tried runnign the commands in the Terminal Emulator in the phone, which does approximately nothing whatsoever.
So, can anyone give me any guidance on any of my Android problems?
Thanks in advance - Ethan
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Ah. Looks like I'll be reinstalling Ubuntu then for the ADB. Thank you for such a fast response.
- Ethan
jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Lies, I'm running windows 7 64bit and ADB works fine.
chris4500uk said:
Lies, I'm running windows 7 64bit and ADB works fine.
Click to expand...
Click to collapse
In that case, do you remember where you obtained the driver from? I would love a link, or a zip file or something...
I'm on Vista x64 SP2 and I can use ADB just fine. You just need to download the SDK and then get the USB driver through there. It used to come included, but now you need to use the ADV and SDK manager and download the drivers as an SDK Component through there.
After that, make sure your phone is set to USB Debugging mode and plug it in then point windows to the new drivers. If it doesn't want to install the new drivers, you might need to remove the old ones first. I had to use USB Deview (DL link at bottom of page) and removed all installed HTC drivers. After that I plugged my G1 back in, pointed it at the newly downloaded drivers and all was well.
I'm running adb/fastboot/android sdk on win7 64b ultimate. The drivers are included in the sdk download. Once you download the sdk, make sure you have java installed. (I had to install JRE and JDK to get it to work properly, not sure if this was needed) Anyhow, when you have the sdk downloaded, run the sdk setup program. Go to settings and check the box for force update (unsure of the exact terminology used there) then go to available updates and your drivers are the last option on the list.

[USB Drivers] Galaxy S GT-I9000 (Working on ICS)

Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.

Getting ADB to work on Windows 8? (Manual upgrade to Android 4.2)

Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Installing Windows 7 Drivers Please wait
Operation Started
android_winusb.inf
The resource loader cache doesn't have loaded MUI entry.
1
0
An Error Occured. Returning to Main Menu.
---------------------------------------------------------------------------------
If you got the message [the resource loader cache doesn't have loaded mui entry]
during the installation procedure dont worry as the drivers have been installed.
Click to expand...
Click to collapse
PCServe said:
Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Click to expand...
Click to collapse
Do you have Android SDK installed?, if so try the following, you're using Windows 8, right?
On the 'old' Windows Desktop, right-click on the bottom left corner
> Select 'Command Prompt (Admin)'
> type ' devmgmt.msc '
> Right click on the driver with warning sign and select update driver > select BROWSE and go to the extras\google\usb_driver\ folder of your SDK and then update the driver. Did that resolve the issue?
It works for the Nexus 7 when it's running, not in fastboot though
PCServe said:
It works for the Nexus 7 when it's running, not in fastboot though
Click to expand...
Click to collapse
Have you rebooted the PC since installing the drivers?, if not give that a go and try again, they may need a reboot to complete the installation.
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
Windows was unable to install your Nexus
Windows could not find 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.
Click to expand...
Click to collapse
I also tried the drivers from ASUS with the same result.
PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
Did you try browsing to the driver location instead of letting Windows find the driver?
This driver has helped others
http://forum.xda-developers.com/showthread.php?t=1766220
PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
turn off driver signing and then do it.Mine works fine in Windows 8..check this for reference:-
http://forums.mydigitallife.info/th...ble-driver-signature-enforcement-in-Windows-8
Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!
PCServe said:
Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!
Click to expand...
Click to collapse
Glad to be of help

[Q] Nexus 4 ADB on Windows 7 Home

After several hours of frustration, I'm just going to ask.
I have USB debugging enabled. When I plug in the Nexus 4 Windows auto installs drivers for MTP.
It's listed under portable devices in device manager. I am trying to uninstall the driver and install the Naked driver. But as soon as I uninstall in device manager, Windows reinstalls, despite me having turned off auto-installation of drivers. I am not able to use the advanced method listed here http://www.addictivetips.com/window...utomatic-driver-installation-in-windows-vista because gpedit.msc doesn't exist for Home users.
I have unplugged the device and manually put it into Fastboot and plugged it in. Windows does not try to autoinstall drivers. I am able to install Naked drivers and the device appears as "Android Phone" in device manager.
How can I proceed?
Donteventrii said:
After several hours of frustration, I'm just going to ask.
I have USB debugging enabled. When I plug in the Nexus 4 Windows auto installs drivers for MTP.
It's listed under portable devices in device manager. I am trying to uninstall the driver and install the Naked driver. But as soon as I uninstall in device manager, Windows reinstalls, despite me having turned off auto-installation of drivers. I am not able to use the advanced method listed here http://www.addictivetips.com/window...utomatic-driver-installation-in-windows-vista because gpedit.msc doesn't exist for Home users.
I have unplugged the device and manually put it into Fastboot and plugged it in. Windows does not try to autoinstall drivers. I am able to install Naked drivers and the device appears as "Android Phone" in device manager.
How can I proceed?
Click to expand...
Click to collapse
Try checking the drivers thread link in my signature.
Stryder5 said:
Try checking the drivers thread link in my signature.
Click to expand...
Click to collapse
The problem is that Windows is auto-installing the driver as soon as I uninstall it from device manager. I have this setting disabled in Device Installation Settings but nevertheless it continues auto-installing.
Donteventrii said:
The problem is that Windows is auto-installing the driver as soon as I uninstall it from device manager. I have this setting disabled in Device Installation Settings but nevertheless it continues auto-installing.
Click to expand...
Click to collapse
When you plug in your n4 in your pc, does it allow you to open the folder for your phone. If it does the drivers are installed. Mine n4 did the same as you when I plugged it in my PC, and did show Android in the device manager.
Use the nexus 4 toolkit to do it.
http://forum.xda-developers.com/showthread.php?t=1995688
jt.61 said:
When you plug in your n4 in your pc, does it allow you to open the folder for your phone. If it does the drivers are installed. Mine n4 did the same as you when I plugged it in my PC, and did show Android in the device manager.
Click to expand...
Click to collapse
It's showing up as portable device, not as Android when MTP is connected. If I manually boot into fastboot, and connect to PC it will show as Android.
Nexus 4 toolkit doesn't work. When I connect the device, it still only shows up as MTP device connected.
How can I stop the "Nexus 4" driver from auto installing the MTP driver?
Nobody else is having this problem?
Sent from my Nexus 4 using Tapatalk 2
Donteventrii said:
Nobody else is having this problem?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Bump
For the love of bump
...
Sent from my Nexus 4 using Tapatalk 2
You could try this installer. If a prompt ever says not to install a driver just do it anyway.
http://www.junefabrics.com/android/download.php
I was having the same issues, toolkit didnt work, auto kept auto installing MTP only, junefabrics.com didn't work by itself, LG drivers didn't work. finally I tried the drivers in sig and adb was installed but the tool kit still didn't recognize it. I ran the one from junefabrics.com after that and hit no to not reinstall the drivers when it asks, but it's hanging when installing pdanet on my phone.
TCMan5190 said:
I was having the same issues, toolkit didnt work, auto kept auto installing MTP only, junefabrics.com didn't work by itself, LG drivers didn't work. finally I tried the drivers in sig and adb was installed but the tool kit still didn't recognize it. I ran the one from junefabrics.com after that and hit no to not reinstall the drivers when it asks, but it's hanging when installing pdanet on my phone.
Click to expand...
Click to collapse
im in the same boat
I'm having these same issues. Very frustrating.
Just fixed the problem by following the directions in this post - http://forum.xda-developers.com/showpost.php?p=34154052&postcount=7
His instructions about cmd prompt didn't work for me, so in device manager I selected View -> Show Hidden Devices.
I removed all android, nexus, other android phones and then reinstalled the drivers via the toolkit. Seems to be working so far!
The MTP driver will always install as that's nothing to do with adb. If you open Device Manager it should have the other option - you then manually install the driver by browsing the the drivers folder when using the 'Update driver' option in the right-click menu when you click on it in Device Manager
BUMP
Donteventrii said:
...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I am having the same problem my windows xp is not reading I install a couple of different drivers still nothing. This the only phone/tablet I am having this issu that my pc is it's not reading the files of my phone.
OTA JOP40D
2nd Batch phone
hello, now nexus 4 updated to 4.2.2 and when i connect to computer the device could not be found
i updated SDK , all the required things inside android 4.2 but still device not found
is there drivers that i can install instead of checking for updates and so on?
jasonmiracle said:
hello, now nexus 4 updated to 4.2.2 and when i connect to computer the device could not be found
i updated SDK , all the required things inside android 4.2 but still device not found
is there drivers that i can install instead of checking for updates and so on?
Click to expand...
Click to collapse
Try downloading pdanet on your pc or downliad a nexys4 toolkit from here and they let u install the drivers
Sent from my Nexus 4 using xda premium
casonswag said:
Try downloading pdanet on your pc or downliad a nexys4 toolkit from here and they let u install the drivers
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried pda but failed
its caused by the android 4.2.2 update...
For anyone still having problems, these are the steps I followed that fixed it for me. (After updating to the latest sdk version and downloading the google usb driver)
1. Uninstalled the driver from Device Manager
2. Let it automatically install the generic 'MTP device driver'
3. Right clicked on the new device and selected 'Update Driver'
4. Selected 'Have Disk' and pointed it to [android-sdk-dir]\extras\google
5. Watched an 'ADB' driver install.
6. Opened Eclipse to successfully run on my N4.

[Q] How do I install the damn drivers?

Well guys I've been trying for hours now, whenever I try to install the USB drivers in order to unlock my bootloader, when I plug in my Nexus it installs the MTP drivers on it's own, if I try to install the google drivers downloaded from ADB all I get is a message saying the best drivers for my device are already installed and it doesn't let me overwrite them.
If I go with the use disk option it doesn't let me choose the usb_drivers folder because it just wants to use a .inf file, whener I follow the instructions the toolkit dictates I read the dead end with the "The best drivers for your device are already installed"
I'm so angry right now.... Please help me.
Are you on a Windows XP operating system by any chance? There are major issues with MTP mounting on WinXP regardless of the service pack you're on. Some people claim they've gotten things working by updating WMP, via a Naked Driver and even by installing the Android SDK. Let me know if you are indeed on WinXP & I'll get you some links
Did you try following Wug's Nexus Root Toolkit to install the drivers? That helped me. I cannot post a link so look around for it.
I'm running Windows 7 64 bit, thanks guys, I just gave up and did it in my sister's laptop, it worked on the first damn attempt, maybe the drivers of my N10 were screwing something up, that's my best guess.
Glad you got that sorted--just for future reference, a common recommendation for people having driver issues with their Nexus devices is to simply go into Win Device Manager, uninstall all your current Nexus & ADB drivers and restart. Then plug your phone in via USB and let the auto installation do its thing. Usually this fixes all issues w conflicting device drivers

Categories

Resources