yashsingh1/xdaforums huggingface dataset:
[SuperSU] DJxSpeedy:
install supersu from market.. update his binary..

leave superuser in /system/ its dead now..
[SuperSU] poncik:
new icon is terrible, swept away all the quality. I hope you can go back to the good old # icon, it was so much better.
[SuperSU] vlt96:
Yea, I love the old icon too, why change?
[SuperSU] Chainfire:
Because I got like 50 emails a day complaining about the icon ...

That's why I'm currently accepting entries for new icons, and we're going to have a public vote next month.

Most votes wins and becomes next icon.

After that, anybody who complains about the icon will be ignored and/or removed from the premises. End of story.
[SuperSU] shaggyskunk:
Only 50, out of how many users - Personally, I would have ignored them - But hey, it'll be fun to see the "creativity" of some of the loons :D

The technical skills for designing an icon, are not in my quiver - but it'd be amusing to see, an image of a rotting apple being skewered by Andy as the icon :p

Sent From Down The Rabbit Hole. AOKP JB- 9/2- Cobalt Theme.
[SuperSU] Pons:
He didn't say only 50, he said 50 a day.
[SuperSU] shaggyskunk:
Yeah, I realized that - 1,000,000+ Downloads is about 2,700+ per day & of that - ONLY 50 emails per day, from people who take issue with an icon that they see, for how long in any given time? :)

Sent From Down The Rabbit Hole. AOKP JB- 9/2- Cobalt Theme.
[SuperSU] Fallen Spartan:
Its your app, you can choose any icon you like. I bet these complainers will still use your app no matter what the icon looks like
[SuperSU] jwds1978:
At the end of the day, who the **** really cares what the icon looks like? I as sure as Hell didn't buy the app because it's icon was 'pretty'; I bought it because it's the best damn SU application in the market! But, then again, some people will always find/need something to ***** and moan about.
[SuperSU] Simba501:
Seriously??
[SuperSU] osm0sis:
I'm a fan of the simplicity of the original but here's my submission anyway.

I'm keeping it simple and effective, with clean lines, but I wanted to throw Andy into the mix too, to hopefully make both camps happy. :D:fingers-crossed:

There are a couple like this already but this is the first keeping the colors, iconography, font and lines nice and clean.

[contest over - submission removed!]
[SuperSU] jco23:
Thx for this.

tappin' that....
[SuperSU] zeppelinrox:
Well just thought I'd throw in an idea from left field...

Superman logo... without the S :p
[SuperSU] vlt96:
++++++++++++ for this one!!!!

Sent from my LG-P500
[SuperSU] SGSLover:
Icon

OK, it's generous of Chainfire to let the Users participate about the icon,

but i really wonder why users complain about an icon for an app that give you ROOT-Privileges...i would understand when they complain about failures, but not because of an icon...

Why should i complain about an Icon if the app works like it should....

Some people have too much spare-time...

Keep on with your great work Chainfire!
[SuperSU] zeppelinrox:
A good icon actually helps "sell it".

Resulting in more downloads
[SuperSU] ontae:
GO Switch Widget 1.54

Hi,

recognized strange behaviour with the app "GO Switch Widget 1.54" (Shortcut Widget - see attached screenshot):

When SuperSU 0.96 ist activated (via SuperSU GUI) during booting the device, the widget does not function when trying to e.g. turn WiFi ON/OFF - it even freezes the system so e.g. SuperSU GUI or another app cannot be launched until the widget process is killed.

If SuperSU is not active during booting the device, all is fine and the widget app functions properly. Activating SuperSU after booting the device works fine then - so apps which require root access are functioning properly.

Any suggestions what could be the problem?

Greets, ontae

My system: ICS 4.0.3

PDA: I9100XWLP7

PHONE: I9100XXLPS

CSC: I9100XXLPH$

Build Date: Apr. 03 2012
[SuperSU] jayjay3333:
I agree with with you. I would never complain about such a thing either... I'm just great full the app was made by a developer that makes my phone awesomeness ;) But like was said it does sort of sell an app. It's like a book cover, the more they are noticed the more they sell.

Personally I really dug the minimalism of the hash tag but hey that just me.
[SuperSU] Chainfire:
Well, there are a lot of hash tag submissions you will be able to choose from. Some much better than my original. So if that's what you're after, be sure to vote for one when the time comes.

I have not put the new submissions up yet, I'm going to use a different system, since I've had a "ZOMG!" amount of submissions ... :)
[SuperSU] Chainfire:
Please read the icon submission rules ...

http://www.chainfire.eu/articles/122/_Submit_SuperSU_Icon_Competition/

I will *not* include icons submitted any other way, including posting them here.
[SuperSU] elite_gamer04:
Sorry to jump in the middle of the Icon Competition posts, hope my post doesn't get hidden!

Just wanting to know if there is an easy way (other then flashing the CMW SuperSU .zip) everytime I flash a new CM10 Nightly - as it obviously re-installs Superuser. I already slightly edit the CM10 Night .zip (removing TVOut and CWM Manger) so I figured if I can do anything else to save me time?

(I have tried simply replacing 'su' and putting the SuperSU.apk in the system/app folder within the zip and removing Superuser.apk to no avail tho)

Cheers!
[SuperSU] vlt96:
In the ROM zip/system/app/ put Superuser.apk from the SuperSU.zip and in /system/xbin put the binary:D

Or just flash after flashing the rom, what is so hard?
[SuperSU] Captain_Throwback:
Personally, I edited my GApps zip file to include the deletion of Superuser.apk & ROMManager, and added the su binary to the zip file (I have the SuperSU app installed from Play Store), along with some slight adjustments to the updater-script. That way it's taken care of automatically.

----------------------

Current Device: HTC EVO 4G LTE | ROM: toasted-deck CM10 | Kernel: Stock
[SuperSU] dakunesu:
got a cool little idea for the OP to put in. cause theres times when it pops up over everything and you dont want it to, have a notification come up that pops up the allow/deny thing. on Ics you could have the allow/deny options on the notification itself, and jb can have the options expandable.

all optional of course
[SuperSU] shoman94:
I downloaded and installed 0.96 from this thread. It updates on first open and also in settings it says v0.94?

I also lost SU for some reason. The apk was showing like a superman or something instead of the # and said I had no SU when I really did have one in the xbin folder.

Any thoughts?
[SuperSU] shaggyskunk:
Thoughts, yeah - you aren't really following the development of superSU ;) Are you sure that you flashed the right zip & do you have superSU enabled?

Sent From Down The Rabbit Hole. AOKP JB- 9/5 X's 6.3.6.beta.
[SuperSU] shoman94:
I downloaded the latest link in the OP. its named 0.96.... pretty sure I flashed the correct one... and of course its enabled.... :rolleyes:

Root worked for a while then it just stopped. The icon changed for the app in the drawer like I said. I reflashed it and it works again but it is still 0.94.

This is my first time using SuperSU and I searched about it in this thread and didn't see anything.
[SuperSU] shaggyskunk:
Try downloading the app from the store - I had some problems getting 96 to stick for some reason, I still don't know what happened?? Try fixing permissions ;)

Sent From Down The Rabbit Hole. AOKP JB- 9/5 X's 6.3.6.beta.
[SuperSU] shoman94:
Funny... an update just came out all of a sudden and it updated to 0.96 even though I had already had it from the OP. Well we'll see how this goes! :D:D
[SuperSU] Simba501:
That's what I had to do; update it via Play Store.
[SuperSU] andrewschumi:
How to incorporate SuperSu in a custom rom?

Hi I am trying to cook a rom from HTC Desire S ICS Stock rom. I use the dsixda's Android Kitchen, but it has only the chainDD's one. I tried manually to put the superuser.apk at the system/app and the su in the system/xbin, but no result, the rom stucks in the initial boot(HTC screen).

Can anyone guide me how to put in the rom the SuperSu?
[SuperSU] shoman94:
Make sure you remove the su in /bin.

But I doubt that's your problem. You either have root or you don't. It's never stopped a boot for me.
[SuperSU] andrewschumi:
So I just put the superuser.apk in system/app and su in system/xbin, and remove su from system/bin. Do i type anything in update-script?
[SuperSU] 3rdstring:
Download Chainfires CWM SuperSU zip & make sure you set the right permissions
[SuperSU] shoman94:
Change this;

set_perm(0, 0, 06755, "/system/bin/su");

To this;

set_perm(0, 0, 06755, "/system/xbin/su");
[SuperSU] Captain_Throwback:
Should also change the symlink from /system/bin/su to /system/xbin/su to the opposite if the binary is being placed in /system/xbin.
[SuperSU] shoman94:
The symlink already does both.
[SuperSU] andrewschumi:
Hi again, I tried what you tell me to do, but no result. Obviously somewhere i did a mistake. But next i gave root permissions with the kitchen(chaindd's superuser), and then i copy the superuser.apk over the existing one in the /app and the su in the /bin, and it worked. When I opened the rupersu, it asked me fror su update, made it, and all ok.

I think I must read a little from android rooting basics to finf out how it works. Any thought where to look first?

Anyway thanks
[SuperSU] apk_xiz:
hi OP thier is some bug with your supersu when i try to grant su permission for es file manager it hang up at es screen but i guess it only happen when i enable logging = full contact (pro feature) .Please fix it thanks
[SuperSU] JBabey:
in version .96 I also have been getting these (Galaxy Nexus AOSP Build, also on cyanogen 9, also on gummynex) - Yes they are from SuperSU as I build it into the rom before flash replacing superuser.apk, and yes I have disabled notifications, disabled logs & individually open each app and disable notifications (pro version).

It was doing it in .95 as well, was just hoping it was a glitchy rom.... today I got the SPrint OTA for the official release of jellybean, and it is continuing the behaviour on a non custom ROM. I read the next 4 pages of the forum after this was mentioned to see if there was a solution but have yet to come across it.

Is there something I can modify in the apk to stop it from toasting me? In my case its not really a minor annoyance, but a huge life ending apocalypse -see what i did there? ; )

anyways more of a "Its still an issue" & "hope there is a way to fix it" rather than a complaint.

-Cheers!
[SuperSU] Chainfire:
Try clearing SuperSU's data, and reconfiguring.
[SuperSU] churchmice:
Hi, Chainfire.

When i enabled the full content logging in the supersu setting, in connect bot ( an terminal emulator ), when i type su, it would hang.

But if i enabled "access only " in the logging in the supersu setting, it is working fine.

Any suggestion ?
[SuperSU] Pons:
Yes, leave it at "access only."
[SuperSU] hazimjaved:
I'm noticing a unique problem of root acces...whenever i try to switching to other roms or restore or backup my phone or also after some days in any rom i just loose my root access SuperSu give me this error there is no binary installed and superSu cannot install it using first build of jb aokp

Any help????

via Google Galaxy Nexus
[SuperSU] RomsWell:
Hey guys,

Maybe someone has run into this alrdy. I dev for the Galaxy tab 2, and for whatever reason i can only get injected root to work via bin. and only on a older set of binarys. If i use xbin i get a fail, if i use the latest binarys i get a fail. And my updater script is correct. Now if i use my older working set of binary and app. I can then install SuperSU and let it update and after the update it moves it to xbin. Everything works fine. Just for the life of me cant figure out why i cant start out using the latest set of binarys.
[SuperSU] Aerowinder:
May I see your updater-script?
[SuperSU] Aerowinder:
I would test the su install myself if I had your file, but with a quick look through the script, I found this:

1) set_perm(0, 0, 06755, "/system/xbin/su");

2) set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");

Could these two lines be conflicting? It seems to me that they appear in reverse order.
[SuperSU] shoman94:
Yes exactly.....That's how I fixed mine.
[SuperSU] RomsWell:
I can't thank you enough. Ive looked it over 100 times and missed that. Works fine now. Ty much.
[SuperSU] JBabey:
That works... i was able to track the issue to Wiping Cache/Dalvik then rebooting... once i reboot after doing the cache wipes the messages start popping up again.

~J
[SuperSU] psychoid:
hi,

i'm trying to install supersu from market, but said is not compatible with my device? my device is Samsung GT-I9100 (Galaxy S2), usually no problem installing supersu from market.. already clear market cache, still problem persist :confused:
[SuperSU] pee-wee:
Flash through cwm form page1

Sent from my HTC One X
[SuperSU] minuteez:
Hi all,

Having problems with supersu.

Rerooted my s3 after the latest update & supersu was installed automatically (fgt what I used to root tho)

Updated supersu via Google play & it shows 0.96 now. But each time I run supersu, it keeps asking me to update binary.

But when I click 'continue' to update, installation fails. In superuser, the version still shows 0.93 instead of 0.96.

I tried updating via superuser. Most times, update fails as superuser can't get root access. But sometimes update is succesfull

but supersu still asks to update binary.

So I downloaded the 0.96 zip from the 1st pg & tried flashing via cwm recovery. This also fails. I get a signature verification error.

Any ideas on what I'm not doing right?

Thanks

Regards

M
[SuperSU] theone10:
Does it support the cmu 9 root disable menu by the setting in cm9?
[SuperSU] rodem77:
Noob question:

I'd like to root my nexus s, flash supersu will root my (already unloked) device? If I prefer to don't use CWM, where I can find a stand alone SuperSu zip?

Thankyou
[SuperSU] shaggyskunk:
Flashing supersu will not root your phone. Use Odin to root it first. If you don't want to use cwm, check & see if twrp recovery will work for your device.

Sent From Down The Rabbit Hole. AOKP JB- 9/21 Stock Kernel - No flicker :P
[SuperSU] Pkt_Lnt:
First post of this thread.

Galaxy Nexus / Tapatalk 2
[SuperSU] rodem77:
So if I'd like to use SuperSu I've to flash before Superuser from here

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

to obtain root and later change it with SuperSu?
[SuperSU] efrant:
No, you can just flash SuperSU.

This is completely wrong.
[SuperSU] rodem77:
Thankyou, I'm reading also yours "How to" and I better understand everything I need. Sorry for simple questions (and probably for wrong section).
[SuperSU] shaggyskunk:
I defer to your expertise - But in your how to,

" How do I root?

As was mentioned earlier, you need to place the su binary and the superuser app into the right spots on your device. In order to do this, you need to already have root access. There are two ways: flash a root package in recovery (instructions here), or manually place the files in the appropriate spots (I will add instructions on how to do this at a later time)."?

This how to, seems to suggest that in order to get root, more needs to be done than simply flashing supersu?

Perhaps I'm missing something?

Sent From Down The Rabbit Hole. AOKP JB- 9/21 Stock Kernel - No flicker :P
[SuperSU] efrant:
:) Yes, you are missing something.

1) When you boot in CWM (or TWRP), you already have root access (while it is booted) by default;

2) What I refer to as a "root package" is either ChainsDD's Superuser zip, or Chainfire's SuperSU zip. Flashing one of these in CWM (or TWRP) will place the correct files in the correct spot with the correct permissions, which will give you root in Android. There is nothing else you have to do.
[SuperSU] shaggyskunk:
Ok, but don't you need root to use a recovery like cwm or twrp?

Perhaps I misunderstood his question, I thought he was asking what he needed to do in order to use supersu?

I've always used Odin to root :)

Sent From Down The Rabbit Hole. AOKP JB- 9/21 Stock Kernel - No flicker :P
[SuperSU] efrant:
Nope.

If you have a custom recovery, all you have to do is flash the SuperSU zip. If you don't have a custom recovery, then you get one by whatever method you want: fastboot, odin, etc.
[SuperSU] osm0sis:
Nope, all you need to flash a custom recovery is an unlocked bootloader. Then rooting is easy because custom recoveries have insecure kernels (root access).
[SuperSU] hammadsaqib:
when rooting the HTC one x u flash the .zip file of superSU in recovery does this install superSU in the system apps??
[SuperSU] CamoGeko:
Why did you quote the post??

Yes it installs root and superSU.

Spun out from a BRICKED and RENOVATED One X.
[SuperSU] shaggyskunk:
Uhm, Chainfire - the Dev, is saying that SuperSU "requires a rooted device".

Still don't understand how/why I am totally wrong? :)

Sent From Down The Rabbit Hole. AOKP JB- 9/21 Stock Kernel - No flicker :P
[SuperSU] efrant:
What you are not understanding is that if you boot your device into CWM, you do have root.
[SuperSU] shaggyskunk:
Thanks,

I'm really not trying to be thick skulled :)

I'm just thinking that I used Copperhead's method to root my phone with Odin - Flashed the recovery with cwm - did a backup - installed superuser from the (then market) Since then I've flashed SuperSU etc.

IDK Maybe I need more coffee, or I've had too much :o

Sent From Down The Rabbit Hole. AOKP JB- 9/21 Stock Kernel - No flicker :P
[SuperSU] efrant:
A) Root is 2 files copied to /system: whether it's 1) su and SuperSU.apk or 2) su and Superuser.apk it makes no difference.

B) The two files from point A above are contained in a zip file.

C) That zip file needs to be flashed with a custom recovery (which will copy those 2 files to /system because your custom recovery has root access). Nothing else.

D) How you get a custom recovery on your device is something completely different.
[SuperSU] decmk:
Root is required only when you install from Google play.

For zip file is required custom recovery.
[SuperSU] nishanty13:
Oh ! I misunderstood.:p
[SuperSU] Mister_Mxyzptlk:
Well, you might not be that far off. Just for kicks I reinstalled SU from Mark... err... Google Play Store and now MobileODIN is happy as a clam.
[SuperSU] ZeroManArmy:
Will you allow this to be included with ROMS?
[SuperSU] DaX05:
Awesome! Thanks!

Beamed from my Nexus S
[SuperSU] PharmCAT:
He mentioned it in the OP,
[SuperSU] GldRush98:
Completely broke SU access on my Galaxy Tab. Cool.

Edit: Turning off the notifications fixed it enough to where I was able to restore the original SuperUser binaries. Whew.
[SuperSU] Wetzel402:
Superuser replaced with SuperSU on my Dell Streak 7. The newest version from the market works well. The previous version failed to install the binary.

Good work!
[SuperSU] fenerbuuh:
again chain gets rich :) gooooood work .
[SuperSU] Mister_Mxyzptlk:
Okay. Apparently some apps won't settle for gaining root access and verifying the presence of an SU binary; they also check for ChainsDD's "Superuser" *.apk from the Mark... err... Play Store. MobileODIN happens to be one of these picky apps.

****************************************************

If you encounter any issues with MobileODIN after installing SuperSU and removing ChainsDD's "Superuser", do the following.

1.) Ensure complete removal of downloaded and pre-installed "Superuser" *.apk's from "/system/app/" and "/data/app/"

2.) Create a new, empty file using your favorite root-enabled file browser

3.) Rename this empty file to match the name of the "Superuser" *.apk you removed from "/data/app/" It should be " com.noshufou.android.su-1.apk". Or if you'd rather, download the one I'm using here: http://db.tt/xOSuJvbq

4.) Copy the file you just created or downloaded to "/data/app/"

5.) Reboot

6.) Verify root functionality with the app that was giving you trouble; i.e. MobileODIN

****************************************************

I may modify, append, or amend these directions if corrections, changes, or additions need to be made. I hope you've found them helpful.
[SuperSU] SyAdmin:
It dosen't work on Galaxy Mini :) on CWM says install aborted.
[SuperSU] vlt96:
Install from market, binary will install and keep SU until you enable it, it needs su permissions to replace the binary, then you can uninstall superuser, worked for me!

I was born in the '90's... 1290's >:)
[SuperSU] Chainfire:
v0.74 released !

v0.74 is now available on the Market and from the first post (unfortunately the ZIP file does not work on all CWM versions).

This update should fix the major problems some have been seeing (root apps freezing, access not given, etc). Thanks to whomever figured out this only happened when USB debugging was disabled, finally allowed me to find the problem and fix it.

Let me know how it works out !

-----------------------------------

Re: Mobile ODIN, Root Validator, etc

An updated version of Mobile ODIN will be released hopefully later today (v2.25). A new version of Root Validator supporting SuperSU should also be released shortly as well.
[SuperSU] DarkhShadow:
0.74 zip works fine with cwm 5.8.0.2

Sent from my ice cream powered Nexus S
[SuperSU] ashok:
root explorer not recognizing supersu. Any help?
[SuperSU] DarkhShadow:
Its issues with root explorer, devs need to update it seeing as I can't use it, I use FX so its not a problem

Sent from my ice cream powered Nexus S
[SuperSU] PharmCAT:
Heh, 4 updates within less than a day, someone needs a nap. :D

As for the newest update, it works fine. 4EXT, Titanium, ES File Explorer, Ad away, Nova Launcher all got root without any issues.
[SuperSU] grgsiocl:
atlast working fine now...yes that was a problem with USB debugging unticked as i did...thanks CF i will buy the PRO and awaiting for your new update on MOBILE ODIN! Right now i cant use the MOBILE ODIN, due to deleted superuser.apk which mobile ODIN looks for it and says "no package of superuser found"
[SuperSU] cbeckstein:
complete mess after first time using wireless tether with supersu 0.74

had just a Super GAU with the Pro version of supersu 0.74 on a SGS2 with stock XWLA4 (Android 2.3.6) ROM with speedmod k2t21 kernel:

installed supersu Pro, everything went fine until I first time started wireless Tether 3.1 beta11 and tried to activate tether, then

phone almost froze, no prompt from supersu (as expected because wireless tether needs su privilege), interupted wireless tether, started supersu, granted su rights explicitly, back to wireless tether, phone still crawling, wireless tether reporting that phone is in a limbo state and should be rebooted, switched off phone by long pressing the power button, phone restarted and hell broke loose:

almost every service crashed upon start (even the logging and launcher service), had to switch off the phone again and when I then attempted to restart phone hang at the Samsung start logo

fortunately I generated a nandroid right before I installed supersu and the phone still was able to boot into recovery enablnig me to restore the fresh backup and again have a fully working phone...
[SuperSU] amitks:
I lost all root access on my Asus Transformer running a Revolver ROM.

Checked USB debugging is enabled. What am I doing wrong?
[SuperSU] grgsiocl:
disable USB debugging and go to supersu app and then click on it. You will see all the applications over there and next to it there is a # symbol. click on it and select grant and save and then launch the application
[SuperSU] rodem77:
Thankyou, in these 2 page I've found explanation to a lot of things that are difficult to find into various root guides!

Now I've another question: the SuperSU zip file that I can find in the first page contain in its name CWM. This mean that is a version specific for CWM or I can use also TWRP to flash it? Why there is CWM indication into filename?

Thankyou
[SuperSU] efrant:
It should flash fine in TWRP. Don't forget, TWRP is relatively new compared to CWM, so when a lot of people say CWM, the actually mean "a custom recovery".