yashsingh1/xdaforums huggingface dataset:
[Magisk] Link_of_Hyrule:
For anyone trying to use Android Pay on the OnePlus One I was able to get a working Magisk Module made you can find it HERE.
[Magisk] Wesley_NL:
yeah i made that screenshot while audio is playing, to check if it kicks in but it dont
[Magisk] Didgeridoohan:
Have you tried changing compatibility mode in settings to compatible? You can't open that status window to check, but you can hear it working.
[Magisk] Wesley_NL:
seems /system/etc/ is read only, it cause viper not to work on n-lite v2 nougat rom on my device, please fix that

---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------

explain more please, tell me how
[Magisk] Didgeridoohan:
Uhm... Not much to explain. In the settings of the V4A app, change the setting as I described. When you toggle settings on and off after that you'll hear if it's working or not.
[Magisk] Wesley_NL:
ahh i see, nope no change in that either
[Magisk] Didgeridoohan:
https://xdaforums.com/showpost.php?p=70931980&postcount=8647

https://xdaforums.com/showpost.php?p=70426733&postcount=7120
[Magisk] chronictheone:
Hi, I am trying to get SafetyNet passing but it says "SafetyNet Failed: CTS profile mismatch".

Trying to find a solution, people are saying there is an option for Superuser on the settings or on the hamburger, but I promise there isn't.

I can't post a screenshot because I have less than 10 messages, but my options are:

Dark Theme, Clear Repo Cache, Disable Magisk, Enable BusyBox, Magisk Hide, Systemless hosts, Enable advanced debug logging, Enable shell command debug logging.

I am using Magisk Manager 4.1, Magisk v11.1, Nexus 6p 7.1.1, Security patch level 05/01/2017. Thank you for your help.
[Magisk] Didgeridoohan:
About passing SafetyNet:

https://xdaforums.com/showpost.php?p=70426733&postcount=7120

About superuser: What does the status page say about root? Could you provide a Magisk log (if you can't get it from the Manager it's available in /cache and can be reached in TWRP). A recovery log from the installation could also be useful.
[Magisk] de.er:
It's not in the Settings, it's in the hamburger menu
[Magisk] janis_dschi:
Does someone know if multirom works? I searched for a while and found nothing except in OP (Proof Video). Magisk v11.1 is installed. Im on cm13 ressurrection remix port for nubia z11 nx531j.

Thanks in advance :)
[Magisk] chronictheone:
Mine only shows

Status, Install // Modules, DOwnloads, Magisk Hide, Log // Settings, About
[Magisk] hsiehboss:
I use different set combination (do not change mgiskhide)and reboot test Until the SafetyNet pass.

Then enable busybox it still pass.

My English is not good, so use google translation. Hope you can understand.

[emoji1]

我從使用 Tapatalk 的 Nexus 6P 發送
[Magisk] chronictheone:
Status page is green, green, red: Installed Magisk v11.1, Latest version of Magisk installed // Properly rooted, 2.79: SUPERSU // SafetyNet Failed: CTS profile mismatch

Cannot share since I cannot have external links yet (need 10 messages). Can you ask something specific and I can look into it?

---------- Post added at 12:08 PM ---------- Previous post was at 12:03 PM ----------

I have tried that combination and unfortunately it doesn't work. Thank you anyway.
[Magisk] de.er:
Properly rooted, 2.79: SUPERSU means you probably didn't fully unroot properly before installing magisk, it should say Properly rooted6:MAGISKSU
[Magisk] Didgeridoohan:
And there's your answer. You're using SuperSU and Magisk Manager doesn't manage that root solution. You need the SuperSU app for that. Magisk Manager manages built-in MagiskSU.

That's also why you can't pass SafetyNet.

Edit: I posted a link for you. Read that...
[Magisk] biggdevon:
If all this does is replace files can it work on other devices or are the files device specific? Noticed a note 3 user reporting success with it.
[Magisk] chronictheone:
Ok I will try. I have already unrooted and installed the zip file for magisk but it gives me an error. I might have to format everything and start again. Thank you for your help.
[Magisk] Didgeridoohan:
If you provide a recovery log from the installation we can probably help...
[Magisk] chronictheone:
WIP Enabled
Installing zip file 'sdcard/Download/Magisk-v11.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
*********************************
Magisk v11.1 Boot Image Patcher
*********************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/mmcblk0p34
- Unpacking boot image
- SuperSU patched boot detected!
- Adding auto patch script for SuperSU
! SU image mount failed...
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
[COLOR="Red"]Updater process ended with ERROR: 1
Error installing zip file 'sdcard/Download/Magisk-v11.1.zip'[/COLOR]
Updating partition details...
...done

It sounds like it wants me to isntall SuperSU, but the problem in the first place was SuperSU being installed? I don't get it :confused:
[Magisk] Captain_Throwback:
Thanks for the log. Your zygote detection isn't working, so you should post that as a github issue with the log (or see if there's a relevant existing issue and post it there).
[Magisk] :
0644 perms are automatically set for new files so no they don't need changing.
[Magisk] Rohaq:
Just a few suggestions for Magisk Manager:

Could we get the option to have a persistent notification to display Root/Selinux status? It'd be pretty useful to check the status at a glance.

Application activities to toggle Root and Selinux separately would be awesome too, as it would allow it to be toggled via a launcher shortcut or Tasker.

Alternatively, a widget that displays Root/Selinux status and toggles them on a tap would also work pretty well.
[Magisk] benwalburn:
[MENTION=6320543]RatchetPanda[/MENTION] I tried flashing your zip on Magisk v6 and it had no effect on my Nexus 6P or OnePlus 3. I dug through your script and applied the relevant parts to the one from the new template and was able to successfully flash it on both devices. I'm not sure what you changed vs my original one (the permission set line in your's still shows as commented out) but my new one seems to work, unlike my original or your fix. I assume yours worked for you, so I'm not sure what's up with that.

Whatever happened, here's a working Nexus Launcher for Magisk :)
[Magisk] dimm0k:
I for one say nay on the persistent notification unless there's a way to turn it off... Tasker toggles would be nice
[Magisk] sansnil:
Agreed. All UX options like this should be that, options. :good:
[Magisk] Rohaq:
Yep, that's why I said "the option" - I just want to be able to quickly check the status in order to avoid having to set up Android Pay all over again because I forgot to disable root before making a payment :)
[Magisk] fjdifede:
Just dirty flash Phh Super User! No need of all the above.!
[Magisk] LLStarks:
I'm a little confused. How did my Magisk ramdisk survive a CM nightly flash? Do I need to extract the boot.img and flash that to start fresh?
[Magisk] zzzhead:
Could any kind soul shed some light on this? Or perhaps it is related to the rom itself ????
[Magisk] Small_Ku:
It not working for me and I cant use flashfire to update my Magisk to v6
[Magisk] smohanv:
Don't know how to use module template. Can anyone please throw a clue on this.

Do we have magisk module somewhere like we have xposed modules......

Thanks.

PS: My understanding is that this module is to merge app installed in to data partition to system partition.
[Magisk] gkillerx:
When instaling phh's SuperUser 17 (Magisk Version) (2016.8.20) I don't have root (titanium backup says: The attempt was made using: "/system/xbin/su". and the phh's superuser app says the binarys are out of date.)

same issue: http://xdaforums.com/showpost.php?p=68288750&postcount=821

I followed this guide: http://xdaforums.com/showpost.php?p=68297880&postcount=855 (thanks [MENTION=6851719]ShankkOG[/MENTION]!)

Device: Oneplus 3

Android: 6.0.1 (OxygenOS 3.2.2)

Magisk Version: v6
[Magisk] smohanv:
This is what the OP posting says,

Systemless ViPER4Android

This is a Magisk port for the popular ViPER4Android sound mod!

Official thread to ViPER4Android: Official ViPER4Android Audio Effects (FX v2.4.0.1)

You have to install ViPER4Android APK after flashing!

Also, do not allow the app to install drivers automatically, as it will install files to your system. If it still complains ViPER4Android is not installed after flashing the zip, please contact me. It means there are some bugs.

Download Link:

Official ViPER4Android v2.4.0.1 APK

ViPER4Android v2.4.0.1 (Magisk Version)

Sorry for being dumb. Flashing magisk version of ViPER installs apk (ViPER app) as well. Don't understand why would i install apk again if magisk flash version has apk built in. Confused...
[Magisk] stangri:
[MENTION=4470081]topjohnwu[/MENTION] -- I believe the first post had some information about Nougat incompatibility, but I've read it again just now and can't find it. Has anyone successfully flashed this on Nougat DP5? The word around town is that Nougat will be released today (well, at worst the week of 22nd), so I'd like to jump ship from SuperSu after official release.
[Magisk] mhaha:
Device Model: Sony Xperia Z5 Compact (E5823)

Android Version: 6.0.1

Stock ROM with unlocked bootloader and patched kernel for rooting on Z5 series

Patched: dm-verity left enabled since Magisk patch would disable it, Sony-RIC disabled

Magisk v6 + phh SuperUser V17 (Magisk version)

Magisk v6 + SuperSU v2.76 (Magisk version)

Problem: I seem to have partially working root. I first used SuperSU, and was able to install systemless xposed and a couple of xposed modules. I was also able to install Adaway and get root privileges.

But I later found that I couldn't get root permissions with the app Total Commander, a file explorer, and an xposed module, NeoPowerMenu. When I open either app, I get a notification that tells me I need to update binaries, but update always fails.

I downloaded a couple of root checkers off the Play store, and all reported that I did not have root.

I thought maybe it was because I used SuperSU instead of the recommended phh's SuperUser, so I reflashed Stock ROM (clean wipe), installed Magisk with phh's SuperUser and tried again. Unfortunately, I encountered the exact same symptoms as before. I get a notification telling me the binaries are outdated.

It seems a couple of people also reported problems with binaries. Any suggestions?
[Magisk] mastarifla:
Any luck with the Moto X 2014 boot issue?

Should I first try flashing the boot image from /u/Junior Passos then try flashing Magisk over that?
[Magisk] smohanv:
I did this and it worked for me.

http://xdaforums.com/showpost.php?p=68295796&postcount=851
[Magisk] topjohnwu:
How did you root your device previously? Can you flash SuperSU directly, or you have to manually flash Junior Passos's boot image prior to flashing?

If it is the latter case, then someone have to make a boot image for you, as Moto do not support auto patching or it is not using the standard boot format. I do not have the device, and I don't know anything about Moto's boot image, so I cannot help.
[Magisk] stratonz:
I can't use selinux toggle, it switch back to permissive by itself. Some suggests?

Inviato dal mio GT-I9305 utilizzando Tapatalk
[Magisk] crusader727:
restore stock boot.img from your rom or dirty flash your rom
[Magisk] Didgeridoohan:
If you look in the detailed log you'll probably see that the script is looking for a backup of the stock boot image, to extract the ramdisk, and failing.

I'm gonna guess you're using a pre-rooted ROM. That means your boot image comes patched for SuperSU out of the box. You'll need to flash a clean boot image, which can be tricky with a custom ROM. Or find a custom kernel with its own ramdisk. Ask in your ROM thread for advice.
[Magisk] jhedfors:
Look at the latest comments in the release thread.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page2
[Magisk] Hgneto:
I might be doing a noob question so apologies if it is: Is using magidisk a way of having root on my S7 Edge Exynos version without triggering/tripping KNOX?
[Magisk] :
Facing a weird bug whenever i enable systemless busybox in setting menu and reboot I am unable to get access to my contact manager & phone app means when i tap the contact manager or phone app it doesn't starts but when I toggle off the systemless busybox & reboot it goes all fine again and i can use the apps [MENTION=1162986]Captain_Throwback[/MENTION] sir plz look at the logs i attached and help if possible

I am on magisk v11.1 and magisk manager 4.1
[Magisk] chronictheone:
No I never installed any custom ROM, I simply unlocked the bootloader and installed TWRP and SuperSU. Then removed SuperSU and tried installing Magisk, to no avail. So this is the original Google ROM at the moment. I think I should have backed up my original ROM but I'm (obviously) new to this and skipped that bit... :( What should I do now?
[Magisk] reis1996:
I'm sorry for being a noob. How exactly do I do that
[Magisk] crusader727:
Go to your device forum and search for stock boot.img / kernel, flash it in TWRP
[Magisk] Didgeridoohan:
That makes it much easier. As [MENTION=5716029]crusader727[/MENTION] says, you need to flash your stock boot image. Extract the boot.img from the factory image/ROM and flash it in fastboot or TWRP. After that you should be able to flash Magisk without a problem.

Edit: could also be a good idea to flash this script before installing Magisk: http://xdaforums.com/showpost.php?p=63615067

That way you'll be sure not to have any remnants of SuperSU.
[Magisk] Paolo83:
HELP with 11.1 tasker does not find root!! why????
[Magisk] crusader727:
SEARCH!!
[Magisk] treezy26:
So I just want to put in my input on this since I was having issues at first. I've been keeping up with Magisk for awhile now but never attempted it because of other factors. Anyways, I gave in and tried the latest 11.1 and immediately got a boot loop. So I was like yea guess its a no go for me. Oh and I'm on 1/21 PN using the 6P with SuperSU latest. But I had to figure out why it wasn't working, I tend to get that way when it comes to roms and such. So I noticed people saying Viper4A was a main factor in why it doesn't work, or so I've read. Then I noticed I needed to get rid of root and flash 11.1 again. So I did and nothing. Then I realized something, I didn't restore stock image when SU asked me to and VOILA...it works. Thanks Magisk! Now I can use Android Pay, which I've honestly never used lol.

Oh and I didn't clean flash my rom either in case your wondering...
[Magisk] Didgeridoohan:
Nice work. That's one of the beauties with Magisk. You very rarely have to do a full wipe. If there's issues it's usually enough with flashing stock boot image.
[Magisk] treezy26:
Yea it seems harder than it is on paper. But a little patience and reading, a whole lot of reading, and I'm good to go. Plus, I'm still using Viper so I'm definitely good to go. Just thought I'd share my experience in case someone here has the same issue as me.
[Magisk] Paolo83:
if I had found an answer I would not ask!!!!!

I don’t know why tasker does not find root. For example to turn on/off airplane mode
[Magisk] chronictheone:
Ok all done (what a pain). I think we are getting there. Now I can see the superuser option on the left but it says "no apps found" when I click it.

The status is now 'Properly rooted // 6.MAGISKSU (topjohnwu).

But the SafetyNet still fails. Any ideas?

---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------

EDIT: SafetyNet Passed! SUCCESS Thank you for your help mate!
[Magisk] peekiephish:
I'm a first time user of Magisk Manager and I have it installed on a Custom Rom (SuperMan v2.1 on 930-F). When I first installed ROM I was able to get into Manager and set settings. It seems that root is properly working. Now when I go into the app it force closes everytime. Is this a known issue? I searched this thread for a solution but wasn't able to find anything. Thank you for your help.
[Magisk] GryphonBR:
Hey mate, so which Xposed version did you use? I'm currently trying MIUI-Magisk by SolarWarez, but it seems to break Magisk functionality and, to make matters worse, to also cause the same SystemUI crash we were discussing before.
[Magisk] bkayy:
Anyone having issue getting arise driver to install using magisk 11

.1 tried renaming audio.conf but still doesn't work any ideas
[Magisk] Filip013:
Yeah, Xposed is tricky. I use MIUI system arm64 Xposed by SolarWarez. (it breaks OTA, but what can you do) You can either have Xposed or SafetyNet at one time. Use Rootswitch to turn Xposed on or off.

As for the SystemUI problems, I was lucky not to have them. I decided to post ADB logs if it happened to me again. What I planned to do was flash Magisk uninstaller, boot MIUI, enable USB debugging, connect phone to PC, use adb to get logs (you need adb client on PC, use the command "adb logcat > logcat.txt"). (This last thing is just to test adb). Then flash Magisk again, let the phone boot (or whatever that state is) and then run the command again.

If you happen to get problems with SystemUI, could you share your log? I'm sure it will help [MENTION=4470081]topjohnwu[/MENTION] fix this.
[Magisk] android_htc:
I am also only able to pass SafetyNet with the above commands enabled in init.d for my Permissive Kernel!
[Magisk] Didgeridoohan:
Could you share your Magisk log, please?
[Magisk] rolandyip:
I facing the similar problem like you but when i enable Magisk hide i can get phone app work properly .
[Magisk] android_htc:
Please see attached log.
[Magisk] rolandyip:
Is this correct Magsik Log i uploaded?
[Magisk] jhedfors:
May sound silly, but did you enable superuser access in Magisk settings? This tripped me up for a short while.
[Magisk] Didgeridoohan:
Why have you put the SIM Tool Kit on the Hide list? This is pure speculation on my part, but that could be the source to your problem...

---------- Post added at 19:17 ---------- Previous post was at 19:11 ----------

That's interesting. Hide does detect your permissive SELinux and activates pseudo-enforce.

Without the scripts in init.d, what do you get if you type getenforce in a Terminal Emulator?
[Magisk] quorn23:
Probably gonna get lost in here, but thanks for the update Dev. :highfive:

Magisk 11.1 works perfectly on my N6P with 6.0.1 (Xposed user). Root management works as supposed and if I need it SN passes fine. :svetius:
[Magisk] clintonbugz:
+1
[Magisk] android_htc:
I get Permissive with and without the script. But, without script SafetyNet fails, see attached screenshot. Copying and activating script again in Kernel audiutor passes safetynet
[Magisk] Didgeridoohan:
If you had searched this thread I'm sure you could have worked out that Tasker can't get root with the current MagiskSU.

https://xdaforums.com/search/thread/3432382?query=tasker
[Magisk] Wesley_NL:
Same here as i showed with logs
[Magisk] Didgeridoohan:
That's interesting. You should probably open an issue on GitHub with all this information and a copy of your boot image as well. Seems like Magisk Hide can't hide permissive SELinux on your device.

Does Magisk Hide work otherwise? Can you hide root from say, a root checker, as an example.

---------- Post added at 19:44 ---------- Previous post was at 19:43 ----------

You could probably also pitch in on that GitHub issue...
[Magisk] RandomPooka:
I've got Tasker enabled in the superuser settings page of Magisk Manager, because I forced it to run a command that calls the absolute path of the su binary. But, as a rule, the app cannot see the binary. It's possible that tasker just needs to have it's search path for that binary updated. I'd consider adding the magisk superuser directory to the PATH variable, but I haven't even checked to see if that's already in it or not. I'll give it a look and see what I can find out about WHERE tasker is looking for the binary, and whether it's already in the path.

-- Update --

I was able to find out the the $PATH variable does include /sbin. It's actually the first thing in it. I also learned that my tasker commands don't need to call /sbin/su directly. It's enough to just call su without the absolute path.

While trying to get Tasker to enable the "Use Root" checkbox, i got nothing on a logcat at all. Zero. No activity from Tasker or su, or even anything else beyond the display manager showing the toast notification that my device does not appear to be rooted.

I think this may need to be addressed by the app developers for Tasker. Perhaps they've still got root hardcoded to certain paths. I don't know/remember how to rip apart an APK to see if that's true or not.
[Magisk] Wesley_NL:
On 6.0.1 mm

That is what what my problem is to , i need to run kernel aduitor with init.d script in order to pass safetynet , it doesnt bug me that much but the feeling to not get it work automaticly but to have to use a work arround to get it to work

On 7.0 i havnt been able to use these commands since aomehow the system is read only , root do work, root hide work to , i can play pokemon go, but i am unable to touch certain files , for example

1. the audio conf for viper4android,

2. /Media/ui/ cant remove them, i like silentness instead bleep when i plug charger or volume controll

3. Enforce and policy cant change permission in order to pass safetynet,

So my conclusion is magisk dont completly root,

---------- Post added at 07:54 PM ---------- Previous post was at 07:51 PM ----------

I dont know where and how thats why i trow itin the forum here
[Magisk] Didgeridoohan:
That MagiskSU sometimes can't mount /system rw is a known issue. Check currently known issues in the release thread.
[Magisk] Link_of_Hyrule:
It should work with any device that has the same NFC chip on Lineage OS14.1 or equivalent.
[Magisk] android_htc:
Sure will do when time permits. I have a Samsung Note 4 and you advised to do the same with my Samsung stock kernel which at least highlighted the issue.

Magisk hide has been working for Android pay and Barclaycard.

On a separate note, I could not pay on the bus with Android pay just now after the above changes (safetynet was green!)... I guess I should have restarted the phone as it was working all day with the pemissive kernel and script!
[Magisk] Wesley_NL:
I see well aslong as i can hide root then its fine i guess, problem is if i move over to nougat i like to have viper working but no luck on that , i tried difrent methods including magisk viper, as i reported it seems ro be active but it wont kick in, and i disabked all other audio live , its just i cant touch the conf file and thats probaly the cause of viper not to work
[Magisk] biggdevon:
You using the stock kernel still? I have all green as well but pay doesn't work. Running stock 6.0.1 with arter97's kernel.
[Magisk] Didgeridoohan:
That's right, you have a Samsung. I keep being fooled by your name... :D

Then it probably has to do with the fact Magisk Hide doesn't play well with Samsung kernels. That you can get it to pass with those scripts is interesting though.
[Magisk] skyrocketeer:
I was running 10.2 before, and since i got the update to 11.0, I installed that however that broke MagiskHide and my phone kept failing safetyNet. SO then I reverted back to 10.2 by completely uninstalling Magisk and then flashing the 10.2 version and phh superuser zip again.

I did hear that 11.1 fixed the MagiskHide issue but I haven't tried it yet.
[Magisk] Filip013:
My device is weird. (Xiaomi Redmi Note 3 Pro running stock MIUI)
[Magisk] android_htc:
Magisk 11.1 does not install on my Samsung stock kernel (tried both in recovery and within 10.2 magisk manager)...I guess we will need to report this issue on GitHub as well.

I am using a Note 4 snapdragon custom kernel from one developer who has made both enforcing and permissive version... both work with a workaround for permissive!

You have a Note 5, so can't really compare apart from the common issue with Samsung stock kernels.