Database Info

[HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux

When I first attempted to install the SDK, I found tutorials that only had bits and pieces about the whole procedure. A lot of Google searches and hours of eye strain. I wanted to write a solid tutorial, but instead of publishing it in a personal blog, I chose to publish it here on xda-developers. This is the definite forum to come to if you are interested in Android/G1/HTC Dream development or costumization. I wrote this to make the enlarge the knowledge of this community.
!! THIS TUTORIAL IS FOR THE LATEST UBUNTU RELEASE: JAUNTY JACKALOPE 9.04 !!
!!START -------------------------------------- Optional Preparation --------------------------------------
This applies if you -
Are interested in installing Ubuntu for the first time.
Are/will be reinstalling Ubuntu from scratch.
Want to keep your SDK installation easy to reach.
Want to keep things nice and clean.
And your machine -
Has a second hard drive.
Has free space for another small partition.
This procedure will make things easier during installation of the SDK and in the long run. Hopefully you've read about partitions. If you are dualbooting, please read this first to get an idea of what you're doing.
While installing Ubuntu and on the Prepare Disk Space screen (partition editor), select "Specify partitions manually (Advanced)"
On the Create Partition dialog, select the following options:
Type for the new partition: Primaryor Logical if you're dualbooting and know what you are doing.​
New partition size in megabytes: 5120MB (5GB) might work. BUT:
ccyrowski said:
It should be noted that if you ever plan on compiling kernels and/or cupcake ROM's you will NEED ubuntu8.04. You'll also need at least 10GB.
Click to expand...
Click to collapse
Location for the new partition: Beginning
Use as: Ext4 or Ext3Filesystem doesn't matter. (?)​
Mount point: /AndroidSDKEnter this manually​
Complete Ubuntu installation as usual.
-------------------------------------- Optional Preparation -------------------------------------- END!!​
You will now install the SDK.​
!!START -------------------------------------- Installing Android SDK --------------------------------------
Installing the SDK is the easiest of all.
Download the SDK.169.9 MB [http://developer.android.com/sdk/download.html?v=android-sdk-linux_x86-1.5_r3.zip]​
Right-click and select Extract Here.
Move the contents of the android-sdk-linux_x86-1.5_r3 directory to your desired location.If you followed Optional Installation, move the contents to your /AndroidSDK directory in the root of your filesystem.​
Close directory window.
-------------------------------------- Installing Android SDK -------------------------------------- END!!​
You will now set up your bashrc file and UDEV to recognize your HTC Device.​
!!START -------------------------------------- ADB + FASTBOOT --------------------------------------
The Android Debug Bridge (adb) is one of the tools that will help you the most when you run into flashing problems or running shell commands directly from your machine. UDEV will not recognize your G1 out of the box, but we will configure it with some rules so it can connect.
We will work with /AndroidSDK as the location of your sdk. If this is not your setup, I think you're smart enough to figure it out.
Editing .bashrc file to use tools from /AndroidSDK/tools/ directory -
Go to your home folder.Example: /home/wddglr/​
Press Control + H to view hidden files.
Look for your .bashrc file and double click to open it with gedit.
Add the following lines to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools
IMPORTANT NOTE
savethechicken said:
This is the way that I have my .bashrc file setup. For those having problems with it not recognizing the adb as a command try this...
Code:
export PATH=$PATH:/AndroidSDK/tools
I removed the {} around ${PATH} and it is working if I had them on it would say that it didn't recognize the command. Removed them and all works well.
Click to expand...
Click to collapse
Setting up UDEV to recognize HTC Device -
Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click save and close.
To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
Setting up fastboot -
Download this fastboot binary from http://android-dls.com.130.4 KB [http://android-dls.com/files/linux/fastboot]​
Once downloaded to your desktop, right click and select Properties.
Navigate to the Permissions tab and configure the following option:Execute: [√] Allow executing file as program​
Click Close.
Move the fastboot bianary to your /AndroidSDK/tools/ directory.
Reboot.
-------------------------------------- ADB + FASTBOOT -------------------------------------- END!!​Now you can use adb and fastboot directly from any terminal. If you chose to do the Optional Preparation, you can now save your Eclipse Workspace and your downloaded/custom ROMs/Themes in this new /AndroidSDK directory keeping things easier to reach and safe from evil disk errors or other mishaps!!! :O​If you are having problems, send me a PM. I will be happy to help.

*applaudes* awesome. Should be added to helpful threads.

very nice! perhaps add a "(How-To)" prefix to thread??

Everything was going great in setting this up until I got to this part "gedit /etc/udev/rules.d/51-android.rules"
I cannot find "51-android.rules" inside of "rules.d"
Any thoughts>?

nicholasbithell said:
Everything was going great in setting this up until I got to this part "gedit /etc/udev/rules.d/51-android.rules"
I cannot find "51-android.rules" inside of "rules.d"
Any thoughts>?
Click to expand...
Click to collapse
it does not exist, you will make it.
do the command as stated above.
Code:
gksu gedit /etc/udev/rules.d/51-android.rules

Damn you beat me to it!
I was just thinking earlier about doing this same "How-To" guide, I was surprise to see it posted just now.
Anyways, great job!

Can someone sticky this thread. Now I have ADB & fastboot on my Win7, Ubuntu, and OS X Partition. Thank you wddglr.

bravo...linux rocks even better now!...

Awesome tutorial for setting this up. Have been using adb/sdk on ubuntu since oct. but this would have saved me some headaches back in the first couple of weeks.
The onlything that is not clear and/or confuses me is
Setting up the udev to recognize the device.
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Have never used this (will now to see if it will do anything) and the only problem i have is that sometimes i have to kill-server to get it to connect correctly but i have seen this happen to almost everyone on many forums since the 9.04 came out. And even after putting this file on the computer i have had the problem.

savethechicken said:
Awesome tutorial for setting this up. Have been using adb/sdk on ubuntu since oct. but this would have saved me some headaches back in the first couple of weeks.
The onlything that is not clear and/or confuses me is
Setting up the udev to recognize the device.
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Have never used this (will now to see if it will do anything) and the only problem i have is that sometimes i have to kill-server to get it to connect correctly but i have seen this happen to almost everyone on many forums since the 9.04 came out. And even after putting this file on the computer i have had the problem.
Click to expand...
Click to collapse
It happens to me also from time to time. especially when i reboot and want to go into adb while the device is rebooting. although that file, 51-adndroid.rules, is what helped me get adb to recognize the device. the guide on developer.android.com talked about 50-android.rules but after a few deep searches i found this: http://groups.google.com/group/android-developers/browse_thread/thread/1d3488c601243686

Okay A few questions for you....
First I fixed the whole "couldnt find the (51-android.rules) file now I am having issues with executing ADB!
When in terminal this is what I get...
"[email protected]:/home/nick# /AndroidSDK/tools/adb
bash: /AndroidSDK/tools/adb: cannot execute binary file
[email protected]:/home/nick#"
and I also noticed something different from when I start terminal the first lines now state
"bash: : command not found
[email protected]:~$"
I dont remember the first line ever being there, but I could be mistaken!
Any help would be greatly appreciated!
Edit: You state creating "Mount point: /AndroidSDK" During Installation, and what I did was Just place my AndroidSDK at root so it is at "/AndroidSDK". I dont know if this makes a difference.
I am actually running ubuntu 8.10 ha! I just tried to update But I keep getting errors! is there anything I can change to get this to work on ubuntu 8.10?

nicholasbithell said:
First I fixed the whole "couldnt find the (51-android.rules) file now I am having issues with executing ADB!
When in terminal this is what I get...
"[email protected]:/home/nick# /AndroidSDK/tools/adb
bash: /AndroidSDK/tools/adb: cannot execute binary file
[email protected]:/home/nick#"
and I also noticed something different from when I start terminal the first lines now state
"bash: : command not found
[email protected]:~$"
Edit: You state creating "Mount point: /AndroidSDK" During Installation, and what I did was Just place my AndroidSDK at root so it is at "/AndroidSDK". I dont know if this makes a difference.
I am actually running ubuntu 8.10 ha! I just tried to update But I keep getting errors! is there anything I can change to get this to work on ubuntu 8.10?
Click to expand...
Click to collapse
okay, a few things -
seems like your .bashrc file isn't setup right (?)
make sure that the two lines you inserted into it are on separate line
Code:
#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools
because maybe export PATH=${PATH}:/AndroidSDK/tools got commented on accident if you copy pasted.
When copying your SDK to the root of your filesystem, did you copy it as your own user or as root? you can use:
Code:
gksu nautilus
to copy system files with complete root privileges.
What exactly are you trying to update, Ubuntu or ... ? There shouldn't be a difference to get this working on 8.10, the only thing that seemed to change was the 51-android.rules file. Maybe this can help -
renaming it to 50-android.rules with
Code:
gksu nautilus
and deleting any backups (use CTRL+H to view hidden files).
restarting udev using:
Code:
sudo /etc/init.d/udev restart
Remember this is for 9.04, not 8.10. I hope this helps.

wddglr said:
okay, a few things -
seems like your .bashrc file isn't setup right (?)
make sure that the two lines you inserted into it are on separate line
Code:
#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools
because maybe export PATH=${PATH}:/AndroidSDK/tools got commented on accident if you copy pasted.
When copying your SDK to the root of your filesystem, did you copy it as your own user or as root? you can use:
Code:
gksu nautilus
to copy system files with complete root privileges.
What exactly are you trying to update, Ubuntu or ... ? There shouldn't be a difference to get this working on 8.10, the only thing that seemed to change was the 51-android.rules file. Maybe this can help -
renaming it to 50-android.rules with
Code:
gksu nautilus
and deleting any backups (use CTRL+H to view hidden files).
restarting udev using:
Code:
sudo /etc/init.d/udev restart
Remember this is for 8.10, not 9.04. I hope this helps.
Click to expand...
Click to collapse
Okay this is how I moved my "AndroidSDK" Folder to root....
[email protected]:~$ su
Password:
[email protected]:/home/nick# mv /home/nick/Desktop/AndroidSDK /
[email protected]:/home/nick#"
And I went to the bashrc file and it is entered in there correctly.
This is still what I get even after restarting Udev...
" bash: : command not found
[email protected]:~$ adb
bash: /AndroidSDK/tools/adb: cannot execute binary file
[email protected]:~$ su
Password:
[email protected]:/home/nick# adb
bash: adb: command not found"
Edit: This is what my .bashrc file looks like, well the top part of it anyways....
#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

Okay your .bashrc is setup right and it's recognizing adb and its directory.
I would say it's something to do with permissions. since you moved it under su, you are not the owner so i would say that you'd have to change the permissions of /AndroidSDK
you can do that with -
Code:
gksu nautilus
Navigate to /
Right click on /AndroidSDK and select Properties
Click on Permissions tab
Select your user account as the owner
hopefully now it will function correctly

wddglr said:
Okay your .bashrc is setup right and it's recognizing adb and its directory.
I would say it's something to do with permissions. since you moved it under su, you are not the owner so i would say that you'd have to change the permissions of /AndroidSDK
you can do that with -
Code:
gksu nautilus
Navigate to /
Right click on /AndroidSDK and select Properties
Click on Permissions tab
Select your user account as the owner
hopefully now it will function correctly
Click to expand...
Click to collapse
I dont understand what this line does...
"gksu nautilus"
when i type it in it asks me for my administrative password and then after i put it in it hangs for a sec and then back to...
bash: : command not found
[email protected]:~$ gksu nautilus
[email protected]:~$

nautilus is the file browser, while using gksu nautilus you can use the file browser under root privileges

wddglr said:
nautilus is the file browser, while using gksu nautilus you can use the file browser under root privileges
Click to expand...
Click to collapse
I dont have Nautilus as a file browser I have Thunar I believe.

Then gksu thunar

wddglr said:
nautilus is the file browser, while using gksu nautilus you can use the file browser under root privileges
Click to expand...
Click to collapse
For permissions it says that I am the owner and the group (I=Nick) for Others it says Read and Write, Access says Read and write. So it seems it has all the right permissions. Any other Ideas?

Partitioning HD
First off, thank you for this thread, it's most excellent. I have a question that is slightly off topic, but not so much. I have Ubuntu 9.04 installed on my recovery partition. This partition is only 10 GB, while I have Vista on my main. I have almost 100 GB free on my main drive, and what I want to know is, if I resized my partitions to give more space to Ubuntu, how would it affect my comp? (if at all). And which OS should I be on while resizing, Ubuntu or Vista?

[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]

[How to]? ADB on Ubuntu 10.10?

Can someone provide a step-by-step guide to installing ADB on Ubunto 10.10 for a beginner please?
Thanks

Still need help
t0ph0id said:
Can someone provide a step-by-step guide to installing ADB on Ubunto 10.10 for a beginner please?
Thanks
Click to expand...
Click to collapse
It's been awhile since you posted, do you still need help. I have a simple method, let me know and I will make you instructions. It wouldn't be a problem.

blas4me said:
It's been awhile since you posted, do you still need help. I have a simple method, let me know and I will make you instructions. It wouldn't be a problem.
Click to expand...
Click to collapse
I would love a quick step-by-step. Been trying to figure this out but failing. Hard.

ADB & FASTBOOT Help: Updated 6/6/12
WORKS FOR x86 VERSION OF 12.04 - 12.10 TO MAKE IT WORK FOR x64 FOLLOW LINK BELOW, THEN COME BACK HERE AND FINISH SETUP. I ALSO ADDED A VIDEO, CHECK IT OUT
1. You must have java installed before you start set up.
http://askubuntu.com/questions/131207/android-sdk-cant-be-installed-on-ubuntu-12-04-64
I know if your new the other instructions can be confusing, so I kinda know what you guys are looking for, just a basic breakdown, I remember when I started playing around with 9.04, the adb setup had me stuck, Ubuntu used to frustrate me, because I didn't understand Unix based systems, but you catch on, especially if your a android user.
JUST A TIP: I make my SDK folder androidsdk, for simplicity and that's how I learned to install. so I'm just showing you the way I learned. I have rooted over 20 different Android devices, and I've installed this method on multiple Linux distros without a problem. For those of you that are new to Linux, know that Linux is hardwired for Andorid devices, same kernal and all, and that's why it's wise to do all things Android on Linux machines, I try to anyway
RECENT CHANGES TO SDK: updated 11/1/12: Just installed on Ubuntu 12.10, and the Linux adb installer is no longer needed, when I ran adb command after copying SDK to my /usr/local/ directory, my device showed up. Some resent changes to the SDK, also changed the way you set up, but not very much. The SDK provides all the files you need to set up, including fastboot.
NOTE: Once you've finished the setup, know that you push & pull right from your home folder, no need to put things in the tools folder like Windows, same thing when you pull, look for the files in the home folder.
1. Go here for the latest SDK
http://developer.android.com/sdk/index.html
(once download, double tap and extract right to home folder, rename to androidsdk)
a. Make android file executable
2. Open teminal.
a. Navigate to your SDK directory
Code:
cd /home/username/androidsdk/tools
you should get [ $ ] at the end of your path.
b. Type
Code:
./android
your SDK Manager should start.
ADVICE: I suggest you only download tools and platform-tools to make the setup quick, you can go back later and install what you need
NOTE: For development purposes you need a copy of ADB & Fastboot in your tools folder, Eclipse looks for ADB in the folder, so if you plan on developing, then you'll need those files there.
3. Open home folder, press ctrl & H to show hidden files, find bashrc
a. Paste in terminal from your document after you input your user name:
Code:
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
export PATH=${PATH}:/androidsdk/platform-tools
export PATH=${PATH}:/home/*********/androidsdk/tools
export PATH=${PATH}:/home/*********/androidsdk/platform-tools
4. Paste in terminal from your document after you input your user name:
Code:
export PATH=$PATH:/androidsdk/tools
export PATH=$PATH:/androidsdk/platform-tools
export PATH=$PATH:/home/*********/androidsdk/tools
export PATH=$PATH:/home/*********/androidsdk/platform-tools
NOTE: For this part you'll need your devices id, here's a list, if your devices id isn't here, use code below.
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Fujitsu 04c5
Fujitsu Toshiba 04c5
Garmin-Asus 091e
Google 18d1
Hisense 109b
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenovo 17ef
LG 1004
Motorola 22b8
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10a9
Pegatron 1d4d
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony 054c
Sony Ericsson 0fce
Teleepoch 2340
Toshiba 0930
ZTE 19d2
In terminal type:
Code:
lsusb
and that will give a list of all USB devices attached to your machine.
a. In terminal, type:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
b. Add these lines, put your device ID between quotations, then save
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="HERE", SYMLINK+="android_adb", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="HERE", SYMLINK+="android_adb", MODE="0666"
c. In terminal type:
Code:
sudo restart udev
5. Download the Linux ADB installer zip, extract to your home folder, make script executable and to run with auto prompt (plug your phone in if it isn't already) then just double click and choose run, then let it do it's thing Takes a second, and it should ask for permissions = user password
NOTE: When you run nautilus your going into file system directory as root, so proceed with caution, and back up any file you plan on editing. Installing SDK doesn't make a folder in /usr/local/ any more, so you'll have to copy SDK to that directory as root.
6. Open terminal, type:
Code:
sudo nautilus
a. Go to :File system /usr/local
b. Copy and paste a copy of your SDK folder there
c. Close root session
d. Close terminal
7. Open terminal, type:
Code:
adb devices
you should see your device, then type fastboot devices it should just go to the next line, you have to be in fastboot to see your device
Now you should have ADB & Fastboot on your beautiful Ubuntu machine!!!!!!!!!!
With narration
http://www.youtube.com/watch?v=HsCd1nMywR8&hd=1
Without
http://www.youtube.com/watch?v=IGAiHkPuhg8
Extra goodie (Aero Snap Windows.) Extract and follow intructions. Enjoy!!!!!!!!!
TIP: For trigger delay, the lower you set it the faster your widows will resize, and I have mine set for left & right edge. Having it set @ right & left is a headache because every time your pointer touches left or right side of the screen , widows resize. So, having them set to the edges works for me.

Just wanted to say thanks, awesome post.

Thanks
star.gazer said:
Just wanted to say thanks, awesome post.
Click to expand...
Click to collapse
I've been waiting to hear feedback, was it a simple process.

I see two problems at first glance with the instructions above:
1. This will only work with two brands, the one
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", MODE="0666"
Click to expand...
Click to collapse
being HTC ("0bb4"), the other
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", SYMLINK+="android_adb", MODE="0666"
Click to expand...
Click to collapse
not known to me. For a list of other vendors, have a look at http://developer.android.com/guide/developing/device.html .
2. You're mixing up adb-related instructions with instructions to change Ubuntu's UI, which is totally unrelated. This "Extra goodie (Aero Snap Windows.)" is neither needed for the task in question nor is it asked for by many Linux users (like me). Also, I wouldn't recommend -- at least not to an average user -- to bypass Ubuntu's package management in order to get some visual sugar. Bypassing might conflict with further updates and lead to a situation where thorough knowledge is required.
As a simple, efficient and painless way I recommend the app adbWireless. No need to install anything but the SDK (downloaded from developer.android.com and only from there) and the app. Then start adb and the app and give the command line provided by the app's display, and you're connected without any messing around with udev and permissions.

Who are you!!!!!!!!!
mizch said:
I see two problems at first glance with the instructions above:
1. This will only work with two brands, the one being HTC ("0bb4"), the other not known to me. For a list of other vendors, have a look at http://developer.android.com/guide/developing/device.html .
2. You're mixing up adb-related instructions with instructions to change Ubuntu's UI, which is totally unrelated. This "Extra goodie (Aero Snap Windows.)" is neither needed for the task in question nor is it asked for by many Linux users (like me). Also, I wouldn't recommend -- at least not to an average user -- to bypass Ubuntu's package management in order to get some visual sugar. Bypassing might conflict with further updates and lead to a situation where thorough knowledge is required.
As a simple, efficient and painless way I recommend the app adbWireless. No need to install anything but the SDK (downloaded from developer.android.com and only from there) and the app. Then start adb and the app and give the command line provided by the app's display, and you're connected without any messing around with udev and permissions.[/QUOTE/]
The other number is the new HTC id, for those who have other android devices, I included the auto script. I've been waiting for someone like you to come along, "a mister know it all", but it's kool. Just to let you know I got Aero Windows from OMGubuntu. I still get updates. as I'm typing my Update Manaer just notified me, that there are updates for me. Obviously your not familiar with setting up ADB&Fastboot on Ubuntu. And you should be smart enough to see that the instructions are just for ADB&Fastboot setup. The instructions for Aero are inside the zip. I put everything here instead of starting a new post, duh, how many members have you helped on this forum. Don't try to confuse other members, with your babble. Next time don't just glance read, read, read, Maybe you just need a friend Two words for you " Open Source "
Click to expand...
Click to collapse

I've been waiting for someone like you to come along, "a mister know it all", but it's kool.
Click to expand...
Click to collapse
Hope you feel better now.

Just a quick post to say thanks.
Easy to follow and got me working on flashing my radio from my new 10.10 installation.

nategs said:
Just a quick post to say thanks.
Easy to follow and got me working on flashing my radio from my new 10.10 installation.
Click to expand...
Click to collapse
Thanks for the feedback.

Thanks
Thank you for the easy to follow post. I am a new user to Ubuntu (and Linux in general) and this was an extremely user friendly tutorial.

blas4me said:
I know if your new the other instructions can be confusing, so I kinda know what you guys are looking for, just a basic breakdown, I remember when I started playing around with 9.04, the adb setup had me stuck, Ubuntu used to frustrate me, because I didn't understand linux based systems, but you catch on, especially if your a android user. You can just copy & paste all of the command. I've done this on 10.04 about four or five times, and 10.10 twice so far.
Edit: I just set up adb on my other lappy, and I notice the SDK is a little different. There is no adb file in the tools folder, it's just in another folder. You don't have to give it permissions, so just follow the instructions, and enjoy the new additions to the SDK.
Note: Once you've finished the setup, know that you push & pull right from your home folder, no need to put things in the tools folder like Windows, same thing when you pull, look for the files in the home folder.
1.Go here for the latest SDK
http://developer.android.com/sdk/index.html
(once download, double tap and extract right to home folder, rename to androidsdk)
2.Open folder and got to tools folder
a.right click on adb, go to properties and check allow execution, choose or add open with auto prompt, do same for android file then double click on android and choose run
b.download and install, let it finish
Note: When I say add these line, I'm saying add the lines under the alphanumeric instructions
3.Open home folder, press ctrl & H to show hidden files, find bashrc
a.add these lines to the top of file,# include, then space it from next paragraph of text
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
4.Open terminal, type: export PATH=$PATH:/androidsdk/tools
a.in terminal, type: gksudo gedit /etc/udev/rules.d/51-android.rules
b.add these lines, then save
c.in terminal type: sudo restart udev
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", SYMLINK+="android_adb", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", MODE="0666"
(plug your phone or phones in if it isn't already)
5.Extract the installer zip to your home folder, make script executable and to run with auto prompt, then just double click and choose run, then let it do it's thing
Note: When you run nautilus your going into file system directory
6.Open terminal, type: sudo nautilus
a.go to /usr/local/androidsdk/tools
b.make adb file executable, and choose or add open with auto prompt, then close root session and close terminal
7.Open terminal, type: adb devices, you should see your device or devices
8.Set up fastboot, go here for the file
http://forum.xda-developers.com/showthread.php?t=537508
a.once downloaded, copy to tools folder in your home directory, and enter root session with sudo nautilus command and add fastboot to /usr/local/androidsdk/tools
b.don't forget to make both files executable, and open with auto prompt,then close root session, close terminal.
9.Open terminal, type: adb devices
a.type:fastboot devices
(if it just go's to the next line your cool, you need to be in fastboot to see your device, if you get fastboot not found, then go back to the fastboot files and make sure you did part:8b
Now you should have adb&fastboot on your beautiful Ubuntu machine!!!!!!!!!!!
Extra goodie (Aero Snap Windows.) Extract and follow intructions. Enjoy!!!!!!!!!
TIP: For trigger delay, the lower you set it the faster your widows will resize, and I have mine set for left & right edge. Having it set @ right & left is a headache because every time your pointer touches left or right side of the screen , widows resize. So, having them set to the edges works for me.
Click to expand...
Click to collapse
Excellent Post. Thank you very much.

I can't get anything but "No command 'adb' found"
I'm trying to follow your instructions, but the section with the export PATH stuff is very hard to follow.
I know that adb is located in:
Code:
/home/USERNAME/Applications/android-sdk/platform-tools
So I would put this in my .bashrc:
Code:
#AndroidDev PATH
export PATH=${PATH}:/Applications/android-sdk/platform-tools
# include
And then I'd type this into the terminal:
Code:
export PATH=$PATH:/Applications/android-sdk/platform-tools
Right?

blas4me said:
TIP: For trigger delay, the lower you set it the faster your widows will resize, and I have mine set for left & right edge. Having it set @ right & left is a headache because every time your pointer touches left or right side of the screen , widows resize. So, having them set to the edges works for me.
Click to expand...
Click to collapse
I followed your guide for adb installation and it worked great. I just want to say thanks.
In the Aero tip, I just wanted to know what you meant by setting it to the right and left edges. When I put my pointer to the edges, the windows resize like you said and I wanted to set it up like you have yours.

You'll get it
Mogomra said:
I can't get anything but "No command 'adb' found"
I'm trying to follow your instructions, but the section with the export PATH stuff is very hard to follow.
I know that adb is located in:
Code:
/home/USERNAME/Applications/android-sdk/platform-tools
So I would put this in my .bashrc:
Code:
#AndroidDev PATH
export PATH=${PATH}:/Applications/android-sdk/platform-tools
# include
And then I'd type this into the terminal:
Code:
export PATH=$PATH:/Applications/android-sdk/platform-tools
Right?
Click to expand...
Click to collapse
Your SDK folder should be in your home directory. You should rename your SDK folder to androidsdk for simplicity, if your pasting the commands from my post. I see the path you tried to export and it's not correct. I said in my post that they changed the location of the adb file, but to follow the instructions. You need to redo your bashrc file, just copy and paste my code lines, and you can't go wrong, trust me. I want your adb&fastboot up & running. Let me know what happens.

I figured it out. I should have put a ~ in front of "/Applications" or "home/USERNAME" in front of it.
Thanks

Devildog8791 said:
I followed your guide for adb installation and it worked great. I just want to say thanks.
In the Aero tip, I just wanted to know what you meant by setting it to the right and left edges. When I put my pointer to the edges, the windows resize like you said and I wanted to set it up like you have yours.
Click to expand...
Click to collapse
You can set edge bindings from two applications, SCSM or Compiz

Mogomra said:
I figured it out. I should have put a ~ in front of "/Applications" or "home/USERNAME" in front of it.
Thanks
Click to expand...
Click to collapse
That's strange I've never heard of anybody using that path, can you still just type in " adb devices " and see you phone or do you have to type " sudo adb "

blas4me said:
You can set edge bindings from two applications, SCSM or Compiz
Click to expand...
Click to collapse
So instead of going to the sides, you are going to the corners, correct?

[GUIDE] How to install SDK/ ADB and do a Logcat and some essential guides

Hello everyone at xda !
As a newcomer I was searching for a bit of help getting started with android tools and its development.
So I decided to help out the newcomers a bit more by creating this thread..
I found this to be essential for our HTC Explorer Development Forum
This guide contains :
Post 1:
Info about SDK / ADB and how to install them on linux and windows.
Logcat- How to logcat , types of logcats , meaning
Adb wireless
Post 2:
Clean install
Paritioning sd
Flashing kernel , recovery
Permissions
What is overclocking ?
Recover from OC
md5 checksum
Post 3:
Video tuts and credits.
Info about ADB/SDK :
ADB
What is adb ?
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
SDK
What is android SDK ?
Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012, more than 700,000 applications have been developed for Android, with over 25 billion downloads.The Android platform has also grown to become a favorite among mobile developers.
Want to download and use adb and SDK ( its in one package )?
Visit http://developer.android.com/sdk/index.html
Extract the files of the package you downloaded from the site as whatever you want to but remember it ?
Windows Specific (VISTA)
Keep your path name to which is extracted to
Eg : C:\(*package-name*) [ eg of package name : adt-bundle-windows-x86 ]
Rename the Folder to C:\(*Whatever you want to name it*) [ eg change "adt-bundle-windows-x86" to "android" ]
In order to run adb do the following steps :
Click start
Search for cmd
Right click and * RUN AS ADMINISTRATOR *
type the following commands
Code:
C:\Windows\system32\>cd C:\android*\sdk\platform-tools\ [*click enter*]
C:\android*\sdk\platform-tools>adb
C:\android*\sdk\platform-tools>adb devices
Now you should get a huge code block with all the adb commands
That means adb has been installed correctly.
adb devices gives you the list of attached adb devices and if their permissions are right..
Setting up ADB as a command on Windows 7/ Vista
Assuming you have done the above steps correctly you should have no problem going ahead
Right click on Computer
Click on properties
Go the advanced system settings
Click on the advanced tab
Go to Enviornmental variables in the dialog box
In system variables find the variable " Path ".
Double click on it and in variable value add the following line at the end of it :
Code:
;C:\android\sdk\platform-tools\;
Click on OK etc and save the settings
now Run command prompt
Type adb and your adb commands will be in function..
You can now run adb as a command and dont need to go to the directory every time.
Linux Specific ( Ubuntu )
PS (important) if someone has a 64bit linux then they need to download 32bit libs
for this, before all these steps run this
Code:
sudo apt-get install ia32-libs
You should have an updated JDK for this.. Just in case..
Code:
$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6
$ sudo apt-get update
$ sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
we need to make a new directory by this command
Code:
mkdir android
then extract by
Code:
tar -zxvf ~/Downloads/android-sdk_r21.0.1-linux.tgz
then move it to the directory we just made
Code:
mv android-sdk-linux ~/android/sdk
the open android sdk manager by
Code:
android/sdk/tools/android
this will open android sdk manager
we need to select just android sdk tools and android sdk platform tools for adb and then select install packages
^^this will download everything required
then we need to set a path to include adb
Code:
gedit .bashrc
and then a file opens and paste this text in that file
Code:
export PATH=${PATH}:~/android/sdk/platform-tools
then we make the above bashrc file executable by this
Code:
chmod a+x .bashrc
then we need to setup device rules and make that file executable
ps sample is the username
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
we need to add full path to adb start server
Type :
Code:
sudo gedit /etc/rc.local
this will open a file
now add this line just above where it is written exit 0
Code:
/home/sample/android/sdk/platform-tools/adb start-server
"sample is username"
after this we dont need to cd to adb directory..we can just type adb devices and the phone will surely show up
Guide for Linux by Gnexus. Thank him Here!
Now we have a blooming xda forum at HTC Pico aka Explorer with :
Cyanogen mod 7
Cyanogenmod 9
Cyanogenmod 10
Cyanogenmod 10.1
Sense 3.5(stock)
Sense 4.0
Which is quite a lot considering our device is considered as
A legacy / low activity device
Click to expand...
Click to collapse
Now with all those ROMs come their respective bugs..
Just saying
" Random reboot "
" I dont know but xyz doesnt work "
" Xyz fces "
Click to expand...
Click to collapse
Gives just another burdening job for a ROM dev of trying to find that same mistake and trying to take a log of it..
At times they are on a different ROM and it becomes difficult for them to flash their old ROMs again..
Sometimes they dont even have the same device !!
So.. Try to ease the job of the dev by bringing whats called a logcat so you can do the following to help them out :
You should have installed adb and fastboot by now
For getting a logcat you should do the following easy steps
Connect phone to pc / laptop ( quite obviously )
Assuming you have rooted your phone you should have required drivers installed ?
To enable ADB mode on your phone go to settings > developer options > Debugging > USB Debugging > ON
1st go to cmd and run as administrator and go to the root of adb
simply type
Code:
C:\android*\sdk\platform-tools>adb logcat
and you get a logcat running on your screen
Want to post a logcat somewhere ?
1] A logcat that can be easily copy pasted and given to someone else :
to do that type :
Code:
adb logcat > cat.txt
*cat is just an example .. it can be Anything logcat.txt, catlog.txt, etc ( let your imagination go wild )
This gives you a logcat at the platform-tools folder .
Now if you get your logcat you can post the logcat somewhere in the dev threads as a whole logcat or you can put specific lines where you want the dev to look at or you know the error is present. There is a character number limitation on a single post on xda for which you can simply upload the .txt file or you can also post it on Pastebin and share the link/url on the thread. This helps a lot .
Alternatively there are apps such as aLogcat or Catlog but installing adb and fastboot is essential as it will not only help you with this but other functions also look further down..
Meanings of symbols in a logcat !
You usually see this at the start of a sentence in logcat .
I/> ===> Information
S/> ===> Silent
D/> ===> Debug
W/> ===> Warning
E/> ===> Error
F/> ===> Fatal
For more information about logcats
Help with solving a logcat from fellow members only for pico ! ​
DMESG (*Useful for devs / beta testers alike*)
Go to your adb directory via terminal / cmd on admin privileges
Type
Code:
adb shell dmesg > dmesgLOG.txt
Terminal emulator :
Code:
dmesg > /sdcard/dmesglog.txt
DMESG is useful for finding out errors / bugs in the hardware aspects caused due to software issues and kernel issues (* eg : deepsleep , bluetooth not working , wifi not working etc . *) which cannot sometimes be easily solved through a simple logcat.
Lastly K-MESG
To help solving with respect to kernels (* Yes it is a kernel not kernal... *)
Kernel issues like a kernel panic and similar. Similar steps to dmesg but the code is
Code:
adb shell cat /proc/last_kmsg > kmsg.txt (*via adb*)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt (*via terminal emulator*)
ADB wirelessly
To use adb via Wi-Fi
Download this wonderful app from the playstore adbWireless
Click on the green button and an IP will come on the app screen. (* eg: 123.456.7.890 *)
On your computer go to your adb directory via terminal / cmd prompt
type
Code:
adb connect 123.456.7.890
Voila! You are using adb wirelessly
Some useful extra stuff !
Adb guide
Note : Please do not quote the entire first post in the replies !

Some other essential guides.
What do you mean by a clean install ?
WARNING ! : Do NOT wipe/format External storage . This will result in the loss of data.
A clean install can be done as follows :
On CWM / Yannou's recovery :
Boot into recovery
Do a factory reset
Go into mounts and storage using volume rockers and power button.
Format /system /boot /cache
Go to advanced : Wipe Dalvik Cache.
On TWRP Recovery :
Go to wipe
Wipe Cache , Dalvik Cache , System SD Ext and then do a factory reset.
Done ! Now flash the required ROM you want to flash!
How to partition SD card ?
Note :
This will result in your SD card being formatted. So always keep a backup of all your files on your computer.
For Stock ROM you need a FAT 32 partition which can be done via computer ONLY.
Via Recovery
Boot into recovery
Go to advanced
Partition SD card (*EXT 2,3,4 etc.*)
Select EXT Size *to whatever you want to preferably 512 mb or more*
Select Swap = 0 mb as Explorer doesnt support swap. ( at least till now )
Partition SD card! (*Will take some time*)
After partitioning is done just remove your SD card (*while your phone is off*) and just insert it back in manually.
Reboot /system (*if you have a ROM installed*)
Connect to PC and check for bad partitions just in case.
Steps 7,8,9 are not mandatory but are a good practice.
Via a computer : ( Windows )
Requirement :
SD Card reader
MiniTool Partition Wizard Home Edition 7.7 .
For further details on this visit this great guide
How to flash custom recoveries / kernels ?
How to flash a custom recovery ?
Via computer
Copy the recovery.img of the custom recovery you are try to flash and paste it in the adb directory ( for windows ==> C:\android\sdk\platform-tools\*paste here* )
Boot your Pico into bootloader (*remove battery and after 3-4 secs press vol. down and power button simeltaneously*)
In bootloader menu connect pc to your phone via usb cable and then there will be a red coloured sign just above the options saying
FASTBOOT USB
Click to expand...
Click to collapse
Now start
Windows Go to platform-tools directory in command prompt and type
Code:
fastboot flash recovery recovery.img
fastboot reboot
Linux Go to the directory of adb and fastboot and type in terminal
Code:
$ ./fastboot flash recovery recovery.img && fastboot reboot
or if path is set directly..
Via phone Terminal Emulator
Take the recovery.img that you want to flash and place it on your sd card ( eg /sdcard/(*here*) )
Begin Terminal emulator app (*Download from playstore*)
Type su (*enter*)
Allow superuser permissions (*enter*)
Note : Now you must get a line beginning with $
Enter
Code:
flash_image recovery sdcard/recovery.img
Still racking your brains over this ? Check out post 3 for video tuts !
For kernels do the same thing except replace replace Recovery.img with Boot.img
Setting permissions
Heard about setting permissions ? Ever wondered what they are ?
On a UNIX based system, every single file and folder stored on the hard drive has a set of permissions associated with it, which says who is allowed to do what with the file. Every file (and folder) also has an "owner" and a "group" associated with it. If you created the file, then you are usually the owner of that file, and your group, or the group associated with the folder you created the file in, will usually be associated with that file.
Click to expand...
Click to collapse
So how to configure them ?
You need a file explorer with Root access
Go to the required folder/app you want to set a permission and long press on it ( in most file explorers )
You will get something like this:
{
"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"
}
Select what is required and close.
Alternative via adb
Same as before from adb directory on cmd propt / terminal
Code:
adb shell
su
chmod 777 /system/app/Notes.apk
INDEX :
r = read w = write x = execute
Reference for chmod
So 777 = rwxrwxrwx 755 = rwxr-xr-x and so on and so forth..
What is overclocking ?
Overclocking is the process of making a computer or component operate faster than the specified clock frequency by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking")..
Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable.
Pros : You get much more performance including gaming performance and overall UI performance..
Cons : Overclocking is always risky if something is configured improperly and may also result in permanent damage of your hardware. As long as it is done safely you are good to go.
You may see some increased power consumption.
Extreme overclocking might kill your hardware.
Undervolting :
The process where you provide less voltage to your cpu rather than the stock voltage.
Advantage:
Reduced heat from your device.
Good battery life.
Disadvantage:
Extreme undervolting will make your device unstable and some times even end up with a boot loop.
Recovering from an OC NAND Wipe..
cute_prince said:
Ok guys, here I am posting NAND Recovery Procedure:
Download the following attachment.. Rename flash_erase.txt to flash_erase ( Its actually a binary file )
Copy this file to /system/xbin directory using Root Explorer. Set permission as 755
Make sure Root Access is enabled for both Apps and ADB in Developer settings
Connect phone to PC .. Now open a terminal ( I am using Ubuntu ) and type the following:
Code:
[COLOR="Blue"]adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0[/COLOR]
Note: when you execute above command you may get an IO error.. Its OK, dont get panic
Now disconnect phone from PC.. Remove battery and reinsert it ..
Goto recovery and:
format /boot
format /system
wipe data / factory reset
Now install your favourite ROM
Once the ROM is booted, goto storage settings.. Everything should be fine now and you should get around 140MB free depending on your ROM
Click to expand...
Click to collapse
What is md5 ? How is it useful?
The MD5 Message-Digest Algorithm is a widely used cryptographic hash function that produces a 128-bit (16-byte) hash value. Specified in RFC 1321, MD5 has been utilized in a wide variety of security applications, and is also commonly used to check data integrity. MD5 was designed by Ron Rivest in 1991 to replace an earlier hash function, MD4. An MD5 hash is typically expressed as a hexadecimal number, 32 digits long.
What does it mean in english ?
For android basically it is used to maintain the uniqueness of a file. It is also used to check wheter the file is the same file that has been uploaded or not .. or wheter the the downloaded file is half downloaded or broken..
You can check the md5 sum of two files. If they match then they are the same file. If they dont .. back to your download screen.
How do I check the md5 sum ?
On windows :
Download this and extract it on your pc..
Just put in the file's location..
Get the md5 sum from the OP
Match them ..
On android
There is an app for it : Android Filve Verifier

Video Tutorial # 1 : How to flash any recovery thru terminal emulator ! By Rishik
Video Tutorial # 2 : How to take a backup of your system! By Rishik
Please thank him for it.. HERE !
Credits : bala_gamer, cute_prince , Genexus , Rishik999, wikipedia , sdk , many tutorials on xda and other forums... and google.

Re: [GUIDE] How to install sdk / adb and do a logcat
Wrong section post in general this isnt any development
Sent from my HTC Explorer A310e using xda premium
---------- Post added at 12:03 PM ---------- Previous post was at 12:01 PM ----------
Mods move this to general!
Sent from my HTC Explorer A310e using xda premium

I knew this was coming .. It is in many development sections even for my old device Sensation. Trust me it is needed in the development section. Mods are free to move it.. Even mentioned it in the first post.. as good as a guide on rooting the pico or even compiling a kernel. Dont you think ?
If you think the people actually read the general section why would the dev thread be full of so much spam ? :silly:

good..nice..
i think this will work on win 7 also??
and give a tut for linux too...if you want i can post one here!!

Adding a lot.. Even video tuts.. if possible..

Video Tutorials
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!

Re: [GUIDE] How to install sdk / adb and do a logcat
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app

Re: [GUIDE] How to install sdk / adb and do a logcat
KiranP23 said:
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app
Click to expand...
Click to collapse
Yeah was about to add it soon...
Rishik999 said:
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!
Click to expand...
Click to collapse
Adding them bro thanks a lot .. I'll pm you
Sent from my HTC Explorer A310e using xda premium

logcats
Thanks a lot OP for making this noob friendly guide!
This really helped me,in getting logcats ..Where first I use to scratch my brains
Such guide will definitely gonna boost up development ! As there would less of noobish post! :victory:
Please,add as much as u can in these guides! :good:
U can still add on ..How to read logcats?
Anyways,I found it really helpful!

Re: [GUIDE] How to install sdk / adb and do a logcat
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium

Re: [GUIDE] How to install sdk / adb and do a logcat
akshat.shenoy said:
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
This will be very helpful if u add meaning of those codes

sometimes after doing the instructions given in your tut for linux adb still returns
HTML:
List of devices
???????????
im on linux mint nadia and this did happen to me
so we need to setup device rules..and because we might use another android phone also its wise to add all the rules, so:
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
and akshat we need to make bashrc also executable..

Re: [GUIDE] How to install sdk / adb and do a logcat
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app

akshat.shenoy said:
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
i aint that much of a genius...but thanx bro
check ur pm..
didnt put all that here because it would have crowded the thread..!

Edited first post .
Changed entire Linux guide for installing sdk tools.
Added a small bit of info right at the end.

Reading logcats (basic)
http://forum.xda-developers.com/showthread.php?t=1378491
I guess this can be helpfull for noobs like me xD
This one is perfect
http://developer.android.com/tools/debugging/debugging-log.html
Real S**t xD

akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!

gnexus said:
akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!
Click to expand...
Click to collapse
They should understand that at least I guess..
still will include thanks..

Rooting generic tablet using ubuntu and adb?

Hi guys, First post here, really looking forward to learn more about android .
I'm trying to root a generic tablet (titan pc008) using linux and ADB.
The thing is when i connect the tablet and run adb devices it doesn't get listed.
So i guess i need to install some sort of generic driver or something but i've very superficial knowledge about rooting and android tinkering in general.
I've already tried killing and restarting the adb server
The lsusb output for my device:
Code:
Bus 002 Device 004: ID 2207:0000
Added this line to the file "/etc/udev/rules.d/99-android.rules":
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", ATTR{idProduct}=="0000", MODE="0666", OWNER="user"

Hi guys.
I kept on googling and finally found a was to set up adb for this device on stackoverflow by Mateus Sousa Mello
I had same problem as you, what i done: Added vendor id to ~/.android/adb_usb.ini
echo "0x2207" >>~/.android/adb_usb.ini
Added the following lines to /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="207/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="207", MODE="0666"
Now my chinese tablet Archos c906 is recognize on ./adb device as:
List of devices attached
0123456789ABCDEF device
Click to expand...
Click to collapse
I hope this might help someone in the future.