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] Rooting my T-Mobile G2 with Ubuntu

First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?

mrfilbert said:
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
Click to expand...
Click to collapse
no need for usb drivers in linux
you have to be sure that you are su on your pc... (i have fedora)
i think ubunto it´s sudo, isn´t it?
and before you can see your device through adb you have to type "./adb kill-server" and then "./adb start-server"
... then "./adb devices" and so on

Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?

mrfilbert said:
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
Click to expand...
Click to collapse
no that happens because you are not root on your pc...
in fedora i have to do the following to see my device:
su (enter)
then enter password
i get this symbol: # = means i´m root on my pc
then i go to my platform-tools directory (cd whatever)
./adb kill-server
./adb start-server
./adb devices ...now you should see your device
then start the rooting procedure, good luck

Use 'sudo su' in ubuntu to get a root prompt.
otherwise you have to set a 51-android.rules file (instructions here http://developer.android.com/guide/developing/device.html)
-Nipqer

Nexus 7 not recognized by ADB in fastboot (Ubuntu 12.04)

So I'm in my platform-tools directory in the terminal, and here is how my commands go
./adb devices
returns List of devices attached
015d18ad5a27fe04 device
so then I go
./adb reboot bootloader
and my Nexus reboots into the bootloader. And then I enter
./adb devices
And there is no device listed. When I type in
./fastboot oem lock
it returns
<waiting for device>
and it hangs here until I control-c out. Am I missing something? I really hope it's not a syntax error
any help would be appreciated. Also, please note that I am in Ubuntu 12.04 on a native installation, so it isn't a driver issue

Silly question, but did you sudo?

thebobp said:
Silly question, but did you sudo?
Click to expand...
Click to collapse
As a matter of fact, I didn't :crying: I had to kill the server and when I did I left su. That's even more humiliating than a syntax error :crying: thanks for the help

Rooting On Macbook Pro

I am getting things set up to root my Nexus 6p using a Macbook Pro. I have Android Studio installed & I see the platform-tools folder like the tutorial says. But my phone isn't showing up as a device on my Macbook nor is the terminal command "adb devices" showing it.
Has anyone successfully rooted their Nexus 6p using a Macbook Pro?
Thanks!!

Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237

lyall29 said:
Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Totally agree! I used this to get a handle on ADB/fastboot and have been good ever since. Which version of OSX are you using, OP? I followed the above guide and use manual command on OSX 10.10.5. I have heard there are some issues on 10.11 though.
Sent from my Nexus 5X using Tapatalk

I used ruby (built in with osx) inside the terminal to install homebrew. Then install android-platform-tools using homebrew. This installs fastboot and adb, AND adds these programs to PATH so you can use adb or fastboot command no matter which folder the terminal has open. Hope this helps!
EDIT:
Link providing steps for how to do this:
http://macappstore.org/android-platform-tools/

Yes I have rooted my 6p using macbook pro. You have to CD to platform-tools and make the command ./adb devices
That was my problem. Adb wasn't even recognized unless I did ./ before the adb command

andrewnelson23 said:
Yes I have rooted my 6p using macbook pro. You have to CD to platform-tools and make the command ./adb devices
That was my problem. Adb wasn't even recognized unless I did ./ before the adb command
Click to expand...
Click to collapse
That means your search path was not set up.
Even executables in ./ not found? Path really messed up.
BTW : I only use a Mac so I've rooted everything from Samsung to LG and now Nexus on my Macs.

lyall29 said:
Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
WOW!!! Thanks!!! I just posted in the when did you root thread that I haven't seen a tutorial on rooting with a mac!!! I did a search and it didn't show up in the results. I figured people assume that if you have a Mac you also have an iPhone! Thanks for posting this tutorial!!!

mikespe said:
WOW!!! Thanks!!! I just posted in the when did you root thread that I haven't seen a tutorial on rooting with a mac!!! I did a search and it didn't show up in the results. I figured people assume that if you have a Mac you also have an iPhone! Thanks for posting this tutorial!!!
Click to expand...
Click to collapse
I don't make that assumption.
I have been using Macs exclusively for 15+ years.
I have never owned an iPhone. I like MacOS because it's got BSD Unix under the hood.
I had a NeXT before that.

Here is the easiest way to install adb/fastboot on a Mac, also installs it correctly in your PATH.
Also if you are running El Capitan, see this.

I have been using Fedora Linux to root my devices and as long as the path is setup you do not need the "./" but once you are booted into fastboot, even with proper path, you need the ./fasboot (Don't ask me why, haven't figured it out). You may also have to execute fastboot as
sudo ./fastboot

dratsablive said:
I have been using Fedora Linux to root my devices and as long as the path is setup you do not need the "./" but once you are booted into fastboot, even with proper path, you need the ./fasboot (Don't ask me why, haven't figured it out). You may also have to execute fastboot as
sudo ./fastboot
Click to expand...
Click to collapse
If you use the link at the top, the ./ isn't required any longer, not sure why.

Everyone thank you so much for all the information. I have been a Windows guy all my life. I bought this macbook about a year ago and I'm still learning. Windows I can go into the registry and tweak almost anything....Mac I fee like a rookie. As I mentioned earlier I think I will use my Surface Pro 3 this weekend to root the phone. This way I won't have to worry about doing anything wrong or get frustrated!

jawmail said:
If you use the link at the top, the ./ isn't required any longer, not sure why.
Click to expand...
Click to collapse
The issue is that I need to use sudo to execute the command fastboot. Since it's sudo it doesn't have the proper path, hence the need to add the ./

How to install ROM, root and backup using LINUX OS?

I'm a daily Linux user and don't have installed Windows on my PC.
So I would like to ask first how to backup my X720 phone into my Linux PC? Then install root and new custom rom using the same OS?
Before I had Samsung phone and was using application called Heimdall in Linux, similar like Odin for Windows.
Is there any similar app for Le Eco or can I use commands in Terminal?

https://www.xda-developers.com/install-adb-windows-macos-linux/
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/

Follow the links above, all you really need is adb. There are some Chinese Windows recovery programs and scripts for certain variants of the Pro3 (like the x722 and the x720) but you probably won't need to use them unless you catastrophically brick the phone somehow. As long as you're following instructions from ROM threads properly, all you'll ever need is adb and the rest you can do through your phone via TWRP or Magisk or whatever.

Well there is one additional hangup...the phone will not appear in "adb devices" at least on Linux Mint/ubuntu...the solution is as follows.
sudo apt-get install android-tools-adb android-tools-fastboot
tar -jxvf lepro3.tar.gz
cp abd_usb.ini /home/<your username>/.android
sudo cp 51-android.rules /etc/udev/rules.d
sudo killall adb
sudo adb devices
Basically you are manually adding the vendor id so adb can find it. Plan on having to use sudo in front of any adb or fastboot commands to avoid possible errors.
It should then find the device and you can follow a tutorial like the one here: https://docs.google.com/document/d/1qFJ7ULjU57XSkm-j8P9vDbnV1JU1YZYQS70StWRlrbo/edit?usp=sharing
I did not create this. It's a copy of the one created by Abel408 on slickdeals but I used it to take my factory phone and install omnirom about 5 days ago on linux.

famewolf said:
Well there is one additional hangup...the phone will not appear in "adb devices" at least on Linux Mint/ubuntu...the solution is as follows.
sudo apt-get install android-tools-adb android-tools-fastboot
tar -jxvf lepro3.tar.gz
cp abd_usb.ini /home/<your username>/.android
sudo cp 51-android.rules /etc/udev/rules.d
sudo killall adb
sudo adb devices
Basically you are manually adding the vendor id so adb can find it. Plan on having to use sudo in front of any adb or fastboot commands to avoid possible errors.
It should then find the device and you can follow a tutorial like the one here: https://docs.google.com/document/d/1qFJ7ULjU57XSkm-j8P9vDbnV1JU1YZYQS70StWRlrbo/edit?usp=sharing
I did not create this. It's a copy of the one created by Abel408 on slickdeals but I used it to take my factory phone and install omnirom about 5 days ago on linux.
Click to expand...
Click to collapse
Hello
I'm new in this community and me too, I have a LeEco Le Pro 3, never flashed, so it has the new updates of EUI 5.9s and all chinese apps.
I'd like to put this ROM
Me too, I'm a linux user, I've Ubuntu 16.04 LTS
Before I never flashed a phone, so I don't know how to do well even if I read a lot of procedures, but all for Win.
How do to the same with my OS?
I'd prefer to follow a complete list of instructions not to make errors and problems to my phone.
I've a LeEco Le Pro 3 (X720) original and never flashed, with 6GB of RAM, and 64GB of memory
Thanks to who wants to help me accurately

Hello,
no one could help me?
Is there no solution for Linux users? How is it possible?

spsturbo said:
Hello,
no one could help me?
Is there no solution for Linux users? How is it possible?
Click to expand...
Click to collapse
In short install ADB&fastboot tools, reboot to bootloader, unlock it via fastboot, flash TWRP, boot into TWRP, do a factory reset, flash your ROM, you're done

BlueFlame4 said:
In short install ADB&fastboot tools, reboot to bootloader, unlock it via fastboot, flash TWRP, boot into TWRP, do a factory reset, flash your ROM, you're done
Click to expand...
Click to collapse
And in more detailed manner?
Could you list the exact commands to type on the terminal?

spsturbo said:
And in more detailed manner?
Could you list the exact commands to type on the terminal?
Click to expand...
Click to collapse
Whoa, no offense but I don't have time for that. Just search for each of these things and you will find an answer. I will also answer specific questions but I don't like unspecific ones like "post the whole process please".

spsturbo said:
And in more detailed manner?
Could you list the exact commands to type on the terminal?
Click to expand...
Click to collapse
Just google it and you will find all that you need.

spsturbo said:
And in more detailed manner?
Could you list the exact commands to type on the terminal?
Click to expand...
Click to collapse
https://ubuntuforums.org/showthread.php?t=2326450

famewolf said:
Well there is one additional hangup...the phone will not appear in "adb devices" at least on Linux Mint/ubuntu...the solution is as follows.
sudo apt-get install android-tools-adb android-tools-fastboot
tar -jxvf lepro3.tar.gz
cp abd_usb.ini /home/<your username>/.android
sudo cp 51-android.rules /etc/udev/rules.d
sudo killall adb
sudo adb devices
Basically you are manually adding the vendor id so adb can find it. Plan on having to use sudo in front of any adb or fastboot commands to avoid possible errors.
It should then find the device and you can follow a tutorial like the one here: https://docs.google.com/document/d/1qFJ7ULjU57XSkm-j8P9vDbnV1JU1YZYQS70StWRlrbo/edit?usp=sharing
I did not create this. It's a copy of the one created by Abel408 on slickdeals but I used it to take my factory phone and install omnirom about 5 days ago on linux.
Click to expand...
Click to collapse
Thank you for your great help! I tried this but it still didn't recognized the device if you use the command "adb devices", instead you need to use "fastboot devices" and add to your file USB id for fastboot.
First you need to find your USB id number by running phone in fastboot mode and use command "lsusb" in terminal. Here are instructions: https://android.stackexchange.com/questions/144966/how-do-i-get-my-device-detected-by-adb-on-linux
Then put those number into your two files:
Put in "adb_usb.ini" your first ID number in my case
Code:
0x18d1
(Don't root directory /home/USERNAME/.android)
for opening file 51-android.rules in /etc/udev/rules.d you need to use root and put this inside:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", MODE="0666", GROUP="plugdev", SYMLINK+="android"
In the end restart the udev service in terminal "service udev restart" and restart the ADB server: adb kill-server && adb start-server. Disconnect and reconnect the device again.

For recovery used this tutorial: https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
I was unable to get info from
Code:
fastboot oem device info
, but manage to unlock the bootloader:
Code:
fastboot oem unlock-go
and successfully installed Lineage 15.1 OS.