search

meefik / linuxdeploy

Install and run GNU/Linux on Android
https://meefik.github.io/linuxdeploy
GNU General Public License v3.0
5.19k stars 678 forks source link

SSH + VNC fail ... Log with checked Debug #527

Open icefireCZ opened 8 years ago

icefireCZ commented 8 years ago

Phone: Lenovo A7000 Internal Storage: 16GB SDCard 90R/45W

Linux Deploy: 1.5.6-192 BusyBox: v1.24.2-meefik Android: 6.0 Arch: armv8l Kernel: 3.10.72+ SELinux: yes Loop devices: yes Support binfmt_misc: no Supported FS: exfat ext2 ext3 ext4 fuceblk iso9660 msdos vfat Mounted system: Kali GNU/Linux 2.0 (sana) Running services:

When i check Debug Mode and start it, it gives me this:

SSH [:22] ... ls: /data/local/linux/etc/ssh/: No such file or directory When i browse for /data/local/linux/etc/ssh so SSH folder/script is really MISSING

chroot: can't execute '/bin/su': No such file or directory When i browse for /bin/su in /data/local/linux so /bin/su EXISTS

chroot: can't execute '/bin/su': No such file or directory again

VNC [:5900] ... chroot: can't execute '/bin/su': No such file or directory chroot: can't execute '/bin/su': No such file or directory and again

I tried Updating ENV, reinstalling APP and whole Kali Linux, but nothing works.

When i try to execute for example this in Terminal Emulator: chroot /data/local/linux /bin/su - root -c 'which sshd' -p 22 it gives me: chroot: exec /bin/su: No such file or directory

It seems chroot somehow won't work with /data/local/linux /bin/su /bin/su behaves as if it don't existed in /data/local/linux or is bad chroot script

Thanks for any help.

fmsouza commented 8 years ago

I'm having the same problem when trying to load archlinux on my device. Mine's a Samsung Galaxy Note 10.1 (2014) SM-P605M.

I noticed that when I install the image with debug mode on, there is an error when trying to install things through pacman:

/usr/bin/pacman: error while loading shared libraries: liblz4.so.1: cannot open shared object file: No such file or directory

I'm running over latest mefik busybox and rooted. It was working before, but i deleted the image, reinstalled the app and tried to redeploy everything again from the beginning. The reason was that I wasn't assured of what I was doing in the first time, so I decided to do it again knowing what I was going to do.