Problems Installing BusyBox - Android Q&A, Help & Troubleshooting

Hello,
I am trying to use an app (MyBackup Pro) which indicates that 'busybox' is not installed or out of date. When I go to install from the Play Store, it attempts to install Busybox 1.26.2 into /system/xbin.
However, when I select 'Install', it indicates the installation of Busybox was not successful. Then it indicates to try installing to a different location to resolve the issue.
Does anyone know what is causing this error?
FYI - My phone (Nexus 6) is currently rooted using Magisk.
Thanks in advance!

Hi, I figured out how to resolve - in the Magisk Manager, there is an option to 'bind mount busybox to xbin' that when selected, fixes the problem.

Related

[Q] Busybox install location

Hi
I used busybox installer from the market, the default was to install it in system/xbin I subsequently installed again, this time in system/bin (don't ask) Will having multiple instances of busybox be harmful in any way? I ask this, as I lost root when I did the second install, and couldn't root the phone again after this via superoneclick. Since then however, I have managed to root the phone through other means. But as this did happen, I wondered if I might run into future problems? Everything seems stable at the moment though.
Thanks.

Busybox update problem (phone freezes)

Current version installed : v1.20.2-cm9
Busybox is installed to /system/bin/
Tried both (even Smart and Normal Install) (xbin and bin) but my phone just freezes when I do that with Busybox Pro.
Meaning I have to force a reset with the power-button.Did uninstall the application twice also, tried even the free-version.
With Busybox Installer the application I was able to install v1.20.2-cm9 without a problem. Verified the installation with (terminal emulator) v.20/2-cm9 bionic. Yes this application is not been updated for four months, meaning that it doesn't have the newest Busybox version.
Is there a other way to get Busybox 1.22.0 installed?
this is so damn interesting. With Busybox Pro it keeps freezing the installation. I downloaded Busybox X. Click on install button and 1.21.1 is installed. Then I was hoping that I would be able to update it to 1.22.0 in Busybox Pro itself, boom it freezes again . Well I am happy with 1.21.1 atleast.
Did inform the creaters of Busybox. Hopefully they fix the file-priveleges problem.

[Q] Problems with superuser su

I just flashed CM11 onto my Amaze (T-Mobile S-ON) and everything runs fine except when I tried to use titanium to restore my apps, it gave me this message: "Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I opened Superuser and scrolled to info. It says "superuser v3.1.3 (46)" and "su binary v3.1.1 (17). When I press on the su, it goes to a binary updater which says "downloading manifest," then, after a minute or so, it says "fail" in red at the end of the "downloading manifest" line. I downloaded superuser by CWM after this problem and when I opened the app, it said: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." It gives me the option to press cancel or Recovery Install. When I press recover install, it says: "There was an error installing Superuser. Please send a log of the error to the developer." I went onto the superuser website, downloaded the latest arm su and superuser, put them on my sd card, went into 4ext and installed both from sd card and still have the same problem.
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Root?
luisandroid said:
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Click to expand...
Click to collapse
I think you are not rooted.
Try app "Simple Root Checker" from Play Store:
https://play.google.com/store/apps/details?id=com.simonedev.simplerootchecker
If not rooted, try this to gain root:
http://forum.xda-developers.com/showthread.php?t=2437057
pbergonzi said:
I think you are not rooted.
Try app "Simple Root Checker" from Play Store:
https://play.google.com/store/apps/details?id=com.simonedev.simplerootchecker
If not rooted, try this to gain root:
http://forum.xda-developers.com/showthread.php?t=2437057
Click to expand...
Click to collapse
I used that app and it said: "Android 4.4.2 HTC Amaze 4G Application Superuser found Terminal Rooted Busybox installed BusyBox v1.21.1" So I am guessing I am rooted. Should I try using that tool to flash SuperSU anyway? Thanks for helping me out with this.
SuperUserSU problems.
luisandroid said:
I used that app and it said: "Android 4.4.2 HTC Amaze 4G Application Superuser found Terminal Rooted Busybox installed BusyBox v1.21.1" So I am guessing I am rooted. Should I try using that tool to flash SuperSU anyway? Thanks for helping me out with this.
Click to expand...
Click to collapse
Nice--my mistake. In your Superuser info, where you found your su binary listed "su binary v3.1.1 (17)", did it give the file specs right underneath--it does in mine.
Also, if you go into Superuser app, then Preferences->Security->Automatic Response, is that accidentally set to "Deny?" Betcha' that won't work.
Is Titanium Backup listed in your Superuser apps list, and if you open the info there, is it "Allowed?"
Probably what you said about re-flash Superuser is reasonable, and worth a shot if the Automatic Response is already set to Allow or Prompt.
I'll also wager that someone else with good insight and experience will stop in the thread with a working answer for you.
luisandroid said:
I just flashed CM11 onto my Amaze (T-Mobile S-ON) and everything runs fine except when I tried to use titanium to restore my apps, it gave me this message: "Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I opened Superuser and scrolled to info. It says "superuser v3.1.3 (46)" and "su binary v3.1.1 (17). When I press on the su, it goes to a binary updater which says "downloading manifest," then, after a minute or so, it says "fail" in red at the end of the "downloading manifest" line. I downloaded superuser by CWM after this problem and when I opened the app, it said: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." It gives me the option to press cancel or Recovery Install. When I press recover install, it says: "There was an error installing Superuser. Please send a log of the error to the developer." I went onto the superuser website, downloaded the latest arm su and superuser, put them on my sd card, went into 4ext and installed both from sd card and still have the same problem.
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Click to expand...
Click to collapse
The problem you describe is common with more recent versions of CM (at least I've experienced it). It's due to the way CM is now implementing their included Superuser app, which is different from how it used to behave and how many other apps expect it to behave. The solution is to flash SuperSU in recovery from this thread http://forum.xda-developers.com/showthread.php?t=1538053 (if it resolves your issues please remember to thank its creator and consider purchasing the full version).
When you set it up, enable "pro" mode, survival mode, allow it to install the scripts, and respect CM root settings. If installed correctly you should be good to go.
I hope this helps
Odysseus1962 said:
The problem you describe is common with more recent versions of CM (at least I've experienced it). It's due to the way CM is now implementing their included Superuser app, which is different from how it used to behave and how many other apps expect it to behave. The solution is to flash SuperSU in recovery from this thread http://forum.xda-developers.com/showthread.php?t=1538053 (if it resolves your issues please remember to thank its creator and consider purchasing the full version).
When you set it up, enable "pro" mode, survival mode, allow it to install the scripts, and respect CM root settings. If installed correctly you should be good to go.
I hope this helps
Click to expand...
Click to collapse
That solved the problem! Got CM 11 running on my Amaze! I made sure to thank the dev! Thank you for your help as well!

Buybox uninstallation Help

Ok so i had rooted my phone using magisk and i got to know some apps need busybox to work properly and i installed it too BUT dumbass me installed it in /system/bin. The installation was succesful and i wanted to uninstall it (to be systemless again) and when i pressed uninstall it showed looks like uninstalling busybox was unsuccessful and the uninstall button got greyed out. Ig since then i am not passing safetynet too so please help me out. I used stericson's busybox app btw. And now apps cant even see that busybox is installed or not all apps say busybox isnt installed.

Installing android app (help)

Hi everyone,
I have bloatware app installed on my android head unit. I want upgrade it to newer version but it fails.
I tried to uninstall it by using different methods. All fails. Then I used universal android debloater it finally uninstalled. But seems not uninstalled completely. When I tried to install the same app manually fails. I tried (adb install file.apk) command and got:
Package signatures do not match the previously installed version.
When I go to apps> system apps, I can see the app there but it’s greyed out and got (not installed on this user)
I tried : adb uninstall [PACKAGE_NAME]
Also failed. Error ( deleted failed internal error)
Please help me to solve my problem. I really need to install the new version of the app.
Run SD Maid Pro - requires Android is rooted.
The app comes with several modules, including a so-called "corpse finder" that detects unused and temporary files and deletes them.
Ameer700 said:
Hi everyone,
I have bloatware app installed on my android head unit. I want upgrade it to newer version but it fails.
I tried to uninstall it by using different methods. All fails. Then I used universal android debloater it finally uninstalled. But seems not uninstalled completely. When I tried to install the same app manually fails. I tried (adb install file.apk) command and got:
Package signatures do not match the previously installed version.
When I go to apps> system apps, I can see the app there but it’s greyed out and got (not installed on this user)
I tried : adb uninstall [PACKAGE_NAME]
Also failed. Error ( deleted failed internal error)
Please help me to solve my problem. I really need to install the new version of the app.
Click to expand...
Click to collapse
Revive the app first
adb shell cmd package install-existing <package_name>
As for how to update idk... install lsposed and try signature check disable module
jwoegerbauer said:
Run SD Maid Pro - requires Android is rooted.
The app comes with several modules, including a so-called "corpse finder" that detects unused and temporary files and deletes them.
Click to expand...
Click to collapse
I tried to root my head unit but failed
Rstment ^m^ said:
Revive the app first
adb shell cmd package install-existing <package_name>
As for how to update idk... install lsposed and try signature check disable module
Click to expand...
Click to collapse
How to disable signature check?
I tried many ways but all failed, I hope if I can change the package name so I can install the app without any issues.

Categories

Resources