yashsingh1/xdaforums huggingface dataset:
[SuperSU] Mike B.:
I think we're heading for a record and the prestigious "Most Posts Made Blindly Without Reading" award. Too bad the winner won't know about it since the results willl be posted here... ;)
[SuperSU] casouzaj:
Flash the SuperSU zip in recovery. Problem solved!
[SuperSU] ballzak:
Is there a way for my app Automate, which uses su, to revoke it's Superuser authorization, so the user is forced to reauthorize the app?

Does SuperSU has its own replacement for the deprecated "android.permission.ACCESS_SUPERUSER"?
[SuperSU] egingell:
Open the SuperSU app, find Automate, click it, click remove or whatever it says.

That permission was never really required in the first place.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] ballzak:
I'd like my app to revoke its authorization without user interaction. Like a broadcast which tells SuperSU to revoke authorization for an app.

Only because most users probably have the option to require the permission disabled.

It had to be remove because it cause "duplicate permission" in Lollipop, since many SU apps define the same permission.

If it was replace with a SuperSU specific permission, i.e: "eu.chainfire.supersu.permission.ACCESS_SUPERUSER", it could still add extra security.
[SuperSU] Frank Westlake:
I do, if I have the knnowledge and time to share.

Frank
[SuperSU] tkjeeper:
Yay you
[SuperSU] xxxstar:
Full unroot/Cleanup for permanent unroot

Hi- I had questions on the "Full unroot" features of SuperSU. I'm uninstalling my favorite Knox, Verizon bloatware, etc., from a Verizon GS5 on OD5 and then want to permanent unroot including removing BusyBox & as many traces of root as possible.

Question 1: does the unroot operation require the BusyBox app to perform permanent removal? I unrooted, but now I need root to uninstall BusyBox- duh. Next attempt I will uninstall BusyBox first before unroot. Should this work?

Q2: my first shot at performing unroot it didn't work. The busy circle never went away. I rebooted, unchecked "Enable Superuser" (disabled it), and retried unroot- success! Root Checker Pro did not find anything at that point. Was this a normal SuperSU app response to require disabling superuser first, or that unroot actually took two attempts? (If it was the first case, I would make a suggestion to have the unroot function first automatically disable superuser before continuing with unroot operations.)
[SuperSU] NZgeek:
This was discussed heavily around the time that the permission was removed. The answer from Chainfire was that it was never going to happen.

The problem with adding a permission specific to SuperSU is that it only works with SuperSU. What about the multitude of other root apps out there? As an app developer, do you really want the burden of having to update your app for every new su that comes along?
[SuperSU] ballzak:
As a developer i wouldn't mind including a few extra permissions if it increased security for the majority of my users.

Anyhow it would be up to the SU app to declare and enforce the permission.
[SuperSU] NZgeek:
I found the last thing Chainfire posted on the matter. The conversation was continued in a Google+ thread: https://plus.google.com/+Chainfire/posts/Ka3ujLb4bJu

It's worth reading through all the comments, especially those from developers. They show pretty clearly why the permission has gone and won't be coming back.
[SuperSU] ballzak:
Thanks, i'll read it.
[SuperSU] weshall:
error in SuperSu

I am on cm 12.1 nightly (yureka) after manually flashing yesterdays nightly update my root access has gone before flashing there was no such problem ...i flashed super su again but when i open superSu a message appears "There is no SU binary installed, and SuperSu cannot install it.This is a problem"
[SuperSU] Rinoceros:
Maybe do a search in this thread?

You are not the only one...

There is a beta version (2.49) which might solve your issue.
[SuperSU] :
I've a question. I'm running a game called SIF which will FC on root detection, therefore I keep SuperSU disabled when running it. If I were to install a root app which modifies the GPU settings of SIF, would it work with SuperSU disabled?
[SuperSU] flipmode_11:
Easier said than done!

When I reboot into recovery Odin Mode is up the top and it says "Downloading blah blah blah".

Where

am I meant to put the ZIP and is there no other way to undo semi-root and first backup and disable KNOX?

Everyone just seems to say "use the zip and boot into recovery", where? /root/ or sd-cart root, or internal storage, or ...?

Then install SuperSU without any issues. (getting binaries error)

Thanks to anyone who can help!

---------- Post added at 07:52 PM ---------- Previous post was at 07:26 PM ----------

Yeah I have to say, those Three (3) Clean-up options for SuperSu are not clear at all!

No pop-up message for PLEASE DO THIS FIRST.

No link or reference to doc's on what SHOULD BE DONE BEFORE.

And zero details whether other software should FIRST BE REMOVED, before undertaking this action.

As far as I know, SuperSU gets it's tentacles locked in, and makes changes, by pointing to itself in core \ config files. However I believe Busybox does the same. I would guess you uninstall things in the same order in which your installed them! :D

But do i choose Option 1, Option 2, or Option 3?

- Re-install [Nope]

- Switch SuperSU App [Maybe?]

- Full Unroot [Maybe?]

Surely #2 and #3 do the same? Or does #3 do more than reversing what SuperSU did in the first place??? (e.g. downloading and installing binaries and so on)...

NFI
[SuperSU] Rock-&-Roll-Hedgehog:
delete
[SuperSU] egingell:
That is *not* recovery. Recovery has a menu system one can navigate using the hard-keys. Use the other volume key to access it.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] NeoLogY:
Just an advice, I think you should read more about rooting@custom recovery@flashing@nandroid, and most important (for me at least) how to avoid from bricking our device, also how to revive@unbrick our device. At least, those info will give us basic picture of the "advance@power user" thingy. Good luck.
[SuperSU] nish108:
Stupid question but does survive mode work for samsung ota? Bl locked, stock recovery.
[SuperSU] Morthawt:
Every time I get an email about this thread, I don't know why... but I always feel like there is a new version of SuperSU that has come out and when I get here I'm like oh... someone just replied.
[SuperSU] Mike B.:
You can still subscribe to this thread but without email notifications. When a new stable version is released, it'll appear in the Play Store. If you wish to keep track of beta versions, you can also subscribe without email notifications to the beta thread (currently at version 2.49).
[SuperSU] HassanM:
Mate uninstall the SuperSU.... Download the file from the link below ... Its a flashable SU....

Dowland and flash it thru recovery....

http://www.mediafire.com/?rtvqqbaie7ob1t3

After flashing/rebooting run the SuperSU again and update the binary.....

Voila!!!
[SuperSU] Zenns:
There isn't any different between the one I downloaded from his site....
[SuperSU] garyfunk:
What ROM are you using?
[SuperSU] Zenns:
CyanogenMod 12.1 Nightly 03/07/2015
[SuperSU] garyfunk:
You need to remove the superuser binaries the CM has pre-installed before you. For instructions, go to the CM thread and ask how.
[SuperSU] PalmCentro:
[MENTION=6569627]Zenns[/MENTION]

by developer options enable superuser access over apps and adb then run SuperSu normal installation...
[SuperSU] abzjji:
delete
[SuperSU] Ja_som:
mmm, this is not rom, are you sure you are on the right place here? :)
[SuperSU] awaisa123:
supersu on cyanogenmod

is it okay to install supersu onto cyanogenmod 12.1 - samsung galaxy note 4 (n910f)
[SuperSU] arlenwoot:
yes
[SuperSU] alphahere:
T-Mobile S5 - G900T - 5.1.1 + Supersu causes bootloop.

G900TTMB1FOF6_TMB (Android 5.1.1) with supersu version 2.46 causes a bootloop (soft brick). See this thread for more details.

http://xdaforums.com/tmobile-galaxy-s5/general/g900ttmb1fof6tmb-android-5-1-1-t3140695

Any additional information needed to help solve the problem?

Thanks.
[SuperSU] Mike B.:
You might have more luck on the

SuperSU BETA thread

which tends to deal with Lollipop-specific issues.
[SuperSU] switch85:
[IMG="SuperSu on TV Show Mr. Robot"]http://i.imgur.com/SPrgLeS.png[/IMG]

It seems SuperSu, isn't it? Seen on a TV show Mr. Robot S01E03.
[SuperSU] newellj79:
Just seen that! Funny!
[SuperSU] NickName98:
Just watched it.

Came here to post about this :P

Chainfire on TV!

I get really excited watching all those phones on the show.. A few minutes earlier, you can see an s5 (I think) with navigation buttons on :P seeing SuperSU was the best :D

Sorry for the off topic.. I'm just so excited Chainfire, ask for credits :P

BTW great show! (so far)
[SuperSU] Lord Childe:
Flashed latest SU through TWRP... but still binary update failure.

Used SuperSU on JB no problem. Now it fails after updating to 4.4. Fully rooted using vroot, which installed Kinguser as well. Rather use Super SU.

How to fix please.
[SuperSU] sam191919:
after installing 5.1.1 rom on my tab2 p3100. i didn't have root access which one i need to flash

is any wipe required to flash super user
[SuperSU] ktmom:
Flash the beta 2.49. I've never wiped anything to flash. I'm on a CM 12 derivative.

---------- Post added at 02:44 PM ---------- Previous post was at 02:41 PM ----------

I think I've seen other posts where Kinguser interferes. A search to find out how to remove Kinguser might give some ideas.
[SuperSU] Lord Childe:
Removing/disabling Kinguser removes root. I'm not going to mess about trying to find another way to root my device, so I'll stick with it.
[SuperSU] xerubium:
Device: Samsung Galaxy SII (i9100)

PIT: 5GB + 7GB Internal Storage

ROM: CM11 snapshot M12

When I open titanium backup, it give a warning that I should turn of the "Mount Namespace Separation" in SuperSU off. So I did it, and SuperSU said I should reboot the device after changing this option, so I did it too.

Then the problems comes, my external SD card disappeared. In the Storage page of Setting, only the two partition of the internal storage shown properly, which follow with a SD card section with only one "Erase SD card" button.

I tried to turn the "Mount Namespace Separation" back on and reboot. No help. I tried to plug out and back in the microSD card(the old ways..). No help.

I have flashed a custom PIT in this device long ago. Does this matter? Are there any trick to get my SD card back without wiping any data?
[SuperSU] Rinoceros:
The popup also says: "If you encounter any issues in TB, please try changing it."

What kind of issues do you had with Titanium Back Up, or did you just turn the feature off?
[SuperSU] marknoll:
Then install superuser and reboot. Once su is installed, you can remove king user
[SuperSU] Lord Childe:
Not as simple as that. Installed Superuser and attempted to uninstall Kinguser via Titanium and I get “This will un-install the system package: “system/app/Superuser.apk” Got to admire the self-preservation of the thing - its tentacles have reached far and wide, and cloaked itself in Superuser. I hit uninstall and Kinguser was a 'strike through' app, as though it had been uninstalled, but reopening Titanium I find Kinguser is still an installed app... and so is Superuser.

If I were having problems with Kinguser, or root, I’d just wipe and start again.
[SuperSU] PalmCentro:
Super SuMe can help you!
[SuperSU] Lord Childe:
Brilliant, mate, couldn't be simpler.

Cheers!
[SuperSU] xerubium:
I just turned the feature off. I never encountered this popup before. As I just update TBPro, I thought it was some compatibility issue of new version.

Later I also tried to insert the microSD card in my card reader, Windows said I need to format it before use. :crying:

I will later try some recovery softwares, hope that only the TOC is damaged while the content still intact.
[SuperSU] egingell:
SuperSU.apk is this app's file name. Uninstalling the one you named is fine.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Rinoceros:
Did you format the SD card in the phone? It might have the ext4 format of Linux (Android is Linux...) so you might try to read it in a Linux machine or install ext2fs on your windows machine and try again. If that doesn't work, you might try a recovery program or if that also fails; format the SD-card as fat32 and insert it again in your phone.
[SuperSU] awl14:
[Q] Crash when trying to run su

Hello,

I've just posted a new thread about a crash issue:

Whenever I try to run su on my Archos 50c Neon, I get a crash report in logcat logs - see

http://xdaforums.com/apps/supersu/crash-trying-to-run-su-t3156614

Many thanks for your help!

awl
[SuperSU] Mike B.:
I don't know what the original problem might be, but it's ALWAYS a wise idea to format an SD Card in the device where it will be used. The recommended (default) format for an external SD Card on current Android is extFAT. You don't need to (shouldn't, actually!) resort to W*ndows or install anything, just let the phone format it.
[SuperSU] Rinoceros:
Maybe you didn't get it, but xerublum can't access his SD-card in the phone any more and he wants to recover the data on it.

But I do agree with you, such a storage should always be formatted in the device BEFORE you start using it.
[SuperSU] Mike B.:
All I saw was his ominous "I have flashed a custom PIT in this device long ago". The output of the "mount" command from the phone's terminal emulator would probably shed light on what happened. Whether the data can be recovered or not is a separate issue and the card may even need an initial formatting from the official SD Formatter depending on how badly clobbered it got, but the essential point is, as you agree, to always (re)format in the device itself, using whatever format the device recommends (presumably extFAT).

Realistically, it's not a matter of IF but WHEN an SD Card will fail, hence the wisdom of making a copy, just in case... ;)
[SuperSU] Unknowin_man:
Hi guys

Plz help

This is game killer app it's asking for root I have already have it and I was rooted my devise many time anybody help me plz
[SuperSU] Mike B.:
This is a BAD app and I suggest you avoid downloading anything from z4root.cn. There is probably nothing wrong at all with your root and what you see is simply an ad for z4root.cn. I can't advise you on "game killers' in general, but please do yourself a favor and let Google and user reviews guide you. If you feel you must use those highly questionable apps, at least make sure you always have a good full nandroid backup!
[SuperSU] zelendel:
You won't find any help here with those apps. Warez apps are banned from this site. So you are on your own.
[SuperSU] PalmCentro:
So kinguser time posted a whole rant why they block installing SuperSu....

http://xdaforums.com/showpost.php?p=61857510&postcount=1233
[SuperSU] mrrocketdog:
ok. have never used kinguser but SuperSu has NEVER failed me thru 4+ yrs and 4 phones.:cowboy:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[SuperSU] Mike B.:
That post is somewhat of a silly tirade without much content. The poster seems very defensive about [MENTION=631273]Chainfire[/MENTION]'s wording that switching from KingRoot

might

cause problems but it would be irresponsible for him to make absolute statements about another product. The SuperSU documentation is merely being properly and wisely cautious, for which we should be grateful.

There are several ways to root a device, and each developer should concentrate on his/her method, cautioning users that he/she isn't responsible for what other products may do. That's just plain common sense! ;)
[SuperSU] PalmCentro:
We root our devices for freedom!

Not to be stuck with a Chinese shady app....
[SuperSU] Unknowin_man:
I don't use it ... I use supersu and also need to hack some games with game killer application but this message showed

i think I don't rooted well
[SuperSU] Mike B.:
Perhaps you didn't have a chance to read the replies to your post. Discussion of such apps is NOT welcome here on XDA, and if it were we'd strongly caution you against using them if you value your phone and data. Your root is probably just fine, but your selection of apps is definitely not! ;)
[SuperSU] Mike B.:
That's exactly the kind of issue [MENTION=631273]Chainfire[/MENTION] warns against. There is a good possibility that you still have leftover remnants from KingRoot . If possible, the simplest way would be to revert to the unrooted state of your ROM and flash the current SuperSU ZIP from recovery.
[SuperSU] awl14:
Many thanks, Mike,

unfortunately, the Archos 50c Neon is based on Spreadtrum 7731, which most probably means that there is no suitable custom recovery (CWM, TWRP, ...) - therefore, AFAIK, I cannot flash rom recovery, as the SusperSU ZIP would have to be signed using the private key of manufacturer Archos. I think this means that I am unable to avoid using the Chinese KingRoot for the first rooting of the device.

I have - seemingly successfully - followed several tutorials on KingRoot removal, and neither SuperSU 2.46 nor the 2.49 beta version had any issues replacing the su binary. The issue "only" is that it simply does not work, but crashes with SIGABRT.

As the native process stacktrace at the time of the crash looks like this:

I/dalvikvm( 4808): #00 pc 000012f6 /system/lib/libcorkscrew.so (unwind_backtrace_thread+29)
I/dalvikvm( 4808): #01 pc 00065e38 /system/lib/libdvm.so (dvmDumpNativeStack(DebugOutputTarget const*, int)+31)
I/dalvikvm( 4808): #02 pc 00059c70 /system/lib/libdvm.so (dvmDumpThreadEx(DebugOutputTarget const*, Thread*, bool)+395)
I/dalvikvm( 4808): #03 pc 00059cde /system/lib/libdvm.so (dvmDumpThread(Thread*, bool)+25)
I/dalvikvm( 4808): #04 pc 0004e5d0 /system/lib/libdvm.so
I/dalvikvm( 4808): #05 pc 00001fa8 /system/lib/libnativehelper.so (jniRegisterNativeMethods+39)
I/dalvikvm( 4808): #06 pc 0004e09e /system/lib/libandroid_runtime.so
I/dalvikvm( 4808): #07 pc 0004e480 /system/lib/libandroid_runtime.so (android::AndroidRuntime::startReg(_JNIEnv*)+23)
I/dalvikvm( 4808): #08 pc 0004ef28 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+271)
I/dalvikvm( 4808): #09 pc 00001486 /system/bin/app_process
I/dalvikvm( 4808): #10 pc 0000e420 /system/lib/libc.so (__libc_init+47)

am I assuming correctly that the "leftover remnants" from KingRoot would have to be in one of those above *.so libraries?

Would there be any other possible way to try and track down which potential leftovers might come into play here? Or would it be possible to detect this from looking at the place in the native C code where it crashes? Am I assuming correctly that the placte to look at would be #05 (jniRegisterNativeMethods+39 in libnativehelper)? What would that mean?

Many thanks one more time!

awl
[SuperSU] Mike B.:
Sorry, I only know enough about Archos phones and tablets to stay away from them! A Samsung Galaxy E7 would have made your life much easier! ;)

Assuming that you can have a fully functional root with KingRoot (if there is such a thing), one approach would be to start with a freshly-rooted configuration then try to manually duplicate all the steps included in the SuperSU 2.49 ZIP's update-binary script. Obviously, having a dependable restorable backup is a requirement.
[SuperSU] awl14:
Hi again,

[Note that my previous posts as well als replies have been deleted by forum admins due to "message flooding"... :(]

fully agreed, but the issue is that over here, the Galaxy E7 is about 3.5 to 4 times the cost of the Neon 50c... :(

Have just started looking into this, and I truly hope that this should be feasible.

One immediate question about this: While the 2.49 SuperSU apk does seem to "uninstall" KingRoot and related apks when it detects them, the update-binary script only contains a number of "rm -rf" commands. Is it indeed sufficient to properly uninstall KingRoot and related apps by hand before running those rm commands (using "pm uninstall"?)? Or is there any other place in the apk where I can find the actions that the apk takes when I want it to remove the "other su" implementation?

Thanks again & best regards,

awl
[SuperSU] Mike B.:
Since you're new here, you may want to familiarize yourself with the

XDA Rules

before getting into more trouble from moderators. Proper posting will also greatly increase your chances of getting help.

I don't know where "over here" is (don't tell me, it doesn't matter) but I was merely pointing out that the suggested retail prices for both phones are identical and clearly the Galaxy would be highly preferable for most people. Cheaper is not always better and a used Samsung might be better than a new Archos... ;)

The update-binary script is exactly what the SuperSU installer does, nothing more, nothing less. It's in Edify format but you should be able to translate that easily into shell commands. It seems you still need to do quite a bit of homework, but that's not really germane to this SuperSU 2.46 thread. I suggest discussing those Archos issues wherever your phone is supported, possibly in the XDA Archos forums but you're pretty much on your own, sorry.
[SuperSU] jazzruby:
Just a courtesy FYI - SuperSU Installer no longer uses Edify script, the 'updater-script' is just a 'dummy' file, the 'update-binary' IS a shell script which communicates with the recovery api/binary through pipeFD ;)

-JR-
[SuperSU] Mike B.:
Correct. That'll teach me not to reply in so many threads at the same time. At least I got it partially right and referred to "the update-binary script". ;)

Thanks for clarifying my post!
[SuperSU] PalmCentro:
Haha Kingroot calls SupersSu a malicious app :)

http://xdaforums.com/showpost.php?p=61899071&postcount=1277
[SuperSU] Mike B.:
Maybe it's the language barrier but apparently he doesn't understand that nobody is forced to use any particular root application, but by the same token nobody should use more than one at the same time.

He seems upset that SuperSU offers to remove any conflicting program and it's unclear why he should even care so much about SuperSU, Super-Sume and other root-related products. I would hope that KingRoot at least considers offering the same courtesy to its users if anyone wishes to replace SuperSU or any other root method with KingRoot.

EDIT

: I did a bit more research. Interestingly, while complaining that SuperSU unfairly claims that an existing KingRoot might cause problems, [MENTION=6674985]Kingxteam[/MENTION]'s own disclaimer states: "5. Install SuperSu to replace KingUser may be cause some unknown error, although you do can do this (sic)", which renders his point completely moot. ;)​

The unfortunate part is that such silly reaction reflects very poorly on KingRoot if its developer is apparently so afraid of "competition". Even if the program were extraordinarily well designed and written, such puerile paranoid behavior would chase most reasonable potential users away from it.

Fortunately [MENTION=631273]Chainfire[/MENTION] sems to have taken the high road by simply ignoring all this silly misguided whining and we should probably all do the same thing in this and other reality-based threads... ;)
[SuperSU] awl14:
Hi again,

well, the street price for the Neon 50c here in "Euroland" is 99 EUR, while best street prices for the Galaxy E7 seem to be EUR 349 - quite a difference... ;) :(

I have already started looking into this tonight, but it's not that easy: From the KingRoot statement cited here by user NewYork!, it seems that KingRoot has added some extra logic to detect any attempts to replace it by SuperSU and make them fail. This indeed seems childish behaviour.

Can anybody who also needed to use KingRoot for first rooting of their device confirm that the code in the SuperSU 2.49 beta "update-binary" is indeed sufficient to circumvent the "self-protection" mechanism of KingRoot?

I will report back here if/when I succeeded with my shell scripting homework... ;)

Thanks & best regards,

awl