So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
Related
I have a Gtablet in which I was able to install and use NVFlash. I used the recommended driver for this process and it works perfectly. Now here is my new problem / challenge. I am trying to learn SDK ADB. As parts of the procedures, I have to install the Google USB driver to have the device recognized as an android device (Or something in that line as per the instructions). Here are the problems:
1.) My Gtab show on the device manager as a storage device and a portable device with the same drive letter as the storage device
2.) I'vr tried removing the NVflash USB driver, but it does not uninstall. Every time I re-connect the device it re-install the driver and goes back to problem 1.)
3.) I used (USBdeview) to try and remove the device and the driver from my win 7 x64 but it just don't uninstall or stop the decive or anything.
4.) I tried updating the driver of the gtab (As in problem 1.)) and it says that the current driver is the most appropriate for the device. And goes back to problem 1.)
In other words..... I am tied up with the NVFlash driver (Tegra I beleive, which is the one described on the NVFlash How to). I am trying to SDK ADB, but it will not allow me to connect cause the Gtab is not recognized as an Android device, but as a storage device or nvidia tegra when in APX mode (I beleive it called).
which step am I missing or doing wrong?
Thanks in advance
Please excuse my lack of technical lingo.....
Did you read the sticky message: adb for your gtab (windows) in the general section?
I had the same problem, except I'm using windows XP. The storage device is not the driver to uninstall. Device manager never showed me any other drivers relating to the gTab.
Using USBDeview I was able to see a different driver (can remember was it was called exactly), uninstalled then reinstalled using the usb driver I downloaded from google and everything was fine.
Ok hopefully this helps someone. After flashing the amazing AOKP ROM (literally best ROM I've ever flashed...Holy stable batman) I noticed that on Win7 x86 or x64 that USB file transfer to/from SD card worked fine...as did Odin but Windows could not find a driver for my phone anymore. This creeped me out because this meant adb would not be able to connect. Running the adb devices command would not show anything.
I tried 3 different Win 7 machines and a WinXP machine all of them used to work but now they didn't I read the FAQ, I goggle searched xda and droid forums and tried everything, cables, switching USB ports, phone settings, dev settings, new usb drivers but, I could no longer get adb to connect.
So I started looking closely at the Samsung USB drivers I have on my machines which worked fine on stock ROMs, and a few other custom ROMs (not blaming AOKP no disrespect) and I found that the hardware id for my device changed and the device string wasn't referenced in any of the USB drivers files. So I forced the correct driver to install and it worked! So if that is all you need to know cool, if you some of you need the steps here they are:
I'm assuming you already have Samsung USB drivers and adb from the SDK installed (if not there's tons of info on this site to get both)
I'm also assuming you installed the USB drivers so they are in the default location, if you extracted a zip file or something you will need the path to the USB drivers
Last assumption... I tried 3 different versions of Samsung USB drivers and for each one the ssadadb2.inf that has the ADB driver was in the USB Drivers\16_Shrewsbury folder...If you don't find it there do a search in the USB Drivers folder and reference that location for step 13
Click Start button, then right-click Computer, then click Manage
Click Device Manager
Expand Other devices, you should see SCH-I500 with the yellow exclaimation point
Right-click it then click Update Driver Software
Click Browse my computer for driver software
Click Let me pick from a list of drivers
Scroll up, highlight Show All Devices, click Next
Click Have Disk
Click Browse
Browse to C:\Program Files\SAMSUNG\USB Drivers\16_Shrewsbury
Double-click ssadadb2.inf, click Open, Click OK
Highlight SAMSUNG Android Composite ADB Interface, click Next
You will get an "Update Driver Warning" saying cannot verify compatibility with your hardware, click Yes
You should see Windows has successfully updated your driver software, click Close
Back in device manager under ADB Interface you should see the driver name you just added....the entry under Other devices should be gone
Connect your data USB cable (not a charging only cable...if you can't tell the difference just be sure you used this cable for data before)
Open a cmd prompt (start>run>cmd enter if you didn't know)
browse to where you installed adb and type "adb devices"
You should see your device and a serial number again....back in business
Like I said no disrespect to AOKP I rock my B31 (soon to be 32) Pink Unicorn proudly This hopefully applies to anyone who had a hardware id change from any ROM.
Hello everybody!
I have a problem related to connectivity between my desktop (Windows) and tablet (Android 4.1). I bought a new device (Colorovo City Tab Vision 7) and now I want to use it for testing of my applications, because emulation of android is very slow on my computer, although I forced it to create snapshot every run.
I have downloaded SDK with Google drivers and also some unofficial drivers I found on web. When I connect my device, it first appears 'Other device' (label is CTVision7) and it's marked as unknown. I tried to install drivers (Google) for it, but windows said that they aren't suitable for my device, as it's not able to find them in specified directory.
After these attempts I tried unofficial drivers. Their installation worked and now my device appears as Android phone, what seems to be good.
But when I run
Code:
adb devices
or launch application in eclipse, there's not avaible device.
I have turned USB debugging on, so it should work.
Am I missing some step to make my device avaible for debugging, or are my drivers wrong? Is there any way to get drivers which surely work?
Anybody else got problems with connecting to the PC with the USB cable?
What "problems" are you having?
The Windows Explorer does not start, though there is the sound when connecting the USB. Tried uninstalling the driver and letting the system reinstall upon connecting, but still cannot see Nexus 9 in Windows explorer. In Linux get the the notification and clicking on the "open with File Manager" gives a quick error message - too quick to read. So I am wondering if anyone got this problem??
Sent from my Nexus 9 using Tapatalk
Same here
I updated my SDK files, but that didn't seem to work either. It does show up as a camera when I change from MTP, so I just started sideloading apps, files, and books to the picture folder, then using a file explorer to move them to the correct folder.
+chuckie59 So I am not alone with this problem! Have used AirDroid to copy things over.
Sent from my Nexus 9 using Tapatalk
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Same for me. Only ptp working. Google USB ADB drivers instaled
mkygod said:
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Click to expand...
Click to collapse
You'll never get it to show up as a driver letter. Android gave up on mass storage a couple of versions ago.
Sent from my Nexus 9 using XDA Free mobile app
If you are on W8.1 then you may have the "ACER Composite ADB Interface" - A Microsoft upgrade fault.
A search for "ACER Composite ADB Interface remove error delete" should give plenty of hits. Here's the first post from http://forums.androidcentral.com/google-nexus-7-tablet-2012/362325-nexus-7-not-recognized-computer-2.html :
Would you happen to know if any Acer drivers are installed on your computer? Here recently there was a Windows Update that installed the wrong driver and made it so that I had the exact same problems as you're having. Here's how I fixed it.
Go To> Control Panel>Hardware and Devices>Device Manager. In Device manager look for something along the lines of "ACER Composite ADB Interface", at least in my case I had the wrong ADB interface installed. You'll know if you have the wrong drivers if you go to Devices and Printers and right click your Nexus 7 and go to it's properties. It should be under the hardware tab where it lists it. If it doesn't just say Nexus 7 then follow these instructions. Once you find it in the Device Manager (once again in my case it was the ACER Composite ADB Interface causing the issue) right click and and uninstall it. There should be a dialogue box that pops up right after which will ask you if you want to delete the drivers. Check this box and proceed with the uninstall. After successfully uninstalling the drivers plug in or unlplug and plug back in your Nexus 7. It should show up now with the correct drivers installed.
Thanks, but I am on Windows 7. Driver is ClockworkMod Ver 7.0.0.1 dated 2012-08-27, which Windows reports as up to date (?). Works for PTP but not MTP.
I have had problems with other devices including the nexus 5 and nexus 10 to connect over mtp. Previously i used the nexus root toolkit which has some wizard to guide you to install proper drivers for mtp and adb. The toolkit is yet to support nexus 9 but you can still use the wizard to uninstall the old drivers and reinstall correct ones
Updating sdk. Uninstall and installing again driver did the trick for me
SORTED!! (sort of) Updated sdk and uninstalled and installed the driver again, but it did not do the trick for me. Gave up on Win7.
Instead had a go on XP. Initially everything the same. Noticed two choices of compatible hardware given: "Google Nexus ADB Interface" (the one I had installed already) and "USB Composite Device". Tried the latter one, and yes it did install. In the device manager it turns up as "Portable Device/Nexus 9" (and not as "Android Phone/Google Nexus ADB Interface" as before).
In Windows Explorer it is shown as "Nexus 9/Internal storage" with all the directories, and actually when inserting the USB I do get auto start. By the way, was having the USB debugging disabled. The driver is Microsoft dated 2006-02-22 version 5.2.5326.4762 - which is not what I would have expected. But it works!
Will try to get something similar to work on Windows 7
SORTED! Yes also Win 7 - and it was easy. Uninstalled the driver, plugged in the USB and it installed! Also got the auto start to choose action. It now turns up as "Portable Devices/Nexus 9" in the device manager and as "Nexus 9/Internal storage/etc" in Windows Explorer. The driver is now Microsoft ver 6.1.7600.16385 dated 2006-06-21. Strange. As long as it is working!
Hello. I'm a happy (?!) user of Win 10 Pro x64 since few days.
I want to connect my RN4X Snapdragon to PC, using usb on my pc's motherboard.
However, despite setting option, that I'll listed below, my phone is still not recognisable as useful stuff.
Without changing anything on my phone since my last flashing topics (Feb and March this year), I was fully able to connect easily to pc with win7 x64. I also was able to connect (using Xiaomi's cable, cheap replacement does not seem to work) phone to win 8.1 x64, where only the basic adb fastboot were installed. But, I cannot do the same on newest Windows.
I've done:
1. Installing minimal adb and fastboot 1.4.3. for all users (I'm the only one account here, but not sure if that's matter)
2. Having programming option enabled, usb debugging enabled and all that good stuff.
3. All four elements on that list - https://************/how-to-fix-mtp-devices-not-connecting-on-windows-10/
4. I've tried to install it as adb interface, installing it manually, installing it by using *.cat files from xiaomi_usb_driver archive, that contain that kind of stuff for newer windowses (it's from this side, if I remember it right - https://www.xiaomiusbdrivers.com/2018/02/download-xiaomi-usb-driver-2018-for_4.html)
5. Almost all stuf from here - https://www.jihosoft.com/android-tips/windows-10-cannot-recognize-android.html. Because I do not have Samsung, Odin mode is not an issue
6. I've tried to install my Redmi 4X as MTP device. However, my phone during each connection to PC started himself in charging mode (I can change it). Even changing it doesn't changing anything, though.
7. Editing the bulid.prop, adding there few lines describing how the phone should behave. I've saved it, but my original version of bulid.prop does not have anything in there about types of connection. I don't remember it word by word, but I've could check in history if anyone will find it interesting.
Drivers for usb 3.1 are pre-installed with mine version of win10 (I cannot install drivers given on my motherboard's dvd attached, system says that I'm currently having them).
When I try to install it manually via device manager, on the first time it says, that is other device, identifed briefly as MTP. However, installing it either as Android ADB interface, fastboot interface or third option does not give me anything. What's worse, even when I've pick windows/INF as my source of drivers for this device, it does not list on "lemme pick ddevice type" MTP type devices. I'm using win 10 in polish, so it might be that I'm blind or does NOT understand translate.
What else could I do? I can of course use wife's laptop with 8.1, usb sticks or other stuff, but I would like to have it sorted out.
Does otg still works to your device?
whatpigs said:
Does otg still works to your device?
Click to expand...
Click to collapse
Not sure. How to check it? We use to have 16GB OTG to USB2.0 (other end was micro usb B), but we must have put it somewhere during moving out to new flat, cause I cannot find it now.
gonna bump it, cause there's not any clue yet.
Same here.