I've been using suhide 0.53 successfully for a few weeks, though it appears the SafetyNet API was updated today. Minutes ago, specifically. Can anyone confirm this? I was passing successfully before, but now am getting response payload validation failed. One other person I know using suhide is now getting the same (was working before), so I was figuring SafetyNet was updated. We are both using systemless xposed (v86.2). When I disable xposed, I'm still getting the same error message. Didn't try fully uninstalling it, nor did I try a clean flash with systemless root and without xposed.
Wasn't sure how / where to see any changes to SafetyNet to confirm further on my own.
Appreciate it!
Same here with the new Magisk solution. No longer working.Can confirm. Using SuperSU 2.78 SR1 with suhide 0.53 fails SafetyNet as of this morning.
Check if your selinux is enfocingCM13 + supersu + suhide + xposed systemless i get safetynet check failed. Since 30 mins ago.
CM13 + supersu + suhide + xposed systemless i get safetynet check failed. Since 30 mins ago.
Check if your selinux is enfocing
Enviado desde mi Moto G mediante Tapatalk
Actually, you need enforcing for make work safety netI don't think SELinux affects it, at least with my setup. Both permissive & enforcing still fail SafetyNet for me.
Nexus 6
Resurrection Remix 5.7.4
B14CKB1RD Kernel
SuperSU v2.78 SR1
suhide 0.53
Systemless xposed v86.2
[...] it appears the SafetyNet API was updated today. Minutes ago, specifically. Can anyone confirm this? I was passing successfully before, but now am getting response payload validation failed.[...]
echo '#!/su/bin/sush\nmount -o rw,remount rootfs /\nchmod 0751 /\nmount -o ro,remount rootfs /'>/su/su.d/06suhide; chmod 0700 /su/su.d/06suhide