[Q] ADB Devices: Empty on Ubuntu (Chinese Phone) - Android Q&A, Help & Troubleshooting

Hello Everyone, my firts post asking for help, Installed ADB on Ubuntu 12.04 and succesfully rooted 1 Huawei and two Lgs but now im stucked woth MY own phone
Got a Chinese Double Sim Phone, actually not bad but after almost one week of trying and looking everywhere i cant get ADB to recognize my phone, When i Type lsusb on terminal, it appears:
Bus 001 Device 003: ID 1782:5d04 Spreadtrum Communications Inc.
my /etc/udev/rules.d/99-android.rules :
SUBSYSTEM=="usb", ATTR{idVendor}=="1782",ATTRS{idProduct}=="5d04" MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1782", ATTRS{idProduct}=="5d04"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{ACTION} --device=$env{DEVNAME}"
But when i put adb devices:
List of devices attached
(Empty)
Anyone, can please give me a hand here please? Thank You

Related

vibrant wont show up in ddms ubuntu

I have SDK and Eclipse installed on my ubuntu box but when I connect my phone and open ddms its just shows bunch of question marks and it says uknown.
any idea how can I get ddms to recognize my phone?
A few devices have this problem. This fix is setup for the nexus one:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="4e12", MODE="0666"
I put the code above in
Code:
/etc/udev/rules.d/51-android.rules
and restart udev
Code:
reload udev
Vendor id and product ids can be found from here " http : // www . linux-usb . org / usb . ids "
sorry for the weird url, i am not able to post them yet, but it is needed for this fix.

EVO3d ubuntu 11.04 setup

If you are having troubles getting your ubuntu 11.04 to recognize your Evo3d here is what I did to get ADB working on mine:
I am assuming you have adb setup.
1. Plug your EVO3d into your pc as charge only
2. in terminal type
lsusb
3. You should see something like this:
Bus 001 Device 007: ID 0bb4:0cba High Tech Computer Corp
that is your evo3D(verify the eight digit id is the same before doing step 6 if it is not change to match your evo3d vendor id)
sudo gedit /etc/udev/rules.d/99-android.rules
4. Enter your ubuntu password if prompted
5. This should have brought up a new gedit file with 99-android.rules as
the title
6. copy and paste this into that gedit document:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
and save the new document.
7. make the new document executable:
sudo chmod a+rx /etc/udev/rules.d/99-android.rules
8. then restart dev environment:
sudo restart udev
9. open terminal and enter
adb devices
10. your evo 3d should be setup
Hopefully this helps anyone having the same issues I was having.
If someone tries this please let me know if i need to change anything.
Sent from my PG86100 using XDA Premium App
I am currently running the same setup. I will try soon and report back. Thank you!
Sent from my PG86100 using XDA Premium App
MiSfit211 said:
If someone tries this please let me know if i need to change anything.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
That will work. It's exactly what I had to do about 5 days ago to get ADB to work with my 3D. Prior to doing that, i would just get "List of Devices attatched : ??????????? NO permissions". I did a bit of googling and found the steps you just posted. Definitely would've saved me some searching if this was up last week This should help out anyone with the same problem, because it definitely works. Nice write up.
working perfect, thank you very much for the guide.
The only thing I had to do in addition was restart the adb server (since it was already running)
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT16MHX28070 device
(Also, the chmod to executable won't hurt anything but isn't necessary)
Thanks for the post!
thanks buddy. this couldnt have been any more helpful. it worked like a charm. this was very easy to follow. I am new to linux and appreciate the effort that you put in to explain getting this to work.
I used this thread and it works perfectly.
XDA/showthread.php?p=11823740#post11823740
MiSfit211 said:
If you are having troubles getting your ubuntu 11.04 to recognize your Evo3d here is what I did to get ADB working on mine:
I am assuming you have adb setup.
1. Plug your EVO3d into your pc as charge only
2. in terminal type
lsusb
3. You should see something like this:
Bus 001 Device 007: ID 0bb4:0cba High Tech Computer Corp
that is your evo3D(verify the eight digit id is the same before doing step 6 if it is not change to match your evo3d vendor id)
sudo gedit /etc/udev/rules.d/99-android.rules
4. Enter your ubuntu password if prompted
5. This should have brought up a new gedit file with 99-android.rules as
the title
6. copy and paste this into that gedit document:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
and save the new document.
7. make the new document executable:
sudo chmod a+rx /etc/udev/rules.d/99-android.rules
8. then restart dev environment:
sudo restart udev
9. open terminal and enter
adb devices
10. your evo 3d should be setup
Hopefully this helps anyone having the same issues I was having.
Click to expand...
Click to collapse
great post.just a heads up, you shouldn't have to do this on 11.10 though. after a fresh install of 11.10 and android-sdk all seems to be working without doing this.

HOWTO: Linux and MTP

This is a quick how to get MTP working on Linux, the guide is for distro's based on Debian (mint\debian\ubuntu) OpenSuse, Fedora AND Gentoo. If there's any missing for major distro's let me know, or add them to a separate post and i'll put them up here
***Debian based distros**
Code:
sudo apt-get install mtpfs
sudo mkdir /media/onex
sudo chmod 775 /media/onex
sudo mtpfs -o allow_other /media/onex
gedit /etc/udev/rules.d/51-android.rules
and add the following line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and then:
sudo service udev restart
***Arch Linux***
Code:
pacman -S libmtp
After installation, you have several mtp tools available. Upon connecting your MTP device, you use:
mtp-detect
and add the following line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and then reload udev rules:
udevadm control --reload
Arch Linux guide is from the ArchLinux wiki
**Redhat\Fedora16**
First of all, I using my computer with other people, who can come over the network, so the 0666 mode bits not a right choice for me. I make it all on a fedora 16, but the distro is really not important.
So the steps:
- add a user to the "disk" group (or whatever You want)
- make a mount point (the media doesn't work for me, across the init removes the content)
- add this mount point to the fstab, with some parameter
- create udevd rules
- restart udevd
- install fuse-mtpfs
- (re)login user
- try it
My common experience is that, the mtpfs is very very very very slow. Really slow, so I can use it only with CLI, any GUI has been coming back with time out
And the "code":
Code:
usermod -a -G disk $LOGINUSER
Code:
sudo mkdir /mnt/sgs2 ; sudo chgrp disk /mnt/sgs2; sudo chmod 0770 /mnt/sgs2
Code:
sudo echo "mtpfs /mnt/sgs2 fuse users,noauto 0 0" >> /etc/fstab
Code:
cat > /etc/udev/rules.d/51-android.rules <<EOF
SUBSYSTEM!="usb_device", GOTO="label_end"
ACTION!="add", GOTO="label_end"
# ATRRS{idVendor}== ertekei:
#Acer 0502
SUBSYSTEM=="usb",ATTRS{idVendor}=="0502",MODE="0660",GROUP="disk"
#ASUS 0b05
SUBSYSTEM=="usb",ATTRS{idVendor}=="0b05",MODE="0660",GROUP="disk"
#Dell 413c
SUBSYSTEM=="usb",ATTRS{idVendor}=="413c",MODE="0660",GROUP="disk"
#Foxconn 0489
SUBSYSTEM=="usb",ATTRS{idVendor}=="0489",MODE="0660",GROUP="disk"
#Fujitsu 04c5
SUBSYSTEM=="usb",ATTRS{idVendor}=="04c5",MODE="0660",GROUP="disk"
#Fujitsu Toshiba 04c5
SUBSYSTEM=="usb",ATTRS{idVendor}=="04c5",MODE="0660",GROUP="disk"
#Garmin-Asus 091e
SUBSYSTEM=="usb",ATTRS{idVendor}=="091e",MODE="0660",GROUP="disk"
#Google 18d1
SUBSYSTEM=="usb",ATTRS{idVendor}=="18d1",ATTRS{idProduct}=="4ee1",MODE="0660",GROUP="disk"
#Hisense 109b
SUBSYSTEM=="usb",ATTRS{idVendor}=="109b",MODE="0660",GROUP="disk"
#HTC 0bb4
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",MODE="0660",GROUP="disk"
#Huawei 12d1
SUBSYSTEM=="usb",ATTRS{idVendor}=="12d1",MODE="0660",GROUP="disk"
#K-Touch 24e3
SUBSYSTEM=="usb",ATTRS{idVendor}=="24e3",MODE="0660",GROUP="disk"
#KT Tech 2116
SUBSYSTEM=="usb",ATTRS{idVendor}=="2116",MODE="0660",GROUP="disk"
#Kyocera 0482
SUBSYSTEM=="usb",ATTRS{idVendor}=="0482",MODE="0660",GROUP="disk"
#Lenovo 17ef
SUBSYSTEM=="usb",ATTRS{idVendor}=="17ef",MODE="0660",GROUP="disk"
#LG 1004
SUBSYSTEM=="usb",ATTRS{idVendor}=="1004",MODE="0660",GROUP="disk"
#Motorola 22b8
SUBSYSTEM=="usb",ATTRS{idVendor}=="22b8",MODE="0660",GROUP="disk"
#NEC 0409
SUBSYSTEM=="usb",ATTRS{idVendor}=="0409",MODE="0660",GROUP="disk"
#Nook 2080
SUBSYSTEM=="usb",ATTRS{idVendor}=="2080",MODE="0660",GROUP="disk"
#Nvidia 0955
SUBSYSTEM=="usb",ATTRS{idVendor}=="0955",MODE="0660",GROUP="disk"
#OTGV 2257
SUBSYSTEM=="usb",ATTRS{idVendor}=="2257",MODE="0660",GROUP="disk"
#Pantech 10a9
SUBSYSTEM=="usb",ATTRS{idVendor}=="10a9",MODE="0660",GROUP="disk"
#Pegatron 1d4d
SUBSYSTEM=="usb",ATTRS{idVendor}=="1d4d",MODE="0660",GROUP="disk"
#Philips 0471
SUBSYSTEM=="usb",ATTRS{idVendor}=="0471",MODE="0660",GROUP="disk"
#PMC-Sierra 04da
SUBSYSTEM=="usb",ATTRS{idVendor}=="04da",MODE="0660",GROUP="disk"
#Qualcomm 05c6
SUBSYSTEM=="usb",ATTRS{idVendor}=="05c6",MODE="0660",GROUP="disk"
#SK Telesys 1f53
SUBSYSTEM=="usb",ATTRS{idVendor}=="1f53",MODE="0660",GROUP="disk"
#Samsung 04e8
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="6860",MODE="0660",GROUP="disk"
#Sharp 04dd
SUBSYSTEM=="usb",ATTRS{idVendor}=="04dd",MODE="0660",GROUP="disk"
#Sony 054c
SUBSYSTEM=="usb",ATTRS{idVendor}=="054c",MODE="0660",GROUP="disk"
#Sony Ericsson 0fce
SUBSYSTEM=="usb",ATTRS{idVendor}=="0fce",MODE="0660",GROUP="disk"
#Teleepoch 2340
SUBSYSTEM=="usb",ATTRS{idVendor}=="2340",MODE="0660",GROUP="disk"
#Toshiba 0930
SUBSYSTEM=="usb",ATTRS{idVendor}=="0930",MODE="0660",GROUP="disk"
#ZTE 19d2
SUBSYSTEM=="usb",ATTRS{idVendor}=="19d2",MODE="0660",GROUP="disk"
LABEL="label_end"
Code:
udevadm control --reload-rules
Code:
yum/apt-get/pacman/etc install mtpfs
Logout-login, for get in to the disk group, connect the device via usb, and try
Code:
mptfs
without any parameter, and it must write out some information:
Code:
[email protected]:~$ mtpfs
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 2, dev 4
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: (NULL)
fuse: missing mountpoint parameter
And finally mount /it must be working now with user account/:
[CODE]mount /mnt/sgs2
or dismount:
Code:
umount /mnt/sgs2
**OpenSuse 12.2**
this method will work for music and photos access only,
Code:
sudo zypper addrepo -f http://packman.inode.at/suse/12.2/ packman
sudo zypper ref (type a to always accept the packman repo)
sudo zypper in mtpfs
sudo vim /lib/udev/rules.d/69-libmtp.rules and add the following line (replace vim with gedit if you want a gui editor)
# HTC One X+
ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0dfc", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
sudo cp /lib/udev/rules.d/69-libmtp.rules /etc/udev/rules.d/.
reboot
When you plug in the phone you will see android phone icon on the desktop click on it to browse your files.
*note
disable any media players from trying to read the device...
** Gentoo **
Code:
Prerequisites
If your device is not recognized by libmtp, try upgrading to latest (or even git) version.
User needs to be in group plugdev to mount device.
MTPFS
You need to add option: user_allow_other in /etc/fuse.conf
$ mkdir ~/AndroidDevice
$ mtpfs -o allow_other ~/AndroidDevice
NOTE: this can take really long time, up to several minutes. As an indication of successful mount the mtpfs will go to background.
To unmount:
$ /usr/bin/fusermount -u ~/AndroidDevice
If mtpfs doesn't work for you try updating to latest version first.
Go-MTPFS
Seems to be more stable
$ emerge -a go
$ mkdir ~/go
$ export GOPATH=/home/$USER/go
$ go get github.com/hanwen/go-mtpfs
To mount:
$ ~/go/bin/go-mtpfs ~/AndroidDevice
To unmount:
$ /usr/bin/fusermount -u ~/AndroidDevice
Troubleshooting
Sometimes (e.g. on HTC One X) USB debugging automatically turns on when device is connected to PC. You need to turn debugging off, otherwise libmtp can't recognise device.
Make sure your Android device is not going to sleep and the screen is not getting locked. Set screen timeout to very long values, or enable in Development section flag "Do not turn off the screen".
Thanks to ihavoc and Fonya1 for the opensuse and redhat\fedora tutorials
thank you a lot for your help.
when i try to acces to the /media/onex direcory i have this :
ls: cannot access onex: Transport endpoint is not connected
After making changes reboot your session or pc and it will probably mount correctly which you've probably done by now.
Sent from my HTC One X+ using xda premium
somemadcaaant said:
After making changes reboot your session or pc and it will probably mount correctly which you've probably done by now.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
excuse me to ask many question but i am really noob. when all this done what would i see in /media/onex ? actualy after mounting the folder is empty
the only thing i need to do is copy files from/to my HOX+
Can anyone please confirm if this is exclusive to the HTC One X+, or would it work for other similar HTC devices such as One X, One S etc. as well?
It still dont work, i have tryed so many things these days to mount my HTC Ox+ as a USB Mass Storage and everything failed.
I tried tou manualy mount a MTP folder on my Ubuntu like Lloir explained here.
I tried to flash a TeamWorkRecovery and a ClockWorkRecovery to access the "Mount USB" option in the menu
my Device is seen by ubuntu but i am unable to read or write anything, for example if I copy a music album, the copy operation starts, takes a very long time an then end whith an error lik "error unable to copy xxxx.mp3 file does not exist"
actualy i am almost convicted that using an MTP device as an usb mass storage under Ubuntu is purely and simply IMPOSSIBLE !
HQRaja said:
Can anyone please confirm if this is exclusive to the HTC One X+, or would it work for other similar HTC devices such as One X, One S etc. as well?
Click to expand...
Click to collapse
works for ALL MTP devices
Thanks a bunch. This should come pretty handy. =)
Lloir said:
works for ALL MTP devices
Click to expand...
Click to collapse
does it works for you ?
how do you copy your files from/to your phone ?
Waiting for Ubuntu instructions (maybe)?
followed instructions to the letter and still cant mount my htc one xL running jellybean on ubuntu
Just a quick reply since this was linked on the front page. Tried with GNex and Ubuntu 12.10 and no dice.
spdrosin said:
Waiting for Ubuntu instructions (maybe)?
Click to expand...
Click to collapse
The instructions for Ubuntu are the first ones (Debian based distros), Lloir mentioned it at the start of the OP:
Lloir said:
This is a quick how to get MTP working on Linux, the guide is for distro's based on Debian (mint\debian\ubuntu) And Archlinux i will add others soon.
Click to expand...
Click to collapse
Linux really needs to add native support for MTP already. They also should add native support for adb as well while they are at it. Its annoying to have to add entrees to udev to even to be able to access the device.
One suggestion for anyone wanting to do this with a device other than an HTC:
You'll need to change the line you add to /etc/udev/rules.d/51-android.rules based on the vendor of your phone.
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Change the code to one of the following USB vendor ids:
Code:
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Fujitsu 04c5
Fujitsu Toshiba 04c5
Garmin-Asus 091e
Google 18d1
Hisense 109b
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenovo 17ef
LG 1004
Motorola 22b8
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10a9
Pegatron 1d4d
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony 054c
Sony Ericsson 0fce
Teleepoch 2340
Toshiba 0930
ZTE 19d2
Most up-to-date list is here: http://developer.android.com/tools/device.html
You can also have multiple vendor lines in your /etc/udev/rules.d/51-android.rules file, just put one on each line. As someone who's testing on a bunch of different devices, I simply put a line in for all of the above
If your vendor code isn't listed, enter the command "lsusb" in a terminal, and you'll see something like this:
Code:
Bus 001 Device 119: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Bus 001 Device 112: ID 18d1:4e42 Google Inc.
The first four hex values of the id is the vendor ID, e.g., for the Samsung it's 04e8.
cloverz7 said:
Just a quick reply since this was linked on the front page. Tried with GNex and Ubuntu 12.10 and no dice.
Click to expand...
Click to collapse
same here with GNex and ubuntu 12.04
Use Airdroid
Using Airdroid and wifi from Tethering hotspot, you can simply access your Android without USB Cable and you can use anything OS. Search on Google Play with keyword "Airdroid"
Hey I have to say first off thanks for taking the time to figure this out! My problem is I am very new to linux and ubuntu. So when I open the terminal and type all the commands after "sudo mtpfs -o allow_other /media/onex" I get the response: "Listing raw device(s) No raw devices found." So should I have the device attached when I do this? Secondly the following command opens a text window. Is this where i type "SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"? Because now I can't save the text file because I don't have root. Should I be typing literally everything in Terminal? or am I just too new and missing a step. Your help would be greatly appreciated because I would really like to learn a lot more about linux however I'm a bit cautious asking for root for things and ****ing up lol. I'm over windows and will never use a mac so I want to learn! Sorry to be an idiot and a pain just wanna learn.
Nschneider7 said:
Hey I have to say first off thanks for taking the time to figure this out! My problem is I am very new to linux and ubuntu. So when I open the terminal and type all the commands after "sudo mtpfs -o allow_other /media/onex" I get the response: "Listing raw device(s) No raw devices found." So should I have the device attached when I do this? Secondly the following command opens a text window. Is this where i type "SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"? Because now I can't save the text file because I don't have root. Should I be typing literally everything in Terminal? or am I just too new and missing a step. Your help would be greatly appreciated because I would really like to learn a lot more about linux however I'm a bit cautious asking for root for things and ****ing up lol. I'm over windows and will never use a mac so I want to learn! Sorry to be an idiot and a pain just wanna learn.
Click to expand...
Click to collapse
That "SUBSYSTEM..." line needs to be appended to the file opened in the text editor. It shouldn't be entered on the command line.
And add "sudo" to in front of that gedit line...i.e., "sudo gedit /etc/udev/rules.d/51-android.rules"
Good luck!
I prefer to use adb. If you want a GUI you can use QtADB:
http://qtadb.wordpress.com/

Need help installing ADB and fastboot tools on Linux Mint 15

Hi,
Not sure where exactly to post this, so sorry if this isn't the right section. I've asked on the Linux Mint community forums (as they should have experience with the OS) but figured I'd also post here (as you guys should have experience with ADB and fastboot).
I recently switched over from Win 7 to Mint 15 and cannot get ADB and fastboot to work for the life of me! On Windows, I just downloaded and installed the Android SDK and had no trouble using ADB and fastboot to mod my phone. It is proving to be much more difficult on Linux.
I've searched Google, Linux Mint forums, and these forums; tried following numerous guides, and still my comp can't recognize my phone. Every time I type in "adb devices" I get "List of connected devices" followed by a blank line. No question marks and certainly no connected devices. "lsusb" shows my HTC One S as connected so I know it's not my USB port.
When I plug in my phone, I get an error message, "Unable to mount Android Phone Unable to open MTP device '[usb:002,005]'" and then a file explorer window opens displaying my phone contents anyways. Not sure if this could have anything to do with it but I thought I'd mention it.
In any case, I've tried so many things and am at a complete loss here. Any help would be great as nothing seems to be working and not being able to flash ROMs on my phone is killing me! :?
Thanks in advance.
No one? Craaaaaaap
DRUMROT said:
No one? Craaaaaaap
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
Check PM.
No luck. This is getting frustrating.
That did the trick for me:
Configuring USB Access
Under GNU/linux systems (and specifically under Ubuntu systems), regular users can't directly access USB devices by default. The system needs to be configured to allow such access.
The recommended approach is to create a file /etc/udev/rules.d/51-android.rules (as the root user) and to copy the following lines in it. <username> must be replaced by the actual username of the user who is authorized to access the phones over USB.
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="<username>"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="<username>"
Those new rules take effect the next time a device is plugged in. It might therefore be necessary to unplug the device and plug it back into the computer.
This is known to work on both Ubuntu Hardy Heron (8.04.x LTS) and Lucid Lynx (10.04.x LTS). Other versions of Ubuntu or other variants of GNU/linux might require different configurations.
Click to expand...
Click to collapse
from: http://source.android.com/source/initializing.html
Maybe you have to google a bit if your device is not included. If you just google 51-android-rules devicename you should find the corresponding entry.
Edit: Sorry, it was another file I used: http://code.google.com/p/51-android/source/browse/51-android.rules in this version, just the vendor is specified so you don't have to care about device id. And not just the owner (here: snowdream) is able to access the device but everyone in its group. But the one above should work as well.
The guides I followed had me create various rules.d files (99, 50, 70) and it still hasn't worked. They've never said to change the username but they must have followed the same rules as your updated link. Either way, I'll try what you've said and see what happens. I'll post back with results. Thanks for the help!
EDIT: Ok so I tried it...and it didn't work.
Not even sure what made me do it, but I decided to search for the tools for a 64-bit system (I'm using a 32-bit). I ended up getting different results and found this script https://code.google.com/p/adb-fastboot-install/ which finally made adb recognize my phone! Thank you for trying to help. Really appreciate it guys/gals.

[Q] [Ubuntu] adb does not recognize device

Hello everyone,
I have a short question which you might be able to answer (at least I hope so).
I just got a cheap Android phone on which I want to learn to do some Android app development. So, I want to use the "adb" tool on Ubuntu to push my app to the device.
First of all, I wanted to find out which vendor is the right one (as the phone itself does not have branding), so I ran "lsusb". The output was
Code:
Bus 001 Device 010: ID 1782:5d01 Spreadtrum Communications Inc.
Thus I figured that "1782" is the vendor ID and I created an udev-rule named "51-android.rules" which contains
Code:
"SUBSYSTEM=="usb", ATTR{idVendor}=="1782", MODE="0666"
I set file permissions with
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
and restarted the udev service aswell as the adb server. But still the output of "adb devices" does not show any connected devices. What am I doing wrong?
I am running Ubuntu 13.04 with Kernel 3.8.0-34. USb debugging on the phone is enabled.
Any help would be highly appreciated,
Phil

Categories

Resources