yashsingh1/xdaforums huggingface dataset:
[SuperSU] KingOfDope:
SuperSu 2.22 works great no issues so far.
[SuperSU] zadigre:
installed and tested on my Galaxy Note 3 running the CM11 M12 Snapshot... everything looks good!
[SuperSU] Bhaskara Rao:
V2.22 working fine on Galaxy Tab 2 p3100 with CM11-Snapshot-M12 and Next Kernel 2.4
[SuperSU] asdfasdfvful:
Download link in the op for the newest zip isn't working for me. Anyone?
[SuperSU] Fif_:
Whoops, way to confuse everyone...

I experienced the issue on a mako Nexus 4 device.
[SuperSU] Snowby123:
Even the smallest typo can create great confusion.
[SuperSU] cdiaz92:
2.68 works for note 5 sm920t thank you
[SuperSU] babydown:
My device is Note 5 (on MM stock firmware 6.0.1). After flashed BETA SuperSU 2.68, SuperSU said "There is no SU binary installed, and SuperSU cannot install it. This is a problem!......"

How can I fix it !!!
[SuperSU] starbucks2010:
I read somewhere that disabling mount namespace separation in su options is solving the issues with TB and su 2.68. Worth checking.
[SuperSU] Alxoom33:
Re.flash SuperSu 2.68 zip. Make sure you enter the correct ADB commands to make it Systemless before flashing.

Website signature
[SuperSU] Dr0idgroove:
Installed SuperSU Beta 2.68 on Nexus 5 running 6.0.1 MMB29Q. Installed via TWRP 3.0.0 in systemless mode.

The issues I had with 2.67 persist. Once you disable Superuser in SuperSU's settings, once you open SuperSU again you will get a notification that the binary needs to be updated and the installation will fail. Trying to enable Superuser in settings again will fail as well. The only way to get root access again is to re-flash SuperSU via TWRP recovery.
[SuperSU] Wyneg:
Before this installation of supersu, did you install other previous version (Not systemless version)?

If yes, you have to reflash android and then install supersu in recovery.

If no... I don't know...

Good luck
[SuperSU] xdamami:
Guys We need buy a SuperSu pro to support our best xda developer!!!

Imagine xda without Chainfire.

Sorry for bd Eng.
[SuperSU] Wyneg:
I want to buy it, but I can pay in google play, I have only paypal T_T
[SuperSU] Jhall8:
Bought long ago
[SuperSU] osm0sis:
Google Play supports PayPal for awhile now. ;)
[SuperSU] Wyneg:
TELL ME HOW...!!!!

Please ;)
[SuperSU] bournaze:
You are right. It fix my problem.

Thanks a lot !
[SuperSU] shaggyskunk:
Just get it from the Store

It's not complicated ?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] clevebb:
Imagine phones in general without Chainfire!
[SuperSU] Wyneg:
Hi!

But how can I pay with paypal in google play???

Thanks!
[SuperSU] RandomPooka:
Play store > Settings > My account > Add payment type > PayPal
[SuperSU] Wyneg:
Thank, master ;)

Update: Nope, maybe in my country isn't available (I'm from Chile)

[IMG="No paypal T_T"]https://lh4.googleusercontent.com/-Hdu0bRM9zbA/VtnMjRDtSBI/AAAAAAAAAzE/LwIXsjmojwI/w1028-h548-no/Sin%2Bt%25C3%25ADtulo.png[/IMG]
[SuperSU] RandomPooka:
Yeah, it's definitely based on country. Sorry to hear that you aren't able to use it
[SuperSU] fmc000:
Bought it in late 2013.
[SuperSU] skyhirules:
Same thing happens on my Xperia Z1 Compact, with Android 5.1.1. I flashed it with TWRP 2.8.7.
[SuperSU] syntesys:
Good evening. I have problems with super su 2.65 and Titanium Backup 7.3.0.1: error backupping, non space left; when I reverted supersu from 2.65 to 2.46, titanium backup restarted to work normal. Now, how can I resolve it???
[SuperSU] LoverBoy2415:
Yeah..After Updating to v2.65 ..turn off the Mount namespace separation option Which is Already marked default in Supersu & Reboot once after its done ..Voilà now You Have Titaniuim backup..back on track ;) ...
[SuperSU] mbze430:
tried using cm-13.0-20160305-NIGHTLY-v410.zip on LG Gpad 7.0 LTE (v410). Then tried to flash the OP SuperSU. getting Error: Certification Verify

Using SuperSU from playstore.... getting bootloop (tried both method of install)
[SuperSU] cloves:
HTC M9 Marshamallow USE OLDER VERSION OF superSU 2.65

BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip.

HTC M9 (t-mobile)

Unlocked

TWRP version - twrp-3.0.0-2-hima

After installing "BETA-SuperSU-v2.68-20160228150503.zip" via TWRP my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.

What can I do now? I have a full nandroid backup. What could the problem be?

***** FIXES ******

Installed BETA-SuperSU-v2.65-20151226141550.zip from TWRP.
[SuperSU] Snowby123:
Did you make a logcat to diagnose your bootloops?
[SuperSU] cloves:
Hi Snowny123,

Installed BETA-SuperSU-v2.65-20151226141550.zip aka 2.65 via TWRP and rebooted and all is working now.
[SuperSU] mielletseed:
Good for you but maybe this problem could / should be fixed?!
[SuperSU] cloves:
Posted inside the superSU thread. Also saw a few other people also having issues the the M9. Not sure what else to do.
[SuperSU] supercowz:
hello everyone, i really need help ...

i try to root my X98 plus dualboot tablet (x86)

there is no TWRP advable for this tablet

so i modified the boot.img to insecure mode

and create a batch file to install superSU 2.67

supersu working great, root checked say all fine, but i have the binary need to be updated bug, and of course allway fail to update

i try with superSu 2.45 and 2.49 same problem

im not a pro and ist the fisrt device i root from scratch,

if anyone can point me where is my mistake lead to binanry cant be updated,would be great

here is my batch file with su 2.49 :

adb wait-for-device

adb devices

adb remount

adb shell mkdir /data/superuser

adb push SUfiles/Superuser.apk /data/superuser

adb shell cp /data/superuser/Superuser.apk /system/app/Superuser.apk

adb shell chown root.root /system/app/Superuser.apk

adb shell chmod 0644 /system/app/Superuser.apk

adb shell mkdir /system/bin/.ext

adb shell chown root.root /system/bin/.ext

adb shell chmod 777 /system/bin/.ext

adb push SUfiles/su /system/bin/.ext/.su

adb shell chown root.root /system/bin/.ext/.su

adb shell chmod 6755 /system/bin/.ext/.su

adb push SUfiles/su /system/xbin

adb shell chown root.root /system/xbin/su

adb shell chmod 6755 /system/xbin/su

adb push SUfiles/su /system/bin

adb shell chown root.root /system/bin/su

adb shell chmod 4755 /system/bin/su

adb push SUfiles/su /system/xbin/daemonsu

adb shell chown root.root /system/xbin/daemonsu

adb shell chmod 4755 /system/xbin/daemonsu

adb push SUfiles/supolicy /system/xbin

adb shell chmod 755 /system/xbin/supolicy

adb push SUfiles/libsupol.so /system/lib

adb shell chmod 644 /system/lib/libsupol.so

adb push SUfiles/99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon

adb shell chmod 744 /system/etc/init.d/99SuperSUDaemon

adb shell chown root.root /system/etc/init.d/99SuperSUDaemon

adb push SUfiles/busybox /data/superuser

adb shell chmod 0755 /data/superuser/busybox

adb shell cp /data/superuser/busybox /system/xbin/

adb shell chown root.root /system/xbin/busybox

adb shell /data/superuser/busybox touch /system/etc/.installed_su_daemon

adb shell chown root.root /system/etc/.installed_su_daemon

adb shell chmod 644 /system/etc/.installed_su_daemon

adb push SUfiles/install-recovery.sh /system/etc/install-recovery.sh

adb shell chown root.root /system/etc/install-recovery.sh

adb shell chmod 755 /system/etc/install-recovery.sh

adb shell rm /system/bin/install-recovery.sh

adb shell ln -s /system/etc/install-recovery.sh /system/bin/install-recovery.sh

adb shell /system/xbin/busybox --install -s /system/xbin

adb shell rm -rf /data/superuser

adb shell su --daemon

adb shell su --install

adb reboot
[SuperSU] wirelesskebab:
Hi there, I was hoping someone could tell me if it's possible to get systemless root on a samsung galaxy tab s2 8.0" (wifi) SM-T710 on 5.1.1? I installed TWRP then installed from TWRP with the zip only not accepting prompt for automated install... I went to change a setting after booting into android and the device restarted and SuperSU app was removed.

The only way I know is to use a permissive kernel but that breaks DRM and the work arounds are not that great.

Thanks for your assistance.
[SuperSU] NPOA556:
Just go to Chainfire's website and click the Donate button in the upper right. Paypal is accepted. I fully agree that he should be thanked by people purchasing his apps and donating a little money once in a while.

https://www.chainfire.eu/
[SuperSU] CVAngelo:
Or purchase the PRO version of the SuperSu app in the Google Play Store. The additional features are excellent!
[SuperSU] clevebb:
the full post you quoted has the reason why your solution is no good.
[SuperSU] CVAngelo:
Yup...I didn't realize I was offering a solution for a problem.
[SuperSU] egingell:
If you'd have been paying attention rather than just read the last post, you'd have known that your "solution" had already been suggested, but the user is unable to buy stuff from the Play Store because of regional restrictions.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] tet-bundy:
Not sure whether to post this here or in the stable thread..

It would be lovely to have an option to hide root from apps i.e. online banking etc. Would be much mor comfortable than using other apps for this purpose. Just hoping u think about it. Not demanding anything, as i suppose there are more urgent issues atm.

Regards

[MENTION=4182290]cainf[/MENTION]ire you are the man!

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] Falinor:
Having issues - I have a N6, and my previous setup was SuperSU Beta 2.67 - deleted su/xbind directory and chmod 751's the su/bin folder. AP worked flawlessly (6.01 from January)

Today I flashed 6.0.1 (March) + used SuperSU Beta 2.68 (auto chmod 751's su/bin). Deleted su/xbind and I used SafetyNet. Passed and green checked all 3. Go to re-add my cards, and I get "Request Failed please verify your card information and try again" even though the information I entered is correct?

When I iniitially setup TWRP, I allowed system modifications. Was that the issue? I then reflashed and chose not to allow system modifications. Same issue.. please help :(
[SuperSU] CVAngelo:
I am not an infant, bro. It was already pointed out to me and I acknowledged my error. I did not realize that I was responding to a problem. I was simply saying that in general people can support Chainfire buy purchasing their pro version.

---------- Post added at 02:03 PM ---------- Previous post was at 01:50 PM ----------

You can control the default action for root access and toast notifications in Settings. Plus you can control root access and toast notifications separately for each app by selecting the app in the App tab and changing the setting from there. This combination of features may provide the ends you seek...no other apps are necessary. Or did you mean something else by "hide root". And my apologies...this thread may not be the appropriate place to have this exchange.
[SuperSU] bobby janow:
[MENTION=6033224]Wyneg[/MENTION] I just bought it for you. $3.99 EU about $4.57 USD. Perhaps I can PM [MENTION=631273]Chainfire[/MENTION] to send you a copy via PM. If not then at least you have contributed. Now if we can drop this silliness and get on with the task at hand. It's been said that if I flash the J version of the March Google image then I can sideload the SuperSU either via adb or Stickmount Pro with my OTG. Has anyone tried this? Can I get systemless root on the new stock image the same way?
[SuperSU] corkiejp:
Chainfire has stated that he has no plans to support methods for online banking etc with SuperSU.

Did you reflash system as well and not just TWRP? If you didn't your system would have been modified by your first flash of TWRP. There is another thread for Android Pay and SafetyNet.
[SuperSU] Falinor:
No I didnt reflash system. Darnit, ok. I just need to reflash system and that is it, right?
[SuperSU] Wyneg:
WHAT?!

Now I'm on debt with you, thanks again ;)

I'll donate to you when recibe my paid ;)

Update: i'm using version 2.68 now, with PRO will be "2.68 PRO"?
[SuperSU] bobby janow:
No debt at all. :) Was time I re-upped anyway. When you install Pro, if you get it, it will only say SuperSU Pro 2.68 in the settings menu and give you other options.
[SuperSU] Wyneg:
Aaaah, you don't have donate button, neither paypal mail info...

I can't accept that!!!! xD
[SuperSU] Alxoom33:
That's an Android Pay issue, not tied to root. Just need to rescan your card and perhaps call your bank.
[SuperSU] Falinor:
Thank you! I just had to rescan my cards. Didnt have to reflash system either! /phew

All good to go now :)
[SuperSU] tet-bundy:
Oh i'm sorry. Now that u mention i remember having read about this..

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] ifwillems:
Good idea! Will do the same!
[SuperSU] greeneyez15o:
2.67 worked great,2.68 cant delete apps using TBackup
[SuperSU] Alxoom33:
Use Root Explorer.
[SuperSU] Juls317:
So I'm on SuperSU v2.65 right now, which i believe is still system-side root. I'd like to move over to systemless, since that seems to be the way root will be supported in the future. However, I'm a little confused as to whether or not systemless root can be used alongside a custom ROM, since I'd have to flash back to the stock /system partition in order to install the systemless root package. I'm sure this is a stupid question and I'm just overthinking it, but I figured I should ask.
[SuperSU] egingell:
Systemless only applies to stock ROMs. The only purpose for systemless is to get OTAs. Custom ROMs don't do OTAs.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Juls317:
Oh, that makes sense then. I don't know why that wouldn't click in my brain.
[SuperSU] Alxoom33:
Not necessarily correct. Systemless is to keep su out of the System Partition, there are other reasons for doing so, such as allowing AP to work with a rooted phone, as an example.
[SuperSU] mielletseed:
You are really wrong and chainfire often enough explained that getting OTA is just a side effect of systemless root. There are many other reasons, just read his posts carefully ....
[SuperSU] CallmeReaz:
I'm on samsung galaxy s3 mini and using OMNI rom. But the 2.68 beta version of SuperSU, not working. Any suggestion?

On TWRP, it saying, Successful and reboot. But when i reboot. nothing happen.
[SuperSU] egingell:
Be that as it may, it's still written for the stock boot image. I can't imagine Chainfire wanting to write in checks and mods for the many, many third-party boot images available.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] fmc000:
Systemless root works perfectly with almost every boot image of almost every ROM on almost every device. BTW, I'm running 2.67 systemless on a custom ROM on my one plus one. Please educate yourself before spreading FUD.
[SuperSU] Manuel15:
I agree. Using systemless on my S2 plus with a custom ROM.
[SuperSU] mielletseed:
There is no such thing like THE STOCK BOOT IMAGE. It differs from device to device ans from version to version.
[SuperSU] egingell:
Drr. Because I totally meant that there was one and only one boot image.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] fmc000:
OK, he's just a troll. Let's not feed him.
[SuperSU] magnamentis:
search for "root cloak" while things can change, at least until recently it was a way to do what you're asking for
[SuperSU] Nino1238:
Manuel, also i s2 plus AOSP GHSR 6.01 2.67 SU, can you confirm please the procedure used for systemless ?

Have you go back to stock firmware or flashed some boot img ?

I am confused about this.

Thks n rgds
[SuperSU] RandomPooka:
Know of any way off hand to do this without Xposed? I'm just learning how useful Tasker and Automate can be, so I'm wondering if there's a way to spoof file permissions via one of those apps so that App X doesn't get to see the /su folder at all by either changing the perceived permissions for the folder or by making the OS think it's not actually a user or in a group with permission to view a specific directory or file. Might even be possible to run the app as a different/restricted user using sudo or su -c
[SuperSU] skyhirules:
So, please in a nutshell, what's the point of a systemless root? Is just a noob question, but could I have an answer please? Because it seems to me that it's better to have a system root.
[SuperSU] a1exus:
Why do you think system root is better?
[SuperSU] mielletseed:
Chainfire explained it broadly. To achieve root in marshmallow it is almost always necessary to patch the boot image (SELinux policies to allow root operations). When it's necessary to patch boot why also patch /system additionally and not just boot?
[SuperSU] Longlast:
hello everyone

my supersu stop working because clean master delete all permissions i tried to install the latest beta supersu 2.68 but it still the same

i have g-900t with 4.4.2 twrp.

any help would be appreciated.
[SuperSU] Chahk:
Anyone brave enough to try 2.68 on N Preview yet?
[SuperSU] Smultie:
First question: does a custom recovery work on Android N?
[SuperSU] mikereidis:
What, an hour after it came out by surprise ? I'm still downloading.

Don't expect Chainfire to drop whatever he's doing today to immediately test/work on it. For previous Android releases he usually seems to take at least 1-2 days before saying much or dropping a new version.
[SuperSU] mikereidis:
Good question as a pre-requisite, but perhaps better suited to the recovery threads for supported Nexus devices.
[SuperSU] shawnten:
recovery boots up for my on nexus 6p
[SuperSU] Smultie:
Cool, can you try SuperSU?
[SuperSU] Chahk:
It does. Why wouldn't it?

Oh, I'm not expecting Chainfire to release anything until the kernel sources are out. I'm just wondering if I will be the first. :)
[SuperSU] blackbird5308:
SELinux patching failure.
[SuperSU] bouchigo:
I already tried it both system root and systemless. Neither works...system root doesn't even boot to OS.

file_contexts is now a bin file (file_contexts.bin), not a text file anymore in boot.img. It will require some looking into by chainfire to get N rooted.
[SuperSU] Zlatty:
I keep getting asked for a password. Weird.... :crying:
[SuperSU] Koragg618:
Maybe it's because of the encrypted kernel?
[SuperSU] bouchigo:
Yeah, that is why it's asking for the password.

Even not being encrypted, root won't work. We just have to give chainfire a chance to look at what can be done, or can't be done. The N release just came out.

You can see I'm not encrypted, and current root methods aren't working:
[SuperSU] deusfaux:
probably something I did - but on hammerhead-MMB29V (Nexus 5 March security) SuperSU 2.68 would fail multiple times when attempting to install via TWRP; it would never complete/succeed, but then a single attempt of 2.67's .zip worked like always. I've done this dozens of times so I'm not sure what is up
[SuperSU] Zlatty:
Ugh. N should be rooted already. He literally had minutes to get the next version of Super Su working for it!!!! ;)

I'm sure that in the next few weeks both TWRP and Super Su are going to be Nified. Until then, let's enjoy these ads everywhere.
[SuperSU] vladashram:
mod edit: content removed
[SuperSU] bouchigo:
mod edit: content removed
[SuperSU] gorilla p:
In the meantime, try Adguard. Best non-root ad blocker I have found so far.
[SuperSU] Ingenium13:
Just an FYI, the new M update for the 6P (MHC19I) and 5X breaks TWRP from accessing data. Can't mount it. Can't even dd it to a flash drive (it tries, but results in a 0 byte file).

I was still able to adb sideload SuperSU 2.68 and it worked, presumably because everything was already on /data and it just needed to patch the boot image. It almost certainly wouldn't work on a clean install. Doubt it was able to make a backup of the original boot image though.

So either the bootloader is blocking recovery from accessing the data partition, or TWRP is maybe loading a selinux policy from the system image that is blocking it. People reported downgrading just the system image allows TWRP to work again. The bootloader and radio are identical to the ones in the N preview that came out today.

Sent from my Nexus 6P
[SuperSU] Pig Vomit:
FYI: As previously reported, stock MHC19I roots just fine using CF-Auto-Root. No need for TWRP if all you are doing with it is rooting.
[SuperSU] ohad129:
Can you explain for noobs how doing it thx in advance
[SuperSU] georgegermanos:
I'm getting the following error when trying to install via Philz CWM Recovery:

Boot image: /dev/block/sda5

Extracting ramdisk

Decompressing ramdisk

Failure, aborting

Any ideas how to fix this? I'm running Extreme Debloated Rom 5.1.1 with Arter97 v11 kernal on an Note 5 n920i. I can't seem to get root anymore and installing the apk from the zip verifies root is no longer present.

Thanks in advance if anyone is able to help :)
[SuperSU] ohad129:
Just let me know how you do it with cf root my device is N6 and the built there is for 6.0.1 so??
[SuperSU] Zlatty:
Thanks on the suggestion. I'll check it out. It must be pretty good as it's not in the Play Store. LOL

https://adguard.com/en/adguard-android/install.html#howToInstall
[SuperSU] force70:
[/COLOR]

There are 2 different updated twrp files out now which fixes this on the 6P anyway.

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[SuperSU] mikereidis:
mod edit: content removed
[SuperSU] ohad129:
Sorry im noob i didnt understand the solution can you drop a guide please
[SuperSU] bouchigo:
While I respect your opinion, I still disagree with you.

It would have been much simpler, and appropriate to simply start a new thread with this information. Simply stating: "Here's a root method that allows root on Android N while we wait for chainfire to come up with a solution, or comments on whether he will even attempt anything", or something along those lines.

That's probably the last comment I'll bring up about the subject as it's leading to off topic chatter/attention that I don't want to impose upon this thread.
[SuperSU] qtipbailey:
Where do you find the updated TWRP files?
[SuperSU] lioryte:
I'm gonna go on a limb and say... twrp site ?
[SuperSU] Ingenium13:
Nope, they aren't there. Still the original 3.0.0 release.

Sent from my Nexus 6P
[SuperSU] Smultie:
It was posted on the TWRP Google+ site
[SuperSU] qtipbailey:
I only see the same 3.0.0-0 versions which aren't able to decrypt data after installing the March update (at least on the 5X). I thought he was referring to some test or beta builds. There's a test build for the 5X mentioned here: http://xdaforums.com/showpost.php?p=65761289&postcount=173 but I don't know from who or where it came.
[SuperSU] Smultie:
Like I just said: TWRP Google+ site: https://plus.google.com/+JoshuaLynch50036/posts/ZcNqBDvNmo7
[SuperSU] Chainfire:
So, I just returned from a ski trip an hour ago... I haven't been able to try N yet, will do so now.

Interesting all three of you appear to be using the Note4. This is on my list to try and reproduce.

Please provide logs of a booted system you have tried Titanium Backup on (and not rebooted since), using the syslog app: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=en

Output of the "mount" command from both a normal adb shell and a su shell would also be helpful, as well as the output of "ps", "set" and "getprop" commands from a normal adb shell. If you don't understand any of that, just skip this step.

See above, please provide the same logs and command outputs.

Put this on my list. Not a bad idea. I do fsck in recovery, but not every boot.

I have still not replicated this exact issue, but this issue is on my radar and that part of SuperSU is on my list to re-code.

Disable the "mount namespace separation" option in SuperSU settings.

Then don't thread jack. The SuperSU forum is about SuperSU.

I wouldn't normally disagree, however people involved with that project have given me too much ****, including accusations of code stealing and whatnot. Their mention to me or in my threads is forever banned.
[SuperSU] Manuel15:
I just downloaded the SuperSU 2.68 zip file and flashed it through recovery. If you are systemless already, no need to go back to stock firmware or flashing any boot.img

If you're using system root, just use the SuperSU "full unroot" option, and then flash the zip file