I've seen this happen once yesterday. Are you on 4.4.4 now or on L? ART or Dalvik?
I think it's related to another issue I've seen, which causes an internal VM crash sometimes, but not sure yet. Can you adb shell, manually kill -9 the eu.chainfire.supersu app and restart it from the launcher, see if it works then? That did solve the issue for me. Or does it just never work, even not after reboots?
I'm trying to use the su --mount-master option, so that I can mount external storage system-wide, accessible to user apps.
su reports no errors, mount reports no errors, but the storage is only accessible to root.
Running KK on Note 3. What's wrong?
Great stuff! I've been following your documentation/updates on context switching, and was wondering if it'd be possible to implement that with the su interactive shell.
I'd like to execute "su --context u:r:untrusted_app:s0" and have a # prompt where all my entered commands execute under that context. Currently it seems to just hang.
There's no terminal access that way. Have you tried simply typing "id"<enter> and seeing if it outputs anything?
The $ prompt has an untrusted_app context, but the # prompt has an init context. Is there any way to change the context of the root (#) prompt? If not, could there be? :fingers-crossed:
There are some definite usage cases where this would be handy for binary execution on /data, we could just specify the context when calling the prompt, like "su --context u:r:untrusted_app:s0". su could just check to see if there's another argument (like -c) after --context; if so execute the supplied command, and if not then open the interactive # shell with the specified context. That would be slick.
Either something is not working, you don't know what you're doing, or I don't understand what you're saying.
su --context u:r:untrusted_app:s0 will generally give you a silent terminal. i.e. what you type is being executed, and you get to see the results. However, you don't see what you type and do not get a prompt. So just typing "id" followed by pressing enter in here should show you output.
su --context u:r:untrusted_app:s0 -c id will execute the command "id" as untrusted_app and return.
If either of these things does not work as described, then there is something wrong.
Ah, my apologies. I didn't catch your meaning! Okay, great, it actually does work! Output of id is untrusted_app from the silent terminal, like you said. Thanks!
So I guess my real request should have been: any way to change context for the interactive shell and still have the terminal not silent, e.g. "[email protected]:/data/local/ #" like normal?
Use system_app Maybe sometime I'll port this to untrusted_app but it's a ****load of hassle for very little gain
sh: No controlling tty: open /dev/tty: No such device or address sh: warning: won't have full job control
I don't know what's going on, but I do know this is not a v2.01 specific thing, as nothing has changed that could influence that.
I Have note 3 n900 with official 4.4.2 ... I flashed Super SU 2.01 From recovery but now i faced this ERROR!
Please Help me
i got a problem on my note 2 gt-n7105, supersu has stopped, this the message that continuously appear on screen.
Actually the firm is a stock 4.4.2. NEE stock base, with root as per yr. procedure.
I follow week all the step described in a different guide (including yours).
I imagine that supersu is the latest version, it's impossible to uninstall from the phone and consequently i can't to reinstall it.
please could you suggest me the right way to solve this problem. Thank you very much in advance.
Preliminary update for Android 4.2's multi-user capabilities.
Only the main user can run the UI and gain root access.
Secondary user's apps will not be granted root, nor can
those users change SuperSU configuration.
This is all temporary. Proper multi-user support is being
Note that if a non-user process (like ADB shell) needs to
prompt for root, that prompt will always appear on the
MAIN user's screen !