-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access denied #1
Comments
Ok |
1 similar comment
Ok |
Thanks |
sorry, how you solve the problem? |
Updated I thought that an update fixed the problem, but I was wrong. I was accidentally using simple BusyBox by putting the new path in the initial command. When I only used BusyBox no root, I can't access busybox.
…On Fri, Aug 31, 2018, 11:53 PM Alsan Wong ***@***.***> wrote:
sorry, how you solve the problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AglYzaCmgn2WaJqvBgmbuQ3Di2JUs9zrks5uWhK5gaJpZM4UcCdG>
.
|
I'm able to install busybox with no root, but does the phone need root permission to actually run the busybox commands? In other words is this app just for installing busybox? It appears that the app installs busybox on my unrooted phone correctly, but I'm not able to run any commands since I'm not root... ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a LG X Charge with Android 7.0 kernel 3.18.31, security patch Nov 6, 2017
and I get access denied try to cd to the directory. I got busybox not found.
H=$PATH:/data/user/0/exa.free.bbin/files <
H=$PATH:/data/user/0/exa.free.bbin/files <
lv7:/ $ echo $PATH
/vendor/bin:/system/bin:/system/xbin:/data/user/0/exa.free.bbin/files:/data/user/0/exa.free.bbin/files
lv7:/ $ busybox
/system/bin/sh: busybox: not found
127|lv7:/ $ cd /data/user/0/exa.free.bbin/files
/system/bin/sh: cd: /data/user/0/exa.free.bbin/files: Permission denied
2|lv7:/ $
The text was updated successfully, but these errors were encountered: