yashsingh1/xdaforums huggingface dataset:
[SuperSU] Mike B.:
What were you updating FROM? If the SuperSU from the Play Store gave you a signature error, then what you had before was

NOT

an older version of SuperSU but something else (and ancient superuser, perhaps?). Assuming you have a custom recovery, try flashing the installable ZIP available from the OP.

By default, SuperSU uses the system language. This can be changed in the settings if necessary but is seldom required.
[SuperSU] garyfunk:
That is a "flashable zip" not a CWM file.

CMW is has not been updated in years and should not be used.

I don't know where you read this but please ignore if. It's mostly misleading and probably wrong.

Download the flashable zip files from the first post here and on the beta thread.
[SuperSU] caldent:
Well as of now I disabled signature verification and installed . The latest one is up and running and even updated the binaries.
[SuperSU] garyfunk:
It seems you and your phone are stuck in the last century. It's time to update your system to the modern software.
[SuperSU] martin_austria:
guide or manual for supersu

I am looking for a guide or manual for the supersu app.

Is there anyone out there?
[SuperSU] egingell:
First: Don't quote the big-ass OP.

Second: Why on Earth do you need a guide for SuperSU???

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] PIRATA!:
I have looked inside the "flashable .zip" files already and have seen that there are other system files.

I assume that the installation script of the flashable .zip would understand what to install according to my device...right??

In case, what will it install for a Samsung S5 Prime SM-G906K with Qualcomm Snapdragon 806??

I have looked at the installer script of the flashable .zip file, but I don't know what will it be chosen depending on my device.

Can someone tell me what will it be chosen? I need this for my personal need as I will install SuperSU let's say "manually", and down here I'll explain why and how.

I got further in my investigation.

I will try to root not with conventional methods like CF-Root but using KingRoot or iRoot apps or others, as I could end up with a rooted device with KNOX 0x0.

(

Note:

for my device there is no other way to have root with KNOX 0x0 as the Towelroot method could not be applied as the oldest KitKat firmware for my device is after June 2014, so CF-Root it's the only official actual method, but will trip KNOX!)

All of those rooting apps force the installation of an alternative "SuperSU", a Chinese one called KingUser.

If rooting succeeds, I will end up with this KingUser installed, plus SuperSU could not be installed over it properly.

The only way is to uninstall KingUser before it, but this would revert root in a non rooted device again, and installing SuperSU would not fix that.

There are procedures to replace that Chinese thing with proper SuperSU here by keeping root achieved before by those apps.

All the replacement procedures uses ADB or Terminal Emulator (I found two of them based on manual typing and two based on automatic scripts), and the replacement involves mostly three files: "su", "busybox" and "SuperSU.apk" files.

Only one replacement procedure involves the replacement also of the "install-recovery.sh" file.

Now, as I see that there are different "su" versions in the different folders in the flashable .zip file (I see also other system files in each folder where I see the su files), and assuming that its installation depends on the different type of device, I better first understand which files would be installed by the SuperSU flashable .zip file so to use those for my device in my replacement procedure.

If you could tell me what will it be chosen by the SuperSU installation for my device, I could look in the installation script at that part and understand how are they installed so to understand how to implement that in my replacement procedure.

P.S.:

what is the version of "busybox" in last SuperSU official?

This is it. I know it might be hard, but I'm quite ok in trying this.

Thank you all.
[SuperSU] Mike B.:
I don't think anyone call "tell you" more than what we've all tried to tell you already. The installable SuperSU ZIPs are not encrypted and you can investigate for yourself what they contain and do. All the files are included and all the scripts can be studied freely. Since, by your own admission, you don't wish to use SuperSU at this time, I strongly suggest you move this discussion wherever alternative root methods for your device are supported.
[SuperSU] PIRATA!:
I think you don't get it.

I'd like to use SuperSU. That's why I'm asking here.

But I'd like to install it without the regular way because of my particular needs.

Maybe you try to move me out just because I'm trying to do something too difficult for you to understand, and you keep on not giving any helpful infos.

I am trying my self to give my support here with my tries and investigating, so please don't treat me like a noob and with superficiality.

If everyone were would choose to be stuck in using standard thing, all XDA could even end up its existence.

I'm trying to manage in trying to have a better solution to something that works but not as supposed, as you all say that the SuperSU flashable .zip file installs all a bunch of other important things.

Just to be clear, I refer to the replacement on this Chinese Supersu with the original SuperSU here that the way it's done now does not replace all the files that the flashable .zip would install!

As I'm trying to manage to all those things that you say that are important, and as I'm not speaking about awful things, I have all the rights to ask and have the correct treatment ad I'm not a simple user and as I'm giving my time for free in something that one day might help someone.

I'm not a developer like most of the people here, but I'm a contributor here as I'm facing things that maybe people like you would probably enjoy without even getting preoccupied about what's behind, so please some respect, as I respect all those that ask for help in something that might help themself or others.

Said this, can someone please help in telling me what does the installation script of the SuperSU flashable .zip file does install for my device (Samsung S5 Prime SM-G906K Qualcomm Snapdragon 806) as I'm not that good in understanding at what family is my device affiliate at?

Simple question, simple answer, all asked with humility to the someone that knows more then me.
[SuperSU] garyfunk:
We think you don't get it. You need to take to the forum for your phone and ask developers. Your wants are beyond the scope of this thread.

In other words, we can't help you here.

You need to become a developer for your phone.
[SuperSU] Mike B.:
The proper way to install SuperSU on a rooted is to use the SuperSU app from the Play Store. If your device is unrooted but compatible, you can flash the installable ZIPs. Thousands of users have had success with those methods on a variety of devices. If you wish to try other approaches, you can certainly do so but you can't realistically expect others to take you by the hand and detail every single step. Specifically if you wish to understand what the ZIPs do, you simply have to look at the embedded Edify scripts. For the record, your Samsung S5 Prime SM-G906K has a fairly common Qualcomm Snapdragon 801 CPU (MSM8084?) of the ARMv7 family. Hopefully you know more about your own device than we do... ;)
[SuperSU] PIRATA!:
Thank you.

Isn't a Qualcomm Snapdragon 805 cpu?

In any case, it's a ARMv7 device.

I'll check the link you mention.

Tnx again.
[SuperSU] explorer-10:
For anyone one lollipop 5.x, is the option for ota survival removed from SuperSU? I don't see it anymore. It used to be there with KitKat however...
[SuperSU] egingell:
The answer you seek is in the change log and numerous other times in this thread.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] explorer-10:
Aka not supported, gotcha
[SuperSU] Chainfire:
Under Lollipop, SuperSU hijacks app_process, which is used by "am" and "pm" calls. I've not noticed any issues with them, but if you are seeing some issues that is the place to start looking.

I've seen this happen a few times. Has something to do with a too fast boot sequence where root isn't really ready yet when SuperSU starts. If you open the GUI and you don't get the notice about updating the binary, don't worry about it.
[SuperSU] schwem:
[MENTION=631273]Chainfire[/MENTION] I have an issue you may be able to shed some light on. I have an LG G3 that I rooted with an app that uses download mode as an exploit in order to force supersu and necessary binaries to the system. It seemed to work just fine as I was able to install recovery with an app known as autorec for my vs985 on lollipop. Well recovery works great. I was able to install a modded stock rom with supersu baked in and I was also able to install xposed and run all root apps wnd modules without a hitch but I am faced with a few issues that seem root related. I am unable to reboot using adb shell. If I type su (enter) I am able to grant terminal emulator super su access but when I type reboot (enter) it acts as if it will restart but the screen goes black and sits till I pull the battery. I also have an issue where I can grant root access to any root file manager but anytime I try to move or copy and paste any folders or files into my system app or priv-app folders I get an access denied error. It seems strange as root is working fine as far as granting supersu permissions but the two things I stated I am unable to make happen. Do you think it may be a supersu binary issue or is there some other issue I could be facing. I am running supersu official from the playstore as the rom installed 2.45 so I updated to the latest stable version. I have tried everything and am at a loss. I've never had an issue where I was unable to move apps or files in file explorers with root access. Please any help would be appreciated.
[SuperSU] NZgeek:
Given that you've got a custom recovery, I'd head over to the beta thread and download the 2.49 beta zip. It has some changes that may well fix the problems you're getting. Install the zip through recovery and post back if the problems continue.
[SuperSU] schwem:
Alright. I'll give that a try. Thanks

---------- Post added at 11:50 PM ---------- Previous post was at 11:15 PM ----------

You my friend are a genious! I am worry free now. I didn't think that was it but it was. The rom I run coes with supersu 2.45 so I figured I borked something by mistake along the way but the binaries or something must've been out of date. Not sure how it all works but I do know that terminal commands all work as they are supposed to now and I can now move things in root browsers to their respective locations. Thanks again man. You saved me from busting out the P.C. and starting from scratch.
[SuperSU] Droid2drummer:
Yes. He is mistaken. The s5 is Qualcomm 801, but prime is 805. The only difference afak...its rather cool i think. You have the note 4 cpu. Lol Im sure the guy knows this but just typed 2 quickly. Ive done the same. There are after all so many to keep up with. Lmao. Peace.
[SuperSU] jgcaap:
Guys anyone having problem with su icon disappearing?

I was forced to work on a work around, run on terminal am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity

But is quite annoying... :/ can any one give a suggestion on what to do? Thanks.
[SuperSU] _jis_:
Are you talking about disappearing su icon from homescreen, from homescreen folder or from app drawer?
[SuperSU] NeoLogY:
Did you tried *#*#0000#*#*?

Sent from here to there
[SuperSU] jgcaap:
Doesn't do anything. I even removed the auto flash from my builds to understand this, and made a clean flash. After flashing ROM i flash SuperSU , it appears working but doesnt appear the icon on launcher as it was supposed to, as also is hidden from titanium backup.

Any explanation for this?
[SuperSU] egingell:
It's always been hidden from Titanium Backup. Titanium Backup doesn't show it because the "allow backup" flag for SuperSU is down.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] jgcaap:
i would swear that it appeared in the past....

Any suggestion to make it appear? having this issue for already 2 weeks... Haven't done anything special on ROm level to loose this :\
[SuperSU] shaggyskunk:
Have you Flashed an updated or different Rom - I've found that Roms that have SuperSU built-in tend not to show it in the app drawer - You could try flashing the SuperSU beta zip and see if that works for you

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] egingell:
It's never been listed. TB actively ignores it. You can ask the TB devs to add an option to ignore that flag or change the flag yourself (decompile, edit the manifest, recompile). It's also entirely possible that TB ignores SuperSU by name (hard coded) - I don't know if TB source is available for looking and I'm not going to check.

As for the other problem, have you tried changing SuperSU's icon in its settings?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] NeoLogY:
I'm so sorry, gave you the wrong code. Its *#*#1234#*#*. When get in supersu, check if there us option to change icon, if appeared, reboot after that.

Sent from here to there
[SuperSU] jgcaap:
Thanks,

I opened and no option to change icon.
[SuperSU] egingell:
This option doesn't exist?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] NeoLogY:
This always happen when your ROM is already have SuperSU as a native SU(its already been cooked in your ROM). Check in ROM Setting and see if you can find superuser tab probably before Developer tab.

Sent from here to there
[SuperSU] jgcaap:
Yes that's what i thought, so i made a build without SuperSU and same thing happens. by any change do you know a proper fix to apply so that when i make the builds it'll work properly?

Even with a clean install.. So anoying -_- . I'm thinking on coming up with a new solution

---------- Post added at 07:12 PM ---------- Previous post was at 06:44 PM ----------

After speaking with one of my testers, it seems this is a cm issue. As is not available after flashing. Interesting.
[SuperSU] NeoLogY:
Glad you figured it. Everyday have something new to learn. :thumbup:

Sent from here to there
[SuperSU] jgcaap:
Yes but the problem persists... Let's see who'll show the solution...
[SuperSU] NeoLogY:
I found this app, its not the solution but for now, u can use it to make any shortcut for hidden app to your hone screen. Its QuickShortcutMaker, in playstore.

Sent from here to there
[SuperSU] JulesJam:
I am trying to run an adb shell as root and SuperSu keeps silently denying my adb shell root access. Is there some way to stop this from happening? Moto X 2013 running 4.4.4 rooted with SuperSu 2.46.

Should I change the default access to grant?
[SuperSU] Zach1928:
Noob queestion- does v2.46 work with Oxygen OS on the 1+1? I'd rather not play around with any beta builds. Thanks!
[SuperSU] egingell:
That app is great, but with the right launcher, it might not even be needed (ADW has the option to add custom shortcuts, for example).

Nobody can answer that question with the amount of information you've provided.

If it's KitKat or lower, probably.

If it's Lollipop, maybe, but probably not.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Zach1928:
Oxygen OS is the in-house rom from 1+1, but at any rate I flashed the zip and it's fine
[SuperSU] egingell:
Saying that is just like saying that TouchWiz is Samsung's ROM. It still has varying Android versions.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Zach1928:
Hardly. Touchwiz is just a GUI. Oxygen OS is a full ROM, Like CyanogenMod 12.1 or ParanoidAndroid. And OxygenOS is one version.
[SuperSU] NeoLogY:
I thought TW is a full OS?(there is TW launcher, if that's what you mean by GUI)

Sent from here to there
[SuperSU] iamnotkurtcobain:
Touchwiz is the whole framework/ui/launcher on top of Android. It isn't just a skin or launcher.
[SuperSU] 089man:
The first time since many many years I used the pro version, if I Flash the stable version on bliss 3 3 build 4 rom, I stay on bootloop.... Any idea? Need im a other version for 5.1 1 lollipop? Where I found.... Beta version works with 5.1 1 lollipop and latest bliss rom?

I9100 Tapatalk, RR 5.0.2 Lollipop
[SuperSU] shaggyskunk:
Both the stable and beta versions flashed fine with 5.02 - 5.1 & 5.1.1 AOSP Roms - Could be (unlikely) a bad download - Which Recovery are you using - TWRP 2.8.6.0 is my choice - If you're not running the latest recovery - You may have to update it

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] 089man:
Now its works, issue in my side. Thanks for answer.

I9100 Tapatalk, Bliss 5.1.1 Lollipop
[SuperSU] john-mccue-grindal:
Keep up the good work!

Keep up the good work, youve got some real talent:)
[SuperSU] mikaole:
just tested 2.46 om M.

Knew it, but needed to test.

Not working
[SuperSU] DesignGrits:
What about Beta SuperSU v2.48? I assume not
[SuperSU] mikaole:
link to beta
[SuperSU] shaggyskunk:
You're posting a link to SuperSU beta 2.49 - Or you're asking for the link?

If you're asking - "Please" might be appropriate... XDA doesn't charge by the word.....

http://xdaforums.com/showthread.php?p=55256620

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] guratr:
Android M

Getting a bootloop on nexus 5 android M with beta
[SuperSU] Fallen Spartan:
But, does it have Klingon? :p

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[SuperSU] omyg:
does it work with unofficial "non-cf" rooted kernels, like this (latest for i9000) :

http://samsung-updates.com/rooted-stock-kernels-for-samsung-roms/

( you didn't have plans to release your version of XWJW5 XWJW6 kernels for i9000 ?)
[SuperSU] Gwystyl:
I've just run over my translation to Dutch and changed a few things. It's easier to understand which word is needed for a translation when you see it in it's context :). I hope it's now more consistent, but feel free to add/change my translations if they are not correct.

The program itself still seems to work correctly, and no translations are running out of text boxes as far as I can see.
[SuperSU] jna9000:
I thougt that superuser as well as SuperSU needs its own su binary which, when called, asks the repective app to grant or deny access.

I thought as well that these apps checks if the installed su binary is the one they need, and ask to install the right one if not. This check doesn't work with the preinstalles su for SuperSU, while superuser doesn't fail.

What should be the use to install superuser only to get su installed so that SuperSU's detection works... :)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[SuperSU] Chainfire:
Should work on any rooted firmware.

Major reason I released this test version! :)

Thanks you for your work. Changes will be incorporated next language update :)

If someone preinstalled Superuser's su, then correct, you need to install Superuser program before you can install SuperSU. This is because of how Superuser's su works. The other way around, I have fixed in my code. You can include SuperSU's binary, and Superuser would still be able to install and work.

SuperSU needs "root" access to install it's binary. Superuser's "su" binary will not grant SuperSU "root" access unless Superuser is installed. And thus, SuperSU cannot install binary.

There's nothing I can do about this. It's weird "su" comes preinstalled in any case at all !
[SuperSU] jna9000:
This tablet is rooted, but grants root to any app requesting it. So SuperSU already has root access to update su, but it hangs detecting it.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[SuperSU] Chainfire:
Can you possible find the "su" binary ( /system/bin/su, /system/xbin/su, or /sbin/su, usually) and post it here ?
[SuperSU] p1lo:
how to repace SuperUser (old) with SuperSU on MiniCM? CWM doesn't work.

Install supersu.apk, copy in system as superuser.apk?
[SuperSU] shark147:
Hi,

Delete or uninstall your "superuser.apk", then you can download and install new SuperSU v0.90 from market (google play).

@chainfire: why sometime PopUp Request "Grant or Deny" don't show? I have the last version v0.90.

Can You check?

thanks :)
[SuperSU] serpent2005:
I have a Galaxy N7000 and I'm seeing the error: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" whenever I launch SuperSU. Attached the su binary. I'll appreciate any help!

EDIT: My issue is finally resolved. I ended up flashing LQ3 using Mobile Odin and checking wipe data/cache and leaving the rest as default. When the flash finished and I booted into LQ3 I was experiencing the same problem -- I had root, but SuperSU would report the same error as before. I launched Google Play and searched for SuperSU and I was given the option to update the installed app. I updated and it worked after that.
[SuperSU] p1lo:
I've try to copy from /data/app/eu.chainfire.supersu-1.apk into /system/app/

delete old superuser.apk,

rename eu.chainfire.supersu-1.apk into superuser.apk

reboot the phone...

At moment SuperSu works... i will see in the future :D
[SuperSU] husharon:
I have the same problem :-(

This is my su file
[SuperSU] jna9000:
It's /system/xbin/su, but as superuser replaced it, I can't... I will try to get it, however. Trying to get it from another tablet.

I remember that supersu displays an empty string as version number (if this helps).
[SuperSU] DJSave:
Georgian translation done!

what else is needed from us translators?
[SuperSU] Chainfire:
Second multi-language test has been uploaded.

See: http://xdaforums.com/showpost.php?p=23427835&postcount=4

Various languages have been slightly modified, and the following languages have been added:

- Croatian

- Georgian

- Hungarian

- Korean

- Slovak

There is now also the option to switch between languages, in the settings tab.

Translators: some strings have been added ( http://www.getlocalization.com/supersu/ ). And if you have not done so already, check this SuperSU version to see if your language looks and behaves as expected.

I think this will be the last "test" before the first "mainstream" multi-language release :)
[SuperSU] p1lo:
added last italian words ;-)
[SuperSU] wanam:
Working on Arabic translation...
[SuperSU] hpchiu:
cwm update supersu work well on hTC one s Z520e
[SuperSU] diperakui:
Malay language complete! :D
[SuperSU] bla84diamond:
Russian

When we can see Russian language in app ?

Localization is ready ;)
[SuperSU] shaggyskunk:
Have a look at Chainfire's post here

http://xdaforums.com/showthread.php?p=61024946

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] CarboN Juniors:
I am having a problems installing SuperSU on my ZTE Blade S6. I cannot install the binary. I believe my phone is supposed to be done on 'Normal' but I have also tried it on the secondary option.

I have root my Blade S6 with kingroot as this is the only option at this time and would like to move to SuperSU...
[SuperSU] shaggyskunk:
Did you try just flashing the zip?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] CarboN Juniors:
Were would I get the .zip and how do I 'flash' it?

Thanks
[SuperSU] shaggyskunk:
The zip is in the OP of this thread (just like almost every Dev puts it)

You would flash the zip with a custom recovery - ie: TWRP

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] CarboN Juniors:
OK so I ran the zip then loaded up SuperSU however it still wanted me to update the binarys and one again failed ?
[SuperSU] shaggyskunk:
Did you uninstall the store build of SuperSU first? - If you didn't - do it now - Wipe cache and dalvik - Flash the SuperSU zip again - Reboot

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] CarboN Juniors:
I have also found this in my phones topic but I do not fully understand it

http://xdaforums.com/showthread.php?p=60818978

---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------

Will try now