The SR1 release changed a lot of SELinux handling aimed at Android 7.x. A bug in this handling caused the installation to break on older firmwares. This update fixes that specific bug.
There were a number of reports of bootloops with SR1 on pre-7.0 firmwares, please re-report them (in the BETA thread) if they still happen with SR2 - otherwise I will assume them corrected by this patch.
+brandon carlson That is normal. Because When SuperSU updates in systemless mode it has to patch the stock boot.img rather than the ones that already patched, so your boot.img will recover to the backup ones you install SuperSU the first time, and kernel is in boot.img. Reflashing the kernel is fine.
+Kjell O I tried all of the above versions...all stuck on bootloop. Then I tried the old version (2.65) and worked (after successful installation it updated to latest version from play store and su binary also updated through the app).
+Kjell O I tried one by one because after trying each one my phone stuck on bootloop and I had to resore my backup again(stock backup), so the reason should be something else that those versions interfer with newer stock version(3.x)
+Kjell O yes you are right...but it was suggested from a m9 xda thread to solve the issue along with using unofficial 3.0.3... Twrp. I tried them after I got issue with 2.79 and apparently the only version that the phone didn't stuck on bootloop was sr1, but the problem was that after flashing nothing was installed and there was no su app.
Stock Nexus 5X 7.1.1 Nougat NMF26F - SuperSU 7.29SR2 and 2.78etc. boot image patcher fails at
Patching sepolicy --- Failure, aborting.
This has been happening with SuperSU builds for me since stock 7.0/7.1 (i've tried living without root...and I'm sick of it ;p) - Anyone else experiencing this particular? Found some references to older versions having this problem but nothing lately.