Database Develop

Drivers are broken

hello,
i am using vista ultimate x64. Always, my drivers and adb works perfectly. today, I tried to install HTC sync and now my drivers are messed up and my computer can't recognize my phone. I have uninstalled and reinstalled the drivers for all of the devices. I have also searched for this problem, but I could not find anything that helped.
Any help is appreciated.

drivers are working
i booted into test mode and installed the drivers

For future reference, here is how to install the drivers or fix the drivers should they not be working.
Everything you need is contained within this:
http://www.divshare.com/download/8845496-f72
This is the howto documentation
This is how to get your android phone to connect to you PC
to use functions like adb and other developer tools.
If you have installed the phone before but adb function dont work
then:
1) Run USBDeview
2) Select the list item(s) that have the word "android" within the description
3) Right Click > Uninstall
If you have done the above, or are plugging your phone in for the first time:
1) Plug in phone
2 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
2 b) If no message appears or you get a message saying drivers failed
to install. Goto device manager
2 b i) start > All Programs > accessories > run
type devmgmt.msc and press ok.
3 b) find the android device in device manager, it will have a warning icon
next to it and be in a section like unknown.
4 b) Right click and install driver
5 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
Click to expand...
Click to collapse

ADB Drivers

Hey everyone,
I have been happily using android on nand for quite sometime, and everything has been going well. However, I must have the wrong adb driver installed on my windows 7 computer and can't seem to remove it fully or install the proper one ever. Every time I remove it from device manager, and plug it back in, windows finds it as an HTC composite device, and adb through command line can't find any devices, ever! I would really like to be able to use this feature for things like tethering and what not.
Also, if anyone has any information on how to tether using any OS, windows, mac or linux, I would greatly appreciate it, along with any applications that might be helpful! I have done proxoid in the past and it worked well, pdaNet looks like it might work, but again I don't have a connection to my windows computer!
Thanks in advance for all of the help!

I am using the android SDK usb driver for ADB, you just have to edit a file and add the vendor ID. I can do things like adb logcat, adb shell gives me odd characters in directory listings,I get a ? from adb devices, not sure what that is about.
C:\Documents and Settings\Administrator\.android\adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e79
0x0bb4
The 0e79 is for my Archos tablet, works fine there. 0bb4 is what showed up in device manager when I plugged in the phone.

I tried to install that driver for my Polaris and it doesn't work.
It shows "Installing Android Phone" while I have my device plugged in. It takes forever and seems that the USB connection hangs the driver install process, but as soon as I disconnect my device, Windows shows me an error message.

Instructions for Vista\Windows 7
For WinVista/Win7
These OS will install Android as a mass storage device. You must uninstall the driver and update to the android driver model.
Instructions:
1) Unplug all removable devices(thumb drive, sdcards, etc) beside the Android phone.
2) Locate "Device Manager", usually under "control panel"
3) Select "Universal Serial Bus Controllers"
4) Select USB Mass Storage Device.
Note: to check if you have the correct device, click on the details tab and select "compatible ids" under properties. There should be three items listed under value.
5) Select uninstall driver
6) Close the window. Now in device manager a new "Android Phone USB device" with a yellow! will appear... If not, Unplug your android device or select Action -> Scan.
Note: view optional steps below if you still have problem with the your windows automatically installing drivers.
7) Click on the "Android Phone USB device"
8) Select "browse my computer to driver software"
9) Under "search this location for driver", Browse for the location that you have unzip the android_usb_windows and select the corresponding folder for your system(AMD64 for 64bit systems or x86 for 32bit systems. Right click -> properties on "My Computer" to check which system you have)
The driver is now installed and is ready to use.r
***Optional.
1. Go to System under Control Pandel.
2. Click on Hardware Tab and Under "Device Installation" select “Never search windows update for drivers”, then OK.
3. Go to Enable debugging on your phone. (Settings->Applications->Development->USB debugging).
4. Run USBDeview and remove all instances of Android Phone
5. Unplug your phone, and plug it in again.
7. Continue on step 7) above.
To turn off search windows update in windows 7, use this link below
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
To turn off automatic driver installation in windows 7, use the link below
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/

Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.

SuperJMN said:
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
Click to expand...
Click to collapse
mine hung as well, what i ended up doing was turnng off the automatic installation. Then uninstalled the adb interface driver that was already installed. Then turning back on automatic installation. Then plugging phone back in and as it was installing automatically, manually installing the adb interface driver at the same time. Eventally the automatic install would error out and the manual install would work. It took like 15 or 20 minutes for it to finish.
when i uninstalled the adb interface, it turned into ''android phone'' in device manager. That was the driver i manually installed while the phone was automatically installing. I know it dont make much sense but it worked for me.

It looks like that will be my fate as well. It also says, that when I do the manual install of the ADB drivers that I already have the most current version installed!!! OH well, keep trying!

Same behavior on my pc with windows 7 32-bits.
When I have lucky the adb driver is connected (working correctly) for a few minutes and then it's disconnected.

i've tried various things to install adb driver, since last night but i've got nothing. i can't install adb driver for my xperia arc.
i installed sdk manager and usb driver. but when i try to install or update driver, i always see this message like "you're using the latest version". So i can't install it.
and also i've tried to uninstall driver and unplugged / plugged my device. then w7 automatically install driver. so i can't install adb driver again.
i want to root my phone, using this way at this link http://forum.xda-developers.com/showthread.php?p=18805560#post18805560
so i must install adb driver, please help me.
thanks everybody
edit: i've windows 7 home premium, 64-bits

WORKAROUND: Captivate adb over USB on Glitch v14 + AOKP m6

I'm running AOKP m6 with the default Glitch kernel v14. The problem I'm was having is no adb over USB.
My PC is running Windows 7 64-bit.
The problem lies in the device showing in Device Manager as "SGH-I897" instead of one of the more common identifiers (which obviously were used by other kernels and/or ROMs as other ones worked fine).
NOTE: unless you NEED adb over USB for something, it will probably just be easier for you to use adb over WIFI. The following isn't super-hard but if adb over WIFI works for you ... use it.
What I attempted to do to fix before doing the workaround (add "tested adb: FAIL" to each step below) ... try these, they may work in your case:
Updated to latest Android SDK, rebooted
"Uninstalled" device in Windows
Tried to "Update Driver Software" using Android SDK USB driver ... error: "Windows could not find driver software for your device"
Tried to "Update Driver Software" using Samsung Kies USB driver ... same error.
(over WIFI adb) ran `setprop persist.sys.usb.config mass_storage,adb` ... no luck, Mass Storage worked before and after, no adb
WORKAROUND:
Summary: you need to add your device string to the USB driver INF file. The following ATTEMPTS to be a full step-by-step to show those who haven't done this before what to do.
Go to your android-sdk folder (assuming you have installed the SDK -and- included the USB drivers ... if not ... that's your first step)
Open %ANDROID-SDK%\usb_driver\android_winusb.inf in your favorite text editor
add the following lines to BOTH sections [Google.NTx86] and [Google.NTamd64]
;Samsung Captivate with Glitch kernel
SGH-I897 = USB_Install, USB\VID_18D1&PID_4E22&REV_0231&MI_01
For OTHER phones with this same problem (skip if you are using a Captivate)
NOTE: For other phones or other ROMs ... try the steps I outline at the end of this post to see if they work BEFORE you hack the driver file. You may not have the same problem I've had here.
You will need to change the lines you add to the file above. To find the right string to add to your inf file:
find your Android device in Device Manager, it SHOULD have a yellow "disabled" triangle icon and is probably under "Other Devices".
right-click the entry for your phone and select "Properties"
go to the "Details" tab
change the "Property" from "Device Description" to "Hardware Ids"
right-click and "Copy" the first entry (should look similar to USB\VID_18D1&PID_4E22&REV_0231&MI_01)
Replace USB\VID_18D1&PID_4E22&REV_0231&MI_01 from my lines above with the value you copied in the previous step
Replace ;Samsung Captivate with Glitch kernel in my lines above with something that describes your device. KEEP the semi-colon at the front of the line.
find your Android device in Device Manager
right-click it and select "Uninstall"
(IF your computer tells you to reboot at this point ... yeah ... you gotta ... so just come back here when done and make sure you've done the "Uninstall" step)
in Device Manager, do "Action" > "Scan"
find your Android device again, this time likely under "Other devices"
right-click the device in Device Manager and select "Update Driver Software"
"Browse my computer for driver software"
click the "Browse" button and find %ANDROID-SDK%\usb_driver\
click "Next"
if it tells you it can't find a driver for your device, SOMETHING above went wrong OR this workaround can't solve your problem
if it tells you "Windows can't verify the publisher of this software" ... select ... "Install this driver software anyway"
you're basically done. Verify it worked by trying the command `adb devices`. Your device should now appear.
NOTES:
If you have this problem, both Recovery mode and normal mode will be unable to connect adb via USB
adb works over WiFi, but I have some scripts that are expecting a USB connection and don't behave well without USB connection for sensing when the device has rebooted
I had adb over USB running on the same phone using Doc's ICS, Stock 2.2 and Stock 2.3
adb recovery mode on my phone works with Corn kernel, so I really think this is an issue with Glitch kernel rather than AOKP

[DRIVERS] Nexus 4 Driver for Windows

If you have windows, you will need these drivers to use ADB or Fastboot with your Nexus 4. The long method of getting this is downloading the SDK and running it. I have extracted the drivers and put it into a rar file for easy use.
Follow these steps if you haven't plugged your phone into your computer before.
1. Download the file.
2. Extra the files into a folder.
3. Plug your phone in.
4. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
5. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
If you already installed other drivers and they don't work for you. Download the drivers below and follow these steps:
1. Enable USB Debugging on your phone.
2. Plug your phone into your computer.
3. Go to Device Manager on your computer and locate your device. It will either be under "Android Devices" or "Other Devices" depending whether drivers have been installed or not.
4. Right click on your phone and select "Uninstall."
5. In the box that appears, check the option to "Delete the driver software for this device" then proceed.
6. When that is done, go back to Device Manager and refresh.
7. Locate your phone and right click to select "Update Driver Software."
8. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
9. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
10. Unplug your phone and restart your computer.
11. Plug it back in and everything should work.
Download link:
http://www.mediafire.com/?8xb50uktar8096i
Thanks to efrant for clarifying exactly how to manually select your drivers.

I would suggest everyone download Android SDK.
You have a Nexus device right?
http://developer.android.com/sdk/index.html

Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.

OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2

ijip said:
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
This thread is for Nexus 4 drivers, not the SDK.
Ask your question in the Q&A section.

theexel said:
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
Click to expand...
Click to collapse
Yep, I never needed the whole SDK before. I only download the platform tools too.

Have any other ADB drivers installed? Because then you need to uninstall those:
Go into command prompt and write:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
Delete all devices including driver software in the "Android Device" section.
Then reinstall the Nexus 4 drivers.
If that still doesn't work, update the driver when connected with usb debugging on and manually add by rightclicking the device, click update driver software, then the "Browse my computer for driver software", then "Let me pick from a list..." then "Show all devices" and then Have disk.
Then you simply point to the driver and select the "Android ADB Interface" (Or something like that) it also has driver for bootloader and composite, bootloader is for fastboot, can't remember what composite is for, but you shouldn't use those.

the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?

qvert said:
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
Click to expand...
Click to collapse
Go to Device Manager on your PC. If debug mode is enabled, you should see your device listed as an Android phone or something of the sort. If it has a yellow exclamation mark or some sort of symbol next to it, then that means the drivers aren't properly installed. Assuming that is the case, follow FISKER_Q's directions:
Right clicking the device, click update driver software, then the "Browse my computer for driver software." Select the usb_driver folder that you extracted and you should be good to go.

Subbed to refer to later when i have the N4
Sent from my Nexus S

jark99 said:
Subbed to refer to later when i have the N4
Sent from my Nexus S
Click to expand...
Click to collapse
This thread is also in the Misc section of the reference guide in case you can't find it later

I did the same thing and I cant get adb to see my device however fastboot will =/

Shambala001 said:
I did the same thing and I cant get adb to see my device however fastboot will =/
Click to expand...
Click to collapse
Did you enable debugging on your phone yet?
If not, go to Settings > About phone, then tap on "Build Number" 7 times. Go back to settings and you will see developer options. Go in there to enable USB debugging.

Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.

Nitemare3219 said:
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Click to expand...
Click to collapse
Glad you got it figured out. :good:

I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.

Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Try leaving the phone plug in. Go to Device Manager. Find the ADB drivers and uninstall it. While in Device Manager, have it scan for new changes. You should see your phone appear. Right click it and manually install the drivers.

Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.

IAMLordspeed said:
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
Click to expand...
Click to collapse
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.

Stryder5 said:
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Click to expand...
Click to collapse
I had to put a check in the box next to "Delete the driver software for this device" to get this to work. Otherwise Device Manager will keep detecting the old drivers.

can't install drivers on win7 or win10

i've tried all suggestions to install the drivers and when i connect my fire to my computer, it shows up as portable device > fire. if i try to update drivers, it says that i am already using the best one, the MTP usb device.
i've followed this:
http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
and also tried the drivers from amazon and neither allow me to select the adb driver.

You have turned adb on on the Fire?

Pond-life said:
You have turned adb on on the Fire?
Click to expand...
Click to collapse
thanks for the reply.
yes, i put it in dev mode by tapping the serial numbers and it is adb enabled.

ultraman69 said:
and also tried the drivers from amazon and neither allow me to select the adb driver.
Click to expand...
Click to collapse
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.

i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
thekrakah said:
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
Click to expand...
Click to collapse

ultraman69 said:
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
Click to expand...
Click to collapse
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.

i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
thekrakah said:
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
Click to expand...
Click to collapse

for some reason, on only one out 4 of my win 10 rigs, i had to turn off driver signature enforcement. to do this go to settings, update and security, recovery, advanced startup, restart now. then in the restart menu push, troubleshoot, advanced options, startup settings, then restart. when booted choose "Disable driver signature enforcement" (which is option 7 on current build). now try to install the drivers. after successful just do a normal restart to enable the signature enforcement again

ultraman69 said:
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
Click to expand...
Click to collapse
Can you verify that, "android debug" mode is turned on in the Fire devices developer settings? At least that was the only way I could reproduce the same message output from "adb devices".

I faut with my win 7 laptop for about an hour with one of my fires. Has the yellow icon on unknown device. Ended up "update driver" "browse for file" "let me choose from a list" picked Android/adb composite device. Adb and fast boot now work. I originally had to install Android studio and some extras to get my first fire to link up. Pm if you need help.
Sent from my Nexus 6P using Tapatalk

I recommend RootJunky tool, does everything and gives you instructions what to dohttp://www.rootjunky.com/amazon-fire-5th-gen-supertool/ Also recommend watching all his videos https://www.youtube.com/watch?v=sVv1D_LNLTg&feature=youtu.be