yashsingh1/xdaforums huggingface dataset:
[SuperSU] zear4fear:
i'm using Huawei P8 ROM GRA-L09C432B321(Android 6.0) and came from B170 (Android 5) with regular root, then made a full update to B200 (also Android 5) and OTA flash to B321.

I've got the SuperSU from this post (beta 2.71 from 30.03.16) and TWRP 2.8.7.0 by jemmini.

I have no vendor or oem folder to flash.

Attached the logcat.

I've also tried to use the compatibility SYSTEMXBIN command.
[SuperSU] grep_i:
After flashing the .zip did you get the question to flash Supersu again or not ?

Also can you verify if you have the Supersu app available on your phone and if so if it shows the exact same version you flashed through custom recovery ?

Do you know if you cleared the regular root before using this Supersu ?

First inspection of logcat:

At first glance it seems that your device had problems with dex2oat some apps including Supersu.

I do not know if it is easy to reflash the latest rom on your device.

It is quite possible that something went wrong during updating your rom.

Reflashing latest rom could solve the problem but it is also possible that you have to do it a couple of times as it is quite possible that the problem occurs again.

Also I am curious is that the only problem you are having your log looks like you should be having more problems with other apps too.
[SuperSU] zear4fear:
THX for first inspection!

I used TWRP in read only mode and didn't get the prompt to install SuperSU again.

The installed version (2.71) is the same in android as in flashed zip.

Before flashing over the rooted system I think I unrooted with SuperSU.

What you said about the log, I've got problems with all root apps as they don't get permissions. In Titanium or in LINK2SD it lasts longer as they trying a long time to get access.

I didn't observed other problems.

I also flashed a stock system and did a nandroid restore of data. Same problem.
[SuperSU] shoey63:
Ok, here are the new logsView attachment 3743945

I took them with Syslog immediately after a random reboot as soon as SuperSU granted permission.
[SuperSU] zear4fear:
Strange thing is if I deinstall SuperSU I've got full root rights but with SuperSU the requests don't come through.
[SuperSU] Fif_:
You may have the SuperSU /su/bin/su that gets called when SuperSU is installed while you also have /system/xbin/su.

Once SuperSU is removed, you fall back to the /system version.

It's probably not a good idea to have both installed...
[SuperSU] Venomous Viper 119:
I have a Nexus 5 running stock Marshmallow MOB30H. Boot loader is unlocked and I have TWRP v3.0.2 running. I flash the SuperSU v2.71.zip in TWRP but I'm not getting root access. Same thing happened when I was running MOB30D.

I have tried rooting with CF-Auto Root and Wugfresh's Nexus Root Toolkit as well. But even they didn't work. Can anyone please tell me how to root this stock build?
[SuperSU] Fif_:
Please provide the recovery log file from a SuperSU flash session. Or a screen capture.

What happens when you launch the SuperSU app?
[SuperSU] zear4fear:
Ah, and how could I unroot the system root after removing SuperSU?
[SuperSU] Venomous Viper 119:
Nothing is happening. But ES file explorer says root failed. Is it only issue with ES that root of not working with the latest build?
[SuperSU] Fif_:
Hard to tell without knowing which brand of su is there, sorry.

---------- Post added at 10:05 AM ---------- Previous post was at 10:01 AM ----------

ES has separate issues.

You may not have root with ES while root is working.

Can you be clearer in your descriptions ("Nothing is happening" when you do what?) and provide the SuperSu install session recovery log file?
[SuperSU] Pkt_Lnt:
Try Chainfire's fix for compatibility mode. It has been posted many times and you can find it in the last few pages.
[SuperSU] zear4fear:
What do you mean, with "brand of su"? Sorry didn't get it.
[SuperSU] egingell:
Chainfire, CM, KingRoot, etc.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
This answers the question from post #5978.

You did not clear your included regular root first.

Now we still have to find out which root is your regular root and remove that if possible.
[SuperSU] sohail667:
is it flash on 5.1.1 lollypop
[SuperSU] Chainfire:
Sorry, still nothing.
[SuperSU] Venomous Viper 119:
It's the issue of ES File Explorer only. Root works fine with other apps.
[SuperSU] grep_i:
Try the suggestion to use compatibility mode or just report to the developer or developers of ES file explorer or start using another file explorer like total commander.
[SuperSU] arbit12:
It's app specific. For me it was only Secure Settings which had problems. Worked after fine after the compatibility fix.

Note Edge N915G

Stock rooted 6.0.1

Wanam xposed v84
[SuperSU] MikeRL100:
Oh boy more fun! I shall call you Master from now on. Or better yet - time for a new formal title. For the great application and the extra stuff you do. Your posts and insight on XDA and Google Plus have helped many developers that write root apps. Decide on a formal title.
[SuperSU] sndrdg:
2.08 - NOT WORKING on Sprint Samsung SGS4 (jfltespr) - Stock 4.3 (Apps and Logs tabs - spinning - Displays nothing).

2.08 - Working fine on Google Nexus 7 {2013} FLO - Stock 4.4.3
[SuperSU] damca:
2.08 - Working fine on Galaxy NOTE 3 - X-NOTE build 20.0 (N9005 NG1)
[SuperSU] giveme13s:
2.08 works fine here on Sony Honami Z1 with DirtyUnicorns ver 7.9
[SuperSU] remicks:
2.08 says invalid zip file when I try to flash via RTBP, downloaded via Chrome, Dolphin & ES downloader with same result. Odd.

Edit: Got it now.

Confirmed working on HTC M8 running GPE 4.4.4
[SuperSU] Musashi74:
2.08 works on i9100 without issues.

i9100 1ROM:Spirit 4.4.4 v1.3

powered by Dorimanx-V10.43v119
[SuperSU] scoobyjenkins:
2.08 working fine on both my devices (devices & roms in web view signature) though have yet to update and see if the update binary prompt is gone!

Tapatalked that shiznit.
[SuperSU] edzamber:
2.08 works great on Pyrana v46 based GNG8 stock (i9505)

Posté via Pyrana v44 by Alan-B

http://xdaforums.com/showthread.php?p=53646684
[SuperSU] Sandivisi:
2.08 work fine on moto g . great!
[SuperSU] Frank Westlake:
2.08 OK on:

- Note SGH-I717 Android 4.0.3

- Note 3 SM-N900T Android 4.3

- Note 3 SM-N900V Android 4.3

Frank
[SuperSU] nexusmaniac:
2.08 works fine on Nexus 5 - LPV81C
[SuperSU] chikimonke:
2.08 working fine on 1+1
[SuperSU] shawnshawn90:
Are u able to post the beta on an installer apk form? I don't have a custom recovery set up yet.
[SuperSU] jurben:
Open the zip. You will find the apk there: common/Superuser.apk
[SuperSU] tangcla:
[MENTION=631273]Chainfire[/MENTION] have you thought about having beta versions of SuperSU available on the Play Store with opt-in?

---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------

Also, would you be able to have an option to remove the Knox detected pop up message on Samsung devices? On the TabPro, if Knox is removed, the tablet starts having random reboots.
[SuperSU] Pkt_Lnt:
Replied to your question in post #13.

http://xdaforums.com/showpost.php?p=55333555&postcount=13
[SuperSU] Megaflop666:
2.08 Working perfectly on tmo note 3, tmo s5, and nexus 7 flo.
[SuperSU] Chinaboy5216:
Working fine on the Note 3, flashed through recovery
[SuperSU] cbeckstein:
2.08 not working on Stock SGS4 with Android 4.2.2 (XXUBMGA). Apps do not detect root and supersu tells me it is missing the binary.

Back to 2.06
[SuperSU] JaCh0o:
Hello,

i bought Pro version to donate you in this case but don't work: 2.08 beta or 2.02 or Pro licence. Can I ask you for verify this? I've made a reply on G+ and here post #6534.
[SuperSU] Streetwalker:
Hmmm I'm having a weird issue here. I just flashed a new build I just made on my Nexus 4 (5.0.0_r6) and SuperSU stopped working. I have SELinux fully disabled in the kernel and a fixed fstab to allow booting. It did work on my previous build and all I changed is that I've added cm's busybox (12.0 branch). What happens is that apps don't detect root and SuperSU says my su binary isn't present while it actually is (as shown by su --help). I tried both 2.19 (which worked on my previous build) and 2.23.

If you have any pointers/need anything to help me debug that it would be great.

Thanks in advance.

Edit :

How I disabled SELinux : https://github.com/WalrusMod/kernel_msm/commit/fd95cba8a30a34f79170439f7a6afd8f93cf5f4a

Related fstab change : https://github.com/WalrusMod/device_lge_mako/commit/46464462008f02866b4724250bef3c5c164d6333

Edit 2 : Just kicked off a clean build, we'll see how it goes.
[SuperSU] mcnamaragio:
Notifications Off also works after this update of SuperSU.
[SuperSU] ThePhoneGeek:
V2.23 works great on Nvidia Shield Tablet after this mornings update to 5.0!

Many thanks!

MG
[SuperSU] StupidIdea:
I'm trying to update my apps to work with Lollipop but SeLinux contexts differ on on different Nexus devices. I need to start app_process with jar from my app's /files folder in classpath. On Nexus5 and Nexus7 it works with system_app or platform_app context but on N4 and N9 none of the contexts can load the jar. I tried 2.20 and 2.23 with same result. Everything works if I switch selinux to permissive.

Question: are there any plans to have some permissive context that would have same rights on all devices (we discussed something similar some time ago)?

Edit: You can try it from here (2.9-beta3): http://xdaforums.com/showthread.php?t=2266428
[SuperSU] swallowingled:
Flashing the zip file fails on Nexus 10 using TWRP. I had to extract the apk to install. Secure Settings still has issues with executing reboot options unless SELinux is set to permissive, but I think this is a Secure Settings issue.
[SuperSU] norti:
Yes, without problems.
[SuperSU] Chainfire:
I'm not sure what I should be seeing here. The version I've downloaded from you seems to use platform_app (I think you should use system_app anyway), I see errors popup in SuperSU's logging (you set LD_LIBRARY_PATH wrongly for 64-bit systems). I don't even see it trying to load any jar. I'll need at least the exact command you use... switching the system to permissive doesn't seem to make any difference for me. As in, your app didn't really work before, and it doesn't when I switch to permissive. The softkeys disappear for a second or two, then return.
[SuperSU] skywayskase:
This has fixed a problem I was having with Helium. It was the only Root-required app I had that wasn't working after upgrading to Lollipop, and now I don't have any more issues. REJOICE!
[SuperSU] StupidIdea:
Removed.
[SuperSU] Tinchoska:
[MENTION=631273]Chainfire[/MENTION] I am having this problem, I've reboot my phone and show up this notification

Click on it but no actualization.... Any idea?
[SuperSU] HassanM:
Go into the app... Click on SuperSU icon.... Once u do that, it will ask u to update the binary... Click on Normal.... Once its complete it will prompt u to reboot....

Reboot!!!!

Done....
[SuperSU] Tinchoska:
Done and nothing... Just don't do anything
[SuperSU] Chainfire:
Did you have the same problem on v2.22 and older, or just v2.23 ? Have you tried flashing the ZIP in TWRP, or only installing the APK ?

Please provide a logcat.
[SuperSU] Tinchoska:
Wait, I think I found the problem... I think it was ultimate navbar dynamic.... Or whatever it write LOL. on beta 22 that make me have a sod.... I am on beta 2.23.... Will report back in a few minutes
[SuperSU] buffal0b1ll:
Fixed Secure Settings app for me on Nexus 9. Thanks again Chainfire :)
[SuperSU] GroteBozewolf:
Hi [MENTION=631273]Chainfire[/MENTION] I really appreciate all your efforts in providing root on our Android devices.

I try to read most of the posts here and see that many people ask the same questions regarding lollipop, root, TWRP and encryption.

Perhaps that somebody can summarise what can and can't be done? Like: Can we encrypt and root (soft brick risk) ? And will CFAR wipe your data of you are encrypted? And why does TWRP not work when encrypted.

I know they are not SuperSu related, but we all need these tools to root.
[SuperSU] andrewjgreen:
Really thankful for this
[SuperSU] WeakControl:
Weak Control working with v2.23 beta

Weak Control was not working with previous version

Now working without change with v.2.23 beta

Nexus 5 Lollipop works fine with the beta as well.﻿
[SuperSU] adrman:
Just flashed 2.23 over 2.22 and SuperSU pro disappeared. I still have root and the Play Store days it's still installed. :confused:
[SuperSU] zear4fear:
Thanks for your support!

I did a complete new install and now it works.
[SuperSU] stanonna:
Some time ago I used the command "echo "BINDSYSTEMXBIN=true" >> /data/.supersu" to enable compatibility.

Now I would like to disable compatibility, wich command must I use ?
[SuperSU] fmc000:
If it's the only line present I think you can just delete the file (it doesn't exist on my phone and SuperSU work just fine). Otherwise you have to edit the file with a root-capable file manager and remove the line.

I suspect you will have to reflash ROM and SuperSU after.
[SuperSU] Chainfire:
v2.72 BETA released - RELEASE NOTES
[SuperSU] Dead-neM:
Well for the force encrypt part, i don't understand

If your device is encrypted. You flash SuperSU it will not decrypt it so were was the problem. HTC 10 is the only reason for that?

Also if you're unencrypted you flash SuperSU v2.72 that's mean now it will force encryption and you'll loose your data cause it will messed up? Wow that's a big warning for people that don't flash kernel with force encrypt disable right after SuperSU

That's mean also that custom kernel have to be flashed after SuperSU now?
[SuperSU] osm0sis:
Custom kernels should always have been flashed after SuperSU so that it's backing up the ROM's default boot.img (necessary for Deltas/OTAs to apply correctly).
[SuperSU] Ja_som:
Just flashed 2.72 on my N5X with Android N DP2 and everything looks OK (I don't see any issues) :good:

EDIT:

same on Nexus 7 II with Android 6.0.1 ;) :good:
[SuperSU] Chainfire:
As I posted on G+:
[SuperSU] cyberon:
About the encryption part, some devices like the one I'm currently using (Nexus 6) suffer from some lag while encrypted, and personally I'm willing to take the risk running unencrypted. Also, every user who chooses to root and flash SuperSU is a advanced user, immo things should remain as they are and not confuse existing users.
[SuperSU] zamula:
Totally agree, and the chances of accidentally becoming encrypted would be much greater than losing your existing encryption. Please keep the current behavior.
[SuperSU] bobby janow:
So I did that, flashed a custom kernel and now should I start the process all over again with 2.72 or just let it go?
[SuperSU] Ningyou Higeki:
Systemless SuperSU can't work in Sony Xperia stock 6.0.1 firmwares, and I will lose root if I flash your original versions on my Sony Xperia Z2 with stock 6.0.1. Other users in the forum told me I had to flash modded SuperSU zip or to disable systemless mode before updating with an original one. Could you force SuperSU to use system mode in Sony Xperia stock 6.0.1 firmwares? Thx in advance.
[SuperSU] Iceberger:
Seems like it was mine own problem and not related to this thread
[SuperSU] skyhirules:
Just a small feature request: if no logging is selected in the settings, then the log tab should not appear at all, instead of just an empty tab.

Thanks in advance.

Sent from my Xperia Z1 Compact with XDA app.
[SuperSU] jesssiii:
I vote for the forceencrypt flag to be enabled by default, and the more experienced, minority, users can choose to change it to run decrypted. I think it would save you some headaches, for one. I'm decrypted and wouldn't mind having to choose that option in the future.
[SuperSU] sswagonman:
Can anyone share the zip for update-UNsu please

Edge of insanity
[SuperSU] osm0sis:
I use FlashFire, so it's dead easy. I chose the new SuperSU zip, have it automatically restore stock boot.img (and recovery.img) and preserve my custom recovery, then I have it flash the latest franco.Kernel AK2 zip. :)

I'm not sure how that worked considering unSU is only designed to uninstall old, system-based SuperSU installations.. :confused:

Some type of log would probably be helpful.

That said, unSU is still available (and over 30,000 downloads now, wow!), linked in my Odds and Ends thread, but please read the link in its description and be aware of the use-case for which it was intended. :D:good:

I've also got a newer zip script tool for use with systemless SuperSU, which toggles the mounting of su.img in recovery each time you flash it so you can change files in the /su filesystem via adb shell, AROMA Filemanager UI/Console or TWRP's included file manager/terminal. Could be useful for people trying to sort out hung/looped boots from su.d or /su/bin additions. It's called SUmount and can be found in my thread as well. ;):cowboy:
[SuperSU] WesTD:
i've flashed on General Mobile 4G Android One 2nd Generation Android N Preview 2 but didn't rooted.
[SuperSU] bobby janow:
Cut your reply for clarity. So I just signed up for Flashfire and I await the d/l from PS. My scenario is that I clean flashed Pure Nexus, SuperSU systemless, and then a custom kernel. So if I wanted to install 2.72 now with Flashfire I'm assuming that it will ask if I want to restore the boot.img from backup. (Not sure haven't used it yet) That boot.img will be from PN? Then it will install 2.72 and re-backup the boot.img and then I can custom kernel again? If I need to search first I'll be more than happy to, just found the Flashfire thread. TIA
[SuperSU] osm0sis:
Exactly right, and FlashFire lets you chain the actions together so you just add the flash of SuperSU 2.72 zip as the first action, (disable EverRoot SuperSU since it's SuperSU 2.71 until Chainfire updates it) and put the custom kernel zip flash action in the list after all the SuperSU stuff, then it'll happen all in one go. :good:
[SuperSU] followmsi:
[BETA][2016.05.10] SuperSU v2.72

Now tested on Pixel C .. works like a charm !

Supersu.zip is perfectly modifying the ramdisk and re-signing the kernel to chromeos.

Thanks again !
[SuperSU] bobby janow:
Perfect. Done and done. Now on the Pro version. ;) (not the freeloader, lol)
[SuperSU] HorstiG:
I have version 2.72 flashed, but is displayed Version 2.71

LG G4 H815 Stock mod Marshmallow

View attachment 3746854 View attachment 3746855
[SuperSU] Gandalforce:
Mine is running fine on systemless
[SuperSU] fmc000:
Something wrong on your side...

Inviato dal mio A0001 utilizzando Tapatalk
[SuperSU] Gandalforce:
How to upgrade

I'm sure almost everyone here knows how to upgrade SuperSU, without losing SuperSU settings, apps etc..

I believe this is the easiest way:

Download and install .apk from either following SupersU on Pushbullet, or finding the .apk from XDA/Chainfire's site.

Download the .zip from XDA thread (1st post) when Chainfire obviously uploads and modifies thread.

Place .zip in SD or internal storage

ADB reboot recovery etc...

​

Get into custom recovery

Flash

Done

Again, just a quick reply, to help you peeps out
[SuperSU] ** A - R **:
Mostly, this will fix the Issue.

[MENTION=631273]Chainfire[/MENTION] Thanks.
[SuperSU] koko115:
With 2.72 i dont have akces root to system files in es explore. On 2.68 all is ok. Galaxy s7
[SuperSU] fmc000:
loooooooooooooooooooooooooooooooolllllllllllll
[SuperSU] koko115:
How fix this ? I install 2.72 with TWRP. On others program like titanium buckup i have root granted. Only on 2.71 and 2.72 i dont have root granted on es explorer ;-(
[SuperSU] 5m4r7ph0n36uru:
Don't use ES as root explorer as su access path doesn't seem well implemented by the app developer. Personally I'm using FX File Explorer and Root Explorer and both work really well with the latest SuperSu releases.
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

Would it be possible to have an option/flag to use a custom size for the su.img? I'm using the HTC 10 now, and looking for some creative ways to add some system mods without actually modifying system, and bind mounting seems to be working well. However, I've run out of space in /su. I'm just going to create a larger su.img and drop my new files into it, but I was thinking it might be nice to have an option to set a custom size, or even add the ability to resize it through the app.
[SuperSU] tag68:
Hint: If you want to keep timestamps on copy/move like every other OS supports it without root, you could use Total Commander. I'm not sure if the mentioned explorers are capable to keep timestamps. If they do, a hint in the linked thread would be nice. Thanks in advance!
[SuperSU] ianmacd:
Steps 4 and 5 can be replaced by using FlashFire. That's even easier and doesn't require a custom recovery.
[SuperSU] Chainfire:
I'll put this on my list for "maybe". I have something else in the works that may be useful, but I will not disclose this yet.

You could look into resize2fs. The same issue exists both for the app as for you though, you need to unmount the image to resize it.
[SuperSU] HorstiG:
Is aware, but what? :D
[SuperSU] fmc000:
I don't know, I just flashed the new zip and it worked without issues. Are you sure that the flash process ended correctly? Do you have the recovery logs?
[SuperSU] grep_i:
Search a little harder on this forum as this question has been answered a lot of times already.
[SuperSU] mielletseed:
Chainfire himself is very bothered that people continue to ask this question again and he stated his mood about this topic often enough. You people really should stop to ask about ES Explorer ... (and search before post!)
[SuperSU] NLBeev:
We know, and don't need to be remembered.
[SuperSU] spainter:
http://xdaforums.com/showpost.php?p=66793453&postcount=10562
[SuperSU] manuelsaborio:
Hello, today I saw a message mention that binaries must be updated. I have tried in normal way, with TWRP, but it does not update.

My phone is Lenovo K3 Note, Vibeui V3.1-1614 Lemonade
[SuperSU] Ch3vr0n:
Wrong topic, use the update failures topic.
[SuperSU] grep_i:
Deleted
[SuperSU] Gandalforce:
Or Rashr
[SuperSU] The Analog Kid:
ES file explorer has been updated today. Hope fix might be there..

---------- Post added at 01:26 AM ---------- Previous post was at 01:18 AM ----------

Flashify will do fine as well...
[SuperSU] egingell:
The change log just says "fixed unsafe implementation". Leaves a lot to the imagination.

And there website is crap.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] The Analog Kid:
Well yeah, that's ambiguous and I'm still on 2.62, so I haven't tried yet...

From my ROOTED XT1563 DS using XDA-Developers mobile
[SuperSU] Alxoom33:
I have uninstalled my ES and ES Pro for various, well documented reasons.
[SuperSU] egingell:
For what it's worth, they still don't work without compatibility mode.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] mobileman88:
the software is becoming crap too. uninstalled ES

---------- Post added at 03:02 PM ---------- Previous post was at 03:02 PM ----------

uninstalled it and running root explorer instead.
[SuperSU] The Analog Kid:
Which Adaway version is this?

From my ROOTED XT1563 DS using XDA-Developers mobile
[SuperSU] mobileman88:
For me 3.1.1 works well
[SuperSU] The Analog Kid:
In fact, Stericson is not responsible for Busybox installer or binary maintenance... and he's actually not responding mail or updating his apps for years now!!!... He just disappeared!!!... as to which path to choose, I've noticed some root apps telling me "Busybox is not installed" or just not responding if Busybox installed either in su/bin or su/xbin; so I ended up using the usual system/xbin path with no side effects at all on 6.0 MM and Beta 2.62-3 SuperSU... Why is that?

From my ROOTED XT1563 DS using XDA-Developers mobile
[SuperSU] junioramboy:
I can't remember the version, this is a old one. The latest one works, I just use because I like the icon better.
[SuperSU] grep_i:
I can get both apps working but this is not the place to discuss your app problems.

Please go ask developer of the app why it is not working or search another thread, please stay on topic.