Related
I keep reading in the posts that one should not update busybox once Xrecovery is installed. But what about the other forms of recovery programs? Could updating wreak havoc with others?
Could someone shed some light on why updating busybox would disturb the working order like that?
Thanks in advance
xRecovery depending on certain version of busybox. Newer versions may not work as old ones and xRecovery will not work.
Ok so far so good but please tell me if it's forbidden to update busybox for something like clockworkmod recovery? Would it cause harm to it as well?
I'm interested in this too. How can we update busybox? Busybox installer isn't working.
vientito said:
I keep reading in the posts that one should not update busybox once Xrecovery is installed. But what about the other forms of recovery programs? Could updating wreak havoc with others?
Could someone shed some light on why updating busybox would disturb the working order like that?
Thanks in advance
Click to expand...
Click to collapse
i prefer not to update if i was you. cwm and xrecovery are the only known compatible recxovery's available for our x8 keep the old version
Just don't update it! Last time I updated busybox, I couldn't acces xRecovery. What's the point of risking it for CWM?
Just don't!
If you really want to update busybox.. use x8 toolbox. Playing around with it a while back I tried installing and uninstalling 3 different versions of busybox that you can install from x8 toolbox. No detrimental effect on either xrecovery or cwm.
http://forum.xda-developers.com/showthread.php?t=1117100
i flashed the latest cf root 5.6 kernel with cwm and mo..the phone.rebooted afterward...bur the kernel doeant look like its been changed.from stock? can someone confirm it for me from yhe attachment? thanks
Check if you have SuperSU and/or CWM app installed. If so - then it's working. Kernel version signature might be the same as rooting replaces your kernel with the same version - but rooted.
yes, I have both of them installed thank you for your help
Hi everybody I just installed existenz rom v7, I want to ask can I update the integrated busybox? I'm worry if it will cause bootloop because I have installed the busybox on another stock based rom but I caused serious bootloop(can't boot into recovery). Does anyone updated it? Thanks![/ATTACH]
You need this specific busybox binary for the dual recovery. So don't update it.
You could use other builds of busybox with lzma compression enabled, any specific reason you want to update?
it's because I wanted to install viper4 android very much... Is it possible to install the single recovery to update the busy box?
Danny-Leung said:
it's because I wanted to install viper4 android very much... Is it possible to install the single recovery to update the busy box?
Click to expand...
Click to collapse
You loose LPA (low power audio) with viper4android. Are you sure it's a) worth it and b) it won't work with the already installed busybox version?
I don't know if the rom uses lmza somewhere else, but for me it sounds unlikely. It would probably be worth a try to uninstall the dual recovery (delete /system/bin/chargemon and rename /system/bin/chargemon.stock to chargemon if there is no uninstaller) and try updating busybox. Backup before, no guarantees and do it on your own risk though. If you want to install a single recovery you have to be on unlocked bootloader afaik.
Another solution would be to compile (or nicely ask the creator of dual recovery) the latest busybox with lmza support by yourself.
If you do that you will lose dual recovery and get a RED led with working phone:silly: that what i got after i did what you mean
Problem same with me..
I want to install Viper4Android..when I installed busybox stericson i got bootloop..
Sorry for my bad English
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" ?
Thread specifically about finding and solving the issue that some are seeing where the apps and logs screen of SuperSU will load indefinitely, while su access does keep working.
r25txe said:
Hi @Chainfire
I just tried the 2.04BETA to see if my issue was resolved, to no avail.
I was wondering have you had any reports of certain settings not being configurable and the "apps" and "logs" tabs endlessly refreshing, i.e., you cannot see what apps you have approved or denied.
My root does work, I can approve or deny requests normally, it's just I cannot go back if I want to reconfigure an app's root access or review logs. Unchecking the refresh app and logs automatically has no effect.
In the settings, uninstall SuperSU will not work, causes an eventual crash of SuperSU (after quite some time) unless you do a reboot. SuperSU will still be there, too.
I'm a Pro user and unable to set a PIN either as SuperSU will just circle endlessly after trying to set one.
I've been reading about other users' issues mostly related to root access itself, but my issues seem to be interface only.
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
Oh, my ..!
It's working now, I just did another reboot (because SuperSU had become stuck again) and on reboot all was working! :good:
:blush:
I'll redownload the licence and test Pro features tomorrow and report back.
Click to expand...
Click to collapse
r25txe said:
All the issues I described are back now.
With or without licence.
Will continue trying/testing see if I can get a pattern.
This is persisting across four phones, one on Gingerbread.
Click to expand...
Click to collapse
mathuaerknedam said:
I'm also seeing this, in 1.94 and 2.02, but I've not yet tried the 2.04 beta. Sometimes it works. I've tried all sorts of different things to identify a pattern, but I've had no luck.
I've also one instance, just last night, of SuperSU requesting root privileges for itself. I can post a screenshot and some log data if that would help.
Sent from my Nexus S 4G using XDA Free mobile app.
Click to expand...
Click to collapse
xlollomanx said:
Same issue I have, is presented from any version after 1.94. However it does not happen always: sometimes shows granted superuser app sometimes not, happens random.
Click to expand...
Click to collapse
It'd be great if we can get a recap of which SuperSU versions, which devices and kernels and firmwares, are affected. Any information you have is welcome. Let's get this issue sorted out.
@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?
xlollomanx said:
@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?
Click to expand...
Click to collapse
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?
I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?
Chainfire said:
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?
Click to expand...
Click to collapse
Now I'm using CWM recovery based (6.0.5.0)
I tested the v1.94 and update v2.0 on a " old rom". Few days later, thinking was my device problem's I performed a full wipe with pristine and installed v2.0 directly from play store, so I could try a cleanly installation of SuperSU (but the problem persist). Here I tried all new versions (I also tried the v1.94, which worked fine, but mainly to uninstall the newer version's as I will explain below) but without success.
I tried in different ways:
I downgraded to v1.94(replacing supersu with root explorer), uninstalled SuperSU, reistalled v1.94(via in-app) and then updated to 2.0 and then v2.01 when update came out from play store.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.0 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.02 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I tried v2.04 and v2.05 with zip-update from recovery by flashing directly over v2.02(this v2.02 is a result from previous test).
I uninstalled SuperSU by replacing supersu with root explorer, installed via in-app v1.94(that work perfectly) and then installed 2.04.
I hope I have answered in the right way in all your questions.
Regards
I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Thank you.
Been playing around, haven't replicated so far. A common theme seems to be CM and CWM, though it works fine in my own testing still... sigh.
mathuaerknedam said:
I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?
Click to expand...
Click to collapse
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.
Chainfire said:
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.
Click to expand...
Click to collapse
I just clicked the big install button for a regular install.
Sent from my Nexus S 4G using XDA Free mobile app
Chainfire said:
Which installation method do you use for busybox?
Click to expand...
Click to collapse
That seems like a probable culprit. Maybe if someone installed your version of 'busybox' we might see a difference.
Frank
Installed BusyBox as well ... still working for me ...
Can you guys having this issue post your /data/data/eu.chainfire.supersu/files/supersu.cfg file ?
Very important 3d
Inviato dal mio SM-G900F X-Note 5.0 con Tapatalk
Nothing here
FeraVolt said:
I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Click to expand...
Click to collapse
These issues are not related, as the problem we're discussing only applies to Android with SELinux, which Gingerbread doesn't have.
Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx
Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
Click to expand...
Click to collapse
It works!!!
The problem was never entirely consistent, so I'll keep checking and report back. But so far, so good!
Sent from my Nexus S 4G using XDA Free mobile app
Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx
Click to expand...
Click to collapse
Hi @Chainfire
I just flashed 2.0.5 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?
r25txe said:
Hi @Chainfire
I just flashed 2.05 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?
Click to expand...
Click to collapse
Flash 2.06 ?
Did you mistype, or ? If you are actually on 2.06 then I'll have to think some more what the issue could be and how to trace it...
Oh, dear.
I am clearly much too tired to be on XDA! I only noticed that you posted 2.0.6. I will try it after work tomorrow, really need to crash now.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
Oh, I see you´re online, I will flash it right now ...
---------- Post added at 01:02 AM ---------- Previous post was at 12:56 AM ----------
2.06 works!!
(Although, 2.0.4 did this to me, too)
We´ll see how we get on tomorrow
Thank you, @Chainfire
---------- Post added at 01:08 AM ---------- Previous post was at 01:02 AM ----------
Not sure its of use, but here is the cfg file after the flash of 2.06.
https://www.dropbox.com/s/2s3kircndbfjqmm/supersu.cfg?dl=0