Does SafetyNet API require full stock to run properly? - Nexus 5 Q&A, Help & Troubleshooting

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:

Related

Android Pay error: unable to verify that device is Android compatible

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?

xmodgames on s7 edge MM

i got the device rooted and as well as got the mod games, installed it, got the hacks, but when i launch the game, it say its not working, the i went to xmodgames.com/faq, followed the steps for enforcing devices, but nothing worked out.
Did any one got it working.
I dislike cheaters so i dont know of the app. Although i have heard of it.
enforcing??
Going of this, i can only assume it means how SU Linux is.
Permissive or Enforcing.
Requires custom Kernel.
Go to Settings -> About Device -> Software Info -> SE for Android Status = XXXXXXX
Mine is Permissive
If this is the case, Abit extreme for a Cheating program is it not....
deadlyheart4u said:
i got the device rooted and as well as got the mod games, installed it, got the hacks, but when i launch the game, it say its not working, the i went to xmodgames.com/faq, followed the steps for enforcing devices, but nothing worked out.
Did any one got it working.
Click to expand...
Click to collapse
flash custom kernel and have busybox installed
i have installed busy box already
which custom kernel is needed can you put the link to the same
Flash custom rom exyfire and in Aroma choose Jesse kernel...
After that you are not going to face issue. AS I am using xmodgames for COC and its working.
You need any custom rom

Non Root Custom ROMs?

Hello all,
I've recently given in to the draconic overlords that demanded no root (i.e. Niantic). I've rolled my phone back to OxyegnOS 2.1.4 (Android 5.1.1). Are there any more recent ROMs, possibly custom ROMs, that do not have root?
Thanks for any help you can offer.
sultans cm13 is specifically unrooted for apps that require no root. theres some xposed modules for things like pokemon go, banking apps, and snapchat if you want to keep root as well.
http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
You can use Magisk and play your game even if you're rooted. Check this out. You can use it with AutoMagisk, which will automatically unroot on the fly when you open the game!
xymic said:
You can use Magisk and play your game even if you're rooted. Check this out. You can use it with AutoMagisk, which will automatically unroot on the fly when you open the game!
Click to expand...
Click to collapse
Thank you. I was using Magisk on CM13 but that stopped working, PoGo was really intermittent. Then I updated Magisk and phhsuperuser and only after the fact realized that they removed the root toggle feature in the latest version. That's what prompted the move to stock and the question above.
The Jack of Clubs said:
sultans cm13 is specifically unrooted for apps that require no root. theres some xposed modules for things like pokemon go, banking apps, and snapchat if you want to keep root as well.
http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
Click to expand...
Click to collapse
Thank you for this. I knew there were some around but I just couldn't filter them out from the root-included ROMs.

Pokemon GO

guys is pokemon Go is working on custom roms...coz i tried in DU rom unable to log in ...so i roll back to stock help me pls:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Nope... They are blocking all rooted devices. And suhide, rootcloak, and Magisk no longer work do to a mandatory Play Services update which updates SafetyNet to detect all known root hiding techniques, for now at least.

[Q] Magisk root, safetynet fails, PGo still works nontheless?!

Hi,
Upgraded my Galaxy S7 (Exynos) to nougat (clean install).
ROM: https://forum.xda-developers.com/galaxy-s7/development/rom-android-nougat-7-0-beta-3-zpkk-odex-t3507499
Kernel: https://forum.xda-developers.com/galaxy-s7/development/kernel-superkernel-v1-0-t3389247
Used supersu with marshmellow before and stopped playing Pokemon Go when they blocked rooted phones. So I tried Magisk this time.
Installed ROM & Kernel, flashed Magisk-v11.1.zip and phh-superuser-magisk-r266-2.zip, enabled magisk-hide, added systemui, disabled USB-debugging. Everything worked, even safetynet check.
Today (two days after install), the safetynet check suddenly failed (CTS profile mismatch), and I was not able to get it working again. -> PGo did NOT work, root still did.
I tried to reinstall magisk, (flashed the uninstaller and reinstalled same way as I did the first time). Root still works, safetynet STILL fails. BUT somehow PGo works nontheless. (?!)
#1 Why did safetynet check start to fail in the first place? Only thing that changed were some app-updates. No system / security update I know of, OTA is disabled anyways.
#2 Why does PGo work atm after seemingly unsuccessful reinstall of magisk (safetynet still fails...)?
Thanks for your input.
just be happy about that u can play POGO

Categories

Resources