yashsingh1/xdaforums huggingface dataset:
[Magisk] st0nec01d:
If you look further back in the thread you'll see a post with a modifed apk (to work with tasker) from dark3ss for magisk manager, along with instructions on how to use in Tasker. Pasted below for convenience:

To use Tasker, Create new task, search for "Intent" Click on "Send Intent"

To enable root

1. Set the action to: com.topjohnwu.magisk.ENABLE

2. Set the package to: com.topjohnwu.magisk

3. Set the target to: Broadcast Receiver

To disable root

1. Set the action to: com.topjohnwu.magisk.DISABLE

2. Set the package to: com.topjohnwu.magisk

3. Set the target to: Broadcast Receiver

Here is the link to how Darkn3ss has got his tasker set up. (ASB is his country's equivalent to Android pay) http://imgur.com/a/LA3lR

After you have done that you can assign that task to a tasker widget

https://github.com/DarkN3ss61/MagiskManager

Here is the compiled APK: https://github.com/DarkN3ss61/MagiskManager/releases/download/0.1/MagiskManager_DarkN3ss.apk
[Magisk] devilloki:
[MENTION=4470081]topjohnwu[/MENTION]

upload to dropbox

https://www.dropbox.com/sh/bzit1ty7036gqek/AAAcojr7p6MNjmF65gTSUr_ja?dl=0
[Magisk] topjohnwu:
I don't recommend to use Magisk Manager as a dependency for tasker support, I provide a more easy way to do so (using system props system).

And BTW, a new version will be up soon :), I'll finalize Magisk and the unroot interface, and start recruiting testers for Android Pay.
[Magisk] JimSmith94:
Does your "more easy way" use setprop as RatchetPanda suggested in this post? http://xdaforums.com/showpost.php?p=68172939&postcount=595

If so, that's what we have been discussing and it doesn't seem to work. If not, could you provide or point to an example? Or should we wait for your finalized unroot interface?
[Magisk] oreo27:
After flashing phh's SuperUser, did you also install the apk from the Play Store?
[Magisk] Shailesh1711:
Yes. I did exactly as per instructions.
[Magisk] RedofTears:
noob question:

How to set selinux permissive in magisk v9? I had tried Selinux Mode changer.
[Magisk] Shailesh1711:
Yes
[Magisk] oreo27:
Alright. What are you using to check root? I heard some older apps don't work with phh's SuperUser. Maybe you can try SuperSU in the meantime?

If you'd like to try this, you'll have to uninstall phh's SuperUser using the built in Magisk Manager then boot to recovery. Flash SuperSU then flash Magisk v9 again. You should have SuperSU to manage root permissions then.
[Magisk] Shailesh1711:
I m using Root Checker Basic to check root. Even in Magisk Manager it is showing not rooted
[Magisk] joshuaw84:
Are the original zip and the new zip the same structure? Open the new one up and see. Without being able to look I'd guess there's a magisk folder at the root of the zip and not the files contained within that are supposed to be at the root
[Magisk] dunkin11:
Bootloop 7.1.1 Nexus5x

I recently sideloaded the 7.1.1 OTA for Nexus5x. Once that finished, I attempted installing Magisk V9 via TWRP. After install, my phone gets stuck on the spinning wheels and won't proceed. If I flash the OTA boot.img again, my phone will boot up like normal.

Any ideas why flashing Magisk V9 causes the bootloop? What logs would be useful?
[Magisk] jjohn7293:
Hey, I'm having a bit of trouble.... I have magisk v9 with Xposed, and my Android pay app works and makes payments perfectly fine, but my Pokemon app will not load beyond the loading screen... Any ideas what's going on???
[Magisk] yochananmarqos:
I installed Magisk + the phh superuser module immediately after sideloading the OTA with no issues.

The TWRP log might be useful.
[Magisk] Shailesh1711:
Hope this recove log helps.
[Magisk] dunkin11:
Interesting.. sideloading OTA kept resulting in bootloop. However, using the factory image flash-all without -w made it work. Not sure why sideloading the OTA resulted in bootloop after installing Magisk V9, but I am good now... Thanks!
[Magisk] jjohn7293:
Here's my safety net results, with Xposed installed.

SafetyNetResponse{nonce='OLlgy555sP4Qve5wK+qxmATZ5MUOUXL6HzSr+rW9mDM=', timestampMs=1481053597360, apkPackageName='null', apkCertificateDigestSha256=[], apkDigestSha256='null', ctsProfileMatch=true}

Can anyone tell me why I can't get xposed to work with safety net??
[Magisk] Portgas D. Ace:
Because current Xposed isn't compatible with Safety Net. Use suhide if you want to use Xposed.
[Magisk] jjohn7293:
I have magisk v9 and xposed, and my android pay works. But despise android pay working, safetynet won't let me access my Pokemon game, and the checker gives me a blue screen. How do I use suhide with Xposed and magisk v9???
[Magisk] Portgas D. Ace:
As I don't use Magisk at the moment, I can't say for sure. But I am sure that others have tried the same, so maybe a search in this thread or in the suhide thread will give you the solution. Maybe just install root switch app (can be found in the suhide thread) and check if it's working, latest version (v1.3.3.2) hides Xposed.

Also check if there are any "su" files inside /system/bin and /system/xbin, if yes, delete them. But make a backup first to avoid any unwanted behavior.
[Magisk] joshuaw84:
Please see this thread for Pokemon related discussion http://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722
[Magisk] Didgeridoohan:
Yes, that's the log I was talking about. Unfortunately it shows nothing... You need to capture it straight after flashing Magisk and Magisk phh's superuser.

Also, the Magisk log can be found in the Magisk Manager.
[Magisk] jjohn7293:
I can't find the link. Can you post the link to 1.3.3.2?
[Magisk] Portgas D. Ace:
http://xdaforums.com/apps/supersu/suhide-t3450396/post69794799
[Magisk] Shailesh1711:
Then, shall i uninstall Magisk?

In Magisk Manager also no logs are seen.p l check the screenshots attached.
[Magisk] yochananmarqos:
This statement is not at all accurate. The current state of suhide does not hide root from SafetyNet let alone hide Xposed.
[Magisk] Didgeridoohan:
Obviously Magisk installed correctly.... Try reflashing Magisk phh's superuser and upload the recovery.log from there. No need to uninstall anything, yet.
[Magisk] Syoenth:
anyone have an S3 with magisk and phh superuser working and safetynet passed? If so, tell me how can I do the same, cause when I install magisk with phh superuser with it apk I can't get superuser privileges, it supposedly show a window prompt, but it don't show it
[Magisk] mobileman88:
You need to enable logs in the Magisk settings of Magisk Manager to save the logs.
[Magisk] Didgeridoohan:
Not quite true... You can enable more verbose logging, but the logs will always be there. I believe the reason no log is showing for [MENTION=7908869]Shailesh1711[/MENTION] is that he has no root. No root means that Magisk Manager can't access the cache folder to fetch the log.
[Magisk] Rhoban:
Did you flash the phh r266-2 zip and did you install the phh superuser app from the play store?

If the phh app is not installed, there will be no window prompt.
[Magisk] Shailesh1711:
Exactly. That's what i m saying that even after following the procedure my phone is showing as not rooted.

And, Advanced debug logging is enabled in the settings of Magisk Manager.
[Magisk] Portgas D. Ace:
For sure? I am using SuperSU v2.78-SR3 with suhide and Xposed v86.2. SuperSU and suhide pass SN, whereas for Xposed the root switch app is required to pass SN on my device.
[Magisk] Didgeridoohan:
Do you see phh's Superuser under "Modules" in Magisk Manager? And, like I said earlier, try flashing Magisk phh's Superuser again and capture the recovery.log right after. It might shed some light on the issue.

You can also copy magisk.log from the cache folder while in TWRP.
[Magisk] AbsolutelyProprietary:
It was recently pacthed I think? Try disabling it
[Magisk] jjohn7293:
Even with no Xposed, I get a blue error screen. I unrooted and then for some reason I got a red screen. I tried the sr4 root and rootswitch, but that didn't work for me either...
[Magisk] AbsolutelyProprietary:
I think it's because it was already triggered
[Magisk] jjohn7293:
Ok so what's the process if I want root and Xposed, with a green safety net on my Galaxy s7 running Superman ROM with the superstock kernel?
[Magisk] ghbuur:
I've got the s7e, superman/superstock/magisk v9, phh/xposed 87.1 by wanam/rootswitch. magisk hide is enabled. to pass safetynet i have to disable xposed with rootswitch, softboot AND reboot again the phone. that works but of course temporarily disables xposed..
[Magisk] jfath:
Unable to detect boot image amlogic s905x

I was getting an error when attempting to flash Magisk v9 to my cheap amlogic s905x android TV box.

Looking at the install script, there is no by-name directory for the partitions, so that search will fail, but the section that looks at fstab.recovery seems like it should have worked. When booted into recovery, /etc/fstab.recovery has an entry that reads: /boot emmc /dev/block/boot. From the shell, I ran grep -E '\b/boot\b' /etc/fstab.recovery | grep -oE '/dev/[a-zA-Z0-9_./-]*' and it returned /dev/block/boot.

Here is the relevant code from update-binary:

find_boot_image() {
if [ -z "$BOOTIMAGE" ]; then
for PARTITION in kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do
BOOTIMAGE=`readlink /dev/block/by-name/$PARTITION || readlink /dev/block/platform/*/by-name/$PARTITION || readlink /dev/block/platform/*/*/by-name/$PARTITION`
if [ ! -z "$BOOTIMAGE" ]; then break; fi
done
fi
if [ -z "$BOOTIMAGE" ]; then
FSTAB="/etc/recovery.fstab"
[ ! -f "$FSTAB" ] && FSTAB="/etc/recovery.fstab.bak"
[ -f "$FSTAB" ] BOOTIMAGE=`grep -E '\b/boot\b' "$FSTAB" | grep -oE '/dev/[a-zA-Z0-9_./-]*'`
fi
}

I didn't debug further, but my only guess is that somehow $FSTAB isn't getting set correctly? I know the grep returns the correct string when I hard code fstab.recovery and run it in a recovery shell.

In the end, I inserted BOOTIMAGE="/dev/block/boot" into the update-binary file and the modified .zip installed without a problem. I have a working Magisk installation.

Not sure if topjohnwu monitors this thread, but thought the info might be helpful to someone.
[Magisk] Syoenth:
Yes I did
[Magisk] Shailesh1711:
I don't see phh's Superuser under 'Modules' in Magisk, it is empty.

As u advised I tried flashing Magisk phh's Superuser again and captured the recovery.log
[Magisk] jcrompton:
Pokemon Go is a GO // SafetyNet is a NO

Guys hopefully someone can at least comment -- I have asked a similar question in the past and no responses.

I have been very successful with my Nexus 6 Shamu with AOSP and CM based ROMs - 6, 7.0 and 7.1 by making sure fully unrooted, flashing a kernel like Flash 1.6, magisk v9, Magisk phh module 266-2, installing phh app and magisk manager 2.5, giving manager root and checking Hide , rebooting and SUCCESS (usually).

However, with Nitrogen ROM (and other ROMs where I have used BlackBird kernel) I get success with playing PoGo but SafetyNet won't pass and of course no AP. The reason I'm making a big deal is just that basically I'm trying to understand ---- I thought PoGo was some how dependent upon SafetyNet ----- so why does PoGo work but SN won't pass??

And is there a fix? What could it be about that particular ROM and / or that particular kernel??

Thanks!!!!
[Magisk] Captain_Throwback:
This isn't the PoGO thread....

EDIT: But the most obvious answer is that PoGO isn't using a full SafetyNet validation. Airwatch uses some SafetyNet and other non/SafetyNet checks. It's probably the same with PoGO. As far as your specific ROM, you'll have to work with the ROM dev on that.
[Magisk] jcrompton:
Yes sir ... thank you -- I do understand and for sure I wasn't asking anything specifically about PoGo

My question was more for the variations or differences in the one ROM and the one kernel ----- and even the variation that there is "partial success" . The more I learn what could cause that partial success then the more I can fix myself or at least help the developers of those ROMs and kernels to fix .

I'm just hoping that you can give me some ideas on what could cause the partial success or at least point me in the right direction.

Thanks for your time !!!!!
[Magisk] Drivepnut:
How are you getting Android pay to work
[Magisk] jjohn7293:
It just does, I have no idea? I'm just really confused because Android pay Works flawlessly, but I can't get Pokemon go to work for ****.
[Magisk] nathlynn22:
Holding off with updating HTC 10 on Viper to 4.0+ sticking with 3.5.0

Wanting to reflash though. And wanting to use magisk. Just for the reason Of wanting Pokemon go to work as my sons always want to play it while we're out.

Is the way to do it.

Wipe

Flash 3.5.0

Use systemless root

Reboot

The install newest magisk manager

And Install phh superuser

Thanks
[Magisk] culiacanazo:
As far as superusering goes when you reboot you need to flash phh's zip right then, followed by the apk while in android.

Depending on your wipe, magisk zip comes before phh's
[Magisk] Abhi142:
Can anyone give me the link of official announcement thread? Plz help
[Magisk] yochananmarqos:
Good grief, it's in the first post (aka OP, original post).
[Magisk] Abhi142:
In this thread?
[Magisk] yochananmarqos:
:

... :rolleyes:
[Magisk] mathy007:
Yes
[Magisk] Abhi142:
Installed magisk v9 & magisk manager 2.5. Where can i toogle root on or off
[Magisk] ammar18:
there's no toggle. use root switch or magiskhide.
[Magisk] mobileman88:
You can't toggle root on and off, however Magisk Hide in Magisk Manager settings allows you to hide root from selected apps. You need to reboot after setting it.
[Magisk] Abhi142:
Link for root switch?
[Magisk] oreo27:
Just a curious question, can I copy stuff to the /magisk directory for it to be loaded by magisk or do I need to do the module.prop stuff as well for it to be loaded at all?
[Magisk] DodoGTA:
Does SafetyNet API check if device is CTS compatible?
[Magisk] Captain_Throwback:
Use the module template.
[Magisk] Shailesh1711:
I have shared the recovery log.

Magisk log shows size 0kb
[Magisk] Mortisoul:
So i have it all installed and working well on my LG V10 with root right up until I launch either pokemon go or DirectvNow both of which are on the hide list. These apps kill root access as per the hid settings and then launch fine, but once the app is stopped via the app tray, my root access is not restored until I fully reboot the device. Then I am good with root access again until I launch an app on the hide list. How can I get it automatically restore root without rebooting my phone?
[Magisk] Didgeridoohan:
Yes, I saw that. Just haven't had time to look, until now.

The flashing looks perfectly fine, nothing amiss that I can see. Hmm....

Really could use a Magisk log. Is it empty after you pull it from cache?
[Magisk] Shailesh1711:
Yes. Pl see screenshot. Even its not allowing to attach the original log file.
[Magisk] Didgeridoohan:
Ok... Obviously there's something wrong with your Magisk installation. Don't remember if you've said, but have you started from scratch? Run the uninstaller, make sure you've got a clean system to start with and try again (and remember to grab recovery.log :D ).
[Magisk] Shailesh1711:
Yes I had started from scratch only. This is the first time i m trying to systemless root my device. I followed the instructions as given i.e. flashing latest Magisk & phh's Superuser. After that installing Magisk Manager& Superuser app from Playstore.

Now, if i flash the Magisk Uninstaller, that should be enough to get a clean system... RIGHT??
[Magisk] PwnCakes193:
A clean system, yes, a clean boot image? No. If you want to truly go back to stock you have to run the uninstaller and then flash your original boot.img from before you flashed Magisk
[Magisk] TubbyStubby:
after doing the correction i am getting another error - Image mount failed ... abort " Error executing updater binary in zip" help pls.

solved - switched to cwm from twrp and it worked dont know why? still.
[Magisk] oreo27:
Quick question. I made a quick magisk module in setting a build.prop edit, made it a cache mod and flashed it which seems to be working fine but it's not reflected on the actual build.prop file. Is this normal?
[Magisk] Shailesh1711:
Flashed Magisk Uninstaller, rebooted & restored boot backup which was taken before installing Magisk.

---------- Post added at 05:08 PM ---------- Previous post was at 04:59 PM ----------

Can u help me doing a systemless root of my device please?
[Magisk] Didgeridoohan:
If following the instructions for installing Magisk to the letter doesn't work for you, I'm not sure I can help you. Have you tried Chainfire's SuperSU?

My opinion is that you should move over to your device forum and search for help there. The chance of someone being able to help is much greater there...

http://xdaforums.com/leeco-le-1s

Good luck.

---------- Post added at 17:33 ---------- Previous post was at 17:31 ----------

Since Magisk v9 you can't use cache modules anymore. You need to use the resetprop tool instead. It's all explained in the Official announcement thread...
[Magisk] Nomelas:
has anyone tried SuperSU 2.78 SR5 yet with Magisk v9? is it compatible?
[Magisk] culiacanazo:
I have. It is.
[Magisk] MrBrady:
Anybody know if the device must be encrypted to pass SafetyNet with Dec security update?

---------- Post added at 04:12 AM ---------- Previous post was at 04:08 AM ----------

What's the flashing process? Kernel, SuperSu, Magisk?
[Magisk] culiacanazo:
I did SuperSU, magisk, reboot system, reboot recovery, kernel.

However, i ignore wether that would be a device/kernel dependant issue (process)
[Magisk] oreo27:
Thanks for pointing me in the right direction. I tried it out by putting the following code into \common\post-fs-data.sh

/data/magisk/resetprop qemu.hw.mainkeys=0

However, it didn't seem to reflect on the build.prop either.

I've also changed the config.sh like so:

POSTFSDATA=true

Attached the module here as well. Perhaps you can give me some pointers. Thanks!
[Magisk] namquang93:
Is there any way to set selinux to permissive (setenforce 0) ?
[Magisk] ammar18:
the answer is in your question...?
[Magisk] namquang93:
I know I can open terminal emulator and setenforce 0, but I have to do that everytime I restart the phone. I remember magisk 1.2 can set selinux to permissive, now I'm using magisk manager 2.5 and ai can't find it.
[Magisk] yochananmarqos:
The kernel has to be flashed first as Magisk, phh superuser and SuperSU all need to patch the kernel to work properly. Flashing the kernel after could overwrite the patches in the ramdisk.

---------- Post added at 06:57 AM ---------- Previous post was at 06:51 AM ----------

You should be able to create a Magisk module to accomplish this. However, SafetyNet will not pass if SELinux is not set to enforcing.
[Magisk] ammar18:
try to find an app like selinux mode changer.
[Magisk] culiacanazo:
Don't "have to".

I'm not arguing your stance could be better.

I'm saying i did it exactly as I've stated and it's working
[Magisk] mobileman88:
I don't think you need to be encrypted, but I have encrypted mine for months. Is there any reason you want to keep your phone decrypted?
[Magisk] MrBrady:
No reason. Just diagnosing.
[Magisk] Didgeridoohan:
I haven't looked at your module, but it sounds ok.

The thing is that you're not changing build.prop, just that single property. Easiest way to see if it works is to open a terminal emulator and type in: getprop qemu.hw.mainkeys. The reported value should be what you've set it to in your module rather than the build.prop value, in which case everything's as it should be and your module is working.
[Magisk] Captain_Throwback:
That code in post-fs-data.sh is wrong. There shouldn't be an equals sign in there - just a space.
[Magisk] Didgeridoohan:
True. [MENTION=4863028]oreo27[/MENTION]
[Magisk] namquang93:
Ignore.
[Magisk] yochananmarqos:
How many times are you going to post the same thing over and over? Your bad forum etiquette is now bordering on spam.
[Magisk] darkeyes22:
If I remove Magisk with Magisk uninstaller, i'll remove root too?
[Magisk] LeRalouf:
That's what it did for me :)

Hello,

I tried flashing Magisk v9 and phh on a Samsung Galaxy A3 2016 (restored to stock first). I flash Magisk and phh (from internal storage) with TWRP and then I get an error about the kernel length so that it won't boot.

Is that because I flash from internal storage ?

Sorry I didn't get the error, I rebooted in download mode since then and re-restored to stock.

Thanks !
[Magisk] darkeyes22:
You are on stock or custom kernel?
[Magisk] LeRalouf:
The phone is freshly bought, I didn't flash anything but the stock ROM, so I'd say stock :)
[Magisk] darkeyes22:
Then try to flash custom kernel, it can help :)
[Magisk] LeRalouf:
Except I can't seem to find any for that particular model (Galaxy A3 2016 - SM-A310F). Anyway, I just reflashed TWRP on the phone restored to stock (latest french firmware from sammobile), and I'll be waiting for someone who has another idea :)

Thanks a lot!
[Magisk] darkeyes22:
Can you tell me what version of TWRP you have flashed? Once I had a recovery loop because of older version of TWRP
[Magisk] KevinX8:
Can someone confirm if SN is still passing on android 7.1.1 with magisk v9 because no matter what I do I cannot get it to pass but as soon as I uninstall magisk boom pass
[Magisk] LeRalouf:
3.0.2-1 :)
[Magisk] darkeyes22:
have you tried to factory reset?
[Magisk] LeRalouf:
Yep :)

I even tried installing one of the ROMs from a french operator, no changes ^^
[Magisk] yochananmarqos:
Excuse me? You keep asking how to set SeLinux to permissive even after you've received more than one answer.
[Magisk] namquang93:
Ignore
[Magisk] DodoGTA:
How can I hide SELinux state (I mean that how I can be in SELinux Enforcing mode without actually being in that mode)?

UPDATE: And as for why I want to do that, my ROM doesn't support SELinux Enforcing (because of quite a lot of denials caused by proprietary blobs and things like that)
[Magisk] yochananmarqos:
Yes, please do solve it yourself. We tried to help, but you just don't get it.

Again, the best on topic solution would be creating a Magisk module. However, as someone else already suggested, SELinux Mode Changer via F-Droid may work without having to create a module as it only requires root access IIRC.

Come to think of it, you never stated why you want to set SELinux to permissive. I can't think of a single reason. Plenty of root apps have been updated to support enforcing.

Please do not reply, let's move to PM if you have more to say.

---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------

You're in luck! Read my last post. Good grief.
[Magisk] DodoGTA:
Please see and revisit my question again (because I added more info to my question)
[Magisk] yochananmarqos:
This would be a question to ask in your ROM thread. This is quite off-topic for this thread and it's partially my fault for addressing such questions.
[Magisk] Rhoban:
To [MENTION=6683596]namquang93[/MENTION] and those who don't want to change the selinux at every boot, run the following commands in a terminal app:

mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh

This sets the selinux to permissive every boot. If you have it permissive by default and want it enforcing, then replace "0" with "1". That should technically work. Good luck.
[Magisk] DodoGTA:
Or someone can run an init.d script with the following contents:

#!/system/bin/sh
setenforce 0

(Change the number from 0 to 1 if you want to set SELinux mode to Enforcing)

---------- Post added at 10:10 AM ---------- Previous post was at 10:06 AM ----------

I noticed a little mistake in this code: ! and # characters should swap their places, like this: !# to #!