yashsingh1/xdaforums huggingface dataset:
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

Tried 2.61 on my A9. While it does appear to root the device successfully, there is an unfortunate side effect - my removable storage is no longer mounted. I believe this may be related to the fstab modification somehow, because that's where my external SD card gets mounted. I'm not sure how to determine that for certain, though. What can I do to help troubleshoot this issue? I have confirmed that when I manually modify my boot.img and flash 2.56, this isn't an issue. Thus my conclusion that the patcher is somehow at fault.

EDIT: Or maybe it's related to sepolicy?

EDIT 2: I see what happened - it broke a symlink that's in my ramdisk. The fstab that gets used on my device is fstab.{ro.hardware}, where ro.hardware=htc_hiae. However, in this case, fstab.htc_hiae is just a symlink to fstab.qcom, which is where all the magic actually happens. I noticed that your patcher looks at pretty much anything named fstab.* and attempts to patch. Is there a way to prevent the patcher from breaking the symlink?

EDIT 3: Or, alternatively, just looking for symlinks and automatically skipping them? Or replacing them from the original boot.img?
[SuperSU] buhohitr:
You stated it worked on 10.1 note 2014? Not for me.

1) Flashed full stock 5.1.1 firmware. Bootup and verified no root.

2) Flash twrp, then boot to twrp

3) Flash Supersu 2.6.1 (also tried with 2.6.0), reboot...and boot loop. Stucked at Samsung logo.

I did this twice and same issue. I saw logs on the screen and they all normal, no failing.
[SuperSU] SamuriHL:
And you DID NOT allow TWRP to root the device during reboot.....RIGHT? Cause if you swipe yes to allowing TWRP to install the su binary, well, that's not following directions. If you did NOT allow TWRP to install the su binary, then I've no idea. It's working fine for me on build OK1.
[SuperSU] s3v3ngal:
Hi tested 2.61 on my s5 kltedv running [MENTION=3322708]albinoman887[/MENTION] cm13 12/03 build and supersu is working perfectly thanks [MENTION=631273]Chainfire[/MENTION] keep up the great work mate
[SuperSU] buhohitr:
Nope, TWRP did not prompt me to root. btw, what twrp version you used? 2.8.7.0 (none touch version)?

edit: Is it possible that you tested with the patched kernel?
[SuperSU] rub1k:
Would like to test rootless 2.61 on a Nexus 6 (shamu) currently running 6.0.0 (mra58k) factory image while upgrading to 6.0.1 (mmb29k) factory image.

Since 2.61 performs boot image mods on the fly since 2.60, can I just go ahead and flash stock 6.0.1 (mmb29k) boot.img prior to installing SuperSU 2.61 via TWRP?

Does the 2.61 script make the necessary fstab edits to disable forced encryption (since a custom boot.img is no longer used with 2.61)? My phone is currently not encrypted and would like to keep it as such...
[SuperSU] SamuriHL:
Yup. I would recommend reflashing the entire OK1 firmware in ODIN, then start over. Flash twrp 2.8.7.0, reboot directly into it, then flash supersu zip. After that it should work fine.
[SuperSU] sirob71:
Tested 2.61 with Nexus 6 6.0.1 - it works.

Dirty upgrade, flashed to stock, fastboot boot twrp image, flashed supersu 2.61. Done.
[SuperSU] jcsww:
I had downloaded 2.60 a few days back when it was posted. I didn't notice there was a new version until after upgrading my Nexus 6 and Nexus 6P to 6.0.1. Everything went fine using 2.60 on both devices.
[SuperSU] chazall1:
I have a boot loop on my Nexus 5, Latest Cataclyism with EX 6.6. Was just flashing from 2.60 to 2.61 in TWRP, Followed the directions. With 2.61 I did not receive a prompt from TWRP to install SuperSU as this happened when I installed 2.60.
[SuperSU] ddominator:
2.61 works on Nexus 5X with stock 6.0.1.

Battery is showing what it was prior to flashing 6.0.1 and rooting. (it's not over 9000).
[SuperSU] veesix:
Good question, I'd like to know about this too ;)
[SuperSU] Midomad:
Same here.

Flashing back 2.60 did not solve the problem.

Dirty flashed the rom and kernel and it boot.
[SuperSU] Mercado_Negro:
2.61 working fine here on N6 6.0.1. Flashed all factory images because I wanted.
[SuperSU] sirxdroid:
Any plans to provide /system versions of SuperSU that automatically patch the kernel, just like the systemless version? Or at least patched kernels for the latest 6.0.1 for Nexus devices?

(I can't move to systemless yet because of a couple of bad apps that don't work with systemless.)
[SuperSU] mbirth:
Tried 2.61 on my Nexus 9 without success. Dirty-flashed official 6.0.1 factory image. Let it boot and create ART cache. Flashed TWRP 2.8.7.1, used it to apply SuperSU 2.61. Nexus 9 booted, restarted the boot process (was afraid it was a boot loop), then came up. SuperSU icon was there, but complained about a missing su binary.

EDIT: Okay, I uninstalled SuperSU and did the procedure again. This time, it worked. Maybe it was some conflict with the old SuperSU binary/APK.
[SuperSU] IronTechmonkey:
I was curious because of the known issues with boot-stalls in CM13 on some devices but your case sounds different. Thanks.
[SuperSU] corkiejp:
Worked for mine.

I flashed just the boot, vendor and system.

Let the device boot up.

Flashed TWRP 2.8.7.1

Used that to flash ElemetalX Kernel and SuperSU 2.61
[SuperSU] PuNcAkE_15'l:
Please help when I try to flash 2.60 or 2.61 on htc one m8 running latest cm13 it doesn't boot up so I have to do a restore a backup to get it to boot. I have root but I don't have a root manager app it's just managed by privacy guard or something
[SuperSU] sirxdroid:
It worked because ElementalX already patches the ramdisk.
[SuperSU] Cares:
Well even on a new clean flash of 6.0.1 with SuperSU 2.61 I still get the Android is starting error.
[SuperSU] street_dog:
Hmmm...why didn't i think of that? :) I will give it a try...
[SuperSU] SamuriHL:
On....what device?
[SuperSU] Cares:
Nexus 6P
[SuperSU] Alxoom33:
On Nexus 6 running 6.0 MRA58R with Cataclysm Mod. 2.61 flashed with no problems over 2.60 but still got the Root Your Device notify from TWRP 2.8.7.1
[SuperSU] ashyx:
OK Chainfire will probably shake his head at this, but I can't help it I'm inquisitive. :rolleyes:

I modified v2.6.1 so systemless flashed on a stock Samsung 5.0.2 rom.

Everything went fine, boot.img got patched and su daemon runs.

However when trying to run any root apps I do get the superuser pop up requesting root access which gets granted. I see a nice toast message saying that app has been granted root permission. Yet it actually doesn't as it still doesn't have root permissions even though when opening superuser it clearly states access has been granted.

Tried Root Checker which also apparently gets root permission, but it doesn't and says root access not available.

Now here's the thing. All this time Superuser is nagging me to update the su binary, so I let it via normal method . After a short time I get the update failed message and to try again.

However I don't need to because now I have full root access and Root Checker confirms root and all root apps are now working.

I checked where the su binary is and it's still only located in su/bin and it seems no modifications to system have happened.

When I reboot I'm back to square one and need to go through the update binary routine again, which always fails, but gives me root anyway.

So not sure what that does, but it works.

This is not a bug report or anything just an observation due my tinkering.
[SuperSU] MG386:
Yes, 2.61 does allow for /data to remain un-encrypted. works fine here. flashed factory image, booted twrp, flashed 2.61, rebooted. still unencrypted. I need to stay on system root because of an app that doesn't request root properly, wondering if i can use modified boot image from MRA58K...
[SuperSU] adrman:
2.61 working perfectly on Angler/stock 6.01. Updated all images except userdata and formatted cache via fastboot, booted to twrp, flashed 2.61 and rebooted to system, denying twrp the opportunity to root.
[SuperSU] Ingenium13:
I haven't tested this, but from looking at the script in the SuperSU.zip file, I think you can do the following after installing systemless root:

adb shell
su
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
exit

And then reboot.
[SuperSU] swapavi:
On the latest 6.0.1 factory image for Nexus 6 and using supersu 2.61 and root appears to work, but when trying to uninstall system apps using TiBu or straight from Root Browser, it acts like it deletes, but when i reboot my phone, all the apps are still there.. So root isn't actually working for that it seems...
[SuperSU] Wake89:
Ah crap. I can uninstall the app, how do I get the binary out?

And once I do, should I reflash 2.52 (since 2.60 already modified my boot.img) or should I install 2.60 again?
[SuperSU] muniz_ri:
v2.60 is definately not working on the G920T OJ7 build but just tested v2.61 and after a couple bootloops it booted up successfully with full root access. Good work.
[SuperSU] drewski_1:
v2.61 working on N7 2013 LTE (deb) with latest 6.0.1 :good:
[SuperSU] Fredro:
did you flash the stock boot.img too? So no need to use modified boot.img?
[SuperSU] Richard_Black:
Any workarounds for the 3k+ battery display bug? everything else seem to work just fine.

On Nexus 6 6.0.1.
[SuperSU] sbd01:
So I updated my N7 2013 to 6.0.1... Unfortunately the old SuperSU 2.52 system root with ElementalX 5.05 doesn't work anymore and causes a bootloop. I do NOT want systemless root or on the fly boot.img modifications, as I don't understand how to disable it and really am more comfortable with using a custom kernel for root anyways (plus some apps like Secure Settings don't play well with systemless). Is there any way to use a 6.0.1-supported version that doesn't modify my boot.img or tamper outside of /system? Thanks.
[SuperSU] Raj d:
Hi,

Can i flash and use SuperSU v2.52 or 2.56 on KitKat Rom?
[SuperSU] aaronc_98:
Where is 2.61 download? I only see 2.52 in OP.

thanks,
[SuperSU] MG386:
This seems to have worked. I need secure settings to work with tasker, and apparently the app hasn't been updated and calls for root permissions in the wrong place. This will work until secure settings gets updated. thank you very much.
[SuperSU] aaronc_98:
Where to dl 2.61?
[SuperSU] drewski_1:
The WIP thread. Also stickied in this forum
[SuperSU] adrman:
Yes. Flash the stock boot image. 2.61 generates it's own modified boot image upon flashing.
[SuperSU] Itachisasuke:
On the Nexus 5X using the traditional root method with BETA SuperSU 2.52 and the modified boot.img from the MDB08I/MDB08M Build causes the camera to not work. The camera never starts and just displays a black screen. To confirm I reflashed the system and boot images from the MMB29K Build and the camera is now working properly.

It seems that we will need a modified boot.img from the MMB29K Build for traditional root with a functioning camera. on the Nexus 5X

Is it possible to use the automated boot.img patcher found in the 2.61 release in a traditional root methodology? Any information is appreciated.
[SuperSU] GROGG88:
You can create a boot.img like many of us had in [MENTION=631273]Chainfire[/MENTION]'s absence, or simply use systemless...
[SuperSU] Itachisasuke:
Creating a modified boot.img for this build sounds like a fun project. Perhaps I will tackle that tomorrow.

The only reason I haven't moved to systemless root yet is because AdAway isn't cleanly working with it without using simlinks and shell boot scripts. Other than that systemless would work great for my needs.

I appreciate the direction.
[SuperSU] GROGG88:
NP. Here's some useful tools for you: https://github.com/grogg/mkbootimg_tools
[SuperSU] deusfaux:
AdAway doesn't work with systemless? What about ES File Explorer, TiBu, Wakelock Detector? There's no point to me updating and achieving root if I can't use the #1 app I need root for.
[SuperSU] Itachisasuke:
Thanks so much for the tools. I was able to unpack the boot.img from the latest MMB29K build and use the sepolicy file from unpacking the modified boot.img from the MDB08I build. I repacked the MMB29K boot.img with the modified sepolicy file and flashed it. Now I have traditional root and a working camera. Thanks again. Was a great learning experience.
[SuperSU] silvertrain78:
Adaway worked perfectly for me with systemless root, as did TiBU.

Nexus 6P

Android 6.0

Edit: systemless root Adaway worked without any extra steps/processes. If the system partition doesn't have enough space, I've seen it require symlinks (with my Nexus 5, for instance). But with the 6P, the stock system partition has enough free space to accommodate a modified hosts file.
[SuperSU] Itachisasuke:
Thanks for the information, I just created a modified boot image for traditional root but I am interested to see if the systemless option with the Nexus 5X MMB29K Build works with AdAway and TiBU. From what you are stating it should work.

Edit: Everything is working using the systemless root SuperSU 2.61 on the MMB29K Build on the Nexus 5X. Thanks to [MENTION=3667193]GROGG88[/MENTION] and [MENTION=5884954]silvertrain78[/MENTION] for the information and guidance.
[SuperSU] Sugarkryptonite:
Is it possible to modify the build.prop using 6.0.1 Shamu with the latest system-less root method? I can't seem to get it to save my build.prop modifications, even with read/write permissions using various different file explorers...very annoying just to modify the DPI a bit.
[SuperSU] SuperSmashedBro:
On my Nexus 6P with 6.0.1, I tried to use systemless root (2.61) and it gets reset each time I restart my phone. Anyone else have this issue? This occurs on 2 Nexus 6Ps that I've tested.

Installing a custom kernel fixed it
[SuperSU] susanta Hazra:
What is root
[SuperSU] Pkt_Lnt:
answer
[SuperSU] diehard2013:
good one!
[SuperSU] :
Not very friendly that an easy question is ignored
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION] SuperSu v2.62 experimental works on Galaxy J2 (SM-J200G). Some users report some apps not identifying root but most apps do work. Thanks for all the effort!
[SuperSU] mobileman88:
I read some reported Titanium backup working. Mine seems to be unable to detect root. Is there something I am doing wrong?
[SuperSU] mobileman88:
TiBU and Adaway does not seem to detect SU. Not sure what I could have done wrong.

I flashed MM 6.0.1 , booted into TWRP , installed SuperSU 2.61 . Then reboot into the phone. My Titanium Backup and Adaway do not detect root.
[SuperSU] PunkUnity:
Just looked through the last 5 pages and see no question that you asked.... what is your question good sir?
[SuperSU] zohaib0001:
[MENTION=631273]Chainfire[/MENTION]

New SuperSu v2.61 is system less now so

can you make a new SuperSu v2.61 install able through windows ?

I mean make a install able pack through windows for those who did not have recovery installed.
[SuperSU] Ja_som:
I had also a issue with Titanium, not with root detect, but I uninstalled some system apps, and after restart there were back. I think Titanium needs BusyBox, because when I installed BB then Titanium was working without any problem.

And I had no issue with AdAway...
[SuperSU] :
My question was if i could use the 2.60 or 2.61 on cm12.1 on sony xperia z2, too
[SuperSU] PunkUnity:
Does regular supersu not work?
[SuperSU] mobileman88:
It's probably due to conflicting supersu due to my phone being rooted normally before I flashed system and then installing supersu 2.61. I got it all working again by doing the following :

1. Uninstall supersu

2. Boot to TWRP

3. Flash supersu 2.61

4. Reboot

5. Install supersu pro from play store

Tibu and Adaway now works. As for busybox, I understand TitaniumBackup comes with its own independent copy of Busybox so it should not be any issue at all.

---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------

I had to do the steps in the post http://xdaforums.com/showpost.php?p=64202079&postcount=3340 to get it all working again.
[SuperSU] CatThief:
[MENTION=631273]Chainfire[/MENTION]

Root is working flawlessly with v2.61 on 100% stock 6.0.1 MMB29K (Nexus 5). Once again, outstanding job!

SuperSU even retained my apps permissions from v2.60
[SuperSU] :
It works but i like to have the latest version. But i think i'll stay at 2.52
[SuperSU] mobileman88:
The latest is 2.61 which is systemless rooting. However, it's still in the beta stage.
[SuperSU] szale9001:
So question for [MENTION=631273]Chainfire[/MENTION] , or anyone that can confirm. For those of us that use custom kernels with this new systemless autopatcher: When we flash a newer version of our custom kernel, would we need to reflash SuperSu 2.6 as well? Just wondering if there is an inbuilt method already to detect this/repatch the kernel or not. Thanks.
[SuperSU] gismoZ:
Both v2.60 and v2.61 work flawlessly on LG G2 Mini (D620R) running CM13.
[SuperSU] white7561:
System less root works only on marshmallow or working on lollipop too?
[SuperSU] gismoZ:
It works on lollipop too.
[SuperSU] mattcoz:
I'm in the exact same boat... well, except with Hammerhead not Shamu. Hmm, in a boat with a hammerhead, doesn't sound safe.

ES Explorer:

12-08 01:39:17.413 5305 14851 W ResourceType: No package identifier when getting value for resource number 0x00000000

Cabinet:

12-08 01:40:39.161 15243 15282 E cabinet-root-commands: Attempt SU: false ls -la "/"

12-08 01:40:39.240 15294 15294 W ls : type=1400 audit(0.0:150): avc: denied { getattr } for path="/persist" dev="mmcblk0p16" ino=2 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:persist_file:s0 tclass=dir permissive=0

12-08 01:40:39.276 15243 15282 E cabinet-root-commands: Attempt SU: true ls -lad "/sbin/healthd"

12-08 01:40:39.340 15303 15303 I sush : type=1400 audit(0.0:151): avc: denied { write } for name="oom_adj" dev="proc" ino=210834 scontext=u:r:init:s0 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=file permissive=1

12-08 01:40:39.389 15243 15282 E cabinet-root-commands: Attempt SU: false ls -lad "/sys/kernel/debug"

12-08 01:40:39.420 15243 15282 E cabinet-root-commands: Attempt SU: false ls -lad "/system/etc"

12-08 01:40:39.449 15243 15282 E cabinet-root-commands: Attempt SU: false ls -lad "/storage/self/primary"

12-08 01:40:39.463 15243 15282 E cabinet-root-commands: Attempt SU: false ls -lad "/mnt/user/0/primary"

12-08 01:40:39.476 15243 15282 E cabinet-root-commands: Attempt SU: false ls -lad "/storage/emulated/0"

12-08 01:40:39.490 15243 15282 E cabinet-root-commands: Attempt SU: false ls -lad "/system/vendor"
[SuperSU] javad28:
Rooted device but not access to Ruth in s6 in 2.61

Please fix
[SuperSU] Taomyn:
[MENTION=631273]Chainfire[/MENTION] I upgraded my N6 and N9 to v2.61 through TWRP without removing the app first, and again like before both still had the old version - I had to install the new APK manually and everything is fine.

This time I got the recovery.log file and attached it here - hope it helps.
[SuperSU] Naisang:
not working for 6p angler mmb29m

I just flashed up to mmb29m, booted, flashed 2.61 from twrp, and under the supersu pro the enable uperuser is greyed out and explains that not (currently) available in system-less root mode.

What do I need to do to get root or what am I missing here ...
[SuperSU] tom1807:
My Experience:

Updated Nexus 6, encrypted to Android 6.0.1 and installed also SuperSU 2.61.

Installed first the original boot.img, then new radio and finally the system.img.

Rebooted into recovery, installed SuperSU 2.61.

Wiped cache and dalvik in TWRP, TWRP said Root is not installed before reboot, of course I ignored that message.

Android upgrading showed up, finally booted up.

The list of authenticated apps in SuperSU was empty (no issue for me), however in the Settings Tab, "Enable Superuser" was grayed out but ticked.

My apps asked Root status, got granted, however, the toast notification went rogue:

Didn't stop to tell me which apps were granted root access in a loop.

After rebooting the mobile again, all was fine.

AdAway and TiBu work. TiBu detected root, AdAway had to create a symlink to work.

Edit for pictures:
[SuperSU] j1gga84:
I installed 2.61 apk on my Galaxy S5 (G900F) running a CM12.1 ROM but updating the binaries failed. After flashing the 2.61 zip in recovery everything was fine :good:

regards
[SuperSU] Ja_som:
I also have it gray with that message, but root works...
[SuperSU] lucarp78:
Hi @chainfire as indicted in the previous post I rooted successfully (with supersu 2.61) my Samsung Galaxy Note Edge (SM-N915FY) updated with the last stock rom (android 5.1.1);

but now the reactivation lock (in security setting) won't enable, also If I reinstalled stock recovery instead of twrp.

Do you have any suggestion?

Thanks.
[SuperSU] mobileman88:
What was the symbolic link you had to create? Trying to figure this out
[SuperSU] edrickmph:
I am trying to install twrp in Android 6.0.1 in my nexus 5 but it says "twrp has detected an unmodified system partition". Anything I need to install so I can go on to root?

Any help on this one
[SuperSU] Chainfire:
Select "keep read only" option.
[SuperSU] edrickmph:
So I will just use read only option. But how can I install SuperSU? And what version do I need to install, I am not on systemless, or do I need be systemless this time?
[SuperSU] tom1807:
I haven't created anything, AdAway popped up with that message after I updated the host file.

Anyway, my system works, my post was only an information how I updated, that AdAway and TiBu are working and that you should not let TWRP install any SuperSu ;)
[SuperSU] Chainfire:
I think the test in this post should explain what you should/shouldn't do.
[SuperSU] edrickmph:
So is it safe to install 2.61? How can I install it if it is on read only in twrp?
[SuperSU] burduli:
[MENTION=631273]Chainfire[/MENTION] sir, can you tell me how can I check did SuperSU modified system or not? I want to be sure that I did everything right.
[SuperSU] H4X0R46:
Same question, how can it install if TWRP is set to read only? As for the "is it safe", it's experimental dude, so might wanna read and read and read some more, I'd be more careful with it lol
[SuperSU] Jacktheskipper:
So any experiences with Nexus 5 (hammerhead) Android 6.0.1 (hammerhead-mmb29k-factory-1943f0f5) and the new SuperSU Beta 2.61?

Can I just flash the factory image, custom recovery and flash it from recovery as usual?
[SuperSU] springer.music:
[MENTION=631273]Chainfire[/MENTION]

Nexus 6 with freshly installed 6.0.1 here - It looks like now most (any?) modifications to /system made in Recovery (TWRP) won't let the phone boot.

TWRP confirms that the operation was successful and without errors but when you reboot the phone gets stuck at the 4 dots animated logo.

I wiped/flashed Boot and System a number of times but even replacing a file like lights.shamu.so seems to prevent the system from booting.

I've just gone back to 6.0 and modifications to /system work again.

Can anyone confirm?

Thank you
[SuperSU] ashyx:
You two fellas need to do some reading up in this thread on what systemless root is.

You're asking questions that Chainfire has already fully documented and answered numerous times already.

Systemless root is exactly what it says, nothing is installed to the system partition. The read only setting in TWRP only applies to the system partition.

This is to prevent TWRP itself from altering it.

The magic is in the boot.img mods.
[SuperSU] edrickmph:
I'm sorry if I ask those questions. But this is the first time I'll be installing systemless root, I had been on SuperSU 2.60 and Android 6.0 on conventional way since yesterday with no problems on rooting, but with the recent update on 6.0.1 and 2.61, just encountered this problem today.

I just hope I can find the answers from previous posts.
[SuperSU] thaidroid:
If you want to completely uninstall system apps on 6.X you need to use this app.

https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
[SuperSU] c3k:
Battery problem still here after full charge (SuperSU 2.61 - Android 6.0.1 - Nexus 7 2013 WiFi). Tried to delete /data/system/batterystats.bin too.

I'm pretty sure I read something about this before, but can't find nothing. Any suggestion?

View attachment 3569111
[SuperSU] jackdubl:
Does systemless root allow you to still make changes to the build.prop?