first of all, i solute all u fine chaps for doing amazing work on hd2 android.
i have a questino about adb usb drivers. i have nexus1 android on my hd2and it seems perfect apart from the fact that everything installs on internal mem and not my sd card. i read a thread about how to go around it by downloading android dev sdk and usb drivers and use some commands to change default install location. keeping it simple, i have installed the sdk but usb drivers have made me pull my hair out all night. i have tried forcing drivers, reinstalled usb mass storage drivers, plugged in - out usb countless times, u name it but the error windows give me is failed because adb composite service is either disabled or not running plus when i do adb devices, it starts the demon but doesnt give device id. in device manager it shows yellow triangle on adb.
i have win vista 32bit.
plz someone help me or i will be a bald man soon getting stressed out...
thanks chaps...
Anyone,,,,?
Still unable to do it, spent 5 hours last night but no results. Feels like ADB USB drivers have something against me..lol
i had huge problems with drivers too and windows 7 64. Try your drivers on another computer with same os, I was surprised it worked. After hours of threads reading I finished by making a mistake with usbdeview and corrupt some usb files -> format
After that I found that changing of android rom helped a lot too. Now all its working perfectly, I hope you will find a less painful solution ...
Related
Hello
I have a stock Vodaphone Magic and I'm looking to root it, but to do this I need to get adb to see it, which I'm having problems with.
When I plugged it in first to charge it used window's default drivers for the SD card etc. Trying to update the drivers with the ones included in the SDK dosn't seem to work as Windows says that they're less recent.
Also, I can't see any sort of "ADB" section in the device manager, even with USB debugging turned on in the phone.
Any help? I'd really like to root my phone so I can use WPA Enterprise!
Edit: Already read the wiki page, no help.
I remember having this problem when I first set up the Android SDK.
However in my device manager I did have a device, it wasn't called Android or Magic or anything similar. From what I remember it was a bunch of random letters and numbers.
From there I right clicked it, went to Properties, Update Driver and then pointed it to the directory with the drivers.
Thats how I did it in Windows 7, if that doesn't work for you then I'm not sure sorry.
Hi,
I recently had the same problem as you. The first time you plug in your phone sometimes Windows will assign USB drivers to the device instead of the ADB interface. To correct this, I uninstalled the drivers and pointed the computer to the ADB files as the new drivers. After those install it should be labelled correctly and work.
Does anyone else have to jump through hoops to get ADB to recognize the Vogue? It seems just like a collosal mess of drivers, which is even worse because different Android builds (2.01 vs 1.5 vs 1.6 vs 2.1) all behave differently.
I'm running Win7 and android via Haret and it is a complete cluster-xxxx of USB drivers. I have the android sdk usb drivers installed, but windows wants to install mass storage and/or usb composite. Then, there is a driver called HTC Dream Composite ADB interface. ADB works for me most of the time when this driver gets installed.
Earlier, I had adb working. Then I accidentally unplugged my usb cable. Plug it back up and I'm back in driver hell.
AARGH! Is this just my problem?
Similar problem
Nope...I've got a similar problem...windows recongnizes my Android ADB device...then when i try to use ADB or ADB explorer...it just won't connect and says their are no devices present. If i leave the hardware screen open...it will put an ! over my device when I try to access it via ADB. Still haven't gotten it to work...gonna try a differnt comp. I'm trying to push the new GPS libs.
are either of you running x64?
No
Windows XP 32 bit.
wasn't it said plenty of times that adb currently doesn't work in windows on nand?
Who said nand? I count one haret and one no comment.
im supposing if it doesn't work in nand, i doubt it would in haret.
I am hoping someone can help me before the ICS OTA hits in the US.
I am trying to root, but I can NOT get ADB to see the TPT.
I am using win 7 64 bit, and have downloaded the adb driver and modified the .inf. It shows up in dev man under android phone as thinkpad adb, but when I run adb devices...nothing.
I installed that latest Java dev and android stk but still nothing.
The TPT is on OTA 2.5.
I have searched everywhere but cannot fined any answer.
Any ideas?
Thanks!
Is USB debugging enabled on your tpt? Did you try a different USB cable/port? On your PC are you in the same directory as adb.exe?
Yes, Yes, and Yes.
ADB is running fine...it just cant see the TPT even tho windows can.
I'm sure you're a little frustrated. I had that happen, and it turned out there were two adb processes running. A reboot fixed that. I'm sorry I don't have the answer.
It IS frustrating, but I appreciate your suggestions!
try running the emulator and make sure you can connect to it via adb, as a check to make sure adb deamon is starting up correctly.
True. Worked for me.
For whatever reason, it was my system that I do all my adb work on....just refuses to see the TPT.
Used my notebook with nothing installed and it went just fine.
My Win7-64 PC could only see my TPT as a portable device, and was listed between drive letters. I wanted to see it under "Android Phones."
After about 6 hours of searching, having installed the Lenovo-provided drivers probably 40 times, I went out on a limb and opened the Device Mangler, individually uninstalled each of the portable devices, including the TPT. Rebooted my PC. Plugged in the TPT, and finally it appeared under Android Phones, and ADB recognized it (I typed "adb devices" in the command prompt and it was listed).
What it came down to is the driver that wanted to be the default was trumping the one I wanted. Beware the Diva. She's not all that.
I should add that I also unplugged a usb card reader (that was making all the drive letters) because I thought that might be the culprit, but it still showed up in the Device Mangler, so I don't think unplugging it made a difference.
I miss Win2K.
Ok so a little background. After hearing about the Carbon backup app a while ago I decided to install it and followed the instructions to do so. One of these steps is to change the normal USB drivers to the ATB ones from the Android SDK. I did this and it all went well without a hitch. However I came to add some movies on to my nexus 7 today and it would only recognize my device in PTP mode (as per the Carbon app requires). I proceeded as normal but found that I could not create a new folder for my films. When i tried i was faced with this error:
However I found that I could create a new folder in one of the existing sub-directories so I proceeded with that. I started copying the movie files over and got another pop up looking like this:
After clickking yes I was soon faced with another error screen:
This happens for nearly every video file i have tried to transfer. I have tried uninstalling the ADB drivers and letting windows install the default drivers it used the first time, however now it will not find any driver software for my nexus 7 unless I point it to the ADB drivers. Whenever I try to connect my device as an MTP device instead of PTP windows will not recognise it and nothing will show up in my computer. Is there any way that i can defer back to the default drivers and use my device on MTP instead of PTP?
Just for a bit of extra info, the same problem is occurring on my nexus 4.
Thanks
Hmm, i have adb drivhttp://forum.xda-developers.com/showthread.php?t=2214386alongside stock drivers for mtp as im sure many do n do not face this problem.
Have you uninstalled the backup app and cleaned the registry?
Try going in to device manager and enable 'show hidden devices' and search for any leftover usb drivers or interface that might interfere with the stock drivers. As a last resort you can download your usb chipset drivers, then uninstall all chipset drivers and usb devices including those hidden, then reinstall the chipset and other drivers u may need. Eg.printer drivers, then try again.
Previously i had a sony erricson phone and it's SE's software screwed up the usb interface n i wasnt able to connect anythin thru usb mtp. That helped me. Alternatively, if u have system restore on you can try restoring to a date before this all happened.
Also, check your device for any apps or settings that might interfere usb functions like usb debugging altho it's rare. Not sure what you did but you might have semi/permanently broken some settings in the device...if you had an earlier backup which was flawless, try restoring to that first. Remember to play safe when doing all troubleshooting, windows isnt exactly smart with device drivers =< worse case you have to reset both the usb drivers and device if nothing works...
Unrelated but might help http://forum.xda-developers.com/showthread.php?t=2214386
Or
http://forum.xda-developers.com/showpost.php?p=39752670&postcount=5
i faced the same problem last week. what i do is go through step by step like what nexus root toolkit suggest. start from scratch. remove all previous drivers and reinstall. Follow to the letter what it says. So the problem is just probably of a bad driver stuff. Remember to restart too.
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