Database Users

adb command

can anyone tell me what the ADB shell command is for going up one directory. I can use "cd" to enter a directory, but always have to exit because cd.. doesn't work like in windows. Also tried cd home, to no effect.
Thanks,
Will

Code:
cd ..
Notice the space. Windows forgives leaving it out, Linux doesn't.

oh...you are the bomb. I was getting so tired of having to exit just to go up one directory.
Thank you.
Will

No problem. Another quick tip, cd / takes you all the way to the root of your file system. Just in case you get lost somewhere

pwd shows you where you are as well.

EASIEST sdk adb guide tutorial instructions

I have learned alot from this site so i figured i'd give something back. these are the the two easiest methods i have found for setting up the android debug bridge. one for windows and one for linux... these instructions should work for any version of windows.
first make sure you download the latest sdk by going to android.com and clicking on developers.
windows:
after you have download the sdk, unzip it to your desktop. rename it to sdk. cut the UNzipped folder on the desktop that you just renamed by right clicking and hitting "cut" then go to start>my computer>c: and paste the folder here. now go into the new "sdk" folder and right click on the "tools" folder and click "send to" then choose "desktop (as shortcut)" you should now have a shortcut on the desktop called "tools-shortcut"
now for the easy part: hold shift and right click on tools-shorcut, holding shift adds the option "open command window here" to the context menu that comes up so click on that. now just make sure your phone is connected to the computer and on ur phone debugging is enabled (menu>applications>development>debugging). on ur command window that came up you should see a black box with white text and the cmd should be c:\sdk\tools> just type "adb devices" and you should see your phone under "list of devices attached" if you do see it you should be able to start running adb commands
adb pull "/location to file or folder on phone" -(the pulled folder or file will be in the tools folder we created earlier which you can still access by clicking on the tools-shortcut on your desktop)
adb push "name of file or folder to be placed on the phone sdcard" -(make sure the file or folder you wish to place on the phone has been placed in the "tools" folder on the computer, again its the same folder the "tools-shortcut" opens up)
hint and examples: i have found a good way to back up and reinstall all ur apps using just adb push and pull. just experimenting and playing around with it i have found you can accomplish installing with just knowing these commands above... if you plan to data wipe and flash a new rom but you don't want to go through the tedious task of reinstalling and you have a rooted android phone then you may use this method to backup/reinstall ALL of your apps. plus this will give you good practice using adb.
backup example:
adb pull /data/app .... let it finish
adb pull /data/app-private ...let it finish
now you should have ALL of ur apps in ur tools folder on ur computer! in the tools folder, create a new folder and name it what u want, i named mine APPS4EVO because i have an evo and and epic and some apps don't work for both so i keep them seperate. cut and paste all of ur apps and put them into your newly made folder. now back to the adb window
restore example:
adb push /APPS4EVO /data/app/
this will push all of your apps in your backed up folder you made earlier to the folder where apps go when they are installed and if you wait 1-10 minutes depending on how many apps you have you should be able to see them on ur phone as if you had installed them one by one. also notice the space between /APPS4EVO and /data/app/ the space seperates the folder from inside ur tools folder you wish to install and the location you wish to put them on ur phone. please be aware that you do not need to type c:\sdk\tools\APPS4EVO because the command window is already being ran in the tools folder, so the location would just be /APPS4EVO in my case.
adb shell -opens up the terminal shell to run commands specifically for the phone, while in the shell you cannot run other "adb xxxxx" commands, you will have to exit the shell by typing "exit"
OPTIONAL: i marked this as optional bc with the above it is not necessary... i have never done this and my adb works great but i have seen it often in other tutorials around the web.... i believe its only necessary on windows 7 and maybe vista. go to start then right click on "my computer" and click on "properties" then in the left pane click on "advanced system settings" then in the window that pops up click on "environment varables" button, in the next window that pops up, under "system variables" scroll down to the "path" variable and double click it. in the "variable value" box do NOT erase anything but add ";c:\sdk\tools" (without quotations). then click ok on all the windows cuz ur done.
thats all for windows.
linux (ubuntu)
extract the sdk to your home/name/ folder and rename it to sdk. now right click on the folder and go to permissions and make sure (run as executable) is checked, now go into the folder and do the same permission change to the tools directory.
now you should be able to run adb commands in the terminal when your phone is connected. same as in windows except your commands will be preceded by your tools folder location....
FOR EXAMPLE:
/home/jay/sdk/tools/adb devices
/home/jay/sdk/tools/adb push xxxx xxx
/home/jay/sdk/tools/adb pull xxxx
EXTRA:
if your having troubles connecting ur phone to ur computer over usb, even after installing drivers, like i sometimes have with my epic, you can download "wireless adb" from the market which i found to be surprisingly easy to use, just like if u were connected by usb, except under adb devices you will show up as your gateway address not ur device name but trust it still works the same.
good luck everyone, i hope this post isn't redundant and i really hope i help someone out there just starting! adb is confusing at first.

adb no longer working

I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?

duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
Click to expand...
Click to collapse
Go into the directory and see if there is a file called adb in there...if it's not check the other folders like tools or something like that i'm at work so i don't know the exact name of the directories...

duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
This is a PC error message stating that the file adb.exe is no longer in the AndroidSDK directory. As zervic mentioned, check and see if the file adb.exe is in that directory.

We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.

duckredbeard said:
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
Click to expand...
Click to collapse
Just reinstall (or unzip if I remember right) the Android SDK into that directory

I started the "update all" in the "installed packages" window. If that doesn't fix it, I shall follow your advice.
Edit: The "update all" didn't fix it.

I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.

duckredbeard said:
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
Click to expand...
Click to collapse
Just so you know that may be a little unstable. It may be worth your while to check the "platform-tools" folder and see if adb is in there, i believe that's where it is by default and it also may be worth your while to run adb from that folder instead of where you jerry rigged it to run. But, on the other hand, it may work the way you have it. You never know. Just figured I'd throw that out there.

While rooting my Nook Color, I came across a recommendation for a free app in the market called adbWireless.
It's AWESOME! No need to use USB or worry about drivers, just install the app, push the big huge button and then type the adb command it shows you to connect to your device. Worked absolutely perfectly on my Nook... haven't tried it on my Aria, but next time I need to ADB something on it, you can bet I will!

did anyone check their tools directory?
ie: C:\android-sdk-windows\tools
LOL

[Q] Installing TWRP/FFF on mac, having issues

For anyone having an issue with installing TWRP and FFF on a mac here's my two cents on how to help.
Make sure you have the sdk, as well as platform-tools downloaded.
Once you've downloaded these things, you're going to need the correct fastboot.exe for macs (rename this fastboot.exe, will probably come as fastboot-mac.exe), I don't remember where I downloaded it, nor do i want to break any rules or piss any people off, but find the correct mac fastboot.exe.
Once you've done all of this, here's what you need to do.
Go to the rootzwiki, or the XDA threads for doing TWRP and FFF on linux. Once you get there, follow ALL of the directions. HOWEVER if you haven't set ADB up with directories( i think this is what it's called) you'll do a little difference.
instead of doing cd Path to ~/androidsdk/platform-tools (or whatever you have your SDK named as) you are simply going to remove the Path to and run it as
cd ~/androidsdk/platform-tools
followed by that you can start using ADB. Instead of running things as
adb root, or adb reboot, you need to include
./ before the commands, IE: ./adb root, or ./adb push
I honestly have NO idea why I have to do everything this way, from what I remember it has to do with directories or something, but either way it's what fixed everything for me.
Don't consider this a guide or anything, as I don't want to be someone who people blame if it didn't work for them, as I'm simply doing what works for me.
I hope this helps the other mac users I'm sure are here that are struggling, cause I had to remember how to do all this stuff before I realized why I was ****ing up doing all this stuff.
Good luck!

It's not a mac thing, you just aren't getting the directories right. Find where you put in in Finder, note how you got there. Once you get a terminal prompt, you need to go to that directory or add it to your PATH.
The easiest place to put the SDK directory is your user directory. In Finder, on the left side, find your username. Copy the SDK directory there. Then your terminal prompt should open to your user directory. Do an "ls" and you should see it listed. "cd" into it, then into platform-tools. Now you should be ready to go.
Once in platform-tools, do "./adb" and it should spit out a bunch of help text. If not, something is still missing. Note that the "./" is required.

i managed to pull the nandroid. now i need to push it back.

so i had a thread about getting these files pulled off of my buddies busted n4. but the adb command given wouldnt work and i didnt figure out how to make a tarball untill after i pulled the files. anyways...
i managed to pull the nandroid using this command - adb pull /sdcard/clockworkmod/backup/2013-08-07.23.11.28/.
what i ended up with were all of the files separately on my pc.
so if i put all of the files back into its own folder with the same name on my pc, what would be the command to push it back onto the new phone that i am about to root. using cwm.
assuming i kept the folder in platform tools. C:\androiddev\sdk\platform-tools
and do i need to create directory in the phone first? .../clockworkmod/backup/2013-08-07.23.11.28
it seems like i remember these commands, or at least i could figure it out by the commands listed, in one of the original root unlock stickies. but they seem to have been replaced with one click dealios. i need to start using adb for all of my flashing and such just so i can stop looking like an idiot for not knowing the simple stuff. in other words i would experiment and figure it out.... but i am afraid that i will just litter his phone with files and still end up coming back here.
thank you.

A quick guide to the adb pull and adb push commands:
Code:
adb pull <remote> <local>
adb push <local> <remote>
Remote being folder location on phone, local being folder location on computer.
So the correct command to pull the backup and put it into a folder under platform-tools (let's use the folder name you are using) would be this:
Code:
adb pull /sdcard/clockworkmod/backup/2013-08-07.23.11.28/ 2013-08-07.23.11.28
All you have to do to put it into it's own folder is put a space after the remote location and type whatever name you want the folder to be.
Now on to your current question. You said you pulled the files onto the computer, but they weren't in their own folder. I would put them into their own folder (we'll use 2013-08-07.23.11.28 for now) and push the contents of that folder to a folder on your phone, that we will also call 2013-08-07.23.11.28 under the backup location (If you want to make sure you have only the files contained in the backup, try re-pulling them using the above pull command. If you're pretty sure you know which ones it pulled, I wouldn't worry about it). Try this:
Code:
adb push 2013-08-07.23.11.28 /mnt/shell/emulated/clockworkmod/backup/2013-08-07.23.11.28/
That'll push the contents of folder 2013-08-07.23.11.28 under platform-tools and put them in a folder called 2013-08-07.23.11.28 under /backup/. If it doesn't exist, it'll create the folder. Now you pulled the backups by using /sdcard/, I didn't know you could just do that, so I guess you could try pushing using that too:
Code:
adb push 2013-08-07.23.11.28 /sdcard/clockworkmod/backup/2013-08-07.23.11.28/
I'm pretty sure those should do the trick. Let me know if that helped.

Johmama said:
A quick guide to the adb pull and adb push commands:
Code:
adb pull <remote> <local>
adb push <local> <remote>
Remote being folder location on phone, local being folder location on computer.
So the correct command to pull the backup and put it into a folder under platform-tools (let's use the folder name you are using) would be this:
Code:
adb pull /sdcard/clockworkmod/backup/2013-08-07.23.11.28/ 2013-08-07.23.11.28
All you have to do to put it into it's own folder is put a space after the remote location and type whatever name you want the folder to be.
Now on to your current question. You said you pulled the files onto the computer, but they weren't in their own folder. I would put them into their own folder (we'll use 2013-08-07.23.11.28 for now) and push the contents of that folder to a folder on your phone, that we will also call 2013-08-07.23.11.28 under the backup location (If you want to make sure you have only the files contained in the backup, try re-pulling them using the above pull command. If you're pretty sure you know which ones it pulled, I wouldn't worry about it). Try this:
Code:
adb push 2013-08-07.23.11.28 /mnt/shell/emulated/clockworkmod/backup/2013-08-07.23.11.28/
That'll push the contents of folder 2013-08-07.23.11.28 under platform-tools and put them in a folder called 2013-08-07.23.11.28 under /backup/. If it doesn't exist, it'll create the folder. Now you pulled the backups by using /sdcard/, I didn't know you could just do that, so I guess you could try pushing using that too:
Code:
adb push 2013-08-07.23.11.28 /sdcard/clockworkmod/backup/2013-08-07.23.11.28/
I'm pretty sure those should do the trick. Let me know if that helped.
Click to expand...
Click to collapse
thanks a ton. it worked. i tried the first option. rebooted recovery. and it could not find the files. i rebooted the phone. and then went back into recovery. the files still were not there.
so then i did the second option. with the sdcard. it worked like a charm. his phone is back to aug 7th. and didnt lose a thing... other than the last four days of his new data.

phermey said:
thanks a ton. it worked. i tried the first option. rebooted recovery. and it could not find the files. i rebooted the phone. and then went back into recovery. the files still were not there.
so then i did the second option. with the sdcard. it worked like a charm. his phone is back to aug 7th. and didnt lose a thing... other than the last four days of his new data.
Click to expand...
Click to collapse
Well that's odd, I'm the exact opposite, I can't see the files in /sdcard/, only the path through /mnt/. I'm not too familiar with how the Nexus 4 handles the emulated sdcard, I just never had the reason to explore it.
Actually, I think the difference between where our recoveries saw the backups is because of a version difference. CWM has changed their backup location in the past, and I'm sure you are using a version that is looking for backups in the /sdcard/ directory, while mine was looking for them through /mnt/.
EDIT:
Oh btw, you might advise your friend to download a file explorer app (I use ES File Explorer) and erase those backups that he didn't use in the /mnt/ folder. I'm sure they are still there taking up space on his phone. You may or may not need root to see the correct folder though.