yashsingh1/xdaforums huggingface dataset:
[SuperSU] dynospectrum:
[MENTION=631273]Chainfire[/MENTION] Thank you for everything over the years ;]
[SuperSU] ianmacd:
After flashing this with FlashFire on my S7 Edge (which had SuperSU 2.74-2 up to that point), I suffered a bootloop. LiveBoot was showing a lot of stuff I don't usually see, but it was all scrolling by too fast to read much of it.

I had to turn the device off and reboot it. It's now booted, but for some reason now needs to optimise the apps. That makes me think that systemless Xposed has been blown away, but I'll have to wait for the device to come up fully before I can say for sure.

UPDATE: Yes, systemless Xposed had been blown away. Perhaps that's an obvious consequence of upgrading systemless SuperSU, but it was the first time I'd encountered it and it was unexpected behaviour. I'm not sure why this resulted in a bootloop, however. When the device came back up, it had properly upgraded to 2.76.

Anyway, I've reflashed systemless Xposed and the device is optimising apps again.
[SuperSU] j1gga84:
I do not understand this properly I guess :confused:

What does CCMT stands for and what does that mean, WHY is CCMT taking over development allthough SuperSU was invented by Chainfire?

regards
[SuperSU] ianmacd:
It's all explained here.
[SuperSU] dechronic:
See Chainfire's G+ post back in Septmber here https://plus.google.com/+Chainfire/posts/XJYJFPtS9Qb

---------- Post added at 06:34 AM ---------- Previous post was at 06:29 AM ----------

Thanks for all your work until now and that which is to come. I hope you see the at least the same success in your future projects that you intend to pursue.
[SuperSU] ulxerker:
works great for me, thanks! (N5X, stock ROM latest, EX Kernel)
[SuperSU] SacredDeviL666:
Thanks for all the time and efforts you had put in for us to have a better device :good::good::good:

sad thinking this is it...:(
[SuperSU] Explorer23:
You simply update the app like any other, the Play Store will automatically detect updates.

Then SuperSU will inform you that it has to update binaries - confirm this action, wait for it to do its thing, restart the device and you're done, now you have latest (stable) version of SuperSU installed.
[SuperSU] jcsww:
Thank you, Chainfire!
[SuperSU] GabbyWC:
I experienced similar results with my Google Nexus 5 and I posted about this at http://xdaforums.com/showpost.php?p=67611329&postcount=10808. My phone also went through a short boot loop of its own after flashing SuperSU v2.76 but I did not have to power off my device because it cleared up on its own. I too was surprised to see that Systemless Xposed had been erased or disabled by SuperSU because that had not happened to me before (and waiting through the lengthy "optimizing apps" sequence two times in a row wasn't particularly fun).
[SuperSU] bobby janow:
Flashfire on 5x DP4 stock recovery? Or wait for cf-auto-root to get updated? Currently it looks like the 2.72-2 version.

edit: Just updated from the PS and it worked. So no need for cf-ar.
[SuperSU] Strobi:
Unfortunately, also the newest SuperSU V2. 76 does not work in combination with the Xperia Tablet Z3 Compact and Android 6. 0. 1..

It's the same failure as before...
[SuperSU] sswagonman:
Thanks [MENTION=631273]Chainfire[/MENTION] for all you have done. Legendary

Edge of insanity
[SuperSU] shoey63:
Still waiting to see you down the Rocko or George and Dragon next time I'm staying at Point Peron[emoji6]

It will never work on Stock Sony elf boot images. Try flashing an advanced stock kernel by [MENTION=4102242]Gustavo RD78[/MENTION] first if he has made one for your device. If not - ask him.

Edit: And, of course, huge thanks to Chainfire for his incredible work on XDA, and for Android in general.
[SuperSU] sswagonman:
Long time since I have been to either of those. Swinging pig maybe or nags head

Edge of insanity
[SuperSU] Ch3vr0n:
I just hope one thing. That SuperSU won't go the way of es explorer now that some obscure 3rd party we've never heard of or without any play store app is finally taking over. There's just no match for superSU
[SuperSU] tiga_x:
Hi Chainfire.

I tried G935A method. works fine.

http://xdaforums.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538
[SuperSU] ldeveraux:
Once you're tired, you can still use this version of supersu. Just don't update if you don't want to. The average user sees no difference, assuming you can turn off the update notification.
[SuperSU] Ch3vr0n:
That'll only work a while. Eventually the issue would rise of no longer working because of the ever changing security environment in android.
[SuperSU] giovaorama:
Probably not the right place to report it, anyway my supersu get updated from playstore but for the first time in many years it is not able to update the binary.

I'll reboot and try again, but i think that flash from recovery is right way.

Nexus 5x with stock android

EDIT: the second time the update from the app works

Inviato dal mio Nexus 5X utilizzando Tapatalk
[SuperSU] Cienight:
After updating normally from Google play to the latest 2.76 version my supersu appears to not be a system though before the update it was a system app. Should I worry about this? There's an option to install it again as a system app...
[SuperSU] Ch3vr0n:
Same thing for my Nexus 7v2. Play store update failed first time to update binaries. Reboot fixed that issue and updated the 2nd time.
[SuperSU] ulxerker:
no need to worry, just leave it as systemless rooted.
[SuperSU] gdecker:
This compatibility check and fix worked perfectly for regaining root v2.76 for es file explorer on my sprint note 4 mm. Did have to reinstall xposed framework. Thanks for all of your work [MENTION=631273]Chainfire[/MENTION].
[SuperSU] TR2N:
Thank you so much [MENTION=631273]Chainfire[/MENTION]. All the best for you!
[SuperSU] Kamal363:
Just update thru play.... then it ask update binary... update... working just fine here.... v2.76 p.... thx

SM G900F 6.0.1 xXx 4.8 Deodexed Boeffla Beta 5
[SuperSU] skyhirules:
There's an option in the settings to make it system app. But after updating the app and selecting it, the pop-up was taking ages to finish the procedure. So, I just flashed the zip through recovery and it's system app again.;)
[SuperSU] Horgar:
Updated to 2.76, and 2.76 Pro from playstore on my Sony z3 with stock based 6.0.1 rom. updated binaries fine, installed to system fine. No issues.

And thanks chainfire for all your work. A legend on XDA.

Bit of a concern as to What's going to happen to supersu in the future, but no criticism of you chainfire you deserve it, but nevertheless still a concern. Same quality in future, stability, regular updates etc?

Thanks again chainfire, all the best.
[SuperSU] Pkt_Lnt:
He discussed that back in September.

https://plus.google.com/+Chainfire/posts/XJYJFPtS9Qb
[SuperSU] Horgar:
Yep, have seen. Still doesn't do much to assuage fears that future supersu won't be as good, reliable, responsive and downright fantastic as it has been in the past.

But as I say, I don't want to sound critical of chainfire, there's nothing to be critical about, all he has done is good and great. It's the future.
[SuperSU] Phrodini:
Good luck and have fun.. Thanks for the greatness.
[SuperSU] clock51:
Sad :pianto:, anyway thanks for all you have done for us :)
[SuperSU] nathanchance:
Thread cleaned. The topic of file explorers not working with systemless root has been discussed to no end in this thread. Search before posting. Additionally, keep things on topic, which is SuperSU, not other apps.

Nathan

Forum Moderator
[SuperSU] ianmacd:
Well, if you trust [MENTION=631273]Chainfire[/MENTION] enough to run code as invasive as SuperSU on your devices, and you understand how much blood, sweat and tears he has put into SuperSU over the years, then you should trust him at least enough to afford him the benefit of the doubt in handing future maintenance of the code over to CCMT.

Transferring ownership of his baby to a new parent can't have been an easy decision, and ensuring that the new owner would take as good care of it as he has over the years was, I'll wager, at the very top of his list of requirements.

If CCMT turn out to be poor guardians of the code, the tide of criticism here on XDA will be unstoppable. Until such a situation arises, however, I'd say we have more reason to be optimistic than pessimistic.
[SuperSU] NLBeev:
First: completely agree with your post.

2nd: using SuperSU many years;

3rd: without SU I would not have so much pleasure of my smartphones.

When I started with rooting years ago [MENTION=631273]Chainfire[/MENTION] was a new name for me.

Now CCMT is new and I will do the same as years ago - using SuperSU.
[SuperSU] RMarques:
LG G3 D855P

CM13 latest nightliy

For the first time ever, binary successfully updated from SU app itself!

Thanks a lot for your hard work [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] ldeveraux:
Yeah that's weird, same for me. I've always had to flash the zip in recovery, but this updated on many of my devices.
[SuperSU] Ch3vr0n:
That's because 2.74 doesn't contain the freeze fixes. Those are in 2.76
[SuperSU] sansnil:
More log please, more.
[SuperSU] silvertrain78:
Guess you didn't read his post!!

OP installed 2.76 and still had freezes
[SuperSU] Ch3vr0n:
Guess you didn't see his edit. The post stated 2.74 at the time of mine. I read his post just perfectly.
[SuperSU] drewski_1:
He edited it. It originally said 2.74 . . . :cool:
[SuperSU] jayyo:
I had originally posted that I installed 2.74 yesterday, which was wrong. I installed 2.76 yesterday. Edited my original post. Sorry for the confusion.
[SuperSU] silvertrain78:
Best practice when you edit a post to change something relevant like that would be to note the change in the original post

For example:

EDIT - Actually it was this instead of that
[SuperSU] The Analog Kid:
A few hours after updating to v2.76, I've experienced, for the first time ever, an spontaneous reboot on my Moto X Play (6.0 MM). Haven't checked for logs yet, but it seems to be a SuperSu v2.76 related issue...
[SuperSU] grep_i:
How can you tell this please prove your point with log files. It could easily be an Xposed module
[SuperSU] Chainfire:
Did you use the world's narrowest terminal and busybox? The ps command is missing a lot of relevant data.

Without logs, and with only a single reboot, there's no reason to assume one way or the other.
[SuperSU] kylepsp:
Chainfire, have you had a chance to check this out? https://code.google.com/p/android/issues/detail?id=213682

Load of other users reporting the same with SuperSu. I installed the latest version last night, no other root apps installed at all, and still got the same issues making the phone unusable.

Thanks for your continued help!
[SuperSU] Chainfire:
The post I replied to (the reply being the post above yours) is exactly about this issue.

I cannot replicate the issue at this time. There are also posters in the linked thread claiming they have the same issue without SuperSU. Additionally, some reporters are running custom kernels making their reports unreliable as well.

Unless somebody comes up with an easy way for me to reproduce this on a fully clean device with (fresh NP4 f;ashed device, factory reset, with only SuperSU installed and nothing else), there is nothing I can do.
[SuperSU] kylepsp:
I appreciate that. I don't know how I can help you reproduce it but I've had it occur on a completely clean device on dp3 and 4 , after factory resets three times after trying to figure out what was causing the issue.

The only constant was rooting it, via auto root. No custom recovery or kernel. Could it be auto root?
[SuperSU] chazall1:
All functioning very well here.

Thanks
[SuperSU] NLBeev:
Nexus 6.

Kernel 3.10.40.

Lite stock rom of Danvdh.

SuperSU 2.76.

All system go. No issues.
[SuperSU] Chainfire:
Perhaps describe in excruciating details exactly how you flashed the device, then exactly what you did when it was booted, then what happens, vs what is supposed to happen.

Previous comments along the line of "just boot and open 40 tabs" just isn't all that helpful. Because I did both and nothing happened :)
[SuperSU] kylepsp:
Anything to help, going to root my phone now with auto root and will report back.But usually I wouldnt ever have to do anything that drastic to cause it, just general usage
[SuperSU] kylepsp:
Yea happened already. No root apps installed. Was just using the phone usually. Fb, chrome and a few others. Then when opening a new page in chrome it completely froze and i had to hard reset the phone.
[SuperSU] Exile1975:
[MENTION=631273]Chainfire[/MENTION] does updating from the play store resolve the memory leak, out do we need to flash in recovery? Sorry I read back but couldn't find a definitive answer. Tia
[SuperSU] Ch3vr0n:
It should, it's the same version. Just released a little later.
[SuperSU] Pkt_Lnt:
Version 2.76 solves the memory leak. Find it in post 1 or the Play Store.
[SuperSU] Exile1975:
The reason I ask is that installing through the play store doesn't change the boot.img the way that flashing from recovery does and I'm not sure if it's only an app/binary update or if things have been changed in the boot.img as well. [MENTION=631273]Chainfire[/MENTION]
[SuperSU] Ch3vr0n:
That's because the play store only updates the apk and the apk in turn the binaries if need be. It doesn't need to modify the boot, it already is (and probably can't anyway, pretty sure only the zip can).
[SuperSU] Pkt_Lnt:
Precisamently. ;)
[SuperSU] The Analog Kid:
Yeah, you're right, sorry. But I've just made an observation; not an accusation. As it happened after updating to 2.76 and without touching any other installed app, I'm still naturally suspicious about SuperSU being involved. Anyway, after that isolated event, so far everything is stable right now though, if it happens again, I'll provide with log as I should have the first time

---------- Post added at 07:17 AM ---------- Previous post was at 06:52 AM ----------

Yeah, sorry. Avoided to provide logs because it was just an observation I've made based on the fact that I haven't touched any other app about 48 hours prior to updating SuperSu to v2.76; it was not an accusation. Anyway, ever since, I've decided to keep observing and so far, everything's right. If that happens again (hopefully not), I'll check and provide the logs if needed. Thanks for the support
[SuperSU] Exile1975:
And that is exactly why I want to know if the zip needs to be flashed again. I'm asking if it's just a fix to the apk/binary, or if the fix was implemented from within the boot. Because if the fix is in the boot image patch then i would need to flash the zip. So again, same question I've been asking [MENTION=631273]Chainfire[/MENTION]

Thanks for trying tho
[SuperSU] Kamal363:
Flashing zip in recovery seem to be small issue.... 'remounting system-fail'.. need to uncheck mounting system read only.... i stick with updating apk thru play... and it just fine as before...

SM G900F 6.0.1 xXx 4.8 Deodexed Boeffla Beta 5
[SuperSU] Chainfire:
Memory leak fix is APK only. In the changelog, changes/fixes that require you to reflash are generally prefixed with 'ZIP' :)
[SuperSU] Chainfire:
Can anyone confirm if TiBu freeze/defrost still works on 2.76 ?
[SuperSU] WhoDunnit:
Works fine here, on one plus one. Checked for normal and system apps.
[SuperSU] CVAngelo:
Really...is this the very detailed description requested of how you flashed the phone?

When your phone froze, you had to hard reset? Do you mean factory reset or do you mean hard restart (pull battery and then restart normally)? If you meant factory reset, did you not first try a battery pull?

Have you tried to clear the Chrome cache or to uninstall-reinstall Chrome? Does the same problem occur with the stock Android browser (it's usually called Browser or Internet and it's a stripped-down version of Chrome)?
[SuperSU] vandyman:
Can anyone confirm if TiBu freeze/defrost still works on 2.76 ?

Yes, it is working for me using a Nexus 5x.
[SuperSU] Darke5tShad0w:
Works fine here for me.

Just a few hours ago i froze apps when doing my clean flash.

N5x, latest ex kernel and pure nexus (july update).
[SuperSU] kylepsp:
Already mentioned with auto root, being the creator of auto root I'm pretty sure chainfire knows how that works.

Hard restart holding down the power button. It's not a chrome issue as it happens all the time with any app, just happened to be chrome this time. Crashed again earlier opening Reddit. It happens after a few hours of general usage, which is hard to record in excruciating detail.

Also, there is no stock android browser on nexus's. And who the hell would ever use it
[SuperSU] avi123456789:
how to root moto e plz sent me link super su
[SuperSU] Mrcactuseater:
Do some reading.

Tapatalk'd from my Twisted, Despaired Nexus 5x
[SuperSU] OldBaldy:
TIBU freeze/defrost working on XT1575 running 6.0 stock.
[SuperSU] grep_i:
What is it that you want us to see with this recovery.log boot phase I guess.
[SuperSU] YasuHamed:
any clue about failure in updating 2.74 to 2.76 ...
[SuperSU] grep_i:
No I have no clue the log you posted has nothing to do with the update of SuperSU.

Seeing that you have sony Xperia Z5 I thought to remember there was something special about that device.

If you used the search button on this forum you can find a thread devoted to sony experia Z5 really don't know why you could not find it or maybe you did not even try.

http://xdaforums.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
[SuperSU] YasuHamed:
[MENTION=6952047]grep_i[/MENTION]

i kept updating my E6833 via flashable zips from 2.65 til 2.74 easily , from same setup

its has became problem from this version only.

furthermore i am not the only one [MENTION=7534750]moormann[/MENTION] also having the similar issue

http://xdaforums.com/showpost.php?p=67661915&postcount=10881

he is on Huawei G8, Lollipop 5.1.

so i am thinking there is something missing about 2.76 since 2.74 in flashable zip which is not helping less popular devices like few huawei and xperia
[SuperSU] grep_i:
Might be he has the same problem with complete different setup I really can not say that by reading his post only.

Maybe you can find an answer to your problems in the sony Xperia threads, please take a look at them and maybe [MENTION=7534750]moormann[/MENTION] has to take a look at the Huawei G8 thread for an answer.
[SuperSU] ktmom:
Start from a clean platform, then flash 2.76 and *immediately* save the log. Read it to see what supersu is saying about the flash process. Maybe you can see the problem and think how much faster that will be.

If *you* are unable to see an error posted by supersu, but you do see the flash process by supersu in that log, upload the log to pastebin (pastebin.com/) and post the *link* here.

When y'all post these lengthy logs in a post, it becomes impossible to use a phone to read the forum. I just page past all of the mess because it takes up so much space.

Please respect everyone else's time by at least trying to help yourself.
[SuperSU] YasuHamed:
please explain "Start from a clean platform"

i have flashed my kernal with modified version and installed flashable 2.65 last month! , it was updating just fine till 2.76 ...

shall i flash my whole MM 6.0.1 then Flash Kernal again?

device Sony E6833
[SuperSU] grep_i:
Clean flash your rom, kernel and Supersu 2.76 immediately that is what he meant
[SuperSU] kchaisu:
SuperSU version 2.76 is working fine on Saga, CM-13 sagaopt. Thank you very much Chainfire for your kind contribution.
[SuperSU] teddy0209:
I think it has something to do with the kernel.elf of sony devices... No problem with system mode, but for systemless it needs patching....
[SuperSU] quanqw:
Please support system mode
[SuperSU] Ch3vr0n:
It already is, always has been and still is the default for a large number of devices. Installing system vs systemless depends on device and rom.
[SuperSU] Tecalote:
Some questions - Thank you :)

I have some questions.

Is it possible to execute this command instead of Terminal-Emulator in TWRP with the build-in Terminal? Does combatibility mode mean, the systemless mode changes back to system mode?

Another question too:

Does the latest Free SuperSU 2.76.zip flashing through TWRP in Marshmallow (or systems with 5.1.1 which requires the systemless mode) automatically root in systemless mode? - or is it required to use the Terminal Command in TWRP (like in older versions of SuperSU) echo SYSTEMLESS=true>>/data/.supersu (dont know, if this was/or is just necessary only with Huawei-Phones running MM, or in general - because I have Huawei p8)

I know, it is not required while flashing the newest update zip, if the phone is already rooted (or prerooted) and it's not required, if the phone is rooted in system mode or running the donation apk.

But for the first rooting of a stock phone, I would like to know. Thank you :)
[SuperSU] Seraphim777:
Yes.
[SuperSU] tamanaco:
Can I use the 2.76 zip file in the first post of this thread to update a Nexus Player currently rooted using SuperSU 2.74 beta or do I need a modified/different SuperSU zip file to upgrade? The Nexus Player is currently running Marshmallow 6.0.1 build MMB30M rooted using Wug's toolkit, TWRP Recovery 3.0.2.0 and SuperSU Pro 2.05.

Thanks...
[SuperSU] Seraphim777:
You can use SuperSU 2.76 zip file in the first post of this thread. No different file for your device.
[SuperSU] Chainfire:
v2.76 S7 QC

For the locked S7 Qualcomm devices using the engineering boot image, here is the root ZIP updated to v2.76:

SuperSU-v2.76-S7QC.zip

Aside from being v2.76, it also fixes some commands like pm not working - you will not get that fix updating only through the APK.

Interestingly, installing xposed might fix that issue by accident. And speaking of xposed, be sure to use a system-installing version of xposed, not a systemless version.
[SuperSU] VE2HRJ:
Hi all,

Here it is again, my SD card is corrupted again by the OS… but I can access the card by my PC or another phone!

So it seams to be a combination of OS 6.0.1 (Canadian Rogers), how it is rooted (Twrp) and the SuperSU free v2.76.

I’ll wipe the phone again tonight and re-install the original Os from the carrier, no Root & no SuperSU.

I’ll wait for a week and see.

Keep you posted.

VE2HRJ :cool:
[SuperSU] UnixSlayer:
Keeps coming up as a bad zip file after download.....

Sent from my rooted Samsung Galaxy S7 Edge - SM-G935T
[SuperSU] cuezaireekaa:
Maybe that's why I can't see it in Flashfire. No matter where I save the zip, Flashfire will not see it to flash. I've tried 2 different browsers and saved to internal and external. Maybe a bad upload.
[SuperSU] grep_i:
Or unroot and see if you can see if the SD card is still corrupted, as you said yourself accessing SD card is OS functionality only, I think TWRP and Supersu had nothing to do with it and your problem is OS only related or else many people would have reported similar issues here.

I hope you will resolve your issue soon
[SuperSU] VinylJStar:
Same here. Bad zip file.
[SuperSU] Chainfire:
If you're getting the corrupt ZIP, are you downloading mobile? The download site tends to not work on download managers (which includes Android's!) and downloads the html file rather than the ZIP file :/

EDIT: Just to note, it downloads fine on my S7 with NoChromo, and on my PC with Chrome.
[SuperSU] TechBSwift:
It's really weird I download on the phone and flashfire couldnt see it. So I deleted the file, downloaded on my computer, copied to my phone and flashfire still cant see it

Edit, it only shows up in flashfire if I select flash firmware ota... It does not show up if I select flash zip
[SuperSU] TechBSwift:
Here's a pic showing its there only if I select flash firmware instead of the normal process selecting zip
[SuperSU] Chainfire:
The original v2.74 for S7QC wasn't a flashable ZIP, and neither is this one. Why would you assume so? This is a replacement ZIP for the older version, the instructions remain the same.
[SuperSU] TechBSwift:
You're right my apologies, I just extracted the files and flashed through adb without any issues. I'm so use to downloading your work, and flashing your work through your apps. See what I did there? I showed you are still the man!!!:good::good::D