yashsingh1/xdaforums huggingface dataset:
[SuperSU] indestructible master:
No SU binary??? .....

I downloaded kingroot again and superSU appeared and asking for root permision O.O wtf??? I dont know what really hapened ... and then i deleted kingroot in that moment, and went in superSU and it asking me to update SU binary ( and a moment ago there wasnt any SU binary code ?? IDK what happened) and i asking you how to update SU binary (is there some files or something) and please explain it nice ( with what app if needs) because i am a begginer with root but not with other stuff ;)
[SuperSU] Manuel15:
There is a thread for binary update issues

http://xdaforums.com/apps/supersu/support-update-failures-t2907365/page57
[SuperSU] Ratawar:
[Error] Moto E1 custom rom binary update fail

Hey guys, in my Moto E 1st gen I'm using this rom

[ROM][6.0.1_r10]Temasek v3.1 for moto E [UBERTC 5.3][STABLE][21st jan update]

and I can't seem to get the binaries updated, I tried both ways, and still. Is there a solution? I'm a newbie, I cant post on the rom's thread.
[SuperSU] kemz_a:
Noob question: currently on su beta 2.66, I see now that 2.67 is out. Are there any special requirements to update to the new version or can I just flash the zip in twrp and be ok?
[SuperSU] egingell:
Go to the correct thread and read it.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] Pkt_Lnt:
There is an entire thread for binary update failures. The link is in post 1 or just go the the whole Super SU forum and look at the topics.
[SuperSU] koko115:
I can install supersu 2.67 on galaxy s6 5.1.1. Twrp give me ramdisk patch failed. After reboot no su binaries.
[SuperSU] HorstiG:
Read please

HGT - Galaxy S5 G900F - LG G4 - OP2 - Tesla TTL7
[SuperSU] Pkt_Lnt:
You can get support in the BETA thread, not here in the STABLE 2.46 thread.
[SuperSU] waheedzaman1998:
Hello Sir!!

I've rooted my android vgotel VENTURE V2 with installing super su directly!! And it just installed binary and it worked but now!! I rebooted my mobile phone and it just lost the root access and it shows that upgrading binary but always fails in upgrading binary and now my phone is stuck between noon rooted and rooted phone :(

I tried factory data reset but still it's having the same problem and it can't upgrade it's binary :(

It can't open in recovery mod as well now whenever i try it opens up in factory mod to check the functionality and that's all okay!!

I need help :(

please can anyone help me :(

I'm really worried I'm not a beginner at root i can root any non rooted but how to root a stuck phone between root and unrooted i don't know!! PLEASE!! Help me!!
[SuperSU] Pkt_Lnt:
Post #1 has a link ot the thread about binary update failures.
[SuperSU] waheedzaman1998:
There's no thread for binary update failure ut just says why it fails!! And I've not done anything as such :(
[SuperSU] egingell:
Yes, there is, right there in the OP just as described.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] waheedzaman1998:
Sir I'll add screenshots for yuh!! I hope u get it but it just simply shows me a pop-up that su update failed
[SuperSU] JedNote2:
Go here http://xdaforums.com/apps/supersu/support-update-failures-t2907365 then post your problem. As everyone said, it's in the OP.
[SuperSU] waheedzaman1998:
It's all what it showed :( :'(

Please help me

I want my device rooted
[SuperSU] waheedzaman1998:
Help mee!!!!!
[SuperSU] Pkt_Lnt:
Come on man!

http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] JedNote2:
[MENTION=6671632]waheedzaman1998[/MENTION] Mate, post all your problems on the link provided to you already. That's the right thread for that and not here.
[SuperSU] waheedzaman1998:
I need help i know the developers can do it!! But the problem is contacting them!!
[SuperSU] JedNote2:
If you want help then post it in the right thread. That's why there is a specific thread for problems like yours for the dev to easily help you out. You can also search in that thread about that problem as I assume that is a common problem for a lot of android phones who attempts to update the binary.
[SuperSU] waheedzaman1998:
Okay thanks mate
[SuperSU] Pkt_Lnt:
The devs are not going to hold you hand and spoon feed you. Look at the numbers of this site man. You are not going to get dev help in this thread. You need to post in the correct thread and do your part to help yourself.
[SuperSU] gorilla p:
Also what is not clear, is if this device was rooted to begin with, or did the user just download SuperSU and hope for root?
[SuperSU] Captain Ayush:
I Usually update su binary with the normal mode, I click on update normally , it takes a few moment and those binaries are updated but a reboot might need ........ I use king root as my root gainer and I also recommend it to my friends too super su gives many problems...........

I hope this might be the answer to your question........
[SuperSU] Gaurav Mehra:
Root ot again
[SuperSU] lenovo P780 Life 07:
No, there is not, I am loking in Main Settings menu and Develeper options settings - super SU no there.
[SuperSU] indestructible master:
Okay,.... but reason for deleting kingroot is because it have malware named PUP.Lotor i used app malwarebytes. Can i just delete that file without deleting kingroot. That is my reason for doing this all. Have you ever have problems with that app.
[SuperSU] Manuel15:
Don't trust that malware warning. Sometimes the apps that use root are recognized as malware, but they're not
[SuperSU] gorilla p:
Theres a kingroot and kingoroot. 2 different apps. Often one works while another wont.
[SuperSU] rfec:
Works fine, thank you. :)
[SuperSU] :
I'm coming from the old 2.52 root to systemless 2.67 on nexus 6P. No kernels. Stock Rom. On 6.0.0 atm

Should I do anything special before updating ??? ???

Like should I do this FSTABSYSTEMRW=true>>/data/.supersu

Or this echo BINDSYSTEMXBIN=false>>/data/.supersu

❔❓❔❓
[SuperSU] fubo73:
Wrong thread. Go to beta or wip ones.

Sent by my SM-G900F, aka Galaxy S5
[SuperSU] vj127:
What version of supersu should I flash for cm13?
[SuperSU] shaggyskunk:
If you're already running CM13 - SuperSU should already be built-in - You can always Flash v2.52 if you want.

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] roymckinney21:
Nicely stated
[SuperSU] didier57:
Hi , I can install this version on my Oukitel K4000 ?

Edit:

I confirm , it works !!! Thank you again Chainfire and again for your valuable work !
[SuperSU] Krunk83:
So I did a factory reset and flashed SuperSU 2.67 which is supposed to be systemless. When I do the check via SafetyNet helper it fails meaning that I do not have systemless. I have checked my system files and I do not have a /su folder in my root directory even though I am gaining root to the apps that need it. Can anyone help me figure out what is going on? Seems strange unless I am missing something. Also, when I reboot from TWRP it is not asking me if I would like to root via TWRP anymore which tells me something isn't right. It always asks me that and I tell it to not install. I'm on a nexus 6P with the latest cataclysm ROM.
[SuperSU] mraliaras:
thanks you great
[SuperSU] egingell:
Factory reset *only* wipes the data partition. It does not restore the factory system. And my understanding is that the script installs over the existing su binary which is still in /system/bin.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] Krunk83:
Any way I can fix this?

Also, to be more specific I wiped everything but data, then flashed the ROM, kernel, and SuperSU.

Nexus 6P
[SuperSU] egingell:
Firstly, the beta thread is where you go for support with the beta. Secondly, if you flashed a rooted ROM, then you will never get systemless unless it's built into the ROM. If it was not a rooted ROM, then I don't know. Either way, the beta thread is where you need to go.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] endrue:
pleass elf my updete lolipop

EDIT - English translation......please help me update lollipop............I'm assuming he wanted a cherry bomb or ice lolly instead
[SuperSU] murrder:
Access denied :)

Hello! I'm wondering if anyone can help me with my problem... Since I can't update photos because I'm a new user, I'll try to explain what's happening...

I've rooted my lenovo tab 2 using the method found on this forum (thank you very much for that), but I have problems giving root access for an application...

1. I've checked if my tablet is rooted using "Root Checker Basic" from GS and it's ok

2. Open the application, a message appears asking me if I want to grant access root, ofc I chose "GRANT"

3. I receive a message from SuperSu Pro, saying that the application has now root access, but at the same time, I receive another message from the application, saying that the root access failed...

4. I check in SuperSu Pro, to see if the app has our not access, and it does

5. Going into log messages, I found one message in red, which I think it's the reason for all of this:

"WARNING : linker : data/data/

com.xmodgame

/cache/injecttest/injecto_21 has text relocation. This is wasting memory and prevents security hardening. Please fix.

255"

Can someone tell me how to fix this?

Thank you very much in advance!
[SuperSU] rich34602:
Where the heck do I go get Su with new path?
[SuperSU] 2x4:
if i have v2.66 (systemless) install, can I just flash 2.67? (i don't care if this switches me over to system)

Will I need to reflash kernel or vendor image or anything again?

Nexus 5X, purenexus rom, systemless (supersu 2.66), xposed, EX kernel
[SuperSU] Pkt_Lnt:
Those are BETA versions and the BETA thread has your answers before you asked.
[SuperSU] 2x4:
I apologize, I looked on there before posting as well but must have missed it. I will look again.
[SuperSU] Pkt_Lnt:
If you cannot find it with a search, then ask in the BETA thread, 99.9% of the BETA users are there.
[SuperSU] mrrocketdog:
lol. and the other 0.01% are here. good work in this thread. [MENTION=4403217]Pkt_Lnt[/MENTION]. appreciate it.:thumbup:

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[SuperSU] murrder:
No one can help me? :(
[SuperSU] :
Do you have a custom recovery? If so, flash the supersu zip in TWRP/CWM and all will hopefully be well.
[SuperSU] murrder:
I've done that already, but with same results :(
[SuperSU] Evanescent:
pro version give the update for beta version? thank you in advance! ?
[SuperSU] Raymond Harper:
Stable supersu me

I can download but when I hit the blue button it only goes about half way and stops. What can I do?
[SuperSU] yarmuhammad:
Install help
[SuperSU] Chainfire:
FYI, v2.65 is currently in staged roll-out on Play.
[SuperSU] ritzusan:
Convert to /system app is disabled

Hi,

I need to prevent users to uninstall supersSU from the phone but the /system Install option is disabled: "Not (currently) available in system-less root mode"

How can I do?

Thank you very much!

The phone is a rooted Samsung J5 with android 5.1.1
[SuperSU] mrrocketdog:
this is prob. the noobiest question , but here goes ; will v2.65 work on lower versions than MM ?

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[SuperSU] IronTechmonkey:
Maybe I've missed something in the ongoing thread dialog but the now closed WIP thread mentions latest WIP (2.67) going to beta and the OP here refers to v2.6.5 but the link in OP here is to BETA-SuperSU-v2.67-20160121175247.zip. Is that by design?
[SuperSU] Tzfardaya:
Yes, wip says 2.67 is *beta*, this is the *stable* thread...
[SuperSU] argeljoseph:
Why does the "Stable" version link download redirects to the BETA link? Anyone having the same problem?
[SuperSU] j1gga84:
Every SuperSU after 2.52 beta was not flashable on my i9100 with CM12.1

I think it has something to do with that "systemless stuff"

Will the next final from play store work?

Regards

Sent from my SM-G900F using german Tapatalk 4
[SuperSU] UberJaeger:
Yes, where is the correct link to stable SuperSU 2.65 or is it just available through play store?
[SuperSU] BeetoCarvalho:
Link Download v2.65 Estable ?
[SuperSU] Badger50:
Here ya go :)

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

---------- Post added at 04:58 AM ---------- Previous post was at 04:53 AM ----------

Sorry, my bad. How bout now :)

http://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip
[SuperSU] BeetoCarvalho:
This is the stable version?

Link beta version.
[SuperSU] Manuel15:
The file is called "beta" because the file wasn't renamed, but it's the v2.65, so it's the stable version.
[SuperSU] egingell:
There's only one v2.65. Whether it says "beta", "stable", or "potato", it's still the same version.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] ashyx:
It would be an idea if there was an option before install to select system or systemless, if the rom supports it, as the zip supports both.

It's fairly easy for cf to implement I would think.
[SuperSU] skulldreamz:
No there is a v2.65 that's a beta from December and there's a v2.65 that's dated 2-2-16 that's stable and its in a staged rollout on google play. Why would [MENTION=631273]Chainfire[/MENTION] make a staged rollout of stable v2.65 if he could just put out the beta work he has already done 2 months ago? And that's why no one has the stable v2.65 yet or very few people...
[SuperSU] eemjee:
Stable: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
[SuperSU] j1gga84:
+1 :good:

But with that solution you have the problem, that you could not install the apk via play store because how would you be able to choose the system status in this case? ;)

regards
[SuperSU] egingell:
Where are you getting that date from? The Play Store... which automatically assigns a release date based on when it was uploaded? If anything was changed, it was the arbitrary verbiage ("beta" ==> "stable"). No dev in his right mind is going to change something in an old version because that change would also need to trickle down to every version that followed and that is a logistical nightmare.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] Chainfire:
No, it isn't. And you can already force the issue if you really want to, as documented in the WIP thread. You really shouldn't want to, though.

Play just updates whatever you have.

Both v2.65's are built from the same GIT tag. If you run them through a decompiler the class files will be identical.

The reason v2.67 isn't rolling out is because there are still a couple of known bootloops introduced in v2.66 that haven't been solved yet.
[SuperSU] kh34d:
Guys, what is the version work correctly with Marshmallow?
[SuperSU] Badger50:
Depends on if you want system root...2.52, or systemless root...2.67. Both of them work fine on MM.
[SuperSU] majkel_94:
The v2.65 doesn't work well - I wasn't able to restore apps with Titanium Backup. I have to use v2.49b, now it works ok ;)

My device is LeTV X600, Android 5.0.2.
[SuperSU] kh34d:
I think System root, plz

BTW. What is the difference?

Thanx for help
[SuperSU] IronTechmonkey:
Actually, if you dig into the manifests in the apk that is within the zip you will see it says 2.67.

[EDIT] I was speaking about the beta version of 2.67 which was linked as stable 2.65 yesterday but the link has since been fixed and a few more have been added.
[SuperSU] kh34d:
Now I downloaded v 2.65 is it work with Marshmallow?
[SuperSU] ashyx:
No it isn't an idea or no its not easy enough to do?

I'm assuming you mean the former? As you've already said it's simple enough to force it with a tweak of the update script.

Rolling on from your last statement can I respectfully ask why you haven't released systemless root to include android < 5.1.1 roms?
[SuperSU] skulldreamz:
[MENTION=631273]Chainfire[/MENTION] thanks for clarifying that. It just seems so much easier for yourself and all the users of supersu to say that the beta v2.65 is identical to the stable. To me beta and stable mean different things especially when you attach a different date to the file. I'm sure I'm not the only one thinking that something had been changed, but anyway appreciate as always everything you do.
[SuperSU] Nimueh:
Would someone here have a link to the last version of SuperSu before it went systemless?

I can't seem to find it on the website :(
[SuperSU] kh34d:
Unfortunately Stable 2.65 or beta 2.67 can't work on Marshmallow [emoji27]
[SuperSU] NYLimited:
Consider that the developer has very little to go on based on the above. I'd venture a guess that logs, which you did not furnish, would have helped a lot. Just sayin'...
[SuperSU] drezz2:
in android 4.4 or android 5... Is it worth upgrading to 2.65 or better leave it at 2.46?

dont know if any of the improvements applied to those versions
[SuperSU] ashyx:
V2.56

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[SuperSU] L.F.B.:
Ok so last stable was 2.46 and now all this systemless thing...

What will change from now?
[SuperSU] HaTrED_:
That's kinda weird cause I'm using lastest beta 2.67 under... Marshmallow! And without a single issue so far.
[SuperSU] Manuel15:
In using systemless root on marshmallow too, and without issues
[SuperSU] Hazlesnow67:
like your apps

I use a lot of your root apps. my 13 year old son downloaded cwm kitkat compadoble 190011 to my sgh-s959g all my play story and Google framework won't reinstall to the phone i tried factory reset did not work i get the error message evrytime i turn on my phone Google services have stopped is there any way you could point me to soon who could help me please. billy story to bother you with this!
[SuperSU] Nimueh:
Hmmm, 8 AM might be too early to find something, but all I see there are systemless versions :confused:
[SuperSU] fredmorist:
Pls. share link v2.49.

Gửi từ SM-N9208 của tôi
[SuperSU] Meminette:
[MENTION=631273]Chainfire[/MENTION] do you know why i cant flash 2v.65 stable release in lastest TWRP im getting failure aborting and i am currently using v2.46 pro

SM-G928W8
[SuperSU] mrrocketdog:
a log might help. after "failure aborting" there should be a box to 'tick' called "copy log". i believe it goes to your internal storage which then you can post and maybe get more help., i.e., the more info he has , the easier the diagnosis.

your question as it stands gives no specifics. just saying.

:)
[SuperSU] Meminette:
ok ill try to find logs so far i only got a screenshot of the failure http://imgur.com/lvjJpyC
[SuperSU] dfogelstrom:
Looked for answers and couldn't find any, please help.

Running latest nightly AICP 11.0 (MM) for the VS985. I have Su 2.51 installed but I would like to install the stable and systemless Su 2.65.

What are my steps? Just wipe system? Or flash right on top?

Thank you so much!!!
[SuperSU] veldom:
Installing SuperSU 2.65 overwrite custom UberKernel (partially solved)

Hallo (and sorry if this was already answered, but I didn't find any related post)

On Nexus 5 with Marshmallow 6.0.1 (coming from 5.1.1), I installed succefully superSu 2.65 and everythin was perfectly running. So I decided to install my preferred custom kernel (Uber)

My problem:

If I install the UBER-M custom kernel after installing superSu ---> I lose superSu and root.

If I install superSu after installing the UBER-M custom kernel ---> I lose the custom kernel (superSu overwrite boot with stock backup image).

Temporary Solution

Installing superSu 2.52 works fine.

So, is it a superSu problem or a kernel related problem?

Thank you for your answers!
[SuperSU] ashyx:
Post #2 BETA-SuperSU-v2.56-20151030013730

It's only systemless if you make it systemless.

---------- Post added at 08:11 PM ---------- Previous post was at 08:06 PM ----------

If your boot.img isn't using gzip compression it wont work.

---------- Post added at 08:18 PM ---------- Previous post was at 08:11 PM ----------

Just do it twice. First time it detects the boot.img is already patched so it restores the original.
[SuperSU] Nimueh:
So ... if I flash it like any other SuperSU "Update" it'll be the "normal" version? :confused:

This is confusing - thanks though :)
[SuperSU] L.F.B.:
Does anyone got the update from playstore?

Any problems updating from play?
[SuperSU] dongerado:
Latest "stable" breaks titanium backup for me. Insufficient space for backup...

Going back to 2.46 and everything works fine again...
[SuperSU] spainter:
Have not had any issues with TiB on my LG, Moto X, or even the Verizon Crappa Tablet (Ellipsis 7)
[SuperSU] damienzaffke:
Got my T-Mobile v10 on CM12.1 with xposed running with supersu version 2.67 runs amazing titanium backup us working fine all my apps are smooth no problems for me
[SuperSU] Dr2003:
I installed Supersu and then bought the plus. If u want to develop apps like this you should know your audience and the apps limitations. I rooted, installed supersu, then thought hey I'll buy the plus app and it has ben a total disaster. Android 5.1.1 Samsung tablet 12.2 inch. I get the same error over and over again, I am sure there are plenty others to. It's like u write the app put it out their and then shut on the guy trying to get it to work. I can have only one binary, so if it don't work, I have to re-root and reinstall another root manager. My suggestion for future is 1. List at least an idea of what brand of devices will not work, or have an app to test to see if it will work on a particular device... secondly, get some more clear and concise doco... your doco stinks!
[SuperSU] zelendel:
And you basic troubleshooting stinks. Not a single log at all and yet you are complaining. It is well known that Samsung devices are anti development. So root and everything else seems to have issues. This is well known and had you even bothered to look it up you would have seen this.

Remember where you are. This is not a site just to make your phone cool. If you don't understand what you are doing then don't mess with your device. Root is not for everyone. Nor should most people even bother with it due to not having the common sense to know how to use it or what to do with it.
[SuperSU] ritzusan:
Sorry for my auto quote (I'm a noob) but reading more I understood a thing: My SuperSU version is 2.65 and it's system-less so it cannot be turned on a system app. I tried with Titanium Backup but I failed hard as TB looses the root privileges during the process (what a noob LOL)

It was installed during the phone rooting with the ROM CF-Auto-Root-j5nlte-j5nltexx-smj500fn.tar.md5.

I tried to uninstall it and reinstall the previous version found in Playstore. Once installe it ask to me for an update (and without is not working) but that update fails every time and it's impossible to use it.

Now, I locked the android installer so the phone users can't uninstall SuperSU from the settings panel. But, of course I can't lock playstore aswell as the phone users will need to install apps and updates from the Playstore.

Maybe in android 5.1.1 I can only install a system-less SuperSU?

Any suggestion to prevent an accidental uninstall?

Thank you!
[SuperSU] zelendel:
Kinda pointless as they can just use a root browser and remove all the SU files.
[SuperSU] rogers11:
Disable "mount namespace separation" option in SuperSU.

It might be called slightly different but this is the reason for the error.
[SuperSU] Dr2003:
Lol, how wrong u are my trouble shooting is gr8, that is how I found out the hard way that you sell an app in the app store that 1/2 works for some people and doesn't work for a whole lot of other people. Posting the logs is pointless, what ur gonna code some fix uo? Lol right. The bottom line is I purchased an app that doesn't work, period. The app has so many problems with it, it's not even funny, the initial install didn't even pick up apps to block root access with. If your going to write an app, you need to know it's limitations. It should not be in the app store, I bet 50% of the people that downloaded don't even use it or never have. I built an app to verify if one click root will work, similar to kingoroot. It was simple to do..... u need to get out more and maybe pick up a manual.... but thanks for the advice....
[SuperSU] ritzusan:
I'll try to lock SuperSU access with Lockdown Pro... However to do it with a root browser they need to install it first and I just want to prevent an accidental SuperSU uninstall