yashsingh1/xdaforums huggingface dataset:
[Magisk] Pasi200896:
Thank you very much for your help either it didn't solve the problem.

For people who wanna look at the Magisk logs, here's the screen.

View attachment 4057883
[Magisk] jhedfors:
There is this app that may show some more info:

https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
[Magisk] biggdevon:
Is this device specific or can it be used across devices?
[Magisk] jhedfors:
I am pretty sure it is cross-device, but may be Nougat only. Worst case, you can remove the module in TWRP if it causes trouble (using Magisk-mount from release thread).
[Magisk] l3enjamin:
I got my root hidden but cannot pass safety net.

My log get whole lot of this, is there some problem when Magical trying to switch to pseudo enforcing?
[Magisk] kopitalk:
I get module installation error on v11.1, both from repo and memory. Any idea? I'm on LineageOS 14.1 unofficial.

Edit: I solved it by disable hide, restart, enable hide again.
[Magisk] yochananmarqos:
You mean sideload via recovery. You need need a custom recovery like TWRP to sideload anything other than official files from your device manufacturer otherwise the signature check will fail.
[Magisk] darkeyes22:
Do I need unlocked bootloader for that?

---------- Post added at 06:42 AM ---------- Previous post was at 06:27 AM ----------

Flash stock ROM, then you can pass. previously I had an issue with LOS 14.1 not passing SN. Fixed it by flashing stock ROM.

Didn't tested on Android Pay, but without magisk check, it also passed SafetyNet helper 8)

EDIT:LOS could pass basic integrity, like root check, so Pokemon GO was working.
[Magisk] chjun90:
Magisk v11.1

I mounted apps in system but they can't display in the apps list by name. All of them list as their package names, and prompt not yet installed as their icon is a gray sdcard.
[Magisk] mike_aldwin:
Hi, I think there is bug in the magisksu that I'm using. Currently, when doing the safetynet check in the manager, I fail. But when using apps (pokemom go, amdroid pay) that use safetynet, it goes through. Any idea why this is happening?
[Magisk] limestone:
Question on Magisk 11 + Systemless Xposed + Android Pay

Hi all:

I have a question.

I have been reading online that it is possible to use android pay with xposed and magisk together, and this website even mentions that I can simple enable android pay without rebooting, but disabling root in Magisk..

https://www.xda-developers.com/use-android-pay-with-xposed-without-rebooting-with-magisk/

However, I suspect that the article uses an older version of Magisk, because in Magisk 11, the unroot option is not available. can anyone confirm?

So right now the only way to use Android pay is to uncheck Xposed module in Magisk, and reboot.. is there an easier way?

Thanks!!
[Magisk] Didgeridoohan:
Are you saying you've made a module to add apps to system? If so, upload the module so someone can take a look at it. A Magisk log might also be useful.

Have you actually made a successful payment with Android Pay? Pokemon Go doesn't need SafetyNet to fully pass, only basic integrity (use an app like SafetyNet Helper to check).

If you have any version of Xposed (system or systemless) you need to disable it to pass SafetyNet. No easier way.

And yes, that article is ancient...
[Magisk] Artim_96:
I'm trying to replicate that, but for me RootBeer Sample keeps showing an X for dangerous props. What could cause that? I installed your module do the rest is all green. The only thing I could think of would be the SPen Commander which normally only works with SELinux permissive. It's running now everything the settings show enforcing, how it should do because Magisk should hide it. But I can't think of anything they could mean with dangerous props.
[Magisk] Didgeridoohan:
Dangerous props could be ro.secure=0 and ro.debuggable=1. That's what RootBeer check for if you look in their source code on GitHub. Other apps might look for other props...
[Magisk] Artim_96:
Ok, I have ro.secure=0 but not the other one. So I just have to set it to 1?
[Magisk] Didgeridoohan:
Sorry, I probably wasn't very clear... :) It needs to be ro.secure=1 and ro.debuggable=0. RootBeer checks for and trigger if finding them the other way around.
[Magisk] Artim_96:
That's what I meant. But if I don't even have the second one I should only need to change the one that i have. Or would it even go off of it's not there?
[Magisk] Didgeridoohan:
Ah... It's just me being dense then. :)

If you don't get a result running getprop ro.debuggable in terminal you should be fine. RootBeer itself only checks if it's set to 1.
[Magisk] Artim_96:
Strange...I can't find it in the build.prop but the terminal returns 1.

Let's see what a resetprop can do
[Magisk] Didgeridoohan:
Because it's in default.prop, in the boot image. Resetprop can set it just fine.
[Magisk] Artim_96:
Ah, ok

EDIT: so, now at least that is going through without any detections. Still get CTS profile mismatch, but that's probably because of the LOS kernel. But since my ROM dev already stated that he wants to build in Magisk for the next release he might take care of that.
[Magisk] ZjemCiKolege:
Hey only i have problem with root ? is stoping working ? only r estart help?
[Magisk] Telperion:
Honor 8 -- Magisk works on Marshmallow, it doesn't work on Nougat. On N the install just fails and reboots the device. What information do I/we need to provide to figure out why the installation fails on N?
[Magisk] jhedfors:
Do you have ADB enabled? I think I read that that can trigger CTS profile mismatch as well....
[Magisk] Artim_96:
Already ruled that one out
[Magisk] Didgeridoohan:
There's been a few users reporting problems with root intermittently disappearing. No-one has been able to troubleshoot it to any extent though... There's been some users reporting success by force stopping the Manager and starting it again to regain root.

Are you using the Manager to install? If so try flashing in recovery. Either way, a recovery log from the failed installation would be useful.

From what I've seen lately I'm guessing that Lineage can't pass CTS. Have you checked if you pass basic integrity (SafteyNet helper is one app that reports this)?
[Magisk] Artim_96:
It says basic integrity true
[Magisk] Didgeridoohan:
In other words: Magisk Hide is working just fine on your device, but your ROM is not trusted by Google.
[Magisk] Artim_96:
Sadly, yes. Maybe someone somewhen finds out what it is detecting and how to hide it
[Magisk] xxBrun0xx:
Magisk seems to break boot.img on the Moto Z play. Unlocked bootloader, kernel that fixes f2fs bugs installed, still no dice.
[Magisk] Artim_96:
Maybe some logs would help. And maybe a sample of the modified boot.img
[Magisk] Sum1992:
I have also same issues. Flashed this but shows some error in twrp. Using nitrogen os on Titan.
[Magisk] Mar-cel:
How to fully remove Magisk Mods as V4A or Xposed?

Gesendet von meinem SM-G900F mit Tapatalk
[Magisk] Jinded:
Deleted
[Magisk] foxdog66:
Magisk manager doesn't ask for root permission and says root status is not rooted. I'm using phh's systemless root and superuser though. How can I fix this?
[Magisk] Kusoo:
Thanks for sharing that info ?
[Magisk] bouchigo:
That's actually misinformation. I'm running the official Nougat release (from OTA) on my Nexus 6P, and I'm rooted with this method...working fine with no issues. The user that had issues must have done something wrong.

Ignore the baseband version, I'm using an older modem that locks onto Band 4 only because Band 12 sucks at my workplace:
[Magisk] kartikb:
Last night when I flashed Magisk, it didn't boot. Tried it again today, working fine now.

Sorry for that.

---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------

It's working, flashed it again today.
[Magisk] Fedroid:
I have a Huawei P8 Lite.

I have installed successfully Magisk and phh superuser zip and app.

Apps get root access like a charm and all seems to go fine until I try to toggle off superuser. Nothing happens, switcher comes back to its original state and root is always enabled.

Maybe is Magisk manager or Magisk indeed incompatible with my phone?

Or maybe I did something wrong?

Thanks in advance
[Magisk] bmg1001:
Can you use Viper4Android without root on the Magisk version? I'd like to reliably use AP but have Viper work at the same time. Thanks!
[Magisk] duminduweera:
Yeap I can confirm this as well, its working fine with the official Nougat.

Could you tell me how you locked your radio to band 4, I have the same exact issue where I live?
[Magisk] bobbarker2:
Has anyone gotten the v4a magisk package/apk to work? I've tried several different install orders and the drivers are never processing.
[Magisk] bouchigo:
I'm using an older radio from one of the earlier factory image releases. It's version 2.15.

EDIT: I got it from this factory image (in case you can't find it anywhere else): MDB08L
[Magisk] wmarcin:
Sorry if already mentioned, but now it passes safety net check on my N6 running MM PureNexus ROM. Before, the unroot toggle wouldn't stick. I'll test an actual transaction soon and report back.
[Magisk] gohamstergo:
Report android pay stuff here: http://xdaforums.com/android/software/magisk-phh-s-superuser-android-pay-t3435921
[Magisk] MrBrady:
I'm using Viper A.R.I.S.E. Numbers release and it works great with Magisk on Android N as long as you set it to permissive.
[Magisk] TheSt33v:
So I'm confused. The OP says that Magisk supports android as low as 5.0, but it also says that it doesn't support anything that isn't supported by official systemless supersu. Last I checked, official supersu only supported 6.0 and 5.1 on Samsung devices. Which of these two statements is correct?
[Magisk] grep_i:
Both statements are correct
[Magisk] TheSt33v:
Then I suppose systemless supersu was updated at some point to support 5.0, which is strange because I can't find any mention of that in its changelog. I know it certainly doesn't install systemlessly on my non samsung 5.1 device.
[Magisk] CrazyCypher:
Hy guy, I would like to swap SystemUI.apk with the modified one, how can I do that with Magisk that I will not actually modify the system partition? Thanks for the answers :)
[Magisk] KaMyKaSii:
Who works with Android 5.0 onwards is Magisk. SuperSU does not support Android 5.0. The version of SuperSU here is a unofficial modified to work with Magisk . If you want root in 5.0 use PHH's SuperUser

---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------

http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382/post68326221
[Magisk] Zer0t3ch:
Working on Nougat (possibly with Android Pay)

For anyone wondering, I was able to pass SafetyNet checks with Majisk & SuperSU (SU temporarily disabled) on a Nexus 6P (Angler) with Nougat (build NRD90M) but I don't have a card to test AP at the moment.

Also, this is without Xposed.
[Magisk] Didgeridoohan:
"Some error" is very unhelpful in terms of troubleshooting... A recovery log from the failed flash is much more useful.
[Magisk] Telperion:
Neither worked, log attached. Phone gets a few lines into zip install then reboots itself, so I had to pull this from /cache/recovery.
[Magisk] Didgeridoohan:
Sorry, no idea then... That log is not from the failed flash and unfortunately useless in this case.

Edit: Have you tried downloading the zip again in case it's a corrupt download?
[Magisk] Sum1992:
See this.
[Magisk] Didgeridoohan:
Looks like your Magisk image is corrupt. Either run fsck through ADB in recovery or uninstall and reinstall Magisk.
[Magisk] Sum1992:
Now it shows this [MENTION=5125527]Artim_96[/MENTION]
[Magisk] Artim_96:
Something is corrupted. The zip can't be it, I used it myself.

For dangerous props I Asus asked for that, the two props are listed a few pages back. For busybox I'm surprised, I thought Magisk would hide it too. Or does your ROM have it included?
[Magisk] Telperion:
Yes, I tried that and also the beta 12 builds and same reboot issue. It could be an issue with the Honor 8 TWRP, hard to say.
[Magisk] Artim_96:
Strange. The test keys one should be fixed by the module, the dangerous props with the to posted a few lines ago. Try the attached one, I added them there
[Magisk] Sum1992:
Now with only one warning.
[Magisk] Didgeridoohan:
Run (without quotes) "getprop ro.build.tags" in a terminal emulator. What's your result?

Also check with this app:

https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker

If you scroll down it should say "release-keys" next to TAGS.
[Magisk] Artim_96:
Then probably either your build.prop or default.prop still shows it somewhere.

Best a be to copy them to your internal storage (best in TWRP, there you can force it to mount system read only) and search for all lines containing "test-key s" and add them to the post-fs-data.sh with test-keys changed to release-keys
[Magisk] Didgeridoohan:
Yup... I figured as much. I had the same issue when using system.prop rather than setting the props with resetprop in post-fs-data.sh. This shouldn't be a problem with the module [MENTION=5125527]Artim_96[/MENTION] made though. It is based on an old template, but that shouldn't matter either... Could you upload your Magisk log?
[Magisk] Sum1992:
Here it is.
[Magisk] Didgeridoohan:
Looks fine... Sorry. I'm too close to my bed time to think of anything else. Maybe try making a new module from the latest template, but that's a long-shot... Good luck.

Edit: You could try removing the -n option from resetprop in the module... Don't know if it'd make a difference.
[Magisk] Sum1992:
Ok thanks.
[Magisk] Telperion:
Update: Rolled back to MM, flashed official TWRP, and was able to flash Magisk zip with no issue. Verified working, and passes safety net check. I think it's likely a problem with the Honor 8's build of TWRP, it's still a WIP.

Tried that, but it still fails. I tried the unofficial build zips of v12 also to be thorough and that fails as welll.

I'm rolling back to MM tonight since it's evidently working there, I'll flash it and then run some analysis to see what's different on Huawei's MM stock ROM/kernel. From there I might be able to provide actionable information to facilitate us getting it working on N.
[Magisk] markjoseph4:
Sir,

Magisk stops work after update v10.2 to 11.1. It lost Root Access after update. I tried to re-root by flashing PhhSuperUser.zip. It shows rooted again but Modules does'nt work at all.

I'm on ViperRom M9 v6.0.0.

Plz help..!
[Magisk] afuller42:
Phhsuper user is no longer needed in 11.1 it has built in magisksu. Reflash Magisk maybe after deleting phhsuperuser
[Magisk] jhedfors:
I just came across this in another thread, and thought you might want to try it....

It involves changing permissions on a couple of SELINUX files.

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828/
[Magisk] staygreen420:
i have a stock s6e international version, and want to root and play pokemon go, im a little lost with a step, in the tutorial it sais trasfer files to sdcard then flash with twrp but s6e doesnt have an sd card. can i copy the magisk 11.1zip after i do the wipe? or do i have to wipe before flash?
[Magisk] jhedfors:
Works the same with the internal SD card. As long as you don't wipe "internal storage" your files will be accessible from TWRP.
[Magisk] Artim_96:
Thank you very much. I'll try that soon and report back as soon as I have results
[Magisk] DarkLanternX:
Put the files in your internal storage then but not inside any folder, you only need to wipe if you flashing a custom rom. If you rooting for the first time or if u wanna stay on your stock rom , just flash magisk, no need of formatting, or cleaning cache or dalvik cache.

Hit that thanks button if this helped ya :)
[Magisk] Artim_96:
Sorry, but it does not work for me. Maybe it's really for MM only, I'm running N.

I'll try it with a module that sets them with post-fs-data, maybe it now needs to be applied on bootup, but maybe someone can report how the permissions should be set on stock Android.

EDIT: it's not working for Android 7. I made a module, maybe someone with an Android 6 Custom ROM can test if it at least works there or if Google already patched that.
[Magisk] danny_bhoy67:
Is it likely that there will ever be a way that we'll be able to use Magisk to pass safety net with xposed installed and active?
[Magisk] Artim_96:
No, not really. It's said that using Root Switch can do that, but I don't know if it still works and on which Android versions/patch level
[Magisk] Phantoml337:
Tried it and no dice, Magisk asks me to flash SuperSU before flashing for some reason...
[Magisk] akk29:
Strange. Did you extract the boot image from the ROM zip? Flash the ROM then flash UPDATE-unSU-signed.zip then flash the boot.img.
[Magisk] aredpanda:
I'm having errogs on some apps that request SU access., namely AdAway and Boeffla Config.

Both have been configured in Magisk Manager to grant access, and show access granted when I check Magisk Manager's logs. However, the apps themselves are refusing to work stating that SU access has been denied.

Any tips?
[Magisk] jhedfors:
Not sure of this is what you are experiencing, but I find that superuser access in settings gets changed to "disabled" from time to time. Re-enabling it fixes it in that case.
[Magisk] aredpanda:
Thanks for the tip but I've trippled checked my Superuser screen and both apps are enabled for SU access. I have another app there(CM's Terminal) which works just as intended when I do `su` in the shell.

EDIT: Took me a while to figure out what were really suggesting. Checked the apps settings and 'Superuser' was indeed disabled. I feel dumb now. Thanks a lot!
[Magisk] jhedfors:
I was actually talking about the switch in Settings, not Superuser tab. But if you have other root apps working, then I am not sure...
[Magisk] fndpena:
I have a nexus 6p, running stock 7.1 + franco's kernel and official supersu systemless root.

Can I install Magisk using the manager app without any trouble? I'm not sure about the custom kernel, can I install over it?
[Magisk] aredpanda:
Please check the edit to my previous post, thanks again! What's bugging me now is while I had superuser access disabled, my terminal app was still able to escalate privileges. :confused:

[MENTION=4946779]fndpena[/MENTION]: Installing magisk shouldnt mess with your kernel in any way. Go for it, just backup first and you can always revert :)
[Magisk] Didgeridoohan:
I didn't have any problems with AdAway and Magisk v11.1 and MagiskSU when I used it. I also just tried downloading and installing Boeffla Config to see if it would work and it does. It did complain at the first startup after granting access the first time, but after closing it and starting it again it seems to work without problems.

You might have some issue with your setup...

Disregard, I was way to slow... :D
[Magisk] jhedfors:
Awesome! :good:
[Magisk] fndpena:
This is probably a common issue for magisk + supersu users, but if someone could give me a quick tip I would really appreciate...

On the SafetyNet check I get "CTS profile mismatch".

How can I fix that?
[Magisk] jhedfors:
Check this thread...

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828/
[Magisk] Didgeridoohan:
It's extremely common if you use SuperSU with Magisk. Happens 100% of the time... :D Sorry, couldn't resist.

You have to use MagiskSU if you want to pass SafetyNet with Magisk Hide.

Tips found here:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] aredpanda:
Start by enabling Magisk Hide and configure it for the applications you want passing safetynet.

Magisk Hide doesn't support SuperSU. I highly suggest MasgiskSU unless theres a specific feature of SuperSU you require.

To hide SuperSU from SN you'll need to install suhide alongside SuperSU. You can find it on the SuperSU forums. Some reports from the pogo community suggest suhide 0.54 has better results for a broader range of devices than suhide 0.55 so you can try both as I don't use SuperSU to be able to provide a more accurate suggestion.
[Magisk] DuMKaSD:
It's there a way to remove a module from magisk without root? Installed a module that sent me into boot loop, dirty flashed the ROM and boots fine, but once I root with magisk boot loop starts again
[Magisk] teddy0209:
Search for magisk mount, it's in the old compilation of magisk modules... Just flash it via twrp and you'll be able to see the magisk folder in the twrp file manager, there you can delete existing modules.
[Magisk] jhedfors:
This.

[MENTION=4470081]topjohnwu[/MENTION] - Could this be added to the release thread's download section? It should be downloaded, just in case ( just like the uninstaller) at the beginning.
[Magisk] Artim_96:
Go to recovery, mount the Magisk.img (easiest with the magisk-mount.zip) and delete the apps folder
[Magisk] fndpena:
Yeah, I noticed that. I can bypass root verification for some apps, such as snapchat, but not for pokemon go because of safetynet. I'll install MagiskSu then...

Being rooted, is there any way I can install MagiskSU over SuperSU without messing with custom recovery? Maybe flashing a zip on FlashFire... I don't know, I've been a long time supersu user...

EDIT: I guess I can do a "full unroot" using supersu app and then flash magisk zip with flashfire, right?

But if I do that, I guess I won't be able to use flashfire since I'll be unrooted...

Or I can just flash magisk zip over supersu, using flashfire...
[Magisk] Didgeridoohan:
If you flash Magisk with systemless SuperSU installed it won't install MagiskSU. You need to fully remove SuperSU before flashing Magisk.
[Magisk] jhedfors:
With FlashFire, could you cue up osmOsis's unsu zip, followed by Magisk zip?

UPDATE: I suspect this may not work for you as I just tested it and it failed. I think you will need to install a custom recovery (TWRP).
[Magisk] requiiiem:
Use recommended gapps?
[Magisk] DuMKaSD:
Thanks, worked like a charm!
[Magisk] Peter.1997:
Hi, I am rerolling my previous post here.

I want Magisk Hide to work on CM12.1 with Android LP

It works perfectly on CM13 on Marshmallow, but I dont like Android 6.0

What I have done to get it working on CM13: Flash ROM, Gapps, unroot, Magisk

The same procedure on CM12.1 doesn't pass SafetyNet status with Magisk Hide...

any ideas?
[Magisk] fndpena:
It's done. I did a full unroot in supersu and booted on TWRP to install magisk, keeping the stock recovery untouched. Worked just fine.
[Magisk] biggdevon:
Your statement is confusing to me. If your using TWRP how is your stock recovery untouched?
[Magisk] jhedfors:
Good to hear you got it working! :svetius:

You can load a recovery in fastboot connected to PC, and not install it. Never done it that way myself though.
[Magisk] staygreen420:
thanks guys :)
[Magisk] Didgeridoohan:
Start by testing if Magisk Hide is working at all. Use a root checker and see if you can hide root from it. If that works, Hide is working. You can also check if you're passing basic integrity or not with an app like SafetyNet Helper.

And there's a whole bunch of other things you can try, some of which I've collected here:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828