yashsingh1/xdaforums huggingface dataset:
[SuperSU] bobby janow:
Same thing just happened to me. About to factory reset now.

edit: Ah details. Running an N5x stock 2.62-3 with Cataclysm overlay and custom kernel. Booted to fastboot, flashed Cataclysm overlay then 2.64 right over that. Got all kinds of FC and No Sim card detected. Went back and flashed system.img and boot.img, no help same FC. Went into twrp and did a wipe system and started over again without losing my sdcard info. Titanium restored and now I'm back where I started on 2.62-3 fully rooted but no custom kernel yet.
[SuperSU] vx2ko:
How and where do we make the changes for systemless root? Do we change it in the update binary file?
[SuperSU] shoey63:
Ok, I see what you mean. I would do it this way -

* flash 2.64 and let it patch the boot.img

* use twrp file manager to delete /su, /data/su.img and /data/app/<folder where SuperSU.apk is stored >

* Flash 2.52

Well, unlocked of course.

On MM, you can't have root without a modified boot.img, systemless or otherwise. And you can't run a modified boot.img on a locked bootloader.
[SuperSU] vt0r:
[MENTION=631273]Chainfire[/MENTION] - Saw the same force closes others have reported when reflashing the leanKernel 1.3 boot image, followed by 2.64.

Nexus 6P running stock MMB29M, previously had 2.62-3 flashed without issue over the same leanKernel 1.3 boot image - I flash the original boot image each time before updating SuperSU.

I dumped a logcat, dmesg and kmsg, but they're on my computer, so I won't be able to send until I get home. Just wanted to fill in the blanks from earlier reports in the mean time.

Sent from your mother's Nexus 6P using Tapatalk
[SuperSU] hhwong:
Anyone know how to hide/disable root temporarily only?

I am pretty hooked on a game but it will shut down if rooted (stupid, i know) =/

In previous versions, 2.52 specifically, all i needed to do is move su/daemonsu from /system/xbin to somewhere else, play the game, and paste it back when i need root again.

Can I do something similar on 6.0.1 stock rom and systemless root?

Thanks in advance.

EDIT: If it helps, the game is Puzzle and Dragons (JP Client)
[SuperSU] Ja_som:
Did you try to disable SuperSU in SuperSU settings?
[SuperSU] hhwong:
it never worked even in previous versions.
[SuperSU] bobafuzz:
I had the same issue, I thought it was the 2.64 root. Turned out to be busybox, uninstalling it from the app fixed it for me. Hope this help you guys.
[SuperSU] osm0sis:
Good find. Perhaps WiFi Calling somehow relies on the new toybox functionality (more functions than the old toolbox), and installing busybox is conflicting with those.
[SuperSU] desorockstar:
Sorry my bosses in the room ...can someone put me through about this system less statement. What does it really mean that it root the phone in system less mode
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION], it seems like the SuperSU zip still mounts system as rw at some point (I'm thinking the generic "busybox /mount system" section), and even though the SuperSU zip doesn't make any modifications this makes TWRP think system is fair game and TWRP makes modifications.

I've had success avoiding/working around this issue with my zips by explicitly mounting system ro (e.g. for build.prop checks) unless necessary. Hopefully you can do something similar, since right now the only way to get TWRP to respect the "mount ro only" setting again after this happens is to reflash system.img in fastboot.
[SuperSU] Faixa-Preta:
According to the developer of Root Checker Pro "The su binaries are not installed on a stock ROM, they must be installed by the user." If this is so how do I do this? I am running a 6P 6.01 stock rom, using 2.64 and all my apps are running fine even though his app shows I have no binaries installed.
[SuperSU] IronTechmonkey:
So... the fact that you are not working for your own boss is the reason you want others to do this work for you here where many of us do this in our free time? In any event, AFIK it is rooting without modifying the system so you can later receive OTAs but you should really check OPs and later pages in this and the SuperSU WIP threads.
[SuperSU] androcraze:
If everything is working to your satisfaction, why do you need to install root?

Rooting is for very specific purposes. You might be able to get by with just a custom boot loader (TWRP).

I'm running a custom ROM right now without root, without issue.
[SuperSU] Faixa-Preta:
I am running 10 root apps is why.
[SuperSU] androcraze:
And flashing the zip through TWRP didn't work?
[SuperSU] Faixa-Preta:
Everything works fine, I think it is a bonked app from the developer. I am currently trying to help him fix it. Thank you.
[SuperSU] ThePresence:
Hi can I flash 2.64 to Android 5.1.1?
[SuperSU] HassanM:
Simply download SuperSU 2.64 apk and install it... After the install is complete, update the SuperSU binary and reboot...

Thats all..
[SuperSU] springer.music:
This may not be related to your issue but where did you install busybox ? /system/xbin or /su/bin?

The latest update to Steriscson's installer app allows for busybox to be installed in /su/bin if you have systemless root. I had some issues with busybox in /su/bin : 1. It made completely impossible to mount /system r/w with any app, 2. Whenever I opened a terminal (emulated or through adb) I got a message like "Id: Unknown id" and then a number that I couldn't identify.

I then removed busybox from /su/bin and installed it again in /system/xbin and all seems to be back to normal now.
[SuperSU] ashyx:
Why would you need to factory reset?

All you really need to do is flash the respective modified boot image.

If your anal then remove su.img from data and uninstall supersu.
[SuperSU] purejoy:
2.64 root(System mode) on Moto X 2014- xt1095 w/ latest OTA(6.0 marshmallow 24.11.18) causes lots of FC errors.
[SuperSU] Chainfire:
I still don't get why the whole world is installing BusyBox. Unless you're doing some really heavy duty scripting/terminaling yourself, what's the point?

Read through this thread and the threads of several other root apps. Having BusyBox installed is the number one reason for root (and even some non-root) apps to stop working properly.

What are you basing this on? Why would you say the ZIP still mounts system as r/w? How have you tested this? How have you reached this conclusion?

All "Root Checker" like apps are complete bull. If root is not 100% properly installed, SuperSU will complain with a notification at boot, or whenever you open it. As far as I know, all the other root management apps do the same. These root checker apps are always lagging behind the latest developments. If you search this thread you'll find many instances of people complaining SuperSU isn't installed right because some root checker app is built for how root worked on Android 4.0.

They can be informative, but they are never leading.
[SuperSU] ashyx:
True I've never actually found a real need for it, however in the past I have had to install it because certain apps specify it must be installed or they won't work.

I can't think which apps off the top of my head right now, but I'm sure someone will chime in.
[SuperSU] egingell:
Some app devs have taken to including their own version of busybox, including Titanium Backup (which also includes sqlite) and Folder Mount, which works perfectly fine from their apps' respective /data directories without the need to actually install busybox.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] r80ies:
I never used busybox, but all my sound mods do. However, those are the only ones that require it. Maybe I should look for new mods.
[SuperSU] bobafuzz:
/su/bin
[SuperSU] bobby janow:
I haven't found a kernel app that doesn't require busybox. Certainly open to suggestions.
[SuperSU] osm0sis:
Well yes, as my post suggests, I have tested this sort of thing by flashing the factory image, noting the "only mount ro" option in TWRP sticks through reboots, then when flashing my own test zips if it mounted it rw at any point (even without any modifications) then TWRP stopped respecting "only mount ro" and made changes and the setting doesn't stick through reboots any more (until you flash the factory image again).

As I said, this is a TWRP issue mostly, but I decided it's still better to make zips only mount rw if absolutely necessary when the intention is to be systemless, and this appeared to workaround it. So, once I altered my zips to explicitly only mount ro for checks (and not mount rw at all if systemless was detected) then they didn't trigger this issue anymore.

Your zip follows the same pattern so it must be mounting rw by mistake at some point, so I reported it so hopefully you could work around this TWRP issue as well. ...I didn't expect it to hit such a nerve? What further proof would you like me to produce? I'll take a look at your latest zip and see if I can figure it out.

Edit

: There's a lot going on with your different functions and mount methods, but the way you're mounting things ro at first looks like it should work fine to me, but weirdly it's still not. My only guess is something funny with toolbox_mount?

Edit 2

: Yup, executing just your toolbox_mount function with "toolbox_mount /system ro" in recovery shell triggers the issue even though $RW gets correctly set to "ro" with $2 and /system is reported as ro afterward. I've got some time right now, I'll see if I can debug it for you. :)

Edit 3

: The problem seems to come from the remounting with the two methods within toolbox_mount due to the different equivalent $DEV points, reducing toolbox_mount to one method or the other fixes the issue. My best suggestion would be to check if the first method worked before executing the second, and only do so if the first doesn't succeed.

Edit 4

: It actually occurs if system is remounted for a second time (using a different device name) when it's already mounted ro, even if remounting again to ro. So you'd be better checking for it being mounted before running toolbox_mount at all. Brutal, TWRP, brutal. :eek:

This is all it takes to reliably reproduce the issue on my N7 2013:

mount -o ro /system;
mount -t ext4 -o ro,remount /dev/block/mmcblk0p22 /system;
mount -t ext4 -o ro,remount /dev/block/platform/msm_sdcc.1/by-name/system /system;

Anyway, obviously we'll file this one away under active TWRP issues to be aware of (again), but I guess it'd still be nice to workaround it if possible.

[MENTION=4878287]_that[/MENTION] [MENTION=1162986]Captain_Throwback[/MENTION] [MENTION=912474]Dees_Troy[/MENTION] [MENTION=631273]Chainfire[/MENTION]
[SuperSU] ouikikazz:
was this on clean install or just update with everything intact?
[SuperSU] osm0sis:
Confirmed, cleaning up busybox in /su/bin resolved issues I was having with FX File Explorer not being able to mount /system rw, and issues I was having with AdAway's webserver. I'm sure that's also the issue with WiFi Calling.

/su/bin is ahead of /system/bin in the path while /system/xbin is after, so the issue is that whatever's in /su/bin takes precedence over /system/bin. For people who still want busybox installed (toolbox+toybox still don't have awk and a few others useful applets, for example) I can see two options:

1) a "smart" install to /su/bin that only installs busybox symlinks for applets that don't have competing symlinks in /system/bin (Stericson's installer does have this as an advanced option), or,

2) [MENTION=631273]Chainfire[/MENTION] could add a /su/xbin which would go after /system/xbin at the end of the path, to function along the same lines as /system/xbin so nothing in it takes precedence over the /system/bin versions.
[SuperSU] sinisthro:
I flashed v.2.64 on my p3110 with cm12.1 unofficial and works fine :o
[SuperSU] BooBzi:
Same for me, I am on XT1572 and with stock 6.0 using 2.64 I got tons of FC's
[SuperSU] Alxoom33:
[MENTION=631273]Chainfire[/MENTION], I mean no offense, but as a relatively experienced user who flashes custom roms on a fairly regular basis (Nexus 6 running Cataclysm Rom on 6.0.1), I prefer the way root was up to 2.52/2.62 with separate System and Systemless zips. Unless there is a toggle in an installer or a simple way of selecting System or Systemless, for example in the SuperSu Pro app, I would prefer flashing separate zips. Just my 2 cents[emoji2]
[SuperSU] Danvdh:
No issues on Shamu with 2.64
[SuperSU] spartan018:
I encountered the same issues, both after the regular update and after wiping.
[SuperSU] purejoy:
It's on clean install. I reverted to stock 5.1 to accept the marshmallow OTA then flashed the 2.64 zip after the first boot.
[SuperSU] zigzampow:
No battery % issue for your? or did I miss a post about fixing that?
[SuperSU] drewski_1:
Folks have reported that the Battery % issue was from using 6.0 kernel on 6.0.1
[SuperSU] Dave08:
2.64 working great

2.64 working fine with system-less on Cataclysm 6.0.1 (Dec. 8 stable) with EX 6.07. Thanks!
[SuperSU] K-alz:
It shows "set warranty bit: kernel) on the top left of my screen every time I reboot my phone. Flashed 2.64. I have a T-Mobile galaxy note edge running stock COK2 5.1.1. It rooted my phone, but that message shows up every time I reboot. Just a feedback. :)
[SuperSU] arteaga323:
Franco Kernel doesn't
[SuperSU] tetakpatak:
[MENTION=631273]Chainfire[/MENTION] SuperSU v2.06 works very fine with Android L test version on my Nexus 7 flo.

The only root apps that aren't working are Quick Boot and Titanium Backup. Quick Boot gets granted permission for an interactive shell, but nothing happens. TB can't recognize root access (it prompts in SuperSU window and I confirmed).

Would some logs be useful? I think my BusyBox might be the problem, it isn't working.

tetakpatalked from Nexus 7 flo / Android "L" test version
[SuperSU] dhampire:
2nd Report

Hi.

I'm sorry for sending last miss-match log.

This time I did as..

adb logcat > logcat.txt

Regards.
[SuperSU] Chainfire:
Slowly but surely zoning in on the issue.

- Install attached version

- Update binaries

- Reboot

- Open SuperSU

- Create a new logcat: adb logcat > logcat.txt

- Before posting, make sure it contains a line saying "[SuperSU][APK][Installer] su --> 207"

- Post the output of (copy/paste): adb shell su --context u:r:system_app:s0 -c id
[SuperSU] dhampire:
Hi.

Q:

Post the output of (copy/paste): adb shell su --context u:r:system_app:s0 -c id

What kind of file(where) ? Please inform me.
[SuperSU] dhampire:
Hi.

I did as your order.

1) Install attached version

2) Update binaries

3) Reboot

4) Open SuperSU

5) Create a new logcat: adb logcat > logcat.txt

- Before posting, make sure it contains a line saying "[SuperSU][APK][Installer] su --> 207"

=> Sure. I checked it in logcat.txt.

Cheers.
[SuperSU] Chainfire:
Actually the output should be something like this:

C:\>adb shell su --context u:r:system_app:s0 -c id
uid=0(root) gid=0(root) context=u:r:system_app:s0

C:\>

Please try again.

Once that works, try this and see what the output is:

adb shell su --self-test

And the output of:

adb shell ls -lZ /system/xbin
[SuperSU] dhampire:
Hi.

1:

C:\>adb shell su --context u:r:system_app:s0 -c id
uid=0(root) gid=0(root) context=u:r:system_app:s0

=> see 01.jpg

2:[code]
adb shell su --self-test

=> see 02.jpg

3:[code]
adb shell ls -lZ /system/xbin

=> too big... can't catch all.
[SuperSU] Chainfire:
That is very interesting. How exactly did you initially gain root on this device? Do you flash full ZIPs through recovery? Or do you use some program like towelroot to get root?
[SuperSU] dhampire:
use vRoot (because of no other tool - inclusive towelroot / kingoroot / Framaroot etc.,- can root my device, I try a lot), and flash supersu 1.9.4, then delete vRoot.
[SuperSU] Chainfire:
Try the attached verion. Would like the logcat and output of --self-test again!
[SuperSU] r25txe:
I believe that Titanium is not yet Android L compatible.

How do you install Busybox? Try using Busybox X (Play Store) after uninstalling all traces of Busybox first.
[SuperSU] dhampire:
WoW !

Hi, Big Thanks for your strong support!

WoW ! Now no notification "need su binary update" in nortification area.

I attached Logcat3 & self test here.

Regards.
[SuperSU] dhampire:
Success !

Hi.

I got success to move SuperSU 2.0.8 to system folder by normal way without problem.

I feel that the stable means happy.

Anyway, Thank you so much for your strongest support!
[SuperSU] jurben:
[MENTION=631273]Chainfire[/MENTION] : i waited for days hoping that someone else with the same case as mine would post here, but it seems noone posted yet.

My device is msm8610 based and previously it's system is JB 4.3. I got ota update to kk 4.4.2 then I install it, but first i changed the updater-script to not delete my PhilZ-CWM. My KK runs well, but i cannot get root access for my apps. With cwm and also with towelroot or other rooting tools I can put su binary and other root 'components' (daemonsu, changing install-recovery.sh, etc) but su command takes forever to finish.

(this outputs is after 'rooted' by towelroot, but i got similar output after installing update-supersu whatever version i used):

'su -v' gave output

1.99:SUPERSU

but

'su' and 'su --context u:r:system_app:s0 -c id' and 'su --self-test'

(stuck / takes forever to finish)

if i use / install update-supersu version 2.02 or higher beta version, 'su --self-test' outputs some lines before stuck:

version_code: 202

version_name: 2.02:SUPERSU

sdk: 19

daemon_sdk: 1

multiuser_sdk: 1

multiuser_userid: 0

multiuser_username: (null)

selinux_present: 1

selinux_enforcing: 1

context[base]: (stuck here)

Some output of 'ls -lZ /system/xbin'

-rwxr-xr-x root root u:object_r:system_file:s0 daemonsu

-rwxr-xr-x root root u:object_r:system_file:s0 su

I don't know whether this info is relevant or not: These lines exist in kernel's log:

<5>[ 187.801792] (09-11 11:36:02.538477353) type=1400 audit(1410406562.527:31): avc: denied { search } for pid=6242 comm="ainfire.supersu" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir
<5>[ 187.802063] (09-11 11:36:02.538747925) type=1400 audit(1410406562.527:32): avc: denied { read } for pid=6242 comm="ainfire.supersu" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
<5>[ 187.802796] (09-11 11:36:02.539480946) type=1400 audit(1410406562.527:33): avc: denied { open } for pid=6242 comm="ainfire.supersu" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
<5>[ 187.803050] (09-11 11:36:02.539734644) type=1400 audit(1410406562.527:34): avc: denied { getattr } for pid=6242 comm="ainfire.supersu" path="/sys/fs/selinux/enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
<5>[ 193.536107] (09-11 11:36:08.272792195) type=1400 audit(1410406568.267:35): avc: denied { read } for pid=6372 comm="su" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir
[SuperSU] Chainfire:
Thank you as well for testing and getting back logs. You're probably not the only person who had this problem, but without you, it would not have been solved today.

Is there no /system/xbin/sugote and /system/xbin/sugote-mksh ?

Those avc lines do not seem to be problematic (SuperSU always generates a number of these)
[SuperSU] jurben:
Thanks for your respon.

They are there.

Some fellow thought there may be scripts or app that blocks/prevent su from getting root so the problem is not from su binary or SuperSU. What do you think?
[SuperSU] Chainfire:
I think I don't have enough information to make any assumptions about this. Plainly speaking: absolutely on idea what is going on here, and no idea how to start debugging. Can you give me more specifics about the device ?
[SuperSU] jurben:
Don't be too bothered. It's ok for me without root access. I just curious.

My device is hisense AD689G / EG668 bundled (locked) with local operator Smartfren.
[SuperSU] dacorsa:
Thanks for all !

Inviato dal mio SM-G900F X-Note 5.0 con Tapatalk
[SuperSU] Chainfire:
v2.08 beta out now :)
[SuperSU] bigwillyg:
No issues on s5 active sm-g870a
[SuperSU] rcobourn:
Yep, that works. ?
[SuperSU] MaLiXs:
No issue in my side with cyanogenmod on s5 (sm-g900w8)
[SuperSU] Srandista:
All 64-bit and Android 5.0 fixes from "Nexus 9 SuperSU" 2.18 included in this beta release?
[SuperSU] HorstiG:
Works without Problems on Galaxy S3 int,

but I found a small blemish in the Log Settings. Doubble Refresh :)
[SuperSU] Chainfire:
Yes.

D'oh. Fixed in the next update. The left one is clear logs, not refresh logs.
[SuperSU] JuggleX:
It says unknown file type.
[SuperSU] HorstiG:
I know :)

HGT - Galaxy S3- S5 - Tesla TTL7 - any KK ROM
[SuperSU] Mandrix8:
Thanks Chainfire,

2.19 works also perfect on my P7

You do the best job all the years

~ Sent from my android /Best Regards ~
[SuperSU] cstratz:
Switching SU off & reboot - now works!

Hi! ... I just have tried out v2.19 Beta with my Note 4 (N910F). ... The issue, that I have described in the v2.16 Stable thread, is gone now (*happy!)! - I have disabled the checkmark (see picture) and could reboot and afterwards re-enable the checkmark and activate SU again. Thank you very much! ... It is a very important feature for me. ... Carsten
[SuperSU] cstratz:
If you

deactivate

: ...

- com.sec.enterprise.knox.attestation

- KNOX

- Knox Notification Manager

... and ...

- Knox SetupWizardClient

... from within Titanium Backup, also SU hints to deactivate Knox should not be displayed any longer on start! (I've a Note 4, maybe you simply need to deactivate everything with 'knox' in the name on your S4!)
[SuperSU] hhairplane:
Any possibility of making a modified boot for Nexus 7 2013/deb?

---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------

Or how hard would it be to make one/convert something from flo to deb...?
[SuperSU] egingell:
I think you're in the wrong thread.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] hhairplane:
I guess so, sorry :(, was just hoping for perhaps some update or if any of the wise people in this thread had a clue on installing root for devices without necessarily a modified boot (even though I know there likely is none, since Chainfire said for the time being).
[SuperSU] JulianJenner:
2.19 BETA works on LGE-P760 CM11, thanks [MENTION=631273]Chainfire[/MENTION]!

Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
[SuperSU] TommyPG:
Fork perfect on Samsung Galaxy S3 Neo
[SuperSU] scoobyjenkins:
I have tries 2.19 beta on both my devices and both got a message asking to update the binary after updating rom. I have Pollux_windy running Unofficial CarbonRom and N9005 running Temasek's Unofficial CM11 with Lean Kernel. My Pollux_windy gave the message again after choosing to update the binary via TWRP. If I remember rightly, V2.16 doesn't ask to update binary.

Tapatalked that shiznit.
[SuperSU] mikeoswego:
Works fine on Moto X XT1060!
[SuperSU] fiffan86:
Is there something wrong with the beta downloads since last night on both my phone and laptop the download is 5kb and is a bad zip. I could download the stable zip just fine
[SuperSU] sndrdg:
Just downloaded it again - 3.5mb. Must be something else wrong.
[SuperSU] lpasq:
n5x 6.0.0 (MDB08I) SuperSU-v2.56 to 6.0.1 (MMB29K) BETA-SuperSU-v2.64

N5X report... Just went from 6.0.0 (MDB08I) bullhead-mdb08i-boot with BETA-SuperSU-v2.56 directly to 6.0.1 (MMB29K) BETA-SuperSU-v2.64, all seems to be working okay. I didn't and do not run BusyBox. My build prop was and is again modded to hide navigation bar and also allow WiDi. Root accessing apps are:

AdAway

ARUnchained Reloaded

Nova Launcher

Quick Boot

Root Explorer

Swipe Navigation

Flashing steps:

part 1

MDB08I boot.img (fastboot)

TWRP .img (fastboot)

BETA-SuperSU-v2.64 (TWRP)

part 2 MMB29K .img flash files of

bootloader

boot

radio

system

cache

vendor

part 3 flash

TWRP .img (fastboot)

BETA-SuperSU-v2.64 (TWRP)
[SuperSU] NZgeek:
The 2.64 installer has to modify the ramdisk in order to work, and the ramdisk is part of the boot image (kernel). That message is telling you that the kernel has been modified in some way and isn't 100% genuine Samsung.
[SuperSU] desorockstar:
Is version 2.52 the same with 2.56