[TOOL][BIN]BusyBox Recovery Flashable Zips **ALL-ARCHS**
- Thread starter YashdSaraf
- Start date
@YashdSaraf
Tested (ARM64). Not working.
Same error. Please check screenshot.
Log file content
#Mon Jan 11 17:15:10 CST 2010
#Ignore umount errors!
Wrong architecture -- Looking for arm64 -- Found
It seems that didn't find the operation to check value for architecture (found is empty)
I attached a zip file that contain /system/build.prop & /default.prop file of the device.
Tested (ARM64). Not working.
Same error. Please check screenshot.
Log file content
#Mon Jan 11 17:15:10 CST 2010
#Ignore umount errors!
Wrong architecture -- Looking for arm64 -- Found
It seems that didn't find the operation to check value for architecture (found is empty)
I attached a zip file that contain /system/build.prop & /default.prop file of the device.
Last edited:
Well at least the log file was created this time
. I used 'grep' command to obtain the device's architecture, which seems to be the culprit in your case. Anyways I've gotten rid of most of the primitive usage of grep in these installers.http://afh.co/c/arm-beta
http://afh.co/c/arm64-beta
Thanks for the support and patience.
I have only updated the installers, not the binaries. If the older busybox installers worked for you, there is no need to update. I'll update the OP if there are any changes to the binary.:good:
Last edited:
@YashdSaraf
Tested ARM64 busybox (v. 06.05.-23015) same error.
I found the problem and the possible solution.
Your recovery script check the value
ro.product.cpu.abi
ro.product.cpu.abi2
ro.product.cpu.abilist
with getprop. It read the value from deafult.prop of recovery image.
But this value if is not correct your batch stop the installation also the file in /system/build.prop are correct.
The value in /system/build.prop are always the correct value.
For test to check the right reading I added these lines to your script
FOUNDARCH1=$(getprop ro.product.cpu.abi)
FOUNDARCH2=$(getprop ro.product.cpu.abi2)
FOUNDARCH3=$(getprop ro.product.cpu.abilist)
ui_print "cpu.abi = $FOUNDARCH1"
ui_print "cpu.abi2 = $FOUNDARCH2"
ui_print "cpu.abilist = $FOUNDARCH3"
then i copied and install the new zip with new script and I checked that no arm64 was not found.
Then I unpacked the images of the recovery and I found the problem.
The recovery default.prop didn't contain the right strings fro cpu architecture.
I believe that the problem is that your script read cpu architecture value by recovery default.prop file instead by /system/default.prop file.
For test I modified the default.prop file of the recovery, repacked and reinstalled the recovery and flash your original zip and now it works.
Then please if you can modify your script to read always the CPU architecture value form /system/build.prop.
I tested theese changes in the script and it worked
--- Original part of the script
FOUNDARCH=$(getprop ro.product.cpu.abi)
: ${FOUNDARCH:=$(getprop ro.product.cpu.abi2 2>/dev/null)}
: ${FOUNDARCH:=$(getprop ro.product.cpu.abilist 2>/dev/null)}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi(2)?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=none}
--- My changes
${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi2?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abilist?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi(2)?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=none}
Tested ARM64 busybox (v. 06.05.-23015) same error.
I found the problem and the possible solution.
Your recovery script check the value
ro.product.cpu.abi
ro.product.cpu.abi2
ro.product.cpu.abilist
with getprop. It read the value from deafult.prop of recovery image.
But this value if is not correct your batch stop the installation also the file in /system/build.prop are correct.
The value in /system/build.prop are always the correct value.
For test to check the right reading I added these lines to your script
FOUNDARCH1=$(getprop ro.product.cpu.abi)
FOUNDARCH2=$(getprop ro.product.cpu.abi2)
FOUNDARCH3=$(getprop ro.product.cpu.abilist)
ui_print "cpu.abi = $FOUNDARCH1"
ui_print "cpu.abi2 = $FOUNDARCH2"
ui_print "cpu.abilist = $FOUNDARCH3"
then i copied and install the new zip with new script and I checked that no arm64 was not found.
Then I unpacked the images of the recovery and I found the problem.
The recovery default.prop didn't contain the right strings fro cpu architecture.
I believe that the problem is that your script read cpu architecture value by recovery default.prop file instead by /system/default.prop file.
For test I modified the default.prop file of the recovery, repacked and reinstalled the recovery and flash your original zip and now it works.
Then please if you can modify your script to read always the CPU architecture value form /system/build.prop.
I tested theese changes in the script and it worked
--- Original part of the script
FOUNDARCH=$(getprop ro.product.cpu.abi)
: ${FOUNDARCH:=$(getprop ro.product.cpu.abi2 2>/dev/null)}
: ${FOUNDARCH:=$(getprop ro.product.cpu.abilist 2>/dev/null)}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi(2)?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=none}
--- My changes
${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi2?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abilist?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=$(grep -Eo -m1 "ro.product.cpu.abi(2)?=.+" /system/build.prop /default.prop 2>/dev/null | grep -Eo "[^=]*$")}
: ${FOUNDARCH:=none}
Last edited:
That sounds like some really hard work.
Actually, in the original installers, I used the code to check both /system/build.prop and default.prop but I was stupid enough
to be mounting system after checking for architecture in /system/build.prop. My bad.Sorry you had to go through all the trouble just to make me realize my foolishness.
Here are the fixed zips,
http://afh.co/c/arm-beta
http://afh.co/c/arm64-beta
I also optimized cleaning time in them.:good:
Those are meant for bovirus as he has been facing issues with the installers attached in the OP.
You can try them out if you wish, but if you already have my busybox build installed, there is no need to try them out.
@YashdSaraf
I confirm that now the latest version that you posted works on Jiayu s3 LP.
Please refresh where you need your build (also all arch?).
I believe that could be suefull a reference based on Android version for SELinux version or standard version).
Busybox standard: up to Android 4.2
Busybox SELinux: Android 4.3 and up
I propose you a change of zip file names. File scheme
Busybox_version_architecture_Standard_YSD - For standard (not SELlinux) version
Busybox_version_architecture_SELinux_YSD - For SEinux version
ex.
Busybox_1.24.2_ARM_Standard_YSD.zip
Busybox_1.24.2_ARM_SELinux_YSD.zip
Busybox_1.24.2_ARM64_Standard_YSD.zip
Busybox_1.24.2_ARM64_SELinux_YSD.zip
Busybox_1.24.2_All_Architecture_YSD.zip
In this way you highlight the busybox version, platform and standard or SELinux version.
Does your btach in SELinux version check if Android support SELinux?
I confirm that now the latest version that you posted works on Jiayu s3 LP.
Please refresh where you need your build (also all arch?).
I believe that could be suefull a reference based on Android version for SELinux version or standard version).
Busybox standard: up to Android 4.2
Busybox SELinux: Android 4.3 and up
I propose you a change of zip file names. File scheme
Busybox_version_architecture_Standard_YSD - For standard (not SELlinux) version
Busybox_version_architecture_SELinux_YSD - For SEinux version
ex.
Busybox_1.24.2_ARM_Standard_YSD.zip
Busybox_1.24.2_ARM_SELinux_YSD.zip
Busybox_1.24.2_ARM64_Standard_YSD.zip
Busybox_1.24.2_ARM64_SELinux_YSD.zip
Busybox_1.24.2_All_Architecture_YSD.zip
In this way you highlight the busybox version, platform and standard or SELinux version.
Does your btach in SELinux version check if Android support SELinux?
That sounds like some really hard work.
Actually, in the original installers, I used the code to check both /system/build.prop and default.prop but I was stupid enough
Sorry you had to go through all the trouble just to make me realize my foolishness.
Here are the fixed zips,
http://afh.co/c/arm-beta
http://afh.co/c/arm64-beta
I also optimized cleaning time in them.:good:
Those are meant for bovirus as he has been facing issues with the installers attached in the OP.
You can try them out if you wish, but if you already have my busybox build installed, there is no need to try them out.
Error while unzipping BusyBox-arm-1.24.2-SELinux_Enabled-YDS.zip to /system/xbin . Reason: unzip : zip flags 1 and 8 NOT supported.
Busybox of TWRP recovery(version 2.8.6.1) is 1.21.0-jb bionic in /sbin/
Thanks a lot!
BTW When I searched for "BusyBox 1.24.2 recovery" through google, I didn't find this post.
It was random that I got here. Maybe change a little name of the topic or add some keywords?
BTW When I searched for "BusyBox 1.24.2 recovery" through google, I didn't find this post.
It was random that I got here. Maybe change a little name of the topic or add some keywords?
Last edited:
@YashdSaraf
followed the link in OP for toolchain link leads to your private file manager on AFH.
Here is public url
https://www.androidfilehost.com/?w=files&flid=50435
followed the link in OP for toolchain link leads to your private file manager on AFH.
Here is public url
https://www.androidfilehost.com/?w=files&flid=50435
Hey,
Thanks for letting me know.
I've updated the op, also the toolchains for mips64el and x86_64 archs have been uploaded.
@YashdSaraf
Need ssl_helper for wget to be able to use https
can you build
Busybox itself contains no SSL code. wget will spawn a helper program to talk over HTTPS. ssl_helper is a tool which can be built statically from busybox sources against a small embedded SSL library. Please see networking/ssl_helper/README.
Need ssl_helper for wget to be able to use https
can you build
Busybox itself contains no SSL code. wget will spawn a helper program to talk over HTTPS. ssl_helper is a tool which can be built statically from busybox sources against a small embedded SSL library. Please see networking/ssl_helper/README.
Hey,
I managed to build ssl_helper using wolfssl (ssl_helper.c wasn't updated for the latest matrixssl release).
Here's the link to the zip containing ssl_helper for all archs - https://dl.dropboxusercontent.com/s/jqjhze4li9z53xx/ssl_helper.zip
Just copy the one appropriate to your device to /system/xbin or /su/xbin whichever you prefer and give it executable permissions rwxr-xr-x(755) and your'e good to go.
I tested wget with https links and it worked for me.
Do report back if it works for you so I can update the op. :good:
I'm glad you got it to compile I've been trying all day and was unable to get it done
tested arm version it works great, thanks
@yashdsraf
Errro installing latets build (24.05.2016) of ALL Arch busybox
http://postimg.org/image/tgo571dmj/
Could you make an add in first post about the error log with the info
If you get an error check the file
/sdcard/BusyBox-YDS-Installer.log
It can useful to post it to report your problems.
Errro installing latets build (24.05.2016) of ALL Arch busybox
http://postimg.org/image/tgo571dmj/
Could you make an add in first post about the error log with the info
If you get an error check the file
/sdcard/BusyBox-YDS-Installer.log
It can useful to post it to report your problems.
Last edited:
I didn't get an error with TWRP 3.0.2 but alot of "Read-only file system" inside the log. But strange is that afterwards the a "Root/Busybox checker" App tells me that Busybox got installed ? Any recommendations what could be wrong ?
Last edited:
@YashdSaraf
Hi. In some Android path Cyrillic names not show if busybox installed.
My Android 6.1 use toybox and Cyrillic names work good.
for example this way /mnt/runtime/default/emulated/0
Second screenshot is toybox work, busybox uninstall.
You can improve this or I need to use system toybox?
Thanks.
Hi. In some Android path Cyrillic names not show if busybox installed.
My Android 6.1 use toybox and Cyrillic names work good.
for example this way /mnt/runtime/default/emulated/0
Second screenshot is toybox work, busybox uninstall.
You can improve this or I need to use system toybox?
Thanks.
Attachments
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
184Update 14-Jul/18: Busybox v1.29.0 released (Complete changelog: here)
Hello XDA,
All the flashable zips include two builds.
SELinux Enabled and Normal
This post will give you a pretty good idea about the difference.
There are 401 applets included in the normal and 413 applets included in the selinux build.
Here's a list for the same.
NOTE: Installing busybox does not modify your device's selinux status.
Architectures supported: arm, arm64, x86, x86_64, mipsel, mips64el and mipseb.
The attached zips install busybox in one of /magisk/bbxyds, [/data/adb]/su/xbin, /system/xbin, [/system]/vendor/bin after cleaning older busybox binaries and their symlinks from the device (if any).
Universal busybox installer flashable zip detects the architecture and installs busybox accordingly.
Code for mounting the su.img and running in embedded mode is borrowed from the SuperSU project.
SELinux status is automatically detected by the installers.
Behaviour of all the installers as well as the cleaner can be manipulated using a bbx.conf file which should be placed in one of /sdcard, /data or /cache. For more details refer to the second post.
TWRP recovery or Flashfire is recommended for flashing the attached installers, however the code is pretty generic and should work on other recoveries too.
Projects using my BusyBox builds are:
Open Gapps
Apps2SD
Project Skynet
StØck ROM Sense 5 by @denkem
Stock Debloated roms for nexus 5, 6, 5x and 6p by @tupac4u
Inlightning Org
Universal SafetyNet Fix by @Deic
If you would like to include my builds in your project, a link to this thread in the project thread would be expected.
Also, if you can, pm me about it so I can add the name to this list.
Credits:
@7175 for his thread
@bovirus @Chinaboy5216 @skulldreamz for testing and reporting
XDA for...do I need to say it
Disclaimer: Neither me nor anyone else at XDA is responsible for what happens to your device. Please use the tools/utilites attached at your own discretion.
Having said that, I'll try my best to help you with any bugs or exceptions you might face.
- Busybox-CLEANER.zip and all the installers clean BusyBox in /su/xbin /data/adb/su/xbin /system/xbin /system/vendor/bin /vendor/bin /data/adb/su/bin /system/bin /su/bin /magisk/phh/bin /su/xbin_bind /data/adb/su/xbin_bind and /magisk/bbxyds
- The installers will automatically detect 32/64 bit arch and install the appropriate binary
- NOTE: If FlashFire gets stuck on a black screen or errors out when flashing, please flash from recovery instead. (There seems to be a /system mounting issue on some devices in FlashFire)
File list:
- Busybox-<VERSION>-YDS-UNIVERSAL.zip
Flashable zip compatible with all architectures.
- Busybox-<VERSION>-YDS-<ARCHITECTURE>.zip
Architecture specific flashable zip files.
- Busybox-<VERSION>-YDS-<ARCHITECTURE>.tgz
Consists of pre-compiled busybox binaries.
Not flashable
- Busybox-installer-<ARCHITECTURE>.bin
Executable files for installing busybox without rebooting in recovery mode. See 2nd post for more details.
Not flashable
- Source code (zip, tar.gz)
Source code files automatically generated via Github releases.
Not flashable
For older versions refer to my androidfilehost, drive, mediafire or sourceforge folders.
Toolchains used for building these binaries can be found here (host arch -> x86_64).
For official busybox source and changelog refer here.
Do report how these work out for you, as most of the testing has been done on emulators.
You can request any applet in this thread. If it does not affect the size of the whole binary or there are enough users backing it, I'll add it in the next release.
When reporting please attach the BusyBox-YDS-installer.log, it should be in either /sdcard, /data or /cache.
Source:
https://github.com/yashdsaraf/busybox
https://sourceforge.net/p/busybox-yds/code31Op
bbx.conf:
Allowed options in bbx.conf are,
- installdir=<path>
Change the directory for installing busybox to <path>. If <path> is not a valid directory, then the installer will fall back to the default installation directory.
Note: Any older busybox installation in the supplied directory will be cleaned.
Warning: Please use this option only if you are absolutely sure about what you are doing.
e.g installdir=/data/local/xbin
- selinux=[0|1]
Controls the selinux support in busybox.
E.g To disable SELinux support
Code:selinux=0
To enable SELinux support
Code:selinux=1
- noclean
Sample:If supplied, the installers will skip cleaning any previous busybox installations.
To install busybox in /data/local/xbin without cleaning previous busybox installations with SELinux support enabled, following would be a valid bbx.conf file
Code:installdir=/data/local/xbin noclean selinux=1
Note: Busybox cleaner only reads the installdir option and cleans busybox in that directory
Self extracting executables:
All the .bin files in the download link in the above post are self extracting executables. They can install busybox directly from a terminal without rebooting in recovery.
Usage:Options:
- Install any terminal app.
- Get root privileges,
Code:
su
- E.g if you have the installer for ARM downloaded in sdcard, run this
in the terminal,Code:sh /sdcard/Busybox-installer-arm.bin
- And watch the magic happen.
-h | --help
Show help message.-i | --interactive
Run script in interactive mode.-nc | --noclean
Do not clean previous busybox installation(s) (IF ANY).-oc | --onlyclean
Clean previous busybox installation(s) (IF ANY) and exit.
If supplied, all other options are ignored except installdir.--selinux=[
es|o]
Enable or disable selinux support in busybox.--installdir=<path>
Install busybox in <path>.Tip: To clean busybox in a custom directory, run the installer in onlyclean mode and set installdir to the custom directory which needs to be cleaned.
e.g. to clean busybox in /data/local/xbin run the installer as
Code:sh <script_name> -oc --installdir=/data/local/xbin21Busybox update
Finally busybox is now fully Magisk compatible.
All the flashable zips will now install busybox as a Magisk module (if magisk >v13.1 is installed), also they can be installed from the Magisk manager app itself.
The busybox cleaner code has also been updated to clean the busybox Magisk module (if found)
Note: The offine installers (.bin files) should not be used for installing busybox as a magisk module. (Anyway, it'll give you a prompt for the same so no worries)
Of course this does not mean that you've got to have magisk installed, the legacy installation still works just fine. :good:
Lastly, sorry for the delay people, had to format nearly the whole core installation code
As always, please test and report if any errors are encountered.14
Ahh nice, I also need x86 and x86_64, but you can take your time.
I can wait for your complete release, I'm not in rush
BTW, I saw you have some issues with zip signing, here is a guide that might help you out
https://xdaforums.com/android/software-hacking/dev-complete-shell-script-flashable-zip-t2934449
Updated the op with links to fixed busybox builds. Do tell if they do not work for you.14BB v1.27.0 released (download link in op), please test and report if any errors are encountered.
Thanks for the heads up @bovirus.
New posts
-
-
Development [ROM][14][STABLE][UNOFFICIAL] Lineage OS 21 for Xiaomi 13 Fuxi- Latest: nguyenhung9x2018
