yashsingh1/xdaforums huggingface dataset:
[SuperSU] ashyx:
You can install v2.52 or v2.56 on any rom (obviously along with required ramdisk changes)

Only mm triggers systemless install with v2.56 otherwise it will use normal system install.
[SuperSU] Lrs121:
That's exactly what I'm facing. It can call su and I can grant it permission but it never actually can use it for root level access.
[SuperSU] swieder711:
Thanks for the reply.

What are the ramdisk changes that are needed? Were they needed for 2.49 so that i might already have the changes?

If I am going to install a rooted ROM for MM than should I just plan on using v2.56?
[SuperSU] Mitul007:
How do I install SuperSu on moto g xt1033? Running on android 6.0 cyanpop
[SuperSU] ffejy462:
I'm using the same device. 2.52 works great with lp and mm stock roms (using it on other devices as well). No other modifications or changes needed. Just flash in recovery. I'd guess you might have had a bad download. Download again and reflash.

mxpe 6.0
[SuperSU] Chainfire:
Once again, system-less is currently not supported on 5.x, regardless of how you edit the ZIP. There's also code in the binaries that needs to be adjusted. It will be here soon, chill.
[SuperSU] ashyx:
Thank you. :)
[SuperSU] joeski27:
I am currently running the 12/2 nightly of CM 13 on my Nexus 5, and have tried getting 2.52 and 2.56 to flash and work. I have been able to get the phone to boot after 2.56 has flashed, however I try to update the binaries and it never works. I don't know what else I'm missing here, just never had this much trouble (or any trouble, actually) getting SuperSU flashed on my phone. Anyone have any idea what I'm missing here??:confused:

Ugh, nevermind, I forgot I need to update the bootloader, dammit. That'll have to wait til I get home from work :(
[SuperSU] Primokorn:
CM nightlies have a built-in zip image for the bootloader and the radio. SuperSU 2.56 doesn't work for now. Use Superuser until CM got it fixed.
[SuperSU] joeski27:
Thanks, I do that for now. I'm just trying to get rid of that damn # symbol in my status bar, don't care which root app I need to use to do it!

So in a nutshell, is the bottom line that no current version of SuperSU works with the CM 13 nightlies, and that it is specifically a CM 13 issue? If so, its been like pulling teeth to find that information over the last 24 hours, been going nuts trying to figure out why this update to the CM 13 nightlies isn't as easy as it should be.
[SuperSU] coukou:
Hello,

I'm using Galaxy Note 4 on Lollipop 5.1.1 rooted and TWRP 2.8.7.0

I've installed SuperSU Pro 2.49, it works just fine ;)

However, I've a stupid question :rolleyes:

What are the "best" settings to get SuperSu working optimized?

Regards
[SuperSU] osm0sis:
Bug / Info for everyone:

Bug:

Info for everyone:

Idea:

TWRP Bug to be aware of:

Idea:

Welcome back [MENTION=631273]Chainfire[/MENTION]! Hope you had a good vacation. Here's a lot of what you missed. :)
[SuperSU] joeski27:
Incidentally, and I don't if this matters, but I did get 2.56 to install, but I was never able to update the binaries. I'm using Elemental X and I've heard that some people have gotten 2.52 to run while using custom kernels. Any thoughts?
[SuperSU] Lrs121:
My bad, I didn't mean for it to come across a pushing for quicker support. I figured that the binaries weren't coded to support apis less then 23.
[SuperSU] Primokorn:
Yep, you have either a bootloop or binaries cant' be installed AFAIR. I guess it's due to toybox (used instead of busybox).
[SuperSU] mlevin:
Many thanks.

Have folks had good success with this systemless root approach on MRA58R? I'm about to give it a go...
[SuperSU] IronTechmonkey:
Confirming this. In CM13 (on Moto E XT1511) with SuperSU v2.46 installed from playstore, attempt update binaries within OS failed. v2.46 and 2.52 flashed.from recovery (TWRP 2.8.7) result in bootloops. The busybox/toybox switch does seem to be jamming up a lot of stuff. Although, in this case, SuperSU is not needed for root and native CM SU has come a long way, SuperSU is the only thing that keeps Better Battery Stats happy for all of its statistical collection, particularly partial wakelocks.
[SuperSU] Chainfire:
Had a bunch of last minute issues to solve. Not today. Maybe tomorrow!

Most of the patching code is ready, but I still need to update code in the APK and do some more testing.
[SuperSU] jesssiii:
My Angler arrives tomorrow. Where are these posted, exactly? I did search (found this post) but am confused about where the modded kernels are being posted.
[SuperSU] p1nky:
I have Nexus5 with Marshmallow and ElemantaryX Kernel, flashed SuperSu 2.52 via recovery and got root. But within OS it shows SuperSU free 2.46 and always to update binary. What to do to got 2.52 within OS and stop Update Messages?!
[SuperSU] Chainfire:
So I got side-tracked a bit trying to figure out why some devices (such as the 5X) won't remount /system r/w anymore, even with selinux and verity disabled. Going to drop that for now, but if someone has the answer, please do let me know.
[SuperSU] LLegion:
Thanks for the update bro!
[SuperSU] coukou:
No one can help:confused:
[SuperSU] ashyx:
Unless you have reason not to just leave everything at default.
[SuperSU] Frank Westlake:
Maybe someone with a 5x can help troubleshoot by copying the mount command from an older version and call that specifically.

ADDED:

Someone might say this is unlikely; true, but it is possible so it should be tested.

Frank
[SuperSU] fhem:
here
[SuperSU] jackdubl:
Where's everyone getting 2.56 from? I can't find it.
[SuperSU] Captain_Throwback:
The link is literally in the post before yours.
[SuperSU] jackdubl:
Doh!
[SuperSU] coldheater:
does anyone have 2.56 Systemless working on their Nexus 6P with MDBO8L?
[SuperSU] sanjoth:
Error using BETA version

Nexus 5 D820

Unlocked MRA58N Android 6.0

I booted twrp into the bootloader to install the supersu(v2.52) beta zip file so as to keep my stock recovery and ota survival.

Installation was complete without any errors in the terminal.

Results :-

-> Bootloop during the 4 dots of loading.

-> Tried to fix it by factory reset,wiping cache. Boot loop persists.

-> Installed factory image of MRA58N and it was running fine, then i screwed it up again by trying to install a newly downloaded zip file which gave the same result i.e Bootloop.

-> Now running stock 6.0 without supersu

Please help with this issue and let me know if a version can run without the bootloop, as I just need the root functionality.

Thanks
[SuperSU] skulldreamz:
Flash this in custom recovery (twrp)

https://www.dropbox.com/s/skbsswb59g3pgsm/BETA-SuperSU-v2.52.zip?dl=0
[SuperSU] santadomingo:
Okay I read all threads about root, but is a way too root n5, without the problem the akku accurance on Marshmallow ??

I hope I write this right,!! My English not so good
[SuperSU] livinginkaos:
Yep
[SuperSU] Chainfire:
Some more showstoppers today, sorry folks.

While the current development version seems to work fine on an array of nearly clean Nexus devices running stock 6.0 (and CM13 too), I've run into some serious issues on my heavily loaded on root apps S6 running 5.1. So I need to figure out that issue first, and/or re-test the Nexuses with a lot more root apps loaded, competing for favors. And it's midnight already :)

To be clear, I don't even think this issue is related to systemless or the modified kernels, rather just a combination of factors.
[SuperSU] coldheater:
can you send the links from the files that you used?
[SuperSU] livinginkaos:
I created my own boot.img from stock. The method is well documented here on xda. Do some research. The best way is to learn what you are doing.
[SuperSU] shoey63:
Hi Chainfire.

It seems flashing the systemless root 2.56 zip changes /system from R/O to R/W, resulting in the unpleasant "your device is corrupt and may not boot properly" message when one flashes back the stock boot.img (On Sony MM concept rom for Z3, not sure about nexus devices). And even worse, when attempting to update, ThisView attachment 3565812 Occurs. Is there an easy fix, besides dd'ing the system.img prior to flashing the modified boot.img and rooting?
[SuperSU] osm0sis:
Sounds like the TWRP bug where if system gets mounted r/w at all it immediately changes recovery-from-boot.p to recovery-from-boot.bak. Whereas expected behavior would be if the "mount ro only" option has been set it should respect it on its end regardless of what happens in the terminal or a zip. :(

[MENTION=4878287]_that[/MENTION], is this something that's getting fixed up in the newer TWRP version?

Best solution I've come up with so far is to avoid it and only mount r/w when necessary in my AK2 zips (and explicitly mount ro if we need to check build.prop), and for my upcoming AIK release I have it check for systemless root and make it change the install directory depending:

suimg=$(ls /cache/su.img /data/su.img 2>/dev/null);
if [ "$suimg" ]; then
mount -t ext4 -o rw,noatime $suimg /su;
target=/su/bin;
else
busybox mount -o rw /system;
target=/system/xbin;
fi;
[SuperSU] _that:
The "mount read only" affects only TWRP itself - it does not prevent other programs from mounting /system writable.
[SuperSU] osm0sis:
Understood, but what I'm saying is the expected behavior is that TWRP should respect the "mount read only" setting and not itself modify /system even if a zip or terminal mounts /system rw at some point This is currently not the case (e.g. as soon as a zip mounts /system rw, TWRP throws away the "mount read only" setting and goes ahead and changes recovery-from-boot.p -> .bak and whatever else TWRP normally does to a rw system). Can that be fixed?

Edit: [MENTION=4878287]_that[/MENTION] Sorry, I see how this is kind of confusing to explain. Hopefully I did a better job this time.. Basically, no matter what a zip does to /system, I want TWRP itself to continue to act like /system is untouched because that's what I set it to do.
[SuperSU] Chainfire:
v2.60 BETA / system-less / automated boot image patcher

Good news everyone, I just posted v2.60 BETA in the WIP thread. The changelog for v2.60 can be found in the STABLE thread, as always.

As the post title implies, this version contains an automated boot image patcher. It works well on all the devices I have tested so far, but it's tricky business. You should flash back a stock boot image before installing this BETA. If you installed SuperSU into /system previously, you need to re-flash stock /system as well.

Please, make sure you have a backup at the ready, and the time and knowledge to reflash your entire device back to stock, before continuing. If not, let others guinea pig and await the results.
[SuperSU] osm0sis:
Working great! I flashed it over hammerhead MRA58N's boot.img, then for bonus points flashed my AK2 zip of franco.Kernel r76 over top of that. :D
[SuperSU] GROGG88:
Hammerhead and Flo working great. Cheers!
[SuperSU] santadomingo:
Here on the Hammerhead too!! Great work!! Thanks
[SuperSU] starbase64:
HTC One M9 (htc_himauhl:6.0/MRA58K/668948.601) rooted without problems.
[SuperSU] lePoMo:
Had this too (with 2.56 aka "systemless root").

My interpretation:

It happened because a previous SuperSU APK was still installed.*

Solution (for me):

Extract Superuser.apk from the common folder in the zip file (the one you flashed via TWRP), and install that on the phone (like you'd install any apk. copy over and open).

---

* I'm kind of confused by this, because at first look, the following code (only executed in case of a systemless install) in the "update-binary" file (don't let the name confuse you, it's a shell-script) in the zip should have remove the old apk and replace it with the new one:

APKPATH=eu.chainfire.supersu-1
for i in `ls /data/app | grep eu.chainfire.supersu`; do
APKPATH=$i
rm -rf /data/app/$APKPATH
break;
done
mkdir /data/app/$APKPATH
set_perm 1000 1000 0755 /data/app/$APKPATH
cp_perm 1000 1000 0644 $COM/Superuser.apk /data/app/$APKPATH/base.apk

ok, having checked that dir (/data/app), i've got multiple folders

drwxr-xr-x system system 2015-11-28 18:54 eu.chainfire.supersu-1
drwxr-xr-x system system 2015-05-24 17:46 eu.chainfire.supersu-2
drwxr-xr-x system system 2015-11-28 20:09 eu.chainfire.supersu-4

judging by the folder modification dates, I'll assume the first one was the one created by the script in the zip, the second one is an old install.

And the third one I can only guess stems from when I manually copied over the superuser.apk (and opened that (letting it install)).

My attempt at an explanation:

The guilty line in my case then is "break", but only because something else provoked >1 folders a long while back. (the "break" only makes a difference with >1 folders).

(just for completeness' sake: the script not entering the loop would produce the same result. as in: it would also work on folder ending in "-1")

[MENTION=631273]Chainfire[/MENTION]:

why the "break" when installing the systemless way?

when doing a classic install, you're removing them all

rm -rf /data/app/eu.chainfire.supersu-*

I'm assuming there's a reason:

From the way your code works, you want to reuse the place the app was previously installed if it was already installed. From that I assume that to update an app that was previously installed you need to reuse the same folder (further assuming android keeps track of where an app was installed).

In that case I guess that if there's multiple folders, finding the right one is a lost cause anyways, bar a simple rule like "highest number wins". One way I can see is to copy the new apk to all the folders the script finds, touch a file clean_up_later.txt in each one, and later clean up duplicate folders from within the app when it finds such a file. (assuming the app knows what folder it was started from). Even if no cleaning up is done afterwards, it shouldn't have a negative impact (instead of outdated apks, there'd be mutiple times the same apk).

As usual with me, sorry for all my guesswork, the assumption is that my babbling can be read and discarded quickly if it's useless ;).
[SuperSU] petrus764:
Worked perfectly on my stock and encrypted N5X, thanks for your great work!
[SuperSU] chikimonke:
Working great so far on N6P, encrypted, MDB08M build with Cataclysm installed over top and flashing [MENTION=3685904]ak[/MENTION] 's kernel after the fact.
[SuperSU] provolinoo:
2.60 requires to flash stock boot back, is a restore of boot partition from twrp backup enough?

I made it just after I flashed stock image.
[SuperSU] KenjiHannya:
Working great on OnePlus One + Darkobas ROM + OpenGapps Pico + SuperSU 2.60

Tnx for u great work ?

?
[SuperSU] dlb4all:
Gonna test it on N5 CM13 with ElemantalX kernel . Hope it works ...
[SuperSU] santadomingo:
Do it and you now it!! [emoji3]
[SuperSU] p1nky:
thanks lepomo, i have managed to install the 2.52 apk within os

i also looked at the /data/app where is only one supersu folder (eu.chainfire.supersu-2) which has actual date.

but when i open supersu or after every reboot i still got the "binary needs update" messages
[SuperSU] provolinoo:
CM13 is already prerooted, no need to flash supersu

Ps

As far as I know, ElementalX is not compatible with Cyanogen
[SuperSU] dlb4all:
I know its preroot by i hate that damn # in status bar .

aaand YES . ElementalX is 100% compatible with cm . ive tested it on cm11 , cm12 , cm12.1

and even on cm13 which it worked flawlessly in all of 'em
[SuperSU] RandomPooka:
The app liveboot requires SuperSu to function. I personally don't like the controls for the built in root on CM. There's reasons that you would need to flash SuperSu on CM. TiBu keeps reporting that the included su binary needs updated and may cause errors and checking the box that says to stop warning about it won't stick. Basically, SuperSu is FAR superior to the CM root and it's utterly ridiculous that CM has their source code deviated far enough from AOSP to keep a bunch of apps from working 100%, or even at all.

ElementalX worked fine with cm13 on Nexus 6 (shamu), but I don't know if it works on all devices.
[SuperSU] vt0r:
Should be fine, yes.
[SuperSU] SamuriHL:
I tried it out on my S4 GPE 5.1 OK1 build and it works fine. Apparently when I tried 2.5.6 I did not get system less as it didn't have the proper binary support as Chainfire mentioned. Very interesting. In any case, this appears to work just fine now. Thanks, [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] chazall1:
2.6 working great on Nexus 5 (Hammerhead), running latest Cataclysm and elementalx 6.6. Thanks for your dedication.

Great work, Thanks
[SuperSU] dbzgod:
Tried on Canadian Note 4 running latest clean stock build of 5.1.1 OK3 resulted in a boot loop.
[SuperSU] DarkHeart Z:
[MENTION=631273]Chainfire[/MENTION] that's really really appreciatable what you are doing . But if I had to unroot without factory reset what I will do then ? my device is android one and I have rooted and flashed custom recovery without unlocking the bootloader . Everythings fine . The bug you said we would encounter actually I did . No major issues so far . Just one . please provide a unrooting method . That will be all :)
[SuperSU] SamuriHL:
Flash your stock boot img.
[SuperSU] DarkHeart Z:
That will remove the su.img and all other components of it too ? I mean complete removal will occur ?
[SuperSU] SamuriHL:
The SuperSU app, meaning NOT the su binary, may still be installed on the data partition, but, root will be completely removed by flashing the stock boot img, yes. HOWEVER, let us caution that if you use root to make modifications to the system partition, which system less root does not do itself, then whatever you did to the system partition must be reversed, as well (i.e. flash the stock system img). But yea, system less root is pretty kick ass in this way.
[SuperSU] kr33:
Stuck in bootloop after 2.52 flash via TWRP

[MENTION=631273]Chainfire[/MENTION], I flashed this version via TWRP on the LG G3 (D855), i've wiped both Dalvik & cache, but now I'm stuck in a bootloop, and ideas why?

Much appreciated
[SuperSU] DarkHeart Z:
Thank almighty google doesn't use AI to detect modifications in system partition :D

---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------

Use the latest version 2.60 . It has bootimg patcher too . And keep in mind it's for android 6.0 only for now .
[SuperSU] SamuriHL:
Depends on your device. Some devices like the Nexus 6 use block patching rather than file patching. This means that ANY change to the system partition causes an OTA to fail.
[SuperSU] DarkHeart Z:
LOL . If I remove the modifications from system partition all will be good right ? my device is android one . Well kinda nexus device though .
[SuperSU] SamuriHL:
Not sure on your device how the ota works. Maybe.
[SuperSU] DarkHeart Z:
I hope it does . Otherwise I have a backup plan for it . only an AI system can detect modifications even after if I remove it before flashing OTA .
[SuperSU] peecs121:
So to flash on Cataclysm 6.0 Nexus 5. Should I flash stock kernel with the newest beta then reflash custom kernel?
[SuperSU] kleinerpogo:
SuperSU 2.60 didnt quite work on HTC One M8 with latest CM13, I had SuperSU installed from PlayStore, deleted it, and then flashed. I get SuperSU-Requests when starting i.E. a root-Task with Tasker, but not only SuperSU is force-closed when started, but also Settings -> extended Settings (where NFC and stuff is) is forced closed when trying to open.
[SuperSU] radonsg:
For v2.60, do I still need to flash the modified boot systemless image before supersu zip? Thanks.
[SuperSU] provolinoo:
Is it possible to have systemless root on CM13?
[SuperSU] drawde40599:
2.60

2.60 working flawless on 100%/Stock MDB08M . N6P

Thank you
[SuperSU] muniz_ri:
BETA SuperSu v2.60 resulted in continuous bootloop on the Samsung G920T running the latest 5.1.1 OJ7 build. Worked great on the Samsung G900T running that devices latest 5.1.1 build.
[SuperSU] CatThief:
[MENTION=631273]Chainfire[/MENTION]

Root is working flawlessly with v2.60 on 100% stock MRA58N (Nexus 5). Outstanding job!
[SuperSU] thaidroid:
An ODIN version of 2.6 would be absolutely brilliant if all you want is root.

I just rooted GPE 5.1 on an I9505 with a clean bootloader, worked perfectly.
[SuperSU] daywalk3r666:
2.60 works perfect on my moto g 2014 with cm13.
[SuperSU] swapnildixit3:
2.60 works well but do I need to flash it every time when I install new CM 13 update?
[SuperSU] daywalk3r666:
i think yes because the cm update installs the stock kernel
[SuperSU] vjtigas:
Does the automated boot patcher work for Android One devices? The first generation has MT6582.
[SuperSU] merothh:
[MENTION=631273]Chainfire[/MENTION] 2.60 working perfectly on moto g 2013 running cm13..You could add it to the list of devices tested !!
[SuperSU] abdyasar:
2.60 works great on my note 4(n910c) 5.1.1
[SuperSU] sNiPe78:
Guys, a question.. After installing 2.60, can we install OTA without issue even if we have installed custom kernel, busybox ? I know the OTA check the genuiness of the system before applying update, so I'm wondering
[SuperSU] tetakpatak:
It is really hard to answer what will happen after so many modifications. Should the problems occur, they wouldn't be necessarily SuperSU related.

So, possibly it would be better to ask this question in another thread, like your kernel's development thread, or your ROM's development thread.

tetakpatalked from N7100
[SuperSU] Taomyn:
[MENTION=631273]Chainfire[/MENTION], confirming it worked perfectly on my Nexus 6, it even kept my previous changes for AdAway. Great job [emoji106]
[SuperSU] jesssiii:
Like to know this as well.
[SuperSU] radonsg:
Tested. Don't need to.
[SuperSU] yaoppp:
Thank you Chainfire! It's a great work! I'm currently using a nexus 5x with latest 6.0 stock version, and TWRP recovery. The 2.60 systemless root method works great on my phone. Though I have some questions:

a) What will the ota check before it starts to update, the /system partition? Will it check /recovery and /boot as well? Since I disable (not uninstall) some of the system apps, like Google games and YouTube, etc, will it corrupt the ota update?

b) When deploy the original root method, we still need to flash a modified boot image. And the systemless root method also based on a modified boot image. What's the difference between them?

Please don't spend too much time on my question. Just a little bit curiosity.

Thank you again!
[SuperSU] kr33:
Thanks, I downloaded 2.60 from another thread, will reflash the CM13 rom and and this binary in TWRP and see what happens. :D
[SuperSU] TCattd:
Tested on Oneplus One with latest Sultan's CM13 build, and is working fine.

Thanks Chainfire :)
[SuperSU] jclm73:
May I have the link please?

Envoyé de mon LG-D855 en utilisant Tapatalk
[SuperSU] burduli:
Where is 2.60 beta?
[SuperSU] JulianJenner:
SuperSU2.60 You can find there: http://xdaforums.com/showthread.php?p=64161544

RedmiNote1W - 5.12.3 MultiROM
[SuperSU] teddy0209:
For sense/htc yes, but for nexus devices it works on stock or custom roms...
[SuperSU] kr33:
I flashed the SuperSU 2.60 and now I get SECURE BOOT verification error, my phone won't boot now...Is it it something it Missed? I flashed supersu 2.60 via twrp
[SuperSU] robygt:
Flashed 2.6 on Shamu from 2.52 on Tesla MM all seems fine. Is this right ?

Inviato dal mio Nexus 6 utilizzando Tapatalk
[SuperSU] TR2N:
Nope. You should reflash ROM to get rid of 2.52...
[SuperSU] thaidroid:
Found two things one is an issue. GS I9505

When you flash a new kernel you loose 2.60 root, just reflash 2.60 and all is fine again.

The issue,

I tried to add my favorite ringtone using RomToolbox Root Browser (.ogg file) on GPE 5.1 OK1 on 2.60 root and it would not let me write to system/media/audio/ringtones

It actually ends up creating an empty file with the correct name.

Uninstalled 2.60 using SU apk and flashed SuperSu 2.52.zip and that allows me to install my own ring tone.