[Help] Magisk 17.1: No su prompts. - Magisk

Hi,
After updating magisk to 17.1, I don't get any SU prompts and even setting the prompt to grant automatically, apps aren't getting SU access. What do I do? It was working fine with v16.

bprayush said:
Hi,
After updating magisk to 17.1, I don't get any SU prompts and even setting the prompt to grant automatically, apps aren't getting SU access. What do I do? It was working fine with v16.
Click to expand...
Click to collapse
Uninstall Magisk completely and reinstall.

bprayush said:
Hi,
After updating magisk to 17.1, I don't get any SU prompts and even setting the prompt to grant automatically, apps aren't getting SU access. What do I do? It was working fine with v16.
Click to expand...
Click to collapse
Same here

Related

MagiskSU version of su fails, saying "Permission denied"

I recently had a problem (see here) with SuperSU, so I decided to give MagiskSU a try. As it turns out, it seems to have the same issue. When I run a process that requires su, it stalls for a while. In the case of MagiskSU, I then get "Permission denied" after about 20 seconds.
Here's what I get with a few basic commands:
Code:
[email protected]:/ $ su
Permission denied
Code:
[email protected]:/ $ su -v
8:MAGISKSU (topjohnwu)
Code:
[email protected]:/ $ su -V
8
Additionally, when I view the log with adb logcat, I see the following message attributed to su:
Code:
exec am failed with 2: No such file or directory
It looks like this is a message produced here, related to loading am.jar. Unlike in my SuperSU situation, this error happens regardless of whether Magisk is set to "prompt" or "grant".
Any idea how I can debug this? Thanks in advance.
Just to make sure: Have you updated the Magisk Manager so that it's just not the stub installed by the Magisk zip?
And if so, does the Manager report you're properly rooted?
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
Frankly I'm surprised this didn't render my phone unbootable! Nothing else was noticeably affected.
I have the same problem, just logcat says:
W/Magisk: su: request rejected (2000->0)
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
I found in the Magisk app under Superuser that "shell" had the toggle turned off. Once I turned it on, su worked in ADB.
Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
You are my Hero...
:good::good::good:Thank You Very Much brooo... :good::good::good:​
Hi all,
I have Magisk v18.1 and I'm also trying to get root access from shell. When I run 'su' in a terminal emulator, I get the message 'Permission denied'.
I did install "ADB & Fastboot for Android NDK" as suggested above. I also checked the root options in the magisk app (v7.0.0) and they are all the default, nothing unusual there.
Could you kindly advice if there is anything I can do in order to get root access from the shell with Magisk?
Thanks a lot in advance
I have a same issue on kitkat
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
geo909 said:
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
Click to expand...
Click to collapse
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
madbat99 said:
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
Click to expand...
Click to collapse
Honestly, that was a classic case of not knowing what I'm doing and just blindly following what other people tried. But good to know what the purpose of that module was, I was wondering!
Hint: Perfdump is the adb shell program, do not disable SU for it
I add my hint: after getting this error message, I checkd the list of apps in Magisk SU: it turned out that I had disabled the "Perfdump" app, because I did not know what it was. It is the adb shell indeed!
I had exactly the same problem on my Android 6.0 with Magisk v19.3 + Magisk Manager v7.3.1. I tried everything, what you wrote (enabled, disabled the "ADB and fastboot" stuff, checked the symlink, ...), but nothing helped me. FYI: previously, I used LineageOS 16 (Android 9.0) on the same phone with this latest Magisk without any problem (but I decided to turn back to the original OS version to avoid instabilities). But now I'm fighting with this dragon.
My wife has Android 6.0 also w/ Magisk, but she got Magisk v18.0 and this works well now... I tried this at me, and surprisingly, that was worked well. Now, I decided to find out, which is the last working version, where is the bug.
The results:
* the Magisk v18.0 with the bundled Magisk Manager - GOOD
* the Magisk v18.0 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v18.1 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v19.0 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.1 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.2 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.3 with the latest Magisk Manager v7.3.2 - BAD
I don't know, the freshest working Magisk v18.1 + Magisk Manager v7.3.2 is a good combination for all cases, but looks working.
Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
Yup thanks it still works up to date
Solved
i had the same problem on my redmi note 7 and the most easiest way is unistall your magisk 20.xxx and install a older one 19.xxx and that should do it but remember bouth zip file (flashibile zip) and magisk apk has yo be older than 20.xxx becouse the devs has made a mistake in the coding( or at leat this is what i think hope im wrong)
just update the magisk manager and install automatically the boot and reboot the phone it will be okay
Solution that works for me GalaxyS9 (starlte)
### restart adbd as root
adb root
### then
adb shell
### WORKS.
### I see '#' in prompt, `whoami` responses: 'root'
### My Magisk version. Reported by `su -v`
23.0:MAGISKSU

Magisk is not installed (v18.1), and Manager denied superuser rights

Hi,
I'm having a problem with Magisk 18.1. When I open Magisk Manager, I see the "Magisk is not installed" error message with the X in a red circle. However, Magisk Manager is up to date. I also get toast messages that say that "Manager was denied superuser rights". However, I'm able to get root in adb shell and entering "su".
If I refresh Magisk Manager by pulling down and releasing, then the following message:
Code:
Requires Additional Setup
Your device needs additional setup for Magisk to work properly. It will download the Magisk setup zip, do you want to proceed now?
Choosing "YES" will produce a "Setup failed." toast message. However, I see that now, "Magisk is up to date".
Despite this, I don't see the full set of Magisk settings (such as Magisk Hide, etc). Also, if I kill the process and reopen Magisk, I will get the same error message again.
I've tried downloading the Magisk v18.1 zip file and reflashing it in TWRP, but still no go.
Device: Nexus 5X with Android 6.0.1
Magisk: v18.1 (18100)
Magisk Manager: v7.0.0
Reflash stock rom and try to reflash if not work wait an update or try to downgrade version
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Sounds like you've ended up with two conflicting Magisk Managers installed (one repackaged, one not). Like this: https://www.didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
Didgeridoohan said:
Sounds like you've ended up with two conflicting Magisk Managers installed (one repackaged, one not). Like this: https://www.didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
Click to expand...
Click to collapse
Thanks! That was exactly it!
I'm running into the same problem. No dual install of manager, either.
Happens on a fresh from-scratch install of v18.1 on a Moto X Pure
Same here, clean install of v18.1 on Mi Max 3 (MIUI 10.2.1.0)
FWIW the problem still exists in v19, with it happening multiple times a day now in 19.3
---------- Post added at 01:31 PM ---------- Previous post was at 01:19 PM ----------
Check out this thread, esp. reply #14 (updated version) :
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
error as well v20.3 on Pocophone, Download and Install zip..installation error
go to settings>apps>magisk manager>allow storage permission.
Magisk update installation failed
I'm also having same problem with the latest update v20.4. I tried installing via Magisk app but it failed. I also tried flashing through recovery but same response.
I also had a similar issue, on a wiped phone. Magisk manager showing magisk not installed. However, using su from adb brought up a superuser request dialogue. I granted it, it hung for a minute, then when I reopened magisk manager it showed that magisk was successfully installed.
Solution
goister said:
Hi,
I'm having a problem with Magisk 18.1. When I open Magisk Manager, I see the "Magisk is not installed" error message with the X in a red circle. However, Magisk Manager is up to date. I also get toast messages that say that "Manager was denied superuser rights". However, I'm able to get root in adb shell and entering "su".
If I refresh Magisk Manager by pulling down and releasing, then the following message:
Code:
Requires Additional Setup
Your device needs additional setup for Magisk to work properly. It will download the Magisk setup zip, do you want to proceed now?
Choosing "YES" will produce a "Setup failed." toast message. However, I see that now, "Magisk is up to date".
Despite this, I don't see the full set of Magisk settings (such as Magisk Hide, etc). Also, if I kill the process and reopen Magisk, I will get the same error message again.
I've tried downloading the Magisk v18.1 zip file and reflashing it in TWRP, but still no go.
Device: Nexus 5X with Android 6.0.1
Magisk: v18.1 (18100)
Magisk Manager: v7.0.0
Click to expand...
Click to collapse
Just install Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip via TWRP
Can get it from here https://4pda.ru/forum/index.php?s=&showtopic=774072&view=findpost&p=97675211
Can't download this DM verity can't find it (used Google translator from Russian to English).
My problem is magisk manager says denied superuser so I can't use magisk hide since I can't reach it(limited options) but my fone is rooted and the new apps get grant or refuse and I can grant them superuser but need magisk hide for banking apps and all. On the latest magisk. Check attachment.
Please help please.
Cheers,
Roger
TheKicKer69 said:
Can't download this DM verity can't find it (used Google translator from Russian to English).
My problem is magisk manager says denied superuser so I can't use magisk hide since I can't reach it(limited options) but my fone is rooted and the new apps get grant or refuse and I can grant them superuser but need magisk hide for banking apps and all. On the latest magisk. Check attachment.
Please help please.
Cheers,
Roger
Click to expand...
Click to collapse
Check here:
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
tried EVERYTHING except clean ROM install. not working still says Magisk Manager denied superuser rights and magisk hide and all missing
TheKicKer69 said:
tried EVERYTHING except clean ROM install. not working still says Magisk Manager denied superuser rights and magisk hide and all missing
Click to expand...
Click to collapse
Uninstalled the Magisk Manager, and possibly also the hidden Manager (named "Manager" or whatever name you gave it) with the generic Android icon? And if you uninstalled both of them, installed the apk again manually?
nothing worked - wiped fone and reinstalled - magisk up and running again

No Magisk prompt when using SU apps

Hey!
I've successfully rooted my S10 (3rd time in a row) with Magisk. I've installed my daily apps, including Greenify, AFWall, AdAway etc. They all were prompting for SU access, and it went fine.
I had to reboot my phone. Since reboot, no app is asking for SU access. Apps that were granted SU access before reboot are working fine in Root mode, yet I can't SU any more apps.
Magisk Logs are fine, no errors, no crashing. I don't want to factory reset once again...
My Magisk modules: Busybox, Energized Protection.
What i've tried:
Updating Magisk to stable / beta
Running Magisk in safe mode
Hiding and restoring Magisk Manager app
Changing any option in Magisk Manager
Removing all modules
Using Magisk hide / disabling Magisk hide
Removing Magisk from battery optimisation mode
Everything else that I could find online...
I have no idea what to do now...
I can't grant SU to any other app...

Terminal Emulator and Magisk

I found the Terminal emulator app that I want to use to do some ADB for PC commands without needing PC and usb. su gives permission denied. So I decided to use Magisk - just installed the Magisk zip from recovery and the Magisk Manager, both are green light in Magisk menu. Now can it grant SU or do I still need SuperSU? SuperSU never worked for me. So Im trying to make it work for Terminal emu, how do I add the Terminal to Magisk's Superuser apps? I also downloaded ADB module from Magisk not sure if there's some ADB native command with it to do the same commands from the phone?
Oh never mind when I typed su in Terminal after having installed Magisk and all its stuff, finally it detected it and the app appeared in Superuser list in Magisk where I can toggle on or off.
xdaprogramm said:
I found the Terminal emulator app that I want to use to do some ADB for PC commands without needing PC and usb. su gives permission denied. So I decided to use Magisk - just installed the Magisk zip from recovery and the Magisk Manager, both are green light in Magisk menu. Now can it grant SU or do I still need SuperSU? SuperSU never worked for me. So Im trying to make it work for Terminal emu, how do I add the Terminal to Magisk's Superuser apps? I also downloaded ADB module from Magisk not sure if there's some ADB native command with it to do the same commands from the phone?
Oh never mind when I typed su in Terminal after having installed Magisk and all its stuff, finally it detected it and the app appeared in Superuser list in Magisk where I can toggle on or off.
Click to expand...
Click to collapse
You will have to
# cd /data/adb
then
# rm ./magisk.db
Do note that in doing so, you have erased all the grant history. However Magisk provides no other options to accomplish this. So this is it.

adb shell su - Permissions denied on rooted Pixel 4 with Magisk

Hey! I have Magisk 23.0 installed on my Pixel 4 (Android 12). The phone is rooted (I can grant apps SuperUser privileges and I also checked that with Root Checker). However, if I try to run su from the adb shell I get Permission denied error and on the screen of my phone it appears Shell was denied Superuser rights. Tbh I have no clue how to fix this, I tried to reboot the phone, clear the cache of Magisk, and set the "Automatic Response" in Magisk to "Grant". Any idea? Thanks!

Categories

Resources