yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
You'll need to remove SuperSU completely, including a boot image without SuperSU patches. The unSU script does not alter the boot image. MagiskSU is required for Magisk Hide to fully function and you can't have Xposed active if you want to pass SafetyNet with Magisk Hide.

There... Now I've held your hand long enough. :D Time for you to do some work yourself. :good:
[Magisk] neth15:
Hey guys, I got little problem. I'm using stock 7.1.2 beta 2 on my Nexus 5X with Magisk root, few modules and one system modification to get second speaker work as tweeter while playing media.

After enabling Magisk Hide and ticking my online TV app (which doesn't work with root), I get successful SafetyNet check and app works, no problem here. However, I can't see Google Play Services here in list of apps in Magisk Hide, so I can't install Super Mario Run. I know I can install it as .apk and tick that, but being unable to do something pisses me off.

Ticking Google Play Store solves nothing. Any ideas?
[Magisk] Artim_96:
Play services in terms of SafetyNet is automatically checked and hidden, checking play services itself wouldn't change anything
[Magisk] neth15:
Nice then, thanks. So, how to convince GP that I'm not rooted and install Super Mario Run, for example?
[Magisk] Artim_96:
Play store doesn't care if you are rooted or not. If you can't install it your device isn't compatible. Maybe country restrictions, maybe Android version restrictions, maybe other, but never root
[Magisk] bigo72:
You can flash Magisk 11.6 and run Supermario, loosing the ability to run every Webview app (like Twitter or the new Google phone app) .... or just forget it and go back to SuperSU, until Magisk people does the .... magic.
[Magisk] neth15:
I see you are not well informed. Otherwise it would be country or OS version restrictions, but Super Mario Run thing is different.

http://www.theandroidsoul.com/cant-download-super-mario-run-play-store-get-apk/

It seems that there're some solutions, but thanks anyway :)

https://xdaforums.com/android/apps-games/make-super-mario-run-rooted-android-t3577748
[Magisk] Newmanl:
What do you mean? Did you lost the ability to use webview within the apps? Don't get me wrong, I'm still able to use webview in Twitter for example, just curious about it.
[Magisk] Artim_96:
That error doesn't seem root related. There is a difference between play store being buggy and throwing out errors and an app not running on a rooted device
[Magisk] billiepreks:
I use Magisk v11.6 since fews days now, and I've 0 problems with Twitter or Google Dialer
[Magisk] neth15:
Definitely not. Personal experience: Android O without root found and installed Super Mario Run without any problems, 7.1.2 doesn't even show GP page with the game. In desktop version of GP, my device is greyed out.
[Magisk] Maquina07:
Hello guys i have a note 4 with resurrection remix, with magisk and xposed systemlees, but don´t pass safetynet SafetyNet Failed: CTS profile mismatch.

Any idea? Thanks!
[Magisk] Didgeridoohan:
Holy Moly.... This one question has been answer so many times now I'm surprised the form doesn't automatically rejects it...

Idea: Xposed. And to answer your next question: No. It doesn't matter that it's systemless.
[Magisk] bigo72:
I'm curious to understand if there is a workaround for this issue.

Android 7.1.1 on AospExtended ROM 3.3 - Mini Dynamic Gapps

Same rom on two devices (Moto G 2015 and Oneplus 3T).

Please guys, don't blame the ROM, it happened again to me on Brokenos two days ago, so it's not a ROM issue (even if it can be a kernel issue, to say the truth: both roms uses LineageOS kernel.

If SafetyNet is passed, every webview app force closes. If I uninstall Magisk and install SuperSu, no SafetyNet passed and WebView apps are working great.

Please tell me if I can help with any log, I don't know, I'm sure I'm not the only one with this issue.

What's your secret?
[Magisk] billiepreks:
I assume it's because of ported version of Magisk for Pixel devices
[Magisk] Newmanl:
Sorry but I don't know how to help...Just for letting you know:

Nexus 5

Lineage OS 20170328

Magisk manager

And MagiskSu

Everything working fine here so far even the webview
[Magisk] billiepreks:
Tried, but of course doesn't works : the installation zip method was modified to works with dual slot of Pixels devices

Yeah I know it's not officially supported, I'll take my chance maybe someone has my answer ! :)

But now I've understand I must wait for official support
[Magisk] Didgeridoohan:
Provide at the minimum a Magisk log (with the issue active) but a logcat from when an app force closes would be useful as well. If you don't know how: https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
[Magisk] Captain_Throwback:
Try disabling the setting of the "ro.build" props in /magisk/.core/magiskhide/enable and see if that fixes your issue.

(I'm assuming you have Magisk Hide enabled?)
[Magisk] holymoz:
Would be good if download section could be sorted by most recent added so I dont have to watch entire list to see if there is a new module
[Magisk] culiacanazo:
Pretty sure that'd be in the works in a not-so-distant future, but the (module) list isn't as big that it takes priority, even with unlisted modules installed.
[Magisk] ShadySquirrel:
I'm too on Magisk v11.6 and no issues with Twitter (not ussing google dialer), only issues with randomly stopping su daemon. Device: Huawei Kiwi, LineageOS build from 29.03, AOSP WebView.
[Magisk] bigo72:
Thank you!

THIS is Magisk internal log, before and after few crashes (gMail, Whatsapp, Twitter, Phone app). To my eyes it looks like the same, there are no differences.

THIS is my logcat during and after Twitter and Whatsapp crash.

I swear I will bless you forever if you solve this to me!

Jokes apart, I did logcats on MotoG2015 because mu Oneplus3T is my daily driver and I switched to SuperSU to make it usable.

Thanks again for your help.
[Magisk] Captain_Throwback:
Did you try what I suggested? I suspect the ro.build.type is your issue.
[Magisk] Scarface05:
I'm currently using a OP2 with CosmicOS(AOSP based ROM).

I was on 11.1 and everything was perfect.

I updated my ROM exactly as per instructions.

I then flashed the 11.6 version which caused apps like Gmail, Pocket, Amazon etc to stop. It was even causing Google Play Services to stop.

Someone​ directed me to flash 11.6-fix and I did. That didn't solve the problem.

I downgraded to 11.1, now the apps don't stop but the safety net fails! It used to pass earlier on 11.1.

What do I do?
[Magisk] Captain_Throwback:
https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post71654787
[Magisk] bigo72:
Yes, Magisk Hide is enabled, of-course.

This method looks interesting. I found the file and accessed it with superuser privileges.

I can see few rows with ro.build. What exactly have I to do?

I'm assuming with "disabling" you mean writing "#" at the beginning of the row.

In example I can read:

BUILDTYPE='getprop ro.build.type'

BUILDTAGS='getprop ro.build.tags'

BUILDSELINUX='getprop ro.build.selinux'

So, do I have to comment all of this rows?
[Magisk] Captain_Throwback:
Yes, comment those and the rows below that check and (re)set the ro.build* props. And then reboot and see if your Webview apps are working again.
[Magisk] anshulsingh:
Finaly I have it all working(PoGo, mario etc..). Thanks to all who helped me in this forum. Presently I am on phroneses N7 Rom V5.2 for samsung note 3 and with lss kernel . I tried many permutations and combinations with magisk and various superusers and here is what worked for me without flashing any other boot image. After so many attempt of trial and error my rom was cluttered with various xposed modules and so I thought of starting from the begining. I am not sure of the reason why it worked this way but at least it worked for me

1. Uninstall xposed module if you have using uninstaller from this link. I had the "xposed V87 sdk23" installed from the same thread so I removed it.

2. Reboot the phone and uninstall the xposed stub from the menu.

3. Uninstall any version of magisk using uninstaller from this link.

4. Reboot the phone and uninstall the magisk manager from your phone.At this stage my phone was basically at the original factory state. I checked the root status using root checker and the phone was rooted.

5. Unroot the phone by flashing UnSu script zip file. At this stage when you reboot the recovery might ask you to root the phone again.Select No this time. After reboot check again and the phone should not be rooted.

6.Now flash the moded magisk v11.6 from this link and reboot and again select No at the root prompt shown by recovery while rebooting. I have no idea for other roms but this modded magisk works for Phroneses rom N7 v5.2 .

7.Install the magisk manager from the play store but dont install the magisk from the manager.we have already flashed the moded magisk.

8.In the magisk settings I have Magisk hide -ON, and super user disabled. See the attached screenshot.

9.Tap the "safetynet check" and it should pass.If not reboot the phone. Again if not turn off the usb debugging as well as the devellopers option and reboot again and it should pass this time.

10. In the magisk hide I had PoGo checked (handeled by magisk itself) but mario unchecked.

Now I am able to play both the games. Havn't tried with other apps but I guess they too should work.

I hope this helps the other users.
[Magisk] bigo72:
OK, what I did (and it didn't worked after the reboot)

I'm marking in red my comment simbols #:

#!/system/bin/sh

MODDIR=/magisk/.core/magiskhide

BINPATH=/data/magisk

LOGFILE=/cache/magisk.log

TOOLPATH=/dev/busybox

log_print() {

echo "MagiskHide: $1"

echo "MagiskHide: $1" >> $LOGFILE

log -p i -t Magisk "MagiskHide: $1"

}

# Only enable when isn't started

ps | grep "magiskhide --daemon" | grep -v grep >/dev/null 2>&1 && exit

if [ ! -d /sbin_orig ]; then

log_print "Moving and re-linking /sbin binaries"

mount -o rw,remount rootfs /

mv -f /sbin /sbin_orig

mkdir /sbin

mount -o ro,remount rootfs /

mkdir -p /dev/sbin_bind

chmod 755 /dev/sbin_bind

ln -s /sbin_orig/* /dev/sbin_bind

chcon -h u:object_r:rootfs:s0 /dev/sbin_bind /dev/sbin_bind/*

mount -o bind /dev/sbin_bind /sbin

fi

# Sammy device like these permissions

chmod 640 /sys/fs/selinux/enforce

chmod 440 /sys/fs/selinux/policy

log_print "Removing dangerous read-only system props"

VERIFYBOOT=`getprop ro.boot.verifiedbootstate`

FLASHLOCKED=`getprop ro.boot.flash.locked`

VERITYMODE=`getprop ro.boot.veritymode`

DEBUGGABLE=`getprop ro.debuggable`

SECURE=`getprop ro.secure`

#BUILDTYPE=`getprop ro.build.type`

#BUILDTAGS=`getprop ro.build.tags`

#BUILDSELINUX=`getprop ro.build.selinux`

[ ! -z "$VERIFYBOOT" -a "$VERIFYBOOT" != "green" ] && \

log_print "`$BINPATH/resetprop -v -n ro.boot.verifiedbootstate green`"

[ ! -z "$FLASHLOCKED" -a "$FLASHLOCKED" != "1" ] && \

log_print "`$BINPATH/resetprop -v -n ro.boot.flash.locked 1`"

[ ! -z "$VERITYMODE" -a "$VERITYMODE" != "enforcing" ] && \

log_print "`$BINPATH/resetprop -v -n ro.boot.veritymode enforcing`"

[ ! -z "$DEBUGGABLE" -a "$DEBUGGABLE" != "0" ] && \

log_print "`$BINPATH/resetprop -v -n ro.debuggable 0`"

[ ! -z "$SECURE" -a "$SECURE" != "1" ] && \

log_print "`$BINPATH/resetprop -v -n ro.secure 1`"

#[ ! -z "$BUILDTYPE" -a "$BUILDTYPE" != "user" ] && \

log_print "`$BINPATH/resetprop -v -n ro.build.type user`"

#[ ! -z "$BUILDTAGS" -a "$BUILDTAGS" != "release-keys" ] && \

log_print "`$BINPATH/resetprop -v -n ro.build.tags release-keys`"

#[ ! -z "$BUILDSELINUX" -a "$BUILDSELINUX" != "1" ] && \

log_print "`$BINPATH/resetprop -v -n ro.build.selinux 1`"

touch $MODDIR/hidelist

chmod -R 755 $MODDIR

# Add Safety Net preset

$MODDIR/add com.google.android.gms.unstable

while read PROCESS; do

log_print "Killing $PROCESS"

set --

set `$TOOLPATH/ps -o pid,args | grep "$PROCESS" | grep -v grep` >/dev/null

[ ! -z "$1" ] && kill "$1"

done < $MODDIR/hidelist

log_print "Starting MagiskHide daemon"

$BINPATH/magiskhide --daemon
[Magisk] Captain_Throwback:
Can you post your Magisk log from after rebooting?
[Magisk] bigo72:
Here it is:

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

* Linking binaries to /sbin

* Starting MagiskSU

* Preparing modules

* Stage 1: Mount system and vendor mirrors

* Stage 2: Mount dummy skeletons

* Stage 3: Mount module items

* Stage 4: Execute scripts

* Stage 5: Mount mirrored items back to dummy

** Magisk late_start service mode running...

MagiskHide: Moving and re-linking /sbin binaries

MagiskHide: Removing dangerous read-only system props

MagiskHide: resetprop by nkk71 & topjohnwu

Initializing...

Modify data structure: 'ro.debuggable'='0'

Existing property: 'ro.debuggable'='1'

Recheck property: 'ro.debuggable'='0'

Done!

MagiskHide: resetprop by nkk71 & topjohnwu

Initializing...

Modify data structure: 'ro.secure'='1'

Existing property: 'ro.secure'='0'

Recheck property: 'ro.secure'='1'

Done!

MagiskHide: resetprop by nkk71 & topjohnwu

Initializing...

Modify data structure: 'ro.build.type'='user'

Existing property: 'ro.build.type'='userdebug'

Recheck property: 'ro.build.type'='user'

Done!

MagiskHide: resetprop by nkk71 & topjohnwu

Initializing...

Modify data structure: 'ro.build.tags'='release-keys'

Existing property: 'ro.build.tags'='release-keys'

Recheck property: 'ro.build.tags'='release-keys'

Done!

MagiskHide: resetprop by nkk71 & topjohnwu

Initializing...

Modify data structure: 'ro.build.selinux'='1'

Recheck property: 'ro.build.selinux'='1'

Done!

MagiskHide: Killing com.google.android.gms.unstable

MagiskHide: Starting MagiskHide daemon

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

Zygote(0) ns=mnt:[4026542897]

MagiskHide: com.google.android.gms.unstable(PID=5676 ns=mnt:[4026542937])

MagiskHide: Permissive detected, switching to pseudo enforced

MagiskHide: Unmounted (/sbin)

MagiskHide: Unmounted (/magisk)
[Magisk] Didgeridoohan:
You'll need to comment out these lines as well (in green):

[COLOR="red"]#[/COLOR][ ! -z "$BUILDTYPE" -a "$BUILDTYPE" != "user" ] && \
[COLOR="seagreen"]#[/COLOR]log_print "`$BINPATH/resetprop -v -n ro.build.type user`"
[COLOR="Red"]#[/COLOR][ ! -z "$BUILDTAGS" -a "$BUILDTAGS" != "release-keys" ] && \
[COLOR="seagreen"]#[/COLOR]log_print "`$BINPATH/resetprop -v -n ro.build.tags release-keys`"
[COLOR="red"]#[/COLOR][ ! -z "$BUILDSELINUX" -a "$BUILDSELINUX" != "1" ] && \
[COLOR="SeaGreen"]#[/COLOR]log_print "`$BINPATH/resetprop -v -n ro.build.selinux 1`"
[Magisk] Captain_Throwback:
Notice that it's still setting the props in that log? You may have to uninstall. Not sure how to make sure it gets set right, though.
[Magisk] bigo72:
After doing what mentioned by [MENTION=4667597]Didgeridoohan[/MENTION] (thank you)

I can't see any more build stuff

Is this log what you guys want?

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Linking binaries to /sbin
* Starting MagiskSU
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute scripts
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.debuggable'='0'
Existing property: 'ro.debuggable'='1'
Recheck property: 'ro.debuggable'='0'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.secure'='1'
Existing property: 'ro.secure'='0'
Recheck property: 'ro.secure'='1'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026542898]
MagiskHide: com.google.android.gms.unstable(PID=5796 ns=mnt:[4026542926])
MagiskHide: Permissive detected, switching to pseudo enforced
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)

Anyway....still crashing :eek:
[Magisk] Didgeridoohan:
Now the props aren't getting set at least... But I saw in your logcat that it can't load webview at all.

03-30 19:53:01.159 E/WebViewFactory(27626): android.webkit.WebViewFactory$MissingWebViewPackageException: Failed to load WebView provider: No WebView installed

Try reinstalling? https://play.google.com/store/apps/details?id=com.google.android.webview
[Magisk] bigo72:
Do you know what? You're totally right! In developers options there is no WebView! Something messed up everything.

I can't reinstall it because it was a system app and I can uninstall just updates.

Do you know what again? I'm going to clean install the whole rom again, and then follow this steps (Editing that famous file). I need sometime, I will come back as soon as I set back everything.

In the meanwhile a big THANK YOU!

EDIT (after a while) : Clean install .... and BAM! It works! I mean, it works without to make any change to Magisk environment files.

What happened? I have no idea, but I can imagine what maybe made the mess:

The first time I flashed SuperSU first, after the rom and gapps, then installed Magisk Manager and flashed Magisk from the manager. SafetyNet check was OK, but WebView disappeared for some reason. Well, not disappeared, but broken.

All this experimentation was on my little mule, my MotoG2015. Now the big work will be to replicate this successful installation on my daily driver, my Oneplus3T .... but you know the geek law: never flash anything after midnight, if you don't want to spend your night trying to figure out what's wrong with your phricking phone :) Tomorrow, first thing in the morning. I'll let you know how it goes.

Thanks again to everybody lost time with me tonight.
[Magisk] Newmanl:
To update to the new release Magisk 12.0...what shoul I do?....do I need to flash zip from recovery and that's all?
[Magisk] teddy0209:
Yes, but try using the manager first...
[Magisk] jaysonic88:
[MENTION=4470081]topjohnwu[/MENTION] I loved using DualBootPatcher but sacrificed it in favor of Safetynet evasion. Any chance you've looked at DualBootPatcher a bit closer? Fingers crossed.
[Magisk] Team DevDigitel:
updating via the manager from 11.6 to 12 on the LG V20 broke the app. It was like post 11.0 where it causes the systemui to FC constantly, service etc to keep dropping. Im going to update the magisk zip thats baked into the rom and re-test but it def causes issues through the manager.

LG V20 LS997 - Running Stock-ish LG 7.0 ZV5

Ill report back if it works when installed directly via twrp dirty or if it can just be baked into the rom to avoid the issues.

---------- Post added at 09:11 PM ---------- Previous post was at 09:02 PM ----------

i use dualboot patcher "snapshpot" with the LG V20 without issue.

It just needs to be installed into your boot.img ramdisk and then you have to patch the rom you want to install and install it via the app. it has some issues with trying to do backups in twrp but otherwise ive run every rom for my device as a dual or tri boot and its worked fine. A little tiresome to patch each rom but its def fun to play with.

i pass safetynet along side having a dualboot patched boot.img with magisk v11.6 installed.

Use android pay and then dualboot to a magisk aosp rom and play pokemon on that side no issues also.. lol
[Magisk] djlah:
Magisk v11.6 is worked for my selected apps in MagiskHide

today update to v12, MagiskHide no longer work. I revert back to v11.6, back to work again. anything I missed?
[Magisk] Covalex:
Lost root after updating from 11.6 to 12
[Magisk] deani77:
I have this 2 particular apps force close since 11.6 to 12.0

1. Google dialer

2. Google keep

Revert back to 11.1 and the FC gone.
[Magisk] clambert11:
Reboot. It didn't do it automatically for me. Once I rebooted on my 6P everything was fine.
[Magisk] virajkin:
Plz fix 12.0 issues, 11.6 is better
[Magisk] Covalex:
Thanks, this fixed it. No idea why rebooting twice fixed it, though
[Magisk] :
Is anyone else receiving very high CPU usage in Magisk 12.0? It seems that MagiskHide is doing something, and I'm not sure how to logcat it.
[Magisk] pennywaltz:
So I am on the Pixel and running PureNexus... I used this method (https://xdaforums.com/pixel/how-to/magisk-pixel-t3573845) to install Magisk to have root and safetynet.

It seems Tasker can't detect my root, but secure settings can. Anyone have any suggestions on getting Tasker to detect root?

I have tried making it do a root action so it request root access, but nothing pops up. Tasker just say "no root access" and there was no pop up asking me to grant it access.. I have also check Superuser within the Magisk app to make sure I didn't accidentally deny access.
[Magisk] Pkt_Lnt:
known issues easily found with search :good:

https://xdaforums.com/showpost.php?p=71634065&postcount=11171
[Magisk] kopitalk:
I can't unbind magisk busybox in v12. Is it a known issue?

Edit: It could be overlapped with my other busybox provider.
[Magisk] teddy0209:
Can confirm rebooting twice does the trick... One M9
[Magisk] khangcobra:
For me v11.1 is the best :D
[Magisk] oreo27:
I'm on 11.1 myself. Haven't had the courage to flash anything higher. I am getting FC on some apps too but it's either this or MIUI.
[Magisk] jaysonic88:
Thanks! I've tried through TWRP but perhaps adding a second ROM via the app will help.
[Magisk] Elanza_48:
[MENTION=4470081]topjohnwu[/MENTION]

The busybox binding option gets automatically enabled on disabling it or after rebooting the device. Please set it to as it is at default.
[Magisk] DKaine:
Whenever I update Magisk using Magisk Manager, from 11.1 onwards, I completely lose root. I've had to reimage the boot image to stock, reinstall Magisk and system less root, as per the directions, to regain root.

I'm on resurrection remix 5.8.2 (nougat, 7.1.1) with newest system less root SR3 on a Moto X Pure (clark).

I'm trying to figure out if I'm just updating Magisk incorrectly or is there something "broken" in terms of Magisk and configuration of my device?

Thanks!

DKaine
[Magisk] NervReaper:
Samsung A5 2016 - Stock Kernel

Magisk v12 finally pass safetynet :D
[Magisk] Scruffy120:
God bless Magisk! 11.6 (i think) allowed me to have root, magisk AND finally passed safety net! I just updated to 12 and lost root :(

samsung galaxy s6 edge+ (stock) passes the safety net and shows ive got the latest (v12 of magisk) installed....but no root! =\

EDIT: Flashed magisk from TWRP, ive got root back and the latest magisk but not passing safety net :(

EDIT2: Flashed back to 11.6 and everythings passing again, think I'll stay here....
[Magisk] JonathanRAZ:
Note 5 tmo stock kernel dqa2 6.0.1
[Magisk] A_Random_Guy:
Updooted to Magisk V12. Magisk shows unrooted

Samsung J5
[Magisk] dimm0k:
[MENTION=4470081]topjohnwu[/MENTION] updating from 11.6 to 12 on the LG V20 isn't working as planned. after a reboot the device looks to be running except the touch interface is unresponsive then shortly after it will soft boot. tried installing 12 via the Magisk Manager and via TWRP, both resulting in the same thing. flashing back to 11.6 and everything is fine again...
[Magisk] broomer68:
Something is wrong here too.

Installed 12, reboot did not work.

Rebooted manual, no root

Reflashed the zip, Rebooted, rooted ok

Checked safety net: ok

Started TitaniumBackup : No Root!

Rechecked magisk manager: unrooted...

On oneplus3T lineage nightly (weekly 23-3)

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
[Magisk] dbarrett480:
Also having an issue of the system totally crashing and soft booting about 3 minutes after powering on my V20 (H918)... Uninstalled magisk and it fixed the issue so now I've gotta find a 11.6 download somewhere to roll back
[Magisk] Didgeridoohan:
Did you disable Busybox in Magisk Manager settings? If you have it enabled, that is. That's a known issue with certain ROMs.