Database Users

Mac os x Adb problem

I downloaded and installed the latest mac intel sdk 1.6 to link with my new rogers magic which is running 1.5. I unpacked everything and restarted my computer. I also enabled debugging on my Magic 3g. When I plug my Magic in, I open terminal in su (root) and once inside the folder, i try running the "adb devices" command however it doesnt work. I get "bash adb command not found". Any ideas from the mac users on here?
should I install the 1.5 sdk, not that it will make a difference since I cant even run the command in 1.6?

any ideas?

Are you putting ./adb devices or just adb devices? because the ./ is very important

tristyB said:
Are you putting ./adb devices or just adb devices? because the ./ is very important
Click to expand...
Click to collapse
.... I am a moron. thank you. I was to excited!!!

ryrules1 said:
.... I am a moron. thank you. I was to excited!!!
Click to expand...
Click to collapse
It's fine, it happens to all of us!

The other options is to add your <android_sdk>/tools folder to your path. That way, you don't need to cd into the folder and use ./adb...you can just use adb from anywhere in the prompt.
Google around but I believe you need to add a line like this:
export PATH=<android_sdk_location>/tools:$PATH
to your .profile file in your home directory.
where <android_sdk_location> is where you extracted the sdk.

[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

[Q] How can i connect adb drivers and ics 3.1 on xp?

Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,

miskiab said:
Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,
Click to expand...
Click to collapse
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log

Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393

I just it but not solved this problem
asm19 said:
Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393
Click to expand...
Click to collapse
hi, thanks for answered my question. But i just tried:
AndroidDriverForPc
Adb Device for AURORA
Huawei_U8800_ICS_ADB_Driver
usb_dirver4
Universal_Naked_Driver_Beta_0.6.2
and orjinal huawei drivers with hisuite.

How can i did it?
asm19 said:
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log
Click to expand...
Click to collapse
edit// "you have to use the adb drivers for ics" I don't have adb drivers. Just i wanting it.
I think this commands for linux, right? Can i it any linux version?
i using this commands what will happen? ( i want learn)
thanks.

any idea?
Is there no one with a different suggestion?

Please give a try to this solution.

m!xal!s said:
Please give a try to this solution.
Click to expand...
Click to collapse
Yes, its ok, adb driver seen by xp but when i can adb shell;
* deamon not runing. starting it now *
* deamon started successfully *
error: device not found
writing, what can i for it?

strange problem!!
device not found

[Q] rooting on linux

I can't find any good rooting guides for linux. Anyone know where I can find one?

If you are administrator then all you have to do is to type sudo in the terminal window to execute commands as root. Or type sudo su to become root user during that terminal session.

Muikkuman said:
If you are administrator then all you have to do is to type sudo in the terminal window to execute commands as root. Or type sudo su to become root user during that terminal session.
Click to expand...
Click to collapse
I think he means rooting his phone while on linux.

I've rooted my phones (Galaxy Nexus and Nexus 4) on Linux. As far as I know there aren't any rooting guides for Linux users specifically, but the process is essentially the same as on Windows or Mac OS X.
The only difference is that you might come across of permission issues (like ADB not working without "sudo ./adb ..." when in recovery, Fastboot not working without "sudo ./fastboot ...", etc.) which can easily be fixed.
I can totally help you if you want.

alfonzo1955 said:
I think he means rooting his phone while on linux.
Click to expand...
Click to collapse
Jaja, yes.
starscream92 said:
I've rooted my phones (Galaxy Nexus and Nexus 4) on Linux. As far as I know there aren't any rooting guides for Linux users specifically, but the process is essentially the same as on Windows or Mac OS X.
The only difference is that you might come across of permission issues (like ADB not working without "sudo ./adb ..." when in recovery, Fastboot not working without "sudo ./fastboot ...", etc.) which can easily be fixed.
I can totally help you if you want.
Click to expand...
Click to collapse
If you could that'd be awesome.

You should search first... http://forum.xda-developers.com/showthread.php?t=1999065
If you running ubuntu or mint, commands like adb and fastboot are in the repos...just install them, and from terminal give: sudo fastboot (whatever you want) or sudo adb

I got it! I didn't know that all you had to do was sudo for whatever commands while the phone's in the bootloader. I thought I'd have to do something with the dll drivers. http://forum.xda-developers.com/showthread.php?t=2018179 says that you might need to install them, but I wasn't sure if this was a windows only thing.
Thanks a lot man!