yashsingh1/xdaforums huggingface dataset:
[SuperSU] logosA:
yes you are right, I had hid root to almost all apps.

set them back to green, but still no luck.

Also now I cannt hide SU hide in apps drawer by pressing up and down volume 3 times.

I am going to set all to green, reboot in recovery, reflash SU , boot up once and then reboot and reflash SU hide to see if it helps

Any other idea?
[SuperSU] DIXES:
I very like suhide 0.55 because it is able to hide xposed (yes, it still works), but it needs very old system which security patch not over 2016-10. If it is possible, I hope newer suhide will hide xposed again in future version.

Thank you Chainfire!
[SuperSU] logosA:
sorry , no luck again.

Maybe in next update. Now I am again able to hide SU hide from apps drawer.

In su hide app , all are green only SU and su hide are invisible(or hiden)

but still no safety net pass
[SuperSU] genius88:
Same here. Is it possible at all?

via Tapatalka
[SuperSU] Chainfire:
I'm sorry but I don't know what is going on with your device, so I cannot fix it at this point.
[SuperSU] Chainfire:
Actually, I do have an idea, but it'll probably involve a custom rebuild of Xposed. Not sure yet.

Either way, I probably won't have any time to look at it before I return from vacation, will be end of September or the likes.
[SuperSU] Chainfire:
v1.05 released

v1.05 released, see the first page for the link and the changelog.

Just some minor updates.
[SuperSU] KaMyKaSii:
A systemless rebuild taking advantage of the new SBIN mode? I think everyone who loves Xposed wants this. But all in your time, enjoy the vacation and have fun
[SuperSU] DB126:
Nope. If you use Xposed (I do) your device is exposed. Simple as that.
[SuperSU] unhappybirthday:
Try using the SuperSU config method instead of directly editing the file. (The line in the OP directly under the one with the .supersu file edit info.)
[SuperSU] DullPeon:
deleted
[SuperSU] Alxoom33:
I agree, use SuperSu config app. But first read op and thread on how it works.
[SuperSU] Excelsior82:
Well, I eventually had it installed systemlessly, but I feel like you're saying I didn't read OP, which bothers me, since I did (and BTW I did tried both methods before posting), but whatever. All that matters is that it works now (although titanium backup does not see root now, which is a different story, and certainly not for this thread).

Thanks for your help anyway.
[SuperSU] Alxoom33:
Sorry, that wasn't my intention. I just wanted you to know that it is important to read up before flashing.[emoji16]
[SuperSU] will5:
I did the adb shell method and didnt encounter any problem. Not sure if that was the proper method.

I was having problems with magisk and some apps, but i needed some root hide. So I switch to this and seems to works fine on an lg v20. Btw, using 1.09 suhide lite.

Thanks!
[SuperSU] DullPeon:
I am running suhide (and supersu 2.82. sr5) on a samsung j730f/ds- also with twrp 3.1.1.1 as per the j730 thread with modified twrp. I used aroma su config to set sbin and enforce SELinux permissions. I have done clean installs from stock rom forward.

I have not been able to pass CTS Profile Match (the other safety net features pass fine). Is anyone with similar hardware having this issue, or has found a solution?

I have tried turning usb debugging off.
[SuperSU] Vivek Kantesaria:
Hello i am using samsung j700f with android 6.0 i tried suhide 1.09 but bootlooped. However no issues with v1.0
[SuperSU] EmiRus:
N5x stock 8.1 1.09 working fine

Still going with supersu & suhide still the best!
[SuperSU] EmiRus:
EDIT : Does this survive an stock update ?

(So after rerooting)

It should right since a user app
[SuperSU] mspasov:
It did, N5x, 8.1, February, su and su hide
[SuperSU] EmiRus:
Thanks man

Wait su did too ?

So u dont have to reflash it? since i always reflash it..
[SuperSU] mspasov:
Su didn't, sorry, I was describing my configuration :)
[SuperSU] EmiRus:
Ah ok thx man i was confused too..:)
[SuperSU] wetxxx:
If I have Oreo stock rom suhide still works? I try install this aps a 5-6 time with or without clean supersu and nothing. My aplication still shows me that I have root. I kill aplication and try 2 option hide from other aplication and hide root.

"Live long and prosper"

P. S. I found a solution. I try hidde suhide for taping vol + and - 3-th times. This features hide suhide and that it!
[SuperSU] viper_swipe:
Running 8.1 ROM , followed every step. Yet faced a fatal error. I first flashed su config and chose sdbin and then just pressed next and next then flashed, SuperSU and rebooted and then went back to recovery to flash su hide but got the error.
[SuperSU] EmiRus:
There's no need to su config on android O+
[SuperSU] viper_swipe:
So , what should I do now?
[SuperSU] RazorTyroz:
Have u ever been using xposed or something tripping cts.I heard that some phone will get trip if bootloader unlock(like mine note 4x nikel).
[SuperSU] DullPeon:
only twrp, aroma, su 2.82 sr5, and suhide. thanks - it may well be the unlocked bootloader.
[SuperSU] twistedominoes:
Can i flash suhide with flash fire and locked bootloader?
[SuperSU] Ch3vr0n:
Probably, but if you bootloop there will because very little to nothing you can do is there's an unlock method available
[SuperSU] twistedominoes:
Does suhide need unlocked bootloader?
[SuperSU] Ch3vr0n:
By itself no, but certain devices have bootlooped after flashing it, and without an unlocked bootloader there's little you can do to recover from such a thing other than flashing a factory ROM.
[SuperSU] twistedominoes:
Well i just tried to flash it with flashfire but i dont see a suhide icon
[SuperSU] jcmm11:
What's the FlashFire log say? (Look in the FlashFire directory of your internal storage)
[SuperSU] twistedominoes:
It says i need systemless supersu. Is there any way to make supersu 2.82 sr5 systemless?
[SuperSU] Ch3vr0n:
No, because it already is. HOW it installs depends on a multitude of factors. As said, let's start by you providing a logfile of some sort, you can start with the one from flashfire

Sent from my Nexus 6P with Tapatalk
[SuperSU] twistedominoes:
It says fatal error /system/xbin/su found
[SuperSU] jcmm11:
Let's start with the basics

What device?

What ROM?

What version of Android is the ROM based on (if not stock)?

Attach the entire FlashFire log, or post it to pastebin.com and post the link here. If you're not allowed to post links yet then just break it up so it doesn't look like a link. Post enough so we can figure out the missing parts (leave of http and www etc, just tell us what's missing)

Do you have a file /data/su.img ?
[SuperSU] twistedominoes:
i think it won't work because it's a snapdragon galaxy s8
[SuperSU] nguyentankiet:
You need install supersu with sbin mode
[SuperSU] jcmm11:
That's my guess, but he refuses to provide what we need to confirm
[SuperSU] Ch3vr0n:
You think wrong. The actual problem was already visible in the image in your very first post. You're not rooted in sbin mode but in SYSTEM mode in /xbin. Suhide REQUIRED system's

Systemless SBIN mode (/data/su/sbin). You need to fully unroot first (perhaps use [MENTION=1143630]osmosis[/MENTION]'s unSU script). Then flash the su config for and select 'sbin' mode. Then flash supersu and then suhide.

Sent from my Nexus 6P with Tapatalk
[SuperSU] MarkAndroid:
Hello,

with SUHIDE snapchat work?
[SuperSU] Ch3vr0n:
Did you try it?
[SuperSU] candiesdoodle:
Yes
[SuperSU] twistedominoes:
how do I flash in sbin mode?
[SuperSU] Ch3vr0n:
Read that post again, I already told you what you need to do.

Sent from my Nexus 6P with Tapatalk
[SuperSU] twistedominoes:
sorry but i dont understand
[SuperSU] Ch3vr0n:
Then you didn't read.

1 You need to fully unroot first (perhaps use [MENTION=1143630]osmosis[/MENTION]'s unSU script).

2 Then flash the su config file and select 'sbin' mode. (You can find out in the sticky up top)

3 Then flash supersu and then suhide.

Sent from my Nexus 6P with Tapatalk
[SuperSU] twistedominoes:
I did ****in read i didnt understand dont assume **** about people
[SuperSU] Ch3vr0n:
Well I can make it a lot more complicated if you don't understand 3 simple steps. Maybe you'll understand the complicated guide?

Sent from my Nexus 7 with Tapatalk
[SuperSU] twistedominoes:
Just because something is simple to u doesnt mean its simple to someone else MOD Edit
[SuperSU] Ch3vr0n:
. I can flash things but when it comes down to for example debug problems, write Android code,

It can't get much simpler sorry. It really isn't complicated

As I said, you need to UNROOT first. Either from within SuperSu itself or by using the unSU script from osmosis. Then you first the SuperSu config zip file from the sticky, and configure it for systemless sbin mode. Then you flash SuperSu and then suhide zip.

If you still don't understand that, then suhide is out of your league and you'll have to use a different solution.

Sent from my Nexus 7 with Tapatalk
[SuperSU] twistedominoes:
i didnt realize the download was right in front of me. So i feel like an idiot and a complete ass. im sorry
[SuperSU] Ch3vr0n:
No worries, apology accepted. That said, Then your options are very slim to non-existent. You could try to see if you can ADB BOOT twrp instead of flashing it.

If that works, you can then place the needed zip files and try that way. But before you do anything, the standard policy applies. BACKUP BACKUP BACKUP, and make sure you know how to flash a stock rom in case you'd need to.

Sent from my Nexus 7 with Tapatalk
[SuperSU] jcmm11:
Ok, I don't do Samsung so you'll have to tell me:

How do you root?

Can you get an adb shell?

Can you push a file to /data ?
[SuperSU] GopalKaul:
You everytime forget, he is [MENTION=4544860]osm0sis[/MENTION] not [MENTION=1143630]osmosis[/MENTION] haha
[SuperSU] SacredDeviL666:
Just edited few posts from last couple of page.

Apart from that you all are good and a happy thread it is :good:

Keep it up :highfive:

Thanks

SacredDeviL666

Forum Moderator
[SuperSU] MarkAndroid:
____________________________________________

- Boot into TWRP

--- adb shell: echo "BINDSBIN=true">/data/.supersu

____________________________________________

I entered TWRP 3.1.1 but the ADBShell command only allows me to clear the cache and if I try to press on the swipe to start the ADB nothing happens and I can only "cancel" the operation.

Besides the TWRP do I have to install some other components to start the ADB?

Is there an ADB command from a PC?
[SuperSU] jcmm11:
If you're in TWRP just start the terminal from "Advanced". Leave out the adb shell part and just start with echo. After using the echo command I recommend you do a cat to verify the contents

cat /data/.supersu
[SuperSU] MarkAndroid:
When I run ADB from TWRP/advanced nothing happens, I do not have the command line to insert the data.

The keyboard does not appear either.

TWRP is put on hold and can only press "cancel".
[SuperSU] jcmm11:
I don't know where you're running that from. You only need to run adb from PC. If already in TWRP from initial TWRP screen click Advanced tab (bottom tab on left hand side).

Next click on Terminal tab (second from bottom, left hand side).

If you're running 3.1.1 you should definitely have a terminal available.
[SuperSU] MarkAndroid:
Perfect! I was pushing on ADB Sideload instead of terminal!

Now, having already installed SU normally in the default position, do I first have to complete UNROOT using APP SuperSU and then proceed to ROOT again?

Xposed still does not work if I install SUHIDE?

There is no way to get it, I use some form!
[SuperSU] Ch3vr0n:
Suhide REQUIRES /su/sbin mode. It's specifically stated in the OP. Anything else won't work and the installer zip will refuse to flash if it detects the su image anywhere else. And no, suhide doesn't work with Xposed. (Or is it the opposite, dno I don't use Xposed)

Sent from my Nexus 6P with Tapatalk
[SuperSU] theArhar:
cant install, nor using echo, nor using aroma config

it says SuperSU must be installed in BINDSBIN mode

BUT IT IS!
[SuperSU] Didgeridoohan:
Uninstall SuperSU completely.

Run the echo command or use SuperSU Config to activate SBIN mode.

Install SuperSU v2.82 SR5.

Install suhide.

If you do it that way and it still fails, I've no idea...
[SuperSU] theArhar:
I am doing it today after clean flash of new version of android through odin
[SuperSU] jcmm11:
Yes you'll have to unroot first. I normally use osm0sis' unSU zip. Don't forget to restore unpatched boot image (there's a zipped copy in /data but you'll have to get it before running unSU)

As stated in OP, suhide is not compatible with Xposed.
[SuperSU] twistedominoes:
so when i try to flash supersu after i flash the config file supersu gives my phone a start up failed i used flashfire
[SuperSU] Ch3vr0n:
Then you're or of options. Likely due to your locked bootloader.

Sent from my Nexus 6P with Tapatalk
[SuperSU] will5:
I got the same problem using by mistake supersu 2.82 instead of 2.82 sr2 or higher.
[SuperSU] twistedominoes:
i was looking through my phone files and i found this in the default.prop: ro.oem_unlock_supported=1. Does this mean i can unlock my bootloader?
[SuperSU] Ch3vr0n:
It looks like it. But that's a discussion beyond the scope of this topic. You'll best ask that in your device section.

Sent from my Nexus 6P with Tapatalk
[SuperSU] Lukalion:
I think this is only the frp/oem lockbut not the bootloader but you have to have your frp/oem and bootloader unlocked. But i suppose you can try.
[SuperSU] KokkoM:
Working fine on Oukitel k10000 pro and Shield android tv with full android :)
[SuperSU] DullPeon:
trying to get this to work on either an A520F (preferably) or a J730G/DS. I am running into the lock screen unlock lag on pattern/code entry.

have tried not using no-verity-no-encrypt bootpatch, and that works fine with version of SU prior to 2.82SR2 - but cannot use SUhide with any such version prior to sr2 2.82 for systemless sbin install.

when try the same routine (flash firmware, flash twrp, go to twrp, wipe data/cache/dalvik, then aromasu to config, then the 2.82 sr5 su) with a su-hide compatible SU version, I get the lockscreen lag again.

My choices seem to be no suhide and no lockscreen lag, or suhide with the lag. Obviously I am looking for a way to get suhide and no lag.

has anyone had any success getting suhide running without the associated lockscreen lag on otherwise unmodified firmware?

conceptually, can anyone suggest why I am getting the lockscreen lag only on the 2.82 systemless su installs, rather than 2.79 etc?
[SuperSU] ciberglo:
Hi. After installing suhide, I noticed high battery drain. Using "busybox top" command, I found that zz99suhide opened a sed process

sed s/test-keys/release-keys/g

And this sed operation was taking forever, and was triggered every time after rebooting.

Is this sed operation supposed to really take so long? I mean, more than 4 hours ?
[SuperSU] sireniankyle:
followed steps, but it doesn't seem to work on S9+. Hopefully a workaround is coming.
[SuperSU] ankitj1611:
not possible in lollipop?
[SuperSU] Ch3vr0n:
Why don't you read the first post again, it states specifically the minimum os.

Sent from my Nexus 6P with Tapatalk
[SuperSU] fuado12:
I can't gate update
[SuperSU] princepb:
Rooted
[SuperSU] Ch3vr0n:
Yes, trees have roots. and so does your device need to be to use suhide. You're point is?
[SuperSU] Ch3vr0n:
I wonder how this https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/ is going to affect us next month when we flash the OTA for example on a nexus 6P like mine. I need root for various apps (like call recording, add blocking). I hope suhide will continue to function until chainfire comes back, cause i don't know what i'd do if it stopped working and my device becomes "uncertified". Let alone not being able to block adds or call recording, not even being able to use the play store would be a massive downside.

This is just F-ed up
[SuperSU] jcmm11:
2 points

1) if push comes to shove you can switch to Magisk.

2) if you actually read the article you'll see that there's an out for custom ROMs (hence the whitelist portion of the headline)
[SuperSU] Ch3vr0n:
And loose flashfire in the process? No thanks, if I don't need to. But that would mean codingcode that took over SuperSU might need to finally get there act together.

Whitelisting I know, but meh, every damn time you flash a ROM? Damn Google.

Sent from my Nexus 6P with Tapatalk
[SuperSU] KokkoM:
You mean flashfire apk? it work with Magisk too.

Sone devices need switch magisk to core mode, but work anyway.
[SuperSU] osm0sis:
They needed to get their act together for 8.1 on the Pixel devices and didn't. I think the only thing we can hope for at this point is Chainfire coming back and fixing FlashFire to work with Magisk again.
[SuperSU] DB126:
Err...why? What's in it for Codingcode? Acquiring SuperSU gave them leverage should it prove financially advantageous. Apparently that hasn't happened and likely won't. What commercial entity wants to behind a tool that compromises security in today's environment?
[SuperSU] osm0sis:
If I recall Chainfire's posts on them correctly, they own a number of well-known root apps, so them purchasing SuperSU was basically vertical integration. You'd think that'd mean it'd be a priority for them to keep it working, but so far we've seen otherwise.. :rolleyes:
[SuperSU] jcsww:
Although I am curious as well. Does it really matter? Look at the crap Facebook has been mining, including phone calls and texts, and yet it has barely suffered a dent in its user base. As much as I am against having my data mined, SuperSU still provides the best root user experience and compatibility out there. We as users, all have a choice in whether or not to use it.
[SuperSU] DB126:
Agreed. Question becomes (for those who care) whether a commercial entity will stand behind a 'product' that will be immediately mischaracterized to suit the biases of those doing the talking. Just look at the ridiculous shenanigans surrounding the latest FB revelations. Truth lies in the eyes of the beholder. A sad statement of today's reality.

Now, if such an offering could be spun as a way to counter nefarious behavior there may be a viable market for the misinformed. Personally don't see it - but also hope I'm wrong.
[SuperSU] jcmm11:
They may well keep it working for their own apps. Doesn't mean they need to open it up to external users. This would be true even if Chainfire had open sourced it. Once they bought it there would be no requirement for them to publish any further changes even if they were updating it internally.
[SuperSU] Ch3vr0n:
Not on oreo it doesnt with magisk above 14.2. While flashfire may work with magisk, suhide doesn't (yet) wich is needed to keep devices "certified". Damn google lockdown

True that, and i'd rather see sooner than later
[SuperSU] osm0sis:
MagiskHide is probably more effective than suhide-lite at this point, but we digress. ;)
[SuperSU] xell75:
No need for Magisk for me, I still use SuperSU on my China Blackview P2 and I use an Xposed Module called "No Device Check" and that makes the PlayStore show my Device as "Certified"
[SuperSU] Crom4rtie:
do you pass the basic integrity test in the safetynet attest app from the playstore ? i don't
[SuperSU] Didgeridoohan:
You can't pass basic integrity with Xposed installed. You can however pass the CTS profile test, which is what the Play Store certification checks.
[SuperSU] Throught:
This version run with Magisk v.16 in Motorola devices (Moto G S5 Plus exactly)?
[SuperSU] jcmm11:
If you're running Magisk you don't need this. You already have Magisk-hide

Plus it won't work
[SuperSU] thiagoserrao:
I'm installing the SR5-SuperSU-V2.82, but when i try to install suhie 1.09, i got error

"Updater process ended with ERROR: 1

Error installing zip file '/sdcard/Download/UPDATE-suhide-v1.00-20170809130405.zip'

Do i need do somehting before install suhide?
[SuperSU] Ch3vr0n:
No, you need to post the rest of the error message during flashing. Not just 1 line of the log.

Sent from my Nexus 6P with Tapatalk
[SuperSU] c3k:
Just installed, selected all Samsung apps in suhide, but Samsung Pay still detect the modified system.

Any way? Must leave supersu to try Samsung pay?
[SuperSU] jcmm11:
Did you hide suhide? See the about tab for more info
[SuperSU] jonnie77:
in n910f with port rom racerom and ael kernel when i am doing all the steps correctly i boot but neither the suhide apk is installed nor i have root access.any opinion?
[SuperSU] c3k:
yes, I did.

I'm reading that once the samsung knox is tripped, samsung pay will not work :rolleyes:
[SuperSU] Ykp99:
Boot into TWRP

--- adb shell: echo "BINDSBIN=true">/data/.supersu

where to write this code
[SuperSU] osm0sis:
Google "adb shell"
[SuperSU] jcmm11:
If you boot into TWRP then enter the terminal (under Advanced). Just start with "echo".
[SuperSU] tuxicMi:
Need help with supersu config

When i flash the supersu config for sbin it says that i need to do it manually what do i do?:confused:
[SuperSU] oneplusfive:
Getting bootloop after successful install on Note 8 SM-N9500 snapdragon model. SuperSU came installed with current rom.

Had to restore recovery with TWRP backup.

This is how I installed it. Flashed SuperSUconfig in TWRP first, then went back and flashed SuperSUrc5 and rebooted.
[SuperSU] mmshasan:
Perfectly done on Redmi Note 3 PRO MIUI9 8.5 Global Beta Marshmallow. Thanks for your hard work.
[SuperSU] funky0308:
No it won't, Samsung Pay won't work and there's probably chance it will never work on custom ROMs or rooted devices (at least not on devices that was rooted the way we are doing on Oreo).

My bank updated their banking app (before it worked no matter what you do) and now it doesn't work even I'm trying to hide root. (It's probably because I'm on stock based but custom ROM and device is rooted, of course).

I rooted my device to install Xposed but when I did all that I realised Samsung is doing a great job and besides few Xposed modules I don't need anything I was using before.

Firmwares are getting better and better just like Android (vanila from Google has tons of features we could only dream of few years ago) so I quite sure we won't need Xposed very soon, maybe even on Android P .
[SuperSU] andrew2432:
That's bold lol
[SuperSU] ankurds11:
Problems regarding installation of suhide in Moto G4 Play

Moto G4 PLay

7.1.1

rooted

used aroma installer to install superSU in systemless SBIN mode

manually typed the command using TWRP terminal

manually modified the .supersu file residing in /data directory

After that reflashed supeuSU

still not working!!!!!!!

while flashing suhide..showing

"SuperSU image found at /data/su.img SuperSu must be installed in BINDSBIN mode

..........ERROR: 1

...................."

:confused::confused::confused:
[SuperSU] Ch3vr0n:
Your last few lines say exactly what the problem is

Sent from my Nexus 6P with Tapatalk
[SuperSU] jcmm11:
Assuming you correctly modified .supersu do not reflash supersu, uninstall and reinstall (make sure .supersu still exists after uninstalling)
[SuperSU] andrew2432:
Sounds like you forgot the adb commands!
[SuperSU] ankurds11:
Though I tried in every possible way previously, it did not work for superSU v2.82 SR2. But it finally worked for superSU v2.82 SR5. It got installed in SBIN mode (systemlessly) . suhide is installed.

Problem is solved!!

Thanks everyone for your concern!!:D
[SuperSU] GuardianUSMC:
echo "BINDSBIN=true">>/data/.supersu
[SuperSU] ankurds11:
First you make sure that you have uninstalled the superSU completely ( if it was installed previously).

In my case I have tried in every possible way, like running the adb command from twrp terminal, modifying the .supersu file manually after finding it from the data folder of root directory . But it did not work. So I uninstalled the SR2 version of supersu completely and freshly installed SR5 . Now the given command worked successfully. If you check the root/data directory you won't find supersu.img anymore... instead supersu files can be found on sbin directory. That's all. Now you can flash suhide.
[SuperSU] drtweak:
Worked for me as well! SR2 didn't work. Downloaded and used SR5 and it worked.

Moto G5S Plus 7.1.1 June 1st 2018 Update
[SuperSU] TRGameAirs:
android 5.0 ?
[SuperSU] cnjax:
Try reading the OP