yashsingh1/xdaforums huggingface dataset:
[SuperSU] jcmm11:
If you need this functionality in 5.0 then you should switch to Magisk.
[SuperSU] Justin Timberlake:
i bricked my LG V30 after using this method.

bootloop, cant go into download mode, recovery mode.

updated

came to TWRP and install Magisk Instead

sorry.
[SuperSU] saoudien07:
Hi, I am trying to install suHide via TWRP, and I get this error:

Invalid Zip file format !

I am running Oreo 8.0, so SBIN by default. I tryed reinstall SuperSu and it worked, and directly after suhide,but no luck, still getting error...

any help please...
[SuperSU] kevosky:
For those using oreo 8.0 or 8.1, can it work
[SuperSU] Ch3vr0n:
Of course it can, as it requires 6.0 or above. Works fine here on 8.1 July patch. Now if it WILL work for you, that's a different matter. Some devices tend do bootloop when flashed.

As such, backup backup backup.

Sent from my Nexus 6P with Tapatalk
[SuperSU] danilo_scala:
great work, thanks, pass in safety net but no login in pokemon go ...
[SuperSU] andrew2432:
What android version? Magisk is best now for that
[SuperSU] danilo_scala:
---------- Post added at 10:58 AM ---------- Previous post was at 10:58 AM ----------

[/COLOR]

android 7.1.1 xperia z5 premiun work magisk beta or stable ? thanks
[SuperSU] jcmm11:
Probably beta. There's a thread for Pokemon + Magisk https://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722 so you should probably post questions there for the best answers.
[SuperSU] c3k:
I'm not passing SafetyNet anymore with S8 exynos / Android 8.0 / last firmware (RGH).

Someone did on Android 8?

I think is time to switch to Magisk...
[SuperSU] jcmm11:
Depends what you're using to check safety net. API changed Aug 1. Try "SafetyNet Helper Sample" from the play store - I know that one's been updated.
[SuperSU] c3k:
Oh, thanks, I was using SafetyNet that give an errore, not a fail indeed.
[SuperSU] GuardianUSMC:
Interesting, I would have expected Root Checker to stay updated with the changes. What's even more bizarre is that on my device it shows Safety Net Passed, so could it be related to maybe newer devices somehow? I don't know just spit balling here.

Thanks for sharing, now if it fails we can try the alternative to see as well. Good to have a heads up.
[SuperSU] osm0sis:
If you join the Root Checker beta via Play Store the current beta build also supports the new SafetyNet checking API. :good:
[SuperSU] GuardianUSMC:
Oh, thank you, awesome heads up, appreciated. :highfive:
[SuperSU] saoudien07:
I am not able to pass safetynet. I am using the last Lineage 15.1 of 20.08.

I follow everything, the installation went without any errors very well, but when i try the app safetynet "attest" I get this error. Any support?
[SuperSU] andrew2432:
Haven't left 16.0 stable yet. Some issues on my google pixel xl running resurrection remix 6 but nothing worth worrying about.
[SuperSU] a7 zero:
:crying:
[SuperSU] saoudien07:
I followed all solutions of previous posts, however I do, supersu 2.82 version of 27.05.17, is always installing itself in /data.

On countrary last beta of 01.10.17, is doing the trick and install itself in /SBIN, from first try.

PS: I used the adb shell command and the Terminal, instead of SuperSU Config file.

Hope it may help others.
[SuperSU] Almighty1:
I tried following the instructions by using the adb shell echo command the first time and also trying flashing the AMORA SuperSUConfig.zip file followed by the SuperSU v2.82 SR5 zip file on a Samsung SM-N950U1 running Chimera v3.0 ROM that uses Safestrap which is TWRP v3.2.2 and already comes with SuperSU v2.82 SR5 on Android v7.1.1 and this is what happens when I try to flash suhidelite v1.09 zip file.

It will say Fatal error:

/system/xbin/su found

and then it says:

Is SuperSU v2.82 SR2 or newer installed?

it doesn't prompt but the script finishes afterwards. Is there anything I can do to get it working since I can't uninstall SuperSU directly as Safestrap depends on busybox which I assume depends on SuperSU.

I have already tried deleting the /system/xbin/su file, flashing the AMORA SuperSUConfig zip file, selecting SBIN mode and leaving everything else on auto-detect and the flashing the SuperSU v2.82 SR5 zip file , rebooting

and also tried the above without rebooting and in both instances, when I try to flash suhide's zip file, it gave the exact same error. Thanks in advance for any help!
[SuperSU] metalgold2301:
hi

in samsung models we rooted with rootedboot.img like chimera tool boot.img

do suhide working for this method root?

thanks
[SuperSU] sakib sakib:
Supersu
[SuperSU] Ch3vr0n:
No su-hide lite

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] xNonCombat:
Hi [MENTION=631273]Chainfire[/MENTION] thanks for this!

I hope it is possible to filter for Hidden/Hide from apps / nothing.

Also the ability to put some other apps in another tab (apps like I never ever want to hide root from or something, like gallery etc.)
[SuperSU] KaMyKaSii:
Dude, you're so late :eek:
[SuperSU] xNonCombat:
Did he quit development for it? I literally came across this yesterday lol.
[SuperSU] Ch3vr0n:
For it? No. For EVERY root requiring tool, yes. For the moment.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] Didgeridoohan:
He has been working on both LiveBoot and C.F.lumen lately, so not completely inactive...

Edit: But, yes, SuperSU is done for and there will be no more development for it.
[SuperSU] ldeveraux:
I think SuperSU has been updated since CF Lumen though;)
[SuperSU] KaMyKaSii:
No. The last SuperSU update was in 2017 and CF Lumen received a updated test version in December 2018
[SuperSU] :
Will it work on android 5.0.2?......Any chance?
[SuperSU] jcmm11:
Probably. Only way to know for sure is to try it.
[SuperSU] Ch3vr0n:
No it won't. It specifically requires 6.0 or above. Might help to read the OP requirements.
[SuperSU] chipola:
Lenovo k5 A6020

Hello Mr. Chainfire. I tried to install you excellente application, but not was success. The system keeps in bootloop with the new and the old version. Device lenovo k5plus A6020; O.S android pie 9; Arch: arm64-v8a, armeabi-v7a, security patches 2018-12-05
[SuperSU] Ch3vr0n:
Good luck with that. Chainfire had currently retired from developing on all his root requiring apps
[SuperSU] osm0sis:
More accurately he's retired from all his root providing apps. He's recently picking away at some updates to his root apps, starting with LiveBoot back in November, and recently updated again a week ago: https://chainfire.eu/

But yes, good luck getting help on suhide. ;)
[SuperSU] jcmm11:
In addition to what's already been said SuperSU (and therefore suhide) will definitely not work on Pie (AFAIK). I recommend you switch to Magisk.
[SuperSU] chipola:
Lenovo k5 A6020

Thank you
[SuperSU] harrymason37:
My device is Galaxy Note 5 N920c naugat 7.0 september 2018 update, TWRP 3.2.1, and its not working, I still can't use my mobile banking app :(
[SuperSU] Ch3vr0n:
And it won't be either, development for it has currently stopped.
[SuperSU] kinghh801:
Yup
[SuperSU] darryl_co:
[MENTION=631273]Chainfire[/MENTION] what do you mean by Xposed not supported? After installing suhide can I install xposed or suhide Will not be able to hide root from apps? Please explain
[SuperSU] jcmm11:
If you install Xposed you will not pass Safety Net, you will always be detected as rooted. suhide is, along with SuperSU, no longer developed or maintained. For active root development/hiding see Magisk. But you still won't be able to hide xposed.
[SuperSU] JhinCuatro:
Xposed is now able to pass safetynet on android pie. EdXposed and Riru Core bypass safetynet. But it's still not enough when it comes to snapchat apparently.

---------- Post added at 05:49 PM ---------- Previous post was at 05:40 PM ----------
[SuperSU] Chainwater:
is Supersu working on Android Q Beta?
[SuperSU] jcmm11:
I'd say the odds of that happening are somewhere between slim and none. And slim left town a few years ago heading for parts unknown.
[SuperSU] osm0sis:
lol
[SuperSU] GopalKaul:
Lol

Lol

Lol
[SuperSU] mo5lis:
I tested it on my note 3 with C9 pro rom 6.0.1

After flashing supersu to sbin mode, the root doesn't work

After flashing suhide, the suhide gui doesn't appear in app drawer and device seem that is not rooted

Reflashing supersu zip file in system mode and root worked again

Thanks
[SuperSU] billa:
After you flashed SUhide then reflashed SuperSU, did the hiding feature work?
[SuperSU] Ch3vr0n:
Wrong topic, suhide needs root, it doesn't root by itself. Oh and chainfire retired from all his root needing aps. This is no longer developed
[SuperSU] juampapo546:
Hello, is there SuperSU for Android 10 ?
[SuperSU] jcmm11:
No. Use Magisk.
[SuperSU] juampapo546:
It's what I usually use but I have a module making me loop and wanted to delete it from /data, my rom is encypted and twrp does not decrypt it
[SuperSU] Ch3vr0n:
Which isn't even remotely related to this topic (suhide-lite). You need to post on the magisk topic
[SuperSU] KaMyKaSii:
Run the adb command below on your computer, turn on your device and plug in the USB cable. As is off-topic, any additional help should be requested in the Magisk discussion thread.

adb wait-for-device shell magisk --remove-modules
[SuperSU] juampapo546:
Ok thanks, however I've formated data , if I have more questions I'll ask them on magisk thread
[SuperSU] Cursed Chico:
I first flash SuperSU Config and select Systemless SBIN mode then Reflash SuperSU v2.82 SR2 then Flash the suhide ZIP

in xiaomi mis5s plus. When i open supersufree, it immediately closes it. i cant also see suhide as an app.

I only want to use an app that needs to be shown as unrooted

edit

i again did flashing suhid zip. this time i wiped cache and rebooted. it waited at start, becasuse there was a progress bard. then i could login. There was different screensaver.

i cant see again suhudi icon. Now i cant open any app.. nothing is clickable :(

edit: after tryings, now i can click apps. UI changed but still cant see suhide icon
[SuperSU] DB126:
SuperSU (and by extension, suhide) is EOL and no longer supported. Best use Magisk if you are looking to hide root.
[SuperSU] Cursed Chico:
so, what should i do now? Supersu has option, "unroot and clean" . Should i do it? It will delete all suhide and other things?
[SuperSU] DB126:
Use that option to start. If it doesn't do the trick there are more aggressive methods.
[SuperSU] Cursed Chico:
It worked, thank you. But still , interface changed like backgorund .
[SuperSU] ibarco:
Google Pay

I searched this thread and i couldn't find any related post.

Google Pay keeps an detecting root although I selected it and all the google apps in the phone. Is there any way to make it work with SuperSu 2.82?
[SuperSU] DB126:
Obsolete; Magisk is the contemporary solution (YMMV)
[SuperSU] ibarco:
It's a pity. Magisk makes my phone reboot almost everyday while SuperSu makes it much more stable.

Thanks for the update anyway.
[SuperSU] alcestneige:
Hello, is this working in 2024 on android 14?
[SuperSU] latinohot:
Doubtfull
[SuperSU] Ingenium13:
Does this (1.05) work on a stock Pixel XL with SuperSU 2.82 SR2 flashed in SBIN mode. It doesn't seem to work for me, I get failed ctsProfileMatch and basicIntegrity. Do I need to flash a custom kernel along with it like ElementalX to hide the fact that I'm bootloader unlocked, as was the case with Magisk?

Also, the vol up / vol down toggle doesn't seem to do anything. Is it possible it didn't flash properly? TWRP seemed to indicate it was successful, and the app was installed.

For what it's worth, it seems all my apps have a UID greater than 10000, including system apps like Google Play Services.
[SuperSU] bggold:
Last night I was able to get both SuperSU 2.82 SR2 and SUHide v1 to work on my stock rom August update pixel xl. I was not able to pass safety net at first. I run the selinux toggler to toggle to permissive so that TWRP will detect version correctly. I change that back to Enforcing and that did the trick. I would rather have SUhide work over TWRP telling me what version is installed.

I am going to give v1.05 a try and will report if I have any issues.

I hope this helps others.
[SuperSU] tikizondo94:
Are you running selinux in enforcing or permissive mode?
[SuperSU] Alxoom33:
v. 1.0 worked without a hitch on my Pixel C running ODP4 8.00 with the SR2 version of Super SU.

Also worked well on my Nexus 6 running the latest 7.1.1 factory image.

Both passed the Safety Net check and Android Pay.

I flashed v. 1.05 on both devices without a hitch. However both fail the Safety Net check "Profile Match" and Android Pay.

Edit, my Nexus 6 started bootlooping. Manually opened TWRP recovery and reflashed v. 1.0 and it passes Safety Net.

Edit 2, a few minutes later the Pixel C had a random reeboot, reinstalled v. 1.0 and it passes Safety Net once again.

Not sure what is the issue with v. 1.05 and my devices.

P.S. is there a location for installing busybox. I have Sterickson busybox pro and have been unable to install in all the usual places[emoji14]

Thanks,
[SuperSU] logosA:
I am running enforcing kernel.

Always Note 2 was a strange phone to deal with. Neither the other hide method is able to pass safety net . but look after I fully unrooted ROM, it passes safety net with no problem. This is happening only with this ROM. Other custom ROMs can't pass safety net, even un rooted in our phone. As I said, we have a ''strange" device. Thank you and of course [MENTION=631273]Chainfire[/MENTION] for all the help. I love root, I don't need safety net, just wanted to help in this seeking. Maybe next time we ll be more lucky
[SuperSU] Ingenium13:
My phone locked up and now is just bootlooping. logcat just keeps repeating "08-10 14:47:29.233 1399 1404 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable."
[SuperSU] Ch3vr0n:
and what exactly is your phone model? Oh there's only just about a couple hundred different phone models. Chainfire doesn't have a crystal ball. Any possible logcat?
[SuperSU] Ingenium13:
My original post several posts earlier state the model, a Pixel XL. I'm on the August security path.
[SuperSU] Chainfire:
All of you, please try 1.06 (see first post for link).

There's an issue with 1.05's parallel startup that breaks things on some devices (but not all). Until I have time to figure that out, I've made the startup a bit slower, but it should fix the issue for probably two out of three.

As for busybox, there's currently nowhere to really put it. Do you only want to use it from root, or also non-root? I think from root may be attainable in SR3, non-root I don't think so. In the meantime you can try this: https://xdaforums.com/showpost.php?p=73328603&postcount=10767
[SuperSU] Zehlek:
How can I uninstall suhide? Not working so I need to use Magisk
[SuperSU] Chainfire:
Just 'Full Unroot' from SuperSU's settings. Then later remove the suhide GUI manually through Android's settings.
[SuperSU] KaMyKaSii:
Flash default boot.img of your rom and delete /data/adb/su
[SuperSU] logosA:
go to SuperSU app in Apps drawer and run fully un root

phone will restart and su will be removed, after that go to settings apps and

just uninstall SU hide as a common app.

chainfire never chained us up with his apps,

always has given the opportunity to users to go back to previous status without problem.
[SuperSU] Fenny:
Just FYI, I was experiencing lockups with titanium backup as a hidden app. Seems that pm hide hangs sometumes, and the phone locks up requiring a three finger salute to get it going again...

Pixel XL BTW.
[SuperSU] Alxoom33:
Thank you. The v 1.06 working on my Nexus 6 Android N 7.1.1. Passed Safety Net and so far no bootloops.
[SuperSU] Ingenium13:
I flashed 1.06 and it boots. However safetynet still fails. SafetyNet attest failed, ctsProfileMatch false, and basicIntegrity false. Does this work with the stock kernel on the Pixel XL?
[SuperSU] sb1893:
I installed suhide v1.0 yesterday and all seemed to be working great. Then today, I flashed suhide v1.06 via the recommended booted, modded TWRP on my Pixel XL. It appeared to flash successfully, but when I open suhide it immediately displays the message that it is unable to gain Root. When I open SuperSU - all looks well there and suhide is shown as an app granted root privs. I did remove suhide to see if it would be able to reacquire root, but no luck. Any ideas? I'm on Pixel XL running SuperSu 2.82 SR2 in SBIN mode and I'm on the August 2017 security patch.
[SuperSU] bggold:
Latest test build of sr2 and v1.06 stock rom August update pixel xl running fine. Even did adb entry for BusyBox and it installed.

Can't wait for flash fire update.

Good job Chainfire
[SuperSU] Chainfire:
I'm using it on the Pixel XL with Stock kernel on August update, adb debugging enabled. Fresh flash.

Remove it from SuperSU and reboot maybe?
[SuperSU] Ingenium13:
Hmmm, it just locked up again. Seems to happen every few hours. Logcat shows the following over and over:

slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.

I just flashed August earlier today. I'll try reflashing it and supersu
[SuperSU] Alxoom33:
Also working well on my Pixel C running Android 8.0 ODP4.

Will try to link to busybox (rooted only) as per guide in your link.

Thank you,
[SuperSU] jcmm11:
For busybox keep reading from the point he gave you. I have a few more relevant posts.

You can install busybox in /data/adb/su/xbin_bind (current location of Base directory) just note that if you're running a custom ROM that comes with a version of busybox pre-installed into /system/xbin it will effectively overwrite whatever you install.

Per Chainfire this is all temporary in any case. A long term solution needs to be found

I modified the installer for osm0sis' busybox and it installed successfully. You should find what I did if you keep reading the rest of the thread from the point referenced.
[SuperSU] Alxoom33:
Much appreciated. Do I need to run the adb commands even after I installed SU v. SR 2 in my Nexus 6 N 7.1.1 and Pixel C ODP4?

Thanks again !
[SuperSU] sb1893:
I tried that. No luck. I'm going to reflash suhide v1.0 for now.
[SuperSU] jcmm11:
You mean setting up /data/.supersu with BINDSBIN=true and BINDSYSTEMXBIN=true?

I assume you already did BINDSBIN=true, else you wouldn't be running in SBIN mode, at least on the Nexus 6. The Pixel C should have defaulted to SBIN mode. But the Pixel C will, if I understood things correctly, have another problem. It lacks /system/xbin. That means that BINDSYSTEMXBIN won't work in any case.

On the Nexus 6 yes you need to add BINDSYSTEMXBIN=true and then re-flash supersu, else xbin_bind won't be created.

The other option is to simply wait and see what Chainfire comes up with in the next revision. He mentioned he has a possible solution, but busybox will be restricted to root only.
[SuperSU] sb1893:
Finally got suhide1.06 to work. I ended up having to manually uninstall the suhide app within Android. Then I was able to reflash suhide v1.06 from TWRP and it then opened cleanly and requested root as expected. All seems to be well now. Thanks!
[SuperSU] dynospectrum:
Feels like X-Mas came early this year. Thank you so much for your work [MENTION=631273]Chainfire[/MENTION].

Cheers sir, donation sent.

59731164L7963911A
[SuperSU] sille:
somebody using this on the Galaxy S8? After typing in the SBIN command, flashing suhide and booting up it ends up in at samsung boot logo and stays there
[SuperSU] Neff_V:
[MENTION=631273]Chainfire[/MENTION] I flashed v1.06 but now my Nexus 5X is bootlooping. How can I uninstall suhide via TWRP?
[SuperSU] Chainfire:
Remove /data/adb/su/suhide folder in TWRP.

Can you try v1.00 ? UPDATE-suhide-v1.00-20170809130405.zip

Remove /data/adb/su/suhide folder.
[SuperSU] sille:
hey, with 1.00 it boots :)
[SuperSU] Chainfire:
[MENTION=5504004]sille[/MENTION] can you please try v1.07 ?
[SuperSU] sille:
thx a lot [MENTION=631273]Chainfire[/MENTION] , now it works like a charme!
[SuperSU] TheMysteriousOne:
Throwing this error with v1.07 and SuperSU v2.82 SR2 . OnePlus One. Android 6.0.1.

[IMG="error-screenshot"]https://dl2.pushbulletusercontent.com/eqqwgXrMuFFx3RTLk14r7LzH3xVy7mQ0/Screenshot_2017-08-11-06-55-55.png[/IMG]
[SuperSU] genius88:
If you have Xposed than look on the 1st post.

via Tapatalka
[SuperSU] KaMyKaSii:
As it is written, you have root installed on /system. You need SuperSU in SBIN mode to install the new suhide. Undo the root completely, flash the unSU zip made by osm0sis to completely remove any traces of previous root installationsand then follow the instructions in the OP
[SuperSU] TheMysteriousOne:
I also have CM. Any alternatives? Unable to use Snapchat.
[SuperSU] Razorbacktrack5535:
Bootloop on Xiaomi Redmi Note 4x with MIUI 9 Global 7.8.10 and suhide v1.07.

Homemenu FC with v1.00
[SuperSU] genius88:
Sorry. I'm too green to give you good answer. I also looking for good solution with Custom ROM and Xposed. Currently I know only one solution - Magisk topic. :-/

Edit: Eventually try No Device Check. It's Xposed module.

via Tapatalka
[SuperSU] Ch3vr0n:
first tried a terminal emulator and type "su" then the command. suhide complained. then did the twrp / adb way. flashed, Seems to work ^^
[SuperSU] oOflyeyesOo:
I seem to be having issues getting SU to install under SBIN. I have put the commands in termenal in TWRP, and doing it through command line on the pc. Both of course give no response, but every time I try to install suhide, it tells me that it was not installed under SBIN. I am running a N6 on DU, so that may be the problem. I am going to try more when I get home from work.
[SuperSU] Chainfire:
try removing /system/xbin/su manually...

SuperSU doesn't need it. CM's root does, but you don't need that if you're running SuperSU.
[SuperSU] genius88:
Is it possible to work with Android Kitkat? I mean sbin mode or manually move files to correct folders under TWRP? If not, I'll give a break.
[SuperSU] DodoGTA:
No, because KitKat doesn't support systemless root in the first place
[SuperSU] pavan3999:
it supports android 5.1 or not? can i use suhide-lite
[SuperSU] nguyentankiet:
Hi [MENTION=631273]Chainfire[/MENTION]

Thank for updated suhide.

I installed supersu 2.82 sr2 with sbin mode. It working, but i had problem: my device (S7 edge - Aug security patch) not detect sim card.

If i install supersu 2.82 sr2 with normal mode then no problem. Any idea?
[SuperSU] DodoGTA:
It may or may not support Android Lollipop, so just try it (also read the instructions in post #1)
[SuperSU] pavan3999:
working but i cant inatall suhide app, it saying parsing error from suhide zip
[SuperSU] DodoGTA:
[MENTION=631273]Chainfire[/MENTION] Please reduce suhide GUI app's minimum SDK version to 21
[SuperSU] pavan3999:
[MENTION=6429309]DodoGTA[/MENTION] bro thanks, suhide app working when i changed minimum sdk version to 21
[SuperSU] SvEgiiVEteR:
SR2-SuperSU-v2.82-SR2-20170808115921.zip

UPDATE-suhide-v1.00-20170809130405-v1.07-20170811001532

Xiaomi Redmi 4X MUIU 8.2.1.0 A6

detected root management app.is this normal?

i.imgur.com/XnzLrVg.jpg

i.imgur.com/yqaUfxk.jpg

for example, snapchat does not see root and SafetyNet Test ok

sberbank finds.
[SuperSU] liudongmiao:
[ redacted ]
[SuperSU] yusukesan:
I use ZUK Z2 with RR rom (7.1.2). Install suhide-lite v1.07, boot is stopped.

v1.00 is OK.
[SuperSU] jcmm11:
From the OP

So no you can't. Marshmallow or Nougat (or O). No KitKat, no Lollipop.
[SuperSU] Chainfire:
Reproduced. Trying to find the cause.

That's great, but why would you post the details? Android Security guys are reading this thread, and even if it is easy for them to find, if it takes them 5 minutes extra that is better.

No, the binder proxy will not be open source.
[SuperSU] Chainfire:
https://xdaforums.com/showpost.php?p=73373962&postcount=10855
[SuperSU] zenyatta80:
SuperSU in SBIN mode problems

I am having the same problem on my Pixel XL. SuperSU does not install in SBIN mode despite the ECHO command. I am unable to attached a screenshot but Rootchecker says SuperSU is installed /su/bin/su.

I am reflashing it from /tmp. Will that make a difference?

Many thanks for your help.