More Closer about ADB ( For Dummies )

Before you read down about How To ADB for newbie, lets take a little review. If you want hack your ADB, you need know what is ADB and how to took closer about this ADB

Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or 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.

When you start an adb client, the client first checks whether there is an adb server process already running. If there isn’t, it starts the server process. When the server starts, it binds to local TCP port 5037 and listens for commands sent from adb clients—all adb clients use port 5037 to communicate with the adb server.

The server then sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. Where the server finds an adb daemon, it sets up a connection to that port. Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections. For example:

Make sure that debugging mode is checked in your G1 Settings, if not ADB will not work.

Supported Operating Systems:
* Windows XP (32-bit) or Vista (32- or 64-bit)
* Mac OS X 10.4.8 or later (x86 only)
* Linux (tested on Linux Ubuntu Dapper Drake)

Section 1: Pre-reqs

System Requirements

Android 32/64 bit Windows USB Driver
*NOTE*
The USB driver for Windows provides support for the following Android-powered devices:

•T-Mobile G1* / ADP1
•T-Mobile myTouch 3G* / Google Ion
•Verizon Droid*
* Or similar hardware on other carriers

Any additional devices will require Windows drivers provided by the hardware manufacturer.

Android SDK

Older Releases *Most likely don’t want this one*
Android 1.5 Platform
Android 1.6 Platform
Android 2.0.1 Platform *Also Located below*

*Newest Builds*

Windows

Mac OS X

Linux i386(x86/32-bit)

*Please note that I am using Vista Ultimate x64 SP1*

Section 2: Where does it all go?

*UPDATE*

Linux users wanting to know how to install/run the Android SDK can check the 2 links below for more info. Thanks to xyrcncp for these links.

Downloading
http://developer.android.com/sdk/1.1_r1/index.html

Installing
http://developer.android.com/sdk/1.1_r1/installing.html

And thanks to tubaking182 for giving us some more commands to use for all the linux users.

You can download it and: (corrected thx to @austinkyle)

You should be able to run the adb commands from any directory

Not too hard to cd to the correct directory but i personally don’t like to type:

And again, thanks to mark925 for his input:

“Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt.”

Now that you have all the essential files you need to run “adb”, let’s get started shall we?

First off you want the make note of where you downloaded the ADB Android Driver and the Android SDK. Both of these files are zipped and will need to be extracted before they can be used. Windows vista has “.zip” extracting built-in and does not require an external app.(I have listed some links below)

Use the links below to install a 3rd-party compression/extraction app:

7-zip 4.65 32-bit

7-zip 4.65 64-bit

(If you do not know how to install a windows executable file, please kill yourself now! )

OK, now it’s time to move our extracted ADB Drivers and Android SDK to a better location(preferably the root of C:\).

- Right click on the extracted folders(android_adb_usb_driver or android-sdk-windows-1.1_r1) and select copy(or Ctrl+C)

- Now navigate to the root of your primary hard-drive(C:\) and right-click then select paste(or Ctrl+V)

After we copy both of our newly extracted folders to our (C:\) drive we now have to install the USB drivers.

- Connect your G1 to your PC using the provided USB Cable or just a plain ole 6-pin to 4-pin usb cable… (I prefer to use one with a ferite core)

DO NOT MOUNT YOUR G1 TO YOUR PC FROM THE G1 NOTIFICATION WINDOW!

- When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android_adb_usb_driver) and install the adb driver.

- Now that windows knows what the G1 is let’s get started learning how to run adb shall we?

Section 3: Running ADB from Command Prompt

Running Command Prompt:

Windows XP: Select Start or Tap the Windows Key on your Keyboard, select “Run” and type “CMD” then hit “Enter”.

Windows Vista: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type “cmd” then hit “Enter”.

- Also, Mikey1022 has reminded me to add the “ADB” directory path as a system variable in windows…

To do this right-click on “My Computer” and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.

Click “New” under System Variables and add the following:

Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools

Now your are in a command prompt! Everybody DANCE!!!

From the command prompt we must navigate to the adb executable within the android sdk. You can find the adb executable in the tools folder within the android sdk.

Let’s point our command prompt to the tools folder now:

Ok, now that you know how to initiate an adb command let’s try one shall we?

Remember, we are still in the command prompt and in the /tools folder within the android sdk….