Anyone get Android Pay and Custom ROM working on their rooted and customized Nexus 5 ?
Here are the steps I took in order to add cards and get Android Pay functioning on my phone:
- Get the Google Pay APK from here: http://www.apkmirror.com/apk/google-inc/android-pay/android-pay-1-0-102576552-android-apk-download/
- You'll also need an upgrade for Google Play Services, I was not able to get it through Apple Pay, I had to get it from here:
http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-8-1-14-2244331-238-android-apk-download/
NOTE: have to install Google Play Services that ends in 238 for the N5
Then do the following steps:
- Install Android Pay
- Install Google Play Services
- Clear Data for Android Pay
- Go into SuperSU and unroot
- setup Android Pay
- re-root using SuperSU
So this allowed me to add/manage cards in Android Pay - but some users are getting an error such as:
"MASTERCARD-XXXX can't be used with Android Pay right now " when trying to pay with their phone.
The other item I noted is that after verifying my credit card with the issuing bank - it took several hours (>8) before I received official confirmation that the card was made available for mobile payment.
I'm guessing that it may take a while before the cards are 'activated for mobile payment?
Anyone able to use Android Pay to make a payment on their N5 (rooted, Custom ROM) ?
Note: I'm running on Cataclysm and HellsCore Kernel.
I just received email confirmation from my bank that my card had been added. I did receive verbal confirmation the day I added it, but maybe it takes a few days. The problem now is that I had removed my card and re-added it this morning, before that initial email confirmation came through. Now I don't know if I need to wait for another email confirmation before trying again.
The process worked for me, but I haven't yet tried to make a payment. One note on the steps (although this is probably understood by most who would be going through the process): For re-rooting SuperSU, you may want to clarify this is done by re-installing SuperSU in recovery.
Empty Hand said:
The process worked for me, but I haven't yet tried to make a payment. One note on the steps (although this is probably understood by most who would be going through the process): For re-rooting SuperSU, you may want to clarify this is done by re-installing SuperSU in recovery.
Click to expand...
Click to collapse
All I did was turn back on "Enable Superuser" in SuperSU Free - I did not re-install SuperSu in recovery...
luigidk said:
Anyone get Android Pay and Custom ROM working on their rooted and customized Nexus 5 ?
Here are the steps I took in order to add cards and get Android Pay functioning on my phone:
- Get the Google Pay APK from here: http://www.apkmirror.com/apk/google-...-apk-download/
- You'll also need an upgrade for Google Play Services, I was not able to get it through Apple Pay, I had to get it from here:
http://www.apkmirror.com/apk/google-...-apk-download/
NOTE: have to install Google Play Services that ends in 238 for the N5
Then do the following steps:
- Install Android Pay
- Install Google Play Services
- Clear Data for Android Pay
- Go into SuperSU and unroot
- setup Android Pay
- re-root using SuperSU
So this allowed me to add/manage cards in Android Pay - but some users are getting an error such as:
"MASTERCARD-XXXX can't be used with Android Pay right now " when trying to pay with their phone.
The other item I noted is that after verifying my credit card with the issuing bank - it took several hours (>8) before I received official confirmation that the card was made available for mobile payment.
I'm guessing that it may take a while before the cards are 'activated for mobile payment?
Anyone able to use Android Pay to make a payment on their N5 (rooted, Custom ROM) ?
Note: I'm running on Cataclysm and HellsCore Kernel.
Click to expand...
Click to collapse
I'm getting that those links are broken/don't work.......
EDIT: I've had the 'Unfortunately, Google Play services has stopped' constantly with any iteration of the Google Play Services update I've downloaded. I just dl'd the 'universal' version 240 from the XDA Developers posting , everything else has worked fine but I'm still getting the service stop error. Anyone have any suggestions on how to get this message to stop? When I go to Manage Apps, there's no option to clear data/uninstall updates, only clear cache and disable (and I don't want to disable it, for sure.)
Joshmccullough said:
I'm getting that those links are broken/don't work.......
EDIT: I've had the 'Unfortunately, Google Play services has stopped' constantly with any iteration of the Google Play Services update I've downloaded. I just dl'd the 'universal' version 240 from the XDA Developers posting , everything else has worked fine but I'm still getting the service stop error. Anyone have any suggestions on how to get this message to stop? When I go to Manage Apps, there's no option to clear data/uninstall updates, only clear cache and disable (and I don't want to disable it, for sure.)
Click to expand...
Click to collapse
What device?
Nexus 5 requires either Play services -230 or -238, not -240
Sent from my Nexus 5 using Tapatalk
I fixed the links - but if they fail again - just goto http://www.apkmirror.com/ and find the latest android pay and latest google play services (ending in 238) apks - and use those.
Pure Nexus Project, tried the steps in OP as well as trying exposed modules to hide root. I also tried using bootunlocker to lock the BL and change the tamper flag to stock. Still no luck.
RoyJ said:
Pure Nexus Project, tried the steps in OP as well as trying exposed modules to hide root. I also tried using bootunlocker to lock the BL and change the tamper flag to stock. Still no luck.
Click to expand...
Click to collapse
Supposedly this Xposed module goes the extra mile, and addresses the real obstacle to Android Pay activation: the new SafetyNet API
http://repo.xposed.info/module/com.pyler.nodevicecheck
Sent from my Nexus 5 using Tapatalk
silvertrain78 said:
What device?
Nexus 5 requires either Play services -230 or -238, not -240
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, Nexus 5. I'll have to try 230, nothing else has worked so far. 240 was supposed to be a 'universal' GPServices.....I see a commenter above posted something about a new Xposed module, maybe have to give that a shot, too.
EDIT: Looks like v.238 was the trick, no Google Play Services errors so far. Now I just have to test out Android Pay somewhere.
Does anyone know if you have to somehow choose between Android Pay and Google Wallet when using NFC payment at a terminal?
Joshmccullough said:
Yeah, Nexus 5. I'll have to try 230, nothing else has worked so far. 240 was supposed to be a 'universal' GPServices.....I see a commenter above posted something about a new Xposed module, maybe have to give that a shot, too.
EDIT: Looks like v.238 was the trick, no Google Play Services errors so far. Now I just have to test out Android Pay somewhere.
Does anyone know if you have to somehow choose between Android Pay and Google Wallet when using NFC payment at a terminal?
Click to expand...
Click to collapse
Glad you got it set. FYI, for Nexus 5 the -230 Play services is universal DPI.
I'm pretty sure at the pos terminal you'll only be able to use Android Pay. It has completely assumed all duties of the old Wallet. If you have a Google Wallet physical card you can add it as an option for Pay, but otherwise Wallet is now just for p2p transactions (like PayPal).
Sent from my Nexus 5 using Tapatalk
silvertrain78 said:
Glad you got it set. FYI, for Nexus 5 the -230 Play services is universal DPI.
I'm pretty sure at the pos terminal you'll only be able to use Android Pay. It has completely assumed all duties of the old Wallet. If you have a Google Wallet physical card you can add it as an option for Pay, but otherwise Wallet is now just for p2p transactions (like PayPal).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Has any one been able to get Android pay to work at a pos?
Sent from my LG-V510 using Tapatalk
silvertrain78 said:
Supposedly this Xposed module goes the extra mile, and addresses the real obstacle to Android Pay activation: the new SafetyNet API
http://repo.xposed.info/module/com.pyler.nodevicecheck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sadly, this still doesn't work.
silvertrain78 said:
What device?
Nexus 5 requires either Play services -230 or -238, not -240
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, Nexus 5. Got it fixed and working as noted above, just needed the right Google Play Services update and then the instructions in the OP worked like a charm.
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
silvertrain78 said:
Glad you got it set. FYI, for Nexus 5 the -230 Play services is universal DPI.
I'm pretty sure at the pos terminal you'll only be able to use Android Pay. It has completely assumed all duties of the old Wallet. If you have a Google Wallet physical card you can add it as an option for Pay, but otherwise Wallet is now just for p2p transactions (like PayPal).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I just noticed that the old Google Wallet app was auto-removed at some point from my phone (I had both for a while), now I've just got Android Pay and Google Wallet, so that makes complete sense.
FWIW, when I tried adding my Google Wallet card to Android Pay, I initially got the 'you can't use this on your phone'/root error; just unrooted through SU, added the card, re-rooted, no message. I just have to test it out on a POS terminal somewhere and see how it flies.
Joshmccullough said:
Yeah, Nexus 5. Got it fixed and working as noted above, just needed the right Google Play Services update and then the instructions in the OP worked like a charm.
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
I just noticed that the old Google Wallet app was auto-removed at some point from my phone (I had both for a while), now I've just got Android Pay and Google Wallet, so that makes complete sense.
FWIW, when I tried adding my Google Wallet card to Android Pay, I initially got the 'you can't use this on your phone'/root error; just unrooted through SU, added the card, re-rooted, no message. I just have to test it out on a POS terminal somewhere and see how it flies.
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Nexus 5 using Tapatalk
Not working at POS
Finally had an opportunity to use Android Pay at a Whole Foods POS.
Touched my phone to the card reader - and Android Pay popped up - with my default credit card.
Then - I got the dreaded: "Visa-xxxx can't work with Android Pay right now" message.
Seems this is a common issue - so it looks like we'll have to wait a bit for this to work.
I'll continue to try it at places that accept Android Pay - and will update accordingly.
NOTE: one thing was apparent... for me the experience of using my phone to pay - is no better an experience (probably more clunky) - than merely swiping my credit card - which I can probably get out of my pocket and swipe, faster than getting out my phone, unlocking it and positioning it on the reader.
Perhaps the security promises with Android Pay will trump a mag stripe card... but from a user experience standpoint... not that great.
silvertrain78 said:
What ROM are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Cataclysm ROM, most recent version.
---------- Post added at 04:40 PM ---------- Previous post was at 04:37 PM ----------
luigidk said:
Finally had an opportunity to use Android Pay at a Whole Foods POS.
Touched my phone to the card reader - and Android Pay popped up - with my default credit card.
Then - I got the dreaded: "Visa-xxxx can't work with Android Pay right now" message.
Seems this is a common issue - so it looks like we'll have to wait a bit for this to work.
I'll continue to try it at places that accept Android Pay - and will update accordingly.
NOTE: one thing was apparent... for me the experience of using my phone to pay - is no better an experience (probably more clunky) - than merely swiping my credit card - which I can probably get out of my pocket and swipe, faster than getting out my phone, unlocking it and positioning it on the reader.
Perhaps the security promises with Android Pay will trump a mag stripe card... but from a user experience standpoint... not that great.
Click to expand...
Click to collapse
Are you rooted, hence the 'didn't work' problem, or it's just plain not working right now?
Yeah, I've putzed around with the original Google Wallet/NFC payment a few times and I found the same thing was true: it's about as much hassle, maybe even more, as using a regular credit or debit card. At least with the cards you know they're going to work, barring some major snafu; with Google Wallet/Android Pay, maybe the place you're at doesn't accept it as payment, maybe the card vendor isn't on-board with Android Pay yet, maybe your phone's rooted and it doesn't work to begin with, etc. I like the idea of having multiple cards available to use with Google Pay, so I can choose which one I want to use at any given time, but I think there's also a lot of barriers to making phone-based payment the default method of payment for people.
EDIT: Well, initial swing and a miss; I had my Google Wallet card set as the default card to use with Android Pay, and got a message saying that the Google Wallet card wasn't able to be used with Android Pay at this time. I was at McDonald's for lunch and if there wasn't a big line behind me I'd have taken time to switch cards and try again, but as it was I froze up and just went with a physical card. I didn't get a 'you're using a rooted phone, you hAxx0rZ!!!! Stop trying to overthrow capitalism and steal Bitcoins, anarchist!!!' error message, at least, so that's a good thing.
Doing more research on this - there seems to be strong evidence that Android Pay won't work on a rooted/custom rom phone.
Lots of speculation as to whether it is related to an unlocked bootloader, root, custom rom, or some combination...
Has anyone tried this on vanilla N5 ?
I'm using stock and I have play services 238 the latest one and Android pay still says "Google play services have stopped" what do I do?
Here's a thought: maybe it's a server-side activation, and that's why it doesn't work for rooted users who temporarily disable superuser when attempting to add a card?
That's the only thing I can think to explain why some users are able to unroot and flip the switch, while others can't
Sent from my Nexus 5 using Tapatalk
Related
So I sent google play an email stating that an app I already paid for (3g watchdog) is showing up as unpaid, gave them my order receipt and they asked for more information so I sent them this.
Allright, I flash New roms to my phone all the time. Normally I just re download all my apps as I switch between gingerbread and ice cream sandwich so I can't use titanium backup. So I flashed a new Rom (ics os) and the app appeared as bought, I clicked download and the market updated to play store during that and the download froze. So I force stopped it and brought up play store again. This time the app appeared as purchase 2.99 . I thought it was the os I was using so I formatted and flashed a gb Rom. Went to download again this time it sai purchase so I went about agreeing to purchase it again to see if it was just a glitch or something. It didn't work it went about charging me but my cc is maxed so I didn't get charged. I contacted the 3g watchdog dev and he said he could refund me just to let him know as he said he found a valid payment record. I can't get refunded because my cc is maxed and I wouldn't be able to purchase it again as payment would not be available which is why I need your help.
The following response came after a week of me sending emails requesting a response.
Thanks for following up and for providing those additional details about the issue you're experiencing on Google Play. In reviewing the information you've provided as well as our records, it appears that this issue is related to the fact that you're not using the authorized ROM that came with your device.
Using any ROM besides the factory default may cause the device to have limited functionality and may cause unexpected behavior with the Google Play Store app. Unfortunately, we won't be able to troubleshoot this issue further because the issue appears to be unique to the way your device is configured, and we can't recreate the issue with our devices here.
To resolve the issue, I recommend using the authorized Android operating system provided by your manufacturer that can be obtained from their website or your carrier.
Regards,
Matt The Google Play Support Team
Seems like google play is jerking me around an awful lot for 2.99. What shall I say to these jerkoffs?
My main gripe with Google Play:
It should remove apps where the developers offer no support for it. Think about all the camera apps and stuff that that that have corks and errors that make them not work on said devices.
MR4Y said:
My main gripe with Google Play:
It should remove apps where the developers offer no support for it. Think about all the camera apps and stuff that that that have corks and errors that make them not work on said devices.
Click to expand...
Click to collapse
Conversing back and forth with them makes me feel like they want me to go f*** myself. I could see how they don't care if you buy a crap app with no support as its an outright money grab with Google's commission.
Sent from my Incredible S using xda premium
I'm not sure where you're having problems simply using Titanium. I switch back and fourth between GB and ICS and use TiBu to batch restore my apps with data and haven't had any problems.
MissionImprobable said:
I'm not sure where you're having problems simply using Titanium. I switch back and fourth between GB and ICS and use TiBu to batch restore my apps with data and haven't had any problems.
Click to expand...
Click to collapse
You're right. Titanium Backup is a useful application. Must have application for rooted phone.
Just sync up a valid, active debit or credit card to your google account and let the dev refund the money so you can repurchase it. You told google that you tweaked your software and now they have an excuse not to help you out.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Other backup tools
View this thread for other backup tools http://forum.xda-developers.com/showthread.php?t=1715955
Hi all,
I have Google Wallet Tap & Pay set up and selected under the settings, despite this nothing really happens when I try to make payments using this. I am on Android 4.4.4 (CM11 Nightly, and Carbon before this), NFC was on and I've tried this at several locations by now.
Before when Tap & Pay didn't work on Verizon I never even got the option to set it up, and but I was under the impression that it did work now. How do I get it to work?
Thanks !!
Google Wallet Tap and Pay No Freaking Worky!!!
GrinReaper said:
Hi all,
I have Google Wallet Tap & Pay set up and selected under the settings, despite this nothing really happens when I try to make payments using this. I am on Android 4.4.4 (CM11 Nightly, and Carbon before this), NFC was on and I've tried this at several locations by now.
Before when Tap & Pay didn't work on Verizon I never even got the option to set it up, and but I was under the impression that it did work now. How do I get it to work?
Thanks !!
Click to expand...
Click to collapse
The issue is that Google does not support custom roms, with KitKat they stopped doing so. I have the same issue you have I am running ATT S3 and the version of wallet my phone is allowed to download is wallet V2.0-r163-v1--release. After talking to Wallet support they said my phone was suppose to have Wallet v.2.0-r172-v6. My guess is that even though my current version allows you to set up tap and pay, it at the same time does not turn on the NFC feature for wallet to recognize the credit card terminal. The NFC is suppose to be used as the triggering device to tell the HCE to listen for transaction information. HCE is software based so it has no hardware to tell it when to process, so it needs NFC to tell it to do so.
Please can someone share wallet v2.0-R172-v6 I would like to try loading it directly to see if that may work.
I have the same version (v18 rather than v1 though)
This is an interesting bit of information, I wonder if the same version works for vzw.
terrylbs said:
The issue is that Google does not support custom roms, with KitKat they stopped doing so. I have the same issue you have I am running ATT S3 and the version of wallet my phone is allowed to download is wallet V2.0-r163-v1--release. After talking to Wallet support they said my phone was suppose to have Wallet v.2.0-r172-v6. My guess is that even though my current version allows you to set up tap and pay, it at the same time does not turn on the NFC feature for wallet to recognize the credit card terminal. The NFC is suppose to be used as the triggering device to tell the HCE to listen for transaction information. HCE is software based so it has no hardware to tell it when to process, so it needs NFC to tell it to do so.
Please can someone share wallet v2.0-R172-v6 I would like to try loading it directly to see if that may work.
Click to expand...
Click to collapse
The version you mention was pushed to my phone today as an update. Haven't tried it yet.
New Google Wallet Update v2.0-R172-v18-RELEASE
GrinReaper said:
The version you mention was pushed to my phone today as an update. Haven't tried it yet.
Click to expand...
Click to collapse
Thanks for the heads up I too have received the update listed above yesterday but have not tried it yet. I will post results later today. I have had broken hope so many times now I think I would **** in my pants if it did work.
Also just a note the update has brought back gift cards in which they removed for a while. The UI is also more streamlined.
Please if this update works for anyone please post.
Thanks..
New Google Wallet Update v2.0-R172-v18-RELEASE Clearly CM 11 issue!
terrylbs said:
Thanks for the heads up I too have received the update listed above yesterday but have not tried it yet. I will post results later today. I have had broken hope so many times now I think I would **** in my pants if it did work.
Also just a note the update has brought back gift cards in which they removed for a while. The UI is also more streamlined.
Please if this update works for anyone please post.
Thanks..
Click to expand...
Click to collapse
I just confirmed that new release Google Wallet Update v2.0-R172-v18-RELEASE does not work at check out. Terminal is not recognized. This is clearly a CM 11 issue. I am running AT&T S3 there is a factory update for my phone that is compatible with google wallet. my guess is that CM is slacking on the S3 as they combined multiple phone to one release and stable version as of yet coming upon a year now, snapshots and nightlies only.
CyanogenMod please fix Google Wallet HCE support for S3 ATT! NFC is not detecting HCE transaction.
Hi, this problem isn't related to Android or Google Wallet version. There is carrier and device restrictions:
http://www.androidcentral.com/google-wallet-tap-and-pay-can-work-any-android-44-device-still-requires-us-sim
All,
As you know Andorid Pay is being pushed out, and replacing Wallet. What everyone might not know is that Android Pay will NOT allow you to ADD cards while rooted. Also, once cards are added and tap and pay is used , there is a ggood chance you will get a message that says something like "Visa-xxxx can't work with Android Pay right now" message.
When attempting to go back to Wallet from TIBu it was still trying to use Android Pay in the NFC settings as well
I would like to share some tricks I discovered on how to add you cards to a custom ROM/rooted device and if your cards do not work on NFC to get Wallet working again
1) go to your SU app and under SU settings UN-TICK Enable Super User
2) install Android Pay from the Pay store
3) add your cards ( they should be carried over from Wallet)
4) Re-enable Super User in the SU app setting
You do not have to enable the device manager and you WILL have to set up lock screen PIN
Now IF your card(s) DO NOT work then you might try using your google wallet card that you can have them send you ( have not added mine as I dont have it at work ) and see if you can make tap and pay purchases with that card.
If you just want to go back to wallet you must Uninstall tap and pay AND delete /data/data/com.google.android.gms I rebooted but might not have to, and then restored the original Wallet from TiBu and everything should work fine, at least for me.
Just went to the vending machine and tested.. worked.
Hopefully this helps some people and saves them some frustration.
Best Regards
UPDATE: 9-22-2015
Just successfully added my Google wallet Credit card ( well prepay ) to Andorid pay and it says that I can't use that card to pay!
WTF GOOGLE! YOU ARE GETTING TO BE USELESS!
To Anyone thinking of switching to Android Pay, DON'T, keep using wallet , it just works!
I couldn't get Pay to work on Adrenaline 2.4. Tried all kinds of suggestions. Still get, "Android Pay cannot be used. Google is unable to verify that your device or the software running on it is Android compatible"
Andorid Pay works with SuperSU 1.71
Android pay currently works with the beta version of SuperSU 1.71
I added my card without error and successfully used it at the vending machine twice at the office.
You must set a lock screen up on your device however.
Still not working for me. Must have something to do with the SuperSU version I'm using (SuperSU Free v2.65).
Drunkula said:
Still not working for me. Must have something to do with the SuperSU version I'm using (SuperSU Free v2.65).
Click to expand...
Click to collapse
I clearly said 1.72, and I even provided a link in my last post
Yes you did. But I've also seen various (imposters?) versions of SuperSU floating around before. I wasn't going to speculate on the reason for the large difference in versions mentioned. But it is a moot point, so I digress...
Drunkula said:
Yes you did. But I've also seen various (imposters?) versions of SuperSU floating around before. I wasn't going to speculate on the reason for the large difference in versions mentioned. But it is a moot point, so I digress...
Click to expand...
Click to collapse
Yea.. But.. He linked you directly to Chainfires official thread. Lol.
carm01 said:
I clearly said 1.72, and I even provided a link in my last post
Click to expand...
Click to collapse
Nah-uh, you said 1.71
I found this link on YouTube where a user explains how to certify the Mate 30 Pro by Google in the Play Store app. I tried this method 1 month ago and although at the beginning the phrase "uncertified device" disappeared from the Play Store, days later the Play Store app showed me that "my device is not certified", so I think it does not work .
Does anyone used this method that explains this YouTube user?
luisvalino said:
Does anyone used this method that explains this YouTube user?
Click to expand...
Click to collapse
its works for some not for all
https://www.gizchina.com/2020/02/26/how-to-install-google-apps-on-huawei-phones-a-new-method/
This works!
After testing every method i found here or on youtube im very skeptical. Its very exhausting to try these methods, praying to get only Google Services and all you get are that SPAM-like Pop ups from Google about not having an cerified device.
I bought my Mate 30 pro on the 2nd of March.
Build 10.0.0.193 and LIO L29. Kernel is 4.14.116.
Maybe its because im german
Well, does anyone tested this method?
CommandoALF said:
After testing every method i found here or on youtube im very skeptical. Its very exhausting to try these methods, praying to get only Google Services and all you get are that SPAM-like Pop ups from Google about not having an cerified device.
I bought my Mate 30 pro on the 2nd of March.
Build 10.0.0.193 and LIO L29. Kernel is 4.14.116.
Maybe its because im german
Well, does anyone tested this method?
Click to expand...
Click to collapse
i tried and was able to install with " Not Certified" error, the trick is Install GMS through any method with DATA and Wifi turned off
install GMAIL using apk file rather than play store, after installing apk reboot and turn data on, log in gmail account using Gmail app and then open play store..... you will be able to install everything you want
You can download Gmail apk from here: https://www.apkmirror.com/apk/google-inc/gmail/
What method to install GMS you use?
guyluvsgals said:
i tried and was able to install with " Not Certified" error, the trick is Install GMS through any method with DATA and Wifi turned off
install GMAIL using apk file rather than play store, after installing apk reboot and turn data on, log in gmail account using Gmail app and then open play store..... you will be able to install everything you want
You can download Gmail apk from ...
Click to expand...
Click to collapse
How do you install GMS without data? What method you use? I can't install GMS with data off, whatever I do, it asks for data.
If you save files in usb type c flashdrive or download to pc and set usb transfer files. No need data, wireless.
This link https://www.google.com/android/uncertified/ where they do the certification is very misleading. When you register in theory it should be fine, but what happens is that Google reviews those registrations and decides which ones to allow. So it doesn't matter if you added your play store ID and clicked Register. I got this information from Google support, because I was asking them quite some times to explain why this service for certification does not work and what is its purpose. They told me that they review those requests in order to allow the certification. They could at least give some feedback on their system showing the registrations status - pending, rejected, successful.
I guess they don't care how many paying customers they will lose when they reject the phones and remove the possibility of even adding them manually.
xchatter said:
This link https://www.google.com/android/uncertified/ where they do the certification is very misleading. When you register in theory it should be fine, but what happens is that Google reviews those registrations and decides which ones to allow. So it doesn't matter if you added your play store ID and clicked Register. I got this information from Google support, because I was asking them quite some times to explain why this service for certification does not work and what is its purpose. They told me that they review those requests in order to allow the certification. They could at least give some feedback on their system showing the registrations status - pending, rejected, successful.
I guess they don't care how many paying customers they will lose when they reject the phones and remove the possibility of even adding them manually.
Click to expand...
Click to collapse
They only started doing these reviews recently. My Mate 30 pro is running GMS without any problem except for the google pay and netflix stuff not working. I had GMS installed on my Mate 30 pro early January...
cfds said:
They only started doing these reviews recently. My Mate 30 pro is running GMS without any problem except for the google pay and netflix stuff not working. I had GMS installed on my Mate 30 pro early January...
Click to expand...
Click to collapse
Lucky guy then!
well, everything works on my mate 30 pro. coo
Device doesn't meet security requirements
Is your device rooted or do you have adb enabled? If the device is rooted you need to do some things to hide it. If your device is not rooted, maybe check to make sure adb is disabled.
Like the comment above says, if you're rooted with Magisk, install this and it should start working fine after wiping the app.
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Adding on to this just because it's about Google Wallet...
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Curiousn00b said:
Like the comment above says, if you're rooted with Magisk, install this and it should start working fine after wiping the app.
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Adding on to this just because it's about Google Wallet...
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Click to expand...
Click to collapse
Wallet is the successor to Pay. They just haven't removed the old app
synesthete said:
Is your device rooted or do you have adb enabled? If the device is rooted you need to do some things to hide it. If your device is not rooted, maybe check to make sure adb is disabled.
Click to expand...
Click to collapse
I am currently rooted I am able to pass safety net I also have hide google wallet in magisk
highgrade said:
Device doesn't meet security requirements
Click to expand...
Click to collapse
Is this when you're trying to pay with Wallet or just setting up the app?
If it's while trying to pay, it might be because you unlocked your phone via face unlock before paying. You might have to unlock with the fingerprint scanner to make sure it works.
Might not be your issue here and I hate to say it but man, the fact that this is an issue at all makes me mad, for any regular user such an error would make absolutely no sense, and you would never understand it unless someone tells you.
highgrade said:
I am currently rooted I am able to pass safety net I also have hide google wallet in magisk
Click to expand...
Click to collapse
I am rooted and wallet is working. Here is how I have set mine up:
Magisk installed:
Zygisk enabled
Enforce Denylist enabled
Denylist blocking: Wallet, Pay, Google Play Services, and some other banking apps.
Install the Safetynet Fix module from this post: https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
Then install the MagiskHidePropsConfig module. (No need to configure it).
Force quit Wallet and wipe its data.
For quite and wiped data for Google Play Services.
Reboot
Then added card.
Those were the only modules that I needed. Maybe disable anything else you don't need while doing this in case they conflict.
JakeDHS07 said:
Wallet is the successor to Pay. They just haven't removed the old app
Click to expand...
Click to collapse
I think Pay has transitioned to being an app to send money to friends/family/etc like Venmo. I haven't used it since its split with Wallet, though.
Curiousn00b said:
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Click to expand...
Click to collapse
JakeDHS07 said:
Wallet is the successor to Pay. They just haven't removed the old app
Click to expand...
Click to collapse
As I understand it, Wallet holds all your "cards" like loyalty cards, gift cards, and transportation passes (metro, train, bus) -- hence "wallet" -- while GPay handles the credit cards for transactions for in-store/shops.
I guess Wallet is the app while GPay might be classified as the process...
Also...
synesthete said:
I think Pay has transitioned to being an app to send money to friends/family/etc like Venmo. I haven't used it since its split with Wallet, though.
Click to expand...
Click to collapse
Yes I noticed that GPay is transitioning to be like Venmo. I haven't used GPay in a long time, but since setting it up on my P7P, it was pushing hard to set things up so I could "easily send/receive payments to my family & friends" (like Venmo, i imagine...)...
simplepinoi177 said:
As I understand it, Wallet holds all your "cards" like loyalty cards, gift cards, and transportation passes (metro, train, bus) -- hence "wallet" -- while GPay handles the credit cards for transactions for in-store/shops.
I guess Wallet is the app while GPay might be classified as the process...
Click to expand...
Click to collapse
Just an FYI, but Wallet is just a part of GPay. What @Curiousn00b had said earlier in this thread is correct. GPay can do everything that Google Wallet does - and more. So therefore, GPay can handle credit cards, debit cards, gift cards, loyalty cards, transit passes, tickets, etc.
The reason why Google has released the Google Wallet app - an app specifically for adding your payment cards, transit cards, loyalty cards, etc - is because a large swarm of people were complaining about GPay being too difficult to use (as the newer features were seemingly confusing to the less tech-knowledgeable folks - which is still around 75-80% of the global population). Google had announced this publicly on a blog post around 1-2 years ago.
highgrade said:
Device doesn't meet security requirements
Click to expand...
Click to collapse
Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
SafetyNet
Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!
efkosk said:
Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!
Click to expand...
Click to collapse
I have Play Store, GPay, and Google Wallet on the DenyList and don't have this error.
And yes, Google can easily decide one day to bypass the DenyList or force hardware attestation at which point you would have to choose between your apps and root. It's been a whack a mole game for awhile now and that's just expected to become worse.
EtherealRemnant said:
I have Play Store, GPay, and Google Wallet on the DenyList and don't have this error.
And yes, Google can easily decide one day to bypass the DenyList or force hardware attestation at which point you would have to choose between your apps and root. It's been a whack a mole game for awhile now and that's just expected to become worse.
Click to expand...
Click to collapse
Thanks!
In the meantime, I cleaned the google play cache storage, added the cards again. I haven't received a bad notification yet
Do I understand correctly that at any time without any action on my part (update app, updateOS) my bank apps, gpay can stop working due to root?
efkosk said:
Thanks!
In the meantime, I cleaned the google play cache storage, added the cards again. I haven't received a bad notification yet
Do I understand correctly that at any time without any action on my part (update app, updateOS) my bank apps, gpay can stop working due to root?
Click to expand...
Click to collapse
If you turn off updates, it's extremely unlikely that it would change, but you're also taking added risk when it comes to exploits and I wouldn't recommend this path.
are we talking about an application or OS update?
If it can stop working for me after the next OS update (via pixelflasher, for example), then that is acceptable for me.
But if it can happen to me after an automatic update of the application via Google Play, it's a problem.
Sorry for possibly stupid questions, I'm trying to understand how it works.
Thank you very much for your help and giving of your time.
efkosk said:
are we talking about an application or OS update?
If it can stop working for me after the next OS update (via pixelflasher, for example), then that is acceptable for me.
But if it can happen to me after an automatic update of the application via Google Play, it's a problem.
Sorry for possibly stupid questions, I'm trying to understand how it works.
Thank you very much for your help and giving of your time.
Click to expand...
Click to collapse
Either can happen. There are ways to detect root that get past our attempts to hide it as it is so an app update can add further detection easily. Just ask my Security Service Federal Credit Union app that won't even open on a rooted phone no matter what I do.
Can I "quickly unroot" it by uninstalling magisk? Does it wipe my data? I want rooted, but I need planB in a crisis situation.
Thx for your reply!
Users with root are not afraid of the situation that they ask for a bill in a restaurant and Gpay won't work for them?
efkosk said:
Can I "quickly unroot" it by uninstalling magisk? Does it wipe my data? I want rooted, but I need planB in a crisis situation.
Thx for your reply!
Users with root are not afraid of the situation that they ask for a bill in a restaurant and Gpay won't work for them?
Click to expand...
Click to collapse
Unfortunately removing root just exposes the unlocked bootloader and GPay won't work with that condition either. It's why I rooted in the first place so I could pass SafetyNet again as Discover is 5% with mobile wallet this quarter.
I carry credit cards with me everywhere I go. It's only recently I've started using tap to pay as it wasn't really available in the Denver area. Even now I can only thing of a couple places that take it - namely the liquor store I go to with my husband lol. Interestingly I went to Dollar Tree yesterday and they have added it.
So if I want to unroot, I will lose data, because after re-locking the bootloader, the data is wiped. I'm right?
efkosk said:
So if I want to unroot, I will lose data, because after re-locking the bootloader, the data is wiped. I'm right?
Click to expand...
Click to collapse
Correct. Honestly I wouldn't say you're at immediate risk of having an issue and that dumping root and all that just for a remote possibility isn't worth it.
You can also turn off automatic app updates for the individual apps in the Play Store. As long as you leave automatic updates on for the rest of your apps, the ones you disable individually will just be sitting there showing updates and you can choose to update them when you're ready.