What is Reddit's opinion of
SafetyNet Helper Sample?
From 3.5 billion Reddit comments
Popularity Score: 126
This app was mentioned in 182 comments, with an average of 2.64 upvotes
Best Comments
Yeah I'm sure this even affects Google devs too.
Even more ironic if the SafetyNet team tries to use an app on their bootloader-unlocked personal phones and now even they can't do it anymore. Shot themselves in the foot.
But I'm almost 100% sure this decision was made by a non-developer higher-up who doesn't even know what a bootloader is. Having just an unlocked bootloader is harmless and not a security risk. In fact, having an unlocked bootloader is completely irrelevant once you're using the damn phone, it's only for flashing stuff. Sure, if whatever you flashed alters your /system folder then it should trigger SafetyNet, but otherwise just having an unlocked bootloader is 100% harmless while your phone is in use.
~~EDIT: Editing my reply to a top comment instead of making a brand new post (Edit TL;DR: SafetyNet works with unlocked bootloaders again)~~
~~So all this shit went down in the middle of the night last night, where you couldn't add cards to Android Pay and the SafetyNet Checker app said my Nexus 6P (with just an unlocked bootloader, no other modifications) failed the SafetyNet check. Re-checked this morning after waking up, Google seems to have fixed the issue. I can re-add the card I removed last night to Android Pay (meaning AP works) and the SafetyNet Checker app says my phone passed the check. My phone's bootloader is still unlocked.~~
~~So you guys might want to re-check and see if having just an unlocked bootloader doesn't trip SafetyNet now. I'm re-emphasizing the just an unlocked bootloader part. If you've messed with anything else in the deep bowels of your phone, your results will (obviously) vary.~~
EDIT 2: False alarm, just tried again after some of you said it wasn't working, can't re-add an AP card and the SafetyNet checker failed.
This is because your phone no longer passes the SafetyNet test Niantic have implemented from Google. I received this on my Mi5 today which previously worked perfectly with Pokemon Go. When I checked if my phone passed SafetyNet via the SafetyNet Helper app on the Play Store I found it didn't pass. This is what a failing phone looks like.
My Mi5 is unrooted and has a locked bootloader and still fails after months of working perfectly. I've specifically not updated it because updated versions fail SafetyNet.
I posted this elsewhere as well, but per Ron Amadeo (Ars Technica):
> I ran fastboot OEM unlock but haven't done anything yet (I mostly wanted to be able to flash new versions). It passes this: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample Android Pay seems to turn on and work but i haven't bought anything yet. Imprint works too.
Source: Comments section of https://plus.google.com/+RonAmadeo/posts/SufpdRohtDf
So fingerprint continues to work, Android pay still activates but he hasn't tried a purchase, and it passes SafetyNet API tests after unlocking the bootloader.
Wrong actually. Any device that checks bootloader state will fail. The majority of our devices do not do this. You can run this app to see if you pass: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
I've confirmed it's a problem with PRIV. I can login with my account on another Android device.
This app indicates a safetynet failure on my PRIV - https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
[--- Hello please read me---]
Update on situation please see this comment.
It's been more than 4 hours since I've hidden everything root-related to FEH via Rootcloak and SudoHide. FEH theoratically can't see anything related to root business going on my phone.
I'm sad to say that the 3001 error has returned, and therefore confirm the theory someone else's mentionned on another thread.
Custom ROMs (by custom I mean every AOSP rom, some Cyanogen based ones (not Lineage), and most of the "chinese" branded phones (understand MIUI and consorts) WOULD NOT PASS the SafetyNet check from Google. Usually this requirement isn't deal breaking but for some reason Nintendo decided to add this as is and prevent "non-really-stock-stock" Android users to play the game. Unless there's some spoofer to make FEH believe that the device passed that safetycheck, there's nothing to do afaik.
For those in the same situation, please install this app and report, maybe we'll find something.
No offense but you have a rather shitty and obscure device. The game is checking to make sure SafetyNet passes, and it obviously isn't. However you can double check with this.
To be honest, there isn't much you can do. It's a crappy no-name device and I'm not surprised that SafetyNet isn't passing (wouldn't be surprised if there is spyware on that thing as well). There are many things that can trip SafetyNet, with root being one of them. And while rooting with something like Magisk can be used to trick SafetyNet, I highly doubt you would be able to get that thing rooted. It seems that there is no development at all for it.
You forgot to mention your specific phone. Assuming you have Google apps installed (which you also forgot to mention), the problem is probably something called SafetyNet. Many banking apps, as well as Google Pay and some games, require a SafetyNet check to pass before running, or sometimes they'll run with reduced functionality.
Some phones will "just work" and pass SafetyNet out of the box, as long as you do not have root access installed, which you also forgot to mention. Other phones will need either a modified kernel or a Magisk module enabled to hide the failed SafetyNet check from the app. Both of these methods are "use at your own risk", they are not supported by the Lineage team.
You may note the irony, in the fact that these banks are mostly checking for rooted devices, and one of the ways to get the app running is to root your phone.
To see if SafetyNet is your problem, you can install a SafetyNet checker app. I've used this one before: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
If pogo tells you you have an unsupported OS: 1) Check safetynet status: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample Your phone has to pass (sometimes it may just be a hickup, try a reboot)
2) Go into MagiskManager and repackage it if you have not done so already: MagiskManager->Setting ->Repackage MagiskManager
3) Add pogo to the list of Magisk Hide: MagiskManager->Magisk Hide-> Check Pogo
4) Delete MagiskManager folder created by Magisk after repackaging itself. Located at /sdcard/MagiskManager
I use CyanogenMod 13 with a Nexus 5. I have ADB and App Root access disabled. Using SafetyNet Helper test, I fail the CTS profile match.
If this affects PoGO, this would be unfortunate. I'm not about to go through some awkward process to cloak the root that I'm not even using just to satisfy an app...
Edit: It affects it (PoGO 0.37 claims unsupported device)... So, my options include using some method on CM13 to break the root I don't even use, or to use the stock Marshmallow ROM which has broken GPS which Google refuses to fix. Fantastic :p
Using GoIV is perfectly safe and doesn't break ToS (I use it myself) it looks like you're failing safteynet for some reason, download safetynet helper and see what it says.
S3 CM13 Snapshot PGO 0.37 Working fine. Used SafetyNet Check and got Green light. Turned off root in dev options and removed su from withing TWRP recovery mode /advanced/terminal (Mount system r/w first) > rm /system/app/Superuser.apk
>chattr -i /system/xbin/su [in case Survival Mode is turned on in >SuperSU]
>rm /system/xbin/su
>rm /system/bin/su [ignore this one if it throws an error]
>rm -r /system/bin/.ext
Install the SafteyNet Helper app and run the check and see if it passes. If it doesn't pass, and you're sure you're on an unmodified stock firmware, then there's nothing you can do besides complain to Niantic. SafteyNet is meant for banking, financial and corporate security apps, not games. The test basically checks for a number of things, one of which includes whether or not your device is certified - I wouldn't be surprised if Vivo, like most Chinese devices, isn't certified. With Niantic choosing to use SafteyNet, it means pretty much most of the non-mainstream Chinese devices will fail the test.
Edit: Ironically, there are ways you can pass the test by actually rooting your device, but I wouldn't advise rooting your device just for that.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Install that and see if your phone passes Google's SafetyNet test. If you don't pass it then the game won't work.
Just pitching ideas, no idea if any of them are relevant:
Make sure you have the latest version of FEH
Make sure the tablet is updated to the latest version of Android for that tablet
Make sure you have at least 2GB RAM
Make sure your tablet passes Google's SafetyNet API with this app
Some people say freeing up memory helps or just trying to put less strain on the CPU by closing other apps.
I have heard reports that FEH just doesn't work on some tablets like an RCA tablet.
Have you tried running the safetynet helper to see what your safetynet status is?
Most root implementations require a custom kernel/kernel tweak to work, and factory resetting it doesn't restore the stock kernel (it just deletes user data and clears the cache). That tweak sets Safetynet off, which is probably what you're getting.
If your safetynet is tripped (you can find out via that linked app) then your only bet would be to restore a factory image onto the phone or flash the stock kernel only (the latter will allow you to keep your data and makes sure root has been completely flushed out).
If safetynet gives you the greenlight - you can play PoGo. If you want to be rooted in the future AND bypass Safetynet (so you can play Go), look into Magisk. I use it on my Nexus 6 allowing me to be rooted and still pass safetynet (for Android Pay etc).
Try downloading and running Safetynet Helper and see whether you pass that? If so, then I have no idea what's wrong. If not, your unrooting efforts have not yet been good enough
Likewise, not rooted but have a custom ROM on my nexus 4 to get me to android v6 (not available normally). Checking https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en_GB it seems that safetynet has been updated and rejects me :( Perhaps worth installing to see if it does the same for you?
My Android Pay was working up until a day or two ago. Found a thread on XDA that reminded me to check with the SafetyNet App I'd installed; Failing also now.
I'm running Bone Stock 6.0 with the Nov 1, 2015 Security Update and Google Play Services 8.4.89 without root
*Edit: added clarity on root
The xposed module worked for me so far as I manged to trick this safety net testing app (I cant test android pay as its not available in my country).
Per Ron Amadeo (Ars Technica):
> I ran fastboot OEM unlock but haven't done anything yet (I mostly wanted to be able to flash new versions). It passes this: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample Android Pay seems to turn on and work but i haven't bought anything yet. Imprint works too.
Source: Comments section of https://plus.google.com/+RonAmadeo/posts/SufpdRohtDf
So fingerprint continues to work, Android pay still activates but he hasn't tried a purchase, and it passes SafetyNet API tests after unlocking the bootloader.
Ron Amadeo, of Ars Technica, has unlocked and posted a screenshot to Google+ of the g.co/ABH Verity warning you get after doing so on the new devices (and on other devices running Marshmallow after alteration). In the comments section of that post he has this to say:
> I ran fastboot OEM unlock but haven't done anything yet (I mostly wanted to be able to flash new versions). It passes this: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample Android Pay seems to turn on and work but i haven't bought anything yet. Imprint works too.
> Source: Comments section of https://plus.google.com/+RonAmadeo/posts/SufpdRohtDf
So fingerprint continues to work, Android pay still activates but he hasn't tried a purchase, and it passes SafetyNet API tests after unlocking the bootloader.
Go to settings in gps joystick and tell me what you have enabled.
​
Also, install this and run it. Tell me if it turns up green or red. It should be green with these values:
- CTS profile match: true
- Basic Integrity: true
I have a droid mini and just started getting that problem a couple of days ago, right before the 2.11 update. I think it's Google's Safetynet check failing and making the app think that the phone is rooted, but Google support is being very unhelpful with figuring that out.
Try running this app and seeing what it says.
Has Magisk actually been updated to be able to check SafetyNet attestation results? I didn't think it had been.
The API changed fairly recently. The only application that I know for sure is capable of testing safetynet attestation state currently is SafetyNet Helper Sample.
Google Pay (and other apps like Netflix) use the "Safetynet" API to check whether devices are secure etc but sometimes Safetynet breaks when applying system updates (this has happened a lot with OP for some reason), or intentionally when you unlock the bootloader (and Root). Root mods like Magisk hide this, but that'll only benefit you if you're unlocked the bootloader.
You can tell if Safetynet is to blame for Google Pay disappearing using a test app like this one. If it returns "Fail" then you know something went wrong with the system update and it broke Safetynet (somehow).
You can always install this app to check and see if your phone passes SafetyNet. Sometimes even a non-rooted device can fail the SafetyNet check and any apps that use it will block you. Not sure if Pocket Camp uses this check like Android Pay and Pokemon Go do.
Also, if your phone was rooted in the past but isn't rooted now there could be some leftover files that it's finding and thinks your phone is still rooted.
Rooting is the issue.
Google uses an API called "SafetyNet" which basically checks if your phone is modified. Rooting causes your phone to fail this check and modifies your save file so you can't play it unless you redownload the game and relink your Nintendo account...until the error pops up again, usually 30 minutes later.
There are methods to hide root, but it's a losing arms race as these methods must be updated everytime SafetyNet is updated. The only way to avoid the error is to unroot your phone properly (not with using a rooting app).
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
The above checks if you pass SafetyNet.
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
If you want to try hiding root, Magisk + MagiskSU + MagiskHide, don't use Xposed.
Thanks for the link. I just side loaded this .019 OTA file over the existing .017 on my 6P. And now SafetyNet Helper finishes the CTS test positive (whereas it failed with .017). So I should be good and I will check Android Pay later today.
Locked and unrooted here as well, getting a "CTS Profile Match" value of False using SafetyNet Helper to check my SafetyNet status. Is everyone else getting the same issue? Only started with September OTA (I'm on T-Mobile if that's relavant).
Thanks for the link. I just side loaded this .019 OTA file over the existing .017 on my 6P. And now SafetyNet Helper finishes the CTS test positive (whereas it failed with .017). So I should be good and I will check Android Pay later today.
Locked and unrooted here as well, getting a "CTS Profile Match" value of False using SafetyNet Helper to check my SafetyNet status. Is everyone else getting the same issue? Only started with September OTA (I'm on T-Mobile if that's relavant).
Do you have developer settings enabled?
If so check "OEM unlocking" that should be disabled. And "USB debugging" that should also be disabled.
Did you have the phone RMAed or second hand? Because if so it could be possible that the previous owner has already done the damage. Try using a safety net detector such as this one to see if that is what the issue is. (https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en)
If you haven't done anything and really want to buy gem best bet would be a factory reset to eliminate the error.
Just logged out and logged back in and mine is still working. Try downloading this checker to see If your phone is passing the safety net check by Google https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Yes. The above should work for a rooted phone, but there's potentially an easier way. It depends on what firmware you have and what rooted functions you want to keep, like Xposed.
This guide should help you out. Make sure you also install SafetyNet Helper or some other app that can check if you pass SafetyNet after hiding/switching root.
I use a Galaxy S4 running on 4.4.2, and RootSwitch 1.3.3.2.
Is your device rooted or do you have a custom ROM? Nintendo has banned those devices and therefore it will not show up in the play store of those devices. Try installing this and if it fails (red screen) you won't be able to download it from the play store or use and apk (will crash on start). You can try bypassing safetynet with magisk and enable magisk hide.
私の環境でもテストしてみましたが確かに起動しませんね... おそらく、Root環境の削除を行ってもSafetyNetAPIを通過する事ができないのでFGOを起動させることができないのだと思います。
Safetynet apiを通過できるかどうかのテストは以下のアプリから確認できます。 https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=ja
I tested it in my fx0 (cm b4), it certainly does not work. This is because cm rom can't pass safetynet api. You can check safetynet api below. Https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
been doing some tests!
if your phone fails safetynet the app will show up as incompatible/won't appear in your store (you can check it by downloading SafetyNet Helper Sample https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample)
based on the info in this thread it wouldn't be a stretch to guess that the app itself also checks this after some time and bricks profile data
EDIT: once i unrooted i passed safetynet and have been enjoying the game for a few days sans ban!
Can you log on to the trainer club online?
I think Niantec sends an email once you're banned, so you should have been notified.
Also, you will also receive the same message when you are blocked due to running a rooted phone or not passing the safety net check. If you try this app, will it say that your phone passes the test? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
You need to flash back with stock ROM. Pokemon Go uses Google safety net.
This App should give green to Play Pokemon Go.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
does your rom by any chance have a built in root functionality which you could enable if you want to? because the present of this option alone will make you fail the safetynet test.
You can use THIS link to test if your phone is able to pass the safetyNet check.
If you do pass it, but still can not log into pgo you should try loging in on antoher device
Das hat eventuell mit safety net zu tun. Es gibt eine App, mit der man safety net testen kann: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Eventuell liegt das Problem darin, dass auf seinem Handy "Google play services" nicht ausreichend Rechte hat im Hintergrund / bei mobilen Daten zu laufen.
You MAY still have the su file in /system/xbin & /system/bin. These need removing or renaming in order to play Pgo.
try: S3 CM13 Snapshot PGO 0.37 Working fine. Used SafetyNet Check and got Green light. Turned off root in dev options and removed su from withing TWRP recovery mode /advanced/terminal (Mount system r/w first) > rm /system/app/Superuser.apk
>chattr -i /system/xbin/su [in case Survival Mode is turned on in >SuperSU]
>rm /system/xbin/su
>rm /system/bin/su [ignore this one if it throws an error]
>rm -r /system/bin/.ext
If no joy You MAY still have the su file in /system/xbin & /system/bin. These need removing or renaming in order to play Pgo.
try: S3 CM13 Snapshot PGO 0.37 Working fine. Used SafetyNet Check and got Green light. Turned off root in dev options and removed su from withing TWRP recovery mode /advanced/terminal (Mount system r/w first) > rm /system/app/Superuser.apk
>chattr -i /system/xbin/su [in case Survival Mode is turned on in >SuperSU]
>rm /system/xbin/su
>rm /system/bin/su [ignore this one if it throws an error]
>rm -r /system/bin/.ext
The message is caused by your phone not passing Google's SafetyNet API test.
Use this app to check your status of SafetyNet:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
you could try downloading this app and try it with wifi and mobile data. This is basically the same test the pogo app does when logging on and you can at least see where the problem lies.
As a last tip i would suggest you compare the settings on your windows phone and your android device regarding background data. If you can't find the error this way i don't think i can help you any further, sry :/
First, make a full nandroid backup, just in case something goes wrong.
In TWRP, mount /system (as read/write), backup and then delete /system/bin/su and /system/xbin/su, flash magisk and phh's Superuser(magisk version) and reboot.
Then install phh's Superuser from the Play Store and Magisk Manager from xda's magisk thread.
Now you can use Magisk Manager to enable/disable root. When it's disabled you should be able to use Android Pay. You can use this app to test.
I erased /system, flashed ROM and opengaps, deleted /system/bin/su and /system/xbin/su to avoid conflicts, then flashed magisk, phh's Superuser(magisk version) (and viper4android magisk version, optional), and rebooted.
You can use this app to check if your phone passes SafetyNet. Just remember to disable root with magisk manager before you try.
I can't help you with the Redmi Note 2 but I got my Redmi Note 3(snapdragon) working with cm. I'm using this rom. Don't flash supersu(I personally couldn't get it to boot after doing so). Instead enable dev options, enable root, install supersu from the play store, don't update binaries but instead just hit full unroot. Restart, make sure root is disabled in dev options then install pokemon go.
You will fail SafetyNet Helper but still can play pokemon go.
Hi, I thought this was going to suck, but it worked out really well. I have an Alcatel One Touch Idol 3 on Cricket; nonetheless. I am running Android 6. I know the instructions on XDA can be confusing, just take your time and READ!
Here's what I did:
- Removed SuperSU (Or whatever equivalent you're using)
- Flashed Magisk-v6
- Flashed phh superuser
- installed magisk manager apk
- installed phh's superuser app
You toggle root with Magisk manager.
You can test with safetynet helper.
Added bonus is now I can use Android pay!
Android Pay use SafetyNet to verify the device and ensure it is compliant.
You can verify the device state using SafetyNet Helper Sample.
I just did some digging for you and your rom already has systemless root as of this post http://forum.xda-developers.com/showpost.php?p=65188779&postcount=4564
If you're curious enough to try it with your M7 just do a full wipe/reinstall of the rom and use https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en To see if it passes still. (and if it does, then switch to the systemless versions of adawy/xposed)
Definitely the easiest solution. But the best way to keep up to date and also use pay is this:
1. Use the unroot option from SuperSu app, choose to restore the boot img, but not to restore stock recovery (we need TWRP for the commands later)
2. After that is done and booted, reboot to TWRP via key combo or adb reboot recovery
3. In TWRP go to Advanced, Terminal, hit the checkmark to choose any starting folder (doesnt matter which)
4. Type in the terminal:
> echo SYSTEMLESS=true>>/data/.supersu
hit enter, and then type in: > echo BINDSYSTEMXBIN=false>>/data/.supersu
enter again
5. Now leave that and install your 2.66 or newer SuperSu zip.
6. check that safetynet isnt triggered by using <strong>this app</strong> or adding a card
Check whether it says failed or succeeded. I don't think there should be a safety net issue on pixel experience without root, but everything sounds like a safetynet fail. If that's the case indeed , you have no choice but to root . There is a way you can bypass safety net if you root. Get magisk and magisk manager and root (plenty of guides on internet). After that install a magisk module called magiskhide props config . See if it works . If it doesn't there is something called universal safetynet fix magisk module . Get that too , if both combined don't work (you need the first one for the second one to work), install termux from play store , type :
su (it will ask for root permission, grant it)
props
And then what read the on screen instructions to change your device fingerprint to pixel 4xl(you can use others too, I use it personally) . This will make everything think you have a pixel 4xl. Like Google etc.
Have you unlocked your bootloader at any point?
You can use an app like this one to tell yo if you pass Google's Safetynet which most financial apps use to check for compromised devices. https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Thank you!
I enabled "Update recovery" and all went smooth. No issue with setting bank app (Citi) and Google Pay with linked CC. Here's screen from SafetyNet Helper Sample (if that means anything).
Which update version of Android 10 are you running? Is the phone rooted or not? Did you perhaps leave USB debugging on inside developer mode?
It could also be a safetynet failure which you can check with the safetynet test app to see if it is working as intended. Some games really don't like if the device is rooted and just close by themselves when detected.
That doesn't sound like Tasker. That sounds like some sort of root app or a modification app.
Try the SafetyNet Helper Sample ( https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en ). If the check fails, then you've got something tripping SafetyNet. Aside from tasker (which in my experience has never even come close to SafetyNet) what else have you installed?
Just a quick info for anyone having this.
If you are on a custom rom, make sure SafetyNet works as intended. Check with SafetyNetHelper Sample, if it reports problems, Brave won't show Rewards.
Fix is to unroot or, if you use Magisk to root, follow this guide. For me (Pocophone F1) hackintosh5 Version worked.
Does the phone pass Safetynet (https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample) ?
If not then Oneplus needs to update google with the device profiles/signatures for things that use it (like Google Pay) to work.
The other thing to try is to uninstall and reinstall the app from Barclays in case they issue different versions for Android 10 vs Android 9.
Is the CTS profile match fixed? I couldn't use google pay with beta 1.
Can someone with beta 3 run this app and confirm that everything is in green please?
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Do you know if either of those apps normally rely on Safetynet passing?
Were you able to successfully make a purchase with Samsung pay? (Just making sure we're on the same page for what "works" means lol, but I imagine with Knox, Samsung Pay probably doesn't care about Safetynet)
I'm not sure. Doesn't seem to be a widespread issue, so it is specific to your device. Are you using a custom ROM or stock? Have you tried making sure you are passing safety net? Here's an app to test that:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
If all else fails I'd go with a full factory reset/wipe and try again.
SafetyNet Helper Sample:pass and SafetyNet Test:failed for me. I have tried to root and hide in magisk and change the device fingerprint,still not working.
May not be rooted but it may not be passing Google safetynet because xiaomi might not have submitted the phone to Google. Try test with this app https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Even in systemless mode, Xposed can always be detected, and will make SafetyNet fail.
Use something like this to check SafetyNet.
Well, that's an unexpected result from my point of view.
What is actually supplying the error, and what precisely is that error? What are you actually failing on, basic integrity, or compatibility test suite?
There's a lot of applications that give false positive or false negative results at the moment. A simple and effective test application is SafetyNet Helper Sample.
The results with play store certification seem to suggest that you're able to pass CTS attestation, and basicintegrity is a much weaker form of validation that very few applications actually care about. To the best of my knowledge neither of the applications you have named care about basicintegrity status at all and just validate cts status so this is altogether quite confusing.
To reiterate:
what are the results as given by the test sample application supplied above
what is/are the error(s) given to you that cause you to believe an unlocked bootloader is the problem exactly, and by which application(s)?
Edit: we should take this to PM this is well outside the bounds of support for this sub
Coming from a midsize town where we raid a lot during lunch, and on the 7th day spin those stops :). Use a Safetynet checker like this one to see if there is a lot to Niantic as a company.
Get this app and check the result of the scan. This sounds like what would happen if your phone doesn't pass SafetyNet tests. This can happens for a variety of reasons, the most common being that the phone is rooted, but can also happen on phones of little-known manufacturers, particularly Chinese brands/cheap phones, especially if they come pre-loaded with a custom ROM or root.
Use a Safetynet checker like this one to see if Safetynet is passing on your device.
There's been times in the past this message has appeared when Safetynet has failed on the device for whatever reason (unlocked bootloader, Root etc). That'll at least narrow it down.
OTA updates aren't the full OS. They just patch your current one. Normally there are protections against trying to patch a modified OS but I just want you to flash the full stock image to make sure. Also this should fix any issues with dm-verity.
Although we might as well start somewhere simpler. Please install this and tell me if it passes the tests.
Snapchat uses Safetynet like many other apps you wouldn't think need it (Netflix, AC: Pocket Camp, PoGo etc) so if safetynet is tripped (which it will be with an unlocked bootloader) then that'll be why you're getting this.
You can use a safetynet tester to see if your device is tripping safetynet which should narrow down what's happening.
If safetynet has been tripped, you can flash a custom kernel which hides the unlocked bootloader (practically all the "big named" kernels do this) or you can flash Magisk which will also hide the bootloader status + give you root and other things like OP related modules for improving the camera etc.
SafetyNet is a security thing from Google that detects device modifications. It's what stops you from using Android Pay. And some other apps, primarily banking apps check it too. Some apps also use it to stop showing up in the Play Store, Netflix does this but it can still be manually installed. You can check if SafetyNet passes with this.
You don't need antivirus. Android isn't like Windows, where anything can access anything. Learn more here. Pretty much all antivirus apps on the Play Store are scams. There are a few exceptions but these are more for alerting you if something happens afterwards, they won't actually be able to do anything. And sorry but anyone online who recommends that app is a complete retard and they shouldn't be trusted for anything. Cheetah Mobile is known to put bloaty, shitty apps on the Play Store that are borderline spyware and adware, and then they pass these off as "utility" apps. A lot of the antivirus apps and "booster" apps on the Play Store are like this. So no, you don't need antivirus.
If you install this app, does your device pass?
Since you unlocked your bootloader, there's a chance you've also tripped safetynet. Thing is Netflix also uses Safetynet, which is most likely why it isn't working for you.
You can check your safetynet status using an app like this one. If it's Red/tripped then you have a couple of options (as relocking the Bootloader will wipe the device):
- Flash a custom kernel which removes the unlocked bootloader check. Editing your prop file in this case won't solve the problem as it sounds like a safetynet problem, not a device problem.
or
- Flash Magisk (which will also root the device, but bypasses Safetynet).
Doing either should allow Netflix to work on your device.
First you need to test Safetynet, you can do it with this app.
If it doesn't pass, it means that you have the safetynet issue. I found this thread in xda that talks about unlocking the bootloader to change the rom (just note, that if you fail you can brick your phone, so you really need to be careful). If you install the cyano rom that it's linked in that thread, and use alongside it Magisk, you should be able to play the game.
Also, if you check the box, you will be able to see the actual model (in case that it has a more specific model, this helps to see which guide would work with it).
You would have to flash over the original firmware for your S5 using a program such as Odin.
Unfortunately I don't have a Samsung phone, so I don't have a lot of experience with Odin, but a quick Google search brought me to this webpage that seems to have instructions for your exact model.
I'm not sure how trustworthy the site is, but it looks okay. The download links don't look suspicious, but if you'd rather use a different website, just make sure the firmware is specifically for the SM-G900I and not another S5 model.
Also, a good app that tells you whether or not you're passing SafetyNet: SafetyNet Helper Sample
very interesting.
Did you use ADB to adjust anything like the display dpi? Maybe try to set the display scaling under settings to standard if you've changed it. Some people with stock S7 edge had similar issue.
Phones failing safetynet check for no apparent reason is somewhat common from what I see. Google and OEMs really need to figure this out.
You can use an app to see if your phone can pass safetynet check https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
The app will not show up on the app store if you get the 803-3001 error. Or more accurately speaking, it won't show up if you don't pass Google's SafetyNet API.
The error 803-3301 occurs if your phone does not pass SafetyNet, typically with rooted devices or emulators--or even a phone that was previously rooted and did not unroot properly.
I was using a GS4 with 4.4.2 and using RootSwitcher 1.3.3.2 to bypass SafetyNet.
This guide might help you.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
The above helps you check if you pass SafetyNet.
Now, AFAIK, the most updated firmware for GS4 is 5.0.1. I actually flashed with a stock S4 5.0.1 ROM--or you can update with Samsung Kies--because I was tired of having to bypass SafetyNet as it's basically an arm's race...but I removed all the bloatware from the stock ROM first, which is the only reason why I really wanted root.
If you aren't super tech savvy, don't know if your phone is modified, and SafetyNet isn't passing with Rootswitcher on: you can use Samsung Kies to update your phone and update to 5.0.1 or even factory reset it to 5.0.1. If you want to keep 4.4.4, you're going to have to know how to flash a stock ROM with Odin and all that jazz.
I guess it is popping up more often...I had an issue with it back in Feburary since I'm rooted, then fixed it by hiding root and haven't seen it since.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
The above to check if you pass SafetyNet. Note that some Chinese Android phones won't pass SafetyNet. Even phones that aren't rooted--if they were previously rooted and improperly unrooted, there may be traces of root left causing it to fail SafetyNet.
If you're desperate for a fix and have a legitimate phone that should pass SafetyNet, you can flash a stock ROM--but this will wipe internal memory so back everything up to a microSD card. Flashing a ROM requires you to download the stock ROM from a 3rd party site, and using Odin3 to flash the ROM.
Started with a Galaxy S4 on 4.4.2, rooted by unlocking the bootloader and flashing a rooted, cleaned stock ROM that I found 3 years ago on XDA. I hid root using Root Switch 1.3.3.2.
Recently I flashed to a stock ROM 5.0.1., deleted all the bloatware with root, and used Magisk to hide root.
About a week ago I unrooted my phone with SuperSU because I didn't need root access anymore and at some point, methods of hiding root are going to stop working since it's an arms race between developers and SafetyNet.
803-3001 is the soft-ban for devices that do not pass Google's SafetyNet--typically it bans rooted devices/emulators, but can sometimes trip on unmodified phones.
If you're not rooted, uninstall/reinstall the game. You'll have to relink your Nintendo account to get your save back.
If you are rooted,
This might be a helpful guide. You can also check if your phone passes SafetyNet with this app:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Edit: If you do not have a linked Nintendo account, you will have lost your save. The best you can do is send in something to customer support and hope they have that data somewhere, but I haven't heard of it being successful.
> https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Thanks! no... I don't know why that would be. It's a new phone I've not installed anything even vaguely rooting on it. I reset to factory when I got it.
What could cause this to fail?
Assuming you've already tried re-installing PoGo and that doesn't work go download and install safetynet helper and see what it says.
With the OnePlus 3T, I opted to stick with stock OOS, unrooted, with a locked bootloader. I have not encountered that message. I assume you are setting up Samsung Pay by initiating the install through the watch? The Samsung Pay manager should be through the Samsung Gear phone app.
I'm sure there are other ways to test it, but I would download this SafetyNet app and see if it passes: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Worst case, I would reflash the latest OOS update. I'm on Beta...3? whichever the latest beta is...
SafetyNet from Google can tell you if your firmware is 100% official. Without going into the technical, this feature will compare the details of your device against the manufacturer's version. That way, they can tell if your firmware is like that which comes out of the box. Try this checker to verify.
You can find stock firmware for Samsung devices here.
try this.
FYI, you cannot use modified ROM. You need to use the official one. I see Note 3 doesn't have Android 6 support. So, it'd better if you revert it back to the official one.
You can test if you pass SafetyNet with this app. It may not give 100 % correct results all the time, though. If you do pass it and still can't get to the game, you may be experiencing the bug I wrote about in the post.
Another possibility is that the error might actually get stuck there if the device has even once triggered SafetyNet. You can try reinstalling the game (if you have linked your Nintendo Account) and then try again and see if you still encounter the error.
> i just assume they have patched safety net
I use this APP to check whether safetyNet is the problem or something else
Try downloading one of the Safety Net checker apps on the play store to try and get an idea of why your phone is not allowed to do it. It could be a low level malware or something that is tripping the safety net.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
The errors will be gibberish most of the time, but a cursory google or reddit search should get you some sort of translation as to why it's failing.
Also check this reddit thread over in /r/pokemongodev for another weird quirk of WiFi vs Cellular connections.
Hope this helps, oh, and I am not the developer of the safety net app...I just wanted to point that out.
> Just beware if the phone has been in use this whole time it might be heading towards the dreaded mmc (I think) error, which is the death of the phone and seems to happen at random after about 2.5 years of use. It's hard to tell if it's an inevitable end or not, or if it's just taken out enough phones to be noticeable.
I don't know about this. Out of the millions of Note 4's sold, I can only find at most 100 (being generous) incidents related to this online. It's probably just blind luck if you receive one that errors out (X amount out of 10,000 units will have issues).
I don't think this issue should play a part in whether you purchase or keep the Note 4.
> Will rooting it breach security of the phone/ prevent me from using android pay?
Yes. Check Xda forums for some workarounds such as suhide or Magisk. You can check whether you'll pass by using the SafetyNet Helper Sample app.
I haven't tried lately, so it may be worth experimenting more.
So if you've unrooted the phone it's possible the Bootloader is still unlocked or that you're possibly running a custom bootloader.
I think you're failing the SafetyNet check that the game does each time someone tries to log into the game.
Try this app or something like it to see where you might be failing SafetyNet.
It might require you doing a full device recovery using the Manufacturer OS.
Good luck.
You can try this to check if you pass safteynet: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
When you do the magisk install. Make sure you open up phh's superuser app, and then go into magisk. Then you will see root as a module. Then enable magisk hide. After doing all this, I needed to reboot to get it to work.
I've never used magisk su. Once you turn it off try this app and see if it passes. If not then i have no clue what to say.
The most important step from all tutorials/guides of how to play pgo with root/xposed is that you have a clean state at the beginning, meaning that you pass the safetyNet with your phone before you begin flashing stuff.
The Safetynet Checker from the playstore is a good tool to check this.
The most common mistake I read about here, is that people do not pass the check, because they did not flash the suhide uninstaller to get rid of the old suhide before flashing something new.
Whoops, meant to post this in the comment below (still new to Reddit, don't know the ins and outs just yet and couldn't find edit.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
My devices are failing "response validation".
snet is part of Google Play Services. If you restrict or disable its data, snet cannot run, and you'll fail the check.
As for the other issues, it could be related to snet, or maybe not. I'd allow the data for GP first, and see if that resolves your issue.
Also you can download Safety Net Helper Sample and check if you pass snet with that. More reliable than PoGO for snet testing.
You probably still have the su file in /system/xbin & /system/bin. These need removing or renaming in order to play Pgo.
try: S3 CM13 Snapshot PGO 0.37 Working fine. Used SafetyNet Check and got Green light. Turned off root in dev options and removed su from withing TWRP recovery mode /advanced/terminal (Mount system r/w first) > rm /system/app/Superuser.apk
>chattr -i /system/xbin/su [in case Survival Mode is turned on in >SuperSU]
>rm /system/xbin/su
>rm /system/bin/su [ignore this one if it throws an error]
>rm -r /system/bin/.ext
Try this app, https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
My nexus 5, unrooted fails it CTS and I get the same error as you. I was able to login in via my nvidia shield tablet so I know I am not banned.
I sent a support email to Niantic 2 days ago but no reply so far.
Would you be so kind as to double check that it's safetynet certified?
This app will tell you: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Edit: downvoted? WAT.
The re-downloading is due to insufficient space on the phone. Make sure you have around 1GB free to be on the safe side.
However, 803-3001 is due to your device failing to pass Google's SafetyNet. It's basically a check every time you start FEH to see if your device is modified from manufacturer defaults--typically, it's due to having a rooted device or a device that was unrooted improperly. If you don't pass the check, it modifies a data file on your phone (DeviceAccount.xml) so that you cannot play. Re-downloading fixes the issue temporarily because it deletes the modified DeviceAccount.xml file on your phone and installs a new one. Here's an app that checks if you pass SafetyNet.
Here's one fix that's been popular with emulators like Nox.
Here's another fix if you don't like the first method with Magisk.
Bypassing SafetyNet is an arms race though. At some point the above methods may stop working, so you may want to consider unrooting if you don't need root access anymore.
And as a final note, make sure you link your FEH account to a MyNintendo account before you do any of this stuff, although it sounds like you've already linked it.
Sure about that? I'm curious if you want to entertain running this: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Are you rooted?
Try this app, does your phone pass?
Does SafetyNet pass? Test with this.
Works fine for me. Pixel
What does this app say for those failing: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Rooted, emulated, and/or unlicensed devices (ex. from China) will run into this issue (error 803-3001) if you can't pass SafetyNet, although I don't know how much you've looked into it. As always, make sure you backup your phone and link your FEH account to a MyNintendo account in case something goes wrong, and err on the side of caution.
Here's a way to check if you pass SafetyNet after implementing possible fixes.
Here's one way to bypass SafetyNet, typically for Nox emulator.
Here's another way to bypass SafetyNet, although one method (RootSwitch) might be outdated. Magisk has been working for most people on android 5.0 and up.
Bypassing SafetyNet is an ongoing arms race--SafetyNet will be updated to patch exploits and people are going to have to find ways to bypass it again.
You can always unroot your phone if you have no further need of root access--although depending on how you rooted, there may be traces of root left behind which causes the device to fail SafetyNet. Flashing stock firmware wipes the device but is a last-resort way of getting everything back to new if you need a phone to pass SafetyNet.
Pokemon Go only works if your device passes the SafetyNet test. I think custom roms are not capable of passing. https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
This app will tell you:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample maybe try this Ap and see, although I don't think it checks CTS profiles
You need to be aware of these 5 things:
Make sure Knox has not been tripped. If it has it means that the phone has been rooted or modified in some way at some point. To check knox you can do it in three different ways, putting the phone in recovery mode, checking in system settings or download a 'Knox trip' app from the play store.
SafetyNet CTS. Most people do not know about this, but this is a Google security feature that has been around for a while now, and it detects any modifications of the phone, even if you are running on stock firmware. For example, if the phone has had an official firmware but with a different CSC. While still being official, it is different from stock and Google will flag this and wont pass the test. This CTS check is used by many important apps like Google Pay, banking apps etc. And if you fail you can't use the apps. CTS can be checked using this app: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Screen burn / Dead pixels. Use an app called 'Dead Pixel Fix' put your phones brightness on full and flick through every colour that appears on your phone whilst carefully looking for any screen burn and dead pixels.
Check the IMEI. You can find it in your system settings>about phone. Or dialling * #06* Once you have your IMEI visit an IMEI checking site like https://www.imei.info/ . It should be free so don't pay for anything. This check will tell you whether the phone has been reported as stolen or blocked on any carriers or not.
Stay away from refurbished phones. Galaxy Note 9 is IP68 water and dust resistant. If the phone has been 'refurbished' it's almost always the case (no pun intended ��) that the back has been opened. This means that unless it has been refurbished by Samsung, it is unlikely to retain the IP68 resistance. So your refurbished phone is not likely to be waterproof. Furthermore there can be dodgy batteries / other components that have failed and been replaced with non-oem parts. Stay away from these. Just buy a good used phone. A good way to know if the phone is refurbished or not is to see if the devices serial number is printed on the back glass. If its not there, its been opened and the back glass is a replacement, dont buy it.
These 5 things will take around 5 minutes max to check in person. Or if you're buying online, I would recommend you use a site with good return policies as for most of these checks you need to have the phone in person.
And just a little side tip..never log in with your main google account in the set up screen or anywhere else in the first use. There could be keyloggers / or other bad software that could steal your datails. Make another google account to download the apps above, and make sure steps 1 and 2 above have passed. If they have, then you know its at least safe to use your phone.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Use the above app to check if you pass SafetyNet, which tends to be the cause of most errors.
Do you pass safetynet?
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
When you run this app what is the result? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Did you hit the uninstall root button? As for the apps that detect root, does SafetyNet pass? Check with this.
The problem is that you're rooted. Android has a feature called SafetyNet, which detects if your device is rooted. You won't be able to login unless you pass SafetyNet.
You can check if this is the case by installing SafetyNet Helper. Anything other than a green screen means you've failed SafetyNet.
To get around this, unroot and read up on how to install Magisk. Make sure your phone is compatible. If your phone isn't compatible with Magisk, you're likely out of luck :(
Download an app called "Safetynet Helper" on the Play Store. It'll tell you whether your device is tripping Safetynet (in case of an unlocked bootloader or you're rooted).
If Safetynet is not triggered - it maybe a glitch, but I can guess it'll be tripped somehow (as your partner can play fine on an identical tablet). If the app shows you a red screen and tells you Safetynet has failed - that'll explain why PoGo isn't launching and is giving you that message. Other apps which use Safetynet (Snapchat and Android Pay come to mind) will give you an error as well if safetynet is tripped (safetynet being Android's version of an anti-tamper mechanism).
If you're running a custom ROM or are Rooted (SuperSU in your app drawer for example), flash this zip file in recovery to remove root if you are rooted/running a custom ROM with root built in (If you have root, it'll be restored in the next step). It'll delete the root files as using the "unroot" function within SuperSU and other root apps doesn't really clean up the files.
Flash Magisk if possible (some Samsung devices aren't supported however so you'll need to do some digging before doing any of this) and enable "Magisk Hide" within the Magisk App as that'll allow you to be rooted AND bypass Safetynet/play PoGo fine. Magisk has root built in so you don't have to worry about re-rooting etc.
Run this app and see if the device passes SafetyNet.
Delete xbin also. and then run the safety net helper app https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
If you're so smart install this and see how you do
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
This one works well enough
Maybe your phone isn't passing safetynet. You can test that with this app
What does this app tell you?
​
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Does it pass SafetyNet? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
If you are willing, you could always use an app to check SafetyNet like https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Are you able to pass SafetyNet?
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Hum I got a successful test with SafetyNet Helper Sample (got true for both CTS profile match and basic integrity) but my phone is failing SafetyNet Test ("fail (SafetyNetApi.AttestationResult success = false or empty payload)") and Root and SafetyNet Checker ("device is NOT compatible with SafetyNet", "SafetyNet request: Failed").
Phone is unrooted (well it was rooted at some points), never changed ROM. (Android 4.4.2, bought in 2015 some months after release, manufacturer left it at 4.4.2 before discontinuing it)
Weird. Did you used this app? (https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=es_AR). Most of the SN checkers are outdated and do not work properly since the latest update of SN.
Someone found what was causing the problem: the game is searching for folders (in your internal and external storage) with specific names (ex. Magisk Manager). If it founds one => unauthorized device lockout error.
https://www.reddit.com/r/TheSilphRoad/comments/97xv7s/unauthorized_device_lockout/e4df1so/
In my case: I had a Magisk Manager folder in my internal storage from back in the days I had my device rooted (almost a year ago). As soon as I removed the folder the game started to work.
Does it pass SafetyNet?
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
First try this app and tell me if you get a green check
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
You can see if your device passes the basic Safetynet checks with this app:- https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Does the SafetyNet Helper app say you're passing (all green)?
Could you test with this app? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Nope. If you didn't manage to link your account, that account is gone.
If you're phone-savvy, the above helped me avoid the error.
Nox emulator also has a way to get past it. Top of page 4:
https://serenesforest.net/forums/index.php?/topic/68725-fe-heroes-error-803-3001/&page=4
Too bad about the Nowis, though.
Edit: If you don't need root and don't want the hassle of trying to bypass the error, then unroot your phone. The error occurs because some phones (typically emulator/rooted devices, but can happen to unrooted devices too) fail to pass Google's SafetyNet API. You can check if you pass SafetyNet here:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Methods to bypass SafetyNet are time-limited. When Google updates SafetyNet, the methods to hide root may no longer work, and you'll have to wait for someone to figure out a way past it.
Also does this app show green when you try it? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Do you pass the SafetyNet check?
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Is SafetyNet passing? Test with this.
Depends. You should try downloading this: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample# to check if Android Pay is supported for your device on Lineage OS.
Do you pass SafetyNet? (You can check with SafetyNet Helper Sample)
Install this app. https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
It should be green to run Pokemon Go. This is a safetynet checker.
Install this app.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Result should be Green to work to Pokemon Go. In most cases custom ROMs have issues with it.
I would run this to check if you pass the safetynet check https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en_GB
Download an app called Safety Net Helper Sample. It will tell you if you're failing snet.
You don't “download SafetyNet,” you use this app to test it: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Can someone confirm if the 7.1 beta is CTS approved?
Good tool for doing it: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
MIUI have been much of a neck pain starting from 7.1 where they have added root access to the feature list. I am guessing this is not passing the SafetyNet check especially if you are not running the Stable ROM or Developer ROM. You may use this app to check against the SafetyNet. Perhaps you can also check if your device is running on these versions and flash it when necessary. Still, I couldn't guarantee flashing these ROMs will help since it still has the root feature included..
This was my chat with them:
Google Support
Xavier K12:27 PM
Thanks for contacting Google Support. My name is Xavier K.
Xavier K12:27 PM
Hi.
Akshit12:27 PM
Hello
Akshit12:27 PM
Android Pay uses SafetyNet right?
Xavier K12:28 PM
Yes.
Akshit12:28 PM
Well
Akshit12:28 PM
I tested safetynet on my mobile device
Akshit12:28 PM
it passes the test when i'm using wifi
Akshit12:28 PM
but fails when i use mobile internet
Akshit12:29 PM
i'll just send you the screenshot
Akshit12:29 PM
I used this app to check status of SafetyNet on my device: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Akshit12:29 PM
This is the result when i'm using my mobile internet: http://imgur.com/y0GbADv
(safety net request: fail
Error Msg: safetynetapi.attestationresult success = false or empty payload)
Akshit12:29 PM
And, this is the result when i'm using my wifi at home: http://imgur.com/NWScJR1
Xavier K12:29 PM
What should I inform user?
Akshit12:30 PM
I want to be able to use it on my mobile internet, even other applications that are using safetynet are
being problematic on my mobile internet
Xavier K12:30 PM
I'm sorry about the that.
Akshit12:30 PM
I don't know why it's failing the test, maybe you could guide me and i can fix the problem
Akshit12:31 PM
did you see the screenshots?
Xavier K12:31 PM
Sure, Please allow me 2-3 minutes.
Akshit12:31 PM
Okay Thanks :)
Xavier K12:32 PM
Thank for waiting.
Xavier K12:33 PM
I have checked the screenshots and I can confirm that as this is the issue with the phone service.
Xavier K12:33 PM
I request you to please contacting carrier billing.
Akshit12:33 PM
okay
Xavier K12:34 PM
As we support Google payments services.
Akshit12:34 PM
carrier billing meaning?
Akshit12:34 PM
I was wondering if changing my APN settings might fix this somehow? or will i have to get a new carrier?
:(
Xavier K12:35 PM
As this is not working through WIFI, it is working on phone you will need to contact mobile suppor .
Xavier K12:35 PM
Support*
Akshit12:35 PM
it is working on my wifi
Akshit12:35 PM
not working on my phone
Akshit12:35 PM
using the same mobile device
Akshit12:35 PM
Moto E 2nd gen
Akshit12:36 PM
let me resphrase, it's working through my wifi on my mobile
Akshit12:36 PM
not working through my mobile internet on my mobile
Xavier K12:36 PM
I request you to contact your phone support, as there are the right person to help you.
Xavier K12:37 PM
Regarding the connection of you internet.
Xavier K12:37 PM
I apologize for any inconvenience caused.
Akshit12:37 PM
So you're sure it's an issue with my carrier's internet?
Akshit12:37 PM
no problem
Xavier K12:38 PM
Yes.
Akshit12:38 PM
Alright, thanks :)
Xavier K12:38 PM
Thank you for understanding.
Xavier K12:38 PM
You are welcome.
Xavier K12:38 PM
Is there anything else I can help you with today?
Akshit12:38 PM
Thank you for being helpful
Xavier K12:38 PM
Thanks for contacting Google Support! I'll send a follow-up email shortly with the details that we
discussed today. If there’s anything else I can help you with, please reply to the email and I’ll get back
to you.
Xavier K12:39 PM
Thank you for contacting Wallet Chat Support. Now that your chat session has ended, we would
appreciate your feedback via our survey at
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample test your phone with this.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
That app runs pretty much the same check Go does to look for root access.
Pokemon Go and many other apps use Google's SafteyNet api which allow them to tell if a phone is rooted and/or passes all of Android's certification requirements.
You can download a SafteyNet checker that will display if your phone passes the certification or not. I recommend this one because it is ad free and safe. https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
I've seen a bunch of reports of the S4 not working anymore. Try this app: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample it will tell you if SafetyNet fails which is believed to be what PoGo uses to determine root. Also check the difference between wifi and mobile data if it makes a difference between pass/fail.
Does this fail or succeed? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Does your phone pass the SafetyNet test? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Does this fail or succeed? https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
So, for anyone who is seeing similar issues, I installed this: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
I am getting Blue status: https://lh3.googleusercontent.com/cApir1zrc2MGbs2hwnHfADg_ahr_I-Ut93nzDjBWY7NnmLS5T1A_3r9mawITF7aeKQ=h900-rw
It looks like maybe my issue is due to SafetyNet failures, but it's really weird: it was working one day, and then i had to restart the app and it wouldn't sign in, and then it worked again once later that day for a few minutes, and then failed again since then! So if it is due to SafetyNet, that is really wonky. I don't know why it would fail/succeed/fail so sporadically. I'm seeing if I can get it back to Green status and then if PGO works again. If so, the old message for SafetyNet failure that I was expecting apparently only works if you get Red status, not Blue status!
You do not (although you can use verification APIs to verify the attestation serverside as well). There are a variety of free demo apps (like this one).
>The overkill comes from Niantic using this to stop cheaters, when there were lots of other less pissy, more classy and less generic solutions.
First, thank you for one of the first inklings of intelligent discussion I've ever seen about this on this subreddit.
There's a hell of a predicament here, and I can sort of see why they went with the approach they did.
To understand the predicament, you have to realize that Niantic's anti-cheat solution for Ingress was developed when they were under the umbrella of Google, and they had provably deep integration with both the SafetyNet and ReCaptcha teams for developing earlier versions of Ingress. I cannot prove this in the space of a comment, so you're going to have to just trust me when I say that "code reuse occurred."
It's likely that they wanted to reuse this for GO, but quickly realized that they couldn't for the following reasons:
- GO is a C++ and C# cross-platform codebase; Ingress' solution was necessarily Java-based, since it used Android APIs
- Pokémon GO is under far more scrutiny than Ingress currently is, and any client-side anti-cheat would be ripped to shreds
So, what to do? They have made their code obfuscation far better in this version, and likely have added a variety of fun things to "unknown6" (really, it's called clientBlob, and has served the same role in Ingress). I do think that "farm out the protection to a third party" might actually be a reasonable engineering solution here, since they have had prior integration with the teams whose solutions they are now using. Hence, seeing hints of ReCaptcha in the prior version, and now SafetyNet.
It might be overkill, and the root detection in and of itself will not stop determined cheaters, but it's really tricky to come up with a better solution given the people determined to break it.
Try running this app SafetyNet Helper and let me know if you pass/succeed.
EDIT: if it succeeds, then you can most likely continue playing PoGo
yeah, I just tested it now, and it seems running the SafetyNet Helper's test always immediately lets me use AP instead of having to wait for the background 'update'/'tick' to detect the non-root state of the device.
Or at least, every single time I've done it, it lets me add a new card to AP (whereas it otherwise still gives the 'AP is not compatible on this device' message).
yeah even for me now, I set it to enable root every day at 2:55 am (Titanium backup is scheduled for 3 am) and disables at 4 am... don't need it aside from that other than when updating AdAway hosts, which is infrequent enough (just on the weekend or something).
Nope, you still will not be able to play.
Download this app. If you get the red background and X of sadness, PokemonGo wont work for you.
:(
I even tried Google's SafetyNet API test. Used this app to check status of SafetyNet on my device:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
it seems to have passed the test, since it says "SafetyNet request: success Response validation: success CTS profile match:true" What else could possibly be causing this problem? :/
Did it pass the Safety Net test after disabling root?
Flash SuperSu as Systemless and you can still use android pay. You can check with SafetyNet Helper to see if your device passes the Google SafetyNet CTS test.
To flash SuperSu systemless get the latest SuperSu.zip (2.76) then go to TWRP terminal and type echo SYSTEMLESS=true >> /data/.supersu then flash SuperSu.
> I have a rooted Verizon Galaxy S3 with a locked bootloader
> It's even running the stock rom
Android Pay does not work on devices which have modified system partitions (i.e. classic root). Verify device compatibility with SafetyNet Check
> Is my phone just too old for Andriod pay?
- Install Android Pay on any NFC-enabled Android device (KitKat 4.4+) Android Pay
Hey could you also check if the device passes the Saftey Net Helper test? I just updated and still failing :(
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
This is most likely caused by SafetyNet being tripped. You can test if this is the case with this app. I know it happened to me when I flashed an OTA instead of downloading it officially through the settings app (as I was rooted). I suggest using a back to stock tool for Marshmallow, or one for Lollipop and then taking the OTA and that should fix your problem.
No. Doesn't pass the Google test: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en_GB
You could go back to CyanogenOS...
I'm not sure if ElementalX by itself would trigger SafetyNet. With systemless root in addition to Elementalx, I have no issues. You need to make sure you didn't disable enforcing for selinux as well (the default option is to leave it enforcing, I believe). If you're on any other ROM besides stock or Cataclysm, I dunno.
Edit, I've found when this app shows green, I'm good, otherwise I've done something wrong: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Also, use this to see if your phone will pass for android pay https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
Yeah touch anything on the system partition, it breaks CTS and thus disables AP. Changing the DPI changes build.prop which resides on system.
Run this app and if it fails you AP will not work.
You can try this util and see if your device currently passes the SafetyNet CTS test:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Yes, but it won't work at first with beta 2.64. You will have to delete the /su/xbin_bind folder with a root file explorer after installing. Then it will work. You can use the SafetyNet Helper Sample app as a test to see that Android Pay should be working.
My Android Pay was working up until a day or two ago. Found a thread on XDA that reminded me to check with the SafetyNet App I'd installed; Failing also now.
I'm running Bone Stock 6.0 with the Nov 1, 2015 Security Update and Google Play Services 8.4.89. Never rooted and Developer options disabled until after things went pear-shaped.
I'm a bit sceptical. What does it say when you run this:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Some observations of different configurations
Test device: LG Volt (LS740) running 4.4.2. Rooted with SuperSU 2.46 as the su app, and Xposed Framework 2.7experimental1 (app_process 58, XposedBridge.jar 54) installed.
There appear to be multiple checks being performed by Android Pay in its current version as of this writing (1.0.103342659 build 930001308). Different parts of these checks can be seen in the following SafetyNet check applications:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample from Scott Alexander-Bown ("SNS" below)
https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground from Cigital ("SNP" below)
The Cigital app seems to do a superset of tests compared to the one from Scott. Here's how they (and Android Pay, "AP" below) respond to the system with different configurations. These tests are only during the addition of cards, as I believe the checks in current Android Pay at payment time are the same as at card add time - I need to go back to the store and try the device in the "AP: working" config below (case 1) to be sure.
The main weirdness is that Xposed itself is somehow triggering Android Pay to fail even if SuperSU is disabled (see case 3 below), though there is one check that Cigital's app performs which does fail with both enabled, so that is one case likely needing a hackfix -- but not the only thing blocking Android Pay right now (see cases 6 and 8).
What Android Pay is doing above and beyond Cigital's checks, I don't know.
SuperSU disabled, Xposed disabled (app can be installed, but framework not installed to /system): SNH: Passes. SNS: Passes. AP: Passes.
SuperSU enabled, Xposed disabled: SNH: Passes. SNS: Passes. AP: Fails with "...could not verify...".
SuperSU disabled, Xposed enabled with no modules: SNH: Passes. SNS: Passes. AP: Fails with "...could not verify...".
SuperSU enabled, Xposed enabled with no modules: SNH: Fails on "CTS profile match". SNS: Fails with "API call verification failed". AP: Fails with "...could not verify...".
SuperSU disabled, Xposed enabled with NoDeviceCheck 1.1: SNH: Passes. SNS: Passes. AP: Fails with "...could not verify...".
SuperSU enabled, Xposed enabled with NoDeviceCheck 1.1: SNH: Passes. SNS: Fails with "API call verification failed". AP: Fails with "...could not verify...".
SuperSU disabled, Xposed enabled with NoDeviceCheck 1.1 and RootCloak 1.52 beta: SNH: Passes. SNS: Passes. AP: Fails with "...could not verify...".
SuperSU enabled, Xposed enabled with NoDeviceCheck 1.1 and RootCloak 1.52 beta: SNH: Passes. SNS: Fails with "API call verification failed". AP: Fails with "...could not verify...".
Are you using the exynos model? Can you run this app and post your results?
Oh no, Stallman was right! A company is taking existing services (SafetyNet, which is used to help protect things like Android Pay), and using them for their own applications!
Turns out that SafetyNet, like ReCaptcha, might be an obstacle to bot developers wanting to ruin the game (root detection is just one of the things it does), so this may actually be a good thing for people who want to play legitimately. There's far more nuance here than people seem to understand: it sucks if you're rooted, but there are a wealth of ways you can hide that from SafetyNet, which has way more things than that up its sleeve.
I'm all for Stallman being right, but the submitter seemed to mix up cause and effect here. The effect was that rooted users couldn't play. The cause was a side effect of SafetyNet being used, not a company trying to take away user freedoms just because they don't like people who root their phones.
Anyway, here's an app that tests SafetyNet on your device. Hopefully this should shed some light on why this happened.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
edit: seriously, questioning nuanced submissions with citations gets you downvoted here? </sub>
I think if you've already added a card, you're OK.
Can you download this app and tell me if you pass or fail please?
I think once you've added your card, you're OK. Can you download this app and tell me if you pass or fail please?