yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
v0.12 release notes

First off, thanks to everyone who has tested this so far. The first release had quite a few issues, and I'm sure this release will add a few more. Hopefully it also fixes a few of them, though :)

The /data/adb/suhide-add and /data/adb/suhide-rm scripts had some obvious errors, which could lead to UIDs not being addable/removable. That should now be fixed.

An error in the install script caused broke installation on 32-bit devices, causing root to be lost for all apps. That should now also be fixed.

Devices that asked for an encryption password/pattern/pin at boot would bootloop. I think that issue is now fixed, but I have not tested this myself yet - let me know how this works out for you.

I've also added theoretical support for x86 and mips devices, both 32-bit and 64-bit variants. Theoretical because I do not have any test devices - so let me know how this works out for you.

I would also like to note that the installer breaks on older TWRP versions. This is the cause for the "No such file or directory" error some get when trying to use the suhide-add command. The only solution is to update your TWRP to a newer version, or use FlashFire to install the ZIP instead.

Last but definitely not least, I have added some basic GUI hiding. In other words, other apps can less easily detect the SuperSU GUI being installed. It's not perfect, but it's something. I learned a few new tricks there, as this hack employs methods I have never used before (fun!).

Due to these changes, you are now required to reboot your device after adding/removing UIDs, for the hiding to become operational. Also keep in mind many apps store the root detection status, so you may want to clear the app data of any app you want to hide root from, before doing that reboot.

Please be advised that you should flash the uninstall ZIP before flashing the new install ZIP, to prevent issues. This will also make you lose the current list of blacklisted UIDs, however.

You can find the downloads attached to post #1 and the changelogs in post #4

I am always interested to hear for which apps this does or doesn't work, so post away.
[SuperSU] mmoogle:
The new version now works for me. Just bought some cookies out of the vending machine with AP.
[SuperSU] nathanchance:
The Nexus 6P is a 64-bit device, that's why it works in your case but not theirs. Just a heads up for the future :good:
[SuperSU] davy4475:
Anyone try this on an s7edge?
[SuperSU] Chainfire:
FWIW, it works on my S7 (non-edge)
[SuperSU] CSX321:
The new version works perfectly now on the Nexus 5. Thanks [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] uicnren:
[MENTION=631273]Chainfire[/MENTION], unfortunately it bootloops for me still on my 6P. As opposed to the first version however, it makes it to the point of asking for my PIN at boot, but no keyboard is visible, so I cannot input anything. After a period in that state, it bootloops, but never back to the PIN input screen.

I dont have time at this moment to grab a log, but will do it later when I have more time.
[SuperSU] bobby janow:
Same here. Uninstalled, rebooted, installed new version, paid for cookies with ap
[SuperSU] Chainfire:
Which Ad-Away are you using? There are various mods to it. System or systemless? Please provide links.
[SuperSU] mmoogle:
AdAway 3.1.2 from either F-Droid or here: http://xdaforums.com/showthread.php?t=2190753&page=1. Both using the systemless hosts mod linked at the XDA thread.
[SuperSU] izeeqo:
I uninstalled it and reinstalled but always crashing...
[SuperSU] grep_i:
OK did you try using another kernel too ?

If this does not work I'm out of options and would advise you to try further in device specific thread.
[SuperSU] izeeqo:
I haven't tried using a another kernel. Currently I am on a custom kernel, but i'll try it.
[SuperSU] Drakit:
I definitely do not run this method, when you install both files and give reboot, no root permissions ... agreed to have a program z2 in room stock 6.0.1
[SuperSU] rolandvrielink:
I found the line with bindsystemxbin in it.

Will pokemon still work when I place this line bindsystemxbin in TWRP recovery terminal??
[SuperSU] marchrius:
Is it possible to have systemless root on G901F without tripping Knox?
[SuperSU] meiser:
Hi,

I installed suhide successfully on CM13. Here's my list of working and non-working apps.

Working:

- EntertainTV mobil

Non-working:

- Payback (Paypack Pay shows "unsecure device")

- ElsterSmart

- Sparkasse+

It's not clear to me how I can find out which mechanism the apps use for the detection. Could you give me some hints?

Regards,

meiser
[SuperSU] Didgeridoohan:
Have you added the UID of the non-working apps to the blacklist?
[SuperSU] ameel:
suhide 0.53 not working with SuperSu 2.78 SR1 on Xperia Z, CM13 Android 6.0.1.

SafetyNet passes when nothing installed.

Install SuperSu 2.78 SR1, SafetyNet fails (as expected). SuperSu runs fine and phone is rooted.

Install suhide 0.53. Installation completes without errors. when mounted, /su contains a folder suhide with files app_process32 and suhide.uid. SafetyNet still fails

Any ideas?
[SuperSU] adamaris1990:
Hi I have exactly the same problem with my friend in previous post....I have Samsung g900f s5 TWRP 3.0.2.0

And last update of XxX marshmallow rom...
[SuperSU] grep_i:
Check the hint one post above yours.

If that does not work you're pretty much on your own as this software is experimental and unsupported.
[SuperSU] adamaris1990:
Because I have the same problem no he can't blacklist of non working apps UID. .No such file or directory! !!
[SuperSU] ameel:
I thought SafetyNet gets blacklisted on install?
[SuperSU] meiser:
Of course! Why would the other app work if I didn't know how to add it to the blacklist?
[SuperSU] grep_i:
In my case this happened but as this software is experimental and unsupported there are no guarantees, so you have to check it for yourself if it really is blacklisted.

You could also try to start from scratch and hope it will then work but it is all guessing.
[SuperSU] Didgeridoohan:
I have no idea what app that is, so for all I know it might use Safety Net (blacklisted by default). Since you didn't mention anything about blacklisting apps, I had to ask.
[SuperSU] bobby janow:
What would be the proper procedure for sideloading the new OTA for the N5x? Uninstall everything, ota, reinstall everything? Everything meaning suhide, Supersu. I am totally stock otherwise with no xposed or custom recovery.
[SuperSU] Ch3vr0n:
You should be able to flash as is. Suhide gets installed in /su and does not modify system.
[SuperSU] Meloferz:
Same phone, same issue, anyone managed to make it works suhide on Xperia Z2 with stock ROM 6.0.1 and custom kernel?
[SuperSU] Ch3vr0n:
[MENTION=2659927]bobby janow[/MENTION] in the event that it does fail (which it might due to modified boot image by SuperSU), I'd recommend you taking a look at FlashFire app by chainfire. It allows you to flash ota's while simultaneously rerooting afterwards. When superSU gets installed, it creates a backup of the stock boot image. With flashfire you're able to restore that backup image, thus qualify for the ota and apply it. When the ota is applied you can then either use the built-in 'everroot' option to immediately after root the new build, or use the SuperSU zip is it's newer.

Flashfire is very powerful and in a sense an on-device replacement for adb and fastboot to flash ota's.
[SuperSU] ameel:
Files didn't copy despite successful install.I copied the files and inverted the links manually. SafetyNet passes now with superuser still working. Next issue is xposed 82.1 installed, activated but modules dont appear to be working even though active. Really weird..
[SuperSU] Ch3vr0n:
Nothing weird at all, you didn't read the first post. It's in the first post you need xposed systemless 86.2 (by a specific user).
[SuperSU] bobby janow:
Not sure why I didn't think of that myself. Just a little out of practice since not flashing much these days. I have used Flashfire in the past to great success and just did it now with the same results. Thanks buddy, I really appreciate the heads-up.
[SuperSU] FreemanAMG:
I just installed the October security patch, and apparently, suhide stopped working after that. Has anyone experienced the same thing?
[SuperSU] grep_i:
I guess you made a typo never heard of Xposed 82.1 you probably meant [MENTION=2476451]romracer[/MENTION] v86.1 which is the same version as is working for me.

If that's the case you could also try [MENTION=4470081]topjohnwu[/MENTION] v86.2

That's because SuperSU tampers with boot.img to work.

Installing October security patch restores default boot.img.

Probably your root access does not work anymore too just reflash root and suhide.

If using custom kernel you have to reflash that too.

If using Xposed framework you have to reflash that too.
[SuperSU] FreemanAMG:
Thanks, perhaps I needed to be more specific.

I installed the October patch manually (flashed all images but userdata.img). Then I reinstalled supersu and suhide, as usual. However, the Safetynet request is not passing anymore. Last time I tested it was yesterday, still with the September patch. Not sure if this new version breaked the suhide support, or Safetynet was just updated again
[SuperSU] bobby janow:
Nothing has changed in the October update for me. I did the OTA, however. Everything still working as before. Try uninstalling suhide and SuperSU and checking safetynet again. If it doesn't work then it is something else.
[SuperSU] LifeDark666:
Problema with Pokemon go...
[SuperSU] voland66:
Flashfire works for me with ota on nexus 5x. Downloaded ota file, then added it to tasklist in flashfire, selected "attempt to restore stock boot and recovery" checkbox, made sure "mount system read/write" is NOT selected and flashed. Flashfire automatically reinstalled twrp, rerooted, and i did not even have to reflash suhide. I did not try Android pay after ota yet but phone passes safety net.
[SuperSU] Skyrider:
Guess I installed the older version http://phhusson.free.fr/superuser-r266-hidesu.zip made for magisk and now everything is actually, very much broken. magisk no longer works (boot loops when I attempt to install) and all uninstallers I used didn't work either. Shame, now I'm forced to reinstall everything again if I want magisk to work again.
[SuperSU] MceeK:
Pokemon should work if everything is installed properly... I have it working on my S3

I think you also need to flash SuperSU again after you put the systembindxbin line in and then install suhide
[SuperSU] vyovyo:
求助

Hello, I can not find systemless xposed v86.2 download points can help me

這邊下載點都掛了
[SuperSU] civicsr2cool:
Fwiw Su hide isn't playing well with any xposed for me. RR v86.1, topjohnwu v86.2 and v86.6 all stick at starting apps with su hide. Su hide and sr1 su play well together for me and sr1 su and all xposed versions work, just not the trio. This is on s4 mini (i257m) and s5 mini (g800m) on various cm13 Roms.

---------- Post added at 09:23 AM ---------- Previous post was at 09:18 AM ----------

https://drive.google.com/file/d/0Bx5gPVuLapkKR2tfUExVNzhQVGM/view?usp=drivesdk

There is also a new compatible version v86.6
[SuperSU] vyovyo:
civicsr2cool

thank you ?
[SuperSU] Zarg95ET:
Will this not work for the Verizon Note 7, i tried to install it and it blocks my phone from booting up due to custom binary blocked by secure boot (boot.img)?
[SuperSU] Droidphilev:
Hi,

Is the hiding of the SuperSU APK/GUI done automatically? I gave it another try today for an app that hates root (and which also scans for the SuperSU APK/GUI). Root was still detected untill i added SuperSU on the Suhide blacklist also. After a reboot SuperSU started crashing but the "root hating app" started working again. Removing SuperSU from the blacklist stopped SuperSu from crashing but the root-hater showed a popup again that i'm using a rooted device. I guess this is not the way it should be/work?
[SuperSU] Triviox:
Someone did can install suhide in Galaxy j5? Always i try still "logo" bootloop =/
[SuperSU] D168:
Would my kernel impact performance after installing suhide? On my Nexus 6P with ElementalX 1.21 kernel, my phone was super slow, and any apps that weren't active would always close. I'm not sure if this was just because of suhide, or if it was a combination of other things as well? I uninstalled suhide and my phone is basically back to normal and runs with no issues, but alas, no Pokemon Go for me.
[SuperSU] gleggie:
Thank you for this. Running flawlessly on my OnePlus 3, stock OxygenOS 3.2.7, rooted with SuperSUv2.78-SR1, with Xposed v86.2

Pokemon Go works for me, though I do not use Android Pay so I have not tested.
[SuperSU] hokiealumnus:
This one got very quickly buried so I thought I'd try again. I just can't get suhide to work. Tried again a few minutes ago too. Any ideas would be greatly appreciated!
[SuperSU] habylab:
Have you managed to get this working with v86.6?
[SuperSU] rafaric:
I have a Huawei P8 Lite and every attempt for install suhide make my phone very slow. I flash with and without magisk but with no luck. Anyone have been this troubles? Sorry for the bad english...:o
[SuperSU] gleggie:
Haven't tried, since the OP states that it should only be used with that specific version of xposed
[SuperSU] traumatism:
Can the files be manually added to an SU folder via file manager like in twrp? Obviously knowing which files of course.

Sent from my Mind
[SuperSU] Ch3vr0n:
What files? You don't add files in suhide.
[SuperSU] akarol:
Wha... I just used Flashfire to update my 6P to the X October update and I didn't need to flash suhide to pass SafetyNet. Does this make sense? It seems like it's working as it should right off the bat.
[SuperSU] Ch3vr0n:
Yes, because suhide gets installed in /su not any partition checked by an ota
[SuperSU] Turk89:
fatal error : system/xbin/su found .. I tried to deleted it but with no success, any help please?
[SuperSU] Rhoban:
There is one in /system/bin too.

Also, SuperSU must be installed in systemless mode. Are you sure it is?

---------- Post added at 01:06 AM ---------- Previous post was at 01:02 AM ----------

Are you sure SuperSU is actually flashing in systemless mode?
[SuperSU] hokiealumnus:
Yes, for sure. TWRP shows it flashing systemless and going through the boot IMG modification as it should. I'm truly stumped, as afaik I'm doing everything right. :shrug:
[SuperSU] Rhoban:
The only thing I can think of is that bump thing.

Is this for official firmware or custom ROM?
[SuperSU] hokiealumnus:
I've tried both actually (three, technically - AOSP and CM based ROMs plus a stock based one) and ended up with Magisk on both. Interestingly, I flash the bump file after Magisk too (or, like SuperSU, it won't boot) and no issues there.

I tried uploading the bump file for inspection but labs isn't cooperating, apologies.

It really is a puzzle, and thank you very much for responding.

Edit - Very interestingly, I just tried phh's hidden su (he just came out with it yesterday) and It works. Only suhide isn't working for me. It's the one I really prefer though, because I'd like the convenience of using Xposed. I'm happy and grateful phh's works; xposed would just be icing on the cake.
[SuperSU] Rhoban:
Could be kernel related maybe? I can't get suhide to work on Slim6. Works on AOSP ROM though. The only difference is the kernel.
[SuperSU] Turk89:
I managed to delete this one but why the one in xbin wouldnt let me to although root browser says "deleted su" but its not. I tried with ES and would return with read-only when i try to delete it. When entering in the terminal echo "SYSTEMLESS=true"> /data/.supersu it created in the data folder a file name called .supersu and have flashed the supersu SR1, is this how its done? Yet the su file in xbin wont get deleted
[SuperSU] Rhoban:
Delete it using recovery. Don't forget to mount the system partition first.
[SuperSU] Turk89:
Although I'm new to all of this but mounting the system partition meaning make it writable not just readable or I have to mount it through twrp? I'll see if I can make it writable so I can delete the su file from xbin using recovery otherwise I'll mount the system partition through twrp.
[SuperSU] grep_i:
TWRP is custom recovery yes you have to mount /system r/w in TWRP custom recovery.

Mounting is not the same as making it r/w you can also mount read only.
[SuperSU] Mauziii:
Can anybody provide a guide to get Pokemon to work? So I've blacklisted it and also tried several reinstalls. But it will never get any further than the loading screen
[SuperSU] Antyhaker:
After successful install (suhide) just reinstall PokemonGO - worked for me.
[SuperSU] Turk89:
[MENTION=6312707]GDReaper[/MENTION] that did the trick, Thank you so much for all the replies. OMG I have unrooted my device like I can't count to try to delete it, how noob that was and all it takes is mounting the system as write not just read and su is deleted through recovery and suhide is flashed successfully. Final question, how do I know if my supersu is systemless? sorry for the newbie question.
[SuperSU] Rhoban:
It says during the flashing of the SuperSU zip if it flashed in systemless or system mode.

The only other way, I guess, is if you have root and pass SafetyNet check.

---------- Post added at 08:54 AM ---------- Previous post was at 08:53 AM ----------

Pokémon GO is blacklisted automatically. There must be something else that is wrong.
[SuperSU] grep_i:
When booted to system you open the superuser app and check for this.

"Install SuperSU into system" should be grayed out and the line under that reads.

Not (currently) available in system-less root mode.

View attachment 3894991
[SuperSU] Taomyn:
A default installation of suhide should be enough - afaik Pokemon Go currently uses Google's SafetyNet API to detect root etc and suhide fixes this without you needing to do anything other than correctly installing suhide.
[SuperSU] grep_i:
You're right worked for me without changing anything after flashing suhide 0.53 in my test situation Pokemon Go started and safety net passes it checks.

This was even with [MENTION=2476451]romracer[/MENTION] Xposed v86.1 installed.
[SuperSU] Turk89:
Unfortunately I didn't pay attention during flashing superSu whether it flashed it systemless or in system mode but I do thank you very much again for the help and replies.

Awesome, I do have exactly what you have stated and the photo you have attached in my SuperSu which I hope this mean that my SuperSu now is installed in systemless mode. So If SuperSu isn't flashed as systemless in this case the "Install SuperSU into system" wouldn't be greyed out, right? Thank you for the help
[SuperSU] habylab:
Has anyone got a link to v86.2 Xposed? The link in the OP does not have it attached anymore. Thanks!
[SuperSU] Rhoban:
Xposed V86.6 should also work with suhide now.
[SuperSU] habylab:
I have several issues with v86.6 specifically. I've given up with Android Pay now so now all I want is a working Xposed. I figured skipping Magisk is probably the best way around my framework issues.
[SuperSU] Ch3vr0n:
No it's not. Pogo used safety net, which uses play services. It's play services that's blocked automatically
[SuperSU] Shadowghoster:
Pogo isn't using safety net. Otherwise it wouldn't work when you use systemless Xposed. SafetyNet isn't passing with systemless Xposed but pogo still works when you have systemless SuperSu and suhide in place.
[SuperSU] osm0sis:
Incorrect. Pokemon GO has been well shown to be using SafetyNet otherwise suhide wouldn't allow it to work out of the box (which it does - only blocking Google Play services, ie. SafetyNet). Search the thread. Whatever weird complications Xposed brings you can probably blame on Xposed.
[SuperSU] Turk89:
I have installed safetynet helper to check if the device can pass the safetynet since now SU is in systemless mode with suhide flashed as well still can't passes the safetynet. Can anyone help me please making the device pass the safetynet check
[SuperSU] traumatism:
Sorry I mean the super user files. Not suhide. My bad

Sent from my Mind
[SuperSU] garreth83@gmail.com:
Note 4 (SM-N910G) - System UI crashes upon start-up and bootloop

[MENTION=631273]Chainfire[/MENTION] - Just tested suhide v0.53 on the below device:

Note 4 (SM-N910G)

Marshmallow 6.0.1

Stock Samsung Touchwiz ROM

Rooted with Systemless mode (v2.78 SR1)

TWRP 3.0.2

ERROR - System UI crashes upon start-up and bootloop.

Liveboot.log attached.
[SuperSU] Mario.D:
Just looked trough your log fast.

It seems that Exposed are to blame for your problems to boot.

Wich version of Exposed are you using?

Skickat från min E6653 via Tapatalk
[SuperSU] Ullson:
Hey Guys it's me again.

Still using an S4 gt-i9505 with the custom rom Ressurection Remix.

I've since tried completely resetting the phone, installing the custom rom again, unrooted (I tried it without unrooting first, didnt work) then flashed SuperSU v.2.76, restarted, flashed suhide v.0.53 (0.52 didnt work). Then I looked for the su-files in the xbin and bin folders first with TWRP (which didnt even show the xbin and bin folders, even though it had su-rights) and then with terminal emulator with su-rights (which showed me the folders, but they were empty).

SafetyNet Helper still says CTS Profile Match: false. (Now it shows an error message: Response payload validation failed)

I tried everything I could think of (the command to flash SuperSU systemlessly and not rebooting after flashing and all the tips you've given me) but I still can't get it to work.

So it's probably safe to say that suhide won't work with Resurrection Remix. Any idea of getting it to work would be much appreciated :)

Thanks for even taking the time to make this work for most people
[SuperSU] Vember31:
Oct 5, 2016 SafetyNet Update

I've been using suhide 0.53 successfully for a few weeks, though it appears the SafetyNet API was updated today. Minutes ago, specifically. Can anyone confirm this? I was passing successfully before, but now am getting response payload validation failed. One other person I know using suhide is now getting the same (was working before), so I was figuring SafetyNet was updated. We are both using systemless xposed (v86.2). When I disable xposed, I'm still getting the same error message. Didn't try fully uninstalling it, nor did I try a clean flash with systemless root and without xposed.

Wasn't sure how / where to see any changes to SafetyNet to confirm further on my own.

Appreciate it!
[SuperSU] petrs1:
Actually response validation: fail me too:(
[SuperSU] djRamage:
I believe you are right, same situation with me.
[SuperSU] loserskater:
Can confirm. Using SuperSU 2.78 SR1 with suhide 0.53 fails SafetyNet as of this morning.
[SuperSU] pharmdeon:
Yes ... no longer working as of only a few min ago ... lame ...
[SuperSU] EViollet:
Same here with the new Magisk solution. No longer working.

I guess this was bound to happen sooner or later.

Let's just hope someone comes up with a solution.

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[SuperSU] mortillo:
CM13 + supersu + suhide + xposed systemless i get safetynet check failed. Since 30 mins ago. :(
[SuperSU] AsturzioAugias:
yep, I was about to write the same thing...
[SuperSU] aldanopolis:
Check if your selinux is enfocing

Enviado desde mi Moto G mediante Tapatalk
[SuperSU] mortillo:
How?
[SuperSU] Sector-z:
Same for me since 30 minute ....
[SuperSU] dratsablive:
Just was going to post. Safety Net was working until about an hour ago. Was able to play Pokémon all day until now.
[SuperSU] garthybarthy:
Confirmed, was working 2 hours ago. Not anymore.
[SuperSU] Vember31:
I don't think SELinux affects it, at least with my setup. Both permissive & enforcing still fail SafetyNet for me.

Nexus 6

Resurrection Remix 5.7.4

B14CKB1RD Kernel

SuperSU v2.78 SR1

suhide 0.53

Systemless xposed v86.2
[SuperSU] euclanville:
Magisk v6 + phh17 without xposed. Toggling failed too
[SuperSU] aldanopolis:
Actually, you need enforcing for make work safety net

Enviado desde mi Moto G mediante Tapatalk
[SuperSU] osm0sis:
Yup, the ante has been upped, [MENTION=631273]Chainfire[/MENTION].
[SuperSU] Sector-z:
People report same thing here too https://www.reddit.com/r/pokemongodev/comments/560o9a/safetynet_updated_again/