yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
Who knows? Why use 2.56 though? Use either 2.52 for system install or 2.60 for systemless.

I'm not sure I understand the question. 2.60 will automagically patch Samsung 5.1 boot images for you.

I'm not sure what is going on, but encryption is unlikely to be the problem.

Great that it works, but in case of issues, please do not report them here, as you did not reflash /system as per the instructions.

As per my other reply, did TWRP ask you to install SuperSU for you because your device wasn't rooted, the first time?

"audit" is always a good first thing to look for.
[SuperSU] olivercervera:
Wow.. Would that mean that we can flash 2.6 and then a customer kernel and keep systemless root? :fingers-crossed:
[SuperSU] teinwhite:
Most definitely!

Thanks again!
[SuperSU] Nbay64:
I'm on Galaxy Tab S2 SM-T710 running 5.1.1. After I flashed the v2.60 zip, TWRP asked me to install SuperSU when I went to reboot the device. I said yes, and that threw my device into a boot loop. I wish I could give you my device's fingerprint, but I don't know how.
[SuperSU] teinwhite:
If you read this post: http://xdaforums.com/showpost.php?p=64161125&postcount=3

There's a line: "If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!"

I'd go through the steps again, but when TWRP asks about root, skip that part.
[SuperSU] geoff5093:
That's why you don't say yes when it asks you.
[SuperSU] street_dog:
Ok, what went wrong? Installed my own built AOSP MRA58N, tried with 3 different kernels and SuperSU 2.52 and 2.60 with same result. Yes, the phone got root and everything seams to work as it should...except from the battery indicator. It looks like i have several thousand percent, if it's true i won't complain, but i suspect it isn't so. This doesn't happen with rooted stock by the way.

http://postimg.org/image/56sq8jmah/
[SuperSU] Majesty00:
Here's my experience with SuperSU 2.60.

I have a Nexus 5 running 6.0 N, rooted and unlocked, of course. I had SuperSU 2.56 with the systemless installed, so I wiped my /system by doing a WugFresh Nexus Root Toolkit upgrade without wiping my userdata. I then flashed TWRP, went into it an flashed SuperSU 2.60. After the long "apps upgrade" process, I opened SuperSU and it said 2.56...

Well, ok then. I wiped, manually my /system with fastboot "flash boot boot.img" followed by "flash system system.img". I went into TWRP flashed SuperSU again and once in Marshmallow and SuperSU was still 2.56. If I run a root checked, it IDs SuperSU as 2.6 tough.

So, what's wrong? :-/

Edit: Forgot to mention I have the Pro version of SuperSU

Edit 2: I've solved my problem by uninstalling SuperSU in Android, reinstalled SuperSU 2.61 in TWRP and finally, reinstalled SuperSU Pro in the store.
[SuperSU] SamuriHL:
Just a heads up for the thread, 6.0.1 images are being posted by Google. Be prepared for an onslaught of "does it work" "I bootlooped trying it" etc. ;)
[SuperSU] lexcyn:
I am debating whether or not trying to root with 6.0.1 ... I mean worst that happens is you re-flash the stock kernel. :p
[SuperSU] SamuriHL:
I'll be doing so on my NX6 shortly. I'm waiting for Android is upgrading... to finish then I'll go boot TWRP from fastboot and sideload 2.6.0 and see what happens. lol
[SuperSU] Captain_Throwback:
Hi [MENTION=631273]Chainfire[/MENTION],

I just tried the 2.60 zip on my stock HTC One A9. I ensured that stock system and boot were in place, and any previous SuperSU was completely removed. Attached is the recovery log from the install. After selecting "Reboot System" in TWRP, the device booted to the splash screen as usual, and then, instead of progressing to the boot animation, the device rebooted again and I was greeted by the bootloader with the below message (the init fs_mgr_mount_all failed line isn't usually there).

I tried booting back into recovery and pulling last_kmsg, but none was generated.
[SuperSU] lexcyn:
I'll try on the N5X then... can't hurt, at least then people will know whether to wait or go flash crazy.
[SuperSU] Chainfire:
Downloading and testing them all as well here. Should have results in an hour or two. The downloads aren't exactly fast.

EDIT: Downloads have completely stalled now. No idea when these files will arrive.
[SuperSU] Chainfire:
Interesting. What firmware was it running? What happened when you rebooted a second time?
[SuperSU] SamuriHL:
6.0.1 on the Nexus 6 worked perfectly for me. Sideloaded 2.6.0 in a memory booted TWRP (kept system RO) and everything's fine. Booted up root explorer and opened the data partition which prompted root. All good. Thanks guys!
[SuperSU] allen099:
Thanks for the update! Did you use the modified boot.img for the "K" version? Or did you simply not flash it? Thanks!

*EDIT* -- Just read the 2.60 release notes. Auto patches the boot image. Amazing! Thank you chainfire!
[SuperSU] Brushstroke:
[MENTION=631273]Chainfire[/MENTION], your 2.15 beta is working great on the latest Lollipop Preview on my Nexus 5. The phone isn't running as hot now.
[SuperSU] Frank Westlake:
2.15 OK on:

- Note_ SGH-I717 4.0.3

- Note3v SM-N900V 4.3 Permissive

- Note3t SM-N900T 4.3 Enforcing

The "#" Notification of 2.13 and 2.14 and the Toast of 2.13 did not occur with 2.15.

Attached are the debug archives for the three devices just for edification. 'logcat' failed on the Note_, don't know why yet.

Frank
[SuperSU] Dr Goodvibes:
Xperia M (C1905) OK now after rebuild

Chainfire,

Thanks for keeping us up to date.

I had the following problem with an Xperia C1905 running Android 4.3

[STABLE][2014.10.15] SuperSU v2.14 - Xperia M loops after binary update

After re-building the phone (and I did this several times) I didn't have any more problems with SuperSU binary update.

When I rebuilt my phone, SuperSU v2.14 was one of the first things I updated.

I updated SuperSU from Google Play after Kernel/ROM install, rebooted the phone, did the binary update and again rebooted the phone.

I did this on each rebuild (approx three times) and didn't have any problems.

My Sony Xperia C1905 with Android 4.3 (SW Version: 15.4.A.1.9) is up and running without problems²

I have not tried the Beta v2.15 version as I'm currently 'good' on the Google play release version.

I'm remind of the Starhip troopers quote:

Sky Marshal Tehat Meru: To fight the bug, we must understand the bug. We can ill afford another Klendathu.

Newsreel announcer: Would you like to know more?

² Note - SetCPU for Root Users apk asks for root privilege (Grant/Deny) after each power-on re-boot. Not really a major problem.

SetCPU also shows toast notifications (even when toast notifications are disabled, using SuperSU Pro) when the phone is being used. It doesn't shown notifications to the extend it becomes unmanageable, just every now and then.

I am using SetCPU profiles for under-clocked power saving and etc.

The notifications and SuperSU access requests may be more to do with SetCPU apk and the fact it's not been updated for over a year, than anything to do with SuperSU v2.14, but just saying.
[SuperSU] JaCh0o:
No, it's not only one issue.Phone it's losing root privileges randomly on this root zip file. I have to enter app and update binaries from time to time (around 10-20 a day, depends on how often I use root needing apps).

Wysłane z mojego Oppo Find 7 przy użyciu Taptalka
[SuperSU] Chainfire:
- Reboot your phone

- Open SuperSU

- Update the binary if needed

- Close SuperSU

- Wait for root to be lost

- Open SuperSU

- Do NOT let it update the binary, just leave the dialog on screen

- Create a logcat and post it
[SuperSU] Chainfire:
Good to know it now mostly works!

I'll look into the SetCPU issue, see if I can replicate it and if its a real issue or just some awkwardness.

Love that movie btw :)
[SuperSU] Dr Goodvibes:
Chainfire, I note that using SuperSU v2.14 on an Xperia S also prompts for SetCPU authorization after a reboot too. [Grant/Deny]

It normally takes a couple of minutes after the startup completes before being prompted.

And also see toast notifications flash up and fade out every now and then.

This happens on an Xperia M (C1905) running Android 4.3 and Xperia S (LT26i) running Android 4.1.2 (Build: 6.2.B.1.9) with DooMLoRD rooted Kernel.

On both mobiles(Handy - Germans, awh bless) I'm just running stock Sony ROMS with only rooted Kernels.

Other applications like Samba Filesharing, ClockSync, Link2SD and Titanium Backup and etc are all well behaved with no observed problems.

Chainfire, as always, thank you for all your support and help.
[SuperSU] JaCh0o:
Please confirm am I thinking in right way:

1. Reboot to twrp

2. Flash SuperSU 2.15 Beta

3. Reboot to system

4. Run SuperSU to apply root permission by updating binaries - normal method.

5. Run Androidsdk command prompt terminal, turn on su and start logcat.

6. Wait until phone will lose root privilege (couple of minutes/few apps later)

7. Run SuperSU to check is it rooted or not (waiting for asking to update binaries again) and quit the app.

8. Stop logcat, pack it and attach ?

Wysłane z mojego Oppo Find 7 przy użyciu Taptalka
[SuperSU] Chainfire:
Sounds good
[SuperSU] urim225:
Can I please ask you to test Hola Unblocker app and see why it doesn't want to accept root. It works in the older SuperSu 2.01 and below but never works In then newer versions. Maybe I'm asking too much from you and sorry for that but I really need this app to work :(
[SuperSU] Tanis64:
GT-I9505

4.3 MKE (DBT)

XPosed

Wanam XPosed

Coming from Version 2.01

Installing SuperSU apk, from zip file (2.15)

Updating SU Binary over the apk normal Mode.

After that reboot device.

Works perfect for me.

With 2.13 and 2.14 SU Binary install over apk hang, even when installed over PhilZ Recovery the App and Log Tab shows only a spinning wheel.

Now everything is fine.

Thanx a lot for the new Beta

Regards

Christopher

Send from the outback with my GT-I9505
[SuperSU] Tinchoska:
Is it possible to install this latest beta with an apk? Instead of zip
[SuperSU] dhatch93:
post #293 from Chainfire tells you how to get the apk from the zip...
[SuperSU] GameMista:
Samsung Galaxy s4 4.3

I have a Galaxy s4 rooted on 4.3 (locked bootloader) with safestrap recovery. I am concerned whether or not to flash the beta zip as it has a file that concerned me (install-recovery.sh in the common folder). My SuperSu failed the 2.14 update and no longer has any function really. It doesn't show apps or logs and i was unable to clean up for a re-install. I was hoping this would possibly fix it.

Edit-my problem was solved. I checked further into my system/bin and found that the two files were identical. Flashed and everything appears to be working fine on my phone again.
[SuperSU] egingell:
install-recovery.sh is just a shell file that executes at boot. I use it to run init.d scripts on the stock ROM. Other apps, like Link2SD, use it as well when something needs to happen at boot up.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Diaphragma:
Running SuperSU beta 2.15 on LPX13D on my nexus 5, and I'm having some problems. I flashed codeblue kernel, SuperSU 2.15 and then the boot.img for SuperSU.

I don't know if I'm rooted properly, because root check by JRummy says I am, but apps like Titanium Backup and ROM Toolbox says otherwise. Here's screens:
[SuperSU] AndroidAssassin:
Bad file every time I try and download
[SuperSU] Chainfire:
v2.16 posted

Just posted v2.16 to my server. Get the link from the first post. Exact changelogs are a in the changelogs post.

This update fixes a number of issues with app grants that disappeared on boot. Should be good now, report any issues like these that persist more than three(!) reboots after update.

I've also started on polishing up some of the visuals in material style. Most changes are pretty subtle, small color updates, icon adjustments. It's certainly not done yet, but even when it is, it wont be the major 'material haulover' some other apps are receiving - ain't nobody got time for that, I'm more concerned with SuperSU working correctly. The material 'light with dark actionbar' theme is selected by default now if running on L if you've never changed the theme option under settings. If you have, you'll have to select it manually. This will not be backported to 4.x, so don't nag me about that. With all the compatibility stuff in SuperSU already to keep it somewhat working across so many different Android versions, adding another compatibility library to backport material support is simply not going to happen - too many conflicts, no time (or will) to solve them.

Anyway, be sure to click all the buttons on all your different Android devices and find out where I made it crash due to these theme changes, and report that back to me :)
[SuperSU] DigitalUnderground:
Thanks for being an awesome dude. [emoji2] I've been using your SuperSu (whenever not on slimkat) for years now... Used to use Mobile Odin Pro and Triangle Away when I had my galaxy devices, and have been following your Lollipop work on SuperSU from a distance. Although you give us SuperSU pro for free... I'm finally going to the store right now to buy it. Hope it helps show appreciation.

Spoiler content hidden.
[SuperSU] CamoGeko:
Thanks [MENTION=631273]Chainfire[/MENTION], you're a legend!

Sent from my N⁴ running Android L
[SuperSU] Majesty00:
I've just flashed Android 6.0.1 and SuperSU on my Nexus 5 and it boots! :D
[SuperSU] Captain_Throwback:
Rebooting a second time does the same thing - takes me right to the bootloader. I think I may know what the issue is - your patcher looks for "verify=" to remove dm-verity, however in my fstab, it simply says "verify". The full line looks like the below:

/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,verify

But since this root method isn't touching system anyway, this shouldn't matter, should it?

It's running stock firmware.

EDIT: Unless the problem is this (from the recovery.log):

dd: writing '/dev/block/mmcblk0p59': No space left on device

Which would mean it didn't install a complete image to my device, which would explain why it can't boot.
[SuperSU] lexcyn:
Confirmed this works on a Nexus 5X with 6.0.1. Thanks [MENTION=631273]Chainfire[/MENTION] !
[SuperSU] Ja_som:
[MENTION=631273]Chainfire[/MENTION] thanks for 2.6, works without any issue on my N5 and N7 2013 with Android 6.0.1 :)
[SuperSU] Chainfire:
The dd error is expected, because it writes 0 to the boot partition before putting back the modified boot image.

It's quite likely the "verify" thing, as the verity key has been removed from the ramdisk, but as the verify flag is still present, the mount_all operation will fail because it cannot mount /system with verification enabled. Boom. Next ZIP update will have this fixed, please do let me know if that fixes it.
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

A couple of other quick notes here:

I did a TWRP backup of boot and confirmed that is was flashed correctly. the verify flag was still there, which I removed, and I also noticed that an export PATH was added to init.environ.rc. I say "added" because in the A9 ramdisk, the export PATH isn't found in that file - it's found in init.hosd.common.rc (who knows why).

After removing the verify flag, the device boots without issue, which surprises me because my system *should* be stock. I'm going to re-flash stock system now to confirm that.

EDIT: Just saw your edit above - yes, that makes sense. But question - why remove the verity key if we're not touching system (especially since verity is being disabled anyway)? Wouldn't it be more secure to leave the key there and retain verity? Isn't that really the point of systemless root?
[SuperSU] Chainfire:
Just because SuperSU doesn't modify /system doesn't mean the user might not want to with other apps. Keep all options open.
[SuperSU] Captain_Throwback:
Understood. Any thoughts on the location of the PATH variable? I'm not sure what'll happen if it's defined in both places. I think the one in init.hosd.common.rc overwrote the one in init.environ.rc, so you may need to add some additional handling for cases like the A9.
[SuperSU] Chainfire:
Awkward. Can you check by doing "adb shell echo $PATH" on a booted A9 ?
[SuperSU] Captain_Throwback:
Appears to be okay.

shell@htc_hiaewhl:/ $ echo $PATH
/su/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
shell@htc_hiaewhl:/ $

So just the "verify" fix and it should be good to go! I'll flash back to my stock boot.img so I can test the next version.
[SuperSU] bb709394:
Did you go the system-less route with SuperSU 2.6 or modified boot image and SuperSU 2.52?
[SuperSU] Majesty00:
I've used the automatic systemless method of SuperSU 2.60.
[SuperSU] spoon76:
Works fine on Nexus 9 (volantis) with 6.0.1 :good:
[SuperSU] ashyx:
Basically for the Samsung devices it's not working on, is it possible to flash supersu v2.60 then the manually patched boot image?
[SuperSU] Chainfire:
Are there Samsung devices it's not working on, where letting TWRP install SuperSU isn't to blame? Because that isn't clear to me yet. But yes, you can always try.
[SuperSU] ste_mir:
Guys, please you need to forgive me, but I have always been on "pre-rooted" ROMs so it is not so clear to me all this stuff.

A month ago I installer SuperSU to root with the "new" method (frankly speaking I don't even know which one is the old and which one is the new).

Now that 6.0.1 is out I would like to update, but I have seen that there is also a new version of SuperSU.

So, in short, is there a easy method to go

from:

6.0 with SuperSU 2.56 and "new" root method

to:

6.0.1 with SuperSU 2.6 and "new" root method

?

I would not want to lose anything of my data and configuration, just like I am doing a "simple upgrade".

Is it possible? And how? What would I do for further Android releases?

Thanks
[SuperSU] Ch3vr0n:
Adb flash stock system and stock boot, update to 6.0.1, boot custom recovery. Flash 2.60, done

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Chainfire:
v2.61 posted in the WIP thread. Changelogs are in the STABLE thread.

Gentlemen, start your testing! :)

These Systemless SuperSU BETA's are slowly approaching what I want them to be. Soon they will be the only BETA's (they'll still be non-systemless for pre-6.0 devices aside from Samsung 5.1, but I won't keep 2.52 around anymore). Might even be time to start updating the CF-Auto-Roots finally. And FlashFire!
[SuperSU] d.cortez:
no, TWRP didn't prompt me to install SuperSU. thanks.
[SuperSU] boxcar8028:
DUDE, YOU IS THE MAN:good::good::good:
[SuperSU] Ja_som:
[MENTION=631273]Chainfire[/MENTION] fast flash of 2.61 on N5 and N7II, and I don't see any issue again :)

Thanks
[SuperSU] drawde40599:
2.61

Is 2.61 working on Android 6.01 . N6 & 6P ?
[SuperSU] Ch3vr0n:
Try it and let chainfire know?

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] PuNcAkE_15'l:
Can someone help when I flash ss v2.56 my phone won't boot so I have to restore my phone. I have root but I don't have a root manager app it's just the default where the only thing it does is ask you if you would like to grant root access then you can't even disable it
[SuperSU] skrowl:
I'm wondering this too. Scared to try it.

EDIT - Rebooted to fastboot, flashed latest TWRP, then used the fastboot menu to reboot directly to recovery, from there flashed 2.61 via TWRP and it worked!
[SuperSU] Chainfire:
Can you post the stock boot image for your firmware?
[SuperSU] nmlssit:
Working flawless with 6.0.1 and a custom kernel ?

Edit: Somebody go tell TWRP team that asking users to install SuperSU is not necessary anymore lol

Inviato dal mio Nexus 5 utilizzando Tapatalk
[SuperSU] Chainfire:
Both of you should be readers in this thread at best, not posters. There will be test reports when users have tried it (and there have been some already). Asking the hour a firmware is released if it works with device X is just counterproductive.
[SuperSU] drawde40599:
I'm at work , I can't till tonight . But if no one has confirmed I will for sure

---------- Post added at 12:30 PM ---------- Previous post was at 12:29 PM ----------

I did read and didn't see my answer . Maybe I missed it . Sorry...
[SuperSU] B4W:
Is there anyway to install this on a Samsung device with a locked bootloader? Specifically a SM-G925A? All the research I have done looks like the answer is no, although it is possible that is above my expertise level.
[SuperSU] Nbay64:
[MENTION=631273]Chainfire[/MENTION] flashed v2.61 on Galaxy Tab S2 SM-T710. Working fine, except that whenever I open the SuperSU app, it tells me that there is no binary installed. What do I do?
[SuperSU] Chainfire:
For locked bootloader devices it depends on a working exploit being available for your firmware. This is not the place to find those, as I do not make nor involve myself with them.

Well, that means it really doesn't work at all. But at least it didn't bootloop. Not sure what the answer is here, as I have no idea what the problem is for you.
[SuperSU] shaklebolt:
Works fine on N6 with 2.61

Works fine on N6 with 2.61

Flashed Android 6.0.1, copied SU2.61 and then flashed in TWRP
[SuperSU] SamuriHL:
Oh sure, now I gotta go sideload all my devices again. Gee thanks! :P Seriously, though, thanks for this. I've tested 2.6.0 on S4 GPE 5.1, Note 10.1 2014 5.1.1, and my NX6 6.0.1 and all 3 work. So this will be a cake walk to sideload them all with 2.6.1.
[SuperSU] IronTechmonkey:
CM13?
[SuperSU] Nbay64:
Wouldn't work, there currently is no version of CyanogenMod for the Tab S2.
[SuperSU] Captain_Throwback:
Not every device that TWRP supports is running Marshmallow . . . but trust me, they already know about this.
[SuperSU] SamuriHL:
Frack. Hey [MENTION=631273]Chainfire[/MENTION] trying to update my S4 GPE that's got 2.6.0 on it:

...

Checking patch status

Already patched, attempting to find stock backup

restore failed, aborting

I'll just go back to stock and reflash but I thought you'd like to know.
[SuperSU] Maxr1998:
SuperSU 2.60 works fine on my 6.0.1 Nexus 6P, though I wonder why the settings of the SuperSU app get removed when updated?
[SuperSU] d.cortez:
[MENTION=631273]Chainfire[/MENTION], i successfully installed 2.61 to my Note 5 SM-N9208, used Root Explorer to successfully rename a filed in the data app folder, opened SuperSU 2.61 Pro and i was not prompted to update the binary. rebooted to recovery to install Viper4A fix (from foreverLoco) and xposed and everything is working so far. initial 2.61 installation steps were:

1 ODIN flashed 5.1.1 AOK2 firmware (latest release for my device)

2 after ODIN flash is complete, ODIN initiates a reboot and installs system update

3 after system update, i rebooted to Download mode and installed TWRP

4 install SuperSU 2.61 via TWRP

5 rebooted device and at the "Galaxy Note 5 boot screen" device rebooted itself

6 got expected "Android is updating message" due to ODIN flash (w/message that Kernel is not SEANDROID enforcing, expected)

7 rebooted to recovery to install Viper4A fix and xposed ver 78, rebooted device and no issues
[SuperSU] corkiejp:
Does that mean you would recommend using systemless v2.61 instead of system 2.52. Going forward?

I successfully update my Nexus 9 to 6.0.1. Flashed latest ElementalX kernel and SuperSu 2.61.

Root works with testing with Root Checker and some root apps.

Edit: TWRP did not prompt to install SuperSU

Once running I used adfree to edit my hosts file and also Installed Busybox Pro (Needed for ElemetalX Manager App) so more than likely have now made changes to my system anyway.
[SuperSU] c3k:
Same on my nexus 7 2013 wifi with supersu 2.61 on Android 6.0.1.

Maybe will be ok after full charge?
[SuperSU] SamuriHL:
Ok, so the Samsung devices DO NOT like to be updated directly from 2.6.0 to 2.6.1. Failed on my Note 10.1 2014 as well. Same problem I posted before about my S4. I'm having to reflash the whole firmware (for some reason my boot img wouldn't flash...will look into that later as that will suck when OTA's come out) so I can then reflash twrp and sideload 2.6.1. Samsung, wtf? LOL
[SuperSU] GPS3:
Same here. Nexus 6 6.0.1. SuperSU 3.52. My indicator shows im in the 4000% range.