yashsingh1/xdaforums huggingface dataset:
[SuperSU] TonikJDK:
And we tested them, all was good...this was all a freak accident with the build process.

Yea, I remembered all that a split second after I posted . :laugh:
[SuperSU] jcmm11:
The OP always gets a notification when someone posts to his thread.

Glad you got things squared away. Unzip is a busybox applet, not found in the default Android commands. You could have setup busybox temporarily in case you ran across other commands in the same situation.

Not sure why you got file not found. Could have tried dropping into the directory and executing from there, but in any case glad it's all working now.
[SuperSU] WiggleCat:
I actually did try that and still came up with the file not being found. Worst part is I had Busybox On Rails installed but wasn't sure if it was interfering or not so I manually removed it a few days ago.
[SuperSU] Srandista:
Yes, it's working, I've just tried that on my Nexus 5 and Nexus 7. Thank you [MENTION=4544860]osm0sis[/MENTION] for workaround!
[SuperSU] samhhmobil:
MANY thanks to [MENTION=631273]Chainfire[/MENTION] for this great work.

If I ever can help, I'm willing to do so.

But... may I ask, when will be the stable/corrected version in the PlayStore? I just can see yet the 2.82 version from May 27th. But that one is the last with the bootloop issue.

Thanks again,

Stefan (samhhmobil)
[SuperSU] Pkt_Lnt:
Thousands of us have downloaded and flashed with no problem. You have a bad download, try again.
[SuperSU] dunghnguyen:
I had it 2.35 updated automatically this evening on Nexus 4 :p
[SuperSU] Manuel15:
I think he meant that you have wiped /sistem
[SuperSU] Ben36:
Turn off data saving in chrome

Sent from my Android 5.0 Nexus 5
[SuperSU] habylab:
Download is always unsuccessful for me, never had this issue before!

Sent from my Nexus 9 (2015). My phone is a HTC One M8! Tapatalk'd
[SuperSU] shobuddy:
So whats are the differences, advantages/disadvantages of installing as a system app?
[SuperSU] Teenight:
Files in init.d doesn't work after every boot. Also, can I delete 99daemonsu in init.d folder?
[SuperSU] Paschfire:
it will free up a few mb's of space on the Data partition for apps, downloads, pics etc. placing superSU in the system partition, other than that I am unsure of any other benefits. also it is less likely to be accidentally uninstalled whilst installed on the system partition as this option is unavailable to system apps from the settings menu.
[SuperSU] dunghnguyen:
2.36 updated automatically ...well done ! Tks dev team !
[SuperSU] ramjet73:
AFAIK [MENTION=631273]Chainfire[/MENTION] == "dev team". ;)

ramjet73
[SuperSU] Ben36:
Go dev team!

Sent from my Android 5.0 Nexus 5
[SuperSU] fredzen14:
How was your p880 brother?? ?

Is she doing fine currently?
[SuperSU] hairdewx:
hmmm I am trying to side load:

adb sideload UPDATE-SuperSU-v2.36.zip

and I get this error:

E: failed to verify whole-file signature

E: signature verification failed

Installation aborted

This is on an ADT-1 running lollipop.
[SuperSU] egingell:
Can't flash using stock recovery.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Gunthermic:
SuperSU 2.36

I know we can include the whole zip to install SuperSu when flashing the zip.. But I like to manually add it myself..I am running into a road block...

Upon first boot up no matter how i add the files, it always wants to update the Binaries...

Structure:

/system/app/Superuser.apk

/system/bin/install-recovery.sh

/system/etc/install-recovery.sh

/system/etc/init.d/99SuperSUDaemon

/system/lib/libsupol.so

/system/xbin/daemonsu

/system/xbin/su

/system/xbin/supolicy

Thats what I added to my Custom ROM.. Every single fresh flash, SuperSU wants to update Binaries and renames daemonsu to daemonsu_old..

Any help and real suggestions..
[SuperSU] canodroid15:
SGH-i747 running unofficial CM12 rooted with 2.36 for 2days no problems thanks [MENTION=631273]Chainfire[/MENTION]!!
[SuperSU] igormz:
Secure Settings and SuperSU problems

Hi, I'm trying to enable system+ module on secure settings, but SuperSU 2.36 ungrant acess to secure setings.

In SuperSU log:

FIRST PAGE

Secure Settings @01/12 08:34

pm grant com.instangibleobject.securesettings.plugin

android.permission.WRITE_SECURE_SETTINGS

exit

sh: <stdin>[1]: pm: not found

SECOND PAGE

id

exit

uid=0(root) gid=0(root) context=u:r:init:s0

My phone is a Samsung Galaxy S3, with CM11 (android 4.4.4) and root acess.
[SuperSU] Clauu:
Hello, n5 + 5.0 and latest supersu i can't touch any option 'grant' or 'deny' at the message prompt.. is not grayed it looks normal but i just can;t select anything, this is happening after fresh install of lolipop.. on kitkat i neved had this issue :)
[SuperSU] greyhd:
Do you have Lux autobrightness? If you do just whitelist SuperSU or disable lux.
[SuperSU] egingell:
... literally every page of this thread in the past two months or more.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] stefguer:
Dear Chainfire : 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] corkiejp:
The version on chainfire's site has the patches for devices that where bootlooping and is the correct one to use! Question was already asked before in the thread.
[SuperSU] osm0sis:
He explained it in his post. The timestamp is one day later for the UPDATE- prefixed one now hosted on his site, and it contains the Xperia/HTC boot loop fix.

I'd pretty much always recommend using the one with the newest timestamp.

Edit: Sniped by corkie! ;)
[SuperSU] Ibuprophen:
If you look at the first 8 numbers (aka Timestamp), following the version, it will reflect the YearMonthDay.

So the first 8 numbers on the first version you listed would reflect:

20170527 = 2017May27

The second one you listed would reflect:

20170528 = 2017May28

Also, the "UPDATE" releases are typically released after the the ones that don't have that indicator. Anything released afterwards are typically numbered in sequence to help prevent any confusion in the order of releases.

I hope i clarified it okay.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] dinkoh:
Anyone experiencing occasional delayed notifications on their pixel XL phones after the updated 2.82.
[SuperSU] Dallebull85:
New version out? I keep getting notifications to update the Binary, was working flawless until now. Latest RR (2.8.3) and running superSu 2.82
[SuperSU] 14mRh4X0r:
Just installed 2.79-SR3 on my Moto G5 Plus, but I'm getting this error in my crash log:

06-01 11:45:43.183 7424 7424 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-01 11:45:43.183 7424 7424 F DEBUG : Build fingerprint: 'motorola/potter_n/potter_n:7.0/NPN25.137-33/35:user/release-keys'
06-01 11:45:43.183 7424 7424 F DEBUG : Revision: 'p3b0'
06-01 11:45:43.183 7424 7424 F DEBUG : ABI: 'arm'
06-01 11:45:43.183 7424 7424 F DEBUG : pid: 7423, tid: 7423, name: sush >>> sush <<<
06-01 11:45:43.183 7424 7424 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7f555004
06-01 11:45:43.184 7424 7424 F DEBUG : r0 a8ca0000 r1 a8ca0004 r2 00010101 r3 a8c97008
06-01 11:45:43.184 7424 7424 F DEBUG : r4 7f555004 r5 00000058 r6 7f583060 r7 beaa5ab0
06-01 11:45:43.184 7424 7424 F DEBUG : r8 00000000 r9 00000000 sl beaa5bab fp beaa5aa4
06-01 11:45:43.184 7424 7424 F DEBUG : ip a8e96860 sp beaa5948 lr a8e62985 pc 7f557800 cpsr 600e0830
06-01 11:45:43.185 7424 7424 F DEBUG :
06-01 11:45:43.185 7424 7424 F DEBUG : backtrace:
06-01 11:45:43.185 7424 7424 F DEBUG : #00 pc 00002800 /su/bin/sush
06-01 11:45:43.185 7424 7424 F DEBUG : #01 pc 000245ab /su/bin/sush
06-01 11:45:43.185 7424 7424 F DEBUG : #02 pc 0001b73d /su/bin/sush
06-01 11:45:43.185 7424 7424 F DEBUG : #03 pc 00016cfd /system/lib/libc.so (__libc_init+48)
06-01 11:45:43.185 7424 7424 F DEBUG : #04 pc 000026a0 /su/bin/sush

Did I do something wrong during the install, or is this an issue with SuperSU?
[SuperSU] jcmm11:
2 things. Latest is 2.82 get it here

https://download.chainfire.eu/supersu

Next thing. Recovery (TWRP) log from the install would be much more helpful than crash log. (Or flashfire log if that's what you used)
[SuperSU] 14mRh4X0r:
I want a systemless root though, which 2.82 isn't (as far as I'm aware). The install log showed nothing out of the ordinary, i.e. the basic remounting, patching boot.img, etc.
[SuperSU] ktmom:
What makes you think 2.82 isn't a systemless version? That have all been since something like 2.46.
[SuperSU] iamaniff:
Just update from playstore, work without issue on Android O DP2
[SuperSU] fjelsten:
This fixed the bootloop issue for me on Xperia Z3 5.1.1. (23.5.A.0.575).

However, the SuperSU app is missing - can I install the version at Google Play?

Thanks :good: (although I did spend the evening fixing this instead of going for a run - but I guess you cannot complain when you are using free software :D )
[SuperSU] osm0sis:
Try `adb uninstall eu.chainfire.supersu` per Chainfire here: https://xdaforums.com/apps/supersu/...78-release-t3452703/post72428986#post72428986

Then you should re-install SuperSU v2.82 using Chainfire's build, since it is the newest stable (newer than Play Store) and contains the Xperia/HTC bootloop fix: https://download.chainfire.eu/supersu
[SuperSU] corkiejp:
[MENTION=2835223]fjelsten[/MENTION] The apk is in the common folder of the supersu zip. You can install that, not the play version.

And as [MENTION=4544860]osm0sis[/MENTION] said use the latest version he linked!
[SuperSU] fjelsten:
I just found out I have lost root. What's the easiest way of getting it back?

Do I need to do a full re-root process or can I just flash some Super SU ?

Thanks in advance
[SuperSU] shaggyskunk:
What device - How did you update SuperSU and what version of SuperSU? Providing in is always a good thing ;)
[SuperSU] corkiejp:
Instead of posting again, you would have got your answer if you read the replies to your previous post!
[SuperSU] fjelsten:
Installing the APK from the TEST1 zip file seems to have restored root. Thanks a bunch
[SuperSU] Chainfire:
Normally, the ZIP from the STABLE thread and the APK in the Play store are identical. The binaries inside the APK are also identical to the binaries in the ZIP. If they are not identical, it may be due to build system difference (the ZIPs posted here are built on my PC, the APK posted on the Play Store is built on one of CCMT's PCs), but if you pull them through a decompiler you should end up with the same code.

In this case I have posted a newer version here than on the Play Store with an additional bugfix for bootloops. Normally when this happens it gets labelled SR1, but the actual SR1 release is very close to done (I thought to have released it by now, but more Pixel/ODP2 issues delayed it), so this is very temporary.

Updating the APK through the Play Store only includes the bugfixes that are inside the APK or binaries. It is not uncommon for more fixes to be part of the ZIP installation script (though this is often limited to support for new devices), these fixes will only be applied if you re-flash SuperSU from ZIP.

At some point, APKs posted here and APKs posted on the Play Store may diverge. The Play Store rules and restrictions are becoming ever tighter, and I actually had to scrap some planned features recently because of it. I have also been considering porting the code to modify the boot image to SuperSU itself, and let it re-flash itself (ZIP like) right from the GUI. But this is one of those things that goes directly against several Play Store rules. It would makes sure you can always get the latest fixes, though.

I don't think CCMT is going to do another stable roll-out just to fix this issue. It will be a while.

Not me, but you're not the first I hear say this. Are there any more details you can give? From how long after boot? Which app notifications? Etc? The more words the better.

Please try v2.82 from https://download.chainfire.eu/supersu

If the problem persists, report back.

Thanks, but which device? Not all O DP2 devices are supported.
[SuperSU] krule031:
Sorry if I'm being rude for not reading past posts, but, is Xperia bootloop problem fixed? :fingers-crossed:

If yes, what do I need to do so I don't experience any problems? I'm currently on SuperSU 2.65 lol
[SuperSU] osm0sis:
Read the post literally above yours.
[SuperSU] napolionnardo:
Hi, Chainfire. Can Root the Samsung S5 G900A with Android MM 6.0.1?
[SuperSU] veez21:
Of course you can. Afaik, chainfire has a lot of samsung devices (including s5 i suppose)

EDIT: i googled it and it's at & t, which, i think is locked? don't bother this reply anymore :o
[SuperSU] garreth83@gmail.com:
Hey guys,

I kinda confused which SuperSU version should I flash for my device if I wanted it to be in Systemless mode?

1. Stable version - SuperSU v2.79 SR3

or....

2. BETA version - SuperSU v2.8.2

I also intend to flash the latest RamKernel RC3 kernel so I need which version works best with this kernel.

See below for information about my device:

Model:	SM-N910G

Model name:	Galaxy Note4

Country:	Singapore

Version:	Android 6.0.1

Changelist:	7899277

Build date:	Thu, 17 Nov 2016 06:31:12 +0000

Security Patch Level:	2016-11-01

Product code:	XSP

PDA:	N910GDTS1DPK3

CSC:	N910GOLB1DPG1

Thanks guys!
[SuperSU] napolionnardo:
I do not understand, how are you blocked?
[SuperSU] veez21:
not blocked..

Is your bootloader locked, cause if it is then you can't install supersu.. since you're running marshmallow
[SuperSU] napolionnardo:
And can something be done about it?
[SuperSU] Cluey:
Please highlight to them how bad that choice is.

The Google Play Store should be the safest place to get an update from, but the version on it will still screw people over.

I didn't update as soon as it was available as I was busy away from home, by the time I got to it it had that reassuring note:

V2.82 Bug Fix on installation error and disable feedback.

I figured this was safe so I installed it.

I definitely made a mistake here as I didn't back up beforehand and it appears that my recovery has gone missing too. I remember the Sony phones randomly losing it sometimes, I never managed to work out what triggered it, but as my phone has been set up and running how I want it to for so long I haven't been following things on XDA.

I've got the phone up and running again, haven't lost any data (I think) but I'm missing root now and to get that back I'll have to jump through lots of hoops. I suspect I'll be downgrading to an exploitable version and then upgrading while keeping root.

Irritatingly the main thing I use root for is removing the bloatware, other than that I don't really need it. In getting it up and running again I've put all that bloatware back on. :confused:
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], I had a feeling that, what you described, was the case but, i really didn't want to state my assumption as a fact without your confirmation on whether it was true or false.

Though, i could be wrong with this but, what had prompted me to ask it that the Play Store version from CCMT is really "counter productive" on their part. If you had released a newer version for testing, as well as to prevent the Play Store updates from undoing your work, to help those who's experiencing issues, then it seems that CCMT will push a matching version out just to match yours.

Also, it just comes across to many users that CCMT knows that your providing the actual support for any/all the issues that many users are having via your Test, Beta and Service Releases, it just doesn't seem right that they are just sitting back while you're doing the work to figure it out and then provide them with the work for a stable release. This compounds the negative feelings/thoughts that many users may have against CCMT and NEVER to you as being the REAL expert regarding SuperSU.

Anyways, i understand you completely, my friend!

When it comes to the app/apk files, located within the common folder of the flashable zip files...

1) ONLY the stable releases will match the app/apk releases within the Play Store because it was compiled by CCMT.

2) ONLY the Test, Beta and Service Releases do not match the Play Store releases because they were compiled by you, personally, and include the changes/fixes that are present within the Test, Beta and Service Releases the app/apk are located within.

Thank you very much for your time, understanding and support for your hard work and determination with SuperSU!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Chainfire:
Yes, if you use the ZIP directly from my site ( https://download.chainfire.eu/supersu )

However, 2.65 is old. It is dozens of releases back. If you're comfortably running that now, why upgrade?

Not by any officially supported (by me or CCMT) means. It has a locked bootloader.

There may be an unlock, an engineering kernel, or whatever - but I don't deal with locked bootloader devices, period.

All SuperSU versions for a long time are systemless by default on all Android 6.0+ firmwares.

Some custom firmwares/kernels tell SuperSU to run in system mode, but this is uncommon.

Look, I understand this is frustrating, but at some point this conversation has to end. This issue doesn't affect that many users (relatively), and statistically most users that will run into the issue will have hit it by now (the damage is already done). Any binary update is risky, and a percentage is guaranteed to fail (thousands of different devices running ten times as many different firmwares with all sorts of apps and hacks installed that may interfere, it is quite literally impossible to properly test for).

The debate is really if the number of people that will fail binary upgrade with a new release is greater than the number of people expected to still hit this issue, and honestly I'm not sure which number is higher.

Even if I were to push it, and I am able to theorize a better fix (perhaps only update binaries on affected devices ?), that will still need to be agreed upon, built, tested, and officially released. Even with a herculean effort, that will be an earliest possible roll-out at the end of Wednesday next week, and I doubt that's even achievable even if I work through the weekend, which I doubt I will. This means again a larger portion of users who will run into hit, will already have run into it.

As I tried to explain above, a Play release is always difficult. A knee-jerk roll-out can be as bad as it can be good. There will be an update to the Play Store of course, but it may not come as quickly as some want.

As for CCMT, they do have their own support forum (hence their low activity here), but you would be mistaken if you think that they do not read the STABLE and BETA posts. As I also stated in a previous post, their guys also worked through last weekend to try and fix the problem. They're not just sitting back, but even if they were, I am compensated for my time.
[SuperSU] Ibuprophen:
I appreciate your clarification and i had based my opinion, purely, on appearance rather than on any facts and I, personally, am aware of the fact that something is being done in the background on top of your efforts to help CCMT out in any way on providing an accurate and stable release.

Your an amazing developer who always provides outstanding and quality software, apps, zips, etc... on top of support for those who need it. This is why I purchased your work a long time ago via the Play Store and a donation (when I can) as well.

I hereby proclaim you Developer of the Year! LOL!!!

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

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] krule031:
[MENTION=631273]Chainfire[/MENTION]

So, I flash that zip and I'm good?

Yeah I know it's old, I rooted my Xperia M2 with tool that is kinda old right now and it came with that version, so I was afraid to update it lol
[SuperSU] dev70194:
The newest one works for the sailfish. just make sure if your on the may bootloader to sign it
[SuperSU] peterlee928:
see link below

for the verified boot signer

courtesy of chainfire

(so u kno its legit)

https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606/page16

cheers
[SuperSU] Thisguy129:
Thanks for SuperSU i love it but I am sad to see you sell it I don't think root will be as good they will probably get payed off to not root from company's it's honestly getting to that point already I don't think it will be to long before root is gone every update blocks the method they do that on purpose. I have rooted everything with 2.79r3 first shoot I didn't use cf auto on my Samsung it worked fine I even keep root downgrading firmware I don't get how that happened you will be missed man I'm done I don't want the new owners on my system sorry. You should come back in a year take your crown back it's only fitting
[SuperSU] dahawthorne:
You should have stopped there. Were you drunk when you wrote this?
[SuperSU] Psiodon:
Thanks for making it possible to root a nearly unrootable 6.0 chinese head init. I rooted with flashfire because of no hardware buttons and no access to recovery. The only minor issue I have had is that after rooting I am no longer able to use volume down unless there is an active app on the screen. If im looking at the homescreen or launcher, volume down from touch screen or steering wheel control doesnt work, but if any app is active on the screen it works. I have no idea how rooting could produce such behavior, I double checked with clean flash then root and the problem appears right after rooting. It's not that big of a deal to me just thought I wpuld pass it along. If there is anything I could provide for you to help you make sense of it let me know.

Thanks
[SuperSU] Thisguy129:
What's the problem why do you guys all chime in Every time I say something someone else comments what was wrong I was nice please you tell me how to talk I love XDA comments there making my day. You are going to start a fight I'm going to ask you to tell me what I did wrong because I know the great XDA minds will let you know
[SuperSU] NLBeev:
The message was about stopping to talk...
[SuperSU] dahawthorne:
I haven't looked at any of your previous posts, but if you get negative comments every time you say something and can still post that comment in this thread then I doubt that you will understand any explanation. It seems obvious to me what's wrong with it.
[SuperSU] Ibuprophen:
I understand how you may be feeling.

I, personally, can tell that there's a slight language barrier (looks like you had converted your language to English) on top of the missing, English, punctuation does appear to those, like myself, as if the text was incomplete or cut-off at the end.

I'm not making excuses for this but, some members don't understand this.

Though many, like myself, can tell by the way the information is structured that this is the case but, there are those who can't tell and makes themselves look even more ignorant than they give themselves credit.

Please don't take it to heart since there are many members who does understand you and wouldn't poke at this barrier.

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

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