I'm running Cataclysm ROM (the Sept. 10 beta), Franco kernel, and I'm rooted and use Xposed. I receive this error when I try to add a card in Android Pay: "Android Pay cannot be used: Google is unable to verify that your device of the software running on it is Android compatible". I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. Wallet still works as it always has.
I've seen scattered reports of this here and there but no concrete solutions. Has anyone figured out a workaround?
I get this same message on a LG G2, fully stock, rooted, running 5.0.2.
After some searching, I found this, and it did work for me: https://www.reddit.com/r/Android/comments/3k0ge4/android_pay_workaround_without_xposedrootcloak/
Short version: In SuperSU, disable root, goto Android Pay and activate cards. After cards are activated, enable root. Cards still worked.
I'm not sure if you will need to remove the xposed framework (uninstall from inside the xposed installer) and then disable root. I do not use xposed, so I can't confirm this.
This worked perfectly, thanks!
I also recommend using Lockscreen Disabler with Xposed to get rid of the lockscreen requirement.
Do you have to be on the stock kernel? I'm on the latest 5.1.x build of stock lollipop and have Xposed Framework & Franco Kernel installed. I tried full un-root in SuperSu and rebooting, but I still can get Android Pay to complete the card setup. Do I have to re-flash the stock kernel? I figured this was going to be a PITA. lol I understand Googles need for security on the devices with Android Pay, but the check they are doing have to be so hard-core.
Were you able to successfully make a payment with Android Pay? I can add my cards to the app, but Android Pay isn't working for me at McDonald's or Walgreens.
Will Android Pay work on KitKat or only 5.x.x? I have 2 Nexus 5s, one with 4.4.4 and another with 5.1. On the one with 5.1, I have tried the rootcloak method to put both New Google Wallet and Android Pay to the list, force stopped Android Pay, ran it to the end, and it still gives me the error saying that it cannot be used and is unable to verify the device or software running on it is Android compatible. I also had already updated to GPS v8.1.14 and was under the impression that it wasn't functioning properly, so I rolled back to a previous version of 8.1.13, still returns the same error.
Did you even read all of what OP had to say:
"I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. "
So your comment helps not at all since OP said they disabled Root and STILL have this issue. I have the exact same issue at OP so your comment is not the answer to this question. Any one ELSE have any idea how to resolve when you have already disabled root as OP said.
---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------
Any one who actually READ what OP said have an answer? How to resolve this situation when you have already DISABLED ROOT in SU.
Possible Fix to Android Pay Root + Xposed Issue...
Just found this. Posted last night. Won't be able to test it for a few hours when I get off this plane...
Since it has bothered me for a few days now, I'm going to post this in a few related threads to help others getting the AP rollout. I just found this which looks promising ( http://www.droidforums.net/threads/new-xposed-module-hides-root.284455/ ) Obviously, this requires xposed and is a little bit off topic here, but this approach was not working for me anyway (stock rom and kernel but rooted and with xposed. Also xposed rootcloak did not work either)
I'm on a plane currently, so I cannot test this, but if anyone else can confirm it works / does not work, that would be great. I had gotten to the point that I was able to set up my AMEX card after a clean stock 5.1.1. install and make a purchase before rooting and adding xposed back in the mix. However, now that I am rooted again, I had a purchase denied earlier today. Hopefully this is the solution.
I have not tried it, but heard it did not always work: https://plus.google.com/u/0/114618417341022236593/posts/dUW1QxDjiFH
this didn't work for me, G3 CM12.1
None of this has worked for me.
Yeah I tried root cloak, disabling super user, and all that but none of it work on my G3 running CM 12.1 either
Disabling root in SuperSU did not work for me.
Also seems no one has had this problem, but on a dark layer theme "invertion ui" the text of the card and exp and ccv are white on white, and none of the above has worked for me either.
Nexus 5
Chroma
Xposed
Hells Core b20
same issue with stock nexus 5 that at some point in the past was rooted... after several updates, i never bothered to re-root. SuperSU still there, but doesn't start - no root. But still Android Pay wont work with this error. ugh.
My workaround was to revert to Wallet.
After failing to get Android Pay to work on my rooted Nexus5 with all the suggestions above, I remembered that Google Wallet worked for me last week before updating to Android Pay. I went to Titanium Backup and restored it, and Voila Wallet with all my data! Next, I unchecked the Auto-Update setting in Google Play for the Android Pay app. Then I remembered a Titanium BU Feature that allows you to break the market link of the app. I have not tried a transaction yet, but it sure looks like the old Wallet app will work just fine.
My wife runs a stock non-rooted HTC Mini2 and is perturbed that her loyalty cards are locked out by Android Pay. I think the solution here is to install a version of Wallet that I found on APK mirror/. I'll need to enable "untrusted" apps in settings after gaining developer rights, but it should work without much effort beyond that. I'll try it when she gets home.
I'm rooted with Xposed. I uninstalled Xposed and SU but I still get the error message. Is there any way round this please?
Related
So I can successfully install superuser v2.40, but it's not working with one of my apps (puzzle and dragons). I have been told me to downgrade to 2.25, but I have been having issues.
The problem is no matter what, when I flash 2.25 it gets stuck in a bootloop. Flashing it on stock, and even flashing it over 2.40, and flashing it over 2.40 when clicking the replace button in the superuser app. What am I doing wrong? Is 2.25 not compatible with my phone?
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
experience7 said:
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
Click to expand...
Click to collapse
Thanks for the reply. On the game's forums, I have been told that masking does not work (if you look at xposed rootcloak it says it's not compatible). And some users have been able to get the game to work with certain versions. I am on the latest binaries and it still doesn't work. The only way to get it to work is to unsinstall SuperSU and reflash it every time I want to play.
On some forums I've read that SuperSU has got a function to "hide" or "temporarily disable" it... Take a look at the app. Hopefully this feature hasn't been removed and maybe that's enough for you to get the game working. It's not a perfect solution but at least you don't have to uninstall / reflash every time. Let me know if it worked
So I have tripped KNOX already. I'm using TWRP, Xstrolite 2.3.
I've tried unchecking superSU root and retrying. I've tried using root cloaker.
Is there an easy way to not have the bootloader unlocked? Or is it once I flashed TWRP, its unlocked forever.
Has anyone else been able to successfully use Android Pay? Post your experience
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
derwreck said:
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
Click to expand...
Click to collapse
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
tlxxxsracer said:
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
Click to expand...
Click to collapse
I also changed the build prop to reflect my SM-G920F model. I really wish I could get Android Pay to function on this device, I tripped KNOX with the full understanding that I was going to lose the ability to use Samsung Pay but never did I imagine that using a custom ROM would cause me to compromise Android Pay as well. I purchased an international unlocked model of the S6 so naturally, the bootloader was unlocked from the factory, I don't know if having an unlocked bootloader necessarily causes you to lose Android Pay. It either has to be due to the fact that we're running a custom ROM, custom recovery, or because KNOX is tripped and it's preventing AP to run like it should.
Try installing the stock rom for your phone. Then under supersu simply uncheck root and see if adding the cards work
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Infekxion said:
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Click to expand...
Click to collapse
When you said you unrooted.. did you uncheck the root box in SU app or uninstalled all together and then reinstalled?
Full unroot under the Cleanup section
Sent from my SM-G920F
think its reading something in the buildprop similar to how google wallet did.
i also tried modifying a few things in build prop to show official firmware nomenclature to no avail.
Infekxion said:
Full unroot under the Cleanup section
Sent from my SM-G920F
Click to expand...
Click to collapse
After you did full unroot. did you reboot? and to reinstall root, you flashed zip again? or what
After unrooting within SU app I just activated my card then reflashed the zip in recovery.
Sent from my SM-G920F
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
rob219 said:
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
Click to expand...
Click to collapse
What rom are you on?
Sent from my SM-G920F
Infekxion said:
What rom are you on?
Sent from my SM-G920F
Click to expand...
Click to collapse
XtreStoLite 1.5 on att
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Mrzoops said:
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Click to expand...
Click to collapse
So i did a fresh install but with Tyrannus rom 5.1, it runs the same base as Xstolite (I believe)
I got android pay working on tyrannus rom 5.1
maybe try backing up your current setup, wipe and flash the rom and first thign you do is try android pay and see if it works. Thats what I did on the rom im running now
I got it working on Tyrannus as well...briefly...although I am not sure how I did it.
Currently on XtreStoLite 2.3, using Xposed + No Device Check and an app called SafetyNet Helper...it says my device is good to go, but Android Pay won't work still.
I hope someone is able to pinpoint what prevents it from working and how to spoof it. I tend to have my phone in my hands a lot more than my wallet.
K, got it working. Fresh install of Tyrannus 5.1, did NOT install Xposed. Immediately turned SU off after 1st boot, before updating Google Play Services. Was then able to activate Android Pay and add cards.
Update 20150924: tried to use it at McDonalds for tap and pay. Android Pay started when tapped but never completed the transaction and I had to use my card.
Hi all, I'm kinda new to learning how the SafetyNet API works, after learning that Pokemon GO and Android Pay use it.
I recently updated my phone to Android 6.0.1, which brought me back to full stock. I still had all of my root apps in, but Android Pay and Pokemon GO still worked with them installed. I re-rooted my phone to change the font, then removed root through SuperSU's "Full Unroot" method. After, I was able to add a card and withdraw from my bank account with my phone, and play the game without any trouble.
Seeing how my phone was working perfectly, I decided to flash the ElementalX Kernel, since I was running it before I updated to Marshmallow. I flashed it successfully and wiped all caches, and was running the new Kernel.
But now, PKGO and Android Pay refuse to work. The logical assumption would be to assume that ElementalX triggers the Safetynet API, but the developer's page says that it works with it. I also vaguely remember that I was able to play PKGO shortly after flashing ElementalX, but I can't remember if I played the game before flashing ElementalX, or after.
What would cause the Safetynet API to trigger? Running SafetyNet Helper tells me that the CTS Profile Match failed, and SafetyNet Playground says that the API call verification failed.
timex987 said:
Hi all, I'm kinda new to learning how the SafetyNet API works, after learning that Pokemon GO and Android Pay use it.
I recently updated my phone to Android 6.0.1, which brought me back to full stock. I still had all of my root apps in, but Android Pay and Pokemon GO still worked with them installed. I re-rooted my phone to change the font, then removed root through SuperSU's "Full Unroot" method. After, I was able to add a card and withdraw from my bank account with my phone, and play the game without any trouble.
Seeing how my phone was working perfectly, I decided to flash the ElementalX Kernel, since I was running it before I updated to Marshmallow. I flashed it successfully and wiped all caches, and was running the new Kernel.
But now, PKGO and Android Pay refuse to work. The logical assumption would be to assume that ElementalX triggers the Safetynet API, but the developer's page says that it works with it. I also vaguely remember that I was able to play PKGO shortly after flashing ElementalX, but I can't remember if I played the game before flashing ElementalX, or after.
What would cause the Safetynet API to trigger? Running SafetyNet Helper tells me that the CTS Profile Match failed, and SafetyNet Playground says that the API call verification failed.
Click to expand...
Click to collapse
Okay, after doing numerous experiments, it was the ElementalX Kernel that was triggering the SafetyNet API.
Kind of a shame, because the development page for ElementalX said that it worked with Android Pay, but I guess Google's always updating it to detect any changes in phone configuration. Kinda surprising that the SafetyNet API doesn't trigger when BusyBox is installed; I would expect it to detect it since it modifies the system a bit, but I guess not.
Oh well. Pokemon GO and Android Pay are working now. Updating to Marshmallow really took away any reason for me to root my phone, so I guess I'll just be using Stock everything for now...
D:
I got a notification this morning saying google play services wanted to update. I thought the google play services app itself was wanting to update, so I went ahead plugged in my watch and let it start.
As it turns out, it was the official update from AT&T to android wear 2.0! Finally! I already had android wear 2.0 on my watch, I flashed it using a kdz that someone had uploaded that had already gotten it on a w200L.
Anyway, once I realized what it was doing I was worried it might brick since I had already updated it previously to a different android wear 2.0 version.
I'm happy to report that it updated successfully. I still had stock recovery so that remained the same. I had used TWRP before, but only booted twrp recovery to flash supersu. I never flashed TWRP to my device, I'm not sure if having TWRP recovery installed would've caused the update to fail.
Changes: I lost root access. That is OK because I only rooted my watch so I could add a new APN to use my watch with a Freedompop sim card. Actually it was a good thing because before the update Android pay didn't work because of my root access, and after the update android pay allowed me to add a credit card and looks like it will work, since I no longer have root, even though my bootloader is still unlocked!
Anyways, I just thought I'd bring this up in case someone else has a question about it. My experience may differ from yours, I am not responsible if you have different results.
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
timonoj said:
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
Click to expand...
Click to collapse
I haven't touched my S7 yet so I can't answer you but this could answer some of your questions:
https://forum.xda-developers.com/galaxy-s7/how-to/debloat-galaxy-s7-services-safe-to-t3432967
You don't necessarily have to root, you have to install TWRP as a custom firmware, then get the script, edit it if you don't want some apps to be removed, apply the script and it's debloated.
But I'm sorry I can't tell you if you can install TWRP without tripping Knox, I can't tell you if installing a custom Firmware will disable Google Pay etc... But I guess you can easily find that information by searching, or someone knowing more than me will help you
Installing TWRP will trip Knox if it's like every other Samsung phone I have owned that referenced Knox or warranty bit in download mode.