yashsingh1/xdaforums huggingface dataset:
[SuperSU] chwiejak:
Is supersu (updating binary) working bad with multirom recovery?

I can not find sulotion for binary.

I have fresh lineage (as primary rom) but still can not run supersu:-\
[SuperSU] Ibuprophen:
I'm just wondering if and what SuperSU detects for system root or just automatically defaults to Systemless root?

I have no issues to report as this does work great on my device, i am just curious...

Thanks!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[SuperSU] DB126:
It is my belief (based on readings and limited experience vs hard reference) that systemless is the default for Android 6 (MM) and above. Can't speak to caveats and other 'special circumstances'. Likely that material exists some-where; just haven't run across it yet.
[SuperSU] jcmm11:
That's correct. To be exact:
[SuperSU] chwiejak:
I am still fighting with binary updatpe..

I tried on both os: cm13 and lineage.

Normal update not working twrp update causing freezing on boot logo.

I have multirom twrp.

Any ideas please?
[SuperSU] luminouche:
Hi

On Redmi Note 4 Global, i lost usb connexion to computer after root. Why ?

After editing Build.prop with :

persist.service.adb.enable=1

persist.sys.usb.config=mtp,adb

Everything is ok, but only with debbuging enabled (if disabled, still no usb connexion)

Why ?
[SuperSU] ktmom:
A log (matlog is a good app) can be really helpful. Start a log, try to connect and look to see what the log says.
[SuperSU] androidfr33k:
My question is if you completely unroot with SuperSu, I have the pro version then re-install the 2.79 binary, I do not see the message like I saw the very first time I installed the 2.79 binary about either checking or installing systemless root. Each re-install just mounts /System, /Data and rootfs, then extracts files, detects compatibility, system mode, some other stuff followed by post-installation script then unmount's /System. I know it had to re-install systemless because when I execute the command "which su" in terminal I get /System/xbin/su and in SUperSu app under settings, Install Supersu into /System is not grayed out allowing you to install Supersu into /System. I also verified that the re-install does not install into su/System/su if that is how it was traditionally installed, and installed "secure settings" app and under the secure+ tab I see System+Module is disabled.

So I have to assume a different script is run when you re-install Supersu?

Edited:

After a quick google search I found that you can force the install of the traditional SUpersu by running this command in twrp terminal "echo SYSTEMLESS=false>>/data/.supersu" but if I change that to true instead, then reinstall I see the original messages such as System-less mode, boot image support required etc etc but now my concern is that it re-applying the hex patches and if it has already has been patched once before, I have to assume it won't be able to patch again since the binary was previously patched?

Edited Again:

I was all wrong I reinstalled SuperSU after running the script before hand with "true" instead of "false" and now its truly in systemless mode. No su in /system/xbin, the which su command shows /su/bin/su and the secure settings settings+ tab now actually has the message no root access, also in supersu pro app settings install SuperSUinto /System is now grayed out because its not currently available in Systemless root mode.

I have actual twrp image backups so when I restore them, is it possible Supersu no longer has patched the boot partition? Everything seems fine now I just need to figure out after a restore of my rom partition images using restore from twrp if for some reason the boot partition is no longer patched by Supersu after a restore?

Is SUperSU now clean from /System

Last Edit:

Well it seems fine now I did a fresh backup then a restore and nothing has happened to SUperSU, I must have done something wrong, however what I mentioned about reinstall or completely unrooting then reinstalling does not install SUperSU binary as systemless so I need the .supersu file in /data.
[SuperSU] 4EverMaAT:
Is there a way to temporarily disable root access? I have a mobile banking app that will no longer allow login screen when it detects a rooted phone.

Asus zenfone 2 max 6.0.1, rooted. (zc550kl)

SuperSu Pro 2.67

---------- Post added at 10:14 AM ---------- Previous post was at 09:38 AM ----------

^^Ok. I unchecked Enable SuperUser and the banking app seems to work.

I then re-checked the SuperUser checkbox and i got an error after 90 seconds or so that SU binary could not be updated. Reboot and try again.

Ok or Reboot. I reboot and i now get notifications that the SU binary needs to be updated.

1) how do i update the binary?

2) if i still have full root access even without updated SU binary, can i permanently suppress the notification?? I dont see a 'do not ask me again' checkbox.
[SuperSU] xanthrax:
Guys , I have performed a small cleaning by deleting [MENTION=7788602]qiurigao[/MENTION] post as per his request and also the other posts related to it

Thanks for understanding

Dan
[SuperSU] 4EverMaAT:
I tried to 'cleanup for reinstall via google play' . After the reboot, i go to google play and when I attempt to install SuperSU, I get error:

"SuperSU can't be installed......Error code -505"

Any ideas?

It is safe to manually flash 2.79.zip from TWRP recovery? (Asus zenfone max zc550kl)
[SuperSU] pizza_pablo:
I think via TWRP is the only way I've ever flashed SuperSU.
[SuperSU] mondohow:
I've seen that error twice, but this was a long time ago. The first time I fixed it by clearing Data/Cache on the PlayStore. The 2nd time I also had to remove then re-add my google account.

Good luck.
[SuperSU] Ibuprophen:
Has anyone seen the following thread?

http://xdaforums.com/showthread.php?t=3370794

It, apparently, is able to disable SuperSU from Systemless Root and perform a System Root.

I'm a little intrigued.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] jcmm11:
Yes. It's been known for a long time that you can force a system install by writing "SYSTEMLESS=false" to the. supersu file (multiple possible locations for that file. I think the one in /data takes precedence.) See comments in update-binary of SuperSU zip for more details.
[SuperSU] grep_i:
I'm talking about file based encryption, I did assume this is the default in Android 7 nougat but of course I could be wrong because I lack real life experience with Android 7 nougat.
[SuperSU] Alxoom33:
http://www.howtogeek.com/269422/how...ats-direct-boot-for-less-annoying-encryption/

Take a look at this article, fyi.
[SuperSU] grep_i:
Thanks for the heads up so I was right to assume it is the default for Android 7 nougat.

At least for phones that are not updated from marshmallow but are preinstalled with nougat.
[SuperSU] banciii:
That kernel-level encryption is an other story. Moreover, the latest (2) TWRP is already working fine with encrypted devices too, so there is no need to flash a decrypted boot image for TWRP anymore. What I am talkin about, the File-Based Encryption (FBE) is a different kind of encryption which can be found only in Nougat. The only thing I wanna use it is because with this new feature, the startup PIN/pattern is not needed anymore (during the boot) and according to the rumors, it also increase the performance. So I just hope the new guys will somehow find a way to make the SuperSU compatible with FBE. As I mentioned earlier, I would gladly help in it.
[SuperSU] hacknmtk:
https://9to5google.com/2016/03/22/android-linux-kernel-vulnerability-patch/

For those wondering why root is failing on newer versions of Android, as well as patched kernels causing problems.

So much for Android being developer friendly.
[SuperSU] Strephon Alkhalikoi:
Android is developer friendly, and people within Google are doing their best to retain root capability for those who want it. But when a vulnerability is publicly exposed in this manner, Google has to act or be seen as not being serious about security.
[SuperSU] hacknmtk:
If they really want to help retain root access for those that want it, why not add it as a stock feature that can be unlocked like the bootloader can be?

Doing that will allow those that want root privileges the access in a more secure way, and for those that don't can just ignore the option.
[SuperSU] DeathArrow:
Tried the last version and some older versions on Android N on Nexus 5 and all result in a bootloop.
[SuperSU] egingell:
If Google includes root, it will probably be a stripped down version and be non-replaceable like a lot of the other stuff people wish they could replace.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] hacknmtk:
I've moved the topic here http://xdaforums.com/android/general/androids-root-fix-t3457508/ to keep from cluttering up this thread.
[SuperSU] zalcsooo:
No it's not. FBE is still in beta (kind of) and it's not the default yet. It can be enabled in the developer settings after installing Nougat.
[SuperSU] bagarwa:
Disable storage force-encrypt

I have Nexus 6P, Stock Android 6.0.1 September patch, SuperSu v2.76, franco kernel r27, Xposed v86.

I am now going to factory reset my device from twrp and then flash the official Android N image.

My question is -

Does flashing the SuperSu-v2.78.zip disable force encrypt flag or will I need to flash the modified boot.img separately before doing that? I hope it's the former, but if it's the latter, can someone please link me to such modified boot.img? I don't want my storage to get encrypted.
[SuperSU] ktmom:
I don't think anything was changed since ChainFire's G+ post for the 2.72 release. I believe the default is still to disable forced encrypt.
[SuperSU] grep_i:
That's not what I read, it says it is enabled by default on phones that come from factory with Android nougat.

Only on phones that are updated from marshmallow to nougat it is optional and you have to enable it yourself.

You are saying this yourself "after installing nougat" you have to enable it yourself not after buying it because by than it would already be enabled by default.
[SuperSU] Alxoom33:
How?
[SuperSU] banciii:
That will be the future. Only for those devices which have Android Nougat out of the box. So the only phone now is (will be) the LG V20. On the Nexus phones, as on my Nexus 5X, the FBE is not the default yet. When you enable it in the developer settings, it even states that it is still in an early stage.
[SuperSU] KingColeV2:
How do you safely uninstall superuser to Install superSu
[SuperSU] grep_i:
In playstore on the app screen you see three dots in the upper right corner, press it and remove the check mark by automatic update.
[SuperSU] snachez:
Yes, I have that unticked already, but the question was how to not let playstore even offer the update. I would like to go into the updates screen and not see an entry at all for SuperSu 2.77 onwards. Similar to resigning an apk so playstore doesnt offer updates. Thanks.
[SuperSU] Mesmurized:
Tucked away this gem for my eventual move to N. So when 7.1 PN came out I jumped. Clean flashed 7.1 PN, EKX & SuperSU 2.79 and my 5x would hang at the animation screen and never finish. After 2-3 hrs and multiple flashes, finally gave up, deleted the file and flashed systemless. Haven't looked back since.
[SuperSU] sanathxda:
I have a Moto g4 plus with twrp and rooted it and my current super user app is named as phh superuser but I need super su

I tried installing it from play store after uninstalling my phh superuser . Unfortunately installation failed both normally and through recovery ..

So can I flash the flashable superuser.zip file to get the super su?
[SuperSU] ktmom:
Please see this post from earlier in this thread.
[SuperSU] sanathxda:
What should I do with the script?
[SuperSU] ktmom:
You go to the post I previously link to. You then go to the thread linked in that post (osm0sis' Odds and Ends) and then go to the first post where osm0sis lists various useful scripts. Look for "unSU script", download it, flash it, profit.

<is there an emoticon for spoon feed?>
[SuperSU] Ch3vr0n:
I'll one-up you.
[SuperSU] Ibuprophen:
I have a question for all you SuperSU Pro's out there... I'm suffering from Brain Damage and the answer will probably make me smack my forehead and say "i should have had a V8!" LMAO!!!

Though, SuperSU v2.79 Stable, has been working like a charm by way of Systemless Root...

I'm wondering if installing it (on my S3 d2vzw using CM13) by way of System Root, I'm thinking that it should work without an issue.

Is my assumption correct? or do I need to check into the Betty Ford Clinic? LOL!

Thanks a Bunch!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] DB126:
Not certain but I'm sure there is a way. Personally I am ambivalent to system/systemless root as I almost always compromise the system partition through direct writes at some point. I also observe the DFWI rule when something is working as designed with no apparent disadvantages. Choose your poison wisely.

You are dating yourself with V8 and BFC quips ... ;)
[SuperSU] Ibuprophen:
HA! There's an older commercial for a drink called a V8 (i believe that the name means that it has 8 Vitamins and Minerals or something). The commercials used to have a person who makes a mistake or something and they would gently smack their forehead with the bottom of the palm of their hand and state "I wish I had a V8!".

Well anyways... I knew that SuperSU used to be installed on CM12(LP) as system root and i thought that it may work for CM13(MM) but, I DO know that issues arise for CM14.1/LOS14.1(N)+ ROM's.

I wasn't 100% sure if System Root would work for CM13(MM) and wanted to get a second, third, fourth, etc... Opinion LOL!

Thanks!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] DB126:
https://youtu.be/ld8eAH0MW00

LOS is a special case as documented here. There are issues securing system root with some Android 6+ builds (laymen explanation) but I have not followed the details and too far removed to comment intelligently.

Err...those V8 commercials...they aired long after I left the nest. Remember them well. BTW, I also moderate the geriatric freedom forum on XDA. ;)

Hopefully someone more knowledgeable jumps in with an answer to your question.
[SuperSU] godofsalt:
Ok from what I do know from Los, is yes use SuperSU either the last beta build, of the Final SuperSU zip.

If you want to actual open up the SU Root in the Dev section, IF YOU USE THE ROM's SU... then some things WILL BREAK, Like Google Pay, or any other app for that sort of things.

This IS due to the ROMs SU, showing up the fact that your Rooted...

Hope this helps.

(move from the S3 to the S5, still play with them though.)

Tanx
[SuperSU] lectricas:
Hi. Sorry for such a late reply, but I'm still unable to root my device.

this is my original post

I've attacked recovery.log.

Please help me.
[SuperSU] Ibuprophen:
I was just wondering if anyone (or even [MENTION=631273]Chainfire[/MENTION], though, he is probably aware of it already) had noticed the following LineageOS Biweekly Review from May 15th?

If you go to the following, direct link, and scroll down a bit, you'll see a title "Kernel su-hide to address an important vulnerabilty".

LineageOS' Biweekly Review #9 - Gello, Jelly and a security advisory {15 May 2017}

I posted it here as it does pertain to the devices SU file and what they had done.

I just wanted to provide a little friendly FYI...

Thanks!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Ch3vr0n:
That su thing only applies to the lineage rom and THEIR own su
[SuperSU] immi803:
Adaway system less mode broken

Adaway system less mode broken with version 80 though never had an issue with v79, anyone? Any help?
[SuperSU] Ibuprophen:
After flashing the v2.80 update, I had noticed the occasional "SuperSU Stopped Responding" but, it really doesn't do this allot.

Then i had realized (and I'm not sure if [MENTION=631273]Chainfire[/MENTION] does either) that, after the release and then the flashing previous Stable releases, i always had noticed that the Play Store always had an update to the SuperSU Pro.

Like clockwork, after a stable release was announced, i flash the update, then I would go to the Play Store where I always knew that there would be the SuperSU Pro there awaiting the update.

With that stated (though i had explained like a book LOL!), i noticed that there was no SuperSU Pro v2.80 there.

I have a feeling that the, very occasional, issue of "SuperSU Stopped Responding" may be the result of the SuperSU Pro still being at v2.79.

Am I just crazy or am I correct?

And if you state crazy, then I will agree with you too... LMAO!

"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:
Here's a possible explanation ;)

And Yeah you're Bat crap crazy ?

https://xdaforums.com/showthread.php?p=72419602
[SuperSU] Ibuprophen:
LMAO!!!

Much better than my Ex-Wife... "Looney Toon Stir Crazy" LOL!

Thanks a bunch for letting me know that it's there.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] ThaHawk:
This update 2.80 just wiped out my root!
[SuperSU] shaggyskunk:
View attachment 4160563
[SuperSU] Ibuprophen:
Okay... I guess i am crazy... LOL!

SuperSU v2.80 had crashed again even after I had updated the SuperSU Pro.

I've provided a screenshot and a Logcat file.

Also, when I had flashed the Stable SuperSU v2.79, everything worked without an issue from SuperSU.

I had tried to go into app permissions and attempted to grant SuperSU the 3 permissions it asked for and the permissions are not keeping. When I exit the screen and go back in to check the permissions i had granted before, it just reverts back. I don't have this permission issue with any other apps but, this one.

I can only think that something is just no right with the SuperSU v2.80.

To add... I have an S3 I535 d2vzw with CM13 and the whole kit and Kaboodle.

please let me know, [MENTION=631273]Chainfire[/MENTION], if you require any additional information.

Thank you very much!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] KaMyKaSii:
Have you tried uninstalling only the SuperSU app and then reinstalling it? Have you tried to upgrade through the TWRP zip? Clear dalvik-cache (why not?)?
[SuperSU] Ibuprophen:
To be honest, I did them all. I even tried to install it via the Play Store and have updated the Binaries via the SuperSU app.

The bottom line is that the issue is not present in the Stable v2.79, it only arises with the Stable v2.80.

EDIT: Sorry for not mentioning this but, i didn't loose root. It's weird... The popup happens very seldom and I've seen no issues, thus far, regarding the loss of root.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] _Altmann_:
Hello.

I have a sony xperia e4. My phone was rooted and i had supersu installed. A few minutes ago i updated Super su. It failed to update the binaries. I rebooted the phone and now i`ve lost the root to my xperia e4. I cant even enter SU anymore. It says "root not detected"
[SuperSU] KaMyKaSii:
Have you ever tested SuperSU v2.79 SR4 to see if the problem also occurs in it? And while still having root access, it works only for apps that you have already granted superuser permissions (assuming you didn't wipe SuperSU data between v2.79 and v2.80) or you can grant permissions normally for new apps? In that case only the main interface leading to the crash?
[SuperSU] bit2shift:
Same here, updated it and suddenly was left without root.~

Flashed the zip and it said "SU binary occupied". The Forum link about it is nothing but bull****.

EDIT: Running from the terminal, su says:

> CANNOT LINK EXECUTABLE: cannot locate symbol "sigfillset" referenced by "su"...

How about providing a proper stable release for Android < 5.0?
[SuperSU] whereme:
Hi, I have a question. Why does supersu v2.80 need so many new permissions? Are "Location" and "Wi-Fi connection information" etc really necessary?
[SuperSU] Mesmurized:
Looks like advertising/smut to me?!?
[SuperSU] whereme:
Do you mean that it collects our information for advertising?:(
[SuperSU] AJ:
does 2.80 work on Android O dp2 on the pixel ?
[SuperSU] SilverFlash:
Doubt that. I just had a look at their announcement, guess the permissions requests may be related to Google Analytics. But it's kinda sad that they use Google product, since SuperSU root Google's Android;)

---------- Post added at 04:26 AM ---------- Previous post was at 04:24 AM ----------

Not sure but I will wait for Chainfire's own update if I wanna try on Android O. Since this update didn't mention it, it's likely not ready yet.
[SuperSU] KaMyKaSii:
https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post72419598
[SuperSU] chenshaoju:
A Chinese Team?

As a Chinese,I'm not trust this,Too many "malware" is come out from China,Like 360,Baidu etc...These company doing tons bad tings in there software,like collection users privacy,push grayness area ads.

I'm out, Even i already buy SuperSU Pro.

Moving to Magisk .
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION] had stated what that the SR4 was for and the d2vzw GS3 was not one of them.

So I just gave it a try and it worked without any problems.

I went and flashed the v2.80 again and the same results as previously.

This may or may not apply but, I did notice that every time I had flashed the v2.80, the device restarted 3 times.

I know that SuperSU can have a device restart a few times but, my device always had restarted once. It's a very odd behavior.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] ashish1989:
Binary occupied error is coming in v2.80

Tried flashing it many times but same problem
[SuperSU] Sebeq1:
I have the same problem...
[SuperSU] Strephon Alkhalikoi:
I had to revert to 2.79 SR3 for now as 2.80 and AdAway aren't playing nice together. With 2.80 installed AdAway will not copy the hosts file to /su/etc/hosts, even though it has root.
[SuperSU] Bobthahog:
Made my device lose root after updating so tried to flash 2.80 in recovery and binary was occupied so had to flash 2.79 and now I have root again. Wish Chainfire was still the 1 developing this app. I use Magisk on my other device and that's the way to go now.
[SuperSU] Mesmurized:
I'm out. No more SuperSU updates for me.

Anyone know if TiB will unlink SuperSU from GP without causing other problems?
[SuperSU] dauchamhetnhe2:
Flash zip 2.8.0. Su binary occupied. Why
[SuperSU] Hagakurje:
same question
[SuperSU] steanne:
to my knowledge, it won't stay unlinked, google will keep forcing it on their end.

however, i made a group of apps i want unlinked from the market in tibu and set it to unlink them all every 6 hours. it's a pain to set up, but once it's done it's easy to add an app to the list.
[SuperSU] dinkoh:
+1. How do you unlink it? I don't see super su as an app?
[SuperSU] AtAM1:
Do not update to v2.80 as the new requested permissions are sufficient to keep tabs / build a profile on you. The mere fact that 2.80 and AdAway are conflicting raises a red flag.

Stay on 2.79-SR3 and enable PrivacyGuard on both SuperSu and SuperSu Pro. Also, disable auto-update for both apps in Play Store. Personally, I wouldn't move forward with v2.80 until we get an official statement from [MENTION=631273]Chainfire[/MENTION] as something isn't right (I have a gut feeling he is as surprised as we are).