Develop Bugs

[Q] I'm having problems with adb and fastboot

I have the Android ADK installed and I have adb. I don't seem to have the privledges to use it though. If I try and use it normally I get
Code:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
I can only get it to work if I start adb as the admin. Then I can use it as a normal user.
Also, I don't seem to have fastboot. Where do I get it?

On some Linux systems, starting adb as root is the easiest way to go about things. Some systems require setting up udev rules to give normal users permissions to run adb. Still others, simply changing the permissions on adb itself and putting it somewhere in the path will work. Running it as root isn't recommended, but it does work.
As for fastboot, Google have stopped pre-compiling it and distributing it with the SDK. You can either compile the emulator to get it or download a pre-compiled binary from HTC's support website.

beartard said:
On some Linux systems, starting adb as root is the easiest way to go about things. Some systems require setting up udev rules to give normal users permissions to run adb. Still others, simply changing the permissions on adb itself and putting it somewhere in the path will work. Running it as root isn't recommended, but it does work.
As for fastboot, Google have stopped pre-compiling it and distributing it with the SDK. You can either compile the emulator to get it or download a pre-compiled binary from HTC's support website.
Click to expand...
Click to collapse
Ok I guess it's just easier to start it as root. Fastboot on the other hand wont work. After I use the command
Code:
adb reboot bootloader
my phone reboots into recovery and has FASTBOOT USB on the screen. When I type
Code:
fastboot devices
it just goes to the command line again and doesn't show anything. When I try and type $ fastboot reboot I get
Code:
< waiting for device >
Any ideas why it's not working?

I'm probably sharing my ignorance here, but did you run fastboot after starting adb as root? You might have to run it as root as well. Also, try unplugging your phone and re-plugging it before running the command.

beartard said:
I'm probably sharing my ignorance here, but did you run fastboot after starting adb as root? You might have to run it as root as well. Also, try unplugging your phone and re-plugging it before running the command.
Click to expand...
Click to collapse
Ok, now I feel really dumb. I guess I didn't run fastboot as root before. I could have sworen I did. Well now it seems to all be working, as long as I am root. I wish I could do it with out having to be root.
Thanks beartard

No problem. In case you're interested in how to do it The Right Way™ here's a post I found on the Google support forums for Android. The author had a Motorola CLIQ. The vendor id for the Slide is 0bb4.
I found this info to be helpful, although there was not much explanation behind it, and in the end things still did not work for me. after a number of hours of debugging (which was kind of fun!) i finally got things working, and wanted to document it here in case others have the same issues. also documented is *how to debug* your stuff, which may be as valuable as the fix!
disclaimer:
i still dont really understand udev very well, so if someone who does can clarify my observations, that would be cool.
my environment:
ubuntu 10.04, device is a motorola cliq.
adb version 1.0.26
eclipse version 3.5.2 (galileo)
the problem:
persistent issues with adb devices returning:
List of devices attached
???????????? no permissions
rat holes i went down:
a) first, be sure that when you write your android-specific rules in /etc/udev/rules.d that you ensure that you name the file with a name that ends in .rules, or else the udev daemon wont read it.
b) Ubuntu 10.04 uses a new version of udev, so some of the documentation you find on the web is out of date.
c) The phone looks like a disk drive to the OS, which caused me some wierdness. more later.
some basics:
a) the udev infrastructure is what the OS uses to dynamically map, present, and control USB devices. you will need to tell udev what to do with your android phone when the phone is in application debug mode (that is why you need the /etc/udev/rules.d/50-android.rules file.
b) the adb (android debug bridge) is the daemon (using network sockets) that allows the IDE to talk to the device. when you run commands like 'adb devices' the command looks for a running daemon, and if one is not running it starts one and then communicates with it.
c) the "no permissions" error message indicates that the adb daemon cannot get the right permissions to access the device as the user that it is running as. normally the IDE starts the daemon as the user you are logged in as. unless the phone device appears in the udev infrastructure with the correct permissions to be accessed as the user you are logged in as, it wont work.
steps:
1) plug your phone into the usb bus on your system. does not need to be in application debug mode yet...
2) verify that you can see the phone by using 'lsusb', e.g.:
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 044: ID 22b8:2d66 Motorola PCS
Bus 002 Device 004: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 002 Device 003: ID 10d5:0001 Uni Class Technology Co., Ltd
...
the line "ID 22b8:2d66 Motorola PCS" is my phone. the rest is other stuff on the usb busses. ignore it.
3) the 4 digit value 22b8 is the Vendor ID of my phone. yours may be different. whatever it is, this is the value you need to use in your udev rule.
4) the Bus number and Device number are useful. you can see what permissions your device is getting at any time by doing
$ ls -l /dev/bus/usb/<busnumber> where <busnumber> is the Bus number above (002 in this case).
the permissions of the device will be the permissions of the file numbered with the Device number above. in my case it was device 044, so the full file path is /dev/bus/usb/002/044
! note - this device number will change when you plug/unplug or enable/disable debug on your device.
5) you can now get *alot* of info on this device now by using 'udevadm info', but you need to use the bus and device info above (remember yours may be different and change). you can use either udev info command --query=all or --attribute-walk, e.g.:
$ udevadm info --query=all --name=/dev/bus/usb/002/044
or
$ udevadm info --attribute-walk --name=/dev/bus/usb/002/044
note that the attribute-walk walks up the bus. the first entry printed should be the lowest device on the chain, which is your phone. in my case some of the lines looked like:
looking at device '/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2.4':
KERNEL=="2-2.4"
SUBSYSTEM=="usb"
DRIVER=="usb"
ATTR{configuration}=="Motorola Config 42"
...
ATTR{idVendor}=="22b8"
...
ATTR{busnum}=="2"
ATTR{devnum}=="44"
ATTR{version}==" 2.00"
ATTR{maxchild}=="0"
ATTR{quirks}=="0x0"
ATTR{authorized}=="1"
ATTR{manufacturer}=="Motorola "
ATTR{product}=="MB200"
ATTR{serial}=="<serialnumber>"
...
where the <serialnumber> is the serial number of my phone, which will show up in the adb devices list when this all works. recognize the items that you will need for the .rules file are there.
6) now, lets write the .rules file. you have two choices. either get the permissions of the phone as it shows up changed to 0666 (rw for all users, including the world) or change the ownership to be your user. i prefer the latter. seems cleaner to me, so i will use this approach for the rest of the info.
7) find out who you are. use the id command, e.g.:
$ id
uid=1000(<your username>) gid=1000(<your group name>) groups=...
where the uid and gid for you are indicated. for now lets use both as 'juser' for the example.
8) now lets create the .rules file. the number at the beginning of the file name is the order that it will be loaded by the udev infrastructure. it may be important. all the examples showed a number of 50, but there are a bunch of things being loaded in /lib/udev/rules.d/ as well. i prefer to make my file name 99-android.rules to force it to load very late in the process. this keeps other later things from clobbering my permissions as they load.
for example, if you use the ATTR{idVendor} attribute in .rules as oppose to SYSFS{idVendor}, then when other later rules load they could over write the permissions you set in your .rules file.
9) you have to use root or sudo to create the file in /etc/udev/rules.d. create /etc/udev/rules.d/99-android.rules and put in a line like:
SUBSYSTEM=="usb", SYSFS{idVendor}=="<Vendor ID>", OWNER="<your username>" GROUP="<your group name>"
and save it.
the SYSFS{idVendor} value needs to match your device id, and the OWNER and GROUP are from step 7 above.
for this example lets use
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", OWNER="juser" GROUP="juser"
if you just want to set the permissions use:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
10) now, when you connect the device (try the application debug mode) you should be able to see that the device appears with the correct user permissions. e.g.(using this example's bus, device, and uid/gid values):
$ ls -l /dev/bus/usb/002
crw-rw-r-- 1 root root 189, 128 2010-10-09 20:02 001
...
crw-rw-r-- 1 root root 189, 131 2010-10-09 20:02 004
crw-rw-r-- 1 juser juser 189, 173 2010-10-10 11:29 044
this is very good, 'cause now adb running as you will be able to read and write the device.
11) if you did not get here, then you have udev issues. dont bother beating on adb, the problem is in udev. your best bet is to go into /etc/udev and edit udev.conf, to change the line
udev_log="err" to udev_log="debug" to see what is going on. then you can follow what udev is doing by opening a terminal window and following /var/log/syslog with:
# tail -f /var/log/syslog
you may need to restart udev, which you can do by doing:
$ sudo /etc/init.d/udev restart
from another terminal window.
this output is very verbose, but you should look to see that your .rules file is being loaded. if not, then that is the issue to fix.
12) if all is ok, and the device has the right permissions, when you put it into application debug mode you should be able to simply start the adb server with:
$ adb devices
and see your device by serial number
List of devices attached
<serialnumber> device
13) if you have problems with adb, here are a few things to check.
a) make sure you see that adb is running, and owned by you by looking for it with ps, e.g.:
$ ps aux |grep adb
you should see a line like:
juser <pid> 0.0 0.1 28160 728 pts/4 Sl 10:18 0:01 adb fork-server server
where juser should be your user id, and <pid> is the process ID.
b) if adb is running as root, you may need to use 'sudo killall adb' to kill it off and then as your user run 'adb devices', which should start the server as you.
c) if you still have problems you can run strace on the server and it's child processes with:
$ strace -f ./tools/adb server
note that the output is very verbose, but look thru there for some kind of permissions problem. lots of 'file not founds' are ok, but as the daemon starts and tries to bind to the device, you may find a permission problem.
hope this helps. sorry to be long winded.
jerichod.
Click to expand...
Click to collapse

[GUIDE *WITH VIDEO*] ADB/Fastboot Easy 5 minute setup (Great for nOObs)

Ok there are some other guides here on the forums for this but they all require you to download the Android SDK. That can be very time consuming and confusing if you run into issues. I have been looking at a way to have the capability to push and pull files using my laptop but i really didnt want to go through downloading and setting up the whole SDK just to use adb.
If anyone has followed any of my threads, you know I am all about trying to get things done in the easiest way possable to help the people that are new to Android. This method has worked for me but there is no guarentee that it will work for you and I am no way responsable for anything that happens to anything unless it works great for you. Then I will take all credit j/k. With that being said:
The first method is for Windows based OS. I have tested it on XP but I would imagine it will work on any Windows OS. If I am informed of something different I will update it here. The Mac version is in post #2 and takes less than 1 minute to do. Much thanks to kwbdc and stlouie65 for the help on this.
Instructions for setting up Adb/Fastboot (windows)
1. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
2. Install drivers on your PC. This is done on the MT4G/HTC devices by going onto your sd card and clicking on the HtcDrivers.exe file while viewing the files on your PC. It should automaticly install them to your PC. If you are using another phone or have trouble installing the ones from your sd card you can try pda.net or HTC Sync for the drivers. Here are links for pda.net 32-bit Windows 7/Vista/XP and for 64-bit Windows 7/Vista. Install the program by hitting "Run" and follow the instructions. You can remove it at a later time.
3. Download the file at the bottom of these instructions to your desktop and extract the contents. There is 1 folder and a install note (these instructions) that should extract. You can use a program called 7-ZIP (google it, its free and a great tool).
4. Open your "Start" menu and click on "My Computer". Then choose "Local Disk C:".(You can now click and drag the adb folder you extracted to the C: drive.
5.Open a command prompt and type cd\adb and hit enter. You should now see something that looks like this C:\adb>
6.Type adb devices then hit enter in the command prompt and it should list your device.
7. You can also type fastboot devices then hit enter in the command prompt an it should list your device. (you must be in the bootloader for fastboot to recognize your device)( adb command= adb reboot bootloader )
You should now be ready to send commands to your phone via ADB or Fastboot. You will need to repeat steps 5-6 anytime you want to use ADB/Fastboot. To send a file using Adb or fastboot make sure to put the file in your "adb" folder before giving the command to send it to your device.
If this helped you please use the "Thanks" button to show your gratitude.
____________________________________________________________________
Please feel free to ask any questions you want and I will help in any way I can.
DOWNLOAD MIRROR
Here are some commands for Adb/Fastboot.
DO NOT USE ANY COMMANDS THAT YOU ARENT SURE OF OR DONT KNOW WHAT THEY DO. I AM NOT RESPONSABLE FOR ANYTHING THAT YOU DO TO YOUR PHONE.
ADB Commands
adb devices - list all connected devices
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections forward specs are one of: tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed
Click to expand...
Click to collapse
.
Fastboot Commands
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Click to expand...
Click to collapse

Mac Instructions
Download THIS FILE Extract the 2 files inside it and place them on your Macintosh HD root. Plug in your phone to the usb, open terminal and type /adb devices.
It should now give u a serial #
To send a file using adb/fastboot the file must be placed in your mac HD Root or you must give the location in your command path.

Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again

92drls said:
Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again
Click to expand...
Click to collapse
Not a prob...Please let me know if this works good for you.

Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?

92drls said:
Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?
Click to expand...
Click to collapse
Put the file you are trying to push in the same folder you created.
ReName it bootanimation.zip
To push your file use this command after you cd into the folder you created.
You also need to be in recovery with your system mounted.
adb push bootanimation.zip system/customize/resource/bootanimation.zip
That is the location of the bootanimation on that rom.
Hope this helped

Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again

92drls said:
Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again
Click to expand...
Click to collapse
I do know how to change it but would rather you have the fulfillment of learning how to do it yourself You can find a great guide and splashscreens in the thread by Iriscience. Make sure to thank him for it.
Back on topic, I'm glad this worked good for you. It really is pretty simple. I dont have have a donation link (I do this for the love of helping people mod their phone) but I would appreciate it if you hit the "Thanks" button at the bottom of any post that have helped you.

Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.

@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.

30Glock said:
@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.
Click to expand...
Click to collapse
geoffott said:
Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.
Click to expand...
Click to collapse
Thanks Guys, I appreciate the kind comments! My whole intention of this thread is to help people that couldnt or didn't want to set up the Android SDK have a good solid way of pushing and pulling files to their phone.

Great guide Drew! I'll finally be giving adb a shot! I've always been intimidated by it.
This helps for sure.
Sent from my HTC Glacier using XDA App

thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?

dominicanman912 said:
thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?
Click to expand...
Click to collapse
You must be in fastboot (bootloader) for fastboot to recognize your device. You can get there by by turning off your phone then holding down the volume down button and the power button at the same time. Our you can use this command via adb (usb plugged in):
adb reboot bootloader
Your device should automatically go into fastboot from the bootloader. If it doesn't you can scroll to fastboot using the volume button and hit the power button.

Thank you for answering my question! I have been reading a lot about adb over the past few days and I feel more comfortable with this way than the pain in the ass sdk method! When I get back on the pc, I will be sure to hit that thanks button because you have been a great help.
Sent From my ICE COLD HTC Glacier aka MyTORCH4G!

How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153

koolkid09 said:
How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153
Click to expand...
Click to collapse
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img

TrueBlue_Drew said:
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you so much!! I have been trying to do this for the past hour now! lol

Awesome post! Saved me a (potentially painful) convo with a friend who's just getting into modding his MT4G.

error
I feel like an idiot, idk what im doing wrong, in command prompt i get this message, 'adb' is not recognized as an internal or external command, operable program or batch file......what am I doing wrong?

Xperia on Ubuntu (Udev rules, Flashtool, ADB&Fastboot)

This is a thread written to try and get poor MilkyJoePD up and running with his Ubuntu build, but it should be of help to anyone.
First of all, what you need:
1) Any version of Ubuntu from 10.04 onwards, with superuser access. The upcoming LTS Ubuntu 12.04 will be a great idea when it comes out, as it'll be maintained for 5 years (so the instructions to install it there will be valid for all that time).
2) Your Xperia Play (or any Xperia phone actually).
3) A Micro USB cable to connect it.
4) An open mind about terminal emulators. They're useful because they allow you to do things quickly and cleanly, if you just know their syntax.
What will we be doing in this thread: we'll set up our Xperia Play so that it gets recognized properly by Ubuntu. In addition, we'll set up ADB and Flashtool, which are programs with which our Xperia Play can interact. Lastly, we'll cover how to summon the "adb" and "fastboot" commands from any point in the terminal, by adding them to the $PATH variable.
Setting up the Xperia phone: udev rules
Android devices don't need specific drivers to work in Linux: you can plug an Android phone and it will be recognised as a flash drive. However, if we want deeper levels of interaction, such as the ones which ADB, Fastboot and Flashtool provide, we have to set up udev rules. Long story short, udev rules allow us to give the proper permissions that these modes require without having to function as superuser the whole time (an undesirable state of things in Ubuntu). Much more about them can be found here for the curious minds out there.
But let's not get lost. We want to set up udev rules, so we'll do it. First of all, we need to know the following: a device connected while it functions normally is not "seen" as the same device when it's connected in the Flash or Fastboot modes. In order to identify it, we can run "lsusb" which lists all of the ports, and connected devices, in our computer.
So, let's connect a Xperia phone which is turned on. We don't have to mount the sdcard as a flash drive, just plug it in. Once you have done that, open a terminal and type
Code:
lsusb
It will list you a boatload of devices, but only one of them is relevant to you right now:
Code:
Bus 00x Device 00y: ID 0fce:aaaa Sony Ericsson blah blah
The device is identified with two alphanumeric chains. The first one is the vendor ID, and the second one is the Product ID, which are the identificators we're going to use for the udev rules later on.
Let's switch off our phone, and plug it in "Flash" mode (hold the Back button while you connect it). Run "lsusb" again in the terminal again, and you'll find:
Code:
Bus 00x Device 00y: ID 0fce:bbbb Sony Ericsson blah blah
The Vendor ID is the same (0fce) for all Sony Ericsson devices, but the Product ID is different, as you can see. This is consistent with the idea that it's identified as "another" device.
The last part would be plugging the phone in Fastboot mode, holding the Search key while we plug the phone. Typing "lsusb" in the terminal again will give us:
Code:
Bus 00x Device 00y: ID 0fce:cccc Sony Ericsson blah blah
Which is, as we know already, a different Product ID.
Now that we have the device ID needed for the udev rules, we can write them. The most expedite way is to write in that lovely terminal:
Code:
sudo gedit /etc/udev/rules.d/99-android.rules
That means, we'll use the standard text editor (gedit) to create the file 99-android.rules in the /etc/udev/rules.d folder. If we visit said folder we'll find other udev rules created already, but they're not interesting for our task. Notice that we ask for superuser permissions with "sudo" as we need them to write or modify udev rules. Once we have put our password we'll find an empty text file. And now we just copy-paste the following syntax:
Code:
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”aaaa″, MODE=”0666″
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”bbbb″, MODE=”0666″
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”cccc″, MODE=”0666″
In human language, this means "Give the devices that are connected through USB and which have the mentioned ID codes the permissions 0666 (read/write access), which need root access".
Once we've filled the gaps, we just save the file. After we close it, we have to type in the terminal "sudo restart udev" and we've taken care of that part. Rebooting the computer has the same effect, but it's a bit of overkill, really.
Flashtool
With the udev rules fixed, we can go to the next step, which would be using Flashtool. It is necessary to mention that unlike the Windows version, Flashtool doesn't need any installation of any kind in Linux, you just run the program (the file called Flashtool) and you're set. You have to download the Flashtool folder, uncompress it and run the program. The folder is compressed in .7z format: Ubuntu doesn't manage 7z packages "out of the box", but that's no problem: go to your terminal, type:
Code:
sudo apt-get install p7zip-full
and that should take care of it. If you're not familiar with that command, "apt-get install" is the way to install packages from your existing repositories in Debian/Ubuntu; installing software in Ubuntu requires superuser access, as I'm sure you know. p7zip-full is a package which adds 7zip support to the archive manager of Ubuntu.
I won't cover how to use Flashtool, since I already did so in this post. While I made the tutorial for an older version of Flashtool, the base functions are exactly the same as before.
Optional: ADB and Fastboot; setting them in $PATH
OK, now we're going to the stronger stuff: if you want to do a bit more than restoring official ROMs and flashing kernels you'll do well in using the ADB and Fastboot programs. They're part of the platform tools of the Android SDK. You can download the latest Android SDK here: http://developer.android.com/sdk/index.html
Once you've downloaded and uncompressed the Linux version of the SDK, go to the "tools" folder and run the "android" file (you need to mark it as executable first, in the properties). That file is the Android SDK Manager. Once it's running, you only need to install the SDK Platform Tools package. The rest are not necessary for our purposes.
Once you install the package, you'll notice that the folder where you unpacked the SDK is bigger. You'll find there the "platform-tools" folder, which contains adb and fastboot. You can run them from a terminal, but that requires you to have your terminal running in the exact folder where your /<Path/to/SDK> directory lies. This can get old really quickly if you use ADB and/or Fastboot frequently, so we'll do a trick that will allow us to summon them from any folder: we'll add them to our PATH variable.
In order to do this, we need to open a new terminal. It will start in our home directory. There is a file called .bashrc in our home folder that we need to tweak, so let's go to it. You don't see it normally, as it's hidden. All files which begin with a . in Linux will be hidden by default. You can see them in Nautilus by pressing Ctrl+H, and in a terminal by typing "ls -a". At any rate, this file is hidden because you usually don't need to touch it, but we'll do it here.
In our terminal, we write
Code:
gedit .bashrc
Again, gedit is the standard text editor in Ubuntu.
We see a lot of stuff we don't need to touch. We just need to go to the final line, after the word "fi" and write below:
Code:
# ADB and Fastboot direct link (this is a comment, so we remember what we did)
PATH=$PATH:/home/Path/to/SDK/platform-tools/
export PATH
We save the modified file, close any terminal we had left open, and now we can use adb and fastboot directly from any folder. Just connect your device with debug mode on for example, and type "adb devices": you should see the ADB identificator of your device.
And with that, I cover the installation guide of Xperia phones in the Ubuntu environment. I hope it's useful to everyone, particularly to MilkyJoePD who has inspired me to write it. If I've missed something I should have mentioned, by all means say it.

Haven't used Ubuntu for a while but I'm taking note of this for later. Thank you for the info.
Sent from a Galaxy far, far away

don't forget to install de dependencies:
Code:
sudo apt-get install libusb-1.0
on 64 systems, you need 32bits libraries, so run:
Code:
sudo apt-get install ia32-libs

With the news of Sony not releasing ICS, I decided to try again to get fastboot working.
While installing the dependencies, I get this:
W: Duplicate sources.list entry cdrom://Ubuntu 11.10 _Oneiric Ocelot_ - Release i386 (20111012)/ oneiric/main i386 Packages (/var/lib/apt/lists/Ubuntu%2011.10%20%5fOneiric%20Ocelot%5f%20-%20Release%20i386%20(20111012)_dists_oneiric_main_binary-i386_Packages)
W: Duplicate sources.list entry cdrom://Ubuntu 11.10 _Oneiric Ocelot_ - Release i386 (20111012)/ oneiric/restricted i386 Packages (/var/lib/apt/lists/Ubuntu%2011.10%20%5fOneiric%20Ocelot%5f%20-%20Release%20i386%20(20111012)_dists_oneiric_restricted_binary-i386_Packages)
W: You may want to run apt-get update to correct these problems
Where do I go from here?

Remove CD-ROM reference from sources
Edit your sources and comment-out / turn off the references for the installation disk (CDROM/DVD). It should be the first thing you turn of after any install anyway. In my humble opinion.
Then run
sudo apt-get update
sudo apt-get -f install
this should resolve any pending issues and get you running.

skeltonh said:
Edit your sources and comment-out / turn off the references for the installation disk (CDROM/DVD).
Click to expand...
Click to collapse
How do I do that?
Sent from my R800i using XDA

Or can somebody can tell me what it means so I can Google it?
Sent from my R800i using XDA

I have a problem, when I try to use fastboot even in the platform-tools folder it says:
fastboot: command not found

On what OS? If it's Linux, you have to add a Dotslash to execute the file.
Swypesation

I have created udev rules as said above, but flashtool still says 'Add udev rules'.
What I am missing here. I'm using Ubuntu 12.04.
Any help is appreciated.

You must start flashtool with root acces

is rooting ur play a wise decission?

wat is better 4 my play, ics or gingerbreadman?

where/what is the search key on a mini pro?
Thanks

Big Thanks for this Tutorial Logesman. :good: Just wanted to add that I think...anyone having trouble installing SDK + Manager has to install Java JDK first. Yes, I got stuck at installing SDK.:silly: I tried to run android file in tools folder (as executable) which opens manager.
From Terminal:
sudo apt-get install openjdk-7-jdk openjdk-7-jre

i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:

roopz said:
i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:
Click to expand...
Click to collapse
I am having same problem on 12.04! I did everything in this thread afaik, and the ubuntu forums. I could really use some help , because I also have problems with adb.
Sent from my R800i using xda premium

install windows might be easier.
Sent from my Xperia Play using Tapatalk 2

roopz said:
i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:
Click to expand...
Click to collapse
cyrusalmighty said:
I am having same problem on 12.04! I did everything in this thread afaik, and the ubuntu forums. I could really use some help , because I also have problems with adb.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Have you tried running adb as root? (After a week of testing 12.04, I left to go back to 10.04, a much better release, imo)
Pax
Sent from my R800x using Tapatalk 2

IE-coRe said:
I have a problem, when I try to use fastboot even in the platform-tools folder it says:
fastboot: command not found
Click to expand...
Click to collapse
seems like you didn't path the fastboot command correctly, try check back again at your .bashrc
roopz said:
i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:
Click to expand...
Click to collapse
same case as the above
cyrusalmighty said:
I am having same problem on 12.04! I did everything in this thread afaik, and the ubuntu forums. I could really use some help , because I also have problems with adb.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
would you mind telling what does the error says?

samsung drivers for ubuntu 13.10?

like the title says, does anybody have the samsung drivers for ubuntu? my phone doesnt want to connect to my computer running ubuntu 13.10

m_reyna_16 said:
like the title says, does anybody have the samsung drivers for ubuntu? my phone doesnt want to connect to my computer running ubuntu 13.10
Click to expand...
Click to collapse
sudo apt-get instal mtp-tools mtpfs
Click to expand...
Click to collapse
type in
lsusb
Click to expand...
Click to collapse
Get the vendor number.
Then use gedit to add the vendor number to :
sudo gedit /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
this will allow adb to see your phone, Note sure if there is a way to install Ubuntu drivers from samsung

dragonstalker said:
type in
Get the vendor number.
Then use gedit to add the vendor number to :
this will allow adb to see your phone, Note sure if there is a way to install Ubuntu drivers from samsung
Click to expand...
Click to collapse
what do you mean by vendor number?

m_reyna_16 said:
what do you mean by vendor number?
Click to expand...
Click to collapse
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:
Code:
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:
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
Samsung Vendor ID:
Samsung 04e8

Pixel 3XL adb works, fastboot not seeing phone?

I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?

CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
This happens because the device drivers are not completely installed.

CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
then: chmod 644 51-android.rules
and: chown root: 51-android.rules

Thank you for the replies.
I tried to use adb/fastboot on a Win7 desktop after I posted the above, and I cannot get the phone and win7 to see each other at all.
I have since tried to get into recovery mode but get "No Command".
What can I do to move forward? Phone boots and works fine once I get out of recovery.
This phone is fresh from Google, never had a sim in it.

Thank you for the detailed answer. I am having difficulty implementing the mods you listed. I have been a Linux user on and off for several years but I do not have deep knowledge of the inner workings.
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS) This returns "permission denied"
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev" <-- I have no rules.d file, just an empty folder named rules.d in that location
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse

Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL

Eudeferrer said:
Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Yes, r28.0.3.

Update:
CruelSun said:
Thank you for the replies.
I have since tried to get into recovery mode but get "No Command". I found out how t get past this, I'm going to do a factory reset and start over.
This phone is fresh from Google, never had a sim in it.
Click to expand...
Click to collapse

Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!

CruelSun said:
Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!
Click to expand...
Click to collapse
Glad you figured it out.
Sent from my Pixel 3 XL

Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol

STALKER18 said:
Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol
Click to expand...
Click to collapse
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Sent from my Pixel 3 XL using Tapatalk

CruelSun said:
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Click to expand...
Click to collapse
Windows has to update. The 30 minutes was probably the update in the background. My windows 10 did the same thing. Linux doesnt work anymore. I used ubuntu with latest adb and fastboot packages. Manually installed newest tools zip. Nothing. I got it to work a few times. Windows 10 is a little buggy too. Only fastboot I found to work on the pixel 3 xl without and or little errors was my MacBook. Which I have dual booted to chromeos and Ubuntu in chromeos. Also restarting on windows anything puts it into the loop of things. You can install adb and fastboot on windows but they need a restart to work. Unless just mounting the file folder and using it that way.

I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
Click to expand...
Click to collapse
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
uicnren said:
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
Click to expand...
Click to collapse
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
uicnren said:
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...

CruelSun said:
I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...
Click to expand...
Click to collapse
Simplest method: https://github.com/corbindavenport/nexus-tools

CruelSun said:
...
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
...
Click to expand...
Click to collapse
I realize this is a bit old now, but, in case it's helpful for someone in the future...
Often the /etc/used/rules.d directory is empty. You just need to add the file 51-android.rules into that directory.
Code:
sudo touch /etc/used/rules.d/51-android.rules
You need to run that command as root which is why it's prefaced with sudo.
Then you can edit the file as described in the first post. As stated earlier, much better to type into your editor rather than cut and paste because you want to make sure no weird html characters get introduced.