yashsingh1/xdaforums huggingface dataset:
[SuperSU] Vipriel:
No go here. I was walking the green belt playing PoGo and catching stuff when I suddenly got kicked out of the game and was presented with the "your device is incompatible" screen. I have removed Xposed 86.2 as well as root switch but this didn't help so it looks like Magisk is getting detected.

I have had occasional issues in the past few days but I have always been able to either just reboot or clear Dalvik and Cache and reboot and get to pass SafetyNet and play PoGo. This time, none of that worked and I am getting red on SafetyNet helper which I never got before (always blue when it didn't work) so this is definitely a new SafetyNet update being rolled out.
[SuperSU] grep_i:
Still working here, so I'm a lucky guy.
[SuperSU] Triviox:
Did you try a clear system reinstall? Maybe have "trash" after flash and flash stuff and stuff.
[SuperSU] Dalamar666:
Hi all

Safety pass again

Migrated from: suhide 0.54 + supersu sr1 + magisk + latest xposed 86.6 ( CTS Error)

To: supersu sr2 + suhide 0.55 + xposed 86.2.

Latest root switch needed

No magisk.

In my opinion, magisk is the problem this time

My process (after nandroid)

* Uninstall xposed

* Uninstall magisk.

Boot img restored

Reboot. Safety pass. No root.

* Flash supersu sr2 in systemless

* Flash suhide 0.55

Reboot. Disable root with root switch. Safety pass

* Install xposed 86.2

All ok. Safety pass with root disabled
[SuperSU] PiCkLeS:
My setup precisely since a week. Stopped working today..
[SuperSU] Tikerz:
This is crap.
[SuperSU] DeTeKa:
Which version of SuperSU you are installing? when I flash version SR2-SuperSU-v2.78-SR2-20161029143931 in recovery it seems to be well installed, but when I start the phone the application SuperSU not appear, and root switch does not detect the root
[SuperSU] Dalamar666:
Try installing supersu app manually and check inside your supersu versión ... Ive sr2
[SuperSU] ashxdafan:
Still no luck with s7 edge thus far.

Tried so many combos alongside sr1 and 2 with suhide greeted with cyan screen time and time again.

Anyone got lucky?
[SuperSU] zapahacks:
Which phone model do you have? Samsung? or which one?

Thanks
[SuperSU] alelopinf:
How can I uninstall suhide? I can't delete su.

Enviado desde mi eMAX mini mediante Tapatalk
[SuperSU] Dalamar666:
Nexus 5

Xtrafactory MM 6.0.1

Elementalx kernel
[SuperSU] zapahacks:
Has anyone figured out why SuperSu + suhide method doesn't work anymore on Samsung Galaxy devices like S6/S7/Edge variants and + variants? It stoped working since previous (not todays) SN update and until now I haven't seen anybody with an explanation :/ or workaround different from Magisk (which is now detected with todays SN update)

Any help related to samsung galaxy users would be appreciated!
[SuperSU] dratsablive:
So I tried the newest SR2 SU and SuHide 55 but still causing bootloop with Android 7.1.1 on my Nexus 6P.
[SuperSU] justmiike:
Thanks, I tried the above, but no dice on Galaxy Note 3. So it looks like this only works for certain devices.
[SuperSU] vicmtzbus@gmail.com:
Help please

I install superSU v 2.78 but i can´t install suhide, help

Updater process ended with error: 1

Error installing zip fiile ´/sdcard/suhide-v0.55 zip´

please i need complet the process :(

Make the process in HTC one M7 Sprint released gsm
[SuperSU] izeeqo:
You need TWRP (3.0.2 or newer, with access to /data )
[SuperSU] vicmtzbus@gmail.com:
mmm

i have twrp v3.0.0-2 and the room vanir 6.0101216 :(
[SuperSU] desztan:
U have supersu 2.78 or 2.78sr1?
[SuperSU] _litz:
This worked for me, too (although I didn't have to nandroid; a simple magisk uninstall worked).

However, after disabling root with Root Switch, it will not re-enable when you hit the switch again.

Rebooting the device every time you are done with AP (or PoGo) is really not desirable ... anyone know how to turn root back on without rebooting?
[SuperSU] vicmtzbus@gmail.com:
i install the two versions.

First i install SR1 but not work, after install SR2 and not work .

Thanks for helping
[SuperSU] desztan:
I assume you have type "echo "SYSTEMLESS=true" > /data/.supersu" in the TWRP terminal before flashing superSU?
[SuperSU] vicmtzbus@gmail.com:
I did so

Echo SYSTEMLESS = true >> /data/.supersu
[SuperSU] higedamc:
Thank you for sharing this detailed info!

By the way, why are you using romracer version instead of topjohnwu? I would like to know the pros and cons between them and what if I want to uninstall romracer ver Xposed after a try? Cuz I couldnt find the exact systemless uninstaller on romracer thread though.

Or can I uninstall the romracer systmeless Xposed via topjohnwu ver, just use romracer uninstaller?

Thnx
[SuperSU] leolawliet:
The weird thing for me is SafetyNet bypasses successfully for everything else but the only thing that doesn't comply is Android Pay.
[SuperSU] kelsony:
suhide is giving boot loop for me, any idea?
[SuperSU] RandomPooka:
It's a known issue with your device.
[SuperSU] kelsony:
I've used this process before, only in another rom
[SuperSU] RandomPooka:
Then it's obviously a rom issue. Try asking in the thread for your rom, or at least provide information such as device name, what rom you're using, and what rom it previously worked with. Nobody here is psychic, and if that info is in your sig, not all apps show your sig.
[SuperSU] kelsony:
First used wanted rom v6.3 where suhide worked and now I'm trying to use xtrestolite v2.6 where suhide gives bootloop, my phone is the Galaxy s5 900H, Exynos processor
[SuperSU] grep_i:
I use romracer because I want to stay close to the original of rovo89.

I do also still use Xposed installer 3.0 alpha 4.

My device is already fully supported by this version so I don't need another version to broaden compatibility.

What's mostly with topjohnwu versions is that there is compatibility for more devices than the original is what I've heard.

On the downloads page of romracer there is a folder for uninstallers.

I have no clue if they work or are needed because I myself never used an Xposed uninstaller.

I never removed Xposed framework completely but

If I want to remove Xposed I only reflash SuperSU that's all to it.
[SuperSU] Paxy:
Confirming that suhide makes boot loop with SR2 on 7.1.1 too.

Nexus 6P
[SuperSU] zaphiel:
My pogo doesn't work with suhide0. 55, and SR2 supersu, and xposed that the partner grep_i post few post ago...

Safetynet test not pass neither.

Im newbie with this, is necessary install something more?

Thanks a lot.

Desde mi OnePlus One
[SuperSU] watoan:
Thanks Chainfire for the project.

I tried on my Nexus 6

- latest 7.0 stock NBD90Z

- OEM unlocked

- Rooted with Supersu 2.78

- Flashed suhide 0.55

- Android Pay 1.8.135831409

But I could not add any card, it prompted out the message "Android Pay can't be used".

Please help, Chainfire
[SuperSU] fozzie:
Are you on a custom DPI? If so, try changing to stock.
[SuperSU] Gosbo:
Thanks to DeadlyByNite i can get sn green, thanks to you for share your configuration ;)

Well, it still work yesterday in the morning, but i was lock in the morning today , i have an htc10 Europe with unlocked bottloader and OFFICIAL stock rom.

Previous config :

Su SR1 systemless with suhide no 06fix + magisk v8 with xsetprop module + xposed 86.2 systemless + rootswitch with check stop all su daemons

When sn fail i try to install SR2, but i have no sucess! try to uninstall magisk with the uninstaller but root wasn't working; magisk v7 don't want to be uninstall i don't understand magisk manager say it is install??!

Then in one step i uninstall xposed then suhide then i flash this :

magisk v8; xsetprop don't want to flash at this step, i can install it only via magisk manager ; SR2 supersu and type in terminal twrp echo SYSTEMLESS=true > /data/.supersu ; suhide 0.55 ; xposed 86.2

Then i reboot and install xsetprop and enable magiskHIDE reboot again and toggle root via rootswitch but sn still fail... Then i reboot for have root on and install No Device check via xposed86.2 reboot and check sn ; it was green ^^ no need to toggle off with rootswitch thanks a lot ;)

So happy too fast :( sn was Green but api fail (sn playground) and still can't add a card too :(
[SuperSU] grep_i:
And you're using root switch ?
[SuperSU] zaphiel:
Yes, disable with stop su daemons...

View attachment 3922861

Desde mi OnePlus One
[SuperSU] Atratus:
Root switch isn't working for me anymore either.

Root switch +Suhide v0.55+SuperSu 2.76-SR1+magisk v7+xposed 86.2
[SuperSU] grep_i:
I'm sorry to tell you that you are not very specific and if i'm going to help you, you have to be very specific about everything please don't let me guess what you did or mean.

Share very detailed about your device and used software versions and what you did to try to bypass safetynet and the exact result written in text or posted as screenshot or even uploaded as log file.

Maybe it is better to ask this question in the POGO thread.
[SuperSU] rumburak001:
Still running here on oneplus 2 with boeffla kernel.

SuperSu SR2 + suhide 0.55 + root switch 1.3.3.2

PoGo runs fine, actually I don't use xposed.
[SuperSU] Dalamar666:
Magisk could be your problem

I had magisk and xposed 86.6 and get cts error.

Delete magisk and installes 86.2. Green again
[SuperSU] dratsablive:
The latest version of SU Hide has not been released yet. Once it's available, install it and try Pokémon again.
[SuperSU] fakhry7:
I have this "no such file or directory" problem. Can anyone care to help me how to solve this problem?

[IMG="not found"]http://i.imgur.com/NkvcyKy.png[/IMG]
[SuperSU] JaLex77:
Clear Case of User error. Their is "no such file or directory" named /data/adb unless you've created one. Everything within the OP was very clear. If you cannot follow it, messing around with adb or shell is not advised.
[SuperSU] fakhry7:
no if you look closely there is already file named suhide-add,suhide-rm-suhide32.so and suhide64.so
[SuperSU] JaLex77:
And that's not how you call the commands. Follow the instructions within the OP, not for installation, for adding apps to the blacklist.
[SuperSU] fakhry7:
Sorry I'm still fail to understand.

"Add to blacklist: /data/adb/suhide-add UID "

Is that a command or not? how to add the UID?
[SuperSU] Chainfire:
suhide v0.50 preview

A NEWER VERSION OF SUHIDE IS AVAILABLE FROM THE OPENING POST

Terribly sorry guys, but there are still a number of showstopper issues with v0.50. Everytime I think I've solved them, something else pops up. I don't have time to document and help people right now either. In fact, I'm rush writing this post as I need to be out the door ten minutes ago.

I hope I can solve some of these problems over the next few days (or weeks, the rate this is going, haha), but in the meantime here is a preview release. Maybe the mechanism is just flawed and it can never be really fixed, who knows; I just don't want to make you guys wait even longer. It will definitely not work (at all or even a little) for everyone!

- This version uses su.d instead of ramdisk modification. If you have an older version installed, you must reflash SuperSU after flashing the attached suhide version

- You need SuperSU v2.78 SR1 in systemless mode

- All the scripts moved from /data/adb to /su/suhide

- I've had some success with topjohnwu's systemless xposed v86.2 until yesterday, then it suddenly stopped working; not sure if SafetyNet had another update? I suggest not using any xposed at this time.

Please help eachother while I'm away.
[SuperSU] uicnren:
EDIT: I am now able to add a card.

When I installed originally, I may not have re-flashed Super SU v2.78 SR1 after installing suhide v0.50.

[MENTION=631273]Chainfire[/MENTION] just a quick fyi post, installed v0.50 (Also SuperSU v2.78 SR1), AP does not work, cannot add card.

patiently waiting for updates, thanks again for all you do!
[SuperSU] bobby janow:
Do we need to have SuperSU installed before suhide? I'm getting an error can't mount /su.
[SuperSU] chocmatic:
[MENTION=631273]Chainfire[/MENTION] thanks. Tested new version and I'm able to add a card to AP
[SuperSU] Opticuhl:
http://imgur.com/S32wujQ[MENTION=631273]Chainfire[/MENTION] works great on latest SuperSU + suhide. Cant thank you enough
[SuperSU] redskinsfan:
Installed 0.5. Stock nougat with ninja 3.7 RC 1 and su 2.78 sr. Android pay now works - at least can add a card, but have not tried a purchase. As a bonus, AdAway now also can get root access. Thanks [MENTION=631273]Chainfire[/MENTION].
[SuperSU] meleelord:
0.5 working here on the 6P, ninja kernel 3.6, stock system. Can get access to android pay to add cards, and Pokemon Go works lol
[SuperSU] JaLex77:
Worked with pokemonGO as well as AndroidPay after adding them manually to SuHide in shell.

Was able to add cards to AndroidPay and use them as well.

Running Latest Stock Android N on Nexus 6P

As Chainfire stated, files have been moved to "/su/suhide" meaning the new add command is "/su/suhide/add UID" not "/data/adb/suhide-add" or "/su/suhide/suhide-add"
[SuperSU] NewBieSS:
Xperia devices can't use systemless root. Poor :(
[SuperSU] corkiejp:
Did you try with xposed?

I don't want to give up xposed for a game I'm not really playing.

But glad to hear Pokemon Go is working for others.
[SuperSU] meleelord:
I don't use xposed so can't say really.
[SuperSU] dratsablive:
Pokémon Go and AP working on stock rooted Nougat. Did not have to add them to suhide.
[SuperSU] JaLex77:
Interesting... That's good to know!
[SuperSU] desztan:
That's good. May I know the supersu version you have used and is xposed installed?
[SuperSU] Atratus:
Nuuu

Okay, I will try that, but I have to download the normal version of xposed right?
[SuperSU] Dalamar666:
No,, systemless xposed 86.2, from first post

Alsoo, flash sr2 ;)
[SuperSU] Atratus:
That worked.
[SuperSU] dratsablive:
Android pay will not work with an unlocked bootloader.
[SuperSU] watoan:
Oh I unlock the bootloader because I need to flash the twrp recovery img, in order to root my device with supersu 2.78, should I lock it back? but as I know locking it back will caused userdata reset, isn't it?

or is there any better way to do it?

Please advise, I really want to get Android Pay working with my rooted device.

Many thanks.
[SuperSU] FreeTheWeb:
Is there a working solutions for dm-verity phones i have s6 edge + and s7 edge so both phones are back on green pass from magisk (uninstalled all) is ok on stock but i would like to have root as well so is the SR from chainfire working with this phone's as is confusing allot of people say it works but not saying what phone model they have
[SuperSU] misteurz:
hi, i just tried to install suhide 0,55 on SuperSU 2.78SR2.

install on twrp with no issue, first boot with no issue : root check says i'm rooted .

But Safetynet helper doesnt pass.

So i run Supersu : it asks me to update binary.

Phone restarts in twrp, update binary,

and now i'm stuck with the LG Logo...

help...

(i'm on LG G5 H850, android 6.0.1)
[SuperSU] an0therus3r:
Does it work on any 7.x ROM?

I flashed this ROM on my OPO and flashed SuperSU R2 and suhide 0.55 but phone didn't boot at all.

Should i downgrade to SuperSU SR1 instead and try again or could this be a ROM issue?

Flashing all zips went just fine, no errors or something.
[SuperSU] deniskr:
Guy's there are only two things that you need to watch on... First is build.prop file, and second is boot.img... prop must stay on stock values, and systemless root like SuperSU,or phh superuser(for magisk) should stay hidden within boot.img..

SUhide( root switch) and Magisk V8 still passes safety net if you instal them right, even systemless exposed (v 86.2) still works if it stay hidden... If you can't pass safety net, that is because of compromised boot.img (to much changed from stock), or because you changed prop in some way... So put those two on stock, and than follow steps for installing SuperSU,SUhide,root switch combo, and then you should be fine... And yeah, that means flash original boot.img from original firmware, and cleen ROM and kernel instal... Unlocked bootloader is only problem if it was locked when you buy your phone...
[SuperSU] ashxdafan:
So far no go for us dm verity devices as far as ive tried. Since the 19th oct safetynet update, none of my combos worked with suhides for me.

[MENTION=6952047]grep_i[/MENTION] was helpful with his detailed guide tbh however it didnt work for me even via cf auto root and then using of flashfire instead of twrp flashed.

My challenge was to fastboot boot twrp.img with stock recovery intact.

Kept getting 'waiting for any device' prompt with no way to progress. Seems its no longer possible?

Perhaps someone will discover a way to preserve verity while having full root access. Pls lord send someone who can show us the light.

Someone like [MENTION=631273]Chainfire[/MENTION].
[SuperSU] grep_i:
Nice story can I ask how someone can change the boot.img to much from stock ?

Other question is what are the stock values of build.prop is there a way I can check if my build.prop is still stock ?
[SuperSU] deniskr:
You instal magisk(and some good modules),you instal systemless xposed, then you uninstall both of them because it's not working...then you instal SuperSU, then you instal SUhide, then you instal patch for root switch, then you find that still not works... Then you cleen all, instal rom, you unroot, and you still can't pass.. Why? Because your boot img was raped by those systemless stuffs... Then you flash stock boot.img and you suddenly pass... For prop? that is even easier to change, especially when you want pixel launcher, or google assistant, and then SN ask itself "WTF, how SGS4 can be my fellow Pixel?" And you get CTS fail...

All systemless stuff's modify boot.img, and more it's modified, more chances that you fail SN...

Prop you can check or change with ES explorer, or you can go in terminal and write "getprop"...
[SuperSU] ashxdafan:
Does your statement account for newer dm verity devices...? Thanks
[SuperSU] deniskr:
Unfortunately no... Just ordinary phones without DM verity...
[SuperSU] henderjr:
If somone is using a newer Samsung phone take a look at this post. Works on my Note 5. http://xdaforums.com/showpost.php?p=69412347&postcount=1215
[SuperSU] zapahacks:
Could you give a try to this please and report back;):good:
[SuperSU] leolawliet:
I'll give it a try later. I cleared the data as well. Thanks
[SuperSU] ashxdafan:
Thank you. Ill give it a shot! Thanks too [MENTION=747208]henderjr[/MENTION]
[SuperSU] leolawliet:
That sucks now I think I know what I did wrong to make AP stop working. I added two lines to my build.prop file earlier to enable EIS on my N5X. I'll see if that fixes the problem if all I must do is remove those lines.

---------- Post added at 09:52 PM ---------- Previous post was at 09:47 PM ----------

I haven't restored the build.prop to stock for the ROM I installed, but with the still modded one I'm using I do have success with PoGo and SafetyNet Playground, I haven't tried AP yet but I restored stock dpi and font size and I cleared the app data for AP and I was able to add a card. I'll try to make a purchase and post if it works or not.
[SuperSU] grep_i:
first do

adb reboot-bootloader

And when you see the bootloader screen do

If on linux

sudo fastboot boot twrp.img

On windows you should start cmd with administrator rights

fastboot boot twrp.img
[SuperSU] deniskr:
SN don't care for DPI, and font size mods within prop file, but change prop so you can instal Pixel launcher, and then SN will care, SN look's for phone ID within prop file, not for color of your font... Similar is with boot.img... SN tolerate some modifications, but if you modify boot.img to much, SN will turn red... Bootloader is irrelevant if it's manufacture unlocked, SElinux is irrelevant if it's not modified...if kernel is permissive, it will pass SN, but if kernel is enforcing, then it will fail when you set it on permissive... The best way to go is with stock boot.img and unmodified prop, then you can see what you can modify, and what will trigger SN... But as I said, SuperSU/SUhide/RootSwitch works if they are installed right, and on clean boot.img...
[SuperSU] leolawliet:
SuperSU + suhide + Root Switch is the only combo that ever worked for me.
[SuperSU] yochananmarqos:
No, do not relock your bootloader unless you're completely stock. Yes, it wipes all user data including internal storage just like unlocking.

As of the last day or two, Android Pay cannot be used with suhide or Magisk Hide due to the new SafetyNet API update. However, you can unroot keeping your bootloader unlocked to use Android Pay. You'll need a custom kernel that includes the commit to hide the bootloader status like Franco or Flash.
[SuperSU] NYZack:
I don't think a lot of this is true. I have modified build.prop on my Nexus 6 to change the model to Pixel XL (to use the Google Assistant). I also use a completely non-stock boot.img (Franco kernel). I can pass Safetynet and today used Android Pay to make a payment. I use SuperSU, suhide, and Root Switch. I had to use xsetprop to set my bootloader locked status to locked, but that's it.
[SuperSU] _litz:
I have SN working with a stock moto X pure, supersu, suhide, and the latest rootswitch.

as long as rootswitch is off, SN passes.

(hint: set rootswitch to use notifications, and it's easy to switch on and off)
[SuperSU] grep_i:
Are you sure that this is true, I really do not believe this, this seems to be misguiding people.

If what you say is true than my boot.img would be raped as you say.

Do you know that reflashing superSU restores stock boot.img before patching boot ramdisk again.

Anyway I modify my boot.img and flashed unsu when not really needed and still I pass safetynet so I guess your story is not correct.

Also I added some random lines to build.prop and still I pass safetynet and as you can read in some threads around here one way to bypass safetynet is by adding a line to build.prop

And you still have not explained how you can see if your build.prop is stock or not.

I have systemless:

SuperSU and Xposed

And a custom kernel that also modifies boot.img ElementalX
[SuperSU] jimbo77:
No permanent solution. So use SR1 + Root Switch only. If you want xposed (like I do) flash systemless 86.2 and if you need to use Android pay or Pogo just Uninstall xposed from recovery.

The whole coming and going takes around 2 minutes. If I want to use pogo I Uninstall xposed and disable root with root switch, after I'm done playing I'll flash xposed again....
[SuperSU] deniskr:
SN scan's boot.img and prop file, and it's not important what you believe.... Modifications are OK if you can hide them, and that is what SUhide do, but would you pass without SUhide? As long as everything is installed properly it works,and that is what I wrote.... When you got red CTS, it's because something was find by SN in your boot.img or prop... Try instal Pixel launcher or google assistant with mod prop that change device name, and than run SN test with your working combo, you will see how it turn's red... As long you don't mess with phone ID in prop file you are good to go,even with random lines that don't do anything with phone ID... As long as you instal SUhide in proper way,it works,until google decide to block it...
[SuperSU] mrxtc89117:
I have an unlocked bootloader, custom kernel and modified build.prop. I pass safetynet green. I installed sr1-supersu-2.78, suhide 0.55, xposed 86.2 and root switch.
[SuperSU] grep_i:
I have Google assistant installed but what do you mean by:

mod prop that change device name

I want to test your theory cause for me it even works with Google assistant installed, can't test pixel launcher as I'm still on marshmallow.
[SuperSU] deniskr:
I have same combo on SGS4 and yeah it works... But who cares for that? I was thinking on people that have same combo but for some reasons it don't work... So yeah, for them clean ROM instalation with flashed stock boot.img would be a good start for solving the problem... When SN will start detecting proper installed SuHide/root switch, then everyone will be red on test....
[SuperSU] chudy_85:
What permission you have on file suhide.uid ??? I ask because copy all file and set permission but when I use root switch it's don't pass safety net

Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka