yashsingh1/xdaforums huggingface dataset:
[Magisk] GtrCraft:
I also had to disable the build type part because I need developer options
[Magisk] Didgeridoohan:
Ah... That's what caused that for some users? Good to know. Thank you.
[Magisk] tamer7:
Great. Now I'm trying to use Magisk 11.6 again on Phronesis N7 port ROM v5.1 on Samsung Note 3 International (SM-N9005).

First I remove the pre-installed system-mode SuperSU and reboot. Check with "Safetynet Helper sample" app, basic integrity check OK, but CTS profile mismatch, because SELinux is set to Permissive. I install Magisk 11.6 (which installs MagiskSU properly) and latest Magisk manager from playstore, make sure MagiskHide is enabled, but the check in MagiskHide itself gives CTS Profile Mismatch. "Safetynet Helper Sample" no longer passes even basic integrity check, even after I add the app in the MagiskHide list.

With SuperSU + RootSwitch-1.3.3.2.apk, safetynet passes both basic integrity and CTS profile match. But "S-Pushtan" banking app still claims it detects root (even after setting ro.build.selinux=0 in /system/build.prop and rebooting).. Hence why I'm still trying to get Magisk working here.

Any ideas?
[Magisk] aeroxy:
Okay thx for letting me know...
[Magisk] steveo17:
same here

hoping this can be updated to allow root to work soon
[Magisk] Didgeridoohan:
If it isn't working out of the box, I wouldn't hold my breath waiting for Android O (8.0?) support...
[Magisk] jhedfors:
Interesting, I have always been able to enable developer options, regardless of build type. Perhaps you are talking about a specific function?
[Magisk] GtrCraft:
No some roms have developer options enabled by default. But user build types should not have it so it removes it
[Magisk] jhedfors:
So, tapping build number 7 times would not work in those cases?
[Magisk] xUniversal:
good tip, with 11.1 I have moved a bit further - now it says rooted, but no root permission. I tried several different Magisk Manager versions. Any tips?

EDIT: Added the recovery.log for Magisk v11.6
[Magisk] Artim_96:
Guess what genius: O is not supported and I highly doubt that Google will ever certify a developer preview/beta. Especially not on the first release. The beta is not meant to be used on productivity devices
[Magisk] Telperion:
[MENTION=6036788]SilverSix[/MENTION] [MENTION=6051103]Tr4il[/MENTION]

I'm having similar but not entirely similar issues on an XT1042. I've tried unrooted versions of the custom ROM, pre-rooted versions, etc, and I can't get root with MagiskSU and there are a host of ramdisk errors when flashing the zip. I can get systemless SuperSU running but because of the errors I can't get a safetynet pass.
[Magisk] Captain_Throwback:
And you already posted a log and your boot.img to Github so this can be researched?
[Magisk] medes22:
Mates i do these steps everytime there's a update for Magisk, kernel etc.

Flash kernel

Flash unsu zip

Flash latest Magisk

And all ticks are always green
[Magisk] Telperion:
Not yet, it was late at night and I wanted to sleep. I have another one to try it on so I'll properly log it.
[Magisk] culiacanazo:
Huh? Who? Where? What? How? But! But! But! But... Why?!
[Magisk] steliosstyl:
Hey guys I have been using magisk for a couple of months now without problems but today after updating it to the latest version android pay fails to work. It opens up but when trying to pay it just says to unroot the device.
[Magisk] Didgeridoohan:
OMG! NOOOO!

Have you verified that Magisk Hide has properly started after booting? Look in the log. If it doesn't say something about MagiskHide daemon starting and killing processes, it hasn't. Fix by toggling Hide off and on in settings.
[Magisk] steliosstyl:
Yep toggled on and off magisk hide then did a restart and that solved it! Thanks
[Magisk] Kyuubi10:
Hey guys, just out of curiosity what happens if a module isn't on the correct template version?

E.g. Magisk version 11.6, but template version 1 or 2.
[Magisk] ayekhine:
I am currently flashing my Nexus 5 with LOS14.1 with Magisk 11.6 and it passes safetynet when the device starts. But after I install custom kernel (Both EX and Franco), safetynet failed. Is it normal? What am I doing wrong?

Step I did - wipe data > flash LOS > flash Gapp > flash Magisk 11.6 > boot > setup > safetynet passed > flash kernel > boot > safetynet failed

What I am trying to achieve - LOS with root passing safetynet on Nexus 5. Thank in advance.
[Magisk] tavocabe:
https://youtu.be/eFxQ_qLrKXo

I know it's possible, don't know how tho
[Magisk] Artim_96:
It won't show up in the download section and might become incompatible someday
[Magisk] Didgeridoohan:
Try changing the order and see if that makes any difference. Kernel before Magisk.
[Magisk] ThePurpleK:
Is there a technical reason for why Xposed can't be unmounted? Is it to do with app_process? I'm just curious.
[Magisk] sansnil:
There's a dedicated thread on the topic of Magisk and AP with lots of great info (yes you can add cards and successfully make transactions with AP and Xposed enabled). Let's not regurgitate here.

http://xdaforums.com/android/software/magisk-phh-s-superuser-android-pay-t3435921
[Magisk] Iceyogurt:
According to the recovery log, I find the Magisk-module-template.zip(2016.8.22) can't recognize directory names with spaces. Hope you improve this and thanks for your effort on Magisk.

*******************************

BetterBatteryStats_xda_2.2.0RC1

*******************************

******************************

Powered by Magisk (@topjohnwu)

******************************

- Mounting /system(ro), /vendor(ro), /data, /cache

- /data/magisk.img detected!

/data/magisk.img: 120/4096 files (0.0% non-contiguous), 7732/16384 blocks

- Mounting /data/magisk.img to /magisk

mknod: /dev/block/loop0: File exists

- Copying files

unzip: can't open /sdcard/Download/flashable/Magisk/Magisk[.zip]

- Setting permissions

- Unmounting partitions

In fact, the full directory of the custom module is /sdcard/Download/flashable/Magisk/Magisk Module/*. After I deleted the spaces in the directory names, the module worked well.
[Magisk] Rahh1112:
[BUG REPORT]

Touch not working after magisk flashing (confirmed that it's not because of any other zip)

Flashed ROM > First boot ok > Recovery > Magisk Flash > Touch not working anymore

ROM Version: CyanogenMod 13 USER (self compiled, I can link sources too if wanted), compiled with ArchiDroid Optimizations (https://github.com/ArchiDroid/android_build/commit/f9b983e8e11624b48ae575da206f1baf6979772c), compiled with DespairFactor toolchain too...if this makes a difference.. also, cache is in f2fs

Device: moto x 2013 (ghost)

magisk.log:

Magisk post-fs mode running...

Magisk post-fs-data mode running...

Preparing bind mounts

Bind mount dummy system

Bind mount module items

Bind mount system mirror

Mount: /system

Bind mount mirror items

Enabling systemless hosts file support

Mount: /magisk/.core/hosts

Magisk late_start service mode running...
[Magisk] aaron804:
Thanks so much for the info Captain_Throwback. However please pardon my ignorance...

1. I'm not sure that net.tethering.noprovisioning=true needs to be in build.prop however historically on marshmallow that is where it was said to be put, and it worked.

2. "It should be as simple as adding a folder called "tethering" to the /magisk folder"

Do you mean add a folder "tethering" to /cache/magisk/ ....... "/cache/magisk/tethering/" ??

3. "adding an auto_mount file" Not sure what you mean, nor how to do that.

4. "a module.prop" Again I don't understand.

5. "and a post-fs-data.sh with the filling content:

#!/system/bin/sh

setprop net.tethering.noprovisioning true

"

6. In regards to 5. I assume I can just use notepad.exe to create a file named post-fs-data.sh with the contents:

#!/system/bin/sh

setprop net.tethering.noprovisioning=true

did you accidentally omit the "=" noprovisioning=true or is that now by design?

7. Lastly how would I run getprop net.tethering.noprovisioning and seeing what it returns.

So sorry I'm asking all these likely simple and obvious questions. I have searched for the answers but haven't found anything straight forward enough for me to wrap my head around it. I really appreciate the hand holding.

Thank you very much!!
[Magisk] smohanv:
Which supersu are you using. Magisk SuperSu or Phh's.
[Magisk] JudgeDread11:
1. Try and see what happens. If the mod works you should be able to see your line when you open build.prop. if your line is there but it doesn't work then there should be an other methods.

2. Use the module template and follow the steps in there. If it's all new is a bit confusing when you start (it was for me) but with some experimenting things will start to make sense.

3. auto_mount file is an empty file to let magisk know it needs to use magisk mounts for the mod. (See op)

4. Module.prop is a file containing info about your mod, for future compatibility with the coming magisk mod manager. (See the op and the mod template)

5. Post-fs-data.sh is a script file that will run your script to make the change in the build.prop. (see module template)

6. Notepad++ is a great tool to edit scripts

7. I think you can run the getprop command from a terminal emulator on your device or using adb when you're connected to your PC.
[Magisk] Captain_Throwback:
So then you'll have to try this method and see if it works.

No. The /magisk folder is in the root of the file system. There isn't a magisk folder in /cache by default, and you only need one there if you're using a "cache mod," which you shouldn't need (and I'm not describing here).

Just create an empty/blank file with that name. Any Android root file explorer should be able to do that. You can even create a new document on your PC if you want - that'll also work. Just make sure it doesn't have a file extension.

I explained that here.

Don't use notepad.exe. Download Notepad++ instead, and make sure the EOL Conversion is set to UNIX/OSX and NOT Windows (the option should be in the "Edit" menu). That probably doesn't make sense to you, but once you look in the program, it should.

The setprop command doesn't use an equal sign. Just copy/paste the script as written, and make sure the EOL Conversion is set properly as I indicated above.

By running that command in a Terminal Emulator in Android or from an adb shell.

Well I wouldn't normally be this helpful, but you caught me on a helpful day, I guess. I'd read through the opening posts in this thread a bit more to try and understand how Magisk works a bit more, so you understand how what I told you fits with it. The update-binary in the Mod template also has some helpful information.
[Magisk] aaron804:
THANK YOU!

---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------

THANK YOU for the hand holding!!!! I really appreciate it. Now I believe I understand the basics well enough not to bother you any more. thanks again!
[Magisk] AndroidGee209:
ive tried Magisk on my Note 3 with both AOSP and TW and it works completely fine except that the camera does not work on either rom after flashing Magisk... love your work though!
[Magisk] nimkip:
Apparently not. I was going off a post from the dev earlier in the thread that said magisk wouldn't touch the system hosts file. I interpreted that to mean that if I checked system/etc/hosts it would appear unmodified. My mistake, carry on.
[Magisk] Artim_96:
I doubt that can be fixed by him, it's a restriction deep inside of Linux because a space means the end of a command. The only thing that can be done would be to manually put a "\" in front of the space for all I know. So instead of /magisk/project name it would be /magisk/project\ name. At least that is recommended for desktop Linux to use for commands when you really want to keep the space.
[Magisk] Fedroid:
Nobody knows why the root toggle doesn't work?

My phone is a Huawei P8 Lite.

Is systemless rooted with the Magisk version of phh superuser.

Any clue?
[Magisk] AndroidGee209:
Do you mind me asking if you have the phh''s superuser app installed?
[Magisk] Fedroid:
Yes i have
[Magisk] siren_shadows:
Is there any way that this could just become part of SuperSU for simplicity purposes? I know it would save a lot of people headaches if it was just a default part of systemless root
[Magisk] Artim_96:
In theory, yes. But I think it would be just too bloated.
[Magisk] N00dle:
Try flashing your system image along with the boot image and then the other install steps. You shouldn't lose data and it will be more of a fresh install. Then work from there.

I had the same issue on my Nexus 5x but I may have done a step indirectly and this helped fix it.
[Magisk] JudgeDread11:
I don't think that will happen. For Android pay to work phh's superuser is needed, it apparently didn't work with SuperSU (I don't use Android pay)

Also the intention is to create a universal interface which can be used by all devs for all mods. Also didn't chainfire announce that SuperSU will be taken over by some company.

It would take the universal out of the universal systemless interface, title of this thread.
[Magisk] siren_shadows:
SuperSU works with Android pay for me
[Magisk] biggdevon:
Successfully flashed/installed v11.6/v4.2.7 on Note 5 N920T.

TRWP = arter97's Custom 3.0.2-0

Kernel = arter97's v22 3.10

Stock 6.0.1 PK6

USB Debugging is on

SafetyNet Passes (all true)
[Magisk] ayekhine:
I have tried below

wipe data > flash LOS > flash Gapp > flash Magisk 11.6 > boot > setup > safetynet passed > flash kernel > boot > safetynet failed

wipe data > flash LOS > flash Gapp > flash kernel > flash magisk 11.6 > boot > setup > safetynet failed.

wipe data > flash LOS > flash Gapp > flash magisk 11.6 > flash kernel > boot > setup > safetynet failed.
[Magisk] Kyuubi10:
What if installed directly via recovery... Will it install successfully?
[Magisk] Didgeridoohan:
In that case I believe the solution is simple... Don't flash a custom kernel. :)

Might be some incompatibility between the kernel and LOS.
[Magisk] ayekhine:
Thank you for quick reply, It does seem to work this time.

Wipe data > Flash LOS > Flash Gapp > Flash Magisk > reboot > setup > install magisk manager > safetynet passed > install FKUpdater > Give root access > Flash kenal > reboot > safetynet passed.
[Magisk] Didgeridoohan:
Ah... Those times that SafetyNet wasn't passing, did you verify that Magisk Hide had actually started on boot? You can see it in the logs. Sometimes it doesn't and you'll need to toggle Hide off and on in settings to restart it.
[Magisk] Artim_96:
As long as it's compressions, yes. If it will run is s different question. It might but it also might not, depending on future changes
[Magisk] deepu458:
Friends i am using this magisk form past 3 weeks or so on RR N (bacon). Today i have flashed the Yashdsaraf (https://github.com/yashdsaraf/bb-bot/releases/tag/v1.26.2-YDS-53)

busybox and then enabled the Enable Busybox under settings. So when i use an app called rootbeer sample for detecting root, busybox, selinux,etc it said that it detected the Busybox under System/xbin/busybox, so is there any way i can hide this like the root we do using Magisk Manager app.
[Magisk] Captain_Throwback:
There's no reason to flash a busybox zip (especially not that one). Just toggle the busybox option in Magisk. Also, busybox doesn't typically cause an issue with apps, so it doesn't matter if it was detected.
[Magisk] JonathanRAZ:
Will give it a try on dqa2
[Magisk] Didgeridoohan:
Unless you use the built-in Busybox (enabled by toggling it in Manager settings) or a Busybox Magisk module, Magisk can't hide it.

Uninstall the Busybox you flashed and just enable the built-in Magisk Busybox.

Edit: Holy Moly I'm slow sometimes. Note to self, finish writing the answer before doing other things. :)
[Magisk] deepu458:
I really thank ur effort to help me here. The reason why i installed the above Busybox was whenever i select Enable Busybox it shows as enabled but after reboot it is getting disabled back and in terminal for busybox command it didnt find any thing.

But i haven't tried the Busybox magisk module yet, so u mean uninstall means just dirty flash rom and gapps and magisk etc?
[Magisk] danielcr12:
Root is not sticking, it disappear after a while.

How can I provide logs?
[Magisk] jasio2k:
Same here on htc one m8 RR 5.8.2 and It was happening with 11.1 as well, uninstall install and over and overagain fix the issuu but how and why ? it is a good question
[Magisk] Artim_96:
1. Turn off busybox in Manager, seems to be a problem since v11

2. In that case you would need to get the logs from /cache but since you have lost root you'll need to boot into TWRP for that. Get the magisk.log from there and attach it here
[Magisk] smohanv:
I am planning to buy LG G5 original version. Does this magisk root works on this phone once I unlock bootloader and flashed twrp. Thanks.
[Magisk] danielcr12:
There is no such options un magisk.
[Magisk] Artim_96:
It will only show up when root is active, so at least make a reboot, otherwise make a clean install
[Magisk] Nazariyhuhalo:
Samsung pass still detects root even with magisk

is there a way I can hide root from it:confused:
[Magisk] LazerL0rd:
MagiskHide?
[Magisk] MaxPresi:
Whenever I activate magiskhide and reboot the phone, all apps that use webview (Steam, for example) give FC.

03-22 20:45:02.638 I/ActivityManager(2520): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.valvesoftware.android.steam.community/.activity.MainActivity (has extras)} from uid 10101 on display 0
03-22 20:45:02.700 I/ActivityManager(2520): Start proc 7708:com.valvesoftware.android.steam.community/u0a79 for activity com.valvesoftware.android.steam.community/.activity.MainActivity
03-22 20:45:02.778 W/System (7708): ClassLoader referenced unknown path: /data/app/com.valvesoftware.android.steam.community-1/lib/arm64
03-22 20:45:03.830 E/WebViewFactory(7708):	at com.valvesoftware.android.steam.community.SteamCommunityApplication.onCreate(SteamCommunityApplication.java:71)
03-22 20:45:03.834 E/crash (7708): APPNAME: com.valvesoftware.android.steam.community
03-22 20:45:03.834 E/crash (7708): java.lang.RuntimeException: Unable to create application com.valvesoftware.android.steam.community.SteamCommunityApplication: android.util.AndroidRuntimeException: android.webkit.WebViewFactory$MissingWebViewPackageException: [U]Failed to load WebView provider: No WebView installed[/U]
03-22 20:45:03.834 E/crash (7708):	at com.valvesoftware.android.steam.community.SteamCommunityApplication.onCreate(SteamCommunityApplication.java:71)
03-22 20:45:09.244 E/AndroidRuntime(7708): Process: com.valvesoftware.android.steam.community, PID: 7708
03-22 20:45:09.244 E/AndroidRuntime(7708): java.lang.RuntimeException: Unable to create application com.valvesoftware.android.steam.community.SteamCommunityApplication: android.util.AndroidRuntimeException: android.webkit.WebViewFactory$MissingWebViewPackageException: [U]Failed to load WebView provider: No WebView installed[/U]
03-22 20:45:09.244 E/AndroidRuntime(7708):	at com.valvesoftware.android.steam.community.SteamCommunityApplication.onCreate(SteamCommunityApplication.java:71)
03-22 20:45:09.248 W/ActivityManager(2520): Force finishing activity com.valvesoftware.android.steam.community/.activity.MainActivity
03-22 20:45:09.759 W/ActivityManager(2520): Activity pause timeout for ActivityRecord{3d3a000 u0 com.valvesoftware.android.steam.community/.activity.MainActivity t52 f}
03-22 20:45:09.769 I/WindowManager(2520): Failed to capture screenshot of Token{bdb5039 ActivityRecord{3d3a000 u0 com.valvesoftware.android.steam.community/.activity.MainActivity t52 f}} appWin=Window{1db1756 u0 Starting com.valvesoftware.android.steam.community} drawState=4
03-22 20:45:10.838 W/ActivityManager(2520): Force finishing activity com.valvesoftware.android.steam.community/.activity.MainActivity
03-22 20:45:10.839 I/ActivityManager(2520): Killing 7708:com.valvesoftware.android.steam.community/u0a79 (adj 900): crash
[Magisk] Nazariyhuhalo:
I tried it it doesn't work it still says root detected
[Magisk] LazerL0rd:
Hmm, you on latest Magisk? If still fails and you have no system mods you'll have to post a log and hope someone fixes it. Sorry mate.
[Magisk] Nazariyhuhalo:
Cool:(
[Magisk] Twinfail:
What's wrong with Magisk?

Latest Magisk Version v11.6

Installed Magisk Version v11.6

Magisk v11.6 disabled

Rooted but no root permissions, not allowed?
[Magisk] str8str:
I flashed the viper 4 Android module it seems to be working but the apk to control it is no where to be found. Where do I get it?

---------- Post added at 03:17 AM ---------- Previous post was at 03:13 AM ----------

I as well lose root on reboot on last version to. Using an n6. A reboot again seems to fix it most times
[Magisk] 1wxyz:
Probably root is working during startup but somehow loses it after some time
[Magisk] JonathanRAZ:
[MENTION=2437714]biggdevon[/MENTION] thank you yes note 5 tmo
[Magisk] Twinfail:
What should I do to fix this?
[Magisk] BustedFly:
For me the same. Magisk v11.6 breaks WebView
[Magisk] Zer0t3ch:
Anyone know if Magisk will work on Android O, and if not, how long it will be until it's working?

Not trying to rush the dev, just curious. I know it just came out.
[Magisk] teddy0209:
Under downloads, tap on the module...
[Magisk] akk29:
Latest version seems less stable with losing root.

Also, when i select systemless hosts for adblock in setting Safetynet no longer passes? This never was a problem before so what's changed?
[Magisk] Didgeridoohan:
You can upload your boot image to GitHub for [MENTION=4470081]topjohnwu[/MENTION] to take a look at and possibly fix any compatibility issues. There's a issue about this opened recently, but no boot image attached.

Are you uninstalling through Magisk Manager? If your device is encrypted already, don't worry, go ahead. If it's not encrypted and you wan't to stay that way it might be better to boot to recovery, flash the Magisk uninstaller and straight after flash SuperSU.

Come on people. [MENTION=4470081]topjohnwu[/MENTION] have enough on his plate working on general compatibility and stability for Magisk. Don't expect him to start working straight away on support for an OS that's in an ALPHA state. Support for Android O will come, in time.

And don't ask for ETAs, it's rude.
[Magisk] aeroxy:
Great mine is a 920FD model so probably doesn't work either...
[Magisk] LazerL0rd:
Just a small question.. how would you install Magisk but keep dm-verity. I know you can do this thrugh the app but if you're gonna use MagiskSU and flash through TWRP.. how do you do it?
[Magisk] 1wxyz:
No idea how to fix. Probably gotta disable magisk hide but I rely on it badly. Hopefully there's a fix to the problem soon.

I have fixed it by performing cleaning installation of ROM.

I only know what causes root to "die" off, it dies off when I launched app "Root Beer sample" or "SafetyNet attest".
[Magisk] onesolo:
We all (cof cof) know that asking ETA is rude, and it is, but asking if it's working already on O, I think that hurts no one. He is not obligated to answer.

For the record, Chainfire already has SuperSu working almost fine on O (he still hasn't released nothing)
[Magisk] Didgeridoohan:
Did you read the question? It was a two-part one:

1 - Does it work?

2 - When will it work?

Question 1 would have been answered by a simple search (it's been asked and answered already).

Question 2 = ETA...

And yes, Chainfire does have basic support for Android O, DP1 on N6P and N5X already, but that doesn't mean Magisk will have it anytime soon.
[Magisk] Tr4il:
Apps like AdAway and Titanium Backup don't even give me the prompt for SU access, they just fail. Haven't tried RootChecker though.

I'll see about posting my boot img, thanks!
[Magisk] BootloopedMillennials:
I have a question about this. A user submitted a recovery log and boot image for a phone I have too. I notice there was no response in the Github thread. Did he not submit correctly?

https://github.com/topjohnwu/Magisk/issues/104

I would like to know because some ROMs we have no working root options and if needed I would submit to make it complete.