yashsingh1/xdaforums huggingface dataset:
[Magisk] android_htc:
Can you confirm if you had v10.2 working on your Note 5?

I tried stock kernel on my note 4 on v11.1 but magisk was was not installed just like you.

No issues with my custom kernel...I can pass SafetyNet and Android pay is now also working on v11.1 :)
[Magisk] Kyleh46:
10.2 was working fine. SafteyNet failed but it ran xposed properly.
[Magisk] biggdevon:
What rom/kernel you using? Pay isn't working for me using arter97's kernel.
[Magisk] Hadookie:
I've finally got the latest Magisk and Manager playing nice with Safetynet however now I'm scared to install any modules fearing the CTS mismatch ?

Has anyone managed to install AdAway without tripping safetynet?
[Magisk] teddy0209:
Activate systemless host in magisk manager settings, reboot then install adaway.
[Magisk] kinfam:
Yes, I have Google assistant and adaway installed, with working Android Pay (just used it on a vending machine actually).

*Edit* As teddy stated above, make sure to enable systemless host.
[Magisk] Kyleh46:
I'll have to try this again when I get home. I just attempted an uninstall of MM 4.1 with a fresh v10.2 installed, installed MM 3, enabled magiskhide, not sure what you meant by SN so I cheched everything that might have that acronynm, updated to 4.1, updated to 11.1 through manager and the same results. I reflashed 10.2 from zip just now and it's working with xposed properly again. Still getting the CTS mismatch for SafteyNet though. I never was able to get net to work properly, might be due to my root addons like AdAway.
[Magisk] de.er:
SN means SafetyNet. You won't pass it with xposed active.
[Magisk] Captain_Throwback:
It's because of Xposed.
[Magisk] android_htc:
I have a Note 4, N910F.

Using Ram Kernel v5, enforcing version
[Magisk] B!GBOY:
it broke titanium backup (freeze/defrost) for me too. went back to 10.2 and its working again.
[Magisk] Captain_Throwback:
Logcats?
[Magisk] FlintStoned-:
Hi, Thank you for your reply. It used to work fine with magisk 10, but since v11 it reboots everytime when putting in and taking out magnetic dock and also magnetic cable charging.

Also, I'm running Xposed so safetynet isn't working for me.
[Magisk] reis1996:
Just flashed latest zip and installed app

Safety net fails, rest everything went fine

I logged in pogo before installing magisk but can't seem to login after. Any reason why?
[Magisk] Captain_Throwback:
You can remove the SafetyNet Helper app from the Magisk Hide list (actually you don't need the app at all).

Also, have you tried disabling all of your modules and seeing if SafetyNet passes? I see you have V4A installed - not sure if that could be the issue, but I see that cause a lot of inconsistency in the thread.
[Magisk] Captain_Throwback:
Disable/Enable Magisk Hide and reboot.
[Magisk] Filip013:
Is there anyone who had difficulties getting Magisk Hide to work with Magisk v11.1 and Manager v4.1, but managed to in the end?

I cannot get Magisk Hide to work with Magisk v11.1 and Manager v4.1, but I got it to work with Magisk v11 and Manager v4. I've already left a bug report with logs on Github, but I wanted to check here anyway to see if someone found a solution.

I only see people here who have set up Magisk v11.1 and Manager 4.1 without issues and people who couldn't get them to work at all.

Also, I want to report that I can pass SafetyNet with system Xposed and Rootswitch (with Magisk v11 and Manager v4).
[Magisk] teddy0209:
I updated directly from v11+4 to v11.1+4.1.... In v11+4, you need to toggle off/on magiskhide again after a reboot in order for it to activate...
[Magisk] Filip013:
Yeah, I know that. That works with v11+4, but I can't get it to work with v11.1+4.1.

I'm fine where I am right now with v11+v4, but I was just curious if I could update my config. (It seems that every other version of Magisk works for me. :D I couldn't get v10 and v11.1 to work, but I had no issues with v9 and v11).

Edit: Sorry, didn't meant to quote [MENTION=3443130]gk1984[/MENTION]
[Magisk] teddy0209:
I don't know what the problem on your side, but the v11.1+4.1 is just a fix for v11+4... ?
[Magisk] FlintStoned-:
[MENTION=4470081]topjohnwu[/MENTION]

Also, when trying to open settings it also crashes, probably more things will cause a crash. I've cleared data and dalvik but not success. When magisk is uninstalled, things work. After installing it again, things crash again like before.

Any thoughts on this?
[Magisk] Captain_Throwback:
There's nothing Magisk/root related in that logcat, by the way - Are you actually checking SafetyNet while it's running? It just looks like an early boot log before stuff has loaded.

Maybe it's related to "MagiskHide: Permissive detected, switching to pseudo enforced" - which means it could be a ROM issue, or Magisk isn't handling pseudo-enforcing properly. Tough to say for sure, though. Thank you for the logs, at any rate, and being willing to try and help :).
[Magisk] Filip013:
Hm... A few pages back people were saying they had the same issue as me. They got v11+4 to work, but not v11.1+4.1. I know that v11.1+4.1 was meant to be simple fix but it broke my config. The issue is probably with my stock ROM (MIUI) which is very strict with apps and processes starting at boot. I know it can be fixed, but it could be tricky. Right now, I am happy with v11+4.
[Magisk] teddy0209:
Yup, MIUI can be a problem sometimes, like they break compatibilities for some mods after an update... ?
[Magisk] klark1kent:
I actually just yesterday figured out the Uncertified in play store didn't have anything to do with magisk, root, etc...When reflashing ROM and obtaining root. With root and magisk installed was still certified. It wasn't until I went into titanium backup. It recognizes my device ID had changed... I accepted the offer to switch it back... And then GPS settings showed me as Uncertified. It's pretty annoying. Trying to track down my original device ID from earlier backups to manually reset it to see if I can get certified again. Would that be the cause of the CTS mismatch by chance ?
[Magisk] DarkLanternX:
SN means safetynet,, glad to hear it's working now. Do you want to run Android pay? Or juz some game like Pokemon go?
[Magisk] Kyleh46:
I was attempting to get PoGo to work. I did notice something curious just now though, I don't see SafetyNet in the list for MagiskHide. Searching for it doesn't help and I can't find com.google.android.safetynet either.
[Magisk] f0xG3:
I've just installed the 2.5.0.5 zip file but I'm unable go install the driver. It gives me error about missing BusyBox. Unfortunately, I dunno how can I make BusyBox detect MagiskSU

Do I need to install something else? I'm using Magisk v11.1 / 4.1.
[Magisk] Captain_Throwback:
That's not curious at all. And that's not the name of the process either. The correct process is hidden by default.
[Magisk] Captain_Throwback:
Did you enable Busybox in Magisk Manager?
[Magisk] klark1kent:
In TWRP when istalling the Magisk it is fisnished with "Updater process ended with ERROR: 1"[/QUOTE]

I had the same error when trying to install v10.2. I had a custom ROM with SuperSU baked in. I thought I'd removed super su when switching to PHH originally but guess something messed up. In order to get the flash to 10.2 to go through I had to remove PHH and use SuperSU as main su app. Once SuperSU was working well I was able to flask 10.2 correctly. I then used SuperSU to remove itself and also ran the unsu script in TWRP just to be sure. Flashed boot.img and the install of 10.2 went through. And I was back on PHH. Of course now that's a little different with the new magisk su but if you're having problems flashing altogether you could try that. I'm on 11.1 and 4.1 MM now
[Magisk] afuller42:
I use Magisk's Built in busy box that's enabled in the Magisk settings. I enable that and reboot.
[Magisk] Hadookie:
As soon as I enable systemless host I fail SafetyNet. Disabling it passes.

Do you pass SafetyNet when enabling systemless host? I was able to install V4A and EmojiOne with no issues. Now all I need is Adaway to make my life complete once again.
[Magisk] Captain_Throwback:
I think most people have that option enabled and pass SafetyNet. That shouldn't be an issue. Have you tried enabling systemless hosts, then toggling Magisk Hide off/on and rebooting?
[Magisk] Filip013:
I was only recently able to pass SafetyNet. When I opened Play Store settings I saw that my device is uncertified. I then went to settings and deleted Play Store data, then I reopened Play Store and had to wait for a few seconds for it load. When it did, I saw that my device is now certified.

So if you can pass SafetyNet try deleting Play Store data and try again to see if your device "gets certified".

This info might be relevant to people who are trying to get Android Pay to work (that's not me because my device doesn't have NFC).
[Magisk] lover:
Use https://play.google.com/store/apps/details?id=stericson.busybox or the donated one. It fixed my problem
[Magisk] danecr7:
Hi,

Here is a log file.

Regards.
[Magisk] moktadir:
Enabled systemless, disabled Magisk, rebooted, still getting CTS mismatch.
[Magisk] teddy0209:
Yup, systemless host, busybox, all enabled...
[Magisk] crusader727:
Magisk aims to install mods systemsless, but hey let's recommend users to modify their /system partition :good::good:
[Magisk] Captain_Throwback:
Disabling Magisk likely won't help if you have an unlocked device - that's what Magisk Hide is for, so obviously you need to have Magisk enabled for that.
[Magisk] yochananmarqos:
Updating Magisk's built-in BusyBox will not modify the system partition.
[Magisk] f0xG3:
I have enabled the BusyBox option and have seen the files under magisk/.core/su/xbin . However V4A still complains of missing busybox.

I don't have to install the one from the store right?
[Magisk] Didgeridoohan:
Your boot image is already patched for SuperSU, but there's no stock backup of the boot image. Therefore the installer script can't restore the ramdisk and fails. I'm gonna guess you're using a ROM that's pre-rooted with SuperSU.

Do you want to use SuperSU or MagiskSU with Magisk? If it's the latter you need to flash a clean boot image (no SuperSU patches) before installing Magisk.
[Magisk] Hadookie:
Thanks for this. I enable systemless host, toggled magisk off and on and I passed SafetyNet, no rebbot. Now time to install Adaway. :svetius:
[Magisk] mrinmaydhar:
SELinux Permissive

I was trying to set up Permissive kernel on my XT1643:Athene using the elementalx kernel. Some posts that help in the process are https://xdaforums.com/xposed/how-to-set-selinux-to-permissive-boot-t3034245 and https://xdaforums.com/showpost.php?p=59026701&postcount=11.

Flar2's method https://xdaforums.com/showpost.php?p=58887725&postcount=230 seems to be sound, but unfortunately we do not have these directories, so the scripts are useless.

Can anybody help me in the process of making my kernel permissive?
[Magisk] danecr7:
Thanks for this answer, I am on stock oxygen OS root with systemless SuperSU zip file with a custom kernel (Elemental-X).

I am satisfied with SuperSU so I would like to keep it.
[Magisk] crusader727:
magisk has post-fs-data.d, see GUIDES & DOCS.

you will have to disable MagiskHide cause it will set "pseudo-enforcing"
[Magisk] geno93:
Hello guys can anyone help me? I have xperia z5 premium with 6.0.1 romaur and today i installed magisk on my phone for pass the safetynet for play on fire emblem hero, install pass withouth any error and the magisk root work properly but i get the safetynet fail cts.... i will post some screen if need .Thx in advance hope someone will help me , have a good day =)! (and sorry for my bad english im italian) Forget to mention i have supersu before i dont know if it mean something ( think i just overwrite it with magisksu ) and i check the option for hide magisk.
[Magisk] GryphonBR:
Thanks for the reply, mate. By recovery log, do you mean the one from TWRP itself? I could provide it, no problem, but it doesn't seem like the issue is with installation, but rather between Lineage's and Magisk's Superuser management - in System Settings, I can see that Lineage acknowledges a partial su installation, but it's limited to ADB only. I have not tried other kernel's either, essentially 'cos my Kenzo has apparently very unique hardware (cameras and fingerprint), so it took me quite some experimentation before I could find a mix that would get everything to work - AGNi kernel with fingerprint patch, since LineageOS now has added the camera blobs as well. As for what topjohnwu has said, I would actually love to help improve compatibility with my devices (I also happen to have an Xperia Z5c), so anything I can do to help, just lemme know :)

Oh, one more thing - v9 was working, indeed, but my issue around v10 was the Manager, not Magisk itself; I've even gotten Manager v4 to work with Magisk v10.2 and phh v266.

If you don't mind me asking, which ROM are you using? I've been struggling with my LineageOS installation on a Redmi Note 3 (kenzo) and I can't get the Superuser functionality to work at all...

Buddy, ain't you using TouchWiz? Last I checked, there's a specific Xposed module for it, topjohnwu's version wasn't supposed to be compatible - same thing happens to my Kenzo when I'm using MIUI, these skins are so heavily customised that Xposed framework needs to be, too.

I just used Titanium Backup to restore apps on one of my test scenarios, Redmi Note 3 (Kenzo) with latest Development MIUI 8. I did have to enable USB apps installation, 'cos at first I assumed it was the enforcing SELinux but switching it to permissive didn't do the trick; then MIUI was complaining about USB installation, so I enabled that and boom!, Titanium Backup back in action for backups and restores.
[Magisk] Didgeridoohan:
Then you should problably start over from a clean boot image (as in flash the stock boot image). After that, flash SuperSU and your kernel before installing Magisk. You should be good to go then...
[Magisk] Nomelas:
Magisk randomly stopped working (it worked fine about an hour ago and I didn't touch any settings) says I no longer have root
[Magisk] Didgeridoohan:
Yeah, like I said, a recovery log probably wouldn't give much...

Have you tried disabling built in superuser management?
[Magisk] bmg1001:
Just wanted to give my confirmation of a successful Android Pay purchase on Magisk 11.1 on a Vending Machine at my local college.

Nexus 6P

Magisk 11.1

App Systemizer and Emoji One Modules

Viper4Arise 2.4 Deuteronomy (Only 2.3.40 and no deep buffer) (this is a system mod, not systemless)

ROM: Dark ROM (based on Lineage)

KERNEL: Flash Kernel 2/4

F2FS
[Magisk] moktadir:
Magisk, BusyBox, Magisk Hide, Systemless all enabled and rebooted, still getting CTS mismatch, Everything worked fine back in v9.
[Magisk] GryphonBR:
Yep, I disabled it in Settings, but it was useless. Trouble is that, apparently, su management is embedded into LineageOS' settings, so I wouldn't even know how to remove it entirely - and, from my understanding, if there's any other su management installed on the phone then Magisk won't take over, or am I wrong in this?
[Magisk] photolarry:
Well I didn't test 4.1 as that wasn't released yet. And it's not my responsibility. I do not have the time right now and disagree with mister throw back. My device is listed in the signature and is supported. Sorry but I'm not obligated to create logcat for anyone. That's your opinion and choice. If I have the time I'll attempt to remove the older version and try 4.1 but again I should not be forced to use his superuser internally. If I wish to keep using phh then that option is mine.
[Magisk] GryphonBR:
Depends on the release, in fact. I've used 4 or 5 from the same dev, 2 had it and the other didn't - but, either way, Magisk v11.x actually takes care of the su itself, as I've tried that a couple of times. The problem I'm facing is that Lineage's Settings have embedded superuser management, and it would seem as Magisk Manager won't work if it detects some other su management in the system.

But I could be wrong in my assumption, I just can't seem to figure out how to correctly detect this, you know?
[Magisk] Didgeridoohan:
[MENTION=1162986]Captain_Throwback[/MENTION] phrased it quite nicely, IMHO:

"So either keep your problems to yourself or help be part of the solution."
[Magisk] biggdevon:
You're also not forced to litter this thread with your complaints since you're not forced to use this software at all. So if you're just going to b!#&h but offer no information to help the community then kindly take deconstructive comments else so you can stop wasting our time so we can help people that are actually willing to contribute to the process.
[Magisk] Rohaq:
Just wanted to say that I just threw a long-overdue donation towards topjohnwu for all his hard work on Magisk and Viper10. Thanks dude!
[Magisk] photolarry:
Then stop posting. I was done yesterday
[Magisk] de.er:
I can't believe this guy. The Dev is doing all this work for free and it's your choice to use it, no one forces you to use it or update it. Take it or leave it. People were asking you for logcats to help you with YOUR f** problem, but you in return come back with this self centred arrogant crap.
[Magisk] westeight:
Working fine on my HTC 10:
[Magisk] GryphonBR:
Weird, it never worked for me in Magisk at all; I only get the "Rooted but no permission" message on the Manager, although in Developer options I can always choose between Disabled or ADB. I even tried to get root permission on an ADB session, and I got the system prompt instead of Magisk's...
[Magisk] photolarry:
That's your interpretation. I'm not asking for any further information or help so leave me alone. I've been contributing to this forum for years and so if I choose not to create log for this issue, that's my choice. I never said I'm forced to use. Yesterday I said it was bad to force his superuser into us without choosing. The conversation is over. Please stop commenting! I can't believe all the attacks on me just for stating one issue.
[Magisk] biggdevon:
Yes. I have hide, busybox, and systemless hosts checked with adaway installed and all green in magisk. SM-N920T stock 6.0.1 with custom kernel
[Magisk] Hadookie:
Thanks for the response. I got everything working fine.
[Magisk] ric69:
Excellent thanks for the great work
[Magisk] GryphonBR:
Thanks for still giving me ideas, really appreciate the effort!

So, I tried a couple of things, but the result always being the same (Magisk Manager reporting "rooted without permissions" and Developer option between disabled and ADB):

-installed a version that has no embedded SU;

-installed a version with embedded SU and removed it manually before flashing Magisk v11 (I didn't try this with v11.1 because it wasn't available at the time yet);

-installed a version with embedded SU and let Magisk handle its removal.

By looking at the installation logs, I could see that Magisk was doing its business nicely (removing the pre-installed su and replacing it with its own), but as I said, none of these methods bore any different result.

[MENTION=4667597]Didgeridoohan[/MENTION], sorry to bother you again, but would you have any suggestions on extended logging I could perform to, maybe, try and catch what's not working properly on my config?
[Magisk] gr8st:
Hmm that's annoying, try disabling xposed all together through magisk and reboot then see if mag port problem persists. Could be faulty rogue module then you must go one by one to suss it out. If not, then all I can think is clean install everything and no data partition restore only TB. New full AOXP will be released soon so maybe just roll back to magisk v10 to hold you over till it's released.

Sucks about safety net hopefully we can figure something out.
[Magisk] GryphonBR:
For Titanium to work? Not necessarily... But I can't even get root to work at all, removing su or not Magisk Manager only has the same "rooted but no permissions" message.
[Magisk] Prfndhatrdofman:
Not working on Moto Z (Nougat). installing 11.1 successful but magiskSu doesn't function. Anyone else run into this?
[Magisk] GryphonBR:
Might be the same issue I have, what OS and kernel are you currently on?
[Magisk] Prfndhatrdofman:
Android 7.0

Build: NPL25.86-30

Stock Kernel.

Magisk 9 worked fine with Phh Superuser (aside from root disappearing after a while, but comes back with reboot)
[Magisk] Filip013:
I'm interested in your case because I also have a Kenzo. Mine is an FPC, but from what you've said I guess yours is a Goodix? I'm currently using Magisk v11 and Magisk Manager v4 on Global Stable (v11.1+4.1 don't seem to work) and I can pass SafetyNet even with system Xposed intalled but disabled using Rootswitch.

I also installed the latest nightly Lineage 14.1 as a data slot ROM in DualBootPatcher. Of course, secondary ROMs can't pass SafetyNet, but I can use MagiskSU and when I activate Magisk Hide and look at the log, I see that it performs all the necessary steps.

Your case seems to be very different. The only explanation I can think of is that if you have a Goodix, so you need to flash... I don't know what, kernels, patches?

If you have a Goodix and want to use a custom ROM, well, that might be an issue for now. I'm sure the developers will figure something out. In the meanwhile, give Global Stable a go (Global Developer and custom MIUI ROMs pass Basic Integrity but not Safety Net because they don't have a registered CTS profile).
[Magisk] vil33:
magisk phh reupload

MagiskHide doesn't seem to work for me(I tried disabling and enabling it and restarting), is there any way you could put back the links for the magisk phh module? thanks.
[Magisk] Nomelas:
A reboot fixed it.. But for how long?
[Magisk] stokholm:
What you say confused me. It can add files to subdirectories of /system (like /system/priv-app/newfile), but can't add files to /system itself (like /system/newfile)? Why is that exactly?
[Magisk] Captain_Throwback:
Not sure why you're confused. It's a limitation of Magisk. You shouldn't need to add any files to the root of /system anyway, so I'm not sure why it matters.
[Magisk] ikostas_1:
is there any working mod for MM 6.0.1 note4 n910C?? it makes bootloop when installed
[Magisk] Alxoom33:
On adb I typed in: shamu: / $ adb shell pm uninstall com.topjohnnwu.magisk

get the error message: /system/bin/sh: adb: not found

So I typed in: su and got the same result after the uninstall command

sush: adb: not found

Not sure what I am doing wrong. Also tried terminal emulator in TWRP with same result
[Magisk] Chahk:
You are already in adb shell, no need to type that in. Just "pm uninstall com.topjohnnwu.magisk" will work.
[Magisk] smohanv:
Yes I did. I can confirm from my experience that Chainfire's apps (i.e cf Lumen, Recently) are recognising phh's root. Also, TiB, LuckyPatcher (sorry to mention this app here) are not recognising phh's root and reports as the device is not rooted. I found a way around. Flashed SuperSu (magisk version) and run all the above apps and accepted root access via SuperSu and then completely uninstalled and removed SuperSu root and flashed phh's. Everything works fine including AP.
[Magisk] Playe:
How did you install it on dp5? Are you decrypted or did use FlashFire?
[Magisk] rignfool:
You have leftover crap in /data/data/ for that app...

Find it and delete it...
[Magisk] adrman:
Interesting. I've not had a problem with TiB and phh's root on my N6p either before or after Magisk.