yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] adriansticoid:
[MENTION=5423715]YashdSaraf[/MENTION], so after I updated to Magisk 13.1, I flashed your BusyBox since Magisk doesn't ship with it anymore. So everything went fine until I opened Titanium Backup. It doesn't detect root although I have more than 10 other apps which I already granted access. I reported this to the Magisk support thread and some users said they had no problems with TiBu and the new Magisk. So I uninstalled the BusyBox 1.27, after that TiBu detected root again. I tried installing BusyBox using Stericson's and Jared's installers and both were fine with TiBu. So the only problem is with your BusyBox. Any ideas on this? I would love to use yours instead.
[Android Software/Hacking General [Developers Only]] nguyentankiet:
+1

But it no problem with supersu
[Android Software/Hacking General [Developers Only]] mauam:
Same here!
[Android Software/Hacking General [Developers Only]] YashdSaraf:
From a quick read it seems the issue is that TiBu detects busybox's su instead of supersu or whatever other su bin you've installed. I'd say it's time we got rid of these conflicting bins which are pretty useless. :mad:

I'll post a test busybox bin after removing su applet ASAP, if you could test that, we'd know if that applet is indeed what's causing the issue. :)
[Android Software/Hacking General [Developers Only]] adriansticoid:
Would love to test it. :)
[Android Software/Hacking General [Developers Only]] ale5000:
If possible could you keep 2 versions please?

For the ones that use it directly instead of installing, it would be preferred to have all applets (including su) and prefer internal applets instead of system ones (using CONFIG_FEATURE_SH_STANDALONE_SHELL) if possible.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Ok, I guess a compromised solution would be, we maintain a blacklist, the applets in this list won't be symlinked while installing busybox, i.e. Say su is blacklisted, it will only be accessible by typing

busybox su

in a terminal. This solution in my opinion satisfies both the cases.
[Android Software/Hacking General [Developers Only]] ale5000:
Yes, it should work thanks.
[Android Software/Hacking General [Developers Only]] Aid777:
Having same issue as the other users above. I have latest Magisk 13.2. Flashed the BB zip and it worked okay. Root Checker Pro states root and BB okay, but cannot start AdAway or TB. Flashify works fine though. Used the cleaner zip and all back to normal.
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5423715]YashdSaraf[/MENTION]

Please build the new busybox using the last version of source code (1.27.1 stable) just released Thanks.
[Android Software/Hacking General [Developers Only]] Tecalote:
[MENTION=5423715]YashdSaraf[/MENTION] During flashing Magisk the script shows the message: system root detected - I think it is really because of the busybox su...

Waiting for new stable 1.27.1. Thanks for your great work :)
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Thanks for reporting people. Could you please get me the output of the following command,

ls /*/*bin/su

I think I know where the error lies, these commands will confirm my doubts :p
[Android Software/Hacking General [Developers Only]] mauam:
Here.
[Android Software/Hacking General [Developers Only]] Aid777:
Sorry, I cannot post my result as I now have flashed ROM again and the SuperSu and flashed this BB zip and it works as it should.
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5423715]YashdSaraf[/MENTION]

When it will be available the busybox 1.271.?

Thanks.
[Android Software/Hacking General [Developers Only]] Chinaboy5216:
When it's ready ...
[Android Software/Hacking General [Developers Only]] Legend_dimebag:
Available pre-release to https://github.com/yashdsaraf/bb-bot/releases/tag/v1.27.1-YDS-201707220844
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Please do not download files marked pre-release, they're for me and some testers and are most likely BROKEN. :)

---------------------------------

BB v1.27.1 released, for changelog and download links please refer to the op.
[MENTION=3563392]mauam[/MENTION] [MENTION=5933297]adriansticoid[/MENTION] Could you please test the latest release and report if the magisk error still persists. :)
[Android Software/Hacking General [Developers Only]] adriansticoid:
Process ended with error 2. Tried to reflash 1.26.2 and it flashed fine.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Thanks for reporting [MENTION=5933297]adriansticoid[/MENTION].

I'm pulling the release for now, will reupload it as soon as the error is fixed.

EDIT: Fixed busybox builds are now available. :good:
[Android Software/Hacking General [Developers Only]] wooser:
MagiskHide (SafetyNet fails) and Titanium BackUp Pro don't work..... What a shame....

[Lastest Version v 1.27.1]
[Android Software/Hacking General [Developers Only]] carlosggb:
Magisk hide, safetynet pass, used the binary on my kernel, all good, great work!

Titanium backup works
[Android Software/Hacking General [Developers Only]] adriansticoid:
Dafuq. Still no go [MENTION=5423715]YashdSaraf[/MENTION].
[Android Software/Hacking General [Developers Only]] leo.riv:
[MENTION=5423715]YashdSaraf[/MENTION]

Can i use with Magisk v13.3
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Ok, the magisk compatible approach does not seem to work.

So I'm making the flashable zips magisk modules themselves, then they can be flashed via recovery or installed from magisk manager. I've written the initial code, I'll post the updated installers in a few hours. Thanks for the patience guys :)
[Android Software/Hacking General [Developers Only]] R1kM@n:
Thank you very much Yashdsaraf for your faster to make the busybox recovery flashable zip! And excuse me for my bad english, I'm italian ;)
[Android Software/Hacking General [Developers Only]] wooser:
Thanks to you bro :)
[Android Software/Hacking General [Developers Only]] Aldideos:
I use your busybox from 9/may/17 and I have no problem with Magisk, I have only to reflash magisk after flashed the busybox.

Thanks
[Android Software/Hacking General [Developers Only]] Allen_Walker:
I use your 1.27.0 arm busybox with magisk 13.3 now.

And have no problems with TiBu and root operation.

I use Universal SafetyNet Fix v2 beta 5 test 4 and MagiskSU.

Busybox installed to system/xbin.

Thanks.
[Android Software/Hacking General [Developers Only]] Legend_dimebag:
[MENTION=5423715]YashdSaraf[/MENTION] I flashed the busybox 1.27.1 and immediately after magisk 13.3 and the safety net is ok, no problem! Sorry for the post pre-release, it was not my intention to create problems! ?
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Busybox 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 :p)

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.
[Android Software/Hacking General [Developers Only]] Legend_dimebag:
No problem with the latest release 1.27.1,Thanks for the constant updates!
[Android Software/Hacking General [Developers Only]] adriansticoid:
Hell yeaaahhh! TiBu works now with your BusyBox. Awesome work [MENTION=5423715]YashdSaraf[/MENTION]. Keep it up. :)
[Android Software/Hacking General [Developers Only]] Allen_Walker:
I flashed bb 1.27.1 and now I have 2 bb in system/xbin and magisk/bbxyds/system/xbin.

It's OK?
[Android Software/Hacking General [Developers Only]] adriansticoid:
Don't worry about that. Those are just the same.
[Android Software/Hacking General [Developers Only]] ale5000:
Thanks.

It isn't urgent but it would be useful a build with these changes included:

They can be found here.
[Android Software/Hacking General [Developers Only]] mauam:
Always force close magisk manager when try to add module (Busybox-1.27.1-YDS-ARM.zip).
[Android Software/Hacking General [Developers Only]] adriansticoid:
Try flashing it in recovery. That's what I did.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
[MENTION=5627087]ale5000[/MENTION] Those commits are in the master branch, I only update busybox when a *_stable branch is updated (e.g For now it's 1_27_stable). This way we can be sure there are no breaking changes in the builds.

Hmm, strange, could you please get me the /sdcard/BusyBox-YDS-installer.log
[Android Software/Hacking General [Developers Only]] mauam:
Do I need to flash it in recovery!? I thought I could install it like a magisk module (through magisk manager), like the others magisk modules.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
You can, and it does work via Magisk Manager on my Mi 4.

That's why I asked for a log, because it shouldn't force close on you. :)
[Android Software/Hacking General [Developers Only]] mauam:
Here you go.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Thanks, but I meant the log from the installation where Magisk Manager force closed on you. :p
[Android Software/Hacking General [Developers Only]] mauam:
:laugh: sorry. Let me know if I grab them or not.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
[MENTION=3563392]mauam[/MENTION], Please try installing this release from Magisk Manager. I just tested it via Magisk manager on my Mi4 and Oneplus 5. I've worked around some mounting errors, maybe they were the culprit in your case.

https://github.com/yashdsaraf/bb-bo...1-YDS-201707241916/Busybox-1.27.1-YDS-ARM.zip

Thanks.

Also, if you face any errors, please send here the /sdcard/BusyBox-YDS-installer.log.
[Android Software/Hacking General [Developers Only]] mauam:
Works perfectly through the magisk manager now. You're the man:cool:
[Android Software/Hacking General [Developers Only]] alecxs:
Hi YashdSaraf,

first of all, many thanks for your work! Have tested with an older Jellybean Phone and Carliv Touch Recovery, its not working. seems the unzip options unknown..?

i have tried 2 times, second try with mounted /data and /system

i just need the binary, like to see download links for binaries only

many thx in advance
[Android Software/Hacking General [Developers Only]] wooser:
Now works very nice :D !!!

Busybox is installed as a Module in Magisk :D

It works very well with Lucky Patcher and Titanium Backup

and I passed SafetyNet :D

Thanks a lot :)
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Thanks for reporting, that has been a long lurking error. I'll look into it ASAP.

The .tgz files in the download links contain only binaries.
[Android Software/Hacking General [Developers Only]] ale5000:
I'm not sure if they are related to the problem reported by [MENTION=7285913]aIecxs[/MENTION] but I have encountered two problems with old recoveries:

1) unzip: zip flags 1 and 8 are not supported (it can be fixed by changing the sign procedure)

2) missing /tmp in the recovery (it can be fixed by auto-creating and auto-mounting /tmp)

I believe I have fixed all compatibility problems, for those interested look at my zip (not related to BusyBox).

[MENTION=5423715]YashdSaraf[/MENTION]

Edit: Looking at the log it seems like the problem 1
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Could you please check if you get unzip errors on flashing https://github.com/yashdsaraf/bb-bo...1-YDS-201707241916/Busybox-1.27.1-YDS-ARM.zip as well?
[Android Software/Hacking General [Developers Only]] Neejay:
I've tried the official zip and this one. The official force closes magisk 13.3 for me, and this one fails. Nexus 6P, 7.1.2. Thanks.

Edit: TWRP flash worked though.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Thanks for reporting, I'll look into the issue ASAP. From a quick look at the log it seems there's some errors mounting the SuperSU img when flashing from magisk manager app. I'll try to reproduce the error on my device. :)
[Android Software/Hacking General [Developers Only]] Allen_Walker:
[MENTION=5423715]YashdSaraf[/MENTION]

Hello.

This Unicode problems stay here again.

https://xdaforums.com/showpost.php?p=67393867&postcount=40

I use 1.27.1 Arm (64) for magisk 13.3 module.

Miui 8, Android 7.

Thanks.
[Android Software/Hacking General [Developers Only]] psychoela:
"Unmounting /system -- umount: can't umount /system: Invalid argument"
[Android Software/Hacking General [Developers Only]] 6hexanexz:
Why cod not working
[Android Software/Hacking General [Developers Only]] schluger:
So only works with arm 64 and 86? Is that correct?
[Android Software/Hacking General [Developers Only]] 6hexanexz:
Please what is new code
[Android Software/Hacking General [Developers Only]] mauam:
Try by yourself & report. I think it only works on 13.1 & above. Check here.
[Android Software/Hacking General [Developers Only]] daitalos:
Excellent! Nice work..

Thanks for update....
[Android Software/Hacking General [Developers Only]] ale5000:
Is it possible to include "read" or another way to read input?
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Could you all please try this release, https://github.com/yashdsaraf/bb-bot/releases/tag/v1.27.1-YDS-201707301927?

I've patched busybox source for unicode support, made some fixes in the installer and switched to another signing method as well.

Please test and report if it works.

Thanks. :)

Why not use busybox's sh instead? It gives you the read command.

If you don't want to spawn into another shell, you can still use it to pipe the input to some other command,

$ busybox sh -c 'read input; echo $input' | busybox cut -d' ' -f2
Hello world
world

Hope this helps. :)
[Android Software/Hacking General [Developers Only]] ale5000:
I need to read only one char with for example "read -n 1" but if I'm not wrong the one on Android is limited and it doesn't support this parameter (and many others).

Also it is just an attempt because I'm not really sure if the Volume +/- button pressed when inside recovery actually output a char that can be read.

There is another binary that should work for this purpose: "keycheck".

But I have only found a compiled ARM version of it, the sources are here: https://github.com/sonyxperiadev/device-sony-common-init/tree/master/keycheck
[Android Software/Hacking General [Developers Only]] Allen_Walker:
Unicode working. Thanks again ;)
[Android Software/Hacking General [Developers Only]] Neejay:
It installed just fine via magisk manager, thanks!
[Android Software/Hacking General [Developers Only]] psychoela:
Perfect thanks:D
[Android Software/Hacking General [Developers Only]] kwanthenewbie:
Arm64 support?
[Android Software/Hacking General [Developers Only]] Legend_dimebag:
Read first post ?
[Android Software/Hacking General [Developers Only]] YashdSaraf:
arm64 non selinux build works just fine, but selinux build segfaults on most devices.

So (for now) either use arm64 non selinux builds or arm (32 bit) selinux builds.

For more info see: https://xdaforums.com/showpost.php?p=72002047&postcount=273

[MENTION=8134535]kwanthenewbie[/MENTION] You don't need to do anything if you're using the latest installers, they'll install arm bins even if you have an arm64 device.
[Android Software/Hacking General [Developers Only]] Tecalote:
[MENTION=5423715]YashdSaraf[/MENTION] I have a problem if I include your build 1.27.1 (latest and the one before) into the Rom script. It does not occur on Android 6 Huawei P8 in Rom script (works perfectly)

- but on Android 7 Huawei P9.

My updater-script installs first Magisk 13.3, after another Magisk module (SELpermissive) and at last your BusyBox. If I do it in that order I get errors and Busybox Installation is broken.

If I let install your BusyBox in updater-script before Magisk 13.3 it is okay (installs to system/xbin) but then it is not a Magisk Module.

I dont know whats happen - because if I flash your latest build (after installing my Rom, if I don't include it) with TWRP on P9 everything is okay. But it works not if it is included in updater-script...

Thanks for your great BusyBox! :)
[Android Software/Hacking General [Developers Only]] Ibuprophen:
I ended up trying it out by redoing the phone.

Installed the new BusyBox and it worked.
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5423715]YashdSaraf[/MENTION]

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.
[Android Software/Hacking General [Developers Only]] m0han:
i'm using an arm64 selinux enabled version that i obtained on 4th april or so with md5: d3bea86e970e2a813edd235cc17abec1. but, the one that is available here is seen to have been uploaded on 6th april and has a different md5. should i switch to the 'newer' one?
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Well at least the log file was created this time :p. 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:
[Android Software/Hacking General [Developers Only]] m0han:
is this meant for everyone? is this worth trying?
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5423715]YashdSaraf[/MENTION]

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}
[Android Software/Hacking General [Developers Only]] YashdSaraf:
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 :mad: 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.
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5423715]YashdSaraf[/MENTION]

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?
[Android Software/Hacking General [Developers Only]] MD500:
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/
[Android Software/Hacking General [Developers Only]] BoGnY:
the AFH directory isn't accessible..
[Android Software/Hacking General [Developers Only]] Benik3:
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? ;)
[Android Software/Hacking General [Developers Only]] jcfunk:
[MENTION=5423715]YashdSaraf[/MENTION]

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
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Hey,

Thanks for letting me know. :D

I've updated the op, also the toolchains for mips64el and x86_64 archs have been uploaded.
[Android Software/Hacking General [Developers Only]] hamzaeid:
thanks pro :good::good:
[Android Software/Hacking General [Developers Only]] jcfunk:
[MENTION=5423715]YashdSaraf[/MENTION]

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.