[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Destructor1365:
Trying to root my S7 Edge tmobile and getting root is not correctly installed,

I am running on most recent September update and keep getting adb error messages. The eng boot seems to have worked as it was successful in odin and i did factory restore afterwards. I have manage to root some of my previous devices but im no expert on any of this. Any help would be greatly appreciated

C:\adb>cd super

C:\adb\super>root.bat

C:\adb\super>adb wait-for-device

C:\adb\super>adb shell mount -o rw,remount /system

mount: Permission denied

C:\adb\super>adb shell mount -o rw,remount rootfs /

mount: Permission denied

C:\adb\super>adb push SuperSU-v2.74-2.img /data/su.img

failed to copy 'SuperSU-v2.74-2.img' to '/data/su.img': Permission denied

C:\adb\super>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:\adb\super>adb install -r SuperSU-v2.74-2.apk

2173 KB/s (6348638 bytes in 2.853s)

pkg: /data/local/tmp/SuperSU-v2.74-2.apk

Success

C:\adb\super>adb shell 0<supersu.cmds

touch /system/xbin/su

chmod 0755 /system/xbin/su

chcon u:object_r:system_file:s0 /system/xbin/su

chmod 0700 /system/etc/launch_daemonsu.sh

chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh

if [ `cat /system/etc/init.sec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then

echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh

fi

sync

reboot

shell@hero2qltetmo:/ $ touch /system/xbin/su

touch: '/system/xbin/su': Read-only file system

1|shell@hero2qltetmo:/ $ chmod 0755 /system/xbin/su

chmod: chmod '/system/xbin/su' to 100755: Read-only file system

1|shell@hero2qltetmo:/ $ chcon u:object_r:system_file:s0 /system/xbin/su

chcon: '/system/xbin/su' to u:object_r:system_file:s0: Read-only file system

1|shell@hero2qltetmo:/ $

1|shell@hero2qltetmo:/ $ chmod 0700 /system/etc/launch_daemonsu.sh

chmod: chmod '/system/etc/launch_daemonsu.sh' to 100700: Read-only file system

hcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh <

chcon: '/system/etc/launch_daemonsu.sh' to u:object_r:su_exec:s0: Read-only file system

.sec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then <

> echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh

> fi

shell@hero2qltetmo:/ $

shell@hero2qltetmo:/ $ sync

shell@hero2qltetmo:/ $ reboot

C:\adb\super>adb shell pm hide com.LocalFota

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.samsung.android.intelligenceservice

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.samsung.android.securitylogagent

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.samsung.sdm

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.samsung.syncservice

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.sec.android.diagmonagent

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.sec.android.fotaclient

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.sec.android.fwupgrade

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.sec.fwservice

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.ws.dm

error: device '(null)' not found

C:\adb\super>adb shell pm hide com.wssyncmldm

error: device '(null)' not found

C:\adb\super>adb reboot

error: device '(null)' not found