yashsingh1/xdaforums huggingface dataset:
[SuperSU] rj.camargo:
Hi, I'm trying to root my HTC One M8. I'm on lollipop dev ed. I installed the flashable zip via recovery but when I run the SuperSU app it tells me that the binaries need to be updated but none of those options work. I'm not rooted so I wanted to remove the app completely, anyone can help with this? If I try the "full unroot" option within the app I get a bootloop until I flash the SuperSu zip again (still doesn't work)

Thanks
[SuperSU] IsolatedKM:
its the best
[SuperSU] stynatu46:
This has probably been answered several times, but why doesn't it update from the play store (does it even get updated there)? Also the app is gone from my app drawer so i can't access it at all. It can only be uninstalled in the play store. Nonetheless it's a great app.
[SuperSU] AA1973:
Most probably your ROM dev included it in Settings.
[SuperSU] occtec:
[MENTION=631273]Chainfire[/MENTION] since N5 5.1 images are out for the N5 and people are already downloading the new images will we need to wait for an update to cf-auto root to be updated also, since the new update included a new bootloader or will the current cf-auto root suffice??

Thanks mate
[SuperSU] XMayhem2099:
It might work

I just flashed the 5.1 image and used the old lollipop cf auto root. I got root access and was able to install twrp. I haven't ran into any problems yet
[SuperSU] Ja_som:
Also, after you use auto root, you can flash new bootloader again.
[SuperSU] SyCoREAPER:
News flash. If it isn't working as it should I can't use the features now can I. Plus any good developers provide support to paying customers.

I know chainfire is a good developer, just wansnt sure where he was

SuperSu is refusing to update the su binary on my tablets. Ordinarily I'd just flash manually but the tablets don't have a custom recovery. It was suggested that I download the zip and extract the binary manually. Where I am stuck is do I use the x86 or x64 binary? The tablet has an x64 processor but thought OS before Android was only x86. So am I going by processor type or OS?
[SuperSU] egingell:
You completely missed the point of my post. You don't pay for priority support. You get the same level of support regardless of whether you paid for pro or not.

That said, did you actually install the pro app? It's a separate app that activates the pro features in the main app.

Edit: Also... Did you try to flash via recovery?

Edit again: There are many apps that will tell you what your processor architecture is or, possibly, the manufacturer's website.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] SyCoREAPER:
And same goes for you.

I don't except priority support, but do at least expect an auto-response with within 2 weeks.

Did you just switch from iPhone to Android?

Read my post, I don't have a custom recovery nor is one available.

AGAIN, READ MY POST. I said I know what my processor is, I don't know WHICH BINARY TO USE.
[SuperSU] commencal661:
If you REALLY know what processor you have, then it's easy to find out whether it's 32bit or 64bit and consequentially, depending on what version of Android you're running, which binary you need to use. Or you just started using the internet and do not know what Google is? And lose that attitude, it'll get you nowhere in life.
[SuperSU] artur0588:
Hi, [MENTION=631273]Chainfire[/MENTION].

Can you look in attached su binary which provided by venom team? This one successfuly load my init.d script with command:

su --permissive-adb

then i can success use command:

adb remount
remount success

Your binarry give me adb permission with init.d script or adb root command but adb remount command return with:

remount of system failed: Permission denied
remount failed
[SuperSU] NeoLogY:
Guys(or even gals). Keep it cool here. No need to fill up all the page. I am no moderator or op, just same as both of you. Please.

Have a good day all.

Peace and out.:thumbup:
[SuperSU] Frank Westlake:
Try running the SuperSU installation script.

- Extract 'META-INF/com/google/android/update-binary' from the SuperSU zip archive to an executable location. Maybe '/data/local'. Make it executable 'chmod 700 update-binary'.

- Edit that script, comment out the two umount commands at the end:

#umount /system

#umount /data

- Change locations to a directory where the script can unzip the zip, i.e.

mkdir /data/local/junk

cd /data/local/junk

- Run the script with an unused arg, fd for stdout (1), and the path to the zip archive, for example:

/data/local/update-binary x 1 /sdcard/Download/UPDATE-SuperSU-v2.46.zip

- When it is finished immediately reboot.

The script will print a lot of error messages, that is normal.

ADDED:

I just took a closer look at the script and it will need more editing. Change the 10 lines below

ui_print " Extracting files"

to:

#cd /tmp; # You are already at your work dir.

#mkdir supersu

#cd supersu

if [ -z "$BIN" ]; then

unzip -o "$ZIP"

BIN=$PWD/$ARCH

COM=$PWD/common

fi

Those 10 lines assume that you already made your junk directory and changed to it before running the script, like I described earlier.

Frank
[SuperSU] SyCoREAPER:
Your post was non-constructive since you didn't answer my question at all.

Lastly, how do I Google something that is one of the few (if not only one) of its kind? I am not aware of any x64 bit processor Androids, only arm64 which is a completely different architecture.

Agreed.

NOW

Back to the original question. Is the SU binary based on the processor architecture or OS?

*************EDIT************

Just saw [MENTION=5545307]Frank Westlake[/MENTION] answered.

Great, Thanks! I will give that a try
[SuperSU] ayemossum:
5.1?

Has anyone tried this on 5.1 yet? I'm going to install either way, but just wondering.
[SuperSU] Psycho Orange:
Yep. SuperSu 2.46 works exellent on 5.1 Stock.
[SuperSU] explorer-10:
Sooo, OTA survival mode isn't apparent on the latest SuperSU running 5.0.1?
[SuperSU] Frank Westlake:
It seems to me that when SuperSU updates the binaries by the "normal" option it probably does just what the installation script does, so if SuperSU failed to update them then this script will probably also fail. But at least you will have a little more knowledge of the situation.

Frank
[SuperSU] Pkt_Lnt:
Lollipop changes removed the ability for that to work.
[SuperSU] SamuriHL:
Just to add to this, some devices like the Nexus 6 can't be OTA updated if they've been rooted as they hash the system partition (more or less) rather than individual files. So the su binary and/or any changes you've made to the system partition will cause the assertion check on the system partition to fail and the OTA to abort. This makes su survival useless, as well, because it would have to be stored on the system partition somewhere, and that changes the hash and fails the OTA assertion. Fun, yea?
[SuperSU] Pkt_Lnt:
I know. I have read that and understand.. I just posted the easy answer to the question because that is what 99.999999999% want.
[SuperSU] Frank Westlake:
It works on my device. I've simplified the process by making a wrapper script that prepares things for the SuperSU update script and then reboots to cause the changes to become effective. I used it to downgrage to 2.40 and verified that 'su' and SuperSU were both 2.40, then I used it to upgrade back to 2.46. '2.46' has a SuperSU of 2.46 and a 'su' of 2.45 and both were restored.

Run the script with a path to your SuperSU zip archive:

update_su /sdcard/Download/UPDATE-SuperSU-v2.46.zip

Here's the script:

#!/system/bin/sh

id|grep "0(root)"||(
echo "This script must be run as root.">&2;
exit 1;
)

if [ ! -f "$1" ]; then
echo "The command line must contain the path of the SuperSU zip archive.">&2;
echo "Example: $0 /sdcard/UPDATE-SuperSU-v2.46.zip">&2;
exit 1;
fi

mount -o remount,rw /

mkdir /tmp
cd /tmp

pwd
unzip -o "$1" META-INF/com/google/android/update-binary
mv "META-INF/com/google/android/update-binary" update-binary
chmod 700 update-binary
ls -l update-binary

if [ ! -x "/sbin/sh" ]; then
linked=true;
ln -s /system/bin/sh /sbin/sh;
else
linked=false;
fi;

su --version
./update-binary x 1 "$1"
su --version

if [ $linked ]; then
mount -o remount,rw /
rm /sbin/sh;
fi;

reboot system

I just noticed that I ran this with '/system/xbin/bash'. I changed it to '/system/bin/sh' but have not tested it with that configuration.

ADDED:

This script is for updating SuperSU while booted into System, not while booted into Recovery.

Frank
[SuperSU] ayemossum:
I can confirm that. I'm up and running on 5.1 with SuperSu 2.46.

Now to wait and see if the annoyances of 5.0 have been solved....
[SuperSU] fix-this!:
our dev was able to root and give us twrp on the new moto e 2015 lte model but it seems to break any and all camera after a reboot. he suggested setting selinux to permissive but that doesn't fix the issue. i did an experiment and unrooted then used the beta 2.43 superuser and the camera works but you have a slower boot time and we loose audio. was wondering if anybody has an ideas or solutions? im going to assume the issue we are having is from superSU.
[SuperSU] gatoremt:
HELP. My phone was updating the new SU Binary. I selected cwm/twrp and now I am in boot loop?? I am using a Note 3
[SuperSU] dimebagdan65:
I'm experiencing this, too, but it's just a minor annoyance. Actually, I don't mind it that much on boot up, because then I know when the phone is ready to rock
[SuperSU] wanam:
Hi Chainfire,

I want to thank you first for your amazing work, I have an issue on Supersu with multilingual support, i added Arabic language to my sgs2 Rom.

On the first boot with Arabic language set as system lang, when i launch an app that needs root access :

i get the prompt to grant access

i choose "Grant", the app hangs for a while then it gives me a popup that the app didn't manage to get root access,

then after some seconds i get the famous Supersu popup explaining the app has granted root access

i check in Supersu app, and i see that indead the app is marked as trusted app

when i launch the app again, i got the same popups as above

if i change the language to any other one including the Hebrew (which i just added too) it works! but no luck if i go back to the Arabic again

Here is my Logcat :

W/System.err( 4092): java.io.IOException: Error running exec(). Command: [/system/bin/.ext/.su, -v] Working Directory: null Environment: null
W/System.err( 4092): at java.lang.ProcessManager.exec(ProcessManager.java:211)
W/System.err( 4092): at java.lang.Runtime.exec(Runtime.java:168)
W/System.err( 4092): at java.lang.Runtime.exec(Runtime.java:241)
W/System.err( 4092): at java.lang.Runtime.exec(Runtime.java:184)
W/System.err( 4092): at eu.chainfire.supersu.SuperUser.a(Unknown Source)
W/System.err( 4092): at eu.chainfire.supersu.Installer.a(Unknown Source)
W/System.err( 4092): at eu.chainfire.supersu.MainActivity$1.a(Unknown Source)
W/System.err( 4092): at eu.chainfire.supersu.MainActivity$1.doInBackground(Unknown Source)
W/System.err( 4092): at android.os.AsyncTask$2.call(AsyncTask.java:264)
W/System.err( 4092): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
W/System.err( 4092): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
W/System.err( 4092): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:208)
W/System.err( 4092): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
W/System.err( 4092): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
W/System.err( 4092): at java.lang.Thread.run(Thread.java:856)
W/System.err( 4092): Caused by: java.io.IOException: No such file or directory
W/System.err( 4092): at java.lang.ProcessManager.exec(Native Method)
W/System.err( 4092): at java.lang.ProcessManager.exec(ProcessManager.java:209)
W/System.err( 4092): ... 14 more

I don't know what file or directory he is looking for in the displayed exception.
[SuperSU] Stupifier:
At least I see others are having the same thing. It basically just flashes constant toasts for a while at boot......then stops. Minor annoyance....but still an annoyance. Figured I'd let the powers that be know.

***Update***

So I just noticed that some of the toast messages are from the OLD Super User App. HOW IS THIS POSSIBLE? The app is gone....it is no longer listed in /system/app folder. Any recommendation/help?
[SuperSU] Evengard:
Exactly the same behaviour with ConnectBot. When you open a localhost prompt and type inside "su", you get no request or whatsoever, just hanging here waiting for something until you abort with ctrl+c. No problems with the superuser app...

KingCobra3D ICS from 16/05/2012, HTC Evo 3D
[SuperSU] segv11:
Turn off "full text" logging for all your terminal apps, connectbot included. The full text logging is making stdin a pipe instead of a pty, and this is confusing the shell into not giving you a prompt, and not echoing your commands, because it thinks it is a non-interactive shell.
[SuperSU] thelucky:
SuperSU is a very nice replacement for superuser. I am flashing this every time I install a release of Cyanogen 9.0 (unofficial) beta on my desire z.

Thanks for the efforts.
[SuperSU] Evengard:
Where can I find that?
[SuperSU] shaggyskunk:
SuperSU - settings - logging *change setting to ACCESS ONLY.

Sent from Down The Rabbit Hole, using Tapatalk 2.
[SuperSU] segv11:
Or if you only want to make the change for specific apps, open SuperSU, click on the app on question, and set logging to "access only" repeat for the other terminal apps.

If you do it this way remember you need to redo it after an app update comes out.
[SuperSU] bsoplinger:
Does it really need to be redone when an app update occurs when you set on a per app basis? Or did you mean a SuperSU update?

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[SuperSU] segv11:
Unless you de-select the "reauthentication" checkbox in SuperSU settings, you need to redo per-app options when the relevant application is upgraded, because SuperSU will consider the upgraded app to be "new" and will forget your prior prefs.
[SuperSU] bsoplinger:
Ah fooey, I was hoping I misunderstood you. I'll make a feature request then. I can understand the reauthentication from a security point of view and actually like that. But just because the version number is different the way I want SuperSU to handle the app doesn't change. So an option, a preference, would be useful.

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[SuperSU] segv11:
Yeah, that would be nice: reset the app's "access" pref to "prompt", but leave the other prefs alone. But I don't mind cause I don't need to update my root apps that often; especially not the ones like terminals with non-default prefs.
[SuperSU] Chainfire:
If you set the global option to access only (preferences screen), if you update an app with re-authentication it will prompt you (once) and set logging to access only by default.

(or at least it should)
[SuperSU] championswimmer:
do you intend to release the sources, (maybe partially, for only the free version) at any point of time in future??

because i see the potential of this to replace the older superuser app in open source projects like CM and AOKP
[SuperSU] segv11:
This has been discussed to death on this thread, and CF has good reasons _not_ to release source. He is OK with including the free version of the su binary and APK in custom ROMs.
[SuperSU] shaggyskunk:
+1

Sent from Down The Rabbit Hole, using Tapatalk 2.
[SuperSU] ArmanUV:
Sorry if this question has been asked before: What is the recommended procedure for someone who flashes CM9 every night and doesn't want to open SuperSu Pro after each boot to update the binaries? Is this ok:

1. Install supersu and pro from market

2. flash cm9 update and the cwm supersu version in recovery

3. reboot and profit?
[SuperSU] lainemac:
Love what you're doing Chainfire.
[SuperSU] rasengan82:
Do you need busybox to install the SuperSU CWM flashable zip?
[SuperSU] gyongyosimate1:
Alcatel Onetouch Idol 2S

Binary update still doesn't work on my Alcatel Onetouch Idol 2S (TCL 6050Y). Either with normal and CWM recovery mode. :(
[SuperSU] Frank Westlake:
Hold [VOLUME_UP/POWER] while it is booting, or boot-looping, then at the download-mode warning cancel download mode.

Frank
[SuperSU] bgmg:
[MENTION=631273]Chainfire[/MENTION] just an fyi...the su binary for 2.46 says 2.45. See pic
[SuperSU] ianpocks:
Which is the difference between Su free and Su pro??? Are there more features???? Thanks for all

Enviado desde mi GT-I9300 mediante Tapatalk
[SuperSU] Mike B.:
Those are the correct current versions. The GUI app is updated more often than the binary. When SuperSU needs a newer binary, it'll tell you.

---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------

It's all explained in the first post of this thread! ;)
[SuperSU] bgmg:
Thanks Mike. Re-read the entire posts 1-3 and in regards to our discussion, I only found this reference:

"Issues installing / updating binaries ?

There's a thread for that: http://xdaforums.com/apps/supersu/support-update-failures-t2907365"​

I then read the entire op of that thread. Chainfire stated in that op "With all major changes to SuperSU, there are updates to both the GUI and binary. The GUI is the part you see on screen, the binary is what allows other apps to actually acquire root access. The first time you open SuperSU after such an update, it will attempt to update the binary to the latest version."

This does not really say that the gui and binary are not supposed to always match. Just in case they are supposed to match, I thought I'd let chainfire know. It is possible he may have just forgotten to increment it. I'm I also a coder, and I know first hand how easy it is to miss something like that, especially when you are your own tester.

If I missed something, please let me know. I'm as human as the next guy.

Either way, it is an awesome app and working great :)

Thanks chainfire and know that I bought all your pro apps to help the cause. :)
[SuperSU] fix-this!:
does superSU seem to work correctly on arm53 cortex based models like the moto e 2015 LTE? seems to break our camera and im trying to find a solution. until we get custom kernels with selinux set to permissive by default users like myself have to unroot. any advice would be appreciated.
[SuperSU] rj.camargo:
Still no help with this? I can't seem to get this thing to work.
[SuperSU] Frank Westlake:
I don't completely understand. Is this a failed root attempt? From what you say I can only guess that the su binaries were installed through Recovery but when you rebooted 'su' was somehow deleted but the other binaries remain. Is that true? I can't see how else you would be "not rooted" and still need to "full unroot".

It seems to me you should flash SuperSU in Recovery again and hope it stays, or else in Recovery manually delete all the su binaries.

Maybe you can provide more information, and don't count on someone searching for anything you've already posted on the matter.

Frank
[SuperSU] rj.camargo:
Sorry if I've not been clear. I wanted to full unroot because the zip file didn't work so I thought maybe if I removed everything and tried again it would work. It didn't. I've flashed SuperSu many times with no luck. Perhaps you could tell me how to remove all su binaries through recovery?

The only extra information I have is that when I try to update the binaries via twrp (through supersu app) the app doesn't do anything, neither by trying the "normal" way. I'm on stock lollipop.

Thanks for your help
[SuperSU] Frank Westlake:
The easy way is to extract 'META-INF/com/google/android/update-binary' from the SuperSU zip archive and comment out all lines that write files to the device, then put that file back in the archive and install it through Recovery. The script deletes everything 'su' before writing new 'su' stuff, so your modified script will be an "un-root" script. There are more things you could comment out but what I've said is the minimum necessary. It might be enough just to insert an 'exit' after all the deletions have been done, but I'm not looking at the script now to be certain.

ADDED:

Instead of commenting out lines (there are many), find the line

ui_print "- Creating space"

and insert these two lines just above it:

rm /system/toolbox

exit 0

The file '/system/toolbox' is created at the beginning and deleted at the end, but we are now exiting earlier than the end so we delete it earlier.

Frank
[SuperSU] Taomyn:
So is there somewhere that provides instructions on how to perform an upgrade from 5.0.1 to 5.1 using an extracted factory image? I did it for 5.0 to 5.0.1 for my old N5 without losing my settings/data but I can't remember where I found the guide.
[SuperSU] SamuriHL:
There are numerous ways to do it. Extract all the files and flash them manually using fastboot, use my house of Nexus, or remove the userdata partition image from the update zip and remove the -w from the flash all bat file. But this is quite off topic for this thread so if you need further help hit me up in pm.
[SuperSU] planb234:
Are you using a custom recovery? A custom recovery allows super user top be reflashed with every boot. If you do not want to install a custom recovery then you need to set your system to official. Try the xposed installer and wanam xposed.

---------- Post added at 03:15 AM ---------- Previous post was at 03:10 AM ----------

I think that Mr Chainfire should go ahead and charge for his app to get it the first time then we wouldn't have to down load the pro version every time.

---------- Post added at 03:17 AM ---------- Previous post was at 03:15 AM ----------

It is easy if you back it up. If you sync with Google it will also automatically upgrade. With settings.

---------- Post added at 03:20 AM ---------- Previous post was at 03:17 AM ----------

If you don't want a custom recovery you can install super user with ADB.

---------- Post added at 03:26 AM ---------- Previous post was at 03:20 AM ----------

I believe he put the solution in the pro version. It has an option to maintain super user through root. For those that are to cheap to pay the man for his work you can reflash manually each time.

---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------

There is no way for anyone to know which apps will need permission. For every one awesome developer like mr Chainfire there is 300 slimy pieces of filth that will attach themselves to your device and rape your network. Super user control is a high security risk and should not be used if you don't know what you are giving it to. I kid of course. Take control but have a back up. Super user is not a security app it is an all access pass. If you don't know say no.

---------- Post added at 03:41 AM ---------- Previous post was at 03:32 AM ----------

If you want to get rid of kings you can uninstall using ADB. Or you are you can probably just install another custom recovery. Try TWRP. Once you change your recovery you can install chainfire with odin or flash in the recovery

---------- Post added at 03:47 AM ---------- Previous post was at 03:41 AM ----------

The most important difference in the pro version is that you paid for some amazing work. The next is the pro version has the option to attach to the recovery so it maintains through reboot or new ROMS. I personally flash chainfire on as the last install on any rom so i know i got it.
[SuperSU] Fant0m3:
I think u may not of understood. I know what apps should and should not have access. I was thinking more or less like how titanium backup has theirs configured your device and settings are linked to a generated ID that is made and saved to your SD card on the first run. You are then prompted after rei stalling app to restore said ID all I'm saying is the same as that but it would restore your settings and lapps that where only previously saved by u that is all...,.I love this app I was just trying to give an idea no biggie either wwa. I was just providing a thougbt .

Cheers and keep up the work!!!! Out shines any others I've used