Database Users

Where to find an Ubuntu guide to root and remove stock apps on the Hero?

If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.

killabee44 said:
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
Click to expand...
Click to collapse
Wouldnt the Mac version work since they are both *nix?

I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app

Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....

romeosidvicious,
Thanks for all your hard work. I and others really appreciate it.

Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Yep, that is something I had to do in windows XP as well. It will help many others as well. Thanks.

Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Great, now my Ubuntu Jaunty machine won't detect the phone. I did the above but it still won't work. Im gonna reboot and retry...
Edit:
Nope, no love for my Ubuntu. It's not seeing the Hero. I will have to research this one.. If anyone has suggestions, please chime in.

Ok, found a solution:
http://forum.xda-developers.com/showthread.php?t=537508
----------------------------------------------------------------
Here is the part that solved it for me:
Setting up UDEV to recognize HTC Device -
1. Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
2. Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. Click save and close.
4. To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
---------------------------------------------------------------------
Thanks to Wddglr for all the useful info. It looks like I will be using other things he posted about. Hopefully that info will help someone else.

Just curious, which version of Ubuntu are you running? I didn't have to make any UDEV changes in Jaunty.

romeosidvicious said:
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
Click to expand...
Click to collapse
I want to follow through with this...
I was following this
http://www.youtube.com/watch?v=ArMO5IHS2eI
until the step came to plug it in and then he suggested typing "adb devices" which told me this.
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?

Onompoly2 said:
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Click to expand...
Click to collapse
Try:
sudo ./adb devices
From the same directory. Or, you can specify the full path:
sudo ~/android-sdk-linux/tools/adb devices
To answer your other questions, it won't work if it says the command is not found.

Okay
It worked but I must have turned into an idiot when i decided my operating system was good enough.
This isn't working, and I am not even upgraded to the operating system the tutorial is written for...
194 updates due... running 8.04 with a bunch of double half installed broken applications.. maybe I should reformat.
I'll let you guys know how things go which ever way it goes.

back again. fresh 9.10 install fully updated.
Following this
http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I get this far
[email protected]:~# sudo su
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools# ./adb push ../asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:~/android-sdk-linux/tools# ./adb shell chmod 0755 /data/local/asroot2
[email protected]:~/android-sdk-linux/tools# /data/local/asroot2 /system/bin/sh
bash: /data/local/asroot2: No such file or directory
[email protected]:~/android-sdk-linux/tools# ./adb shell /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/559/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It seems as though after it says "SUCCESS" that my terminal just stops responding to code...
Tried reading the link to where he made the tutorial from, but its a mixture of ubuntu and windows with 30 pages of posts.
Any thoughts/help?
Thanks
[Continuing]
So just pretending that everything is going as planned I reboot the phone and it actually turns my computer off as well..
So I continue with the steps.
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools# ./adb push ../recovery-RA-heroc-v1.2.3.img /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
1199 KB/s (3352576 bytes in 2.730s)
[email protected]:~/android-sdk-linux/tools# ./adb shell
$ su
su: permission denied
Click to expand...
Click to collapse
But Get permission denied.
I'm going to go ahead and start over but skip the first line that i input that said SUCCESS and stopped the terminal.
(really don't know what i'm doing but I think I need to get these two lines in
cat sh > su
chmod 4755 su)
EDIT: on second thought perhaps this has something to do with me being logged in as root on my computer from the get go, i'll try that.
A dummy and his cell phone perhaps soon part.

# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.

buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
I didn't, although i did try that as well
after I would do the mount commands i would no longer get a $ or a # sign, it was just a bunch of nothingness...
I ended up booting up my girlfriends vista and then spent quite a while figuring out how to get the driver for adb, I had to follow two different windows guides for rooting for some reason as well... so if that says anything.. just imagine how long it took me to realize how to get the driver hahah

buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
no, I'm having the same problem. After the "mount" command it gives me nothing.
Edit: doing this in karmic

Odd. I've had no problems following the generic procedure from theunlockr on ubuntu. My only suggestion would be to turn
Code:
./adb shell /data/local/asroot2 /system/bin/sh
into
Code:
./adb shell
/data/local/asroot2 /system/bin/sh
I'm not sure why it should make a difference, but on my computer "./adb shell <command>" exits the shell when it finishes. From what you've pasted, it doesn't look like that's happening to you, but that's my only guess right now.
If you run "./adb devices" do you see your serial number?
And out of curiosity, why are you running as root on your computer? (sudo su) Have you tried just starting the adb server as root, and running the rest of the commands normally? Does this work?
Code:
./adb kill-server
sudo ./adb start-server
./adb devices

ubuntu abd

What exactly do I need to use adb in ubuntu 10.4
I cannot get anything to work and I'm not too familiar with linux.
I have the sdk downloaded and my terminal opened up to my tools directory, but I literally cannot figure out what I'm doing, no commands work and I can't even find my device (adb devices)
I have exclusively used windows for adb on my previous two phones, but I'm using ubuntu more and more so I would like to be able to use adb in it.

Easy.
cd /path/to/sdk/tools
./adb

ADB doesn't recognize my incredible in 10.4 when I do ./adb devices it is blank.

I've tried with the phone set to charge only and to disk drive.
I've tried following this:
a couple of topics concerning a rules file in /etc/udev/rules.d
I greated a 51-android.rules file and it looks like this now:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0ff9", MODE="0600", OWNER="mbambic"
I've restarted udev a few times and killed the adb server and done ./adb devices to restart it, no luck.

Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.

x.v_ said:
Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.
Click to expand...
Click to collapse
yes, I've used adb numerous times on windows

http://developer.android.com/guide/developing/device.html
I'm no expert, but this is what I followed and my phone shows up in adb devices.

OK, that was my bad with debugging not on.
Now I'm getting the following:
#./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
I've tried with and without the rules file I created in /etc/udev/rules.d called 51-android.ruleswith the following entries that has been chmod a+rx
version 1
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
or version 2
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0c9e", MODE="0600", OWNER="myusername"
or version 3
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
based on this info:
$ lsusb
Bus 001 Device 022: ID 0bb4:0c9e High Tech Computer Corp.

Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again

I keep getting no command 'adb' found when I try to type any command

I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
Assuming you downloaded the sdk pack, your problem is that adb isn't in your path. Take a look at h t t p://developer.android.com/sdk/installing.html. To just temporarily add it, at the shell prompt enter:
Code:
export PATH=${PATH}:<your_sdk_dir>/tools
Also, you may have permission problems when running adb. The easiest way around this is to run adb as root, i.e.: sudo adb (but you'll also have to add adb to root's path then).

mtxpert said:
Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again
Click to expand...
Click to collapse
Ok, so you used both lines in your 51-android.rules file? Interesting, so you're making the driver specific to the DI? I've been operating with just the first line, which allows to use the DI and the G1, but then again, I've also been unsuccessful at rooting
br125 said:
I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
In Linux Mint 9 x64 Isadora (much the same as Ubuntu 10.04 Lucid Lynx), I added the path command to my bashrc file in ~/user. Not sure how to make it global (prob would go somewhere in the mysterious&powerful /etc), but I'm the only user on my system, so for my purposes that doesn't matter

(how to) adb for noobs, by a noob

This instructional piece is brought to you by a complete noob. Please be aware that this is simply telling how I got ADB to work on LinuxMint 10 Julia. Some of the steps may be unnecessary but since I am a noob, I took bits and pieces of info and advice to finally accomplish my mission. The main reason I am writing this is because a lot of the tutorials I found are not written for people new to Linux like myself and I found myself confused by simple instructions because I was unfamiliar with some basic terminal commands.
The first thing I did is watch this video on youtube.com. The instructions I am about to give for installing the SDK comes from here.
http://www.youtube.com/watch?v=t8UREMU-wSU
This video walked me through step by step how to install the Android SDK in Ubuntu. Since LinuxMint is a derivative of Ubuntu, it worked perfectly.
The first thing to do is go to this link and download the SDK for Linux.
http://developer.android.com/sdk/index.html
Then move the file to your home folder. Open a terminal and first “cd” to your download folder. Then move the file as follows: ( please be aware that anywhere you see “tombepa”, replace it with your username)
[email protected] ~ $ cd Downloads
[email protected] ~/Downloads $ mv android-sdk-linux_x86.tgz /home/tombepa
After you have moved it, you must unzip it. This is done with the “tar” command. First you must be in your home folder within the terminal because that is where the file is. After you moved the file, your terminal will still be in the Downloads folder and look something like this:
[email protected] ~/Downloads $
Simply type “cd” without the quotes and press enter to return to the home folder:
[email protected] ~/Downloads $ cd
[email protected] ~ $
Then type in the “tar” command and press enter to unzip the file:
[email protected] ~ $ tar xvf android-sdk-linux_x86.tgz
You will then see a lot of lines of text as it unzips. This will create a folder within your Home folder named “android-sdk-linux_x86” and it will contain all the contents it needs for now. It is then safe to remove the android-sdk-linux_x86.tgz file itself from the Home folder. If it is the only .tgz file in the folder then you can type this and press enter. It will remove all .tgz files from the Home folder.
[email protected] ~ $ rm *.tgz
Now it is time to start the SDK and download the packages for Android Development. Now I am not sure if this is needed just to get ADB to work, but once again, I am a noob and was just going by the instructions. In the terminal, you must enter the newly created folder by typing:
[email protected] ~ $ cd android-sdk-linux_x86/
Now that you are in the folder, type this to start the SDK:
[email protected] ~/android-sdk-linux_x86 $ tools/android
A fews lines of text will come up and then after about 5 seconds the SDK graphical interface will open.
This can be seen in the video. On he left side, click the option that says “Available Packages.” Then click “Android Repository” in the middle of the screen. Once you have clicked that, it will automatically select all packages. I left it that way and clicked “Install Selected.” This took about 15 minutes to complete. Once again, probably overkill to install everything, but whatever.
From there I was graced with a link from CondemnedSoul to set up ADB. The link was:
http://wiki.cyanogenmod.com/index.ph...he_Android_SDK
This wasn't exactly the right page I was looking for, but in bold print, it said for ADB go here:
http://wiki.cyanogenmod.com/index.php?title=ADB
(I left the first link in because it gave good info as well on installing the SDK. So thanks CondemnedSoul on pointing me in the right direction!)
It instructed me to download a file linux_adb_fastboot.zip and extract it to ~/bin. After learning how to do that, I typed:
[email protected] ~/Downloads $ unzip linux_adb_fastboot.zip -d ~/bin
What does it do? I don't know, just following orders.
Then it said I needed to set up udev. This apparently gives me and you the permission to use adb on the android device. There has to be rules written and permission given that the computer and the phone recognizes. The first thing to do is create a file called “51-android.rules” in this directory: /etc/udev/rules.d/
Since I can't remember which step actually worked to create the file. Here is the link I was using. I used them all because I did not really know what I was doing but it worked. If anyone can be more specific on how to create it, please enlighten me and I will amend this and give you credit of course.
http://forum.androidcentral.com/linux/57132-how-set-up-udev-rules-ubuntu-10-10-a.html
After it was created, I had to put all the rules in place. After using the instructions on setting up udev from Cyanogen, I came up with these rules. I put them in the file I created by using Nautilus to go to the file, right click on it, then select “Open as Administrator.” I do not know how to do it from the terminal, sorry.
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0c98"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0ff9"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", OWNER="tombepa" GROUP="tombepa"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0c98"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0ff9"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", OWNER="tombepa" GROUP="tombepa"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", USER="tombepa"
(Once again, wherever you see “tombepa”, replace it with your username.)
Click save, then exit all programs and reboot your computer.
Plug the phone in and open a terminal. Navigate to the tools folder inside the android-sdk-linux_x86 folder by typing:
[email protected] ~ $ cd android-sdk-linux_x86/
[email protected] ~/android-sdk-linux_x86 $ cd tools
[email protected] ~/android-sdk-linux_x86/tools $
Then to test to see if it is working, type:
[email protected] ~/android-sdk-linux_x86/tools $ adb devices
If it says;
List of devices attached
HTXXXXXXXXXX device
And the X's are actually numbers, then there you have it! ADB is working.
From there I was able to push my very first apk straight to my phone. With some help from Busphan, I was directed to save the apk I wanted to the “tools” folder, then type:
[email protected] ~/android-sdk-linux_x86/tools $ adb push WHATEVER.apk /system/app
The first several tries it did not work. I then read some more and one website suggested to type:
adb kill-server
adb start-server
adb devices
adb remount
adb push WHATEVER.apk /system/app
I knew it had worked this time because after the last line, a line of text came up telling me how large the file was that was moved. Then I rebooted the phone by typing:
adb reboot
And there it was. Thank you one again to Tazzpatriot, CondemnedSoul, all the devs out there that put this stuff on the internet and youtube for us to learn, and especially Busphan for seeing me through the last steps.
Once again, if you guys see somewhere for me to be more clear about something, tell me what to fix and I will amend this post and give you credit.

Awesome job man, I will definitely check this out, as I'm in the process of replacing ubuntu with mint 10 to try it out. This will come in handy to set up sdk and adb. Thanks for posting this.

Thank you, I'll add the thanks and check it out when I get home
Sent from my phone, duh

Just finished installing Mint 10. I will post again after I run through the sdk advanced process.
Sent from my Ginger Tazz using XDA App

Busphan said:
Just finished installing Mint 10. I will post again after I run through the sdk advanced process.
Sent from my Ginger Tazz using XDA App
Click to expand...
Click to collapse
When you get to the part about creating the File in udev for rules, if you can help me polish it up a bit, I am sure others would appreciate it.
Sent from my Droid using XDA Premium App

tombepa said:
When you get to the part about creating the File in udev for rules, if you can help me polish it up a bit, I am sure others would appreciate it.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
Well, all went well, except we I got to the tools/android command. I kept type cd tools/android, lol. As for the udev portion that is beyond me, but I just followed the commands in the link and it worked. Although, I didn't do the extra stuff you said with nautilus. I wish I had some more input to "polish up" the udev portion but if folks follow the link it will be fine. So my thoughts are you wrote very good instructions to get adb working on Mint or Ubuntu. Again great job. Now all I have to do is go back in and set up eclipse.

Just a quick tip, most of the time when you are typing on a command line, such as the cd command, you can let the shell auto-complete the line by pressing tab. For example, when the active directory is your home, you can start typing cd andr and then press the tab key and it may/should automatically fill in the rest for you (cd android-sdk-linux_x86/.)

doogald said:
Just a quick tip, most of the time when you are typing on a command line, such as the cd command, you can let the shell auto-complete the line by pressing tab. For example, when the active directory is your home, you can start typing cd andr and then press the tab key and it may/should automatically fill in the rest for you (cd android-sdk-linux_x86/.)
Click to expand...
Click to collapse
Thanx for the tip. Tgat does make it go faster and have less mistakes
Sent from my Droid using XDA Premium App

Thanks for the guide, i got it working, once i remembered it was abd instead of adb lol... i'm a noob still

[Q] Setting up ADB on nook with Ubuntu

Hey everyone, I'm a big newb when it comes to Ubuntu. I got into it because I wanted an OS that was as open as CM7, and so far it's great! I was trying to install ADB on my computer and I was using the link http://forum.xda-developers.com/showthread.php?t=921169. I got JDK installed, and sdk, its about step 4 that I get lost. In terminal when I put in $ ./adb devices it doesn't list any devices. I might be wrong, but I think it needs to recognize my nook as a adb device before I can do anything else. Am I missing a step? Any help would be great!

actorman46 said:
Hey everyone, I'm a big newb when it comes to Ubuntu. I got into it because I wanted an OS that was as open as CM7, and so far it's great! I was trying to install ADB on my computer and I was using the link http://forum.xda-developers.com/showthread.php?t=921169. I got JDK installed, and sdk, its about step 4 that I get lost. In terminal when I put in $ ./adb devices it doesn't list any devices. I might be wrong, but I think it needs to recognize my nook as a adb device before I can do anything else. Am I missing a step? Any help would be great!
Click to expand...
Click to collapse
Follow the steps from Nookdevs.com here http://nookdevs.com/NookColor_USB_ADB
In your case, since you have everything setup. Make note specifically to run this command from the link posted above:
Ensure that your rooted NOOKcolor is plugged in.
Run the following command in terminal:
Code:
mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb devices
If you get output that looks like the following you have succeeded:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[YOUR NOOKCOLOR SN] device
-Racks

racks11479 said:
Follow the steps from Nookdevs.com here http://nookdevs.com/NookColor_USB_ADB
Click to expand...
Click to collapse
okay on step 4 it says to edit your .bash_profile, by putting the command in terminal
nano ~/.bashrc
then append these lines at the end and save the file.
export PATH=${PATH}:<your_sdk_dir>/platform-tools
I'm not sure what it's asking me to do. After putting in nano ~/.bashrc do I just scroll to the bottom and add that line? And if that's it, how do I save it?
Told you I new! But thanks for showing me the right link.
Oh, that command you told me to pay attention to doesn't work for me but when I type in
$ cd ~/android-sdk-linux_x86/platform-tools
[email protected]:~/android-sdk-linux_x86/platform-tools$ ./adb devices
it now lists my device with permission, the same way that command was supposed to.
I just need help setting my path in bashrc!

actorman46 said:
okay on step 4 it says to edit your .bash_profile, by putting the command in terminal
nano ~/.bashrc
then append these lines at the end and save the file.
export PATH=${PATH}:<your_sdk_dir>/platform-tools
I'm not sure what it's asking me to do. After putting in nano ~/.bashrc do I just scroll to the bottom and add that line? And if that's it, how do I save it?
Told you I new! But thanks for showing me the right link.
Oh, that command you told me to pay attention to doesn't work for me but when I type in
$ cd ~/android-sdk-linux_x86/platform-tools
[email protected]:~/android-sdk-linux_x86/platform-tools$ ./adb devices
it now lists my device with permission, the same way that command was supposed to.
I just need help setting my path in bashrc!
Click to expand...
Click to collapse
1. Yes, just scroll to the bottom and add 'export PATH=${PATH}:~/android-sdk-linux_x86/platform-tools/platform-tools' to the file.
2. Once you add the path, to save and exit. Press 'Control' and 'X'. It will give you an option to save changes. Type in "Y" and then press "Enter"
3. After you save the file you have to run:
Code:
$ source ~/.bashrc
That should now set the correct path to your SDK tools. You might have to restart terminal for it to take effect.
-Racks

Enable ADB under Ubuntu/Linux

Alright so it turns out making ADB work for the Kindle Fire under Ubuntu is just a touch more difficult than in Windows.
Thanks to Gbhil (@ AndroidCentral) for the write up on windows it was a great jumping off point to try to figure this out.
Also thanks to the guys on chat.andirc.net (Skourg3 in particular for helping me figure this out the first time).
Let's get down to the nitty gritty yeah?
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
You can confirm that it took by using the cat command
Code:
cat ~/.android/adb_usb.ini
You should get a return of '0x1949' (plus any other rules that you may have added in the past).
Now really that should work but everytime you run adb you will have to either run it as root or using the sudo command. To allow standard user access we have to setup a udev rule.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
That should open up gedit for you to edit the file 51-android.rules. If this is the first time you have added any udev rules the file will be empty as gedit will have just created it for you. go ahead and add in the following.
Code:
# adb/fastboot protocols for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Save that than add in the user group androiddev.
Code:
sudo addgroup --system androiddev
And add your username to that group.
Code:
sudo adduser <username> androiddev
Replace <username> with your primary username without the <> around it.
After that you will need to logout and log back in for these values to apply. You will probably need to restart the adb server as well.
Change directory to your platform-tools directory and run the following.
Code:
./adb kill-server
./adb start-server
Assuming all went well that should work properly and you can than connect through adb, if for some reason this doesn't work try restarting your computer (though I do not believe this is necessary).
If you don't want to type the "./" before all of your adb and fastboot commands, you need to add their parent directory into your PATH environment variable. For example, (assuming you are using the bash shell) if you have adb and fastboot in your /home/<username>/bin directory, you want to define...
Code:
PATH=~/bin:${PATH}
or
Code:
PATH=${PATH}:~/bin
It just depends on whether you want your own binaries to be used before the system equivalents or after. Most people would probably use the first one to have your own binaries be the preferred ones, but either one should work for adb and fastboot since there are no system binaries by the same names.
If you don't want to have to do this for every shell you open, you can place the definition at the end of your ~/.bashrc file. If you need it for you your login shell, you also need to put it into your ~/.bash_profile file. If you don't want to maintain two parallel files with much of the same information, take a look at this post.

Sblood86 said:
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo ~/.android/adb_usb.ini 0x1949
Click to expand...
Click to collapse
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
That will create or append to the file as necessary.

no adb_usb.ini file
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
That will create or append to the file as necessary.
Click to expand...
Click to collapse
Somehow the guide I followed for setting up adb/fastboot on Ubuntu did not create the udb_usb.ini file.
I had to go into android-sdk-linux folder on my home directory and copy the one provided with KFU. Only then I could use the echo command.

freefaling said:
Somehow the guide I followed for setting up adb/fastboot on Ubuntu did not create the udb_usb.ini file.
I had to go into android-sdk-linux folder on my home directory and copy the one provided with KFU. Only then I could use the echo command.
Click to expand...
Click to collapse
This...
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
will definitely create the file if it doesn't exist, but only if the ~/.android/ directory exists (with the correct permissions). It won't make those directories if they don't exist. I'm guessing the .android directory wasn't there when you ran the command.

kinfauns said:
This...
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
will definitely create the file if it doesn't exist, but only if the ~/.android/ directory exists (with the correct permissions). It won't make those directories if they don't exist. I'm guessing the .android directory wasn't there when you ran the command.
Click to expand...
Click to collapse
I read a lot of guides and did what they all said and ended up with a working adb command but my kindle was still not detected. At the end it was this thing that solved the issue.
I dont think I had that "android" folder (i did not unhide the home folder to check but since i setup the android sdk inside "android-sdk-linux" folder, i doubt "android" folder was there).
It's because of these tiny details I was sugesting that you, sir, create a how-to for setting up adb on ubuntu (only if you feel comfortable doing it, that is).
Thanks.
Sent from my Amazon Kindle Fire using XDA

My OS is Mint 12, so same as Ubuntu (except for Unity and a bit of non open-source software) and setting up ADB was also a little bit more difficult than I anticipated. I don't know how other distros are.
The guide that got me most of the way there was this one http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62, and then I hit the same problems as the OP. I had to do a bit of mostly useless searching and reading before I found the entry provided by Gbhil and .adb/ devices made the legend "0123456789ABCDEF device" pop up.
I updated every platform in the sdk while I was at it, oops, must get that 4 or 5 gigs of space in my Home folder back sometime.
A kindle fire specific guide for Ubuntu would be awesome, I hereby second freefaling's nomination of you, Sblood86, as author of said guide, if you're into it, because you seem pretty good at it.

Someone asked me about my Ubuntu setup last night and I thought that I should contribute back to this thread with the same information.
You can add another udev rule to cover fastboot commands on FFF so they don't have to be run as root...
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
If you don't want to type the "./" before all of your adb and fastboot commands, you need to add their parent directory into your PATH environment variable. For example, (assuming you are using the bash shell) if you have adb and fastboot in your /home/<username>/bin directory, you want to define...
Code:
PATH=~/bin:${PATH}
or
Code:
PATH=${PATH}:~/bin
It just depends on whether you want your own binaries to be used before the system equivalents or after. Most people would probably use the first one to have your own binaries be the preferred ones, but either one should work for adb and fastboot since there are no system binaries by the same names.
If you don't want to have to do this for every shell you open, you can place the definition at the end of your ~/.bashrc file. If you need it for you your login shell, you also need to put it into your ~/.bash_profile file. If you don't want to maintain two parallel files with much of the same information, take a look at this link.
http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html
I follow the recommendation at the end.
Hope that helps someone.

kinfauns said:
Someone asked me about my Ubuntu setup last night and I thought that I should contribute back to this thread with the same information.
You can add another udev rule to cover fastboot commands on FFF so they don't have to be run as root...
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
If you don't want to type the "./" before all of your adb and fastboot commands, you need to add their parent directory into your PATH environment variable. For example, (assuming you are using the bash shell) if you have adb and fastboot in your /home/<username>/bin directory, you want to define...
Code:
PATH=~/bin:${PATH}
or
Code:
PATH=${PATH}:~/bin
It just depends on whether you want your own binaries to be used before the system equivalents or after. Most people would probably use the first one to have your own binaries be the preferred ones, but either one should work for adb and fastboot since there are no system binaries by the same names.
If you don't want to have to do this for every shell you open, you can place the definition at the end of your ~/.bashrc file. If you need it for you your login shell, you also need to put it into your ~/.bash_profile file. If you don't want to maintain two parallel files with much of the same information, take a look at this link.
http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html
I follow the recommendation at the end.
Hope that helps someone.
Click to expand...
Click to collapse
I spent something like 3 weeks trying to find the rule that worked with fastboot lol... thanks!
Your link is dead btw.

Sblood86 said:
I spent something like 3 weeks trying to find the rule that worked with fastboot lol... thanks!
Your link is dead btw.
Click to expand...
Click to collapse
Well it worked a couple of days ago when I made my post. It's not my fault it took you so long to read it.
All it really said was to add...
Code:
if [ -f ~/.bashrc ]; then
source ~/.bashrc
fi
to the .bash_profile file so that it will source the .bashrc file regardless of the way you got to the shell. Then you only have to maintain the .bashrc file and only put login shell specific info into .bash_profile
I picked up another tidbit yesterday while engrossed in the whole CWMR bricking thread. Ubuntu has a plugdev group that's used for (mounting?) hot-pluggable firewire/USB devices... sounds a lot like the KF. The first user created on the system is automatically put into that group. Since most Ubuntu desktop are going to be single user machines anyway, that's going to be THE user for the majority of these cases. So, creating a androiddev group just for the KF is probably not necessary most of the time. You can just skip the addgroup and adduser to group commands if you just want to adjust your rules to use the plugdev group instead.

First I'm going to apologize for not being good with this stuff. Now I'm going to ask questions that will probably frustrate some readers. If you aren't irritated by them please help me out.
Sblood86 said:
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
What is the entry provided by gbhil? Where do I get it? I thought I had adb in here but apparently I don't because when I run the echo command I'm getting "no such file or directory."
Can anyone dumb this down for me just a bit. Add the steps I'm obviously going to need as a newb?
Thanks

hortstu said:
First I'm going to apologize for not being good with this stuff. Now I'm going to ask questions that will probably frustrate some readers. If you aren't irritated by them please help me out.
What is the entry provided by gbhil? Where do I get it? I thought I had adb in here but apparently I don't because when I run the echo command I'm getting "no such file or directory."
Can anyone dumb this down for me just a bit. Add the steps I'm obviously going to need as a newb?
Thanks
Click to expand...
Click to collapse
The most likely cause of that error is you don't have a .android directory in your home directory. You'll need to run the following command before that echo command...
Code:
mkdir ~/.android
That will create a ".android" directory in your home directory (~ is shorthand for your home directory). Then you can create that adb_usb.ini file with the "0x1949" line in it.

Thanks for the help. Stuck again.
After that you will need to logout and log back in for these values to apply. You will probably need to restart the adb server as well.
Change directory to your platform-tools directory and run the following.
Code:
./adb kill-server
./adb start-server
Click to expand...
Click to collapse
logged out and in. what is the name of the "platform-tools" directory?
OK found them and realize they're 2 directories. How to I write to 2 directories at once? I'm going to try one at a time. Looking forward to the elaboration on this.
---------- Post added at 06:16 AM ---------- Previous post was at 06:03 AM ----------
ok followed all the steps except this one.
Code:
PATH=~/bin:${PATH}
Code:
PATH=${PATH}:~/bin
Seems like that's for people that not only know what they're doing in the terminal but spend a lot of time there.
Is there a way to confirm that I've enabled adb before I proceed?
Will I need to follow the latter half of these step everytime I want to enable adb or just the start server command?
Again sorry for newb questions and many thanks for the help.
Tried to push pokey's 9000 fb and it didnt work. I don't think I have adb enabled or something.

hortstu said:
What is the entry provided by gbhil? Where do I get it? I thought I had adb in here but apparently I don't because when I run the echo command I'm getting "no such file or directory."
Can anyone dumb this down for me just a bit. Add the steps I'm obviously going to need as a newb?
Thanks
Click to expand...
Click to collapse
I'm guessing Gbhil is a user who originally posted this information, but not sure...
If you go into a Terminal program, like UXTerm or whatever, you simply type that echo command as shown. It will append the 0x1949 to that .ini file in the hidden folder (.android), so adb can see your device. Of course, this is assuming you have a .android folder. It should be in your Home directory.
When I was playing around with custom ROMs and recovery, my KF stopped registering at 0x1949 at one point. Just in case that is happening to you, plug in your KF to your Linux PC. Go into a terminal program and type lsusb. You will get a list of devices and your KF will be there somewhere. If it is not 0x1949, you will see the correct number. If you get a different number (0x whatever), run the echo command for that number, too. No problem having more than one id num in your adb_usb.ini file.

hortstu said:
Thanks for the help. Stuck again.
Click to expand...
Click to collapse
Don't take this the wrong way, but you might want to take a step back from this and learn a little bit about getting around in Linux before you tackle this project with the Kindle Fire. If this is your primary OS, at least knowing how to navigate around the directory structures, how the PATH variable affects how you run commands, and many other things will be invaluable in your day to day use of the operating system. Linux has come a long way to being user-friendly, but it's still reliant on the users knowing their way around the command line interface... much more than the other two big OS's.
There are countless primers and introductions on the basics of getting around the unix/linux command line. I suggest you search for some and familiarize yourself with them.
In the meantime... the "platform-tools" directory the OP refers to in his post is part of Google's Android SDK distribution...
http://developer.android.com/sdk/index.html

kinfauns said:
Don't take this the wrong way, but you might want to take a step back from this and learn a little bit about getting around in Linux before you tackle this project with the Kindle Fire. If this is your primary OS, at least knowing how to navigate around the directory structures, how the PATH variable affects how you run commands, and many other things will be invaluable in your day to day use of the operating system. Linux has come a long way to being user-friendly, but it's still reliant on the users knowing their way around the command line interface... much more than the other two big OS's.
There are countless primers and introductions on the basics of getting around the unix/linux command line. I suggest you search for some and familiarize yourself with them.
In the meantime... the "platform-tools" directory the OP refers to in his post is part of Google's Android SDK distribution...
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
This would be a good start:
vic.gedris.org/Manual-ShellIntro/1.2/ShellIntro.pdf
Sent from my Amazon Kindle Fire using XDA

OK thanks for the help. Realize I should probably know more about this stuff.
Really want to root for the sake of swype and google store. Tough to commit hours to this stuff since I have a family and a job that is non tech.
I have rooted my evo but that was a while back. Seems a little more complicated on the kindle. Thanks again. Not taken the wrong way.

Sblood86 said:
Alright so it turns out making ADB work for the Kindle Fire under Ubuntu is just a touch more difficult than in Windows.
Thanks to Gbhil (@ AndroidCentral) for the write up on windows it was a great jumping off point to try to figure this out.
Also thanks to the guys on chat.andirc.net (Skourg3 in particular for helping me figure this out the first time).
Let's get down to the nitty gritty yeah?
First you will still need the entry provided by Gbhil, go ahead and set it using the echo command in a terminal.
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
You can confirm that it took by using the cat command
Code:
cat ~/.android/adb_usb.ini
You should get a return of '0x1949' (plus any other rules that you may have added in the past).
Now really that should work but everytime you run adb you will have to either run it as root or using the sudo command. To allow standard user access we have to setup a udev rule.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
That should open up gedit for you to edit the file 51-android.rules. If this is the first time you have added any udev rules the file will be empty as gedit will have just created it for you. go ahead and add in the following.
Code:
# adb/fastboot protocols for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Save that than add in the user group androiddev.
Code:
sudo addgroup --system androiddev
And add your username to that group.
Code:
sudo adduser <username> androiddev
Replace <username> with your primary username without the <> around it.
After that you will need to logout and log back in for these values to apply. You will probably need to restart the adb server as well.
Change directory to your platform-tools directory and run the following.
Code:
./adb kill-server
./adb start-server
Thanks for the post and the guide.
I have a little problem. i.e How do i change the directory to platform-tools directory before i ru the code u gave me. Please dont be mad at me becouse the truth is i am a new user.
Click to expand...
Click to collapse

majexy033 said:
Thanks for the post and the guide.
I have a little problem. i.e How do i change the directory to platform-tools directory before i ru the code u gave me. Please dont be mad at me becouse the truth is i am a new user.
Click to expand...
Click to collapse
As in; from your terminal use the 'cd' command to change directory to where-ever platform-tools is actually installed on your PC.