yashsingh1/xdaforums huggingface dataset:
[SuperSU] ZarltanXDA:
[MENTION=7280276]ipdev[/MENTION]

Thanks for the above response, I took your advice on deleting the file and it was a success, as of now SU Hide Lite is fully working on Lineage OS 14.1 following the step by step and deleting the conflicting /system/xbin/su file
[SuperSU] tHset-01:
Yeah,i even have to reflashed it that way, cause suhide found su in xbin,so i used a script to clear all root and flashed SR3 using aroma installer and suhide afterwards.
[SuperSU] DIXES:
Does anyone try suhide 1.08 on Asus Zenfone 2 (ZE551ML) with stock firmware Android 6.0.1? I tried it but SafetyNet check failed, even though root hidden feature works well, selected apps doesn't detect device is rooted.
[SuperSU] KaMyKaSii:
As has been said several times, please try again after wiping PlayStore data
[SuperSU] DIXES:
No, it doesn't work either. But if I use SuperSU (not sbin mode) with Root Switch or use Magisk then SafetyNet check passed.

Maybe it is an x86 issue with SuperSU 2.82 (sbin mode) with suhide 1.08? Asus Zenfone 2 is an Intel Atom platform Android phone.

SuperSU 2.82 (SBIN Mode) with suhide 1.08

Magisk v13
[SuperSU] Ch3vr0n:
That's because you don't need 2.82, you need 2.82-SR3.

Sent from my Nexus 6P with Tapatalk
[SuperSU] enjelpuspa:
Great work! Still waiting for Xposed compatible version :)
[SuperSU] Midomad:
Working like a charm on my OP3T.View attachment 4263886
[SuperSU] Abolfazl:
Is anyone able to get this to work with the AirWatch Agent app? It is still able to know that I am rooted.
[SuperSU] osm0sis:
Did you add the app to the suhide list?
[SuperSU] id74em8:
suhide fatal error: code 1

device cancro

android 8.0

suhide posts the message

"fatal error: /system/xbin/su found"

I cleaned /system and reflashed os and SuperSU. Verified systemless mode.

error persists.
[SuperSU] DodoGTA:
Mount /system partition and remove /system/xbin/su file manually using TWRP before flashing SuperSU and suhide (It's built on AOSP for debugging purposes on userdebug and eng build variants)
[SuperSU] max414:
Safety net passed.

App put in red mode in supersu hide

Still detects root

S6e nog33 rc

Nne 5.1

Bootloader unblocked
[SuperSU] dallen5:
What's the steps on doing this?
[SuperSU] DodoGTA:
I'm assuming that you're in TWRP and you installed your ROM before doing this

1. Tap "Mount" and tick the checkmark in the box labeled "System"

2. Go back to TWRP's main screen and tap "Advanced", then "File Manager", "system", "xbin" and "su"

3. And then, tap "Delete" and swipe the slider at the bottom of the screen

Now, you can go to TWRP's main screen, tap "Mount" and untick the checkmark in the box labeled "System" (And then, you can go to TWRP's main screen)

And, you're done! (Now, you can flash SuperSU and suhide)
[SuperSU] mossywell:
Good thing I read about wiping Google Play Store data - before that I thought "oh no, it didn't work"! ;)

[MENTION=631273]Chainfire[/MENTION]: as quite a few people have had this problem, might it be worth adding wiping Google Play Store data to the OP? Just an idea.

Cheers!
[SuperSU] dallen5:
Thanks alot
[SuperSU] Abolfazl:
Yes I added Agent to suhide to hide root from it (red icon) and it still does not work.
[SuperSU] jcmm11:
Did you hide SuperSU? (See 'About' in suhide, 'hiding apps' section)
[SuperSU] Abolfazl:
That fixed it after I rebooted the phone
[SuperSU] Abolfazl:
So this was able to initially work but as I went through the process it knew my device was rooted and it stopped working.
[SuperSU] id74em8:
I did that already, but for some reason it seems to have come back. Thanks though, I figured it out.
[SuperSU] jeff880814:
For My Sony XZ Rooted Device

It doesn't seems to work on my rooted Sony XZ, I follow every step on the instruction, but every time i reboot, and i tap the SuperSU, it just showed that the su binary occupied, this message showed up every time i re-swipe the supersu file. Can anyone solve this problem for me, sorry for my bad English.
[SuperSU] zeft64:
Is supersu-sr newer than normal super super?
[SuperSU] tufyuma:
Sorry, Wrong forum.....
[SuperSU] Paschfire:
SR~"Service Release"

Pls read the OP section of SuperSU thread, also OP#2 explains SuperSU version numbering and SR builds in greater detail including access to ChangLog information.

See here > https://xdaforums.com/showpost.php?p=68530643&postcount=2
[SuperSU] zeft64:
For some reason I keep getting this. Idk what I'm doing won't here
[SuperSU] osm0sis:
Flash unSU then use the SuperSU Config AROMA zip to enable BINDSBIN mode in the .supersu config file, then reinstall SuperSU, then install suhude.
[SuperSU] Droidphilev:
Are you flashing ElementalX before SuperSU config and SuperSU? If so: remount /data in TWRP before flashing SuperSU config and SuperSU. (i don't know why ElementalX aroma installer unmounts data after flashing). As osm0sis adviced: also flash unSU. I always flash it right after flashing the rom zip.
[SuperSU] zeft64:
Nevermind. I figured it out I just forgot to tell you guys ?
[SuperSU] jmfurtado:
SuHide on Galaxy A3 2016

I tried it using TWRP on my rooted Samsung by successfully setting the SBIN mode on SU ( which I verified with RootExplorer ), reflashed the last SU version and the SuHide zip file with and without rebooting between the 2 installations.

After that process my apps could still identify the root on my device and no SIM card could be recognised any longer.

I always keep a full backup so I only had to restore the device back.

I keep using Samsung because they are reasonably reliable and I can always get their original ROM files and use them with Odin, but it annoys me all the increasing "safety" restrictions and the loss of warranty for refusing not to be able to manage my devices the way I want!

And I love xdadevelopers for making it possible!

Good on you

Jose Furtado

( From Estoril, Portugal )
[SuperSU] bschatzow:
No. I did not want to change slot b. With pixel you can have different versions on each slot.
[SuperSU] bschatzow:
I did the full flash all.bat before I saw the other SU. This allowed me to root again.
[SuperSU] :
suhide won't install for some reason

I'm on Nexus 5 using Pure Nexus 7.1.2 (20170731 version) and I did the following steps:

1) Clean install Pure Nexus through TWRP

2) Do the AROMA script for SuperSU Config through TWRP

3) Install SuperSU v2.82 SR3 through TWRP

4) Reboot into Android to verify SuperSU install

5) Try to install suhide from TWRP

But I get the following error every single time (I've tried this in various ways about 5 times until now):

"/system/xbin/su found" (attaching a photo of the error)

Any ideas?

P. S. - I did the entire thing once again right now (even upgraded TWRP to the latest version just in case), clean install. The problem is that when I install SuperSU it creates the file /system/xbin/su and therefore the suhide installation fails. Not sure where to go from here - either my AROMA config script isn't working or there's something else ****ing up this installation.

Either way, I'm giving up for now since I've wasted several hours without any real progress.
[SuperSU] osm0sis:
Flash unSU after your ROM, then do the rest of what you described.
[SuperSU] jcmm11:
That sounds as though you set BINDSYSTEMXBIN to true. If so that's a mistake, you don't want to do that.

If it doesn't work again, after doing what osm0sis' suggests, post the contents of /data/.supersu

(I haven't used the AROMA config so not sure exactly how things are specified in there)
[SuperSU] :
It worked!

Thanks, osm0sis and jcmm11!! :)
[SuperSU] SSH316:
I can't pass safetynet on my I9300 andoid 7.1.2 with RR/crDoid/LineageOS

No error during install Su 2.82 SR3 and suhide 1.08
[SuperSU] DodoGTA:
SafetyNet check result?
[SuperSU] SSH316:
View attachment 4269614
[SuperSU] jcmm11:
Did you install SuperSU in sbin mode?
[SuperSU] SSH316:
Yes, even tried with supersu config( aroma) and no success with passing safetynet
[SuperSU] Zehlek:
Stupid question, I'm running NOS Oreo on Kenzo, does this mean SBIN is already active and I just have to flash the two files in TWRP(SuperSU and Suihide?
[SuperSU] rocky78:
changed in build.prop.editor from user-keys to release-keys and now it doesnt detect its rooted.

But stil it dosent let me log in because of "security prblems".

Maybe all now is left to do is contact my admin and ask them to release my blocking on the server.

Will update.
[SuperSU] GopalKaul:
[MENTION=631273]Chainfire[/MENTION] it does not work on my nexus 5 on LOS 14.1 . Even though I put it on SBIN mode, it does not work. Any help?
[SuperSU] rocky78:
build prop editor.

Why?
[SuperSU] KaMyKaSii:
I think you should make it totally explicit that it is not possible to install suhide having Xposed (in my case on /system) since the installation will fail when detecting it. At least I understood that we should test and report whether it worked or not. But I'm not an English speaker, I may have misinterpreted it
[SuperSU] SolarPlexus:
Just to confirm: for boxer it works as it should be ;)

Many thanks !

Gesendet von meinem A0001 mit Tapatalk
[SuperSU] genius88:
Guys, is it masking installed Xposed too?

via Tapatalka
[SuperSU] Ch3vr0n:
No, because if you read literally 2 posts above you it's not possible to install if you have xposed.
[SuperSU] genius88:
Sorry for my post. :-/ I thought there is an option to make them work both, but it wasn't tested.
[SuperSU] SimplyCity:
S8+, TWRP 3.1.1-2, Echoe Rom based on AQG5 / AEL kernel, no xposed, 2.82sr2 SBIN mode with suhide-lite v1. Fast as lightning, stable as mountain, green as passed SN and great as Chainfire® brand. No issues to report. Thank you very much. Amazing work!
[SuperSU] nkk71:
Great work :)
[SuperSU] rickysidhu_:
Gave this a try out of curiosity, and it seems like hiding root from apps such as Snapchat and Mario Run work great. However, I'm unable to pass SafetyNet.

I'm doing this simply out of curiosity and do not require SafetyNet to be passed, but I'm just playing around with this and seeing if I can make it work. I'm wondering if I did need it to pass, do I need to hide something other than Google Play Services in suhide? Also, should I be selecting the "hide root" option (red icon) or hidden from other apps (blue icon)?

I am using a Google Pixel XL, so I'm not sure if this may be the reason of SafetyNet failing (because of the A/B layout).
[SuperSU] KaMyKaSii:
Are you in stock rom? Because Safetynet has two steps, the CTS and the basic integrity check. Normally the first one only goes into stock roms (the custom roms devs modify the information in build.prop and so the device is not recognized as certified by Google) and the basic integrity check passes if you can hide root or any similar modification what you have done in the system
[SuperSU] rickysidhu_:
I am running PureNexus and I also noticed my Play Store shows uncertified. I'm guessing these are the culprits as to why it was failing. All good as I don't need it to pass, I was simply curious and decided to give it a try.

It's still great to be able to login to Snapchat without having to unroot first though! Thanks for the information, it was helpful :highfive:

Update:

A simple restart gave me certified on the Play Store and SafteyNet passed! However, suhide still has a green checkmark for Google Play services and yet it still passed

Update 2:

Left my phone for a few mins and when I went to scan my fingerprint, the reader was unresponsive. Same went for hardware buttons; had to force restart and now SafetyNet is back to failing (I still have certified in Play Store). I also noticed Play Services reverts back to a green checkmark every time I change it to hide root. Once I reenter the app, it's back to green. No big deal for me but it's definitely interesting to observe all that's going on with this lol
[SuperSU] donthateme702:
[MENTION=631273]Chainfire[/MENTION],i used the superuser.apk that was inside the zip to install the update,so i just would need to flash the Update -suhide.zip i twrp correct?
[SuperSU] TR2N:
Now it works as it should, thank you Chainfire!
[SuperSU] smallKING81:
I flashed all successfully but something is going wrong. HTC U11 DUALsim, ROM Viper 1.6.0 no Magisk, stock kernel.
[SuperSU] Chainfire:
Seriously, what kind of comment is that?

You messaged me a similar empty statement on IRC.

If you have something to say, say it...
[SuperSU] Chainfire:
You don't need to checkmark Google Play Services - in fact, you should not. SafetyNet is hidden from automatically.

The reason the checkmark doesn't show up right is a logic issue with UI. Multiple Google packages use the same UID, it only shows the checkmark changed for the first one. That'll be fixed next update.
[SuperSU] Chainfire:
SR2 needs to ZIP flashed in SBIN mode. As per the instructions.
[SuperSU] Ch3vr0n:
Sbin isn't active in a rom. It's supersu that detects the ROM version and decides on some checks what to do. For Oreo, the default su mode is sbin.

Sent from my Nexus 6P with Tapatalk
[SuperSU] Zehlek:
So I just flash the two zips then correct?
[SuperSU] Ch3vr0n:
instructions are in the first post
[SuperSU] Alxoom33:
Yes! Easy peasy.[emoji2]
[SuperSU] DodoGTA:
[MENTION=631273]Chainfire[/MENTION] Does it require the kernel to have setns support for the mount namespace?
[SuperSU] TheUndertaker21:
anyone tried this with samsung pay for gear 3

i found solution that if you delete busybx and hide it with magisk, you can bypass it

but on suhide, busybox didn't install

not sure what else Spay is looking for. maybe su? lol
[SuperSU] bdvince:
This suhide method does not work to hide Safetynet on Samsung devices, unfortunately.
[SuperSU] alx.enrqz:
I have the same problem. If I install the stable release i cannot install suhide. If I install the beta I can now install suhide but there is suhide binary error upon opening supersu
[SuperSU] Chainfire:
Works fine on my S6, S7 and S8...
[SuperSU] max414:
Doesnt work with s6e and nne 5.1
[SuperSU] Chainfire:
That's a custom ROM... if you figure out which properties it breaks, the fix should be easy.
[SuperSU] max414:
I am not sure if anything is broken here . It passes safety check and has root but apps still detect that device is jailbroken.

Yes i have turned on apps in su hide. Doesnt make a difference .

Is there a reference app to use?
[SuperSU] max414:
Safety net passed too
[SuperSU] jcmm11:
'RootBeer Sample' is a good app for testing root detection. Apps may be checking for the existence of SuperSU. Have you hidden SuperSU? (See 'about' in suhide).
[SuperSU] max414:
Any comments on this ???

I installed systemless binary ..and su hide
[SuperSU] jcmm11:
You have to hide supersu
[SuperSU] DodoGTA:
Can you also install RootBeer Sample, add it to the suhide list and give the screenshot of that app's result?
[SuperSU] max414:
Like this ?

I already have this
[SuperSU] jcmm11:
Now go and read the 'about' section in suhide. Specifically the section about hiding apps. Just click on the word 'About'
[SuperSU] SSH316:
Before adding the app to suhide

View attachment 4270562

After adding it(still detects root)

View attachment 4270563 View attachment 4270564
[SuperSU] max414:
After adding in su hide and volume up down combo to hide suhide and super su
[SuperSU] DodoGTA:
Are you sure that you installed SuperSU in BINDSBIN mode?
[SuperSU] jcmm11:
That's fine. The only thing it's picking up is busybox, and nothing hides that. Just remember that this app is a sample of things that can be looked for. And that the conclusion is "may be" not "is" rooted.

You should be fine with any real app
[SuperSU] SSH316:
Yes sir

Twrp terminal: echo "BINDSBIN=true">/data/.supersu

Even i did flash SuperSU Config and did select Systemless SBIN mode then reflash SuperSu 2.82 SR3 when safetynet failed for the first time
[SuperSU] SSH316:
I did unroot from SuperSu app and delete suhide and i can pass safetynet but rootbeer thinks that i'm might be rooted :confused:

View attachment 4270777 View attachment 4270778
[SuperSU] thearc77:
Hiding Rootbeer inside suhide, killing apps, hiding with comp key Rootbeer do not see root
[SuperSU] SSH316:
I did that and i couldn't hide root, don't know why my device failed
[SuperSU] DodoGTA:
[MENTION=631273]Chainfire[/MENTION] [MENTION=4470081]topjohnwu[/MENTION] It looks like that suhide-lite is (somehow) similar to Magisk Hide :(
[SuperSU] jcmm11:
Looks like you may have some build.prop mods it didn't like. I think that's what it's complaining about with the "dangerous props" test.
[SuperSU] SSH316:
Old kernel ? :(

It seems like i will be back with rootswitch

---------- Post added at 06:48 AM ---------- Previous post was at 06:42 AM ----------

Maybe
[SuperSU] sb1893:
For the the past few security releases and the Oreo upgrade, I've always followed the full procedure to reinstall SuperSu 2.82-SR3 and suhide.v1.08. However, I noticed on this latest upgrade to the Oreo Sept 2017 security updates, that suhide appears to still be installed after completing the upgrade. (This time I "unhid" SuperSu and suhide prior to flashing the full OTA). I did have to flash SuperSu from the modded TWRP to recover root. But once I did that it appears that suhide was still fully installed and functional. So I have not reflashed suhide at this point and all seems to be working fine in terms of hiding root. (Haven't attempted to pay with Android Pay yet, but SafetyNet Helper passes still.) So - I guess I am wondering what the recommended procedure is after taking version upgrades and/or the monthly security updates? Should we still flash both SuperSu and suhide or just flash SuperSu and expect suhide to not require a reflash/reinstall?

Thanks!

S
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] a simple question. After applying an update and re-rooting do we need to reflash su-hide? or should we be good to go?
[SuperSU] DIXES:
Sorry, I forgot to say, I'm using SuperSU 2.82-SR3.
[SuperSU] KaMyKaSii:
If you did not wipe data, I do not think so. After installing SuperSU again (and consequently patching boot.img), suhide will also activate at the next boot. But just to be sure, you can check the existence of the /data/adb/su/suhide folder and also the /data/adb/su/su.d/zz99suhide script
[SuperSU] pluviet:
When I flash suhide v.108 in TWRP I have ERROR 1. Why ?
[SuperSU] Ch3vr0n:
Who knows? Why don't you start by posting the FULL ERROR MESSAGE and/or twrp log. Not just saying 'error 1'. That alone means squat diddely doo.

Sent from my Nexus 6P with Tapatalk
[SuperSU] pluviet:
I followed this guide: https://xdaforums.com/apps/supersu/2017-08-13-supersu-config-t3655754 (all Auto-detect), but then I installed Su in Systemless SBIN and it's ok :)
[SuperSU] Ch3vr0n:
What's ok? Obviously since I'm running suhide I've already installed su in systemless sbin mode before the config zip was even available. That's not the question. The question is can I update from my current stock ROM 7.1.2 to 8.0.0 without needing to reflash suhide after rerooting (through flashfire)?

Sent from my Nexus 6P with Tapatalk
[SuperSU] jcmm11:
I agree with KaMyKaSii. If you don't wipe /data you should be fine. If you do wipe you'll definitely have to reinstall.

That said, going from 7.x to 8, personally I'd probably do a clean install - which would mean wiping data and reinstalling apps (including re-flashing suhide). Since Supersu defaults to sbin mode with Oreo at least I wouldn't have to worry about /data/.supersu
[SuperSU] Ch3vr0n:
Well I took the plunge. Updated to Oreo, rooted again with SR3. Everything just peachy and didn't reflash suhide zip

Sent from my Nexus 6P with Tapatalk
[SuperSU] BustedFly:
Hi.

How can I hide root in Apps? I try it with phone info pro but the apps says every try...phone status root : yes

Hope you can help me.
[SuperSU] DynamicDonkey:
No need to spam the same content, but it's very simple. Open up suhide (assuming you have it installed) then click on the check box next to the app you want to hide root from until it turns red. After that, click on the X in the top right corner. It will take a few minutes to do everything it needs to but that should do the trick!
[SuperSU] BustedFly:
Thx for your Help. Sorry for the tripple but it's a bug on the site or my phone.
[SuperSU] pavan3999:
help, showing su binary occupied when suhide lite v1.08 installed in sbin mode on my redmi 3s miui9 latest global beta rom. With out installing suhide supersu is working fine
[SuperSU] DynamicDonkey:
Is that an Oreo ROM?
[SuperSU] W@r10ck:
After updating to sept build of oreo and do the same steps that i did before my safteynet has failed on CTS Profile match. I can still open android pay though. Has anybody encountered this on Android O sept build? Thank you.
[SuperSU] jmiller3342:
yep. I can't get into snap chat or android pay. it's so annoying.... but the app says it works...
[SuperSU] DynamicDonkey:
Running September built perfectly fine.
[SuperSU] W@r10ck:
So what did you do to pass those steps? Do you have to flash unsupersu? Install supersu again then flash suhide update?
[SuperSU] DynamicDonkey:
I used FlashFire and downloaded the OTA zip from Google
[SuperSU] W@r10ck:
Unfortunately flashfire failed for me as im using a modified boot img for my nexus 6p so i had to update it through flashboot. Thanks.
[SuperSU] DynamicDonkey:
Yep. I'm on a Pixel so I guess it's different. Sorry I couldn't help you!
[SuperSU] pavan3999:
marshmallow rom
[SuperSU] Didgeridoohan:
This has popped up here and there and always for 6P users... Since it's only the CTS profile check that fails it does sound like Google messed something up for the certification of the september update.
[SuperSU] DynamicDonkey:
Make sure your using the proper version of SuperSU, 2.82 and it is installed in SBIN mode.
[SuperSU] pavan3999:
yes i'm using 2.82 sr3 in sbin mode
[SuperSU] DynamicDonkey:
When you get the error, did you tap on "How to solve"?
[SuperSU] TR2N:
Hi guys,

I have a problem. Somehow I have hided SuperSU app with the volume button combination in suhide. I am not able to start it from the Launcher because the app isn't listed anymore. Tried manually unroot and uninstalling SuperSU and suhide but nothing helps. Is there a way to make SuperSU showing up again?
[SuperSU] jcmm11:
Same combination as to hide it in the first place. Will hide both supersu and suhide. Vol up/down 3 times within 3 sec.

If suhide is visible and supersu isn't then the apk probably needs to be reinstalled. You can extract from the common folder in the zip.
[SuperSU] Shriac:
I am unable to pass safetynet. both CTS match and basic integrity show false. I used supersu SR3 and suhide. I can hide root but banking apps not working. I am on Galaxy S6 stock.
[SuperSU] osm0sis:
SBINBIND=true?
[SuperSU] Shriac:
Yes Root checker shows su path as /sbin so yes installed it correctly.
[SuperSU] osm0sis:
Still working great here on stock Oreo Nexus 5X.

Did something modify /system on your device? Perhaps it enforces the write-count check.
[SuperSU] Shriac:
I don't remember but it must be because of Build.prop edits done for Viper.
[SuperSU] W@r10ck:
I still can't figure out why i can't install busybox even after upgrading to .19 sept build.
[SuperSU] Shriac:
I factory reset the phone then installed TWRP recovery and then Supersu 2.82 sr4 using the config method. Then installed SuHide then hide the apps still not able to pass safetynet and integrity. Previous to installing Supersu it passed.
[SuperSU] osm0sis:
Use a smart busybox installer like mine?

Check my Odds and Ends thread.
[SuperSU] W@r10ck:
What do you mean smart busybox installer? Is that a different application?
[SuperSU] osm0sis:
Sigh. It's my zip. In my Odds and Ends thread.

I mean a busybox installer that knows where to install itself.
[SuperSU] W@r10ck:
Thanks it worked! :)
[SuperSU] ianmacd:
Out of interest, what's the run-time overhead of suhide-lite?

There was a definite performance hit with its predecessor, suhide, but since this is a stripped down version of that, I'm curious whether there is any noticeable overhead remaining.

Does anyone observe such an overhead with suhide-lite?
[SuperSU] galaxys:
Haven't noticed any overhead! It's very lite... :o
[SuperSU] ianmacd:
Thanks. I've installed it on my S8+ for a trial run.
[SuperSU] Bosko1976:
SuperSU v2.82 SR4 and Suhide-lite v1.08 perfectly work. Thanks Chainfire