Permission denied #703
Comments
|
Do you have root access? |
|
Yes, l have root |
|
I reinstall application, reinstall os, but not solve this problem. |
|
Please install BusyBox in /system/xbin. Try to change "Settings -> PATH variable" to /system/xbin and run "Settings - > Update ENV". Also image size set up to 2047 MB (busybox mke2fs limitation). |
|
Busybox /su/xbin Now :02:55] ## bootstrap/rootfs : do_install && do_configure |
|
Which version of BusyBox installed? |
|
21:04] ## core/mnt : do_start directory Busybox 1.26.2 meefik and stericson |
|
46:39] chroot: can't execute '/bin/su': No such file or directory Súpersu sistemless 2.79 |
|
I'm solve this problem :) |
|
On some Android platforms, there may be a 'grep' command located elsewhwere under the pathnames in the app's shell process environment and listed in $PATH – such as /system/bin/grep – in addition to the 'grep' command installed by Meefik's BusyBox distro – such as at /system/xbin/grep. At the user's option, one may run a shell command, 'which grep', in an ordinary terminal emulator so as to determine which grep command is being located, first, by the respective shell command interpreter. One may wish to rename the "Dysfunctioning grep", to accomodate the grep installed with the respective BusyBox installation process. Of course, the "Dysfunctioning grep" may have been installed on a read-only partition – in which instances, one might consult documentation about rooting one's Android device and correspondingly, an app such as LSpeed, so as to be able to remount the partition in read-write mode, sufficient to rename the respective 'grep' shell command. Personally, though I'm not too well familiar with the partitions/mount points layout in Android platforms, I wonder if the issue may be correlated with the set of permissions with which the respective partition is mounted, in which there is the "Dysfunctioning grep"? If it may be an issue of pathnames, maybe the LinuxDeploy app may exec the "Ideal Grep" with a complete shell pathname, in a future update? With an appropriate app deployment – permissions-wise – perhaps LinuxDeploy may even read a shared configuration property from the respective BusyBox app, to determine the BusyBox installation prefix, automatically. Perhaps there is a work-around, however, or it may not be an issue of pathnames. When running the LinuxDeploy menu command, 'Status', I'm seeing a similar "Permission Denied" issue during exec for the fdisk and sed commands, as well as the singular 'grep' shell command. The former commands are installed under xbin, but I'm not all too certain of their source otherwise. I've uninstalled a secondary BusyBox distro – now having only one BusyBox installed – and rebooted the tablet, still seeing the 'exec' issue. Perhaps it may be a matter of the filesystem permissions, towards however the respective filesystem is mounted, if not the shell process permissions with which the commands are applied to exec? I see that the app already does 'su', before calling those shell commands. Maybe it may be anyhow correlated to SE Linux and Samsung Knox, alternately? |
Settings of linux deploy:
Properties:
remote conntection:
|
|
@carver2 this helps thanks. A common mistake poeple do also is downloading the wrong busybox, there are several busybox programs out there make sure you download the one from @meefik |
|
Setting the Installation Path to ENV_DIR, as shown, solved my problem (in Android 10). Directory installation also works inside the ENV_DIR. |
|
Changing install directory to ${ENV_DIR}/rootfs/linux has also helped me, thanks @carver2 |
I have meefik busybox
Install button ----> permission denied
Configure button ------> permission denied
The text was updated successfully, but these errors were encountered: