yashsingh1/xdaforums huggingface dataset:
[SuperSU] Wake89:
Since I haven't put much on my tablet yet (N7 2013) I think I'll do the cleanest route to fix it.

Reflash stock from Google.

Flash twrp multi rom 287

Flash supersu 2.60 zip

My only question is, which version supersu apk to install when I'm done?

I'm going to stay on 6.0 due to the difficulty some are having with 6.0.1.
[SuperSU] springer.music:
[MENTION=631273]Chainfire[/MENTION]

Although going back to 6.0 allows for /system to be modified (again), I now get "Unfortunately process com.android.phone has stopped" and the SIM card is not detected.

I initially thought that this was caused by the new 6.0.1 radio being incompatible with 6.0, so I flashed the 6.0 radio again and then wiped cache/dalvik with no success.
[SuperSU] fasthair:
N7 Battery Reporting

Glad I found your post before I tried to flash this to solve this problem. My N7 2013 has the same issue with the battery reporting. I started a thread in the N7 2013 forum about it.

I haven't read to far back in this thread to see if other devices are having this issue or if it is just us N7 users.

fasthair
[SuperSU] c3k:
[MENTION=4289856]street_dog[/MENTION] had the same problem, not sure device type, seems a mobile in his screenshot
[SuperSU] Chainfire:
How exactly did you enable this percentage display?
[SuperSU] c3k:
100% stock, it changes after 6.0.1 + 2.60 update
[SuperSU] Chainfire:
I'm not sure which part of that explains how you enabled the percentage display :)
[SuperSU] c3k:
Percentage is shown on stock ROMs when the notification is pulled down the second time... I didn't enabled nothing

EDIT: percentage in status icon activated with system ui tuner (http://www.androidpolice.com/2015/1...heres-a-new-way-to-activate-or-deactivate-it/)
[SuperSU] Chainfire:
Well, I did not know this. You live and learn :)

Either way, with a cleanly flashed 6.0.1 /system and /boot on my Nexus 7 2013 Wi-Fi (flo), then installed SuperSU v2.61, this battery issue does not occur.
[SuperSU] Chainfire:
On a freshly flashed 6.0.1 /system on Nexus 6, there are 0 bytes free on /system. Likely any modifications you think you are making just result in deleted/corrupted files, and this is why it won't boot.
[SuperSU] springer.music:
Do you mean that there's even less space than on 6.0?

Titanium Backup reports that there 15.6 MB free. Shouldn't this be enough for a very small mod such as an edit to build. prop?
[SuperSU] Ja_som:
[MENTION=2024094]c3k[/MENTION] and [MENTION=2992105]fasthair[/MENTION]

I also have Nexus 7 (2013) Wi-Fi (flo), stock Android 6.0.1 and SuperSU 2.61 and I don't have the battery percentage issue...
[SuperSU] FletchF:
OK, thanks. Sorry for the misinformation.
[SuperSU] Rapper_skull:
Are you sure you flashed the stock boot.img? It happens on Nexus 5 too with custom kernels and/or [MENTION=631273]Chainfire[/MENTION]'s modified boot image. Flashing stock system.img and boot.img, then installing SuperSU 2.61 fixes it.
[SuperSU] Golf c:
Do you mean that there's even less space than on 6.0?

Titanium Backup reports that there 15.6 MB free. Shouldn't this be enough for a very small mod such as an edit to build. prop?

The 6.01 stock image I flashed was over 1000 MB.
[SuperSU] springer.music:
And... you were very right! Thank you [MENTION=631273]Chainfire[/MENTION]!

I deleted some system apps (Newsstand, News & Weather and Books) and I was then able to modify /system.

PSA: Since TiBu doesn't seem to be able to delete system apps on 6.0.1 yet, I used SD Maid and it worked like a charm.
[SuperSU] Chainfire:
@ everyone

This post is likely an important one going forward, it could be the answer to various issues people have on 6.0 related to /system.

The conversation below pertains specifically to Nexus 6 @ 6.0.1, which has an almost full /system, but I'll bet the issue exists on all Nexus devices.

So after some further investigation, something pretty odd is going on.

ext4 (the filesystem) has various types of reserved blocks.

I suspect the tools on booted Android do not count one type of reserved block. Indeed, when you use "df" utility (both toolbox and toybox), it shows 15mb or so free. Using the same "df" utility in recovery (busybox) shows 0b free. It does show that not all blocks are in use, but the remainder is likely reserved.

If you use a root shell on either booted Android or in recovery, trying to write contents to a new file in /system will fail. To make matters worse, file creation succeeds, but writing content does not, so you end up with a 0 byte file. You need to delete a few extra megabytes of files, before you are able to write even 1 byte to a new file!

Many editing tools remove the old file and write a new file at the same spot rather than truly editing a file. I'm not sure if the latter has any chance of succeeding, but the former would definitely fail in this scenario.

While the issue is understandable technically, it is likely to trip up a lot of tools, as the error is generated at the least expected moment.

This issue is a magnet for file corruption and bootloops. Beware this issue when modifying anything on /system!

DEVS Immediate hunch is that the difference is explained by usage of struct statfs's bfree vs bavail member.

TL;DR Yes, even though TiBu and whatever other tool are showing you megabytes free, adding/modifying files is likely to give unexpected results on a (near-)full /system partition, and an unlucky edit can definitely prevent the device from booting! Can't give you exact numbers right now, but before modifying files or adding files to /system, I would recommend deleting files until you have at least 30-ish mb free.
[SuperSU] Ja_som:
http://xdaforums.com/showthread.php?p=64201941
[SuperSU] jcsww:
The almost full system also causes issues with AdAway, when trying to add to the hosts file. The simplest way to solve this is by using Titanium BackUp after rooting to remove useless system apps, like Google+, Docs, and all of the other stock bloatware that is installed by default.
[SuperSU] thaidroid:
System app Remover works great where RomToolbox and TB fails on Android 6.X

https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en

Posted the link earlier but worth repeating
[SuperSU] GPS3:
I don't know what how or why, but doing this fixed my battery percentage error.

I'm assuming it was the SuperSU 2.52 and shamu-mra58k-boot.zip (/system install) combo that didn't like 6.0.1.

SuperSU v2.61 seems to have fixed it.

For my information, have I done a system-less root by using 2.61?

Thank you.
[SuperSU] mukintaras:
About this percentage bug -- on Nexus 5 systemless root doesn't seem to have a bug, but "ordinary" root with modified kernel does. Problem is that systemless root doesn't work with V4A (or V4A doesn't work with wrong selinux mode). Point is -- I personally need non-systemless boot.img for hammerhear 6.0.1. Is there a way to achieve that?
[SuperSU] c3k:
I solved battery percentage bug flashing again stock mmb29k boot.img and SuperSU 2.61.

Since first time I use SuperSU 2.60, I flash again the stock boot to confirm the bug, but no lock, working with 2.60 too now.

Finally I found the real bug: me. I forgot to flash the boot during the update process so I was running mmb29k (6.0.01) with mra58u (6.0.0) kernel!

Maybe [MENTION=2992105]fasthair[/MENTION] [MENTION=4289856]street_dog[/MENTION] break the habit to flash boot.img like me :)
[SuperSU] lynnux:
+1 It's probably on the V4A people to come up with a solution to this, though. Can't hurt to ask ?

Everything else on my N5 is working fine with 6.0.1 + SU 2.61. Thanks.
[SuperSU] mukintaras:
Of course I'd go there first (and I did a few days ago) -- but there will be no good, because as far as I understood V4A development stopped quite a while ago
[SuperSU] kundica:
I was about to flash TWRP to install this on my S6. Would an Odin flashable version of Systemless SuperSU avoid tripping Knox? Doesn't really matter to me but if I can avoid it, why not.
[SuperSU] :
I think this latest superSU is to a point where I can switch to systemless without loosing functionality in *most* of my root apps. just a couple things I could not find info on after reading through a ton of posts here. I am hoping someone can point me in the right direction

1. If we want to modify /system (remove apps/files/modify build.prop) is there anything that allows this with 2.62? Usually I used solid explorer but it will not delete files in /system with this version of superSU (EDIT/UPDATE root explorer seems to work ok to remove files in /system without any strangeness like blank files etc...if anyone has any feedback about this I'm still open to hear it, thanks!)

2. What is the recommended solution for a working busybox install with systemless

3. What is the recommended solution for adaway?

TIA
[SuperSU] Naisang:
[solved] had root all the time - ES File manager doesn't detect

I used a few other apps and did have root all along the way. thanks [MENTION=631273]Chainfire[/MENTION]!

ES File explorer doesn't detect this method of root however. So that's the issue, but easily surmountable: used another app. ..
[SuperSU] RusherDude:
[MENTION=631273]Chainfire[/MENTION], thanks for the awesome work, as always :)

One fast question: Up there you said that you were not recommending systemless v2.61 "yet" over v2.52, but that you "would soon". For Android 6.0.1 and maybe next releases, the system option will be completely dumpled out, or both options will be eligible? And for now, can we keep with 2.52 forward until new advice or its not recommended anymore? I am one of those that end up doing a lot more modifications to /system so systemless root doesn't seem any better than normal root, and not worth the hassle.

I'm sorry if I skipped anything :P

Thanks a lot!
[SuperSU] mobileman88:
Yes. 2.60 and 2.61 are systemless roots.
[SuperSU] jcsww:
I have no issues with Titanium BackUp on 6.0 or 6.0.1.
[SuperSU] mattcoz:
I was able to update build.prop using recovery per Chainfire's recommendation. Thanks!
[SuperSU] street_dog:
This problem occurs on my Nexus 5.
[SuperSU] zohaib0001:
[MENTION=631273]Chainfire[/MENTION]

SuperSU V2.61 system less

Please make it compatible with Sony Xperia devices on 5.1.1 also
[SuperSU] GPS3:
Thank you. Incredibly easy to do.
[SuperSU] sirxdroid:
Thanks for your replies [MENTION=631273]Chainfire[/MENTION] and for your continued work and support. While systemless root is the right longer term move, until we get unionfs/overlayfs I don't think many of us can escape still modifying /system for various reasons. Yes, we can already bind mount by hand various files and directories and manually fix apps that need need to change /system (and even some of them need to be installed as system apps) but this gets annoying quickly at least for Nexus devices that receive the monthly security updates from Google.

I would appreciate it if you could still have an easy way to have a /system based root. I read your post about touching su in /system, would be possible to provide a flashable zip that does just that? Or a version of SuperSU that has the switch set to install in/system? Just looking for an easy way to be able to take the monthly security updates without going the custom ROM or kernel way. Thank you.
[SuperSU] jcsww:
I completely agree! I change some system sounds and add the no tether check to the build.prop with every update Although systemless root isn't the best option for me. I do think having both as an option would be great, if not too much to hope for.
[SuperSU] ettore88:
Hi guys!!!My question to you.I have Samsung S5 with CM12.1...Supersu 2.60 or 2.61 are compatible?Bye
[SuperSU] TR2N:
Hi guys, is there a way to install busybox for systemless root?
[SuperSU] Ja_som:
Install to /su/bin

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post64174675#post64174675
[SuperSU] hassann98:
Hello

After installing supersu 2.61 in twrp recovery The phone was bootloop

galaxy s6 edge

G925FXXS3COK5
[SuperSU] TR2N:
I tried with Busybox Pro, but it installs always to system\xbin...
[SuperSU] sirxdroid:
Copy /su/bin/su into /system/xbin and you should be good. I think. You have to remount /system rw to do it, then reboot.
[SuperSU] Ingenium13:
I had this happen once before. It's causes by a newer sqlite database schema being used. The database gets updated to the new schema and when you revert it breaks it. Watch logcat while it boots and you should be able to see the file that's causing the error. Delete it and reboot and it'll be recreated with the correct schema for 6.0.0.

Sent from my Nexus 6P
[SuperSU] c3k:
Modify the kernel is very simple, you can find a thread for 5x maintained by me and the instructions to build you own are posted few page before in this thread.
[SuperSU] Poeta:
[MENTION=631273]Chainfire[/MENTION] i flash the SuperSU 2.61 in my Moto G 2014 (CM13), the SuperSU works great but my Bluethoot dont detect any device.

PS: solved. I flash again the CM13 and supersu, wipe cache/dalvik and now all works well :)
[SuperSU] springer.music:
Thank you! Good to know. I'll keep that in mind for the future.

Further to [MENTION=631273]Chainfire[/MENTION] 's tip about not having enough space in /system, I've again flashed 6.0.1 and removed some system apps. All seems to be working OK now.
[SuperSU] :
2.61 does not seem to work completely with titanium backup. I can no longer delete system apps. Any fix for that?
[SuperSU] Theliels:
Working Fine systemless 2.61 here in my N5, and i can mount and change my system partition perfectly.

Some of my Root applications have required however "touch" su on /system/bin and /system/xbin, but all working now.

thank Chainfire. http://xdaforums.com/member.php?u=631273
[SuperSU] junior00027:
me too
[SuperSU] Crazy Chuckster:
Is there a write up on how to root a Nexus 5x with systemless? I cant seem to find the steps.
[SuperSU] Maxr1998:
Well, just install TWRP recovery, and flash newest SuperSu from there. Done.
[SuperSU] Ch3vr0n:
Sure. Adb flash stock system and boot. Boot up custom recovery, flash latest beta, done.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] Crazy Chuckster:
Well that's easy enough! Can I disable encryption with systemless as well?
[SuperSU] Ch3vr0n:
Afaik you don't need to decrypt then reencrypt.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] bing321:
2.61 systemless does not persist after reboot

Hi, just upgraded to nexus 6p to 6.0.1 and flashed 2.61 with twrp. Everything works as before, except the modifications to boot.img do not appear to persist between reboots. Is anybody else having similar issues?
[SuperSU] PuNcAkE_15'l:
[MENTION=631273]Chainfire[/MENTION] has v2.52 or up been tested on htc one m8 running Android 6.0. Everytime I try to install super su I have to restore my phone. I have root but I've just been using privacy guard as my root manager
[SuperSU] Kristian2018:
Just flashed 2.60 on my m8 running jw 4.01 A9 mm ported rom with elementalX kernel and no problems so far
[SuperSU] vincowoo:
A.A sir having problem system uid asking for permissions ... mostly happens in incoming calls even can't answer phone call. Dialogue box appears again and again until i pull off battery or long press power button for 1-2 minute ?

Reflashed stock firmware

Updated busybox

Updated su binaries using beta 2.52 apk (as worked for one member)

Fixed android permission

Wiped cache and delvic cache

Nothing seems to work

Please help me

I am using s5 900fd stock kk version

Xposed , twrp , and back on su version 2.45 installed all works fine except on occasionl phone rings.
[SuperSU] occtec:
[MENTION=631273]Chainfire[/MENTION] updated to latest beta but terminal emulator reporting 2.15 installed. After flashing latest 2.16 I wasn't prompted to update binaries after reboot??

Edit: Nexus 5 on MAHDI 2.9 Final
[SuperSU] Chainfire:
The answer you seek is in the first post.

Now go stand in the corner for a while and be ashamed of yourself ;)
[SuperSU] Tanis64:
Read the first post:

BETASuperSU v2.16 = Binary v2.15

Send from the outback with my GT-I9505
[SuperSU] occtec:
Haha, LOL! Don't ask me how I missed that one, better go back into that corner as you suggested [emoji5]
[SuperSU] Megaflop666:
V2.16 is working great on s5, note 3, gear 1 and on kk rom on my nexus 7, BUT, I'm having troubles with root on nexus 7 lollipop preview.

Setup:

Nexus 7 2013

Multirom manager

CM11 primary rom

Lollipop preview secondary room

Injected modified boot.img

Flashed V2.14 and play store updated to V2.16

Can only get root in terminal emulator so far

Root checker says its there

Tibu says no root

Es file explorer says no root

Anything I'm missing in the setup?
[SuperSU] mpgrimes:
Code blue l kernel is not compatible with the latest preview, says so in the thread. Latest release has a new kernel and no source available yet to build one
[SuperSU] Diaphragma:
It's supported. http://xdaforums.com/google-nexus-5/orig-development/kernel-t2803857
[SuperSU] mpgrimes:
My bad. Thanks for pointing it out. I'll try it and test supersu
[SuperSU] Diaphragma:
Cool beans. I've got Titanium backup, and greenify to work by updating to the beta versions. Still, most root apps will not work.
[SuperSU] Megaflop666:
Update: root explorer pro now works with root, and terminal emulator still works.

Completely uninstalled es and tibu and reinstalled them but still no luck with root there.

Edit: I'm an idiot. Got tibu for lollipop and it works great. Still battling with es file explorer.
[SuperSU] 1haumann1:
es file explorer needs an update so don't waste your time and try another one ;) x-plore e.g. works fine for me

keep calm and have a Nexus :D
[SuperSU] steviemch:
Strange, I'm using ES (I wouldn't use anything else tbh) on my N4 running the latest N6 port, and root functions work without a problem. Editing files, changing permissions etc all work as expected.

Sent by Borg neural subspace transceiver node.
[SuperSU] Ben36:
Do you get miscellaneous battery drain tho?

Sent from my Android 5.0 Nexus 5
[SuperSU] steviemch:
Yeah, but it doesn't bother me at all. It's been there since I flashed the very first preview 3 months ago, and doesn't actually impact on my battery at all, I actually get quite good battery/sot.

Sent by Borg neural subspace transceiver node.
[SuperSU] Ben36:
It's probably es causing it tho. I just find it annoying. Lol

Sent from my Android 5.0 Nexus 5
[SuperSU] JaCh0o:
Logcat attached. Started logcat after reboot, entered SuperSU updated biniaries - normal method, success, opened and closed few root needing apps - lost root privillage, opened SuperSU app on question to update binaries - canceled = quit for app then stopped logcat.

Please find solution you're the only hope. I can provide file which got working binaries (system doesn't revoke them).
[SuperSU] sndrdg:
A sometime loosing battle with Root App Devs - Thanks CF.....

It would seem to me - that if developers of "root needing" applications want to continue to sell their wares, they need to do a better job with supporting and keeping up with [MENTION=631273]Chainfire[/MENTION] efforts to provide this "Root Granting" framework. With the challenges of "L", context switching, Knox, SELinux etc..., you would think that root app developers, would go out off their way to be here, on beta forums, to see what's coming, to support CF, to make suggestions, and perhaps most importantly to learn how to best write applications that work with the root framework that CF is providing.

Perhaps a classic case in point: CF provides new Market Version for mass public consumption. A popular root app program by Fahrbot, called Call Master (Root Call Blocker), seems it can no longer obtain root, and continuously attempts to obtain root, causing amongst other things, unexplained battery drain. Fahrbot is usually quick to fix his product, but what disturbed me was

the release note comment "Workaround for new supersu". As if SuperSU was the cause.

What was his "workaround" - It was issuing his root command as follows:

"sh -c su 0 -c sh".

(Perhaps those more technical - can see what this does instead of plain "su 0" - and can figure out why this "workaround" - solved this devs problem)

CF I appreciate your continued efforts to stay on top of this. (ie. and spending less/ no time on trying fix/prevent people from voiding their warranty's - imo, screw the warranty - I need root)

Regards,

Doug
[SuperSU] Chainfire:
Something keeps deleting your su binary file ...
[SuperSU] remicks:
[MENTION=631273]Chainfire[/MENTION] ironically I'm actually working on proper supersu integration across all devices and architectures without the annoying binary update on first run for the ROM I'm working on now because of 90% of what you just said. And thanks to your easy to understand method of installation I've almost got it completely ready. Hopefully other devs will pick up this method of integration for the benefit of their end-users. We also labeled your space in settings as Chainfires SuperSU since you don't get enough credit for your awesome work.

TL;DR = You rock and keep up the awesome work.

Spoiler content hidden.
[SuperSU] dechronic:
Shouldn't systemless su for Marshmallow be the following?

su
mount -o remount,rw /system
touch /su/bin/su /system/sbin/su /system/sbin/su
mount -o remount,to /system
[SuperSU] maximumentropy:
If you're using my zip to set the supolicy for v4a, I just updated it for compatibility with systemless root. The zip will still modify your system, but the /system/su.d/50viper.sh script no longer hard-codes the path to supolicy. I'm using it with systemless SuperSU 2.61 and it is working for me on a Nexus 6.

https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0

Regards,

maximumentropy
[SuperSU] hinmatth:
Same here :(
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION]

So the classic, ever so great method of root has been dethroned then? Just like that? No more system root? Not even a thorough explanation or farewell?

If systemless is the future, fine. I just won't update atm. Apps that install on the system partition are iffy or they require symbolic link or they just don't work. Too much work if you ask me.

I understand this is a transition but i would of at least liked system root support until systemless gets good enough.

/Rant

With that said, Is there a way to update Nexus 6P to 6.0.1 system root right now?
[SuperSU] tsadev:
Would like to see this for my VS985 as well, attached is a python script (open_bump.txt, xda doesn't allow .py files) that does the "bumping" . I figure it might be of some use in writing a custom script for the G3s.

NOTE: Open Bump script was created by a group called CyboLabs in response to the closed source bumping method originally provided for G3 variants (read: drama). I don't have a link available but a quick search should direct you in the right place.

I saw your post saying that you don't know that you will include it. While I understand why you wouldn't want to, if you're okay with it I might like to maintain (for a time at least) a modified version of 2.61 that includes the bumping script for those of us with G3s once mine comes back from LG.

Thanks for all your hard work!
[SuperSU] ranasrule:
Can someone point me towards a download link for 2.61 ? Is it safe to flash/install on custom roms ?
[SuperSU] force70:
Search function works wonders dude :D

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

Sent from my Note 5, Note 4 or Nexus 6
[SuperSU] WhammyDroid:
This.

How do we get around this?
[SuperSU] CLAWHAMM3R:
I flashed all fresh MMB29K, then 2.61 and did not let TWRP root me, but I keep getting fails updating the supersu binary. Let me know how I can help. I wouldn't rule out user error, but I followed the straightforward instructions straightforwardly.
[SuperSU] dechronic:
Two previous very recent posts, have suggested a different app to accomplish this.....each post suggests a different app

1. http://xdaforums.com/showpost.php?p=64206594&postcount=3370

2. http://xdaforums.com/showpost.php?p=64208381&postcount=3392
[SuperSU] Neverendingxsin:
Same issue here.
[SuperSU] Maxr1998:
I guess the patched boot image still allows disabling encryption; [MENTION=631273]Chainfire[/MENTION]?

If yes, then you only need to format data from TWRP (data & internal storage).
[SuperSU] mobileman88:
What file should be deleted?