yashsingh1/xdaforums huggingface dataset:
[SuperSU] dcacklam:
So, has anyone managed to get a version that doesn't wreck WiFi calling on Tmobile (US)?

I've got a Nexus 6, and applying Systemless Root breaks WFC. Flashing boot 'back to stock' results in wifi calling coming back, so it definately is systemless root (probably via the use of a custom kernel) that is breaking things.
[SuperSU] DaweisCZ:
I tried install on GT-P7500 6.0.1. by TWRP ... all went fine but when i boot in system , root is gone ... any ideas ?? Working with 2.52 tho
[SuperSU] codycook:
Nexus 6, 6.0.1 December. Systemless rooted on 2.64. Tried to flash the latest using zip. It flashed alright I guess but it couldn't repatch my already patched boot image. Should I reflash stock boot and reinstall? My problem is SuperSU can't seem to update the version of su. Said to come here.
[SuperSU] osm0sis:
I recently found Cyanogen(Mod) Recovery doesn't have /data (or /cache) mounted by default. :eek:
[SuperSU] bgx:
Thank you chainfire for help. Here's the log from my huawei mate s. Seems that patching the img goes wrong?

Gesendet von meinem CRR-L09 mit Tapatalk
[SuperSU] Chainfire:
Yes

Supporting ChromeOS bootloader and boot images is a ****load of work. Lots of stuff needs to be ported. I'm simply not going to do it for one device, that's not even very popular.

It should never have shipped that way, and it is unlikely we'll ever see another device with this setup.

In other words, the Pixel C is so far the only device that's officially unsupported.

No idea.

Please provide your recovery.log file from TWRP.

Yes, try reflashing stock boot and trying again.

Can you even use CM recovery to flash arbitrary ZIPs? I thought it just did CM-signed stuff. Never really looked, though.

It thinks your system should be able to work with system-mode root. But it can't. I don't know why.

You can try forcing system-less root by doing this:

adb shell "echo SYSTEMLESS=false>>/data/.supersu"

before installing SuperSU again through TWRP.
[SuperSU] osm0sis:
Just needs to be test-keys signed like we usually do. :good:
[SuperSU] bgx:
I tried with systemless=false but now I stuck on black screen while rebooting. I will upload the log.

Damn can't rollback to lollipop stuck on mm but need root...
[SuperSU] Chainfire:
Try reflashing /system if you have a full firmware (if you do, link?), then doing systemless=false, TWRP flash supersu.zip, and post log.

Before rebooting, wipe /data/security/current, if present.
[SuperSU] bgx:
Will try later. I roll back all the time with an unroot script I found some where in the posts. Hope that's OK?

Will post later the result. Thx for helping out chainfire

Gesendet von meinem CRR-L09 mit Tapatalk
[SuperSU] osm0sis:
Please do not repost my script, link to my post if you must. 24,000 people were able to find it just fine on their own. It's also stated in the instructions in that post that it is for 2.52 only and has no effect on systemless root..
[SuperSU] bgx:
Oh sorry didn't know that. I change my post. Sorry.

Gesendet von meinem CRR-L09 mit Tapatalk
[SuperSU] devil-kin:
I've been trying to root my OnePlusX, that I got yesterday. For some obscure reason I keep getting avc denials, in several apps. It's running OxygenOS 2.2.0, android 5.1.1. Does this need a special boot image? I thought just flashing the latest (beta/stable) supersu would do the trick, but sofar, no luck (especially with TitaniumBackup)

Any ideas?
[SuperSU] bgx:
Tried with wiping security but also black screen. More can't do at moment because I'm not at home. Try later and report.

Gesendet von meinem CRR-L09 mit Tapatalk
[SuperSU] Ch3vr0n:
Instructions clearly state that the last build supported for lollipop is 2.49 official. 2.67 beta requires marshmallow or some way Samsung rom's.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] shaggyskunk:
I've successfully Flashed 2.66 on a Note 3 running SlimLP 5.1.1 - Lollipop fyi

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] Ch3vr0n:
Then your lucky I suppose. Beta details do specify M requirement

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] xdadroidabc:
Device - Edge plus 5.1.1

Using Systemless root 2.67

Titanium backup work only if untick mount namespace separation but doing this Tasker does not work properly. (developer said to keep enabled)

No issue with system root 2.52 and both working fine with namespace separation enabled.

Any help will be appreciated if both can be used.
[SuperSU] Tinchoska:
https://mega.nz/#!nIUTRBII!mljS6rJF175DH9hpjeEbeKG3HmNLPwL9MU2KX4vRCz0 here you have, let me know what else you need

Enviado desde mi SM-T700 mediante Tapatalk
[SuperSU] cdiaz92:
Ive been using the 2.67 beta for some time now on my note 5 6.0 marshmallow. It works good with most root apps but has trouble with the WiFi tether app keeps rebooting my device when the app is enabled.
[SuperSU] bgx:
Here's a new log.
[SuperSU] followmsi:
No good news for a pixel c owner :(

There is already a working 2.66 version for pixel c - done by [MENTION=4867279]cheep5k8[/MENTION]

Don´t know how much porting he has done for this version .. works fine.

Will see how "we" manage this issue on the long term.

"officially unsupported" - sounds not so nice :)

Cheers
[SuperSU] tet-bundy:
Why update when everything works?

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] devil-kin:
Okay, I missed that (and can't find it?) .

Also assumed that, with a new version becoming stable, if would support older android releases too... It's going to get mightily confusing for anyone if you need to keep in mind what version you need to flash for a specific android release. But I'll test it tomorrow.
[SuperSU] rogers11:
Read the changelog. Your information is completely wrong.
[SuperSU] Chainfire:
Please provide logs of said avc denials.

You have misinterpreted. This is not the case.

This issue has been reported for a while, and I have *finally* been able to reproduce it properly. I hope to have a fix next update.

The boot image is using a compression format not currently supported by SuperSU's auto-patcher. It will be another week or two before I have a fix for that.
[SuperSU] Tinchoska:
Thanks, ill be waiting forma that,if you need tester ley me know

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] bgx:
Hey chainfire. You have found something in my logs for rooting huawei mate s with marshmallow? Or you need something more?

Gesendet von meinem CRR-L09 mit Tapatalk
[SuperSU] rootinchase:
I have a galaxy s3 that is still stock 4.4 and I was wondering if there was a way to do a systemless install on it.
[SuperSU] xdadroidabc:
That forces me to use custom kernel. To use stock kernel I must have to use system less method which giving this error.

Thank you very much.
[SuperSU] dcacklam:
I figured it out.

It's busybox being located too far forward in the path in the /su folder, that is breaking wifi calling.

Moving busybox from /su/bin to /su/xbin (mount -o remount,rw /su; mv /su/bin/busybox /su/xbin/) and rebooting brings back wifi calling.

Perhaps BB could be placed in the xbin folder in future releases, to unbreak WFC?
[SuperSU] osm0sis:
Already well known. I proposed and Chainfire created /su/xbin for this very reason. Tell your busybox provider to fix their installer.
[SuperSU] lethang90b:
i could not find /su folder in system to change permission to able android pay. any help please ? im running last pure nexus rom, then already flash super 2.67
[SuperSU] nathanchance:
This thread is a better space for this discussion, I will mention you in it with the response.
[SuperSU] _that:
How can the presence of busybox break any ROM feature? Is this about the symlinks or about the busybox binary itself?
[SuperSU] osm0sis:
It's about the PATH order. /su/bin is ahead of /system/bin in the modified systemless root PATH, so anything in /su/bin takes precedence over the ROM binaries/symlinks in /system/bin. Not sure why WiFi calling is reliant on toybox, but it clearly is, and as to why busybox's applets aren't as good as toybox's in this respect, your guess is as good as mine; someone on T-Mobile or Project Fi with a 6P or 5X should debug what's happening when broken. :)

The main reason we're still seeing this pop up is because Stericson hasn't updated his installer to use /su/xbin instead of /su/bin by default when it detects systemless root (and preferably not offer to use /su/bin at all since that's equivalent to /system/bin in terms of breakage). I presume he's busy, since I emailed him over a month ago. :confused:
[SuperSU] Flopik2:
I have no clue :(
[SuperSU] _that:
I know about the PATH order, but how can just moving the busybox binary without moving the symlinks fix that?
[SuperSU] A_XDA457:
Systemless Root

Where can I find the systemless root install?
[SuperSU] a1exus:
I believe first post, should do it..
[SuperSU] Halaster:
I am stuck in a boot loop on my S-OFF Sprint HTC One M9 running the latest marshmallow build using BETA-SuperSU-v2.67-20160121175247.zip.

Everything appeared to install perfectly fine, and stated it would reboot a few times, but it has been stuck in a boot loop for an hour.

User Error: I am not running a custom kernel.
[SuperSU] osm0sis:
Ah! I didn't read that part closely enough, I guess. Not sure, maybe if the /su/bin symlink is faulty it falls back to /system/bin which is next in line?

Edit: Yup. That's why. He'll still need to fix his busybox installation by deleting the old symlinks and making ones for the new location, but his system is back in working order just by breaking the /su/bin links.
[SuperSU] AndDiSa:
Only to mention: v2.67 doesn't install systemless on Nexus 7 (2012) with Marshmallow while v2.62 does :(
[SuperSU] JimSmith94:
Interesting, this is the first I've heard of this. I just noticed that my WiFi calling hasn't been working about since I installed SU 2.67. Would doing this move with Root Explorer accomplish the same thing?
[SuperSU] Aakash Kaushal:
Can i flash v2.67 over v2.46....without any bootloop?..i am using s4 (gti9500).
[SuperSU] spainter:
http://xdaforums.com/showpost.php?p=64161125&postcount=3

If you are coming from any SuperSU install in /system, you must re-flash the stock system (and vendor and oem, if present) partition contents prior to installing this.

If you are coming from a SuperSU 2.56 system-less install, you must re-flash the stock boot image prior to installing this.

If you are coming from a SuperSU 2.60 system-less install, or were not rooted at all, then you can just flash the ZIP without any special prior instructions.

If TWRP offers you to keep /system read-only, indeed keep it read-only.

If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!

If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image. The boot image patcher currently only supports gzip compressed ramdisks and the standard Android boot image format. Some devices do not use the standard format, and many custom kernels use a compression other than gzip. A backup is made (/data/stock_boot_<sha>.img.gz) of the original boot image before patching it.

Further implementation details (including an updated list of changes to the ramdisk) are explained in the installer script itself, as usual.
[SuperSU] Aakash Kaushal:
I am using v2.46 in 5.0.1 touchwiz(unofficial rom)...can i directly flash it...actually i dont know about system less image?

My rom has already rooted by default(v2.46)...i just want to update my supersu..

Can i uninstall 2.46 with the suuninstaller.zip or from the app itself and then will flash the 2.67 beta su...?will it work?
[SuperSU] Manuel15:
The unSU zip only works with 2.5.*

Use the app's option and then flash 2.6.7, it should work
[SuperSU] Aakash Kaushal:
Okay i will try..i hope it will not give a bootloop:p

Edit - flashed successfully...thankyou mate:)
[SuperSU] AggelosGR:
i cannot install it at my sony xperia m with cyanogenmod13.

tried from TWRP and with supersu from google play.

anyone managed to install it?
[SuperSU] Manuel15:
The app can't install root by itself. About the flashing using TWRP, could you provide logs?

After trying to flash SuperSU, use the save log option in twrp, and then share the logs here
[SuperSU] AggelosGR:
Cyanogenmod 13 has already root enabled.

nightly version is 20160209 and i havent touched anything.

here is the twrp log
[SuperSU] aheeejd:
I've been flashing 2.66 ever since mm was having issues with the 2.52 beta, & the 2.46 regular. Is this updated 2.67 ok to flash instead of 2.66? For mm only right. Sorry if asked,
[SuperSU] Manuel15:
CM13 has system root inside the system.

According to the log the script tried to install the system-less root (it seems to me). This will cause issues, did you have bootloop?
[SuperSU] AggelosGR:
no bootloop cause nothing installed.

what version shall i try?
[SuperSU] Tinchoska:
Same problem here on a Moto x, take a look at this answer chainfire gave me http://xdaforums.com/showthread.php?p=65195500 maybe it's the same....

Enviado desde mi XT1095 mediante Tapatalk

---------- Post added at 08:25 PM ---------- Previous post was at 08:25 PM ----------

Try with a custom kernel....

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] dcacklam:
At least on my device, I had not run a busybox-link-installer. Busybox was in /su/bin, but all of my /system/bin (et-al) links still pointed to toybox (as per ls -la)

The mere presence of busybox in /su/bin was causing the 'issue'.

Moving it to /su/xbin/ without doing anything else brought back WiFi calling, while apps that are looking for the busybox binary specifically are still able to find it.

---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------

You don't need systemless root with CM. It doesn't actually 'gain' anything for you, as CM is rooted-by-default/design.

Systemless root is for folks running stock roms (including Nexus devices), who want root without modifying their system partition (So as to allow OTA updates & (incidentally) make Android Pay work.

---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------

Yes.

If you have replaced any symlinks to point to busybox instead of toybox, you would have to change them back, as well.
[SuperSU] Ch3vr0n:
[MENTION=4544860]osm0sis[/MENTION] your wish has finally been granted. Busybox just updated with /su/xbin support

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] osm0sis:
Haha not quite.. While /su/xbin is now in the list in Stericson's app, it still appears to default to /su/bin when it detects systemless root. :silly:
[SuperSU] Ch3vr0n:
True, but you can still manually select xbin. :) better than nothing

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] zishukkc:
i'm allready using SuperSU v 2.66 on my Samsung Touchwiz 5.1.1

please tell me the procedure to update to v 2.67??

can i just dirty flash it using TWRP???
[SuperSU] nathanchance:
Yes.
[SuperSU] Aakash Kaushal:
I recommend you to first uninstall the v2.66 from the app itself or from uninstaller and then flash the 2.67 (by the way many ppl said to dirty flash but you should always uninstall the previous one while updating to new one and also i dirtle flashed to the latest version 2days ago and i got bootloop thatz why i am saying.)
[SuperSU] zishukkc:
thanks, so you mean first i shuold full unroot using the SU app itself & then flash it?
[SuperSU] Aakash Kaushal:
Yes...but do a nandroid backup first, if anything goes wrong.
[SuperSU] zishukkc:
ok thanks buddy! ✌
[SuperSU] bgx:
I think I found, why root ended in bootloop on my Huawei Mate S. I found that ro.secure=1 in default.prop

Is there a way to set it to 0 in twrp and it survives a reboot?
[SuperSU] robertogl:
Well, i've a problem. On Android 6.0.1 i've tried only beta 2.66 and 2.67, and with both i can't see SuperSu app on drawer, and i can't see the popup for deny root access. Every app can use root without asking me (so root is working).

I'm on CyanogenMod 13, i can see the SuperSu apk if i search with some file manager, but it doesn't seem to work... Anyone has that problem?
[SuperSU] simple man:
On CM, SU settings are either in settings, or developer settings. I'm pretty sure it's developer settings. I can't remember which one, because I'm not using CM.
[SuperSU] robertogl:
Yes, but there are Cm SU settings, not SuperSU settings. On previus CM (like 12.1) SuperSU took the place of CM root (not in the settings, but with the app). If now i enable root from settings, i lose SuperSU (and some apps, for some reason, need that).
[SuperSU] jtwebfusion:
Did you let it boot up before flashing SuperSu? If not, I recommend doing that.
[SuperSU] Jamesits:
No. For some reason I need to setprop something every time it finishes boots, so I need root on first boot.

Would this bring further side effects?
[SuperSU] firefoxjds:
CM 13 is already rooted

In order to acess root options go to settings and then about phone, under the about phone menu scroll down to the build version. Tap the build seven times to unlock developer options. Go back out to settings menu open developer otions near the bottom beside about phone. Scroll down to root. You can enable root there for apss or adb or both :) cheers, hope this is helpful.
[SuperSU] apollokid:
OK I have a Nexus 7 (2013) and I cant for the life of me get a Systemless root via 2.67. I previously was rooted the old way and reflashed the system partition back to the latest stock image (Feb 2016) per directions. Every time I attempt a systemless root however, it does a System-Root not Systemless. I've tried both via TWRP (3.0) and via adb shell:

echo SYSTEMLESS=true>>/data/.supersu

Doesn't seem to make a difference. Anyone else have this issue with Flounder (Wifi only)?
[SuperSU] Ja_som:
No, I don't have this issue, I use systemless root since v2.62, and I always get systemless root....
[SuperSU] spainter:
Flash the system and boot images both have to be stock.
[SuperSU] boomop:
Thanks, in fact I have had root activated in dev options before I successfully installed systemless root. The problem with version 2.67 was in fact due to a corrupt download.
[SuperSU] Tinchoska:
Guys noob question, what us the difference between installing busybox on su\bin and system\bin

Enviado desde mi SM-T700 mediante Tapatalk
[SuperSU] Ch3vr0n:
Simple, the latter modifies the system partition and voids ota eligibility.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] apollokid:
flashed the bootloader

fastboot update image-razor-mmb29q.zip
[SuperSU] Ch3vr0n:
That's not stock. You have to flash the STOCK boot and system from the previous. Which I believe was mmb29k. Fastboot update isn't the way to do it

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] corkiejp:
In system it modifies the system partition, so OTA's won't work. Check Out Chainfire's Flashfire app.

And it also advised to install it to /su/xbin to avoid conflicts with system apps (something do with paths).
[SuperSU] Chainfire:
I wish people would stop posting this and similar messages, because it is completely wrong. Yet someone posts it in either this BETA or the STABLE thread almost daily.

Regarding CM, various other root methods (last time I checked, including CM's root) do not generally allow root apps to modify SELinux policies. Some of these ROMs run in 'permissive' mode where it doesn't really matter, but by now many run in 'enforcing' mode. This means that any root apps you run this way are still restricted by any SELinux policies that may be in effect, and they cannot change them. As such, these are not 'full' roots, as your root is still restricted in arbitrary ways.

In essence, you are still restricted to doing whatever the person who authored the SELinux policies thought you needed to be able to do. Stop me if this sounds familiar - the whole reason we need root access is because we don't want to be restricted to what the Android devs thought was all we needed to be able to do!

Thinking you are able to predict the limits of what people will want to be able to do is in my opinion nothing less than naive. And while it is obvious why Google does it, to me it seems wrong to have it in a root solution.

Note that locking down SELinux policy modification if the user wants that is a one-liner bootup script, while opening it up is not possible at all with these 'naive' roots.

Regarding systemless, it is not just to make OTAs easier, stock ROMs, Android Pay, or not modifying /system. Those are side effects. From 6.0 onwards, any boot image based on AOSP (without specific mods) requires patches to be able to provide root. Systemless root exists primarily because if we already modify boot, we don't need to also modify system. Why do two invasive modifications if we can get away with modifying just one? That is the base, OTAs, AP, etc, are just added benefits.

It is by all means the new normal. That some ROMs (boot images really) can do a proper system-based root is the exception, not the norm. The option only still exists on 6.0+ so it can potentially make life easier on the flash-a-holics, should everything they flash be able to handle it gracefully. And we're certainly not at that point at this time.

Sorry but I don't think this property is related to your bootloop.

Hmm, I don't see anything SuperSU specific in your excerpt. I am travelling so I can't check your full log at the moment though.

Please post TWRP's recovery log.

It isn't? As far as I'm aware that update command would flash both the stock boot image and system image.
[SuperSU] Tinchoska:
So, we still aren't able to have super Su on cm, I got the point?

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] Wyneg:
I have super su 2.67 on CM13 (xt1040) working flawlessly... ¿?
[SuperSU] Gandalforce:
Did you back up data and system? Try to flash last known working SuperSU. Then unroot, install SuperSU beta app, then flash zip
[SuperSU] Tinchoska:
I can't get it work.... Chainfire told me it was a boot stuff problem.... That he will try to fix... Do you have a customer kernel?

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] Wyneg:
Nope, CM normal kernel, what custom recovery are you using?
[SuperSU] Tinchoska:
Twrp 3.0.0-0 and before this one I was using previous version... You? Do you have a flashing Method? Or just flash?

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] Wyneg:
Just flash in recovery, but I always do a wipe (dalvik and cache) before and after install rom, supersu, xposed, etc.

Using TWRP 3.0.0.0 (before 2.8.7.0).
[SuperSU] mielletseed:
Wiping before AND after is what good for?
[SuperSU] Wyneg:
I don't know, it's just in case, xD
[SuperSU] juanspot:
moto x pure edition

Hi there, produces boot loop in my xt1575 Marshmallow with TWRP 3.0.0-0. =(
[SuperSU] Dr0idgroove:
I can't enable SuperSU after disabling it in SuperSU 2.67 beta

After disabling SuperSU in the app's settings and then opening the app a couple of minutes later I always get the message "the SuperSU binary needs to be updated". When I click Yes the update always fails. When I click cancel and go to settings to re-enable SuperSU it fails too. Yet when I then open the app again and cancel on the binary update message and go to settings it does show SuperSU as enabled. The notification with the # icon in the notification bar remains though.

I'm using a Nexus 5 with Android 6.0.1 (MMB29Q). Installed SuperSU in systemless mode via TWRP 2.8.7.1
[SuperSU] Manuel15:
Can you post TWRP log?
[SuperSU] krazyace35:
Any update on a fix for supersu 2.67 causing bootloop on M9 Marshmallow
[SuperSU] Quarktown:
SU problem

hi all,

first thanks Chainfire for opening a new world on android :).

I have a question.

I have a Nexus 5x with latest supersu 2.67 systemless root: all is perfect but with xmod app (dunno if you know the app) i have trouble granting su permission, the app grant permission on opening but when i have to use the main feature it report that su is not present. i wrote to the developer but no answer yet.

i read that with systemless root there could be some problem for the app to grant permission due to the method used by those app for requesting su.

anybody had the same issue also with other app? there could be any solution or workaround? can normal root solve this problem? does it worth or better wait?

thanks in advance and sorry for my bad english ;)