yashsingh1/xdaforums huggingface dataset:
[SuperSU] Jacktheskipper:
Nexus 5:

Came from the modified (cf-auto-root) kernel, flashed stock boot.img in fastboot, then went straight to recovery and flashed supersu 2.30, everything seems perfectly fine up until now, thanks a ton again! :good:
[SuperSU] Zen Arcade:
2.30 working as expected on Note 2 - SGH-I317, 4.4.2 stock - via Philz 6.48.4
[SuperSU] kermitoo:
2.30 is running great on N4 stock with Franco Kernel r214
[SuperSU] bigwillyg:
No issues on stock galaxy s5 active
[SuperSU] Cheater912:
Does this work with encrypted boot now?
[SuperSU] w_bovine:
No boot for you!

Bloody hell. I wanted to go back to the stock kernel and then flash Supersu 2.30. I know I did it correctly, but now my Nexus 5 just sits on the boot up screen with those colored circles spinning around.

Has anyone experienced this, and if so, what was done to correct it without having to do a full install yet again? Woe is me.
[SuperSU] Ja_som:
I had same problem on my N7II when I flashed stock kernel via Flashify. Then I flashed kernel again via fastboot and also system.img and after that I flashed TWRP and 2.27 (now I have 2.30).
[SuperSU] VivaErBetis:
The trick is to flash system.img too [emoji106]
[SuperSU] Blac Caesar:
Beta 2.30 working well here. Nexus 5, RastaPop 5.0.0_r7, Elemental X
[SuperSU] Chaplan:
Can i flash 2.30 over 2.27 with codeblue kernel?
[SuperSU] albert_htc:
If I flash boot.img and system.img will I loose any data / settings ?

Thanks
[SuperSU] danarama:
Why wouldn't you be able to?

Are you flashing a data image too?
[SuperSU] Chaplan:
[MENTION=2872010]rootSU[/MENTION] because i see a lot of users saying they went back to stock kernel before they flashed 2.30. So I thought that maybe it was needed in order for 2.30 to work.
[SuperSU] albert_htc:
I was planning on just flashing the boot.img but a few posts in this thread suggest flashing the system.img as well.

I happy to be advised the best way forward.

Thanks
[SuperSU] nldxda:
I've got two icons for the same app?? Or are they different? There's only one listing in "all apps" .. Both of them are 2.35.. How can I delete the extra app?
[SuperSU] Ja_som:
http://xdaforums.com/showpost.php?p=57048873&postcount=918
[SuperSU] yanner2012:
Uauuu [emoji106]
[SuperSU] sidamos77:
Just downloaded CF Auto-Root for the Nexus 5 and saw that it patched the kernel, although I thought, this is not necessary anymore. Then, after reboot, I started SuperSU and it says v2.20 instead of v2.35!?﻿
[SuperSU] occtec:
Just flash v2.35
[SuperSU] Chainfire:
Spent a few hours getting my old Xperia Z update to 5.1 and tried v2.79 --> v2.80 upgrade on it. Unfortunately I could not replicate the bootloop on it.

As of yet, I have not been able to reproduce v2.80 causing a boot loop. If you've had the bootloop on an Xperia with v2.80 and are willing to help find the cause, please speak up.
[SuperSU] jcmm11:
[MENTION=631273]Chainfire[/MENTION] Nexus5x, Pure Nexus (May release, 7.1.2), Franco kernel

Currently running 2.79 SR3. Downloaded 2.81 zip. Flashed zip via TWRP (3.1.1 I think. Whatever latest is).

Install placed files, apparently successfully. Then went to patch kernel. Found backup version of stock kernel. Patch failed when patching sepolicy.

I then decided to try just restoring the (patched) version of Franco. Phone booted and some startup items that need root appeared to run ok (I think). But afwall failed when applying rules. Then got pop-up that SuperSU had stopped. After that root was lost.

Restored data partition and all is working again.

Recovery and dmesg logs attached.
[SuperSU] DEVILOPS 007:
I got that too but forgot to log it. I have a Screenshot and got this on 2.81 not 2.80.
[SuperSU] NachoB:
I actually didn't check on v2.8.0, but v2.8.1 not working for me. HTC 10, unlocked with S-On, running Viper10 v5.10.0.

I saw a post in the main thread for my device, to uninstall SuperSU, reboot, then install v2.8.1 via Play Store, install binaries, reboot again. This didn't work for me. After Play Store install I get Root undetected.
[SuperSU] Ibuprophen:
@Chainfire... I know that this is reflected from my specific device but, i had previously overlooked it and thought that it might help you out.

The following information is from the TWRP logs following the flashing of the SuperSU v2.81 and i believe that it may be helpful regarding a failure regarding the boot image.

********************************

Stock boot image backup missing

--- Stock restore failed, attempting ramdisk restore

sukernel v2.81 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk] ...

Removing [init.supersu.rc] ...

Removing [sbin/launch_daemonsu.sh] ...

Removing [su] ...

Removing [fstab.qcom] ...

Creating [fstab.qcom] ...

Removing [.subackup/0000_fstab.qcom] ...

Removing [init.environ.rc] ...

Creating [init.environ.rc] ...

Removing [.subackup/0001_init.environ.rc] ...

Removing [init.rc] ...

Creating [init.rc] ...

Removing [.subackup/0002_init.rc] ...

Removing [sepolicy] ...

Creating [sepolicy] ...

Removing [.subackup/0003_sepolicy] ...

Removing [.subackup] ...

Removing [.subackup/index] ...

Saving to [/sutmp/ramdisk] ...

--- Ramdisk backup restored (OTA impossible)

- Checking patch status

sukernel v2.81 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk] ...

----- patch check -----

Loading from cpio:[init.rc] ...

Finding [daemonsu]

-!Found

Finding [SuperSU:PATCH]

-!Found

Result: not patched

rm: can't remove '/sutmp/ramdisk.original': No such file or directory

*********************************

I hope that this too will help you out in the other issues reported.

Though, i had outlined a specific portion, I've also attached the TWRP Recovery and Dmseg Logs in case you require the whole picture.

Please let me know if you require anything further.

Thank You!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Chainfire:
SuperSU v2.82 SR1 is released now, this entire post is obsolete

As this post will probably be updated with new files, please include the exact filename of the ZIP flashed in your reports.

SuperSU-v2.82-CCMT-GooglePlay

Both the flashable ZIP as well as the APK are attached.

This is in staged roll-out right now on Google Play.

It solves the biggest root loss issue, removes the feedback screen (and thus removes the requirements for the controversial permissions), and fixes the su.d / bind bug.

Xperia users should note that this version may still boot-loop, and it is advised to use v2.79 (and disable auto-update) until we find the cause

SuperSU-v2.82-20170528234214-TEST-1

A test version of v2.82 aiming to solve the Xperia bootloop issue (and some other issues)

Do not use unless you know what you're doing, have backups, etc.

Older test verions:

UPDATE-SuperSU-v2.80-20170524085154.zip

Original v2.80 compiled by me instead of CCMT (fixes one of the major root loss issues)

SuperSU-v2.80-20170525215916-bindfix.zip

Test version that (maybe) fixes mount namespace separation / su.d / bind mounts at boot / AdAway

UPDATE-SuperSU-v2.82-20170526223454

Above bindfix version, but version code modified to v2.82 so it doesn't auto-update to v2.81 from Google Play. Please note that this version force closes for some users, that problem has been fixed in the CCMT/GooglePlay version.
[SuperSU] Chainfire:
Please see my post above this one.

All patches will be based on v2.80, not v2.81.
[SuperSU] jcmm11:
I haven't tried 2.80, but can if it will help. For now I'll just wait further developments.
[SuperSU] wilsonhlacerda:
First of all: thanks for all your previous and current work. Hope you solve problem soon.

BUT PLEASE do consider to put v2.79 back in Play Store. I got that you can not the expected way, but sure you can put it as a new "fake" 2.82 or so. Just put it anyway.

I know this is not a clean solution, but it is THE solution now. This is very important to stop the spread of the buggy v2. 8x. Think about the tons of mobiles that have not updated till now... They will all within next hours, days. An true 2.79 with a fake 2.82 version will avoid problems to them, beside not be a problem to the ones that already moved to bug 2.8x
[SuperSU] lukjod:
How to revert back to sr3 on htc 10? Tried via twrp and all looks ok after install but dont have su icon after restart in programs and any root needed app is not working. Really **** situation, what else can i do to have root again.
[SuperSU] DEVILOPS 007:
You could just download 2.79 zip from chainfires website and flash it in recovery.
[SuperSU] DEVILOPS 007:
2.81 didn't work for me but I just tried this one you posted here and it worked fine.
[SuperSU] Shahbaz_23:
+Seconded
[SuperSU] Chezbel:
Exactly the same here on HTC 10
[SuperSU] wilsonhlacerda:
Read again what I wrote.

By the way, I do not have any problem just because for critical apps like su I leave automatic updates off and always check how rollout is going and/or I guarantee I have nandroid backup before taking the risk. :)
[SuperSU] Chainfire:
You're preaching to the choir here.

Please don't start this debate _again_. I am trying to solve the actual issues here, not debate things I cannot currently change.
[SuperSU] Chainfire:
Try:

adb uninstall eu.chainfire.supersu

Unintuitively, this may bring back SuperSU after a version downgrade.
[SuperSU] osm0sis:
In case it hasn't already been read by anyone here, it's worth reading Chainfire's status update on the issues from the stable thread: https://xdaforums.com/showpost.php?p=72428986&postcount=1645
[SuperSU] wetxxx:
Only supersu 2.79 without sr3 works on on HTC 10 S-ON. Other version can't give me a root. Chainfire I will wait to fix problem and cross my fingers for You. Cheers mate :)

Wysłane z mojego HTC 10 przy użyciu Tapatalka
[SuperSU] wilsonhlacerda:
And I thank you! I even suggest you to focus on it instead of reading comments here just like you did on the stable thread, maybe only every hour or so. That probably will let it easier for you and calm down the other anxious people.

But meanwhile people all around the world is updating their SU on play store to v2.81 now and bugging their mobile, every minute. An v2.79 as a fake 2.82 will stop that. But sure it is your decision to do this one time temporary solution or not.
[SuperSU] jcmm11:
UPDATE-SuperSU-v2.80-20170524085154.zip

This successfully gave me root, but bind mounts don't appear to take effect. They show as mounted when you issue a mount command, but adaway is disabled and none of the font files that I've bind mounted are taking effect. (This all worked fine with 2.79 SR3)

Nexus 5x, Pure Nexus 7.1.2, Franco kernel
[SuperSU] Chezbel:
Thanks, I can confirm that version works for me to on HTC 10, sr3 does not.
[SuperSU] osm0sis:
The current workaround is to disable mount name space separation in SuperSU settings and reboot. Read the post I linked above.

This resolved both of the issues I was experiencing in my device setups.
[SuperSU] lukjod:
Android 7 based rom?
[SuperSU] NachoB:
Installed via TWRP v3.1.0-1. No SuperSU in Apps and root apps hang at requesting permission (only tried TiBU). HTC 10, unlocked, S-On, Viper10 v5.10.0.

File: UPDATE-SuperSU-vQ12.80-20170524085154.zip

https://pastebin.com/k4rNndW2
[SuperSU] Chezbel:
Yes, Android 7 (Nougat) firmware and LeeDroid ROM, s-off
[SuperSU] Flo_webRadio:
On Samsung Galaxy S6 Edge (SM-G928F) works perfect.

Inviato dal mio SM-G928F utilizzando Tapatalk
[SuperSU] lukjod:
thanks, it worked, after that I've installed sr3 by twrp recovery.
[SuperSU] jcmm11:
New test file, confirming that's not fixed yet. My solution was to reflash 2.79 SR 3 ? I'm perfectly happy there. Now to get out of here and stop cluttering the thread unless I have something relevant.

But glad to know about alternate workaround, if needed. Either the linked post was expanded, or I somehow stopped reading halfway through the first time around.
[SuperSU] Chainfire:
Which one works? v2.79 or v2.80 ?
[SuperSU] dr.ketan:
UPDATE-SuperSU-v2.80-20170524085154.zip

Worked on N920I with Nougat (S8 port) + TWRP 3.0

Also random mount is fixed as well

PS: 2.81 was not worked (lost root)

[MENTION=631273]Chainfire[/MENTION] I am on hangout for half an hour in case need to test anything
[SuperSU] p407e2:
Everything works with 2.80 on my Nexus 6, stock 7.1.1
[SuperSU] Chainfire:
In the test releases post ( https://xdaforums.com/showpost.php?p=72429329&postcount=9810 ) I added a 'bindfix' ZIP. That version may fix the bind mounts / AdAway / su.d issue with 'mount namespace separation' turned ON.

Please test and let me know if it works for you. In case anyone cares, it's actually O-compatibility-code that broke this :)

I sure wish an Xperia boot-looper would come to assist...
[SuperSU] Ibuprophen:
Unfortunately, [MENTION=631273]Chainfire[/MENTION], the UPDATE-SuperSU-v2.80 reflected the same results as i had reported on the following 2 posts.

https://xdaforums.com/showpost.php?p=72428342&postcount=1627

https://xdaforums.com/showpost.php?p=72429303&postcount=9809

I had attached Screenshots as well as the TWRP and Logcat files for you to review.

Please let me know if you require any further information.

Thank You!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock
[SuperSU] dr.ketan:
I am not using adaway so not aware of exact issue but I have tested by downloading adaway and seems working fine.

I have flashed only UPDATE-SuperSU-v2.80-20170524085154.zip and NOT bindfix

Mount Namespace separation is On
[SuperSU] dr.ketan:
Missed to add ss
[SuperSU] osm0sis:
bindfix appears to do the trick on my Nexus 7! The boot animation is Nexus again. :)

Edit: Didn't do the trick on my Nexus 5 that has a xbin_bind mount set up with the Root Switch custom_ramdisk_patch.sh and app.

Symptom is Root Switch can't disable root. Disabling mount name space continues to work here though.
[SuperSU] Ibuprophen:
My deepest apologies [MENTION=631273]Chainfire[/MENTION]...

The post with your BindFix was posted shortly before my post and had not tried it yet.

I'll report my findings as soon as I can.

Thank You!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Chainfire:
[MENTION=7487527]Ps24u[/MENTION] [MENTION=393455]tobbbie[/MENTION] [MENTION=644756]xalaros10[/MENTION] [MENTION=4888288]junk031[/MENTION] [MENTION=488914]Rebel2k[/MENTION]

It would be great if you guys could help me figure out what the exact cause of the issues is for your Xperias.

Is any of you available for testing and have a custom recovery available?

Even if 2.81 works for you, 2.82/2.83 will not unless we find the cause of the bootloop. I have an Xperia Z available but unfortunately it doesn't have the same issue.

For starters:

(1) does v2.81 work for you?

(2) does v2.80-bindfix ( https://xdaforums.com/showpost.php?p=72429329&postcount=9810 ) work for you?
[SuperSU] Chainfire:
Your ANR/crash issue will not be fixed by this.
[SuperSU] Wolfcity:
Blindfix update fixed the adaway issue which was the only issue for me on 2.80.
[SuperSU] Chainfire:
Hmm, all my manual tests succeed. Weird.

Can you try this? Open two adb shell's simultaneously.

Shell 1:

mount

Verify /system/xbin is listed as a mount

Shell 2:

su --mount-master
umount -l /system/xbin

Shell 1:

mount

Verify /system/xbin disappeared
[SuperSU] jcmm11:
[MENTION=631273]Chainfire[/MENTION] bindfix appears to have worked to fix bind issues. However I got "SuperSU has stopped" pop-up somewhere along the line. Did NOT lose root.

Catlog attached

(And another "SuperSU has stopped" just showed up)
[SuperSU] quincho54:
I'm on Nemesis refined v.3.6.1 on Note 4 SM N910 H

Deinstalled Super SU v.2.81 from play store. ( but had no any problem) Installed your 2.80. Works well on the Note 4.
[SuperSU] martyfender:
Both 2.80 and 2.81 have seemed to work fine on my Nextbook Ares 8, Intel Bay Trail x86, Android 5.1.1, when flashed through twrp in the default for the device, system mode.

For some time I have been using an app: apps2sd to move apps to a second external sd card, ext4 partition. The author of the app recommends to disable mount name space separation in supersu for the app to function properly. It does use bind mount points, I believe.

My question: Would your bind fix potentially allow this app to work properly with mount namespace separation enabled in supersu? Or would this best be asked the author of said app, [MENTION=6726362]vickybonick[/MENTION] ? I could flash and test, if you think this might be a potential fix

Thanks
[SuperSU] ousasma:
On aptoide there also v2.81

View attachment 4161428
[SuperSU] Ch3vr0n:
Thats because those things grab every version out there, even if there's issues with it. They don't care
[SuperSU] Chainfire:
It's only a work-around, but I think you can get rid of those crashes by uninstall the SuperSU APK, rebooting, then re-installing it.
[SuperSU] Chainfire:
Just try it. If apps2sd isn't properly built to cope with mount namespace separation, then it will not work properly. I don't have a definitive answer for you, and neither will the app's author. Trying it seems like the quickest way to go.
[SuperSU] martyfender:
I flashed the bind fix zip and the bind mount point in app2sd appear to be working correctly as shown by a toast message at boot and in the app bind results menu. I used the authors advanced mount script option. I may test his su.d option again though. I has used the su.d method in the past, but after a few reboots the app I moved to the external sd card would only be partially linked. I will have to test for a while to confirm that the app continues to be linked, though.
[SuperSU] Rebel2k:
Hi [MENTION=631273]Chainfire[/MENTION]. I would have helped with pleasure of course, but as I mentioned earlier, the affected Xperia Z1 is the one of my father leaving hundreds of kilometers away. I had to debug that remotely, so I cannot really play and try things anymore. Hope one of the other Xperia owners would be able to do the requested tests and we can all figure out what the problem is!
[SuperSU] ithehappy:
I lost root on my Pixel XL after downloading the version from Play, that's normal? Other users reported same.
[SuperSU] Ch3vr0n:
Read the stable thread last couple pages or reflash SR3 in the mean time
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], I just wanted wanted to report the results regarding the SuperSU v2.80 BindFix.

Still the same, unusual, results as i had reported within the following 3 posts.

https://xdaforums.com/showpost.php?p=72428342&postcount=1627

https://xdaforums.com/showpost.php?p=72429303&postcount=9809

https://xdaforums.com/showpost.php?p=72430261&postcount=9839

I also attached additional Logs/Screenshots as well as the TWRP and Logcat files for you to review.

It, seems to me that this issue is still a result of permissions that are reflected within the Logcat file (located within the attached zip archive) as it also shows this information upon the initial launching of SuperSU.

Please let me know if you require any further information.

Thank You!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] shaggyskunk:
Seems some have trouble reading the post above theirs - Reading the last few pages seems a bit optimistic - lol
[SuperSU] koekoek91:
[MENTION=631273]Chainfire[/MENTION]

Im on a Xperia XZ F8331.

I don't have any boot loop issues with v2.81.

My process:

-Flashed SuperSU 2.79 SR3,

- Rebooted and updated the app from the playstore bringing me to SuperSU v2.81.

- Opened SuperSU and it asked to update binaries, so I clicked okay and installation was a success.

- Then rebooted again and all is fine.

I would be happy to help you test for Xperia but I assume because everything works fine for me I can't be of much help?

In case I can help, just let me know.. have a few days off so I got some time :cool:
[SuperSU] osm0sis:
Yes that​ does work. Weird indeed! :confused:

I'm on the go with my Nexus 5 right now so I did that with 2 Terminal Emulator app instances - hopefully that's comparable.

Here's the custom_ramdisk_patch.sh from Root Switch if it helps you reproduce the issue, since it all definitely still works on SuperSU 2.79 so there must be a regression somewhere:

#!/system/bin/sh

SYSTEMLIB=/system/lib
if [ -d /system/lib64 ]; then
SYSTEMLIB=/system/lib64
fi

# extract files
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-extract $1 init.environ.rc /sutmp/init.environ.rc
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-extract $1 sbin/launch_daemonsu.sh /sutmp/launch_daemonsu.sh

# patch init.environ.rc
sed '/export PATH \/su\/bin/s/^/#/g' -i /sutmp/init.environ.rc

# patch launch_daemonsu.sh
sed '3iexport PATH=/su/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/su/xbin:/system/xbin' -i /sutmp/launch_daemonsu.sh

# push back files
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add $1 $1 750 init.environ.rc /sutmp/init.environ.rc
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add $1 $1 750 sbin/launch_daemonsu.sh /sutmp/launch_daemonsu.sh

# link supolicy to /su/xbin_bind
ln -s /su/bin/supolicy /su/xbin_bind/supolicy

exit 0suhidr

Root Switch v1.3.3.2 from the official thread: https://www.asus.com/zentalk/tw/thread-173542-1-1.html

Just to reiterate the symptom is root won't disable using the Root Switch in-app toggle without mount name space separation disabled, even on SuperSU v2.80-bindfix.

P.S. SafetyNet passes with root disabled if that gives you any hints for a suhide update. ;)
[SuperSU] shaggyskunk:
If you use Google - Gapps - The Internet - You're likely participating with Analytics.....

https://en.m.wikipedia.org/wiki/Google_Analytics
[SuperSU] Chezbel:
Sorry for the late reply. On htc 10 with android 7 firmware and s-off, I needed to use 2.79 to get root back.

2.79 sr3 and later was not able to get root back.
[SuperSU] nitramus:
Exact same thing on my 10 running latest leedroid and latest us unlocked firmware 2.48.617.1.

I tried 2.8 this morning and was working fine but 2.81 gave root undetected.
[SuperSU] Wolfcity:
Just forget 2.81 for the moment. [MENTION=631273]Chainfire[/MENTION] posted these versions for testing purposes:
[SuperSU] jcmm11:
This seems to have worked. Thanks.
[SuperSU] Johny Cipeli:
Devs, I don't know if it will be useful, but here is a link with the recovery log which shows 2.80(success) and 2.81 (no success) flash. http://s000.tinyupload.com/?file_id=85075292743930233667
[SuperSU] Ps24u:
Chainfire, I'm one of the Xperia Z1C dudes who had bootloop with 2.80.

I then reinstalled an old TWRP backup that had 2.79 installed, and proceeded to install 2.81 from Play.

It installed binary and rebooted just fine, and all seems to be working ok.

I now made a new backup with 2.81 so I can help with testing. Just let me know what you want me to test.

I'm also curious if you can make any sense of this:

--

Here on Z1C Busybox says I have 1.22.1 installed to /sbin/

It's prompting me to install 1.26.2 to /system/xbin

--

Should I update as Busybox wants me to? Does this have any impact on SuperSU? I'm a bit confused about which binary is actually needed and/or in use by SuperSU.
[SuperSU] manpildo:
Mistakes happen, so far all updates of SuperSU have been seamless and working, so you are allowed an error once in a while (I didn't know you were still working on this fyi, I thought the new maintainers were completely responsible for stable Play Store updates).

If this helps you anyhow, then my update from 2.79 SR3 to 2.80 through the Play Store was without problems. 2.81 through Play broke it.

I am using Nexus 5X with Pure Nexus 7.1.2.
[SuperSU] wetxxx:
I confirm! I also have HTC 10 Android 7.0 Stock rom, but I haven't S-OFF. Only 2.79 version works for me. Its strange but before install 2.81 and than 2.80 I use to SS 2.79 SR3. Can't You explain what's happened?

Wysłane z mojego HTC 10 przy użyciu Tapatalka