yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
First part (known issue, that's fixed in the next release):

https://xdaforums.com/showpost.php?p=71092344&postcount=14

Second part:

Where on earth did you see it explained that you can pass SafetyNet with Xposed? Deactivate or uninstall and you have a chance of passing...

You can check if Magisk Hide is working properly by adding a root checker to the Hide list. If it can detect root when it's not on the list, but can't when it's been added, Hide works and you've got other issues.
[Magisk] dagoban:
I use systemless xposed so that shouldn't be any problem.

Also I already get safety net issue when just having TWRP+ magisk with no xposed whatsoever.

Also every root checker detects root nomatter if i enable it in the list or not.
[Magisk] Didgeridoohan:
Of course it's a problem! Systemless or not doesn't matter. Magisk Hide can't hide Xposed, period. You'll need to deactivate it or uninstall or you won't pass even if you get all other issues sorted.

I've just created a thread with a bunch of tips and tricks. Check it out, there might be something there that can help you:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] Telperion:
Unfortunately that's part of the problem, no stock kernel source. I'm working on adding using insmod but so far I get an error when trying to add the loop driver.
[Magisk] ishtiz:
Hey can anyone please help me on how to install magisk on ZenFone 2 with lineage 14.1?? I tried just flashing the magisk zip but it resulted in recovery bootloop.....i also tried flashing systemless su but it resulted same...so what did i do wrong?
[Magisk] Didgeridoohan:
This is straight from the release thread, currently known issues:

Since you're using LineageOS I don't know if it's applicable, but worth a shot.
[Magisk] Mikxx:
Is there any way to completely uninstall the preinstalled root so I can use only magisk im on dualboot ressurectionremix
[Magisk] Sam Nakamura:
No need to remove the pre-installed root, just flash magisk zip and install magisk manager from Playstore.

I'm on RR N and it works just fine...
[Magisk] DarkLanternX:
Use this,

Hit thanks if this helped :)
[Magisk] DarkLanternX:
U have to uninstall the preinstalled super su first, i had some problems with that too,

To fix it follow these steps:

1. Clean reflash rom

2. Flash unsu

3. Flash magisk without rebooting ( rebooting can cause bootloop as there is no boot.img )

4. Install manager

Thats it...enjoy ;)
[Magisk] jcrompton:
If you want the full functionality of magisk you do have to use magiskSU. therefore you do need to unroot any pre-rooted ROM. You can use the script that is listed in one of the answers to your post. but the way I do it is to mount the system in TWRP and then I just go and delete the Su files in system/bin and system/xbin

---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------

Magisk Hide will not work with any other root than MagiskSU in the current version
[Magisk] Captain_Throwback:
I think that user was saying that the Magisk installer will remove any pre-existing root when it installs. That was a recent update, I believe.
[Magisk] jcrompton:
I think I did see that it was supposed to do that period but just yesterday I did an I with root in place and it left my phone rooted, installed Magisk, but kept giving an error that Magisk Hide would only work with MagiskSU.

I had to manual remove the prior root

Granted it may be partially due to improper Magisk installation on my S7 Edge

BTW ... you never did comment on my query for any hope for a fix or work around for full installation (I.e. working Magisk Hide) on AOSP (non Sammy) ROMs for my SM-935F S7 Edge ????
[Magisk] Captain_Throwback:
Well if it's not working for me and I haven't fixed it, I'm not sure what you expect me to be able to do for you?
[Magisk] jcrompton:
Strange question ....... ??????? I wasn't expecting you to do anything for me unless of course you are offering .......

I was asking exactly what I asked ...... Is there hope for a work around? Is there someone that might could have more knowledge as to why it's happening? Is it a Magisk problem or is it a kernel problem? The potential combinations of questions are possibly endless

But nevermind ...... I wasn't asking you to do anything for me specifically ...... Just hoping to have a cordial , not condescending, dialog about an issue that was effective both of us ,,,,,,, not sure why I expected something do ridiculous!!
[Magisk] Captain_Throwback:
The extent to which I've looked into it is to see that it isn't working. That's it. I know I seem to appear to have all the answers here, but in reality, when it comes to Magisk, I'm just a glorified tester. So my reaction to your questions was not meant to be condescending, but rather to express confusion as to why you'd think I'd have any of those answers in the first place.

EDIT: I'm not even actively seeking answers to those questions, as the device on which I have those issues isn't my active/daily device.
[Magisk] jcrompton:
My apologies for appearing to have expectations.

Thank you for explaining

I guess I'm just a bit frustrated because I'm trying to act in good faith and put people together that might have solutions ........ the ROM developer and their kernel developer(s) act as though they have no interest and state that the only way to fix things is to get the "magisk" people to fix "their" problem. I was just hoping to find out who the players were so a dialog could be started between the different people. Certainly not in a demanding way ... but more with a sense of hopefulness
[Magisk] Captain_Throwback:
I know [MENTION=4470081]topjohnwu[/MENTION] has plans to look into all the issues people are facing, but he's just one person, unfortunately. I think his first priority is supporting devices where the boot.img gets broken by flashing Magisk, since those result in unusable devices. Fixing SafetyNet compatibility issues is on the list, but much lower priority than helping people who can't use this on their device at all.
[Magisk] jcrompton:
Understood .... Thank you
[Magisk] Sam Nakamura:
I can confirm that flashing magisk zip + installing magisk manager from Playstore gives full functionality on op2 with official RR N..

Hide works (safetynet), SU works, modules work...
[Magisk] jcrompton:
That's awesome .... I guess for me the problem is the only partially functioning Magisk installation on my device (that's great because it was always an added step to worry about unrooting before installing Magisk in the past)
[Magisk] Sam Nakamura:
For me it worked to just flash zip provided on first post on this thread and installing the manager form store, did try the manager in-app install option..
[Magisk] jmiller3342:
So I am wondering what this is for?? I flashed magisk and I get this...? What does it mean?
[Magisk] Sam Nakamura:
Bro, these are basic functions..

You better use search function of this thread or Google :)
[Magisk] Mikxx:
thats what i tried and pokemon go didnt work (unable to autenticate) magisk was installed tho but safetynet check failed (for now i use omni rom for magisk pogo works but the magisk safetynet check failed there too
[Magisk] jmiller3342:
I mean how do i fix that? Limited root??? What does that mean?
[Magisk] Sam Nakamura:
https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post69648715

Would have shown if you'd have used search as suggested..

---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------

I made the experience that it depends on the rom you are using, on some I do pass safetynet on other not.. Im not sure but it seems there has some dedicated commit to be involved of some patch, but that's just guessing as I haven't had a closer look yet as it worked out of the box so far for me, at least on my daily driver rom.. :)
[Magisk] Didgeridoohan:
Are you using MagiskSU and what version of the Manager do you have installed?

Whoa... That's an old post about an old (fixed) problem. I doubt it has anything to do with the problem [MENTION=7266551]jmiller3342[/MENTION] is facing...
[Magisk] Peter.1997:
Pokemon GO on Resurrection Remix (LP 5.1)

Hey guys, I can't figure out how to get PoGo working on my G900f and the Resurrection Remix Rom V5.5.9 on Android Lollipop.

I tried everything i got to know on XDA and other Forums: Installing Magisk, Unroot it with a unroot.zip, used phh's Superuser, unrooting with the SuperSU App...nothing worked.

The thing is, it works perfectly fine on Resurrection Remix 5.7.4 with Android 6.0.1 (Magisk, Xposed and even PoGo), but I want Android Lollipop because of some reasons (especially the Audio Limiter, maybe someone can help me fixing this on Android 6.0, then I would be really happy! :D).

What I want: Resurrection Remix or CM12.1 running Android 5.1, and Magisk to function, to play PoGo again..

OR: Ressurection Remix or CM13 running ANdroid 6.0, but I want to use Viper4Android, but this does somehow lower my Audio Volume, when there are Bass Drum Kicks etc.
[Magisk] Mikxx:
could it be because of we have diffrent devices?
[Magisk] Sam Nakamura:
Not sure, I'd tend to think that it's more rom specific..

---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------

Well, sorry then.. :) maybe to fast as error output seemed to be the same..
[Magisk] Mikxx:
then how does it come pogo doesnt work for me? could you do me a favor and test it out so we know its rom based because magisk on its own works (as far as i noticed)

because if so i need to look no further,
[Magisk] Sam Nakamura:
Oh, no way I install this game..

I'm absolutely not into PoGo :)
[Magisk] Artim_96:
Well, obviously you didn't gave superuser rights to Magisk installer. Just go into SuperUser tab and give permission
[Magisk] Mikxx:
well thanks anyway
[Magisk] jmiller3342:
I did...
[Magisk] Artim_96:
Also uninstalled every other root managing app?
[Magisk] jmiller3342:
Yeah.. I flashed PHH superuser but I don't like it...
[Magisk] Momotani-Hitoshi:
Stickmount doesn't work with Magisk installed. I get "service is busy" when trying to mount. Any workaround/fixes or alternatives?
[Magisk] karthik km:
The modules does not contain application

Why?
[Magisk] chas123:
He has a legitimate issue that rebooting won't fix. Magisk depends on su files from recovery. If the dev that maintains the recovery (twrp) for your device hasn't included supersu in recovery, you can reboot all you want. It just won't work
[Magisk] Captain_Throwback:
Magisk doesn't depend on any su files in recovery? Not sure where you're getting that from...
[Magisk] dizM0nkey:
Magisk w/Marshmallow and HTC 10?

Are there any Magisk compatible ROMs running Marshmallow (so I can still used Xposed) for my HTC 10? I've looked at LeeDroid and Viper10, but both Magisk versions of the ROMs look to support Nougat only ... not Marshmallow.

Help is appreciated.

Thanks,

diznanl
[Magisk] chas123:
Well when I flash the latest on my m10, and look at / there is a supersu folder. Not there after flashing on my axon 7. Benny added the su files to twrp recovery and now they show on my 7. They link to /magisk on boot. OMJ was who I got it from.
[Magisk] Captain_Throwback:
The supersu folder in TWRP has NOTHING to do with Magisk. And no, they don't link to anything on boot, as they only exist in the recovery ramdisk. Magisk and SuperSU are two completely different and separate things. I'm sorry, but you have it all wrong.
[Magisk] chas123:
Try it yourself. Boot to recovery, and look at root in file manager. There is /supersu, but no /magisk. Boot up and look at root using a file explorer. There is /magisk, but no /supersu
[Magisk] Captain_Throwback:
You're not listening to me. The /supersu folder that you see in TWRP is part of the RECOVERY RAMDISK. It simply doesn't exist when you boot the device because, well, you're not in recovery. There's no /magisk folder in recovery because the magisk.img doesn't get mounted in recovery - only when booting into Android. It's really that simple. I'm not sure why you don't understand that these two things are completely unrelated, but they are. One has NOTHING TO DO WITH THE OTHER. Period.
[Magisk] chas123:
Where does the /supersu folder come from after flashing magisk bone stock?

On a HTC 10
[Magisk] Captain_Throwback:
I don't understand your question. The /supersu folder exists in TWRP already. What do you mean, where does it come from? Unpack the TWRP image, you'll see it in there.
[Magisk] chas123:
Stock img's- I flash ONLY magisk 11.1 on my HTC 10. Go directly to home>advanced>file manager ( Your twrp Thank you BTW), and there exists a /supersu folder in the root that was not there before. There is no /magisk folder ( I get it- img has not been mounted). I boot up, install root explorer, grant it root permission, look at root- The binaries have now been linked to /magisk and there is no /supersu folder. Try it.
[Magisk] Captain_Throwback:
Before you flash anything, just boot into TWRP, and use the File Manager to look at root. The /supersu folder is there. It has NOTHING to do with Magisk.
[Magisk] chas123:
I'll try. Do you know offhand where the su binary is supposed to get installed on 11.1?
[Magisk] Captain_Throwback:
All I did was boot into recovery, decrypt, and use File Manager. Look what we have there...
[Magisk] Captain_Throwback:
See attached.
[Magisk] chas123:
Thanks for the help. That gives me something else to go on. Earlier version was working good.
[Magisk] Captain_Throwback:
Earlier versions didn't have MagiskSU. It used a modified version of phh's (NEVER SuperSU). So there have been some changes. [MENTION=4470081]topjohnwu[/MENTION] is working on compatibility for devices right now, so just be patient and maybe the next update will work better on your device.
[Magisk] arrrgh:
Has anyone gotten MagiskSU to work on Nexus 10? Starting with freshly wiped device I get no error during flashing and Magisk itself gets installed properly but MagiskSU is missing (no root after multiple boots). I can get root with SuperSU but would prefer MagiskSU. I tried both the stock (5.1.1) and Pure Nexus (7.1.1) ROMs and the same happens on both.
[Magisk] Artim_96:
Then get rid of it...
[Magisk] :
Thread cleaned.

Do not post or discuss warez.
[Magisk] whalesplaho:
i use magisk v11.1 but if i try to enter twrp, it freezes

Xperia Z5

Nougat .376

Kernel- https://xdaforums.com/xperia-z5/development/kernel-zachs-kernel-playground-z5-wip-t3340725
[Magisk] Captain_Throwback:
What does your inability to enter TWRP have to do with Magisk?
[Magisk] whalesplaho:
flashed a kernel, enter twrp, flashed magisk v11.1 den reboot... install magisk manager & shows root. later i tried to enter recovery but freezes at bootlogo.
[Magisk] Captain_Throwback:
That doesn't answer my question. Magisk doesn't touch recovery. So you need to look elsewhere to solve your problem.
[Magisk] whalesplaho:
im entering recovery fine with supersu & phh superuser.... thanks for tha help!

im fine with phh superuser, thought lil help might be given.
[Magisk] Devhost97:
https://github.com/topjohnwu/Magisk/issues/87

Hello :)

What does mean ? Do you make fix to next version of Magisk or what ?
[Magisk] Xennet:
[MENTION=4470081]topjohnwu[/MENTION]

Installed t latest version of magisk 11.2. Flashed from twrp. From ur release info its mentioned dat busybox v is 1.26.2.

But my budy box v is stii 1.26.1.

Tried flashing busybox v 1.26.2 yds from twrp but ending in error..

Log file...

#Fri Feb 24 05:19:37 CST 2017

#Ignore umount errors!

================================================

BusyBox 1.26.2-YDS arm (Stable: 03 Feb/17)

-----by YashdSaraf@XDA-----

================================================

Mounting /system --

Checking Architecture --

Looking for => 'arm', found => 'arm64-v8a'

64 bit architecture detected --

Checking if busybox needs to have SELinux support --

SELinux support is ENABLED --

Systemless root detected --

mkdir: can't create directory '/magisk/phh/bin': No such file or directory

***Abort!!***

Cause: Installation directory /magisk/phh/bin is not accessible

Quitting installer -- Check /sdcard/BusyBox-YDS-installer.log for errors

Please help
[Magisk] Didgeridoohan:
That's exactly what that means! :good: Next release should hopefully make a whole bunch of incompatible devices compatible.
[Magisk] jcrompton:
I was thinking about this last night ... and I know this may be a little self-serving but I did want to share a perspective. I know that "passing SafetyNet" is wonderful byproduct of using Magisk but Magisk Hide in general has other benefits for hiding itself from various apps (banking, etc etc). So I was hopeful that the fact that Magisk Hide in general being borked for at least the AOSP versions of S7 Edge (in that any app that you check Magisk Hide force closes or even causes boot loop) might move it up a half a notch on the priority list for [MENTION=4470081]topjohnwu[/MENTION]

(I'm sure that busy doesn't even describe ...... )

But my main point was that it's not ... just ... passing SafetyNet

I guess the real question is -- is it something on the boot image side (certain devices , lack of sources , etc) or is it even something that can be fixed on the Magisk side. I made a feable attempt at extracting the "stock" kernel boot image for the S7 Exynos and comparing to the AOSP boot image and the differences seemed tremendous ... so I wasn't sure where to start
[Magisk] chudy_85:
I have busybox v1.62.2
[Magisk] aiola1982:
I can confirm that flashing Magisk breaks the ability to enter twrp (build into kernel) on Xperia Z5/Z5c. Let's wait for new version and (hopefully) full support for sony.

[MENTION=4471890]whalesplaho[/MENTION]

You can use "fastboot boot kernel.img/recovery.img" if you need twrp until it gets fixed.
[Magisk] Captain_Throwback:
Oh this is for devices without a recovery partition? All bets are off, then...
[Magisk] laggardkernel:
Open Magisk Manager, enter Settings, enable busybox. In fact, busybox from Magisk is put in /data/magisk by default, enable this switch and it will be linked and exposed in /system/xbin.

Look at the your info picture, the busybox is /system/xbin/busybox. That means it's a real binary file, may be the default busybox in your ROM. If it's the busybox from Magisk, it will be shown as a link pointing to /data/magisk/busybox.
[Magisk] jhedfors:
Did you not see the above post? You can get kicked off of the forums for discussing applications that rip-off developers. This is a developers forum after all.
[Magisk] jnx_r:
I have installed Magisk and the safetynet check is also OK. It is working as expected on RR 5.8.2 OP3t. Checked with Pokemon Go. But the root check keeps failing for this one app:

https://play.google.com/store/apps/details?id=cris.org.in.prs.ima&hl=en

Does this app not work in everyone every other rooted device as well?
[Magisk] lalitjoshi06:
If safety net passes then Just go to magisk hide and tick this app and reboot, it will work.(working on my device Armani)

But other one

With mine other device, this app not working. Force closings and shows you are rooted. I m on leeco s2 RR 5.8.1. In this device not passing safety net, so I think that's why not working.
[Magisk] jnx_r:
Yes, I did that mate. It's still not working. Did you try running the app on your device? What does it say? In my device safety net is pass OK. Root checker also declares non rooted device. Even Pokemon Go is working fine. But it still says, that its a rooted device, so it wont run.
[Magisk] Captain_Throwback:
App is working fine here after installing and enabling Magisk Hide. Initially I tried to open it, and got a toast about my device being rooted. Swiped the app away from Recents, added it to the Magisk Hide list, and opened it again. Immediately worked.
[Magisk] royal_eagle:
Guys,

Airwatch still detect root even after ticked settings and airwatch agent on magisk hide list, any idea?
[Magisk] Nomelas:
Do the email app too

Also make sure you remove any root permissions to that app that you might have set

Also, airwatch is finicky, you might need to un enroll and reenroll after
[Magisk] jnx_r:
Okay, I am confused. Am I doing this right? I've put a few screenshots, can someone tell me what I'm missing here.
[Magisk] Captain_Throwback:
Seems the app is detecting something else. I see you have modified toasts in your ROM, so I assume you have some other mods going on. The app is likely detecting some other type of mod. Couldn't speculate as to what that is.

EDIT: Looks like you're using a CM/LineageOS/AOSP non-stock ROM. That's probably what the app is detecting. A logcat or dmesg might give you more information. Either way, Magisk is doing its job. If you find out what it's detecting, *maybe* Magisk can be updated to patch/hide it. But that really depends on what it is, since it's not tripping SafetyNet.
[Magisk] xsycox:
I am trying to get Xposed running with systemless feature, but it just does not get started. It says, it is installed, but not activated. Without systemless it was working fine.

The log says, there is no access to the log. Eacess or so.

Redmi note 3 pro with NX ROM (marshmallow, www.nxrom.us) and Radon kernel.

This is what I did/installed:

I flashed Magisk 11.1 and installed the manager app. It seems to work, as I get those two green marks/fields. Unfortunately, the safetynet mark/field gets red, when I test it. :\

I flashed https://superuser.phh.me/superuser.zip (phh's superuser) and installed phh's superuser app.

I installed the Material design xposed installer http://xdaforums.com/devdb/project/dl/?id=21776&task=get

Then I went to Magisk's modules and installed the systemless 87 framework (by robo).

Still it says, the framework is installed, but not activated ... and whatever I do, I do not get it activated. I reinstalled everything for the fifth time or so.

It also seems, that Xposed installer does not "see" the root. At least, I do not get a pop-up asking for root rights from it.
[Magisk] Xennet:
On my Op3t irtctc app works fine after magisk hide..Safety net check is green..

Think its t problem with ur RR ROM. I am on freedom OS...

Check t magisk log whether it is hiding cris.org.in.prs.irma which is t irctc app...
[Magisk] jnx_r:
Yes, you're right, I am on RR 5.8.2 on OP3t. Need to figure out what exactly is tripping the root check for this app.

I think it is doing what it is supposed to. But like [MENTION=1162986]Captain_Throwback[/MENTION] says, its detecting something else, which is obviously different in RR from the stock rom. Because some other similar apps are working fine.

EDIT:
[MENTION=1162986]Captain_Throwback[/MENTION] , I also checked this app with Slim7, which ships without root. It still said that my device was rooted, yet it somehow works on the stock rom with root.
[Magisk] jhedfors:
I found this app to be helpful to find what may be causing root detection.

https://play.google.com/store/apps/details?id=com.scottyab.rootbeer.sample
[Magisk] Dale Rumball:
Root beers and and chainfires
[Magisk] biggdevon:
Which chainfire app are you referring to?
[Magisk] yochananmarqos:
The app has not been updated to detect anything systemless, so it's useless in this case.
[Magisk] jnx_r:
The app seems to be weird, I tried it on Lineage, and it said that it was rooted out of the box. Same with Slim Rom.

Also I would like to add, that I managed to get Magisk working for the app, in Lineage OS. Maybe Magisk isn't able to hide root in RR, because its boot image is such that it supports root out of the box.

But why wouldn't it work the same in Slim Rom? Since it doesn't have root in it either?
[Magisk] Dedede_:
I've installed last lineage os build,that rebases CAF and now safetynet is failing,it says that CTS profile mismatch
[Magisk] apc:
This is a known problem of the S6, see this thread.

I created a small Magisk module with the proposed solution. Just load the attached .zip from Magisk Manager. Or wait until it gets added to the official module repo.
[Magisk] lalitjoshi06:
I installed linage 13 official build today for leeco s2.

Strange with magisk CTS false, but with magisk hide that irctc app is working fine.

But SBI pay app not working it show you are rooted.