Develop Bugs

Google Pay - Android Pie - Credit Cards keep requiring verification

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

Uconnect App on Pie

Pixel 2 XL on 9.0
Bootloader Unlocked
TWRP Recovery
Rooted via Magisk 17.1
The Uconnect app for my Jeep no longer functions because the new version for Android 9.0 checks for an unlocked bootloader or root. When trying to login to the Uconnect app, I receive a popup that states I'm using an unapproved device. When contacting the developer, they claim that it's because my device is a security threat. I've tried Magisk Hide to no avail.
Any suggestions?

Same thing here too. I have an older S6 Edge + running a rooted Android 7.0 with Magisk 17.1. Magisk Hide doesnt fix it as well.

having this issue as well with the latest uConnect app. Pixel 2XL is rooted and unlocked. I loaded the latest stock firmware 9.0 and tried the uConnect app prior to rooting and it works on my end, but still a no-go once Magisk is installed. I even tried the magisk hide and the module that can alter prop to further hide magisk and no go. I think it may be that it is looking for root and is awfully good at finding it. If anyone can get this to work, would be great! I dont get why FCA is so worried about root. One would think that since we have to go through a VERY specific sequence to get root and unlock the bootloader, that we would have quite a grip on what goes on with our phones. Anyways, if someone comes up with something......

Uconnect is detecting Magisk Manager. You have to uninstall it in order for Uconnect to work.

Well that sucks

I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.

TechnovationLLC said:
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
Click to expand...
Click to collapse
And you are rooted?

CyberpodS2 said:
And you are rooted?
Click to expand...
Click to collapse
I tested root and non rooted. Both seemed to function fine for me. I initially thought rooted might be the issue for me, but it ended up being the old app.

Fresh install from play store gets me this.

Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.

MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
Sadly, if I install an older version it prompts to update with no way around it... If anyone knows a version that works please post here.

Wondering if a logcat would help to pinpoint the issue and assist the magisk developer with a fix.

MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
The old (black) version of the app doesn't work with 9.0

Very discouraging
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.

Viol8ter said:
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Click to expand...
Click to collapse
Which version of Android are you on and which app version? Thanks!

lu270bro said:
Which version of Android are you on and which app version? Thanks!
Click to expand...
Click to collapse
I am on 8.0. Though I read somewhere someone said to hide the magisc manger with random name and it worked after clearing app cache. I'm happy and thankyou.

Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.

Machine318 said:
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Click to expand...
Click to collapse
I have never been able to get it working on this phone since the blue icon change. Sucks...

why does a car/radio company care what a joke glad i dont have a car with unconnect

OK boys and girls. I think I found a fix. might not work for all of you, but I got the App to load and let me in.
I'm running the latest Pie version, Magisk 18.1 (Riru - Core v16, Riru - Ed Xposed) and XPrivacyLua (xposed module)
in XPrivacyLua for the Uconnect App, I restricted, Get Applications. Uconnect Logs in.

Google pay / etc

After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?

Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176

xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
I have a Gear S3 and it seems to work well ONLY if you hide Magisk Manager and then use Magisk hide Samsung Pay. This is as of a couple weeks ago when all the bootloader unlock detection was happening. I haven't tried since then. You can fail CTS/Safetynet, but still get Samsung Pay to work.

Knxed_ said:
Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
Click to expand...
Click to collapse
There's like 50 links. There which do I download?

xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
Only reason why I have yet to root my Pixel 2 XL.

Ya im not sure how to fix GPay on this device!

xSpartacusx said:
There's like 50 links. There which do I download?
Click to expand...
Click to collapse
This link here is the most up to date version of the GPay patch, this will link you the download. You gotta flash it through recovery to get it working.
https://github.com/stylemessiah/GPay-SQLite-Fix/releases/download/v2.0/GPay.SQLite.Fix.v2.0.zip

Unable to install Google Play on Matepad (BAH3-L09)

Hi. My Matepad is BAH3-L09 and I was not able to install Google Play on it as I keep receiving "LZPlay not support" in Chinese language. I tried several top instructions on YouTube, but none works. Anyone managed to install it on your Matepad?

Same Problem here, BAH3-W09

fonetech just posted a new video. maybe it can help you guys?
https://www.youtube.com/watch?v=wxqEZMX6Kl8

Dr. Light said:
fonetech just posted a new video. maybe it can help you guys?
https://www.youtube.com/watch?v=wxqEZMX6Kl8
Click to expand...
Click to collapse
Unfortunately the lila g app itself doesn't work on the Matepad 10.4 version.
So no luck with those "install on every device" videos.
Seems to be the same with the P40 Lite 5G model
Here is a screenshot of the error:

Dr. Light said:
fonetech just posted a new video. maybe it can help you guys?
https://www.youtube.com/watch?v=wxqEZMX6Kl8
Click to expand...
Click to collapse
I just tried and the LZPlay does not work.

vichet007 said:
I just tried and the LZPlay does not work.
Click to expand...
Click to collapse
Fischmaster said:
Same Problem here, BAH3-W09
Click to expand...
Click to collapse
You have to use an older backup app. take a look at this video
https://www.youtube.com/watch?v=6TnuamFAp8g

p82maarj said:
You have to use an older backup app. take a look at this video
https://www.youtube.com/watch?v=6TnuamFAp8g
Click to expand...
Click to collapse
Unfortunately we are not talking about the "May Backup App Error".
I tried that already.
Please take a look at the pictures added to this post.
First one is our problem, the second picture the may error.

Fischmaster said:
Unfortunately we are not talking about the "May Backup App Error".
I tried that already.
Please take a look at the pictures added to this post.
First one is our problem, the second picture the may error.
Click to expand...
Click to collapse
:crying:
Hope any solution. I have a Mediapad M6 and I could install it. And I want to update my Mate 10 with Mate 40 pro...but I would like to have the option of install GMS

p82maarj said:
:crying:
Hope any solution. I have a Mediapad M6 and I could install it. And I want to update my Mate 10 with Mate 40 pro...but I would like to have the option of install GMS
Click to expand...
Click to collapse
I hope so, too.
Don't know yet, why it is not supported.
At the moment you can't really find anything about it on the internet.
I've got Gapps installed on my P40 Pro. For a mobile phone, I think it is required.
On the tablet however, i think its more a nice to have than really necessary.
Furthermore, I wrote to Amazon Video, Netflix and Disney+ support and all of them said that "they are working on it"
So fingers crossed that HQ Streaming of those services will be available.
Although Disney+ does Stream in 1080p without Widvine L1.
Edit: Found an article about the problem. https://www.justandroid.net/2020/07...ernative-solutions-also-affects-matepad-10-4/

I'm having the same issue installing on Matepad 10.4 WiFi (BAH3 W09). No method works, LZplay (G icon app) always gives the error button on opening and cant go any further. Tried replacing 'backup' app exactly as directed in a couple of videos, no luck.
Anyone got Google 7&Play to install on this model?

Looking into this I would guess Huawei have removed the 'stubs' in the system firmware that allowed the LZplay app to work in the first place (and allowed it to install the required stuff as system apps). If newer devices are being rolled out without those 'stubs' then we are out of luck as far any LZplay method goes.

noolder said:
Looking into this I would guess Huawei have removed the 'stubs' in the system firmware that allowed the LZplay app to work in the first place (and allowed it to install the required stuff as system apps). If newer devices are being rolled out without those 'stubs' then we are out of luck as far any LZplay method goes.
Click to expand...
Click to collapse
I don't really know what the function of the "stubs" file is, but if it is removed, is it possible to add it back and then install LZPlay?

vichet007 said:
I don't really know what the function of the "stubs" file is, but if it is removed, is it possible to add it back and then install LZPlay?
Click to expand...
Click to collapse
Actually, it isn't 'stubs', I got that wrong. It's an undocumented API that existed in the firmware/ROM that allows LZplay to install the google stuff as system apps (and they need that to work). If they have removed that API from affected models, and it looks like many new ones might be in the same boat going forward, then I cant see any way of a user restoring it.
If that is the case then the only way to get GMS/Play etc will be a new non LZPlay method (that seems unlikely given the system access required) or if the ban gets lifted and Huawei add it back in future firmware updates (not sure how likely that would be either). A shame, as this is a very nice tablet otherwise.
Another thing to note is this doesn't have a gyroscope either, though the spec sheets wrongly say it does.
I've only just got my Matepad 10.4 from the Huawei UK store, so I'm seriously thinking of sending it back in the 14 day window. I could live without GMS/Play, but it is annoying.

Just one workaround - you can install VMOS virtual machine. It is not perfect - they have just Android 5.1 and 7.1 images and of course you have to start the application, but it works.
Between the AppGallery and the VMOS I have all I need. And the Trump's stupid trade war just allowed me to get the top tablet cheaper than Huawei would sell it otherwise. Every cloud has a silver lining.

And one more solution - HiSuite enables (as of today, not sure for how long) to downgrade firmware. And LZPlay works on the older firmware.
Of cause - the downgrade will delete all data on the tablet.

mirekluza said:
And one more solution - HiSuite enables (as of today, not sure for how long) to downgrade firmware. And LZPlay works on the older firmware.
Of cause - the downgrade will delete all data on the tablet.
Click to expand...
Click to collapse
Ive no problem erasing everything, but are you sure it will work on an older firmware? Do you have a link to that info at all?
Pretty sure the firmware mine came loaded with ended with 115. LZPlay didn't work with that and I have let it update since then to the latest version. I think the first version made for this tablet ended in 108 (can't see an earlier revision in a google search). I assume that's what the first models in early April would have shipped with. If LZPlay has never worked with this model though downgrading wont be any help.

It worked for my tablet which I bought a few days ago, but I now realize I have LTE version - so different model.
Still I guess the LZPlay problem may be similar. LZPlay does not fully work anywhere anymore. Even when it works, it fails to do its work on its own and has to be helped by manually installing things. I used https://youtu.be/pdgGkHEe7V4 .
My experience: After getting the tablet I updated it to the newest firmware and then tried to install GP. Bad luck. No device admin request from LZPlay, just small popup with two buttons in Chinese. I guess Huawei removed the API as written above. After downgrade through Hisuite (4.6GB download), LZPlay "worked" (it asked to be device admin and shown screen where it would have downloaded GP things if it had worked properly - though the downloads failed - I think that is normal). Then I went according to the describtion which was under the YouTube video. I had to redo installing of APKs twice (maybe I did not follow it perfectly first time) and I added Google account when starting Google Play Store (so not as described under that video), but it worked.
I was kind of confused by LZPlay for some time - the fact it fails to download etc is normal state of things. I guess it used to be one-click solution, but not any more. Still I guess that running it is essentiall to enable other steps to work.

mirekluza said:
It worked for my tablet which I bought a few days ago, but I now realize I have LTE version - so different model.
Still I guess the LZPlay problem may be similar. LZPlay does not fully work anywhere anymore. Even when it works, it fails to do its work on its own and has to be helped by manually installing things. I used .
My experience: After getting the tablet I updated it to the newest firmware and then tried to install GP. Bad luck. No device admin request from LZPlay, just small popup with two buttons in Chinese. I guess Huawei removed the API as written above. After downgrade through Hisuite (4.6GB download), LZPlay "worked" (it asked to be device admin and shown screen where it would have downloaded GP things if it had worked properly - though the downloads failed - I think that is normal). Then I went according to the describtion which was under the YouTube video. I had to redo installing of APKs twice (maybe I did not follow it perfectly first time) and I added Google account when starting Google Play Store (so not as described under that video), but it worked.
I was kind of confused by LZPlay for some time - the fact it fails to download etc is normal state of things. I guess it used to be one-click solution, but not any more. Still I guess that running it is essentiall to enable other steps to work.
Click to expand...
Click to collapse
and which version of firmware you have now? my tablet out of the box does not find new firmware versions

Lively_Alex said:
and which version of firmware you have now? my tablet out of the box does not find new firmware versions
Click to expand...
Click to collapse
I have the model MRX-AL09 with EMUI 10.0.1.177 - that is the downgraded version.
I was probably on 10.1.0.120 before - at least I think so, I did not write it down before downgrage

mirekluza said:
I have the model MRX-AL09 with EMUI 10.0.1.177 - that is the downgraded version.
I was probably on 10.1.0.120 before - at least I think so, I did not write it down before downgrage
Click to expand...
Click to collapse
yes, now i have 10.1.0.121.
Ok, I’ll save the data and try to roll back the firmware.
Have you tried updating your tablet to the latest version after installing google services?

GPay card cannot be set for contactless payments

Hi, I need help adding a card to gpay.
The card cannot be added for contactless payments. I don't know what it is or what could have happened while playing rom. In the original, everything worked well. After that I switched to alexis rom and everything worked. After some time I tried xFire rom and also nothing. I wanted to try the resurrection remix because it's my favorite rom from previous phones and I don't know there because I left it due to problems with the Gear S3 Frontier parking. Using Odin, I recorded the original rom and the problems started. The card could not be added at all, but it was resolved with the bank. The problem was logging the card on multiple devices and the bank fixed it. The card can be added manually, but the settings for contactless payments cannot be completed. The process ends when the card is verified at the bank. I thought it was a rom problem, but I tried several roms and the problem is the same.
I tried to set the card on my older asus zenfone max for m1s HavocOS and the card was added to gpay without any problems. So the problem must be in the phone.
Could someone please help how to fix this? I'm really desperate. Sorry English, I use google transalator

Are you rooted?

Yes. Currently alexndr rom. Magisk hide. Neither the banking app nor the gpay app report root. Safenet check pass
The strange thing is that a week ago on alexis rom it still worked. Now it is not possible to add for contactless payments on any rom. Manually yes, but only for online payments. The contactless payment setup ends during the verification process at the bank.

jampce said:
Yes. Currently alexndr rom. Magisk hide. Neither the banking app nor the gpay app report root. Safenet check pass
The strange thing is that a week ago on alexis rom it still worked. Now it is not possible to add for contactless payments on any rom. Manually yes, but only for online payments. The contactless payment setup ends during the verification process at the bank.
Click to expand...
Click to collapse
I have no idea what to suggest then, it can't be root related because safety net passes, have you tried adding another card to google pay?
Sent from my SM-G960F using Tapatalk

I tried to add a girlfriend card and it ends the same way. My card on my old phone can be added normally .. That's why I don't understand .. I already received an answer from Google support that everything is fine on their part ..
So there must be something wrong with the phone. But what .. Bootloader I have for sure flash as well. The only thing that comes to mind can be influenced by CSC? I don't know what it was originally like, but I chose XEZ (Czech) when installing alexis, which it probably should be. But there was a card to add and after replacing other roms it doesn't even go there.
I'm still thinking. Before flash original rom using odin, I twrp wipe all the partitions (including vendor and preloaded). It still seemed to me that everything was not right, so I did it. Couldn't it be wrong? If so, can it be fixed? Although I assume odin will record everything again