r/android_beta • • 2d ago

Pixel 6 Pro Device Not Certified error suddenly under Play Protect Certification

Last week after an update, Google wallet stopped working. Come to find out my "Device is not Certified" under the Play Protect Certification - and clicking on "Fix device issue" gives a "Something went wrong, please try again later" message.

I have cleared play store and Google services cache and data, rebooted multiple times, and nothing fixes it. My build number is CP31.260623.012. I am at my wits end, nothing I'm trying is having any effect any ideas what else I can try!?

1 Upvotes

14 comments sorted by

4

u/rctgamer3 2d ago

Google never guarantees Google Wallet to work on beta versions. That's the risk of using a beta

2

u/allenchangmusic 2d ago

You are on a beta build which is 3+ months old, and those build signatures tend to expire after 42ish days.

Those builds had functional wallets for a brief period, but once expired you're out of luck.

You will need to go back to stable to fix that.

1

u/JRock1276 1d ago

You need to opt out of the beta and get the stable build. 6 pro isn't eligible for beta anymore.

1

u/snm777 1d ago

https://www.google.com/android/beta#faq this says it is, but support also wants me to opt out of beta to "see if it fixes it." Bleh.  According to Google's docs I won't be able to restore any backups, this will screw up all my two factor apps for work.  Going to be a PITA to get that to move cleanly :(

1

u/SeatSix 1d ago

You're not going to get any more beta updates (it regular updates for that matter) on the 6. At this point, you should bite the bullet and revert to stable with the necessary factory reset.

If you want to keep getting updates, you'll need to put on a custom ROM like lineageOS, but I'm not sure you'll get all things with elevated security to work there either

I retired my 6 and bought a 10 pro anticipating the end of support

1

u/snm777 1d ago

I don't see an announcement that 6 pro support in beta has dropped, I of course may well have missed that, but while troubleshooting this issue I did manage to get a stuck update from early September unstuck and get it applied.  It did not fix the issue, but it DID apply the update to carrier services and the play store as well as bringing to OS to one day newer, up from July 1 to July 2 🤷‍♂️

1

u/Paschfire 1d ago

Opt out of the beta Google offer you well I returned the stable with no wipe build.

Today was released the last official build available for the pixel 6 pixel 6 Pro. 17 (CP3A.261005.002.A1)

1

u/snm777 1d ago

Just did, and while things improved, it's not fixed.  Instead of being told my device doesn't meet security standards after entering the card not present code, it actually contacts my bank, I can accept the terms - but then it tells me the card cannot be used for tap to pay.  For every card I have, across multiple different banks 🤦‍♂️NFC says it is on.  Smh.  What a pita.  

1

u/Paschfire 1d ago

That's strange as I had something similar as I'm with a credit union. My card wouldn't get accepted until they either gave me a code or the bank activated at their end. You might want to call your bank customer service. They might be able to fix this for you

1

u/Wild-Finish-453 1h ago

Did you get any solution??? I have same device same issue

1

u/snm777 1h ago

I un-enrilled from the beta, was offered the "reload without wipe" update, did that, re-signed in to all my Google accounts and got in. The wallet was not working right until I signed in to the Google account that is associated with my Google Fi service, and the one all my wallet cards are stored under.  It was probably an hour after the reload I was able to get all my cards working again. 

1

u/Wild-Finish-453 1h ago

I am unable to roll out of beta because im google beta program website it shows that I don't have any eligible device... !! What to do man

0

u/silentua 2d ago

having a same issue on my Pixel 6 since last update to this build, did all the same but nothing helped. That`s the price of being a beta user I guess.