yashsingh1/xdaforums huggingface dataset:
[SuperSU] iBowToAndroid:
This happened to me with two Note 4s - one Sprint and one T-Mo, both on 5.1.1. Baseband, IMEI, Software version all went "Unknown" after installing 2.66 on a purely stock system. Everything came back after flashing a stock tar, and CF Auto Root rooted them fine with no adverse affects.
[SuperSU] :
I have a bootloop after install 2.52 beta on completely stock rom. Why?
[SuperSU] nathanchance:
Stock Android 6.0.1 doesn't have the proper sepolicy for system root. Flash SuperSU 2.67 and you will have systemless root.
[SuperSU] garyd9:
The simplistic single-word answer without giving enough information was in response to the question that also didn't give enough information (and likely was in the wrong forum anyway.)

What phone, what version of supersu, what app that requires root, what is the error message. Oh, and being that your using CM, you might have better luck talking to whoever is putting CM together on your device - I thought that CM came pre-rooted. If so, you'll need to communicate with the CM folks, and not here.
[SuperSU] Nekromantik:
Anyone on 2.67 have issues with re-enabling after disabling root in supersu app?

It unroots fine and then says it failed rooting and try again after reboot.
[SuperSU] Arsinn:
Is it possible to rooting mm (v6.0) by supersu+custom recovery or not?HTC m8
[SuperSU] zerber:
the su binary needs to be updated

can someone help me?!
[SuperSU] Pkt_Lnt:
Here.

http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] swallowingled:
This happened to me. I told it no to updating the binary and then canceled the dialog that told me it failed and then I immediately started receiving the notifications that apps were being granted root access. So for me at least it said it failed but it did not. All my root apps work as they did before, no issues and didn't need to reboot and try again.
[SuperSU] Nekromantik:
Yeah it works even though it asks for update,

However I cant stop the notifications. Annoying.
[SuperSU] gorilla p:
I ran into a strange issue on my Nexus 5X. I'm running Resurrection Remix (CM13 base). I flashed SuperSU systemless 2.67.

I have looked at my screen a few tines and would randomly see it powered on, but black. I can only see the dimly lit backlight. There were no notifications and it didn't go away on its own.

I checked wakelocks and SuperSU screen wakelock was active for 3h26m in the past 20 hrs.

I'm not sure what would cause this.

Any input?
[SuperSU] bobby janow:
I've just not been able to reenable SuperSU from the app itself once I disable it. I'm on 2.67 an N5x, Stock image with Cataclysm overlay and Franco r-5 anykernel. Even a reboot keeps popping up the message about reinstalling binaries. Rebooted again and SuperSU app will not launch at all saying something like, SuperSU is not installed or can't be found. Recovery flash of 2.67 brings everything back to normal. Anyone else seeing this or can be more specific on the exact error message?
[SuperSU] gorilla p:
You need to do some reading in the ROM thread.

Restore to latest factory. Easy to do it via Wugs.

Root and install custom recovery via Wugs

Boot to recovery and factory reset, format data if you want to disable encryption.

Flash ROM and GApps and boot to ROM. Ifnit gives you vendor binaries error, flash latest vendor image

Reboot to recovery, flash vendor image if needed, flash UnSu, flash superSU
[SuperSU] bunklung:
I am trying to change $PATH within a su.d script, but it's having no effect. Does this require a change to the kernel? Or is that $PATH being established AFTER su.d is executed?

I don't see where SU is modifying the PATH and when I unpack my unpatched stock kernel there is no mention of PATH in init.rc.

Certainly not the default place for a N6 PATH:

http://android.stackexchange.com/questions/3768/how-is-the-default-path-set
[SuperSU] osm0sis:
I don't think you can export any changes to the global path in Android unless you edit the ramdisk, which is in init.environ.rc (since KitKat, I believe). Beyond that the closest thing you can do is override it on your own specific shell instance by changing the command in your terminal emulator app, or within the script you're executing.
[SuperSU] Alxoom33:
Re flash SU 2.67

---------- Post added at 06:06 PM ---------- Previous post was at 06:05 PM ----------

Re flash Su! 2.67.
[SuperSU] gorilla p:
I reset and checked wakelock info again and saw Greenify had been causing a long wakelock.

I was trying the aggressive doze, and I also noticed it was unchecked for some reason under "Accessibility".

I checked it again and disabled aggressive doze. I'll see if that fixes it.
[SuperSU] Sachi315:
BETA 2.67 Issues

I installed beta 2.67. Wiped cache before and after. Install worked but crashed some android apps so I reinstalled stock marshmallow and installed 2.56 which had no issues its working fine.
[SuperSU] bobby janow:
I don't know what Wugs is nor do I care to know. I can restore to latest factory with my eyes closed. I don't care to disable encryption and if by now I haven't flashed the vendor.img I'd not be here. Please don't patronize. But thanks for the info.
[SuperSU] discslinger:
Please clarify...

Are you saying there is no need to type these commands if already "systemlessly rooted" so to speak? I am rooted on systemless root btw.

Also, when you say, "Select current folder" - what folder are you talking about? And in the case of the issuing a terminal command in TWRP menu - are you saying a text box open up when the 'current folder' is selected. This sounds weird the way this is worded, please clarify this - I appreciate it!

One thing Solved:

I see hitting the check mark in the corner brings up a terminal command box- or whatever that is called. Still... fuzzy on the "don't need to worry about it". What is 'it' ? Tx!
[SuperSU] nathanchance:
Yeah if you are on 2.60+ and flash 2.64+, the installer will keep your systemless root. You only need to worry about those commands on a clean install (when you wipe the /data partition). The current folder should usually be root ( / ). Yes, a text box will pop up that you type those commands in.
[SuperSU] discslinger:
Thank you! Now on Pure Nexus! Starting up now. Booted. Got 'vendor image out of date' message.

Is that a correct message... considering that I did flash the ' latest vendor.img' ?

I was on mmb29K and just double checked I did indeed download the correct zip.

Do I need to flash a stock vendor image?

Tx. in advance!

Going ahead to setup phone now.
[SuperSU] wvcadle:
Now that Google has patched AP, is there still a benefit of systemless root compared to traditional? For now, if one is rooted traditionally, could one still use AP by disabling SU beforehand, then re-enabling it?
[SuperSU] j1gga84:
I have a problem to install 2.67, I got following error message in recovery when I am trying to flash:

Boot image patcher:

-Finding boot image

-Boot image: /dev/block/mmcblk0p5

-Extracting ramdisk

-Failure, aborting

Using stock kernel.

The strange thing is that it worked in older builds of the CM12.1 based ROM I have currently installed.

It works without problems when I flash 2.46 in recovery :confused:

regards
[SuperSU] osm0sis:
Systemless is still the best way to root Marshmallow, and required for OTA on some devices.
[SuperSU] blackg3cko:
Where can i get cf- autoroot?
[SuperSU] Ja_som:
http://autoroot.chainfire.eu/
[SuperSU] Sc4ryB3ar:
Except for people already on L. Right?
[SuperSU] bombadier:
I thought to get supersu working on lollipop you needed the kernel to be patched so is a bit more involved than the usual flashable, the preview had the kernel patched so maybe 2.19 will work but for the factory images you would need to use CF-autoroot
[SuperSU] Sc4ryB3ar:
Ahhhhh, makes sense :)
[SuperSU] mr.pedro:
Lollipop factory image for Nexus 4 is available. I have unlocked bootloader and cmw recovery installed. Can I root it like in previous android versions? Can I simply flash "BETA-SuperSU-v2.19.zip" via CMW and root will work? Or is there some new step that is needed? I ask, because I have read that in lollipop rooting will be complicated. And I already have found this (autoroot.chainfire.eu) and I am confused.
[SuperSU] zadigre:
this has been discussed multiple times...

Lollipop right now needs a special kernel to be able to root.

CF-AutoRoot has been updated for the Nexus 4... you should use this method to root.
[SuperSU] mr.pedro:
Thank you for asnwer. And what about using custom kernels? If I want to use custom kernel, they will have to be updated too. Right?
[SuperSU] markd0wn:
Where do you see this? At the time of this post, http://autoroot.chainfire.eu/ still shows the KTU84P (4.4.4) AutoRoot version for the Nexus 4.

EDIT: Nevermind, just noticed that in the other thread, Chainfire said "the current Nexus 4 CF-Auto-Root should work, I updated that earlier today".
[SuperSU] clamitas:
Why won't Secure Settings get permissions on Lollipop?

I have flashed the latest AF-Root with SuperSU v2.20.
[SuperSU] Ben36:
Do u mean app ops?

Sent from my Android 5.0 Nexus 5
[SuperSU] clamitas:
No, I mean Secure Settings. The Tasker Plugin.
[SuperSU] Ben36:
Ah i see. I don't use tasker so assumed u meant that. Lol

Sent from my Android 5.0 Nexus 5
[SuperSU] mpgrimes:
Titanium has been updated on play store to work with lollipop. I've been using it for 2 days. And I'm using supersu 2.19
[SuperSU] yanner2012:
Yes, now it's work.
[SuperSU] varazir:
When I try to active the secure settings module I see this in the SU log.

I'm running 2.19
[SuperSU] JmaJeremy:
Flashed 2.19 to my Nexus 4 running Lollipop 5.0...SuperSU says the binaries are missing when I try to run it. I looked through the thread and couldn't find any solution to the problem. Does anyone know what to do?
[SuperSU] bombadier:
Use CF auto root for the nexus 4 it will patch your kernel and install version 2.20,the version you want may still be labeled for 4.4.4
[SuperSU] emperortomato:
I have the same issue w/ Secure Settings, running SuperSU 2.16 on Nexus 5 with Android 5.0, build LRX21O. Secure Settings has been granted permission, but when I try to enable the "System+ Module," it gives the message "Unable to grant permission" and then "Granting permissions failed".

The message logged in SuperSU is:

/system/bin/pm[6]: app_process: Permission denied

I've attached the two messages logged by SuperSU when trying to enable System+. The 'id' call occurs first, then the failure.
[SuperSU] mag01:
That's the application, not SuperSU, problem - it has to be fixed by the Secure Settings developers. They need to execute the pm commands in a privileged SELinux context (u:r:system_app:s0 I think).
[SuperSU] wvcadle:
I'm using a custom ROM, so I am not concerned with OTAs. I'm mainly looking for the easiest way to use AP with a custom ROM, as I've been doing until Google patched it yesterday.
[SuperSU] Pkt_Lnt:
You will get more help here.

http://xdaforums.com/apps/supersu/supersu-safetynet-android-pay-t3298115
[SuperSU] nathanchance:
If your ROM is pre-rooted, stick with the built in root. If it isn't, just flash SuperSU 2.67 and let it make the call.
[SuperSU] Alxoom33:
Go to the Su AP thread. You will find all your answers there.
[SuperSU] aavvaallooss:
http://www.xda-developers.com/android-pay-no-longer-working-with-systemless-root/
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=64913001&postcount=4589
[SuperSU] edrickmph:
All of a sudden, I got this message "the su binary needs to be updated, continue? But continuing just keep me failed installation.

I'm on the latest catacylsm, will cata still update coz its halted indefinitely or is it dead? Just asking. Or do I need to change now to another custom rom already?
[SuperSU] edrickmph:
Reinstalling SuperSU 2.67 solves the issue.
[SuperSU] SamuriHL:
^^^^^ You may want to add some useful info to your post like what device, version, etc you're trying to install it on. :)
[SuperSU] igchy:
2.67 works fine for me on nexus6p / stock mmb29q.
[SuperSU] Krunk83:
So no more Android pay with systemless root? Google made a backdoor patch? Doesn't work for me anymore.

Sent from my Nexus 6P
[SuperSU] Alxoom33:
Wrong thread and wrong conclusion.
[SuperSU] Chainfire:
FYI: FlashFire was updated to v0.26, can flash 6.0 OTAs and keep your root - https://plus.google.com/+Chainfire/posts/FjWwBm9vGyj
[SuperSU] cinco312:
Would this work with today's OTA or does it have to be updated?
[SuperSU] chenrp:
flashed on oneplus one and i see battery drain... anyone else?
[SuperSU] Chainfire:
FYI, the latest WIP thread beta, v2.67, has been promoted to 'main' BETA. It's stable enough now, in my opinion. All the info in the WIP should be cleaned up and documented elsewhere in the near future.
[SuperSU] Captain_Throwback:
Is that the one with the fix for the output on embedded custom ROM installs? (I know you changed that after the 2.67 release)
[SuperSU] Chainfire:
I had to double check, but it isn't.
[SuperSU] Nadiro2000:
Hello everyone, I'm new in XDA :)

Sorry for my English, I'm French.

I've a Lenovo Medion x5004 with a stock ROM (Android L 5.0.2)

Build ID: MEDION_X5004_S23A_201_151021

Board ID: msm8939

Chipset Platform: msm8916

I don't know how I can root it. This phone is new (+- 5 month). Any idea?

(I don't know if I am in the right topic. If I'm in the wrong topic, please redirect me :) )
[SuperSU] Paget96:
This version seems to work very nice.
[SuperSU] jollaman999:
Thanks for your nice work!

But could you support various types for ramdisk decompressing?

Like lz4, xz etc...

It seems it only working with gzip compressed ramdisk image.
[SuperSU] antibond:
Hi everyone)) Which files is for lenovo k3 note on that thread

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

I mean files i need for rooting stock android 6 rom.

Thanks.
[SuperSU] Chainfire:
Working on it :)
[SuperSU] Tinchoska:
Hi guys, is someone here get it work on cm 13? Cause the cm root stuff is not good.... and I'm flashing this but it doesn't install, after boot there's no supersu. ... any idea?

Enviado desde mi SM-T700 mediante Tapatalk
[SuperSU] Yeti47:
Yep beta version supplied in post 1 works fine for me on cm13 (sm910c) ☺️
[SuperSU] j1gga84:
Also for 2.65 final?

It has also the mentioned problems..

2.65 gives me bootloops on CM12.1 of [MENTION=1597520]Markox89[/MENTION] on my I9100, I guess ramdisc is not gzip compressed, also other ROMs for I9100 are affected (I guess also official CM13 by LysericAcid)..

2.52 beta is the last SuperSU that works.

regards
[SuperSU] shawek:
2.67.zip works without problems on 5.1 stock GPE rom,with bunch of 'x' module's and root apps.im using it for few days now and all is fine.just to share info.

Sent from my HTC One
[SuperSU] Tinchoska:
I am on Moto x2 and can't get it work I don't know what's going on....

Enviado desde mi SM-T700 mediante Tapatalk
[SuperSU] AndroidGX:
I confirm, SuperSU 2.52 i still the winner for me too :good:

After some tries and experimentations with SuperSU 2.6x, I have many problems with keeping root sometimes after flashing some kernels in LG G4 H815.

Sometimes root disappears for unknown reason, but I guess it's due to that "patching" system about boot.img.

I really prefered the 2.52 old basic system partition flashing (I keep it safely somewhere on my computer) :cowboy:

Cheers'
[SuperSU] gk1984:
Just wanted to share that SuperSU 2.67 won't flash systemless on the Nexus 9 with the latest Feb factory images or the Jan. factory images. Even if I terminal command echo SYSTEMLESS=true... it defaults to the System mode, which doesn't patch the kernel and causes bootloops.
[SuperSU] fhem:
It works on these
[SuperSU] gk1984:
Well, it wasn't working with the straight factory images which is what I prefer to stick with. I'm not sure what's different. 2.67 works fine on my Nexus 6 if I force Systemless via terminal command, but not on the 9.
[SuperSU] fhem:
The odexed rom I linked is 100% stock factory.
[SuperSU] corkiejp:
Tried tonight on Nexus 9 (ElementalX kernel) with v0.27, it failed due to a modified system.

Must have happened when I unfortunately touched the system when trying to restore /su/xbin_bind backup folder I created to it's default name.

I decide to flash the factory images, so it will be march update before I try again.
[SuperSU] Alxoom33:
Did you enter the ADB commands in TWRP to force Systemless Root? If not, that may be your problem.
[SuperSU] Taomyn:
I too always flash the full factory images excluding data to my N9 LTE, and SuperSU 2.67 is still fine after the Feb update.
[SuperSU] Ch3vr0n:
2.67 works fine on my nexus 5 too after using flashfire to update it to mmb29q

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] gk1984:
Yes, I did. Tried a few times. And I know I'm doing it correctly because it works on my Nexus 6 this way.
[SuperSU] amit3880:
The 2.67 zip works find on AICP MM rom (Based on CM 13 ) on my i9300 using TWRP latest.

Thumbs up for good work.
[SuperSU] Ja_som:
Hi, yesterday I rooted my new Nexus 5X with SuperSu v2.67, and as others I have warning on device start ("Your device software cannot be checked for corruption. Please lock the bootloader."), Is there any normal solution, not "flash custom ROM"?

Thank you :)
[SuperSU] Darke5tShad0w:
Not as far as im aware but you don't need to do anything.

Its just a visual indicator with no ill effects.

Whatever you do, Do not relock your bootloader!
[SuperSU] Ja_som:
I don't like it, is ugly :)

Yes, I will not relock it, I was only thinking if is not possible to block that when boot is patched, or is in other part of Android?
[SuperSU] Darke5tShad0w:
Not that I have seen so far but many would be interested if you find it including me lol.

Anyways you might get a better response over at the 5x forums as its related to unlocking the bootloader and not supersu so we are technically off topic here :p.
[SuperSU] Meminette:
nvm -_-
[SuperSU] s-android:
i have m8 dual sim with android 6

i flash 2.52 and 2.66

but no completely root

any solution??
[SuperSU] Tinchoska:
I've clean flashed cm 13 on my Moto x2 after i set everything I've flashed latest beta from open post and got no root access.... Any idea? This happened since first day I've flashed cm two or three days ago...

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] Alxoom33:
A similar notice showed up when first rooting the N6. Usually, flashing a custom kernel or custom Rom gets rid of the ugly Notification.
[SuperSU] Ingenium13:
This is in the bootloader itself and is new on the 6P (and likely 5X), in addition to the kernel warning. It wasn't present with 6.0 on the Nexus 6. So a custom kernel or ROM wouldn't get rid of it.

Sure it would be nice to get rid of, but how often do you really see it? And it's not like it waits for you to acknowledge it or anything. I completely understand why Google put it there.

Sent from my Nexus 6P
[SuperSU] fifo209:
Just wanted to say thanks Chainfire. Using your post I was able to use a Ref 4.4.4 device to push/mod/pull the sepolecy and include it in my boot for an 8996 MSM product.

unfortunately I don't have access to a recovery img yet so I had to push it and grant permissions locally. SuperSU complain it need to update but it actually work fine granting su to apps that call for it. I now have a nice new Marshmallow rooted toy.

You are awesome !
[SuperSU] gd6noob:
Are all SuperSU above 2.52 all systemless root?
[SuperSU] Ch3vr0n:
Yes, unless you force system install through adb

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] srnoth:
http://xdaforums.com/showthread.php?t=3240052

Works like a charm.

Edit: look on the first page for "visible-BHZ10i-n5x.zip".
[SuperSU] Gandalforce:
Finally got 2.67 to install.

Backed up data after Unroot.

Factory Reset.

Went through first time setup

Installed 2.67 via app.

Restored data.

RE-root.

I think that doing the factory reset was not needed. After restoring data. SuperSU was gone. So then I just installed via app, and then updated binary/RE-root via Flashing. Seems confusing but it only took less than hour. The new TWRP is great too.
[SuperSU] Flopik2:
The new version notification when i got already 2.67 is annoying
[SuperSU] Alxoom33:
I never see it on my Nexus 6. I'm sure a custom Rom developer will figure it out.
[SuperSU] Gandalforce:
There's 2.68?
[SuperSU] j1gga84:
yes and because my ROM uses another ramdisk compression than the one SuperSU above 2.52 uses I cannot use builds over 2.52 anymore :(

regards
[SuperSU] Tinchoska:
Guys, I can't use super su over cm1, it just doesn't install.... if I try to update bynaries over the app, it will say that bynaries didn't update and make me reboot, after that I loose cm root..... any idea?

My phone moto x 2 victara

Rom: cm 13 2016/02/04 nightly

Enviado desde mi SM-T700 mediante Tapatalk
[SuperSU] bgx:
I try 2.67 on my Huawei Mate S with the Marshmallow Beta but hat bootloop. What can I do to archive here root on stock MM? Some infos you need chainfire?
[SuperSU] arter97:
[MENTION=631273]Chainfire[/MENTION] Is this intended?

In SuperSU BETA v2.67,

getvar() and

if [ -z "$NOOVERRIDE" ]; then
# read override variables
getvar SYSTEMLESS
getvar PATCHBOOTIMAGE
getvar BOOTIMAGE
getvar STOCKBOOTIMAGE
getvar BINDSYSTEMXBIN
fi

is executed before /data or /system gets mounted.

So if anyone wants to get it overridden, should do it manually on unmounted state(thus rootfs/tmpfs) everytime they enter the recovery.

Is this intended?
[SuperSU] gorilla p:
I've tried 2 different ROMs (First CAF/CM13 based, 2nd AOSP based) and on the last ROM, I started getting a strange issue using SuperSU 2.67 systemless where screen would randomly stay on, but be black, so only backlight was on. I thought maybe it was Greenify, or a lock screen add-on until I removed both and it continued. I even switched ROMs. I didn't notice the screen issue last night, but I also didn't check and I now have the same long SuperSu screen wake lock lasting even longer.
[SuperSU] Chainfire:
Support for other compression algorithms is underway.

No idea really. I've only test one specific CM13 device so far, but that is working fine. Have you tried installing the ZIP through a custom recovery? Updating from CM SU to SuperSU on Marshmallow through the APK is not supported.

How did you install it? TWRP?

Yes, I do need more info, but I'm not sure what info yet. Please try flashing again and post your /tmp/recovery.log from TWRP.

Not really. On modern recoveries, /data is always mounted though, so ZIPs don't have to worry about the encryption. That still leaves the /system case that fails though. Either way, though it does mostly work using /data, it's wrong and I put it on the list to correct this.

This is a very tricky to diagnose issue.

The wakelocks created by SuperSU, unless you are updating the binaries, all timeout after 10 seconds. Android itself is responsible for honoring that timeout.

The only thing I can imagine right now that would cause SuperSU to malfunction like this, is an app causing the su binary to be invoked at least once every 10 seconds. This could potentially trigger the wakelock, and re-trigger it before it times out.

Try using tools like 'ps' in adb shell to trace which apps are calling su. Then it becomes a game of finding the culprit. Note that it's not necessarily the fault of that app's developer, it could be an issue in the su binary trigger by that app.
[SuperSU] Tinchoska:
Yeap, using the zip has no effect.... I've flashed the zip but nothing happened, what do you need so I can help?

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] Chainfire:
The recovery log for starters, /tmp/recovery.log while TWRP is still running. I think its copied to /cache/recovery/last_log by the time you've rebooted into Android, but not sure. The former would be the better choice to send.
[SuperSU] Tinchoska:
I am totally noob when things to do are related to that, reboot I not recovery flash super su, reboot into android copy that file to you so you can see it, am I right?

Enviado desde mi SM-T700 mediante Tapatalk
[SuperSU] followmsi:
Is 2.67 ready for pixel c ?

The bootloader seems to be very special and people had somehow killed fastboot functionality.

Any experiences on pixel c here ? ?