yashsingh1/xdaforums huggingface dataset:
[SuperSU] GiGiSSiMo:
I'm on GNEX 5 with 6.0.1.

With 2.61 there are no problem at all, otherwise with boot image + 2.52 the battery percentage on status bar is displaying i've 3.450% battery!

Anyone else have this problem?
[SuperSU] shipping guppies:
Digital Signatures?

Dear Chainfire,

do you publish digital signatures for the ZIP files from your Super SU binaries somewhere?

Regards

S.G.

PS: SuperSu 2.61 is running just fine on Android 6.0.1 on my Nexus 5X and Naxus 7 2013 Wifi.
[SuperSU] 0088:
I have the same problem. Stock 6.0.1, ElementalX kernel.
[SuperSU] Harmveenstra:
Same problem on stock 6.0.1 with Franco R76 kernel and 2.61 SuperSU
[SuperSU] FSMcas:
Could you please explain one thing to me: is 2.61 systemless-ONLY or can I just flash it over my "classic" 2.52 / 2.56?

Thing is: I've got the battery problem as well, and some claim, 2.61 fixes it. I don't care about the systemless stuff and rooted classically with a custom kernel (latest franco) and SuperSU 2.52 (which upgraded itself to 2.56). If I now flash 2.61 in TWRP, will this break my root because this version is systemless-only and interferes with the old one or does it simply upgrade my binaries to 2.61?

Sorry, I don't get the whole picture yet... Thanks!
[SuperSU] Ingenium13:
/data/data/com.android.providers.telephony/databases/telephony.db

Sent from my Nexus 6P
[SuperSU] Taomyn:
Has anyone else have issues with 2.61 and AdAway?

On my Nexus 6 (MM 6.0.1) with 2.60 it all worked fine, but with 2.61 it complains that there is not enough space. I have checked my bind script is in /su/su.d and confirmed it runs as I can see the new mount point at /su/etc/hosts (I also checked in TWRP that the original hosts file is untouched, and it is). I can change the bound hosts file myself using /etc/hosts without issues so I'm sure it's all fine. I have reflashed 2.61 and that hasn't made any difference.

Even stranger is that my Nexus 9 (MM 6.0.1) also on 2.61 is not having any issues and AdAway is happily working.
[SuperSU] 0088:
Resolved it by flashing stock boot.img, then supersu 2.61, after that ElementalX kernel. Everything works fine now...
[SuperSU] mobileman88:
Thanks. Great
[SuperSU] Speedo.thc:
Hello , 2.61 works well on Motorola Moto G 4G XT1039, rom CM13 nightly.
[SuperSU] nytebird:
All is well w/D851. CM 13 12-7 2.60. Great job [MENTION=631273]Chainfire[/MENTION]! Thank you.
[SuperSU] edrickmph:
Finally rooted using the stock boot.img! Running now in Cataclysm 6.01 and ElementalX 6.07.
[SuperSU] Didgeridoohan:
From the Work In Progress thread (http://xdaforums.com/showpost.php?p=64161125&postcount=3):

"If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this."
[SuperSU] dechronic:
This was mentioned a few pages back, specifically for Nexis 6. Apparently Google's system image fills almost the entire partition so much that some apps see 0 bytes free. So Adaway can't modify the hosts file. It was suggested to remove some system apps for it function properly and modify the hosts file. Search the thread to be sure as I am sure that is how someone got it to work.
[SuperSU] Chainfire:
Unless the 5.1.1 cannot be rooted without a custom kernel, it's not likely.

I'm not sure what you mean here.

[MENTION=1162986]Captain_Throwback[/MENTION] is testing the M8 as well and finding/reporting issues. I don't think he's running CM13 though. Still I'd recommend 2.61 over 2.52 in this case.

I have no immediate reply to this but I've added this information to the bump section of my to-investigate list :)

Fur the xth time, yes, the patched boot image disables forced encryption. You can run encrypted or unencrypted with it.

Several people do. I think it's because you're using the 6.0 boot image on 6.0.1, but I'm not completely sure.

d3d2b6d94bad25b2002b4203a65f8ee7 *SuperSU-v2.61-20151207213702.zip
[SuperSU] jineshpatel30:
I've been testing 2.61 on Nexus 5 ( latest 6.0.1) for 2 days now and it works Gr8 on some apps , some apps can't authenticate it and some even can't see that Phone is rooted.

here are details,

TB , Adaway , Xposed , root explorer works without any problem.:good:

Clean Master & root cleaner and similar apps can't detect root at all !

PS: back on 2.52(system modified) version on (Nexus 5 , 6.0) Clean Master asked for Root access and when we grant, SuperSu Shows "granted" popup but app give authorization error {similar error was present in Lollipop with SuperSu 2.46 which was fixed in v2.49 }

.
[SuperSU] vincowoo:
Sir , ???You didnt replied my post ?

#3438 [MENTION=631273]Chainfire[/MENTION]
[SuperSU] thaidroid:
If I have two images backed up on my phone.

A is MM 6.x with 2.61 Root

B is GPE 5.1 with 2..52 Root

What happens if I restore one over the other and vice versa?

I have TWRP 2.8.7.2 on I9505
[SuperSU] Captain_Throwback:
I'm not actually testing on the M8 - I've been testing on the A9. I can test on the M8 too, if that would help.
[SuperSU] GiGiSSiMo:
Anyone colud please tell me where i can find 6.0.1 pathed boot image or i can gain root access with supersubeta 2.52 with stock 6.0.1 boot image?

Thanks a lot.
[SuperSU] mobileman88:
As mentioned before. Just need to create empty su files in system, reboot and it all works
[SuperSU] jineshpatel30:
Can you guide me ?

Empty su file means "su" as name without any extension right ? & where to put it ?

What permissions & user to grant
[SuperSU] Taomyn:
Ah, yes I did see that but I hadn't put 2'n'2 together, but that probably explains it. I'll report it to the AdAway developer so they are aware.
[SuperSU] jc monkeyballs:
It seems like WiFi calling is not working after installing 2.61 on my Nexus 6P with 6.0.1.

Is this a known issue?

Can anyone confirm if T-Mobile WiFi calling works on one of the other systemless roots?

I'd be willing to provide a log or other needed information if someone could point me in the right direction.

Thanks.
[SuperSU] Ja_som:
Please read last post from [MENTION=631273]Chainfire[/MENTION] here:

http://xdaforums.com/showthread.php?p=64224716

Why you want to use 2.52 when you can use 2.61 with which you don't need to patch boot manually.
[SuperSU] mobileman88:
Set /system to read write mode. Google if you do not know the commands.

Then

touch /system/xbin/su

touch /system/bin/su

reboot
[SuperSU] GiGiSSiMo:
Because with 2.61 i can't temporaly disable root, and i use this function for the home banking app, so i prefer the traditional and not experimental way...
[SuperSU] Ja_som:
So you need to search for it maybe on your device forum, or make it yourself.
[SuperSU] kundica:
T-Mobile WiFi calling works on my Galaxy S6 using SuperSU 2.61.
[SuperSU] jineshpatel30:
there is no such files in "xbin" & "bin" folder as i used system less mode !

( and i didn't allow twrp to install it's own su as recommended by [MENTION=631273]Chainfire[/MENTION] )
[SuperSU] ettore88:
Hi!!!Supersu 2.61 works on Samsung S5 g900f CM13?
[SuperSU] Chainfire:
FYI, this is fixed in v2.62, which will be released today or tomorrow or so.
[SuperSU] GiGiSSiMo:
I've searched and i don't know how to make it: i wouldn't ask here for help indeed.

Thanks a lot.
[SuperSU] haseoxth:
Hi folks, have some confusions when using the latest version of SuperSU.

I rooted my nexus 5 (running android 6.0.1) with the latest SuperSU 2.6.1 (using the systemless way) and find some apps on my phone can't detect root permission properly or working fully functional, then I try to root it again with the system method and find the issues I had before get resolved.

Just feel curious whether anyone have the same issues as me.
[SuperSU] Neverendingxsin:
What he means is on a nexus 6p with 2.61 systemless root on 6.0.1 doesn't stick after the first reboot. I'm on stock 6.0.1 and can confirm that after any kind of reboot my phone no longer has root access and I have to reflash 2.61.
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

Just a quick update on this - I tested on my M8, running Google Play Edition, and I also tested on CM13, and in both cases, SuperSU 2.61 rooted them fine. It's only on my A9 with the symlink getting overwritten that I still have an issue. And based on your recent posts, I'm assuming that's fixed in 2.62 ;).
[SuperSU] shipping guppies:
Thanks. But I should have been more specific: I meant a cryptographic checksum :o
[SuperSU] jc monkeyballs:
Are you on 6.0.1 ?
[SuperSU] Chainfire:
Try again with 2.62 when it's out.

Working fine for me on my 6P ...

Thanks, and yes, should be fixed in 2.62, let me if it works when it's out.

You're going to have to be even more specific, as the MD5 posted earlier is a cryptographic checksum.
[SuperSU] Neverendingxsin:
Tell me if i did something wrong, I was on stock 6.0 with 2.52 system root. I flashed the 6.0.1 image via fastboot (everything but userdata and recovery) then in TWRP I flashed the 2.61 systemless root and rebooted. Then granted root access to all my apps. Rebooted back to recovery, flashed the latest franco kernel that only works with the systemless root and when I rebooted root access was gone.

I've tested it by just normally rebooting and it doesn't stick. Did I mess up getting it flashed correctly?

Nevermind, rebooted again and all is good :)
[SuperSU] haseoxth:
Thank you for the response sir Chainfire, I will keep an eye on the future updates and let you know the result after testing it on my device.:good:
[SuperSU] Evo_Shift:
I like to use adaway and delete/modify my system apps and sounds quite a lot. Can systemless root do that? It seems like people mostly want it so they can use OTA updates or whatever which to me isn't an issue since updating isn't very hard even when rooted. If systemless root becomes the standard way to root your phone (chainfire said 2.52 is going away earlier) will we still be able to modify the system if we want? It seems like no since one of the notes in the OP of the WIP thread about systemless root says not to mount /system " /system should never be remounted r/w, I hope I didn't miss anything here". Wouldn't that be needed to do the things I want to do?

Edit - I see chainfire said we could still edit system if we want in post #3470. I think I just need to step back and forget about it for awhile, lol...I am just confusing myself now. I will stick with the old way on my 5X for now it looks like due to issues specific to that device.
[SuperSU] mlin:
At this point I've been using 2.52 simply because there are apps, including Chainfire's own CF Lumen, that do not seem to properly detect root using the systemless method. Once the systemless method works as reliably as the system method -which it sounds like may be the case in 2.62- I will gladly switch to the systemless method. I know you weren't talking to me, but those are my reasons for wanting to use 2.52 over 2.61.
[SuperSU] sirxdroid:
I fully understand 1-3 above (even before you posted this). All I was looking for was an easy way to do #4 above so that broken apps that expect su somewhere in /system. continue to work. Otherwise it doesn't really matter to me whether root is system or systemless, I'm not concerned at all at this point about modifying /system all I want is for apps to continue working (things like TiBu, ES File Explorer, etc)

Thanks.
[SuperSU] shipping guppies:
Ah yes, I should have written (cryptographically) signed checksum. This all is about knowing that the package has been generated by a reliable source (hopefully you).

I think your work is rather important and significant that it deserves high protection!

Suggestion: something along: "sha256sum *.zip | tee /dev/stderr | gpg -a --sign"
[SuperSU] Theliels:
and that is the reason you need to enter this command, which it does is create two blank files, since some applications look for those files specifically to see if your device is rooted or not
[SuperSU] Chainfire:
I am not aware of any issues with the latest CF.lumen version and systemless root. Works fine on all my devices here.

I gave you an md5 of the ZIP. The APK inside the ZIP is cryptographically signed automatically, and (should) contain the same files in assets/ as the rest of the ZIP does. Besides, you're download it from either XDA or my own download site (any other source would be stupid).

If you can't trust what is posted here, where did you expect me to post my certificate safely? By mail?

Long story short: no.
[SuperSU] kundica:
No. S6 5.1.1 stock.
[SuperSU] mobileman88:
Your can try

Rootcloak to get around this
[SuperSU] GiGiSSiMo:
So i've to install also exposed framework... I prefer wait some days and having 2.62 [emoji2]
[SuperSU] Ja_som:
It's OK ;)

As Chainfire wrote a while ago I also don't have any issue with CF.lumen, also all apps which I use does not have issues with systemless root, except Secure Settings, but still it works (GPS switch in Tasker).

Also I think that systemless root with boot autopatch is easier to flash, I don't need to search for new patched boot images...

Chainfire does a very good job in this :) ?
[SuperSU] mlin:
Strange. When I loaded it up on my Nexus 6p rooted using the systemless method and SuperSU-v2.56, the app seemed to detect root permissions because I didn't get the initial message of "... we won't look nearly as good as with root..." So I figured all was well, root was detected and the app would work fine. However, I quickly noticed screen filtering didn't look as effective as with traditional root methods. Strangely, I'm not sure if this makes sense, but it almost looked like it was somewhere in between root and no-root, which from a coding standpoint probably isn't possible. Once I switched to the traditional method, CF Lumen resumed doing its job the way I know and love (fantastic app BTW, one of my must haves for any device!). I'll try again when 2.62 is released. Thanks for the response and all your work!

---------- Post added at 09:05 AM ---------- Previous post was at 09:00 AM ----------

Thanks, maybe something funky with 2.56. I'll try again with 2.62. I totally agree systemless is easier, but it just wasn't delivering the results I expected. Perhaps there was some user error on my part.
[SuperSU] pikachukaki:
Hi can i install this supersu without twrp so i can take the OTA's without re-flashing stock recovery all the time??
[SuperSU] Rapper_skull:
Creating those two files works, but now TiBu fails to run /system/bin/su
[SuperSU] sirxdroid:
I think you need to reboot your phone. SuperSU is supposed to replace those empty files with the correct ones on boot. At least that's what I understand from scanning this thread, I haven't tried it myself.
[SuperSU] corkiejp:
It is possible just to boot TWRP instead of flashing it and use that to install supersu.

fastboot boot <name(& location) of TWRP image>
[SuperSU] qdroid:
If I flashed 2.52 system beta on the Nexus 6p but want to switch to 2.61 systemless, do i have to remove 2.52 system prior or will applying 2.61 systemless handle this? If I do need to remove 2.52, how do I do that?

Thanks
[SuperSU] mrRobinson:
Yep. That's exactly what I do.
[SuperSU] Captain_Throwback:
Unfortunately this isn't an option for everyone :/
[SuperSU] CatThief:
Thank you for that. Seriously, this is exasperating. If any of these people haven't done their systemless homework, or homework on any root method for that matter, they shouldn't be messing around with root in the first place. And I say that most sincerely.
[SuperSU] Neverendingxsin:
Adaway works fine for me on 6P
[SuperSU] Rapper_skull:
Thank you, it works now.
[SuperSU] vacsed:
If I understand correctly, those blank files will be created on the system partition, which again modifies system and defeats the purpose of a systemless root installation as OTA will not recognize the system partition as being genuine and therefore refuse to update anything...
[SuperSU] Ja_som:
You mean 2.52 not 2.62...

You need to reflash your system and maybe also boot (not sure, but will be better to do it), then flash 2.61...
[SuperSU] jcsww:
I don't think most people care about being able to receive OTA's. If a new factory image comes out, people usually flash that long before the OTA will hit their device.
[SuperSU] tsadev:
Just to elaborate on [MENTION=631273]Chainfire[/MENTION]'s response earlier, I don't think you fully understand what you are asking for. As Chainfire already told you, MD5 IS a checksum, which when used with a MD5 verifying tool will tell you if the file you have downloaded is from Chainfire or not. Here's a good read that will tell you about MD5.

EDIT: Did some reading of my own and saw that MD5 isn't the most secure out there in comparison to other algorithms available, though as Chainfire said, you should be downloading the files from XDA or Chainfire's own site anyways. The rest of the argument below still stands though.

On a side note, that command will pipe the sha256 checksum from the given input to the tee command, which will pipe it's output to gpg, which will do nothing because --sign isn't correct (most implementations require -sign). And even if that command successfully runs, all you are doing is creating a signature of a signature. Why?

I'm not sure why you're writing to /dev/stderr in that tee command either.
[SuperSU] IronTechmonkey:
Good point, although there is at least one group of people who would have to accept OTAs even if willing to re-flash a stock image: Those who got stuck with a device that never experienced an OS update and have not available stock Image (an unfortunate and increasing trend with MoForola).

---------- Post added at 01:45 PM ---------- Previous post was at 01:42 PM ----------

If one is available /\
[SuperSU] ashyx:
[MENTION=631273]Chainfire[/MENTION]

Is there anything untoward in this recovery.log which is preventing root on the Tab S2 sm-t710?

http://pastebin.com/fAufmsZW
[SuperSU] Theliels:
of course, any modification on /system invalidate Google Pay or OTA, but I think this is irrelevant for most. Ideally we want root and continue to receive and update OTA directly, but even with systemless mode you ca¡n't do it, you have to flash boot anyway.

On a personal side, I prefer/need access and change my system partition, not only to modify the hosts file, but to delete content, add myself and others.
[SuperSU] sirxdroid:
Oh, there are other Android devices out there besides Nexus? :)
[SuperSU] Captain_Throwback:
I'm not Chainfire, but from looking at that log, it seems that su.img never gets created because of this error with make_ext4fs:

CANNOT LINK EXECUTABLE: cannot locate symbol "using_default_flexbg" referenced by "make_ext4fs"...

Seems like a busybox/toolbox issue, unless make_ext4fs is being built from source, in which case you have a bad version (and maybe using the busybox/toolbox version would be better)
[SuperSU] chazall1:
I got everything up and running yesterday on my Nexus 5. All working as expected. I know you backup the stock_boot image file in /data/. I have two backed up stock boot images. I had SuperSU 2.60 first and I have 2.61 currently. Do each of your upgrades create a new stock boot image? and can I delete the old ones?

Thanks
[SuperSU] osm0sis:
Good catch. It's dynamic and needs to be static to work universally most likely.

Edit: Hmm it's a recovery command, not an included binary.. so not sure why the linking error. [MENTION=631273]Chainfire[/MENTION] might need to do some of his LD_LIBRARY_PATH magic to fix it up or there's something wrong with the recovery build you're using.
[SuperSU] Ingenium13:
That's the point.... The touch command simply creates empty 0 byte files with those names (so it should in theory work on devices with 0 free space on /system). The SuperSU boot script takes care of making them point to the new location and in effect turns it into system root.

Sent from my Nexus 6P
[SuperSU] shipping guppies:
Hi Chainfire,

Okay, one last question:

Why is the ZIP file (not the APK inside) internally signed by "android@android.com" ? :confused:

(you are right, the interal sigature of the ZIP is even better than checksum suff ;)
[SuperSU] osm0sis:
Google "android test keys" ;)

Allows it to be flashed in "stock" AOSP-built recoveries.
[SuperSU] alessio89g:
Hi, I just flashed Official MMB29K, in my Nexus 5 and SuperSU 2.61 SystemLess, but I have an issue:

ES File Explorer doesn't prompt me for root permissions; if I try to enable "Root Explorer" toogle in the left panel, a message says that the Test failed, bla bla bla.

But other apps have successfully obtained the root permissions.

What the hell?!
[SuperSU] TsarFlow:
Same here. Pro version.

Envoyé de mon Nexus 6 en utilisant Tapatalk
[SuperSU] Pkt_Lnt:
As stated before. The dev of ES File Explorer probably has hard coded to look for su in /system and not it is not there. Please notify the ES File Explorer dev to update it for systemless root.
[SuperSU] IronTechmonkey:
Touche! :) and while I'm here: Along that distinction of Nexus/Stock and Non-Nexus/Custom I'd like to correct an unintentionally false report of an issue i made earlier. Although it is likely the more experienced SuperSU folk know this it seems a few others experienced it it so:

When flashing recent CM13 official nightlys, an old habit of enabling native CM's native SU after ROM flash/first-boot but before flashing SuperSU was preventing SuperSU from assuming control of app SU permissions. It makes sense (although I dont fully understand the mechanism) but, having gotten away with doing that in CM11 and CM12 for so long I was still doing it and may not be the only one. So, if SuperSU 2.61 flashes OK on CM13 but does not assume app SU control make sure native CM is not enabled before flashing SuperSU. I dont know if disabling native CM SU after flashing SuperSU works.
[SuperSU] haseoxth:
Or you can wait for the future updates of SuperSU and try it again, as Chainfire said before 2.6.2 will have some workarounds for these "incompatible" software.

If you know how to modified a kernel you can also using the non-systemless method to root your phone just like before.
[SuperSU] PuNcAkE_15'l:
[MENTION=631273]Chainfire[/MENTION] same thing happens with 2.61
[SuperSU] sirxdroid:
Too bad you can't actually contact them, the emails sent to their contact address bounce back. ES is not what it used to be ... looking for alternatives ...
[SuperSU] smitharro:
Finally have the 2.61 working on my Moto G 2014 with CM13/Android 6.0.1. All is running fine, but the first boot took some time...

Written with my XT1068 using Tapatalk on CM13
[SuperSU] ArclightX:
Solid Explorer is what you're looking for. Seriously give it a go you won't be disappointed.
[SuperSU] smitharro:
ES Explorer working fine here (SuperSU 2.61):

View attachment 3570892

Written with my XT1068 using Tapatalk on CM13
[SuperSU] Ch3vr0n:
Cyanogen file manager here :P

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] jcsww:
I use Root Explorer and haven't had any issues with systemless root.
[SuperSU] Cares:
Here's my logcat on a fresh boot. I'm on a Nexus 6P with Android 6.0.1 and SuperSU v2.61.

I'm getting "Android is starting" message for a couple of seconds after every boot. I would greatly appreciate it if you could diagnose my issue. Thank you!
[SuperSU] Pkt_Lnt:
Quote the two having problems, not me, I don't use ES File Explorer.
[SuperSU] osm0sis:
Try FX File Explorer. Been my favorite for awhile now.
[SuperSU] mtw4991:
N6P, 6.0.1, encrypted, currently rooted with SU 2.52. Can I delete 2.52, flash stock boot image, then custom kernel, then 2.61 to get system less root or do I need to reflash system also? And do I need to reflash vendor.img again prior to 2.61?
[SuperSU] pkelly517:
Heresy!
[SuperSU] tsadev:
You can, but....

Per Chainfire's previous posts, if you want support on any issues that may arise then you must have a stock /system. I don't know about vendor.img though, you'll have to get a reply from the other N6P users here.
[SuperSU] TonySuperPony:
That's because you are on Cm. There is an su binary on the system partition from cm itself. The app sees that and acknowledges that root is on the system.

On nexus Rom, there are no su binaries on system. So es thinks there is no root and does't even bother to look for it anymore. :)

Verstuurd vanaf mijn A0001 met Tapatalk