yashsingh1/xdaforums huggingface dataset:
[SuperSU] jcmm11:
If I had to guess (and it is totally a guess) it's expecting systemless and your attempt at manual install was system mode.

So why aren't you just flashing the zip? Oh and what version of Android are you running?
[SuperSU] spainter:
Which device are you trying to do this on? You show a Note 4 and a Note 7 in previous posts?

As you stated above you loaded the files from the arm64 folder. If it was the Note 4 you loaded the wrong binaries.
[SuperSU] ramrastus:
We can convert superSU as system app via TB?

I'm on latest SU 2.82 Test1 build.
[SuperSU] WiggleCat:
I don't have a custom recovery installed. I'm on 6.0.1.

---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------

It's the Note 7. If I mentioned the Note 4 previously in this thread it was an error.

6.0.1, and I don't have a custom recovery installed so I can't flash the zip file.
[SuperSU] miksontije:
[MENTION=631273]Chainfire[/MENTION]

First time i installed UPDATE-SuperSU-v2.82-20170526223454.zip with latest TWRP and i have supersu stop working error.

Today i installed SuperSU-v2.82-CCMT-GooglePlay.zip also trough TWRP and this version seems to work fine with my N5x.

Idont know where it stucked with first version.
[SuperSU] firebie:
Xperia Z1C - SuperSU-v2.82-20170528234214-TEST-1.zip - works
[SuperSU] Chainfire:
My first version still had the Feedback screen + required permissions, on some Android versions that could cause a crash if they were not explicitly accepted. The CCMT build is newer and has this removed, and thus the crash is gone. Good to know it works.
[SuperSU] Chainfire:
Great news, thanks, hoping for some more confirmations soon!
[SuperSU] CyberZeus1977:
Hi [MENTION=631273]Chainfire[/MENTION] do you know why I don't see 2.82 on Play Store but only 2.81? I'm currently on 2.79 SR3.

Thanks!

Sent from Enterprise bridge
[SuperSU] Chainfire:
It will be another day or so before it is available to everyone.
[SuperSU] Chainfire:
I don't have release posts etc yet, but I have updated the changelogs up to yesterday's test release: https://xdaforums.com/showpost.php?p=64916199&postcount=3

If you came from last stable, start at 'v2.79 CCMT', for most of you the changes start at 'v2.79 SR3', I guess.
[SuperSU] Arturiuz!:
SuperSU 2.82 works on Xperia X Performance Nougat 7.1.1 with AndroPlus kernel v23 on ftf 41.2.A.2.199.thanx [MENTION=631273]Chainfire[/MENTION] !
[SuperSU] Chainfire:
[MENTION=3507415]Chezbel[/MENTION] [MENTION=5043370]nitramus[/MENTION] [MENTION=646985]wetxxx[/MENTION]

As I've said before, I have been unable to replicate the problem on my HTC10.

It's a long shot, but you could try version v2.82-...-TEST-1 as described in this post, and let me know if it works? https://xdaforums.com/showpost.php?p=72466669&postcount=10109
[SuperSU] WiggleCat:
Is there a way to just flash the 2.79 ZIP without custom recovery or fasrboot?
[SuperSU] Chainfire:
If you have basic root working already you can try FlashFire.
[SuperSU] WiggleCat:
I can't use root with apps because I can't get the binary to work, but I can use root with ADB.
[SuperSU] samhhmobil:
[MENTION=631273]Chainfire[/MENTION]

this test version (SuperSU-v2.82-20170528234214-TEST-1.zip) seems to be corrected with the boot problem. My HTC One(M7) boots cleanly and root works (shortly testet with ghostcommander, AdAway and local shell, manually su).

Thanks a lot, you're great!

Stefan (samhhmobil)
[SuperSU] -DM-:
Can confirm as well, flashed SuperSU-v2.82-20170528234214-TEST-1.zip a few hours ago on an Xperia z5-premium (with RomAur and Zach's Kernel, still on MM 6.0.1) and everything running smooth...but then again didn't experience any root loss or bootloops as others have pointed out here when I updated from v2.79 SR-3 to v2.80, the only glitch I had at the time was a pop-up saying that superSU stopped right after every boot but that was about it, root apps behavior were normal...I did go back to 2.79 pretty much right away as precaution after checking this and the stable threads.

But once again the Test-1 is perfectly fine...

Thanks
[SuperSU] Chezbel:
I did mention this already, but with so many msgs it's not surprising if you didn't see it :). Here is what I said

UPDATE-SuperSU-v2.82-20170526223454 is working on HTC 10, Android 7, firmware 2.41.401.4, s-off, LeedDroid ROM. Adaway and TiBu appear to be fine.
[SuperSU] droseofc:
[MENTION=631273]Chainfire[/MENTION] I tried the test zip. I had already been in and out of that situation like 3 times trying diff ways to get systemmode all the way. The farthest I got is it saying it was installed to system already, but binary was occupied. I did notice something diff during install with the test zip. Something I did would cause certain su zip installations to freeze midway, like at extracting files or somewhere in there requiring a hardboot.

At that time other su zips would not install, this one would completely and boot up the system. The only way I have been able to get su to say it was system mode was by having magisk first otherwise it loses root during reboot after it closes from the install to system option.

I have a custom rom (moar note5 nougat), and the option of stock kernel or one that I am pretty sure is not patched for systemmode su. Previously, with skyhigh kernels I would be able to let it boot after installing kernel (systemless auto) and unroot through su, then flash systemmode in twrp.

It's not a huge huge deal at all ,just things like this make me want to figure it out otherwise I cant stop tryin, and i've already wiped and flashed probably 7 times so far. If you want me to test anything else feel free to let me know I'm at a good test time with no worries of losing anything on phone.
[SuperSU] long long:
Root
[SuperSU] NLBeev:
Nexus 6 stock 7.1.1 May update. Unencrypted data partition.

Playstore notification su 2.82 need binary update.

Flashed: UPDATE-SuperSU-v2.82-20170526223454.zip in TWRP-recovery 3.1.1.0.

EDIT

From time to time forced closes (as mentioned bij Chainfire).

Solved by flashing CCMT-Google play version 2.82.
[SuperSU] erfandl:
[MENTION=631273]Chainfire[/MENTION]

2.82 google play bootloop on xperia z ulta android 5.1.1. if you cant fix this problem just tell us. in this week I flashing my phones 10 times
[SuperSU] ZRK_NanDRD:
Read this article

*Chainfire Recommends Staying in SuperSU

2.79 for Xperia Users*

https://www.xda-developers.com/chainfire-recommends-staying-in-supersu-2-79-for-xperia-users/
[SuperSU] Chainfire:
I asked you in an earlier post to try this version: https://xdaforums.com/attachment.php?attachmentid=4164510&d=1496008012
[SuperSU] koekoek91:
You can't expect [MENTION=631273]Chainfire[/MENTION] to magically fix the issue without any help from us users.

If you had read your mentions and had read back in this thread, you would know that Chainfire needs help from Xperia users to track down the issue. I myself have mentioned you and Chainfire did aswel.

He even mentioned you only a few posts above yours, on this very same page, where he mentions you and links to a post where he has attached a NEW test version for Xperia users to test.

Please start to actually read a few posts or preferably even a few pages back to see how progress on fixing issues has been going, and try to actually contribute to help fix the issue.... instead of getting frustrated and blaming him for wasting your time :rolleyes:
[SuperSU] shoey63:
Lol
[SuperSU] jcmm11:
You have adb so you can unzip the file into a tmp directory and then manually run the update script. I saw instructions for this from Chainfire just recently, somewhere. But basically push the

SuperSU.zip to /tmp

unzip the file

Run

/tmp/META-INF/com/google/android/update-binary 3 1 /tmp/SuperSU.zip

That should do the trick. If I have a mistake there hopefully someone will correct it. 6.0.1 defaults to systemless mode.
[SuperSU] corkiejp:
Thank you for clarify that point, if i had not read that I would have installed your first version.

Thank you for posting the changelogs.

Tested the CCMT (SuperSU-v2.82-CCMT-GooglePlay) build on both RN3 (Kenzo - xiaomi.eu 7.5.25) and Nexus 9 (latest 7.1.1 security build). No problems to report!

Note, updated from 2.79-SR3 and haven't used the problem versions.

Thanks
[SuperSU] Jengo:
This version SuperSU-v2.82-20170528234214-TEST-1.zip works on Sony Xperia Z1 stock 5.0.2 (14.5.A.0.270) without any bootloop. :good: Thanks very much! :)
[SuperSU] Chainfire:
That was an entirely different situation in recovery mode, where the available binaries and command are different - the install scripts depend on these.

There's a good chance those instructions will not work (they might though, it's just pretty likely there will be an error somewhere)
[SuperSU] tramp20:
I can confirm too that SuperSU-v2.82-20170528234214-TEST-1.zip works on Sony Z1c Android 5.1.1 ( no boot loop, AdAway ok).

Flashed with TWRP.

Thanks to Chainfire
[SuperSU] WiggleCat:
I'll give this a try. Thanks.
[SuperSU] skyhirules:
At last! For the first time after 2.79 stable, no boot loops with 2.82 TEST 1, on my Xperia Z1 Compact with stock Android 5.1.1! All the 2.79 SR's were boot looping, as I've mentioned before.

Good job chain! I hope you don't spoil it in the final stable release! ?
[SuperSU] jcmm11:
[MENTION=7539361]WiggleCat[/MENTION]

At a (very) quick look through the script he's likely to run into trouble if the script decides it needs to remount system as rw, since there's no /etc/fstab.

The lack of /sbin/sh shouldn't cause a problem since it should just default to /system/bin/sh. TWRP using ash as opposed to stock using mksh shouldn't cause a problem (at least I didn't spot anything obvious that won't work under mksh). I guess we'll find out. Might be good to know for some future situation. Nothing else jumped out at me, but as I said it was a very quick look and I could easily have missed something.
[SuperSU] ratelutz:
:good: SuperSU-v2.82-20170528234214-TEST-1.zip workes on my Xperia Z2 Tablet and my Xperia Z5 :good:
[SuperSU] habylab:
2.82 fixes my issues.
[SuperSU] Sachin ET:
Play store update makes Viper4Android non functional.
[SuperSU] corkiejp:
Which version did you get from the playstore? If it is still v2.80 or 2.81 then problems have been fixed with v2.82.

Check chainfire's post for information and download links. Or my last post on the previous page also has the links.
[SuperSU] Alxoom33:
SuperSu 2.82 Playstore versions working well on Nexus 6 running 7.1.1 Stock, with EX 4.21 kernel and Pixel C Tablet running Stock Android O Dp2.
[SuperSU] Chainfire:
I can't promise anything...
[SuperSU] B1tman1ac:
Note 3 Lollipop

Upgraded to v2.82 on Note 3 Stock Lollipop 5.0 via app update from Google Play and had booting issues (would not boot into decryption password screen, continous Samsung Logo plus only made the usual Samsung boot sound for half a second). . . reverted to 2.79-SR3 via TWRP and it booted properly.
[SuperSU] Jengo:
Could you perhaps elaborate (shortly) what the problem was? I’m curious and want to learn something. :angel:
[SuperSU] truelies1:
HTC M7 with Android 5.1 using twrp can't boot on both 2.82 binary and 2.79 sr3 binary, stay on animation. 2.46 boots without problem.
[SuperSU] Chainfire:
On some devices, the selinux policy patch call at bootup wasn't performed. Oversight during refactoring.

Did you try this version? https://xdaforums.com/attachment.php?attachmentid=4164510&d=1496008012

Did you try this version? https://xdaforums.com/attachment.php?attachmentid=4164510&d=1496008012
[SuperSU] CyberZeus1977:
Updated my Nexus 6P stock 7.1.2 from 2.79 SR3 to 2.82 via Play Store. All ok!

Thanks [MENTION=631273]Chainfire[/MENTION]

Sent from Enterprise bridge
[SuperSU] dev70194:
Why don't you just install SuperSU from the play store? Having all apps allowing access without a prompt is a huge security vulnerability.
[SuperSU] zeugme:
Which version should I flash through TWRP on Google Pixel (sailfish)?

Thanks!
[SuperSU] SAGI1:
Can not root device N7100 after removing magisk

Hey all, I have some problem of root my device with super su, after removing magisk 12.0

I have Samsung Galaxy Note 2 n7100 device. [MENTION=631273]Chainfire[/MENTION] or someone can you please advise what I am doing wrong

I am using:

twrp 3.0.2.0

AICP ROM 28/05/17 NOUGAT ROM - it include magisk 12 installed

open gaps 7.1 pico

Magisk uninstaller

Supersu v2.8.2 google play.zip

Steps to reproduce:

1. install AICP rom 28/05/17

2. Install Gaps

3. Check that the phone boot up -> phone is rooted with Magisk 12 (buit in in rom)

4. Navigate to twrp

5. Install supersu -> Phone is rooted with also super su

6. Navigate to twrp

7. Install magisk uninstaller -> wipe cache - phone is uo No root

8. Navigate to twrp

9. Install supersu

Expected results:

phone is rooted with supersu

Actual results:

Phone not rooted

Link to rom: http://dwnld.aicp-rom.com/?device=n7100

Link to twrp: https://dl.twrp.me/t03g/

Link to openGaps arm 7.1: http://opengapps.org/

Link to magisk uninstaller: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[SuperSU] :
Report Regarding Samsung Device:-

Latest SuperSU V2.82 Google Play Version Works Flawlessly On Samsung Galaxy Note 5( Tested And Worked As Expected On S8+ Ports Using Device N920G) Since Previous Versions Were Causing Losing Of Root Access With Bootloops Too In Some Cases And Hats Off To Beloved [MENTION=631273]Chainfire[/MENTION] To Provide Quick Assistance Towards Issue And Sorting Out It As Quick As Possible

Thanks Again [MENTION=631273]Chainfire[/MENTION] And Whole SuperSU Development Team
[SuperSU] wetxxx:
I uninstall 2.82 and than from TWRP install this 2.82 Test-1 version. Android was standup but I can`t see SU apk. So I get from Play store and it seems good. I`m testing :)
[SuperSU] ocd_amp:
If one wants to stay with Version 2.79 (last known version to have worked for my device(s)) then how can one Avoid being pestered to upgrade from the Google Play Store? The Flashable Zip seems to contain the same signature which makes Google Play Store recognize that you have it installed and then shows the update. The funny thing is after all this time, Google Play Store still does not allow functionality to HIDE updates. Really a piss ant company.

So where can one obtain version 2.79 which will not be recognized by the Play Store?
[SuperSU] Wolfcity:
Just turn off auto update from PlayStore. For all apps (in PlayStore settings) or just for superSU (3dot menu in the upper right of the app).
[SuperSU] bemagrp:
https://xdaforums.com/showthread.php?p=72429329

You have to flash SuperSU-v2.82-CCMT-GooglePlay.zip through twrp, then vsb version 8.

---------- Post added at 09:02 PM ---------- Previous post was at 08:56 PM ----------
[SuperSU] truelies1:
HTC M7, the 2.82 test edition works, all others are boot loop. Thanks
[SuperSU] Ps24u:
SuperSU-v2.82-20170528234214-TEST-1.zip works Ok on my Z1C as well, thanks Chainfire!
[SuperSU] Schleiereule:
I want to add another positive report: I experienced the boot loop issue as well, on Xperia Z1C, this solved it for me. Thank you!
[SuperSU] B1tman1ac:
No I originally tried the one from the play store.

But I downloaded this 'test1' version and applied it via TWRP recovery and it worked. I am able to boot into system.

Only 2 issues:

1. Had some minor system ui not responding upon initial boot up which I solved by closing the system ui when it asked me too but I've had this problem before so I don't think it's related to the update or necessarily Super SU.

2. The touch key fw version gets out of sync on every Super SU update (not just this one) I apply so the back key does not work. The fix is to go into the fw update screen (*#2663#) and update the touch key fw so that the physical part # and software both read 0x10.
[SuperSU] nitramus:
For me 2.82 from play store works just fine. Do you still want me to try it out? Only 2.81 did not work for me. Installed app and binary just fine but lots of apps where acting up.
[SuperSU] calikevin:
Root itself works with 2.82 for me, but it breaks functionality for RootSwitch which is unacceptable for me. I'll be staying on 2.79 indefinitely until this little bug is fixed.
[SuperSU] osm0sis:
He said he'll look into it once he gets the Xperia/HTC thing sorted out. For now you can turn off mount namespace separation as a workaround. It's some kind of remaining regression in the sdcardfs code that broke su.d.
[SuperSU] yung40oz84:
Using SuperSU-v2.82-20170528234214-TEST-1 on pixel XL and no issues thus far.
[SuperSU] DannyR49:
Reporting on latest test with:

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

Device:

Xiaomi Redmi 3 w/- CM14.1 Nougat 7.1.1

Working again from .AU down under with TEST-1

version.

Previous tests:

v2.82 fixed loss of root (SuperSU

-v2.82-CCMT-GooglePlay.zip) after going back to 2.79sr3 first to confirm regain of root.

PS: I wish someone could address SAMBA not running under Nougat:

XDA post #1083:

http://goo.gl/ZThzfm

Many thanks to [MENTION=631273]Chainfire[/MENTION].
[SuperSU] GopalKaul:
Hi [MENTION=631273]Chainfire[/MENTION]

Updated from SuperSU 2.79 SR3 to 2.82 via app. 2.80 and 2.81 too didn't cause issues with me.

Oh, BTW I have a nexus 5. Android 7.1.2, Dark ROM based on lineage OS.
[SuperSU] Didgeridoohan:
You really shotgunned this message out there, didn't you? :laugh: Anyway...

Recovery log from the last, failed, flash of SuperSU might shed some light on the issue.
[SuperSU] Adarsh balu:
[MENTION=4843136]flroots[/MENTION] Hey I'm using Moto g4 plus (XT1643)

Just as promised i tested the new v2.82 using play store update and is working well and i did not lose root . Please again that is all i can say i dont know how you lost root.

Thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] hbbxmjbb:
If 2.81 or 2.82 could make the phone not to enter recovery and fastboot?I met someone using Lineage OS couldn't enter those modules.
[SuperSU] calikevin:
You're saying 2.82 should work with RootSwitch as long as that option is unchecked? I will have to try that and see. What's the HTC thing exactly, would it affect my M9 or only newer models?
[SuperSU] osm0sis:
It's the bootloops we've been discussing. Yes, RootSwitch works fine with that unchecked (reboot first).
[SuperSU] Chainfire:
Release notes for v2.82 - https://plus.google.com/+Chainfire/posts/4iCwWhRLtoT
[SuperSU] C0rneille:
2.82 on Nexus 9

SuperSU 2.82 from the Play Store on Nexus 9 (flounder) 7.1.1 N4F27B: successful update of binary, restart, no trouble, AdAway works.
[SuperSU] TonikJDK:
FWIW, updated from 2.79 SR3 to 2.82 via the playstore on a Pixel Xl on May N with zero issues.
[SuperSU] Licaon_Kter:
I did raise a flag, and asked again, but I know you're a busy guy and 2.79 worked ok... I did subscribe here just in case you would answer.

Hope this is now fixed, I'll go and update...
[SuperSU] WiggleCat:
This is what I got.

D:\Dallas\Documents\Things\Odin3 v3.12.3\platform-tools>adb root

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

D:\Dallas\Documents\Things\Odin3 v3.12.3\platform-tools>adb root

D:\Dallas\Documents\Things\Odin3 v3.12.3\platform-tools>adb push SuperSU.zip /tmp/install.zip

[100%] /tmp/install.zip

D:\Dallas\Documents\Things\Odin3 v3.12.3\platform-tools>adb shell

root@graceqltespr:/ # cd /tmp

root@graceqltespr:/tmp # rm -rf install

root@graceqltespr:/tmp # mkdir install

root@graceqltespr:/tmp # cd install

root@graceqltespr:/tmp/install # unzip ../install.zip META-INF/*

/system/bin/sh: unzip: not found

127|root@graceqltespr:/tmp/install #
[SuperSU] WiggleCat:
I created the directories manually and pushed the folder instead. Now I get this.

root@graceqltespr:/ # cd /tmp/install/

root@graceqltespr:/tmp/install # chmod 0755 META-INF/com/google/android/update-binary

root@graceqltespr:/tmp/install # META-INF/com/google/android/update-binary 3 1 /tmp/install.zip

/system/bin/sh: META-INF/com/google/android/update-binary: No such file or directory

1|root@graceqltespr:/tmp/install #
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], first of all, no apologies needed from you. It was an unforeseen/unfortunate oversight that does happen and your quick/swift action with supporting this only reflects credit upon yourself and the developments you provide. Thank you for this!!!

Now I have a 2 quick questions...

What is the difference between the superuser app/apk file within the common folder of the SuperSU Flashable zip and the SuperSU app/apk within the Play Store?

And a quick side/caveat question off the first question...

Does the superuser app/apk from the Flashable zip also include all the fixes/changes that the Flashable zip itself have/include?

Thank you very much!!!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Sr. Zé Alguém:
It is normally the same, when it is compiled by the same person. For example, the zip from the SuperSu site contains the same apk from PlayStore, probably because both are compiled by CCMT, therefore builds made by Chainfire will be different.
[SuperSU] WiggleCat:
I managed to get my root (SU binaries) back using ADB with the script i forgot I still had that installed SuperSU in the first place when I installed the rooted debug ROM. No ROM flashing, no wiping data, no screwing anything up.

Now the problem is I'm on 2.74 without pro. If I update to 2.81 both regular and pro using the APKs I have will it mess everything up again? 2.80 and 2.81 both worked on my device, it was 2.82 that broke the binaries.
[SuperSU] Sr. Zé Alguém:
[MENTION=7539361]WiggleCat[/MENTION]

Now that you have root working you have options:

1. Don't mess with what is working properly and don't try things that can break your configuration.

2. Flash TWRP, make a backup and then flash SuperSU Zip or another ROM with su: https://www.xda-developers.com/how-to-install-twrp/

3. Don't do any of the above and read a book about Android (or become friendly with Google).
[SuperSU] WiggleCat:
I can't actually flash TWRP because I'm pretty sure my bootloader is still locked. When I boot into bootloader mode via recovery it just goes into download mode without a warning screen beforehand, which is also why fastboot wasn't an option.
[SuperSU] WiggleCat:
Since it DID work last time I figured it would this time too and tried it. Worst case scenario I use ADB's root to run the script a second time since there wasn't any boot issues the first time either. Luckily I was right.

Im going to be staying on 2.81 until the next version is at least stable enough that there's no more reports about root being lost.

Edit: I think I found out why it was screwed up. Once the binaries stopped working I was forced to uninstall to downgrade. While going through the settings I found this little gem. (Second screenshot.)

Root requests were being denied due to being uninstalled with a PIN enabled, however with the binaries no longer working there was no way to enter settings to remove the PIN because the app would just close itself. The older versions of SuperSU couldn't see I was rooted because they were being denied root access. The script forced it in using ADB's root access, which doesn't require the binaries and then installed the binaries with the older app.

For people like me who have a PIN enabled, a future (or even the current) screw up with the app update like this could cripple most of them permanently if they ever uninstall to downgrade, which will probably be the first thing they do. That's probably something that needs to be addressed. I happened to have a permanently rooted ROM and a script to install an older version of SuperSU with the binaries on this particular ROM, there's not many others that also have this convenience.
[SuperSU] TonikJDK:
Have you considered a Beta program here...where you post up the apk and we test it. You will get faster feedback and can pull it in a heartbeat. Then increment it one version when you put it on the playstore so we all get back on that system?
[SuperSU] jcmm11:
The SR releases are betas. This thread is the beta thread.
[SuperSU] WiggleCat:
[MENTION=631273]Chainfire[/MENTION] Not sure if an edit would give someone a tag notification so I'll just tag you here instead since I forgot to in the quoted post.