Hello everyone!
Since I installed the new Android 10 Open Beta 1, I can no longer associate credit cards with Google Pay.
I state that I only have the bootloader unlocked, for future use, when interesting kernels or mod Magisk will come out useful.
I have the following error message:
"Couldn't finish setup to pay in stores - This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I find the absurd thing, since with Android 9 stable I had the bootloader unlocked, root access and custom kernels.
Everything worked properly.
Some idea?
Do you have the same problem?
Thanks in advance!
I have experienced a similar problem with Pokémon Go, which I suppose uses SafetyNet to detect root etc. Hasn't that been the case with Google Pay too? So if both Pokémon Go and Google Pay refuse to work and both uses SafetyNet as "protection"-service, maybe that means that there's an error regarding SafetyNet on the Open Beta 1?
it was installed without my permission there is no app it seems but if you type covid-19 in search it may pop up on some people phones in the uk not sure when or how it got installed and cant seem to remove it from my device yet was wondering if anyone can figure out how to
opjuice said:
it was installed without my permission there is no app it seems but if you type covid-19 in search it may pop up on some people phones in the uk not sure when or how it got installed and cant seem to remove it from my device yet was wondering if anyone can figure out how to
Click to expand...
Click to collapse
It's linked to Google play services, But my understanding it is just the API service and does nothing without a covid tracker app so it should be save to keep it unless someone can chime in with more info.
The only way to get rid of it is to delete Google Play Services. That's how they snuck it in. On Android Pie it's simple. Just debloat via ADB using pm list packages prompt and voila! it's gone. On Android 10 it works the same EXCEPT none of the google apps, firefox, instacart, or anything like that will WORK. So you can de-google all you want - they've baked it into everything. It's something I'm struggling with now since I was forced to upgrade.
I got a few of questions regarding the current state of using Google services on the P40-series devices to make sure my understanding of the situation is up to date (I'm specifically using P40 Lite but my guess is all this applies to any P40 device):
What did I actually do to the phone currently? - I keep reading about multiple methods to get things working, mentioning freezes and other modifications, so I want to know what exactly I did myself. To get the phone working on my side, I went through a firmware downgrade, then installed Googlefier and went through the steps in it. Is this the freeze-thing that people mention or is it something completely different?
As far as I understand, we have currently only 2 options, would this be a correct way to describe them?:
Googlefier - to allow logging in Google accounts, use of Google apps however with non-working notifications (and notification delays)
MicroG - resolves all/almost all notification issues however no use of Google account/apps is possible
Updating the Google Play Services the normal way through Google Play Store is pretty much not possible, is that correct?
As far as I understand, if a factory reset is performed on a phone that previously had Googlefier installed and working, re-installing it will not require a firmware downgrade (only installing Googlefier and setting it up will be needed, not a whole downgrade again). If that is correct, is there a way to fully restore a stock firmware that would leave the phone in its factory state?
Any information or clarifications would definitely be welcome.
I just wanted to make sure the information I have is up to date since there are so many things floating around and a lot of them appear to be very outdated.
I have the same questions, I just bought a P40 pro, and don't really now what to do, to solve this problem
Gato.evolution said:
I have the same questions, I just bought a P40 pro, and don't really now what to do, to solve this problem
Click to expand...
Click to collapse
I didn't ask anything regarding a problem, I just want to know what type of workaround the method I used was along with a few general questions, I'm not actually asking how to get something working (other than notifications in some apps, everything else is fine on my end).
So googlefier was a package of apps that simplified the process of downloading and installing multiple apks manually. The app that it came with is lzplay and it becomes a device admin.
I don't know much past that, but how did you get most notifications to work?
I just bought a P40 pro last week and working on exploring best option going forward too
Googlefier is actually a wrapper work which eventually uses LZPlay to get the job done. B/c of the limitations in LZPlay, people need to get P40 phones downgrade to an old firmware so that LZPlay could work - I find it not really possible as I couldn't find the correct firmware for my P40 pro now (maybe it's b/c of my region ... )
Then recently there is DualSpace, haven't tried it but looks like an easy go
It looks like a method of separating a new user/app space (sounds like a VM on a physical computer sort of concept ?)
Google actually has very similar thing called "work profile" I remember that can setup a personal as well as a work related dual accounts on same phone and the data space are separate also allows diff. security policies
Work profiles | Android Developers
Learn how to make sure your apps operate smoothly in a corporate environment by following some best practices.
developer.android.com
ykjae said:
So googlefier was a package of apps that simplified the process of downloading and installing multiple apks manually. The app that it came with is lzplay and it becomes a device admin.
I don't know much past that, but how did you get most notifications to work?
Click to expand...
Click to collapse
No clue, they just work on my side, only did a downgrade followed by the Googlefier process and then update to the latest security patch.
Google Play Services version is highly out of date though (v20.09.13).
Anyway, could still use information on my original questions.
@CrisR82
I can tell you if you factory reset the device it would just wipe it. Which in theory should leave it at its current software firmware version. So no you wouldn't need to downgrade again. (Unless you upgraded after getting Google services to work)
I also got most of everything working perfectly now. But I decided to freeze gsf with icebox so I could get all notifications.
It's actually not bad. I was able to find all apps that I use on Huawei app store and if not I then use apkpure or aurora.
Hi,
First sorry for this vague post. I am on Android since 2012. During 2012-2014 I used to try out lots of custom ROMs as I was in college and I had mobile like Samsung Galaxy S3 and then later Nexus and the OEM abandoned the updates after a while. After that I started working and since then have been on multiple Google line of devices, first Nexus and now my latest is Pixel3. I am generally happy with the phone. However, my Pixel3 stopped receiving updates I started thinking why I should dump this and buy a new one when it's perfectly working fine for my need.
I just came to this site after like ages to see what is the current status of custom ROMs. It seems overwhelmingly new now. I remember back then we had some sharp edges and something or other didn't work. Since then I am more into google ecosystem now. I use google Fi for phone. I like and use most of the google feature. So just wondering what will I lose by moving to custom ROM and am I ready to live without those features or should I just accept that I will not have any updates and if I need the updates I will have to buy a new phone.
I am not much interested into rooting and gaining advanced controls or doing anything extra nerdy. I will be perfectly happy with just getting the security patches and whatever feature is there if they keep working.
1. what are some good custom ROMs popular these days?
2. What are the things I'd lose moving to custom ROM?
3. Does all hardware for ex: Finger print, NFC work?
4. What about google apps, I mostly like all google app like camera, google pay, phone, play store
5. I like the google specific features like call screening and google assistance, google feed. I guess I will lose those.
6. I also use google Fi, can I still use that seamlessly or is there any gotchas I need to be aware of?
7. Is there any other way to keep my phone Googlized and receive security updates. It is totally acceptable if I can get security patches after some delay and not via OTP but have to sideload manually.
r0b0 said:
Hi,
First sorry for this vague post. I am on Android since 2012. During 2012-2014 I used to try out lots of custom ROMs as I was in college and I had mobile like Samsung Galaxy S3 and then later Nexus and the OEM abandoned the updates after a while. After that I started working and since then have been on multiple Google line of devices, first Nexus and now my latest is Pixel3. I am generally happy with the phone. However, my Pixel3 stopped receiving updates I started thinking why I should dump this and buy a new one when it's perfectly working fine for my need.
I just came to this site after like ages to see what is the current status of custom ROMs. It seems overwhelmingly new now. I remember back then we had some sharp edges and something or other didn't work. Since then I am more into google ecosystem now. I use google Fi for phone. I like and use most of the google feature. So just wondering what will I lose by moving to custom ROM and am I ready to live without those features or should I just accept that I will not have any updates and if I need the updates I will have to buy a new phone.
I am not much interested into rooting and gaining advanced controls or doing anything extra nerdy. I will be perfectly happy with just getting the security patches and whatever feature is there if they keep working.
1. what are some good custom ROMs popular these days?
2. What are the things I'd lose moving to custom ROM?
3. Does all hardware for ex: Finger print, NFC work?
4. What about google apps, I mostly like all google app like camera, google pay, phone, play store
5. I like the google specific features like call screening and google assistance, google feed. I guess I will lose those.
6. I also use google Fi, can I still use that seamlessly or is there any gotchas I need to be aware of?
7. Is there any other way to keep my phone Googlized and receive security updates. It is totally acceptable if I can get security patches after some delay and not via OTP but have to sideload manually.
Click to expand...
Click to collapse
1. LineageOS
2. I have not found anything lost.
3. Yes
4. You can download the Google Camera app from the play store. Probably the phone app also, but I have not tried it. Google Pay will require rooting and Universal SafetyNet Fix module.
5. Don't know, as I don't use them.
6. I don't use Fi, but would expect it to work.
7. I'm not aware of any other way, but have not looked. Lineage does everything I need.
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.