Hey guys, every time I restart my phone, and it goes through the process of checking storage and everything, I get a little hash symbol icon in the top bar that says 'su binary outdated' when I click on it, it doesn't look all that safe but it pops up every time, im worried if I go through with it it may be a virus... I rooted my phone with z4 root and installed lag fix v2. Anyone got any advice or guarantee that it is safe? It wants to down load a file when I press update but I *****ed it ang closed it...
Sent from my GT-I9000 using Tapatalk
Its the super user binary should be safe as almost everyone is using the super user app. It enables root permissions to the apps you want. Should update to v3.0 i think, ive done it no problems so far...
stuey.89 said:
I get a little hash symbol icon in the top bar that says 'su binary outdated'
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I just upgraded my FW via Kies the other day from 2.2 to 2.3.3 KG3 and lost my root in the process. Have not rooted it again yet as been trying to sort out the best way to root with KG3 - seems some people having problems with speedmod (my root kernel previously) and KG3.
I still have the superuser icon and i'm getting the same message as you to update it - I have hit go ahead but it won't because I don't have root access but if you are rooted it should be safe to update it.
As soon as i root my phone again I certainly will....
EDIT: flashed .tar file found here:
http://forum.xda-developers.com/showthread.php?t=1211939&highlight=haloimplant&page=19
and rooted again no problemo. still on same kies-upgraded KG3 stock firmware. Superuser updated with busybox and TiB updated. now to find a decent kernel/rom....
Hey guys, can u help me, i cant update SU binary, i dont know why? I had some custom ROM and i went back to the stock, but today i wanted to root my phone again, and when SU shown, i go there to update it and binary, but binary wont update... Can anyone tell me whats the problem?
Sorry for my english...
vujkeraf said:
Hey guys, can u help me, i cant update SU binary, i dont know why? I had some custom ROM and i went back to the stock, but today i wanted to root my phone again, and when SU shown, i go there to update it and binary, but binary wont update... Can anyone tell me whats the problem?
Sorry for my english...
Click to expand...
Click to collapse
You have to connected to internet
SnowPluralism said:
You have to connected to internet
Click to expand...
Click to collapse
I am always connected to the internet, but it fails to update... Dont know why
Reroot the phone is your only option
Sent via that ninja standing right behind you
vujkeraf said:
I am always connected to the internet, but it fails to update... Dont know why
Click to expand...
Click to collapse
Go to market ... Update superuser app and try again
Sent from my GT-S5830 using xda premium
http://forum.xda-developers.com/showthread.php?t=1837056
Here u will find latest SU app.
Flash from Recovery
vujkeraf said:
Hey guys, can u help me, i cant update SU binary, i dont know why? I had some custom ROM and i went back to the stock, but today i wanted to root my phone again, and when SU shown, i go there to update it and binary, but binary wont update... Can anyone tell me whats the problem?
Sorry for my english...
Click to expand...
Click to collapse
I had this issue too, but i coudnt fix it, updating the SU app wont change your phones binaries, i updated but in the end it couldn ask for root permisions and update failed, so i decided to go to options and hide the outdated binaries notification and troubles solved, i know its not the best way but at least it wont bother me anymore lol
try superSU, i tried on my friend tablet when superuser didn't want to update then it automatically solve the problem.
idk if it will works on yours but it never hurts to try...
look if superuser is listed on the list with apps that get root (in superuser-app)
if yes => delete it, close it, reopen it and try again to update
if not => reboot, DONT DO ANYTHING BESIDES THE FASTEST WAY into superuser app and then try updating
if 2 is not working, retry it about 5 times. worked for me once. (not exactly at 5 times, but i ha to repeat this and on one try it suddenly worked. strange but....well...did the job)
Thx guys, it helped. I just rooted my phone again and the problem is solved.
I have sought on way to update my SU app,
but i flash many root's app and the old version persists
any idea ?
Reynaldo Aguiar said:
I have sought on way to update my SU app,
but i flash many root's app and the old version persists
any idea ?
Click to expand...
Click to collapse
Could always use adb interface and push latest su binary to it. Then try to load supersu app.
bunny12 said:
thanks it did work for the time.... but why its still written update when su binary is already updated to its latest version can you tell please
Click to expand...
Click to collapse
Ignore it, even if you update it again it is just the same...
Sent from my GT-S5830 using Tapatalk 2
This thread is for SuperSU releases that are still in testing, and are not yet available through the Play store. The main thread for stable SuperSU releases is located here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703. The changelogs are in the old release thread.
Please keep track of the version numbers in the thread titles, as the latest test release may not always be newer than the latest stable release.
The latest test release is:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
RELEASE NOTES
That is a recovery flashable ZIP (I recommend FlashFire or TWRP). If you want to install via APK, it is also present inside the ZIP, in the common folder.
--- reserved ---
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
StupidIdea said:
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
Click to expand...
Click to collapse
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Chainfire said:
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Click to expand...
Click to collapse
No pressure. Its up to you if you decide to publish it before L release or not but I will be glad to test it on L and report if functions that I use in my apps work with it. As for xposed in theory these 5 points rovo89 posted should work with "permissive" but I guess he will verify it himself.
Of topic: I understand its beyond su binary but did you even thought about adding an option to start activity in system or root process? Benefits are simpler interaction with system services and improved service life (faster restarts). Let me know if question is not clear.
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
cioce said:
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
Click to expand...
Click to collapse
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Have you tried completely removing the com.sec.knox.seandroid package from your device?
MasterMind33 said:
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
Click to expand...
Click to collapse
The reason device default theme is not selected by default is because a lot of OEMs have some godawful themes set by default that everybody would nag me about ...
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
MikeRL100 said:
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
Click to expand...
Click to collapse
#realworldproblems
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Chainfire said:
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Click to expand...
Click to collapse
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Chainfire said:
Have you tried completely removing the com.sec.knox.seandroid package from your device?
Click to expand...
Click to collapse
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
cioce said:
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Click to expand...
Click to collapse
I'm not talking about not having root at all. The problem (as I understand it) is caused by having any packages at all in a "disabled" state. This may ultimately cause a crash which triggers a reboot.
At the same time, keeping that package enabled in combination with root, will break various root commands, which you may not even notice (root apps will just appear to randomly fail and be unreliable) which in turn is also known to cause reboots.
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
Click to expand...
Click to collapse
Just because you haven't noticed the issue doesn't mean it isn't there. As for using it, having root prevents KNOX from working anyway.
...
The point is, solving this problem is not as easy as making that popup optional.
dhampire said:
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Click to expand...
Click to collapse
Please clarify what happens in the following circumstances:
- in-app binary update: normal, and reboot
Keeps saying binary needs updating? Or also results in bootloop?
- in-app binary update: TWRP/CWM
Bootloop?
- latest flashable ZIP with TWRP/CWM
Also bootloop?
It's strange if they don't all result in bootloops...
I know testing is very annoying for you because you need to reflash your system every failed test, but if you want to help solve this problem it's going to require some work.
First test:
- If you have SuperSU 1.94 installed, use the "full unroot" option from settings to remove it.
- Reboot into CWM/TWRP
- Install the latest BETA ZIP but do not reboot
- Adb shell into the device
- "mount /system"
- "ls -l /system/xbin/*su*", post the output here
- "ls -lZ /system/xbin/*su*", post the output here
- Remove /system/app/Superuser.apk
- Reboot into Android
- See if there is a bootloop
Sorry for my poor english. not bootloop. never bootloop. but su binary update loop -> need su binary update again on every boot after update su binary....continue...keep saying need update.
---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
If 1.9.4, there are no problem like that. but only twrp use su binaly update. normal update makes unroot.
dhampire said:
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
Click to expand...
Click to collapse
Not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
dhampire said:
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
Click to expand...
Click to collapse
Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
...
Please:
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Frank
Frank Westlake said:
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Click to expand...
Click to collapse
No it was not a busybox issue, it was an odd bug somewhere in the binary
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
dhampire said:
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
Click to expand...
Click to collapse
Please confirm the app actually says 2.06
This logcat does not list the output I expect. Did you open SuperSU again after rebooting?
How did you make the logcat? "adb logcat > logcat.txt" ?
good day sir, i just rooted my fone today and updated my supersu but the update is failed. i tried searching from other forums and search the net, did all that but still not updating. i just only tried normral update because i dont have CWM/TWRP on my device and it's hard to flash it because our device is currently not supported by it.
- Exact device model
Cherry Mobile Omega Infinity (x100) Philippines
- Exact firmware version
Modem_Cherry_Omega_Infinity_V14.0
- Exact Android version
4.2.2
- Exact SuperSU version
SuperSU Free v2.40
- Interfering apps
i have installed busybox but unistalled it
- Update methods tried
i tried normal only
- What kind of root are you left with
- Nothing seems to have changed at all, even the GUI still shows the old version number
- Logs from SuperSU (very important)
idk how to use logcat but my logs ate just xmods
aspintr said:
good day sir, i just rooted my fone today and updated my supersu but the update is failed. i tried searching from other forums and search the net, did all that but still not updating. i just only tried normral update because i dont have CWM/TWRP on my device and it's hard to flash it because our device is currently not supported by it.
- Exact device model
Cherry Mobile Omega Infinity (x100) Philippines
- Exact firmware version
Modem_Cherry_Omega_Infinity_V14.0
- Exact Android version
4.2.2
- Exact SuperSU version
SuperSU Free v2.40
- Interfering apps
i have installed busybox but unistalled it
- Update methods tried
i tried normal only
- What kind of root are you left with
- Nothing seems to have changed at all, even the GUI still shows the old version number
- Logs from SuperSU (very important)
idk how to use logcat but my logs ate just xmods
Click to expand...
Click to collapse
hi
i have on my htc one m8 android version 5.0.1 , s-on, I tried to s-off but to no avail ,I followed the tutorial and I stuck with binary failed with supersu (trying to get it off with Sunshine)
eventually left me to install a custom rom (android 4.4.4 ,Android_Revolution_HD-One_M8_22.2 ) after I install custom rom, I tried again with supersu and sunshine and we succeeded now i have S-OFF, I didn't received the error.
Now I'm back to stock Android 4.4.4 from 5.0.1
aspintr said:
good day sir, i just rooted my fone today and updated my supersu but the update is failed. i tried searching from other forums and search the net, did all that but still not updating. i just only tried normral update because i dont have CWM/TWRP on my device and it's hard to flash it because our device is currently not supported by it.
Click to expand...
Click to collapse
If you have a terminal on your device and know how to run a script then try this:
http://forum.xda-developers.com/showthread.php?p=59353023
aspintr said:
i have installed busybox but unistalled it
Click to expand...
Click to collapse
If the script fails you might need to reinstall busybox, or maybe it just won't work on your device.
Frank