So I tried doing the systemless root thing. I tried confirming that android pay would still work by removing my cards then attempting to re-add them and it failed. I tried undoing what I did by flashing stock recovery, boot, and system. Still a no-go. I tried running the flash-all.bat (i removed the "-w" so I would keep my data). Still can't add a card.
I resorted to running the flash-all.bat, build MDB08M, to be 100% stock. I STILL CANNOT add a card. The message has been the same every single time "Android Pay cannot be used - Google is unable to verify that your device or the software running on it is Android compatible"
Am I missing something? I don't understand how a 100% stock flash is not able to work.
If it makes you feel any better I've been running 100% stock since day 1 and tried using Android Pay for the first time today. Failed same as yours saying device or software couldn't be verified. I had originally set it up using my card that was already set up on my Google account. When this card didn't work I removed it and tried adding the card again manually. Couldn't even add a card. Tried rebooting several times and disabled developer options. Still not working.
I can select a card already on my google account, accept the terms, then the message pops up. Happens with two different cards associated with my account.
I'm fully stock, but unlocked bootloader.
Android pay used to work as recently as 4 days ago, but failed today with the error unable to verify.
Not willing to relock bootloader. Was there an update of Google play services that changed the way they check for modifications to include bootloader unlock?
I went back to complete stock relocked bootloader and Android paid don't work for me because chase bank stopped supporting Android pay so I went back to custom ROM
Just to note my bootloader is unlocked, otherwise I am 100% stock.
I manually tried updating Google play services to the latest version, but Android Pay gave me the same message but at a different point in the process - right after I clicked "Add a credit or debit card." I wasn't even able to see cards already associated with my account like before. I ended up uninstalling the update because it seemed to make things worse.
I just tried this app and it says I'm failing the SafetyNet check:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Same here. Completely stock 5x with nova. Had added a card, but wasn't working so I deleted it to try to re-add. No luck... Pretty annoying actually. I don't use it that often, but there have been several occasions I forgot my wallet going to the grocery store and paid with android pay cause it's all I had. Hope it gets fixed soon.
Looks like it is working all of a sudden. I was trying the safetynet checking app a few times a day... just tried now and it finally passed. Gave android pay a whirl and both cards were able to be added without issue. So apparently something happened on Google's end. Google play services is the same version now as it was when android pay failed to work.
I was failing the safetynet API yesterday. I still am.
I was also unable to pay with anything yesterday, but today I was able to add a card. Presumably it's partially fixed.
I went completely stock with relocked bootloader and STILL failed the test.
If it's working again, it's probably something wrong on Google's part. I'll try adding a card with systemless root
Ugh, what a headache, I ended up deleting everything for no reason.
Anyone else find it to be working now? I ran the safety net check last night and it passed. Tried adding my card and this time it worked. Big G must have fixed something on their end.
Related
So heres the scenario:
I have an HTC Desire with Froyo loaded. I had rooted it with unrevoked 3.21 and everything was going fine until an OTA update (apparently an update for marketplace) came out. Yes, I made a stupid error and updated using the OTA and lost the root.
Now I did a factory reset and tried rooting it again with unrevoked 3.22. And surprise surprise! It got rooted again!!
Now the problem here is that, I am trying to re-install some paid and some free applications that were on my phone earlier and Marketplace refuses to even show up those apps in search results...!! They are not present my phone because of the factory reset. Now when I search for the same app in Appbrain it throws up the search result and when I click on it, it behaves as if the app is installed in my system and shows me options like "Open - Uninstall - etc."
Is there some cache in my system that makes it believe that these apps are still there somewhere? I deleted everything from my SD Card and I tried clearing the marketplace cache. I also cleared the Dalvik Cache (dont know if its in any way related to the marketplace, but I still did it)
So what is it thats going wrong? Why arent these apps showing up? Any help would be appreciated. I am quite disillusioned with Android marketplace.
try to install market access to try another country instead. after installing market access force stop market and clear cache.
Tried that, but it didnt work.
After searching the internet about this problem I realised that every ROM has a fingerprint that needs to be registered with Google. If this is not registered with Google, then users cannot find apps that are Copy Protected in the market.
I had recently received an OTA (about 2 weeks ago). So I am assuming that either HTC has not bothered to register this fingerprint with google or google has not updated their database. Either way the situation is pretty deplorable.
The only workaround that I found on the internet is to edit the build.prop file in the Android system (of course you need root access for this). I am planning of trying to do this so that I can fool the market into believing that I am using an older ROM version which is registered with them.
Well, just tried the build.prop method. Successfully spoofed the marketplace.
Shame on Google for having such restrictions. If I didnt have root access and I didnt know about this spoofing method, then I would just have to wait endlessly until either HTC or Google moved their rearside and get things working.
Really disappointed with Android.
If anyone is able to help me, I would greatly appreciate it.
I installed Google Wallet (via this APK) when I first got my Verizon LTE GN a few weeks back. I've since used the app daily and it has worked perfectly, up until this evening.
Today, for the first time ever, I decided to unlock my bootloader in order to root my device--all of which went smoothly. I then re-downloaded the above GW APK (since unlocking wiped my device) but now when I launch the application, the screen stays at "Initializing your device - This may take a few minutes depending on your network connection." The application doesn't freeze (the circle continues to spin), but after 30 minutes of waiting, still, nothing has happened. I've tried reinstalling the APK but that does nothing. I have 4G connectivity and have tried over WiFi also.
I am running stock recovery, stock ROM, stock everything on 4.0.2. All I did was unlock the bootloader & root the device. I've done quite a bit of searching but have been unable to find a solution. Does anyone know what may be causing the issue or what I could do to fix it? I really enjoy using the application
I'm having a pretty similar problem.
CDMA Galaxy Nexus.
When I first got the phone, I downloaded the Google Wallet apk and it worked fine. Used it a few times out in the real world.
Today, used the wug unlock/root method, and installed a custom rom.
Though the rom feature log said it contained Google Wallet, it did not.
I redownloaded the original APK that I had used and it installed, but now I get this "Unfortunately wallet has stopped" message every time.
In fact, it comes up on the screen at random intrevals.
Not sure if there's anything I can do.
Do you guys have NFC enabled from the settings menu?
Also, did you try disabling and re-enabling NFC? It's different hardware, but after flashing one ROM I had to disable/re-enable GPS before it would work... worth a shot.
I have been rooted with SuperSu/Suhide since September and now am using Magisk 14.2 with the October security updates (flashed image and removed "-w" to retain data). I pass all of the safetynet checks from various apps under both conditions. I am having a problem adding cards to Android Pay. I add the card, verify the CVC, agree to the terms, and then get a popup saying that Google Play services has stopped. It does not finish verifying the card and clicking on the card results in the "Google Play services keeps stopping" error. This has happened since the September security update (did clear user data then) and I cannot find what may be causing it. I did edit the hosts file and build.prop when using SuperSu/Suhide, but now only the hosts file with Magisk. Anyone have a similar issues or know of solutions? Thanks.
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
Not sure if it's related, but I updated to September's Oreo build using fastboot flash of the factory image. I removed -w to save data. After this I was no longer able to purchase apps in the play store, always caused the play store to crash. Free downloads worked fine but paid transactions never went through. I ended up flashing the factory image and wiping data and all is well. I am unrooted.
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
I have the same issue can't buy apps. Get to the point of buying it and get FC. Doesn't matter if I'm rooted or not. Tried magisk and suhide
Not sure what could be the exact reason. I had google play services stopped problem on my Note 3, but it was not rooted. I followed a guide on Mobipicker, that worked for me. You can also refer, but not sure that will work for rooted devices.
I know this is old, but I found this thread because I had been having the same problem...I found the fix for my situation and figured I'd share in case anyone else came across the same issue... Everytime I tried to verify my card Google play services stopped...
I remembered that it checks that you have a secured lock screen when you set up at some point...I turned off smart lock location, on body detection, and face... Worked without any problems...
I'm at home, so I'm not sure if smart lock was preventing it from working just by being turned on, or if it thought I didn't have a secured lock screen because smart lock was triggered by me being at home...
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Google Pay can be used under rooted device?
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
sb1893 said:
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Click to expand...
Click to collapse
JD_dadada said:
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
Click to expand...
Click to collapse
I've always been able to leverage the root hiding capabilities offered by the root providers I have used. Originally suhide for SuperSu...then when I moved to Magisk MagiskHide. Both have worked well for my root (and unlocked bootloader) hiding purposes. I've always been able to use Android/Google Pay, banking apps, alarm system apps, Netflix, etc...Occasionally, the cat and mouse game catches up with the root hiding solution, but the developers have been pretty quick to overcome any of the challenges encountered thus far.
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Zaczero said:
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Click to expand...
Click to collapse
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
javlada said:
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
Click to expand...
Click to collapse
Looks like I found the problem (at least in my case).
Some ROMs got issues with fingerprint scanner. I noticed that in my bank app after adding the fingerprint unlock it started to crash. Also in google play I couldn't add fingerprint as payment confirmation.
In Google Pay one of the steps of verifying cc is fingerprint check. I think that this fingerprint bug may cause the google pay to fail.
After installing a ROM with fingerprint scanner working properly (now I'm on LineageOS) the issue went away. Got my cc verified successfully with root and rom
Hey guys just updated to the latest magisk manager and magisk root on my pixel a few days ago but i just noticed that my Google pay had removed my bank card. Checked magisk manager and went into the magisk hide list and nothing was checked so i manually checked necessary apps including Google pay. Now even after that and after a reboot and clearing data of Google pay AND despite magisk passing a safetynet check Google pay still refuses to accept my bank card. Should i roll back to an earlier version when it was working? Is there something broken in the lastest magisk manager?
Thanks in advanced.
February security update
Magisk manager 7.0
Magisk 18.1
ElentalX-P2-2.09
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
CyberpodS2 said:
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
Click to expand...
Click to collapse
Thanks so much for confirming must be a problem on my end. I've been getting random freezes at night which had me waking up with no alarm. Guess it's time for a clean install because obviously something went wrong on my end. Thanks again G.
Yeah....there's a (good) chance that it's just as what happened with @acheney1990 and me...
you can read all about it HERE, but suffice it to say; it can easily be on the banking's end "flagging" with all the validation that's needed -- which is it's own headache trying to understand why they keep tripping it up this way....
Hey did you ever happen to get a solution on this? I seem to have run into the same problem because everything is setup the same as before, but since I've upgraded to Pie in Feb security, I can't use Google Pay (unable to pay in store), Zelle, or the Chase app (force closes immediately, apparently on checking my GPS location it seems).
My problem started when I updated my Moto x4 to latest Pie update 29.69-26-5. I was on Magisk 18.1, and Manager 7.0 which I had to uninstall to get the update. After reinstalling Magisk, Passing safety net, I get a message at the POS saying my phone won't work with Google Pay. My debit card (Chase) is still listed in Google pay on my phone but when I try to add another card I get "This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way"
if I clear the storage and uninstall and re-install Google Pay, it still has my debit card listed, so for whatever reason, it's keeping my payment info even though I cleared the storage.
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Itachisasuke said:
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Click to expand...
Click to collapse
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
simplepinoi177 said:
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
Click to expand...
Click to collapse
That is exactly what has been suggested and even outlined here and there. I tried a couple different scenarios but it became too cumbersome trying to juggle it all. I'll just wait for an update to be released. Lol