Database Info

Configuring USB Access for Nexus S 4G for development

I'm looking to dabble in making my own rom just for the hell of it, and to learn what the devs do
but before I start I need to set up usb access for my phone, and was wondering if you guys could point me in the right direction for doing so

download and install Android SDK,
in the phone just go into settings --> applications --> development --> usb debugging
and use ADB to connect and execute commands
done

that's it? damn I thought I had to configure something else been using this guide, and it threw me for a loop on the usb access part
http://source.android.com/source/initializing.html

ROB281 said:
that's it? damn I thought I had to configure something else been using this guide, and it threw me for a loop on the usb access part
http://source.android.com/source/initializing.html
Click to expand...
Click to collapse
The "Configuring USB Access" part is for using adb with regular user account on Ubuntu . Because normally you need to have root permission to access a USB device e.g. you have to type sudo adb devices instead of only adb devices
To follow the guide, use the following command:
Code:
cd /etc/udev/rules.d
sudo nano 51-android.rules
Then copy/paste the lines in the guide into the file and change <username> to your account name, in my case it would be something like: (notice the OWNER= part)
Code:
# adb protocol on crespo (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="suksit"
# fastboot protocol on crespo (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="suksit"
Then save the file and plug in your Nexus S. If you can use the command adb devices then you're good to go.

ADB from Linux

I just got a refurbished Xoom wifi from woot.com. I am trying to access it via adb from my Ubuntu PC, but it doesn't seem to recognize it. I have followed the guides for the udev rules, and it works (to a degree). It seems that my PCIIDS may be different, and this may be the problem.
I previously owned a g-tablet and a Zenithink epad, and was able to access them through adb, after changing the udev rules.
I also want to root it, and I understand that it must be able to recognize it to do that. There seems to be three modes that you can start it up in, RSD, Fastboot and Android Recovery. I'm not sure if I should be in RSD or Fastboot for adb to work, but each mode gives a slightly different PCIID.
I do have a fastboot binary for Linux, but it too needs the PC to first "see" the Xoom.

For me, in opensuse
lsusb to see the constructor and id ( be careful the id change between normal mode, recovery and fastboot)
mine is :
In normal mode
Bus 002 Device 006: ID 22b8:70a8 Motorola PCS
with debug on
Bus 002 Device 006: ID 22b8:70a9 Motorola PCS
In Bootloader
Bus 002 Device 006: ID 18d1:708c Motorola PCS
In bootRSD
Bus 002 Device 006: ID 22b8:70a4 Motorola PCS
Edit or create your /etc/udev/rules.d/92-motorola-xoom.rules
to reflect the id's of your xoom
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a8", MODE="0666" SYMLINK+="xoom"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a9", MODE="0666" SYMLINK+="xoomdebug"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="708c", MODE="0666" SYMLINK+="xoombootloader"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a4", MODE="0666" SYMLINK+="xoombRSD"
Click to expand...
Click to collapse
restart udev or reboot
sudo /etc/init.d/boot.udev restart
And normally you should see your device with
adb devices

Thanks for the reply.
I have been trying something very similar. I don't believe that I can directly copy a SuSE version to use on Ubuntu, but it gives me some ideas.
Here is what worked for my g-tablet:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
I think that was for mounting it to transfer files. I tried something like that for the Xoom IDs, but it didn't give me adb access.
I'll keep plugging away!

I finally got it to find it in adb. I'm not sure what did it, but rebooting the PC may have helped.
I am still not getting it to be seen by fastboot. I am following a How-To for rooting that first requires unlocking the bootloader. That is why I am trying to get fastboot to work.
If you know of a better way to root it, please advise me.
Thanks.

Just plug it when in fastboot and note the ID and constructor (mine change from 22b8 to 18d1 depending of the state) in that state and add it to your rules
reboot and try again

I've done that, with and without USB debugging enabled.
I think that the Linux versions of fastboot that I am trying may not be working. I am currently trying to install everything needed on my Win 7 laptop. The windows SDK includes fastboot, where the Linux version doesn't.

Ran it in windows and it is now performing the unlocking. It's disappointing that it isn't working in Linux.

I found another copy of Linux flashboot, from somewhere on the web. That one seems to work if I run it with root permissions (sudo). Otherwise I get this:
Code:
$ fastboot devices
no permissions fastboot
I'm not sure if tweaking the udev rules will fix this, but running it with sudo is no big deal. I'm just glad I got it to work.

[Q] Linux ADB and my GT 7+

For whatever reason, my GT 7+ is showing: ????????? offline/device when I run adb devices. I've tried running adb kill/start as root, still nothing. I've cycled "USB debugging". I'm running ubuntu 10.10. Every thing but adb is working but adb
Any insight or help would be helpful.

udev.
See: http://wiki.cyanogenmod.com/wiki/Udev

Answered
Here's the rule I put up in /etc/udev/rules/98-android.rules:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666" #all samsung devices
Then restart udev and then restart adb and it's up!

This method is hard to remember. You can also start adb as root with:
adb start-server
and it should work that way, at least until adb is closed. You do not have to do all the adb commands as root, only the start.

Jason_25 said:
This method is hard to remember. You can also start adb as root with:
adb start-server
and it should work that way, at least until adb is closed. You do not have to do all the adb commands as root, only the start.
Click to expand...
Click to collapse
Why do you need to remember it? Create a udev rule once and you never have to deal with it again.
Running things as root should be avoided if possible.

I have found that there may be an issue with ubuntu 10.10 and this tablet. For me, it seems that the MTP crud is interfering with adb. If I freeze the MTP application on the tablet, I have no problem.
...and now it gets even stranger: If I boot ubuntu 10.10 in a virtual machine (vmware 8.x), its fine even with mtp enabled.
I haven't had any issue at all with my gentoo boot. (However, I've been trying to do the android development with ubuntu as it appears to be directly supported by google.)
(This really isn't an issue for me, as I actually prefer to keep MTP disabled so I don't get popups.)

Entropy512 said:
Why do you need to remember it? Create a udev rule once and you never have to deal with it again.
Running things as root should be avoided if possible.
Click to expand...
Click to collapse
Because I work on computers other than my own?
Because I have more than one computer?
Because I sometime reinstall the OS?
Because I don't have magical fail-proof hardware?
Because udev gets messed up and apt-get replaces the rules file?
This method is simpler for new users. The adb tools are straight from google so can be trusted and the udev approach just adds a lot of complexity.
edit:
garyd9 said:
I have found that there may be an issue with ubuntu 10.10 and this tablet. For me, it seems that the MTP crud is interfering with adb. If I freeze the MTP application on the tablet, I have no problem.
Click to expand...
Click to collapse
I do not seem to have any problem using 64-bit debian, which you probably know Ubuntu is based on. I have even built the AOSP with it without much trouble. Though, deploying it to a device is a different matter for me.

How to Internet Pass Through from Linux to Sensation?

Hi everyone
I have a Sensation 4g and my system runs Ubuntu 12.04.
I was wondering if there is any way to make Internet Pass Through work with Linux?
In Windows, I install the HTC Sync and it works, but what about Linux?
Thanks

NikosDim said:
Hi everyone
I have a Sensation 4g and my system runs Ubuntu 12.04.
I was wondering if there is any way to make Internet Pass Through work with Linux?
In Windows, I install the HTC Sync and it works, but what about Linux?
Thanks
Click to expand...
Click to collapse
It works by default
In windows it asks for htc sync coz it need drivers to recognize the device
In Linux drivers are not necessarily required
You can just connect the device and use Internet pass through
(if you got adb working on that pc already then you are good to go)
Sent from my pyramid.. Through blazing fast sonic waves

I remember this as well on Ubuntu 11.04 - I only needed to modify some lines for ADB to get it work

well add the attached 51-android.rules file to /etc/udev/rules.d/ ( remove the .txt extension to the file ..i need to add it to attach in xda )
and chmod it to 755
(i.e chmod 755 /etc/udev/rules.d/51-android.rules )
then try the pass through it might work

For me it is not working
Let me explain what I did.
First of all I connected my phone with the laptop. In the beginning the
Code:
adb devices
was giving me ??????????? but I restarted the server as root and then adb was recognizing my device properly.
Then I chose Internet Pass Through in my phone but despite the fact that Ubuntu recognize my phone as a Wired Connection 2 (Wired Network - HTC Android Phone) I don't have internet on my phone. Also when I chose the Internet Pass Through in my phone, the
Code:
adb devices
list is empty (is this normal?).
So, ganeshp I pasted the rules that you gave me in the /etc/udev/rules.d/ and I changed the permisions but no luck. It doesn't work.
Also, after enabling the Internet Pass Through after some minuter I get a failure message on my phone that says
Unable to connect to PC
Either you don't have the latest version of HTC Sync installed on your PC, or another phone is already using Internet pass-through on your PC. Please ensure......etc
Click to expand...
Click to collapse
davebugyi what lines you needed to modify in the adb to get it work?

No one has an answer for this? If you are using Internet pass through without problems in your linux OS share what you did to make it work.

NikosDim said:
No one has an answer for this? If you are using Internet pass through without problems in your linux OS share what you did to make it work.
Click to expand...
Click to collapse
I've got my HIS working in Ubuntu 12.04 (DHD also). No root access or adb needed. Just simple script for Network Manager. I've posted a blog entry about this, it's in Russian, but you can use Google Translate to read it. http_://blog.loquens.org/?p=489

NikosDim said:
For me it is not working
Let me explain what I did.
First of all I connected my phone with the laptop. In the beginning the
Code:
adb devices
was giving me ??????????? but I restarted the server as root and then adb was recognizing my device properly.
Then I chose Internet Pass Through in my phone but despite the fact that Ubuntu recognize my phone as a Wired Connection 2 (Wired Network - HTC Android Phone) I don't have internet on my phone. Also when I chose the Internet Pass Through in my phone, the
Code:
adb devices
list is empty (is this normal?).
So, ganeshp I pasted the rules that you gave me in the /etc/udev/rules.d/ and I changed the permisions but no luck. It doesn't work.
Also, after enabling the Internet Pass Through after some minuter I get a failure message on my phone that says
davebugyi what lines you needed to modify in the adb to get it work?
Click to expand...
Click to collapse
all you have to do is to use sudo
HTML:
sudo adb devices

Do the following:
Press CTRL + ALT + T to open the Terminal.
Inside the terminal type:
Code:
lsusb
Output should look something like this
Code:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 003: ID 0bb4:0c86 HTC (High Tech Computer Corp.) Sensation
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Take note of these two values 0bb4:0c86 next to the HTC (High Tech Computer Corp.) Sensation.
Then type:
Code:
sudo nano /etc/udev/rules.d/51-android.rules
That will open a file named 51-android.rules then type:
Code:
SUBSYSTEM="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c86", MODE="0666", OWNER="username"
In the text above change 0bb4 and 0c86 with the numbers you got from the lsusb, and instead of the username type youre user name.
Press CTRL + O and hit enter, then press CTRL + X .
if your adb-server was running up until now you need to kill it and restart it as root so type the following:
Code:
adb kill-server
sudo adb start-server
Then to check if everything worked out type
Code:
sudo adb devices
If all went well there should be an output similar this and you are good to go:
Code:
$ sudo adb devices
List of devices attached
BLABLABLA device
Edit: I assumed by the way that you have turned USB Debugging on :> that covers adb part, for the Internet pass trough you dont need drivers for linux just select the mode when you connect your device and you should be good to go.

USB debugging not working properly (on Ubuntu)

Hello,
I just got a new U11, hoping to use it to test/debug my Android apps. But I cannot get it connect to ADB reliably. I have tried everything I could, including
enabling developer options + USB debugging
adb kill-server, adb start-server and adb devices
revoking USB debugging authorizations
authorizing & remembering my PC
I've tried countless combinations of the above, but adb keeps showing unauthorized or offline. Very very occasionally adb shows "connected", but Android Studio freezes when I run my app. When I unplug, Android Studio immediately unfreezes. But again, when I plug my phone it becomes unauthorized/offline.
My other Android phone works without any issues. Is it a bug with the stock firmware?
The phone is running stock European firmware, with everything stock (including locked bootloader).

Could anyone please test/confirm this on their Linux laptop/desktop? Any fixes? Thanks a lot!

Strangely, it works on Windows. Maybe Ubuntu kernel update yesterday broke adb :crying:

I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Sent from my XT1575 using Tapatalk

drzoo2 said:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Click to expand...
Click to collapse
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution

spolarbear said:
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
Click to expand...
Click to collapse
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.

microcris said:
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
Click to expand...
Click to collapse
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.

My Xiaomi running LineageOS (basically AOSP) doesn't have any issue. Perhaps HTC Sense heavily modified some USB options?

spolarbear said:
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
Click to expand...
Click to collapse
I have no problem with my M8 and my computer.
Android "is" Linux. By that, at least, tools like adb and fastboot must be very well tested under Linux :angel:.
Try to open you computer file browser and to browse or copy some files from/to your computer/phone. I'm unable to do that also.
I tried to root my phone in the same day I received it and I was getting really worried because I was unable to use fastboot (I by that I was thinking that my device was defective), even the simple "fastboot getvar all". Then I remembered to switch to another computer and voilà, everything was working perfectly.
Maybe HTC has something broken in the USB3.0 stack.

File transfer and fastboot don't work on my Ubuntu either.

spolarbear said:
File transfer and fastboot don't work on my Ubuntu either.
Click to expand...
Click to collapse
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).

microcris said:
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
Click to expand...
Click to collapse
I tried 4.10 and 4.4, neither worked

I have same problem with Windows 10 64Bit.

All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?

I have solved my problem. I have install Windows 10 new and now all working.

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
What Linux distro/version are you running? I've been trying to get this working with Arch and it's driving me nuts!

I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
Flinny said:
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Click to expand...
Click to collapse
Got it working by downloading adb straight from Google instead of using the Arch package.