yashsingh1/xdaforums huggingface dataset:
[SuperSU] SamuelBegui:
We have the same Safetynet, the difference is that, with the ROM I tested this on the ROM developer Sultan had removed the kernel flag that checks your boot status. The commit is here https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5

proc: Remove verifiedbootstate flag from /proc/cmdline

Which is why Safetynet passes on my end and anyone elses end who has this disabled. Typically, older devices has this disabled which is why I passed safetynet along with other people who have older devices. So to sum everything up from what Sultan discovered, there are no different versions of Safetynet.

Correct me if I'm wrong, but is your ROM checking the boot status of your device?

Scratch what I said before, this is really weird. It's passing on my end using that method I posted. :/ My device is the OnePlus 3. It never occurred to me there could be different versions of Safetynet, I wonder why that's the case. If your device is unable to pass Safetynet with that method then eventually I'm going to get caught up to speed with you guys then. :crying:
[SuperSU] grep_i:
For me this setup is still working for 2 days now.

How do I know which version of safetynet is rolled out to me ?

I'm also on Nexus 5 so maybe I'm not on the stricter safetynet like you, but how can I figure that out ?
[SuperSU] osm0sis:
No way to know as far as I know, though there must be some kind of internal versioning.. but it may never even get exposed to the user device since it's controlled server-side.. [MENTION=631273]Chainfire[/MENTION], any idea if we can determine this?
[SuperSU] doctorw8land:
in twrp filemanager try deleting all folders relating to supersu in /data/app and /data/data
[SuperSU] osm0sis:
Nonono, that's part of TWRP's ramdisk (which is why it's being recreated), leave it alone; it's only in TWRP and has absolutely nothing to do with your actual root status.
[SuperSU] doctorw8land:
oh oops, well it's worked for me in the past somehow, maybe i deleted something else too :confused:
[SuperSU] lucbondar:
root switcher 1.3.1.2 doesnt requires "stop all su daemons" ticked, so tasker/automate can keep root access even with root switch enabled, but now "su" folder is hidded, not renamed tu "su2"..so, how we can make a root enable task?
[SuperSU] steve51184:
So this ^
[SuperSU] mrxtc89117:
Isn't it simply just running the shell code for disable.sh and enable.sh in the /data/data/com.corner23.android.rootswith/files ?
[SuperSU] dtriguero:
Just wanted to list what's working for me currently to pass safetynet

T-Mobile s4 sgh-m919

supersu2.78 sr1(systemless)

Xposed 86.2(topjohnwu systemless)

Suhide0.55(no 06suhide)

RootSwitch1.3.1.2( don't have to tick stop-all-su-daemons with this version)

Just a thought if changing the /su name is what's working why couldn't the supersu installation script simply install/mount to a different one than /su would that possibly work cause don't most none hard coded root apps just call su in away that it don't matter the paths of su binary or would it require changing something in the su binary for that to be possible

sent from my SGH-M919 BadAss TinkerToy

---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------

I believe its /su3 now from reading its change log for 1.3.1.2

sent from my SGH-M919 BadAss TinkerToy

---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------

Yes should be just run the scripts

sent from my SGH-M919 BadAss TinkerToy

---------- Post added at 08:05 PM ---------- Previous post was at 07:55 PM ----------

K my scripting/coding skills are limited and suck at best but have been trying to mod the supersu installation/scripts to test my Theory but can't seem to get it to work. When I flash it it places the files in example /su2 and creates the new image su2.img but fails after attempt to patch supolicy and aborts so no new boot.img is created/flashed to boot/mount the su2.img to /su2 but if can get to work su2 won't work cause according to RootSwitch forum Google looking for /su2 now so would need to be /su3 or something other than /su2

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] mrxtc89117:
I don't think it has anything to do with the folder. I has to do with su in $PATH. From reading what root switch does, it removes su from path by renaming the folder or the file (su to su_)
[SuperSU] dtriguero:
that's for system root it changes to that systemless I believe it only changes /su to something different /su* which in turn removes su temporarily from path since the su.img is mounted to /su at boot from the boot.img being patched when supersu installed with no /su folder for it to show the mounted su.img there is temporarily no su in patch until /su* is renamed back to /su I could be way off and wrong

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] PokeAlert:
Humm, where do you download RooSwitch 1.3.1.2?? The latest one I see is 1.2.9.1
[SuperSU] nohctis:
did not work for me. Note 5 Stock Rom with unlocked bootloader. :crying:
[SuperSU] Dyspr0sium:
For me it's renamed to /oem by default. Looking at the disable.sh script, it seems you can specify a name to rename the /su folder to by providing an argument. E.g. "disable.sh myfolder" will rename /su to /myfolder.
[SuperSU] lucbondar:
nice!!

so this command actually works for restore root with Tasker/Automate :good:

(Root Switcher 1.3.1.2, "stop all su daemons" unticked)

/oem/bin/su -c "/data/data/com.corner23.android.rootswitch/files/enable.sh"
[SuperSU] dratsablive:
Pokemon Go works with unlocked bootloader
[SuperSU] bigcid10:
not on my htc 10

sel linux enforcing kernel

s-off,unlocked BL

278 sr1

roothode 1.31

no xposed

no suhide

doesn't pass safetynet

pokemon doesn't work

leedroid 10 v2.7.0
[SuperSU] johnchua:
Looks like he decided to quit. No more update

This is probably last version.

Check the last post for it.
[SuperSU] robertjayc:
For those of you using Note 3 and just want to play Pogo, these steps are for you!

1. flash TWRP 2.8.7.0 - https://dl.twrp.me/hlte/

2. flash Phronesis Rom N7 v3.1 Feature Rich & Smooth (clean install) - http://xdaforums.com/galaxy-note-3/development/rom-phronesis-mm-rom-v1-0-feature-rich-t3463244

3. along the installation it will ask you to to install stock rom or something just choose "stock"

4. after the installation is complete reboot your system and unroot the tag along "supersu"

5. boom! your good to go! POGO working! no need to flash xposed, suhide, supersu, magisk, rootswitch etc...

If you have different phone try to find another Phronesis Rom that matches your device.

The installation of the rom's instruction can also be found here: http://xdaforums.com/galaxy-note-3/development/rom-phronesis-mm-rom-v1-0-feature-rich-t3463244

GOODLUCK!
[SuperSU] milkotop:
Pogo work if just instal supersu systemless and rootswitch...and why if flash xposed pogo no work
[SuperSU] tallgrasshawk:
I think I do. Running Pure Nexus 7.0. UL Boot, Elemental X kernel. Have SuperSU SR1, suhide 0.55, Root Switch.

Checking 'stop all su daemons' in Root Switch, I still fail Safetynet Playground, but I'm able to still add a card to AP (haven't had a chance to make a purchase yet).

Edit: Just checked again, I'm now failing both Safetynet Playground and adding a card to AP.
[SuperSU] desztan:
May I know where is it?
[SuperSU] robertjayc:
Rootswitch 1.3.1.2

RootSwitch-1.3.1.2.zip

---------- Post added at 04:56 AM ---------- Previous post was at 04:55 AM ----------

just scroll down on on the comments you will find it

https://www.asus.com/zentalk/tw/for...zMTk4fGJjZTE1YWYyfDE0NzcxMDgzOTV8MHwxNzM1NDI=

---------- Post added at 05:04 AM ---------- Previous post was at 04:56 AM ----------

For everyone's pleasure...

ROOTSWITCH 1.3.1.2 https://www.asus.com/zentalk/tw/for...zMTk4fGJjZTE1YWYyfDE0NzcxMDgzOTV8MHwxNzM1NDI=
[SuperSU] alexpower:
True,

A Custom kernel can modify this flag,

Ask your kernel dev.

Gesendet von meinem HTC 10 mit Tapatalk
[SuperSU] bouchigo:
It seems like it's working for me. I built a kernel from the latest sources for Nougat 7.0 with the 7.1.1 ramdisk for my 6P, and I'm getting this:

I haven't tried rooting yet, but I will in a little bit.

---------- Post added at 11:09 PM ---------- Previous post was at 10:27 PM ----------

Yeah, it's working. I'm rooted with magisk and the boot.img I built from source with the fix posted earlier.

Running Nexus 6P on latest beta Nougat 7.1.1, and unlocked bootloader.

I would use SuperSU and suhide, but 7.1.1 bootloops whenever suhide is flashed.
[SuperSU] ruchern:
Magisk with any forms of SU hiding?
[SuperSU] bouchigo:
Yeah:
[SuperSU] ruchern:
I assume that you're enforcing and not permissive right?
[SuperSU] bouchigo:
Yeah, I don't need to run as permissive.
[SuperSU] 135Shadowsoul:
works great, ty VM.

but it should be possible even without rootswitch installed, you just need the enable/disable.sh. So it would be easy to cops /data/data/.../files > maybe internal sdcard and

/su/bin/su -c "/*path to your internal storage folder*/enable.sh"

and

/oem/bin/su -c "/*path to your internal storage*/disabhel.sh"

. Does any1 know a reason why this should not work?
[SuperSU] billyJ:
thanks,

It was my guess, as I wiped evertyhing and after flashing twrp it was the same again.
[SuperSU] milkotop:
work in my phone just flash supersu systemless and rootswitch,no suhide,no xposed
[SuperSU] dtriguero:
Yes it is possible I managed to get it to work with out the RootSwitch app itself I put the disable/enable scripts in /data and set script permissions to 0755 then deleted RootSwitch app and still pass. I also tried placing them on internal/external storage but didn't work scripts couldn't execute from those locations. So now I just and apps to tasker profile much like suhide gui just select ones I want tasker to work with.

S4 sgh-m919(unlocked bootloader)

supersu2.78 sr1(systemless)

xposed 86.2(systemless)

suhide0.55(no 06suhide)

tasker

enable/disable scripts(pulled from RootSwitch and put in /data)

Tasker is my new suhide gui lol sort of at least till safetynet updates to block new RootSwitch scripts

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] photolarry:
Referred here from Android Pay

I read the posts marked 3889-3893 which he says are the ones explaining it is possible to still have an unlocked bootloader with Android Pay working. But I feel dumb because I am tired and missing where instructions are. I know suhide worked before all this happened at google with safetynet a few days ago but now if this is at bootloader level, how to trick it into thinking it is locked but yet is not locked? I guess am unsure what method is working now. Please advice.
[SuperSU] Rhoban:
SafetyNet uses something called 'verify boot' to check if it is locked.

Verify boot is part of Android, but only since KitKat. Anything lower than that doesn't have it and if SafetyNet checks for it, it won't find it, so it will give the benefit of the doubt and let's it pass anyway.

In other words, if somebody were to remove that verify boot from the kernel, SafetyNet would pass even with an unlocked bootloader.

A member, Sultanxda, did exactly that with a CM13 ROM for the OnePlus One.
[SuperSU] photolarry:
So you mean kernel is modified?

In this custom ROM you are saying it is built into that custom kernel? If so, I would just need a custom kernel that has the flag turned off right? I am running a stock NBD90Z rom with a few changes I made once rooted. But it still is basically stock with a custom kernel and of course rooted. So can I do Android Pay with my setup with use of different kernel?

TY
[SuperSU] HpNoTiQ:
How did you manage that?

I wanna try on my Nexus 5x.
[SuperSU] photolarry:
For OnePlusOne

But not for my device which is a Nexus 6.
[SuperSU] dratsablive:
It's because of the root, try without root and unlocked bootloader.
[SuperSU] Rhoban:
I assume that flag can be removed from any kernel.

But this is just one of the steps it takes to make SafetyNet pass. It can still detect root and Xposed. And some say it even requires an enforcing kernel.

So there's a lot more to it.

Bypassing SafetyNet is starting to become tedious, so I've stopped trying.
[SuperSU] osm0sis:
It may have been merged into AOSP, I haven't checked, but it definitely was only enabled on Nexus devices that launched with Marshmallow or later.
[SuperSU] zezayer:
Has anyone managed to get suhide working on android 7.1?

Have been getting boot loops on both my Pixel C and 6p with this. I had it working well on 7.0.

Super SU 2.78 SR1 flashes and android boots but I get bootloops when flashing SUhide v0.55.

Anyone else having similar or found a solution?
[SuperSU] dratsablive:
I have the same issue when flashing suhide on my 6P with the developer preview.
[SuperSU] alexpower:
I tried it, unroot unlocked bootloader gives you safetynet red

Gesendet von meinem HTC 10 mit Tapatalk
[SuperSU] HamsterHam:
Suhide with root toggle.
[SuperSU] dratsablive:
Pokemon is not looking for bootloader, just root.
[SuperSU] henderjr:
Note 5 here too and no go using suhide. Just Magisk with magiskhide works but no xposed.
[SuperSU] Ch3vr0n:
Pogo isn't looking for anything. safetyNet is which is what Pogo uses. And if that was just looking for root, he would be green. As he stated he unrooted, meaning: no root, and he's not green he's red.
[SuperSU] bigcid10:
I did a clean install of leedroid with the nonroot option

and it still failed the safetynet app

it must be because of the unlocked bootloader

which is back to my previous statement

if one developer can get away with trying to force us to lock

our bootloaders and kill rooting and we can't stop it

we are screwed
[SuperSU] nohctis:
Just SuperSU and Magisk8? No need for Root Switch?

Thanks.
[SuperSU] Chrifister:
Results from a stock G900W8 on 6.0.1, comes with unlocked bootloader:

-SuperSu 2.78 SR1 systemless, Suhide 0.55, 06suhide, Xposed 86.2 systemless - Safety Net and other app fails on Oct. 19.

-Removed 06suhide - fail.

-Installed Root Switch 1.2.9.1 - fail.

-Uninstall SuperSu, Suhide, Xposed, and Root Switch - pass.

-Install SuperSu, Suhide, Root Switch 1.2.9.1 - fail.

-Uninstall Root Switch 1.2.9.1 and install 1.3.1.2 - fail.

-Copy Root Switch patch files and reflash SuperSu - pass.

-Install Xposed 86.2 - fail.

-Uninstall Xposed - pass.

So root passes but not with Xposed. Considering the phone is in a rural area, that other app is not playable without Xposed.

It sounds like Safety Net knows if your bootloader is supposed to be locked or unlocked. There are only so many carriers out there so Google would know which ones lock their bootloaders. Or are carriers removing that bootloader check in their stock ROMs?

There must be some way to run Safety Net in a clean sandbox like anti virus scanners do.
[SuperSU] Surfinette:
The strange thing is I have unlocked bootloader on both rooted phones Nexus 5 and Nexus 6P, and SafetyNet fails on both my phones, but I can still play PoGo on both phones using rootswitch...
[SuperSU] dratsablive:
I am on stock 7.1.1 and unlocked bootloader on Nexus 6P. Pokemon works fine for me.
[SuperSU] bigcid10:
right,but my htc 10 came with a locked bootloader and I unlocked it through

the htc dev site

yours was probably unlocked from the start being it was from google

correct me if I'm wrong
[SuperSU] dratsablive:
No I had to unlock it first. Had to enable developer options, then select OEM Unlocking, then unlock it. It came from Google locked.
[SuperSU] negroxxx:
install nanorom 5.8 stock with different kernel (arte97)

; without magisk and suhide.

without SuperSU

safetynet is green

SuperSU install from the recovery and suhide. safetynet is light blue

install root switch; disable root and safetynet still blue

what am I doing wrong?

and enter these commands I can explain
[SuperSU] zapahacks:
Working xposed on Samsung Galaxy S6/Edge since latest Safetynet update

Hi guys, have any user of a Galaxy S6/Galaxy S6 Edge managed to make root + xposed + pokemon go work since the last update?

I searched for "Galaxy S6/edge info" through the posts but they all seem to be related to the previous version of safetynet check (before 18th of october)

Until now I have only managed to make root + pokemon go work together on a custom rom with a custom kernel with SElinux on Permissive state, but no Xposed :( (not official nor systemless) and I really like snorlax module!.

So any help (or the simple fact that someone has actually managed to make exposed work on these specific Samsung models) would be reaallly appreciated!

Thanks!
[SuperSU] bigcid10:
Then I'm in the same boat

I just removed SuperSU 278sr1 and I'm trying phh-superuser-magisk-r259 and Magisk 8

see what happens

even when I removed root altogether ,it still failed safetynet(red)
[SuperSU] deniskr:
Those with fabric unlocked bootloader are free of SafetyNET boot.img check, they can pass SN if they hide SU, but those with custom unlocked bootloader,well they are in deep sh*t... For them, only modified kernel with disabled boot.img check flag can work... But this is really lost war... Before SN was updated on weakly base, now you are lucky if trick with SUhide and rootswitch works 24h,so what's the point in developing new method of hiding SU, when another day google will update SN,and they will make jokes with us?...
[SuperSU] gc_geforce:
I have the same phone, I did most of the patch but it cannot find the supersu. Zip for the adb. How did you patch the root switch? And do you still have suhide installed?
[SuperSU] KatariaMax:
I am using systemless xposed 86.6 should i downgrade
[SuperSU] dratsablive:
SafetyNet will always fail with an unlocked bootloader, but if you have no root, and removed suhide, then PokemonGo should work.
[SuperSU] alexpower:
That's not the point, I know safetynet is red, but Pogo runs.

Gesendet von meinem HTC 10 mit Tapatalk
[SuperSU] phuhcue:
You're a legend! Thanks. I needed that patch.

Here's what I did. Tmo Note 5 - Darkstalker v11, Skyhigh Kernel permissive. Super Su 2.78 - this is the device state I started in.

Extracted boot.img from stock DPG1 rom.

Used Tar Packager to make an Odin bootable tar and flashed the stock boot.img.

Flashed the patch you linked to. Booted up and passed SN check, pogo is go.

Go into recovery and flash magisk v8 and phh superuser. Boot up again.

Install Magisk Manager and phh app.

Toggle root and reboot.

????

Profit.

I got excited when I read your reply and forgot to unroot. Apparently I didn't need to. SuperSu app is still installed. So there's that.

My question now is xposed. Will any version of xposed work with my setup?
[SuperSU] AbiDez:
Sorry guys, really sorry... Wrong thread for me...

My mistake....
[SuperSU] lg-ks20:
SuperSu.zip = SR1-SuperSU-v2.78-SR1-20160915123031.zip
[SuperSU] dinc2010:
I installed the OTA beta for Nexus6P (NPF10C) and obviously lost root/twrp recovery. After flashing twrp & SuperSu2.78 + disabling root with latest root switch, PoGo no longer works :( wondering if it had to do with me modifying the build.prop file in order to get Google Assistant to work?
[SuperSU] ChanceGPM:
Safety net pass

I'm using the official Resurrection Remix rom with SuperSU v2.78, latest systemless xposed version 86.6 and magisk v7 with root switch (hide all deamons checked). It passes Safety net like charm and has done since almost 2 weeks back. I played pokemon today and Safety net shows green at this moment of time I'm writing this. Xposed modules works when playing pokemon aswell.
[SuperSU] bigcid10:
ok,I just flashed a clean update build of leedroid 10 v2.7.0

no root,no nothing

safetynet fails,pokemongo runs

going to try the ph root and magisk 8 method next

backup first OC
[SuperSU] lg-ks20:
these posts might be helpful :

http://xdaforums.com/showpost.php?p=69249925&postcount=988

http://xdaforums.com/showpost.php?p=69251954&postcount=992
[SuperSU] tallgrasshawk:
Nexus 5x users, The Flash updated his kernel to bypass safetynet checks....for now.

http://xdaforums.com/nexus-5x/development/kernel-flash-kernel-v1-0-october-15th-t3480827/page23
[SuperSU] Chrifister:
^^ what he said.

Since suhide causes a slowdown on the phone, it was removed and the phone is still passing Safety Net. So now it's working with just SuperSu(reflashed with Root Switch patches) and Root Switch 1.3.1.2. Xposed will cause a fail whether it's active or not.

The Root Switch patches are for SuperSu. Just rename dot.supersu to .supersu and copy both both files into /data. Then flash SuperSu again and it will install with both patches.
[SuperSU] zapahacks:
I have one question for those who have the required knowledge about how suhide works.

What exactly does suhide 0.55 do? does it hide root, does it hide xposed, or both?

I am asking this because I want to know if it is possible to do, by commands, the same that suhide 0.55 does BUT targeting my current configuration (Magisk V8 with hide + phh's Super User) in order to be compatible with xposed 86.6 (86.2 is not compatible with Magisk)

I have the feeling that suhide doesn't have any effect in trying to hide Xposed 86.6 when installed within a "Magisk" setup, I am basing my thougths on what I see when I flash the 2 different version, I see Xposed 86.2 is flashed under /su, and when flashing Xposed 86.6 I see it is flashed under /magisk. So this kind of explain to myself why xposed 86.2 doesn't even install when using Magisk V8 setup + it also makes me belive that the reason of xposed triggering safetynet when using Magisk + phh's super user is that maybe suhide 0.55 is not doing the 'thing' on the correct paths?)

So my thoughts are that maybe executing by commands the same actions suhide 0.55 does, but with the correct directories, (which I believe are different depending if you use SuperSU or if you use Magisk+phh's) will achieve hidding Xposed 86.6 mounted in /magisk correctly.

As I said, I know anything about how this actually works, but does anyone with more experience thinks about an easy possible fix for this?
[SuperSU] bigcid10:
Tried the ph root and magisk 8 method

no go, pokego still doesn't fly
[SuperSU] czecx:
Nexus 5x with unlocked bootloader, SuperSU 2.78-SR1Systemless + Suhide 0.55 + root switcher 1.3.1.2 + latest Franco Kernel R23 with aplied patch to tamper bootloader status = SafetyNet green.
[SuperSU] bouchigo:
I'm sure by now you've realized that you need a modified boot.img to get SafetyNet to pass. I don't have a 5X, so I didn't build a 5X boot.img from source with the mod.

Same as reply to photolarry...you need a modified 5X boot.img.
[SuperSU] photolarry:
Nexus 6 - Shamu

I do not have a 5X.....I have a 6. And yea I need a modified boot img but that is called kernel and possibly superuser mods that are flashable. If you are saying I need to just modify the stock boot image somehow, that makes no sense.
[SuperSU] HpNoTiQ:
I've understood but which tools do I need to unpack original boot.img apply the model and repack it?
[SuperSU] Barfelonous:
Hi guys. Using cm13 RR on my sprint note 3. I've got safety net to pass, but have somehow lost my xposed and the mods are not working. I flashed super su sr1 2.78, suhide .55 and root switch 1.3. Pogo works, safety net pass, but lost xposed
[SuperSU] bouchigo:
The boot.img is the kernel(zImage) and the ramdisk combined. The changes need to be made in source so the changes are made to the zImage. It may be possible to unpack and edit the zImage, which I'm not sure how to do if that is the case. Building from source is not that hard, and it's always best to work from source whenever possible, at least that's the way I see it.

You need to build it from AOSP source.
[SuperSU] HpNoTiQ:
I use ex kernel which is think mod directly the original boot image dont you think it is easier to mod ex kernel zip?
[SuperSU] bouchigo:
I think it uses a pre-built zImage, you'd have to ask the dev. of Elemental to add that change to his source when he builds his kernels.
[SuperSU] photolarry:
We do not have Franco nougat kernel yet...to my knowledge...And what is root switcher?

---------- Post added at 10:39 PM ---------- Previous post was at 10:38 PM ----------

Most of us are not developers with Unix build machines that can do that easily. I could learn it but never did.