I've been looking everywhere and I can't seem to find the drivers for Linux anywhere. Does anyone have them or know where to get them? I've checked Motorola's website, Verizon's website, and Google but I can't seem to find them. I need these for my computer running Ubuntu 10.10. Any help would be greatly appreciated
Where you are going, you don't need drivers
I'm running Ubuntu 10.10. If you are just trying to connect via Mass Storage (ie, access the sdcard), then it should just work. Depending on how your system is set up, you may have to manually mount the device.
If you want to use the development tools, like adb or something, then all you need to do is to (as root) create a file called:
/etc/udev/rules.d/51-android.rules
And put in it:
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
(Note: that is the Motorola vendor ID, so if you have also want a phone to work that isn't made by motorola, you will have to find their vendor ID. You can find those here:
http://developer.android.com/guide/developing/device.html#VendorIds
HTH
Related
Hi all,
I've searched the forums (honestly), but I can't find an answer to my problem.
I have a Vodafone branded 32B phone.
I installed the AndroidSDK as supposed to, added the path, made the phone root, booted into the recovery console using fastboot and flashed my phone with different operating systems... but during all this time I hever got ADB to work.
Whatever I do, adb never finds the phone. Fastboot works and finds it, when it's in fastboot mode, but ADB never. So, I can't permanently install the recovery console nor do any of the other funky stuff.
ADB doesn't work when the phone is in fastboot mode nor normally operating. I have USB Debugging turned on. The phone works normally and I can access the SDCard just fine.
Any help?
Suggestion.
Look into purchasing a G1 to be kept as a spare and used for development. That's what I've done with my G1. GParted is within most recovery images nowadays, therefore you can do most anything there, well...important functions that is. Keep that in mind.
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Reignzone said:
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Click to expand...
Click to collapse
that's what i had to do to get it to recognise my phone.
i'm pretty sure the driver came with SDK. either way i've attached the one i used.
go into device manager and update the driver it's currently using with the attached one.
Incorrect driver.
It should be the 1st driver listed in the Android SDK file.
As far as I know, you could also choose to push ADB to your system32 file folder under the C: drive in your computer. That is if you're using a Windows machine.
just a thought
Are you on windows or linux? If you're in ubuntu try sudo adb ... the default unprivilaged user doesnt automatically have access to the device.
If you're in Windows I would uninstall the Android Phone device in device manager and reboot with the phone disconnected. Then connect it and install the usb driver from the sdk when prompted. Might also pay to download the sdk again.
Install HTC Sync
Another known way to fix the issue is to download and install HTC Sync http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
This seems to install the correct drivers
For more info check the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02
Hey Guys,
Forgot to mention I'm on Windows Vista 64 bits.
That last suggestion did the trick. I went to the site and downloaded the HTCDriverUpdate_Vista_64bits.exe, and within seconds I had an ADB connection.
Thanks for your help!
I develop Android apps, and I recently rooted, Rom'd, and kernel'd my Incredible. (I installed a custom kernel and rom). Now, when it tells me to debug on a running device and to select a running device, my Incredible doesn't appear in the list.
Can somebody solve how to make it appear? Thanks!
does adb find it? if not usb debugging might be turned off check settings->applications
adb doesn't find it. USB debugging is also on.
if you are running eclipse on linux you will have to add your cellphone´s vendor to /etc/udev/rules.d/51-android.rules for eclipse to recognize it
just google: 51-android.rules eclipse vendor device and you will get the whole list of vendors and how to set up the rules according to your distro
if you are on mac or windows im clueless cause i´ve never try it there...
on windows i´m guessing you have to have the drivers installed, on mac probably is something like on linux
I'm on a mac, and how exactly would I change the cellphone vendor? (assuming it works for mac)
Hello everyone,
So I've installed ACER's adb drivers, but when I connect the tablet to my computer it shows up as an MTP device. I've tried updating the driver and manually browsing to the driver's location, but windows says that driver is not compatible with my device? BTW: I am running a fresh install of Windows 7 64-bit.
Any tips would be appreciated.
Thanks!
I'm having the same issue. It seems like everyone else's Iconia "just worked" with adb.
I've tried installing the acer drivers. It puts a folder in my Program Files directory...but I don't see what I'm supposed to do there. There's "EUUDriverInstaller" but when I click on it nothing (seems to) happens.
When I plug the device in it uses some generic Microsoft driver to show the device contents but composite adb doesn't show up at all like it does for my Droid.
I've reboot several times on both device and laptop. I've uninstalled / reinstalled the application that made that driver directory.
I opened an application in the driver directory under the x64 folder and it opened up the windows driver installer and installed some drivers...but still no composite adb when I plug it in.
It was called "dpinst" and installed:
Linux Developer Community Net
Acer, Inc (androidusb) USB
Google, Inc (WindUSB) USB
then a couple others about a modem and ports
It is on usb debugging and I've toggled it on and off.
It's running 3.1 stock and I'm on x64 Windows 7
Both command prompt adb devices is empty under "List of devices attached" and Eclipse devices is empty.
My sdk is fully updated.
Curiously it appears Acer hides the driver if you specify Honeycomb 3.1
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
apapousek said:
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
Click to expand...
Click to collapse
I appreciate the suggestion, but I'd rather not install another partition just to adb connect this tablet.
Some additional differences I've noticed.
It seems like the tablet is going straight to mounting if that means anything. Connecting my Droid doesn't bring up the Autoplay menu while connecting the tablet automatically asks me how I want to access the data in the autoplay menu. It does *say* usb debugging is on, but no "ACER composite ADB interface" appears in my device manager.
Edit:
It seems like my situation is comparable to this guy in regards to the device just being treated like a flash drive. forum.xda-developers.com/showthread.php?t=734139 He says the rom was the problem...but I can't see why this stock rom should have an issue.
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
I'm too on Windows 7 64bits and for the drivers I go to http://support.acer.com/us/en/product/default.aspx
If you want I have re-upload the drivers on my 4shared
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
bpivk said:
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
Click to expand...
Click to collapse
I don't seem to have another icon. I have this one referring to the Iconia Tab, but when I right click on it it just treats it like a flash drive.
I can't link the picture yet (need to have 8 posts), but there is on "Acer Iconia Tab" in Devices and Printers, but there's no yellow exclaimation mark and when I right click it it just has the option to browse files, it treats it like a flash drive.
It's under "Unspecified"
EVEALEX62 said:
I'm too on Windows 7 64bits and for the drivers I go to
EDIT : [Had to remove URLS to quote]
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
Click to expand...
Click to collapse
I've downloaded those drivers, unzipping them, and ran the setup several times =/.
EDIT:
I feel like a tool, someone at stack overflow suggested I switch to a different port (not just unplugging / re-plugging it into the same one), I guess that finally told windows to reanalyze it. Should have figured it would have been something silly for such a basic problem, shame on me for keeping all my other ports full.
Thanks for the help everyone!
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
EVEALEX62 said:
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
Click to expand...
Click to collapse
That worked! Thanks.
Figured it out
Hey guys,
Thanks for all of your suggestions, but none of them worked. I ended up having to disable automatic driver installation, then went into Windows\System32\DriverStore\FileRepository and deleted the folders corresponding to the drivers that windows kept on insisting I wanted. After that everything worked great!
I've just updated the Dell Streak 5 wiki with a guide to setup fastboot for linux in the Flashing guide section.
Oh, the sdk finally readded the fastboot binaries for *nix and osx are finally readded.
Main reason the nix and osx guides were stubs were that previously the fastboot binaries for all 3 os groups were missing from like platform-tool r6-r9 and they're included again in r10
I'm gonna update fastboot+adb.zip to include these files and take a look at the win drivers and do a big update.
I'm also going to rewrite your portion once I get fastboot+adb.zip reorganized and bring it to parity with the win version. Thanks!
Finally, the *nix portion will be added to the s7 and venue guides too to maintain parity and the s10 one when I get around to making the rest of it
Yeah, i saw your edit, i've since shortened the guide, because the relevant additional info is available on the android website and i've linked it, however, having only adb and fastboot in a zip is even better.
I'll see if the Mac version works on PC-BSD 9, and if it does, i'll add that as well (you never know)
No command udev in my fedora. At least in the my user PATH! In my root's PATH, I have only udevd and udevadm! I use Fedora, are these instruction Ubuntu specific?
Ultimately only the basics will be covered, I'm not willing to add (or even let others add) a dozen different branches to support every different flavor of linux.
When I'm ready to release a new Fastboot+ADB I will trim it down more if needed and leave it at that, currently it's pretty much about what I'd like it to be, it's mostly just a little formatting to make it match the rest of the guide.
The guide techincally also skirts the issue of different windows versions, there might be some minor things depending on which ver of windows and if it's x64/x86 but those details are left to the user to fill in on their own.
Users should be able to fill in some stuff like this on their own, just like the implied availablity of a unzipper.
If it's something that's specific to fastboot or adb and it's missing, we'll add it of course.
bazzoon said:
No command udev in my fedora. At least in the my user PATH! In my root's PATH, I have only udevd and udevadm! I use Fedora, are these instruction Ubuntu specific?
Click to expand...
Click to collapse
Udev is the udev daemon. I'm not familiar enough with Fedora to know what's the command to restart it, but you could reboot the computer and the new rules should take effect.
Yes, it is Ubuntu specific, since i use it, and the intructions on the official android site are for Ubuntu.
Actually the only thing that isn't mentioned anywhere, except in the Streakdroid install guide, was adding the -i 0x413c option after fastboot (or the respective USB VendorID), an omission that took me along time to find and kept me really frustrated by being unable to change ROMs.
Edit The Manii
I've linked to the SDK-Platform tools zip on the official android site, to save a few steps of installing the full SDK, so for now, you don't need to host a separate zip of adb and fastboot, until Google updates the SDK.
-i 0x413c is optional depending on how your env is set up.
I believe that optional step you made to register that ID makes it optional on *nix too, but as I dont use fastboot under linux I cannot verify.
It is optional under windows though.
I merely havnt finished testing the s7 drivers, the zip was missing the *nix/osx fastboot binary, it always had the adbd binary
For me fastboot didn't work without that option, just stayed on 'waiting for device' despite having read pretty much every guide that's out there for setting up fastboot and adb on linux (and ubuntu specifically), even though adb worked perfectly fine.
As far as not adding a custom rule in udev, I'm pretty sure it's needed since it's posted on the official android site and it's stated that it's required in order for the OS to recognize your phone.
As for the Mac OSX version, just downloading and extracting the SDK Platform-tools package and running fastboot from there should just work, but i don't have a Mac to test it on.
Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!
Is adb enabled on your phone ?
Did you restart udev or rebooted ?
btw, saw this and work allot better than standard 12.10 mtp
http://www.webupd8.org/2013/01/upgrade-to-gvfs-with-mtp-support-in.html
lvandam said:
Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!
Click to expand...
Click to collapse
nardusg said:
Did you restart udev or rebooted ?
Click to expand...
Click to collapse
Yes, every time after I changed something in the rules list I restarted udev and rebooted as well.
Do you have java installed properly? Here is the post I used to get adb working on Ubuntu 12.10 (its post #62 the OP was for Ubuntu11). It didn't work till I set the proper permissions as stated in the post under editing the udev rules (line in post where it shows sudo gedit /etc/udev/rules.d/99-android.rules). I did a 64-bit install and it worked perfectly. Basically what you are doing is manually entering the Nexus 4 into the list of devices as its not there by default.
http://forum.xda-developers.com/showthread.php?p=19446284
That solution worked for me! Many thanks.