yashsingh1/xdaforums huggingface dataset:
[SuperSU] maybeme2:
I never permit auto updates. On principle. I want to know what is happening on my phone. ?
[SuperSU] amit1748:
Hi Guys

I'm currently on rooted 5.1.1 stock ROM on Xperia Z1 with SuperSu v2.79 and my app got updated recently asking for binary update. Which in turn results in a bootloop, already tried twice and just got my ROM back up again just the way I like. Unfortunately the app has updated again and asking for binary update, which I don't want to. Is there a way to downgrade the app? So I don't face a bootloop again. ?
[SuperSU] jcmm11:
So do I (want to know). Note that I only allow auto-updates over WiFi. In 90% of the cases I manually trigger the updates. In the cases were it auto-updates first I get notifications so I can revert if I really want to (but those would have been set for manual approval in any case)

If you have something like afwall+ installed you can block access to WiFi for the play store and eliminate any auto-updates, even if they're enabled. (This option obviously depends on your data plan).

---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------

Just flash the zip from Chainfire's site.
[SuperSU] amit1748:
Thanks that worked, but now I don't have the app at all and can't get root access for any new application. The old root applications work fine. :/
[SuperSU] ktmom:
That sounds like you are unrooted. Specifically what did you flash (from Chainfire's website), and what does the recovery log from that flashing say?
[SuperSU] amit1748:
I already had SuperSU v2.79 zip, that's what I flashed again. And the log did not show any errors. So I don't know what happened. :)
[SuperSU] DB126:
Extract the SuperSU apk from the 2.79 zip and install that. This will only work if device remains rooted.

---------- Post added at 02:58 PM ---------- Previous post was at 02:55 PM ----------

Read the series of posts just prior to your Q for detail on preventing future automatic SuperSU updates via Play Store settings. A couple different approaches to consider; both easy to implement (tick the box; profit).
[SuperSU] HotBoyLayne1985:
I have an boost mobile LG Tribute HD and i was wondering whats the best and right way to do it with out a computer. Thanks
[SuperSU] ferranvilaro:
Working against Kings**t

2.82 working on my AGM X1 18k

Installed from TRWP

First uninstalling and killing Kingr**t

Thanks a lot ?
[SuperSU] amit1748:
Thanks a lot that did the trick. I've disabled all updates for now. I'll read the previous posts regarding disabling future updates of the SuperSu app. Thanks again :)
[SuperSU] rizla2:
Latest version is still broken and causes bootloop on Xperia, why is this on Play Store?
[SuperSU] DB126:
While v2.80-2.82 certainly have issues (especially on Android 4.4.x/5.x) the overwhelming majority of updates go smoothly. That said, not sure what the push is to promote the 2.8x branch. Seems devs should rollback to 2.79 core until remaining issues are ironed out.
[SuperSU] zohaib0001:
[MENTION=7678190]SuperSU Release[/MENTION]
[MENTION=631273]Chainfire[/MENTION]

I have sony xperia XZ device running stock 7.1.1

i report before that on v2.82 update init.d is not working in xperia, i also try the v2.82 zip that is made for sony devices but result is same init.d not working.

but its working fine in 2.79 release.

Please fix this issue in next update. Please
[SuperSU] Dylan Hameleers:
why can I not install to /system? great app.. keep it up 6/5 stars :)
[SuperSU] ktmom:
system mode version
[SuperSU] Sachin ET:
Can anyone help me with the download link of latest stable release.

Thanks
[SuperSU] ulxerker:
Here you go: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
[SuperSU] Sachin ET:
Thankyou :) :good:
[SuperSU] A.D.I.O.S:
latest version in playstore still forces bootloops on xperia devices..

why is it still online? at least put a “WARNING!!“ in the description!

not everyone checks this forum before updating..
[SuperSU] Paschfire:
Well if you're blind flashing without read up on changes or know issues etc..(as you basically stated above) sorry to say it but that is your own fault, it's no one else's.
[SuperSU] tobbbie:
No bootloop for me - I have Z3 compact running stock MM and SuperSU Pro 2.82 from Play Store.
[SuperSU] A.D.I.O.S:
it's not flashing when i update via playstore and it's not blind, if i read the update description, but it doesn't state anything like that.

so how is this my fault?

it's not a big problem for me, because i have a backup, but all versions since 2.8 gave me bootloops.

also i have to exclude supersu everytime i update my other apps.

so no matter who's fault it is, there has to be a warning! doesn't hurt and would save a lot of trouble for many people, right?
[SuperSU] DB126:
A bit of homework prior to installing/updating any root related app is assumed, especially one as powerful as SuperSU (root manager). Hand-holding and root are generally not synonymous.
[SuperSU] A.D.I.O.S:
agree, but still i think it's a no go to leave a faulty (for most xperia devices) version for months in the playstore and don't mention it anywhere..

that's not very user friendly...
[SuperSU] DB126:
Kinda surprised this app remains in the general Play Store. Not really aligned with Google's business strategy (plus TOS) and a bit dangerous for noobs to be messing with. I always grab from XDA after waiting a bit to insure stability.
[SuperSU] maybeme2:
Absolutely right. The "update" also caused problems for nexus 5 users like me running 5.1.1. Because we are just end users it took me a week to figure out how to get back to normal. At least a warning should be put on it or better still remove it till you get it right. What's the emergency in moving away from 2.79 that at least works?!!

---------- Post added at 03:32 PM ---------- Previous post was at 03:22 PM ----------

That's ridiculous. There are multiple updates every day on the playstore. If the user needed to investigate each one on specialized threads before routine updates there would be no time to do anything else. It is not unreasonable to expect that an update on playstore is safe!
[SuperSU] Paschfire:
You are comparing SuperSU root that highly modifies the /System status to other main stream apps available on PlayStore that update/install into the /Data partition? Sorry your statement is ridiculous.

Just because it's available on PlayStore doesn't mean you don't need to be aware of what your updating/installing. SuperSU isn't a calculator app, there's a big difference.
[SuperSU] maybeme2:
If it's that special it should not be offered as a common app "update" on the playstore.

It's one thing when you are rooting a phone and quite another thing when you are just accepting a play store *update* to an installed app.

But, whatever.... All I can tell you is that it is causing unnecessary harm to working installations.

"Just because it's available on PlayStore doesn't mean you don't need to be aware of what your installing. SuperSU isn't a calculator app, there's a big difference."

Nobody is discussing installing it. We're discussing an update to an existing installed working app.
[SuperSU] Paschfire:
I was referring to the same discussion, I've since edited in update/install into my previous remarks.

Sorry I still don't agree, whether it is a simple update that came via PlayStore or first time flashing SuperSU, it is still a highly involved System modification.

You shouldn't be installing/updating things if you don't know how to return your device from an errored or bottlooped state, these responsibilities lay solely on the end-user. The Developers cannot foresee every possible problem that can arise from installing/updating.

When you modify your device beyond stock it should always be applied as basically an unwritten warning/rule you should always proceed with caution and be prepared for the worst in any case.
[SuperSU] maybeme2:
OK. You win.......
[SuperSU] Nitz327:
Careful expressing your opinions or they'll lock the thread again :rolleyes:
[SuperSU] ChiDi9901:
I still like the suggestion where simply a warning message is put into the description. Not so hard to do and everybody would be at least aware of that bug which is not a secret at all. Then this discussion can be ended for all.
[SuperSU] DB126:
Never that clean. Will likely result in a wave of drama laced XDA postings and Play Store comments suggesting the latest device calamity was a direct result of SuperSU updating with zero supporting evidence aside from the warning.
[SuperSU] maybeme2:
Or, users will decide to simply move to phh's Superuser - like I did. Works fine without the headaches and dangers of non-open source code.
[SuperSU] DB126:
Sure - nice to have choices. Pick your poison; none are perfect.
[SuperSU] maybeme2:
You are so correct. I'm back with SuperSu 2.79.....
[SuperSU] callihn:
2.82 doesn't boot on my LG K7 ms330 running 5.1.1. Tried APK and Zip with same results, wiped cache and dalvik/arts cache , stuck on boot animation. Good thing I backed up first. Guess I'll be on 2.79 until something better comes along.
[SuperSU] jcmm11:
Did you try 2.82 SR1?
[SuperSU] rickysidhu_:
I got this strange request for root access. Not too sure what it is and a quick Google search didn't provide anything useful.

I was in the middle of installing a Substratum theme when this happened, and I just let the timer run out, as I didn't feel comfortable giving something I don't know root access.

If anyone knows what this is/whether it's safe to grant root access, please feel free to share! Thanks in advance :)

Google Pixel XL

SuperSU 2.82 Stable

PureNexus June build (clean flashed)

EX Kernel 1.12
[SuperSU] BlueJeans:
I don't know what it is but this is something I would consider suspicious and wouldn't allow root access.
[SuperSU] Ch3vr0n:
Very weird. IT's like the SuperUser manager app is requesting root access to itself as the root manager. [MENTION=631273]Chainfire[/MENTION] any idea?
[SuperSU] Legendary Cryptid:
Good to know SU keeps on evolving.
[SuperSU] Ibuprophen:
WOW!... SuperSU requesting itself Superuser access... I know that I had seen this one before but, that was quite a while ago...

If my memory is serving me correctly (though, my memory has reflected a Bootloop/Stuck in Boot/the old Blue Screen of Death... LMAO!)...

I thought that this was related to the Android system itself recycling UID's that had been previously whitelisted then at some point in later had been uninstalled and then at some point in time later, the same yet newer package (of the uninstalled one) gets installed again and then the system just keept using the older/former permissions.

Though, I could be wrong or explained it incorrectly (or something like that) but, I had thought that [MENTION=631273]Chainfire[/MENTION] had addressed this issue a long time ago (a year or more).

Just providing my own thought/opinion regarding this in hopes of helping out... :) .

______________

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

https://xdaforums.com/signaturepics/sigpic4828250_7.gif
[SuperSU] r1l_Alex_™:
Agreed. I thought so aswell. I came across this very same thing about a day ago. I even went and Checked Current UID vs WhiteListed UID data from "firstboot" [SnapData] taken on our bench. Compared "Current" state, Isn't showing any of it.

Ehhh? Still a very crazy "old" reborn ghost coming back from the dead? /TSR
[SuperSU] NoobInToto:
Same. I got the same request, while substratum was loading theme ( I believe it requested access when it was installing theme for 'package installer').

I am on

Nexus 6P

Purenexus June build

Ex kernel 4.11

SuperSU 2.82 stable

I initially granted it access, before going into the app and denying it.
[SuperSU] kingbenzima:
I have an S4 what release should I flash?
[SuperSU] Tanis64:
With my S4 and 4.4.2 i have Problems with the 2.82 stable and SR-1 so I switched back to 2.79.
[SuperSU] Aid777:
I have used SuperSu on my previous phone (LG G3 and was very happy with it), I now use Magisk for the SafetyNet pass so I can use a particular app. I guess I can live without it though. Anyway SafetyNet fails for the time being, but I'm sure it'll be fixed with an update. Does the Netflix app work with SuperSU?

My main question is why do you choose to use SuperSU over Magisk? I think there are some compatibility issues with Magisk. I cannot install BusyBox and so cannot set SELinux to permissive and therefore cannot do certain stuff. If I want to switch back to SuperSu, what is the best way to uninstall Magisk, should I just flash the uninstall zip?

My device is LG G6 H870

Thanks guys
[SuperSU] Wolfcity:
I have been on SuperSU since I root phones but a few weeks ago I got a "binary occupied" message after every (clean) flash, I never used anything else than SuperSU so that message is a bit strange. I got it with 2.79, also with 2.82, it appeared a while after successful flashing it.

So I moved to magisk too, no other choice.

I really wonder what has happened to superSU, it was always my favorite rooting app.

If you want to go back from magisk you should use the magisk uninstaller, uninstall the manager, maybe flash your stock boot.img and if you want to be safe use the unsu.zip by osmosis.

After that you should be able to flash superSU again.

If you still have problems dirty flash your rom.
[SuperSU] sid12400:
SuperSU Pro Bug on Oneplus 3

Hello everyone.

I am new in the Root domain and I root a Oneplus 3 which runs under OxygenOS 4.6.1 and Android 7.1.1 with SuperSU PRO v2.82.

The software works fine and gives me administrator rights, but all the settings I configure inside the software, such as no longer requesting root authorization from a software reset by default as soon as I quit the software.

Do you know where this may come from?

Thank you in advance for your help. ;)

---
[SuperSU] drumbo1:
You have to get "beta" SuperSU v2.82 SR1 and all will be OK.
[SuperSU] CRasH180:
Can you or someone else provide the location of the "beta" SuperSU? My HTC One A9 keeps giving me the error "SU Binary Occupied". It links to an article that is extremely old and I am not sure if should still be following that or not.

http://forum.supersu.com/topic/886/htc-general-guide

Thank you for your assistance,

CRasH180
[SuperSU] Paschfire:
Using the Search feature on XDA's main/home page, type in.. supersu beta, press enter.
[SuperSU] CRasH180:
Thank you very much! It worked and now have SuperSU v2.82 SR1 installed.
[SuperSU] Wolfcity:
The last time I checked the beta thread it was stated that the latest beta SuperSU SR1 is just for pixel phones (if I remember that correctly). As posted above I got that 'binary occupied' message after every clean flash on my Moto g titan. I tried SuperSU 2.79,2.79 SR3 and 2.82. As it's recommended for a HTC user would it make sense for me to try 2.82 SR1?

I never had problems with any SuperSU version on this device, this happens after a clean flash of my standard rom Aosp extended.
[SuperSU] Ibuprophen:
First of all, i don't believe that the SuperSU v2.82 SR1 release itself was only specific for the Pixel device BUT, Chainfire did outline/provide further/additional instructions for the Pixel devices and SuperSU v2.82 SR1.

With that stated, if your question is, in fact, regarding what Chainfire outlined for the "SuperSU v2.82 SR1" and, specifically, for the "Pixel" device then you should be posting this question on the "SuperSU v2.82 SR1" thread.

Here's the link to Chainfire's instructions for the "Pixel" post, i believe, you may be referring to within the "SuperSU v2.82 SR1" thread.

Pixel Specific Instructions - [BETA][2017.06.09] SuperSU v2.82 SR1 by Chainfire

If that is what you're referring to then be sure to read that post carefully.

I, personally, would recommend that before posting any further questions, within that thread, you should take a look at the following/subsequent posts after that one (above), because there were a good handful of questions that were previously answered (specifically regarding the Pixel devices) and any further questions that you may have might be one of those that had been asked and answered already.

If your question is regarding none of the above then you'll really have to elaborate/specify more on the following thread.

[BETA][2017.06.09] SuperSU v2.82 SR1 by Chainfire

Good Luck!

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.

×MY DEVELOPMENTS×

[APP][TOOL][4.2+]The SELinux Toggler

[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}

×IN DEVELOPMENT×

[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch

Will Supersede "The SELinux Toggler"

×IDEAS FOR DEVELOPMENT×

[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}

[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
[SuperSU] Wolfcity:
Thx for your reply, I did post that issue in the beta thread but it seems to be very rare, so until now no response:
[SuperSU] ale5000:
[MENTION=631273]Chainfire[/MENTION]: Hi, I have a problem with zipadjust; if the zip archive is created with 7za (7-Zip) then zipadjust will corrupt the archive in many cases.

Are you or someone else working on zipadjust?

Ref.
[SuperSU] Chainfire:
zipadjust is made specifically to deal with Info-ZIP made files. All other archivers, all bets are off.
[SuperSU] Professor Woland:
This has been probably asked too many times but I can't see it here.

Does super SU support .lz boot images or it can handle only .gz?
[SuperSU] KaMyKaSii:
Apparently just gzip. Even Magisk which is the younger brother already has support for other compression formats. Anyway, if you are having problems with this, you can try the mod below:

https://xdaforums.com/apps/supersu/ramdisk-compression-exchanger-t3533327
[SuperSU] lk5plus:
nice app. thanks to dev and all.
[SuperSU] Noja G6:
Pop up su binary occuped too
[SuperSU] pendor24:
Hello

Recently, I have a popup that says

- "Su binary occuped"

I pass the popup and I open the supersu parameters that I propose to install supersu in the system. Something that has not happened since verse 2. 46.

I am on nougat with the verssion on 2. 82 SR1. On G935f
[SuperSU] Wolfcity:
Same problem after a clean flash on my titan.

The message should state that there's already another root solution on the device.

But after a complete clean flash of a non pre rooted ROM (AEX 4.4) this seems to be not the case.
[SuperSU] pendor24:
For me it's not a problem but rather a good news to be able to install again supersu in the system.

Rather than "you have a limited root supersu can not be converted to apk system".
[SuperSU] einverne:
latest supersu soft brick my oneplus3 , T_T
[SuperSU] jekyll530:
SuperSU v2.82 SR1 works perfect on OnePlus 3, refer to the BETA SuperSU thread.
[SuperSU] xing xi:
After I install SuperSU with TWRP, my phone Xperia Z3 starts bootloop.

What should I do?

Thanks.
[SuperSU] Wnsly:
Hold your power button till your phone shuts down (60 sec). Then boot to twrp and re-download SuperSU and it reflash it. If it doesn't work flash a backup of your ROM.

Sent from my Sony Xperia XZ
[SuperSU] RMarques:
Ive read it, kinda superficially I must confess, can anyone confirm if this latest v2.82 is System or Systemless?
[SuperSU] amitroutray:
Why this message is coming when I am trying to change the SELinux mode. When my other root applications working perfectly.

Triggered from rn4
[SuperSU] jcmm11:
By default, on a fairly up to date Android version (6.0+), it's systemless. Internally it runs some checks to determine if it needs to install systemless (it would prefer a system install if possible, but it almost never is)
[SuperSU] RMarques:
Thanks man. By any chance, do you know which is the last system only root method? I need it in order to do the very first boot after disabling forcing encyption on my OP3T so I can install multirom.

Thanks
[SuperSU] jcmm11:
No I don't. But you can force a system install. Create a file /data/.supersu with contents of

SYSTEMLESS=false

If you open up the supersu zip and look inside the update-binary file you'll find some pretty extensive documentation.
[SuperSU] RMarques:
Thanks I'll keep researching and I'll take it as an option.

Cheers
[SuperSU] Diaze:
Xposed flashable zip pls?
[SuperSU] ktmom:
This isn't an xposed thread ☺
[SuperSU] Shtiff1:
Lol
[SuperSU] wuhoatu:
Flash SuperSU 2.82 or update via Google Play, both cause my Xperia Z3 D6616 T-Mobile bootloop. Back to 2.79 and everything is OK.
[SuperSU] jcmm11:
What happens with 2.82 SR1?

Edit: or SR2 which was just released
[SuperSU] Chainfire:
SuperSU v2.82-SR2 has been released!

Release notes here: https://plus.google.com/+Chainfire/posts/YCoHDpNaY38

Please see the BETA thread for further details and discussion: https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] piperx:
Thanks Chainfire ?
[SuperSU] :
Thanks For A New Release Matser Of Root [MENTION=631273]Chainfire[/MENTION]
[SuperSU] skyhirules:
Latest SR1 and SR2, both fix the Xperia boot loop issue. Tested on Z1 Compact.
[SuperSU] Geoffxx:
is it now safe to update 2.82 from PS on xperia devices or are there still issues, are we still needing to use beta versions, it's hard to tell exactly what is on the Playstore, can I suggest the next time you release a new version on PS that you make a point of stating that xperia issue is resolved, saves me going through pages of post for answers.

just asking

Ok I see still beta SR2 after reading and searching
[SuperSU] Jamsserty:
Thanks for your info , waiting
[SuperSU] Chainfire:
To ease configuration and do away with all the echo "...">>/data/.supersu commands, at least on ARM-based devices:

SuperSU Config (AROMA)

(NOTE: it does offer SBIN mode, but you'll have to be running SuperSU v2.82 SR2 or later for that to actually do anything)
[SuperSU] Chainfire:
SuperSU v2.82-SR3 has been released. See the release notes here: https://plus.google.com/+Chainfire/posts/JRn87G77gey
[SuperSU] JPT223:
I cannot find a working root method for my S3 neo i9301. SuperSU 2.8.2 tells "not rooted". Shouldn't it offer installation of su?

Since systemless is available this shouldn't be any problem? do I have to force systemless mode somehow? android version is 4.4.2... ancient :)

thanx

tried but failed:

$ echo "SYSTEMLESS=true" > .supersu

$ adb push .supersu /data/

failed to copy '.supersu' to '/data//.supersu': Permission denied

$ adb root

adbd cannot run as root in production builds
[SuperSU] Ch3vr0n:
Android 4.4 doesn't support systemless, period. If you want a systemless root & all the benefits you'll need a new phone.
[SuperSU] Ghostface009:
Please halp :crying:

issue: "su binary not found (in releases older than 2.80)/root undetected" after a certian period past booting.

+ this appears when running su command

device: Axon 7 A2017U

WARNING: linker: /su/bin/sush: unused DT entry: type 0xaa1303e054ffff68 arg 0xaa1403e2d2800081

CANNOT LINK EXECUTABLE "sush": empty/missing DT_HASH/DT_GNU_HASH in "/su/bin/sush" (new hash type from the future?)
​

Ofcourse I picked the last 2 lines because I don't want to flood the thread, but Im sure pros and bros can relate and help me through this :'l please tell what is this and how to fixit :crying:
[SuperSU] Maxxvds:
my chin actually hits the floor whenever i read some of the posts in these long threads...then i just gotta walk away.......
[SuperSU] boxcar8028:
How is SU working with Oreo 8.0? I’m on 7.1.2 with SU 2.82 I read somewhere that BusyBox is not working with SU. Should we use 2.8.2 or 2.82-SR3 with Oreo 8.0?
[SuperSU] Anuj Upadhyay:
I am not able to fully unroot

Showing failed
[SuperSU] ulxerker:
2.82-SR3 is working with Android O, 2.82 won't.