I have the SDK for windows installed and have the drivers downloaded but they can not install. Even with my phone plugged in, i have tried all 3 different usb settings and currently have debugging turned on.
NOTE: The driver im trying to install is the adb driver.
Also this may be my first android phone but i do know my way inside and out on a computer
farquep,
I'm an Android newbie myself, but I don't think you need those SDK drivers. I tried installing them, and they weren't working for me, either.
I'm not sure if you're trying to root/enable sideloading on your phone, but I found that the drivers included with HTC Sync seemed to get me where I needed to be as far as THAT effort goes.
If you're just trying to hook up your phone to your PC, and expecting to be able to access it like a removable drive, I'm pretty sure you'll be unable to do that until you go through the rooting/sideload enabling process. I never had any luck with it UNTIL I rooted my phone, and I'm pretty sure that's by AT&T's design.
Regards,
Corporate Dog
You need to modify the .inf file for the driver to include your device/vendor code manually or just do what I did which is easier and install HTC sync won't hurt anything you don't have to use it. It will modify the file for you. Or you could have someone upload there modified file. At any rate the problem is the USB plug and play system that does not recognize your device. It only recognizes a handful of devices and the ARIA is not one of them. Good Luck.
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.
I finally decided I'm going to root my nexus. Everything seems very simple, except one small problem. I don't have the USB drivers installed. No biggie, I downloaded the 2.1 SDK that supposedly had the USB drivers in it. But for the life of me I can't freaking find them.
As I understand it they should be located at :
C:\AndroidSDK\USB driver\
Unfortunately, inside AndroidSDK there is no USB Driver folder. In fact, no where in the subfolders is there one either. Now perhaps I'm just a total idiot and am missing something, but I've been trying to figure this out for the last 40 minutes and cannot find the damn drivers.
Can anyone tell me how dumb I am? Please?
The USB drivers are a separate download. It's way down the list of things you tick when choosing what to install.
Heh... as above, run the SDK setup and tick the USB drivers.
Then they'll be in \SDK\USB driver\
worth noting if you're on windows 7 x64 you'll need to dl both 32 and 64 bit versions of java jdk to get the actual sdk to run to download the drivers.
then make sure usb debugging is on, and you're away from there
Best way to get the ADB drivers installed correctly is to just install the PDAnet client for your computer. It'll install the correct drivers per your OS.
http://www.junefabrics.com/android/index.php
Thanks guys, you're awesome!
I just downloaded DroidExplorer, and it installed everything I needed for the SDK/ADB. Saved me alot of precious time..
I'm trying to use my new Epic to test an application I made a while ago but I can't seem to get Eclipse or the Android Eclipse plugin to recognize my phone.
The android documentation says that I need to install the USB driver package from the list of available packages in the SDK and AVD manager, but there is no USB driver package. In addition, I am unable to even mount my EPic to my computer to do simple file transfers, regardless of whether I use the drivers that Windows downloads from Windows Update or if I use the official driver package from Samsung.com. Although I will get a drive to show up when I plug my phone in, it will be a light grey and attempting to access it leads to it timing out after a few minutes.
I've attempted this on 32-bit and 64-bit editions of Windows 7, and I do have USB debugging enabled. I'm probably missing something since this is my first Android phone, but I sure can't figure it out and I consider myself pretty proficient with this type of stuff
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Aridon said:
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Click to expand...
Click to collapse
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Roisen said:
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Click to expand...
Click to collapse
I downloaded the drivers from Samsung website but am still unsuccessful in mounting my sd card to my Windows 7 64bit pc. Anybody has found a solution??
i had to edit 70-android.rules to include the samsung drivers code 04e8
I fiddled for a couple of hours and it just started working. No idea what I did, so sorry I can't be of more help to other people with this problem.
i'm not sure what this eclipse thing is, but i was having problems connecting my phone to my computer.
but after doing a battery pull, it all started working again. sounds noobish, but hey, it worked!
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.
so I got the latest Universal Naked Drivers 0.73 zip file, extraced it to its own folder on my desktop, and then I opened device manager, went to Other Devices>Nexus 4, right clicked, uninstalled, restarted my laptop and nexus 4, and then opened device manager again, and this time clicked on Update Drivers for nexus 4, and when I select browse files on my computer, then I click that folder, which has two sub folders in it, one for AMD64 and then i386, and there is also some other files in the main folder, outside the subfolders, called androidwinusba64 and androidwinusb86, as well as two more called android_apxusb and android_winusb.
But When i click on the main folder so it searched through that and the two subfolders, it keeps saying it's not finding any drivers for my device, and i've tried clicking on each of the sub folders, and neither of those make it work either. I've done what every guide has shown me, which I've installed drives hundreds of times in my 27years of life, and I have never had a problem before. Especially not with Android devices. I can't get my brand new 16gb nexus 4 that i just got yesterday (got it while I wait for Tmobile to get the Nex5 in stock, and then I am switching them out) to show up under my computer as a media device so I can actually drop files onto it. I dont get what the issue is here. I know that the 4.3 update (which I updated to last night when i first powered on my phone and activated it) cause some driver issues from what i've read, but supposedly they have been fixed or whatever, and this Naked Driver is supposed to help as well. But getting them installed first would work better lol. everytime I plug the phone in, it tries to install the drivers itself, but it keeps failing for some reason. Any thoughts on how to proceed ?
It's ADB driver, you need to enable USB Debugging. If you are using Windows 8, reboot it into advance mode and disable driver signature checking.
eksasol said:
It's ADB driver, you need to enable USB Debugging. If you are using Windows 8, reboot it into advance mode and disable driver signature checking.
Click to expand...
Click to collapse
i already know all that lol I've been modding for quite a few years, so I know all about USB debugging, thanks tho. That's definitely not the problem. I can get the phone to work with ADB no problem, but I can't get it to show up as a media device like its supposed to when i have that selected in the USB mode options.
Oh, and I am sorry, I shoulda clarified, I am on Win 7. I already read about the Windows 8 thing tho. Which I got a copy of Win8, so I do plan on upgrading soon, check it out see what its like. But I just gto a new copy of Ubuntu, so I've been playing around with that a lot lately.
Anyone ? I have tried so many different things and Just can't get it to work, bout to chuck my laptop out the window lol
I can't speak for the naked drivers as I have never used them, but the ones that come with the SDK work fine with Win 7 on Android 4.3 (Copy and pasting files with Windows Explorer, adb, fastboot, etc.).
Did you resolve your issue? If not you should try to run "Usb Tree View" and make sure your phone internal USB switch is set to PDA and not MODEM or BOTH etc. I don't know how that works for the Nex4 but its a thing to look at.