yashsingh1/xdaforums huggingface dataset:
[SuperSU] grep_i:
Are you sure it needs suhide v0.55 it seems not to rhyme with it's functionality can not imagine that it is a dependency probably only need superSU.

Basically you have 2 root hiders I do not see the point in that, is it possible that this also works when not in posession of suhide v0.55, I guess so.

Can anyone confirm this works without suhide v0.55 and does not give performance problems ?

---------- Post added at 10:05 PM ---------- Previous post was at 09:56 PM ----------

Are you sure your setup is nothing more than:

Supersu v2.78-SR1 systemless

suhide v0.55

06suhide script

SElinux permissive kernel
[SuperSU] jesssiii:
Does root switch work by itself to pass safetynet? (turning it off)

Nexus 6P
[SuperSU] FabioSan:
Interesting, but I can switch manually :)

But how in the sky, niantic is bypassing everytime the hide root?

Inviato dal mio ONE E1003 utilizzando Tapatalk
[SuperSU] dtriguero:
It should but the whole idea behind suhide is for u to be able to keep root enabled and still pass safetynet root switch defeats that purpose

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] bobby janow:
Not only is 06suhide not working but root switcher is not working either. Going to unroot entirely now and if I can get some confirmations that either still work I will redo the whole shebang.
[SuperSU] garthybarthy:
Rootswitch is working fine here still, must be something wrong your end.
[SuperSU] pharmdeon:
the 06suhide is still working for me currently and has been since doing it, ie no issues yesterday, last pm, today as others have reported. This may change as the day goes on, however. But all is good now. I have not tried the root switch recently tho
[SuperSU] beatbreakee:
Can anyone help me to get SUHIDE working on galaxy tab s2? When I flash it, it just freezes on the Samsung logo while booting. Is there something else I need to do?

Process I do is:

1. Flash supersu sr1

2. Reboot normal

3. Flash suhide.55 in recovery

And this is where it gets stuck
[SuperSU] Kris6699:
Root switch nor SUHide is working for me. Was yesterday.

---------- Post added at 11:54 PM ---------- Previous post was at 11:53 PM ----------

Those of us having problems. Try uninstalling root switch. That fixed it for me.
[SuperSU] bobby janow:
So weird. Unrooting now to make sure it passes unrooted. Then reinstall.

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

Starting all over again. Thanks.

Full unroot still not working. Something is very wrong.
[SuperSU] Kris6699:
Same here. Full unroot doesn't work. Do you have the new Google Nexus launcher or build.prop tricks?

Any ideas other people? Nexus 6P No superSU or anything and fails safety net. I do have the Google assistant unlocked with build.prop tuning pure Nexus 7.0 Ninja kernel.
[SuperSU] bobby janow:
Yes I did but I removed that too. I wonder if they flagged my device if possible or something I installed while on "Pixel" trips it now. Sneaky bastards, huh?
[SuperSU] Kris6699:
I'm not sure. I'll try a multi ROM install and see if it trips it.
[SuperSU] jesssiii:
I understand that. Just wanted to know if anyone tried it without suhide. Which, as Chainfire said, is a losing battle.

Nexus 6P
[SuperSU] MrMeeseeks:
Does anyone know what's going on with SafetyNet? I'm not even rooted on my OnePlus 3. All I have done was unlocked the bootloader and adb pushed an ad blocking hosts file with twrp and I'm failing.????
[SuperSU] RandomPooka:
You've modified the system partition. Safetynet will fail
[SuperSU] robertjayc:
suhide

how to check if suhide was successfully installed? TIA
[SuperSU] snke:
If you haven't had any errors in recovery you are ok
[SuperSU] bobby janow:
We modified build.prop but restored it to the original. Even with it modified SafetyNet passed until this afternoon. So it's something else.
[SuperSU] Kris6699:
Just wiped system. Flashed PN 7. Still having fail. I think my device has been blacklisted
[SuperSU] deniskr:
I tried all, and then I just wiped everything, done clean CM13 ROM installation, unroot with superSU, and safetyNET still don't pass...
[SuperSU] Omniata:
Can anyone check if device_admin_deactivator is being called by the safetynet API on either devices failing, or those working and what the results are?
[SuperSU] dtriguero:
06 still working for me

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] TechnoGeek2134:
I don't even have suhide installed on my phone anymore, am completely stock and unrooted, and yet, for some reason, I can't seem to pass SafetyNet as of today. Android Pay refuses to work, as a result. I did, of course, have suhide installed on my phone at some point and I did a full cleanup of both root and suhide the last time it got patched, to get Android Pay back again till a fix came by. I never got around to install the latest suhide or any other root hide methods, yet I might as well have due to this sudden continued failure. I wonder, since a few posts on this thread mention this symptom as well, if my device has been blacklisted, because Google knows somehow I did have it installed at some point?
[SuperSU] robertjayc:
I have Note 3 with custom rom TouchwizMM

I unroot the tag along SU.

SCENARIO 1:

1. flash the Supersu v2.78-SR1 systemless - SUCCESS

2. flash the suhide v 0.55 - SUCCESS

3. flash the xposed v86.2 topjohnwu - SUCCESS

= BOOTLOOP

SCENARIO 2:

1. flash the Supersu v2.78-SR1 systemless - SUCCESS

2. flash the suhide v 0.55 - SUCCESS

3. did not flash xposed v.86.2 topjohnwu to prevent bootloop

4. installed root switch 1.2.4 - SUCCESS

= CANT TOGGLE TO DISABLE. AUTOMATICALLY GOING BACK TO ENABLE. BOTTOM LINE CANT PLAY POGO.

I really need your advise on what should I do next. Thank you very much in advance.
[SuperSU] kingwp1:
Worked for me too! Everything was failing for me yesterday but I'm up and going again. PoGo and Android pay are both working.
[SuperSU] dtriguero:
Mine stopped working yesterday both playground and helper failed but today they both pass I haven't changed anything it's something with safetynet messing up my set is

Supersu 2.78 sr1(systemless)

suhide0.55 + 06suhide

xposed 86.2(systemless)
[SuperSU] Ubaldo.ht:
For some strange reason I was able to pass Safety Net and play PGO with just SuperSU v2.78 and SUhide 0.55 on my galaxy S6, didn't do anything more.

I made a post in the PokemonGOdev subreddit explaning everything.
[SuperSU] CrazyCypher:
I just tried it: htc10, latest Xposed, magisk, SuperSU, suhide 0.55, soft reboot, root switch off: I can play pogo
[SuperSU] voland66:
How does one check this?
[SuperSU] Kris6699:
How?

---------- Post added at 01:56 AM ---------- Previous post was at 01:54 AM ----------

I'm failing even without system modified, pure Nexus 7 Nexus 6P no root no SUHide
[SuperSU] Omniata:
I'm not a 100%, my Android debugging is limited at best, but it's part of the API call, it allows google to blacklist processes/apps, and allows the safetynet API to force/stop them. It is possible to debug a connected Android device remotely.

I'm wondering if their dev's are now trawling through ROM's, both standard and non-standard, in addition to apps and looking for "every" inconsistency to make it impossible to use anything other than those provided at manufacture/through carriers.

I unrooted fully about 2 days ago by reflashing the unrooted ROM I had as a failsafe. I did have to reformat the data partition, ext4 to ext3, back to ext4 though to get TWRP to read/write to it.

I'm still green, but haven't yet re-rooted until a stable way is found, I am now going to take a backup through TWRP before I root/modify, so if it does go pear shaped I can at least restore to the last good working state and not have to reinstall everything over again.

I'm interested to know how they can blacklist devices though, there's nothing in any agreements that explicitly states they can store device IMEI numbers, etc.

The safetynet API isn't geared towards that either.

At the rate they're going they could be in breach of their own terms of service, as Android by nature is supposed to be open source, and they are drifting dangerously close to/are committing coercion, forcing someone to do something against their will, which became a criminal offence in the UK last year, but not well published.

I'm speaking with a few Solicitors at present to see what legal implications, if any, Google may be breaching, it may be fine in the US, but if not in the UK they have to make an exception.
[SuperSU] Rls4ever12:
Everyone in the safety net battle. It takes only 2 minutes or less to root or vice versa unroot if using chainfires su. I myself am Using dirty unicorns 10.6 waiting for 11 if course but du comes with su so I just go to su app full unroot then flash unsu zip. If I want pogo or Android pay. Then when I am done with those flash su again doesn't take long at all.
[SuperSU] voland66:
I just tried to add a credit card in AP on my wife's Xpreia Z5 Compact phone -- never rooted, locke bootloader (never was unlocked) -- and it failed. In addition, both safetynet helper and safetynet background fail. So I am guessing this is some issue with safetynet on the google side. We'll see.
[SuperSU] mattkroeder:
It appears like Google may be requiring locked bootloaders now to pass SafetyNet if reports are true
[SuperSU] bobby janow:
Where did you see that?
[SuperSU] dtriguero:
I believe my T-Mobile s4 is unlocked don't think it ever was and I'm still passing

Supersu 2.78 sr1

Suhide0.55 + 06

xposed 86.2

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] mattkroeder:
Nothing official but I've been seeing a few users say this. I probably shouldn't have used the word "reports". That made it sounds more official than it is.

People are finding that by re-locking their bootloaders, they are passing SafetyNet again

here

http://xdaforums.com/nexus-6p/help/fail-safetynet-complete-wipe-t3483207

and some users on reddit reporting the same thing

https://www.reddit.com/r/Nexus6P/comments/586bq7/android_pay_stopped_working_on_nonrooted_device/

https://www.reddit.com/r/Nexus6P/comments/584x5t/has_anyones_safetynet_failed_recently/
[SuperSU] voland66:
Except that, as I mentioned a couple of messages above yours, my wife's phone with locked bootloader and never rooted fails the safetynet test. On the other hand, some people are saying that they still pass safetynet rooted. I think we just have to wait and see what happens on google side.
[SuperSU] mattkroeder:
You're right. We'll just have to wait and see.
[SuperSU] waylo:
I think Google, in trying to fine tune their SafetyNet special sauce to catch Magisk and more recently suhide users, have pulled in a lot of false positives. The reports of unrooted, unmodified phones failing would point to this. Hopefully they're re-tune the sauce soon to avoid at least the false positives.
[SuperSU] MrMeeseeks:
I have been passing with modified hosts file up until today.

Edit: Funny thing is PoGo works, but Android Pay fails. I think they are checking for unlocked bootloaders now. That brings up another question though. Did Google kick out Niantic or something?
[SuperSU] pharmdeon:
What about phones that come with unlocked bootloaders ... pretty sure the sprint s5 was unlocked?
[SuperSU] Rhoban:
Topjohnwu, the creator of Magisk, said that no matter what he did, he couldn't make his HTC 10 pass SafetyNet.

So Google probably did some stuff to SafetyNet specific for HTC. And may other OEM will follow soon.
[SuperSU] beatbreakee:
Sorry for repost, but here's logcat from live boot where I can't get my Galaxy Tab S2, sm-t710 to get past the Samsung screen. Any help would be greatly appreciated.
[SuperSU] robertjayc:
FINALLY IT'S A SUCCESS!!!

Device: Samsung Note 3 N9005 with custom rom (TouchwizMM).

Start from scratch...

Steps:

1. unroot the tag along SU of touchwizMM.

reboot

2. flash TWRP 3.0.2-0 - https://dl.twrp.me/hlte/

reboot

3. Recovery Boot TWRP > Advance > Terminal - type this command echo "SYSTEMLESS=true" > /data/.supersu

4. flash the Supersu v2.78-SR1 systemless - https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip

reboot

5. flash the suhide v 0.55 - http://xdaforums.com/apps/supersu/suhide-t3450396

reboot

6. I did not flash xposed v.86.2 topjohnwu because I'm having bootloop on my device.

7. I installed root switch 1.2.4 apk- (not sure if this is necessary coz I cant toggle the disable button)

8. Very Important!!! at least on my device. Download and install ADB on your PC then install - https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view

9. Open the command prompt, connect your phone to your PC make sure your phone is unlocked and USB debugging is turned on

10. type adb devices type again adb shell then type su You should see a # leading the line rather than a $. Finally type this or copy this on your computer echo '#!/su/bin/sush\nmount -o rw,remount rootfs /\nchmod 0751 /\nmount -o ro,remount rootfs /'>/su/su.d/06suhide; chmod 0700 /su/su.d/06suhide

11. Reboot and enjoy

It should be noted that if you implement the above, you're going to have to rm /su/su.d/06suhide before installing the next suhide update.

SOURCE: http://xdaforums.com/apps/supersu/suhide-t3450396/post69132799#post69132799

I hope it helps because it worked for me. Good Luck
[SuperSU] bobby janow:
Those reports, I'd call them that at this point, are quite numerous and consistent. Unlocked bootloader fails, locked passes. Chilling. But in reality, that is the only way they could have done this with people like Chainfire around. They have to answer to big banks around the world as Apple has done with failures due to jail breaking. They obviously have their sights set on a global market of mobile payments and needed to shut it down once and for all. Perhaps another reason Verizon has locked the bl on the Pixel line.

I'll await the final word from CF and perhaps they will modify SN so as to let us pass again. But you know they are reading these threads and they now know they have found the way. It's up to them if they want to keep it like that. Somehow I think the banks have slightly more pull than a few old Nexus folks. Will it kill development, I can't say. That depends on what else will start using SafetyNet now that they know what it can do. AP I can live without but my banking app I use all the time. They lock that and it's curtains for me and rooting.

Now watch.. CF will have figure this out by the time I hit submit.
[SuperSU] koko115:
3.00 AM

Safety stop working ;-( with 06suhide
[SuperSU] waylo:
That's potentially a server or connection issue. Use safetynet playground instead.
[SuperSU] JaymzTA:
I am currently not rooted, but my bootloader is unlocked. PoGo and Android Pay are running fine.
[SuperSU] pharmdeon:
Checked root switch just now ... passes

Edit: reenabled root switch and rebooted ... still passing
[SuperSU] nyknight77:
People who are having problems might want to dirty flash your ROM (just wipe dalvik/cache not system&data), then go through the process again of installing superuser/suhide/06suhide. This worked for me, passes both safetynet helper and playground with greens.
[SuperSU] voland66:
It's all over the map. I unroot, dirty flash the stock rom (even system but not data), wipe dalvik/cache in twrp -- I still don't pass.
[SuperSU] Chrifister:
Still working on an S5 G900W8 with an unlocked bootloader. Buddy says SuperSu + Suhide + 06suhide + Xposed 86.2 + SELinux enforcing(stock ROM). Safety Net Playground reports success and that other app is working.

Hasn't been sporadic at all. Not sure why everyone is installing Root Switch? Suhide hides root. You shouldn't have to switch it off.
[SuperSU] NYZack:
Me too. Nexus 6, completely stock. Reflashed boot, system, recovery. Even deleted the backup boot images in /data created by SuperSU and Magisk. Still fail safetynet on both Safetynet Helper and Safetynet Playground, and can't use Android Pay.
[SuperSU] koko115:
On safetynet aygroud to failed.
[SuperSU] deniskr:
That is logical explanation... They probably restricted to locked bootloader, but not for all devices, at least for now... So that would explained why some of us can't pass safetyNET no matter what we do...
[SuperSU] MrBrady:
Could it have to do with the device being encrypted or not?

My Nexus 6 running Pure Nexus 7 (Nougat) unrooted use to pass, but now doesn't. While my wife's Nexus 6 is 100% stock, encrypted and locked bootloader and passes fine.

But throughout the day my pass results on my N6 have been all over the board. Fail, the green the blue and back to fail again.
[SuperSU] SamuelBegui:
Welp it appears that if your ROM is preloaded with root you won't pass Safetynet.

It appears not even Sultan's stable unrooted ROM for the OnePlus 3 can't bypass Safetynet. Seems I'm out of gas here folks. :/
[SuperSU] voland66:
My nexus 5x shows phone being encrypted (i think it's default on stock rom). Bootloader unlocked. Fails safety net.
[SuperSU] tavocabe:
They might be checking for locked/unlocked bootloader. I just clean flashed Sultancm13 on my OnePlus one and couldn't pass safetynet checks even though the rom comes unrooted. I proceed to flash systemless root and suhide and 06suhide making sure pokemongo and safetynet playground are listed but neither couldn't pass the checks. I couldn't pass with COS 13 fully stock unrooted either. Might try relocking the bootloader and test tomorrow.
[SuperSU] SamuelBegui:
Literally tried the same thing and I failed as well.
[SuperSU] venomrat:
I'm posting an update. Safety net passed for me using SuHide 0.55 & 06suhide script.

It seems that the twrp did not install Suhide 0.55 correctly. The suhide folder was missing a couple of files.

/su/suhide/list did not execute as list was missing.

I used Flashfire to do the install instead. I then ran the 06suhide script from terminal.

Hope this helps someone.

Afternote: I did not check my version of twrp before flashing.. I was using an older version of twrp. That's why the install failed.
[SuperSU] Atratus:
My bootloader is unlocked and I still pass. I wasn't earlier yesterday night, but now I do.
[SuperSU] Dobsgw:
Still passing using the root switch method. Not even using 06 Suhide.

Sony Xperia Z3 which requires unlocked bootloader for any kind of kernel modifications such as systemless root.

I don't think Google can penalise users with unlocked boot loaders because some people buy their devices unlocked second hand etc or use it to unlock their SIM.

Whilst Google is being very aggressive about their anti-root campaign I think they want to keep it restricted to just root users.

If they stray out of that territory they might start pissing off a larger number of users. Let's not forget that most android users enjoy the fact that they aren't limited like iOS users are.

If Google takes this the wrong direction (which I don't think they will because they're not dumb) they could end up in a similar situation to the companies fighting piracy. It actually harms the legitimate consumers more than it does the pirates. Pirates strip out all the DRM crap and have clean files. The legitimate consumers are left having to deal with crap like Denuvo which can damage SSDs etc as it causes multiple writes on installing games. Pirates don't get that but those who paid do....

So if Google takes this the wrong way they might end up harming more legitimate non root users than root users. After all we are ready to use hacks and work around to beat them and remain unaffected, but if you didn't have root and safety net went off then you're out of luck...

(Didn't expect that to be more than 1 paragraph well done if you actually read that :/ )
[SuperSU] voland66:
Something strange is happening. I just started safetynet playground and just as I pressed the "query the api" button I thought that it might have come up already green. Not sure if it was really green. The test failed. I swiped the app away, restarted it and tested -- the test passed. On the third try it failed again and now it continues to fail.

Edit: and now it randomly falls and passes; at one point i was able to get to scan card screen in ap
[SuperSU] Danny94:
RootSwitch doesn´t work anymore for me !

But Systemless supersu + suhide 0.55 + 06 fix, done like #3291 written.
[SuperSU] utbf:
Hello,

i can find so many posts about a root switch (even a screenshot) but i cant find something to install this?

Can anyone give me a link for this pls.

Thank you
[SuperSU] izeeqo:
Why i can't change my SELINUX mode to Enforcing with SELINUXMODECHANGER app? It says me "app was unable to gain root access" (attachment 1). I'm rooted i have systemless root SUPERSU V2.78 SR1 and root checker says that i'm rooted (attachment 2). Even with a terminal emulator, i can't change the SElinux with this command (setenforcing 1) it says invalid argument, when i type getenforce to know what is my mode, it says permissive (attachment 3) . What can i do to change the selinux mode to Enforcing please? I'm on stock rom Android 6.0 Marshmallow with kernel custom (xceed kernel) i have suhide v0.55 and the 06suhide script.
[SuperSU] soder:
Download from F-droid or something like that. The latest version there works for me.

---------- Post added at 11:41 AM ---------- Previous post was at 11:39 AM ----------

All this about the root switch. Why do people use that if they use suhide?

/Söder
[SuperSU] EViollet:
Because suhide isn't enough for everyone.

For me, for instance, suhide doesn't hide enough. And Pokemon Go won't start.

Root switch does the trick.
[SuperSU] izeeqo:
Thank you, it works, i changed it to enforcing, rebooted but it says Selinux mode changed to enforcing (attachment 1) and when i type getenforce in terminal, it says permissive (attachment 2). What is the problem?
[SuperSU] grep_i:
That I don't get too, I asked that question but no one seems to bother to answer that or is capable of answering that, so my guess is they are just trying something after suhide v0.55 is not working for them anymore.

They don't even bother to remove suhide v0.55 before trying something else just out of ignorance.

As soon they see that root switch works for them they tell everybody how they did it even though it's not the right way to do it but who cares it works[emoji4]
[SuperSU] izeeqo:
I think you have good knowledge, I wonder if you can solve my Selinux problem that I mentioned a little earlier, please?
[SuperSU] grep_i:
I can try, first thing you could do is try another kernel, some are SElinux permissive and some are from the SElinux enforcing kind and I don't know all kernels by head but I can see in your signature that you are using a custom kernel.

Maybe you can find out if this custom kernel can be put in SElinux enforcing mode and if not if there is another kernel available for your device that can.

Another thing you could try if not already tried is root switch, there's a lot of talking around in here about that method.

And there is another method which involves Magisk.
[SuperSU] soder:
And what are the real deal with this? What does it do that suhide doesn't?

/Söder
[SuperSU] izeeqo:
Ok thanks, for the kernel, i would see later
[SuperSU] danman7:
So, I am seeing reports of Safety Net now failing on systems only for having an unlocked bootloader. Any confirmation or ideas?
[SuperSU] EViollet:
I have no idea. If I knew I wouldn't find the need for Switch Root.

All I can say is that I tried all the steps using the suhide.6, but it still fails on launching PoGo.

Chainfire said himself that the hack may or may not work on all devices. I suppose I'm on a device that's no go.

Regards,
[SuperSU] fozzie:
Nope, it's passing fine here on a OnePlus One with unlocked bootloader, SuperSU 2.78 SR1, suhide 0.55, 06suhide patch, stock ROM, Franco kernel...
[SuperSU] soder:
OnePlus One here to. Unlocked bootloader, SuperSU 2.78 SR1, suhide 0.55, 06suhide patch, Magisk v8, Xposed 86.6 systemless version.

Passing fine on Enforcing mode SELinux. (Not Permissive)

/Söder
[SuperSU] bobby janow:
Completely stock n5x, no root at all, unlocked BL, wallpapers from pixel, new dialer from pixel,.... Fail

---------- Post added at 05:33 AM ---------- Previous post was at 05:31 AM ----------

I wouldn't announce that. Lol