yashsingh1/xdaforums huggingface dataset:
[SuperSU] zelendel:
You explained everything when you said one click root and kingoroot both of which are jokes.

Also let me let you in on something. Just about every single rom on this site uses this app and it works for millions of users everyday. Im not gonna get into it with you as it is plain you have no idea what you are doing or talking about.

Also no one cares what you paid for. That has nothing to do with this thread. Take it up with the dev by official means.
[SuperSU] dongerado:
Perfect! Everything works now!
[SuperSU] Manuel15:
What a hell do you mean with "you need to know an app limitation"?!? He made a great job developing SuperSU. Millions of people use it in hundreds and hundreds of smartphone, and it works in almost all the cases. When something goes wrong, people come here, describe the issue they had, provide logs when possible and if the issue wasn't caused by an use mistake (as in most cases), the developer tries to fix the bug, and in most cases he succeed. But you came here just to complain.

Have you described what's gone wrong? You just wrote " I keep getting the same error over and over ". What kind of error is it? You didn't provide ANY information about your issue! How do you think the developer can solve an issue if you don't tell him what kind of issue it is (if you didn't cause the issue making mistakes)? And anyway, if the issue was caused by the payed add-on (and I don't think so, because all the work is done by the main app), just uninstall it and see if it solves the issue.
[SuperSU] kato7youknow:
hope this helps.

Just go back to super_su_v2.46

Flash in recovery. twrp , cwm
[SuperSU] ashyx:
You realise you have made yourself look a complete and utter teacake.

I'm not going to pick apart your post which has just about every single point incorrect.

More of this is about user error than the sterling work that Chainfire has presented to this world.

Literally millions and millions of devices worldwide(and that's no joke) use these exploits without issue.

Instead of screaming and kicking and spitting out your dummy give the developer a chance to fix the problem by providing the correct information and more importantly logs of when it occurs.

I can guarantee if you do that you will have the developers full attention and respect.

How else do you think issues get solved if everyone just complained instead of providing useful feedback?

You have the entire development community to thank for that.

So simmer down and help yourself and maybe lots of others by being a bit more constructive and less critical.

---------- Post added at 02:24 PM ---------- Previous post was at 02:18 PM ----------

V2.56 is the first systemless root exploit, but had to have a modified boot.img to work which needed to be done manually.

If it wasn't modified then it's just installs as normal system root.

However now that is done automatically thanks to Chainfire's magic in the later versions if the device supports it.

ALL systemless root builds can also still install to system if the device doesn't support systemless root.

This means that only one supersu zip is needed for every device on the planet.
[SuperSU] Slender Troll:
What's the most recent version that can be used with Paranoid Android 5.1?
[SuperSU] shoey63:
I think [MENTION=7259029]Dr2003[/MENTION] just downloaded supersu from playstore and expected it to root his phone lol.
[SuperSU] Dr2003:
You have listed a few inaccuracies, 1. I was directed to this thread thru SUPERSU when I loaded it, 2. "Just about every device", means what, there are a lot of devices that it doesn't work with, 3. There is nothing wrong with expecting seemless installation, as a developer, I MAKE my money and a lot of it to make it easier for my users to use our products. I rooted a tablet not a phone, supers was one of the products that was recommended by those joke of a companies u mentioned. The cf rooting using Odin worked easily, so easily my grandmother could have dun it.... so until you can add some benefit to this discussion, I suggest u move on and chastise someone else, I made several suggestions to the maker of this software... this rooting flash processing is simple work, I do this stuff in my sleep....
[SuperSU] access9:
Just had to say that I'm a professional developer (not android), and I have never seen the kind of language you used (disrespectful, arrogant, entitled and bratty) directed at another developer in my career. Get off your high-horse and show some respect.
[SuperSU] ashyx:
Agreed, a REAL developer would never berate another developer like that. Especially one of such obvious talent and commitment to the community.
[SuperSU] Dr2003:
Lol, not a phone nooby.... tablet and I downloaded it with all the other software that was used... making a copy and flashing over is not a very difficult procexx, build a little smarts into it... not much to ask...
[SuperSU] Pkt_Lnt:
If you are such hot $#!+ why not just code your own su app that works like you want instead of flapping your lips about how great you are?
[SuperSU] zelendel:
To be honest I would watch your tone before you end up banned.

Now as I said this works for millions of users. If you can't get it to work then guess what? The issue is between the chair and the keyboard.

Sure there are some it doesn't work on. Not every device can be rooted. Just look at Samsung crap. There are a few devices that are completely locked down. No unlock for the bootloader or root. Just the name of the game.

As far as your claims go until you show something then they are all hot air.

Now if I were you until you can grow up and act accordingly then I would avoid posting or you will be banned.
[SuperSU] xunholyx:
You do realize that CF Auto Root is made by the same developer, correct?

And still, not one log or real explanation of the exact issue you are facing..........:rolleyes:

Also, how about posting some links for the apps you have created so that we can check them out?
[SuperSU] zelendel:
I think we are beating a dead horse. If he knew how to get the log or was a real developer then he would have it posted and not act like he does. My best advise is to ignore him.
[SuperSU] Tzfardaya:
But he's funny....
[SuperSU] pogodancer:
Hey friends,

no other problems at the moment? Let's be kind. Let's enjoy the weekend.
[SuperSU] yiannis1621991:
To root my flo with the latest factory image is 2.65 ok or do i need the latest 2.67?
[SuperSU] dono89:
2.65 stable is enought (aleady did on my nexus 7 32gb wifi - flo)

[MENTION=631273]Chainfire[/MENTION], All: do you know when will be released the stable version in the official play store?

Thanks
[SuperSU] fmc000:
Agree 100%. It's not a difficult process at all. Except for you it seems and this, along with your language, speaks for your level of intelligence.
[SuperSU] white7561:
Well [MENTION=7259029]Dr2003[/MENTION] even me can get log easily (im not EVEN a developer) so yeah. Ur lack of understanding is high i guess

---------- Post added at 09:36 PM ---------- Previous post was at 09:34 PM ----------

[MENTION=7259029]Dr2003[/MENTION] btw. Not for show off. Im 14 years old atm. So if u are "REAL" dev. Then why dont u give some respect?
[SuperSU] :
The real issue here is determination of what a teacake is
[SuperSU] Tzfardaya:
Obviously it's a cake made from tea... :P
[SuperSU] jesssiii:
But the one labeled potato works the best!
[SuperSU] camp0s:
Just to report, using the 2.67 beta keeps telling me at reboot that "the su executable must be updated", but after every reboot using the command "su -v" in the terminal reports the version v2.66.

Samsung s2 i9100, Slimsaber 4.4.4 Uber 5.3, Dorimanx kernel 10.50v004.
[SuperSU] spainter:
Have you tried using the un-root in the apk and reflashing the zip in TWRP?
[SuperSU] murrder:
Still waiting for help... Would be great if the developer of this program could help me out...
[SuperSU] spainter:
If SuperSu is working with other apps and just dropping on the one. Try unchecking the separate name space in SuperSU and rebooting. There are apps that seem to have a problem flashify some times doesn't seem to wait long enough to recognize root has been granted and some have been having to uncheck separate name space to get TiB to work. Those are problems with the apps not SuperSU.
[SuperSU] Tzfardaya:
A) what app

B) try fully closing the app, and open again after granting root.
[SuperSU] CE20934:
I prefer the "po-tah-toe" release.
[SuperSU] Tzfardaya:
Po-tayt-oh works better for me.
[SuperSU] rs tony:
Why i dont get play store update?
[SuperSU] Robot76:
Yes, I immediately went and looked for the potato version as thought I missed something :good:
[SuperSU] dfogelstrom:
If someone could help me please. I have searched and cannot find a simple answer. I am on beta superuser 2.51 on a VS985 running AICP (cm13 base). Can I just format system, cache, and dalvik cache and then flash Su 2.65?? Thank you!!
[SuperSU] mosimchah:
No, you would have to flash the ROM and Gapps after wiping everything, after the ROM is flashed, you can flash SuperSU.
[SuperSU] bonny_k-9:
Do please, to PIN input window was in the style of the material design.
[SuperSU] luigi97777:
supersu but this is fine for the root to all samsung phones?
[SuperSU] flipmode_10:
SuperSU Improvements

@CHAINFIRE

Please add an option "Replace SuperUser with SuperSU"

Currently you only have an option to change to another 3rd party SU, but not moving to yours.

Pleeeease improve! Perhaps as "PRO" support feature?

Thanks.
[SuperSU] :
Your request is unnecessary. Once you install su and binaries you are done.
[SuperSU] Manuel15:
How could add an option inside someone else's app?
[SuperSU] GilGameshn1:
What are you on ? It is good ... [emoji11]

---------- Post added at 04:57 AM ---------- Previous post was at 04:57 AM ----------

Thanks almighty [MENTION=631273]Chainfire[/MENTION] ...
[SuperSU] methoddon1:
lmao... that was good.
[SuperSU] egingell:
I flashed v2.65 on my T-Mobile SGS5 w/ Lollipop 5.1.1 and it seems to be functional (systemless) except that when I try to uninstall a system app, the phone reboots. I can manually remove the APKs, but not with TiB or ES File Explorer.

I'm still exploring ways to get TiB to work - it can't seem to get write access to sdcards.

Sent from: SGS5 - LP 5.1.1 / SGS4 - JB 4.2.2
[SuperSU] edzamber:
Hi,

Did you uncheck Separation of the namespace in SuperSu settings ?
[SuperSU] egingell:
No. In fact I checked it. lol

Edit: Never mind. It's not checked.

Sent from: SGS5 - LP 5.1.1 / SGS4 - JB 4.2.2
[SuperSU] edzamber:
Try to uncheck and Reboot ...
[SuperSU] egingell:
It's not (see my edit). I unchecked it first thing.

Add: I got TiB to work per this post. Thank you, Internets.

Add: I managed to uninstall a system app Lookout (crap app, by the way) and it didn't crash. Then I uninstalled T-Mobile TV, a "priv-app" app, and it didn't crash. Maybe it was just the T-Mobile app or the TiB backup folder setting. *shrug*

Sent from: SGS5 - LP 5.1.1 / SGS4 - JB 4.2.2
[SuperSU] Evo_Shift:
With the newest stable release if I take a stock ROM and flash TWRP I should be able to just flash 2.65 and I am good right? There are no instructions in the OP for flashing but I assume the custom kernel is no longer needed right?
[SuperSU] egingell:
I finally updated my Sprint SGS4 to Lollipop 5.0.1 and flashed v2.65 (it flashed as normal-system - maybe survival mode worked?) It seems to be doing well.

That's what I did. No custom anything... except recovery (TWRP), of course.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Spegeli:
Play Store no longer Up2Date?

Last Version (2.46) from 10. März 2015.

//Edit: nvm found this -> http://xdaforums.com/showthread.php?p=65113356#post65113356
[SuperSU] galaxyuser15:
I have older version 2.46 installed. Can I just flash latest stable over it using TWRP?

or do I need to remove the older version first? or do I have to follow some other instructions?

thanks
[SuperSU] Aakash Kaushal:
Firstly uninstall the supersu from the app (you will find option to uninstall in settings)..then flash the latest supersu..also make sure to take nandroidbackup first , if anything goes wrong,you will be at saferside..:thumbup:
[SuperSU] berlen:
Hello, I have a g2 running cm13. I am not able to use supersu like in cm12.1, if I try to update the binaries, I get bootloops. Can anyone confirm that supersu is usable in cm13? Which version do you use?

Thanks for your help!
[SuperSU] thecuriousmate:
Have you tried built in Root Access setting under Developer options ?
[SuperSU] Manuel15:
It seems the built in CM root causes issues (maybe conflict?) with SuperSU, I'd suggest people using CM12.1/13 to not use SuperSU in that ROM
[SuperSU] daniu:
Hi,

I had been using 2.46 on my S2 with 12.1 successfully for a long time, but on cm13 it does not work any more.

regards
[SuperSU] berlen:
in cm12.1 it was sufficient to boot and enable the root permissions via apps and adb and then flash supersu (I was using v2.46). Doing the same thing in cm13, even using v2.65/67, causes a bootloop. There is a root permission handler in cm13, but I am used to supersu (also because it removes a notification icon #)

So I was wondering if anyone successfully flashed supersu in cm13...
[SuperSU] Chainfire:
Not sure if you did or didn't do this, but for CM be sure to do this:

- wipe system

- reflash CM

- flash latest SuperSU through ZIP in TWRP (not CM Recovery, there is an issue with that under investigation)

As far as I know, there is no CM13-specific issue with SuperSU, it works fine on my test devices in combination. That doesn't mean there isn't an issue with specific devices running CM13 and SuperSU though.

One specific issue is that SuperSU may not be able to patch the kernel. Please review your TWRP log to see if this is the case!

I am working on a SuperSU update that should make these issues easier to diagnose, report, and fix.
[SuperSU] daniu:
Hi

Not sure if that only applies to the s2 but on the Galaxy S2 supersu does not work with cm13.

One point is probably selinux set to enforcing. Someone wrote that changing to permissive does not work and results in bootloop. Someone suggested that the reason is the kernel still booting with enforcing - not sure if this makes sense ...

Is toybox instead of busybox a problem for supersu? Would it help to install busybox additionally? Is that possible at all?

Atm there seems to be nobody able to use your supersu with the s2 under cm13

Regards

Sent from my x-phone using brain 2.0
[SuperSU] kh34d:
[MENTION=631273]Chainfire[/MENTION] +1

in my device doesn't work if my rom Enforce, but work if permissive
[SuperSU] daniu:
Hmmm ... it is in the op that selinux has to be permissive that is not new or are you saying that you also get bootloops when setting to permissive?

Sent from my x-phone using brain 2.0
[SuperSU] Chainfire:
Do you have a link to the exact CM13 ZIP you are using?

Whether the kernel still boots with enforcing depends on your method to set it permissive.

SuperSU works fine with toybox. As always, busybox is far more likely to be the problem than to be the solution to anything.

Put it in permissive mode, boot it up, and post the logcat.

If /data/misc/audit/audit.log exists, also post that.

Also, when flashing SuperSU, does it actually succeed patching the boot image?

SELinux does not normally have to be permissive for SuperSU to work.
[SuperSU] egingell:
Both of my phones are "enforcing" with them working fine and SuperSU working fine on both.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Bonoboo:
Can I answer for him?

We have same device, Sony Xperia M with CyanogenMod 13

SuperSU (any version, Stable or Beta) fails up at patching boot (just nothing changes), so we need to force "system mode".

When SELinux set to "Permissive" of course all fine.

Here I already monitored audit log and most interesting line is:

Our maintainer, [MENTION=4343949]PecanCM[/MENTION] said:

He won't made changes for 3rd party app in device tree, as we have official CM support (I guess so).

Is this "fixable" by SuperSU without editing sepolicy in ROM source code?

By the way, after flashing SuperSU in recovery.log supolicy tool states, that all patching went successfully.

For info, here our sepolicy.

P.S. Huge thanks for all your efforts.

P.P.S. Sorry for my English.
[SuperSU] 24imelqui:
I have the old supersu 2.46 thats comes with my ROM, stock ZF2 Custom ROM. Can I just directly flash it over the old supersu thru twrp w/o uninstalling?
[SuperSU] daniu:
http://pt.tapatalk.com/redirect.php...host.com/?fid=24407100847293134&au_id=3499916

Lanchon S2 trim enabled kernel

Sent from my x-phone using brain 2.0
[SuperSU] pkelly517:
First, your English is far better than my anything-other-than-English. In fact, I didn't think English wasn't your native language until that line. No need to apologize. I commend you..

And, if you continue to post with logs, details from other threads and such, post away. You are in the the top 10% of XDA already.
[SuperSU] Cellphonenote4:
I would just like to know how to use wifi tethering opition without having to pay extra fee to sprint. I use odin and rooted my phone but can not find right app to bypass the tether option on my phone. What am i doing wrong?
[SuperSU] daniu:
Why did you think this is the right thread for your question?

Honestly I don't get your problem but I am pretty sure you are in the wrong place ...

Sent from my x-phone using brain 2.0
[SuperSU] Chainfire:
I need a log of patching boot and know why that fails. System mode will not work on CM without modification that the maintainer doesn't want to do - for good reason!

What needs to be fixed is the boot image patching, in this case.

Thats just the kernel, what about the ROM itself?
[SuperSU] daniu:
sure - sorry ... I use: http://download.cyanogenmod.org/get/jenkins/148264/cm-13.0-20160208-NIGHTLY-i9100.zip at the moment.

But I guess the newer ones from here are not different ...

regards
[SuperSU] hgmichna:
Page 999

Does everybody see this thread at page 999? Not bad!
[SuperSU] Bonoboo:
Thanks for answer!

Attached full recovery logs after flashing Stable 2.65 and Beta 2.67

Used TWRP 3.0.0-0, of course same with older versions.
[SuperSU] Follow_and_Feel:
*Noob question*

Hey guys. I'm running CM13 on an LG G4 Intl. Just wondering....is there a way to enable backup script to survive CM nightlies with systemless root? Or in any way? Just curious. That would mean that I don't have to flash SuperSU.zip every time I flash a new nightly.

Is there any way to get this feature working in SuperSU app?

Sorry if the question may sound dumb

Cheers mates :)
[SuperSU] Naudiz:
Not sure if this is a bug or intended:

If you flash SuperSU with /system unmounted, it will ignore .supersu file residing there,even though it does mount /system as a first step itself. I always have to manually mount /system in TWRP to prevent systemless mode, which doesn't work on CM12.1 for i9100.

Which leads me to the next question:

I read the notes inside updater-binary and if I got it right, SuperSU should always try system-mode first on Lollipop roms, right?

So I was surprised, why it tries systemless on CM12.1 on my Galaxy S2 (and fails).
[SuperSU] loonie01:
I'm getting the same update error.
[SuperSU] yreham:
Installed by flashing with 4ext recovery no wipe and everything went well except that I have Pdroid installed and it doesn't see it like it used to see superuser. Bravo mildwild cm7 rom and kernel.

Before I did this I installed from the market and nothing was working so I uninstalled it (maybe because it wasn't installed in the file system, like when I flashed the zip)thank you chainfire
[SuperSU] Chainfire:
v0.73 was just released, it should fix a few issues. Sorry for the rapid succession of updates, but I've been having about 12 conversations crossing eachother trying to get some issues fixed.

v0.73 is now on Market, or available as CWM ZIP that only works for some people in the first post.

Hopefully that takes care of the bulk of the issues.

There's a lot more stuff to fix though, so it'll be an interesting few days!
[SuperSU] velopirate:
Exact same issue on my Droid Razr Maxx
[SuperSU] vwvanman:
On SGS2 running ICS, installed okay, opened and tried to update the binary buy this failed. but now seems to be working and managing SU permissions.

Biggest problem is when I open the app I get an error saying "there is no super SU binary installed and that it can't instal one. This is a problem."

when I tap OK, the app closes.

Any ideas?

Thanks
[SuperSU] Chainfire:
Update to v0.73

Update to v0.73
[SuperSU] madd0g:
Fixed the installation issue, thanks for the prompt update.

Have a suggestion though: can you set the Grant action to be on the right on ICS (like OK button) ? It makes it more consistant with the system (you get used to right side OK button on ICS).
[SuperSU] velopirate:
Installing the latest version worked like a charm! Just purchased a Pro license. Thanks so much!
[SuperSU] yreham:
If we had already flashed 0.71 can we flash 73 over that
[SuperSU] Chainfire:
This will probably happen in an update soon, yes.

Yes!
[SuperSU] yreham:
I have Pdroid installed and it doesn't see this app like it used to see superuser
[SuperSU] codesplice:
.73 seems to have fixed it - thanks ChainFire! Pro order on the way :)
[SuperSU] vwvanman:
Fantastic, working now

Thanks
[SuperSU] XDA mark:
Just installed .73, everthing seems fine. I opened Voltage Control, SetCPU and Chainfire 3D and SuperSU asked for permissions. When I open other apps like KitchenPro (S II CheckROM app) or Voodoo Louder it does not ask for anything. I still have SU installed, maybe that is the doing the job for those? Sorry if I missed a comment regarding this but with so many comments comming so fast I might have missed something.

Anyway, really respect your work Chainfire

Edit: Titanium Backup and Root explorer work too.
[SuperSU] SaschaHa:
0.73 does not work for me :(

After installing via CWM all root-apps does not work anymore. If I try Superuser to get the binary updated, it fails because of denied permissions. Any way to get SuperSU get deinstalled and to get the old binary?

Edit: Galaxy S2, XWKK5, Siyah-Kernel v2.6.13

Edit 2: SuperSU says, the requesting app has SU, but it doesn't...
[SuperSU] qzfive:
CWM Recovery gives error 0 when trying to flash via recovery :(

HTC Chacha, CWM v5.0.2.8
[SuperSU] nicholaaaas:
i flashed my rom again (no wipe) and update the binary then deleted superuser. everything seems alright now
[SuperSU] Benzoman:
Never mind of course... I'm just too tired is my only problem, well, besides ignorance.:p
[SuperSU] elartista3390:
great,it is the best,thanks man!:D
[SuperSU] retnuh:
What I have found is, you must have usb debugging turned on. NONE of my apps that require root access will work unless I have it turned on. Superuser did not require this.
[SuperSU] cortezone:
SuperSU binary update failed

I'm in a bit of a pickle with SuperSU. I had superuser elite installed and working then when I upgraded my Samsung galaxy SII ROM to ICS I installed SuperSU with CMW. After this upgrade nothing works. I tried to uninstall SuperSU but after uninstalling it appears in Play Store asking to update (alternative is open).

I've uninstalled superuser elite but still now show. When I try opening any app requiring superuser access I get a message saying that the app has been granted but none of the apps work.

I'm quite stuck and contemplating reflashing my ROM. BTW I got the pro version. I've attached an alogcat output perchance this can help the gurus locate where my problem is.

Cheers
[SuperSU] nkojic:
Well i can not unninstal superuser totally. Dont know why. But i can install supersu. So i will try to install fresh rom and try to get logcat then. But the problem is in update i am sure because everything works with supersu that comes with Mikes rom
[SuperSU] coldcaffeine:
With superuser installed, install SuperSU. Load SuperSU and update the binary. Then load a file explorer with root r/w access like Root Explorer. Most likely you'll find superuser.apk is installed in /system/apps. After updating the SuperSU binary, you can just delete the superuser.apk.
[SuperSU] nkojic:
So what is the problem in my supersu update??