Database Info

Ubuntu 8.10 x64 can't find G1

Connect my G1 with my laptop(Ubuntu 8.10 x64)
When I run the adb devices, it only said: List of devices attached
No devices line; It lists one line when I start the emulator program.
And not like the SDK for windows, there is not some folder related to drivers.
Does it support for linux x64? plz help.~

have you activated the debugger in your g1 ?

oh I remember when I was in ubuntu now
you gotta launch adb daemon as root
try this :
adb kill-server && sudo adb devices
and let me know if it worked

dixxa said:
have you activated the debugger in your g1 ?
Click to expand...
Click to collapse
Absolutely, it works fine in Vista x64 with SDK 1.1 r1

I had to do two things to get this to work (although this was on x86) -
1) Build the kernel with the Android drivers enabled. This might not be necessary; I have no idea if they are turned on in the kernels you get from the Ubuntu repository as mine has been custom built for a while, but I'm guessing that they aren't enabled by default because they are in the "staging" area as of 2.6.29.1. So these were in Device Drivers/Staging Drivers/Android.
2) Add a "50-android.rules" file to /etc/udev/rules.d that has this line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
The idVendor is different if you have an ADP phone, I believe; this was the value worked for mine (non-dev). You can do an 'lsusb' after it's been plugged in and see what shows up. Also, try grepping /var/log/messages for "udev" after you plug it into a USB port and see if there are meaningful messages.
- Chris

Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help

noz.geek said:
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
Click to expand...
Click to collapse
copy the 50-android.rules file you created into a file called 51-android.rules. The problem is related to the order in which things are launched and copying this file to the new name will solve your problem.

I should also note that you will have to restart udev Or reboot or logout/in
to restart udev, In terminal type:
Code:
sudo /etc/init.d/udev restart

sudo is necessary~ thx

Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK

npak243 said:
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
Click to expand...
Click to collapse
Code:
$ sudo mv /etc/udev/rules.d/50-android.rules /etc/udev/rules.d/51-android.rules/code]
that should fix it ;)

Thanks,
It can work now!

I have the same problem here. adb used to be able to see my phone when I was using Ubuntu 8.10. After I upgraded to 9.04, it never worked. I tried change the udev rule file from 50-** to 51-** or as haykuro suggested to 51-**/code. I also changed the permission to 777. And I did kill and restart adb-server several times under root, but I still get nothing~~~
Can anyone help?

Android SDK 1.5 trouble in Linux

I am a new to using Linux, I just downloaded the SDK 1.5 and I am having some trouble getting the tools to work properly. For example. If I try to open the emulator it will just sit there and do nothing. I cannot get adb to work either. I set it up / the instructions. Any ideas on what I am missing? Thanks

easiest way to fix the adb problem is to move your adb command that is included in the SDK into your /usr/bin or /bin directory. if you have a problem with either of those then type cd ~/<sdk>/tools followed by ./adb the "./" tells the phone to run the command in the current directory, otherwise you could just type the directory to adb to run it i.e. ~/SDK/tools/adb that's all you need. as far as the emulator i have no idea because i have never gotten it up and running properly

How do I add the ADB command to usr/bin?

You can do as followed:
- Run the Terminal
- cd to your sdk/tools directory
- Run these command:
Code:
#./adb kill-server
#./adb devices
If you see your HTC has been remounted, it's done!

sudo mv ~/sdk/tools/adb /usr/bin/adb

tubaking182 said:
sudo mv ~/sdk/tools/adb /usr/bin/adb
Click to expand...
Click to collapse
Got it thanks for your help! I still can't get the emulator to work. Oh well Thanks again

What version of Linux? Are you using 64 Bit? What is the result of typing
Code:
java -version
You created the AVD, right?
What do you get when you type:
Code:
android list avd

stovenator said:
What version of Linux? Are you using 64 Bit? What is the result of typing
Code:
java -version
Ubuntu version 9.04 & 64 Bit
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
You created the AVD, right?
What do you get when you type:
Code:
android list avd
Click to expand...
Click to collapse
bash: android: command not found

They made a change in 1.5 SDK that you must specifiy the virtual device you want the emulator to run. if you just double click on "emulator", it will print the error to console and exit.
So first cd to the tools directory of the sdk and type android[return]
you will be given the commands that android (the program) will accept. you can also do this for emulator.

Great!! Everything is working well now. Thanks for everyones help!!

How Do I get fastboot working in Ubuntu?

jordanjf86 said:
How Do I get fastboot working in Ubuntu?
Click to expand...
Click to collapse
http://andblogs.net/fastboot/

fastboot is included in the 1.5 sdk, once you get adb working it should start working as well.

billc.cn said:
fastboot is included in the 1.5 sdk, once you get adb working it should start working as well.
Click to expand...
Click to collapse
Actually it doesn't seem to be in the Linux 1.5 SDK; I had to build it. It's in the Windows SDK, though. Kinda weird.

Android SDK 1.5 emulator trouble in windows
hi i m new to xda and to android i m not tech savy
i install sdk 1.5 i try ddms it works good what when i try to lanch emulator nothing happnes and i try by going in command promt im getting this error can any one help me out in this
C:\Documents and Settings\jass>emulator
emulator: ERROR: You did not provide the name of an Android Virtual Device
with the '-avd <name>' option. Read -help-avd for more information.
If you *really* want to *NOT* run an AVD, consider using '-data <file>'
to specify a data partition image file (I hope you know what you're doing).

karan09 said:
hi i m new to xda and to android i m not tech savy
i install sdk 1.5 i try ddms it works good what when i try to lanch emulator nothing happnes and i try by going in command promt im getting this error can any one help me out in this
C:\Documents and Settings\jass>emulator
emulator: ERROR: You did not provide the name of an Android Virtual Device
with the '-avd <name>' option. Read -help-avd for more information.
If you *really* want to *NOT* run an AVD, consider using '-data <file>'
to specify a data partition image file (I hope you know what you're doing).
Click to expand...
Click to collapse
First, this is the wrong thread for such a question. This thread is about SDK issues in Linux, and you're asking about using debugging tools in Windows.
Second, if you say yourself that you are "not tech savvy", then I'm not quite sure why you are wanting to play with the SDK tools. I don't mean this in a derogatory way; I'm just not sure what it is that you're trying to accomplish.
That said, Android dev docs can be found here, and information specifically about the emulator is here.
- Chris

[HOWTO] Guide to running ADB under Fedora 11 (and equivalent distros)

Ok, I have fedora 11 installed on most of my computers, since i love this distro to death. My big thing was trying to get adb to work. This is my guide to get it to work, for now.
First things first. Navigate to /etc/udev/rules.d as root. Create a rules file called 50-android.rules (touch 50-android.rules). NOTE: You are better off looking at the contents and picking a rules number set other than what is listed. Sometimes udev is picky. For the newbies, so if any rules start with '50', then change the number by one or two, like 51 or 52. Paste this into the file:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
Make sure you use ATTRS, not ATTR or SYSFS, since this is a newer updated udev system.
After that, run udevadm control --reload-rules to reload your rules files. Now just run ./adb devices as root to make sure it recognized your HTC dream. I am working on this fix right now so you don't need to be root, keep patient. Now you can adb shell into your device either as root OR normal user, just as long as you start the server as root. This is a permissions problem, and hopefully I can fix this and/or find a fix soon.
I wrote this because i searched high and low through google, and only found a few good parts as far as a fix. Hopefully this helps a few people out there.

Just wondering if this has helped anyone. If not, delete this thread or do whatever with it....

I have adb on my eeepc 900 with f11 I believe this method works too as well. although it says it has been tested with ubuntu, it works pretty well with f11.
http://www.talkandroid.com/android-sdk-install-guide/
Installing The Android SDK
First you will need to download the Android SDK pack .zip archive, once downloaded find a suitable installation location on your machine and extract the zipped files.
Please note: This installation location will be referred to as $SDK_ROOT from now on through this tutorial
Alternatively you can add /tools to your root path which will prevent the need to specify the full path to the tools directory along with enabling you to run Android Debug Bridge (adb) along with other command line tools.
To add /tools:
Linux
1. Edit the ~/.bash_profile or ~/.bashrc files looking for a line that sets the PATH variable.
2. Add the full path location to your $SDK_ROOT/tools location for the PATH variable.
3. If no PATH line exists you can add the line by typing the following:
4. export PATH=${PATH}:<path to your $SDK_ROOT/tools>
Click to expand...
Click to collapse

It helped me, since the creation of the file my OpenSuSE 11.0 recognizes the phone perfectly
Thanks a lot for your hint.

thanks it helped me. ill be looking forward to getting it to work without root

just use sudo instead

Just a heads up for user's using Ubuntu 9.10, this isn't needed. I connected my G1 to it and ran ADB with no adjustments to udev or anything else.
Pretty much it works out of the box.

Here is my version
download the .tgz file from googlecode
http://developer.android.com/sdk/index.html
sudo tar -xzvf android-sdk_r3-linux.tgz
Click to expand...
Click to collapse
Code:
sudo gedit ~/.bash_profile
heres my bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH=$PATH:/android-sdk-linux/tools
Click to expand...
Click to collapse
logout
login
connect android g1 device via usb to pc
open a terminal
Code:
adb devices
if you cant get a device try it with superuser.

Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb

Another option is to edit the /etc/profile and add
PATH=$PATH:/<Path to android-sdk>/tools
This option will allow any user to use the adb tools when logged in or if you
su -
into another user

I wrote a short guide as well for Windows and Ubuntu. Might help others.
Unfortunately, as anyone with a passing acquaintence with ADB knows, the scrolling issue can be a killer. I swear the other day I pressed "up" twice and it composed "rm /sdcard/rootfs.img /sdcard/system.ext2" and executed it. We run Android on our SD's btw.. Was not cool. Instead, I use ADB via telnet and it works beautifully. Here's how:
Code:
adb shell telnetd &
adb forward tcp:9999 tcp:23
Now type this: "telnet localhost 9999"
Enter "root" and hit enter
Finally update PATH: "export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/sbin:/system/bin:/system/xbin:/system/xbin/bb:/data/local/bin"
Okay, so 4 lines to enter and you have a "regular, sane" shell connection to the phone and you can actually scroll through history and text without it jumbling the text and executing random code. Enjoy.

lbcoder said:
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Click to expand...
Click to collapse
that works too as well but i would rather open up a terminal and type
sudo adb devices

sensimila said:
that works too as well but i would rather open up a terminal and type
sudo adb devices
Click to expand...
Click to collapse
WHY would you want to make it *MORE COMPLICATED*??
There is NO NEED for root.
/path/to/adb ...
THATS ALL.

This is kind of funny... i wrote this because i had trouble with it, so i am just sharing my fix...

In case this is interesting to someone:
The fix mentioned in the first post has to be applied to open SuSE x86 and x64 edition to make the G1 work. The external device works without it, but not the adb device.
Thanks again!

Just wanted to come and post that this does work with OpenSUSE 11.2 x86. Did this hoping to get adb to work with my LG Ally and it does. Thanks!

(Still) works for me on 64bit SUSE 11.4.
Before adding this file, I could not access my device with adb, received permissions errors.
Added this file, and I can shell into my device.
Permissions on adb itself was not the problem, it was access to the device when udev found it.
[edit]Actually used the lines from http://developer.android.com/guide/developing/device.html[/edit]

[Program]Bash simpleroot OTA 1.47.651.1 for Linux users - update01 rlsed

This is an adaption of Simpleroot for rooting OTA 1.47.651.1 in bash-script for linux users
In order to use this root you will need to have installed the android SDK on your linux machine, either via your distributions package management system or manually.
The user you are logged in with will need to have access to the adb tool that comes with the android sdk. Usually this means adding the user to the android group after installing the sdk, but specific methods of attaining access may differ by distribution.
- One method of setting up the sdk can be found Here
To begin using the bash simpleroot after installing the sdk and verifying access to adb, navigate to the directory where you extracted the simpleroot files in a terminal (read: console or command prompt if you prefer that terminology) and do an
"sh p1.sh"
to begin step 1 of the process,
then follow the instructions that you will be given as the script runs (it will tell you when to run the next script in the chain, etc).
SPECIAL THANKS to ItsMeCD for being a guinea pig on irc and successfully rooting his evo using bash simpleroot.
UPDATE 24-July-2010, 14:45 (2:30pm): Download replaced due to nasty evil bugs that crept into the original scripts and prevented them from running. if you downloaded before this time/date, please re-download
Simpleroot Bash Edition, by netarchy
Bugfix update: Update 01
- Fix some confusion in script execution feedback during p2.sh that may lead the user to believe the process has failed when it has not
- Clarified output during p4.sh to better reflect how long the user should wait before confirming the attempt to root has failed
Extract the update to the same place you extracted the original download, and overwrite files if prompted.
Simpleroot Bash edition Update-01

Great job! This will make my life so much simpler when more of my coworkers ask me to root their Evos. Good looking out for us lazy Linux vets

jmlott said:
Great job! This will make my life so much simpler when more of my coworkers ask me to root their Evos. Good looking out for us lazy Linux vets
Click to expand...
Click to collapse
Windows has no place on any computer of mine ;D
Be sure to lemme know if you run into any issues. Eventually I'll streamline it to need less interaction, maybe even make a gui for the cli-fearful.

Running it now...re-downloaded and extracting.

Posted a bugfix update to clean up script errors and clarify output.

Worked First Time
Didn't see any success stories yet, so I thought I'd post mine. Downloaded and ran the scripts and got root first time.
Now rockin Froyo courtesy of CyanoGenMod6. (Tried to leave a url to the ROM, but I'm too much of a noob on the forum

damnit ! - linux n00b - i gotta be close - errors on scripts... help ?
[email protected]:~/a/t$ ls
adb ddms hprof-conv p2.sh ra-rec.img
amonra.sh dmtracedump layoutopt p3.sh README.txt
android draw9patch lib p4.sh simpleroot-bash
apkbuilder emulator mksdcard part1 source.properties
cleanup.sh etc1tool mtd-eng.img part2 sqlite3
clockwork.img flash_image NOTICE.txt part3 traceview
clockwork.sh hierarchyviewer p1.sh PC36IMG.zip zipalign
[email protected]:~/a/t$ sh p1.sh
adb not found, exiting.

xda98052 said:
[email protected]:~/a/t$ ls
adb ddms hprof-conv p2.sh ra-rec.img
amonra.sh dmtracedump layoutopt p3.sh README.txt
android draw9patch lib p4.sh simpleroot-bash
apkbuilder emulator mksdcard part1 source.properties
cleanup.sh etc1tool mtd-eng.img part2 sqlite3
clockwork.img flash_image NOTICE.txt part3 traceview
clockwork.sh hierarchyviewer p1.sh PC36IMG.zip zipalign
[email protected]:~/a/t$ sh p1.sh
adb not found, exiting.
Click to expand...
Click to collapse
Putting the sdk tools binaries in the same dir with the scripts isn't going to make them magically find them (you're thinking windows style here), you need to put the android sdk tools in your PATH variable. The wiki referenced in the first post has an example of how to do this.
An example for you:
let's say you extracted the android sdk to /home/foo/androidsdk
and the tools are in /home/foo/androidsdk/tools (this is just for the sake of example mind you)
you would want to edit your .bashrc and add in
export PATH=$PATH:/home/foo/androidsdk/tools
You can then make that kick in by logging out and logging back in.

Just to Clarify...
Can I get root access without having to wipe my phone?

Having a problem
UPDATE: booted into clockwork and flashed Fresh ROM, ROM Manager works fine now. Thanks again for the awesome root method Netarchy, you are my hero!
Hey Netarchy, first want to say thank you for giving us Linux users some simpleroot love. Good job.
I ran all the scripts and everything seemed to go as you said it would. No error messages, all was well, I ran clockwork.sh and my phone booted in to clockwork just fine!
Code:
Pushing ClockWork Recovery
1534 KB/s (2752512 bytes in 1.751s)
Clockwork image pushed!
pushing flash_image
610 KB/s (26172 bytes in 0.041s)
flash_image pushed!
Changing permissions...
Permissions changed...
Moving recovery image...
Recovery moved...
Rebooting...
===============================================================
===============================================================
Recovery Flashed! please run sh cleanup.sh
===============================================================
===============================================================
Yay! So I installed ROM Manager on my phone and then my hopes are dashed. When I try to download roms it says I have to have ClockworkMod Recovery installed, so I tell it to install from ROM Manager, and I get this...
An error occurred while attempting to run privileged commands!
Click to expand...
Click to collapse
Any idea what I might have done wrong? Or should I just start the whole process over again? I noticed in my settings my software number was showing 1.17.651.1 now instead of 1.47.651.1 before I rooted.

netarchy said:
- One method of setting up the sdk can be found ...
Click to expand...
Click to collapse
Not allowed to post links (yet?)
Thanks for this but there's no info at that link just this...
AndroidSDKLinux
From Villain ROM
Jump to:navigation, search
There is currently no text in this page. You can search for this page title in other pages, or search the related logs.
Click to expand...
Click to collapse

ADB 1.0.32 for OTA update!!!

Hey folks!
I'm following this guide. From the command lines on Updating the platform-tools, I get an error "please consider trying to update again without a package filter"
Code:
android.bat update sdk -u -t platform-tools,tools
Downloaded the latest SDK and drivers. after writing down recovery.img, system.img and boot.img, I'm unable to update via sideloading.
Code:
adb sideload update.zip
The recovery screen turns out "You need adb 1.0.32 or newer to sideload to this device." I've checked out the SDK and confirmed the "Android SDK Tools (24.0.2)" and "Android SDK Platform-tools (21)" have been updated, which is possibly the ADB and fastboot etc.Now what more does it require to get ADB updated.
I've already updated the platform tools, sdk tools from the package manager. Regarding the PATH variable, Please shed some light though. I'm no experianced under LINUX or it's distro's nor have much knowledge in CMD terminal either. I've located the (cd) path to where the android.bat is installed for the 1st command line operation below.
Code:
android.bat update sdk -u -t platform-tools,tools
How come the 1st update platform-tools command went out wrong? All command line operations/downloading and writing down under the fastboot menu went out smoothly, except this sideloading.
Thanks.
:angel:

cloutz90 said:
to show the adb version use
Code:
adb version
it should be 1.0.32 or newer (see image attached)
Click to expand...
Click to collapse
I checked with the exact command line also, it's the same 1.0.31! Also the package manager shows out I'm at the latest platform and SDK tools.

Sigh of relief!
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:

CODENEX said:
ISSUE SOLVED FINALLY!
Ah yeah! Many thanks to the ADB Minimal team :good: Updated the ADB version to the directory and it served my good!
The OTA update went like a breeze.
Anyhow, THANK YOU FOR LOOKING INTO THIS THREAD! :angel:
Click to expand...
Click to collapse
Having the same issue. How exactly did you "update the ADB version to the directory"

ADB issue
SantinoInc said:
Having the same issue. How exactly did you "update the ADB version to the directory"
Click to expand...
Click to collapse
about this ADB version issue, i have a different phone, but was facing almost same sort of problem.
I think he might have referred to this thread: http://forum.xda-developers.com/showthread.php?t=2317790;)