Has anyone been able to access their touchpad via ADB on with CM7 Alpha?
If so, what's the trick. I'm running Win7 Pro 32bit, Android SDK is installed with the latest Java 1.7 and USB debugging is on and displayed in notification.
FYI - I'm used to using ADB with my droid eris on GSB so I've tried most of the known stuff. Are there ADB drivers for the TouchPad around?
Thanks in advance.
All ADB drivers are in essence the same, you should be able to use the official ones Google releases with any device.
To get ADB running with my TouchPad(Windows 7 x64) I had a USB Mass Storage Device with the hardware id(USB\VID_0BB4&PID_0C02&REV_0227) I had to go an change the device driver to a USB Composite Device, once I did that the ADB interface showed up and I was able to install the driver.
The mass storage device I changed was this one (USB\VID_0BB4&PID_0C02&REV_0227) and not this one (USB\VID_0BB4&PID_0C02&REV_0227&MI_00).
Here is a link to the Official ADB Google driver http://api.ge.tt/0/8FtSNo8/0/blob/download you may need to force the driver to install.
Worked perfect. Thanks!
adbWireless ftw. No need for cables/drivers.
https://market.android.com/details?id=siir.es.adbWireless&feature=search_result
This worked for me. No modded .ini file or driver needed.
It detected and installed the"USB Composite Device" automatically.
http://rootzwiki.com/topic/6622-cm7-adb-driver/
win7 x64
Related
Hi.
I'm trying to make some custom native software for android but I need some help getting started.
What I have done so far is getting a HTC Hero, GSM version.
Flashed a custom rooted ROM. update-hero-generic-2.73.405.38-rooted-signed.zip
Installed the sdk and ndk on Windows.
Downloaded and built the open source android project in a VMWare ubuntu image.
What I'm trying to do now is to get ADB talking to my Hero.
I have USB debugging on in the applications->development menu on in the Hero.
When I attach the phone to my XP PC it detects it and asks for drivers, I point it to drivers in android-sdk-windows\usb_driver, windows won't load them because they do not match the hardware.
I can install the driver manually but eventhough the device manager lists it as working (android phone with android composite ADB interface) adb cant find it.
adb devices just give me an empty list.
I tried this on a Windows 7 box and it seemed to work there, is there something special I need to do to get it working on XP?
Installing HTC Sync (drivers included) should resolve.
Thanks!
I actualy tried that before posting but it did not seem to work.
I now tried it again and this time I manually installed the driver in the HTC directory and now it works.
Previously, I was on TRON 1.2 and had no issues with ADB and/or USB tethering.
Since updating to TRON 2.0, I have not been able to tether my usb connection via adb (ive tried clockworkmodtether, pdanet, klink).
USB debugging is enabled. I tried disabling, rebooting, and enabling again, but I have had no success.
When I run "adb devices", it tells me my device is offline.
BTW, I am on windows 7 64 bit.
Thanks!
trud9340 said:
Previously, I was on TRON 1.2 and had no issues with ADB and/or USB tethering.
Since updating to TRON 2.0, I have not been able to tether my usb connection via adb (ive tried clockworkmodtether, pdanet, klink).
USB debugging is enabled. I tried disabling, rebooting, and enabling again, but I have had no success.
When I run "adb devices", it tells me my device is offline.
BTW, I am on windows 7 64 bit.
Thanks!
Click to expand...
Click to collapse
To use adb in 4.2.2, you need the most recent version of Android platform-tools from the SDK. Open the SDK Downloader like you did when initially installing adb and update the platform-tools package. (Make sure you kill any instances of the current adb process/daemon running on your computer.) It should be able to connect after that, although you'll be asked to authenticate it on your phone the first time you try.
El Schisne said:
To use adb in 4.2.2, you need the most recent version of Android platform-tools from the SDK. Open the SDK Downloader like you did when initially installing adb and update the platform-tools package. (Make sure you kill any instances of the current adb process/daemon running on your computer.) It should be able to connect after that, although you'll be asked to authenticate it on your phone the first time you try.
Click to expand...
Click to collapse
Thank you, I updated my sdk and its working like a charm!
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
kam5iz said:
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
Click to expand...
Click to collapse
For me. Go into Device Manager and find the unconfigured device and manually assign the driver to it.
EDIT: Which you may need to get the android sdk and download the usb driver and manually assign it with those.
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!
Is there any signed adb driver for GT2 Pro for Windows 10? I can see only WinUsb device "ADB Interface" after connection but empty adb devices list. On Windows 7 I can use legacy method but it doesn't work on W10. Thanks.
Go to Windows update and check for updates. It should show compatible adb driver. Manual adb driver install did not work for me. Also make sure to use up to date platform-tools.
I have no problems with windows 11 everything works, before I had win 10 and also no problems
I found a Driver setup file in Android 13 image. I have installed it and restarted the pc. After connecting the phone I can see signed Android Composite ADB Interface (made by Oppo) in the Device Manager but still after executing adb devices there is no device in the list.
OK, found the root cause, if somebody has a similar issue, it works with minimal adb fastboot v1.4.3 from here