yashsingh1/xdaforums huggingface dataset:
[SuperSU] VivaErBetis:
Re: [01.02.2013] SuperSU v1.04

Hi Chainfire,

I guess you know it, but anyways: the described behavior still happens. I have just upgraded to 1.04 from GPlay and the system app option was lost (I know it's normal). Then, when I converted it to system app again all configuration was lost (again).

In fact I needed to restart in order to saw app in menu again but the config was lost before restarting because in order to reboot I use an app that need superuser and SuperSU ask me for permission.

If this can help; I'm using android 4.2.2 in a nexus4. If I can help more just ask me.

Thanks and best regards.
[SuperSU] Chainfire:
I didn't actually even try to fix this for 1.04, as the crash/freeze fix was too important to wait, but I'll look into it for the next version.
[SuperSU] ironia.:
R: [01.02.2013] SuperSU v1.04

I see an' init' app listed in super su

What is it? Tnx
[SuperSU] avkiev:
Security issue ?

If we have system with preinstalled binary su from SuperSU, then

if we doesn't install SuperSU or delete it then

all apps will obtain root if ask it, without any messages.

Is it normal ?
[SuperSU] Chainfire:
This is by design. If you remove the SuperSU GUI, the su binary always grants access. It also grants access from recovery, or when Android isn't booted up yet (this is before 3rd party apps can run).

This is by no means a security issue, this is documented behavior and exactly as intended.

If you want to unroot, unroot. If you wan't hasslefree root, uninstall SuperSU's GUI.
[SuperSU] avkiev:
Ok, clear, thanks
[SuperSU] MaestroOrg:
Hello!

I'm still having problem on an AT&T HTC One X. Whenever SuperSU opens I get a message saying that the binaries need to updated, but when I choose Continue I get an 'Installation failed' notification. Interesting the new option show up and the version number updates. This behavior occurs every time i open SuperSU.

Additionally, whenever I toggle the Enable Superuser option I get either an Installation Failed! or Uninstallation Failed! message depending on it's state (checked or unchecked). Doing a clearup for unroot also doesn't appear to work - SuperSU closes out but remains after a reboot. The same happens when choosing the option to install SuperSO into /system.

Also the notifications for mksh persist regardless of whether Trust System User is enabled or not.

At this stage I'm guessing something has gone significantly wrong with my install of SuperSU - but I'm somewhat flummoxed as to how to remove it and start again as the in-app options don't have any effect. :(

When AT&T finally push the Jelly Bean update will this likely remove SuperSU anyway, or worse could this interfere with the process?

Any help would be greatly appreciated!

AT&T HTC OneX on stock 4.0.4.
[SuperSU] shaggyskunk:
I'm not an expert, but from what I've read, yes. If your phone is running an older o/s maybe not, but any gingerbread for sure. There are two different threads on this... You may want to read both. It seems like there were some problems for some people.... But some have rooted phones with custom roms & kernels.

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] sparksco:
Read the OP! HTC you "Must" have s-off just like superuser or or writing to the system partition while booted might fail. All other non-htc devices you probably need the bootloader unlocked or something to that effect. Not really sure because I've only owned HTC devices personally.
[SuperSU] :
Chainfire i bought all your apps that you did so far to support all your work on Android devices but can you take a look at this post of mine?

http://xdaforums.com/showpost.php?p=23507770&postcount=2908

I had some serious issues with SuperSu so far which lead me to install the old superuser!

Can you have a look at it please?

Btw, all the lag and phone getting extremelly hot and lock happened after i did a restore with Titanium Backup but not giving root permissions and rebooting afterwards!

I tested both ways:

1) Full wipe, install checkrom, install SuperSu CWM, restore apps (just app.. not data) and rebooting without giving root permissions to apps!

And

2) Full wipe, install checkrom, restore apps (just app.. not data) and rebooting without giving root permissions to apps!

In the second option all went well.. no lag on booting, no overheating of the phone!

That's why i suspect it is a SuperSu issue!

Thanks in advance and keep up the amazing work you have done so far :D
[SuperSU] dimebagdan65:
Sorry but it doesn't say anything in the OP about HTC devices needing S-Off to use this. If you're unlocked via HTC's method and rooted you can install SuperSU directly from the Play Store... Works flawlessly on my Evo 3D 1.5 HTC Unlocked running ViperROM. Moved eu.Chainfire.supersu-1.apk to /system/app and deleted superuser.apk thru ES File Explorer, fixed permissions (again using ES), reboot, profit. Full root access and can temp unroot to watch Flixster and Play Store rentals
[SuperSU] PharmCAT:
S-OFF = root, no?
[SuperSU] zonbal33:
I have an HTC Rezound, obviously rooted it already has the original SuperUser installed. After I install SuperSU, there are two icons in my app drawer.

I have Superuser 3.0.7 installed and the new SuperSU. Do I need both of them? Can I delete the older one or do I need both?
[SuperSU] dimebagdan65:
No... I'm S-On and rooted. S-Off allows you to flash the boot partition from regular old CWM, RA or TWRP recovery rather than having to do it via fastboot USB recovery
[SuperSU] dimebagdan65:
See http://xdaforums.com/showthread.php?p=23516191
[SuperSU] PharmCAT:
Make sure SuperSU is working, no issues with the binaries updating when you open the app. And if all is well you can safely remove superuser 3.0.7
[SuperSU] Chainfire:
I can flash CheckROM later no problem, I want to get to the bottom of this problem. However, I suspect it's a combination of SuperSU and <some app>. Which root apps did you have installed ? Can you replicate the problem <without> restoring data ?

EDIT: Have flashed CheckROM v5 and installed SuperSU, so far no issues. Not sure if media scanner is taking longer than usual, but I don't notice any lagging or hanging ... yet.
[SuperSU] mike2nl:
Found the thread here yesterday in the evening.

Will do my tests on HD2, SGT7 and SGT 10.1 3G.

I'll report later about the tests...
[SuperSU] :
Well i have a lot of root apps but will make a list for you and pm it to you.. in checkrom notehd v5 some guys had the same issue has i did! Mate let me take a bath and ill pm you with that list ok? ;)

Edit:

pm sent!
[SuperSU] shaggyskunk:
Well after some consternation, I opened superSU & Damn... SMOOTH as Silk, It was as easy as falling out of bed! :p I'll be getting the paid version tomorrow!!

Thanks Chainfire!!

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] hanzi54:
I purchesed SuperSU but the installation faild, after I installed also the free version it seems everything is ok...

How do I uninstall "Superuser from ChainsDD" there is no uninstall option on my SGS2

Thx
[SuperSU] shaggyskunk:
First off, I'm pretty sure that the instructions said that you have to install the free version first.

The information that was provided, says to use esExplorer or rootexplorer to find the chainsDD superuser & delete it from there.

One thing that I'm not clear on, is if there is any problem in having both on the phone?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] Fallen Spartan:
There is no issue with having both on phone. As per Chainfire's quote, SuperSU is a full replacement

As for deleting chainsDD version. Use rootexplorer and delete it from system/app/
[SuperSU] dswaggz:
Can anyone tell y my phone tripping I initially installed the first release of this application lost root functions superwiped then reflashed can anyone "chainfire " help me

ⓥⓘⓐ ⓔⓘⓘ4ⓖ
[SuperSU] shaggyskunk:
Did you delete chainsDD superuser before you installed Chainfire SU?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] djaykid11:
Is there any way to use this app to temp unroot to take an OTA on Evo3D h-boot 1.5? I want to be able to update radios and so far there is no way to do it. I apologize if anyone asked this already. thanks in advance!
[SuperSU] mrlo:
Installed SuperSU Pro v0.75 from Google Play on SGNote running Criskelo Note v.7, AbyssNote ver. 4.1.

No problems at all. Work like a charm. All the apps, I'm using, that requires root work fine.

Thank you Chainfire for this great app.
[SuperSU] Chainfire:
I suggest using CWM, TWRP, or whichever custom recovery is used on your device, to flash the ZIP linked from the first post. If /system is not writable, some functions will still not perform as expected, but at least the basics should work after this procedure.
[SuperSU] hameerabbasi:
Re: [01.02.2013] SuperSU v1.04

I'm having an issue with SuperSU. Neither the prompt, nor the toast notifications pop up. The app is just put on hold during a prompt with no way to grant or deny access.

I'm using the busybox binaries instead of Samsung ones for sh, dd and mount, and my /system/bin/sh is set to

#!/system/bin/busybox sh
/system/bin/busybox sh --login $@

With the proper permissions (755). My busybox is in /system/bin
[SuperSU] :
Re: [01.02.2013] SuperSU v1.04

Did you flash it via cwm or play store DL?

Sent from my GT-N7000000000 using Tapastalker 2
[SuperSU] MountainX:
Similar problem here. I read all the replies in this thread and I don't see an explanation of the problem. In my case I have a brand new Nexus 4 that I unlocked and rooted. I installed Super SU from the market but I get the error "There is no SU binary installed,and SuperSU cannot install it.This is a problem!"

What is the cause and what is the solution? Thanks.
[SuperSU] meinnameisthase:
AW: [01.02.2013] SuperSU v1.04

Try flashing the zip file (see first post) in recovery... That will install the binaries too.
[SuperSU] MountainX:
OK, that worked. So are the instructions in the OP wrong? It clearly says you can just install the apk from Google Play. But that didn't work for me. Flashing the zip did work.
[SuperSU] hameerabbasi:
I actually used Exynos-Abuse on my Note 2, and did all subsequent updates via Play Store.
[SuperSU] ogre_x:
I don't think they're wrong. OP says that SuperSU needs a rooted device, i.e. an installed su binary. You need to get that in there once (for example by flashing the ZIP-file), Then the market version can update it after that.
[SuperSU] MountainX:
Good explanation. I think your explanation should be added to the OP, actually.
[SuperSU] lancemoreland:
What is the benefit of "Install SuperSU into /system"? Everything seems to work fine for me either way.
[SuperSU] My1xT:
for starters it isnt that vulnerable, coz without root you cant delete/uninstall it (so better set your permissions of root apps right) meaning that there's no way (@least with the correct settings) that someone uninstalls the gui and can do what he want...
[SuperSU] zodiaxe66:
blib
[SuperSU] lancemoreland:
If this was in response to my question above, I am not able to follow what you are saying.
[SuperSU] My1xT:
yes it was. well, lets try to explain it slower...

if you are rooted but have sSU as a normal app

the main problem is it you (or someone else) uninstalls it normally (over appmanager in settings or alike)

then there would be unlimited root rights

meaning that that someone can do what he wants

even if you have pro with root-pin

coz the binary has an "all allow" command when there is no GUI (Graphical User Interface/the app itself)

that is kinda dangerous...

and also

I think I heard that sSU in System can solve modding things or so, but here i am REALLY not sure...
[SuperSU] hameerabbasi:
I actually flashed over my ROM w/o wiping data (Stock Odin flash), and re-rooted using Exynos-Abuse, and updated SuperSU using the Play Store. That solved it, but I'm sensing there may be a bug if it's happening to people other than me. Did you happen to modify the sh binary?

EDIT: Try clearing Cache/Dalvik. I never tried that, it may work, and there's no harm in trying. The flashing cleared cache & dalvik automatically, so that may have been the problem.
[SuperSU] zodiaxe66:
Tried every trick I know, now I'm charging my phone and do a factory reset to see if this fixes it and if not i'll do a system wipe and reflash my rom..

All i did was upgrading to su 104 from su 102 and moved it to system like I have done since supersu was released.ATM most ROM dev's uses version 0.98..most stable I think.

Have a nice day:good:
[SuperSU] ChodaBoyUSA:
I received a notification that Titanium Backup was unable to get superuser access. Launching Titanium verified this fact. When I launched SuperSU, Titanium was not listed. I must have installed a new version of Titanium (as well as SuperSu and BusyBox). I was never prompted to Grant permission for the new version of Titanium. ???

I tried your suggestion and cleared Cache/Dalvik and now all seems to be working correctly. (Of course, I forgot to try just rebooting first to see if that was all I needed.)

Thanks!
[SuperSU] zodiaxe66:
Got my su prompt toast back by wiping cache/dalvik/system and reflash the rom..no data wipe was needed.

Got 0.99 version installed so gonna try upgrading to 1.04 from market.hopefully everything will go as planed and this is my last post here..
[SuperSU] dabeez98:
link not working... for the flashable zip
[SuperSU] offenberg:
Confirmed. Share the file? I kinda need it right now :)
[SuperSU] lancemoreland:
Check your PM
[SuperSU] offenberg:
Thank you :D
[SuperSU] sdeft:
Hi Chainfire

What is the purpose of the .ext dir & su in the system/bin directory ?

Apologies if this has been asked before.
[SuperSU] My1xT:
well, the su file is the binary, which puts the root rights into Android.

.ext directory? never heard...
[SuperSU] ogre_x:
Sv: [01.02.2013] SuperSU v1.04

Looks like a copy of the su binary in the .ext folder. Diff says that the files are identical. Probably using it when replacing the binary from the app?
[SuperSU] My1xT:
could be...

---------- Post added at 11:19 PM ---------- Previous post was at 11:02 PM ----------

but CF, why disable before nandroid???

and before Nandroid Bakup or Restore???
[SuperSU] o-l-a-v:
Will the zip version also root, like "SU_Busybox_Package"?
[SuperSU] chrone:
Re: [01.02.2013] SuperSU v1.04

No busybox, only su (the binary of superuser to gain root access) and supersu (the app that manages su).

Sent from my Nexus 4
[SuperSU] o-l-a-v:
Ok. So, if i want to update "SU_Busybox_Package" to include SuperSU v1.04, all I do is to switch the "Superuser.apk"? Will it work?
[SuperSU] chrone:
Re: [01.02.2013] SuperSU v1.04

Haven't tried that before. As far as i know, superuser and supersu are different app.

Sent from my Nexus 4
[SuperSU] I'm TheQuest:
Hi chrone

You are right, they are two different Apps and developed by two different Developers.

Take Care

TheQuest :cool:
[SuperSU] My1xT:
if you want to do that, you have to update superuser.apk and the su file(the binary)...

@chrone intrestingly either SuperSU and Superuser are named Superuser.apk in the flashable zip, so you cant say which one it is...
[SuperSU] chrone:
Re: [01.02.2013] SuperSU v1.04

Oh i see, that's why. :D never tried superuser from ChainSDD before. Hehe

Sent from my Nexus 4
[SuperSU] My1xT:
well I had it on my Ideos x3 coz It was preinstalled on Cyanogenmod, but exchanged with sSU, coz of problems with 3.1 binary

and sSU Pro is better...

and it is chainsDD
[SuperSU] o-l-a-v:
Who takes the challange? :)

Create SuperSU v1.04 version of SU_Busybox_Package.zip?

I included the original
[SuperSU] My1xT:
well, nothing easier than that...

just wait a bit.

Edit: that should do it.

contact me if there's something...

Edit2 sorry wrong file...
[SuperSU] o-l-a-v:
Thanks sir ;) Will try next time i flash stock Huawei fw
[SuperSU] My1xT:
no prob, we're all friend, and "sir"? well, i am 17...
[SuperSU] Sloth:
haha
[SuperSU] ImgBurn:
Where did you get this from:confused:

Contains some busybox & SuperSU v0.98.
[SuperSU] bsoplinger:
Re: [01.02.2013] SuperSU v1.04

Either that or my guess is that its for the protect

su across OTA updates setting. After all a copy of su must be squirreled away somewhere.

I asked this one ages ago. Whatever gets done to protect the su binary can mess up Nandroid. So the only safe thing is to turn it off to be sure Nandroid doesn't get confused.
[SuperSU] kobridge:
Couple of questions to CF and anyone -

1. does anyone experience the random reboot after installing SuperSUNoNag.apk?

2. CF, what's the right way to install the SuperSUNoNag.apk? For me, I created CWM flashable zip file with SuperSU and SuperSUNoNag together and placed into /system/app. Do you see any issue doing that?

I'm a Galaxy S2 user and I provided my ROM users SuperSUNoNag along with SuperSU. For me, I experienced several random reboot after I moved SuperSUNoNag.apk to /system/app. Before doing this, I didn't experienced any random reboot. All permissions are fine...

Here are 2 CWM flashable zip files -

one is with SuperSUNoNag and another one is only with SuperSU. I believe only with SUperSU doesn't have any random reboot issue.

Thanks!

SuperSu_104.zip (with SuperSUNoNag.apk)

SuperSu_104_SuperSUonly.zip
[SuperSU] calisro:
Re: [01.02.2013] SuperSU v1.04

no reboots here. my nonag is in data though...
[SuperSU] chrisneal:
How to install SuperSU when Superuser is already installed?

Hi all.

I apologize is this is already discussed in this thread. I did search, and didn't see it...but might have missed it!

I have a rooted Galaxy S3 with Superuser and watch to ditch it for SuperSU, but don't want to mess it up in the process. :) Can someone please give me the steps? With these root/su apps, I don't want to accidentally remove or not remove something, or reboot or not reboot, when I should :D

Thanks so much for your time.

Chris
[SuperSU] 3rdstring:
Re: [01.02.2013] SuperSU v1.04

Flash the CWM zip in the OP. It will replace Superuser with SuperSU
[SuperSU] hameerabbasi:
Just install SuperSU, update the binary by running it once, then delete /system/app/SuperUser.apk.
[SuperSU] chrisneal:
Perfect. Easy enough! Thanks.
[SuperSU] My1xT:
so I also did it on Ideos x3 which had su preinstalled, but I wanted to have sSU coz I have pro and so I can protect my sister from root...
[SuperSU] Chainfire:
SuperSUNoNag is not for standard flashables, it's only to include in your complete ROM flashable.

It shouldn't trigger any reboots either, sinces it just an empty file from a code perspective.
[SuperSU] My1xT:
I have a question, can I do sth. about sSU Pro that I dont always have to install it, everytime I install a new Rom, can I mod the flashable so that my license is in?

ONLY FOR MY DEVICES
[SuperSU] Xelio:
Hi, my Nexus 7 was running fine with SuperSU 0.99. But after update to 1.02 or 1.04, all apps can't get root permission. There is no popup of SuperSU. And I get following error form logcat

E/ShellInterface( 2407): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 2407): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 2407): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 2407): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 2407): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 2407): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 2407): runCommand error: Error running exec(). Command: [/system/bin/su] Working Directory: null Environment: null

E/ShellInterface( 2407): runCommand error: Error running exec(). Command: [/system/bin/su] Working Directory: null Environment: null

E/ShellInterface( 2407): runCommand error: Error running exec(). Command: [/system/bin/su] Working Directory: null Environment: null

I found there is no /system/bin/su exist, so I copy /system/xbin/su to /system/bin/su. The error of /system/bin/su gone, but still no root permission

E/ShellInterface( 1664): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 1664): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 1664): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 1664): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 1664): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 1664): runCommand error: write failed: EPIPE (Broken pipe)

E/ShellInterface( 1664): runCommand error: write failed: EPIPE (Broken pipe)

Could anyone help?
[SuperSU] AlxMAX:
I would like you the enlighten me about the meaning of the basics. From what I've read, I've learnt the app still warned about a newer version of the su executable. Will it still run even if I choose not to update the su executable? If I choose to update the su binary and the phone reboots, is there a way to recover it from somewhere and copy it to the right place in recovery mode?
[SuperSU] chrone:
Re: [01.02.2013] SuperSU v1.04

As posted by CF, flash the new su.zip with custom recovery will do the trick for you. :)

Sent from my Nexus 4
[SuperSU] damnation333:
Hey,

I am running CM9.1 and Abysskernel 2.0 and now found out I need SuperSu. Been trying to get it working, but no luck so far.

Tried the flashable zip. Tried the reinstall trick, but every time it tries to update the su binaries, I get a failed. I have working internet connection on the phone. Any workaround for my trouble?

Thanks.
[SuperSU] nibrwr:
Re: [01.02.2013] SuperSU v1.04

Do you have Superuser installed in /system/app? If so, simply grant SuperSU root permission in Superuser and voila
[SuperSU] damnation333:
Hey.

Problem is that superuser force closes all the time, so I cannot open it.

Just tried the following:

Nandroid to backup before Abysskernel (only flashed that today anyway; running DreamKernel). Here I can grant superuser rights to SuperSU and superSU updates properly. Then I flash Abyss and I get immediately the message that superuser isn't working and I can't setup SuperSu.

Any ideas why that is?
[SuperSU] calisro:
Flash Abyss kernel in recovery, then do a reboot recovery (not a reboot device but instead reboot recovery), then flash the supersu zip then reboot. That should work I think.
[SuperSU] damnation333:
fantastic! that worked now! :) Thanks guys for your help!
[SuperSU] eddydc1:
Re: [01.02.2013] SuperSU v1.04

could someone tell why i should use this? i have su whats working so why would i install this
[SuperSU] My1xT:
well Superuser is a nice app and so on, but Chainfire made this app, coz he had Problems with superuser, and I also had some...

if you are happy with superuser, it's ok, then you wont need this...
[SuperSU] goodtimes50:
I apologize, I know it's been a while. This did not fix the issue. I've done some messing around and I can confirm that running Fix Permissions in TWRP triggers the issue and that multiple notifications occur for a single root request. This happens even when "Show Notifications" is not checked.
[SuperSU] bsoplinger:
Re: [01.02.2013] SuperSU v1.04

I've seen the same thing, a bunch of notifications for what seems like a single event and ignoring my settings of no notifications. Is there something useful I can do to help gather information to get this fixed?