We can understand why Google is now cracking down on Android Pay. As Google releases its Pixel devices, it doesn’t want people tinkering too much with an Android Pay enabled device. So the rules are simple: If your device is rooted, no Android Pay, if your device’s bootloader is unlocked, no Android Pay either, even if you haven’t modified the system at all.
A Nexus 6P owner discovered that his Android Pay was no longer working because his bootloader was unlocked. Although the phone is not rooted, this is no longer enough for Android Pay to run, the device must have a locked bootloader, and cannot be rooted either.
As Google devices are getting into the hands of not just Android enthusiasts, but also the general public, Google is more concerned about Android Pay’s security.
Allowing Android Pay to work on a rooted device or a device with an unlocked bootloader would be a serious security flaw, as any tinkerer can figure out how the system ticks and potentially steal credit card info, if this happened, it would put a scar on the payment service's reputation.
Disabling Android Pay for modified devices is the only way Google can ensure everyone’s sensitive credit card information is safe. Bummer for those who like to flash ROMs and use Android Pay, as the two can no longer occur in unison.
I have this problem on my Nexus 6P running Android 7.0 (both on NBD90X and NBD91K). Bootloader is unlocked, but it's running stock Android and is NOT rooted.
Ya this is my screenshot used here. I updated 2 days ago not thinking anything of it. I knew the pixels were to be locked down but to lock down nexus dev devices in the same way even after they have worked with Android pay for so long (as long as you...