yashsingh1/xdaforums huggingface dataset:
[SuperSU] Magissia:
Do you need one in hand all the time or if someone lend you one it would do the trick ?

Regards
[SuperSU] gpzbc:
replace superuser with supersu

I am wondering if someone might be able to help me out?

I originally rooted my GNex Verizon with superuser. I recently discovered supersu and decided I wanted to try it out. So I installed supersu from the play store, granted it superuser permissions, updated it, and verified that I still had root access, and I did. Then I went into my file explorer and deleted the superuser apk from the system/app folder. Everything seemed to work perfectly. However, every time I flash a new rom, superuser comes back and takes over supersu.

I can fix it by simply repeating the process I described, but I am wondering if there is a better method for me to replace superuser with supersu that doesn't require me to redo it every time I flash a new rom.

Thanks for your help.
[SuperSU] 3rdstring:
Grab the update . zip from the op & flash it after you flash your ROM
[SuperSU] gpzbc:
Sounds good. I will give it a try.

This may be a dumb question, but will I have to flash it every time I flash a rom?

Also, it says it is CWM flashable. Can I also flash it in TWRP?

Sorry for the noob questions.

Thanks
[SuperSU] Pons:
Yes, and maybe. Depends on which version of TWRP you have, and which update-binary he's using. TWRP recently came out with an update that made all the older binaries incompatible, much like when CWM made everyone switch to edify from amend.
[SuperSU] gpzbc:
Thanks for the reply. I was feeling adventurous so I went ahead and tried it. It worked fine for me on TWRP 2.3.2.1.

Thanks again for your help.
[SuperSU] Gradjevinac:
Can i flash zip from 1st post on my HTC Sensation to gain root acces again?

I instaled custom ROm and lost root acces :)
[SuperSU] meinnameisthase:
Yes, you probably can. Or you can a least. Give it a try. ;)
[SuperSU] myepicyear:
Comment deleted. My sincerest apologies for encouraging someone's work. :o
[SuperSU] Perka:
This should be in q&a section?
[SuperSU] osm0sis:
It's about the SuperSU icon competition and the reasons behind it, so I don't think so, no.
[SuperSU] adell_:
The easiest way is flash SuperSU after flashing your ROM.
[SuperSU] gpzbc:
Thanks for your reply.
[SuperSU] myepicyear:
10char
[SuperSU] gpzbc:
Well, I answered my own question. I flashed a new rom without flashing supersu and sure enough superuser came back and deleted supersu. I just can't seem to get rid of superuser!

I guess I have to flash supersu every time I flash a new rom.
[SuperSU] Mac of York:
That's correct. Flashing a rom wipes system and any system apps such as supersu are overwritten.
[SuperSU] gpzbc:
Oh, I didn't know that. Thanks.

Then why didn't I ever have to flash superuser when I had that installed? I flashed roms all the time and superuser maintained itself just fine. Is it possible that superuser is baked into the CM10 nightly roms that I am flashing?
[SuperSU] bombadier:
What I do is open up the Rom zip,delete the superuser.apk from system/app and copy SuperSU's superuser.apk there, copy the su binary to system/xbin and then flash the ROM,job done
[SuperSU] droopyar:
supersu rocks

Supersu is by far the best tool for rooted phones management. I have post in cyanogenmod to use this instead of superuser.

I am interested in hiding the icon of supersu in applist, someone knows how to do it?
[SuperSU] Roberto_Lim:
I just keep SuperSu on my SDCard and flash it right after flashing a ROM. Sometimes without realizing it I replace it with itself :rolleyes:
[SuperSU] Pkt_Lnt:
Because the developer of the ROM you use includes superuser in the zip, so it installs when you flash the new ROM zip.
[SuperSU] shaggyskunk:
I do have a question. I'm running Liquid rom atm, and I don't think that this was happening on cm10, but the 99 version doesn't survive a simple reboot? If I go into recovery & flash the zip, after reboot I still have to update it from the store?
[SuperSU] gpzbc:
That makes sense. Thanks guys.
[SuperSU] cebs:
Galaxy Note II N7105 4.1.1

I'm on a stock rom and i tried to instal supersu and recovery and i not able to complete anything...

I used Samsung Galaxy Note 2 Toolkit v2.3.1...

I do everything and something is going rong...

Supersu says: "There is no SU binary installed,and SuperSU cannot install it.This is a problem!" and i still with no recovery...

Tried with superuser but no results

With stock recovery i'm not able the flash with the internal memory, only external...

I tried several times and the result is always the same...

ROM: JRO03C.N7105XXALIJ

Kernel: 3.0.31-240505

se.infra@SEP-76#1

SMP PREEMPT Wed Sep 26 21:28:21 KST 2012
[SuperSU] polobunny:
Problem isn't related to SuperSU, you simply haven't rooted your Galaxy Note II right. Ask in this thread, which is the toolkit thread rather than here:

http://xdaforums.com/showthread.php?t=1923956
[SuperSU] bostonbassman78:
Sounds more like u missed the step of unlocking your boot loader

Sent from my Paranoid Android Gnex
[SuperSU] cebs:
The problem is not with the toolkit because i had donne this before os version 4.1.2 and everything went fine... :)

Where can i find how to unlock boot loader?

Thank you all guys
[SuperSU] Jay Aristide:
From your PC command prompt, type "adb reboot-bootloader". When it reboots into fastboot, type "fastboot oem unlock". Your n7 will wipe all userdata (including your sd card) and reboot.

---------- Post added at 04:55 PM ---------- Previous post was at 04:52 PM ----------

P.S. Toolkits suck. This is a nexus device. Install adb and fastboot and do it manually :) Give a man a fish/teach a man to fish and all that

Edit: LOL, didn't realize I wasn't in a nexus thread... Toolkits still suck, though.
[SuperSU] benlm72:
SuperSU and freezing

Hello,

I'm testing a build that includes SuperSU to grant root rigths. I've noticed a strange behaviour : when an app requests root rights for the first time, I have a message from SuperSU asking me to allow/deny access. Then, when another app requests rights for the first time, the same message is very long to come, sometimes it doesn't come. In these cases, there's no root request logged (log is set for access). It seems to that app having already asked for root rights can start but with more time than if no app has asked for root rigths for the first time.

I've tried to disable log, I've unchecked the notification, but I still have the same problem.

Is it a known bug ? Does a workaround exist ?

Thank's for your help !
[SuperSU] TheAngelus:
I'm having an odd issue suddenly. All was working fine until today as far as i know.

Open supersu and it wants to update the binary, press continue and it says its failed.

some apps are working such as setdns and esfileexplorer which needs root/su, others says there is no root like adaway.

If i restart i sometimes get told no apps can get root, and other times they are working fine.

I was getting the mksh problem popping up but it hasn't come back for some time.

im only on stock ics 4.0.4, rooted.. htc one x.
[SuperSU] V0odo0:
Hi all, can i falsh the latest flashable supersu zip in TWRP??? i have galaxy nexus with stock image 4.1.2 ...
[SuperSU] Jay Aristide:
Yes. For all intents and purposes, CWM and TWRP are synonymous.
[SuperSU] V0odo0:
thanks mate .. :) .. it works .. i was doubted coz its name said "CWM flashable"... i just wanted to be sure .. :)
[SuperSU] romeoh:
I'm having the same issue with my EVO 4G LTE that i updated yesterday to JB 4.1.1 the supersu when it asks to update the binary and press continue the screen gets dark and rebbots and it does the same thing when i try to update Adaway app. I checked if i have a good root or not by using root checker it shows Rooted. I'v never had any problem with SuperSu before the update.
[SuperSU] TheAngelus:
Mines started rebooting when i press continue to update binary. Its very disconcerting.
[SuperSU] k2trill:
I don't understand why after 9 MONTHS, this app which is supposed to control root access, still requires ANOTHER app (superuser) in order to update and actually work. Even when you flash the zip which you would think would work " out of the box," you still end up with nothing usable until, again you flash the original superuser. At what point will this become ORIGINAL and INDEPENDANT???
[SuperSU] shaggyskunk:
Really? That's pretty funny - superSU works perfectly AND independently on both my skyrocket & n7. Could it be that you're doing something wrong?

I don't EVER have to flash superuser - EVER. :)
[SuperSU] defim:
I you should not use root...
[SuperSU] VivaErBetis:
I agree. I flashed SuperSu with CWM Recovery in order to gair root in my Nexus 4 and it worked like a charm. Never used Superuser app.
[SuperSU] adell_:
It works out of the box for me.
[SuperSU] lancemoreland:
Same issue for me. Just started after we got the JB update. The binary update message cannot be bypassed to get to settings. If you cancel the program closes, if you select update the phone reboots.
[SuperSU] k2trill:
You didn't have to update binaries in order to use it the first time?

You actually bought and/or use a Motorola Defy. That alone shows how irrelevant your opinion is....

So, you didn't have to update binaries in order to use it the first time either huh...?

Congrats to you all with your success stories, but please understand what I am talking about before you make incomparable arguments. You guys are obviously still on Gingerbread or ICS and/or not using JB with newer (I assume only HTC) devices with different system read/write properties (which can only be written to in recovery while S-ON). I've been following this app since DAY ONE, and when it was FIRST released and for months even after that, BEFORE you could use this app, it had to aquire root privileges to update binaries by outside means i.e. superuser (which by the way has never depended on a like app to update IT'S binaries. I purchased this app to support the dev yada, yada, yada but I think by NOW, by NO MEANS should it STILL require the very app it is designed to replace. The SuperSU recovery flashable zip and the app itself is pretty much useless in our situation. Doesn't even makes sense to have to update binaries with the flashable. It should, as I said previously, work "out of the box!"

Sent from my HTC DNA™
[SuperSU] zelendel:
Look the dev made the app the way he wants/needs it to be. If you don't like it then don't use it. Or better yet make it yourself.

Batcom2
[SuperSU] shaggyskunk:
Using superSU on skyrocket (Samsung) running cm10 & Nexus 7 (Asus) running cm10.1 so, newer devices and jellybean :rolleyes:
[SuperSU] adell_:
I think he means the problem only occurs on JB with newer HTC devices.

I'm using JB on a very old HTC device (HD2) and don't have this problem.
[SuperSU] Kurre:
Dude just calm down a little :) I didn't say "ah ha" or anything else like that to you..Just trying to..Well what ever :rolleyes:

And no, I won't be buying anything else than nexus devices now on, but that's just me :)

Sent from my slimbeaned GNex :)
[SuperSU] k2trill:
I'm cool. Trolls irritate me tho. I'll buy a Nexus when. HTC or Apple makes one. I buy for build quality. I tried Samsung. My last one was a Galaxy Nexus. To me, Samsung makes really nice tablets. The phones tho, not so good (to me). They remind me of Cadillac cars... look really nice on the outside, but inside, sub par.
[SuperSU] zelendel:
It is comments like the past few that make Developers leave and stop doing the great work they do. If you cant use the app for what ever reason then move on. If your not willing to help the dev then use something else. ITs plain and simple. Telling someone what they should do with their app is not only tacky but pointless. Now If you have some insight to the help the dev then by all means help out but if not then there is no reason to post now is there?

As for your comment, I have been following this great Dev work for years and have been using this SU since back in beta stages so dont assume to think you know everything or anything for that matter. Any more comments about this should be done by PM.
[SuperSU] adell_:
Well, I think that comments like these make apps improve. I still remember when a member pointed out that this app had some security issue, many other members flamed him. But eventually, Chainfire fixed the code and the security was strengthened.
[SuperSU] Jay Aristide:
So, with HTC, you can't flash zips from CWM? There is a CWM flashable SuperSU zip in the OP of this thread...

Also, on the subject of overall device quality, I find it funny you talk Apple up but denounce Samsung, as iPhones are about 60% Samsung. As for HTC... Well, let's just say that until very recently, every single one of their phones looked and felt like a brick, and even now, they tail the *rest* of the market on battery life.. Oh, and their displays look terribad. I'd take a Galaxy ANYTHING (even Prevail) over an HTC One X...
[SuperSU] osm0sis:
Bug reporting is well and fine it's just the tone.
[SuperSU] k2trill:
Once again, you show that you ignore RULE #1 and or just flat out cannot read. Someone please send this guy a pictogram that illustrates what is posted in the LAST LINE OF THE OP's SIGNATURE because I cannot draw. Tacky and pointless are the comments that you keep posting. Mine are however backed by FACT. When a person puts something like that in their signature, comments, questions, suggestions, and opinions, like mine are in fact what you will see in the thread. Now, if I knew how to fix the issue or had a suggestion, I would do so, change the graphics and launcher icon, and repackage the app so I could sell it just like he is because then MY app would more CLOSELY live up to the FIRST LINE in the OP, "SuperSU is the Superuser access management tool of the future."

---------- Post added at 01:56 PM ---------- Previous post was at 01:49 PM ----------

and you also remember I'm sure how similar trolls and fanboys tried to come down on that guy. I do. I was there...

---------- Post added at 02:10 PM ---------- Previous post was at 01:56 PM ----------

Read post #1728 as I am quoted there and since zelendel deleted my original post so no one would understand what is even being discussed. People like him do that to try and make a person like myself appear mad or angry in a thread to members just joining in when in fact I am only disgruntled and feel about misled. You can even go back before even my initial post to post #1716 and view someone who is having the same issue that would not exist it were addressed months ago.
[SuperSU] zelendel:
^^^^^^^^:good::good::good::good::good::good::good:
[SuperSU] Jay Aristide:
Hey, DOUCHEBAG (yeah, YOU)

You know what's ironic? You're calling the people in this thread trolls when your own demeanor is so piss-poor that nobody even wants to address your issue; They just want you to shut the hell up. I mean, do you think you're going to manage to insult Chainfire into dropping what he's doing and addressing your individual problem (that's apparently caused by a protection scheme implemented by HTC, not by Android, and NOT by Chainfire)? There are a lot of people on this thread with HTC devices - both old and new, OTA updated, CWM flashed, and even stock - who are not having the problems you're describing. This tells me your issue is something of a fluke, and not status-quo for your device.

Now, this is probably going to earn me an infraction, but eff it. You need it:

YOU are EXACTLY the kind of user XDA does not need. People like YOU are the reason developers stop developing. You bring nothing to the table but insults, complaints, and an absurd sense of entitlement. You abuse GOOD developers and trash-talk senior moderators, then expect people to take anything you have to say seriously. Here's some advice: try not being a complete PRICK some time, and see where that gets you. You can catch more flies with honey than you can with vinegar. From what I've read in the past 10 pages of this thread, the only person coming remotely close to trolling is you. Though, I wouldn't really call it trolling, I'd call it a complete and total social ineptitude (and I'd probably blame your parents for that).

P.S. trash-talking a moderator is a real good way to get your ass kicked off these boards, altogether.

P.P.S. Moderators, If you're going to delete this post, PLEASE PLEASE leave it up long enough for senor asshat to read it.
[SuperSU] k.electron:
question about super su - is it now working with multiple users? id like to take some tibu backups and restore them to my wifes accounts for games.
[SuperSU] Jay Aristide:
Nah, not yet. I asked a week ago and he said he was still a few weeks out from a proper multi-user implementation.
[SuperSU] iamelton:
k2trill, just get the hell out of here!

you give no useful comments to anyone, and are not needed here..

apparently you are being ignored by chainfire.. like it or not!

you may go elsewhere and whine about your being treated poorly..

nobody cares! just go away..
[SuperSU] Chainfire:
Shees, I leave this thread alone for a few days ... it explodes.

And while I do appreciate everybody rallying to my defense and their willingness to put a good troll down - and I mean this in the most respectful way possible - please try to refrain yourselves from getting into arguments. If you do not agree with somebody, think he's an asshat, etc, actually responding/joining the argument is seldom productive, however well-intentioned.

Now, k2trill was unhappy about the situation, and I certainly do not appreciate his attitude, but he may actually have a point in there being a problem in some configurations (that I do not actively support). SuperSU does trigger a secondary binary update even after being flashed through CWM. Apparently this is a problem for S-ON devices, and if it can be fixed using the CWM ZIP, why not attempt it ? I'll add this to my to-do list to at least try. Maybe it is minor and can easily be fixed, and everybody will be happy.

@kengkaj.s I'm not sure what you are referring to specifically, but generally such a problem would have been fixed regardless of how it was reported. Contrary to what this all may look like, making a fuss will not make me fix things quicker, it'll just make me angrier while I'm fixing it.
[SuperSU] Jay Aristide:
I think the *easiest* way to fix it would be to make sure the CWM flashable zip here always has the latest binary in it. On a more creative/intuitive front, though, how hard would it be for SuperSU to realize it's in this particular situation and create a CWM flashable zip on the fly containing the latest binary? When it's created it, it could either tell the user to reboot into recovery amd flash it, or do it on it's own..

Edit: Hell, you could even have it create an update.zip so it works with the majority of stock recoveries.. I know my SGS4G *never* had a proper CWM, and to get to CWM, it had to sit in update.zip on my sdcard...
[SuperSU] Prodepressiva:
Can somebody help me on this SuperSU problem, please? http://xdaforums.com/showpost.php?p=35546742&postcount=127
[SuperSU] Chainfire:
The ZIP does have the latest binary version in it, that's not the issue. The issue has to do with how SuperSU creates a backup copy for OTA survival and temp-unroot. The ZIP has to be modified to also do this, I guess.

Creating a ZIP on the fly is slightly problematic due to the signing process, and I'm just not a fan of the process.
[SuperSU] guijarrelson:
Is there an option to autoupdate su binary or manually check?

Thanks for all.

Tapatalked as you see from SGS CyanogenMod 10
[SuperSU] osm0sis:
Nope. Because it's packaged with the apk. :good:
[SuperSU] dgreyesq:
update binary groundhog day loop!

Phone is HTC Evo 4G LTE, HTC dev unlocked, rooted, S-On. Rolled back, accepted OTA for radios, then unlocked again, so back to the start of this sentence.

Root is fine. SuperSU functions EXCEPT if I try and run SuperSU (which was flashed from zip in OP) it asks me to update binary. If I say yes screen goes black and phone reboots. If I say no, then app closes and I can't access settings.

In google play there is no option to uninstall. I have tried deleting from system/app and reinstalling both from google play and by flashing zip. Same result.

Any help available?

thanks!
[SuperSU] Chainfire:
Can you try flashing the attached ZIP, and see if it gets rid of the popup ?

If it does, can you use "ADB shell" (or a terminal app) and run the following exact commands, and let me know if they work and/or at which command it reboots, if any ? Please copy/paste all the output to http://pastebin.com/

su
mount
mount -o rw,remount /system /system
mount
echo test > /system/test
mount -o ro,remount /system /system
exit
exit
[SuperSU] dgreyesq:
I flashed the zip and after reboot, started SuperSU. Sadly, same popup. Cancel simply closed app. Install resulted in dark screen then reboot.

I can also run the commands in a terminal window, but how do I get you the output?

Never mind the last question - I think I figured it out and sent you the output despite the lack of success with the zip. Perhaps that will help

additional note - commands did not cause reboot for me either.

EDIT: here is my paste: http://pastebin.com/WqSaspRH
[SuperSU] lancemoreland:
It does not get rid of the dialog and exhibits the same behavior as the original.

Edit: Sorry dgreyesq, looks like we were typing at the same time.
[SuperSU] rawintellect:
I pasted my output from adb shell here:http://pastebin.com/Fybbmnz7

My phone never rebooted issuing any of those commands.
[SuperSU] Chainfire:
Hmm, interesting. Will look into it further.
[SuperSU] dgreyesq:
Thanks again!!! I have edited my reply (several times now) and I hope I have provided the information you need. I have no hope of figuring this out on my own.
[SuperSU] CoolApps:
I am wondering, shouldn't SuperSU be in Application development and also in this forum in the same time? ;)
[SuperSU] dgreyesq:
Any progress?
[SuperSU] Chainfire:
Sorry, I got sidetracked with the whole Exynos exploit thing. I'll get back on this.
[SuperSU] CoolApps:
Mmmm... Exynos exploitation...

Good work Chainfire. :)
[SuperSU] dgreyesq:
And if I even understood what that meant.......

Thanks!
[SuperSU] eliaspizarro:
Same q?
[SuperSU] DarkhShadow:
He already said unless he has one, no

Sent from my Jelly Nexus S
[SuperSU] billyho7993:
Has there been any progress in this problem cuz I am having the same problem since being on jb...I'm also HTC dev unlocked, rooted and s-on...I still get root access for everything except for titanium backup now
[SuperSU] -star-:
Just an idea, is or was superuser.apk from chainsdd installed parallel to supersu on your device?
[SuperSU] Chainfire:
Regarding this "install binary" issue, unfortunately, if I test the ZIP I posted a few pages back ( http://xdaforums.com/showpost.php?p=35570635&postcount=1747 ) this *does* get rid of the dialog for me. But I don't have an S-ON HTC device, so it is not exactly the same. Somebody with an affected device is going to have to jump into IRC and find me there so we can test this "live" and figure out what is going on.

If you jump in and want to help with this issue, please check if there's a TWRP for your device, it is much easier to test with than CWM.
[SuperSU] lancemoreland:
I am happy to help if no one has taken you up on this, I have an HTC Evo lte 4g, s-on with TWRP installed and am crashing while updating the binary. I am not too familiar with IRC. Walk me through contacting you via IRC and I'll help out.
[SuperSU] goodtimes50:
So I had a weird issue the other day. When I unlocked my phone I got the little message saying BetterBatteryStats had been granted superuser access (as expected) and then I opened up setCPU and got the same notification for setCPU (as expected). However after that it seemed to get stuck in an infinite loop of showing those two notifications and there was nothing I could do to stop it short of rebooting. The phone got pretty warm too. I went into SuperSU and everything looked fine in there. The night before I noticed that my phone had shut off and when I felt it it was extremely hot to the touch, like to the point that I almost couldn't hold it. This makes me wonder if the same thing had happened while I wasn't using the phone.

Any idea what might have happened?