yashsingh1/xdaforums huggingface dataset:
[SuperSU] JimSmith94:
I wouldn't count on that as proof. I had Android Pay working a few weeks ago, booked a ride with it, and four days after the ride got an email from Uber saying that my payment had failed!
[SuperSU] tabp0le:
That's what I meant. Will it show green for Locked/S-OFF?
[SuperSU] Captain_Throwback:
I already answered your question.

Here's a more thorough response.

P.S. My device is LOCKED, S-OFF.
[SuperSU] paradoxiumwind:
flashing this now causes my device to get stuck on the boot logo :/ I can use the remover to uninstall it and it works again.
[SuperSU] lg-ks20:
have u installed root switch app ?

if have, make sure that root is enabled FIRST b4 stop all su daemons & then disable root. don't mess up the steps sequence in root switch, otherwise it won't work.
[SuperSU] osm0sis:
Some people just have a stronger update for SafetyNet right now, with which Root Switch doesn't even work (at least on Marshmallow). I think it's an extremely slow staged rollout or they're trying different things in different segments to make sure they don't roll out false positives widely again.
[SuperSU] vital21:
AM i really the one with such strange problem??
[SuperSU] henderjr:
Agreed. I'm not a noob and no matter what solution I try I can't get SafetyNet to pass with Root even though it seems to work for a lot of others. Sprint Samsung Note 5 Stock

edit: Well the whole suhide and root switch solution didn't work for me. But I went back to stock and was able to get SN to pass using phh's root and superuser, magisk v8, magisk hide checked in settings. NO go on xposed with magisk hide (which chainfire said would be the case). Bummer
[SuperSU] mattzeller:
My 2¢: I don't really think they are blocking phones with unlocked bootloaders. That would mean they would ban Sprint, Sprint MVNOs, as well as their own customers from using services that require SafetyNet to pass. I don't think they would want to hurt sales of the new Pixel and Pixel XL over something like this since they sell it with both a unlocked bootloader and locked one, unless they have a way to figure which provider you are with and only block you if your not supposed to have an unlocked bootloader.

Sent from my SCH-R220
[SuperSU] ashxdafan:
Anyone? Been trying prior to th above post tbh. Help.
[SuperSU] Vipriel:
Same setup and same problem here. The only difference is that I have an SM-G930F (flat S7) instead of the Edge.

Someone mentioned that the problem has to do with DM-Verity on newer devices. Older devices that don't use it are fine with the above configuration I think. I am using Superman ROM 14.5 with the Stock S7 kernel (enforcing) and it's no go. Bootloader is obviously unlocked.
[SuperSU] alanmv567:
How did you delete 06suhide?
[SuperSU] Vipriel:
Chainfire said that the "stop all daemons" thing doesn't work on MM. So it may look like it works on MM but you can't really use it and PoGo doesn't work. On Nougat though, it looks like the feature is working.

On the other hand, I know for a fact that there are other factors involved because I can't pass SafetyNet (blue screen with Payload Failed) and PoGo doesn't work when I use a stock kernel (enforcing) with no root. I have also read that some people can pass SafetyNet and play PoGo on a stock ROM but if they modify any parts of the ROM (unbloat, etc.), then it's no go.
[SuperSU] henderjr:
So far the best I've got is Magisk v8 with phh's SuperUser and the Magisk Hide ticked in Magisk Manager settings. I pass safety net and have root. But won't pass safety net with xposed. Better than I was. Though will miss my xposed modules!
[SuperSU] stone1979:
I agree. I've reverted to stock rom on my Nexus 6P, but I have not locked the bootloader. SafetyNet passed successfully and I can play POGO without any issues.
[SuperSU] Kris6699:
After three days of failing safetynet no matter what. I'm passing again. Tried 3 times pass on all of them. Yes!!!

Edit: Failing again. I give up.
[SuperSU] ashxdafan:
Hey thanks mate. DM-Verity workaround for us would be reflashing stock rom is that correct? If so once twrp is flashed I won't be able to get in unless factory reset is done correct? Pain in the ass this safetynet.. Shishh
[SuperSU] tabp0le:
I tried setprop ro.boot.verifiedbootstate green but nothing happened. How did you manually set yours?
[SuperSU] mattzeller:
No problems here either, have L720 CM13, SR71 2.78, suhide, and root switch with "stop all su daemons" selected, and unlocked bootloader (never been locked)

Sent from my SCH-R220
[SuperSU] trevorcobb:
Me too. I have a Nexus 6p on the 7.1.1 developer preview. SuperSU 2.78SR1 installs fine but when I flash suhide my device hangs on the moving colored dots screen forever.
[SuperSU] Captain_Throwback:
Using a modded binary from a friend. You won't be able to change it just using a standard setprop.
[SuperSU] Kris6699:
Can you provide it. Or at least tell us how?
[SuperSU] Captain_Throwback:
Not at this time.
[SuperSU] Kris6699:
Okay, thanks.

---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------

What binary does it use. If you point me the right direction I'll try to mod my own.
[SuperSU] kingracer:
Hi everybody, can somebody tell me if this awesome thing working or not on 7.1 dp 1? Thanks :)
[SuperSU] Vipriel:
This is my understanding, yes. I don't pretend to understand all the details but stock ROMs are signature verified based on the hash of the block device:

https://source.android.com/security/verifiedboot/

"The dm-verity feature lets you look at a block device, the underlying storage layer of the file system, and determine if it matches its expected configuration. It does this using a cryptographic hash tree. For every block (typically 4k), there is a SHA256 hash.

Because the hash values are stored in a tree of pages, only the top-level "root" hash must be trusted to verify the rest of the tree. The ability to modify any of the blocks would be equivalent to breaking the cryptographic hash. "

So, my understanding is that my custom ROM (Superman ROM for S7) doesn't work with SafetyNet and PoGo out of the gate with no root/xPosed selected through Aroma, as well as Stock G930F kernel because it's modified from the Stock image (unbloated, etc.) So the signature check fails on the hash because of the modified blocks.

If this is true, I would imagine any DM-Verity using device would fail SafetyNet on a custom ROM (i.e. CM13 as it's not OEM signed).
[SuperSU] tabp0le:
It uses /system/bin/toolbox (if setprop is what needs to be modified)
[SuperSU] mrxtc89117:
With phh superuser, can you hide root? Or is there a switch to stop root. I thought this no longer works for passing safetynet.
[SuperSU] rolandvrielink:
What does this mean?
[SuperSU] Kris6699:
Try again. Maybe internet trouble.
[SuperSU] dratsablive:
I am on stock rom on Nexus 6P no root but boot loader unlocked. Safetynet and AP fail but PoGo works.
[SuperSU] deniskr:
And agian I can't pass safetyNET... Until now everything was fine with CM13/SuperSU R1/SUhide/Root Switch combo on GS4, but now is fail again...
[SuperSU] henderjr:
I went back to stock and verified SafetyNet is green. Then flash twrp, magisk v8 zip, phh-superuser-magisk-r259.zip. Then install the phh superuser app from playstore and MagiskManager-v2.1.apk. Latest Magisk Manager has an option in settings to "Enable Magisk Hide" which hides root but not xposed. Works for me. SafetyNet is green.
[SuperSU] mrxtc89117:
Ok thank you. I might try this. I'm using root switch but I don't like the implementation. It looks dangerous renaming and remounting. phh superuser seems like a cleaner approach.
[SuperSU] stone1979:
In SafetyNet Helper, it fails (CTS fail) for me on stock rom sometimes, passes others. Not sure what is happening there. Funny thing is, when I was rooted and had suhide installed it was showing passed constantly but I couldn't play POGO. On the other hand, SafetyNet Playground always shows me as failing. So I'm not 100% sure that SafetyNet Helper is reliable, but who knows. I may try relocking my bootloader just to test it, but I'll probably just see how things go.

I suspect, the days of have a convenient root are coming to a end. Rootswitch is an option, but I'm not that enthusiastic about it. In all honesty, I suspect more developers will start to use safetynet as it cracks down on cheating/hacking, but we'll see.

---------- Post added at 04:06 PM ---------- Previous post was at 03:51 PM ----------

It works. I just flashed it and I'm currently playing POGO. I can't test AP cause I'm in Canada.
[SuperSU] NWTSCL:
I wonder if it's related to geography.
[SuperSU] carlosggb:
Hiii, which phh superuser you flash?

Thanks in advance
[SuperSU] stone1979:
This is working, but ultimately I think most of these options will fail. Topjohnwu stated on the 18th, "So the conclusion is that I will not spend that much time bypassing Safety Net in the future." From what Chainfire has previously stated, I think he feels much the same way about the future of keeping SuperSU hidden. I think eventually we'll have to learn to live without root, or live without apps that require safetynet.

---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------

I followed the directions right from the Magisk page. phh-superuser-magisk-r259.zip

http://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[SuperSU] mrxtc89117:
For me, as long as there is an option to turn off root and xposed (not hide), then I'm happy. I just want to be able to turn them back on when I need it. Root Switch I think might work for a while because it is renaming folders so that su is not in $PATH and safetynet cannot find it.

The Xposed Manager has an option to turn it off too.
[SuperSU] stone1979:
I agree, but with the way safetynet is going, that may not be that easy of an option. It's not ideal, but it's definitely a best of the worst kind of scenario.
[SuperSU] mrxtc89117:
I agree with you too. But Saferynet like all apps has it's limitations too. I doubt it scans all the folders to find su if it's not in $PATH. There are thousands of files and that will take a long time.
[SuperSU] _litz:
No root, to me, is a dealbreaker ... on my setup, it's required for two things :

1) adaway

2) the ability to kill an app (required for tasker tasks that launch music apps based on BT connectivity, and kill them when done)

At the current time, neither of those two items are possible without root.

(I could care less about cheating while playing a certain game...)
[SuperSU] dylmye:
Managed to add + verify my UK card today, with no problems. Here's my setup.

Device on wifi in the UK, with UK IP

OnePlus One on CM13-Sultan for Bacon

SuperSU v2.78-SR1-20160915 123031

suhide v0.55 + suhide GUI: hidden UIDs 10137 (Android Pay); 10084 (SafetyNet Helper)

Xposed by TopJohnWu v86.2 for SDK 23

Root Switch 1.2.4

SELinux: Enforcing

Kernel: 3.4.0-Sultan-CAF

Security Patch Level: 2016-09-06

Bootloader: Unlocked

Hope this helps, I'm happy to add extra details.
[SuperSU] gqukyo:
Same setup as mine and I get the same as well. Just gotta wait for an update if there will be one. Lol
[SuperSU] mrxtc89117:
You can try Magisk V8, phh superuser 259. I read a few posts up that this works without xposed. Magisk Manager has an option.
[SuperSU] dratsablive:
If you have suhide loaded it will loop. Flash the suhiderm zip then you should be good.
[SuperSU] soder:
May I ask why adding SafetyNet Helper to suhide? It's just an app to see if you pass SafetyNet. To see that suhide has hidden root for apps that otherwise will make you fail SafetyNet.

Or am I wrong?

/Söder
[SuperSU] michaeldcoates:
Quick question, if I have an older version of SU installed will flashing this beta (so I can get suhide) overwrite it or should I uninstall the old version first? Thank you
[SuperSU] grep_i:
There's no need for that but he can.

Safetynet helper does not even need root to operate.
[SuperSU] robertjayc:
Uninstall the old then install the new. :good:
[SuperSU] waylo:
From one of the Nexus forums, someone reported that the official Android twitter is confirming the unlocked bootloader is the/a cause for SafetyNet failure.

https://twitter.com/Android/with_replies

Samples:

https://twitter.com/Android/status/789158228563230720

https://twitter.com/Android/status/789140120691732481

https://twitter.com/Android/status/789135888542556161

Which goes hand in hand with the verifiedboot status.

(Unless there's a misinformation loop where Android employees are getting their info from reddit/XDA :p )

Odd that there are still so many random reports from folks with different hardware/software configs claiming SN still passes.
[SuperSU] Ruvahkiin:
¿With root swith xposed modules work?
[SuperSU] ScottIsMyName:
I'm not sure if this will help anybody but here's my "story":

Running Pure Nexus 7.0 (from 10/10) on a Nexus 6.

Prior to 10/19, my phone was passing safetynet using SuperSU 2.78, suhide, and the 06 suhide fix posted by Chainfire

On 10/19 Safetynet stopped working.

Tried removing the 06suhide fix, did not work

Tried installing multiple versions of RootSwitch (1.24, 1.29.1), with the SU Daemon kill box checked and unchecked, still did not work

At this point, I removed the RootSwitch app, fully unrooted via SuperSU app, removed suhide with rm-suhide 0.51 (in TWRP), and flashed the stock boot.img from my Rom. Still did not work!

As a final resort, I tried dirty flashing my ROM, and voila, SafetyNet started passing again.

Reinstalled SuperSU 2.78, suhide (without 06 suhide fix), and RootSwitcher 1.29.1 and it still works.

So it appears that for me, dirty flashing my rom seemed to wipe out whatever safetynet was detecting.
[SuperSU] michaeldcoates:
Thank you for the reply, unfortunately I had already tried to overwrite the old version and it seems to have worked ok anyway with just the SuperSU app updated and my settings in there saved from the old version. Seems ok...

However SUHide will not install properly since I updated to Android 7.1.1. Beta even with the SR1 SuperSU - is that normal?
[SuperSU] cubandanger05:
That's very odd indeed. I removed root, xposed, suhide, etc. I'm running slim ROM with custom kernel, I have a nexus so I have unlocked my bootloader and I can indeed pass safety net, play pogo, and use android pay without issues.
[SuperSU] mattzeller:
Probably because they have bootloaders that were locked. Those of us on carriers that don't have locked bootloaders to begin with, there would be nothing for them to verify against to detect a modified bootloader.

Sent from my SCH-R220
[SuperSU] robertjayc:
any link for suhiderm zip?
[SuperSU] Ch3vr0n:
That's a typo is suhide rm. You can find it in the same place you found the installation zip.
[SuperSU] gqukyo:
Didn't work for me, probably had a different phone and setup than me,

Yup, I know, that's how I got it back working. I'm not too concerned about AP but if my jailbroken iPhone can work with Apple Pay, we have to be able to get AP working without all this back and forth. Maybe something on our X-mas wishlist? Lol
[SuperSU] AnironGlass:
How to make Automate .flo script for Root switch with "stop all su daemons"?
[SuperSU] Ch3vr0n:
I suggest you ask that in the proper topic. This isn't the home of Tasker, it's the home of suhide.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] michaeldcoates:
After a lot of messing around I have Android 7.1.1 beta on my Nexus 6P with SR1 SuperSU on it. SUHide apparently will not work with this set up. Can anyone confirm that is true please?
[SuperSU] Captain_Throwback:
Alright, so I tested this out, and it seems that even with suhide installed, SuperSU is tripping SafetyNet, independent of the ro.boot.verifiedbootstate status. I tried with v0.55 and tried adding the 06suhide fix, but in both cases, SafetyNet failed.

Only the method I linked above is working for me on the HTC 10 and A9.
[SuperSU] mattzeller:
Why bother? Once it's checked its checked, opening the app and turning off root takes about 3 seconds, I don't really understand why you would want to make things more difficult

Sent from my SCH-R220
[SuperSU] mrxtc89117:
Add kill_daemon at the end of the script.
[SuperSU] carlosggb:
Hi there! are you using phh r259 or another version?
[SuperSU] midgarsormr:
Nothing works at this point. Pretty sure I'm a victim of the bootloader.
[SuperSU] Mudvayne622:
Would this be the same for tasker?
[SuperSU] Captain_Throwback:
That's the only version I'm aware of that works with Magisk.
[SuperSU] Barfelonous:
Hope we figure out a fix soon. Still detecting su
[SuperSU] grep_i:
Oops

Accidently replied myself
[SuperSU] EnriqueNote5:
ist work one note 5 ?

for she saying OS CUSTOM NO WORK
[SuperSU] negroxxx:
I sad not pass safetynet

I use

Supersu 2.78

Not install suhide

Rootwitch 1.2.9
[SuperSU] trevorcobb:
Can confirm. Same exact setup. No workie.
[SuperSU] Olympus593:
Enforcing. Stock kernel of Nexus 5 FakeNexus Pixellized ROM. Also, as many others, both SafetyNet apps always fail.

Although I'm not on a country that AP is available, I installed from APKmirror, got the e-mail from google advising of the AP being setup on the device and... AP didn't work, showed a message about not being able to identify the system.
[SuperSU] grep_i:
I do pass safetynet.

Spent the whole day figuring out how to get this working.

Got it working but I still have no clue how and why.

I tried a lot of different things and none of them seem to work but than it suddenly began to work out of nowhere, had the same setup the whole time.

Supersu v2.78-sr1 systemless

Elementalx-n5-6.24

Xposed v86.1 systemless [MENTION=2476451]romracer[/MENTION]

Suhide v0.55

06suhide

Root switcher 1.2.9.1

Safetynet passes green in 2 apps safetynet helper & safetynet playground, Pogo and snapchat are working too.

Apps dependent of root are not working for obvious reasons when root switcher is enabled but when disabling they work instantly without reboot.

Disabled root with root switcher, see screenshots

View attachment 3910175

View attachment 3910176

View attachment 3910177

View attachment 3910179

Enabled root with root switcher without rebooting, see screenshots

View attachment 3910180

View attachment 3910181

View attachment 3910182

View attachment 3910183
[SuperSU] Johnny Wong:
It is ironic that the Nexus 6p users are the ones hit with the new unlocked bootloader check from safetynet first. I only unlocked the bootloader so I can address the battery drain issue on this phone with another kernel. Hopefully the smart people will come up with a solution but for now, I'm back to stock and locked.... I'm going to say it, mind as well get an iPhone 7 Plus...lol
[SuperSU] robertjayc:
May i know how to change the SELINUX to Enforcing? Also, is Elementalx-n5-6.24 will work on Samsung Marshmallow? Thanks
[SuperSU] mattzeller:
Maybe people can chime in whether their phone comes with their bootloader locked or not, since some are still passing like me who's bootloader was never locked (S4 originally on Sprint, now Boost) but my sister's Note 5 (Verizon) does not pass anymore.

Sent from my SCH-R220
[SuperSU] MDHACK:
I can confirm that the latest Root Switcher + its patch worked for me. I tested SafetyNet Helper and it went green.

My config:

Note 4 N910T Stock everything 6.0.1

SuperSu v2.78 SR1

Root Switcher + Patch

I noticed that if I use Adaway with the systemless patch SafetyNet fails
[SuperSU] deega:
Patch? What patch?
[SuperSU] MDHACK:
If you read the Root Switch website they mention the patch
[SuperSU] gleggie:
SuperSU2.78 SR1 keeps installing into system mode. As a result, I am unable to install suhide v0.55. I keep getting "Fatal error: /su could not be mounted"

"Updater process ended with ERROR: 1 Error installing zip file"
[SuperSU] Coogibay37:
Does anybody have a fix for Pokemon Go I've been trying everything for the past couple of days and nothing works all is giving me unable to connect and I install everything that you guys were saying and nothing works on my Galaxy Note 5 with note 07 custom ROM I installed

SR1-SuperSU-v2.78

suhide-v0.55.zip

RootSwitch-1.2.9.1 I even check the little Box that is called Stop all su daemons and nothing works
[SuperSU] Triviox:
I dont understand why need Patch, how it work? Im with SuperSU v2.78 SR1 systemless in Android 6 pass OK safetynet without that Patch... Them i cant understand why or who need use that Patch. Thanks!
[SuperSU] grep_i:
In a terminal type the following to see SELinux status

getenforce

To change SELinux to enforced type:

setenforce 1

To change SELinux to permissive type:

setenforce 0

ElementalX-N5-6.24 probably won't work on Samsung devices because it's especially made for Nexus 5 devices.
[SuperSU] MDHACK:
I think it is relative to different devices. Not all systems are the same. Without the patch SN failed, but with the patch it worked. I haven't tested AP or PG to confirm it completely.
[SuperSU] Captain_Throwback:
What does "getprop ro.boot.verifiedbootstate" report?
[SuperSU] grep_i:
Do you have a source for the patch we all like to know what this patch is and where we can find it.
[SuperSU] MDHACK:
I don't have it with me right now, but you can check Root Check webpage. Someone posted the link for the page in previous posts. I used the search option.
[SuperSU] osm0sis:
It seems to confirm what I had guessed from my testing; they remove /su/(x)bin from the path, do root with xbin_bind instead and change the location of supolicy to bypass the checks. Sounds like something [MENTION=631273]Chainfire[/MENTION] might be able to wizard around more effectively for the next suhide.

This also acknowledges and apparently resolves the issue for the people who've got the more strict (more updated?) version of SafetyNet right now, like myself.

It's only on the Chinese version of the thread (where 1.2.9.1 is located). Not sure if it still requires suhide, but it's fair to assume it does since it always has previously to work 100%: https://mega.nz/#F!NwUAxKjA!lodsOX94Wd4I5HfBFR3jJg
[SuperSU] MDHACK:
Yes. The page is in Chinese, but they have some instructions in English in there. I did not install suhide. Not sure how to check SN version, but suhide stoped working two days ago even with 06suhide as other people mentioned.
[SuperSU] robertjayc:
on your android 6, is it only supersu v2.78 sr1 systemless that you put on your phone to pass safetynet?
[SuperSU] mrxtc89117:
Where is this webpage in Chinese?
[SuperSU] osm0sis:
See my updated post above.
[SuperSU] Triviox:
I have Galaxy s5 with CM13 unroot and root with supersu v 2.78 SR1 systemless + suhide 0.55 + xposed 86.2 systemless + switch root 1.2.9.1.

Pass safetynet and play pogo
[SuperSU] mrxtc89117:
Well, it points to mega.nz and not the actual asus website hosting rootswitch. I would like to see what it says if I can find it. A search leads me nowhere.
[SuperSU] lg-ks20:
The link is inside Root Switch v1.2.9.1. Scroll down to the bottom & click "Tap to visit ZenTalk thread" or u can tap here https://www.asus.com/zentalk/tw/thread-173542-1-1.html
[SuperSU] MrMeeseeks:
It's not just 6P users. My Oneplus 3 fails with an unlocked bootloader. The only thing I was using it for was ad blocking though so I just relocked it and found a browser with built in ad blocking. Too bad it doesn't help with other apps though.
[SuperSU] osm0sis:
Try tapping the "Chinese version" link.. :rolleyes:

For what it's worth, not even that newer patched method worked for me; not with suhude + 06suhide, not with only suhide, and not with suhide uninstalled.

What does still work for me is flashing unrooted N5 stock boot + franco.Kernel AK2. I backed it up in TWRP (it says boot.emmc.win but it's really a boot.img) and have just been flashing it from franco.Kernel updater any time I need to use something SafetyNet-related. Then I also have a boot.img backup of stock boot + SuperSU v2.78-SR1 rooted + franco.Kernel AK2 that I flash back to in TWRP (using the awesome flash image functionality) when I wants my roots back.

Flashify app or my Flashlt script would also work to flash the unrooted boot.img. :good:
[SuperSU] Jayman007:
looks like it doesn't support my nexus 5x

AFAIK, you can't just go toggleing the bootloader lock on the 5x without making sure you have a non modified stock bootloader in place. Maybe I'm wrong about that though.