yashsingh1/xdaforums huggingface dataset:
[SuperSU] Alxoom33:
Unfortunately there is only 1 custom kernel available for the Pixel C. I have been using it.

---------- Post added at 07:08 PM ---------- Previous post was at 07:06 PM ----------

Hah! That makes sense. What device are you using?

---------- Post added at 07:14 PM ---------- Previous post was at 07:08 PM ----------

Thanks. Good to know.
[SuperSU] grep_i:
Suhide v0.55 works perfectly with SuperSU v2.78-SR2 on MarshMallow.

Great work and it still passes safetynet.
[SuperSU] pkelly517:
Pixel C
[SuperSU] grep_i:
Have you already tried with the new SuperSU version ?
[SuperSU] Mudvayne622:
Did you just flash over SR1 or is there more to do?
[SuperSU] grep_i:
How to bypass safetynet on Nexus 5

Just flashed over and it worked.

But because I lost custom kernel I flashed again and followed this procedure:

I started with flashing suhide remover and SuperSU remover in that order here are the links to the files while booted to custom recovery TWRP that is not flashed on my device.

suhide remover

superSU clean up script

I'm on stock rom Nexus 5 Hammerhead Android 6.0.1 M4B30X [MENTION=222739]google[/MENTION] & LG

ElementalX-N5-6.24 [MENTION=4684315]flar2[/MENTION]

Supersu 2.78 SR2 [MENTION=631273]Chainfire[/MENTION] & [MENTION=880175]ccm[/MENTION]T

Flashfire v0.53 [MENTION=631273]Chainfire[/MENTION]

Suhide v0.55 [MENTION=631273]Chainfire[/MENTION]

TWRP 3.0.2-0 [MENTION=3335771]teamw[/MENTION]in (not flashed on device I only boot to it with adb and fastboot)

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

Root Switch 1.3.3.2 [MENTION=1813976]shakalaca[/MENTION] (Stop all su daemons enabled)

I assume you have basic knowledge and understand you have to store all downloaded files at the same folder just for ease.

I just started with flashing the rom with android tools on linux it is a package in default repo if using Windows google minimal_adb_fastboot_v1.4.zip or click here.

Download the latest factory image for my device from the Google Developers website factory images and extracted it.

Download TWRP for my device from here

Download ElementalX for my device from here

Download SuperSU v2.78-SR2 from here

Download flashfire from here or in Google Playstore

Download suhide v0.55 from here

Download Xposed from here

Download Root Switch from here or direct link here

Extracted all files.

Plugged my device with USB debugging on to the computer.

Start a command line on my computer to run adb tools commands.

adb devices

You should see something similar to this

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
094be4ca13dc031cdevice

adb reboot-bootloader
fastboot boot "path to your downloaded twrp.img for your device"

You will be booted to custom recovery, make sure you never mount /system read/write if you ever want to update through OTA.

Copy the following to your devices sdcard:

suhide remover

Supersu remover

ElementalX

Supersu

Flashfire

Suhide

Xposed systemless v86.1 SDK23

Root Switch

Flash in one go:

suhide remover v0.51

update-unsu.zip

Supersu v2.78-SR2 systemless

ElementalX Kernel

Xposed v86.1 Systemless

suhide v0.55

Reboot your device to system and install Root Switch apk found on sdcard.

Start Root Switch app and select the checkmarkbox by "Stop all su daemons" and disable root.

You should now be able to pass Safetynet and play Pogo and login to SnapChat.
[SuperSU] Mudvayne622:
Wow that's a lot. I'm not using a custom kernel. Currently RootSwitch is working for me without su daemons checked. Used PoGo and Android Pay today. I just wanted to flash the SR2 update and have it work. Not completely redo my phone.

Is there any real advantage to updating now?
[SuperSU] pkelly517:
Nope, and no plans to do it. I have root. Root is root. There is no better root.

I generally only update when it gives me a feature I don't have.
[SuperSU] grep_i:
No there isn't if your not using Android nougat 7.1.1

And in your case just flashing new version of SuperSU would be sufficient.

I wrote down the whole procedure so one could learn how to do it from scratch.

As you could read in the first line I already told that flashing over works also but because I want my custom kernel and Xposed to work systemless (custom kernel patches boot.img but because superSU restores original one I loose custom kernel by flashing superSU).

I did it this way and I wrote down the most secure way to do this on a Nexus 5.

The whole procedure doesn't take longer than 5 minutes if you have all the files downloaded already in one place like me.

If you don't have suhide installed the whole procedure takes much longer because of the rebuild of dalvik cache or dex2oat which on my device alone takes about 15 minutes, so this procedure is much faster for me.
[SuperSU] Alxoom33:
Didn't work with 2.78 SR2 on my Pixel C, either.
[SuperSU] grep_i:
OK so you didn't have problems with root in Android 7.1.1 but only with suhide.

I can't tell for sure if suhide works with the updated SuperSU version but wouldn't you try if there's a possibility it works that's why I asked you.
[SuperSU] Gamer_Josh:
This may seem stupid to ask, but how do you actually utilize SuHide? I've flashed it, but I can't seem to find the installed app to use it.
[SuperSU] Ch3vr0n:
There isn't an installed app. You didn't read op fully. It's primarily a command line tool only, however there is an unofficial GUI app listed in the op as well as being available in the play store.
[SuperSU] izeeqo:
I did a dirty clean on my LG G3, initially in Safetynet Helper I had green screen with marked success at safetynet request, responsr validation and cts profile match, I just changed my recovery, I installed TWRP, and Safetynet is red screen, safetynet passes but in CTS PROFILE MATCH is marked fail and the two others are success, is that means that my boot.img file was modified by installing the custom recovery? thanks
[SuperSU] yochananmarqos:
What, pray tell is a "dirty clean?" You either clean flashed (wiping data, system, cache & ART/Dalvik) or you dirty flashed skipping wiping data.
[SuperSU] RandomPooka:
^^ Possibly they just breathed on the data and rubbed it a bit with the tail of their shirt?
[SuperSU] izeeqo:
Yes i did a clean flash (wiping data, system, cache & ART/Dalvik). Reflashed stock ROM and the problem wasn't about installing recovery custom, it was when i installed kingroot, now i have uninstalled it and i'm not rooted so, cts profile match is true, but if i root my device, cts profile match became false... No way to keep it green with root ? (SuperSU)
[SuperSU] 135Shadowsoul:
well, you can try install supersu systemless (just look arround in this thread for instructions) and use suhide. if it does not work, you may try latest rootswitch (look arround in this thread again).if nothing works... some people reportet some magisk-actions work but i dont know anything about this, i am not using magist. On my Samsung S4 (GT-I9505) with CM13, SN passes with SR1 systemless + suhide + rootswitch
[SuperSU] pkelly517:
I have no need for suhide anymore. I'm done with the cat and mouse game. I don't play PoGo, and root is more important than Android Pay. I've stopped installing it on all my devices.

If it allowed watching movies I've paid for in Google Play Movies, I might try again.
[SuperSU] Jhyrachy:
Hi, i flashed suhide 0.55 on my nexus 5x with android 7.1.1 and it's stuck at boot, any suggestion?

I had the latest supersu and twrp
[SuperSU] 135Shadowsoul:
flash the -rm.zip, it seems like suhide does not work on android 7.1.1 at the moment

(please correct me if i am wrong)
[SuperSU] Jhyrachy:
Well, it worked, thanks!
[SuperSU] 135Shadowsoul:
yw :)

but ofc you can not use suhide^^

for android pay/pokemon you may try rootswitch as long as suhide does not work (just look arround, links for rootswitch are posted a lot of times now)
[SuperSU] shoey63:
There is no support for Nougat, and no more updates due to the new Pixel file system. This thread is EOL.
[SuperSU] Jhyrachy:
yeah, obv suhide will not work, but at least i'm glad i still have my phone working without a reflash

I'll take a look at rootswitch and a kernel patch to hide unlocked bootloader state.

Thanks a lot!
[SuperSU] grep_i:
Latest SuperSU and TWRP is to you which version ?
[SuperSU] Jhyrachy:
it was twrp 3.0.2-2 and supersu v2.78 SR1

but [MENTION=5300075]135Shadowsoul[/MENTION] already told me how to solve it
[SuperSU] grep_i:
You know this software is completely unsupported and experimental not only on nougat but also on marshmallow and any other version of Android don't you ?
[SuperSU] jackmcbarn:
Um, no:

(emphasis mine) It's temporarily on hold, not EOL.
[SuperSU] chuman72486:
Is this not being updated anymore? I've been hoping to find a version of suhide that works without needing to add even more software (rootswitch) just to play a game. Plus I want to be able to keep root and xposed on and working whole playing which only suhide could allow.
[SuperSU] Alxoom33:
I agree.

I'll believe it when we hear from [MENTION=631273]Chainfire[/MENTION]. He has been busy on rooting the Pixels. Suhide v. 56+ or some other solution, I expect will come soon enough. Patience young Padawan. The force is with us!
[SuperSU] Zhairus:
I can not install sunhide 0.55 over supersu 2.78 SR2. TWRP tells me you need SuperSU 2.78 SR1
[SuperSU] chuman72486:
I just want to get my phone to behave. I uninstalled Magisk, rerooted with the latest SuperSU, flashed Systemless Xposed, flashed suhide 0.55,and installed Root Switch. I tried toggling root and it still fails Safetynet checks.
[SuperSU] 135Shadowsoul:
Warning: Offtopic

at least for players in germany there could be some hope for this. german privacy laws forbid some things niantic does, like giving data away or (and that is the interesting point) just stop the usage by modifying the licence agreement (including banning people just because using of root). iirc, they have time up to end of 2016 to change their behaviour in those cases.

For every1 who is able to understand (read) german, here a quotation:

[...] Konkret heißt das, dass Niantic den Nutzervertrag nicht mehr einseitig aufkündigen kann. Das passierte unter anderem, als Handys mit Root oder Jailbreak kein Pokémon Go mehr spielen konnten. Mitunter muss der Entwickler diese Regelung in Deutschland wieder zurückziehen. [...] Source

Own and quick&dirty translation into english: niantic is not allowed to terminate licence agreement one-sided. This happens amongst others, as mobile phones with root or jailbeak could not play pokemon go anymore. The developer has to draw back this regulation for germany.

If any1 has a better english translation, feel free to tell me, i will change it :)
[SuperSU] Alxoom33:
Suhide v. 0.55 not working with Android 7.1.1. What device are you using and what version of Android? Need information and preferably logs if you want useful information back.
[SuperSU] 135Shadowsoul:
you can try to remove (not only hide/disable, remove) xposed, sometimes it helps... but if you want to use xposed, then bad luck, sorry :(
[SuperSU] Pig Vomit:
Just in case people missed this, I thought I would copy and paste Chainfire's comments regarding further suhide development directly from his Google+ page:

suhide

Some of you have expressed disappointment on me not having updated suhide to work around the latest couple of SafetyNet updates, even though I know how. I was waiting to see how the changes introduced with the Pixel were going to play out. Unfortunately I have to report that there are some new complications with doing something like suhide on a partition layout like the Pixel's - the /system_root mount and /system symlink are tough to hide. I doubt I'll be putting more time into suhide until I can think up a workaround for these problems.

Whether we ever see another suhide release or not, thank you to Chainfire for all the work he put in to the project.
[SuperSU] grep_i:
Are you on Nougat 7.1.1 or ?
[SuperSU] ashxdafan:
I second that. [MENTION=631273]Chainfire[/MENTION] youve been our messiah. Thank you!
[SuperSU] Zhairus:
I have in Phronesis port Note 7 v.3.1 and my phone is Note 3.
[SuperSU] grep_i:
Alright and your android version is ?

You know what this is a custom custom rom, you probably are better out with asking these questions in the rom specific thread.
[SuperSU] just4u32:
Hey all,

Thanks a lot for this!

I'm dying to try it on my android box (Beelink GT1), but I'm scared as I do not know the origin of the root.

The device got rooted in one of the official firmware updates.

Would you say it's safe? Is there any way I can verify?

Please consider there is no custom recovery. This is a new box.

Thanks in advance
[SuperSU] mac.os.x:
Nothing is "safe" from exploitation.

---------- Post added 31-10-2016 at 12:01 AM ---------- Previous post was 30-10-2016 at 11:58 PM ----------

I use the SR 2 Beta SUPERSU, it's all I use. Never had issues.
[SuperSU] RandomPooka:
I wouldn't bet on it being rooted from the manufacturer's update with SuperSU, and especially not with a version compatible with suhide. Wouldn't recommend trying to use it unless you've got some way to unbrick or recover from boot loops if they happen.

If you can do that, forge onward and let people know it works (or doesn't). If there's no way back to stock .. NOPE. A whole big barrel of nope.
[SuperSU] just4u32:
That's what I was thinking. Is there a way to check if and which supersu version is installed?
[SuperSU] ipdev:
Not sure about tv devices but google is full of root checker apps.

(root validator is the one I am currently using.)
[SuperSU] osm0sis:
Tried it without Xposed and using franco.Kernel, but still doesn't work on my N5. I doubt Xposed or ElementalX are making a difference here (especially since I still pass SafetyNet with unrooted stock + franco.Kernel).

So the "more strict" SafetyNet is still very much a thing for some portion of users.
[SuperSU] drewski_1:
Same on 6p 7.1.1 beta
[SuperSU] Ch3vr0n:
Use SR2
[SuperSU] grep_i:
Did this more than 20 times now and it always seems to work, also did it the wrong way on purpose a couple of times and it's not working than.

In which country do you live, do you think it's region based the more strict check of safetynet.

I really don't believe it that there's different versions of safetynet check.

The check is online and in my opinion it does not make sense to have different checks for what would be the criteria do you think I'm not buying that.

The check is the same for everyone that's what I believe.

There must be something else different on your phone is it possible you have some sort of adblocker that blocks on hosts file basis ?
[SuperSU] RandomPooka:
Not really sure, to be honest.
[SuperSU] ktimque:
-delete-
[SuperSU] osm0sis:
I flashed it "all at once" like you recommend, so I sincerely doubt method has anything to do with it.

Plenty of things are geofenced by Google, but I agree it's not a logical way to do it. It's probably just random like they do a staged rollout. Basically, just 1/10th or whatever fraction they want gets the version they want to test to make sure it doesn't give false fails.
[SuperSU] grep_i:
OK I guess you're right than.

In my case it only works if I flash all in one go if not I don't pass safetynet.

Too sad it doesn work for you, is it possible you flashed custom recovery on your device I didn't.

---------- Post added at 02:14 AM ---------- Previous post was at 02:12 AM ----------

in terminal on device or adb shell from computer type the following

su --version

This will show you which su version you have, in my case it showed:

2000@hammerhead:/ $ su --version
2.78:SUPERSU
[SuperSU] Alxoom33:
Same with SR2
[SuperSU] newbreedsoftware:
I have a Sprint Note 5 running Moar 6.0 and Wanams Xposed module, is that version supported or does it have to be the systemless xposed?
[SuperSU] grep_i:
Please read first post OP carefully, there you'll find the answer to your question.
[SuperSU] just4u32:
2.77:SUPERSU

What are the chances I'll be able to upgrade it simply by flashing a newer version?
[SuperSU] grep_i:
If your device is supported chances are very high you'll succeed by using that procedure.
[SuperSU] negroxxx:
s6 some user could happen safetynet with suhide and Xposed ???
[SuperSU] droid_1989:
To flash this, we have to wipe data before hand right?

Think that's the reason why I'm getting stuck on boot screen. Using 7.1.1 developer preview on Nexus 6P
[SuperSU] HpNoTiQ:
Hi, I've got the same problem than you on my Nexus 5x in France.

I've compiled ExKernel 1.20 with sultanXDA patch (http://xdaforums.com/showpost.php?p=69391475&postcount=3230) and it was tough to get it work.

I've tried lots of time but here is how I got it to work :

Format everything.

Flash stock rom. + wipe data in recovery (my phone always show 16gb instead of 32gb).

Flash TWRP.

Flash FED-PATCHER (to disable encryption).

Launch et configure (google backup)

Once on desktop, reboot, flash SuperSU, Xposed RomRacer, Kernel with SultanXDA patch, titanium backups and start.

Then rebooted and installed Suhide 0.55 (no suhide 06fix!) rebooted and installed rootswitch 1.3.3.2.
[SuperSU] cahollow:
Issues with suhide and 7.1.1 dev preview

Good morning. I have been trying all weekend to get suhide flashed properly on my Nexus 6p. I have wiped completely and started fresh with the dev preview download of 7.1.1 from Google. I then flash TWRP then install the lastest supersu (2.78 R2) and reboot. The phone boots with root access just fine. It is after the next step, in which i flash suhide that I run into issues.

I have tried flashing both with TWRP and Flashfire but the result is the same both times. I get to the multicolored Google screen and can't get past it. I have waited as long as 30-45 minutes to make sure the boot wasn't just taking a long time but it just stayed on that page.

I'm aware that it could very well be changes made in 7.1.1 but I wanted to see if anyone else had had similar issues.
[SuperSU] izeeqo:
Safetynet detects suhide ? Can't bypass safetynet with suhide installed... or must i have the 06suhide fix ?

---------- Post added at 14:27 ---------- Previous post was at 14:20 ----------

I've installed SUPERSU 2.78 SR2 in systemless mode, i disabled root in root switch, safetynet passes, but when i installed suhide with root disabled in root switch, safetynet don't pass, it fails... Why ? I don't have Nexus 5, i have LG G3
[SuperSU] just4u32:
And.. it works!

However, it appears like the app I'm trying to fool is still detecting root.
[SuperSU] osm0sis:
Recovery also can't be the deciding factor, since as I said it passes with unrooted franco.Kernel, flash SuperSU and it fails, no other changes.

While I don't doubt in the least the process works for you, flashing unSU over untouched stock ROM is actually a pretty baffling requirement; all that should do is mount /system rw, which also potentially allows TWRP to modify /system, seemingly contrary to the cause.

Has /system/recovery-from-boot.p been renamed to .bak on your setup?
[SuperSU] grep_i:
As far as my memory can recollect it was about "Nexus 5"

---------- Post added at 03:12 PM ---------- Previous post was at 03:07 PM ----------

I have no clue why it does not work on your device but may I ask why you even want suhide if your already passing safetynet without it ?
[SuperSU] Artim_96:
It's not really working on 7.1.1. Chainfire knows that and he's working to solve that problem

https://plus.google.com/+Chainfire/posts/fvEPo42GKXS
[SuperSU] izeeqo:
Because i want to install xposed v86.1 by romracer and bypass safetynet
[SuperSU] cahollow:
Thanks Artim! I figured this was likely the case, just wanted to be sure before I wasted any more time on getting this to work.
[SuperSU] grep_i:
I know that in my case I don't really need to flash update-unsu.zip I added this step for people complaining that they can't flash suhide due to finding the SU binaries in /system I wanted to include those users also in my procedure.

And flashing it like this is easier for people than finding the binaries themselves that's why it ended up in my guide.

Normally I would remove it manually by remounting /system rw and remove the binaries myself this does not happen often.

I never install in systemmode the only times I had systemmode installed was when testing install scripts that didn't work correctly and gave me systemmode install instead of systemless even when I had chosen for systemless.

My /system/recovery-from-boot.p had not been renamed and I'm not sure if you can call my device untouched stock rom as I did had systemmode root on it although it wasn't intentionally even than my procedure worked.

I know that it is possible to modify some portions of /system without breaking OTA support.

As I'm always flashing factory images I don't care for OTA support but this time I will try and see if I can OTA update my device without problems.

I'm anxious to know if it works after all thanks for pointing my in that direction, this is gonna be my new project to OTA update with this setup.
[SuperSU] SpasilliumNexus:
After a week of thinking Pay no longer passes with the Tasker + Root Switch and SuperSU + suhide method, I've decided to add a notification to let me know when root gets enabled and disabled. Came to find out that I had to block Play Services too as it's called upon adding cards and paying.

...SMH.

Stock 6.0 on 2015 Moto X Pure

frankenclark kernel 0.14 (in enforcing)

SuperSU 2.78-SR2

suhide 0.55

Root Switch 1.3.3.2

Android Pay 1.8.135831409

Google Play Services 9.8.77 (440-135396225)
[SuperSU] callumbr1:
I have flashed supersu 2.78 sr1 systemless, when i flash suhide through twrp i get an error about su systemless not installed? G925f with twrp xposed v86.1 wanam. Any help please? Thanks
[SuperSU] Dalamar666:
Safety updated again

Root switch does not work

Cts error (red)
[SuperSU] 135Shadowsoul:
did you disable built-in root (if existing) and deleted /system/bin/su- and /system/xbin/su-files? Did you do the "echo" command? maybe wrong xposed version?
[SuperSU] Triviox:
Here Galaxy S5 G900M, CM13 unroot, suhide 0.55, SuperSU v 2.78 SR1 systemless, Xposed 86.2 systemless, Root Switch 1.3.3.2. Still working; green in safetynet helper and can play PoGo.
[SuperSU] fozzie:
Still works fine here.
[SuperSU] 135Shadowsoul:
on my SGS4 it is still green

did you reboot directly before? if yes, this may cause a problem. Do you use SafetyNet helper?

€dit: reboots directly before running SN helper app cause red on my device everytime. i have to wait a bit (~ 2-3 min after rebooting), but po/go works. looks like a problem on SN helper
[SuperSU] Dalamar666:
Thanks all

I've magisk 7 and latest systemless xposed (86.6) with suhide 0.54. Yes, i use the saf helper

I think that could be related to magisk, because I read about people with phh's that have cts error (red)

Also, could you provide your full settings?

I'll go to try deleting magisk and xposed....
[SuperSU] ScottIsMyName:
Confirmed. Was working fine before with 2.78 + suhide + magisk (for xsetprop) + root switch for the last week.

Now getting CTS profile error.
[SuperSU] snke:
Anyone can post latest root switch?
[SuperSU] steve51184:
Why not use suhide 0.55?
[SuperSU] Ja_som:
http://www.asus.com/zentalk/tw/thread-173542-1-1.html
[SuperSU] steve51184:
https://www.asus.com/zentalk/tw/for...MjY4OTNifDE0Nzc5NDU4MTV8MHwxNzM1NDI=&mobile=2
[SuperSU] snke:
Have you tried if it works with SuperSU v78 sr1 and suhide 55?
[SuperSU] steve51184:
Yes works perfectly
[SuperSU] snke:
Which device?
[SuperSU] steve51184:
OnePlus 3 but should work on most setups fine
[SuperSU] DeTeKa:
A few hours ago i get red screen in safetynet helper. I proceed to uninstall supersu, suhide, magisk 7 and xposed 86.5 and reinstall only supersu 2.78 sr1+ suhide 0.55, green screen again, the problen seems to be asociated with magisk and xposed, sorry for my poor english
[SuperSU] Triviox:
Did you try add Xposed 86.2 systemless and Root Switch 1.3.3.2? If have luck, you will pass Safetynet with Xposed :) (like me hehe)
[SuperSU] DeTeKa:
I'm working in it :) I will report when finished