[Magisk] Vipriel:
Sure. In my case, I was using Magisk v8 and Phh's Superuser r259 prior to the latest SafetyNet update. After the update, to follow Zapahack's instructions I simply had to uninstall Magisk v8 with the uninstaller file from recovery (Magisk-uninstaller-20161004.zip). I then uninstalled the apps associated with Magisk (Magisk Manager is one and I can't recall if uninstalling Magisk from recovery removes Phh's Superuser APK or not - if not, just uninstall they way you uninstall Magisk Manager). At this point, Magisk is gone and you are unrooted since Phh's Superuser was a Magisk module.

If you want to flash a custom kernel, this is when you do it. If you do it later, you'll have to do the steps that come after again because flashing a custom kernel will reset your boot image. In my case, I went ahead and flashed the new Prometheus Kernel (this was just for me wanting to test it - it's not necessary). Then do the Ramdisk patches. You can do this one of 2 ways:

1-Get ADB working on your phone if you don't have it installed on a PC already. If you need it up and quickly, just go to the XDA thread labeled "[TOOL]Minimal ADB and Fastboot [10-22-16] by shimp208" (I don't know if we are allowed to link to other threads here so I just put the title but if you Google it, you'll get there). For ADB to work properly, you need the Samsung drivers installed on the PC as well. Easiest way to get the latest drivers is to install Samsung SmartSwitch which will automatically install them for you. Then you boot into recovery to copy the 2 patches to /Data (that's all you are doing with the ADB commands listed). Make sure to run the ADB commands in recovery because within the ROM, even though you can get ADB Shell root access, depending on your ROM you won't be able to get ADB root access (this is easy to figure out btw - if you are getting permission denied when issuing the ADB push command within the ROM, it means the phone does not have ADB root access. You can try typing "ADB root" which is supposed to restart ADB in root mode but at least in my case, this doesn't provide a root request on the phone and I still get permission denied). All this talk was just to state that if you want to ensure the ADB push works, make sure you do it in TWRP.

2-Since all you are doing is copying 2 files to the Data folder within / , you don't necessarily need to use ADB. You can just use a file manager to do the operation. I use Solid Explorer as my File Manager but I'm sure ES File Explorer or whatever will also work. This requires root access though. So if you are already rooted, you can simply mount Root with your favorite File Manager, navigate to Data and copy "custom_ramdisk_patch.sh" and "dot.supersu". Then you have to rename "dot.supersu" to ".supersu" and you are done.

OK, with the Ramdisk files copied, you can now go ahead and root. If you used the ADB method, just go ahead and flash SuperSU 2.78 SR2. If you did the File Manager copy method, once again go ahead and flash SuperSU 2.78 SR2 again (even though this means you have already flashed SuperSU 2.78 SR2). The reason you would flash SuperSU again even though you are already rooted is because the Ramdisk patches need to be present to do their magic when you are flashing SuperSU. This is where I might be totally wrong! Perhaps all you need is the file copy and maybe it doesn't matter whether you root after or before. The instructions by both Zapahacks and the maker of the Ramdisk patches state to flash SuperSU *after* though which makes it sound like there is an interaction between the SuperSU install and the patches. So you may need to test this out. If you want this done the most straight forward way, do it with an ADB push from within TWRP which doesn't require you to be rooted. As long as you understand what you are doing through, you should be OK.

After you are rooted, install the latest Root Switch APK (1.3.3.2). At this point, you are either done or if you want Xposed, you have another step. If you want Xposed, you can either flash Systemless Xposed 86.2 (latest version that does not require Magisk) or System based Xposed 86.1 by Wanam for Samsung devices from recovery. I have tested both and they both work for me (but I can't use Xposed while I am playing PoGo). Then what you do is either open Root Switch and turn Root to OFF or if you also have Xposed installed, you turn off Xposed first from Root Switch (this will automatically soft reboot your phone), and then turn Root to OFF once again from Root Switch and you are done.

One thing that's important to remember is to do a wipe Dalvik/Cache if things are not working for you after all the steps. Also, it sometimes takes a minute for all processes to kick in after the ROM is booted up. So if you hastily open SafetyNet helper as soon as the ROM boots and you get Red or Blue, don't panic. Give it a minute or 2 and then try again. Same with PoGo. Also, you may occasionally not be able to get into PoGo after you close it (it may hang). If this happens, just reboot, toggle Root back to OFF and you should be good again. If you follow all these steps, you should be working just fine. Some people are saying that their Xposed modules actually work while Xposed is toggled to OFF (which is what you need to get PoGo working) within Root Switch but that's not the case for me. Your mileage may vary.

---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------

Sure. In my case, I was using Magisk v8 and Phh's Superuser r259 prior to the latest SafetyNet update. After the update, to follow Zapahacks' instructions I simply had to uninstall Magisk v8 with the uninstaller file from recovery (Magisk-uninstaller-20161004.zip). I then uninstalled the apps associated with Magisk (Magisk Manager is one and I can't recall if uninstalling Magisk from recovery removes Phh's Superuser APK or not - if not, just uninstall the way you uninstall Magisk Manager from within the ROM). At this point, Magisk is gone and you are unrooted since Phh's Superuser was a Magisk module.

If you want to flash a custom kernel, this is when you do it. If you do it, later, you'll have to do the steps that come after again because flashing a custom kernel will reset your boot image. In my case, I went ahead and flashed the new Prometheus Kernel (this was just for me wanting to test it - it's not necessary). Then do the Ramdisk patches. You can do this one of 2 ways:

1-Get ADB working on your phone if you don't have it installed on a PC already. If you need it up and quickly, just go to the XDA thread labeled "[TOOL]Minimal ADB and Fastboot [10-22-16] by shimp208" (I don't know if we are allowed to link to other threads here so I just put the title but if you Google it, you'll get there). For ADB to work properly, you need the Samsung drivers installed on the PC as well. Easiest way to get the latest drivers is to install Samsung SmartSwitch which will automatically install them for you. Then you boot into recovery to copy the 2 patches to /Data (that's all you are doing with the ADB commands listed). Make sure to run the ADB commands in recovery because within the ROM, even though you can get ADB Shell root access, depending on your ROM you won't be able to get ADB root access (this is easy to figure out btw - if you are getting permission denied when issuing the ADB push command within the ROM, it means the phone does not have ADB root access. You can try typing "ADB root" which is supposed to restart ADB in root mode but at least in my case, this doesn't provide a root request on the phone and I still get permission denied). All this talk was just to state that if you want to ensure the ADB push works, make sure you do it in TWRP.

2-Since all you are doing is copying 2 files to the Data folder within / , you don't necessarily need to use ADB. You can just use a file manager to do the operation. I use Solid Explorer as my File Manager but I'm sure ES File Explorer or whatever will also work. This requires root access though. So if you are already rooted, you can simply mount Root with your favorite File Manager, navigate to Data and copy "custom_ramdisk_patch.sh" and "dot.supersu". Then you have to rename "dot.supersu" to ".supersu" and you are done.

OK, with the Ramdisk files copied, you can now go ahead and root. If you used the ADB method, just go ahead and flash SuperSU 2.78 SR2. If you did the File Manager copy method, once again go ahead and flash SuperSU 2.78 SR2 again (even though this means you have already flashed SuperSU 2.78 SR2). The reason you would flash SuperSU again even though you are already rooted is because the Ramdisk patches need to be present to do their magic when you are flashing SuperSU. This is where I might be totally wrong! Perhaps all you need is the file copy and maybe it doesn't matter whether you root after or before. The instructions by both Zapahacks and the maker of the Ramdisk patches state to flash SuperSU *after* though which makes it sound like there is an interaction between the SuperSU install and the patches. So you may need to test this out. If you want this done the most straight forward way, do it with an ADB push from within TWRP which doesn't require you to be rooted. As long as you understand what you are doing through, you should be OK.

After you are rooted, install the latest Root Switch APK (1.3.3.2). At this point, you are either done or if you want Xposed, you have another step. If you want Xposed, you can either flash Systemless Xposed 86.2 (latest version that does not require Magisk) or System based Xposed 86.1 by Wanam for Samsung devices from recovery. I have tested both and they both work for me (but I can't use Xposed while I am playing PoGo). Then what you do is either open Root Switch and turn Root to OFF or if you also have Xposed installed, you turn off Xposed first from Root Switch (this will automatically soft reboot your phone), and then turn Root to OFF once again from Root Switch and you are done.

One thing that's important to remember is to do a wipe Dalvik/Cache if things are not working for you after all the steps. Also, it sometimes takes a minute for all processes to kick in after the ROM is booted up. So if you hastily open SafetyNet helper as soon as the ROM boots and you get Red or Blue, don't panic. Give it a minute or 2 and then try again. Same with PoGo. Also, you may occasionally not be able to get into PoGo after you close it (it may hang). If this happens, just reboot, toggle Root back to OFF and you should be good again. If you follow all these steps, you should be working just fine. Some people are saying that their Xposed modules actually work while Xposed is toggled to OFF (which is what you need to get PoGo working) within Root Switch but that's not the case for me. Your mileage may vary.