yashsingh1/xdaforums huggingface dataset:
[SuperSU] bombadier:
Same story on my nexus 7,SuperSu 2.20 is working and my device is rooted just not with Titanium Backup I guess we will have to wait for an update to titanium

Updated to the test version of titanium and at least it gets root,file operations not working due to lollipop changes to the folders (apps are now installed in folders)

Dont think I need the pie patch as I am not running a preview build,stock image.
[SuperSU] Megaflop666:
You need to get the latest tibu from Twitter, not the play store. If you are still having problems with tibu there's a PIE - PATCH out there you should try flashing. I'll see if I can go find the thread.

See post #446 for PIE patch thread link.
[SuperSU] mixtapes08:
Download the beta app here. Check out [MENTION=243871]Titanium[/MENTION]Backup's Tweet: https://twitter.com/TitaniumBackup/status/532645824883593216?s=09

Sent from my Nexus 5
[SuperSU] bombadier:
Dont use twitter which is why I didn't know that there was a test version available will try that

WIll start to watch twitter on the run up to the new version of android
[SuperSU] Megaflop666:
Neither do I. I read about it when the lollipop build started coming out with the dev previews.

Bypassing the new PIE security check
[SuperSU] mixtapes08:
I have the pie security patch and a kernel that supports root on 5.0. Titanium works just fine on my official android lollipop update. I'm using the stable version of SuperSU.

Sent from my Nexus 5
[SuperSU] xgoo:
A similar problem also occurs with ES File Explorer (3.2.2) when enabling root explorer and granting permission, it gives an error message: "Sorry test failed. This feature cannot run on your device."

Used CF-Auto-root on a stock Nexus 5 Lollipop.
[SuperSU] Megaflop666:
Again, try the pie patch. My es file explorer root explorer works perfectly.
[SuperSU] FletchF:
Anyone having trouble with SuperSU Pro on Lollipop? I rooted my N10 with the latest CFAR and root works fine. But, when I install SuperSU Pro, it's doesn't enable the Pro features.
[SuperSU] FletchF:
Nevermind. I re-ran CFAR and the Pro features are now enabled. (Actually, I'm not sure if it was the re-root or just the reboot that fixed it.)
[SuperSU] satanb:
i just flashed a custom recovery and then flashed super su 2.16 and i got root access

---------- Post added at 08:36 AM ---------- Previous post was at 08:17 AM ----------

nope sorry, i didnt get root access:(
[SuperSU] Pkt_Lnt:
Lollipop? Posted by the OP, he knows a thing or two about this.

http://xdaforums.com/showpost.php?p=56702285&postcount=436
[SuperSU] starbase64:
no problem, but doesn't work :( titanium says no root
[SuperSU] yanner2012:
Titanium needs to be updated for Lollipop . You need use Titanium test r6, it works fine.
[SuperSU] starbase64:
Link? pls
[SuperSU] yanner2012:
http://t.co/PhE5wkvHkA
[SuperSU] onesolo:
Where the hell is SuperSu 2.20 ?? I only see 2.16 and beta 2.19...
[SuperSU] bombadier:
SuperSu 2.20 is bundled with CF-Autoroot and is only for android l,no need for a flashable zip

Tapatyping fae the Nexus 4
[SuperSU] thereassaad:
But deepsleep already fixed on latest supersu its there on su/su.d/ .
[SuperSU] skulldreamz:
If anyone has spoke ill about [MENTION=631273]Chainfire[/MENTION] you will feel the wrath of his super sung fu and be warned he is a 2.66 degree black belt!
[SuperSU] alex00006:
How?

Please explain this
[SuperSU] thereassaad:
Chainfire add the deepsleep fixed on his latest supersu v2.66 so its already fixed ..
[SuperSU] alex00006:
can i use TWRP after root with su 2.66 and deep sleep fix????

Or

after root with su.266 i must flash again

recovery stock???
[SuperSU] thereassaad:
I already used them on my s6 mm 6.0.1 & already deepsleep fixed by Chainfire with his supersu v2.66 & also with his twrp modded .. so no problem u can used them at the same time mate ..
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] now that SuperSU is relatively stable I updated my nexus devices to M, and successfully rooted with 2.66. Now, I found the xbin_bind link but here's the kicker. How can I delete that without mounting as R/w, because from what I read even mounting as rw is enough to block OTA's on systemless.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] osm0sis:
It's in /su, which you can mess with as much as you want instead of /system. So just delete /su/xbin_bind and don't worry about mounting /su rw. :good:
[SuperSU] Ch3vr0n:
The thing is, neither of my file managers will let me. Cyanogen file even with root access I can't see beyond internal storage and https://play.google.com/store/apps/details?id=com.speedsoftware.explorer says it can't because the system is read only. See image.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] Chainfire:
v2.67 released in the WIP thread. For the list of changes, see the changelog.

I strongly recommend flashing the ZIP rather than doing an APK upgrade if you are on a Samsung device or are currently experiencing any issues.

It has finally come to the point where the changelogs have exceeded the post size limit and I had to split them up into two posts. Shees.
[SuperSU] thereassaad:
Sir i just flash v2.67 over v2.66 on s6 tw mm 6.0.1 but the supersu app not showed on app drawer?? I tried to extracted then install it as a normal but its there already there & its won't install over it ...
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] Pretty sure this has been reported before but wanted to confirm this for (atleast my N5) that the logs are blank when clicking on a log entry. My settings are to store the complete contents, not just the access. Using SuperSU 2.67beta
[SuperSU] Chainfire:
Try uninstalling it manually through Settings->Apps, or "adb uninstall eu.chainfire.supersu", reboot afterwards (even if it failed), then try installing the APK again.
[SuperSU] osm0sis:
Yeah, sometimes you have to mount /su rw. I didn't mean "don't worry about it" like "you don't have to" I literally meant "don't worry about it, just go ahead and do it," since it has no effect on /system. :)
[SuperSU] thereassaad:
Done after i uninstall the app through adb then reboot then install it as a normal & now its installed & working thanks sir .
[SuperSU] carlitobahsoun:
hi....what is mean adb assad???

N920c/64g/stock rom/rooted v2.66/skyhigh kernel v3.7/stocky mode v1.4/xtreem music mode v7.0.3/xposed :greenify+amplify+power nap+wanam
[SuperSU] Ch3vr0n:
Not very experienced with terminal commands. Since I don't want to drag this off topic, could you pm the set of commands I need to do that? Thanks.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] thereassaad:
Connect ur phone to pc then run adb shell & type this

adb uninstall eu.chainfire.supersu

Or from setting/application if u didn't found supersu app then u will find this ok

eu.chainfire.supersu

For me i did it through adb shell bro ..
[SuperSU] osm0sis:
No terminal required since any root explorer apps should allow you to remount within it.. If yours somehow does not, try FX File Explorer. If you're hellbent on your old explorer the terminal command is simply: mount -o rw,remount /su :good:
[SuperSU] Ch3vr0n:
Fx worked thanks, and left /system as ro. Confirmed that through that other app that stated the status on top. Thanks

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] carlitobahsoun:
ok i deleted from setting/app/ flash from recovery and everything ok...why they are deleting xbin???

N920c/64g/stock rom/rooted v2.66/skyhigh kernel v3.7/stocky mode v1.4/xtreem music mode v7.0.3/xposed :greenify+amplify+power nap+wanam
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

Do you have any idea why, when bundling the SuperSU zip as part of a ROM install as you detail here, that the recovery log contents get deleted? When flashing the zip standalone, the log is fine.
[SuperSU] carlitobahsoun:
i unistall from app and fladh v2.67 from recovery and all ok...assad why they are try deleting that file xbin.bind

N920c/64g/stock rom/rooted v2.66/skyhigh kernel v3.7/stocky mode v1.4/xtreem music mode v7.0.3/xposed :greenify+amplify+power nap+wanam
[SuperSU] thereassaad:
Xbin its already here not deleted bro please re flash it again ok but 1st uninstall the supersu app then reflash it ok
[SuperSU] carlitobahsoun:
yes that what i did and everything ok...thanks dear

N920c/64g/stock rom/rooted v2.67/skyhigh kernel v3.7/stocky mode v1.4/xtreem music mode v7.0.3/xposed :greenify+amplify+power nap+wanam
[SuperSU] milojoseph:
can you share this twrp mod plz
[SuperSU] thereassaad:
Twrp for s6 tw mm 6.0.1 its by chainfire modded one

Here is link

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

For rebooting to recovery i used this app

https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot

i just use it booted to recovery as old methods by keys not working so that's why i used 3rd party app & its did the job..

& all the credits wents to Chainfire & bigbiff so the thanks went to them ...
[SuperSU] Chainfire:
@ everyone

What is up with the big ass screenshots recently. Please do not.

I have no idea.
[SuperSU] Ch3vr0n:
For the record, I only install the zip log is empty just the same.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Captain_Throwback:
Just talked with [MENTION=912474]Dees_Troy[/MENTION] in #twrp, and changing this line in the updater-script:

run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");

to this:

run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", [B]"0"[/B], "/tmp/supersu/supersu.zip");

prevents the log from being deleted.

There's quite a bit of discussion going on about it now. The reason it works? "Because Linux" was the response I was told to provide :). Also Dees_Troy said you could hit him up on Hangouts if you wanted to discuss further.

So at least we have a way to display all of the logging now.
[SuperSU] _that:
Background: this is the fd that is supposed to be connected to the recovery's command pipe. However when calling it from an updater-script it is not possible to use the correct fd number (that was passed by recovery to the update-binary). 0 is stdin (where writes will probably end up nowhere) and 1 is stdout, and stdout is connected to /tmp/recovery.log. I guess that the shell redirection with ">" in ui_print() truncates the log and that using ">>" should prevent the issue.
[SuperSU] Captain_Throwback:
I can confirm that changing ">" to ">>" in the ui_print function fixes the log truncation. That might be the best way to go.

EDIT: [MENTION=4544860]osm0sis[/MENTION] I think any of your shell scripts, if using similar functions, will have the same issue. I believe I brought it up in your thread before. I'm glad that there's finally an explanation for it.
[SuperSU] osm0sis:
My scripts don't self-reference like that so should be okay? I've checked the logs after my zips as recently as yesterday for debugging purposes and they seemed to go all the way back to boot.
[SuperSU] YHG:
Configuration : multirom

Rom 1 stock and601 su 2.66

Rom2 cataclysm 601 v0501 EX6.10 su 2.66

Rom 3 chroma v 1801 su 2.66

Install 2 .67 on each rom

Update normal choice binary su failed on each rom

Try update su67.zip on chroma : failed with recovery

I come back to su2.66
[SuperSU] Captain_Throwback:
The issue only occurs when the zip is called from the updater-script of a ROM install. Is that how you've been checking yours?
[SuperSU] osm0sis:
I flash my zip then I cat /tmp/recovery.log; I'm not following you here, maybe you can explain it to me over in my Odds thread?
[SuperSU] backslashV:
echo systemless=true>>/data/.supersu command doesn't help, I still need to delete /su/xbin_bind/ to get android pay to work. anyone else having the same issue? TWRP>Terminal>system folder>press the select button that's where I enter the command.
[SuperSU] Ch3vr0n:
Please use the topic chainfire created a few posts back, Android pay posts belong there no longer here

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Captain_Throwback:
That's not the command to prevent xbin_bind from being created. Re-read the post with the download links.
[SuperSU] nathanchance:
echo BINDSYSTEMXBIN=false>>/data/.supersu is the command to get rid of /su/xbin_bind, in addition to the other one for systemless. All Android Pay discussion should go to this thread by the way.
[SuperSU] backslashV:
thank you. two questions:

1. do I have to run the command you mentioned before flashing supersu?

2. what is the point of running the systemless command then?
[SuperSU] nathanchance:
1. Yes.

2. You need the systemless command to force systemless root. The two commands are not mutually exclusive, you need both of them for AP
[SuperSU] Chainfire:
Attached version should fix all this.

Rather than nixing the output, it now detect being rerouted to logs, prevents truncating the logs, and even tries to figure out the right fd to write output to, so the script output actually ends up on-screen.

Note that you break all that if you change the number from 1 to 0 :)

Will of course be part of v2.68 whenever I release that.
[SuperSU] Captain_Throwback:
Nice! Just tried it, and this works well. The SuperSU output now appears in the console even when the zip is embedded as part of a rom zip installer. Thanks, Chainfire!
[SuperSU] doomscooter:
Where the last beta?
[SuperSU] Ch3vr0n:
The wip thread, the search will point you to it.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] edrickmph:
After an update to SuperSU 2.67, 500 firepaper live wallpaper already crashes!*

Any solution to this one?

I have uninstalled the app and reinstalled it, but same thing happens.
[SuperSU] boomop:
When I try to flash v2.67 over v2.66 TWRP (2.8.6.0) exits and restarts immediately (OPO Sultanxda CM 13 Rom)

After reboot into system v2.66 is left untouched.
[SuperSU] Manuel15:
Installed 2.67 yesterday. No issues :)

Just deleted the SuperSU app before flashing.
[SuperSU] jib@rmi.ge:
Trying to flash 2.67 on CM13 (for u8833 by chil360 with opengapps 6.0, twrp 2.8.5.0), it just does not show up, the builtin superuser persists.
[SuperSU] rogers11:
It works for me on N4 and N5. Installed together with the latest Nightlies with Cyandelta.
[SuperSU] edrickmph:
Weird it is working now without doing anything[emoji2] .
[SuperSU] XkunX:
V2.67 fixed deep sleep issue on my Note 5 N9208.

Also, just noticed that the Private Mode works with V2.67 without Xposed.

Thanks! [MENTION=631273]Chainfire[/MENTION]
[SuperSU] Gandalforce:
Flashing 2.67 on HTC One M9 causes bootloop. Dang....
[SuperSU] botteur:
boot loop too with LG G3 @ CM13 :(
[SuperSU] Blac Caesar:
[MENTION=631273]Chainfire[/MENTION] v2.67 running perfectly on OnePlus One. NucleaRomReborn (CM 13 base)
[SuperSU] Gandalforce:
I'm gonna factory reset, then re-root. Restore app data after.
[SuperSU] MaFiBoSS:
v2.67 what's new (changelog)?

Thanks :)
[SuperSU] Swamphound:
Follow the instructions in this thread http://xdaforums.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105/page7
[SuperSU] :
Saved it but it doesn't tell me what these things are.
[SuperSU] Swamphound:
Sorry I couldn't be more help. I'm just a simpleton thankfully enjoying the work of others and I just followed the instructions in the thread I linked and get a pass in the safetynet app and have Pay working.
[SuperSU] :
It's a good thread thanks for posting it.
[SuperSU] shoey63:
Yep. changelog is what's new.
[SuperSU] egingell:
Normally, I would totally agree with this smartass post; however, dude is looking for the change log for 2.67 which is *not* in that post.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] corkiejp:
The changelog got to big to be posted in one box.

See here: - http://xdaforums.com/showpost.php?p=64916199&postcount=3
[SuperSU] Chainfire:
Did 2.66 work?

G3 kernels need to be 'bumped'
[SuperSU] MaFiBoSS:
21.01.2016 - v2.67 - BETA

Thanks :)
[SuperSU] Gandalforce:
2.66 did not work as well, only 2.65..
[SuperSU] GinomC:
Running 2.67 on clean 5x

but disk encrypt is broken..

Any fix for this?

adb logcat says

cryptfs us unable to dismount /data because its busy
[SuperSU] backslashV:
Why is safetynet so inconsistent lately? Test passes only half of the time. I'm on 2.67 systemless

(Also tried 2.61 with same results)
[SuperSU] Captain_Throwback:
Wrong thread.
[SuperSU] backslashV:
Has to do with supersu. What is the right thread?
[SuperSU] Pkt_Lnt:
See this.

http://xdaforums.com/showpost.php?p=64913001&postcount=4589
[SuperSU] th3:
$0|&#!! I have my [HTC One M8] ROM running all stock LL, flashed OTA MM, now flashed TWRP. All working well. Then I needed root and the message came up to flash in TWRP and I accepted.

Frah it's stuck in boot ever since, with mm-camera-img.img errors... before I could take a backup :/

Any way to resolve this?

Many thanks!
[SuperSU] holeindalip:
Flash the unsu.zip through recovery and try that
[SuperSU] aiyeumiforever:
I have HTC One M8 M8_UL (S-ON; Relocked; HBOOT 3.19.0.0000; HTC_Asia_WWE) which has just upgraded OTA to Android 6.0 - 6.14.707.1 with stock recovery and not unlock Bootloader yet. Im looking for the way to root the phone. Does anyone know exactly which solution i should choose: Traditional or Systemless one? (http://xdaforums.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210)

And which SuperSU version to root this phone?

Just want some confirmations casue i don't want to mess it up. Thank you so much !
[SuperSU] Chainfire:
On 2.65, can you get me all the system logs? https://play.google.com/store/apps/details?id=com.tortel.syslog

Additionally, please get me the output from the following commands inside a 'su' shell:

ps -Z
id

A link to whatever firmware you are running would also be very helpful.
[SuperSU] zman01:
How can I dump the boot.img for modifying without root access?

edit: Got it :P
[SuperSU] DroidForLife33:
I accidentally swiped to install superuser at the end of TWRP. Is there a was to revert back. Thanks moto x pure
[SuperSU] Maxr1998:
Reflash system, reflash SuperSu.

It could be enough to only reflash SuperSu.
[SuperSU] Manuel15:
Flash the unSU zip and flash SuperSU again

http://xdaforums.com/showpost.php?p=63615067
[SuperSU] MaFiBoSS:
I testing the v2.67 and seems to be OK :D

Only a question, is normal the small number of apps when I wipe the DALVIK CACHE, after the first boot, only: "Optimizing App 1 of 22". Normally is 202 +/-.

Thanks
[SuperSU] TR2N:
No need to wipe any caches. Wiping cache is a myth from the stone age...
[SuperSU] Manuel15:
Sometimes it happens to me too, probably it will optimize the other apps the next boot
[SuperSU] GinomC:
Oh, sorry forgot to say this is stock 5x with 6.0.1

any tips?

anyone got disk encrypt working?

Also my Tmobile Wifi is not working either (as far as I can tell)
[SuperSU] smokeythebear3:
I have the HTC One M9 also. I tried 2.67 and 2.66, both caused bootloops. 2.62 and 2.65 worked for me without this issue.
[SuperSU] Alxoom33:
2.67 working just fine on Nexus 6 Systemless.
[SuperSU] Gandalforce:
Okay, I'll get that to you via message soon
[SuperSU] TacoKing0218:
I'm on shamu, trying to do a flash into /system, but the installer is choosing to go systemless. Is there any way to force an install into /system?

Xposed isn't flashing if I have systemless. If I can't force an install into /system, is there anything else I can do to make the xposed framework install?
[SuperSU] nathanchance:
Are you on stock Android? System root isn't possible without a custom boot.img as far as I am aware on 6.0.1. If it can't install into system, it chooses systemless, you can't force system root. You may ask over in the Xposed forum to see if they can help you.
[SuperSU] TacoKing0218:
Yes I'm on stock. Apparently xposed doesn't like roms (not sure about this, don't want to try). Thanks for your suggestion :)
[SuperSU] killall:
You need to make room in /system folder to install xPosed. Just delete some of the language packs or google apps you don't use.
[SuperSU] TacoKing0218:
Ah yes, I forgot about all of the talk about the system partition being taken up by too many apps.

It worked like a charm :) thank you so much!
[SuperSU] fmc000:
A question: does current SuperSU 2.67 (installed in systemless mode) survive ROM updates or does it have to be reflashed every time? I upgraded from 2.52 without first wiping /system (my bad) and now I have in /system/addon.d the survival script but I suspect it came from the previous installation.

I searched this thread for "addon.d" and for "backup script" but didn't come with anything useful.

Thanks in advance.
[SuperSU] Ch3vr0n:
You didn't flash /system : you didn't follow instructions, anything wrong is your own doing.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] fmc000:
Which part of "my bad" you did not understand in my post? I know perfectly that I missed a step, I'm just asking something else. And, BTW, flashing /system makes no sense, you probably meant "format /system".

Anyone else with some more constructive input for me, please?
[SuperSU] Ch3vr0n:
Makes perfect sense, no I didn't mean /format. Directly reflashing why system erases the 'old' one. That's how it works on my nexuses anyway. And it should survive rom updates because as the name implies it's not installed in /system which is the part that gets updated. Systemless gets installed to /su/xbin and its the boot image that gets modified. So you might have to reflash the existing boot before doing an update or if the update fails

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] fmc000:
I ended up with formatting /system and reflashing ROM, gapps and SuperSU. A couple of minutes of effort but now I feel "safer".
[SuperSU] GROGG88:
If the update includes a boot.img you will need to reflash su.
[SuperSU] Alxoom33:
No, you should reflashed SU.
[SuperSU] fmc000:
Thank you both.
[SuperSU] ExceterM:
System RW problem with systemless 2.64+

This is probably a n00b question that will incur the wrath of a thousand "use the search box, n00b" responses, but after going through at least 50 responses, I'm all out of options.

I have tried flashing 2.62-2.67 and finally decided to say screw it and went back to 2.52 because I can't get the system to remount rw. I use the build.prop tethering workaround to use my wifi hotspot, but even after using the adb shell in recovery to use the "echo FSTABSYSTEMRW=true>>/data/.supersu" command, I still can't get system to remount rw so I can modify the build.prop. I even tried going into su adb shell to run the "setenforce 0" and remount using the "mount -o rw,remount /system" command, and the "mount -o rw,remount -t ext4 /system" command, and the "su -c mount -o rw,remount /system, and none of it allowed me to remount system as rw. Even with busybox installed and the SuperSU running, neither ES File Browser (root access active) or Root Browser allowed me to change the permissions. What am I doing wrong and/or missing and/or any solutions?

Thanks in advance.
[SuperSU] Captain_Throwback:
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post64208563#post64208563

Please use search . . .
[SuperSU] ExceterM:
woop there it is!!!

But this covers the problem. Not a solution. Is there a workaround with the Moto N6 running on systemless 2.64+ on 6.0.1 to allow /system rw or am I SOL for now and should just stick to 2.52?
[SuperSU] Chainfire:
Are you sure you tried with 2.67 ?

I just tried this on a freshly flashed N6 MMB29S (6.0.1 + January patches) and "mount -o rw,remount /system" from a "su" shell works fine for me.
[SuperSU] abescalamis:
Hi, the root 2.67 works perfectly on a note 5, I just wanted to report that the only issue that found is when I do a full unroot and select to restore the stock boot image, it restores the stock recovery but the phone gets on a boot loop, I still had access to download mode I re-flash twrp, and flash supersu 2.67 and the phone worked again, It also worked when I only re-flashed the TWRP custom recovery, I still haven't figured it out how to fully unroot.

(I think that by doing a factory reset from the stock recovery could fix it too, but I'm not sure I don't want to do it at this time, because I would have to re-do my phone all over again)