Magisk v18.0 adb shell: su not found - Magisk

Hi
I rooted my Nexus 5 with custom rom Paranoid androind 7.3.1(Nougat 7.1.2) using Magisk v18.0
When I run the su from adb shell, it says su: not found
Code:
C:\windows\system32>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
​
I looked in Magisk Manager -> SuperUser, to check if shell needs toggle to enable root, but didnt find the entry for shell. Please help

First make sure that adb shell is working as it should and then take a look at the "Superuser Access" setting in the Magisk Manager. It should be set to "ADB only" or "Apps and ADB".

Didgeridoohan said:
First make sure that adb shell is working as it should and then take a look at the "Superuser Access" setting in the Magisk Manager. It should be set to "ADB only" or "Apps and ADB".
Click to expand...
Click to collapse
"make sure that adb shell" - How do I do this?
Superuser Access is set to "Apps and ADB" in Magisk Manager

Related

Latest SuperSU stalls indefinitely on new systemless install, Moto X Pure Edition

I recently got a repaired Moto X Pure Edition running Marshmallow. I unlocked the bootloader and used fastboot to start TWRP, then set up the systemless install of SuperSU 2.79. The installation seemed successful. I watched it patch the boot image and upon reboot, the SuperSU app was available. It seems happy when I run it.
However, if I run the terminal emulator and type "su", it stalls indefinitely. Nothing happens. The SuperSU "allow/deny" dialog does not appear and nothing shows up in the SuperSU logs. The same happens when I run su via "adb shell" on my PC. TitaniumBackup also stalls when it starts with "Detecting SU and Busybox".
I originally installed SuperSU 2.79, then found the SR3 update and installed that as well. Both had the same problem. The su binary is not completely broken, as some commands work.
Some commands that work:
Code:
[email protected]:/ $ su -v
2.79:SUPERSU
Code:
[email protected]clark:/ $ su -V
279
Code:
[email protected]:/ $ su --help
SuperSU v2.79 (ndk:arm64-v8a) - Copyright (C) 2012-2017 - Chainfire & CCMT
...
Any idea why SuperSU isn't working?
Okay, here's another data point. I switched the default permission from "Prompt" to "Grant", and I can get root. The problem has something to do with showing the dialog.
I figured it out. In a previous cleanup attempt, I failed to restore the link named /system/bin/app_process that points to /system/bin/app_process64. This fixed it:
From the TWRP terminal:
Code:
mount /system
cd /system/bin
ln -s app_process64 app_process

Supersu is still unable to access permissions after authorization

Please excuse my poor English
After HUAWEI mate10 brushes into supersu2.82 SR5,
Open supersu prompt without obtaining root permission
But use
ADB shell
$su
Stuck in here, does not appear #
If you uninstall supersu, then execute it
ADB shell
$su
#
There will be root
I'm sorry, I don't have permission to publish pictures
bbs.xxroot.com/data/download/1.jpg
bbs.xxroot.com/data/download/2.jpg
bbs.xxroot.com/data/download/3.jpg
Sorry, I can only send pictures to other forums, the above is the web site!
@Chainfire
@Chainfire
@Chainfire

Magisk/E: Unknown id: pm, with "pm uninstall" shell command

Hi, i have a Nexus 6P based on 7.1.1 with Magisk root v14.0 with Magisk manager v14.0.
With the terminal emulator app i'm trying to execute this commands:
Code:
su
pm uninstall org.telegram.messenger
But i got an error: Android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died etc..
But if i connect my Nexus 6P to my pc, and via ADB i try to push this command
Code:
adb shell pm uninstall org.telegram.messenger
It works. I don't know if it's related to Magisk, but i tried to build an app made by that execute "pm uninstall org.telegram.messenger" after "su" to get root shell but nothing, i got only an error on my android monitor: "E/Magisk: Unknow id: pm" and obviously telegram has this package name and it is installed as user app. Someone can help me ?
smartandroidtech said:
Hi, i have a Nexus 6P based on 7.1.1 with Magisk root v14.0 with Magisk manager v14.0.
With the terminal emulator app i'm trying to execute this commands:
Code:
su
pm uninstall org.telegram.messenger
But i got an error: Android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died etc..
But if i connect my Nexus 6P to my pc, and via ADB i try to push this command
Code:
adb shell pm uninstall org.telegram.messenger
It works. I don't know if it's related to Magisk, but i tried to build an app made by that execute "pm uninstall org.telegram.messenger" after "su" to get root shell but nothing, i got only an error on my android monitor: "E/Magisk: Unknow id: pm" and obviously telegram has this package name and it is installed as user app. Someone can help me ?
Click to expand...
Click to collapse
Are you able to uninstall the normal way thought settings>apps?
Sent from my H1611 using Tapatalk

Magisk command line

Is there any way I can do things like enable magiskhide or grant su access from the su command line?
If you type "su" you still need to grant root access in dialog pop-up.
For enabling denylist:
Code:
magisk --denylist enable
More here:
Magisk Tools
The Magic Mask for Android
topjohnwu.github.io

How to grant magisk su permissions to an app using adb?

Hello,
I am developing an app that requires su permission, whenever I reinstall it I have to grant permissions again on first launch. Is there a way I can grant the app su permissions using adb while the phone is connected to the computer?
Ideally I want a script that has:
Code:
adb install myapp.apk
adb shell su -c 'grant magisk permission'
Thanks,
Z

Categories

Resources