yashsingh1/xdaforums huggingface dataset:
[SuperSU] martyfried:
I've tried and failed to find info on this, so forgive me if it's some well-known issue...

I have a Nexus 5X with the latest PNP rom/kernel. I have SuperSU Pro v2.82

In the settings is a checkbox "Enable superuser". When I run the SuperSU app, I get an alert "SU Binary occupied".

But my real question is, what is this supposed to do. No matter what I've done with it, I never pass Safety net check; should it affect this? If not, what is its function?

I mainly just user SuperSU for backups before updating, and other occasional use. So, I'm trying to find a way to be able to use Android Pay, and enable root as easily as possible when needed, but I don't want something too complex.

FWIW, I was able to pass safety net with the same system minus SuperSU.
[SuperSU] ktmom:
I would flash osm0sis' unsu.zip (scroll down the 1st post to find it). That should take you back to an clean status. Then flash the last known working version.

This next I'm asking sincerely; why, when the device is 2 OS version releases behind, does everyone jump to the newest release trying to address issues in the newest developer release (O)?

---------- Post added at 14:04 ---------- Previous post was at 13:57 ----------

SuperSu is a root solution. There are others. Root, in this context, allows apps on your device to have access system wide. Rooting your device without taking other steps will always flag SafetyNet. There are other ways to trip it as well.

I humbly suggest that your questions indicate a lack of knowledge that is going to give you trouble in the long run.

Try reading (before jumping into installing) about Magisk and Magisk Manager and what all it might do to help you achieve your goals.
[SuperSU] Ibuprophen:
Just a suggestion...

Did you try using the following release from Chainfire?

UPDATE-SuperSU-v2.82-20170528234214.zip by Chainfire

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Benny100:
UPDATE-SuperSU-v2.82-20170528234214.zip Not Working Samsung S7 Edge Port 8 Rom
[SuperSU] shadow2797:
Thank you so much for the reply. Unfortunately, I believe I flashed it twice. Can you point me to a guide on how to flash system.img? I'm not sure where to find that. It's not in the firmware.zip. Should I just attempt unSU anyway?

Here's a sincere answer, I didn't check the changelog. My Android apps update automatically every night. So when I get an annoying notification that I NEED to update my binary, it seems like something that is a security fix, not something only meant for the newest smart phones. Granted a little research would have given me pause, and I'm kicking myself for not doing it. It's probably going to cost me. I also hoped it would fix an issue I had right before, which was my phone becoming a completely unresponsive black screen and needing a forced reboot. It was a wayward hope, but I thought the update would be relatively safe.
[SuperSU] ktmom:
I know nothing about your device :) Maybe this thread will help. I might try flashing the unsu.zip of the next step it to flash system anyway. I don't see how it can hurt, but, I know nothing about your device :)

Once you get going again, you might consider turning off auto update for supersu.
[SuperSU] martyfried:
Thanks, but I've been using Linux as my only desktop OS for many years, and have helped many people fix problems with their system, so I have a enough of an idea of what SuperSu does to keep out of trouble. There are some fine points of Android that I don't know, but I do know enough to keep out of trouble. Also, I dare say I probably know more than most of the people on this site, judging by what I've seen.

But one thing I don't know is exactly what the checkbox called "Enable superuser" does. Obviously, I can tell that it disables the ability to elevate to root privileges, but is that all? I guess for people who have a lot of apps that are automatically enabled, it would be convenient, but I don't have that problem.
[SuperSU] shadow2797:
Fortunately, unSU appears to have worked perfectly! Thank you so much for your help.
[SuperSU] jcmm11:
So I just tried unchecking that box. Then I fired up a terminal emulator.

su not found when trying to get root.

Opened up SuperSU again, got a pop-up about "su binary occupied" (which makes sense when you think about it). Ignored that, went back into settings, re-enabled superuser. su available again just as before.

I've never turned that off before, never needed to. I don't think it'll effect safety net, I suspect it's basically left over from early methods of temporarily hiding root (a precursor to root switch, if you will) which is now outdated.

It could also be used if multiple people have access to the phone so that nobody else can access root (turn this off and pin protect the app)
[SuperSU] ktmom:
You're right, it doesn't affect SafetyNet.
[SuperSU] Wolfcity:
I think the "enable superuser" option is the switch to enable the inbuilt superuser app of your ROM (not superSU, probably the lineage os root addon). So your device has root previlegues. If you flash superSU it says binary occupied what means nothing else than: There is another root app present on this device so I can't work as I should.

If you think about it the message makes sense even when the translation is a bit irritating.

So what you can do is:

a) Delete superSU​ by a full unroot inside the app and use your inbuilt superuser when you need it.

b) The same as above, than flash unsu.zip to delete the inbuilt root addon. After that flash superSU again (which shouldn't state binary occupied as there is no other root application anymore because of flashing unsu.zip) and use that as your root solution.
[SuperSU] ktmom:
In the supersu app settings, there is an option to enable / disable supersu.
[SuperSU] vaderyeh:
Hello I have a Samsung Galaxy S8 Plus carrier unlocked device (SM-G955UZKAXAA). I looked at the CF Auto Root device compatiblity list and see that SM-G955U is listed. Will this Odin flashible file be compatible for this variant device?
[SuperSU] ktmom:
If the device is listed, I think the primary criteria for Samsung devices is the bootloader is unlocked. There is a thread specifically for CF-Auto-Root.
[SuperSU] vaderyeh:
Thank you, I'll post that inquiry there.
[SuperSU] jashancheema:
Send me latest saftynet bypass version
[SuperSU] ktmom:
Doesn't exist
[SuperSU] pendor24:
magisk 12 .
[SuperSU] ktmom:
Coulda swore this was the supersu thread.
[SuperSU] andrew2432:
Yes but you dont flash this from odin, you do it from your custom recovery.

1. Download odin: flashing tool for Samsung (sounds like you did).

2. Look for twrp recovery for smg955u and download it...img file i think is the way to do it this way.

3. Put smg phone in download mode, Use Odin to flash twrp recovery...PDA mode or something like it, Google can help ya with those specifics.

4. Once you get twrp, boot into it and install/flash supersu 2.xx rx from the custom recovery.

I'm a few galaxies behind ya (pun?!?!) But the newer TWRPs are having some compatibility issues with random things. I may still be on a 2.8.? version

[MENTION=7177145]jashancheema[/MENTION]

You're gonna need to look around a bit more. TThere's are a few basic methods out there floating around. There are many factors that can/will determine your ability to pass sn checks. Device, ROM, security patch, xosed interest, and others.

By default magisk + magisk hide alone will do it.

SuperSU+rootswitch has a method. I thought I read the newer CF SuperSU passes naturally.

Throw some more info out and we can help more!
[SuperSU] pendor24:
Excuse me for the off topic

Yes, it's supersu

But nothing prevents informing gently a young member, who I am sure, once his information in pocket will find the way alone.

Good evening .

End of hss
[SuperSU] andrew2432:
EFF that the fight against Google is one sided enough without pretentious behaviour. Didn't realise I was on /xda/

Its time to work together. We are at a tipping point.
[SuperSU] Ibuprophen:
I another word (as [MENTION=631273]Chainfire[/MENTION] had previously commented) regarding Google's decisions on what can/can't be done on the Android...

"Though, whatever Google does that is/isn't ethical or immoral, Google will do what Google wants to do and there's nothing that can be done unless they get their way"

Now back to the regularly scheduled program (SuperSU)... :)

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] TioCareca:
Magisk manager support SuperSU, so no real off topic as some options can be used in Magisk with SuperSU...
[SuperSU] user99168561:
Device: Samsung Galaxy Tab A 8.0 (SM-T350)

ROM: HTKO STOCK+ 1.2 [5.0.2]

Xposed is installed

After using the in-app update or flashing SuperSU 2.80 or 2.82 the update appears to be successful but after rebooting the boot stage will only reach the animated Samsung logo and stay there indefinitely. Restoring a backup of the system partition allows the device to boot again. What can I do to get the SU binary updated?
[SuperSU] martyfender:
Have you tried the newest 2.82, only released on Chainfire's site? It has the latest, released fixes in it:

https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip

It is newer than the playstore version and the one released by CCMT.

[MENTION=4544860]osm0sis[/MENTION] unsu script might be of use also to remove any remanents:

https://xdaforums.com/showpost.php?p=63615067

Flash it in TWRP.

If anybody has any better advice, please post.
[SuperSU] user99168561:
I just tried it and it works, thanks.
[SuperSU] martyfender:
Good, I'm glad I could help. Were you able to fix it by flashing the new SuperSU zip, or did you also have to flash the unsu zip?
[SuperSU] user99168561:
I only needed to flash the SuperSU zip.
[SuperSU] Shtiff1:
How can I see the date code or the rest of the version that I am running? Currently only found where it says 2.82. Downloaded from the Play Store. XT1254, 6.0.1, stock rom.
[SuperSU] vaderyeh:
I appreciate your thoughts,

but alas TWRP is only available for the Exynos version. Mine is the Snapdragon version but a network, too all carriers unlocked variant. That is why I inquired about the CF Auto Root option. I went to that thread but no dice there either (yet). I also know that the bootloader needs to be unlocked which I haven't done that yet since I haven't received a clear reply about CF Auto Root yet for my variant.,

thank you again.
[SuperSU] Chainfire:
v2.82-SR1 has been released - https://xdaforums.com/showpost.php?p=72604085&postcount=10323
[SuperSU] mkaraniya:
How could i uninstall super su?
[SuperSU] mrrocketdog:
might try this : (all credits [MENTION=4544860]osm0sis[/MENTION] , of course) ;

http://xdaforums.com/showthread.php?p=63615067
[SuperSU] Wildcat2083:
I am aware all the pro package does is add features, the code actually resides in the supersu app not the pro package, at the time of my original post the test release of 8.28 was not out furthermore being i have a galaxy s7 snapdragon/Qualcomm version the root method is a bit different, chainfire stated updates usually won't work for me
[SuperSU] Ibuprophen:
That post was per [MENTION=631273]Chainfire[/MENTION] and any clarifications to it is between you and Chainfire.

Thanks.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] vdbhb59:
1. What does CCMT stand for mate?

2. If I use this 2.82 flashable for a clea installation, would I be able to root?

Danke

Vishal
[SuperSU] Didgeridoohan:
1 - Coding Code Mobile Technology. The company that owns SuperSU.

2 - The point of flashing that zip is to gain root... I'm not sure what you're actually asking. :confused:
[SuperSU] vdbhb59:
Apologies, if I confused.

I meant to ask, if I do a clean install and use 2.82, will it root? Or do I have to use 2.79 first and then 2.82?
[SuperSU] mauam:
Simply flash 2.82. It'll root.
[SuperSU] vdbhb59:
Cool.

One more thing. Do you use Magisk? CTA failed/mismatch issue!

Any workaround?
[SuperSU] jcmm11:
https://xdaforums.com/apps/magisk/advisory-safetynet-to-updated-t3621403
[SuperSU] vdbhb59:
Danke mate. Will try now.

Edit: Not working.. :(
[SuperSU] Didgeridoohan:
You're talking about passing SafetyNet in a SuperSU thread? Using Magisk?

Even when the current issues with the updated SafetyNet gets fixed, that's not gonna work. Magisk can't hide SuperSU.
[SuperSU] Mainaharen:
I have sony xperia E3 accidentally flashed the normal v2.82 (instead of the bootloo0 proof supersu)n i got camera common,Google play store,serviced forced stopped issues.Today i tried to reboot my phone n phone stuck at sony xperia logo n nothing happen .Suggest me how can i fix my sony xperia e3? Please help
[SuperSU] xonich:
Hello,

I tried to flash supersu 2.82 via TWRP on Moto G5 XT1676, but it does not install (it does not find ramdisk.img)

What can I do ?
[SuperSU] Ch3vr0n:
I'd start with the twrp recovery log from the flashing attempt
[SuperSU] Fatih15:
Hi admin, i have a problem in supersu permissions .. i allow "zygote64" to be able to root access, but i did not install it .. would it interfere with my smartphone? Or it is a virus / mallware! #thanks
[SuperSU] Ibuprophen:
I've seen the zygote access request before on another thread and I did a quick lookup for my own re-familiarization on it and i haven't seen anything negative regarding the zygote access.

Though, the zygote is a part of the Android system and typically inherits root access as part of the Android system, it's just an odd thing, for me, that it's requesting it in that manner.

Permitting Superuser access to the zygote should be granted as I've seen many individuals have issues if they deny it because it's a part of your system.

I do understand this but, am a bit challenged in explaining it via text so, if you need more information, it would be great if one of the "resident experts" could assist in this.

I'm not sure if [MENTION=631273]Chainfire[/MENTION] had any other feedback, questions, concerns, etc... regarding the zygote.

I wish you the best of luck!

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] mrrocketdog:
maybe this could help ,

https://android.stackexchange.com/questions/166211/why-are-zygote-and-whatsapp-asking-for-root

or this

https://www.google.com/amp/s/xdaforums.com/nexus-5x/help/zygote64-root-permission-t3480664/amp/
[SuperSU] jcmm11:
Both of those have guessed that it's malware, which it most definitely is NOT. [MENTION=631273]Chainfire[/MENTION] posted a response about this somewhere along the line, someplace. It's a minor bug of some kind since zygote (64) automatically has root access. I think he said it's a timing error of some kind, but I might be wrong about that.
[SuperSU] ktmom:
Zygote64 is a core process to Android. There is a threat out there (called Triada) that can infect the zygote process. That has nothing to do with root. I think if I saw it pop up requesting root permissions I'd investigate.
[SuperSU] KaMyKaSii:
Probably because you're using this mod...

https://xdaforums.com/xposed/modules/mod-whatsapp-extensions-add-extra-t3452784/post68477859
[SuperSU] Fatih15:
I never installed Whatsapp mod or whatever it is, because I do not know whatsapp mod what use !!!
[SuperSU] Fatih15:
zygote64, root access !!
[SuperSU] KaMyKaSii:
Weird. If you don't mind, you could show us your apps, maybe there's some suspicious app
[SuperSU] Fatih15:
What kind of app ?? Which is on xpose or what ??
[SuperSU] KaMyKaSii:
It would be best to show all the apps in your drawer
[SuperSU] Fatih15:
Like this sir ??
[SuperSU] ktmom:
Take a look here: https://xdaforums.com/xposed/xposed-modules-suppose-to-zygote-root-t3567105
[SuperSU] guliver365:
Since the upgrade to SuperSU v2.82 at each reboot I got all my applications being optimized, is there a way to stop this behavior?
[SuperSU] xdapao3:
For those who might be interested, now that I have found the time (and the willpower :p ) to properly troubleshoot it: SuperSU was innocent, there was an issue with AutoRemote. Set both my smartphone and my tablet to "skip BT" in the Advanced settings and the problem was solved.

A bit weird because I hadn't recently changed those settings and have always had unchecked though BT to BT has never worked (I kept it unchecked hoping that a future update would fix it since it would be very useful in a few scenarios :p ).
[SuperSU] exc3ssive29:
Hello I installed latest stable supersu through Twrp recovery mode, but I always get stuck in a boot loop. Twrp is the latest version. The rom is stock Sony android. Bootloader is unlocked and the device is Xperia z1. Any help please?I
[SuperSU] Ibuprophen:
Did you read through the following posts from [MENTION=631273]Chainfire[/MENTION]?

https://xdaforums.com/showpost.php?p=72489449&postcount=10187

https://xdaforums.com/showpost.php?p=72526044&postcount=1712

I wasn't sure if your up to speed with Chainfire's posts regarding the Xperia.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] ermal666:
I updated through play store on my Xperia Z3V, but stuck on bootloop after updating binaries.

Any suggestion?
[SuperSU] ktmom:
Look at the service release (SR) in the beta thread. Read that thread about your phone. There's been loads of activity the last couple of weeks.

If you need to reset things to get out of a bootloop, try flashing osm0sis' unsu.zip. That will unroot you.
[SuperSU] ermal666:
I messed things up. Now i dont have twrp anymore for some reason. Anyway I managed to revive another phone of my friend same xperia model. But after updating with latest supersu beta the icon of super su wont appear in launcher.
[SuperSU] ktmom:
It's usually visible in settings.

As a point of protocol, it's better to post about beta behavior in the beta thread. It's much less confusing to future readers of the stable thread.
[SuperSU] ermal666:
Thank You but it is not showing anywhere. I checked the settings but no luck.
[SuperSU] ktmom:
Then install the apk that is contained in the zip. All of this is discussed in the beta thread.
[SuperSU] corkiejp:
Install the supersu apk found in the common folder of the zip!
[SuperSU] ermal666:
I will. Thanks a lot! :)
[SuperSU] j1gga84:
Is there a script file (SuperSU.sh) that SuperSU will survive a ROM update?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[SuperSU] Ch3vr0n:
That's for your rom maker to implement. Not SuperSU
[SuperSU] kongacute:
Im try to flash SuperSU on my Galaxy S4 i9500 (exynos based), but it always show like this: TWRP 3.1.1

*********************

Boot image patcher

*********************

- Finding boot image

--- Boot image: /dev block/mmcblk0p18

- Extracting ramdisk

- Decompressing ramdisk

--- Failure, aborting

Im using RR v5.8.3 : https://xdaforums.com/galaxy-s4/i9500-develop/rom-resurrection-remix-n-t3591063

Kernel : https://xdaforums.com/galaxy-s4/i9500-orig-develop/kernel-smartpack-project-lineage-os-14-t3590858

And XTREMEMusic Mod v8.8.5.

Any solution for this???
[SuperSU] maybeme2:
I am not as knowledgeable as some of the other posters on this thread and need some advice with the current google play supersu update (2.82).

My phone is a rooted (twrp) nexus 5 running stock 5.1.1 and xposed. My current supersu is 2.79 and working fine. I accidentally "updated" my apps from Google play using the "update all" option. Big mistake! On every reboot after that android would optimize each installed app so that the reboot would take up to 30 minutes. After a lot of app uninstalling/installing and long reboots, I finally isolated the supersu update as the culprit.

I am now finally back with supersu 2.79 and a working system after restoring an old nandroid backup, losing recent data along the way.

My questions are:

1. How do I stop Google play from continuing to offer the troublesome supersu 2.82 update? Don't want to accidentally repeat what I went through.

2. Searching the web I believe the developers are aware of problems with 2.80 and 2.81, but are they aware of the optimization/long boot problem with 2.82? How will I know when it is solved, if at all? Or at least how I can remove the update offer from Google play?

Thank you in advance for any help.
[SuperSU] DB126:
Stick with v2.79 for now. Repeated dalvik cache rebuilds on Android 5.1 based ROMs is a known issue that has not been resolved in the latest 2.82 SR1 'test' build. Developers can not reliably reproduce the problem but acknowledge that it exists based on the volume of user reports.

To the best of my knowledge you can not stop the Play Store from offering the latest build.
[SuperSU] SilverDragon24:
Not flashing on x86

When I try to flash this on my x86 Asus T00F it fails to patch the boot image. Is there any way I can disable systemless mode?
[SuperSU] SimplyCity:
Please take a look here: https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] jcmm11:
Go to SuperSU in the Play Store. Click the 3 button menu in upper right hand corner. Uncheck autoupdate.

The update will still be offered, but not applied unless you manually approve it. This includes if you select "update all", you will be asked if you want to skip or include the update.
[SuperSU] DB126:
Described "update all" prompt for individual apps is inconsistent with the behavior on every device I that own (various ROMs and Play Store builds). Selecting Update All installs every app without further prompting. The only exception is when additional permissions are required on Android 5.x and below.
[SuperSU] maybeme2:
Thank you jcmm11 and Davey126.

You are correct Davey126. I don't have auto update selected and - Davey126 is correct (as always) - if you select update all, it will include the Supersu update without a popup because it does not require additional permissions. However, in the Google play version I have there appears an X to the right of each app update to exclude it. So it is possible to use "update all" for numerous updates and then click on the X to exclude SuperSu.

My real question is where I should look to see when this app optimization problem is solved so I can safely stop doing the above?

It was mentioned that the developers had trouble fixing this bug because it was inconsistent. Well, from painful repeated experience, it is very consistent on my phone and, since I now have an up-to-date nandroid backup, I would be happy to volunteer to the developers as a beta tester if that would help. But I don't know how to contact them. The website at the bottom of the google play supersu screen goes to a forum of users which has nothing to do with the developers. So does the listed email.
[SuperSU] DB126:
Yep - neglected to mention the ability to exclude individual app updates on a case-by-case basis. You will need to do this everytime as selections are non-durable.

Suggest monitoring SuperSU beta thread for the most recent updates.

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] jcmm11:
See attached images. What I described is what happens, for me.

Pure Nexus, 7.1.2, Nexus 5x

Phonesky_7.9.80.Q-all_0_PR_159305549-80798000
[SuperSU] DB126:
Appears you have auto-update globally enabled (first image) but have chosen to exclude individual apps on a case-by-case basis. Interesting config; I never permit auto-updates from the Play Store (or any source that I have control over) so never considered this arrangement. Shows how we can get set in our ways and overlook obvious alternatives. :)

[MENTION=6910712]maybeme2[/MENTION] - please consider this clarification from [MENTION=4487388]jcmm11[/MENTION] which may or may not meet your needs. Keep in mind the consequences of globally enabling/disabling auto-updates.