Help - Wear OS Q&A, Help & Troubleshooting

How to permanently fix adb isn't recognized as internal or external command in windows 7
Sent from my Le X507 using Tapatalk

Assuming it works when you're in its directory, run it from that directory or give the full path when you run it. Or do as I do, add the directory to your path. Then you can run it from whatever directory you're in.

Related

copy files to computer

I am rooted but just on the Stock ROM. How can I copy a file in the data\app-private dir to my PC. I have paid for apps but cannot get them from the market. I want to have a backup of this is case I have to reset the phone again.
I tried the cp command but it did not work. I am also not using APP2SD.
I have had good luck using app "Root Explorer"... seems to do the job of moving and copying that folder.
(I am on Modco using App2sd)
You can run a command on your PC while your phone is connected
Code:
C:\>adb pull {location on the phone} {location on your pc}
dailypush said:
I have had good luck using app "Root Explorer"... seems to do the job of moving and copying that folder.
(I am on Modco using App2sd)
Click to expand...
Click to collapse
This worked great to copy them to my sd card, can you also use this to add apps back like Sprint and HTC apps and widgets.
dagnasty said:
You can run a command on your PC while your phone is connected
Code:
C:\>adb pull {location on the phone} {location on your pc}
Click to expand...
Click to collapse
I tried this from the C:\> and got adb was not recognized
I tried from the android/tools and got the same error and tried from insdie the phone. No luck moving files from the CMD prompts. I am not sure where to go from here.
My bad, I added the path to the SDK to my 'path' system variables. It should work if you are in the tools directory of the sdk.
It says pull is not recognized as an internal or external command is what it says when I do pull in the Android/tools dir
Here is what I typed
pull /system/app/Stock.apk C:\
or
pull /system/app/Stock.apk/ C:\
neither work

how did you guys install the android sdk?

I am running ubuntu and im am trying to install the sdk, i searched on the internet and messed around with it for 2 hours last night and still could not figure it out, it is a tgz file, Any help would be great. Thanks
deleted
Im having the same problem except I have everything installed just need to figure out how to get my computer to recognize my phone
if i remember correctly,cd to the directory where you saved the sdk tarball, then as mentioned above extract it using tar zxvf
cd to the extracted directory and you should see /tools
cd into /tools and you should be able to load the sdk by typing ./android
if you add the /tools directory to your path in your .bashrc, you will be able to type android straight in the terminal to load up the sdk.
hope that helps
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
Alright i have the the sdk installed i just need abd commands to work now
Don't forget to add the tools directory to your PATH

[Error] Unable to apply PUSH Command in ADB

Hello mates,
I am trying to Copy the BUSYBOX file to my /data/local/bin directory. But when i use the 'push' command it say adb: command not found. Hereby i have attached the image of my terminal.
Would you please help me in copying my files to the directory "/data/bin/local"
Also, where should i put the files which i need to copy. Eg. Since i need to copy 'busybox' to the /data/local/bin/, should i put the busybox in my Desktop, i.e. /home/android/platform-tools directory?
You should've not run the command from within the adb shell. Just go to the tools folder and type "adb push busybox data/local/bin" ofcourse without the ""
The busybox should be indeed be present in the folder from witch you run adb, in your case the "tool" folder.
Good luck!
Erwin
Sent from my HTC Wildfire using XDA App
@ErwinP.
Thanks for rectifying this mistake.
It worked.
You're welcome! I had to learn it the hard way myself, so I'm happy ik I can help someone! ;-)

How to copy CWM backups to PC from /mnt/shell/emulated?

So, CWM saves its backups and blob directory in /mnt/shell/emulated which is not accessible via MTP. I've started using TWRP for all my new backups but I would like to copy the existing CWM backups to my PC before wiping the directory on my phone. It's currently using 8-9 GB. However, when I try to move the directory from /mnt/shell/emulated to a directory in a directory in /sdcard, the move operation ends instantly and nothing is copied. I'm wondering if the problem is that I don't have enough free space. I've got about 2.5 GB free.
EDIT: It appears that you need to have enough space to copy the entire directory before deleting it. The phone ran out of space halfway through a file copy using ES File Explorer. I guess that's why Root Explorer won't allow the move to begin.
Use adb to pull the directory to your computer, adb pull /mnt/shell/emulated
I would like to do this as well like I used to do with older versions of CWM on my Gnex. Then it was as easy as moving the large backup file found in /sdcard/clockworkmod/ folder.
I just tried that adb pull command mentioned in the post above and this starts to copy the entire contents of my phone to some unknown source on my PC (I can't find where?).
How would one go about simply backing up a CWM nandroid restore file onto a PC?
dralways said:
I just tried that adb pull command mentioned in the post above and this starts to copy the entire contents of my phone to some unknown source on my PC (I can't find where?).
Click to expand...
Click to collapse
It copies to the directory that you ran the adb command from, so if you run abd from c:\windows\apps\adb it'll copy the files there
peachpuff said:
Use adb to pull the directory to your computer, adb pull /mnt/shell/emulated
Click to expand...
Click to collapse
Thanks for the help. I don't know why I didn't think to do that myself.
Create a folder on your computer and open the command prompt from that directory. And then run adb pull /mnt/shell/emulated/clockworkmod/backup
This way only the backups will be copied to your pc, not the whole storage.
cmd prompt not working
dushan90 said:
Create a folder on your computer and open the command prompt from that directory. And then run adb pull /mnt/shell/emulated/clockworkmod/backup
This way only the backups will be copied to your pc, not the whole storage.
Click to expand...
Click to collapse
Hi, I just ran into this issue also. I tried the cmd prompt but it doesn't pull anything. It says 'adb' is not recognized as an internal or external command, operable program or batch file.
Any help would be greatly appreciated, I know it's been a while since the last post but thank you.
SlickJamesBtch said:
Hi, I just ran into this issue also. I tried the cmd prompt but it doesn't pull anything. It says 'adb' is not recognized as an internal or external command, operable program or batch file.
Any help would be greatly appreciated, I know it's been a while since the last post but thank you.
Click to expand...
Click to collapse
>Go to your android sdk folder/platform-tools.
>r.click an empty space while holding down the shift.
>Select Open Command Window here
>then run the adb command
This should work
dushan90 said:
Create a folder on your computer and open the command prompt from that directory. And then run adb pull /mnt/shell/emulated/clockworkmod/backup
This way only the backups will be copied to your pc, not the whole storage.
Click to expand...
Click to collapse
how if I want to put it back into CWM? is there any specific way to do that? or I just have to copy and paste the data to the "/mnt/shell/emulated/clockworkmod/backup" directory.
Haven't you tried this?

[Q] ADB pull problem on linux

Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!
smokewagon said:
Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!
Click to expand...
Click to collapse
Maybe this will help?
http://www.herongyang.com/Android/adb-push-and-pull-Command.html
Not a big fan of the CLI.
Sent from my Nexus 7 (2013)
Your problem (almost certainly) is that you don't have a /sdcard directory (folder) on your computer unless you created one (there certainly is no default /sdcard in a linux desktop system).
I also don't know how you installed ADB on your computer.
(This should work, otherwise I'll have to change what I wrote below).
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
A little extra basic info for you, and welcome to linux. Soon you have the power to take over the world (ha ha ha... no, actually I'm not kidding at all).
As a basic rule, you should pretty much always be working inside of your home directory, for dealing with your personal files. Your home directory is /home/yourname. On my computers, my home is /home/kirk. My wife's home directory is /home/amy.
"~" is a shortcut for the home directory, for whomever is logged in at that moment.
If you wanted something that is on your desktop, it would be in the directory: /home/yourname/Desktop (~/Desktop). If you wanted to use your documents directory, it is : /home/yourname/Documents(~/Documents).
/home/yourname is where you usually where want to do your stuff.
"/" is the very root directory of the whole system, so you would be better off not creating and doing things like making directories like "/sdcard". That's a bad move. Leave root for system files. Not that you are necessarily going to destroy something by creating a /sdcard directory. But it'll cause you a few hassles.
So, use /home/yourname/sdcard (~/sdcard). Or if you want it on your desktop, (like I did above) use /home/yourname/Desktop/sdcard (~/Desktop/sdcard). Doing things inside of /home/yourname(~) means that you are the owner of that folder and everything in it, not root.
Otherwise you will just be causing headaches for yourself and having to grant yourself root permissions to work with those files (hassle). There's no good reason to do that to yourself. And if you did give yourself root permissions, and screwed up other stuff in the root directory like in: /etc or /dev or /bin, then you will REALLY be irritated.
Stick to your home for your personal files. /home/yourname (~)
Leave "/" or the "root" directory for system files.
You could check my little bash program for adb for Linux too. It's a program to be used in the terminal and it'll pull data off the sdcard etc. You can find it here
Sent from my Nexus 4 running Android 4.4
Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk
smokewagon said:
Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Try it without any installation of drivers just install adb tools and try the command line or my little tool. If it's not working, check the guides how to set up the usb-rules for adb
Sent from my Nexus 4 running Android 4.4
Thanks, will do.
Sent from my Nexus 4 using Tapatalk
iowabeakster said:
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
Click to expand...
Click to collapse
BAM INDEED! It worked! I am pulling the contents now. Thanks a ton, and thanks for the other basic linux info, I will put it to good use.
Any other tips on using Linux to root android?
Shooooot....
So after the pull command finished, i opened the sdcard directory I created on my desktop, and it was empty....the pull command said this when it was done...
1733 files pulled. 0 files skipped.
2129 KB/s (995292697 bytes in 456.480s)
Any ideas?
Ok, I played with some settings and got it to work, though I don't know why it worked.
USB Debugged is enabled.
The first time I tried to 'pull' i had my USB computer connection set to "Camera (PTP)" - it didn't work.
I tried again changing the USB computer connection to "Media device (MTP)" - it didn't work.
I changed it back to "Camera (PTP)" and my computer recognized it in a different way than the first time (a dialog box popped up asking me what I wanted to do with the pictures that were on the device I had connected, this didn't happen the first time).
I am glad the pull command finally worked, I just wish I knew why.
I guess it's a tough road being a linux NOOB and a (near) Android NOOB. It's good to learn something new and keep my brain young.

Categories

Resources