yashsingh1/xdaforums huggingface dataset:
[SuperSU] steanne:
...huh. you're right. well, that's frustrating. gotta be deliberate on tibu's part, but it might make sense: it needs supersu to work, it probably doesn't want to give you the chance to break it.
[SuperSU] tramp20:
I too had problems after updating to 2.80:

My smartphone is in a permanent bootloop so I had to restore a CWM backup.
[SuperSU] jugoslavpetrovic:
Thanks guys for reports, I am still with SR4, I dont need new unstable bug privacy corrupted ****, just simple root as it was with latest chainfire made. SR4 2.79 is fine. It doesn't seems right that if already rooted and as said less secure device gets backdoors to send data online.
[SuperSU] Jengo:
I’m also stuck in a bootloop, but unfortunately Recovery is also not working any more.

I leave my phone like this for today hoping that there will be a quick solution without reinstalling everything.

Sony Xperia Z1 on Stock 14.4.A.0.108 with root
[SuperSU] Tanis64:
I have waiting for this to happen since Chainfire is no longer responsible for this Playstore SuperSU App.

- New permissions without an explanation for what and why.

- some users here report that with 2.80 Add SuperSU stops working together with AdAware.

Installing 2.80 on my phone...

Both methods to update SU Binary failed.

Normal way takes about 4 minutes to say it doesn't work.

CWM/TWRP leads to an occupied SU-Binary.

The Devs or the company behind this SuperSU versions should keep in mind that the success of SuperSU was because we trust Chainfire.

Bringing up a bunch of new permissions and changing the way the binary was installed without mentioned on word about it, is something I don't trust, exspecially not when it was an app that can make every thing on my phone because it self manages the root access of everything.

As long there is no clear word from them to explain the changes I will stay on V2.79 which works great for me.

The play store should become an option to exclude APK's from Update (freeze version)
[SuperSU] Dr Goodvibes:
Xperia Z1 Compact

Android v5.1

Using SuperSu v2.80 the phone goes into a boot loop after the version is installed.

The binary update is successful and then a reboot is suggested.

After that it's just a constant boot loop.

Restored phone, but can not successfully install SuperSU v2.80
[SuperSU] doongoo:
Updated the version to 2.80 , binary updated itself within some seconds. Everything just fine, as before.
[SuperSU] Chainfire:
We're investigating why v2.80 is losing root for some users. Stay tuned.

As for the additional permissions, they are related to a feedback screen which allow you to submit bugreports. Analytics will also come at some point (which you will be able to opt-out of), which requires more or less the same permissions. Note that permissions are meaningless for root apps anyway.

I still work on the SuperSU code and review all changes that make it in. Please stop raising a panic. The bug may well be my fault.
[SuperSU] one.:
After installing on my Z3V (D6708) I got stuck in a bootloop. Rolling back to 2.79 fixed it.
[SuperSU] Jengo:
What about the bootloop for the Xperia Z1 users? The “Compact” users can obviously use Recovery to restore, for me even Recovery doesn’t work anymore.
[SuperSU] Chainfire:
I have no idea how Xperia's work. I am not a Sony guy. You'll probably have to re-root starting from stock boot/recovery?
[SuperSU] thewaywardgeek013:
LG D802 Stock Kitkat v4.4.2 User here. Once I installed the new v2.80 lost root altogether. Said it was going to update SU Binary, but seems it went ahead and removed root.

Tried reverting back to previous versions but still didn't fix it. Seems I need to reroot my phone. Right?
[SuperSU] Haphim:
For what it's worth, I have a new LG V20 (US996) - official bootloader unlocked. I installed TWRP, then flashed SuperSU-v2.79-201612051815.zip. In TWRP, it said it ran fine - but after rebooting the phone normally, SuperSU wasn't installed. I didn't have root.

I tried this multiple times with no change. It was only after I used TWRP to Format Data (thus eliminating the decryption), that the SuperSU flash took properly.
[SuperSU] erfandl:
2.80 after update binary on XPERIA Z Ultra android 5.1.1 stuck on bootloop. only this version have problem older worked perfectly. please fix this problem
[SuperSU] Rebel2k:
Yes, same problem on Xperia Z1. How do you get back the phone to work at least? [MENTION=2514812]erfandl[/MENTION] did you manage to get it to boot again?
[SuperSU] micr0g:
Pixel user and the update from playstore work fine.
[SuperSU] Chainfire:
For anyone that has updated to v2.80, lost root, and went back to v2.79, can you try if this v2.80 updates correctly?

Please list device and Android version.
[SuperSU] erfandl:
there is no way to back normal boot. I reflashing my phone and lost all my data :(
[SuperSU] Rebel2k:
Wow! Not good... Did you try flashing back an older version of super su first? Did you try to dirty flash your rom not to loose anything before?
[SuperSU] erfandl:
wait I testing it.

---------- Post added at 10:18 AM ---------- Previous post was at 10:13 AM ----------

no the problem not fixed ! and again I get bootloop

XPERIA Z Ultra Android 5.1.1

---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------

yes I flashing 2.7 but not fixed. :(
[SuperSU] Geo_Tech:
[MENTION=631273]Chainfire[/MENTION] Binary occupied for me too after updating from playstore. Then i flashed the zip and had same results. So i flashed 2.79 again and all is working fine.

Edit: galaxy s3 4.4.4 kitkat
[SuperSU] petrsiri:
In my case Adaway is not working after updating SuperSU to 2.8 (i get the message that applying the hosts file to your system failed). I haven't noticed any other issue. Oneplus 3 with OOS 4.02
[SuperSU] xalaros10:
I too had problems after updating to 2.80:

My smartphone Sony Z1 Compact is in a permanent bootloop, try to flash older versions v2.79 SR3 or S4 with no luck. Any help I have no backup.
[SuperSU] erfandl:
there is no way my friends ! i'm too loosing my data
[SuperSU] Klaus N.:
Xperia XZ (F8331), Android 7.1.1 Sony stock fw

I still have root with this v2.80, but ofc it says, it's not possible to have systemless root with this version. I think, that's the reason, why AdAway - which was running in systemless mode before - doesn't work in systemless mode anymore.

Remark: I haven't tried v2.80 provided at PlayStore.
[SuperSU] ALIGATOR26:
At me on Samsung Galaxy S7 everything it is ok! Thank you!

Trimis de pe al meu SM-G930F folosind Tapatalk
[SuperSU] AtAM1:
Thanks for your statement.. The way the recent update was pushed out without any explanation for the additional permissions is a good enough reason for users to be concerned... Also the OP's initial post was only updated after 2.80 was released to the public and users began complaining. In this day and age, one must not take such discrepancies or security issues lightly.

I am also glad you are still reviewing the code - can you confirm this is the case for both SuperSu and SuperSu Pro apps? Furthermore, what additional steps/measures have you taken to ensure what you review is what gets released to the public? Or is the onus on us to scrutinize recent versions ie. making sure they are not phoning home?

Please don't take this as us raising panic ... we are not. We are asking valid questions considering SuperSu is a critical component of the rooting process.

Personally I believe, and I am sure 99.999% of android users would concur with me, that you are a valuable asset to the android community. Your work is truly appreciated.

Thanks!
[SuperSU] Klaus N.:
Deactivate systemless mode in AdAway and try again...
[SuperSU] Chainfire:
Where does it say this? Can you screenshot that?
[SuperSU] petrsiri:
Thanks a lot! It works now!
[SuperSU] erfandl:
[MENTION=631273]Chainfire[/MENTION] what can we do now ? please release new version to fix this problem
[SuperSU] Klaus N.:
Here you go...
[SuperSU] mamalujo2003:
su binary occupied

Hello, I updated the supersu app through the Play Store a short while ago. After doing so I was promoted to update the binary. I tried the normal way. It was unsuccessful, so I rebooted to try the other way. It rebooted into recovery then rebooted into system. The binary did not update. Instead I get the following pop-up, "su binary occupied." What does that mean? I've never seen that before. I am using CM11, 4.4.4, on a Galaxy Tab 3 8.0 lt01. For recovery I am using the latest TWRP, 3.1.0.1. None of the apps that require root will work because they don't see the root. Any suggestions?
[SuperSU] Chainfire:
You misread. It actually says it is currently in systemless mode. Not that systemless mode is impossible.

Not sure what is going on with adaway though. I don't think you should set it to /system mode.
[SuperSU] Chainfire:
Last I checked the Pro version doesn't actually contain any code. It's an empty package, all the code is inside the non-Pro package, it just checks for Pro presence.

After release I download the released (non-Pro) APK from Play, decompile both it and my own versions, and check for differences. I have not gotten around to that with v2.80 yet, for the same reason I hadn't update the changelogs, made a release post, etc: the time of day of the release coincided with my evening plans :) I had expect it all to be released earlier in the day, but working across timezones is tricky sometimes.

Regarding updates on posts on XDA, I think it is important to realize that XDA may not be the first priority for them like it is for me. Still, I don't think getting updated within hours is that bad a score.
[SuperSU] thewaywardgeek013:
LG D802 Stock Android Kitkat v4.4.2

Tried this and said root undetected, so it seems that the Google Play Store update to the SU Binary threw out my SU access. Will try to reroot when I get to my PC. Hope this helps.

NOTE:

Just reverted to SuperSU 2.79, though still didn't have root access when I reverted.
[SuperSU] Dr Goodvibes:
Model: Xperia Z1 Compact D5503

Android: 5.1.1 (Build 14.6.A.1.236)

Bootloader: Locked

Still fails.

Side loaded the apk you referenced.

The SuperSU binary update completed successfully.

However reboot just puts phone into boot-loop.

Thanks for helping out Chainfire :)
[SuperSU] Chainfire:
Did you actually re-flash your firmware and wipe data before trying the v2.80 I attached ?

Or did you just flash it over your non-working system ?
[SuperSU] Chainfire:
Thanks, very interesting to know the update both completed successfully and the phone refused to boot. This is a very important distinction from the update just failing.

Did the v2.80 from Play also update successfully and then fail to boot, or did it not even update?
[SuperSU] erfandl:
yes I flashing fresh ROM and full wipe

google play and apk and flashable zip have this problem
[SuperSU] Klaus N.:
Ok, you're absolutely right - was my fault.

And about AdAway: Went back to SR3 SuperSU 2.79, and it works again in systemless mode.
[SuperSU] Chainfire:
For my replication purposes, can you link me to the exact version of AdAway you installed ?

Imagine I'm a complete noob at using AdAway (which I actually am, I've never used it other than test installs)
[SuperSU] xalaros10:
The v2.80 from Play updated successfully and then fail to boot (I had bootloop).

I flashed v2.78, now phone boot ok, root seems ok but I have lost the icon on surface of SuperSU although there is in Apps. How does it appears again?
[SuperSU] Klaus N.:
Yes, of course:

https://f-droid.org/repository/browse/?fdfilter=adaway&fdid=org.adaway

(It's Version 3.2 - Added on 2016-11-27)
[SuperSU] Dr Goodvibes:
Yes. That's correct.

Both the Google Play store version and the version you referenced for sideload successfully updated the binary.

I've had other Minix Android TV boxes lose root with v2.80 where they failed to update the binary and said "unsuccessful" so that's why I'm using my Xperia Z1C as a test as it has a TWRP restore available. :fingers-crossed:

On my Xperia Z1C I have SuperSU v2.79 installed in /system as a system app.

P.S. Hours ago I updated an Xperia C1905 Android 4.3 to SuperSU v2.80 and it installed, updated the binary and rebooted without any problems.
[SuperSU] vampirefo:
I am not having any problem with 2.80 or with adaway, I use system root instead of systemless root though.
[SuperSU] xela1989:
After update to 2.80, when i open SuperSu, i see that " SU Binary Occupied" ... How revolve it? Thanks
[SuperSU] Chainfire:
At this point I have been able to replicate this behavior:

- Binary update fails

- Root is lost

I have not been able to replicate this report yet:

- Binary update succeeds

- Root is lost or boot loop upon reboot

So please keep those reports with exact device, firmware and Android version coming. Certainly somebody has this issue on a device I actually have and can help me replicate.
[SuperSU] erfandl:
Binary update succeeds

boot loop upon reboot

Phone: XPERIA Z Ultra ( C6833 )

android 5.1.1 build 14.6.A.1.236
[SuperSU] buttie:
On HTC One m9 stock (Androdi 7.0, 1st February 2017 patch) the app (and binaries after) update correctly, still root is unavailable and AdAway cannot move hosts to su folder in systemless mode.
[SuperSU] jcrt2000:
Note 4 (Sm-N910T)still on Android 4.4.4 build (KTU84P.N910TUVU1ANK4). App updated fine binary fails and removed root on reboot. If I reflash version 2.79 in twrp root returns. I am ignoring binary update notice and root is still working
[SuperSU] paaaulo:
Nexus 5x 7.1.2 May 5 2017.

Updated correctly, still root is unavailable and AdAway can't move hosts to su folder in systemless mode.

2.79 SR3 works fine.
[SuperSU] piccit:
My 2 cents on AdAway issues: I stopped following AdAway closely when all the systemless drama happened, so idk what exactly the "Enable systemless mode" checkbox does, but I had to turn that OFF for AdAway to detect that the hosts file had been updated.

I had applied my own bind mount su.d script (as opposed to having AdAway create one, which I think it had the ability to do, and I thought that's what it did for "systemless" mode) and confirmed that AdAway was in fact updating the hosts file even though it was reporting failure.

Idk what it checks differently when it thinks it's in "systemless" mode, but the whole point of the bind mount is that AdAway can continue working with /system/etc/hosts, so I can't think of a good reason why changing that setting should affect the check
[SuperSU] Rebel2k:
Model: Xperia Z1 C6903

Android: 5.1.1 (Build 14.6.A.1.236)

Bootloader: Locked

Update to 2.80 went fine, but not possible to reboot after that. The reboot goes into boot-loop forever...

Tried to flash ZIP 2.79 and wipe cache & dalvik + fix permissions, that helped rebooting properly. Now I have a couple of "Google Play Services" and "Hangouts" errors from time to time, but at least I rebooted.

Thanks for your help Chainfire!
[SuperSU] RodimusConvoy:
Updated app from the play store, ran app, app asked for binaries, I said yes, app then asked to reboot, I say yes, phone reboots, no more root.

I went through the process to re-root (Kingroot), then used SuperSU-Me Pro to replace the Kingroot root manager with SuperSU. The version of SuperSU that SuperSU-Me uses is v2.79. I'm going to stay with this version until the updated version is fixed.

A little info: I have the Cricket-branded S4, BOA1 boatloader. No ROM exists for this, I won't attempt other versions for fear of bricking my phone. No recovery other than stock (i.e. no TWRP), everything is stock and Android 4.4.2.
[SuperSU] Ps24u:
Exactly same issue here with Z1C : bootloop.

2.80 is bad.
[SuperSU] ulxerker:
Its not bad, its just buggy for only a few devices and the developer is already working on it. So please be patient.

---------- Post added at 12:38 ---------- Previous post was at 12:35 ----------

2.80 working fine here, updated SuperSU via PlayStore and binary via app after that. see sig for device details.
[SuperSU] NicoCaldo:
Update today from the APP. No more root.

Trying to reinstall SuperSU via TWRP, all right but when I open the app it says SU Binaries occupied and I no more have root permits

Please fix

gt-i9300 cyano 11-20160115 snapshot with boeffla kernel 2.14 cm 11 ng kernel version 3.0.101
[SuperSU] Chainfire:
Could you try this version?

https://xdaforums.com/showpost.php?p=72422699&postcount=1445
[SuperSU] Wolfcity:
Moto G 2014 (titan} Aosp Extended 7.1.2, May 5 2017. Binary update succeed, AdAway can't move hosts to su folder in systemless mode.
[SuperSU] xalaros10:
On Sony Z1 Compact (Lollipop 5.1.1) installs fine this new version, update binaries OK but after bootloop again.
[SuperSU] krule031:
I got bootloop on Xperia M2 after updating.

My M2 is: D2303, Android 5.1.1

Guess it's something with the Xperia devices lol
[SuperSU] shikasp:
First time this boot-loop thing ever happens to me. Needless to say im kinda freaking out atm (desperately looking for info/tutorials to solve this)

xperia Z1 compact, same as Rebel2k said some posts above update went fine and now im stuck on boot-loop
[SuperSU] Rebel2k:
Yep, for sure, because it seems to only affect Sony Xperias... ;) Could that be because of the custom recovery? Which one do you guys have? On mine it's DualRecovery.

---------- Post added at 01:01 PM ---------- Previous post was at 01:00 PM ----------

You can try what I did to be able to boot again (installed SuperSU 2.79 ZIP through TWRP and then wipe cache & dalvik). Doesn't fix it all, but you should be able to reboot.
[SuperSU] dunjamon:
I've had the same issue and have tried the version posted above. I'm still seeing the same issue on my N6P. :(
[SuperSU] dauchamhetnhe2:
I installed this apk and it works fine
[SuperSU] User_99:
Lost root after latest Play store update. Su binary cannot be updated. Message Su binary occupied was shown. Flashed old version prior 2.79 an all is fine again. Now use 2.76 Pro

Stock Samsung 4.2,2 Rom on Galaxy Note 8.0
[SuperSU] dunjamon:
Did you update to 2.8 via the store and then install this over the top? I tried that and I still didn't have access.
[SuperSU] shikasp:
Thanks, I'll try that later, now Im letting the damned thing cool off a bit, it almost set on fire after all that non-stop boot-loop action.

I do have TWRP, shall I be able to find 2.79 on the files on my phone (maybe under the install menu?) or do I need to manually put it in?
[SuperSU] Ps24u:
DualRecovery here as well.

Flashed SuperSU zip 2.79 from TWRP and it's rebuilding dalvik cache atm..
[SuperSU] Rebel2k:
First you need to download it from the website (http://www.supersu.com/download, or directly the file https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip) and go into TWRP, plug your phone to a computer, send that zip file onto your internal sdcard storage, and then from TWRP, go to install > select the file and reboot after the installation is over. Good luck, hope it's going to work for you.

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

So, you'll probably be able to go back to a working state right after. That's what happened to me (my father actually) but then some "Google Play Services has stopped working" and "Hangouts has stopped working" errors have been popping out... Didn't have time to work on fixing this yet (remote debugging is not that easy ^^).
[SuperSU] :
Moto G 2014 titan xt1068

Running Lineage 14.1 latest nightly

I downloaded v80 flashable package from the main thread. Everything seems to normal but on every reboot supersu get force stopped. Also I'm not able to grant permission in app details. It actually checked but reset upon return n says no permission granted.
[SuperSU] dunjamon:
I updated to 2.80 via Play Store, rebuilt binaries and there was no root. I then went back to 2.79 and it all works. Then I updated using the apk provided above, rebuilt binaries and there is no root again.
[SuperSU] djwdj:
不是在北京经营吗？为什么supersu没有中文官网
[SuperSU] dauchamhetnhe2:
I have updated v2.8 on chplay and failed. I installed v2.79 twrp zip and normal back
[SuperSU] ulxerker:
English please.
[SuperSU] Chainfire:
I have found (but not solved) the issue with AdAway. Please stop reporting it for now.
[SuperSU] erfandl:
but I dont have AdAway ! please fix this problem for sony smartphones
[SuperSU] djwdj:
Not operating in Beijing? Why does the official website have no Chinese?
[SuperSU] xalaros10:
On Sony Z1 Compact (Lollipop 5.1.1) trying the above zip file 2.79 via TWRP, then clear cache and Dalvik cache then reboot phone all worked OK (root OK, icon of SuperSU reappeared on surface that it was lost although there was on Applications, AdAway work OK). Thanks.
[SuperSU] ldeveraux:
I flashed the zip in TWRP after the same issue and I'm up and running 100%
[SuperSU] tobbbie:
bootloop on Xperia Z3 Compact after SU (pro) update to 2.8

On all my devices it always worked, but now I am lost in boot-loop on my Xperia Z3 compact. It still had Lollipop on it (the 5.1 but not latest which it failed to upgrade after rooting it). Of course I also have all goodies installed for a rooted device, especially also XPosed framework (.87)

Steps that I remember

installation of both Super SU and -pro (I wonder why so many new rights are requested though...) was ok

Update of SU binary was ok, I think but I might not have noted the difference between "Successful and "Unsuccessful" (which I noticed on my galaxy tab) - please change the "unsuccesful" to "Failed" - which is more striking to notice

Entering SU settings to put it to system partition

Confirming the "Cleanup and prepare" pop-up

enjoy the boot-loop since then

Hint for those who want to get out of the boot-loop: press and hold Vol-Up and Power simultaneously after a new reboot starts until you receive 3 vibrates in sequence - then you powered off. No need to rip the device apart or let it boot until battery is depleted.

As I have a locked boot-loader I have no updated recovery and it seems there is no fast way to get access to the system partition to fix the issue in any way.

What options do I have here?

how can I access the internal Sony-Recovery? I had some double-vibrate occurring (keeping Vol-Up or Vol-Down pressed and held) but reboot -loop continued, so if there was a recovery, then I can not enter properly.

unlock boot-loader (I can do on my device) and get the one from Sony Open devices Program? I applied for using the EMMA tool but some approval is pending - no idea how long THAT will take...

Sony-Companion Repair device? This will wipe my user-data - and so far I still would not want to go this option.

On my old Galaxy Tab 2 7 GT-P3110 the update via play-store works but it fails to update the su binary the usual way.

Oh sigh - i wanted to spend the day otherwise than debugging this :(
[SuperSU] shikasp:
Did what you said, my phone is working again after android ran some installation processes. I will keep an eye on this thread for more fixes.

Thank you for your support, Rebel. :o
[SuperSU] Ghisy:
Just fyi: I updated from 2.79SR3 (flashed through recovery when clean installing the latest Pure Nexus for the Nexus 6P) to 2.80 through the Play Store and lost the ability to apply AdAway hosts file. Binary updated fine and everything else related to root worked.

I did a full unroot within the SuperSU app, rebooted and flashed 2.79SR3 again. I had to grant root for all the apps that needed it again BUT AdAway works again now. So beware if you use it, stay on SuperSU 2.79SR3 for now!!!
[SuperSU] Puff:
You've basically posted an answer to your own question here. But if you don't have TA partition backup (and I don't know if root privileges will be there to do that in that state), you'd be a bit screwed as you'll lose the DRM keys and will have to meddle a bit to restore the functionality (getting the keys back is impossible without a backup). Apart from that, I don't suppose it'll allow you to flash anything if it's not signed and whatnot.

The other thing could be flashing the temporary recovery (if I remember correctly, it can be done here).

edit: of course you can flash the stock FW via flashtool and start from there, but as you know, you'll lose root and any of your customizations
[SuperSU] Zgadnijcie:
For me 2.80 doesn't remove root. Binary updated succesfully. Everything is ok since yesterday.

Huawei P8 Lite TT (OmniRom 6)