Related
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
Hello,
i need help to create a small magisk module to make Samsung SHealth working again on my Samsung S20 Ultra 5G. At the moment device is rooted but /system is readonly. to make changes to build.prob a magisk module should work.
In build.prop the value of ro.config.tima=1 must be changed to 0.
That's all.
Maybe some of the experts could create a small magisk module for me?
Thanks!
If you can't create your own module, try MagiskHide Props Config. You can easily change prop values with that.
don't know how it works, but with your help shealth is now working.
thanks
Didgeridoohan said:
If you can't create your own module, try MagiskHide Props Config. You can easily change prop values with that.
Click to expand...
Click to collapse
Any tutorials how to use props-config?
rxk said:
Any tutorials how to use props-config?
Click to expand...
Click to collapse
I linked the relevant part of the docs above, but here's a link to the documentation in general:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
If all you want to do is to change a prop value, you just need to install the module, run the props command and pick the "Add/edit custom props" option and just follow the on-screen instructions.
Thanks mate. I not knowledgeable in doing this stuffs but i will try once i rooted my new galaxy s20 (xsa australian stock).
Still searching for easy to follow procedure on how to root s20 ultra.
Thank you.
rxk said:
Thanks mate. I not knowledgeable in doing this stuffs but i will try once i rooted my new galaxy s20 (xsa australian stock).
Still searching for easy to follow procedure on how to root s20 ultra.
Thank you.
Click to expand...
Click to collapse
As far as I've seen, if you can unlock the bootloader it should just be a matter of following the official instructions:
https://topjohnwu.github.io/Magisk/install.html
Of course, you might find more info on the S20 forums here on XDA.
Didgeridoohan said:
I linked the relevant part of the docs above, but here's a link to the documentation in general:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
If all you want to do is to change a prop value, you just need to install the module, run the props command and pick the "Add/edit custom props" option and just follow the on-screen instructions.
Click to expand...
Click to collapse
Hi didgeridoohan,
I already installed Magiskhide Prop Config and Busybox modules and termux app as well.
steps :
open termux >
su
ro.config.tima (but it returns not found)
I am not sure what the correct props command syntax for changing ro.config.tima to "0" for S Health to work.
Thank you.
rxk said:
Hi didgeridoohan,
I already installed Magiskhide Prop Config and Busybox modules and termux app as well.
steps :
open termux >
su
ro.config.tima (but it returns not found)
I am not sure what the correct props command syntax for changing ro.config.tima to "0" for S Health to work.
Thank you.
Click to expand...
Click to collapse
Well, yes... If you enter nothing but that into the terminal prompt that would be the result.
If you want to use the MagiskHide Props Config module to change the prop you'll have to start by running the command "props" (without quotation marks). Pick option 4 ("Add/edit custom props") and then follow the on-screen instructions.
If you need more info, the linked docs cover the use of the module pretty well.
Hello everyone, I try to create a module to replace my build.prop because I do not please change it (system play only).
I do not understand much to magisk modules, can someone make me the module or I can put my build,prop please?
Or if impossible to replace the buil.prop by magisk, can be add the line :
persist.debug.wfd.enable=1
Thank you I've been trying since yesterday and I really can't do it so it seems to be simple
You don't need a module to do that.
Edit: For future reference... I've been reminded that persist props are, well, persistent. No boot script is needed, just run the resetprop command and the value will remain set even across reboots. Until a new value is set, of course.
Simplest way is to just use a boot script and the resetprop tool:
Code:
resetprop persist.debug.wfd.enable 1
Or if you really want to use a module you'll just have to add the line to system.prop and nothing else:
Code:
persist.debug.wfd.enable=1
Or you could use MagiskHide Props Config and the custom prop feature.
And Magisk doesn't actually alter the build.prop file:
https://github.com/Magisk-Modules-R...etting-a-custom-prop-or-removing-a-prop-value
Thank you for this quick response. I'm going to try to figure out how to do this script because I really don't know all this
Hi, I solved the problem with the module activated and in termux
Code:
su
Props resetprop persist.debug.wfd.enable 1
Now he finds the TV but restarts the phone as soon as he connects on it
If you're having problems creating a boot script it might be easier to use the MagiskHide Props Config module. It'll do it for you.
Hi, I aI think I did it. Here's how to do it with the installed module magiskhide props
Code:
su
Props resetprop persist.debug.wfd.enable=1
He finds me the TV, but as soon as he connects to the phone restarts is there a way to solve this problem?
chuppito said:
Hi, I aI think I did it. Here's how to do it with the installed module magiskhide props
Code:
su
Props resetprop persist.debug.wfd.enable=1
He finds me the TV, but as soon as he connects to the phone restarts is there a way to solve this problem?
Click to expand...
Click to collapse
I'm not sure what you're doing there, but that's not right...
If you're gonna use MagiskHide Props Config, just run
Code:
su
props
And then pick the "Add/edit custom props" menu (#4). Follow the on-screen instructions to set your prop.
If you're going to use resetprop as a standalone tool you run:
Code:
su
resetprop persist.debug.wfd.enable 1
That will only survive until a reboot though, which is why you would have to put the line in a service.d boot script if you want it to be permanent.
Edit: For future reference... I've been reminded that persist props are, well, persistent. No boot script is needed, just run the resetprop command and the value will remain set even across reboots. Until a new value is set, of course.
If I use props, I have no options
If I use setprop it doesn't tell me anything
Edit :
With props where I have more options I managed to do.
It was already on 1 while it started again several times.
I watch as soon as I get home if it connects or restarts as soon as it tries
The TV is well detected but as soon as I try to connect, the phone makes a small reboot
chuppito said:
If I use props, I have no options
If I use setprop it doesn't tell me anything
Edit :
With props where I have more options I managed to do.
It was already on 1 while it started again several times.
I watch as soon as I get home if it connects or restarts as soon as it tries
Click to expand...
Click to collapse
Does your edit mean you figured it out? If you didn't, here goes:
From your first screenshot, showing the props module ui, it tells you to "Enter the prop to set". So if you enter persist.debug.wfd.enable you'll get to the next screen where you can enter your desired value (and also see what the current value, if any, is).
The second screenshot is exactly as it should be. You're not supposed to get any feedback if it works.
About your other issues, I have no idea...
Yes I was able to understand how it works. I found a post for other problems on xda, if I understand, google deleted files last July to make this trick obsolete and sell its chomecast
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.
Hi guys,
I'm trying to make a script to enable the android 11 notification shade blur in my pixel 2 xl,, so far I have managed to successfully enable it with ADB with this command:
adb shell
taimen:/ $ su
taimen:/ # setprop ro.surface_flinger.supports_background_blur 1
taimen:/ # stop
taimen:/ # start
It does work fine but as soon as the phone reboots it is lost
I made a magisk module and also managed to make a setprop mod with magiskhide that does indeed successfully add ro.surface_flinger.supports_background_blur 1 in build.prop, but the mod does not work unless I adb and input the command
adb shell
taimen:/ $ su
taimen:/ # stop
taimen:/ # start
I believe this is to restart system UI.
Is there any way to do this in magisk automatically at boot?
When I input in termux
su
# stop
The phone seems to try to restart the UI but it gets stuck in google logo, unlike when I do it via adb the screen goes blank and comes back alive when I input via adb
# start
I'm a complete noob in this stuff, I would really like to make a magisk script or module that let me do this, it would be useful to try first via termux to avoid a magisk boot loop in case something goes wrong with this script. The notification blur is actually the only reason I unlocked the bootloader an rooted the phone...
Thanks in advance.
You should use Magisk's resetprop tool.
All you should need in your boot script is this:
Code:
resetprop ro.surface_flinger.supports_background_blur 1
Try using service.d first, but if that doesn't work move the script to post-fs-data.d.
Or, if you're using a module, use a system.prop file.
Does "magiskhide props config 5.3.6" uses resetprop?
I did try that in service.d and post-fs-data.d
As I said, the property does seem to be changed with the setprop, since after a restart of the phone all I need to do is
Adb shell
Su
Stop
Start
And I get the blurred notification shade...
Yes, MagiskHide Props Config uses resetprop (but there you generally don't need to change to late_start service or post-fs-data, the default should be fine most of the time).
With resetprop you shouldn't need to run stop/start. That's the difference.
I did not try the delay option. I really don't know what else I could try though...
Maybe there's a delayed script I could run with the stop/start command?
Edit: sorry if I understand what you're saying, should I delete the magiskhide props config key and instead do it manually? That way I should no need the stop/start command.
I thought you had been doing it manually all along... To quote your first post: "I'm trying to make a script", "I made a magisk module and also managed to make a setprop mod".
If the stop/start commands need to be included for this to work, making your own boot script with the resetprop command and stop/start commands is the way to go.
Yeah yeah sorry, I did manage to make the module, the setprop mod I was referring to was via magiskhide...
My problem is when I try to run this stop/start script in termux
#!/system/bin/sh
su
cd
cd data/adb
stop
start
The phone goes to google logo and is stuck there, I'm afraid if I do that with magisk I could get a non booting phone...
Does this script sounds good to you?
#!/system/bin/sh
resetprop to.surface_flinger.supports_background_blur 1
stop
start
BTW I really appreciate your help!
Edit: just ran this script from termux and stuck at google logo...
Edit 2: if anyone is wondering or maybe it helps someone I ended up making this simple script in service.d
resetprop to.surface_flinger.supports_background_blur 1
Then I discovered all I needed was the terminal command
# killall surfaceflinger
And Systemui does successfully restart with the blurred background, so I created a home screen shorcut with this terminal command and all I need to do is hit the shorcut shortly after booting and it works, it's not automatic but it gets the job done...
Thanks @Didgeridoohan for your help... XDA rocks!
Hello!
I don't know if you're still looking for this but decided to share anyway.
Attached to this post is a Magisk module that enables Background Blur that survives reboots....
It's weird that a simple Magisk module with a system.prop doesn't work but ok... had to create this version which uses a service.sh script to do the job.
You'll need Magisk, obviously.
Enjoy!
Cheers!
Thank you for making this. The double restart is kinda annoying tho
Typhus_ said:
Hello!
I don't know if you're still looking for this but decided to share anyway.
Attached to this post is a Magisk module that enables Background Blur that survives reboots....
It's weird that a simple Magisk module with a system.prop doesn't work but ok... had to create this version which uses a service.sh script to do the job.
You'll need Magisk, obviously.
Enjoy!
Cheers!
Click to expand...
Click to collapse
Is this module device specific or will it work on other devices running Android 11?
rodken said:
Is this module device specific or will it work on other devices running Android 11?
Click to expand...
Click to collapse
It should work on any device running Android 11.
Typhus_ said:
It should work on any device running Android 11.
Click to expand...
Click to collapse
Perfect - functions as expected on OnePlus 8 OOS 11.
How about android 13?