yashsingh1/xdaforums huggingface dataset:
[SuperSU] danilo_scala:
I lose root in Xperia z5 Premium in update play store, now i flash 2.81 again? I try and no work
[SuperSU] vampirefo:
Just updated to 2.81 via playstore no problems, I only root via system mode, don't use systemless mode.
[SuperSU] kojak1989:
With newest version 2.81 I don't have root.
[SuperSU] shaggyskunk:
You might want to mention what device you have.......etc ;)

---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------

You too - What device etc.... & From the Store or TWRP zip?
[SuperSU] alphamode:
Same issue going around, I lost root after updating from the play store. Nexus 6p I had 2.79 installed via a flash and updated to 2.80 from the play store and all was fine, then updated to 2.81 and it asked for a binary update which is said failed, then it said it couldn't detect root. I tried flashing a 2.81 zip but it failed saying it was already patched
[SuperSU] Didgeridoohan:
Restore your backup. Or, if you don't have one, clean flash your device and start over.
[SuperSU] Arceist Justin:
Four devices same problem. Galaxy Tab 3, Galaxy Tab e Lite, Galaxy s4, and the zip fails every time on Droid Bionic
[SuperSU] manpildo:
Yup, I think it's time to jump ship. Those new maintainers are shady as hell, no explanation whatsoever for the new intrusive permissions, and on top of that the latest "stable" update broke root. I hear Magisk is the new big thing now, should give it a try.
[SuperSU] Ps24u:
On Xperia Z1C, i restored an old backup with TWRP that had 2.79 installed.

Then went to Play store and updated to 2.81, installed new binary was successful.

This time it rebooted OK, no bootloop and everything seems to be working OK.

So for me update 2.81 is now working fine on Xperia Z1C.
[SuperSU] jeffyh:
TWRP Error on v2.8.1 update on LOS nightly 2017-05-25

was rooted on lineageOS 2017-05-18 / superSU v2.80 / boot-signer then updated to lineageOS 2017-05-25 which always causes root loss and tried to flash SuperSU v2.81 in TWRP and getting an error

TWRP log

[COLOR="Red"]...
- Patching sepolicy
--- Failure, aborting,
[/COLOR]
[SuperSU] ManDone.vRs:
i feel unsafe too with SuperSU , removed and magisk installed ;)
[SuperSU] CyberZeus1977:
Did you unroot from SuperSU app?

Inviato dal mio Nexus 6P utilizzando Tapatalk
[SuperSU] Flo_webRadio:
On LG G4 (H815) 2.80 and 2.81 are OK.

On Samsung Galaxy s6 Edge plus (SM-G928F) 2.80 is OK, 2.81 don't works, not root. (I have tried with update from playstore and twrp)

Inviato dal mio SM-G928F utilizzando Tapatalk
[SuperSU] kojak1989:
Nexus 5x, Pure Nexus rom at first from play store I update it but after in TWRP, version of TWRP 3.1.1.0
[SuperSU] :
I had no problems with 2.80.

Now after the second update (2.81) I also lost root.

I'm using a HTC 10 and updated via PlayStore -> updated binary inside the app and reboot.

Edit: Got 2.81 working now on my HTC 10.

I just uninstalled the app, rebooted, installed 2.81 again from PlayStore, updated binary, rebooted.

Now root is working with 2.81.
[SuperSU] Ch3vr0n:
Theres nothin excessive. If you'd do your research and read the last couple pages you'd know those permissions are related to a new feedback screen implemented in 2.80+ for debugging and logging purposes.
[SuperSU] Arceist Justin:
That still didn't work! I reflashed TWRP and SuperSU and STILL NO SuperSu

Anything else to try??
[SuperSU] Didgeridoohan:
By clean flash I meant wipe your device and reflash your ROM. Is that what you did? Or, better yet, restore your backup (but I'm guessing you don't have one).
[SuperSU] tdunham:
Quoted: "I feel unsafe too with SuperSU , removed and magisk installed"

This is fairly disrespectful to this developer. If you have concerns, by all means take whatever measures you deem necessary but to voice this in open thread is not called for.

A msg to all the newbies:

This is a development thread, you should already have a clear plan in place to recover your phone back to its previous state before flashing ANYTHING to the phone. And some of the comments I'm seeing from you folks aren't helping here as well. ;)
[SuperSU] sirxdroid:
2.81 is busted on Nexus 6P, no root, went back to 2.79 SR3 clean flash of latest stock image.

Stay away until the issues are sorted out.
[SuperSU] jeffyh:
Man, you guys are harsh. For the work this dude does, give him a break.

Also, would be helpful to provide more info than essentially "i lost root"....
[SuperSU] rgraville:
Valid point. I don't do OTA updates because I like to control the update process. January is the last time I updated my device with a dirty flash, hence the backup just after validating things were working.

I probably should check for a new image, take new backups, and flash the updates. In all the spare time, right? :)
[SuperSU] SHADOW-XIII:
disrespectful is to add all those permissions and not mention a single word about it on the play store app page/update
[SuperSU] matrixx1:
Supersu 2.81 made my phone Nexus 6p loose my root. Updated from Playstore.

Then I tried it via Twrp, same. I had to revert to 2.79, hope that still works

Yeah 2.79 still works. If you own Nexus 6p DO NOT update Supersu bc you will loose root.
[SuperSU] Mesmurized:
Thankfully the installation process identified these permissions. Keep in mind a 'root' app doesn't need to ask permission" ATM I'll pass...
[SuperSU] Ibuprophen:
Okay [MENTION=631273]Chainfire[/MENTION]... To start, I'll repeat what my device is. I have a d2vzw GS3 with CM13.

I flashed the v2.81 in TWRP and cleared the Dalvik.

I noticed something that i remember seeing before but, it didn’t occur to me till a coconut hit me on the head LOL!

On a previous post, i had posted a screenshot (with a Logcat file) of that popup message stated that the SuperSU had stopped responding. I later added that the popup didn’t happen very much at all as well as still keeping root.

Now i had looked a bit into this, and tried a few things to be sure of it, and noticed that this popup had only been happening when a change in my network state occurred. Meaning that actions (automatic or manual) regarding the devices network state like going from WiFi to Mobile Data (vice versa), changing from Global to LTE, Reseting the default APN and anything else linked to it.

Now after comparing the 2 recovery logs, between the v2.80 and v2.81 (post flash), i found nothing really substantial.

So i turned to compare the 2 Logcat files...

Bear in mind that I had previously stated that SuperSU v2.80 (and now v2.81) is the only app that I was unable to grant any of the 3 permissions to within my devices Settings --> Apps. What happens is that when i toggle the 3 to grant all permissions to SuperSU, and then go back 1 and find that those 3 will not stay granted.

Back to the Logcat comparison... They both have identical errors (in various ways) as the following 2 examples show.

"PackageManager: Not granting permission android.permission.ACCESS_NETWORK_STATE to package eu.chainfire.supersu because it was previously installed without"

---AND---

"AndroidRuntime: java.lang.RuntimeException: Unable to start receiver eu.chainfire.supersu.NetworkConnectionReceiver: java.lang.SecurityException: ConnectivityService: Neither user 10078 nor current process has android.permission.ACCESS_NETWORK_STATE."

With that stated, i noticed that, for my device (and possibly others too), the bottom line has to with the ability for SuperSU to obtain proper Permissions for anything that it asks for which is also reflected in the 3 permissions (as previously stated) that won't stick.

I've attached the 2 Logcat files for you to compare yourself.

I have a feeling that, the permissions issue with SuperSU, MAY also be, somewhat, of a contributing factor regarding the issues many others have been experiencing too

Please let me know if you require any further information.

Thank You!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] nowster:
Quick fix:

Flash your boot.img

Flash the 2.79 zip (some devices need the SR3 version).

Grab the 2.79 apk from http://www.supersu.com/download

Overwrite the bad SuperSU package:

adb install -r SuperSU-v2.79-20161205182033.apk
[SuperSU] KHEMS91:
Can i install SuperSU as system app??

Is there any way to do that?
[SuperSU] Mesmurized:
Look here for better info: https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] buttie:
Good find, I can confirm the same log entry after app FCs on Nexus 9 with AOSP 7.1.2 based Pure Nexus ROM. App in fact crashes after connection state have changed.
[SuperSU] Droidtimex:
[MENTION=631273]Chainfire[/MENTION]

Supersu 2.81 made my phone (Nexus 5x android O DP2) loose my root. Updated from Playstore today...

I tried it via Twrp, its the same...

Last 2.80 works...
[SuperSU] wizardwiz:
I simply booted at recovery and re-flashed the good ole 2.79SR3 to get root access again.

No 2.8 nor 2.81 are working on my nexus 6p with 7.1.2. Didn't have to re-flash boot.img nor system.img.
[SuperSU] _Altmann_:
I have a sony xperia e4. This model doesn't have recovery mode. What am i going to do?

I rooted my device a couple of years ago with Kingo Root.

It was easy to replace Kingo SuperUser with supersu. I just had to install SU and Kingo SuperUser gave root permission to it. Then i just had to uninstall Kingo SuperUser

But now Kingo SuperUser blocks SU and doesn't give it root permission. That means i cant root the phone with Kingo and replace with SU anymore. I cant install SU via zip file because, like i said, i don't have recovery mode.

So i ask again. Can someone please explain me what am i going to do?
[SuperSU] And_roid4_all:
Samsung Galaxy s8 work su 2.80 but to upgrade 2.81 will lost root. :rolleyes:
[SuperSU] Chainfire:
Thanks, this is definitely going to help to figure out what the ANR/crash issue you have been seeing.

However, I'm 99% sure it is completely unrelated to users losing root or boot-looping.
[SuperSU] sirxdroid:
Does the new SuperSU have any setting to disable the analytics tracking? Or there's no way to opt-out?
[SuperSU] SergeyVl87:
Xiaomi Redmi Note 3 Pro, Android 5.1.1

Today have updated SuperSu from 2.79 to 2.80 via Google Play. Binary update (normal mode) has failed.

After reboot I have bootloop.

I have try to install 2.79 via TWRP, after reboot - bootloop.

I have try to remove SuperSU using UPDATE-unSU-signed script via TWRP, after reboot - bootloop.

I have try to reinstall firmware (without wipe) using FastBoot - bootloop.

How can I fully deinstall (or successfully install) SuperSU? I need to repair my phone without wipe.
[SuperSU] samhhmobil:
HTC One M7, Stock Firmware 5.0.2, TWRP 3.0.2 SuperSU 2.81 crashes

Hi

I installed today 2.81 SuperSU Update (last stable running version was 2.79). After reboot the M7 is hanging in bootscreen, nothing happens. Only hard shutdown (Vol-Down and Power) is possible! Sigh.

Recovery works, but you cannot boot into the system.

Factory reset didn't help.

Only a complete firmware flash was the solution, and EVERYTHING on the phone is lost.

Second step after that was flashing TWRP recovery again, everything works well, but after installing the the juvenile phone the SuperSU (via TWRP) it hangs in the same manner, so the second time it was necessary to flash the complete firmware.

What's wrong there?

Thanks,

"samhhmobil"
[SuperSU] thegios:
May e it's already been said but...

Nexus 6p with 2.79 flashed from TWRP and working.

Android 7.1.2.

Updated SuperSU from app to 2.80 and still working.

Updated from app to 2.81 and no root.

Reverted to 2.79 from TWRP and have root.
[SuperSU] VivaErBetis:
Nexus 5x Using TWRP 3.1.1-0, zip install

- V2.80 Install OK but forceclose after every boot. But I think SuperSU works.

- V2.81 Install Failed:

- Patching sepolicy
sukernel v2.81 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk] ...

Saving to [/sutmp/sepolicy] ...

libsepol.avtab_read_item: more than one specifier
libsepol.avtab_read: failed on entry 235 of 7502
supolicy v2.81 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Patching policy [/sutmp/sepolicy] --> [/sutmp/sepolicy.patched] ...
- Failure!
--- Failure, aborting
Segmentation fault
[SuperSU] BonnyBedlamBoy:
updating to 2.81 via playstore on my galaxy tab 4 running lollipop as usual without issues. with oneplus 3t on latest beta lost root. same with 2.80 update via playstore. it only works updating with twrp to 2.80 that is still running well.

log says patching sepolicy failed (with 2.81) in twrp
[SuperSU] frov:
Just lost root on 5X with PureNexus after upgrading via playstore from 2.80 to 2.81...
[SuperSU] gthebest:
Hello. I update su in 2.81 but I can't update the su binary anymore. I try to reinstall it but with no success. I have the Huawei mate 8.
[SuperSU] Chainfire:
Thread is open again. Thank you for your patience.
[SuperSU] Goldenmeadow:
Optimizing app every boot on 2.82

Hi!

I have Nexus 4, stock ROM, rooted.

Couple days ago updated SU to 2.82.

Now every boot my phone is optimizing all 134 apps and it takes 30 minutes... Reverted to 2.79 - all good.

Am I along?

Thanks​
[SuperSU] xdapao3:
I went from SuperSU Pro 2.79 to 2.80 -> 2.81 -> 2.82 on both my smartphone and tablet (look at my sign for HW and SW info) without apparent problems (I also use AdAway BTW) BUT I am having problems with several Tasker's longer tasks, it seems that it "hangs" and executes them with long pauses between the various commands (on both my Note 3 and Tab S). I am not 100% sure that the problem started at the same time of the SuperSU updates but Tasker has not been updated in a while and I definitely didn't have this problem until recently. Can it be related to SuperSU? Most of those tasks do not execute commands which need root or invoke plugins which need root.

Is there some log/info that I may send to help identify the problem?

What's the best course of action, reverting to 2.79 or simply waiting for further updates..?

TIA
[SuperSU] moocou:
I don't have any problem as far as I can tell so there's no need to read the following!

But if anyone's feeling kind who might know the answer, here's my question...

The tl;dr is ... Should I update the SU binary? But I think you need more info.

I updated from 2.79 to 2.80 on playstore. Then realized maybe it was a bad idea from the comments. I then decided to ignore the "SU binary needs to be updated" notification. I've had no problems.

My phone is an S5 but it thinks it's an S7 or something because I'm using Phoenix ROM.

I avoided SU 2.81 but I've now updated to 2.82. Still no problems. I'm still ignoring the "update binary" thing.

I was trying all the time through this to avoid rebooting my phone but it does it by itself in my pocket sometimes and I'm 99% sure it has rebooted and, as I say, I don't seem to have any problems and my phone is still rooted.

Is it a good idea to update the SU binary?

Or is the fact that I never updated the binary (since I updated from 2.79 to 2.80 and then 2.82) the very reason that I haven't had any problems?

PS. Thanks, [MENTION=631273]Chainfire[/MENTION] and all who sail in SU. I've never had any complaints and I think you're handling this just right.

I'm a very dumb user. I don't even remember how I rooted the phone or if it was part of the ROM, so tbh I don't even know what SU is. It just seems to be necessary and therefore I'm grateful. But because I'm so stoooopid, I don't want to go down the re-rooting route if I can avoid it.

:)
[SuperSU] immi803:
Adaway system less mode broken

Root fine on one Plus 3t

But adaway system less mode broken :(
[SuperSU] mereu123:
Sony Xperia Z2 D6543

Android 5.1.1

Version number 23.4.A.1.232

Bootloop after binary update.

Back to version 2.79 with recovery.
[SuperSU] BLZv022z9EziSid4Gcsvujjfx:
Also a bootloop after upgrading on Play store...

However, I lost nothing, and I needed to upgrade my ROM. So thanks actually for forcing me to upgrade! :D
[SuperSU] Chainfire:
Which Android version is this?
[SuperSU] Goldenmeadow:
Sorry, 5.1.1
[SuperSU] Chainfire:
Well the first step is making sure it's related to v2.82. Try reverting to v2.79, and note if your problems instantly go away. If they do, please report to the SuperSU BETA thread and we can see about tracking and fixing the problem.

I always advise running the same GUI version as binary version. You're probably still on v2.79 binary. If you're scared to update the binary (you'll probably be fine), try going back to v2.79 of the GUI (so the notification disappears), then disable auto-updates for SuperSU.

Which exact SuperSU version?

The latest build should fix that - https://download.chainfire.eu/supersu

The latest build should fix that - https://download.chainfire.eu/supersu
[SuperSU] Chainfire:
(My) release notes for v2.82 posted here - https://plus.google.com/+Chainfire/posts/4iCwWhRLtoT
[SuperSU] mondohow:
See above.. Chainfire beat me to it...
[SuperSU] mereu123:
this file download.chainfire.eu/supersu (UPDATE-SuperSU-v2.82-20170528234214.zip) it's OK

the supersu.com/download (SuperSU-v2.82-201705271822.zip) version bootloop

Thanks!
[SuperSU] BLZv022z9EziSid4Gcsvujjfx:
As I indicated in my post, I'm not mad at all :) I'd like to thank you for all the work you've done to give us such a good tool instead. Everyone makes mistakes every now and then...

I flashed a new ROM (which I was delaying for ages), and I'll have everything back up and running in no time.
[SuperSU] luattic:
SuperSU 2.82 Test-1 Work on SM-T580 under Extremely V1.0 Rom

SuperSU-v2.82-20170528234214-TEST-1.zip

Tried with my SM-T580 under Extremely V1.0 Rom work well with more reactivity than the 2.79.

More details : Here.
[SuperSU] mondohow:
use the one Chainfire indicated above download.chainfire.eu/supersu (UPDATE-SuperSU-v2.82-20170528234214.zip)

https://download.chainfire.eu/supersu

It's his own compiled version that should help with Xperia devices.
[SuperSU] pizza_pablo:
I blindly updated SuperSU, the day before yesterday without even thinking about this thread I have been following. I just checked and it is v2.82, in both app manager and the app's settings tab.

I have not experienced any issues on Moto X Pure Edition 2015 running TruPureXMM v2.9 with February 2016 security patch.
[SuperSU] Licaon_Kter:
Yep, I tested and it does work ok, hope that @SuperSU Release updates the OP with that build.
[SuperSU] xalaros10:
On Sony Xperia Z1 Compact installed this zip file v2.82 from here https://download.chainfire.eu/supersu and it's OK. But didn't asked to update binaries and also although version number says 2.82 into application, in Android Settings/Applications/SuperSU says v2.78 Is it normal?
[SuperSU] MysteryIII:
Update through Playstore caused Bootloop. Flashing v2.82 zip file didn't fix it. Falshing v2.78 fixed it. If I flash v2.82 it will cause bootloop again.

€: Ok on Chainfire's page seems to be fixed version, while in OP still linked to "corrupt" Version. Please fix link in first post, as most people will directly use what is there.
[SuperSU] pendor24:
Hello for v 2. 81 or 2. 82

I exex the apk of the zip I install it, it asks to update the binaries, once done I flash the zip and everything rolls.
[SuperSU] stefguer:
v2.82 is available with 2 versions, what should be used ? what is the difference please ?

SuperSU-v2.82-201705271822.zip

http://www.supersu.com/download

UPDATE-SuperSU-v2.82-20170528234214.zip

https://download.chainfire.eu/supersu
[SuperSU] zputnyq:
This version seems better "UPDATE-SuperSU-v2.82-20170528234214.zip", especially when u use xperia device. As it's stated it contains some fix/fixes
[SuperSU] Benny100:
UPDATE-SuperSU-v2.82-20170528234214.zip working S7 Edge

Thx!
[SuperSU] Plex82:
I've a xiaomi mi5s and I've a bootloop after the binary update of the new SuperSU version. I tried to flash several older SuperSU's, but I'm still having a bootloop. I tried the Update of SuperSU 2.82, but no luck.

Does anybody know how to fix my mi5s?

I use chinese miui 8.5.2.0

I think android 6.0.1
[SuperSU] Idebutterpiep:
Can you write me the exact steps to root a Samsung S7 Edge.

Thank you.
[SuperSU] seffparker:
Can't remount / and /system as Read/Write

I have updated from v2.79 to v2.82 and noticed can't remount as RW anymore. Not sure its a bug as earlier in 2016 or a security feature.

Anyhow, managed to fix by a workaround by disabling Mount namespace separation and reboot.
[SuperSU] corkiejp:
You could restore a backup of boot and system partitions, if you have got them?

If not extract the boot.img from your rom zip and try flashing just that.

Which SuperSU zip version did you flash?

Make sure to use "UPDATE-SuperSU-v2.82-20170528234214.zip" which has fixes for devices that where bootlooping (xperia and some others).
[SuperSU] _Altmann_:
Can someone help me please?

I have a sony xperia e4 (E2105) I had root until SU 2.80

I rooted my phone a few years ago with Kingo Root. Back then it was simple to install SU. Kingo Superuser gave root permission to SU and then i just had to uninstall Kingo. But now Kingo Super User blocks SU. It doesn't give it root permission anymore. On the other hand this phone doesn't have a recovery mode so i cant flash any zip file. My question is, how can i re root my xperia e4 with SU?

Thank you!
[SuperSU] Ibuprophen:
The following link should have what you're looking for.

http://xdaforums.com/showthread.php?t=3567502

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise

---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------

The following link should have what you're looking for.

http://xdaforums.com/showthread.php?t=3573361

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Plex82:
I tried the UPDATE-SuperSU-v2.82 but still bootloops. I've solved the bootloops with the following steps:

1. Download flashable recovery zip of china rom 8.5.2.0

2. Install with recovery

3. Reboot

4. Flash UPDATE-SuperSU-v2.82

5. SuperSU works and rooted!
[SuperSU] Ibuprophen:
[MENTION=827636]Idebutterpiep[/MENTION], you stated S7 Edge and i tried to help you out by providing a link that states S7 Edge and you responded (very disrespectful with CAPS) by stating that it's not for the "Exynos".

First, you never stated that you were looking for the "Exynos" specifically since you only stated for the "S7 Edge".

Secondly, the XDA Forum has a specific area dedicated to your device. Why are you not searching/posting this question there?

I'm just beside myself right now...

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] pendor24:
At home it works on S7 edge (SM-G935F) and on S8 + (SM-G955F)
[SuperSU] immi803:
May security patch

[MENTION=631273]Chainfire[/MENTION]

Does it work with may security patch?
[SuperSU] derenio:
[MENTION=4295471]Goldenmeadow[/MENTION] same issue here. I've uninstalled/unrooted the 2.82 and installed the 2.79 through TWRP - everything works!

Also, I haven't cleared the cache and didn't have to go through the apps' optimization.
[MENTION=631273]Chainfire[/MENTION] does the apps' optimization is affected by the SuperSU updated?

So far all my apps requiring root work as before despite being optimized while 2.82 was installed.
[SuperSU] vegetaleb:
Am I the only one to have trouble with V4A and this SuperSu? It will freeze V4A and will reboot the phone every 2 minutes
[SuperSU] pizza_pablo:
This may not help, but at any rate, I'm using ViPERAtmos 4.8 Sony Beats Universal Edition, to I usually just use the Atmos, I just played a tune and manipulated Viper equalizer, with no I'll affects.....( or is it effects ? \_0_/ )