yashsingh1/xdaforums huggingface dataset:
[SuperSU] Aservatenkammer:
In Germany also.

http://www.isup.me/chainfire.eu
[SuperSU] shaggyskunk:
Here's a link to my Dropbox for SuperSU v2.42 beta - to help people out while Chainfire's link is down

I really hope that Chainfire doesn't mind - I'll delete this link as soon as Chainfire's link is up....

https://www.dropbox.com/s/npeh8qelstetiip/BETA-SuperSU-v2.42.zip?dl=0
[SuperSU] wildnet:
it looks like LeaseWeb problem?
[SuperSU] drinkypoo:
download site is not responding

And all the random download sites which claim to have it look suspicious
[SuperSU] shaggyskunk:
Well - I assure you that the download link I posted - is Chainfire's beta - I'm running it - So my reputation is on the line.... Your choice
[SuperSU] drinkypoo:
Well, I assure you that the download site you posted is down or at least unreachable, as I said. I know the official download site is good when it is up because I downloaded it and used it on my moto g 2nd while it was up. But now it is down and I no longer have the file and would like to find an ALTERNATE download site which is not dodgy like the ones I find with google
[SuperSU] shaggyskunk:
It's not a download site - it's a link to my Dropbox - where I uploaded Chainfire's beta 2.42 - appreciate it or don't - your call.
[SuperSU] oranget:
Downloaded and installed fine here..thanks for the link to new Super SU 2.42!
[SuperSU] skidaway:
If you download from anywhere else, make sure the checksums match. Here are the ones from BETA-SuperSU-v2.42.zip downloaded from chainfire's site when it was released last week:

md5:

cb35e43838d89a29a61d88f3496ee5da

sha-1:

73a9e57994d5fba0ea0349c35e0136acb9ebc9d2

Personally, I would wait for an official mirror or response from chainfire before downloading from anywhere else.

edit: the file shaggyskunk posted matches.
[SuperSU] greogory:
I definitely appreciate it, so thank you for helping out.

I figure you must have a really good reason for requiring my SSN, bank account numbers, PDF of my signature, certified copy of my birth certificate, and my mom's maiden name, otherwise you wouldn't have asked, right? Everything else makes sense, since you said you'd hook me up with a trustworthy Nigerian prince. But I still don't understand the relevance of my shoe & waste sizes, and inseam length. But you know what you need to do things the right way better than I do.

BTW, my certified DNA and complete genome reports should arrive Monday. They got delayed because the nice Russian men with all those interesting tattoos who take care of all my business paperwork said they needed an extra day off to play Whack-A-Mole™. I guess they take their friends to Chuckie Cheese on holidays or something?

;)
[SuperSU] Scurzmann:
Thanks for the link bro.downloaded,installed and works well:D
[SuperSU] drinkypoo:
There's no need to be so defensive. I do appreciate it, now that the site is back up. I didn't appreciate it when it was inaccessible for a while, since I couldn't use it. Now that it's back, I appreciate it again.
[SuperSU] rogersb11:
I'm with you. I build my own philz so I have the final official version but runs like a champ on L while I continue to read if twrp issues. New update apparently fixes it but I won't be leaving my trusty Philz unless I am forced and even then I'll probably just update my own device tree
[SuperSU] Manuel15:
Well, I have TWRP, I had no issues
[SuperSU] shaggyskunk:
Sorry if I came across as being defensive - I just would never knowingly post a link to anything harmful ;)
[SuperSU] popliuc:
Link working now
[SuperSU] wildnet:
servers is online now ;)
[SuperSU] mindmajick:
Shaggy is a trustworthy good ol dude. I'm sure it just offended his honor... As it would mine. Everything resolved now ?.

Back to your regularly scheduled repeated questions.

-> Sent from my mind to your screen
[SuperSU] egingell:
The point being that it only deletes files related to SuperSU. No user data. It doesn't even revert any changes to system files.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] persona78:
Huawei ascend g6

All right ?

I have a HUAWEI ASCEND G6 and had problems in root because I could not remove the Kinguser without removing the root and the SuperSu even with permissions not settled, and i started to have problems in phone which forced me to leave the system in the rom, and i found what follows: http://huaweidevices.ru/r2534oe3m5k...wei_Ascend_G6-L11_V100R001C00B127_General.rar

It works but now I can not install SuperSu at al... :\

Help please.

Thanks
[SuperSU] loco1911:
Great

is the best superuser application ;)
[SuperSU] TechPlease:
Download not working.

I'm trying to download SuperSU from cf.morose.nl, but it looks like the server is down right now. Any solutions on where to get it?
[SuperSU] Pkt_Lnt:
post #1
[SuperSU] TechPlease:
Post #1 ultimately takes me to cf.morose.nl.
[SuperSU] Pkt_Lnt:
Weird. i see http://download.chainfire.eu/supersu
[SuperSU] TechPlease:
And that, when the link within is clicked, takes me to cf.morose.nl.
[SuperSU] Pkt_Lnt:
Do you have a proxy? It sends me to

http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
[SuperSU] TechPlease:
I don't think so, how would I tell? Your link worked perfectly though. :)

When I looked at the link it was : http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip?retrieve_file=1
[SuperSU] dj4n90:
nexus odexed 4.3 (JWR66Y) bootloop

Installed latest update (v2.4) (from playstore) to 2pc Galaxy Nexus "maguro" yakju

Both ended up in bootloop. :(

Did "normal" update , after that SuperSu gave choice ok-reboot

On both picked ok , phone boots en goes into bootloop.

Was able to break the bootloop with cf-autroot. (reinstall) :D

Hope this info helps.
[SuperSU] jignesh2594:
can't download!

i can't download update file from the given link!

HELP!:crying:
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=57827397&postcount=8040
[SuperSU] jignesh2594:
link!

Link is working but i can't download the attachment!

[IMG="Attachment is not working! it shows as in image"]http://xdaforums.com/picture.php?albumid=11713&pictureid=47400[/IMG]

Reupload the file!
[SuperSU] Pkt_Lnt:
Must still be data center problems. His CFAutoRoot site got hammered after Christmas.

https://twitter.com/ChainfireXDA/status/549148095553216512
[SuperSU] jcfunk:
the tmp-mksh is not loading libs properly. I'm getting this errors, first was thinking was a bad lib. Traced it to your shell. Never had issue until I moved to newer android other SUs don't work. Was using miui's in ics rom.

ERROR: ld.so: object '/vendor/lib/libNimsWrap.so' from LD_PRELOAD cannot be preloaded: ignored.
[SuperSU] Chainfire:
Again, it's not "my" shell, it's just a copy from /system/bin/(mk)sh. You're still barking up the wrong tree.
[SuperSU] jcfunk:
No problem, if no one else notices. Just annoying when it popping up every command when in chroot doing linux on android. For me, I fixed by switch to CWM su, which has a problem of going back to / when called.

If its just a copy from systems mksh, then problem lies with mksh from stock rom. Which is very possible, I have tried to change tmp-mksh binary but that cuased errors.
[SuperSU] Chainfire:
The problem is in fact not with mksh, it's with the ROM. unset LD_PRELOAD
[SuperSU] Sachiru:
Currently using Oppo Find 7a on ColorOS 2.0.0i. Root works, however whenever I update SuperSU if it tries to install an updated su binary the installation "succeeds", but upon restart root is lost and SuperSU cannot reinstall it. Any tips on how to update to latest SuperSU on ColorOS 2.0.0i? I have pro version and it would be nice if I can use all updated features...
[SuperSU] xsteven77x:
Best Superuser app in existence for android! Keep up the great work!!!
[SuperSU] leech4:
Help updating SU binary

I have an android PC stick (MK809IV Kitkat 4.4.2 with Rockchip Rk3188T inside, No brand)

I tried to root it manually throug adb using different su binaries, all are said not found when using SuperSU except one.

For this last su binary, SuperSU prompts me that binary must be updated but fails to do so.

Mounted system rw, pushed files in correct locations and changed permissions and ownership of files but still fail to update.

My question is : can I do this manually by using included su binary inside apk and if yes, which one should I use (I think Rockchip RK3188 is Cortex A9 SOC)

Should I use the arm version ? if yes what did I miss ?

Please help !! Because I cannot get root to work properly (Through adb I have ID : root@rk3188:/ #
[SuperSU] riccardo91:
I have problems installing the binary updates on an Alcatel Pop C7 (normal method): JellyBean 4.2.2, Kernel 3.4.5. I rooted succesfully with Kingo User :(
[SuperSU] russellvone:
unroot completely

then re-root with Kingo

install superSU and give root permissions to it via Kingo

don't try to update or anything just back out of superSU

then install a root explorer and give it root permissions and go to

/system/app/

and delete the Kingo app

then return reopen superSU and allow it to do it's thing
[SuperSU] HassanM:
A very happy new year to everyone.....
[SuperSU] sasaphrazz:
Can someone help? I keep getting installation failed after trying to update binary. LG G3 on CM 12 beta.
[SuperSU] Scurzmann:
Same to you too bro!:D:thumbup:
[SuperSU] abalam:
Haha
[SuperSU] bityfne:
Is there another place i can download superSU.zip ... every search i've done has taken me to chainfire.eu but the site is down apparently. Or is there a easy way to make a flashable zip with the apk?
[SuperSU] remicks:
SuperSU Mirror: http://downloads.blissroms.com/Add-ons/UPDATE-SuperSU-v2.40.zip

<- Click me for m8 downloads!
[SuperSU] bityfne:
omg thank you so much.. i was literally stuck in the middle of rooting my tablet lol
[SuperSU] remicks:
No problem, glad to help.

<- Click me for m8 downloads!
[SuperSU] bkayy:
Thanks now rooting my nexus 7
[SuperSU] riccardo91:
Deleting was impossible, I don't know why. But I solved unrooting with Kingo, rooting with Rotgenius, I installed supersu from play store, I gave permissions to supersu and updated binaries :)

Happy 2015!
[SuperSU] gh0stshell:
Binary Update Prompt

After updating SuperSU, which is awesome BTW and I have used others and always go back to your SU app, anyway, after updating when opening the app it should prompt me to update the binary until I do correct? If, not is there a way to tell what binary is installed and if not current a way to trigger a way for it to be checked/scanned so it does get updated?

Also what does the disable KNOX do? I already manually disabled the APK for it and other system apps I dont want running without my express consent like OTA updates.

Thanks in advance!!

Reading the post above mine, I never had to give SuperSU permission to do things, just apps like quick boot and hostname changer to proceed with changing the hostname or rebooting my phone.
[SuperSU] remo0073:
To verify root, binary and busybox I use this app

https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator

Sent from my Moto G
[SuperSU] Scurzmann:
Type "su -v" in terminal to determine what binary version is installed
[SuperSU] lil.masoud:
It worked on htc chacha very well,,,tnx a lot:thumbup::thumbup:
[SuperSU] motisu:
insufficient free storage problem again

Hi Chainfire,

I installed via CFAR Supersu which automatically upgraded itself via playstore to 2.40 and is working with most of my apps. However, I am getting the insufficient storage message with TiBu 6.0.3. As per instructions, I turned off the namespace option as well as tapjacking. I still am getting the message. I am running stock samsung 4.4.2 with NO changes other than Supersu installed on my Tab4 10.1".

Any suggestions?
[SuperSU] Playdoe:
kinguser /su issue

Hey guys,

Don't know if this is the correct place to post this question but it's now 6:00 am. And after countless hours searching the web i can't seem to find a solution. I have a Zte n9520 also known as the Zte max or Boost Max. The only option so far to root the phone is using kingo which as most of you know installs kinguser (supposedly a Chinese version of SU) among with kinguser the root installs SuperSU, and I knowing SuperSu prefer the app. UPON root both apps ask for superuser and then kinguser takes over, while SuperSU continuously tells me on my notifications that my binary needs to be updated. I try the normal method and the Twrp method to no avail. I'm an intermediate at rooting but I'm guessing my apps constantly crashing and force closing is due to this binary update but being in place. In one thread I read to try to get rid of kinguser move the su from xbin/su to bin/su and try to uninstall kinguser, problem there was my file manager..even with root rights will not allow me to get rid of the xbin/su..maybe I'm supposed to or not..i thought it'd help. So any help would be appreciated. I really would rather have my good ol' supersu than an app I barely know. Any help would be appreciated. And is updating the binary the issue making my apps crash?
[SuperSU] Chainfire:
New beta released. http://download.chainfire.eu/692/SuperSU/BETA-SuperSU-v2.43.zip. See BETA thread here: http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] Arisey:
Muy buena aplicación esta heeeeee y necesaria jajajajajajaj felicidades
[SuperSU] Strephon Alkhalikoi:
[MENTION=6153712]Arisey[/MENTION]: Please post in English. It's a site rule.

Google Translation

Arisey: Por favor, publique en Inglés. Es una regla de sitio.
[SuperSU] Arisey:
Ok very nice
[SuperSU] rik91:
Great job.
[SuperSU] motisu:
TiBu problem update

I don't know if this problem is with TiBu or with SuperSu. I moved the TiBu backup folder from external SD to internal and the batch backup works without any problems. I moved it back to externalSD and the problem comes back.
[SuperSU] white7561:
If u use samsung. Theres a problem that u cany write external sd. So u must edit some permissions on /system/etc/permissions/platform thingy
[SuperSU] motisu:
Yes, it is indeed a Samsung Galaxy Tab 4. Can you please be more specific about what needs to be changed?

Edit: never mind, I found it once I knew what to look for. Thanks for pointing me in the right direction.
[SuperSU] rogers11:
This worked on my wife's S4 mini in this case.
[SuperSU] Chainfire:
It is pretty bad if modifying that permission is actually the fix - TiBu should take care of that itself.
[SuperSU] remo0073:
Did anyone use CF-Autoroot on Moto G GPE with Lollipop 5.0.1?

Thanks in advance.

;)

Sent from my Moto G
[SuperSU] tilo140380:
great work :D
[SuperSU] motisu:
[MENTION=631273]Chainfire[/MENTION]:

It did solve the problem and I apologize for even suspecting that it was a Supersu bug.

I am surprised that TiBu didn't even mention it on their troubleshooting site, but I would really expect Samsung to fix this as it is a MAJOR inconvenience.

Ah well, at least I've learned for future use and to heads-up others who may need this information.

Thanks again for all your hard work.
[SuperSU] CyberpodS2:
There are "fixes" for that across the S5 forums also. It seems to be intentional on Samsung's part as part of their hardening security along with the Knox Crap. Most custom roms are patching that now on the Verizon S5.
[SuperSU] HassanM:
Waiting for the updated version.... Although the Beta version 2.43 is out.... Im sure the King of All - [MENTION=631273]Chainfire[/MENTION] is working on it.....
[SuperSU] gorilla p:
Hey [MENTION=631273]Chainfire[/MENTION] On having trouble with the latest 2.43 beta.

I'm using BoldBeast call recorder and after updating from 2.40 to 2.43, I started having trouble gaining root access. Ive tried having SuperSU reprompt for root and it states that root was granted, but it doesn't work.

I also set SuperSU to grant access to all requests and that didn't work either.

It is resulting I. The following error in the logs.

01-03 11:48:40.889 E/libprocessgroup(13552): failed to make and chown /acct/uid_10071: Read-only file system

01-03 11:48:40.889 W/Zygote (13552): createProcessGroup failed, kernel missing CONFIG_CGROUP_CPUACCT?

"I like my Nexus 4 and my Unicorns Dirty."
[SuperSU] BathroomTile:
Finally updated to stable version 2.40 from 2.35, yay! I checked "Reinstall," and the "uninstalling" pop up remained on the screen for about 30 minutes, so I was afraid something broke. I closed the app, reboot the phone, hit "reinstall" again, and finally it worked properly. Rebooted from there, updated binaries, and everything seemed to go smoothly. Thanks for the progress! :)
[SuperSU] Chainfire:
Neither of these errors have anything to do with root.
[SuperSU] gorilla p:
I've confirmed it has something to do with 2.43.

I went back to 2.40 and it was working fine.

I went back to 2.43 and it failed again.

I went back to 2.40 now and it is working fine e again

Something changed from 2.40 to 2.43 that is causing root to fail.

"I like my Nexus 4 and my Unicorns Dirty."
[SuperSU] Chainfire:
I'm not saying the problem doesn't exist, just that those error lines you quoted aren't the cause (they could be one of the symptoms though). Please check if the situation occurs with 2.41 and 2.42 to further narrow down the issue:

2.41: BETA-SuperSU-v2.41.zip

2.42: BETA-SuperSU-v2.42.zip
[SuperSU] methuselah:
regarding ota

[MENTION=631273]Chainfire[/MENTION]

i have a very genuine question if you shed some light it will be great. I use Moto G XT1033 first generation. Well Motorola is about to push lollipop updates on this version too. I rooted last year in may. Now some nexus users are reporting that their ota failed because they are rooted. As Google owned Motorola at the time when the moto g was launched it means probably there is some similarity between the ota's hat land of both phones..

Now my question: I have created a backup of official ROM 4.4.4 with clockworkmod recovery at the beginning when i rooted my moto g., so if i restore that backup and use the option from the supersu to completely wipe away root functionality will be able to get back my ota. unlocked boot-loader is not a problem. that backup is still enact in my laptop. i will revert back to that backup once ota notification available on my screen. Will supersu allow me to get it properly ?? What you say about this ?:confused:
[SuperSU] Chainfire:
2.44 beta released! See http://xdaforums.com/showpost.php?p=55256620&postcount=1.

Got myself a Moto G 2014 (dual sim) to try and figure out what the problem was. Works fine for me now, let me know if *any* bootloops still occur for you MotoG users.
[SuperSU] methuselah:
well awesome that you holdsmoto g xt1033 now.. will reply back as soon as i will get a notification on my phone that there is a update is available for lollipop...

but i asked that when the update comes on my notification screen like "lollipop update available" then if i choose the unroot option from supersu menu will i able to install the update normally without failure ?
[SuperSU] Rinoceros:
This is a Beta! And so not available via the Playstore.

You need to flash this manually through recovery.
[SuperSU] luca020400:
As you said : it works perfeclty with moto g 2014

Great work !!
[SuperSU] methuselah:
well i know that

well i know that lol....read my question what i asked him.
[SuperSU] Rinoceros:
I DID read your question, but you are expecting from Chainfire to test his peace of software on ALL Android phones, even the rare one like yours.

That is completely impossible for Chainfire. He is relying on people to will try this on their own phone.

If you don't like it to do it on your own phone then wait until someone has done it on a phone like yours.

If you want the benefit of a rooted phone, use the software and take the risk, but don't ask here if it works. With you are thousands of others and it will be a complete mess here if all those people ask these question: "will it work on my phone?"
[SuperSU] methuselah:
Well I didn't asked him to try. I asked him whether it can withstand or not . I never meant to ask him about trying himself moreover he got his life too, to look after. What I asked what is his view that could supersu removal will allow me to install ota lollipop. He got best knowledge about super su coz its his brain child creation.. Its my mistake if I was heard like , that please try yourself and then tell me. The last thing rest on me exactly whether to try to use this option myself. Well this is Dev thread and I won't make it more of talking thread....
[SuperSU] HassanM:
I hope [MENTION=631273]Chainfire[/MENTION] comes up with the stable update soon (after the current 2.40).....
[SuperSU] 089man:
2.44 works great here. Never I had problems with a build. Used pro version and flash every time the update zip. Used Samsung s2 with lollipop based on cm 12 unofficial.

Thanks Chainfire for many years great work and great working SuperSU... Never I used the superuser free version included on difficult roms.

I9100 Tapatalk 4, RR 5.0.2 Lollipop
[SuperSU] okidokiss:
Exactly the same here.

TY Chanfire.
[SuperSU] GroteBozewolf:
Just read the beta thread and see if it works on your brand phone. If so, flash the beta. Unless many people report issues it is usually stable.
[SuperSU] efrant:
Unless something has changed in the beta versions, the answer to your question is probably not. Based on my personal experience (on a Nexus 5), it seems like the "full unroot" option does not revert the install-recovery.sh file back to what it was, and thus the update would fail (unless of course you replace that file with the stock one).
[SuperSU] pkelly517:
I have 100% confidence it will happen...

When it's ready.

That's generally when updates happen.
[SuperSU] CyberpodS2:
There is nothing wrong with the last batch of betas. I have run every one without issue on the S5.
[SuperSU] pkelly517:
I agree completely.

My point was that he shouldn't ask when the next stable version is released. It will happen when Chainfire feels it's ready.
[SuperSU] methuselah:
Well that read I will do one thing flash whole stock firmware again. Thank you from guiding me in the direction
[SuperSU] baltics:
I loaded the latest beta version and it has silently denied greenify. The SuperSU log advises it is only available in the pro version.
[SuperSU] fs71gh:
No UI in 2.40

Flashed 2.40 over 2.02. It results in no SuperSU icon or inside-settings SuperSu I get. The inside-settings Superuser does not also take to SuperSU.
[SuperSU] Deltadroid:
[MENTION=631273]Chainfire[/MENTION]

The backup script created by SuperSU is overwriting a file on rom updates. I have removed /system/bin/log from the backup script to prevent it from being overwritten. Also, the backup script is not restoring SuperSU properly with CM12.

--- 99-supersu.sh.orig	2015-01-08 22:59:09.478308800 +0100
+++ 99-supersu.sh	2015-01-08 22:59:18.102308794 +0100
@@ -19,7 +19,6 @@
xbin/otasurvival.sh
lib/libsupol.so
lib64/libsupol.so
-bin/log
bin/.ext/.su
etc/init.d/99SuperSUDaemon
etc/install-recovery.sh

Best Regards
[SuperSU] mdj87x:
Thanks for work. Can i try 2.44 v on G S 4 mini 9190 ?
[SuperSU] oranget:
Just updated to new 2.44 SuperSU..no problems.
[SuperSU] PAGOT:
I am sorry if this is OOT, but maybe somebody will point me ot the right direction.

I was using an Xposed application to hide my root. Since Xposed is not working on 5 and I recently installed CM12

I disabled the Root via the developer settings of CM. This did not help.

However and this is why I am posting this here, SuperSU option to permanently remove Root did .

Its funny but right now whenever I flash a nightly I have to:

1. enable root in developer settings

2. install SuperSU

3. Permanent Unroot(or whats it called, cant go into the App now as the Device Admin app is watching) via SuperSU

4. disable root in developer settings

5. reboot

To get rid of Root to be compliant.

Anyone here with some better advice?

Also thanks to Chainfire. Its funny that I have to use a SuperSU app to remove root from another source ... but at least thanks to this I seem to be compliant and don't have to go back to KK.
[SuperSU] hosseinhk:
I using 2.44 pro it's work fone