The purpose of this thread is to make u familiar with the ADB (Android Debug Bridge)
It is a tool that lets u communicate with ur android device that is connected to ur pc.
In the first tutorial we shall learn some basics of adb and then advance to use pro commands in further tutorials.
Requirements
1. Adb link - http://developer.android.com/sdk/index.html
Direct link for windows 32bit
http://dl.google.com/android/adt/adt-bundle-windows-x86-20130917.zip
Direct link for windows 64bit
http://dl.google.com/android/adt/adt-bundle-windows-x86_64-20130917.zip
(Link may be removed after some time by google itself)
2. Windows based pc ( yes we will use windows and not linux as i dun want to communicate anything that i havent tried by myself )
1. Download and extract the zip in any drive , lets say C:
2. Go to C:/adb/sdk/platform-tools and u will something like
View attachment 1937059
{
"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"
}
3. Now press shift key + right click on mouse/keypad
http://forum.xda-developers.com/attachment.php?attachmentid=1936847&stc=1&d=1367732560
select open command window here
then type adb start-server
in order to ensure ur device is connected and recognized by adb , type adb devices , u will get something like this
View attachment 1940190
Now once your adb is setup up, lets play.....
GETTING LOGCAT THROUGH ADB
Easiest of all
just type
adb logcat
u will see entire log ur phone,
use ctrl+c to skip it
To get logcat in a file
type
adb logcat > logcat.txt
u will see a file logcat which will save ur phone's realtime process log.
TO GET A BUGREPORT
type adb bugreport
bt bt bt.. this will show info that wont b readable ..
so type
adb bugreport>result.txt
http://forum.xda-developers.com/attachment.php?attachmentid=1936973&d=1367737608
USING ADB WITH SUPERUSER PERMISSIONS
for this , u must be rooted
command
adb root
if it is success it will show something like
http://forum.xda-developers.com/attachment.php?attachmentid=1937056&stc=1&d=1367740210
INSTALLING AN APP VIA ADB
to install any app, make sure there is no space in the name of the apk...
and u should know its location,
command that u use is adb install
i have installed a game papertoss via this command, if u get success u will get something like this
View attachment 1936893
View attachment 1940189
COPYING A FILE VIA ADB
this is pretty easy
command u use is
adb pull
i have given a example by pulling the framework-res.apk from system/framework folder
View attachment 1940191
the file that u pull, u will see it in the platform -tools folder
PUSHING A FILE INTO YOUR PHONE
very similar to pull, bt this copies file from ur pc to ur android .
command u use is
adb push
For eg,
i have pushed the papertoss.apk file from C:\sanket\apps to sdcard/nimbuzz folder through the command
adb push C:\SANKET\apps\papertoss.apk /sdcard/nimbuzz
if u get success u will see something like this
http://forum.xda-developers.com/attachment.php?attachmentid=1937039&stc=1&d=1367739756
this command is very powerful and u can shift an entire video or movie folder via a single command anywhere on ur android
more commands added
thanks to @Guich
Code:
adb remount
This command remount the /system partition in read/write
Code:
adb usb
Restarts the adbd daemon listening on USB
Code:
adb shell
Run remote shell interactively
The command set shall b updated within few days.
Feel free to drop ur comments, corrections, commands.
All commands have been verified by me..
once i learn more, i will share more.
criticism is welcomed if its healthy
Thread material is not copied and will never be.
Thread will be updated with newer and complex commands soon with pics.
For developers, this is just a piece of cake which they can do with their eyes closed
i have made this specially for beginners ( like me )
reserved for future
Good job!
I think you can add in op this command:
Code:
adb remount
This command remount the /system partition in read/write
Code:
adb usb
Restarts the adbd daemon listening on USB
Code:
adb shell
Run remote shell interactively
Code:
adb devices
List all connected devices
Anh, adb will work in recovery too, write it in op if you want
Wow this a great tut!
Def gonna link back to this!
Thanks a lot for making this!
:beer:
Tnx for great tutorial... great stuff for noob like me to begin with
Sent from my Desire HD using Tapatalk 2
I'd use a Image Hoster for your pics, then you wont get "invalid attachment" errors.
XperienceD said:
I'd use a Image Hoster for your pics, then you wont get "invalid attachment" errors.
Click to expand...
Click to collapse
there are just 6 pics which are visible (atleast in tapatalk)
rest non working links are to b removed ;
Great stuff m8 :thumbup:
How about including backup and restore commands
Sent from my Nexus 7 using Tapatalk HD
Thanks for this great tutorial. :thumbup:
Thank you for this. It sounds alot easier than i thought :thumbup:
Sent from my GT-S5830 using xda app-developers app
Good job
A little suggestion, from a guy used to Linux. Beginners are always lost with shells, so for this one :
drsanket_xperia_u said:
Code:
adb shell
Run remote shell interactively
Click to expand...
Click to collapse
Why not proposing some shell commands to explain a little about this adb feature ?
Or you can add a paper/article about it, such as this one : http://www.fortystones.com/40-linux-shell-commands-beginners/
It's cool , thank you.
are there any more commands for logcat and thanks for bug report XD! I think it's called switches or something.......
drsanket_xperia_u said:
The purpose of this thread is to make u familiar with the ADB (Android Debug Bridge)
GETTING LOGCAT THROUGH ADB
Easiest of all
just type
adb logcat
u will see entire log ur phone,
use ctrl+c to skip it
To get logcat in a file
type
adb logcat > logcat.txt
u will see a file logcat which will save ur phone's realtime process log.
TO GET A BUGREPORT
type adb bugreport
bt bt bt.. this will show info that wont b readable ..
so type
adb bugreport>result.txt
http://forum.xda-developers.com/attachment.php?attachmentid=1936973&d=1367737608
Click to expand...
Click to collapse
I was wondering about the adb commands I would use to push a Deodexed /system/app and /system/framework onto my phone? I can't find the path when running adb in recovery and not sure I'd I can just push it while Android is running. Any help or direction on where to read up would be appreciated.
Were you able to su from adb in recovery? Else your phone may not be system dir mounted and usb driver mounted.
You can use adb while running. Root your phone for better results.
Sent from my GT-S5360 using xda app-developers app
I've never used adb, but I'm familiar with rooting/recoveries, blah blah blah. What state does the phone need to be in to use it?
justin1701 said:
I've never used adb, but I'm familiar with rooting/recoveries, blah blah blah. What state does the phone need to be in to use it?
Click to expand...
Click to collapse
You use it when android is booted. And you have to activate usb-debugging.
In some custom recoverys you can also use a feature callen "adb-sideload" where you can push files to the device while in recovery.
many thank! I'm new to android device a d this very useful tips now I try installing custom rom and learning about android development
Sent from my HTC Butterfly using xda app-developers app
Nice tutorial to start with..... thumbup....
doctor_droid said:
The purpose of this thread is to make u familiar with the ADB (Android Debug Bridge)
It is a tool that lets u communicate with ur android device that is connected to ur pc.
In the first tutorial we shall learn some basics of adb and then advance to use pro commands in further tutorials.
Requirements
1. Adb link - http://dl.google.com/android/adt/adt-bundle-windows-x86-20130219.zip
2. Windows based pc ( yes we will use windows and not linux as i dun want to communicate anything that i havent tried by myself )
1. Download and extract the zip ADB in any drive , lets say C:
2. Go to C:/adb/sdk/platform-tools and u will something like
View attachment 1937059
3. Now press shift key + right click on mouse/keypad
http://forum.xda-developers.com/attachment.php?attachmentid=1936847&stc=1&d=1367732560
select open command window here
then type adb start-server
in order to ensure ur device is connected and recognized by adb , type adb devices , u will get something like this
View attachment 1940190
Now once your adb is setup up, lets play.....
GETTING LOGCAT THROUGH ADB
Easiest of all
just type
adb logcat
u will see entire log ur phone,
use ctrl+c to skip it
To get logcat in a file
type
adb logcat > logcat.txt
u will see a file logcat which will save ur phone's realtime process log.
TO GET A BUGREPORT
type adb bugreport
bt bt bt.. this will show info that wont b readable ..
so type
adb bugreport>result.txt
http://forum.xda-developers.com/attachment.php?attachmentid=1936973&d=1367737608
USING ADB WITH SUPERUSER PERMISSIONS
for this , u must be rooted
command
adb root
if it is success it will show something like
http://forum.xda-developers.com/attachment.php?attachmentid=1937056&stc=1&d=1367740210
INSTALLING AN APP VIA ADB
to install any app, make sure there is no space in the name of the apk...
and u should know its location,
command that u use is adb install
i have installed a game papertoss via this command, if u get success u will get something like this
View attachment 1936893
View attachment 1940189
COPYING A FILE VIA ADB
this is pretty easy
command u use is
adb pull
i have given a example by pulling the framework-res.apk from system/framework folder
View attachment 1940191
the file that u pull, u will see it in the platform -tools folder
PUSHING A FILE INTO YOUR PHONE
very similar to pull, bt this copies file from ur pc to ur android .
command u use is
adb push
For eg,
i have pushed the papertoss.apk file from C:\sanket\apps to sdcard/nimbuzz folder through the command
adb push C:\SANKET\apps\papertoss.apk /sdcard/nimbuzz
if u get success u will see something like this
http://forum.xda-developers.com/attachment.php?attachmentid=1937039&stc=1&d=1367739756
this command is very powerful and u can shift an entire video or movie folder via a single command anywhere on ur android
more commands added
thanks to @Guich
Code:
adb remount
This command remount the /system partition in read/write
Code:
adb usb
Restarts the adbd daemon listening on USB
Code:
adb shell
Run remote shell interactively
The command set shall b updated within few days.
Feel free to drop ur comments, corrections, commands.
All commands have been verified by me..
once i learn more, i will share more.
criticism is welcomed if its healthy
Thread material is not copied and will never be.
Thread will be updated with newer and complex commands soon with pics.
For developers, this is just a piece of cake which they can do with their eyes closed
i have made this specially for beginners ( like me )
Click to expand...
Click to collapse
nice. You should explain that the users Need debug enabled AND how to enable developer menu on android 4.1
Related
SETTING UP ADB FOR WINDOWS USERS
The example shown in the video tutorial is running Windows 7. XP, Vista should run the same way.
1) Download the SDK program for your OS Here..
2) Download the latest Java Platform if you don’t have an updated version.
3) The SDK program will download in a .zip file. Extract that file somewhere easily accessible [like your desktop!]
4) You should now have a folder on your desktop with a name: android-sdk-windows
5) Drag that folder into the root of your HD…
The pathway should be something like: Computer > Local Disk ( C: ) > android-sdk-windows
6) make SURE to install the USB driver package in SDK... this way your device will be recognized when running adb commands later on...
Now that you have placed the SDK program there you can run ADB commands. But you need to run them Manually. Most people go into the tools folder and click adb and expect it to work its magic… you can stare all you want, but all it’s going to do it open a command prompt, run commands, and disappear. Now, don’t go “ZOMG I DON’T KNOW WHAT TO DO! IT WONT WORK!” …. Trust me, it will work..
6) Open a command prompt, go to windows start menu and click “search” or “run…” and in the box type: cmd and then press enter. This will execute the command prompt [terminal]
7) Now connect your Eris via USB. MAKE SURE YOU HAVE USB DEBUGGING ON!! If you don’t, go to settings < applications < development and check the box: usb debugging
8) Don’t mount your SD card yet.
9) Now you are almost ready to execute your first adb command. But first you must re-direct the path in command prompt to be your tools folder in SDK… this is what command should look like before:
C:\Users\YourUserName>
Now type in command: cd
But DON’T press enter… drag and drop the path from your SDK tools into that command line, so it should look like this:
C:\Users\YourUserName> cd C:\android-sdk-windows\tools
Now press enter. NOW your command prompt should say:
C:\android-sdk-windows\tools
Ok, last part… to test adb type in command: adb devices
Now it should return something like:
List of devices attached
HT9ANXXXXX Device
Ok so now you can execute Adb commands. Make sure you always have your command prompt pathway set to SDK tools or it WILL NOT WORK! You can now also execute adb commands directly to your device from it’s shell by typing: adb shell followed by your command.
For Visual people here is my short Youtube video explain it all again... and here is my screen shot to show you what it should look like, pay attention to my command prompt.
Another example: Custom boot animation for NON-ROOT USERS.
1) Find / create a boot animation that works with the Eris
2) name the Zip file bootanimation.zip
3) place .zip file in SDK tools folder
4) Follow above instructions to set path in CMD to tools folder and connect your device
5) execute this command:
adb push bootanimation.zip /data/local
Feel free to PM if you have any questions... I hope this helps
adb
Could someone sticky this please?... and I think themes and apps is a good place for it..unless you think it belongs in general..
Help
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
cornjo said:
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
Click to expand...
Click to collapse
EDIT: See OP at bottom for directions.
how do i install an apk file right to my phone using the "cmd"
jibbz said:
how do i install an apk file right to my phone using the "cmd"
Click to expand...
Click to collapse
adb install whatever.apk
n1ghtwish said:
adb install whatever.apk
Click to expand...
Click to collapse
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Hopefully its this simple
jibbz said:
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Click to expand...
Click to collapse
You probably don't have the .apk file in the same directory as sdk tool folder
try moving it there and see if that works.
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Ok, so if you can see your phone through adb, then you are definitely on the right track. Unfortunately, I'm not really familiar with OS X anymore so I'm not quite sure how to do it. Just sit tight for now until someone who does use a Mac, or has more of a clue then I do can help you out.
But seriously, don't pull your hair out. It won't stay on your head forever ya know...
Edit: oops, just saw this is JI6 (Froyo) not JF6, so I can't help you, but here is a general overview:
from terminal inside Android sdk main directory:
tools/adb devices -> list all devices connected that ADB can see
tools/adb shell -> gets a normal user shell on your phone
tools/adb reboot recovery -> reboots into recovery mode, suitable for update.zip root method
--------------------------------
Place the root update.zip on internal sdcard.
from terminal inside Android sdk directory:
tools/adb reboot recovery
Select the update software option, and you will be done.
laxwillsch said:
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Click to expand...
Click to collapse
Start simple:
If you open a terminal on the mac, and go to your android SDK tools folder; what happens when you type ADB shell?
Or if you type any of the ADB push commands?
You need to give more detail around what you are seeing for us to help you.
Ok so if I am in terminal and i type in my /android-sdk-mac_x86/tools nothing happens and it just says /android-sdk-mac_x86/tools is a directory. But if I type the same but with /tools/abd it opens the abd command lines, like how to write code. Then when I try to "adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin"
it says "-bash: adb: command not found"
however when I type laxwillsch$ /android-sdk-mac_x86/tools/adb shell
it does give me the drop down $
but when I then try to write the next line of code "chmod 0755 rageagainstthecage-arm5.bin"
it says "chmod: rageagainstthecage-arm5.bin: No such file or directory"
I am stumped I am beginning to think i need to buy a pc as I am very interested in android development and want to learn more, but it seems all the tutorials are run assuming you are on a PC
EDIT** I have downloaded the android SDK started pack, and the 2.2 root pack and they are all in my /android-sdk-mac_x86/tools folder that is directly on my Macintosh HD for simplicity
Do you know how to change directories (cd command)?
The problem is that you are trying to work in one directory, but all your tools are in another.
So change directories to the tools directory:
cd /android-sdk-mac_x86/tools/
now run your adb commands - you may have to type ./adb to tell your mac to look in the current directory for the adb command (that is what ./ means "start here")
Also, try to understand what is happening so you can more easily troubleshoot: chmod is a command to change permissions, and you are running it on the phone. If you can't push the file to the phone, then you can change it's permisssions. I guess you never got rageagainstthecage on the phone, so there is no way to chmod it.
If you can't do this on a mac, a PC is not easier. I use both, and like both, but you need to learn basic commands first - they apply to the mac terminal and the windows cmd prompt.
Getting root means moving in and out of the phone - adb shell - puts you in a terminal on the phone. So you really need to understand cd (change directory); pwd (present working directory - shows you where you are); cp (copy); and know your current path - what the ./ does.
I hope this helps, not trying to sound condescending - maybe practice a linux terminal tutorial would help
Thanks so much, I am at school right now and cant test out all that but you are really helping me understand all this! I will post tonight and let you know how it goes. again thank you
ok so i dont have my usb cable with me but I was playing around with the commands that you suggested and ureka! i finally got to a point where it says "h70-33-65-19:tools laxwillsch$" thats a first! and when i type pwd it shows "/android-sdk-mac_x86/tools" so that means I am working out of the right directory right? and from here I enable usb debugging connect my phone then just copy and paste the codes from the thread correct?
yes, it sounds like you are on the right track. But take it nice and slow when you follow the steps. It is very important that the commands are entered exactly as you see them.
Also, one step tells you to wait for something to run and kick you out of ADB - wait just like it says - takes about 45 seconds but feels like forever.
If you are in the tools directory - just by typing "adb" no quotes will give you whole page of adb commands - if you get a "command not found", then you need to add the ./ and make it ./adb
Hope this helps and again, read the commands step by step a couple times first so you understand what is happening.
In a nutsell, you push the rage file;
change its permissions, run it;
get kicked out of ADB and then open a new ADB shell;
you are now root;
remount the system partition to give you write access when it reboots;
reboot;
push over some files;
change permissions on files you pushed;
reboot;
Some things to know - SU is a command for gaining root access; when you use SU your prompt changes (in adb shell) from $ to #
If you are succesful you should see the SuperUser app listed in your apps.
Done and Done just rooted successfully couldnt have done it without you! thanks so much
ADB:-
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as rebooting and rebooting in recovery mode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
USB Debugging MUST be turned ON in the device for ADB to see it & Developer options is hidden in Android 4.2 and
above, Hitting Build number 10 times in
About Phone/Tablet reveals the menu (Thanks lilHermit for reminding me to add it)
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE (If you however want to set environment variables. Click on Show Content)
We can easily append the sdk platform-tools and tools folder to your systems environmental path variable directly from command line(cmd) by simply issuing one command and performing a system reboot:
Code:
[COLOR=Black]SETX PATH "%PATH%;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\platform-tools;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\android-sdk-windows\tools" -m[/COLOR]
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
(Thanks to WugFresh for telling me :victory
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. However, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Note:
If you have spaces in path of apk, you can execute the command without breakage if you include the path inside quotes. (Thanks to etcman)
Eg:-
Code:
adb install "G:\Program Files\AreeB.apk"
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
ls: Shows list of directory
cd: Changes working directory
rm: Removes the file
logcat: Displays logcat
mount: Mounts the partition
busybox: Busybox Applets
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
paxChristos for amazing logcat guide
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
Reserved
Reserved Once More
Last One
Reserve the guide
install full rom
how to install a full rom from adb?
Pretty sure it's impossible. Sorry.
Sent from my E15i using XDA Premium App
Perfect Guide to use ADB Commands..
It is very clear and perfect guide to use ADB commands.. I tested this all and works fine..
You can use apks to do logcats from the phone too, I use catlog.
About Broadcom being open sourced made me laugh hahaha.
open source broadcomm, i see what you did there .
Updated OP
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Android-fany said:
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Click to expand...
Click to collapse
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
iamareebjamal said:
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
Click to expand...
Click to collapse
I already reinstalled it like 5 times. Still doesn't work.
Android-fany said:
I already reinstalled it like 5 times. Still doesn't work.
Click to expand...
Click to collapse
Which Windows?
Which ROM?
iamareebjamal said:
Which Windows?
Which ROM?
Click to expand...
Click to collapse
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Android-fany said:
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Click to expand...
Click to collapse
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
AW: [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies
iamareebjamal said:
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
Click to expand...
Click to collapse
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Android-fany said:
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Click to expand...
Click to collapse
Very strange
Download My Phone Explorer and check if its working!!
Its just 2mb-6mb
Contents / Thread overview
Introduction
What is Fastboot?
What is adb?
How to install adb and fastboot
How to test adb and fastboot work
OK Gimme some useful fastboot commands please!
OK Gimme some useful adb commands please!
A little more about using Windows command prompt
Myth Busters
Introduction
adb and fastboot are very useful command line tools. They can be used from Windows, Linux or Mac to carry out tasks on your android device, such as moving and backing up files, rooting and restoring your phone to it's factory state. Understanding how to use these tools could save your phone when you get yourself in trouble. This is especially true of rooted users. Particularly those of you who are "new to the scene". You definitely should read and understand this thread before you do ANYTHING root related.
This thread is not intended to be a non-exhausted reference. It is merely here to give an overview of the most basic of basics
{
"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"
}
What is fastboot?
Fastboot comprises of 2 components.
1) Fastboot mode on the phone (The Bootloader)
2) Fastboot tool on your computer
Fastboot is a small command line tool that you can use from your computer whilst the phone is connected via USB and you are booted into the bootloader. The most common uses for fastboot are:
Unlocking the bootloader - needed as part of the rooting process
Flashing a custom recovery to the device - needed as part of the rooting process
Flashing factory images - used for saving / trestoring your device back to stock
Being able to do these 3 things are essential before rooting. Many new users skip learning these and use a toolkit to root. As a result, when they mess up and we try to explain what they need to do to fix their issues, it becomes very difficult for us to help as fastboot is not understood. It is YOUR responsibility to understand these things BEFORE you mess up.
What is adb?
adb is another small command line tool that stands for "Android Debugging Bridge". Again, it can be used from a computer connected via USB to your android device. It can be used whilst the device is booted into Android or (if you have a custom recovery), it can be used in recovery too, unlike fastboot (yes, adb and fastboot are NOT the same thing) which can only be used in the bootloader.
adb can be used to push files to (or pull files from) your phone. It can also be used to execute many of the commands available in Linux terminals (Or Android terminal emulators) on the device itself. We're not here to cover all these commands however. We just want to cover the basics.
How to install adb and fastboot
adb and fastboot are very easy to install and can be installed on Windows, Linux and MAC computers. The Windows install can be a little bit more complicated than the other 2 and may need additional drivers installing too.
Windows.
There is a very handy tool that can install adb and fastboot in 15 seconds. It is recommended that you use this to install adb and fastboot. Please see the link immediately below for that tool:
ADB, Fastboot and Drivers - 15 seconds ADB Installer - Really quick and easy way to install adb and fastboot (by @Snoop05). Downlkoad links are at the bottom of post 1.
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide (to which again, you should answer Y)... This then allows you to type adb commands in the command prompt without having to open a particular directory first. You may or may not understand what I mean when I say that, but take it from me, its much more convenient and easier to use this way.
There is actually a manual way of doing what the 15 second installer is doing, by extracting the adb.exe and fastboot.exe to your computer and using the Windows Enviroment variable PATH to make the executables work system wide, however the installer is much quicker, but for reference:
Code:
right-click computer > properties > advanced > environment variables.
under system variables click "path" and click "edit"
at the end of the line, add the below:
;c:\adb_fastboot
where c:\adb_fastboot is where you decided to extract adb and fastboot executables.
Please note, the semi-colon ; is VERY important.
You can do this if for some reason the installer becomes unavailable
It will also ask if you want to install device drivers. Actually, say N to this as we're going to cover that next, using the Universal Naked driver which has better compatibility.
Here is a link to the naked driver: DOWNLOAD THIS which has been taken from this thread:
[ADB/FB/APX Driver] Universal Naked Driver
Some of the below instructions are taken from the thread above by @1wayjonny but I have moved them here to make it easier for you guys.
Code:
To install on Windows 7:
- Ensure existing drivers are uninstalled first*
- Extract the zip to c:\adb (created earlier by the installer)
- Right-click "Computer" > Manage in windows and choose "Device Manager"
- Boot the Nexus 5 to the bootloader (Volume down + Power) and connect the USB Cable
- Watch for any new devices with exclamation marks appearing
- Right-Click the new device > Update driver software
- Choose the "browse" method and browse to c:\adb then follow the wizard to the end.
*To uninstall existing drivers, boot into Android and connect the USB cable. Monitor device manager for the device showing up. To uninstall the device, right-click it to uninstall it. At the prompt, ensure you also choose to delete the driver. Repeat this for bootloader and recovery.
Code:
To Install on Windows 8, you must additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
Once that is done, your Windows computer is configured for adb and fastboot.
In device manager, the device should show up as below, depending whether you are booted into recovery or bootloader...
Recovery - Android Device > Google Nexus 4 ADB Interface
Bootloader - Android Device > Google Nexus 4 Bootloader Interface
If it shows as something different, either you have existing drivers in the way or something went wrong.
Linux and Mac
Here is a really simple tool to install adb and fastboot on the above OS. The only expectation is you know how to open and run a terminal command. Please see the link immediately below:
Nexus Tools 2.2 (Featured by XDA) - adb and fastboot installer for Linux and Mac (by @corbin052198)
Once you have installed adb and fastboot from the above link, you're ready to go.
How to test adb and fastboot work
As previously mentioned, adb and fastboot are both command line tools. That means you must run these tools from command prompt (cmd in Windows) or Terminal (Linux and Mac).
Remember earlier, I mentioned that fastboot can only be used in bootloader? and adb can only be used in Android (or custom recovery - lets cover that later)? We can use the command "fastboot devices" and "adb devices to see if we have adb and fastboot working correctly.
Lets try it.
Boot your phone into android
Connect it to your computer via USB
Open cmd (start > type "cmd" on Windows) or Terminal (Mac/ Linux
Type in the windows "adb devices" and press enter
Here is what we don't want to see:
Notice how there is nothing underneath where it says "List of attached devices" That means it cannot see any device
Here is what we DO want to see:
We can see that there is now a device listed.
OK lets test fastboot. Unplug the USB and turn off the phone. When it is off, hold down Volume down + power until you feel the vibrate. You will now be in the bootloader. Reconnect the USB cable.
In the same window (cmd or terminal) we're going to now type "fastboot devices".
Again, here is an example of what we don't and do want to see:
If in both modes, you can see your devices "Serial Number", then you know they are both working. If they're not working (mainly Windows users) you may want to check this additional thread about troubleshooting drivers.
[*] Diagnosing USB Driver and ADB issues in Windows - Ensure ADB and fastboot WORK before you root (by @MaxRabbit)
Please note that if you cannot get adb and fastboot to work "system wide", you can open the command prompt to the location of the adb and fastboot executables exist and try from there.
OK Gimme some useful fastboot commands please!
Here are some of the most useful fastboot commands you will come across. Fastboot is used mostly for flashing images to the devices partitions on the internal memory.
Code:
fastboot oem unlock
This unlocks your bootloader and allows you to flash a recovery to root. WARNING, this will wipe your device. If you actually want to do this, please follow this guide:
How to Unlock Bootloader, Install Custom Recovery and Root - The preferred method. Allows you to learn and understand the basics (by @Chromium)
Code:
fastboot flash recovery recovery.img
This will flash a recovery.img to the recovery partition. The command is broken down into "fastboot flash" (what to do) "recovery" (where to flash to) "recovery.img" what to flash there. In the terminal or command prompt, you cannot just type "recovery.img" though. It has to be the path to where the recovery image is. For example, if my recovery image is on my desktop, I would have to type:
Code:
fastboot flash recovery c:\users\rootsu\desktop\recovery.img
It is worth noting, that it IS case sensitive, meaning if your file is called Recovery.img, you must type the capital R...
Other things you would flash:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
These will flash the system image (ROM) and bot image (kernel) as you would if you were returning to stock. If you want to return to stock, please use this guide:
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63)
You can also boot into a recovery.img without flashing it...
Code:
fastboot boot c:\users\rootsu\desktop\recovery.img
which is "fastboot boot" (what to do) "c:\users\rootsu\desktop\recovery.img" what to do it with. As you may have noticed, we did not define the recovery partition in this command, that's because we're not flashing it....
OK Gimme some useful adb commands please!
At the moment, we are going to assume you have a custom recovery and you have booted into recovery. The reason for this is using adb in recovery can be much simpler.
Here are some useful scenarios for using adb.
Backup your sdcard to your PC
Code:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
**Please note, some recoveries may "mount data" automatically on boot, so don't be disheartened if you get an error stating device or resource busy. This probably just means you can't mount what is already mounted**
/data/media/0 is the real location of /sdcard for your information. Also referred to as "The mount point". What we have done here is "adb pull" (what to do) "data/media/0" (what to move) "c:\MyBackup" (where to move it to)
Push a zip file from your PC to your sdcard (useful if you wiped your sdcard and rom)
Code:
adb shell
mount data
exit
adb push c:\rom.zip data/media/0
What we have done here is "adb push" (what to do) "c:\rom.zip" (what to move) "data/media/0" (where to move it to)
You can of course also use adb to push and pull files to and from /system too. You just need to:
Code:
adb shell
mount system
exit
I mentioned earlier that using custom recovery is much easier for adb than whilst booted into Android. You need to ensure you have a kernel that allows insecure adb before you do anything with system and data partitions. You also need to ensure that USB debugging has been enabled in developer options.
For example, to mount system to pull files whilst android is running you have to:
Code:
adb root
adb shell
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
...which is clearly a little bit more involved, so I recommend you use recovery for adb push and pull. You can find more detailed information on adb here: http://developer.android.com/tools/help/adb.html
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd " or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Another point to make with command prompt or terminals, is if you do a particular command, it is "pre-programmed" to "expect" a particular format of that command.
For example, we know that adb push as a command expects after it . This means the command is actually
Code:
adb push
BUT if you put something AFTER , for example -
Code:
adb push somethingelse
, it will assume that the "somethingelse" is a bad parameter, and the command will fail. It will probably display (or "print" which is the technical term in a terminal) a helpful guide of how the command should be used instead of trying to run the command which it does not understand.
You're probably wondering why I am telling you this. Well quite simply, it is a warning about folder names. Imagine you have c:\users\rootSU\My Documents as a folder. You assume the command is then
Code:
adb pull /data/media/0 c:\users\rootSU\My Documents
but it is not... There is a space in between My and Documents. What you have actually done is
Code:
adb pull Documents
because it uses a space to signify the end of a command or parameter. It is best to avoid using folders with spaces in them. Avoid as much as you can. In the event it is unavoidable (Although when is it ever>) then please surround the path with quotation marks,
Code:
adb pull /data/media/0 "c:\users\rootSU\My Documents"
so that way, it sees everything between the " " as a single parameter.
Myth Busters
Myth 1: You need USB debugging on to use adb and fastboot
If you cannot boot into Android, it doesn't matter. You DO NOT need USB Debugging turned on to use adb outside of android. USB Debugging is an Android ONLY setting. Fastboot obviously also does not need debugging either as this too is outside of Android
Myth 2: to adb push or fastboot flash files, they must be in the same folder as adb or fastboot executables. Sorry but this is rubbish. You can pass the full path of the image you're flashing or file you're pushing in the command and fastboot / adb can be called system wide if you've set them as an environment variable or used the 15 second installer
This should absolutely be a sticky!!
Sent from my EVO using XDA Premium 4 mobile app
Evolution_Freak said:
This should absolutely be a sticky!!
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. I created it specifically to put in the general sticky in my signature. Section 1a and 4
Great work @rootSU definitely should be sticky!
psycho693 said:
Great work @rootSU definitely should be sticky!
Click to expand...
Click to collapse
Thanks. Its in there. All in the main sticky thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
Thanks. Its in there. All in the main sticky thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It helps a lot because I have been looking for a good guide to pull system files while the phone is running
psycho693 said:
It helps a lot because I have been looking for a good guide to pull system files while the phone is running
Click to expand...
Click to collapse
Cool
The main thing for me was we had a diagnosis thread and we had a full guide for rooting or returning to stock but nothing to answer the how to set up or how to adb push basic questions... I've seen several threads today alone
Sent from my Nexus 5 using Tapatalk
Very cool, didn't actually know the push/pull commands or that driver you reference
wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:
simms22 said:
wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:
Click to expand...
Click to collapse
LMAO! rootSU, this is freakin awesome. Every thread that I find complaining about issues with toolkits will be redirected here. If this isn't stickied it should be a crime.
Sent from my Nexus 5 using xda premium
I suggested to the mods that we have just one sticky in general that has all the threads we believe to be Stickies within it. That way we can control it ourselves but without making it messy, so we have that now ( see signature).
Sent from my Nexus 5 using Tapatalk
Thanks for listing my Nexus Tools
corbin052198 said:
Thanks for listing my Nexus Tools
Click to expand...
Click to collapse
Thanks for making them
Sent from my Nexus 5 using Tapatalk
simms22 said:
wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:
Click to expand...
Click to collapse
How do I flash the toolkit? I think its bricked :silly:
Good thread.
Amazingly detailed thread. There's no way to mess up reading this thread, the noobs will definitely learn if they can do the reading first that is.
I will laugh when a noob asks, "fastboot? It takes about a minute for me to boot!"
Sent from my Nexus 5 using XDA Premium 4 mobile app
I'm not sure what this all is, but awesome guide!!!!
? I'll be frequently linking this too.
Good job my friend, i am sure it's really helpful for a lot of people
Tapatalk Team SlimRoms
Added the below section about using command prompt. Hopefully a little more detail should help.
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd <directory>" or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Click to expand...
Click to collapse
Added a bit more about using directory paths with spaces.
Sent from my Nexus 5 using Tapatalk
After a week with my new nexus, it's time for a litlle fun... But first must say thank you for this explanation.
Sent from my Nexus 5 using Tapatalk 2
Allright. I recently broke my S3 LTE's LCD when i was trying to change glass. Now my problem is that it tells my S3 is an portable media player, so it won't let me just open my folders and stuff. What i can do to save my important pictures and stuff. Thanks in advance!! :fingers-crossed::good:
Is adb enabled on the device?
Magik_Breezy said:
Is adb enabled on the device?
Click to expand...
Click to collapse
I don't think it's enabled, but i can't be sure im right.
Such Name said:
I don't think it's enabled, but i can't be sure im right.
Click to expand...
Click to collapse
Unfortunetly there is no instantaneous way to see if adb is enabled and you will be required to install the relevant tools to know.
1. Download and install the Samsung USB Drivers from http://developer.samsung.com/android/tools-sdks/Samsung-Android-USB-Driver-for-Windows
2. Download and install minimal adb and fastboot from http://forum.xda-developers.com/showthread.php?t=2317790 - thanks to shrimp208 for providing us with this so we don't have to install the whole SDK.
3. Run cmd and change directory to the location of adb.exe (e.g. cd C:\users\admin\downloads\apt), run 'adb.exe start-server' then 'adb.exe devices' to see if your phone has adb running.
If adb is running you can copy files from you're phone's file system to your pc with 'adb pull' (e.g. adb pull adb pull
/data/app C:\users\admin\downloads\apt).
Best of luck
Magik_Breezy said:
Unfortunetly there is no instantaneous way to see if adb is enabled and you will be required to install the relevant tools to know.
1. Download and install the Samsung USB Drivers from http://developer.samsung.com/android/tools-sdks/Samsung-Android-USB-Driver-for-Windows
2. Download and install minimal adb and fastboot from http://forum.xda-developers.com/showthread.php?t=2317790 - thanks to shrimp208 for providing us with this so we don't have to install the whole SDK.
3. Run cmd and change directory to the location of adb.exe (e.g. cd C:\users\admin\downloads\apt), run 'adb.exe start-server' then 'adb.exe devices' to see if your phone has adb running.
If adb is running you can copy files from you're phone's file system to your pc with 'adb pull' (e.g. adb pull adb pull
/data/app C:\users\admin\downloads\apt).
Best of luck
Click to expand...
Click to collapse
Huge thanks for this help. It tells me "List of devices attached: 430008b6b6f9a0b1 device" and sorry for stupid question, but what does that mean?
Such Name said:
Huge thanks for this help. It tells me "List of devices attached: 430008b6b6f9a0b1 device" and sorry for stupid question, but what does that mean?
Click to expand...
Click to collapse
That is your device id, this means you should be able to recover your files.
Initiate 'adb.exe shell' and it should automatically select your device. You can then navigate using the 'cd' command to change directory and 'ls' to list all files/folders in that directory. After finding the files you can pull them from your device to your computer
Magik_Breezy said:
That is your device id, this means you should be able to recover your files.
Initiate 'adb.exe shell' and it should automatically select your device. You can then navigate using the 'cd' command to change directory and 'ls' to list all files/folders in that directory. After finding the files you can pull them from your device to your computer
Click to expand...
Click to collapse
Thanks you very much . I was able to save all files/memories with ADB. I can't even thank you enough! :laugh:
I'm glad I could help, praise the ADB. Hit thanks if you wish