yashsingh1/xdaforums huggingface dataset:
[SuperSU] Pkt_Lnt:
Having used both, I find that root is root.

You are asking if chicken is better or worse than chicken to eat.
[SuperSU] Strephon Alkhalikoi:
And moving files from the systemless location to /system/xbin is probably the worst solution given to resolve the issue. The best is to notify the app author that their app needs to be updated. The acceptable alternative is to enable compatibility mode in /data/.supersu, remove systemless root and flash again, but this will break Android Pay.

Current versions of ES File Explorer, if you want the bloat and the crud they add, actually work with systemless root. Without decompiling the app to look at the code, I suspect they simply added the systemless paths to that array they use in the app, something which Chainfire does not recommend.
[SuperSU] aakifshamsi:
ZIP is CORRUPT on Lenovo K5 Plus

I am trying to root Lenovo K5 Plus, but it keeps saying Zip is CORRUPT! Someone help?

I have copied file from Laptop.
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION], et al. :)

Just posted my solution over in my Odds and Ends thread. Should be useful with [MENTION=4419114]rovo89[/MENTION]'s Systemless Xposed on the way, and any other mod making use of any substantial amount of space in su.img. :highfive:
[SuperSU] aakifshamsi:
Created ZIP on device itself and it worked. Thanks to ES File Explorer.
[SuperSU] SultanAlush:
htc m8 gpe trying to root on marshmallow

i found out my bootloader is unlocked and S-off, maybe bc its GPE. i installed the latest TWRP. i downloaded the latest supersu zip file onto the phone. but the installation process didnt work. tried reverting back to an older version of TWRP,same result - heres a video of what happens when i click install https://goo.gl/photos/wqrFiaEXyFUqgt3b7

id very much appreciate any help, thanks
[SuperSU] kRel:
Update SuperSu: bootloop

I have OnePlus 2 with CM 13MM 6.0.1 Official with verified unlocked bootloader, in developer option I have root access active (only app) and installed SuperSU v2.76

The SuperSU operation was flawless until yesterday.

since yesterday happens that applications that need root permission, on every apps startup, ask confirmation to obtain root privileges, although they are regularly stored in SuperSU with root access.

Today, starting SuperSU to deepen on this oddity, I get the well-known message stating that SuperSU needs to be updated. Update I do as always through recovery.

The phone goes into bootloop. After an initial recovery of nandbackup, and after a subsequent attempt to update SuperSU via recovery, the OP2 goes into bootloop a second time.

However, if I go on [MENTION=631273]Chainfire[/MENTION] site, I read that the latest version is the same as the one I installed and used successfully until yesterday the 2.76 - 2016-06-30 ...

What to do ?
[SuperSU] fmc000:
Disable integrated CM root or don't install SuperSU.
[SuperSU] brossovitch:
Or enable option to respect CM root.. Which makes SuperSU do as the option in developer options says.
[SuperSU] kRel:
Hi Fabio...

So why since I CM13 6.01MM SuperSU has always worked well until yesterday? Moreover, I have tried to disable the CM root, but in this case the root does not work anymore ..

Please brossovitch, where is this option in 6.0.1 CM13 MM? Perhaps with SuperSU Pro? Wait... find-it... now i try. . .
[SuperSU] brossovitch:
As long as you have CM ROM you have the CM SuperSU version..

Here's some screenshots for you..
[SuperSU] kRel:
I found it and I popped, but keeps telling me to refresh SuperSU ...

I am afraid of another boot-loop
[SuperSU] bjbirch:
Try choosing normal instead of twrp/cwm recovery to update SuperSU

---------- Post added at 07:39 PM ---------- Previous post was at 07:36 PM ----------

Try using normal instead of cwm/twrp recovery to update SuperSU
[SuperSU] glauberlima:
Systemless: BETA-v2.74-2 = Ok; STABLE-v2.76 = Aborts

Hello everyone!

I"ve been trying to update SuperSU to the latest and gratest v.276 unfortunately without success :(

Here's what's going on:

At step "Creating ramdisk backup" right after the following lines:

Append@0004 [* sepolicy 0004_sepolicy]
Creating [.subackup/0004_sepolicy] ...

STABLE 2.76 outputs what looks like a dump of "launch_daemonsu.sh" file which halts the script execution while BETA 2.74-2 outputs the expected line.

BETA 2.74-2 output:

Append@0005 [+ sbin/launch_daemonsu.sh]
Append@0006 [+ su]
Creating [.subackup/index] ...

STABLE 2.76 output:

Append@0005 [+ # Copyright (c) 2013, The Linux Foundation. All rights reserved.
# Not a Contribution.
#
# Copyright (C) 2012 The Android Open Source Project
#
# IMPORTANT: Do not create world writable files or directories.
# This is a common source of Android security bugs.
#
import /init.environ.rc
import /init.usb.rc
import /init.${ro.hardware}.rc
import /init.${ro.zygote}.rc
import /init.trace.rc

You can find the both logs attached.

These tests have been executed on my Moto X 2014 running untouched stock ROM and TWRP 2.8.7.1.

Does someone have any clue?

Thanks!
[SuperSU] brossovitch:
Yeah, recently SuperSU makes CM13 bootloop.

Always have a good Nandroid or you can boot recovery and wipe your system partition and reflash ROM & GApps. Either way works

Best to just flash SU with each nightly update you flash. CM Downloader has an option to autoflash add-on zips with each update and even an option to clear cache or create a Nandroid.

However, it's not really necessary to use SuperSU since Superuser is built into the CM13 ROM. If I could get it installed into the system without bootloop I would but its risky. I miss using SuperSU, especially since I've paid for pro.

I also hate the system-less mode and how it makes installing busybox worthless since it installs busybox in the wrong place and doesn't work.

Edit: Installed from play store and into the system, seems to be working. Let's see of it begins glitching my system like usual and changing icons and stuff again..
[SuperSU] fmc000:
In my experience SuperSU and CM root don't get on very well together. Now I expect that with the systemless root things may only worsen. Moreover, the integrated CM superuser works just fine, so unless you have a very specific app that requires the thorough SuperSU selinux work, I'd suggest you to not flash it at all.
[SuperSU] ktmom:
I found this link doing a quick search of "moto x" in this thread: http://xdaforums.com/showthread.php?p=67470192
[SuperSU] kRel:
Thanks for all . . . .

Unfortunately it is an anomalous case and there was nothing to do. Probably they have corrupted the SuperSU binaries. It did not work even uninstalling SuperSU with subsequent re-installation.

The solution was the "deep" removal of SuperSU, so as expected from its settings. After the restart, it did not work even more SU stock CM

Afterwards I came into recovery, I flashed the latest version of SuperSu and everything is back in place ...
[SuperSU] osm0sis:
This is fairly misinformed. Root is root and $PATH is $PATH; systemless root doesn't limit write access to /system, and, if you are using a busybox installer from someone with half a brain, it'll install to /system/xbin or /su/xbin, both of which are correct and work since they're pretty much equivalent in the $PATH hierarchy.
[SuperSU] glauberlima:
Thanks [MENTION=6617276]ktmom[/MENTION]

In fact I'm already using SYSTEMLESS=true.
[SuperSU] brossovitch:
Thank you.

I had issues, sorry.

Earlier Nightly CM builds I had a lot of issues with the system-less install. Maybe its System related and not SU.

And the installer I use has the option and seems to only do one at a time. Its been okay w/o BB now anyhow. SU works better w/ the System now. . . .Thank you.
[SuperSU] belrik:
Hi, apology if I am missing something but having installation issues under CM13 with bacon (OnePlus one). "Normal" install fails despite root being enabled and twrp installation yields a device that hangs at the CM boot logo indefinitely. I've searched for workarounds but not found any. Tested on 20160724 nightly and twrp 2.7.0.5.

Using SuperSU to allow DriveDroid to work. Thanks.
[SuperSU] ktmom:
Are you aware that there is a built in root within CM13? Is that root not enough for your needs? You probably need to disabled the built in root before trying to install a SuperSu in recovery.

This has been discussed for several posts just a few posts above.
[SuperSU] kenny54:
Is there a problem with the latest update ? Supersu keeps slowing down and heating up my phone and the latest update says it fixes the memory leak issue but from the reviews it looks like people are getting their devices bricked and the binary fails to update like whats the issue? Is this new update safe?
[SuperSU] Pkt_Lnt:
No.

There is a problem with users not reading and understanding what they are doing, and then blaming something they don't understand.

Post a logcat to show how SuperSU is slowing down your phone.
[SuperSU] :
It could be a coincidence. I flashed the latest zip and few days later had lags and freezes that prevents me from unlocking the phone or opening apps. It disappeared after flashing an old version and updating via Play Store, I think it could be the zip file itself.
[SuperSU] kenny54:
What do you mean logcat? Do you want the log from within the supersu app?
[SuperSU] ktmom:
http://xdaforums.com/showthread.php?t=2274119

Understanding how to troubleshoot and pull logs is a fundamental part of modding your device.

In all likelihood, you have a poorly coded app making way too many calls to su. Read this thread, it's been discussed countless times in painful detail. This release was in beta and heavily tested before its release.
[SuperSU] Pkt_Lnt:
[Tutorial] How to Logcat
[SuperSU] seanhanrei2000:
I got a message from one of my apps.

Error: only position independent executable (pie) us supported.

Im using rooted marshmallow. How can i fix this?
[SuperSU] kenny54:
Umm. A little help here?
[SuperSU] Pkt_Lnt:
All the lines are truncated. Download the full log and place it on pastebin or such with a link here.
[SuperSU] kenny54:
this is my issue it constantly restarts itll be time were it says it restarted 170 times in 50 minutes. Please help
[SuperSU] ktmom:
SuperSu restarts each time it's called. You've got a poorly coded app that is calling supersu multiple times instead of just keeping a connection open.

Pull a log, put it on pastebin and link here. Also search this thread for previous discussions about poorly coded apps.

---------- Post added at 18:30 ---------- Previous post was at 18:22 ----------

If it isn't SuperSu that is throwing this error (I'd be surprised if it is) then you need to contact the app developer to fix it.

If you really think it SuperSu, then pull a log, put it on pastebin and link here.

Wikipedia
[SuperSU] Magissia:
It's sad that the zip goes straight into patching boot image, if the bootloader is not unlocked it will wreck things.
[SuperSU] force70:
But you would have to be a pretty dim witted individual to flash this on a device with a locked bootloader in the first place wouldn't you lol?

Sent from my Note 5 or S6
[SuperSU] :
Lurking in Reddit has told me that they do indeed exist
[SuperSU] force70:
Lol, I don't doubt it....they exist here also sadly....far too many in fact.
[SuperSU] billubakra:
Is there any safe way to replace KingUser with SuperUser without formatting the phone? And which app should we use to see if KingUser is using the internet in the background to make connections with their servers?
[SuperSU] guhvanoh:
Well, my Sony Xperia Z2 & tablet Z both have SuperSU v2.76 flashed via TWRP and their bootloader are locked. Or am I on the wrong track heading for.....
[SuperSU] mikhaelkh:
When I go to "settings", both "refresh" and "clear logs" buttons dissapear.
[SuperSU] Mkhant30:
It is off topic here. You can try SuperSu Me Application.
[SuperSU] shoey63:
Guys, SuperSU zip only works on standard Android boot images. Stock Sony uses kernel.elf. Totally incompatible. Equally incompatible is the ramdisk.cpio and ramdisk-recovery.cpio packed into the boot.img method.

Get your devs to use this workaround https://github.com/jackfagner/twrp-sony-recovery-boot-script/blob/master/README.md
[SuperSU] Cj7Andy:
Help with ? binary? Issue.

First thanks for the time and effort [MENTION=631273]Chainfire[/MENTION] . This is my first root on a Samsung. I have an S6 edge +. Sm G928P. I used Odin and was able to PASS the root. When I open SU it works and three root checker apps say it's rooted but I cannot get any root apps to work. Most say their is a missing binary. I have tried to uninstall the root and do it again but it will not uninstall the root. I do not know where to go from here.

Thanks in advance for any help.
[SuperSU] Pkt_Lnt:
post #1 has a link to the binary update support thread
[SuperSU] lucadalba:
Hello to all.

Since I've modded my Samsung Galaxy S5 SM-G900F with Android 6.0.1 Marshmallow, I never had problems to flash SuperSU SystemLess.

But when I've updated my firmware to G900FXXU1CPG1 with 1 July 2016 SECURITY PATCH (obviously I lost root beacuse I've flashed firmware via Odin) and I try to flash SuperSU 2.76 (zip tried to flash in SystemLess mode..) it FAIL WHEN IT TRY TO PATCH SEPOLICY (error is also noticed in recovery.log.. more info here: http://xdaforums.com/showthread.php?p=67909012)

You can get more info in this post and in the one linked before: http://xdaforums.com/showthread.php?p=67904553

The error is most

probably caused by the new Security Patch 1 July 2016

Has anyone this problem (SuperSU failure) with this security patch?

You can check security patch on Settings>About Phone>Security Patch Level

Thanks in advance

Sent from my SM-G900F with DeoXPer Pure MM ROM
[SuperSU] shaggyskunk:
I'm running an AOSP CM Based 6.01 Rom with the July 5th Security Patch and no issues with 2.76 - So fwiw I don't think that it's the Security Patch...?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] lucadalba:
I think there is a difference between Samsung Security Patch and AOSP ones.. so I mean only TouchWiz firmwares..

Anyway thanks for reply

Sent from my SM-G900F with DeoXPer Pure MM ROM
[SuperSU] ktmom:
I think you're right. In that case, don't you think that the operative issue isn't SuperSu but rather firmware and should be asked in a device forum?
[SuperSU] lucadalba:
Yes but I have also seen that is a Samsung SEPolicy problem that sometimes (more than one time) affect our devices making impossible rom installation.

So I wrotten that post to know if other people have same problem as mine.. yes maybe I'm partially OT but anyway that post was SuperSU related.. obviously not a "bug" because changing in SEPolicy are made by Samsung, but anyway I just want to notice it (done in update failure thread with more info and precise error) and maybe know if someone other has this problem..

Notice the problem only in a device thread wouldn't be very useful (IN MY OPINION) for SuperSU development.

Anyway I don't want to stay here to complain problem and I already searched the problem in recovery log and wrotten the error.. and I'm also available to provide other logs and test eventual fixes (if I haven't problems)..

Obviously I don't expect Chainfire or other devs provide a solution in 1 second.. we do modding for free and we do it in free time.. But obviously I hope for a solution.

Thanks

Sent from my SM-G900F with DeoXPer Pure MM ROM
[SuperSU] Joeisgood99:
Thanks for the reply.

SU works perfectly with stock sony kernel.elf., and ramdisk.cpio packed in with ramdisk-recovery.cpio, (otherwise I wouldn't be able to root my stock z5c and use TWRP) For example AndroPlus kernel has exactly this set up and achieves root with Chainfire SU system-less install. The script in your link is just one of the many ways to get sonys kernel to boot in to TWRP, it doesn't root the kernel.

Omni kernel boots in to TWRP fine. Reading Chainfires install script he has taken that sort of kernel set up in to consideration. As the log states the main issue is that in omnirom version of ramdisk there is a slightly different layout to the ramdisk which throws the checks at the start of the install as it thinks there are some parts missing when in reality they are one folder in. I have attempted to change the install script my self but had no luck.

I understand Chainfire cant make different META-INF folder for every variation of every custom Rom on every phone which is why I wanted to fix it my self. Just seeking guidance from the guy who knows the script best.... or anyone that cares to look in to it.

By the way. RESPECT! for including Australia s greatest beer in your avatar.
[SuperSU] holygoatofsteel:
My phone has been stuck in an "Android is starting" and then the Aerom logo bootloop for about 20 minutes now, any ideas?
[SuperSU] netreign:
restarting phone...
[SuperSU] Magissia:
They exist and I'm repairing their phones that doesn't boot because of this, thankfully it's not complicated to flash boot image back
[SuperSU] Iceberger:
I've flashed the zip from recovery
[SuperSU] Logan:
Hello guys i am cm13 in i9300 s3 international supersu 2.76 used to work perfectly i updated the nightly and in rooting using supersu 2.76 according to twrp log it uses system mode not systemless which causes bootloop anything i can grab that help to fix it? Thanks
[SuperSU] ldeveraux:
You probably need to disable the cm superuser, reboot, then flash supersu. Don't quote me on the steps, but there should be a guide posted.
[SuperSU] ktmom:
What the previous posted said, plus there is a method to "force systemless". Search the beta thread if you need more specifics.

That said, using a custom ROM you shouldn't need to worry about protecting the system partition.
[SuperSU] allnex:
I installer TWRP 3.0.2-1 and tried to flash SuperSU 2.76. The problem is that the process fails and I get this error:

- Creating ramdisk backup
-- Failure, aborting

I tried to flash the stock system, recovery and boot images but the problem persists.

Thanks.
[SuperSU] ktmom:
You provide to little information. What device? What ROM? And just saying stock isn't enough. You need to be specific. Take the entire log and upload it to pastebin then *link* to the pastebin here.
[SuperSU] USBhost:
is this normal

is this normal :confused:

rootfs on / type rootfs (ro,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,noatime,nodiratime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,noatime,nodiratime,mode=600)
proc on /proc type proc (rw,noatime,nodiratime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,noatime,nodiratime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,noatime,nodiratime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,noatime,nodiratime,mode=755)
none on /acct type cgroup (rw,noatime,nodiratime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,noatime,nodiratime,mode=755,gid=1000)
none on /config type configfs (rw,noatime,nodiratime)
none on /dev/memcg type cgroup (rw,noatime,nodiratime,memory)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,cpu)
pstore on /sys/fs/pstore type pstore (rw,seclabel,noatime,nodiratime)
adb on /dev/usb-ffs/adb type functionfs (rw,noatime,nodiratime)
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (ro,seclabel,noatime,nodiratime,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/VNR on /vendor type ext4 (ro,seclabel,noatime,nodiratime,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data type f2fs (rw,seclabel,noatime,nodiratime,background_gc=on,user_xattr,acl,inline_data,extent_cache,active_logs=6)
tmpfs on /storage type tmpfs (rw,seclabel,noatime,nodiratime,mode=755,gid=1000)
/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,nodiratime,data=ordered)
[B][COLOR="Red"]/dev/block/loop0 on /system/xbin/busybox type ext4 (rw,seclabel,noatime,nodiratime,data=ordered)[/COLOR][/B]
/dev/block/platform/sdhci-tegra.3/by-name/CAC on /cache type ext4 (rw,seclabel,noatime,nodiratime,data=ordered)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other)

this happens when i flash supersu on android n and when busybox is installed in system/xbin (ps it was a clean install)(dont remember if this happens on mm)

and when i used fuser to find what pid it was every pid that belonged to supersu.

if an app tries to use busybox then they just freeze.

to fix i just do "umount /system/xbin/busybox" and everything is working again.

but this is getting very annoying to do on every reboot.
[SuperSU] osm0sis:
That should work as long as it's linked to an existing /su busybox; I guess your busybox installer wanted to ensure it was being used over the ROM's, (but, that's pretty pointless when /su/xbin already is dominant over /system/xbin).
[SuperSU] USBhost:
the thing is i pushed busybox to /system/xbin

i had nothing to do with /su

also why would it mount busybox as ext4?

P.S. i build my own busybox. i dont like using others.
[SuperSU] osm0sis:
It is bind mounted so just inherits whatever it's parent is set to for mount options and type (in this case /su). No idea what the deal was that set that up. It's weird.
[SuperSU] USBhost:
vary... maybe the big man himself has an idea :fingers-crossed:
[SuperSU] ZRK_NanDRD:
(S3 i9300 Running 6.0.1 Resurrection Remix M v5.7.1)

For many hours I flashed SU-2.76.zip in different methods but,non seem to work, it all led to bootloops.

Then I decided to flash back SU-2.62.zip rebooted, thereafter I flashed Xposed rebooted & used the phone for the rest of the day without flashing back Boeffla kernel.

-SELinux » Permissive

-Developer Opt- Root Access » Apps & ADB

-Busybox already installed

After a day of device usage without Boeffla on the device I then flashed SU-2.76.zip through Flashify app (My Recovery: TWRP 3.0.2.1) & it booted without any bootloops.

Keep in mind that I never switched off Root Access on Developer Options (Root Access » Apps+ADB)
[SuperSU] Hydrogen_:
good :D
[SuperSU] cuchuflytado:
SUPERSU

would like to kwow if it work for xperia ST23a !
[SuperSU] mozilla008:
Problem here. Everytime I update SU Binaries, after reboot Ghost Push Trojan is always detected by Stubborn Trojan Killer (STK). I think STK removes the updated SU binaries and revert the old one because if I reboot, SuperSU is asking for SU Binaries update again. Is it normal? Please help. Thanks.
[SuperSU] egingell:
That's STK's problem not SuperSU's.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] mozilla008:
Okay. I think I just need to uninstall STK then. Thank you.
[SuperSU] Cr0ssL1nk:
In your original post, you said: !!! SuperSU requires a rooted device !!!

But, some people says you only need to flash SuperSU to root your phone and it really works:

- http://xdaforums.com/showpost.php?p=67978015&postcount=8

- http://xdaforums.com/showpost.php?p=67975552&postcount=18

This makes your warning statement a bit strange. Are they really rooted even though their root checker says yes ?

So, does it means SuperSU can root every phones that exists if you have a recovery or does the warning statement means something else ? :confused:
[SuperSU] fmc000:
The SuperSU apk requires a rooted device to work. If you flash the zip from the recovery you get both the su binary and the SuperSU apk.
[SuperSU] Cr0ssL1nk:
That's much more clearer, thanks.

So happy to know that SuperSU.zip is a universal phone rooter as long as you have a custom recovery ! :victory:

By the way, does it also works for Intel Atom based phones or do they need a specific x86 su binary version ?
[SuperSU] MichaelSaya:
It will work with any custom recovery. It will not flash with stock recoveries.
[SuperSU] Cr0ssL1nk:
Indeed :good:

Does the su binaries are 100% the same for Intel Atom based phones ?