yashsingh1/xdaforums huggingface dataset:
[SuperSU] :
It only goes up to 2.65 start reading before **** talking to other people.
[SuperSU] Aakash Kaushal:
I know that but using that kind of language is also not appreciated..:confused:
[SuperSU] force70:
Big thanks to CF for the continued updates

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[SuperSU] :
Wrong! There is a link to the changelogs of all versions!
[SuperSU] AF_624:
I have tryed on an S5 6.0.1 beta stock rom and it doesn t work.

Rigth now i m using v2.67 NOsystemless that i found on an S5 fórum.... but root is not stable.... some operations with root apps prevent the phone to enter in deepsleep.

Systemless root seens not to work on S5 6.0.1. I dont know if was you who made a NOsystemless version of 2.67 or another person.

If it was you i wonder if you made a NOsystemless version of 2.68 too, so i can test.

Thanks for your work.

Respect,

André
[SuperSU] alex00006:
Friends who do not test 2.68 ??
[SuperSU] nathanchance:
It's because Chainfire had to split it into two posts, calm down. Here is the post for 2.66 and newer, you should have seen it if you clicked into the full thread.

Well 2.68 has only been out for a few hours and we're not a tech support desk. It's common courtesy/forum rules to wait 24 hours before bumping. Additionally, you could be the one to test and come back to let everyone know if it works and if it doesn't, you can help Chainfire fix it. That's the whole point of this thread and XDA as a whole. Just make your backups and flash away.
[SuperSU] spainter:
Flashed 2.68 on my Nexus 6 and 2013 Nexus 7 Deb via TWRP. No problems with update, and everything working.

Thank you [MENTION=631273]Chainfire[/MENTION]
[SuperSU] dr.ketan:
Working fine on note5 marshmallow latest built

http://xdaforums.com/showpost.php?p=65570698&postcount=500
[SuperSU] CartmanX88:
2.68 works great on ZTE Z7 mini 6.0.1 using TWRP, thanks :)
[SuperSU] Help The Peace:
Deleted
[SuperSU] :
Working good on Galaxy s3 with CM13 (Resurrection Remix 5.6.4) Flashed with TWRP 3.0.0-0
[SuperSU] Alxoom33:
Flashed 2.68 on my Nexus 6 running Cataclysm I D over [MENTION=1228596]danv[/MENTION]h stock debloated Nova Q. No problems to report. I did notice that permissions were already changed in /su/bin to 751. Is that part of SuperSu 2.68 or a remnant from my setup of 2.67? Thanks [MENTION=631273]Chainfire[/MENTION].eu !
[SuperSU] nathanchance:
It is an added feature in 2.68 per the changelog
[SuperSU] Alxoom33:
Any...now I see it. Thanks.
[SuperSU] osm0sis:
I'm actually surprised that got added officially, since it might have flown under Google's radar if it hadn't.
[SuperSU] caltech87:
Having a problem with installing SuperSU on an M9.

-Unlocked Bootloader.

-Installed TWRP 3.0.0.0, the two new versions wouldnt allow me to access recovery mode, no problem.

-Installed SuperSU using the zip file copied to phone, it worked fine.

-Tried installing ViperOne ROM, failed because its Android 6.0 and I guess I need s-off to install the newer firmware version, etc. Ill wait for official OTA update and forget the custom ROM.

-I did a factory reset and now every time I try to install SuperSU the phone reboots just before it finishes. I dont get the success message then reboot myself.

I tried restoring the backup I made before the custom ROM installation attempt, still fails. Tried wiping caches/data.
[SuperSU] Manuel15:
Are you trying to use latest beta version with a non-marshmallow based ROM? I read latest versions require at least Android 6.*
[SuperSU] caltech87:
-Yes, 2.68 BETA. Like I said, it worked fine then I tried the custom ROM which failed, so I did a factory reset + tried my restore from before the custom ROM install.

-Just tried the 2.67 BETA , same problem.

-Tried the 2.65 STABLE, same problem.

-It gets to "placing files", then "restoring files" steps and then the phone just restarts.

-Tried using the TWRP file manage to delete the SuperSU folder and then install, no bueno.

-Im going to copy my backup to external SD and maybe try wiping everything including internal storage
[SuperSU] DJTeeJay:
I didn't see anything mentioned regarding MM for v2.68.

Is this an update for the SuperSU v2.67 build 57 Beta [Marshmallow Fixed]" version???

*edit* I am running a non-Samsung model, the Moto X Pure.
[SuperSU] force70:
That is completely inaccurate.

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[SuperSU] Marília de Oliveira:
Nice :D

~ Z3c ~ Xperia Performance Max Fury™
[SuperSU] magnamentis:
big smile nathan, all a matter of time :) (kidding of course, full respect for your usual patience)
[SuperSU] kamilmirza:
v2.68 working great on G920F 6.0.1
[SuperSU] arteaga323:
2.68 working flawlessly on stock M Feb update, Franco kernel
[SuperSU] MrTrip:
2.68 Not working on HTC One M9 Verizon Android 6.0. Neither is 2.65 or 2.67. Will not install Root. Started post over here http://xdaforums.com/showpost.php?p=65559640&postcount=637
[SuperSU] jbfountain:
Are you trying this on a completely stock MM rom, or has it been previously rooted?

Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
[SuperSU] ipdev:
SuperSU BETA 2.68

Installed fine & working great on my :

T230nu(4.4.x Custom) - T330nu(unofficial cm12.1 rr) - T530nu(unofficial BlissPop 6) - (KFHD8.9) jem (unofficial cm13 rr)

Had to force install on my NookHD9 (unofficial cm13.x.x) Used a command i found reposted twice. Works now, not systemless.

Made a soft brick out of my (KFHD7) tate running unofficial cm13.

(OK, I had to FastBoot it back to 12.1 nightly. Trying su268 from there.)
[SuperSU] kchaisu:
SuperSU beta 2.68 is working fine on Saga, CM-13 sagaopt by Mustaavalkosta. Thank you very much.
[SuperSU] alex00006:
hi

i have N920C(Note5) with Android 6.0.1

i reflash stock kernel and Root again with 2.68 and reboot phone

no Bootloop or any problem

Root successful .....

Deep sleep fix

tnx a lot chinfire very tnx

screen shot me please seen
[SuperSU] NoLimit64:
Didn"t expect problems and haven't seen any. SuperSU 2.68 working as expected on my Nexus 6P :)

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] Fiscelan:
Yep, working also well here on my Nexus 6P.

Cheers
[SuperSU] Help The Peace:
Chainfire

May I ask you how to fix the following?:

I flashed your .tar file via Odin (flawlessly) on my Galaxy S6 (SM-G920F). Everything was fine. I could reboot totally normally and everything went smooth as well. But then I wanted to backup everything (yes, that is somehow stupid, but okay...) and flashed the official TWRP via Odin. After that I could not boot anymore to any recovery (just the Download Mode) and it would bootloop.

How to fix that? :(
[SuperSU] Manuel15:
Probably your issue is not related to SuperSU, but to the recovery. Try flashing it again, or flashing another version of it
[SuperSU] Help The Peace:
I tried flashing TWRP version 2.8.7.2, 3.0 and the modified 2.8.7.2 TWRP by Chainfire. Neither of them let me boot up :/

Any other advice? Should I go even more versions back of flashable TWRP?
[SuperSU] Manuel15:
You could try another recovery, like cwm, and see if it boots (normally I would not suggest cwm, but if TWRP doesn't want to work, you can try it). If neither cwm (or an older version of twrp) boots up, maybe the only way to fix your issue is to flash back the stock firmware.
[SuperSU] Chainfire:
http://xdaforums.com/showpost.php?p=65564569&postcount=316, that one might work.

It should however be noted that this has absolutely nothing to do with SuperSU. It's your recovery that isn't working, it's your recovery that is the issue, and thus you should be taking the time of the people who make said recovery, and be asking this sort of question in the relevant TWRP thread, and not here.
[SuperSU] Chainfire:
There are still other issues with M9, but rebooting at this stage would implicate something outside of the SuperSU ZIP itself. Are you even S-OFF ?

(is that even needed? I have not really kept up with HTC since their mass consumer deception with the TyTN II)

Please, stop spreading this nonsense. 2.68 works on Android versions as old as 2.3. Where did this even come from? I see it re-posted by people all the time...
[SuperSU] ambasadii:
[MENTION=631273]Chainfire[/MENTION]

any tips to fix wifi problems and system horrible lags on my G920F with SU 2.68 less-mode + stock kernel

http://xdaforums.com/showpost.php?p=65573484&postcount=9407

regards ambasadii
[SuperSU] Chainfire:
Doesn't seem to be anything weird with those logs. Have you tried with v2.68 ?

From an adb (root) shell from TWRP, with /data mounted, you may be able to test things with

echo PERMISSIVE=true>/data/.supersu

before flashing the SuperSU ZIP. This partly disables SELinux and is handy for debugging issues like these.
[SuperSU] Chainfire:
As I read it, you're asking about an issue you're having with a stock/SuperSU'd kernel on a custom firmware. I don't give any support on that. And certainly not on wifi issues, which usually come down to a version mismatch between the drivers inside the kernel and the firmware files, and are hell to track and fix.
[SuperSU] Alxoom33:
Have you unlocked your bootloader and had TWRP or CWM working on this device? If you have a locked bootloader you may need an alternative method, such as Safestrap.
[SuperSU] caltech87:
Thanks for the reply. I flashed the stock RUU from HTCs website and was able to get SuperSU installed. Getting s-off was another story but all-in-all a success. :good:
[SuperSU] MrTrip:
I've fixed it. Pre 6.0 the bootloader could remain locked and you could flash custom ROM and get Root. 6.0+ with the new system-less mode for rooting, you need to have an unlocked bootloader. Thought I was S-OFF and installation reported a success, I could not achieve root because the bootloader could not be modified.

Unlocked bootloader, all is good now. Apologies for the confusion. This should probably be noted somewhere that HTC requires S-OFF and also UNLOCKED bootloader for 6.0+
[SuperSU] Help The Peace:
I knew you were a genius! It worked!! You are my favourite dev and I think I already donated to you. Deserved. So much deserved!!
[SuperSU] Captain_Throwback:
You're right, this definitely isn't a SuperSU issue, but I don't understand how your bootloader is locked and you're S-OFF? Don't you have to unlock to get S-OFF? Why would you relock after that? I guess I don't understand. Anyway, this is off-topic, so I'll digress.
[SuperSU] Alxoom33:
I purchased the Pro Version of Flashfire to thank you and support further Development. I have a Nexus 6 and I am running [MENTION=1228596]danvh[/MENTION] light stock Rom 6.01...Q and I am using Systemless Root SuperSu 2.68 Pro, EX Kernel with a number of Layers themes. Are there instructions/OP for using Flashfire? I want to use it for the March Google update. Thanks!
[SuperSU] Help The Peace:
Chainfire already solved my problem [emoji4]
[SuperSU] hgoldner:
Only all over the M9 forums is it "noted."

Search and read, my friend. Search and read.
[SuperSU] Chochiwpg:
My apologies since I didn't see this asked or mentioned anywhere. But is SuperSU v2.68 indeed systemless root? I am using 2.67 and I know that it is, but I don't see it listed as being systemless for 2.68 so I just wanted to confirm. Thanks.
[SuperSU] nathanchance:
Any version after 2.64 will be both system and systemless root. It prioritizes root via system and if it is unable to do so, it will take the systemless route, as I am sure you know.
[SuperSU] extenue:
Hello community,

Is someone got success with lg g4 , MM and locked bootloader ?

Thanx

XT
[SuperSU] nathanchance:
Nevermind, pay no attention to me.
[SuperSU] extenue:
Nope , i am running lg g4 LL with locked bootloader and i am fully rooted
[SuperSU] fmc000:
What? Seriously, I don't understand why people write about something they don't know. FWIW, my Kindle Fire 7' (Ford) is rooted with SuperSU even if it has a locked bootloader (and actually not by my choice, there's simply no way to unlock so far).
[SuperSU] nathanchance:
Ah I forgot about the Kindle series, my friend has one. I also forgot you can boot to TWRP without having it actually installed. I apologize for the incorrect information, I appreciate the call out.
[SuperSU] fmc000:
And I apologize for being rude, it was uncalled for.
[SuperSU] nathanchance:
All good! :) my experience is primarily with Nexus devices so unlocking the bootloader is like the first step to modification because it takes one command lol, I have much to learn about the other OEMs.
[SuperSU] scoobyjenkins:
It seems some devices behave differently to unlocking/ rooting, I made the mistake of rooting a Sony tablet without first unlocking the bootloader and it was unusable until I flashed a stock image and then the external storage was undetectable! I somehow managed to exchange it for another but could have ended up with an expensive paperweight ?

Tapatalked that shiznit.
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION], unfortunately I want to report that letest beta 2.68 is also not able to perform boot.img patching in MotoG 2014 running official marshmallow 6.0. Earlier I had reported that none of the beta or stable version is able to do this and results in bootloop except beta 2.62-3.
[SuperSU] RandomPooka:
Lg g2 and g3 are the same with the locked bootloader. When I had a moto Droid X and Bionic, both of those had locked bootloaders. All of the above were running cm7-12.1

You needed to root them first and then flash a custom recovery
[SuperSU] Alxoom33:
Yes, but you need Safestrap for those.
[SuperSU] chazall1:
letest beta 2.68 working fine no issues with systemless.

Thanks
[SuperSU] RandomPooka:
I'd all but forgotten about Safestrap! The memories!

---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------

Really digging the permission already being set to 0751 on systemless root
[SuperSU] gorilla p:
Don't forget about safestrap. Safestrap is what saved the Amazon Fire phone from a short and miserable existence.
[SuperSU] Alxoom33:
And the Bionic and the S4 for those that locked their bootloader.
[SuperSU] jwds1978:
Been using v2.68 on my Note 3 (SM-N900W8), with stock deodexed 5.0 ROM, without issue. ?
[SuperSU] _alexndr:
SuperSU v2.68 BETA, and Samsung 6.0.1 CFARs

Today's beta update to SuperSU comes with a number of bugfixes and changes, as is usually the case. The important thing this release is compatibility with the new Samsung 6.0.1 retail firmwares.

While the previous SuperSU versions worked fine out-of-the-box with Samsung's beta 6.0 firmwares, the retail firmwares had some extra 'security'.

AUDITDENY

First, they AUDITDENY'd nigh every possibly permutation of SELinux rules. In English, that means they took a pretty convoluted (and possibly performance degrading?) route of disabling policy violation logging.

While they undoubtedly had a brilliant reason for this, this is annoying for developers (both root and non-root) as seemingly random failures are often related to SELinux violations, and you no longer have a way to spot those.

As such, SuperSU now disables all AUDITDENY rules in the SELinux policy.

Permissive mode

Second, they finally killed off per-type permissive mode. While full permissive mode had been disabled on Samsung firmwares for a while already, we could (and did) switch individual types to permissive mode.

For example, the 'init' context, where commands run through 'su' are usually executed with SuperSU, was one of these permissive contexts. This significantly reduced the amount of interaction root app developers had to have with SELinux - many apps needed no changes.

As this no longer works, SuperSU now patches the SELinux policy so that virtually all common cases root apps encounter should be covered. In theory, from a root app's perspective, it should work the same. However, it is always possible I've missed something. As such, developers of root apps should take some extra care and do some extra testing on Samsung retail 6.0 firmwares. Don't forget to report issues to the relevant XDA thread.

Again, I'm sure they had a spectacular reason for doing this, even though it doesn't change anything in practise but add to the number of rules every syscall has to check against.

So if I understand above note correctly (hidden content) - at this moment in case of Samsung's 6.0.1 retail firmawes you recommend forcing "PERMISSIVE=true" variable in .supersu while rooting. Am I right?

I'm not sure if at this moment patching Samsung's sepolicy without "permissive *" policystatement is sufficient or not. I'm not asking about security but I'm asking about compromise between security and root utility/compatibility + overall system behavior
[SuperSU] j1gga84:
Everytime I dirty flash a new kernel update or ROM update SuperSU does not work anymore and is resetted to the build in version of ROM or kernel. Is there anything I can do to keep 2.68 installed?

I did not have this issue with 2.67

regards
[SuperSU] Chlorophyll:
same here

same here
[SuperSU] Chainfire:
You have absolutely not understood correctly. There is no action required on the user or ROM development side. Root app developers need to check their apps for issues. I don't expect any issues, but there might be.

The PERMISSIVE=true flag is a debugging thing only. It wasn't even mentioned in the post, so why are you even connecting the two?

If I would be recommending using this flag or "permissive *" policystatementfor Samsung 6.0.1 retail firmwares, I would've mentioned either of these things in the G+ post dedicated specifically to Samsung 6.0.1 retail firmwares you quoted.
[SuperSU] funfun99999:
With SuperSU v2.68 battery drain when the n915fy sleep is higher than SuperSU v2.67.
[SuperSU] catalyst05:
not working properly in n915f 5.1.1 stock rom. i reverted back 2.67 super su. it works like a charm
[SuperSU] Fen-X:
Hi,

I use the last beta version (v.2.68) on my oppo find 7s on omni rom 6.0.1 nightly. All is ok but one thing. Is it normal that the option in settings for intall supersu in /system is in grey color and indicate that this option is not avalaible on system with limited root ? Does this mean that my phone is not completly rooted. I have no issue with root access and root checker shows that my phone is rooted.

Can someone say me if there is a probleme with my root or if it s normal because i understand that this version of super su desn t modify the system. Maybe it s normal maybe not.

Sorry i forget to change setting languange. If needed english language tell me anf i ll post a nrw screen

Thanks for your replies
[SuperSU] Maxr1998:
I guess the translation is just a bit misleading. In German, the option is called "Not available in systemless root". So, there's that.
[SuperSU] Fen-X:
Thank you very much Maxr1998. With your good translation i understand that all is normal even the newests supersu releases are systemless versions. Thank you so much.
[SuperSU] wilsonad664:
You need to be S-Off on HTC phones to install custom ROMs. You also need to wipe cache, dalvik cache, and data in most cases.
[SuperSU] Captain_Throwback:
No, you don't. You simply have to unlock the bootloader. That isn't the same as S-OFF.
[SuperSU] sarshar:
I'm on 6.0.1 marshmallow with my Samsung Note5 N920C powered by SuperSU 2.68

this is the first time I'm experiencing stability of SuperSU after a long time since 2.46 or less.

It has been flashed very easily with no headache of multiple errors nor incompatibility

Xposed 80 x64 and SkyHigh 2.1 kernel are responding greatly.

Thanks a lot
[SuperSU] Fif_:
Symlink target wrongs in /system/xbin w/SuperSU 2.68 (and earlier)

I've been playing with OmniROM (omni-6.0.1-20160302-mako-NIGHTLY) on a mako Nexus 5 device.

I found an interesting problem.

I have busybox installed in /system/xbin, with all the regular symbolic links.

I also have pigz installed in /system/xbin and a symlink from unpigz to pigz.

If I boot without SuperSU installed the unpigz symlink is fine.

lrwxrwxrwx root root 2016-03-02 10:53 unpigz -> unpigz

If I boot with SuperSU (tried 2.65, 2.67, 2.68) installed, then this symlink is corrupted:

lrwxrwxrwx root root 2016-03-02 10:53 unpigz -> pigzbox

The unpigz link points to a non-existent pigzbox. All the other busybox links in xbin seem to be fine.

If I reboot into recovery, /system/xbin/unpigz is back to pointing at pigz.

SuperSU is to be mounting xbin with a loopback, presumably to inject the su binary as part of the systemless mode, but this loopback mount is corrupting symlinks.
[SuperSU] bournaze:
System seems more slow with 2.68 on note 4 n910f lollipop. Titanium backup can't obtain root !
[SuperSU] clevebb:
Just used titanium backup and 2.68 today. It was a clean install and mm.
[SuperSU] bournaze:
I've tried to wipe davlik and cache but Titanium Still not obtain root. Revert back to 2.67 fix the problem
[SuperSU] spainter:
I use SU 2.68 and TiB on my Nexus 6, 7, and 2013 Moto X XT-1060 Dev Edition with no problem except I have to turn of Name Space option on the Moto X. The two Nexus Devices do not require this, they run stock marshmallow and systemless root where the Moto X is running stock 5.1 with 2.68 in system root.
[SuperSU] xXCoolGuYXx:
Does this new su update work on the lg g4 h811 mm ?
[SuperSU] gorilla p:
Just to clarify, is it a Mako or Nexus5?
[SuperSU] tobitege:
[MENTION=631273]Chainfire[/MENTION]: thank you for adding fixes for the deamonsu processes, will test it right away on LG G3 Lollipop! You're awesome (old news)... :)
[SuperSU] Blac Caesar:
Flashed v2.22... Nexus 5, stock Lollipop (LRX21O), Elemental X v2.03. Running smooth, Pro recognized, no problems with other root apps. Thanks for the work, [MENTION=631273]Chainfire[/MENTION], as always :)
[SuperSU] HorstiG:
Thanks for Update, all works fine on Galaxy S3 - KK 4.4.4 Liquid Smooth - Boeffla Kernel Omi NG Beta7
[SuperSU] rafael.trad:
Working perfectly on my HTC one M8 GPE!

Thanks again! xD
[SuperSU] ciano865:
nexus 4 lollipop

installed beta 2.22 .zip with TWRP non problems

Nexus 4 NX5 rom based on AOSP LRX21T
[SuperSU] Scipizoa:
so far so good on nexus 7 stock lollipop beta 2.22 via twrp as well
[SuperSU] Megaflop666:
2.22 working great on all my device's (see signature)
[SuperSU] c3k:
Hi, I'm a root noob, I've read something about selinux and "how to su" and I'm trying to understand why the following command won't work:

root@hammerhead:/ # id -Z
id -Z
uid=0(root) gid=0(root) context=u:r:init:s0
root@hammerhead:/ # settings put global airplane_mode_on 1
settings put global airplane_mode_on 1
/system/bin/settings[5]: app_process: Permission denied
1|root@hammerhead:/ # sh -c "settings put global airplane_mode_on 1"
sh -c "settings put global airplane_mode_on 1"
sh: /system/bin/settings: /system/bin/sh: Permission denied

I'm on a nexus 5, lollipop ota, supersu 2.20-2.22 (same on a clean install on a nexus 7 2013 wifi)

if set selinux to permessive everything works
[SuperSU] Swamphound:
Type su then enter. If it says permission denied you don't have root.

sent from my Liquidsmoothed LG-VS980
[SuperSU] Chainfire:
The correct line would be:

su --context u:r:system_app:s0 -c "settings put global airplane_mode_on 1"
[SuperSU] GroteBozewolf:
Does the 2.22 still require the CF auto root? planning on doing the OTA update on my Nexus 4
[SuperSU] Murshad007:
Installed succesfully, as an apk extracted from zip..

Working fine

Sent from my LG G Flex F340K Stock KitKat 4.4.2 Rooted

using XDA Free mobile app
[SuperSU] jediratte:
2.22 working like a charm on N4 with Frankened by syko + unleashed 92 a8
[SuperSU] duki994:
Possible G2 blank screen bugs

[MENTION=631273]Chainfire[/MENTION]

It's possible that SuperSU causes bugs with LG G2.

At first I thought that kernel was problem, but after some time SOD (blank screen on wakeup) issue has been fixed in kernel. Then I changed to everything stock (ROM+Kernel) and issue persisted.

It continued happening after that. I looked at logs, and there was some strange su activity in the moment of bug happening. Now more users are reporting this, as it seems not to be kernel model

I am currently using SuperSU 2.19 BETA and will flash 2.22 BETA immediately.

Can you tell me how to pull logs specific to SuperSU, cause maybe some apps or ROM services might be causing bugs? :)

Thanks in advance :)
[SuperSU] Chainfire:
For starters, pull a full logcat of the issue happening
[SuperSU] rcobourn:
Looking good on Note 4.