[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] gotmilk702:
Issues with root

Hi guys!

Odin flashed without issue but the ADB shell commands don't look like they should after I ran the root.bat. The result is the phone boots with custom symbol, i have the weird new icons for messaging/VoLTE and it doesn't remember wifi passwords. I found the fixes, but when the fixes required root the phone failed to call SuperSU to give root permission. SuperSU fails when trying to update the binary "normal method" Root checker shows no root. All signs point to failed root. Anything I might be doing wrong? Thanks for your help!

Here is the results of root.bat :

Microsoft Windows [Version 10.0.14393]

(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\ricky>cd\samsungroot

C:\samsungroot>root

C:\samsungroot>adb wait-for-device

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

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

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

1791 KB/s (33554432 bytes in 18.292s)

C:\samsungroot>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh

128 KB/s (4686 bytes in 0.035s)

C:\samsungroot>adb install -r SuperSU-v2.74-2.apk

1839 KB/s (6348638 bytes in 3.370s)

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

Success

C:\samsungroot>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

root@hero2qltetmo:/ # touch /system/xbin/su

root@hero2qltetmo:/ # chmod 0755 /system/xbin/su

root@hero2qltetmo:/ # chcon u:object_r:system_file:s0 /system/xbin/su

root@hero2qltetmo:/ #

root@hero2qltetmo:/ # chmod 0700 /system/etc/launch_daemonsu.sh

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

ec.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

root@hero2qltetmo:/ #

root@hero2qltetmo:/ # sync

root@hero2qltetmo:/ # reboot

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

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

error: device not found

C:\samsungroot>adb reboot

error: device not found

C:\samsungroot>