yashsingh1/xdaforums huggingface dataset:
[Magisk] PGHammer:
That is a relatively easy fix, I just have to remember it. (Don't enable busybox in Magisk Manager, and stick to the defaults otherwise.)
[Magisk] rocky78:
what custom rom did you installed and does it come pre-rooted?

did you disabled busybox and tryed to pass it again?

give some info
[Magisk] Skulltec:
Custom ROM is pure Nexus it does not come rooted. i tried to play with the settings whiting​ magisk manager.

At first it worked untill I flashed custom kernels, now it does not even work when I flash the boot.img that comes from the ROM and reflash magisk without a custom kernel. I had this issue too at pixel ROM which also comes without root but could be fixed by flashing a original boot.img from Android factory image, however this will end into boot loop with pure Nexus. I don't know if you're familiar with pure Nexus, it is the most used custom ROM for Nexus / pixel devices :)

P.s I searched on the XDA forum and Google to find a solution without any luck :(
[Magisk] teddy0209:
Try starting fresh, full wipe...
[Magisk] Skulltec:
that's what I did. As soon I flash elemental x or Franco Kernel the safety will break. Seeing successful stories from people from both kernels is why I don't know what goes wrong
[Magisk] teddy0209:
Flash the kernel prior to flashing magisk...
[Magisk] Skulltec:
that could be the reason. I'll try when I got home. thanks ;)
[Magisk] Didgeridoohan:
Also, don't enable Magisk busybox. It'll conflict with the busybox that comes installed with Pure Nexus and it breaks Magisk Hide.
[Magisk] rocky78:
at first try what he suggested, and is that dosent work, try the one from your thread:

https://xdaforums.com/showpost.php?p=72015528&postcount=9705
[Magisk] :
Im using cm13 i want install lineage os what i do for install magisk when i install lineage os ? Please help

I only flash the magisk.zip ?
[Magisk] :
Yeah :)
[Magisk] Rush94:
Mine its unable to find magiskhidelist and safetynet fails my rom comes with v12 magisk pre installed and this issue i am facing since updated to 7.1.2 rom RR 5.8.3 , device : Condor , kernel : clarity kernel 1.7
[Magisk] kamild_:
Any chance for MagiskSU to support SELinux contexts? I'm using an app (Automate) which requires a different SELinux context to work properly, and MagiskSU doesn't seem to provide that functionality.

Thanks :)
[Magisk] fabrquila:
Similar problem with Titanium here, thank you for posting this.

ROM unofficial RR for OnePlus 2 latest build by nicesoni ash. Magisk v12. Tried almost everything. Titanium doesn't recognize root because "su" command can't be executed. Not even in a terminal app.
[Magisk] Iceman248:
For me, this begs the question of "Does Magisk have the same script that keeps current kernel mods intact that ElementalX does? Personally, I flashed Magisk first, then kernel, never had an issue.
[Magisk] yochananmarqos:
You'll probably have to ask the AutoMate developer to look into it.
[Magisk] kamild_:
That's what I have done first...

Here's the thread (and dev's response): https://groups.google.com/d/msg/automate-user/NVDxt4JnsXU/UJPUNe9bAQAJ
[Magisk] teddy0209:
That depends on the kernel format... Kernel first before magisk is still advisable, as it will work most of the time... If it fails, you just need to restore the backup created by magisk...
[Magisk] JohnHorus:
Magisk and kernel together cause Permissive, either or remains Enforcing

Kind of a weird issue, I tried searching but I couldn't figure out how to narrow it down enough to find anything relevant.

I'm using Phoenix AOSP Extended and RenderBroken's EAS kernel on the Oneplus 3, and I'm having a weird issue with SELinux. The ROM is enforcing by default, and if I flash just the kernel, or just Magisk (12), it runs in Enforcing as normal. However, if I flash both Magisk and the kernel (in either order), SELinux boots in permissive mode. I tried putting scripts in init.d, su.d, and post-fs-data.d to set it to enforcing, but none seemed to run. I finally noticed the service.d directory, and the script seemed to run from there and cause SELinux to switch to enforcing at boot.

All I've been able to gather from this is that whatever is unexpectedly causing SELinux to switch to permissive is running after post-fs-data scripts, but before service scripts, as I see on the first page of this thread that those two run at different times. I don't really know what to make of it, though.

I've been talking to the Kernel's developer and he didn't seem to know why this would be. He was just finishing a big release, so I said I would clean flash and try with that. I just finished doing so, and it's still happening, so I thought I should look into it further myself as well as bugging him about it.
[Magisk] DodoGTA:
That kernel sets SELinux to permissive
[Magisk] JohnHorus:
Do you have any idea why it's only doing it when Magisk is installed? My only guess would be that Magisk is running some scripts that the kernel isn't. Do you have any idea what directories Magisk would run scripts from, aside from init.d and su.d?
[Magisk] DodoGTA:
What kernel are you using?
[Magisk] DodoGTA:
Your kernel tries to set SELinux to Permissive: https://github.com/RenderBroken/RenderKernel-AnyKernel2/blob/rk-op3-los-n/tools/ak2-core.sh#L111
[Magisk] QQRaju:
Is there a magisk module that can enable onscreen navigation buttons and disable the hardware buttons..?
[Magisk] Kokochitnaywinaung:
Root my device ,my 3th party app can't download

Unknown source can't open,setting unfortunery error
[Magisk] Didgeridoohan:
If it can be done with build.prop edits and by replacing files in /system with edited files you could easily make one. Take a look in the All-In-One wiki for details.

Details, details, details... So many more details needed...
[Magisk] Artim_96:
It can. For enabling on screen keys you only need to add one line to the build.prop, for disabling the hardware ones you will need to replace a few files in /system which you edited first... If you're lucky. It should work, bit at lest in my Samsung I can only disable the home key and the soft keys back light, no idea why
[Magisk] enzoevo:
Version​ 12.0 killed my Dots & Co game. It crashes or won't load. If I go back to previous version it runs without incident. Anyone having similar issues?
[Magisk] Didgeridoohan:
It's possible that the game looks for certain values in ro.build.type or ro.build.tags and don't run if the "wrong" values are found. Magisk v11.5/v11.6 changed these prop values by default if Magisk Hide was enabled. The usual suspects is if your ROM has ro.build.tags set to "test-keys". Many apps wants this value to be "release-keys".

Of course, all of this depends on if you have a custom ROM and have Magisk Hide enabled. I've no idea with the amount of information at hand, so I'm just guessing...
[Magisk] enzoevo:
Thanks. Yes I have hide enabled. Running PuerNexys and I haven't updated to latest version yet, which uses release keys. The game starts up and crashes at different points. Never the same.
[Magisk] rignfool:
This sounds like user error somewhere...

My guess would be to look for a new app you installed... From somewhere shady...

Or the ever popular 'tasker script gone awry'... Though I doubt that...
[Magisk] cesar_9046:
The version 12.0 drain my Battery!!
[Magisk] RandomPooka:
Without log files and/or data from something like Better Battery Stats, you can't and won't get any help from anyone.
[Magisk] RJASSI21:
I am using Xperia z2 Marshmallow with exiztenz rom which is already rooted with supersu app just wondering if I flash this will I then have systemless root or do I have to delete my current root some how?
[Magisk] godstriker8:
I have a OnePlus X on stock Oxygen 2.2.1 (their equivalent to Android 5.1.1).

I have a problem passing SafetyNet. It suceeded in the Magisk manager app before I installed Magisk, so I'm confident that the ROM isn't the issue.

All I did was install Magisk v12 in recovery, boot up in order to activate Magiskhide and rebooted again, and now SafetyNet claims I have a CTS profile mismatch.

After enabling verbose logging, I saw that the MagiskHide didn't unmount anything, it only stopped at:

"MagiskHide: com.google.android.gms.unstable"

To fix this, I followed the guide's (https://xdaforums.com/showpost.php?p=71154562&postcount=4) instructions: I uninstalled Busybox, checked that logcat support works using a terminal app, and still nothing.

Any other way to fix this?
[Magisk] ammar18:
What fix? It appears to be no errors at all...

If you are talking about the CTS Mismatch, enable Magisk Hide.
[Magisk] enzoevo:
LOL. I installed nothing but the game after a fresh install of the ROM and magisk. This isn't my first rodeo, some change in magisk is affecting the game. I could care less about the game. I'm just giving feedback to maybe help improve magisk. [emoji111]
[Magisk] acestars:
i have some questions

1. can i create module that run script at post-fs mode?

2. how to to get module relative dir from script in $modid/system/bin without hard-coded it?
[Magisk] davejimson:
Thank you, anyway what is magisk hide
[Magisk] enzoevo:
Try rebooting after enabling. Check the log to see that it actually turned on.
[Magisk] ammar18:
It hides magisk, superuser, and other things that can trip SafetyNet, or apps that won't work WITH root.
[Magisk] Artim_96:
1. You can but it's recommended only if needed. In general you should use the services .sh

2. You don't need to take care about any directories. Best is to just make a module from the template and write your script into to services.sh

---------- Post added at 01:03 AM ---------- Previous post was at 01:01 AM ----------

Well, it hides Magisk modules, but only SuperUser in terms of MagiskSU. Otherwise someone could think phh's SuperUser is meant and I don't think it's still supported
[Magisk] acestars:
so how i need to do if i want to run in post-fs mode? is it enough if i create post-fs.sh in common dir?

i want to create script that can be run by user manually, the script can access module dir without hardcoded it, how to do it?

Thanks
[Magisk] teddy0209:
You have to remove existing root first... You'll probably need a clean boot.img...
[Magisk] Didgeridoohan:
There's also a section right there about making sure you haven't turned off Logger buffer size in developer settings. Have you checked that?

Could you run the following two commands in a terminal app (as su) and report back with any errors:

sh /magisk/.core/magiskhide/disable
sh /magisk/.core/magiskhide/enable
[Magisk] Rush94:
Dude those code in mine fails i am unable to hide ? Its not able to find magisk/hide list and when i navigate to the folder it doesn't have that file more over all my files have only read only mode no write access how do i change that

Here's the log

My device Condor

Os: RR 5.8.3

Android: v7.1.2

Kernel: Clarity kernel Rebkrn v1.7

Magisk : v12

Magisk manager : v4.3.3
[Magisk] Didgeridoohan:
Yes, like I told you in the Pokemon thread, you've got issues with read-write.

You can check with the mount command in terminal for what partition is messing with you (/magisk, /data, I don't know). They should be shown as rw.

I don't have the commands in my head to remount a partition rw and don't feel like doing your research for you at the moment. Google is your friend (or possibly some other user)...
[Magisk] Mysterion1:
Hey guys,

I have installed latest magisk on my Nexus 7 (2013) with AOSP Android 7.1.2. Magisk indicates a proper installation and root.

Here's the issue I'm facing:

After the (very short) installation of modules I reboot my device, but no modules have been installed...

I already reflashed the rom and magisk, but the problem remains.

Magisk works fine on my One M9, so I haven't done anything wrong on my N7.

Any ideas on how to fix this?
[Magisk] Artim_96:
I don't think that's possible
[Magisk] Rush94:
I tried solid explorer with magisk root but failed
[Magisk] Magissia:
Greetings, is it possible to mount something only for one specific application ?

Is it possible to mount read only a folder inside data partition ?

I would like to lie to an application to make it look like nothing exist at some path.

I usually did it using xprivacy but this project is not maintained anymore and doesn't work properly on Android 6.
[Magisk] RJASSI21:
Hmm OK I have ways of removing it im on locked bootloader so I can only flash stock kernels.
[Magisk] rocky78:
i don't know solid explorer, but in root explorer

when you open the app. you can go to root folder, and then you can switch to read/write root folder.

mybe that will help.
[Magisk] teddy0209:
If you have locked bootloader then it won't work for you as magisk modifies the kernel...
[Magisk] RJASSI21:
Ah ok thanks for that then will just continue using it on my z4 tablet then that has unlocked bl. Damn the UK for its carriers and keeping some Xperias permanently locked ?.
[Magisk] teddy0209:
Xperias are one of the most dev friendly devices with official unlocking... Just don't buy from a carrier... ???
[Magisk] kyzn:
Try tapping each colored outline until you see them replaced with a check mark. Sometimes that's what makes it work. I feel like the colored outlines are just placeholders of what permissions you should grant it in /root.

And by default, solid explorer grants you read/write when you give it root permission.
[Magisk] Rush94:
After click and saying apply i got that error. You see in the screenshot
[Magisk] Rush94:
Tried with root explorer but failed too
[Magisk] harrez:
Magisk manager forced closed when downloading module.

---------- Post added at 10:42 PM ---------- Previous post was at 10:02 PM ----------

hello ! , i encountered the same problem . What i did was update to the latest magisk manager via playstore and the problem solved
[Magisk] Artim_96:
No, that's not how Android works.
[Magisk] Magissia:
That's not how android works but by default each process has it's own mount tree, that caused problems because apps remounting as read/write for other apps wouldn't work anymore, and mountfolder had to update to work at some point due to that mountspace separation that is present by default.
[Magisk] Xephyrex:
Psuedo-enforcing mode?

I'm using a ROM which requires the kernel to be permissive, as such I can't actually change to enforcing. I saw on the Magisk thread that there is a feature that allows you to be on permissive but Magisk would automatically mask it so the system sees enforcing, allowing you to pass safety net, however, I boot up Magisk manager in this permissive ROM, along with Magisk hide enabled but safety net still fails presumably because the kernel is permissive. Why does it state in the thread that you should still appear as enforcing even if the ROM is permissive, since it isn't working for my ROM and safety net doesn't pass.

Can someone shed some light on this issue?:confused:

---------- Post added at 03:05 PM ---------- Previous post was at 03:01 PM ----------

To be clear, I have no way of setting the kernel to Enforcing as the ROM requires permissive. Is there anyway to pass safety net for a permissive ROM?

P.s my device is the Galaxy Note 4 N910C running the Nemesis N7 port (latest update)
[Magisk] leolawliet:
Upon updating the app earlier today, it's starting to force close again like the other day. Please fix..

Edit: I tried a bunch of different things but uninstalling custom overlays did the trick. If anyone experienced force closing with the new update while using a Substratum theme that might be skinning over Magisk Manager (such as Flux) I suggest disabling the theme and seeing if there's an update for it, otherwise just disable it and don't mess with it till the issue gets resolved.
[Magisk] culiacanazo:
Not only uk, us and mx too!
[Magisk] FlyGuyPanPeter:
I am using autoroot Chainfire which installed SuperSU 2.74 for me.

I have flashed SUhide through Flashfire but it didnt worked as expected.

I decided to Flash Magisk through Flashfire and all went OK.

The only thing, I can't pass SafetyNet check, it gives the error CTS Profile mismatch and I have tried many things from other users but still it doesnt work.

Help me get Magisk Hide working. I think the problem is that I dont use MagiskSU but SuperSU. How can I switch easy without custom recovery or wipe data? I have encrypted my phone thats why custom recovery isnt a option. I can only flash through Flashfire.

Here is the log:

Here you see the current status:

[IMG="status"]http://www0.xup.in/exec/ximg.php?fid=11124335[/IMG]
[Magisk] teddy0209:
You have already read about it, magisk does mask selinux state... You have probably other things triggering SN... Check the tips and tricks thread...

---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------

Remove supersu first before you flash magisk... If you only can flash using flashfire, then you're out of luck as it needs root...
[Magisk] Didgeridoohan:
You probably have something else causing SafetyNet to fail. You can check the logs if pseudo-enforcing is kicking in. For more things to look for when troubleshooting Magisk Hide, take a look in the link in my signature.

And don't forget to provide logs if you need further help after checking out that link.

Yes, the reason you can't pass SafetyNet is SuperSU.

To use Flashfire, you'll need root. More precisely SuperSU or MagiskSU. If you have systemless SuperSU installed, Magisk won't install MagiskSU. If you remove SuperSU, Flashfire won't work and you'll need a custom recovery to install Magisk.

Quite the conundrum...

If you'd had a system installed SuperSU, the Magisk installation script would try to remove it and install MagiskSU instead.

Good luck...
[Magisk] culiacanazo:
Or you could use ff powered by SuperSU to unsu, flash boot, and then magisk in one sitting.

Thing is, if you're one of the "lucky ones" to reboot just to find "magisk installed - not root available" you'll pretty much be "ducked" (consider that last word initialed with the letter to its right in a QWERTY)
[Magisk] FlyGuyPanPeter:
Yes I think its mission impossible. I dont want to lose my encryption so I cant use custom recovery so I can't flash Magisk so I cant use Magisk Hide :(

Any alternative for Hide Root? My security patches are from september 2016 but SUHIDE doesnt seem te work... I have it succesfull installed and the packagename blacklisted but it doesnt hide the root.
[Magisk] rignfool:
You have some supolicy or sepolicy error...

You will have to take it to your kernel dev, they need to modify their SELinux policy to work with magisk
[Magisk] DodoGTA:
What type of encryption do you want to keep?
[Magisk] FlyGuyPanPeter:
Full disk encryption.

1. I first encrypted the phone

2. Autoroot Chainfire SuperSU

3. FlashFire

4. Flashed Magisk
[Magisk] dahawthorne:
I'm confused too. My Nexus 6 has been encrypted for ages, I've installed different ROMs many times and TWRP has never quibbled at any time. It asks for my device unlock key, that's all.

Edit: I'm seeing time after time after time "I installed SuperSU and then Magisk and I can't understand why Magisk doesn't work". Does nobody actually do any reading before posting this same question over and over again?
[Magisk] FlyGuyPanPeter:
Ooh that's very strange... I use TWRP 3.0.0.2 for SM-A310F from ashyx on this forum and it doesn't ask for unlock key... it just says 0mb internal storage.
[Magisk] Artim_96:
Try flashing Magisk through the manger and set keep force encryption
[Magisk] dahawthorne:
I don't see a mention of your device unless I've missed it. There is a new TWRP 3.1 for many devices. Are you certain that your device is encrypted? In Security under "Encrypt device" it says "encrypted"? If TWRP is able to work on your device without a key...
[Magisk] FlyGuyPanPeter:
It doesn't says its encrypted because I allready did it... And now it says: Secure startup (look screen)

Screen: http://www0.xup.in/exec/ximg.php?fid=78460509

And TWRP is not made for sm a310f so member ashyx made it work for a310f and 3.0.0.2 is the latest version

---------- Post added at 08:19 PM ---------- Previous post was at 08:17 PM ----------

I tried this before but I got somehow installation error (after unzipping phase). But I dont remember if I checked force encryption. If I want to try it now I first need uninstall Magisk and then try it again right?
[Magisk] dahawthorne:
I don't recognise that screen, and it doesn't show any encryption. The fact that TWRP works without a key makes me believe that you have no encryption - how can TWRP work on your device without a key if the contents are encrypted? That makes no sense to me.
[Magisk] FlyGuyPanPeter:
I flashed TWRP with ODIN. TWRP is working but I can't use the advanced features like install/flashing etc because my device is encrypted it shows 0mb internal storage, so TWRP is useless to me.
[Magisk] Artim_96:
Yes, better try with a fresh start. But I don't know where that actually lies in, maybe you only need to flash your stock boot.img to re-enable force encryption. Then flash it with that enabled, if it doesn't work we need the logs
[Magisk] FlyGuyPanPeter:
So this is what I did:

1. Opened Magisk Manager and pressed uninstall which rebooted my phone

2. Opened again Magisk Manager seeing still the status green that Magisk v12.0 is still installed

3. So I just decided to press Download and Install and check Force encryption ON (thinking maybe it will just overwrite the current install)

4. Anyways this time the install worked without installation error and it rebooted again my phone

5. But it still doesnt pass SafetyNet...
[Magisk] Artim_96:
Passing SN shouldn't have anything to do with encryption... Of Google didn't just change it again. But passing it is practically a science itself. If anyone could tell what needs to be done to pass that would be great, but it's mostly just trial and error and maybe you just can't pass it
[Magisk] FlyGuyPanPeter:
Magisk says before put Magisk Hide ON that it doesnt support Magisk Hide work together with SuperSU so that's why I believe I need MagiskSU, but in order to get MagiskSU I need uninstall SuperSU and then I lose my root and then flash Magisk through TWRP but this is again impossible because TWRP can't work with encrypted phone, you now see my problem?

I also read many other people issues with pass SN, I disabled USB debug etc and it don't works for me.

Are there any alternatives for Hide Root?

I have installed SUHIDE and I have read this works if your phone have security patch before november 2016, I am using patch from september 2016 and it doesn't works. SUHIDE it self is succesfullt installed and I can add packagename to the list etc but it doesn't hide the root for the app.

Any alternatives or any fixes?
[Magisk] Artim_96:
Ah, so you have a Samsung phone. Well, normally you can decrypt the phone by wiping /data. Then stay in TWRP and try to flash Magisk which should work now. That should break the forced encryption then and you'll have no problems with TWRP anymore
[Magisk] godstriker8:
I never touched logger buffer size, still says 256.

But I think I did get an error running those commands, not really sure what it means though:

u0_a98@OnePlus:/ $ sh /magisk/.core/magiskhide/disable

MagiskHide: Stopping MagiskHide daemon

/magisk/.core/magiskhide/disable[16]: can't create /cache/magisk.log: Permission denied

/magisk/.core/magiskhide/disable[20]: kill: 1387: Operation not permitted

MagiskHide: Killing com.google.android.gms.unstable

/magisk/.core/magiskhide/disable[27]: can't create /cache/magisk.log: Permission denied

MagiskHide: Killing com.nintendo.zaba

/magisk/.core/magiskhide/disable[27]: can't create /cache/magisk.log: Permission denied

MagiskHide: Killing com.snapchat.android

/magisk/.core/magiskhide/disable[27]: can't create /cache/magisk.log: Permission denied

1|u0_a98@OnePlus:/ $ sh /magisk/.core/magiskhide/enable

u0_a98@OnePlus:/ $
[Magisk] DodoGTA:
You ran those commands without root permission