yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
Do you remember if any Samsung OTA updates were applied to the OJ7 device? Like security policies and such?

Try going to recovery and removing all the contents of "/data/security" (but not the directory itself), and see if that helps.

CFAR will be updated soon enough.

For now, yes. It's on the list to make a solution for, but keep in mind CM13 isn't exactly the priority.

The SuperSU installer makes a backup of the stock kernel. If /system has not been remounted r/w and busybox was installed to /su/bin instead of /system/[x]bin, using the "Full Unroot" option in SuperSU->Settings might allow the OTA to succeed. But the more you modify, the smaller that chance becomes.

(1) Generally only boot (not recovery) is checked, but OTAs may fail when done in TWRP instead of the stock recovery. Merely disabling apps (though depending on the method) generally should not influence /system, and should not break OTA.

(2) One installs to /system, the other doesn't.

Which device?

It's weird, XBIN mode is the original systemless mode used for various exploits. And you're still seeing 2.52 instead of 2.60. Something is wrong.

I think 2.52 was installed in /system and you didn't reflash /system, like put in bold in the instructions (...)

That's a strange issue but with this little information there's no way to know what's going on here.
[SuperSU] c3k:
For what I know:

1) OTAs (until today) check only system partition, disable a system app (with titanium?) should not make alterations

2) Systemless do same operation as previous one, plus it create a link (bind mount) to the su binaries that physically are now on /data partition instead of /system
[SuperSU] kr33:
[MENTION=631273]Chainfire[/MENTION], i am using the LG G3 D855....I completely wiped everything on my phone via TWRP.../Data /System etc. The phone booted fine before flashing Supersu 2.60, then after flashing and wiping both Dalvik/cache thats when I get the secure boot error verification message.
[SuperSU] burduli:
[MENTION=631273]Chainfire[/MENTION] sir, will 2.60 BETA work on unofficial AOSP 6.0 build? I'm just going to perform clean flash of Marshmallow and then flash SuperSU 2.60 BETA.
[SuperSU] Chainfire:
Is it an unlocked international G3 ? Or a carrier-branded US one ? Or... ? Which Android version does it have ?

I'm not intimately familiar with the G3. I do have one here somewhere, but it's a Korean version.
[SuperSU] Chainfire:
I don't know. Please let us know the results of your test ;)
[SuperSU] kr33:
It's the unlocked international version. I was using CM12.1 (Stock was Lollipop) on it before I decided you move to Android 6.0 (CM13), but unfortunately as soon as I install SuperSU 2.60 i get that error and the phones doesn't boot further. I'm not sure what I'm doing wrong here :)

I also want to just say thank you for your time and hardwork on SuperSu...as well as your responses in trying to help :good:
[SuperSU] TonySuperPony:
Is there a solution for ota survival of the kernel? For example: If I flash an update of Cyanogen mod. And it overrides the kernel, is there a method to automatically reapply the kernel patch. Or do we have to reflash?

Verstuurd vanaf mijn A0001 met Tapatalk
[SuperSU] Chainfire:
OK, so what you're saying is: "2.60 ZIP installer doesn't work on the LG G3 D855 on CM13" (which nightly?) . That's a lot more information than you originally provided.

I'm not sure what is going wrong either at this point. Will need some investigation. Does CM13 use it's own kernel or stock kernel on the D855 ? Is it CM13 or the bootloader throwing this message ? Probably you can't answer these questions and I'll have to look at it myself at some point. Again though, CM13 is not my priority at this time.

Again, CM13 is not the priority. That being said, for CM specifically, I think an update survival mechanism is certainly possible and will probably be built soon enough.
[SuperSU] burduli:
It worked great! I don't know if it touched /system partition or not but my device has proper root privileges. Here's what I did:

Wiped /system, /cache, /data and /boot partitions.

Flashed Marshmallow and Gapps minimal package.

Booted into system (Just to make sure that ROM works).

Flashed SuperSU 2.60 BETA.

Booted into system and checked root.

One more time, it works great, thank you very much :) I also installed SuperSU Pro from Play Store.

P.S. The device is Samsung Galaxy Grand (GT-I9082) running unofficial AOPS 6.0 build by [MENTION=3117667]pawitp[/MENTION]
[SuperSU] muniz_ri:
I flashed the zip immediately after a full OJ7 firmware flash via Odin so there were no security updates applied. But i went ahead and removed the contents of data/security anyway but device continues to bootloop.
[SuperSU] Cares:
The process was easy to get on v2.6. The thing I do notice though is that boot time increased maybe 10-15 seconds. Should this be normal behavior?

Also even previously on 2.52 and also 2.6 I always get the "Android is upgrading" message for a second on boot. It doesn't actually upgrade anything and boots up. Is that normal?
[SuperSU] eradicator006:
2.60 does not work on my lg g3 d852 running CM13. The zip appears to install with no issues. Once you reboot after you flash the 2.60 zip I get a secure boot error and the led cycles from red, blue and green.

From what I understand with the g3, the kernel needs to be 'bumpd'. The stock cm kernel is bump'd. After running the supersu auto patcher I'm guessing that the kernel is no longer bump'd.
[SuperSU] Wake89:
I'm having some trouble with this. I Have a N7 2013 I got on black friday, I let it update to marshmallow OTA before I ever flashed anything to it.

I unlocked the boot loader, but I am unable to put any files onto the root of the device. Windows cannot access it. I ended up flashing TWRP but TWRP can't mount the internal storage (among many other folders) so I can't copy and past any zip files from the emulated sd card to the root of the drive. Basically it's impossible to flash zip files from TWRP.

So I have to leave TWRP on and sideload the SuperSU file onto the device. It claims success but when I boot into M, SuperSU says the binary wasn't installed.

I went back to stock using the stock package from google. I then tried flashing the modified boot.img and then SuperSU 2.52 but it still doesn't work. the log screen on TWRP says it basically can't mount any of the directories. everything is red.

I don't think I can get anywhere until TWRP is able to mount those partitions, but neither the modified boot.img nor SuperSU 2.60 are able to make any changes to the device.
[SuperSU] d.cortez:
although my device was not listed - Note 5 SM-N9208 - I ODIN flashed the latest OK2 firmware, installed SuperSU 2.60 and device bootloops upon reboot. just sharing my observations/experience. steps followed:

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 install and reboot to confirm flash worked, i rebooted to Download mode and install TWRP

4 install SuperSU 2.60 via TWRP

5 reboot device and device bootloops (w/message that Kernel is not SEANDROID enforcing, expected)
[SuperSU] Blac Caesar:
[MENTION=631273]Chainfire[/MENTION]

Systemless v2.60 working perfectly on OnePlus One, latest CM 13 Nightly
[SuperSU] robygt:
Dang, yes, I'm guilty of all charges, didn't re-flash /system.

Inviato dal mio Nexus 6 utilizzando Tapatalk
[SuperSU] ashyx:
[MENTION=631273]Chainfire[/MENTION] Similar situation for a member on the galaxy tab s2 forums.

Flashed a previously unrooted sm-t810 with v2.60 on 5.1.1 OJ1 firmware and it bootloops.

The boot images are standard boot images so should work.

Also need to ask a question regarding the manual patching way.

Now that [MENTION=631273]Chainfire[/MENTION] has made supersu v2.60 compatible with 5.1.1 is it still viable to patch the ram disk manually for systemless root?
[SuperSU] provolinoo:
:confused::confused::confused:
[SuperSU] Nbay64:
[MENTION=631273]Chainfire[/MENTION] Systemless v2.60 is not working on my Samsung Galaxy Tab S2 SM-T710 running on Android 5.1.1. It puts my device into a bootloop upon reboot.

Here are the steps I took:

1. I ODIN flashed 5.1.1 T710XXU2BOJ1 firmware (latest release for my device)

2. After ODIN flash is complete, ODIN initiates a reboot

3. After system install and reboot to confirm flash worked, I rebooted to Download mode and installed TWRP

4. Made a backup in TWRP

5. Installed SuperSU 2.60 via TWRP

6. Rebooted device and device bootloops (w/message that Kernel is not SEANDROID enforcing, expected)
[SuperSU] illuminae:
I own a Nexus 5 running Android 6.0, unrooted, locked bootloader, encrypted, and no custom recovery. Can I just flash the boot.img using adb too root my Nexus without unlocking my bootloader and thereby resetting my phone? Or is that not how it works. Would appreciate a hint :).
[SuperSU] ginkage:
Tried rooting my Nexus Player (fugu) with it. Failed at first, but then I added one line:

if [ -z "$BOOTIMAGE" ]; then BOOTIMAGE=$(readlink /dev/block/by-name/boot); fi

to the META-INF/com/google/android/update-binary file (obviously, to the "Boot image patcher" section), and it succeeded! Awesome! :)

I know the path should have been /dev/block/platform/intel/by-name/boot, but for some reason I had it there...
[SuperSU] Ingenium13:
Anyone know how to manually setup a unionfs or overlayfs mount to get apps like SecureSettings to detect root? It seems the required kernel modules aren't present on stock Android.

Sent from my Nexus 6P
[SuperSU] kaodd:
Galaxy S5 Neo SM-G903F

the device is on stock and not in your list, but i have to ask: can i use "systemless root" ?:fingers-crossed:
[SuperSU] Return2legacy:
OnePlus One:

CM 12-06 nightly + xposed v78 + pico opengapps

Root works but the system-less root option is grey.

The phone reboots automatically at the first time then it boots normally.
[SuperSU] veesix:
Noob question about systemless root v2.60:

I am currently on 6.0 MRA58R (Nexus 6), rooted and unencrypted with 2.52. Will I stay unencrypted going with 2.60 and reflashing stock boot.img and system.img?
[SuperSU] Chainfire:
Not sure about the boot time (though first boot after ZIP flash could be significantly slower). The Android is upgrading thing should have stopped with 2.60 (everybody has this on 2.56), but perhaps rebooting into recovery, manually removing all /data/app/eu.chainfire.supersu* and /data/data/eu.chainfire.supersu* folders, rebooting, and re-flashing the ZIP will solve this for you.

I have put investigating the 'bump'ing on my todo list.

New flo's have a new flash chip revision, and the version check in the kernel source needs to be changed from v6 to v7 (http://pastebin.com/qnXepmGq). This hasn't been done on the latest TWRP for flo, that is why it does not work. I have pinged Dees_Troy about this (again) - I ran into this issue before myself. In the meantime, the MultiROM/F2FS fork version of TWRP for flo does work - https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img.

No, you need to unlock your bootloader first (which will wipe your data), then flash TWRP, then flash the 2.60 ZIP through that TWRP.

Sorry, I do have a Nexus Player but I hadn't tested it yet. It's in use at my TV. I have put this on my todo list to fix - thanks!

As mentioned many times in this thread, unionfs/overlayfs is on the todo list, if we had that working it would be included.

We won't know until you try.

What do you mean system-less root option is grey? There is no system-less root option.

I'm not sure what is going on with these Samsung's. It's working great on my Note5 (G920T) on OJ5 and S6 on OI9. Downloading K5 now, to see if it makes a difference.

Are any of you able to pull a dmesg and/or logcat before it reboots?

I'm surprised it completely reboots in any case, rather than just declines giving you root.

EDIT: What are your firmware's fingerprints? (adb shell "getprop | grep fingerprint")
[SuperSU] SamuriHL:
I'll give it a go on my OK1 Note 10.1 2014 and see what happens. Will take a while as I gotta remove 2.5.2 first and reinstall stock through ODIN. I'll report back later.
[SuperSU] Wake89:
Thanks for the help, it worked. Here are the steps in case someone else has a brand new N7.

1. unlock bootloader

2. flash twrp multi rom 2.8.7 (posted by Chainfire in post #3169)

3. adb sideload SuperSU 2.60

4. i dont know if this is necessary, but I did it because someone else said they had to do it. After SuperSU finishes, TWRP will give you a big 'reboot system' button. Instead, I went to the home screen of TWRP, pressed 'reboot', then 'bootloader'. A message popped up saying SuperSU binary wasn't installed, would I like to install it. I swiped to confirm. If you just press 'reboot system' supposedly you won't get the prompt to install SuperSU binary.

5. Boot into Marshmallow. Update SuperSU from the play store.

6. SuperSU will say the binary will need to be updated, press to continue. In my case, update of the binary failed even after reboot. However, it still works, everything says I am rooted.

I haven't played around yet much, so I haven't seen any side effects yet.

Edit: after every reboot, a notification comes up saying the SU binary needs to be updated. I guess I can just try to turn off notifications.
[SuperSU] ink718:
Hello, can someone explain difference between tradition rooting and systemless root. And what is the benefit of systemless root? Someone with knowledge and not "think" please ☺
[SuperSU] IronTechmonkey:
I may have seen this also, while exploring boot stalls when flashing SuperSU 2.52 via TWRP 2.8.7 onto Moto E XT1511 with CM13 unofficial and official nightlys after about 11/1/15. Today with the CM13 12/6/15 nightly SuperSU 2.60 flashed OK but did not take control of SU access leaving native CM SU in charge, and in SuperSU settings an item/toggle mentioning systemless was grayed out.. which makes sense considering CM13 doesn't need SuperSU for root. Maybe this is what [MENTION=6854589]Return2legacy[/MENTION] saw.
[SuperSU] SamuriHL:
Ok, got that done. Works fine on OK1 on the Note 10.1 2014. Thanks, [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] Return2legacy:
Enable Superuser
Not (currently) available in system-less root mode

Install SuperSU into /system
Not (currently) available in system-less root mode

The options above are grayed out.

Is this normal for non-nexus devices?
[SuperSU] Wake89:
One more question.

Using the SuperSU 2.60 version of modding the boot.img and providing root, is SELinux still enabled and enforcing?
[SuperSU] timeToy:
2.60 Systemless working fine on US Moto X style with Marshmallow update.

:good:
[SuperSU] eradicator006:
Got 2.60 working on my g3 d852 with cm13. I installed supersu through twrp. I then extracted the supersu modified boot image using dd. I then used this method to bump the image: http://xdaforums.com/lg-g2/development/tools-bump-kernel-offline-t3073261 After bumping I flashed the bumped boot image and everything works as it should.

Bumping doesn't look too complicated. It could be integrated in to your script.
[SuperSU] IronTechmonkey:
Normal may be a relative term with this type of (core to the system) and pace of (rapid) development.

This one I dont really understand but it does not seem weird, and It is certainly better than a boot-stall.

This makes sense on a rooted ROM such as CM13.

Also, If you haven't already done so, peruse the various SuperSU threads (there are several) including the OPS and recent posts.
[SuperSU] thaidroid:
Problem solved maybe it's a GPE issue(SamuriHL explained it to me) the system is not mounted in 2.60 it is in 2.52

Anyhow make a Ringtone and a Notification folder on your SD card and put your favorite sound in the respective folder and off you go.

At least that works on GPE 5.1:D:D
[SuperSU] foxsprout:
Should I use this 'systemless root', but I decided to install other cool stuff like Xposed, others. that are supposed to modify /system partition, can I proceed with OTA should new firmware is pushed?
[SuperSU] elreydenj:
Does this mean with 2.60 that we don't have to flash a systemless boot.img prior to flashing SU in order to use systemless root?
[SuperSU] swallowingled:
Correct. The new 2.60 automatically modifies boot.img. Just flash the original stock boot.img before flashing 2.60.

http://xdaforums.com/showpost.php?p=64161125&postcount=3
[SuperSU] dbzgod:
Doing this fixed it and systemless root is now working on Canadian Note 4 SM-N910W8 Stock OK3 5.1.1 .

I also noticed that there was an issue with the SE Policy that prior to updating to the OK3 build the previous build of OI4 from October, its SE Policy was still in effect. Deleting the security SE Policy OTA update caused the built in one from Novembers firmware to take its place.

Also after applying and rebooting, it boot looped once then successfully booted.
[SuperSU] ncsuwolfs:
put new systemless root on my mom's 6P so i could turn noise cancellation off through build prop. im assuming this keeps her from getting otas the normal way? only asking since root is systemless, does ota see build prop edits?
[SuperSU] osm0sis:
With a 6P it patches the whole system partition, so OTAs will fail after any change to /system, no matter how small.
[SuperSU] ncsuwolfs:
Thanks, that's what I assumed.
[SuperSU] ConnorAAVance:
So if the GS6 on 5.1.1 was rooted this way, it could work for the GS5, right? Or am I completely misreading the information?

More specifically, the GS5 on AT&T.
[SuperSU] Alxoom33:
Appears to work great. Root checker says I'm running 2.60. However, my SuperSu Pro appln still says 2.56. I have a N6 running.Cataclysm MRA58R.

Edit: Deleted Super Su app and reflashed Su 2.60 zip with a Cache and Dalvic wipe and all is good!
[SuperSU] PuNcAkE_15'l:
Can someone help on my htc one m8 I'm using cm13 latest build and I have root but it's like the default application I can't get supersu when I try to flash v2.56 it doesn't boot and I have to wipe whole phone and install o.s through pc and I really want supersu
[SuperSU] prathameshsd:
[MENTION=631273]Chainfire[/MENTION]

SuperSU-v2.60-20151205163135.zip working fine on my Moto G2 (2nd Generation) XT1068 running on Official Android 6.0 Marshmallow Soak Build.

Edit 1 : Root Access Lost After Rebooting.

Edit 2 : Restored TWRP Backup & Flashed v2.60 Again, Root working.
[SuperSU] lucarp78:
I rooted successfully my Samsung Galaxy Note Edge SM-N915FY with stock fw N915FYITV1COI1.
[SuperSU] :
Can i use the 2.60 on cm12.1 on xperia z2? I like to be uptodate and have latest version ;)
[SuperSU] Cares:
I did this but no luck. I rebooted with both folders deleted and wiped cache and dvalik and I get "Android is upgrading" even without flashing SuperSU.
[SuperSU] diehard2013:
greetings fellow cyanides,

I just finished flashing the latest cyanogenmod 13 nightly on my nexus 7 (2013).

lt was wiped and formatted prior to that.

l also immediately flashed the latest openGapp nano (zip queue) followed by a factory reset and wipe.

Reboot and now l have CM13 fresh.

Should l enable Root under Developer's Options before rebooting into TWRP 2.87.0 and finally flashing (installing) the su2.6.0 beta zip from Chainfur?

is he aware of this new conflict?

Thank you!!
[SuperSU] Maabus95:
V2.60 working great on my old S3 d2can running latest release of [MENTION=4551784]matrixzone[/MENTION] Unofficial CM13 thanks very much [MENTION=631273]Chainfire[/MENTION]
[SuperSU] Chainfire:
This in fact half-breaks the SuperSU installation. Do not let TWRP auto-install SuperSU. If you don't have issues now, you will have issues down the line.

The description certainly implies so.

Yes.

I'm not sure I will though, this is a device-specific thing.

Only left is to produce a logcat, which will list errors while booting, and fix those.

Uninstall all copies of SuperSU (through settings->apps), then reflash the ZIP.

Examine logcat, find the error, and fix it.

No you need not, and what conflict ?
[SuperSU] Chainfire:
I'm not sure what is going on with these Samsung's. It's working great on my Note5 (G920T) on OJ5 and S6 on OI9. Downloading K5 now, to see if it makes a difference.

Are any of you able to pull a dmesg and/or logcat before it reboots?

I'm surprised it completely reboots in any case, rather than just declines giving you root.

EDIT: What are your firmware's fingerprints? (adb shell "getprop | grep fingerprint")

EDIT#2: If TWRP told you your device was not rooted, did you let it auto-install it? If so, that is probably your problem.
[SuperSU] kaodd:
Galaxy S Neo

doesn't work on SM-G903F :crying:

seems like impossible to root this device !

Maybe just maybe you can help us out :fingers-crossed:

Some guys try to do something there http://xdaforums.com/galaxy-s5/general/galaxy-s5-neo-sm-g903f-user-thread-t3207909/page30

regards

kaodd (noob)
[SuperSU] jib@rmi.ge:
Is it safe to combine 2.56 boot image with the latest ElementalX kernel on Nexus 9 wifi (volantis)?
[SuperSU] jacomail95:
Edit: Deleted
[SuperSU] Wyneg:
Super su v2.60 installed in CM13, moto g xt1040, nightly 07/12!

I tried to use Greenify, but automated hibernation doesn't work, simply don't lock screen, but Supersu gives superuser permissions... ¿?

Thanks!
[SuperSU] Pkt_Lnt:
You need to ask in the Greenify thread.
[SuperSU] bitstra:
Confirm, that SuperSU 2.6 (systemless/experimantal) runs fine with [ROM][OFFICIAL][THEA][6.0] Cyanogenmod 13.0 [UNIFIED] nightlies, on

Motorola moto-G 2014 LTE (thea)!

Tested with CM 13 stock kernel...

- Switching user per app with SuperSU Pro works too!

Thanx [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] ashyx:
[MENTION=631273]Chainfire[/MENTION], is it still viable to manually patch the ramdisk for Samsung 5.1.1 boot images for use with v2.60 systemless root or has the method changed since v2.56?
[SuperSU] shoey63:
There are some slight changes that 2.60 does to the ramdisk that are different to the "manual " method.

I think Chainfire will release another update which assumes the necessary modifications have already been done.
[SuperSU] Taomyn:
Damn, after saying it worked with SuperSU-v2.60-20151205163135.zip on my stock but encrypted Nexus 6 I noticed it hadn't as the app still said v2.56

I saw a response from [MENTION=631273]Chainfire[/MENTION] about uninstalling the app from Settings,Apps then reflashing the ZIP, so I did the following:

Uninstalled the app

Reflashed, everything except recovery as I wanted to keep TWRP

Booted into TWRP

Flashed SuperSU-v2.60-20151205163135.zip

Rebooted

When I finally was able to access the phone, I discovered no sign of SuperSU :(

I rebooted again to TWRP reflashed the ZIP once more, and still not there.

So extracted the Superuser.apk from the ZIP, copied it to the N6 and installed it manually. Apart from having to authorise all my apps again, things have remained working.

Same thing happened with my Nexus 9 LTE - perhaps something to do with encryption?
[SuperSU] teinwhite:
Thanks for this!

I have v2.6 running on an N6 without any (apparent) issues.

I ended up not flashing /system, but told SuperSU to prep for full unroot. Rebooted into bootloader. Flashed boot.img from MRA58R. Went into recovery, flashed v2.6 and then flashed the latest Elite kernel. Told TWRP to reboot system and when it said that root wasn't installed, told it to skip it.

Booted into the OS and installed SuperSU Pro. Have full root again. Settings shows v2.6.
[SuperSU] corkiejp:
Haven't used system-less myself.

But the latest ElementalX kernel will modify the boot image for supersu, so you don't need to flash the boot image.
[SuperSU] d.cortez:
[MENTION=631273]Chainfire[/MENTION], thanks for replying... fingerprint info below:

- PS C:\WINDOWS\system32> adb shell "getprop | grep fingerprint"

- [ro.build.fingerprint]: [samsung/nobleltezt/noblelte:5.1.1/LMY47X/N9208ZTU2AOK2:user/release-keys].

later today, i will try 2.60 root process again and try to grab dmesg or logcat.
[SuperSU] :
I really don't know :(
[SuperSU] Cares:
Not sure what to look for in logcat to diagnose what is causing Android is starting message. There's thousands of lines. Should I search for a particular phase?

Sent from my Nexus 6P