Database Users

[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)

Ok, so I'm going to make a little write up on how to easily install ADB and fastboot on a Mac. It's actually quite simple, and plus you don't have to worry about drivers like in Windows.
Instructions
First, make a folder named "android" (no quotes of course ) You can place it anywhere on your hard drive, it doesn't really matter. Put it somewhere you'll easily remember, because you're going to be using it a LOT. I placed mine on my desktop.
{
"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"
}
Next, you'll want to download the android SDK from Here. (you won't need to install Java first like you would on a Windows PC, though I would recommend it anyway)
(As pointed out by Wlmeng11, you could skip this step just download a zip that I will have attached at the bottom of the page containing the adb and fastboot files instead of downloading the whole SDK)
When the SDK finishes downloading, Unzip it and the contents of the "android-sdk-mac_x86" folder into your android folder.
Once you have done that, open your android folder. Go into the tools folder inside of it. Double click on the file called "android" (possibly called android sdk) This file is a UNIX executable and will open within a Terminal window.
When it finishes opening, check the folder called tools. Make sure both "Android SDK Tools" and "Android SDK Platform-tools" are selected within the tools folder. Click install and wait for them to download.
When they finish downloading, go into the platform-tools folder inside your android folder, then copy adb and fastboot and paste them into the root of your android folder.
Now that you have adb and fastboot installed, we're going to want to test them to make sure they work.
Go ahead and plug in your android device at this time. Make sure android debugging is enabled in settings. Go into Settings > Apps > Developer and check it there (for Gingerbread 2.3 and lower) or go into Settings > Developer Options and check it there for Ice Cream Sandwich or Jellybean. As of now, there are two ways to access adb and fastboot.
Open a Terminal window (look in Applications > Utilities if you can't find it). Type "cd" followed by the path you saved your android folder to (I'm going to use the Desktop for this demonstration) it should look like this
Code:
cd /Users/<yourusername>/Desktop/android
Press enter.
Now you need to actually execute an adb or fastboot command. To do this, you'll need to type "./adb (or fastboot) <command>" For this tutorial, we will use "ADB devices" since it doesn't actually do anything to the phone. (we won't use fastboot since it requires rebooting to the boot loader which is different for every device)
In the same terminal window as before type the following:
Code:
./adb devices
then hit enter. It should turn up your device's serial number. If it does, proceed to the next step, if not recheck your steps, then leave a post in this thread.
(if it says * daemon not running. starting it now on port 5037 *
* daemon started successfully * that is perfectly normal)
Now, at this moment, ADB and Fastboot are both completely useable. However, it's very annoying to have to CD into the directory and use ./ in front of every terminal command. I'll show you how to add it to your path so you don't have to do any of that.
Open a new Terminal window and type
Code:
nano ~/.bash_profile
it will open a window that looks like this:
(Yours will probably be blank, because I've added a lot of stuff to mine over the years)
Add a line to it that contains the path to your android folder. (again, I'm using Desktop) It should look like this
Code:
export PATH=${PATH}:/Users/<yourusername>/Desktop/android
Once you have added that, press CTRL+X to exit, then Y to confirm the save then press enter. It will close the nano editor. You can close the Terminal window now.
Now we need to verify that it works. Open a new Terminal window and type
Code:
adb devices
If it shows the serial number, then you have set it up successfully and are good to go!
If you have any questions or issues let me know in the thread below.
If this has helped, please press thanks!
Awesome! This made the front page of XDA Thanks guys!​

Added screenshots

you won't need to install Java first like you would on a PC
Click to expand...
Click to collapse
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw

wlmeng11 said:
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw
Click to expand...
Click to collapse
Lol I'll fix that. Thanks btw. I'm out today, but I'll give you one tomorrow (too lazy to use my phone)

To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound

wlmeng11 said:
To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound
Click to expand...
Click to collapse
Maybe, I actually use other parts of the SDK . Ill look into that though

AshtonTS said:
Maybe, I actually use other parts of the SDK . Ill look into that though
Click to expand...
Click to collapse
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.

I still prefer linux
I still prefer the linux enviroment, although its handy to have the adb on my macbook for when I'm not at home and have bricked my device :S
I had already got this setup, I just didn't know the ~/.bash_profile bit Now I know had to add my own programs as actual programs and not just aliases XD

First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.

Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.

wlmeng11 said:
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.
Click to expand...
Click to collapse
Indeed, though this method allows you to update your adb and fastboot via Android SDK Manager (ASM). Also, in cases where all you need is adb and fastboot, you can speed up future update checks by going to "Tools"->"Manage Add-on Sites..." in ASM and click on "Disable All" button in "Official Add-on Sites" tab. From there on Android SDK Manager will check only the default repository containing tools and APIs.

visor said:
First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.
Click to expand...
Click to collapse
It could be done that way, but I personally put other stuff in the android folder on my Mac, and also it's a bit quicker to just drag a file into one folder on your desktop than into a folder within a folder

straycat said:
Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.
Click to expand...
Click to collapse
You won't be able to install the SDK, but you can extract the android.zip to a folder named android on your desktop or wherever and use that in place of the SDK step

AshtonTS said:
You bet! this will work on any mac running any OS X (unless Google blocks the install of the SDK, but I have a way around that.
Click to expand...
Click to collapse
Actually, that's a PowerPC Mac, so Intel OSX software will not work.
There is no official support for PowerPC that I know of, but someone on XDA did make binaries for PowerPC.
Sent from my HTC Rezound
Edit: yup, official sdk is x86 only.
BTW, here's the link to the ported binaries.
http://forum.xda-developers.com/showthread.php?t=898744

So many graces, this thing has saved the life because I have not a PC windows, thank you still

varanhia said:
So many graces, this thing has saved the life because I have not a PC windows, thank you still
Click to expand...
Click to collapse
Glad it worked for you

Hi,
Thank you very much. Worked like a charm.
Regards,

Awesome thread. Thanks for taking out the time

DarkSorcerer said:
Hi,
Thank you very much. Worked like a charm.
Regards,
Click to expand...
Click to collapse
nigameash said:
Awesome thread. Thanks for taking out the time
Click to expand...
Click to collapse
Glad it helped you two
Sent from my HTC Sensation

Hi thanks so much for this. Ive been wanting something like this for months/ almost a year.
All the other guides didnt work for me, but this was simple and easy to follow.
Ive encountered one problem and its device specific. My nexus 7 tablet works great with adb, but my htc evo 4g lte doesnt. its rooted, and running cm 10 4.1.2. its debugged any idea how to make it see the device?
UPDATE. so i turned on my usb storage on the device and it now sees the phone. Great work!!!!
Am i going to have to connect storage to mac all the time for this to work on any device?

[Tutorial] How to install Android SDK tool & HTC's drivers [BEGINNERS FRIENDLY]

[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]​
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.​
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
{
"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"
}
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!

Nice guide
Very concise

Lucky Thirteen said:
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]​
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.​
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!
Click to expand...
Click to collapse
This works fine on windows 8 I needed that for my HTC Desire C and I managed to do with this! Thank you!

I didn't know about that shortcut. Very nice.

:good:
Why isn't that driver link in a stickied thread?? Solved my connectivity issues.

Rooting My Htc Desire C
I need to know How to root my HTC DESIRE C ,like this beginner friendly method.Many websites are showing different ways to do it and some ways didn't work for some people iam afraid my phone becoms a brick.so please help xda developers.
And this helped a lot....Thank You So Much

I have the HTC One for AT&T, I have the drivers installed and everything works fine when the phone is powered on I can transfer stuff back and forth easily. Although as soon as I boot my into the bootloader and select the fastboot and fastboot usb and when I run my adb devices in the CMD it comes up blank under the devices connected with several cables in all 4 usb ports. What is wrong? Help please

this helped me thanks. I followed everything to the tee. I only had a problem with changing the .txt to.bat extension however in notepad choosing save as and adding ".bat" in quotation marks allowed me to change the file extension

What an awesome tutorial! Thank you very much flawless!!! :good:

can you delete the android-sdk folder once everything is finished?

please ppl can u upload sdk for me ? i can not do it , iran is banned from google . just one developer man
here is my requested thread
http://forum.xda-developers.com/and...k-23-0-5-android-l-api-21-api-20-api-t2915318

[WIN][TUTORIAL]HOW TO USE ADB,DDMS AND TAKE A LOGCAT {pictorial explanation}

{
"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"
}
HOW TO USE ADB , DDMS & TAKING AN LOGCAT ..etc​
THIS GUIDE HAS BEEN FEATURED ON XDA-PORTAL :highfive: .....still any doubt about this Mind blowing guide ?? ​​
WHAT IS ADB???​
EXPLANATION ​
Whenever you create an android app or when you develop an Rom , it is important that you must deliver GOOD QUALITY APP or ROM , that are rid of Bugs ..Eventually you might come across a situation when your APP or ROM isn't working or it is bricking the device or some things are not working .These situation can be tackled only with a proper debugging tools ..So ADB ( android debug bridge) is a powerful Debugging tool and a tool which allows us to step through each line of code and examine the value of each variable.It offers us some of the powerful tools ..Debugging is not a big deal for the people who come from a JAVA programming background .Dalvik VM in android supports java debug wire protocol to attach to the device over ADB
Click to expand...
Click to collapse
ADB​ADB or ANDROID DEBUG BRIDGE is a command-line utility that is often used to communicate over the debug channel with a connected phone or virtual device (emulator). ADB can control your device over USB from a computer, copy files back and forth, install and uninstall apps, run shell commands, and more...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
SETTING UP ADB :- ​
1) Install Java JDK :-​Before installing the Android SDK, you’ll have to install Oracle’s Java development kit. You can download it from here...(click me !!)
Even if you already have the Java runtime (JRE) installed, you’ll need to install the JDK as well.
After installing Java JDK , you can now download the Android SDK from Google .
NOTE:- If you see a any type of Java-related error during installation, then download and install the x86 version of the JDK, not the x64 one ..
Click to expand...
Click to collapse
2) Installing android SDK:-​Download Android SDK from here...(click me !!!)
After clicking on "DOWNLOAD FOR OTHER PLATFORMS" , you will get an extended menu ..
After downloading the .exe file , then Double click on the .exe file and install it in C:\ Drive or on whichever drive you wanna install .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3) Android SDK Setup
Click to expand...
Click to collapse
Once the Android SDK is downloaded and installed, launch the SDK Manager application from your Start menu.
Enable the Android SDK tools and SDK Platform-tools checkbox and click the Install button. This downloads and installs the platform-tools package, which contains ADB and other utilities.
After installing these packages , Go to the place where you installed ANDROID SDK . IN MY CASE , IT IS :-
Code:
C:\Program files(x86)l\Android\android-sdk\platform-tools
If you used a different install location, you’ll find ADB in the platform-tools directory,inside your ANDROID-SDK directory .
Browse to platform tools and hold Shift and right-click inside it, and select Open command window here...
Click to expand...
Click to collapse
​
NOW YOU WILL SEE THIS :-
Note :- To use ADB with your Android device
1) you must enable USB debugging on it. You’ll find this option under Developer Options on your device’s Settings screen
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2)You must install your device drivers :- Individual OEM USB drivers for windows are available for each manufacturer and are listed in the official document ..
After you have downloaded you device drivers, then we have to install on our pc. for that :-
a) connect the device to the computer
b) right click on MY COMPUTER and click manage
c) go to devices > other devices and right click on device and select update driver software.
d) you should see an option to " BROWSE MY COMPUTER FOR DRIVER SOFTWARE" , which you nedd to click on and point to the location of your device driver installation file..​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
​
To test whether ADB is working properly, connect your Android device to your computer using a USB cable and run the following command:
Code:
adb devices
Now it will show the devices connected
Now you have sucessfully installed ADB and now we are good to go further..​
WHAT IS A LOGCAT :-​
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
TAKING AN LOGCAT :-
Now type this in the terminal
Code:
adb logcat -v long > logcat.txt
or
Code:
Code:
adb logcat > logcat.txt
you shall have a log file called name of logcat.txt inside your ADB folder.
SOME OF THE USEFULL ADB COMMANDS :-
Code:
adb install C:\package.apk
– Installs the package located at C:\package.apk on your computer on your device.
EG -adb install G:\xda.apk
Click to expand...
Click to collapse
Code:
adb uninstall package.name
– Uninstalls the package with package.name from your device.
EG :- you’d use the name com.quoordy.xdadevelopers to uninstall the Xda developers app.
Click to expand...
Click to collapse
Code:
adb push C:\file /sdcard/file
– Pushes a file from your computer to your device. the command here pushes the file located at C:\file on your computer to /sdcard/file on your device .
EG :-adb push G:\system\framework\framework-res.apk /system/framework
Click to expand...
Click to collapse
Code:
adb pull /sdcard/file C:\file
– Pulls a file from your device to your computer – works like adb push, but in reverse. EG :-adb pull /system/app G:\rom\system\app\
Click to expand...
Click to collapse
Code:
adb logcat
– View your Android device’s log. Can be useful for debugging apps.
Click to expand...
Click to collapse
Code:
adb shell
– Gives you an interactive Linux command-line shell on your device.
Click to expand...
Click to collapse
Code:
adb shell command
– Runs the specified shell command on your device.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
doctor_droid said:
When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \\sdk\platform-tools [Hit ENTER!]
C:\\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
Click to expand...
Click to collapse

WIRELESS ADB​
1. ROOT IS NECESSARY !!
2. Enable USB debugging.
3. Install Wireless ADB from the play store
4. Activate it .
5. In your computer, open a command line (cmd.exe for windows), go to ADB's directory and type:
Code:
adb connect 192.168.0.3:5555
Keep in mind that the port (the :5555 part) is optional, the 5555 is the default one, usually you don't need to change it, unless you're using it
6. That's it ..!!
credits: @El_Dark
FAQ TO BE ADDED SOON .....

DDMS
The Dalvik Debug Monitor Service (DDMS) as it is known is one of the application debugging tools that must be a part of every ANDROID app developers's toolkit..This is very very useful to the app developers.Its is a very powerful debugging tool environment and offers various unparalleled debugging features like heap information , logcat monitoring , file manager.It is available by default in ECLIPSE IDE environment or even in the ANDROID SDK.It works on top of ADB for device communication..
DDMS can be stated as a standalone application as part of ANDROID DEVICE MONITOR.The Android Device Monitor is a standalone which can be used in case you do not use the eclipse development environment , though the integration with Eclipse is something that other IDE'S could be envious of.​
HOW TO USE DDMS ??
1)AS EXPLAINED IN THE ABOVE POST , INSTALL ANDROID SDK....AFTER YOU HAVE INSTALLED PLATFORM-TOOLS & SDK TOOLS..NOW GO TO ANDROID FOLDER AND OPEN TOOLS
2)NOW RUN MONITOR.bat AS ADMINISTRATOR
3)NOW ANDROID DEBUG MONITOR WILL APPEAR ..
Now let's learn about its components and it's use's
DDMS VIEW COMPONENT'S :-​
DDMS offers a set of view components , each of which show relevant information related to the connected Emulator.
DEVICES :-
The device panel shows the details of each process that are running in the connected device.There are various operations that can be performed from this panel.
Each of the icons present in this panel performs the functions as follow's :
Debug Process Icon :- It show's the state of connection of the debugger.
Update Heap :-Clicking on this enables Heap information for the process so that we do not have to do memory deallocation manually.
Dump HPROF :- Generates a Heap Dump , useful for tracing memory leaks in your app.
Cause GC :-Invokes the Garbage collector to collect heap data.
Update thread :-Show's the information about the running thread in the thread tad for selected process
Start Method Profiling :- Tracks the metric's related a method. It collects information like the amount of time taken to execute a method,number of calls.
Stop Process :-Stops the currently selected process.
Screen Capture :- Takes a screenshot of whatever is displayed on the screen.
Reset ADB :- Ast he name suggets,it resets ADB.
THREAD'S :-​The thread tab on the right of devices view shows informatiom related to the thread for each process selected in the devices view.The information shown can described as follows.
ID :- A unique ID assigned to each thread dby Dalvik V,, which are only odd numbers that start from 3 .
Tid :-The linux thread associated with each thread , ehich matches the process ID for each main thread in a process.
Status :- Status of the thread in VM , out of daemons are marked with an asterix.other values can be among running?sleeping/init/starting.
HEAP​ :-
the heap view show a information and statistics about memory heap .To view heap usage,follow these below steps
From the devices view,select the process for heap usage which has to be examined.
click on update heap
From heap Tab , select Cause GC to enable collecting heap data
Everytime you need to update your heap statistics.This will show you the amount of memory allocated to each
ALLOCATION TRACKER​The allocation Tracker show a real time information about allocation happening in the application over a certain period of time.To enable allocation Tracking.
[*]select the process to be tracked from device panel
[*]click on start tracking from allocation tracker tab.
[*]perform any actions on the devices or emulator that you want to be tracked.
[*]click on Get Allocations objects, since tracking was enabled .
NETWORK STATISTICS​ ;-
The network tab allows you to track and optimize the amount of network data your app is using.It even allows you to tag network sockets so that you can differentiate between types of data .It will indicate the speed and amount of data received /transmitted ..
EMULATOR CONTROL :-​One problem with testing Android devices using an emulator or developer device is the fact that it is unable to examine the performance of the app in the reak world conditions . like call or SMS is received/sent or when a particular location is reached.To be specific the emulator Tab allows you to to emulate the following real world conditions :
Telephony Status :- the following options are available to set the status of phones network.
Voice :- unregistered,home,roaming,searching,denied.
Data :- unregistered,home,roaming,searching,denied.
Speed :- Full,GSM,HSCSD,GPRS,EDGE,UMTS,HSDPA.
Latency :- GPRS,UMTS
Telephony Actions :- Telephony actions allow you to spoof the network.
Location Settings ;- Emulator control allows you to sppof the location
FILE EXPLORER :-​As the name says it lets you view the directory and file structure if the device and lso easily copy files to and from the emulator so as to enable easy data transfer in a manner similiar to ADB or ADB pull command.
SYSTEM INFORMATION :-​As the name says , it give's us the particular information about the GPU load , CPU load....
DDMS HAS ALSO AN INBUILT LOGCAT VIEWER :-​
​
Happy Developing and learning ​
CREDITS ;-
Google inc.
@iamareebjamal
@Nabs Zains
@amogh420
@srt99
@Maxx247
@iamareebjamal
@El_Dark
@doctor_droid
@CharsiBabu
@lokeshsaini94
@hellraiser
@Zeuscluts
@Partimus.prime
@Lifehacker7
if i forgot you , just PM me .. i will be very glad to add it ..

How to Remount system partition as R/W
Go into Platform tools which can be found in your Android folder..
Hold shift button and right click ..Select "open cmd window here" in the pop-up window ...
first type
Code:
adb shell
Get Root Privileges ..
Code:
su
then type
Code:
mount grep system
and then you'll get
Code:
mount grep system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Here fill the above command with neccesary system partition,appropriate device path and mount point ..Like
Code:
mount -o rw,remount -t yaffs /dev/block/stl12 /system
This is how it looks :
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# mount grep system
mount grep system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#

nice one added to Guide Ride

Excellent guide! :good:

:laugh: COOL finnaly i found some tutorial
thx :good:

Nice guide. But you may wanna fix the problem.txt bit in the logcat part. It should be logcat.txt.

Thank you to you all ,for showering me with you best wishes.
sgt. meow said:
Nice guide. But you may wanna fix the problem.txt bit in the logcat part. It should be logcat.txt.
Click to expand...
Click to collapse
i will edit , just a second .thnk you for you little help.

nice guide bro...very good work...:good:

That's weird I posted a reply but it didn't actually post it on the forums, this should help a lot of new comers that have never really had a tut that explain ADB , even the more advanced users miss simple things.
Sent from my SGH-M919 using Tapatalk 4 Beta

can make a guide for Wireless ADB?

My device doesnt show up in the list....i do flashing on this system and everything else

Excellent guide. thank you. I was always under the impression that eclispe needs to be install to get ddms coz I saw ddms when I installed eclipse 2 yrs back. Good to know we can do it without eclispe.
Thanks alot.

shift + right click
ok when i click shift + right click i dont get to open a cmd window help.
My computer
Microsoft windows xp
media center edtition, version 2002, service pack 3.
I was reading this but i got no where.
http://forums.majorgeeks.com/showthread.php?t=214139&goto=nextoldest

ravvio said:
My device doesnt show up in the list....i do flashing on this system and everything else
Click to expand...
Click to collapse
please reinstall the drivers... and restart the computer.
if it still doen't work . follow this thread : - click me ..!!
don't download any firware from there,they aren't for your device .. just try what it is said there .. !!
mattoaida said:
ok when i click shift + right click i dont get to open a cmd window help.
My computer
Microsoft windows xp
media center edtition, version 2002, service pack 3.
I was reading this but i got no where.
http://forums.majorgeeks.com/showthread.php?t=214139&goto=nextoldest
Click to expand...
Click to collapse
Are you sure.. ??

-MR.WORLDWIDE- said:
please reinstall the drivers... and restart the computer.
if it still doen't work . follow this thread : - click me ..!!
don't download any firware from there,they aren't for your device .. just try what it is said there .. !!
Are you sure.. ??
Click to expand...
Click to collapse
Yes I am 100% sure, even read that article and can someone else running windows xp try shift right click
Sent from my SGH-T959V using xda app-developers app

mattoaida said:
Yes I am 100% sure, even read that article and can someone else running windows xp try shift right click
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Same here

EXCELLENT POST! This will come in very handy. Thank you.

mattoaida said:
Yes I am 100% sure, even read that article and can someone else running windows xp try shift right click
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
vladimirheroj said:
Same here
Click to expand...
Click to collapse
Sorry guys i can't help you ...i don't know what's with that WINDOWS XP ..Please wait for some time,i will see if i can get some help for you both guys .
Thank you,
-MR.WW-

[ TOOL ][ SYSTEM | NORMAL ][ APP-MOD-MAKER ] Juno - 1.6 [divinemamgai]

{
"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"
}
New Version Out! - 1.6
Juno utilizes the features of a program called APK – Tool, and pushes it to another level, the level of ease! Now even if you are not aware of what is required to create fully functioning system apps for your Rom or Device, you can still make some pretty basic mods with this tool, OR you can go pro and create some pretty awesome mods! (Well for that you will need to know how to edit smali files and other xml files of system apps properly)
With this tool you easily Pull system apps from your phones /system/app directory and start editing them. Once done you can easily build the modified version of the system app and can instantly install them to your phone!
(Please refer to the section How to use? Before doing anything idiotic.)
Once done you can also get cleared of all the residual files too with just one single command.
At last I want to state this with all caution – You are using this tool on your own risk! Any damage done to your device is completely your fault and I’m not to be blamed for any kind of damage done to your device.
​
Step - 1 : Setting Up your PC!
Download The following resources first:
Android SDK [ Draw-Patch.9 Tool ]
Java SE Run-time Environment 7 [ Java Dependencies For APK - Tool ]
Now let's begin setting up your PC,
Install the above mentioned programs.
Go to Advanced System Properties.
It looks like this:
Go to Environment Variables, then create a new System Variable, having name JAVA_HOME and value as the path where you have installed the JRE.
It looks like this:
Now after creating the JAVA_HOME variable, search for Path system variable in the System Variables list. Now this is a bit tricky. Once found click on it and then on Edit. Move the cursor to the end of the string till you see ";" (without quotes), add the path to your JRE bin folder just after it.
It looks like this:
OK, so if everything went fine and just as what instructed then you are all good to proceed to Step - 2!
Step - 2 : Installing Juno!
First download the zip provided at the download section of this post, then extract it and execute the Juno.[Current-Ver].exe (eg. Juno.1.1.exe) setup file.
It looks like this:
Now click Next. In the next window if you want to change the directory of the Juno then just press Browse and choose your custom directory. If done click Next.
It looks like this:
In the next windows just press Next, and let the program to be installed on your PC!
It looks like this:
In the preceding window click on Run Juno if you want to execute the program now or just press Finish.
It looks like this:
Step - 3 : Setup the Program!
Open the program, Juno, from start menu or from the directory itself.
Please open the program in Administrator mode, by right clicking and selecting Run As Administrator. This is necessary for ADB and APK - Tool to work properly.
Note: If you have installed the program in a Drive which is not protected by Administrator Rights, then you can skip running it as Administrator.
It looks like this:
Now first enable USB - Debugging in your phone and connect it via a USB - Cable to your PC [ If you have any doubt on how to do that please refer to screens below. ]
Need help?:
In the Juno program console enter the command LOADRESOURCES and press Enter. Then enter PULL and press Enter and sit back and relax till the program loads all the necessary Resource files from your device.
It looks like this:
The Juno program usually only pulls and installs the Resource files of CM based roms automatically and also for the Xperia Stock roms. So if you are using any of those then just skip the preceding steps.
But for other Roms or Phones the developers will need to extract the required resource files from their devices or roms. For that follow the preceding steps:
Extract the required Resource files in to the main directory of the program. This can be done by using PULL command of the program or by manually retrieving required files.
Then while in the program, enter LOADRESOURCES, and then enter CUSTOM.
Enter the File-Name of the Resource file you just copied to the main directory. (Only the file-name no extensions!) And press Enter.
Now let the program complete the process, if you see no errors then everything has been completed just fine.
Now repeat the same with all the other Resource files.
Need help?:
If all the above mentioned steps have been completed successfully, then your program copy is ready to be used!
​
From Version 1.3, the How to use guide will be included with the program,i.e, in the form of Read Me.
Copy the apps you want to mod in the pulled directory of the program, if you want to do that manually, but you can even pull apps from your device using PULL command.
But for lower functions please refer to the section below.
The following section is going to cover all the functions supported by this program.
Legend - Function-Name [ Function-Code ]
Just enter the Function-Code given for each defined function below in the program to start that function.
Load Resources [ LOADRESOURCES ]
This function will allow you to load the necessary resource files which are needed by the APK – Tool to decompile the required system apps.
The sub-functions which this section includes are –
PULL – This function is for pulling the required resources straight from your device. [Note: It will only efficiently work for CM based or Stock Xperia roms and for other roms please use the sub-function CUSTOM]
INSTALL – This function will install the resource files automatically which you have copied in the res directory of the program. [Note: It will only efficiently work for CM based or Stock Xperia roms and for other roms please use the sub-function CUSTOM]
CUSTOM – This function is to be used when you require to install extra resource files of your rom. You have to provide the file-name of the custom resource file which you have to copy or pull from your device to the root directory of the program. And it will be automatically installed.
Mod [ MOD ]
This function allows you to mod your system apps. You have to enter the file-name of the system app which you have copied to or pulled to the root directory of the program. The program will automatically decompile or compile depending on the fact that what has already been done.
If the app is not compiled, then the program will first make a backup of the system app [Note: Please do not delete the backup folder under any circumstances as it may lead to false build, which will damage your device!]
Then the program will decompile the app and it will be available for the user to mod it in the working directory of the program.
If the app is already decompiled then the program will compile the edited app (irrespective of the fact that it has been edited or not.) and will generate a complete build in the build directory of the program, which will be ready to install to your device, keeping in mind that no error has occurred.
Delete [ DELETE ]
This function is used to get rid of the residual files after your entire project has been completed.
This function will delete the working folder and the backup folder without prompting, whereas the Main app file and the Build app file deletion will be prompted.
You just have to enter the file-name of the app you want to get rid of, and rest will be handled by the program itself.
Pull [ PULL ]
This function is used to pull or get the system apps from your device. But for that your device must be connected in USB – Debugging Mode.
You just have to enter the file-name of the app you want to pull or get from your devices /system/app/ directory. The app will be stored in the root directory of the program.
Install [ INSTALL ]
This function will let you install the build app to your device. But for that your device must be connected in USB – Debugging Mode.
You have to enter the file-name of the app you want to install. The app must have to be built to be installed.
Restart of the device is mandatory right after you have installed the app.
Exit [ EXIT ]
This function will exit the program.
​
Current Version - Juno.1.6
Download Juno -
Juno.1.1
Download
File Size: 5.99 MB (6283847 bytes)
Juno.1.2
Download
File Size: 6.09 MB (6387181 bytes)
Juno.1.3
Download
File Size: 6.10 MB (6397218 bytes)
Juno.1.4
Download
File Size: 6.10 MB (6397661 bytes)
Juno.1.5
Download
File Size: 6.34 MB (6643420 bytes)
Juno.1.6
Download
File Size: 6.32 MB (6629667 bytes)
​
Juno.1.6
Similar to that of 1.5.
Juno.1.5
Juno.1.4
Juno.1.3
Juno.1.2
​
​

Change - Log
Juno.1.1 - 28th Sept. 2013
Initial Release
Options for Pulling and Installing apps directly to phone are added.
Options to Pull required resources from the phone directly are added.
Use of independent installer.
Juno.1.2 - 5th October 2013
Bug - Fixes
User - Interface changes.
Some minor under-the-hood changes.
Directory structure re-defined i.e. APK - Tools files are moved to a folder named apktool and some other files are moved to res directory in order to make the programs main directory look clean.
Capability to mod framework files and other Google Play apps (some) made official. (Note: This can be also done in the previous version too.)
Juno.1.3 - 9th October 2013
Bug - Fixes
User - Interface changes.
Some minor under-the-hood changes.
Added new feature to Pull Resources from a defined directory in your devices system folder.
Juno.1.4 - 14th October 2013
Bug - Fixes
Added support to create compressed apps! With some compressed over 50% compression ratio.
Juno.1.5 - 18th October 2013
Added Option to create compressed or non-compressed builds.
Added notification sounds to keep you posted when program has completed it's procedures, or when it ask for compression of the builds.
Minor UI changes.
Juno.1.6 - 3rd November 2013
Minor UI fixes.
Last Version.
Build with different compiler.
​

Oh! Thanq so much! You made dat more easier..
Sent from my MT27i using xda app-developers app

cpkunki said:
Oh! Thanq so much! You made dat more easier..
Sent from my MT27i using xda app-developers app
Click to expand...
Click to collapse
Welcome buddy, I hope you will love the upcoming version! Well it has already been finished, I'm just waiting for the release date to come.

divinemamgai said:
Welcome buddy, I hope you will love the upcoming version! Well it has already been finished, I'm just waiting for the release date to come.
Click to expand...
Click to collapse
Oh! I tried it out! Thats great!
Even i am waiting for the next release.
Thanks again.
Sent from my MT27i using xda app-developers app

cpkunki said:
Oh! I tried it out! Thats great!
Even i am waiting for the next release.
Thanks again.
Sent from my MT27i using xda app-developers app
Click to expand...
Click to collapse
Next release is out there...!!! :laugh:

[APP] [TOOL] [Win | Mac | Linux] ADB Master: Easily manage multiple Android devices

ADB Master helps you manage and monitor multiple Android devices using ADB (Android debug bridge). One click to switch adb to wireless, perform actions, commands or view and compare installed apps, running processes with cpu usage or browse logcat data for multiple selected devices… At the same time. Without root!
Updated November 2015
Download ADB Master 1.61 for Windows, Mac or Linux.
Quick start
1) Make sure ADB is installed on the PC
- http://developer.android.com/sdk/
OR
- http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
OR
- http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
2) Install and run ADB Master for your operating system.
3) Set the ADB location in the “Control” tab of ADB Master by browsing to the folder containing the “adb” binary. The background will turn green when the correct folder is selected.
Notes:
- For an Android device to appear in the list, enable "Settings > Developer > USB Debugging" on the device and connect it to the computer with a USB cable.
- In ADB Master, select one or more devices from the list of USB or WiFi connected devices to perform actions or view information on them...
Windows Users: You will need to install the Android ADB drivers if your device is not detected.
Automatic updates under Windows: If you get an error updating an older version using the built in update feature, try running the app as an administrator (right click and select "Run as administrator"). You only need to do this to update the app - not every time you run it.
Mac users: If you get an error that the app is corrupt or cannot be opened, try right clicking it and select open to allow it to run (you only need to do this once).
Linux users: The new 1.5 linux version includes a run script and has some special permission set as follows:
(Thanks to Craig D) if you want to run ADB-Master via its icon, the .jar permissions need to be set to 'executable'... This can be done by opening a Linux terminal and typing: chmod +x ADB-Master.jar.
Without setting the permission to +x you can only run it from terminal by typing: java -jar ADB-Master.jar.
If you like the app and want to support it, please purchase the paid version in the Google Play Store (search for 'ADB Master').
Using the ADB Master GUI
Device lists
View attachment 2670819 At the top of the application are the device lists. These lists provide a way to list and select devices to work with.
There are two lists:
1) USB connected devices with a button to switch the selected devices to WiFi (tcpip) mode. This will install “Helper.apk” to display adb state on the device and enable the device to be discovered and connected to by ADB Master.
NOTE: The device(s) and the computer must connected to the same WiFi access point for a successful ADB-Over-WiFi connection.
NOTE: Unfortunately, some android builds do not have the ability to use ADB-Over-WiFi without root.
2) WiFi connected devices which has a button to switch the selected devices to USB mode. This will uninstall “Helper.apk” and set the device back to USB mode.
Control tab
View attachment 2670799 This section allows you to perform actions or commands on all selected devices.
- Shutdown, reboot, reboot to recovery or reboot to bootloader by selecting the devices and then pressing the desired button.
- Press power, back, home or volume up and down buttons on all selected devices at the same time.
- “Identify” a device installs and runs a small utility to wake the device and display the same information that appears in the device list as well as the IP address.
- Execute any custom ADB command in the ADB Command box and hit enter or press “Execute” to run that command on all selected devices. NOTE: This function treats spaces as command separators so it may not work for all possible adb commands at the moment. View the results of the command in the “ADB Log” tab.
Applications tab
View attachment 2670866 This section allows you to compare and manage applications (packages) on all selected devices using the adb commands “adb pm list packages -e”, “adb pm list packages -d” or “adb pm list packages”.
- Install an APK from your pc
- Enable (requires root and su to be installed on the device)
- Disable (requires root and su to be installed on the device)
- Uninstall multiple apps on all selected devices with one click.
- Pull selected apk's
- Pull screenshots
- Start apps
- Force-stop apps (Only works with Android 3 and above)
- Clear app data and cache
App listing color key:
- Green: The app is installed and enabled on all selected devices
- Black: The app is installed and enabled on some selected devices
- Orange: The app is installed on some or all devices, but is disabled on one or more
- Red: The app is installed on some or all devices but is disabled on all installed instances
Processes tab
View attachment 2670801 This section uses the command “adb shell top -m 20” to list the top 20 processes running on the device. It lists all selected devices in one view making it easy to monitor multiple devices at the same time. Future features include the ability to terminate processes and use custom top commands.
Logcat tab
View attachment 2670802 View live Logcat data from all selected devices in one list making it easy to monitor multiple devices at the same time. Future features will enhance this section with the use of filters and colors.
- View and save Logcat messages to files
ADB Log tab
View attachment 2670803 View a log of commands executed by ADB Master. It logs the device, commands and their responses.
V1.1-BETA Changes:
- Fix for incorrect process display in Windows
- Removed the extra blank lines in logs on Windows
- Fix for device name not set correctly in Windows
V1.2-BETA Changes:
- Added tcp reset/disconnect button
V1.32 Changes:
- Added adb sideload feature (useful for ROM developers)
V1.33 Changes:
- Renamed Log tab 'Console'
- Moved ADB custom command fields from Command to Console tab for better context and visibility of command responses
V1.41 Changes:
- Added ability to pull selected apk's
- Added ability to save Logcat messages to files
- Added ability to pull screenshots
- Added ability to start apps
- Added ability too force-stop apps (Only works with Android 3 and above)
- Added ability to clear app data and cache
- Added time stamp to Logcat messages
- Fixed connect command to include the port for some versions of ADB
V1.51 Changes:
- Fixed some delays on the UI when connecting to a device
- Added buttons to open pulled screenshots and apk file locations
- Added installer for Windows users
- Added Mac .app package
- Added Linux version with required permissions set and a run script
V1.60 Changes:
- Added drag and drop to install applications (drag APK's to the application list on the applications tab)
- Added ability to select and execute a file containing ADB commands or drag and drop adb command files onto the console tab
- Added ADB Master automatic updates. Get notified when an update is available then download and install it.
- Added some useful buttons in the control tab that open various control panel items on all selected devices (all buttons may not work on all Android platforms).
V1.61 Changes:
- Improved handling of multiple commands in a single line to allow complex scripts to execute successfully.
- Fix for the way commands are handled in Windows related to line feed characters.
Execute adb commands from a file:
Command file(s) must contain valid ADB commands, one per line and may also contain comments. The starting keyword "adb" is assumed for each line and is optional in the file.
To comment a line, start the line with any of the following (common) comment delimiters: ";" "//" or "rem" as well as ":".
When selecting file(s) using the browse button, you will be prompted with a message containing the commands to be executed before they are executed. Drag and drop command file(s) onto the console tab to execute them without a prompt.
WARNING: ADB Master exposes powerful and advanced tools for working with your Android devices and misusing it can result in the device malfunctioning... REALLY.
Disclaimer: Although great care has gone into creating it, this software is provided AS-IS and you use it completely at your own risk. All rights reserved.
Download ADB Master 1.61 for Windows, Mac or Linux.
The above download links provide the recommended latest versions. Previous versions of ADB Master are also available below.
Note on automatic updates under Windows: If you get an error updating an older version using the built in update feature, try running the app as an administrator (right click and select "Run as administrator"). You only need to do this to update the app - not every time you run it.
XDA:DevDB Information
[APP] [TOOL] [Win | Mac | Linux] ADB Master: A multi-android ADB graphical interface, Tool/Utility for the Android General
Contributors
extremewing
Version Information
Status: Stable
Created 2015-03-07
Last Updated 2015-03-22

Seems Good...! (Y)

I saw a device today that was not completing loading of the apps list and a few other strange things including strange numbers for the processes cpu percentages. I will be looking into this a bit more so you can expect an update soon.

Today, I uploaded a new version that fixes some issues under Windows.
Please see the original post for the download link!
Thanks
Adrian

A new version is in the OP.
It includes a new "Reset" button for tcp connections that have stopped working, particularly useful when waking the PC or changing access points and the old connection is no longer working.

New feature in V1.3: ADB Sideload
I had a request to add ADB "sideload" capabilities to the app (useful for rom developers) and here is the first version to test out that includes this feature. I will update the OP soon if no one has any problems.

V1.31 Increased timeout for sideload
This version has an increased timeout for the adb sideload feature. It is possible the execute thread was not waiting long enough for the upload to complete?

good work, thanks
it's hard to remember the command for me,

V1.32 is now available from the first post
New feature: adb sideload - upload and install updates to a device in one step.
Sideload mode is a special option in the Android's recovery. It was introduced in Jelly Bean (4.1) and higher.
Please see your recovery's instructions on starting sideload mode.

Some small changes in V1.33 on first post.

After some positive feedback, I have published this new 1.33 version on the play store too.

This is a wish list of features to add to ADB Master and I will be working on implementing them.
- Add ability to pull selected apk's from the selected devices
- Add ability to save logcat messages to files
- Add ability to pull screenshots
If you have any other requests, please post here!

Hi, a suggestion: can you make possible to connect to a device with a known ip? I don't want to install those apks...

vipervault said:
Hi, a suggestion: can you make possible to connect to a device with a known ip? I don't want to install those apks...
Click to expand...
Click to collapse
Ok let me figure out what would make sense in how to do that.
Just out of interest, why do you not want to install the apk's (I assume you mean helper.apk)?

vipervault said:
Hi, a suggestion: can you make possible to connect to a device with a known ip? I don't want to install those apks...
Click to expand...
Click to collapse
Just so you know, executing the connect command at a command prompt when you know the IP is quite easy too. The command would be "adb connect <IP>". The good thing with the helper.apk with ADB Master is that it will take care of this for you and even re-connect when a connection is broken for some reason.
Anyway, still waiting to see why you do not want to install the apk's? You could uninstall them straight away from the Applications tab too.

.jar won't open
I double-click on the jar, but nothing happens. Anyone know why this could happen?

Aidoboy said:
I double-click on the jar, but nothing happens. Anyone know why this could happen?
Click to expand...
Click to collapse
You need to have Java installed and then the file type ".jar" should be associated with the java runtime correctly.

Best tool ever!

Vingadero said:
Best tool ever!
Click to expand...
Click to collapse
Thank you! Your feedback makes it worthwhile.
If you have any suggestions or special requests, please feel free to post them.

extremewing said:
This is a wish list of features to add to ADB Master and I will be working on implementing them.
- Add ability to pull selected apk's from the selected devices
- Add ability to save logcat messages to files
- Add ability to pull screenshots
If you have any other requests, please post here!
Click to expand...
Click to collapse
Great tools! Any progres with
- Add ability to pull selected apk's from the selected devices
???