![]() Also mind that the Android/su shell syntax is quirky, to say the least: I finally got these to work using the system path (and note these must be copies with root ownership - not symlinks to original files). passing a -e '/data/data//dropbear/ssh' argument, or adding the directory to beginning of PATH - but got the same results. Rsync error: error in IPC code (code 14) at jni/pipe.c(84) Rsync: Failed to exec ssh: Permission denied (13) First of all, even though I could run both /data/data//dropbear/rsync and /data/data//dropbear/ssh individually, running the common rsync -avPHK /data/ failed again due to permissions error:.Alas, this idea got broken on several accounts: Well, I thought, if I can log in by SSH and do su easily, I can just run the utilities from command line to start the rsync session from the phone to PC's SSH server. That should have been easy to do with rooting support in both Android toolkits, but on this phone the SimpleSSHD did allow me to connect (and with public-key auth available for free, unlike SSHDroid) - but only as a "user", and SSHDroid could not start at all due to some execution errors. Alas, this team failed for me on a particular older phone that I wanted to slurp to the PC "as is" for all accessible files (including system ones) keeping their original permissions and owners, which of course needs root on both sides. They even include niceities like rsync and ssh binaries that are quite useful. During my backup adventures, I came across many nice tools, such as SSHDroid and SimpleSSHD that allow me to SSH from my computer to the Android device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |