[Samsung Galaxy S7 Guides, News, & Discussion] :
[MENTION=2976080]navis83[/MENTION]

Ok, here we go:

Root V2

C:\Users\Administrator\Desktop\sammy>Root.bat

C:\Users\Administrator\Desktop\sammy>adb wait-for-device

C:\Users\Administrator\Desktop\sammy>adb install -r SuperSU-v2.74-2.apk
4149 KB/s (6348638 bytes in 1.494s)
pkg: /data/local/tmp/SuperSU-v2.74-2.apk
Success

C:\Users\Administrator\Desktop\sammy>adb shell mount -o rw,remount /

C:\Users\Administrator\Desktop\sammy>adb push SuperSU-v2.74-2.img /data/su.img
5113 KB/s (33554432 bytes in 6.407s)

C:\Users\Administrator\Desktop\sammy>adb shell mount -o rw,remount /system

C:\Users\Administrator\Desktop\sammy>adb shell touch /system/xbin/su

C:\Users\Administrator\Desktop\sammy>adb shell chmod 0755 /system/xbin/su

C:\Users\Administrator\Desktop\sammy>adb shell chcon u:object_r:system_file:s0 /system/xbin/su

C:\Users\Administrator\Desktop\sammy>adb shell sync

C:\Users\Administrator\Desktop\sammy>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
error: device not found

C:\Users\Administrator\Desktop\sammy>adb shell chmod 0700 /system/etc/launch_daemonsu.sh
error: device not found

C:\Users\Administrator\Desktop\sammy>adb shell chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh
error: device not found

C:\Users\Administrator\Desktop\sammy>adb shell if [ `cat /system/etc/init.sec.boot.sh | grep daemonsu ; echo $?` -ne 0 ]; then 1>/dev/null 2>&1
The system cannot find the path specified.

The device freezes, the SuperSU is installed but do not get root. After rebooting, the device remains installed supersu. Knox still 0X0.

@

@

@

@

Root V3

C:\Users\Administrator\Desktop\sammy>Root.bat

C:\Users\Administrator\Desktop\sammy>adb wait-for-device

C:\Users\Administrator\Desktop\sammy>adb install -r SuperSU-v2.74-2.apk
3897 KB/s (6348638 bytes in 1.590s)
pkg: /data/local/tmp/SuperSU-v2.74-2.apk
Success

C:\Users\Administrator\Desktop\sammy>adb shell mount -o rw,remount /

C:\Users\Administrator\Desktop\sammy>adb push SuperSU-v2.74-2.img /data/su.img
5338 KB/s (33554432 bytes in 6.137s)

C:\Users\Administrator\Desktop\sammy>adb shell sync

C:\Users\Administrator\Desktop\sammy>adb reboot

C:\Users\Administrator\Desktop\sammy>adb wait-for-device

C:\Users\Administrator\Desktop\sammy>adb shell mount -o rw,remount /system

C:\Users\Administrator\Desktop\sammy>adb shell touch /system/xbin/su

C:\Users\Administrator\Desktop\sammy>adb shell chmod 0755 /system/xbin/su

C:\Users\Administrator\Desktop\sammy>adb shell chcon u:object_r:system_file:s0 /system/xbin/su

C:\Users\Administrator\Desktop\sammy>adb shell sync

C:\Users\Administrator\Desktop\sammy>adb reboot
error: protocol fault (no status)

C:\Users\Administrator\Desktop\sammy>adb wait-for-device

C:\Users\Administrator\Desktop\sammy>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
failed to copy 'launch_daemonsu.sh' to '/system/etc/launch_daemonsu.sh': Read-only file system

C:\Users\Administrator\Desktop\sammy>adb shell chmod 0700 /system/etc/launch_daemonsu.sh
chmod: /system/etc/launch_daemonsu.sh: No such file or directory

C:\Users\Administrator\Desktop\sammy>adb shell chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh
chcon: /system/etc/launch_daemonsu.sh: No such file or directory

C:\Users\Administrator\Desktop\sammy>adb shell if [ `cat /system/etc/init.sec.boot.sh | grep daemonsu ; echo $?` -ne 0 ]; then 1>/dev/null 2>&1
The system cannot find the path specified.

The device freezes in the Samsung logo (can not remember if restarted after it or entered directly into the system), but continues without root.