[BETA][2017.10.01] SuperSU v2.82 SR5

[Arsinn]

Is it possible to rooting mm (v6.0) by supersu+custom recovery or not?HTC m8

 

[zerber]

the su binary needs to be updated
can someone help me?!

 

[Pkt_Lnt]

the su binary needs to be updated
can someone help me?!

Here.
http://xdaforums.com/apps/supersu/support-update-failures-t2907365

 

[swallowingled]

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.

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.

 

[Nekromantik]

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.

Yeah it works even though it asks for update,
However I cant stop the notifications. Annoying.

 

[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?

 

[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?

 

[gorilla p]

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?

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

 

[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

 

[osm0sis]

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

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.

 

[Alxoom33]

the su binary needs to be updated
can someone help me?!

Re flash SU 2.67

Sent from my Nexus 6 using Tapatalk

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

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?

Re flash Su! 2.67.

Sent from my Nexus 6 using Tapatalk

 

[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?

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.

 

[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.

 

[bobby janow]

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

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.

 

[discslinger]

Please clarify...

You go into TWRP > Advanced > Terminal Command, then select the current folder (it could be the root folder, it doesn't matter). Then type the command(s) in the text box one by one. You don't need to worry about it since you are already on systemless root.

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!

 

[nathanchance]

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!

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.

 

[discslinger]

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.

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.

 

[wvcadle]

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.

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?

 

[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

regards

 

[osm0sis]

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?

Systemless is still the best way to root Marshmallow, and required for OTA on some devices.