Android Pay or Pixel issue?

[Blacknight30]

I recently tried to add a card to my Android Pay app, after tapping on the add card option I get a message that says that google could not verify the device. I've sent a ticket to Android Pay support, I've also now started seeing issues with my credit union apps. I've since factory reset the deice due to other odd issues. Has anyone else seen this issue?

 

[N4Newbie]

Is your Pixel rooted?

 

[Gdraft#WN]

Android pay works much better on my pixel than it ever did on my G3.

My only issue would be when there is any kind of update, either os or Android pay. I have to reload my card.... And the bank has to verify.

Really blows when you are at the store with only your phone and it says your card has not been verified.

 

[Blacknight30]

It's not rooted.

 

[JimSmith94]

It's not rooted.

You can't have an unlocked bootloader either, unless you use a kernel that bypasses the check.

 

[anon(596177)]

I recently tried to add a card to my Android Pay app, after tapping on the add card option I get a message that says that google could not verify the device. I've sent a ticket to Android Pay support, I've also now started seeing issues with my credit union apps. I've since factory reset the deice due to other odd issues. Has anyone else seen this issue?

I'm bringing this thread back to the top of the forums because I have the exact same issue starting from around the exact time of your first post.

I last used android pay successfully on Dec 3rd, on dec 6th (the next time i tried to use it) i was getting this error. Im frustrated all to hell with it because I use android pay instead of my CCard since its faster than the chip readers.

Ive scoured the net enough now and found enough of these related posts (6 or 7 instances over the course of the last 2 weeks) to feel comfortable in thinking that this is not random hardware failure or random software corruption and that there is indeed a pattern somewhere.

For reference, I am on android build 7.1, NDE63X on a Verizon Pixel, NOT rooted, Bootloader is LOCKED and I have verified both of these things since the issue started occurring.

From the information I have gathered, this error comes up when a software verification check fails with a specific google API. The check basically verifies that you are running a non-modified or altered version of android. if it passes, you can add and use a card, if it fails, you get the warning we are experiencing now. Considering we have not altered our phones in any way, this check should not be failing.

Another app on the play store, "SafetyNet Helper Sample", allows you to run a test on the same API that android pay uses to verify your version of android is unmodified (allegedly). When I downloaded this app and ran the test, that test also FAILED. For reference, I ran this test on my old 6p as well, and on the 6p it PASSED. As far as I am aware, the 6p's android pay still functions fine, as i am able to add a card to android pay on the 6p without it throwing an error.

------ Would someone who has a pixel that android pay still IS WORKING on please download that app and verify that the test passes? I would greatly appreciate it.


Since android pay stopped working on my phone, the only modifications I have done to it is update apps.
- I noticed the google app updated on the 3rd. I uninstalled the app updates for it and tried android pay again unsuccessfully.
- To my knowledge and through my sifting through apps, no other android system app has updated since the 3rd, although its possible i may have overlooked some.


Im also curious as to whether this issue is going to affect receiving the OTA, as my phone has not updated yet and it has not received a notification that an update is available even after manual searches. I believe the OTA's rely on the same verification process to verify your OS hasnt been tampered with, right?

---- To Blackknight, or anyone else with this issue, Have you tried factory resetting and has the factory reset fixed it? I considered trying a factory reset, but a factory reset for me is an all night job to set the phone up again and i want to avoid that for as long as possible.

Any information anyone can add would be appreciated!

 

[anon(596177)]

*BUMP*

I'd really like to know the answers to my questions in my previous post if anyone could shed some light

 

[therealasd]

Pixel XL from Google Play Store, Nougat 7.1.1, Build # NMF26O, unrooted, locked Bootloader, Android Pay works, SafetyNet Helper passes.

 

[N4Newbie]

*BUMP*

I'd really like to know the answers to my questions in my previous post if anyone could shed some light

Okay, I'll bite.

I ran the SafetyNet test and it was fully successful.

I added a new credit card to AndroidPay (one that I had not previously added) and it was successful as well.

The only thing I can think of that hasn't already come up is that (at least previously) AndroidPay requires that your device be secured - that is, you must have a PIN or other lock in place.

Other than that, the only thing I can think of is that you have an app installed which is interfering...

 

[anon(596177)]

Thank you for your response. I guess I should have mentioned that I do have a pin in place, so it's not that. I definitely think it could possibly be an app that is interfering, but considering it's been less than a week since the last time it worked and I haven't installed any new apps in that time it makes it a little harder to track down.

I hate to think an app would cause that API failure. But I guess I've seen crazier things.

Thank you very much for running that test for me. That at least gives me some confirmation that if that test passes I'll be able to use Android pay again. Now all that's left is to hear from somebody who did a factory reset after having this issue and whether or not that worked for them. Id do it myself, but a factory reset takes me so much time to get the phone back to the way I want it too I don't really care to do it if it's not going to do anything for me.

 

[N4Newbie]

Thank you for your response. I guess I should have mentioned that I do have a pin in place, so it's not that. I definitely think it could possibly be an app that is interfering, but considering it's been less than a week since the last time it worked and I haven't installed any new apps in that time it makes it a little harder to track down.

I hate to think an app would cause that API failure. But I guess I've seen crazier things.

Thank you very much for running that test for me. That at least gives me some confirmation that if that test passes I'll be able to use Android pay again. Now all that's left is to hear from somebody who did a factory reset after having this issue and whether or not that worked for them. Id do it myself, but a factory reset takes me so much time to get the phone back to the way I want it too I don't really care to do it if it's not going to do anything for me.

These are just random thoughts, so take them as such:

1. Go to Settings -> Security -> Device administrators. What items are checked? On my Pixel XL, I have only Android Device Manager checked.

2. Settings -> Security. If you have "Unknown sources" enabled, try disabling it.

3. Settings -> Security -> Trusted credentials. On the System tab, I have a ton of items listed, all of which are enabled. You? On the User tab, I have nothing at all.

4. Settings -> Security -> User credentials. Mine is blank.

5. Settings -> Security -> Trust agents. I have only "Smart Lock (Google)" listed and enabled

 

[Turbod]

I had the same thing, non rooted and bootloader locked, same message. Jumped through all the hoops, factory reset, side loaded the latest update, etc... Only thing that worked was to unlock the bootloader, flash the factory image, and relock the bootloader.

 

[anon(596177)]

These are just random thoughts, so take them as such:

1. Go to Settings -> Security -> Device administrators. What items are checked? On my Pixel XL, I have only Android Device Manager checked.

2. Settings -> Security. If you have "Unknown sources" enabled, try disabling it.

3. Settings -> Security -> Trusted credentials. On the System tab, I have a ton of items listed, all of which are enabled. You? On the User tab, I have nothing at all.

4. Settings -> Security -> User credentials. Mine is blank.

5. Settings -> Security -> Trust agents. I have only "Smart Lock (Google)" listed and enabled

1. Same

2. Already disabled

3. All the same

4. Same

5. same


Thanks for checking, was worth the attempt!

I had the same thing, non rooted and bootloader locked, same message. Jumped through all the hoops, factory reset, side loaded the latest update, etc... Only thing that worked was to unlock the bootloader, flash the factory image, and relock the bootloader.

Exactly what I didnt want to hear. Verizon Pixel and im pretty sure at this point I cannot unlock the bootloader, otherwise while I would be super annoyed in having to set the phone up again at least it would be a fix.

 

[N4Newbie]

Near the end of this thread Please help me troubleshoot why Android Pay … | Google Pixel XL it is implied that it is a known bug that came with the November security update.

Question: have you received the 7.1.1 system update yet?

 

[Erik Read]

Having the exact same issue but mine didn't start until Dec 21 or 22. My last successful AP transaction was Dec 19th.
There was some type of update that happened the day it started not working.
I have a bug report going through Google now.
I really don't want to reset.
SafetyNet Helper fails on CTS checks.
My phone (Pixel XL) was bought straight from Google, not rooted, only Developer mode turned on.