Database Users

Some help with Eclipse and ADB in Linux

Hey, did a search but couldnt find a solution. I'm having problems getting my device to pull up in adb remount on Ubuntu. When I try remount it says no command 'adb' found sometimes or permission denied when it does work, I have root and USB debugging enabled on the devices (a Nexus One and G1). When I try adb devices I just get ?????????????? unknown.
Also, and I don't know if it's related, but in Eclipse, I can't get the SDK location loaded, I have the directory right, but when I hit Apply or OK nothing happens, it just doesnt load. So if I try to start a project I have no Build Targets to select from.
Any help would be appreciated. I have everything running fine in Windows but I'm fairly new to Linux I haven't used it in years. I'm running Ubuntu distro if that matters. Thanks.

i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated

Hello,
The problem with linux having trouble with adb probably lies with a permission issue try adb kill-server && sudo start-server.
The other issue is most likely because you did not download any targets yet. goto windows in eclipse and select android sdk and adv, then at available packages or something like that download your target

i can't even get that far. i switch to my androidSDK/tools and then "adb devices" all i get is 'no command adb found'

I did the first couple times too, then I went to command and did:
su
<enter password>
cd
export PATH=${PATH}:<your_sdk_dir>/tools
then when I adb remount or adb devices it gives me the unknown device thing
but I think the next secret is here
http://forum.xda-developers.com/showthread.php?t=613217
in like the 3rd post. However I think the export PATH is a temp fix because the ~/.bashrc needs to be modified with the path settings and I have no idea how to do that. I just get lots of permission errors or file not found for everything I try, even with root. I'm just using Eclipse in Windows for now, and hopefully someone can help us out cause I'd like to work on roms but I guess I need to brush my Linux up first.

http://forum.xda-developers.com/showthread.php?p=5377103
i found some help elsewhere on the net, and posted it up at the end of this thread. they were having similar issues with the dream, apparently.
i also found this
that link there will probably get you hooked up

adb devices now has a readout!
and, you're right about adding the export PATH=${PATH}:<your_sdk_dir>/tools to
~/.bashrc
i think this command will do it. run in terminal
gksudo gedit ~/.bashrc
i just made a comment line that says
# android sdk export path
and another line underneath it that says
export PATH=${PATH}:/home/timmyd/androidSDK/tools
because that's where i have the extracted sdk
all good, i think. now, let's see what's going on ...
oh yeah, don't forget to enable usb debugging on the device itself.
settings>applications>development
allow usb debugging

screeny works at least
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Cool, I'll try that out tomorrow.

timothydonohue said:
i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated
Click to expand...
Click to collapse
Hi all!!!!
I have a problem with my HTC Tattoo, can't connect the tatto with adb in ubuntu and eclipse Helios.
/android-sdk-linux_86/platform-tools$ ./adb devices
List of devices attached
???????????? no permissions
Thank you very much.

Hi, I have tha same problem with ????? and can't connect to eclipse my galaxy, so the solution is just use the instructions from the h**p://developer.android.com/guide/developing/device.html
I solve this problem with
1. Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
The USB Vendor IDs foreach manufacturer
Manufacturer USB Vendor ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
Click to expand...
Click to collapse
Hope to help you!

[Tutorial]How To -ADB- Logcat & Basic [NEW OR NOOB]

Well this my first own post on General Section
I am sharing how to use the (ADB)
which seem many of us should have some basic on it
(FASTBOOT) will be added later on.
-SIMPLE & EASY-
Is a proper way to tell what wrong's and bug you encountered by a log
Requirement :
Click to expand...
Click to collapse
-Adb Driver for Xperia X8 or This Universal_Naked_Driver
-Adb files (Repacked for you)
-Android Version 1.6-4.1.1
Click to expand...
Click to collapse
Set Up
Click to expand...
Click to collapse
Install the Driver For Adb for your device (Example :X8)
Unpack the Adb Files To A Folder (Named Whatever you like Example: Adb) on local disk C: (Recommend)
Turn on USB debugging on your phone: Settings>Applications>Development>USB Debugging
Go to Start Menu and Search for CMD (Command Promt) (Run as adminstrator)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Prompt CMD with the location you extracted the ADB Files (Mine at C:/adb)
Therefore key in this
Code:
cd c:/adb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check Connected Device & Enable the Adb Server
Code:
adb devices
Wait for few seconds till the server is up and if you connection is working
Should show that the device name is there
If connection is offline should check whether build.prop has this line :
Code:
persist.sys.usb.config=mass_storage,adb
Add this line to build.prop if you need to do so
ADB Logcat
When able to have adb connection between device then you
can now do a pretty simple logcat
Code:
adb logcat > logcatfilename.txt
Replace "logcatfilename" with anything you like and shall log all over the text file
Can then stop logging just pressing Ctrl+C
Enable Access to System
If Encountered that your system not mounted
Code:
adb remount
If some still keeping error then need to boot cwm to adb
ADB Shell
Adb Shell Is A Little Advance So No Really Gonna Cover Up Here
Prompted by
Code:
adb shell
Checking Memory/Swap Progress
Code:
free
You can remove app/files by
Code:
rm -r /filelocation/filename.format
Replace " /filelocation/filename.format" with anything you want to remove such as latimime.apk so you replace with /system/app/latimime.apk
Adb Pull
Now You Should Know To Command using CMD
To Pull
Code:
adb pull /system/app/browser.apk
Replace "l/system/app/browser.apk" with location and file name you want to pull
Adb Push
Now You Should Know To Command using CMD
To Pull
Code:
adb push browser.apk /system/app
Replace " browser.apk /system/app" with file name(On the same folder of the adb files) & location you want to push that file into.
Adb Install
Should be same as pushing method but normally to data folder
Code:
adb install angrybird.apk /data/app
Replace "angrybird.apk /data/app" with file name(On the same folder of the adb files) & location you want to install into
Final :
I hope this Tutorial Is Clear Enough For Other's member which want to
learn adb.You can use this tutorial & i know there many more better adb tutorial
but i am just showing basic knowledge logcat and adb command that can easier
both developers and user.Any Comment & Suggestion can reply below.
I will fix/add if needed.Sorry for bad english & grammar
Credits :
Dev Whom Teached Me Basic Adb
1wayjonny For Universal Naked Driver

pswd
What password for ADB archive?

nikmaletz55 said:
What password for ADB archive?
Click to expand...
Click to collapse
steriod << Password Sorry for missed out
Fastboot tutorial when there's free time :cyclops:

I can't download the GingerLewa.

@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?

fastboot...i think we dont have fastboot

sgt. meow said:
@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?
Click to expand...
Click to collapse
fotak-x said:
fastboot...i think we dont have fastboot
Click to expand...
Click to collapse
i make this for adb for X8 & Other phone as well
i know there no fastboot but maybe usable for otheer phoness

Password Trouble for Mac Users trying to root device using Command Terminal

Ok I was on a break at work today and read a post about someone unable to login to their command terminal password. I tried searching for the post but I could not find it. Anyway if you see this or anyone else who has encountered this problem, maybe this will help.
Let's begin, if you enter the command "su" followed by a command all on one line...
i.e. su ./adb
you will be prompted to enter your password however, once you press enter your password you will get a return message "su: Sorry".
I kept doing this until I realized for whatever reason mac wants you to first type the command "su" then enter your password. Once you do that,
your username will change to something like "sh-(some numbers here,some numbers there) # " After you see the new username you can then enter a command that requires superuser access. The command I used above doesn't but just for sake of example. Also make sure each program you use in SDK like adb or su start with ./ like the example above. Windows and I believe linux do not require this. Hope this helps anyone that has been receiving that dreadful message "So sorry" I mean "su: Sorry".

How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version
rootedkfirefan said:
Ok I was on a break at work today and read a post about someone unable to login to their command terminal password. I tried searching for the post but I could not find it. Anyway if you see this or anyone else who has encountered this problem, maybe this will help.
Let's begin, if you enter the command "su" followed by a command all on one line...
i.e. su ./adb
you will be prompted to enter your password however, once you press enter your password you will get a return message "su: Sorry".
I kept doing this until I realized for whatever reason mac wants you to first type the command "su" then enter your password. Once you do that,
your username will change to something like "sh-(some numbers here,some numbers there) # " After you see the new username you can then enter a command that requires superuser access. The command I used above doesn't but just for sake of example. Also make sure each program you use in SDK like adb or su start with ./ like the example above. Windows and I believe linux do not require this. Hope this helps anyone that has been receiving that dreadful message "So sorry" I mean "su: Sorry".
Click to expand...
Click to collapse
rootedkfirefan,
Thank you for taking the time to post this comment, this made us clarify our Root tutorial:
How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nexus 4 Not Recognized by ADB in Mac OS X

Hi Folks,
I am running Mac OS X 10.8.2 and I have ran into the following issues. I am trying to root a friend's Nexus 4 that's on 4.2.2, unlocked bootloader and USB debugging enabled/on.
I can easily root this on my Windows desktop but I thought I'd try out the Mac. Do note that I am not getting the "Allow USB Debugging" message that pops up on the phone when you connect it to a computer normally and you select Allow for the respective RSA key. The one that shows up after 4.2.2 is updated from 4.2.1.
I am not getting the above prompt when hooking up the phone to my Mac. *PS I removed the name of my MBP pro and the user name.
Okay so here are the two issues/scenarios:
1) I downloaded the latest ADB and Fastboot Mac OS X 64 bit files from the ADB dev tools website, etc. The files are "adb" and "fastboot"
When I type "./adb devices" since the "./" command is for Mac on the terminal, I get the following message and it does not show up any device listed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then when I type "./adb reboot-bootloader", I get the following:
__________________________________________________________________________________________________________
2) When I use an older adb and fastboot files from last year: "./adb_Mac" , "./fastboot_Mac" and "ADB-Install-Mac.sh", I get the following:
When I type in the adb devices command and the adb reboot-bootloader command:
The serial # shows up this time (Again I have crossed out half of it lol)
When typing in the reboot-bootloader command:
Now to my knowledge, I know that I am getting the device offline mode based on using the old ADB and Fastboot files. So the way to fix it, is to download the updated files but it doesn't result in anything at all.
With the updated ADB and fastboot files, and by booting into fastboot mode manually and then typing in ".fastboot devices", I get the Error Could Not Get Pipe Properties error in a loop.
Would appreciate the help folks!
T.I.A

Try this command
adb kill server
adb start server

scream4cheese said:
Try this command
adb kill server
adb start server
Click to expand...
Click to collapse
Beauty! I didn't know that it has to be done for the same in OS X. Query, does this have to be done every time or?

[TOOL][LINUX] Ezy-Adb - Shell script for the quick install and use of adb on Linux

I made this tool to make adb commands quicker and easier to carry out, as I use adb a fair bit. It's similar to this one but I wanted to include some different functions and put more focus on the hassle free installation of adb on various Linux distributions.
It's a simple script that has the most useful adb commands in a menu format. I also added an adb installation menu which automatically detects what system you have and installs the correct package and it's dependencies. Not every system is supported yet but I'll add more in time.
Code:
[I]I am not responsible for any damages caused by your use of this tool.
Please do some research if you are unsure of anything.[/I]
Features:
Installs adb and configures udev rules.
supports ubuntu, debian, mint, suse, redhat, fedora, centos, elementaryOS, Mageia
Adb over network
Manages files into organised directories
Reboot menu
Pull, push, sideload, shell
Logcats and system dumps
Install and uninstall apps
Unlock bootloaders
Remotely take screenshots and create screen recordings
Full adb backup and restore
More to come
Download Link
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
Extract file anywhere in your home directory
cd to the same directory as ezy-adb.sh
Open a terminal and change permissions with this command:
Code:
$ chmod 755 ezy-adb.sh
Run the script with:
Code:
$ ./ezy-adb.sh
Thanks to @raziel23x. I learned a lot from studying his apktool script.
Enjoy

Changelog
28/09/15
Initial release
29/09/15
Added diagnostic tools sub menu with dumpsys fuctions
merged log and log dump into diagnostic tools
30/09/15
Added option adb over network
Added option uninstall package
04/10/15
Merged reboot functions into a sub menu
10/10/15
v1.3
Script now scans for a connected device before executing commands
Date in (y,m,d,H,M,S) added to screenshot name
y, H,M,S added to date on screen recording name
Bug fixes
Minor ui tweaks
25/11/15
v1.4
Install adb now supports elementaryOS and mageia
Bug fixes
23/12/15
v1.4.1
Fixed derp on adb install

Art Vanderlay said:
I made this tool to make adb commands quicker and easier to carry out, as I use adb a fair bit. It's similar to this one but I wanted to include some different functions and put more focus on the hassle free installation of adb on various Linux distros.
It's a simple script that has the most useful commands in a menu format. I also added an adb installation command which automatically detects what system you have and installs the correct package and it's dependencies. Not every system is supported yet so i'll add more based on feedback.
Features:
Installs adb and configures udev rules.
supports ubuntu, debian, mint, suse, redhat, fedora, centos
Manages files into organised directories
Reboot menu
Pull, push, sideload, shell
Logcats and dump files
Install apk's
Unlock bootloaders
Remotely take screenshots and create screen recordings
Full adb backup and restore
More to come
Instructions:
Extract file anywhere in your home directory
cd to the same directory as ezy-adb.sh
Open a terminal and change permissions with this command:
Code:
$ chmod 755 ezy-adb.sh
Run the script with:
Code:
$ ./ezy-adb.sh
Download Link
ezy-adb.sh.tar.gz
Thanks to @raziel23x. I learned a lot from studying his script.
Enjoy
Click to expand...
Click to collapse
I've always wanted an easy way to install adb and config udev rules on Ubuntu but i just couldn't so i had to switch to BBQLinux. But now i don't have to :laugh: Thank you bro.

kirito9 said:
I've always wanted an easy way to install adb and config udev rules on Ubuntu but i just couldn't so i had to switch to BBQLinux. But now i don't have to :laugh: Thank you bro.
Click to expand...
Click to collapse
No worries Glad to help.

Nice work m8

Thanks buddy :good:

good job man
in this way it will not be necessary to rename screenshots
adb shell screencap -p | perl -pe 's/\x0D\x0A/\x0A/g' > ~/EZY_ADB/ScreenShots/$(date '+%Y%m%d%H%M%S').png
thanks

asmanao said:
good job man
in this way it will not be necessary to rename screenshots
adb shell screencap -p | perl -pe 's/\x0D\x0A/\x0A/g' > ~/EZY_ADB/ScreenShots/$(date '+%Y%m%d%H%M%S').png
thanks
Click to expand...
Click to collapse
Cheers. That'll make things easier

nice job man, thannks! Your tool makes my nerding easier :laugh:

Thanks, bro, It's Really Helpful