Google as of late updated the SafetyNet API to recognize and block bootloader unlocked devices from using Android Pay. And it’s accessible for all App developers to exploit if they need to impair rooted users from using their administrations.
What this implies is you can never again use apparatuses like Magisk or suHide. Which we used to hide root access on your device and use Android Pay. The SafetyNet API now checks your device’ bootloader status using the verified boot highlight that Google presented with Android 4.4 KitKat.
In any case, fortunately, people over at xda as of now have a workaround. That is to sidestep SafetyNet’s opened bootloader check and use Android Pay on a device with opened bootloader and root. All gratitude to developer Sultanxda.
To hide the opened bootloader from SafetyNet API, Sultanxda evacuated support for verified boot banner from his modified part. Which gives the SafetyNet API a feeling that the device doesn’t bolster the verified boot highlight and consequently enable it to breeze through the test.
Also See: Sprint releases Stagefright fix for Galaxy S6, S6 edge, S5, Note edge, Nexus 5 and Nexus 6
In this way, what you have to do to get Android Pay to work with the unlocked bootloader on your Android device. It is located an exclusively/modified piece which doesn’t bolster verified boot. And then flash it to your device to sidestep SafetyNet check. Along these lines, you can keep on using Android Pay with root using the traps you’ve used already to hide root from Android Pay.
We’ll update this post with a rundown of custom pieces with verified boot bolster evacuated for the same number of devices as we can discover. If you know of any, do tell us in the remarks segment beneath.
Via: XDA
