yashsingh1/xdaforums huggingface dataset:
[SuperSU] billyho7993:
If I'm understanding you correctly no superuser from chaindd was not installed on my phone only superSU
[SuperSU] ajs1122:
Willing to help

I'm willing to help if possible on this too. I have an Evo4G LTE, HTC Dev unlocked, S-ON HBoot 2.09 Rooted. Basically, I took the Sprint OTA, and the unlocked and rooted using TWRP and SuperSU. Nothing special and I was basically just impatient for JB.

It does not appear that the binary install issue is something unique to the SuperSU app, but rather something that HTC and/or Sprint actively did to restrict access. I tried ChainsDD's Superuser app and while it does let you in the app, if you go and try to update the binaries it also does a hard reboot. Likewise BusyboxFree if you attempt to install does a hard reboot. Both AdFree and AdAway hard reboot if you attempt to update the hosts file. WifiTether also does not work. It basically says that everything is working but does not seem to broadcast. No SSID visible and it doesn't work using invisible either. If you try to reinstall binaries/configs, it doesn't allow it, but at least it doesn't do a hard reset.

I'm not sure if that is all common knowledge now, but I haven't seen a collection of issues related to binaries posted anywhere during my searches so I figured I would at least pass on what I've found.

I'm far from being a programmer, but I am willing to try some things out and do what I can to assist if needed.

-ajs
[SuperSU] rawintellect:
I have chainsDD's latest binary (flashable zip) in my manual root thread. So it won't even attempt to update. And you can access the settings without it crashing. Still the same boat though. Any app trying to write to the system partition will cause a hard boot:

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

or get it directly from his site: http://androidsu.com/superuser/
[SuperSU] ajs1122:
Thanks

Yep, I already grabbed that from your thread and did that last night. That's how I knew the same issues were happening in Superuser. I'm actually most interested in finding a workaround for the underlying issue. Wifi Tethering and Adblocking are probably the 2 biggest reasons that I root my phone and they are both broken at the moment. Really it's my own fault for taking the OTA. Just trying to help where I can.
[SuperSU] rawintellect:
You can use easy teather pro (if what you're teathering is a laptop or tablet with usb) if you don't mind using a usb cable. Or try foxfi for true wifi tethering. Heck you don't even need root! You can download the app here as it's no longer available on the market (after sprint cried about it)

http://foxfi.com/
[SuperSU] ajs1122:
Foxfi doesn't seem to work with JB (read it didn't but gave it a shot anyways). Tethering with USB isn't a great option for my tablet. It's a Transformer so I have USB with the keyboard but I typically don't have that along. Might try it if I get in a pinch tho.

I posted in the Q&A over at the EvoLTE page to move this convo out of this thread and not clutter it up anymore than it is. If anyone has any solutions tho, I'm all ears.

-ajs
[SuperSU] adell_:
It is in this thread. So many people flamed the one who reported the bug. Don't you remember that? Whatever, I am glad to see that the app is being improved again.
[SuperSU] cbbplanet:
i'm trying to temp unroot my phone in order to have access in an app (the app blocks all rooted phones)

however, I go into SuperSU, uncheck the box and disable supersu, but problem still persist in that app. I've heard from other people on the forum saying it worked for them so I'm just wondering if I'm doing something wrong.
[SuperSU] maluus:
Dear developers of the supersu. I don't know if anyone informed but after htc one s jb update there seem to be compatibility problem.

Note: I had posted this message in another post but I believe this is the right one :d
[SuperSU] rootrider:
+1

Binary can't be updated. Some apps get root access others don't. Busybox can't be installed and after each failure updating the binary, htc wants an error report. lol

Superuser doesn't work as well.

Please pm me if you want/need additional information.
[SuperSU] Jay Aristide:
There are cwm flashable zips of busybox.
[SuperSU] rootrider:
Found one that works with superuser. Thank you. At least Titanium is fully working again.
[SuperSU] lvtjul:
Hello, can you provide the link of the thread where you found the flashable busybox?

Thanks !
[SuperSU] rootrider:
Shurely. It's here.

You're welcome.
[SuperSU] :
+2

It crashes upon updating the binary, yet, strangely enough, still manages to give some of my apps superuser acces.
[SuperSU] PharmCAT:
SuperSU > Settings > Uncheck "Enable Superuser"
[SuperSU] macho3215:
SuperSU breaks mobile Odin Pro

Mobile Odin gives error 'mobile odin - error "could not locate superuser package"' after installing SuperSU. Is there a fix\workaround to this?
[SuperSU] Chainfire:
Update to Mobile ODIN v2.25.
[SuperSU] wackydroid:
Very slick!!! Everything works perfectly on TF101 and Evo 4G.

Happyhappyhappy!!! Joyjoyjoy!!!

:D
[SuperSU] jsgraphicart:
Even after all the updates, the settings tab still freezes the app. I don't know if this is a bug for everyone or just me.
[SuperSU] sparksco:
Disregard post.
[SuperSU] Chainfire:
Can you try a "clear data" for the app, see if that helps ?

Doest it just come up with a black screen, does it produce a "not responsing" popup allowing you to close or wait, or does it produce an error ?
[SuperSU] akamustang:
Perhaps someone could enlighten me as to what some of these problems and issues have been?
[SuperSU] DaX05:
I would like to know also. I haven't had any issues. If you're having issues please state SPECIFICALLY what your issues are. We might be able to help if we know what the problems are.

Beamed from my Nexus S
[SuperSU] Benzoman:
Using Task 14 Fat ROM on Samsung Galaxy Tab 10.1 GT-P7510.

Just received an auto update. Went to the app and it said binary update needed. Everything went great and its still functioning great. :D

I was worried since I had many problems, previously posted, with the first release, but everything seems fine still. Just thought I'd let you know.
[SuperSU] lowspeed:
How do i restore superuser?
[SuperSU] sparksco:
You can download the zip from Rom Manager and flash it in recovery. Then un-install SuperSu
[SuperSU] lpsi2000:
Chainfire, Great app and just purchased the license. I have a request due to an issue I have with an application which is checking for root. Your new app does hide "su" very well but it seems my app is also check for Superuser.apk and if that is installed then I am toast. However, for years I have been getting around this by rename the apk file. In the last six months the app has gotten smarter and the renaming of the apk file does not work anymore. So rename your apk right now works and I am sure it is because your app is not showing up in the app install list like the other Superuser.apk use to (e.g. superuser).

I am also certain the vendor will soon push an update to check for your app especially considering how popular this is and going to be. Since I don't want to put this app on blast here just in case their PPL are also here. I can PM you the market link of the app so you can check it out. I am sure this will go a long way of making root as stealth as possible.:D

Again great work, you have now retired all my fancy unrooting / hide scripts:p
[SuperSU] wonsanim:
Thanks Chain;)flashing now:D
[SuperSU] Chainfire:
Well, you can PM me the name and the app and I can check it out ...

However, you should be aware that the temp-unroot is not specifically built to evade detection and to always offer that. Simply because it is impossible. I have thought of a great many ways how to hide su from programs, from simple to complex, and there's always a way around, there will always be a way to detect.
[SuperSU] netban:
Hi mate, love the great SU replacement you have created!

I have ran into one problem but it is not your app. The problem is I just want to use SSU but everytime I uninstall SU, it is still there after a reboot :-( tried to delete via titanium and rom manager but to no avail.

I'm using NEAK 1.4 and UltraToxic 8.1, any help wod be greatly appreciated :-)

Thanks
[SuperSU] Mister_Mxyzptlk:
I know you can't keep up with every single app out there. But Google Play Movies is a hugely popular app. Is there any way you could at least get some kind of functionality in SuperSU to allow proper functioning of Google Play Movies?
[SuperSU] Chainfire:
No, I can't. Why not? Because I do not have access to Google Play Movies at all, because I'm not from the US.
[SuperSU] lpsi2000:
Agreed, but I have an idea that might work for my case and many others. I will explain the next time I catch up with you on IRC after you review my PM.
[SuperSU] DarkhShadow:
What's chainfires irc?

Sent from my ice cream powered Nexus S
[SuperSU] :
That still isn't a 100% working solution, is it? I mean, your "/system" directory still ain't writeable.
[SuperSU] kemeia:
Nice mate!

Problem solved. Thanks a lot :good:
[SuperSU] :
:eek: How?
[SuperSU] lvtjul:
thanks !
[SuperSU] rawintellect:
Chainfire you might want to contact mikeyxda as it seems he's solved the problem of the popup asking to update the binary. Now I'm not saying he's solved the reboots. I'm pretty sure that's still happening but here's his thread:

http://xdaforums.com/showthread.php?t=2048229
[SuperSU] osm0sis:
Looks like he didn't really "solve" it per se, just work around it:

Makes sense for a ROM since the binary will definitely exist (and be up to date), but sadly this isn't really an option for the public app.
[SuperSU] rawintellect:
Ok "worked around it". How is this NOT a viable option for the public release? Is it really necessary to check for the latest release upon opening the app? Superuser 3.2 doesn't do this. It gives you the option to check for the latest release. Which is better than the current situation.
[SuperSU] osm0sis:
Because the su file is bundled with SuperSU.apk, not separately downloaded via the app like in Superuser. SuperSU needs to check whether it needs to unpack its su binary or not. This also keeps the app and binary from getting out of sync, causing problems like it can with Superuser.
[SuperSU] rawintellect:
Well why would chainfire attempt to remove the popup then? It seems you're saying it's absolutely necessary for the popup to exist? Yet he did create a test zip a few pages back attempting to do this very thing.
[SuperSU] osm0sis:
Ah you're right in a sense, I had my wires crossed, it's the OTA survival backup copy check that's causing problems, not the main binary version check. Either way removing the check altogether doesn't seem like the best solution, now does it? It would likely break OTA Survival Mode by letting THAT file get out of sync or be missing.

Edit: One thought I just had for a viable workaround is to have the app make that OTA survival copy only if the option is enabled in settings, copying it fresh each time. That way no check would be required and hopefully wouldn't anger s-on. :good:
[SuperSU] rawintellect:
I didn't say remove it altogether. I said make it an option. Again go back a few pages he's trying to do this VERY THING. I see no logical reason to have that app attempt to update the binary immediately upon opening it. And apparently chainfire agrees as he's attempting to do this very thing.
[SuperSU] osm0sis:
No YOU didn't say remove it, but the post you linked DID. Why are you trying to strike an argumentative tone with me? I'm just trying to supply information, even if I got a detail incorrect.
[SuperSU] rawintellect:
I do believe this is EXACTLY what I've been saying. Sorry you didn't read it that way. It should be an OPTION in settings. It should NOT do this as soon as it opens.
[SuperSU] osm0sis:
Sorry but linking to a post in a ROM thread saying "he's solved it" when all he did was remove the check is not you suggesting chainfire make something optional, and there is no way to read it as such. Anyway, I'm hoping Chainfire can work out a solution that will make you happy. Best of luck. :good:
[SuperSU] rawintellect:
I'm not trying to argue. I'm stating facts. You're pushing a bad point. I didn't say remove the check. I said make it optional. You're tone has been argumentative from the start. I'll just leave you to your own thoughts and not comment anymore as you seem dead set on believing you were correct. You weren't. Chainfire was trying to remove the popup. Fact. There's no other way you can say that. But enjoy your condescending tone. I'm sure it's gotten you far in life. I'm done here.
[SuperSU] osm0sis:
Just because my posts aren't full of smiley faces doesn't mean they're angry or condescending, so I'm sorry you read it that way but any intonation you felt was just what you brought to the table in your reading of it.

Once again, take care. :):D:cowboy::cyclops::highfive::fingers-crossed::cool::good:
[SuperSU] Chainfire:
I wasn't trying to remove the popup - that would be easy. I was trying to make sure everything was set up right so the popup wouldn't be triggered (still not completely sure why it still is, even with the new ZIP - but as I can't test this, I have nothing to go on).

Anyways, after some more consideration, this is not the way to proceed, nor is making the update optional. SuperSU works entirely differently from Superuser internally (even though they seem to act similarly), as such, having an outdated binary is simply not an option - if the binary and user interface are out of sync, all sorts of weirdness could happen. They don't necessarily have to happen, but enabling this option would make my support email box explode even further.

Even with the way I originally thought to work around this has some serious drawbacks, on an S-ON system some features have to be disabled and/or changed or havoc could still be triggered. What I am currently thinking of doing is making a separate S-ON ZIP file that includes a /system/S-ON file or so, and SuperSU will disable any functionality related to writing to /system if that file is present.

But I haven't built anything yet, I'm quite busy with the holidays.

Simpy disabling the check - though the only option available for you right now - is not a proper solution in any way, and it could cause some serious trouble in edge-cases.
[SuperSU] My1xT:
hi, I have some trouble with my Samsung Galaxy S Wifi 5.0 (YP-G70) and the CWM sSU. when I flash it, it says that there would be no su binary and no one can be installed.

can you help me there???

besides, on Galaxy Note 2 (GT-N7100) and Huawei Ideos x3 (U8510) sSU works well with the pro.
[SuperSU] JohnKuczek:
The zip from the op works great on my Galaxy Nexus w/ TWRP, but I cannot get it to work on my Xoom Wingray w/TWRP. Has anyone had any luck with the zip on a wingray? If so, did you do anything special, or did it just work?

(CWR does not work on my Wingray, can't seem to find the internal storage, and won't mount the SD...)
[SuperSU] goodtimes50:
This is still happening occasionally, although it's not always as severe. Sometimes opening the SuperSU app will fix it, but it's still a problem. Any idea what might be causing this?
[SuperSU] dwmw2:
Using --command option with a non-root user

To check the SIP registration status of the built-in SIP client, I need to run the 'service' tool as the radio user:

su radio -c 'service call sip 5 s16 sip:0333340xxxx@a.speechless.aa.net.uk'

However, that doesn't seem to work. The '-c' option does, but only for running commands root with no alternative user specified.

I've worked around it for now by 'echo service call ...' | su radio. But that means I'm granting permission for an interactive shell (to Tasker) and I'd prefer not to. Am I missing something, or does this not work correctly?
[SuperSU] Chainfire:
This does indeed not work correctly. The commandline parsing code I copied from Superuser to ensure compatibility. Seems Superuser has updated that portion, I will probably fix only this specific case:

su <username> (other options)

(Though note I'm not actually sure this now works with Superuser, I just noticed they updated the parsing ;))
[SuperSU] Chainfire:
Voting for the new SuperSU icon is (finally) open !

http://www.chainfire.eu/articles/127/_Vote_SuperSU_Icon_Competition/

Cast your vote ... !
[SuperSU] simplelife:
Any chance to fix SuperSU .Zip , Mr.ChainFire ?

Happy New year .
[SuperSU] avataranjie:
Happy new year
[SuperSU] rawintellect:
I'll just leave this here:

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

With the screen shot that shows supersu is now working fine on hboot 2.09 with s-on. Thanks to flar2! Problem solved. No need for a modifed supersu removing the popup. No need for a seperate file for s-on folks limiting supersu actions. It works. I'm using the zip from post 1. I even bought the supersu pro. the /system partition is now writable for me. No reboots.
[SuperSU] Chainfire:
I was just going to start on the code for this. I'm happy I paused to check the thread one more time!

On to the next feature on the to-do list ...
[SuperSU] rawintellect:
Well I saved you some work sir. You might want to update post 1 with the link to flar2's thread? It might save you endless cries from us s-on folk saying "supersu keeps rebooting my phone"...just a suggestion sir. :D
[SuperSU] lancemoreland:
Just flashed it and all is good. So it was the kernel causing the issue not the hboot or was it his system write module that fixed the issue? Whatever the case Ad-free and everything else is working as it should.
[SuperSU] rawintellect:
The system write module is what actually fixes this issue. Each time you flash a new rom (or flash a new version of the rom you're using. Dirty flash or full wipe) you will need to reflash that system write module. Mikeyxda has included the system write module in his rom. So if you are running meanbean 1.9 or higher you won't need to reflash. Hopefully more developers will bake this into their roms and save us the trouble of having to do this.

The module that actually zaps the write protect in the Elemental-EVO-JB-v0.7.zip is located in /system/lib/modules/wp_mod.ko. The other one is just the oc module and I don't believe that's necessary to correct the write protection issue in /system. I think just adding the wp_mod.ko into a flashable zip will do the trick and allow us to use the purely stock kernel with no overclocking. It could theoretically even be added to supersu's zip by chainfire. After all if you flash this on a device that doesn't need it it can't hurt according to flar2 and it would DEFINITELY end any issue anyone has when flashing supersu on an affected device. I believe flar2 is encouraging folks to do just this very thing as mikeyxda has added it to meanbean 1.9 (as noted above).
[SuperSU] SecUpwN:
+1 VOTE for adding it to chainfires flashable ZIP! :)
[SuperSU] romeoh:
Can i just flash the zip on my stock rom or do i need to flash another rom after? I really wanna stick to stock.

Thanks in advance.
[SuperSU] TheByteSmasher:
Regular chainfire zip works fine on stock

Sent from my Nexus 4
[SuperSU] ChungHung.Chen:
Dear Chainfire,

Is any plan to re-support multiuser in Android 4.2 ?

By now I can't use TB to transfer my wife's data to 2nd user in my Nexus 7 (4.2.1).

Perhaps TB can do something, but is any plan or solution now?

Sorry to bother you and thanks for your great app.
[SuperSU] flar2:
HTC added something to the kernel in the latest JB updates that prevent writes to /system.

wp_mod.ko is a simple kernel module that disables the write protection (http://xdaforums.com/showthread.php?t=2059411). All that's needed is to insert the module. But it has to be done at boot, because if you make changes to the system partition and then add the module, you could corrupt the filesystem.

This affects the One XL, One S, Droid DNA, EVO 3G LTE and likely any new HTC devices or others that get updated to Jelly Bean running kernel version 3.4.10. Most devs are adding the module to their ROMs now.
[SuperSU] rawintellect:
flar2's new release 0.8 now has the option to NOT install the boot.img so as long as the kernel has init.d support you should be fine. For the record true stock kernels don't. But this really is just a modified stock kernel. You really should flash it.
[SuperSU] romeoh:
Thanks bro, I'll try it right now.
[SuperSU] Chainfire:
Sorry but that just isn't going to happen as OEM specific patches have no place in my ZIP. I have no problems with modified CWM ZIPs based on my own including said modules being posted in your specific device forums, though. But if anybody does do that, they should clearly mark that it is a modified ZIP and not my original.

Proper multi-user support is planned for the next update (but no promises)
[SuperSU] shaggyskunk:
There's an update for superSU on the store - 13/01/04 ;)

I would imagine that Chainfire will have an updated zip in due course.
[SuperSU] Chainfire:
Last update is 2012.12.04 actually... where are you seeing this ? Might it be related to Google's bug of not having any December recently ?
[SuperSU] shaggyskunk:
My bad:o I'd rebooted my n7 running aokp - saw the update for SU, and only read the 4 in the date - Sorry :o

Once I'd realized my error, I tried to edit my erroneous post, but kept getting invalid post id :(
[SuperSU] Parisatis:
Work great thanks !
[SuperSU] simplelife:
So you are no longer support flashable SuperSU .Zip ?

Thank
[SuperSU] Chainfire:
That's not what I'm saying at all.
[SuperSU] Magissia:
Hello, could we get a "always ask" option ? (in addition to ask, agree, deny)

Always ask would do the same thing "ask" does, but will check the "ask" box by default when the app request root acces.

Regards
[SuperSU] lancemoreland:
Nevermind. Did not read correctly.
[SuperSU] simplelife:
Apology for misunderstanding .Can you please explain why SU.Zip not working but SU. Tar work ?

Thank
[SuperSU] meier2009:
Does SuperSU installs a BusyBox?
[SuperSU] decmk:
No
[SuperSU] Magissia:
get a busybox zip, or install it manually from ADB while in recovery

Regards
[SuperSU] Perka:
Or just get busy box installer in play store :)
[SuperSU] dragxdk:
Thanks chainfire for this good app!! :D :thumbup:

Ps : just a little bug on my device with titanium, when i open titanium, the program don t ask nothing or not popup at all, then with another apps no problems.

I try to delete titanium and install again but i allways have the bug... Strange

tapatalked
[SuperSU] arnabJ:
question

Heyi!!

Am makin a custom rom. alls set jus one last thing. i have to root it.

How to do that?

am a newbie or noob watever u say.

my rom is flashing witout root n alls good. then i try to root it with stone boy's all samsung gingerbread root.ip but wen i open ur app aftr rooting it says:

THE SU BINARY NEEDS TO BE UPDATED.CONTINUE?

I PRESS CONTINUE.

IT SHOW UPDATING SU BINARY N THEN INSTALLATION FAILED. WAT TO DO?

ANY OTHER METHOD TO PRE ROOT MY CUSTOM ROM.

MY DEVISE DETAILS : SAMSUNG GALAXY POCKET DUOS INDIAN VARIANT GALAXY Y DUOS LITE.

MODEL NO. - GT-S5302

STOCK ROM N KERNEL.

I DNT HAVE BOOT.IMG OF MY KERNEL.

THANXXX IN ADVANCE.

LOOKING FORWARD TO UR SUPPORT.
[SuperSU] molesarecoming:
has anyone here experienced mounting issues or anything root/permission related?

looks like we cant mount system anymore, writing to config files fails. we havent touched supersu for ages since it always worked.
[SuperSU] My1xT:
maybe they changed sth. in Droid, so you should keep the bins always recent (in SuperSU that's no problem, with superuser there was a problem in the 3.1 binary, so I has to get the old one from the rom and reflash it, but now I use sSU Pro and I LOVE it).

but chainfire one question, may I put sSU and Pro in roms before I flash them, so I have sSU as System app and I dont want a security hole in uninstalling ssu pro -> no pin or alike, neither that my sister moves it on microSD or sth. alike)

and how will the license check done (on the Ideos x3 -> Cyanogenmod 7.2[Droid 2.3.6] are 2 Google accs [mine for payapps and easy remote install and hers])?