Develop Bugs

Solved - Working Non Stock Rom for Android Pay on M8

I am looking for any ROM that can be installed and allows Android Pay to work. I sometimes forget my wallet and would like to have the ability to use Android Pay. I was excited when I got AICP to install and pass safety check, but it doesn`t actually work at the terminal. I now read that all AOSP based roms have problems with NFC payments.
Does anyone have this working on an M8. There are some old threads, but none that actually report that it works.

Are you rooted with Magisk?

redpoint73 said:
Are you rooted with Magisk?
Click to expand...
Click to collapse
Yes. So far I have tried AICP 7.1 Rom, which passed safetynet check, but would not actually work on a store's terminal. Perhaps an NFC issue with AOSP Rom? I also tried Lineage 15, but could not get it to recognize google play services and could not get the play store to work as a result. I am now on lineage 14.1, which agains passes safetynet check but will not work at the terminal.
As I am aware, Magisk only allows Android Pay to be installed, but when it comes time to validate the purchase, there is either an NFC problem or something prevents the purchase from being validated.
So if anyone has a non stock rom that works with android pay on the m8, I would like to know about it. There have been a few threads, but none seem to offer a current resolution.

I'm not personally a user of AOSP ROMs, nor Android Pay, so my advice is limited. Just chiming in, as long as you are passing SafetyNet, and have Magisk Hide enabled (in Magisk Manager settings) than I don't think it's a safety net or root issue. Like you said, it might be an issue with AOSP ROMs and NFC.

I tried Resurrection Remix. Same result. Passed safety check but would not work at the store terminal.

Cannot use payments on nougat. Have to go to marshmellow.
NFC works, but HCE does not, which is whats required.

Success. I went to ViperOneM8 6.1.0. Installed the rom. Then deactivated Su in the Su app. Then properly installed Magisk by creating a new boot.img file and then flashing that new boot.img file with twrp. Magisk 14 showed safetynet passed both test. Off I went to the store to buy a chocolate bar, unlocked the phone, tapped it on the terminal and buzz buzz, payment approved. Very nice.

Google pay not working with magisk?

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

GPay Can tell root now???

FIX:
1. Add Google Services to Magisk Hide (if you're on Magisk 18.1 use "su magiskhide --add com.google.android.gms" in terminal)
2. Add Google Pay and Google Services Framework to Magisk Hide
3. Go to data/data and rename com.google.android.gms to com.google.android.gms.bak for example (or delete it altogether, but backing up seems safer)
Reboot and do whatever you like in GPay, it should work now. That's all I've done. I don't think you need to reinstall Magisk.
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??

mine is fine
try re flash your rom

i42o said:
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
Click to expand...
Click to collapse
Long thread and a lot of moving parts, so work backwards on the thread. Personally, I am just waiting until a final and formal fix is found on stable Magisk and up to date Play apps.
https://forum.xda-developers.com/app...ssion-t3906703

My experience with this issue is I run GPay, go back to Magisk, safetynet fails on both.. So I force close Magisk, clear cache and data.. reboot. Open Magisk back up, Safetynet passes.. Gpay sets up fine. Sometimes you have to do this several times and it's a real pain but it's always worked for me..

this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!

dipstik said:
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Click to expand...
Click to collapse
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?

jbarcus81 said:
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
Click to expand...
Click to collapse
Get a 2.83 build. Xda shortens links and you lose them on copy text

dipstik said:
Get a 2.83 build. Xda shortens links and you lose them on copy text
Click to expand...
Click to collapse
I know.. it's ridiculous, appreciate the clarification!

I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.

rob42ert said:
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
Click to expand...
Click to collapse
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.

This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5

TonikJDK said:
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
Click to expand...
Click to collapse
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.

sliding_billy said:
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
Click to expand...
Click to collapse
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.

TonikJDK said:
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
Click to expand...
Click to collapse
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.

sliding_billy said:
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
Click to expand...
Click to collapse
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.

Bogega said:
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Click to expand...
Click to collapse
And the doubt kicks back in, LOL. Luckily, I just carry a real card until this is formally solved (hopefully).

Bogega said:
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
Click to expand...
Click to collapse
Sadly this method only works for a limited time.
Overnight GPS updates to version 15 by its own self and GP stops working.
I'm not sure I'm ready to to this procedure daily just for Google pay. For the time being I'll use my card until Magisk developer finds solution to this problem.

Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.

yeah nothing worked for me even when I uninstalled magisk and tried the steps above on stock. Ended up factory resetting. but thats the last move to do

TonikJDK said:
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
Click to expand...
Click to collapse
Google Pay is a real asshole and doesn't let you know something is wrong until you actually tap to pay.
It's happened to me a couple of throughout my ownership of Pixels.

Safety net passes but Google pay doesn't work?

Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?

zee24 said:
Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?
Click to expand...
Click to collapse
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.

SageWilliams said:
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.
Click to expand...
Click to collapse
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this

zee24 said:
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this
Click to expand...
Click to collapse
Great, I will say its hit or miss sometimes. Mine worked in stores for a few days, then stopped saying I was rooted so I had to redo the method to get it back.

This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .

prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Great. Finally a fix. All like above but used Magisk 19.0. Thanks. I hope we're able to keep finding fixes like this. Google pay is a convenience.

According to this, it is to be expected on Pixel devices, vs others.
Advantages:
If you will see the list of the advantages and the list is too long of the magisk. This is the best Android application which you can use on your device. Let’s take a dive in the advantages of the Magisk.
You can use Financial/Banking applications.
You can use Snapchat without any issues.
You can also play Pokemon Go on your rooted Android device.
You can install OTA updates on your device.
You can also install System-less Xposed framework on your lollipop and marshmallow devices.
You can use Android Pay.
You can also bypass SafetyNet.
You might Face issues in:
Google Pixel and Google Pixel XL devices. The work is in progress, and we are working on i.
Magisk Manager cannot be placed in adaptable storage, or superuser will not work
MagiskSU does not support multi-user, and we are working on it to make multi-user support.
MagiskSU does not work on Android O preview, and we are working on it.
Click to expand...
Click to collapse
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com

Droid_Nut said:
According to this, it is to be expected on Pixel devices, vs others.
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com
Click to expand...
Click to collapse
Ever since that site was verified to be a fake.
https://www.google.com/amp/s/www.xd...kmanager-com-not-official-website-magisk/amp/

prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Thanks so much dude....much appreciated

How To Guide Rooted S22: How to make the new Google Wallet work

If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.

Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).

Vattu said:
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Click to expand...
Click to collapse
Yeah this thread is now out of date. The updated safetynet fix is a much better option now.

You don't need just the safetynet module. You need Shamiko along that.
So latest Safetynet + Shamiko 0.5.2 (the latest version right now) and you're all set. You gotta whitelist the banking apps you use and they'll work perfectly fine. These 2 were enough to allow my preferred ridiculous banking app to work without an issue, without any other modules or tweaking and such.

dragos281993 said:
You don't need just the safetynet module. You need Shamiko along that.
Click to expand...
Click to collapse
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.

aurny said:
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
Click to expand...
Click to collapse
No. I only had Magisk installed with Zygisk turned on. I first installed Safetynet Fix then Shamiko. The first module wasn't enough for my preffered banking app to not detect that the bootloader was unlocked. Shamiko fixed that. I simply installed it as a module in Magisk

Thanks, good to know. I haven't had that issue yet but I'll remember this in case I need it in the future!

aurny said:
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Click to expand...
Click to collapse
Thank you very much, it worked perfectly.

This actually worked, thank you!