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] Root Xoom with linux ?

i ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please

Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk

Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse

well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see

Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse

elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.

cheers for all your help will give this a go "Dont want to back to windows

Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now

glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)

have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?

elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).

Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working

elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.

all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse

depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img

error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)

What am doing so wrong its lucky am not bold yet been trying this all day

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"

I have put the file on the desktop ? is that what u mean

[Q] adb devices returns '??????????????? no permissions'

This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?

JAMCx said:
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
Click to expand...
Click to collapse
Did u allow your pc from the phone when connecting it to adb?

JAMCx said:
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
Click to expand...
Click to collapse
Just "sudo adb devices"
Happens to me on my ubuntu build VM too

bud77 said:
Just "sudo adb devices"
Happens to me on my ubuntu build VM too
Click to expand...
Click to collapse
Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.

JAMCx said:
Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.
Click to expand...
Click to collapse
Did yo follow these steps already ?
If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:
Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules.
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
(From here)

bud77 said:
Did yo follow these steps already ?
(From here)
Click to expand...
Click to collapse
Above my pay grade ... I'll just plug it in the Mac
Thanks though.
Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.

JAMCx said:
Above my pay grade ... I'll just plug it in the Mac
Thanks though.
Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.
Click to expand...
Click to collapse
Just had the same problem and solved it by creating the file above.
Create the file
sudo vim /etc/udev/rules.d/51-android.rules
add the line below:
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"
and reload the the new rules by using this command (or reboot ):
sudo udevadm control --reload
unplug the device and plug it back in and now "sudo adb devices" should show the correct name and status.

Do sudo bash, then password, the adb and fastboot work fine for me. If using windows cmd, run as admin.

Nexus s fastboot on Ubuntu 15 64bit

So dont ask me why, but I was redoing windows and just for no reason ended up with Ubuntu instead with actually no knowledge of Linux. Still I love trying out new things and I think I am loving Ubuntu so far, only can't get fastboot/adb to work with phone. Honestly I thought it would be easier here than on windows... Alas..
Problem is 'adb devices' when I connect phone within ROM works, (adb debugging enabled), result is:
List of devices attached
3530B61945F400EC device
But when I run the same command from bootloader it does not list any devices.
Even from the ROM when i try fastboot reboot command it just gets stuck on <waiting for device>.
Did some googling and came across:
sudo gedit /etc/udev/rules.d/51-android.rules
and added:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="fasih"
fasih being my username.
Still no luck.
Any help?