5,596,700 Members 46,183 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Setting Up ADB/USB Drivers for Android Devices in Ubuntu maverick 10.10?

Tip us?
 
thisisspeedy
Old
(Last edited by thisisspeedy; 3rd December 2010 at 10:36 PM.)
#1  
thisisspeedy's Avatar
Senior Member - OP
Thanks Meter 2
Posts: 130
Join Date: Oct 2010
Talking [Q] Setting Up ADB/USB Drivers for Android Devices in Ubuntu maverick 10.10?

OK so I tried these instruciton for Lucid on Maverick. I would post the link but I can't cuz I'm a newbie.

Quote:
Download the latest Android SDK from Google: Android SDK
Extract the TGZ file to your home/user directory
NOTE: User would be your username
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Login as root and create this file: /etc/udev/rules.d/##-android.rules
NOTE: In the above file replace ## with the number 50 if you are running Gusty/Hardy/Dapper (50-android.rules) or with the number 70 if you are running Karmic Koala/Lucid Lynx(70-android.rules)
Or simply type in terminal sudo gedit /etc/udev/rules.d/##-android.rules then enter your password
The file should read:
For Gusty/Hardy: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Dapper: SUBSYSTEM==”usb_device”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Karmic Koala: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Lucid: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
NOTE: In the above lines the code ”0bb4″ refers to a HTC device. If your phone is from a different manufacturer, replace the code with the appropriate from the table below.

Execute: sudo chmod a+rx /etc/udev/rules.d/70-android.rules
Reboot
To run ADB you need to add an environment variable to your bashrc file:
Open a terminal window and type: sudo gedit .bashrc
Add the following line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
Save and close
You should be ready to go, type adb devices in a terminal window with your phone plugged in.
If you see a serial number pop up that means you are done. Should look something like this:
List of devices attached
HT99PHF02521 device
If for some reasons when running adb devices gives you a “no permissions” error, try typing the following in terminal
adb kill-server
adb start-server
USB Vendor IDs

MANUFACTURER USB VENDOR ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
Common ADB Commands

- Lists which devices are currently attached to your computer

adb devices
- Drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly

adb shell
- Lets you install an Android application on your phone

adb install
- Remounts your system in write mode – this lets you alter system files on your phone using ADB

adb remount
- Rets you upload files to your phones filesystem

adb push
- Lets you download files off your phones filesystem

adb pull
- Starts dumping debugging information from your handset to the console – useful for debugging your apps

adb logcat
Now, as for the credits, I took TheUnlockr “How To” for Windows as a base for this guide.
But it doesn't work in maverick. Please help. Because I really want to overlock my phone.

Also keep in mind I'm fairly new to Linux so be easy on the newbie.

Thanks guys.
 
thisisspeedy
Old
#2  
thisisspeedy's Avatar
Senior Member - OP
Thanks Meter 2
Posts: 130
Join Date: Oct 2010
49 views and no responds? Please help I'm desperate here.
 
thisisspeedy
Old
#3  
thisisspeedy's Avatar
Senior Member - OP
Thanks Meter 2
Posts: 130
Join Date: Oct 2010
So did post this in the wrong section? This silent treatment is killing me. lol
 
benholiio
Old
#4  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Feb 2008
in terminal type:

$ sudo -i

$ gedit .bashrc

insert the same line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools

$ exit

$ sudo -i

$ adb kill-server
$ adb start-server
$ adb devices
 
hungrysquid
Old
#5  
hungrysquid's Avatar
Junior Member
Thanks Meter 0
Posts: 21
Join Date: Jul 2010
Quote:
Originally Posted by benholiio View Post
in terminal type:

$ sudo -i

$ gedit .bashrc

insert the same line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools

$ exit

$ sudo -i

$ adb kill-server
$ adb start-server
$ adb devices

Dude this is for adb, not for recognizing the USB...

My phone is HTC Desire and I am still figuring out why it doesnt work on 10.10 with all the rules...
 
benholiio
Old
#6  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Feb 2008
Quote:
Originally Posted by hungrysquid View Post
Dude this is for adb, not for recognizing the USB...

My phone is HTC Desire and I am still figuring out why it doesnt work on 10.10 with all the rules...
I'm assuming thisisspeedy got to the same stage i did: USB connects, i can access files through maverick, however adb won't detect the device to allow push/pull/shell.

simply elevating to root & editing the bash script on maverick solves the problem.

I have my Galaxy S connected to Maverick via USB, and i can run all ADB functions.

It should work for HTC using the correct code. If you have a problem with Ubuntu detecting your device on USB when you've set USB to mount on Android, PM me and I'll see if i can help.
 
Daughain
Old
#7  
Senior Member
Thanks Meter 6
Posts: 148
Join Date: Nov 2010
Location: DFW, Tx
Could someone post a link for the Lucid dirs? Thanks.

Sent from my T-Mobile G2 using XDA App
 
thisisspeedy
Old
#8  
thisisspeedy's Avatar
Senior Member - OP
Thanks Meter 2
Posts: 130
Join Date: Oct 2010
Default Thanks for everyone responses.

I figured it out thanks to this.
[QUOTEThe Android Debug Bridge (adb) is a tool lets you manage the state of an emulator instance or Android-powered device.

I was trying to run it for the first time on my ubuntu 9.10 box and I kept getting this error:


desktop:~/dev/Android/android-sdk-linux/tools$ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'arb' from package 'arb' (multiverse)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'sun-java6-jdk' (multiverse)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found


What was I doing wrong?

A quick google search shows me the error of my ways.. I haven't added my Android SDK tools directory to my system path!


It should go something like this...

open a terminal window and type:

$ echo $PATH
---(should return the directories associated with $PATH)

$ export PATH=$PATH:/home/YOUR-USERNAME/sdk/tools
---(replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)

$ echo $PATH
---(you should now see your tools directory added to the end of the $PATH variable)

$ adb devices
---(now adb should do something, if nothing else at least error, no devices)


And now I get:

List of devices attached
emulator-5554 device


Sweet Success!

p.s. Adding to the system path in Windows is along the lines of :
right-click '(My) Computer'
Select 'Properties'
Go to 'Advanced' or whatever tab you find 'Environment Variables'
Select 'Path' then 'Edit' and add your new path in.][/QUOTE]
The Following User Says Thank You to thisisspeedy For This Useful Post: [ Click to Expand ]
 
Hic007
Old
#9  
Junior Member
Thanks Meter 0
Posts: 3
Join Date: Feb 2011
Default adb trouble

Hi i am runing on Ubuntu Maverick with device Huawei U8110 on Celestial Teapot 4 ROM
java jdk ver6
installed Android SDK and tools in the home folder

i edit the rules file 99-android.rules to SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"

saved and added the file permisions

restart the udev
Connected the Phone put the debug mode on
kill the adb then started

And Then Run The comand
root@hal:/home/android-sdk-linux_x86/platform-tools# ./adb devices
List of devices attached

There is nothing in the list....?
HELP!? Please......
 
tknv
Old
#10  
Junior Member
Thanks Meter 1
Posts: 27
Join Date: Aug 2010
Location: Tokyo

 
DONATE TO ME
Wink I use it for Marveric.

vim /etc/udev/rules.d/70-android.rules

# IS01
SUBSYSTEM=="usb",ATTRS{idVendor}=="04dd",ATTRS{idP roduct}=="04dd",MODE="0666",OWNER="root"
# GalaxyS
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idP roduct}=="681c",MODE="0666",OWNER="root"
# bravo
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"

add like a above. then
/etc/init.d/udev restart

Good luck!

Tags
abd, drivers, maverick
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Sony Xperia Z, ZL, ZR, and Tablet Z to Receive Official KitKat Update in May

It’s no secret that although Sony is one of the most … more

Force Translucent Status Bar in KitKat ROMs with Xposed

It’s been a while since Android 4.4KitKat wasreleased, and we’re slowly … more

Fix the Ambient Light Issues on Your Google Nexus 5 using Xposed

The Google Nexus 5 is a great and rather popular device. This LG-produced … more