yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
I've never really trusted ES... :) Have you tried mounting any other way, say through terminal (Google's your friend, I don't have the command in memory)?

And like I wrote, the rw issue is already solved in source so it'll be in the next release. [MENTION=4470081]topjohnwu[/MENTION] is working really hard to fix all the issues. Patience... Apps failing to recognize root is mostly a problem on the app side, and there are ways around that too...

Looks like you're using the official Xposed installer. Use DVDAndroids unofficial installer instead (as stated in the support thread for this Xposed version).
[Magisk] jackie_jagger:
I was using Magisk for a while on my N6P pure nexus rom. I updated to the latest Pure Nexus last night, installed ElementalX kernel and magisk after. I've been stuck on the boot screen since, I don't recall the first boot taking so long? What did I do wrong?
[Magisk] Didgeridoohan:
Impossible to say. Try again, but make sure you can boot without ElemantalX and Magisk first...
[Magisk] zeugme:
[MENTION=4470081]topjohnwu[/MENTION]

Did you have anything new regarding Google Pixel support ?

Thanks and kind regards
[Magisk] Didgeridoohan:
https://xdaforums.com/showpost.php?p=71133174&postcount=16

He's one guy. It'll be ready when it's ready...
[Magisk] Lazdaa:
Anyone else has problems randomly loosing root? I'm running Magisk 11.1 with Magisksu and sometimes after a while root just doesn't work anymore. A reboot fixes this but still annoying.

I'm on a OPO with Sultan's CM 13.
[Magisk] Didgeridoohan:
There's been a few reports of this, yes. You could try force closing the Manager or swiping it away from recent apps. Some users have reported success with this. If this work, try removing it from any battery saving feature/app (doze, Greenify, etc).
[Magisk] rolarocka:
Can someone post the magisk uninstaller here? No matter what I try I can't download it from the official thread...

OnePlus One - Tapatalk
[Magisk] karthik km:
Magisk working fine now
[Magisk] kasiopc:
Hi,

I have a Moto X Play running 7.1.1 with AOSPExtended ROM (unlocked BL). Magisk installed and Safetynet passes, can use Android Pay etc. However there is a travel app for tickets that is detecting root, despite being in Magisk Hide. The app is here net.corethree.lothianbuses

Running Magisk on my LG G4 with magisk on stock debloated ROM (unlocked BL), Magisk successfully hides root. Is there a method to check what could possibly be causing root check to trip?
[Magisk] RandomPooka:
Discussion of that app is not allowed on XDA.
[Magisk] karthik km:
OK

Thanks
[Magisk] Didgeridoohan:
[MENTION=6429574]karthik km[/MENTION] Good!

The app could be detecting "dangerous props", for example ro.build.tags=test-keys. It could also be detecting Busybox and it could be dependent on other apps that also need to be hidden. Check my tips and tricks thread for tips:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] xatou:
Which are the positive of magisk except to hide the root?

Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
[Magisk] RandomPooka:
Modifying all sorts of system settings and files without actually modifying them. You're just having your device use your new/replacement files instead of the ones that are on the device's actual system partition. This lets you change things without actually triggering software that checks for tampering. (SafetyNet being one of most popular examples)
[Magisk] Nomelas:
To add,

It allows you to make changes to the system without having to redo it after every OS update.
[Magisk] Didgeridoohan:
This!

Debloating system apps, making user apps into system apps, changing build.prop values, replacing system UI audio, adding notification sounds, etc. All of this is done with a single flashing in TWRP instead of manually editing and pushing files and apps with numerous reboots.

I love Magisk!
[Magisk] jhedfors:
I strongly suggest editing your post before the moderator removes it.
[Magisk] rignfool:
You will never get help with this here...
[Magisk] karthik km:
Edited

Thanks

---------- Post added at 03:36 PM ---------- Previous post was at 03:36 PM ----------

Got it

Thanks
[Magisk] :
Hey guys. I have successfully flashed Magisk11.1.zip and it works flawlessy now. SafetyNet pass even with USB debugging enabled. My question is, can I change back SuperSU to Chainfire ? Or do I have to use the Magisk Manager app for su ? Thanks and I'm using a OP3T
[Magisk] kasiopc:
I decompiled the APK and think I found the method it is using:

static String isDeviceRooted() {
boolean check1;
boolean check3;
boolean z = false;
String buildTags = Build.TAGS;
if (buildTags == null || !buildTags.contains("test-keys")) {
check1 = false;
} else {
check1 = true;
}
boolean check2;
try {
check2 = new File("/system/app/Superuser.apk").exists();
} catch (Exception e) {
check2 = false;
}
try {
if (new BufferedReader(new InputStreamReader(Runtime.getRuntime().exec(new String[]{"/system/xbin/which", "su"}).getInputStream())).readLine() != null) {
check3 = true;
} else {
check3 = false;
}
} catch (Exception e2) {
check3 = false;
}
if (check1 || check2 || check3) {
z = true;
}
return Boolean.toString(false);
}

I checked build.prop but it was already set to release-keys. The others props were not present however, so I'll try adding in the safe ones.
[Magisk] biggdevon:
Is there any way to hide busybox and/or the presence of the altered props?
[Magisk] Sum1992:
Saftynet failed. USB debugging disabled and magisk hide enabled. How to make it safetynet passed?
[Magisk] Didgeridoohan:
If that's all it's looking for you should be good with Magisk Hide... The props I list in my thread is just an example of common ones. There might be other ways for apps to detect unsafe systems as well.

Busybox I'm trying to figure out myself. If anyone has any tips they're welcome...

And about the props: I've just updated my tips and tricks thread with a little something about that. Under "Things to try" in the link from the post you quoted.

---------- Post added at 16:57 ---------- Previous post was at 16:55 ----------

I'm just throwing this link around like confetti at the moment:

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

Check there for a collection of tips to pass SN.
[Magisk] biggdevon:
I'm assuming these are all found within the build.prop? I don't have all the ones listed in your post but the ones I do have are set correctly. I used the root beer app and it's listing busybox, SELinux flags, and occasionally dangerous props. Not sure why the props go in and out, can only assume it's *Magisk*???
[Magisk] Didgeridoohan:
Not all of those values are in build.prop. There's also default.prop in the boot image... Use getprop to see if you have the props set to values that are deemed safe.
[Magisk] Joloxx9:
TiB, solid explorer, and other apps have same have same problem
[Magisk] Didgeridoohan:
Yes, and like I've said, it's a known problem that's been fixed for the next release... I'm not quite sure what your point is.
[Magisk] cygery:
Hi, I'm the dev of Toggle Network Type 5.0 and similar root toggle apps.

I need to use the u:r:system_app:s0 context when SELinux is set to enforcing. Using SuperSU, this works fine out of the box. However, using MagiskSU it does not due to SELinux policy issues:

Initial try:

$ su -cn u:r:system_app:s0
Cannot execute /system/bin/sh: Permission denied

With this SELinux audit message:

[ 9587.900778] type=1400 audit(1488213960.674:1746): avc: denied { entrypoint } for pid=7083 comm="su" path="/system/bin/sh" dev="mmcblk0p25" ino=466 scontext=u:r:system_app:s0 tcontext=u:object_r:shell_exec:s0 tclass=file permissive=0

First patch:

$ su -c 'sepolicy-inject --live "allow system_app shell_exec file entrypoint"'

Result: shell opened, but not root:

$ su -cn u:r:system_app:s0
$ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0

With this SELinux audit message:

[ 9849.582906] type=1400 audit(1488214222.354:1761): avc: denied { use } for pid=7339 comm="sh" path="/system/bin/linker" dev="mmcblk0p25" ino=366 scontext=u:r:system_app:s0 tcontext=u:r:su:s0 tclass=fd permissive=0

Second patch:

su -c 'sepolicy-inject --live "allow system_app su fd use"'

And it works:

$ su -cn u:r:system_app:s0
#

Also, please check my post here: https://xdaforums.com/showpost.php?p=71213626&postcount=1005

Could you please review those patches and maybe include them by default?
[Magisk] Joloxx9:
Thanks, I hope new release will be released soon
[Magisk] RandomPooka:
You could change back to the SuperSU root solution, if you wanted to uninstall magisk, install SuperSU, and then reinstall magisk. I believe that's the procedure, anyway. You'll want to look at the install instructions to check on how to get SuperSU and magisk working nicely. I think you need to start fresh, get your SuperSU running, and then add Magisk after that's in place.

Why would you want to? You're going to lose all the things that you were saying work flawlessly now that you have MagiskSU/hide. Magisk can't hide SuperSU.
[Magisk] kasiopc:
Just changed all the "safe" values but no dice. Is there a way to see what files the app is trying to access, or values it wants to look at? Sort of like Process Monitor for Windows or strace for linux.
[Magisk] topjohnwu:
Thanks for the insight from a root developer!

As in my changelog, I implemented the context change feature, but not sure if it's implemented correctly.

BTW, if I'm not wrong, the context change is for bypassing some certain selinux restrictions, am I right?

If that's the case, in all of my superuser versions (and the latest SuperSU beta, since Chainfire uses a similar approach what I've been doing to deal with selinux for quite some time lol), all root shell is running in a environment which it's similar to permissive (means all actions are allowed)

You can try to not include the "-cn" command and see if everything works.

If you want to maintain backward compatibility to old SuperSU version, check the "su -v" if it's SuperSU
[Magisk] Artim_96:
Not without any info.

But if you are running a custom ROM you can forget that. Most of them can't pass and might never do. In most cases it's because of a LineageOS based kernel
[Magisk] Phantoml337:
Hi, I've flashed Magisk over a stock Galaxy S4 ROM with a stock bootloader and while it hides the root and passes SafetyNet, I can't turn on WiFi no matter what I try. LogCat shows driver errors:

Wi-fi driver is unstable. Received cmd_statemachine reset

and the wifi device goes into an error state.

I've tried several ROMs and well as a completely stock one and have been unable to resolve this.

Thanks for any help
[Magisk] cygery:
Thanks for your quick reply.

Yes, in my case the context change is to bypass a combination of SELinux and Android permission restrictions. In detail, I need the system-only permission to modify the phone state which I could previously access using the system_app context.

And thanks a lot for your suggestion, omitting the context parameter works well with MagiskSU so I'll add an option in my apps to simply disable usage of that parameter and everything should be fine :)
[Magisk] skinnywaffles:
Hey this is probably a noob question but I'm running PureNexus on my 5x and everything is working fine but the only problem is that my Magisk only lasts for one boot. If my phone dies or I have to flash something, I have to flash Magisk everytime to keep root. Is that the point or am I doing something wrong? Thanks
[Magisk] jhedfors:
I would suggest editing your post removing any reference to warez, as it can get you booted from the forum. It is a developer's forum, and that app is - to put it mildly -anti-developer.
[Magisk] skinnywaffles:
OK? Lol. Thanks but that still doesn't answer my question
[Magisk] jhedfors:
Sorry, I don't know what is happening with your Magisk installation - more details are necessary. If you attach some logs it would be helpful.
[Magisk] karthik km:
Can any one help me?

I don't understand what is safety net and

CTS profile mismatch

Thanks in advances:good:
[Magisk] Ethan140310:
Guys I'm having this issue, I installed Magisk, and in the app it said rooted, and I use root apps without issue. But after a few days andor reboots, I lost my root, and have to flash the zip through TWRP again to gain root...

Anyone know why and how to fix??? Pls help...
[Magisk] karthik km:
Use magisk uninstaller to remove full magisk from system

And again flash latest magisk

It will solve your issue

Thanks
[Magisk] Ethan140310:
Okay, trying and will report back if it helps
[Magisk] candiesdoodle:
I have the same issue. Removing magisk and reinstalling doesn't help

It happens only when magisk hide is enabled and rebooted. {On 11.1}
[Magisk] Didgeridoohan:
SafetyNet is Googles way of making sure your device isn't rooted. CTS profile mismatch basically means your device isn't trusted.

If you don't need to use apps like Android Pay or others that use the SafetyNet API you can ignore it. Otherwise check this thread for some tips:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] Teura:
What am I doing wrong?

I have Magisk installed on my Galaxy S3, running Temasek CM13 / Android 6.0.1. Magisk manager says latest Magisk v11.1 is installed, and it's properly rooted (6:MAGISKSU (topjohnwu)). However, whenever I try to run anything that requires root, like Greenify, some features of Tasker, Titanium Backup, Solid Explorer accessing root folders, all the apps try to acquire root privileges and after a while, Magisk shows a toast saying "X is denied superuser rights." . No prompt before that, no nothing.

Magisk manager is set to have superuser access on apps and adb, although I tried apps only as well. Automatic response is set to promt, with timeout of 10 seconds. Even if I set response to Grant instead of prompt, it still automatically denies all requests. Magisk log shows all the requests that have been made, and that they've been denied.

By searching, I found this old message: https://xdaforums.com/showpost.php?p=68072551&postcount=293 . However, I haven't deleted anything from the MagiskSU GUI because there never has been anything. Just autodenying everything.

So, what to do?

Edit: And yes, I've uninstalled Magisk, first the app and then flashed the uninstall zip. Booted afterwards to make sure nothing remained, and then flashed the 11.1 zip again. Didn't help.
[Magisk] leolawliet:
So far the latest update hasn't given me issues with passing SafetyNet, also hasn't lost root at any point. I'm still getting used to it. I was on 10 for a while before giving 11.1 another chance and I'm glad everything worked out after waiting for some updates to the Manager app.
[Magisk] Ethan140310:
Nope, not working at all, still lose root after reboot
[Magisk] kantjer:
Praise Magisk
[Magisk] Pasi200896:
My original post from Magisk hide troubleshooting-thread. Hope there's help in here.

Hey people,

I've got two issues in use of Magisk.

My device is Samsung Galaxy S6 Flat (G920F) running Alexis Rom (The end of MM). Magisk v11.1 and Manager v4.2.6.

Issue 1: Since yesterday I can't pass SafetyNet any more. It only shows me "CTS profile mismatch" if i check. I didn't change anything, but somehow yesterday in the morning everything was ok, afternoon no SafetyNet pass.

Issue 2: Always after reboot and opening Magisk Manager it says there is no Magisk installed, but I flashed v11.1 already a few times. Well, it says I have to install "Magisk v11,1" - yes. With a komma. After installing this version of Magisk, it recommends me to reboot my device. Before yesterday I just denied and SafetyNet passed after turning Magisk Hide off and on again, but now this doesn't work.

Hope anyone can help me. Please feel free to ask if anything you need to know isn't mentioned.
[Magisk] :
I see. Thanks :D
[Magisk] akk29:
Try JDC Teams Optimised Lineage 14.1 - a Nougat ROM that works nicely with Magisk. Make sure to fully remove SuperSU as described in this thread and turn off USB debugging. Works perfectly on my S4 (i9505).
[Magisk] xForsa:
correct me if i'm wrong but i seem to be having a hard time to get this up and running.

you see i have this rom that i like, it's a custom rom.

Now what i want is just to be able to play pokemon go using magisk.

I made a nandroid backup,wiped everything that was wipeable. next i flashed the stock rom from samsung to get a clean bootloader.

But then it hit me, i need root to be able to run a custom recovery like twrp. so i used CF auto root. this worked like a charm and installed twrp.

after booting several times to make sure everything is right, i installed SU systemless by using the command in the terminal & flashing the zip after.

then i booted again because i read somewhere that this is needed.

Then after rebooting into recovery i installed magisk v11.1.

The problem is, everytime i start magisk manager i get 2 green checkmarks(rooted properly etc.) but the niantic check keeps loading forever.

Was this the right way to go about this or can you guys give me some tips on how to go about this?

My rom is this one: link
[Magisk] Didgeridoohan:
Your problem is SuperSU. It's not compatible with Magisk Hide which is needed to pass SafetyNet. Remove SuperSU (either through the SuperSU app or osm0si's unSU zip) and start over. When you flash Magisk it automatically installs MagiskSU (if it doesn't detect systemless SuperSU). After that you enable Magisk Hide in the manager and you should be good to go. If you can't get it working take a look in this thread for a collection of tips and tricks to try:

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

Edit: You might have to flash a clean boot image after removing SuperSU. You'll find it in your ROM.
[Magisk] AtlasRedux:
Unfortunately pointless now, unless you have a kernel that also reports your bootloader as locked.

SafetyNet is updated to demand locked bootloader AND unrooted now.

So no Pokemon Go or pay apps for me on my Z3+ :(
[Magisk] Didgeridoohan:
That update happened a while ago... And the ability to hide an unlocked bootloader has been in Magisk since v9. Are you saying it doesn't work for you?
[Magisk] Captain_Throwback:
Um, no.

Magisk hides unlocked bootloader and root, so...that's the exact point.
[Magisk] AtlasRedux:
Not on 7.1.1, I should have pointed that out.
[Magisk] xForsa:
Thankyou for your advice, i will try this out!

in the meantime i tried dirty flashing the rom, booting, installing magisk and removing the su app.

now i'm getting this. http://i67.tinypic.com/2prww2x.png

Thanks in advance.
[Magisk] gvmiguez:
I'm having an issue since yesterday, I'm not passing SafetyNet. I didnt do anything on my S7 Edge, yesterday in the morning it pass Safetynet without issues. MagiskHide is enabled, usb debugg off and rebot a lot of times. It can be an SafetyNet update?
[Magisk] Simeonico:
How do you make AdAway work with systemless hosts? I enable systemless hosts on Magisk Manager but in AdAway, systemless mode is greyed out and it still modifies the system hosts.
[Magisk] darkeyes22:
Can I flash Magisk with locked bootloader? (On rooted device and FlashFire)
[Magisk] Artim_96:
It's greyed out and ticked. So that means you can't disable it.

And no, it doesn't modify the system hosts, only the copy mounted over it

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

If you can flash it through a custom recovery, yes. I don't know if flashfire is able to flash it, you'll need to try that. But keep in mind that you might not be able because it includes MagiskSU and I don't know if it installs of you are already rooted
[Magisk] darkeyes22:
What if I will flash unSU, then Magisk?
[Magisk] Artim_96:
Then Flashfire will probably stop working before it can flash Magisk, don't now
[Magisk] darkeyes22:
What if I will sideload Magisk through fastboot?
[Magisk] Didgeridoohan:
Does Magisk Manager report MagiskSU as your root solution now? And you've enabled Magisk Hide? Also, a Magisk log could be useful.

Does the logs show that Magisk daemon has started? Have you tried disabling and then enabling Hide after a reboot?
[Magisk] jhedfors:
I currently have Magisksu/TWRP. For fun I installed FlashFire, selected UNsu zip (re-arrange to first executed), selected to backup, and FLASH. It worked just fine. I would think it should work for you. Let us know how it goes!
[Magisk] Artim_96:
...since when is it possible to flash zip files through fastboot?
[Magisk] darkeyes22:
I mean adb sideload... You can flash firmware files there, so why not Magisk?
[Magisk] Artim_96:
Could work. Too long ago that I had a phone with those capabilities...

But since when can it flash with a locked bootloader?
[Magisk] darkeyes22:
If you remember, can you tell me a name of device?
[Magisk] Simeonico:
You are right, I didn't see it was ticked because I had the brightness quite low. I thought that being systemless, it would place the modified hosts file in a different path outside of system.
[Magisk] Artim_96:
No, that's not how systmless works

---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------

Nexus/Pixel devices and probably Motorolas. Those are the only ones I know. I don't even know if OnePlus if capable of it
[Magisk] darkeyes22:
You think it can work on a Lenovo Yoga Tab 3 850L tablet? Because it quite looks like stock/pure android
[Magisk] Artim_96:
Very unlikely, but for that you'll have to search your devices forum
[Magisk] Pasi200896:
No ideas how to solve? :-/
[Magisk] Captain_Throwback:
Tried uninstaling Magisk and re-installing?
[Magisk] darkeyes22:
Issue 1- Custom ROM's usually can't pass SafetyNet. However, a phone still can bypass root detection, so you can still play Pokemon GO or use snapchat.
[Magisk] jhedfors:
Have you tried [MENTION=1162986]Captain_Throwback[/MENTION]'s suggestion?

I am curious what your result is when running this app - have you tried it?

https://play.google.com/store/apps/details?id=com.scottyab.rootbeer.sample

I am no expert, but I don't think this is quite true about custom ROMS. If you can remove all traces of root, and hide the reporting of the unlocked bootloader, you should be OK. Some apps look for other things as the Root Beer Sample app shows, that could potentially cause issues. Magisk can solve many of those things by modifying the properties the ROM reports.
[Magisk] Pasi200896:
I re-installed Magisk 2 times now, but nothing changed. I'll post some screenshots here so you can maybe look at it.

View attachment 4057844 - That's what Rootbeer says before re-installing.

View attachment 4057845 - That's what Rootbeer says after re-installing.

View attachment 4057846 - That's what Magisk Manager says if I try pass SafetyNet.

I know, not every Rom works with Magisk but that was why I installed Alexis Rom - it worked perfectly with it so I could use SafetyNet-Apps again. Like I mentioned before: it suddenly stopped working just a bit more than 1 day ago. It worked for weeks before. So no matter about other custom Roms, Alexis works.
[Magisk] jhedfors:
I forgot to mention that you need to select the Root Beer Sample app in Magisk Hide, reboot, then run it again.

Also, did you flash osmOsis's UNSU zip to make sure you removed all traces of built-in root?
[Magisk] Pasi200896:
Did the steps you told me. Rootbeer shows something different now: View attachment 4057861

But still no SafetyNet pass. Any other ideas?
[Magisk] jhedfors:
Getting close! Do you have a root management app left (e.g. PHH SuperUser apk, or other)?
[Magisk] jhedfors:
I made this module to change the release-keys as well as the selinux flag - bit I don't think it effects safetynet...
[Magisk] Pasi200896:
Done... Next screen looks like this: View attachment 4057878

But SafetyNet stays the same.. CTS Profile mismatch
[Magisk] jhedfors:
Hmmm.... Sorry, I am not sure. Hopefully someone can offer another suggestion! I wonder if the Magisk logs show anything useful.