Database Develop

Activate Android Pay on a rooted phone

I'm on M3 rooted with Despair kernel.
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted, I figured out that's because of root.
I tried to unroot in SuperSu. First by disabling Enable Superuser root button, second by Full unroot. Both methods didn't work, Android pay still couldn't be activated.
I then tried to format and flash boot, system, recovery MPA44I images. I started to get a RED message your phone can't be trusted on boot. Android pay still couldn't be activated. NOTE: I didn't erase data partition.
I don't want to do a full factory reset.
What are my options now ?

jodvova said:
I'm on M3 rooted with Despair kernel.
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted, I figured out that's because of root.
I tried to unroot in SuperSu. First by disabling Enable Superuser root button, second by Full unroot. Both methods didn't work, Android pay still couldn't be activated.
I then tried to format and flash boot, system, recovery MPA44I images. I started to get a RED message your phone can't be trusted on boot. Android pay still couldn't be activated. NOTE: I didn't erase data partition.
I don't want to do a full factory reset.
What are my options now ?
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...per-preview-but-it-will-in-the-final-release/
Sent from my Nexus 6 using Tapatalk

Thanks!

jodvova said:
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted . . .
What are my options now ?
Click to expand...
Click to collapse
Paying with money.
(Just joking, forgive me. I just got a message of the bank that we have to pay for nfc paying)

jodvova said:
I'm on M3 rooted with Despair kernel.
Got Android pay update and tried to activate it by adding a credit card information. It bailed out saying that my phone can't be trusted, I figured out that's because of root.
I tried to unroot in SuperSu. First by disabling Enable Superuser root button, second by Full unroot. Both methods didn't work, Android pay still couldn't be activated.
I then tried to format and flash boot, system, recovery MPA44I images. I started to get a RED message your phone can't be trusted on boot. Android pay still couldn't be activated. NOTE: I didn't erase data partition.
I don't want to do a full factory reset.
What are my options now ?
Click to expand...
Click to collapse
This might be worth a look.
http://www.xda-developers.com/xda-external-link/no-device-check-xposed-module/

adfurgerson said:
This might be worth a look.
http://www.xda-developers.com/xda-external-link/no-device-check-xposed-module/
Click to expand...
Click to collapse
Thanks for the link. I just tried it with N6Shamu and it doesn't seem to work for me.

CharFalco said:
Thanks for the link. I just tried it with N6Shamu and it doesn't seem to work for me.
Click to expand...
Click to collapse
Same here. Nexus 6, latest chroma build, rooted, bootloader unlocked, using xposed RootCloak and the No Device Check modules. No dice.

Is there any way to revert back to the old Google Wallet?

CyberZion said:
Is there any way to revert back to the old Google Wallet?
Click to expand...
Click to collapse
Go to the Android Pay app info, and uninstall updates. This will roll it back into Google Wallet. You should also go and uninstall the new wallet app if you have it so as to avoid confusion.
After that, I had to find an APK site that could update my wallet app back up to Version 9.0. I've since disabled auto-updates to the Google Wallet app until I see some signs of support for root.

I'm unlocked, rooted, and running Xposed w/ Android Pay setup and have had no issues...

ethan.r.besbris said:
I'm unlocked, rooted, and running Xposed w/ Android Pay setup and have had no issues...
Click to expand...
Click to collapse
Have you actually been able to make a purchase? I got everything setup and activated but received an error message when I tried to use it. I then disabled root and rebooted to try the payment again. Did not get the error message this time but the transaction did not complete.

I made a payment this morning using Pay without a problem.

ethan.r.besbris said:
I made a payment this morning using Pay without a problem.
Click to expand...
Click to collapse
Weird since Google has already announced on the complaints in GPS that currently Development Builds and Rooted Devices are not supported. Is Xposed Masking root for you?

GMoGoody said:
Weird since Google has already announced on the complaints in GPS that currently Development Builds and Rooted Devices are not supported. Is Xposed Masking root for you?
Click to expand...
Click to collapse
i installed it fine yesterday(into /data/data/), and added a card no problem. i have root, an unlocked bootloader, am running m(jdx rom), and have a custom kernel. using google play services 8.1.14.

simms22 said:
i installed it fine yesterday(into /data/data/), and added a card no problem. i have root, an unlocked bootloader, am running m(jdx rom), and have a custom kernel. using google play services 8.1.14.
Click to expand...
Click to collapse
Have you tried to make a purchase? @ethan.r.besbris was the only one I know of that has successfully purchased something with root. I too have everything installed but the vending machine and whole foods today gave me errors when actually trying a transaction. I am trying to figure out what the difference is. As of now I do not have Xposed installed.

GMoGoody said:
Have you tried to make a purchase? @ethan.r.besbris was the only one I know of that has successfully purchased something with root. I too have everything installed but the vending machine and whole foods today gave me errors when actually trying a transaction. I am trying to figure out what the difference is. As of now I do not have Xposed installed.
Click to expand...
Click to collapse
no, that was my mistake. after i installed it to see if all was alright, i uninstalled it, and got rid if my nfc. all my friends have gotten weird messages after install, so i assumed i was fine. i dont need it, or want it, i was just trying to help out my friends.

simms22 said:
no, that was my mistake. after i installed it to see if all was alright, i uninstalled it, and got rid if my nfc. all my friends have gotten weird messages after install, so i assumed i was fine. i dont need it, or want it, i was just trying to help out my friends.
Click to expand...
Click to collapse
No worries. Thanks for the input. Seems to be a lot of different results out in the wild right now. Not the best launch
Sent from my Nexus 6 using Tapatalk

ethan.r.besbris said:
I'm unlocked, rooted, and running Xposed w/ Android Pay setup and have had no issues...
Click to expand...
Click to collapse
What ROM?

Stock.

ethan.r.besbris said:
Stock.
Click to expand...
Click to collapse
Interesting, you're stock 5.1.1 rom like me but you're rooted w/ xposed. The only person rooted where it works is Simms22 and he's on JDX M rom which AP is said not to work. @simms22 what did you do special?

Android Pay Issue with Root

Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Googling has led me t believe that this is an error related to the app detecting root. I tried both of these methods, but neither has worked. http://bit.ly/1LnwzAZ http://bit.ly/1LnwEog . I've tried each separately with rebooting in between as well as trying them together all to no avail.
Other than following the guide above the only root-related things I have modified on the phone are the removal of some verizon apps via titanium backup and adding the following xposed module: "NoSafeVolumeWarning".
One thing that I noted was when I uncheck "Enable Superuser" inside of SuperSu 2.46 it displays a message saying "Uninstall Failed !" It still displays the "Superuser is disabled and hidden" underneath the box and if i enable it again and disable it it does not pop up with the uninstall failed message. Does this have something to do with write protection?
Any help would be greatly appreciated!
Thanks,
Adam

johnnyboy239 said:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Click to expand...
Click to collapse
Having the exact same issue. Just upgraded to 5.1 today, xposed Rootcloak as well as No Device Check installed. Also tried Disable SU. Still get the same issue.

Same. I tried uninstalling SU, Hide My Root, and Rootcloak...nothing has worked. Found out today that the app updated when I went to buy something at Walgreen's. How ****ing embarrassing is that?

So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.

Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.

Same problem, few apps frozen with TiBu and xposed installed. Any other work around? s

johnnyboy239 said:
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Click to expand...
Click to collapse
check to see if your phone allows pin codes to be deactivated at times. I have mine set to not be used at home work and if I am carrying the phone. It is quite useful feature in settings Lockscreen but I am on COS 12.1 OnePlus basically CM

I haven't tried it yet, but I think they only way we'll get this working on root is to install it on stock unrooted, back it up with TiB or Helium, root and then reinstall/restore.

Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.

Ezekial said:
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Click to expand...
Click to collapse
I'm in the same boat. Couldn't get AP to work. Just loaded up the previous version of Wallet. Now have two wallet apps, but whatever. Both appear to be working.

Has anyone tried to get Android Pay working by re-locking the bootloader and temp unrooting on a Nexus device (say, a tablet), then getting AP up and running, and then checking to see if it was usable on your other device(s)??....I was curious if Android Pay would work on ALL of your devices once it was set up properly. Working with lock, unlocking, rooting, etc. is much easier on a Nexus than it would be to work on a Moto, or similar.
Does this make any sense?

KenNashua said:
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Click to expand...
Click to collapse
Tried AP for the first time at Panera today and failed...seems even with Root Cloak on AP and Google Play Service as well as No Device Check, it still fails.

Google Pay: "You can't pay in Stores with this device" on Unrooted LineageOS 16

Google Pay: "You can't pay in Stores with this device" on Unrooted LineageOS 16
Hi. I have issues paying with Google Pay since April of this year. It worked before and without any modifications to the System, it stopped working since the beginning of this month.
I had my Phone rooted ages ago with Magisk but have removed it in January since it was causing the same issue I have now. Only that my Phone is now unrooted. The Phone is Google Play Protect Certified and still passes all the SafetyNet checks (since it's not rooted, this should be obvious)
My Phone is Running LineageOS 16 since March and (as I said before) it was working even with LOS 16. It just stopped working for no appearant reason.
Anyone having a similar Problem, or any idea on how to fix it?

Chickenbreadlp said:
Hi. I have issues paying with Google Pay since April of this year. It worked before and without any modifications to the System, it stopped working since the beginning of this month.
I had my Phone rooted ages ago with Magisk but have removed it in January since it was causing the same issue I have now. Only that my Phone is now unrooted. The Phone is Google Play Protect Certified and still passes all the SafetyNet checks (since it's not rooted, this should be obvious)
My Phone is Running LineageOS 16 since March and (as I said before) it was working even with LOS 16. It just stopped working for no appearant reason.
Anyone having a similar Problem, or any idea on how to fix it?
Click to expand...
Click to collapse
If you had been following the LOS thread you would already have your answer. LOS no longer passes Safetynet out of the box. You need a Custom Kernel.
Or use Magisk again.
Bear in mind that LOS is never supposed to pass Safetynet out of the box. It goes against their policy. The last few months have been a gift, but this is simply a return to normal condition for LOS. Custom Kernel or Magisk. Same as it always was.

Dirk said:
If you had been following the LOS thread you would already have your answer. LOS no longer passes Safetynet out of the box. You need a Custom Kernel.
Or use Magisk again.
Bear in mind that LOS is never supposed to pass Safetynet out of the box. It goes against their policy. The last few months have been a gift, but this is simply a return to normal condition for LOS. Custom Kernel or Magisk. Same as it always was.
Click to expand...
Click to collapse
So the only way of getting Google Pay consistently working on LOS is by using a custom Kernel? I've quit Magisk because it was causing Problems.

Chickenbreadlp said:
So the only way of getting Google Pay consistently working on LOS is by using a custom Kernel?
Click to expand...
Click to collapse
Yes.
The goto Kernel used to be Caesium, but development has stopped again. The last build will work fine though, and was tested a few days ago on LOS. Safetynet passed as expected. There are of course other Kernels and other ROMs. crDroid is based on LOS, and passes Safetynet out of the box.
Just remember to clear Data and Cache on Play Store after flashing the Kernel. Google Pay etc will work fine afterwards.

Or if you build your own LOS builds you can simply let your build patch this in LOS kernel. [emoji4]
Also, most problems with Magisk gets solved by adding those apps to MagiskHide.
Skickat från min ONEPLUS A3003 via Tapatalk

March Update... ctsProfile: false on clean install?

Is anyone getting a problem passing safetynet with the March install? Clean wipe and install, I have root but can't pass safetynet. I've wiped it 4x... no luck. Can anyone help?

I have a feeling SafetyNet hasn't been updated with the March builds (hoping anyway). Unless they've figured a way to detect root and we need a Magisk update.

It wasn't giving me any problems before after installing March update but just noticed now it isn't passing. Sometime in the last 2 days something happened.

Having the same problem. Was fine yesterday.

JasDevi said:
Having the same problem. Was fine yesterday.
Click to expand...
Click to collapse
Guessing Google did something to detect unlocked bootloader since a bunch of people are experiencing it.

I flashed back to a clean Feb build and got the same thing. I thought it was me.

Gosimer4 said:
I flashed back to a clean Feb build and got the same thing. I thought it was me.
Click to expand...
Click to collapse
I tried that as well no luck

I too am having this issue.
I tried fixing it with " Magisk Hide Props Config" with no luck.
Guess we just have to wait until there's a Magisk update

same here

wonderlander17 said:
same here
Click to expand...
Click to collapse
It's a widespread problem being discussed over in the magisk forums. Seems like Google is changing something server side with their checks. Don't think it is related to the March updated since checks are failing on older firmwares

Same here for me.
Anyone else have "Device is not certified", under Play Protect certification?

This happens on nearly all phones running March 2020. Saw it on my Pixel 2XL running March 2020 PixelDust and on a Pixel 3XL running Srock with Magisk as well. Just look into the Magisk Discussion Thread and you'll see that Google seems to have changed something again. Reports are coming in on the said thread in masses.
Sent from my Pixel 4 XL using XDA Labs

Was just about to create a thread about this.
I didn't know this was a common issue amongst many users, so I clean flashed twice in just as many days
I thought maybe I had accidentally flashed the AT&T version when that's not my carrier, or that my dtbo or boot image was corrupt, or patching the stock boot image in Magisk went wrong. I also tried switching kernels and so on.
So far no functionality for my use case has been broken so at least that's a plus.

Same thing happened here with Pixel Experience ROM. Used to work fine, then updated to March 5 security patch, and ctsprofile won't pass anymore.
Though at some moment it did pass, as I've even could get Play Store to show certified and such, but then it failed later on.
Google Pay, banking apps and everything seems to be still working, so it's just a visual glitch for me, at least.
Enviado de meu MI 9 usando o Tapatalk

This literally just happened to me today. Was all good on March update until today and now can't pass cts no matter what.

I read somewhere that may be correlated with unlocked bootloader. So we have to wait for new Magisk update probably.

Oh wow I thought I had installed a module that may have failed it but when I tried just Magisk it still broke. Now I know that the March Security update broke it...

tisla said:
Oh wow I thought I had installed a module that may have failed it but when I tried just Magisk it still broke. Now I know that the March Security update broke it...
Click to expand...
Click to collapse
It's something Google has done on their end. So going to an earlier firmware won't help. Definitely looks like the bootloader status is being detected.

It is most definitely on Google's side, I ONLY use Carbon ROM 9 (AOSP) and it hasnt changed in weeks, no updates, no security changes, then out of the blue a few days ago, it fails. The only thing that changed was Google's side, to test it out, I just rebuilt my Pixel 2 XL with the same Carbon ROM OS, same steps, same base Google firmware (which was working last week), and it fails CTS. No changes on my side, not one, this is Google modding changes on their side unfortunately. I will note, that Netflix shows up in the play store NP (when it IS a problem or MAGISK isnt passing correctly, it wont show up in the play store), so it still works perfectly fine for me. I do not use any bank apps but TD (which is fine, but no GPay) so I dont know if it affects GPay.

GPay still working over here on March update

A71 Data & Root Issues

Hello,
The last couple of months and completely out of no where my 4g data randomly stops working. The status bar icon shows that it's stuck on upload and won't download any data. The only way I've found to fix it outside of restarting the phone is to change the cell band type from auto to wcdma then back.
Anyone have any ideas on how to fix this?
Second issue is with Magisk and I know this is for Samsung but I figure why not ask anyway. As of yesterday after a reboot I lost root. Magisk apps shows I need to install magisk and install the app even though I'm in the app. Also a bunch of my apps are acting like I've never uzed them before and they need to be setup again. I haven't installed any updates so I'm not sure what caused it.
I've tried completely uninstalling Magisk and reinstall and that didn't do anything. The install went through fine but after launching the app it still says no root.
Any ideas?
Thanks

Hi, I think it has been updated and Magisk is useless due to new layers of security. I guess we'll wait until a new rom is made for the new update, including stock. I don't know if Magisk can release a new version and overcome this.
Thanks.

Reflashing the custom firmware then also Reflashing Magisk did get it working for me again.
I've since updated to the newest firmware, flashed OneOS and Magisk and it's been working fine until a little while ago when Magisk randomly shows as not installed again after a reboot.
I take it no one else has had this issue still?
Thanks