[Magisk] SidneyD:
Problems with Magisk on Galaxy Note II

I am attempting to get Magisk working on my phone. I have followed the instructions, however it's not working properly. I have a Galaxy Note II running OctOS (CM13 based, Android 6.0.1 ROM). Below are the steps I've performed and the result. Would anyone be able to tell me if I'm simply doing something wrong, or if I've encountered a bug?

Before starting I downloaded Magisk-v6.zip, phh-superuser-17-magisk.zip, xposed-v86.5-sdk23-topjohnwu.zip, Magisk_Manager_v1.2.apk, and XposedInstaller_by_dvdandroid.apk. Then I made a full backup in recovery.

ATTEMPT #1

• Used SuperSU to unroot system ('yes' to attempt stock image, 'no' for stock recovery).

• Reboot; check an app that requires root (Titanium Backup); Privacy Guard asks if I should grant root to TB; yes; TB tells me that my "su binary (version "16 cm-su") is functional but might not work reliably with some Android 4.3+ ROMs."

• Reboot to recovery; mount /system rw; look for instances of su; find and delete /system/bin/su and /system/xbin/su; reboot.

• Check TB and it cannot gain root; install and run Pokemon GO; works.

• Reboot to recovery; mount /system rw; flash the following in order: Magisk-v6.zip, phh-superuser-17-magisk.zip, xposed-v86.5-sdk23-topjohnwu.zip; wipe cache/dalvik; reboot.

• Process list goes bananas (I later learned that this is due to SELinux being set to Permissive on startup); install phh's SuperUser from Google Play Store, install Magisk_Manager_v1.2.apk; open Magisk Manager and attempt to toggle root off, and SELinux to Enforcing; in both cases the toggle just bounces back after a second; clearly something is wrong.

• Reboot to recovery, mount /system rw, restore backup.

ATTEMPT #2

• Used SuperSU to unroot system ('yes' to attempt stock image, 'no' for stock recovery).

• Rebooted directly to recovery; mount /system rw; delete /system/bin/su and /system/xbin/su; reboot.

• Check TB and it cannot gain root (Privacy Guard does not pop up); install and run Pokemon GO; works.

• Do some reading and discover there's a 'superuser.zip' that literally states that it's been tested with the Galaxy Note 2. Download and reboot to recovery.

• Mount /system rw; flash superuser.zip; wipe cache/dalvik; reboot.

• Install phh's SuperUser from Google Play Store; check TB; Privacy Guard does not pop up, but SuperUser does!; allow; TB tells me that my "su binary (version "17 me.phh.superuer cm-su subind suinit") is functional but might not work reliably with some Android 4.3+ ROMs."

• Reboot to recovery; mount /system rw; flash Magisk-v6.zip; wipe cache/dalvik; reboot.

• Process list going crazy again; install Magisk_Manager_v1.2.apk and open; root status: not rooted, Selinux status: permissive, both toggles are greyed out and unusable.

• Reboot to recovery; mount /system rw; flash the following in order: phh-superuser-17-magisk.zip, xposed-v86.5-sdk23-topjohnwu.zip; wipe cache/dalvik; reboot.

• Process list crazy; open Magisk Manager and SuperUser pops up!; allow; I can now toggle root and SELinux!; when I put SELinux to enforcing, the process list regains it's sanity; toggle root off.

• Install and run Pokemon GO; fails Safety Net.

• Open Terminal Emulator and go looking for su; find a file, '/sbin/su' and a directory, '/data/su/'; I can delete /data/su, but it says that /sbin/su is read only.

• Turn root back on in MM and open TB, TB tells me that my "su binary (version "17 me.phh.superuer cm-su subind suinit") is functional but might not work reliably with some Android 4.3+ ROMs."

• Remount rootfs as rw and delete /sbin/su; Pokemon GO (after clearing app data) now works.

• Rebooting causes /sbin/su and /data/su/ to return; neither of these can be found in recovery so I cannot remove them there.

So if you read all that you'll see that I have two problems:

1) Magisk v6 causes my phone to start with SELinux in permissive mode. I do not want my phone to be in permissive unless I tell it to.

2) phh-superuser-17-magisk.zip by itself does not provide root, but the "regular" superuser.zip does. However, superuser.zip creates /sbin/su and /data/su/ which causes Safety Net to trip even when Magisk has root toggled off. While I can delete these it requires me mounting the rootfs file system as rw which I'm betting is something that I don't want to do.

Any ideas on what the problem(s) could be?