yashsingh1/xdaforums huggingface dataset:
[SuperSU] Quinny899:
orange on my 5X which was just fine until yesterday. Stock Nougat (NBD90W), with modified boot for SuperSU and Magisk.

SafetyNet fails obviously

Also it may be worth noting before others start suggesting, no, setprop does not work to reset that value.
[SuperSU] dadonali:
that means, when i have unlock my bootloader at my galaxy s7 i cant never use any safetnet apps?
[SuperSU] Captain_Throwback:
It might be helpful to list your device too ;).

Devices that come with Marshmallow seems to have the prop, while older devices that got an upgrade to Marshmallow do not. Can you confirm which category your device falls into?
[SuperSU] edyny1:
pogo no good for me, even after adding the 06 script on my S6 Edge
[SuperSU] osm0sis:
Did you try repackimg --original? That should be roughly identical, so it would be interesting to know if it passes. If the ramdisk gets repacked at all the checksum does get changed because of (at least) timestamps.

So far, in my testing on a pre-"verified boot" device the new detection is not anything outside of the rooted ramdisk/root processes, ie. su.img and SuperSU app don't trigger a fail.
[SuperSU] edyny1:
i upgrade my S6 Edge to marshmallow and I'm still failing and pogo not working anymore
[SuperSU] CrazyCypher:
Maybe they are checking only the developer options if OEM unlocking is ticked then it fails maybe?
[SuperSU] Captain_Throwback:
I hadn't tried the --original flag, but I just did now. The resulting boot.img is still slightly different in size from the previous one and the original one (I assume because of the signature), but ro.boot.verifiedbootstate does report green status after repacking. I guess I'm not sure how that helps me, though.
[SuperSU] Dalamar666:
SAFETY STILL PASS WITH ROOT SWITCH!

you have to mark "stop all su daemons" in root switch, reboot and disable root

Works for a lot of people like me!

Root off with root switch WITH "stop all su daemons";)

Suhide 0.54

Xposed 86.6

Magisk 7

Unlocked bootloader

Nexus 5, elementalX kernel, xtrafactory (near to stock) 6.0.1 MM
[SuperSU] Triviox:
Here Galaxy S5 G500M.

I flash stock MM with odin, them flash twrp and CM13. I unrooted CM 13 and other steps i said in last post.

I not sure, but i think this device have MM since i did buy (the original stock rom was MM, but i repeat..im not sure!)
[SuperSU] Captain_Throwback:
Nope.

I don't have that checked on my HTC 10. It seems to have no effect on the verifiedbootstate prop.
[SuperSU] Boosik:
Huawei Mate 8 here. I have unlocked bootloader, SafetyNet passes, pogo works. Unlocked bootloader and verifiedbootstate is ORANGE (yea all capital). No root.
[SuperSU] soder:
I dont know if it's ok to do this, or if it's for any good, but here are my info.

I also use the 06suhide fix, and I today started with stock /system and boot.img

/Söder
[SuperSU] bw03:
Moto X Pure running TruePureXMM 2.8.2 <- MM 6.0

topjohnwu's systemless xposed 86.2

Superuser 2.78-SR1

suhide v0.55 with 06 workaround

Unlocked Bootloader

No root switcher app\apk installed

When I run the getprop ro.boot.verifiedbootstate, I get nothing back.

Passes SafetyNet Helper test and can play Pogo

edit: Not passing SafetyNet anymore. DAMN YOU GOOGLE!!!!!
[SuperSU] jcrompton:
The problem is your boot image. It needs to be unaltered or stock for it to work
[SuperSU] Devilix:
With "stop all su daemons" and reboot, did not solve safetynet pass atleast for me...

I'm with:

-suhide 0.55

-xposed 86.2

-galaxy note 3 CM13

without magisk was working.

I don't know how can i check my bootloader if it is unlocked or not...
[SuperSU] itsancho:
:D thank you so, so much!!! :good:

Nexus 6 here with Chroma Rom

SuperSU 2.78SR1

Suhude 0.55 (without 06fix)

Root Switch 1.29.1

It was working all day, till an hour ago, (SN blue), but when I did what Dalamar666 said in his post SN is green again!

Thanks again, Dalamar666!
[SuperSU] osm0sis:
Nope, still not working here. Nexus 5, stock ROM.

It doesn't, really, just good to know. ;)

I systematically unmounted/removed all SuperSU related files from the live ramdisk, including app_process32, and killed all daemonsu processes, and it still failed. Yet, stock boot.img + AK2 flash of franco.Kernel (unrooted) passes.

Whatever it is SafetyNet is looking for (for those of us who have received the update), it's very specific.
[SuperSU] Devilix:
where did you have download Root Switch 1.29.1 ???
[SuperSU] osm0sis:
Typo? 1.29.0 is the latest from the official download: https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=110357

But yeah, Root Switch still not working here with or without the 06suhide fix. I must have the latest-latest SafetyNet update?
[SuperSU] badfishie:
Worked for me!
[SuperSU] steal25:
Heres my set up and Pogo still works fine.

-Root switch (root disabled, "Stop all su Daemons" ticked and Selinux Enforcing)

-topjohnwu's systemless xposed 86.2 (posted in OP of this thread)

-Superuser 2.78-SR1

-suhide v0.55

-Unlocked Bootloader (S-OFF)

-ElementalX-HTC10-0.22 Kernel

-Output of "getprop ro.boot.verifiedbootstate" = Orange

-Device is HTC10 USunlocked on TMO

I dont use android pay and havent verified safetynet with either of the mentioned apps in this thread.

While going through previously trying to fully unroot my phone i decided to run the latest USunlocked RUU and the rom i am running is Venom 320 from a backup from before the RUU. Im about to fresh flash Venom330 and attempt the same setup. will report back.

Hope that helps someone.
[SuperSU] SamuelBegui:
I'm going to see if that had been the case. If it was i'm gonna be happy but mad at the same time for not doing something so easily. Haha.
[SuperSU] Dobsgw:
I have UB and SN got updated and was returning blue.

Installed latest root switch and checked the disable all SU Daemons and now it passes again.

Give it a go.

No 06suhide on my device
[SuperSU] duowing:
I'm running stock Us Unlocked 1.96.617.2 on my HTC 10. Cleanslate kernel, SuperSu in systemless, suhide .55, and 06suhide. My phone is S-off, locked status. The verifiedbootstate command reports red. The safety net playground and helper have been failing for the past couple days, but Pokemon has been working. I even used it around 11am. I'm in Ohio. Right now at 1pm Pokemon no longer works for me
[SuperSU] zapahacks:
Does anybody using SAMSUNG devices newer than the galaxy S5 been able to bypass with the new method (ticking su daemons in the root switch app)?

I believe is samsung related (or at least new models related, until galaxy S4 it would simply bypass again by ticking si daemons as mentioned)
[SuperSU] LakerFam0824:
This doesn't look promising... http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
[SuperSU] 135Shadowsoul:
Galaxy S4, running CM13 (no xposed, no magist, only CF-stuff including 06suhide) failing atm

[MENTION=3648153]LakerFam0824[/MENTION] and what about devices with unlocked bootloader by default? (like my Samsung S4, pre-Knox bootloader)
[SuperSU] adrman:
I'm not sure that's happening for all devices yet, but it certainly is on some. I checked my wife's Nexus 6 last night. It has an unlocked bootloader, but is completely stock and never been rooted. AP throws a "device can't be verified" error when trying to add a card.
[SuperSU] osm0sis:
Yeah that's what I tried. Still blue. I also cleaned the live ramdisk out manually of all things SuperSU - ie. did a more thorough, irreversible (until reboot), job of what Root Switch does - and then killed the su processes (including the prompt I was in) and it still failed.

I think it's looking at the $PATH since that's the one thing I can't change, and separates it from stock boot+AK2 franco.Kernel unrooted, which does pass.
[SuperSU] duowing:
For the heck of it I tried the root switch. Disable all is daemons and rebooted. No go, failing with helper/playground and no Pokemon login. I really don't care about AP. I set it up wanting to use it and have yet to go somewhere that lets me use it
[SuperSU] Dobsgw:
I'll update if it stops working tonight or tomorrow.

It's possible that I haven't had the update yet but I'm sure I have because I was getting fails on my previously working setup
[SuperSU] dadonali:
Can somebody Tell me if its worked with s7 with Stock Rom and Knox 0x1? Or check the safetynet also the Knox trigger?
[SuperSU] Triviox:
In S5 it dont check knox, i have knox 0x1 and still pass safetynet OK.
[SuperSU] dinc2010:
I have had no problems the past 5 days using SuperSU 2.78 + suhide 0.55 + suhide06 script.... unfortunately now SN fails (red) and PoGo is no longer working. I have a Nexus 6p with stock rom
[SuperSU] curiouso9:
Safety updated again?

While playing pogo about 20min, walk walk walk spin pokestop

BAAAMMM, ur device not compatible, lol they check safetynet while spin pokestop? not login only?
[SuperSU] deniskr:
Only way for SN to check bootloader status is trough kernel, so theoretically it should be possible to mask status by modifying kernel itself to fake bootloader stats... But as chainfre said it's "cat & mouse" game, and cat(google) is always in advantage... AP alone it's not so much of the problem, but if app devs start to go on SN(like PoGO did), well good bye customisable android, and welcome new iOS in shape of android...
[SuperSU] Triviox:
Now stop works suhide 0.55 + 06suhide fix. =(

SafetyNet dont pass and cant play PoGo :'(
[SuperSU] 99poison:
Still working with root switch (y)
[SuperSU] dtriguero:
suhide hides root and xposed fine on mine I don't use root switch

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] negroxxx:
I install suhide solution?
[SuperSU] chris900:
Official download more updated (chinese): https://www.asus.com/zentalk/tw/thread-173542-1-1.html
[SuperSU] frecciak:
I have a problem with suhide, if i install root and xposed, all work well, but when I install suhide the system becomes slow and impossible to use.

You have tips?

Phone : Huawei p8 (gra-l09)

Android : Stock marshmallow

Kernel: P8-Kernel-for-Root-Stock-MM.zip (from Tecalote XDA)

Root : sr1 2.78 systemless

Xposed : Xposed 86.2 topjohnwu (systemless)
[SuperSU] twcobra:
Well Pogo was working this morning then broke a few minutes ago. The update must have just hit my 6p. I then removed suhide and su. Plus folders.

Flashed my boot image and booted back up. All Pogo and Pay are working again. Bootloader is unlocked on ABC Rom.
[SuperSU] 99poison:
I use su hide 0.55 + Root switch + super su systemless. In Root switch app Check "Stop all su daemons". Safety Net is passed again. :D
[SuperSU] dtriguero:
It does try to hide xposed but only systemless I believe. If u read the lines in the 05suhide file it binds app-process to attempt to hide it maybe it don't work right with all device setups

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] negroxxx:
Xposed use?

fails safetynet
[SuperSU] 135Shadowsoul:
I got po/go back to work (and safetynet helper back to green) with following combination:

GT-I9505, CM13 + SR1 systenkess + suhide (no!! 06suhide, with it always failed, just remove it with rm-command) + NO magist/xposed + rootswitch v1.2.9.0 (ticked stop daemons), unlocked bootloader and enforcing SELinux. (If you need any more information about my configuration, just ask)

but i fear, it is only a question of time until google will update it again and make it failing :(
[SuperSU] 99poison:
I don't use xposed.
[SuperSU] bobby janow:
I think perhaps at this point we try to determine if it's the bootloader or not. I'm completely unrooted with stock everything on an N5X and I can't pass checks. So if this is the case with a majority of users then let's just forget root for now and get it to pass with an UBL. If it can't pass unlocked then there is no way suhide or root checker pass/fail will do anything but muddle the conversation. If and when we can get it to pass unrooted then we can go back to a solution for root.

http://www.androidpolice.com/2016/1...unlocked-android-phones-android-pay-affected/ There is a line at the end that says it might be a Google bug and to just wait it out. I'm not too sure about that but I'll give it a little more time before I lock and start all over.
[SuperSU] Triviox:
Here not work. Thanks anyway!

PS, do you use xposed? Edit. I saw in other post dont use it
[SuperSU] Kris5490:
For me pogo also stopped working today, xposed 86.2, suhide 0.55, root switch 1.29 and 2.78sr1... Hate it!

Safety net check: Blue
[SuperSU] mwalt2:
Sorry if this is somewhat off topic, but is there a way to bind mount build.prop similar to how you can the hosts file? I'm wondering if you could have root, a modified build.prop, and a stock boot.img this way.
[SuperSU] henderjr:
Safetynet expires every 30 minutes (I think but it could be a different amount of time). So it likely just needed to do another check and failed due to the new security checks.
[SuperSU] jcrompton:
I agree with this line of thinking --- I don't think bootloader lock vs unlock is the issue

Being ignorant ,, how do we change or alter the $PATH ??
[SuperSU] osm0sis:
It's in init.environ.rc and can't be changed in memory (well, without Chainfire-esque hackery) without a reboot. It's probably also looking for modified permissions on / now too, which is pretty unique to the 06suhide fix, and would explain why those who have it working (for now) had to remove it.

Seems like it's not just a staged rollout, but like they're testing different updates with different people.
[SuperSU] civicsr2cool:
Doesn't look promising at all. I can only see it going one of two ways, More strict where the whole play store is locked by safetynet or them giving up the fight.
[SuperSU] bobby janow:
Then why can't people pass who have never been rooted and those of us that only rooted and subsequently fully unrooted? Su has nothing to do with this.
[SuperSU] NYZack:
So the odd thing for me is that, like your wife, I had an all-stock Nexus 6, but with an unlocked bootloader (admittedly, I rooted it previously, but I flashed recovery, system, and boot back to stock). It failed Safetynet, and I couldn't add a card to Android Pay. But after flashing TWRP and Franco kernel, I am again able to add cards to Android Pay, though the Safetynet test apps still show failure. I'm still not rooted.
[SuperSU] _litz:
I can't see why not ... you can bind-mount the hosts file for use with adaway; shouldn't be any reason you can't bind-mount any other file you want as well.
[SuperSU] Crepusculi:
Another thing I don't believe has been tested is if a wipe and re-flash of userdata works.
[SuperSU] Captain_Throwback:
And how would you do that without patching boot.img? Currently root requires a patched boot.img, not stock.
[SuperSU] dinc2010:
Can't pass SN nor start PoGo by choosing disabled Root & stop all su daemons with latest Root Switch

Nexus 6p stock with SuperSU+SuHide0.55+suhide06 script
[SuperSU] deniskr:
I can confirm shadowsoul post... On GS4 works but without 06suhide.. My setup SGS4 CM13, last SuperSU, Suhide55 and root switch with "stop all su daemons"

Bootloader unlocked
[SuperSU] Nomelas:
06suhide is now not working and failing safetynet (worked an hour ago). Only option is it use root switch.
[SuperSU] bobby janow:
Been tried, still doesn't pass. It was a full wipe, system, sdcard, the whole shebang.
[SuperSU] Crepusculi:
Bad news.... Just had a coworker test for me. Locked bootloader, never rooted, stock everything N6 on MOB31H, and passes SafetyNet.
[SuperSU] MaxPower742:
I'd never actually thought to try the "stop all su daemons" checkbox. Just tried it, and pogo is actually working! But, not for long I'm sure.

systemless xposed 86.2, suhide .55 (does suhide even matter here?)
[SuperSU] bobby janow:
My wife has an S5 full stock and it passes. Never unlocked or rooted. At this point I believe the only way we will ever get it to work is either relock the bl or hope that Google made a mistake and apologizes to us. Hmm.. I wonder which it will be?
[SuperSU] steal25:
just fresh flashed Venom330 and Pogo still works. same setup the only thing i may have done differently then what i listed is i flashed osm0sis unsu.zip before flashing Superuser and suhide.
[SuperSU] Triviox:
Someone can pass safetynet or play pogo with xposed? If are some way to pass safetynet with xposed please share it xD
[SuperSU] jcrompton:
Who knows

I just didn't think it was bootloader because I don't and never have had a locked bootloader
[SuperSU] bobby janow:
I know me either. It's the first thing I do after logging in.
[SuperSU] foosee:
So this means tabs like 10.5 who never had bootloaded locked will fail safetynet checks ?
[SuperSU] pHaez:
So, I flashed everything back to stock yesterday and relocked the bootloader, and passed SafetyNet every single time I tested over the last 24 hours (probably 30 times). I decided for ****s and giggles to unlock the bootloader again. I did a test right before unlocking and passed fine. I haven't done anything else other than unlock the bootloader. Started phone back up, did a fresh setup (didn't restore apps or settings), let everything update, and then tried testing SafetyNet, and am failing again. It is definitely the unlocked bootloader, as there are no other factors at play.

I am using a Nexus 6p.
[SuperSU] twcobra:
I think Google must be fishing us with different updates and watching us whine to see which update does the most damage. XD

I'm bootloader unlocked root removed and working. At least until Google reads my post and sends me the new update XD
[SuperSU] Prack:
Yeah I'm still not convinced that bootloader has anything to do with it. I'm stock/unlocked bootloader and PoGO works fine. I tried locking and unlocking my bootloader, still works both ways. I've rebooted my phone, checked for any kind playstore updates. I can't reproduce the issue that others are having.
[SuperSU] dratsablive:
If safetynet is checking if the bootloader is unlocked does that mean it has Administrative Privileges?
[SuperSU] dinc2010:
I removed the suhide06 fix by using a su shell and typing 'rm /su/su.d/06suhide' then reboot

I disabled root on Root Switch without checking 'stop all su daemons' (cause i forgot)

SN is now blue and PoGo works again....go figure

Wondering if I should uninstall SuHide0.55 at this point?
[SuperSU] dadonali:
When i have Knox 0x1 by my Galaxy S7 is thats mean my bootloader ist unlocked, when i complete flash a full stockrom and dont root or anything?
[SuperSU] MRDOCA:
Not working anymore for me with any method. Safety net shows blue screen with root switch aswell.

S7 edge exynos

Echoe rom

Enforcing stock kernel

Unlocked bootloader

Xposed 82.6

Chainfires 56 workaround

Root switch

Was passing all green till this morning

Oh well was fun while it lasted. I'll just sit back and watch pogo die a slow lonely death.
[SuperSU] Prack:
Root switch is the opposite of what suhide does, you can remove it if you plan to continue to use root switch.
[SuperSU] Devilix:
Of course there is a way!

supersu 2.78 sr1 + xposed v86.2 + suhide v0.55 + root switch v1.2.9.1 ( with "stop all su daemons" checked).

SafetyNet pass!
[SuperSU] grep_i:
I'm not an expert in this but as I read the lines it is used to bypass app optimization and not hide the fact that Xposed is installed.

Also there is no mention of this in the change logs, I think this would be mentioned because it is a pretty big addition to a root hiding app that it hides Xposed as well.

Correct me if I'm wrong.

I can not pass safetynet but I can still use pogo and snapchat.
[SuperSU] foosee:
Exact, I don't think it is relate to BL too :

Just tried here, reinstall stock rom for T800 and safetynet is working

Reinstall TWRP : still working

install SU 2.78 SR1 (systemless) + suhide 0.55 : not working.
[SuperSU] NetWasp:
Do you have a link to root switch?
[SuperSU] Triviox:
Do you delete 06suhide fix? I have the same configuration, but with 06suhide added
[SuperSU] jcrompton:
Wow

That stinks ..... Really crazy because I've still got the locked bootloader and pass on PureNexus but no pass on some others
[SuperSU] Captain_Throwback:
It's not in the changelog because it has always been the case. The "Xposed" section is the OP states which version(s) to use for it to be hidden by suhide. Many people have been using it that way since the beginning - I'm surprised you weren't aware of it :confused:.

EDIT: Actually, I'm wrong. It IS in the changelog, lol - and it has been the case since v0.51, apparently.

(bold mine)
[SuperSU] kipperfish:
I can confirm that this works for me on my N6 (06suhide fix deleted)
[SuperSU] starcms:
Very odd, was failing yesterday, now everything is passing! Didn't make any changes. SuperSU 2.78 SR1 + suhide 0.55 + 06suhude. Both SafetyNet apps show green screen/success. This is on a N6 with unlocked bootloader and permissive kernel.

Edit: Literally 15 minutes passed, I posted this, and now both apps are failing again (red screen)....
[SuperSU] Triviox:
Yeah!! 06hide was the problem. I only removed /su/su.d/06suhide with Root Explorer :D

Now i can play PoGo + Xposed and pass Safetynet without problems!

CM13 unrooted + SuperSU 2.78 Systemless + suhide 0.55 + Xposed 86.2 Systemless + Root Switch 1.2.9.1 (with "stop all su daemos")

Thanks!!!!!
[SuperSU] iconoclastnet:
Folks seem to be forgetting a few things about how safetynet is designed to work.

First is that what safetynet does is compare what's on your phone against an expected profile ("CTS" in the official newspeak).

Many of the things it's looking at, such as particular configuration properties or hashes of the content of your system partition, are going to differ from one device to the next by their very nature. Sure many of the checks are static across devices (does an 'su' binary exist, etc.) but there isn't one universal profile that is being checked regardless of device. So It should be no great surprise if sometimes what works for one device doesn't for the next.

Second is that safetynet downloads the specific checks it's expected to make at runtime. The specific checks being made can be frobbed by Google at anytime. So just because it passed five minutes ago and you've changed nothing since then doesn't mean it's going to pass now.

If they start using bootloader locked/unlocked state as part of their determinate it might not mean that all unlocked devices are screwed (perhaps those that came unlocked out of the box would be an exception because they still match their expected profile) and it might mean that your friends phone works fine unlocked while yours doesn't.
[SuperSU] Devilix:
remove that fix, i have never installed it... Also i read some post ago, that is just that fix to make safetynet failing...
[SuperSU] alexpower:
Rootswitch 1.2.9.1 works with stop all deamon for Pogo,

but safetynet still red by cts profile.

When I toggle root off with root switch, I'm not able to turn it back by app, need to restart phone.

Suhide .54 xposed 86.2

Gesendet von meinem HTC 10 mit Tapatalk
[SuperSU] Pig Vomit:
Have a 6P. Had 2.78SR1, suhide55 with suhide06 fix.

Just now, I removed the suhide06 fix, ran the suhide-rm zip, did a complete uninstall of superuser (from the app).

Failed AP, Helper, Playground.

Reinstalled everything except userdata from factory image. Stock boot, stock recovery, stock system, etc.

Still failing everything. Only non-stock issue is my unlocked bootloader (not going to relock just to check!).

Edit: For the hell of it, I just did a reboot (last check was after first boot from reflashing everything but userdata). Still fail Helper and Playground, but now can add a card on Android Pay.
[SuperSU] corkiejp:
My RN3 Pro was passing all-day and could load game, rebooted my device and started failing.

Can confirm removal of 06suhide and using Root Switch 1.2.4, can load the game again. Bootloader unlocked.
[SuperSU] NetWasp:
I've tried this in 4 different ROMs all fresh installs, and all fail to boot, I flash the remove zip and they boot....this is surprising from chainfire!
[SuperSU] Crepusculi:
Good word!!!
[SuperSU] AsturzioAugias:
I removed 06suhide, rebooted, installed root switch.

If I disable root safetyNet helper gives a green check and android pay works. If I re-enable root, the helper gives "payload error" screen and android pay does not work. I also have xposed v86.2