Database Users

[Guide] ADB with Galaxy S in Ubuntu *Updated 9-10-10*

I still see a lot of people having trouble with ADB in ubuntu, so here is quick guide for anyone still having trouble.
The guide is located HERE and also can be viewed on post #12
*Updated 9-10-10* Thanks to xipher_zero for his very quick and easy guide (Much better than my original).
Hope this helps some people having issues.

If I install unbuntu it overrides my win7 correct?
Sent from my SGH-T959 using XDA App

Oh my!! I've been searched for this guide for a long time Thanks you so much MR.the3dman

Wykedx
Oh boy... where to get started. You could install Ubuntu without overwriting your W7 installation. Then you would "dual boot" your computer. As it boots up, you choose which OS to load. Or of course you could install Ubuntu on a computer by itself.
You don't need to install Ubuntu just to use ADB. ADB runs on both Win and Linux. What is it that you are trying to do? If you just want to learn linux, then make yourself a live CD and you won't have to worry about overwriting any operating systems.
But this is not a linux forum. If this is something that you are interested in, then google is your friend.

if you are interested in trying ubuntu, you might check this out: http://wubi-installer.org/. or just run a LiveCD, as already suggested.

Do you happen to have a HTC??
My output of lsusb:
Code:
Bus 002 Device 002: ID 04e8:681d Samsung Electronics Co., Ltd
Shouldn't /etc/udev/rules.d/51-android.rules contain 04e8 instead of 0bb4?
And no, even that didn't help me. I'm on Ubuntu Lucid Lynx 64 bit.

fantasyzer said:
Do you happen to have a HTC??
My output of lsusb:
Code:
Bus 002 Device 002: ID 04e8:681d Samsung Electronics Co., Ltd
Shouldn't /etc/udev/rules.d/51-android.rules contain 04e8 instead of 0bb4?
And no, even that didn't help me. I'm on Ubuntu Lucid Lynx 64 bit.
Click to expand...
Click to collapse
Thanks for noticing that! I have updated the rules with the correct ones. I have an htc also and uploaded the wrong rules. I am also on Ubuntu Lucid 64 bit and this is what worked for me. I also have done this on my netbook which runs 9.10 so I am really not sure what the issue is then. Did you use ADB from the sdk or from the app inventor adb in the guide?

If I read correctly when browsing for this topic, your instruction is to drop in these rule files, and then run adb using sudo
When using sudo to run adb, it'll always work, regardless of what's in your rules file
If you have your rules file correct, you don't need to do sudo adb
Just adb will work fine

animefans said:
If I read correctly when browsing for this topic, your instruction is to drop in these rule files, and then run adb using sudo
When using sudo to run adb, it'll always work, regardless of what's in your rules file
If you have your rules file correct, you don't need to do sudo adb
Just adb will work fine
Click to expand...
Click to collapse
I did try this, I removed my rules and reloaded my udev folder then tried adb with sudo and it was a no go (I get nothing listed under the list of devices). Also the only way I could get adb to recognize anything without sudo was by adding a line in the rules making my user as the owner, but even still without sudo under devices I get ???????????? no permissions. With sudo and the rules everything works fine which is why I wrote the guide that way.

If you don't want to run ADB as root you can follow the steps in this post
http://forum.xda-developers.com/showpost.php?p=7282335&postcount=4 - FOR SAMSUNG ONLY DEVICES!!!
after you installed SDK.
I also have adb in my path so I do not have to be in the tools directory, and can execute it from anywhere
In my .bashrc file (if you are using bash shell)
Code:
export PATH=$PATH:/path/to/android-sdk/tools

Thanks the3dman for the guide. Unfortunately I am still having problems as when I run the sudo ./adb devices nothing is listed. I followed the directions step by step and also confirmed my Vibrant is in debug mode (also confirms on the phone it is in debug mode when connected via usb. I even rebooted everything again, double checked everything and still no devices listed. I am running Ubuntu 10.04 Any ideas? Thanks so much!
-mG

Four Step ADB installation in Ubuntu
Here is a simple guide without using custom debs:
1. Download the SDK:
wget dl.google.com/android/android-sdk_r07-linux_x86.tgz
2. Extract the archive to the current directory and move into the extracted directory.
tar xvfz android-sdk_r07-linux_x86.tgz && cd android-sdk-linux_x86
3. Move the "tools" folder to your local system folder:
sudo mv tools /usr/local/share/android-tools
4. Create a symbolic link to the adb executable:
sudo ln -s /usr/local/share/android-tools/adb /usr/local/bin/
Done!
from a terminal type:
sudo adb devices (This will start the server and search for connected devices)

Are you running Ubuntu 64bit? If so you need to make sure that you have the 32bit compatibility libraries installed. From the command line run the following:
sudo apt-get install ia32-libs
This will allow you to run 32bit apps in 32bit mode. Not sure if this is whats causing your issue, but it might be worth a shot.

xipher_zero: Thank you, I followed your steps and it is working now.
Oh, I am running 32bit Ubuntu so that was not the problem.

lqaddict said:
If you don't want to run ADB as root you can follow the steps in this post
http://forum.xda-developers.com/showpost.php?p=7282335&postcount=4 - FOR SAMSUNG ONLY DEVICES!!!
after you installed SDK.
I also have adb in my path so I do not have to be in the tools directory, and can execute it from anywhere
In my .bashrc file (if you are using bash shell)
Code:
export PATH=$PATH:/path/to/android-sdk/tools
Click to expand...
Click to collapse
This is not working for some people that is what is being figured out. I am in the process of updating my guide and the new and better one should be up shortly.

xipher_zero said:
Here is a simple guide without using custom debs:
1. Download the SDK:
wget dl.google.com/android/android-sdk_r07-linux_x86.tgz
2. Extract the archive to the current directory and move into the extracted directory.
tar xvfz android-sdk_r07-linux_x86.tgz && cd android-sdk-linux_x86
3. Move the "tools" folder to your local system folder:
sudo mv tools /usr/local/share/android-tools
4. Create a symbolic link to the adb executable:
sudo ln -s /usr/local/share/android-tools/adb /usr/local/bin/
Done!
from a terminal type:
sudo adb devices (This will start the server and search for connected devices)
Click to expand...
Click to collapse
This version worked well also! Thanks its much shorter and easier than my method.

MrGibbage said:
Wykedx
Oh boy... where to get started. You could install Ubuntu without overwriting your W7 installation. Then you would "dual boot" your computer. As it boots up, you choose which OS to load. Or of course you could install Ubuntu on a computer by itself.
You don't need to install Ubuntu just to use ADB. ADB runs on both Win and Linux. What is it that you are trying to do? If you just want to learn linux, then make yourself a live CD and you won't have to worry about overwriting any operating systems.
But this is not a linux forum. If this is something that you are interested in, then google is your friend.
Click to expand...
Click to collapse
thanks for the response, and sorrry i didn't see this before lol,
what i am trying to do is be able to use adb, at the moment I can't seem to use it because my default.prop is not correct so i heard i have to use linux to be able to edit my default prop...when i try to adb push or remount i get permission denied and yet I have superuser permission and everything.
do you have to root your phone while being an administrator on the computer?

Wykedx said:
thanks for the response, and sorrry i didn't see this before lol,
what i am trying to do is be able to use adb, at the moment I can't seem to use it because my default.prop is not correct so i heard i have to use linux to be able to edit my default prop...when i try to adb push or remount i get permission denied and yet I have superuser permission and everything.
do you have to root your phone while being an administrator on the computer?
Click to expand...
Click to collapse
Try putting your phone in clockwork recovery then issuing the adb commands, and yes your phone has to be rooted.

Thanks for the excellent how to, however...
I've still got a problem:
after "sudo adb devices" (step 5) I always get this message:
List of devices attached
??????????? no permissions;
while "lsusb" gives me that:
Bus 002 Device 007: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone
so how can I solve this?
(Kubuntu 10.10 is my current os)

RiverTam said:
I've still got a problem:
after "sudo adb devices" (step 5) I always get this message:
List of devices attached
??????????? no permissions;
while "lsusb" gives me that:
Bus 002 Device 007: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone
so how can I solve this?
(Kubuntu 10.10 is my current os)
Click to expand...
Click to collapse
you'll need to edit a usb rule to "look" for the samsung phone. i forgot what file to edit and what to put in there, once i find the file, i'll post it from my laptop.
EDIT: lol, i found it.
http://forum.xda-developers.com/showpost.php?p=7343021&postcount=1

[Q]Need help with ADB shell/push/etc

So im trying to mod my launcher of my stock desire build in my HD2 with 'rosie remap' found here ----> http://forum.xda-developers.com/showthread.php?t=876464
i downloaded all the neccesary sdk/adb/java requirements. the command part is where i get confused. here are some questions:
1. before i start the commands, do i restart into clockworkmod recovery? or is this another type of recovery?
2. i tried using the commands in 'cmd' while in android debugging mode but it seems like the commands required in that thread isnt working for me.
what am i doing wrong?

mini_robot said:
So im trying to mod my launcher of my stock desire build in my HD2 with 'rosie remap' found here ----> http://forum.xda-developers.com/showthread.php?t=876464
i downloaded all the neccesary sdk/adb/java requirements. the command part is where i get confused. here are some questions:
1. before i start the commands, do i restart into clockworkmod recovery? or is this another type of recovery?
2. i tried using the commands in 'cmd' while in android debugging mode but it seems like the commands required in that thread isnt working for me.
what am i doing wrong?
Click to expand...
Click to collapse
You can actually run ADB commands with the phone in Android or in CWM. I would recommend doing it in CWM though as you would typically have to reboot after pushing anything into the system folder... Just make sure that if you boot into CWM that you mount the /system partition/folder first before pushing anything to it!
As far as running the commands, out of the box the Android SDK doesn't add the tools to the Windows environment path. You either need to CD (in the command window) to the location where the SDK tools are located or add the tools to your environment path.

Digital Outcast said:
You can actually run ADB commands with the phone in Android or in CWM. I would recommend doing it in CWM though as you would typically have to reboot after pushing anything into the system folder... Just make sure that if you boot into CWM that you mount the /system partition/folder first before pushing anything to it!
As far as running the commands, out of the box the Android SDK doesn't add the tools to the Windows environment path. You either need to CD (in the command window) to the location where the SDK tools are located or add the tools to your environment path.
Click to expand...
Click to collapse
I did exactly that. I added the sdk tools to my path. Im just unsure of the commands

mini_robot said:
I did exactly that. I added the sdk tools to my path. Im just unsure of the commands
Click to expand...
Click to collapse
Oh, ok. In that case here is an example to push files to a device:
Code:
adb push tun.ko /system/lib/modules/tun.ko
This will push tun.ko from your present directory in a command window to /system/lib/modules/tun.ko. You always have to specify the full path and filename as the destination. The source can be a relative path.
Pulling files from a device works exactly the same way, just in reverse:
Code:
adb pull /system/lib/modules/tun.ko tun.ko
If you have more questions try checking out the ADB reference here: http://developer.android.com/guide/developing/tools/adb.html.

Mac compatibility

Hello, I am just curious if anyone knows of updates that will allow mac compatibility for rooting and bootloader unlocks. I know a lot of this is new, but I do not own a windows computer and I am not able to find a way to root my phone with my macbook.
I appreciate any help.
edit: I am also still running 4.1.52 and cannot get my phone to update... I thought there was a more current software available? Everytime I go into my phone to "update" is says my device is up to date.

bump it up!

In terms of rooting, can you not use gingerbreak? It's an apk so it doesn't matter if you're on a Mac. You just need to get it onto your phone somehow.
I'm also on a Mac, and for most things, I use the OS X version of adb and redo any windows batch scripts to bash style. There aren't too many mods that use actual windows execs, except rsd lite.
Otherwise you'll need bootcamp / virtualbox and a copy of windows...
Sent from my MB860 using XDA Premium App

You can do absolutely everything on Mac. I'm almost sure someone post a guide about fastboot, sbf_flash on a mac/linux
Enviado desde mi MB860 usando Tapatalk

Just run VMware Fusion & run a windows emulation..
Sent from my MB860 using XDA Premium App

I've done everything (except flash radio) on mac. There are binaries available for mac for "moto-fastboot", "adb (google SDK)" and "sbf_flash". Just search the forums. All commands will be through the terminal and will be the same as linux version
moto-fastboot: http://forum.xda-developers.com/showthread.php?t=1138092
sbf_flash is here: http://blog.opticaldelusion.org/2011/04/universal-binaries-running-same.html#more
and there's a version of adb in gingerbreak.apk if you don't want to install adb with the android sdk.

I dont know what that means... haha! Hopefully superoneclick works for the atrix eventually.
thank you for the responses.

I did everything in a virtual machine. No problems.
Sent from my MB860 using XDA Premium App

Ok im guessing this is a better place than any. anyone know how to get fastboot to work on mac? im tired of barrowing PCs lol I can adb,get it start up but everytime i go into the flash commands i get command not found. anyone know why?

joshyy_rey said:
Ok im guessing this is a better place than any. anyone know how to get fastboot to work on mac? im tired of barrowing PCs lol I can adb,get it start up but everytime i go into the flash commands i get command not found. anyone know why?
Click to expand...
Click to collapse
Add the directory where fastboot and adb are to the $PATH variable in ~/.profile
Also you can add it temporarily with the command set $PATH=$PATH:/path/to/adb
Edit: detailed instructions.
In your home folder create a folder, let's call it android_tools
Copy adb, moto-fastboot, etc to it.
Open terminal
type nano .profile
add in the file the next line:
export PATH=$PATH:~/android_tools;
press ctrl+x, then y to save the file and quit from nano
close Terminal
Open Terminal then type adb or moto-fastboot or whatever is inside android_tools and this command should be recognized.
if it fails, maybe you need to set exec permissions to the commands, open terminal, type cd ~/android_tools, then type chmod +x *
Hope this help
Enviado desde mi MB860 usando Tapatalk

(GUIDE) HOW-TO-LINUX --- Restore your BRICKED Nexus 7 using fastboot and Linux

Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS​
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:

Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)

oldsoldier2003 said:
Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)
Click to expand...
Click to collapse
I appreciate the info, I've only ever used Ubuntu Linux and every method that I had found so far was super in depth and not exactly simple. I've been doing this stuff for a while, so it's no big deal for me, but I wanted to provide something for people who don't do this kind of stuff every day. Just trying to contribute to the "cause" i guess. lol

Good tutorial

Help
Zesty01 said:
Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS​
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:
Click to expand...
Click to collapse
First link in "Dowload" is dead !

Thanks for this simple tuto !
In introduction of your thread, you can put this link : http://developer.android.com/tools/device.html

[TOOL]Latest ADB and Fastboot for Win, Linux, Mac

Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android​
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
The last SDK Platform-Tools for Win, Linux and Mac you can always find here - https://developer.android.com/studio/releases/platform-tools
Arhive:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar

sorry for being a noob and asking for another device in a different forum,
but will these adb drivers also work with nexus 4???
need them to sideload 5.0.1

IS this for android 5.0 GPE?

http://forum.xda-developers.com/htc-one/general/guide-windows-8-1-fastboot-adb-t2970692
i have anaged to get it working after expereincing the problems stated here by others ... follow my steps here for those who still have trouble

lewonsky said:
IS this for android 5.0 GPE?
Click to expand...
Click to collapse
Yes, this for all version. It' latest update from official Android SDK Platforms.
See link in OP.

Golv said:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
Click to expand...
Click to collapse
I think you forgot to mention that this is only for Windows. So it does not work for Linux or Mac.

Quick, fast, no frills, just the necessary files itself. Hopefully this thread gets updated whenever a new release comes up

thanks, nice share bro :good:

how to use those files
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6

[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
open a command window and change directory to the folder where adb.exe is installed. Then you can use adb commands. Commands syntax is as follow:
Code:
adb [target] <command>
You only need to specify the [target] if you have more than 1 android device or emulator connected simultaneously, otherwise the command will be directed to the only connected device, so the syntax will be:
Code:
adb <command>
So if you want to sideload a rom to your device, boot in your custom recovery and start the "sideload" mode.
In the command window:
Code:
adb sideload my_rom.zip
Don't forget that the rom.zip must be in the same folder where adb.exe is
If you want to use "adb push" instead of "adb sideload" then boot in custom recovery (not in sideload mode) and use the following command:
Code:
adb push my_rom.zip /sdcard
You can read more about adb commands here: http://developer.android.com/tools/help/adb.html#issuingcommands
adb sideload explained here: http://android-revolution-hd.blogspot.in/2013/12/ow-to-use-adb-sideload.html
If you have more question about what file to sideload or push a rom to your device, you should ask in the correct forum, Amazon Fire HD 6 forum is here: http://forum.xda-developers.com/fire-hd

thank u
save my day

How do you install the new adb 1.0.32 over the old version and will it work with the moto X 2014?

its dosnt work for me
and i need it ((
every phone i want use sideload , its say me , use adb 1.0.32 or newer
and when i want use adb 1.0.32 , show me this error in all adb commands :
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
what should i do ?

update adb
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
go to this website: https://fl1.androidfilehost.com/dl/...803384/minimal_adb_fastboot_v1.3.1_setup.exe?
download and install it to your computer, then try to sideload it through there.
if that doesn't work just download the stand alone SDK from the android studio website and after its downloaded, open the .rar file and extract it to a new folder to your desktop. after that open it and search for a folder that says platform tools and look for the ADB .exe file and copy it, then go to your C drive and go to programs and try to find the android studio folder, when you have located it open it and look for a folder named platform tools, then delete the adb.exe in that folder and paste the new one in there or you can probably just copy the whole platform tools folder and replace the other one in the C drive.
I hope this helps, if it doesnt just message me and im sorry for the late reply.

alishadlou said:
* failed to start daemon *
error: unknown host service
what should i do ?
Click to expand...
Click to collapse
this usually means the phone is not communicating with your PC.
- either your phone is corrupt
- the connection is corrupt
- or the cable is bad
Tip: add the path of ADB.exe to your system Environment Variables, so you can call it w/out first navigating to it.
- Right click Computer > Properties > Advanced system settings
- Environment Variables ... > edit "Path" by adding the path to ADB.exe.
ie.
Windows 10 x64, i simply add: D:\PortableApps\ADB
for other Windows, you may have to add to the end of "Path", click edit > scroll to the end > add ;D:\PortableApps\ADB;
(don't forget to add the semicolon at the end)
Now you can simply launch Command Prompt and enter: ADB sideload *file*

Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android​
Download: fastboot_adb(1.0.36)_110716_r24.0.rar

Not working on Android 6.0
This and older versions will not work on Samsung S7E for system backup and restore.
It accepts the commands, but the confirmation popup supposed to open on the device never does. For a few 6.0 users on other devices, it opened up but the backups were not really completed.

thanks bro. nice share :good:

Thanks, you save me too much time!!

my adb was working fine for my Note 4. I followed the instructions to upgrade bootloader
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Now, I keep getting device offline when used adb devices command. Do you think, upgrading ADB will solve this? thank you