Device-info: - Phone: Sony Xperia Z1 - Model number: C6903 - Android version: 5.1.1 - Build Number: 14.6.A.1.236 - Rooted, BusyBox and Terminal Emulator installed (Play Store Version!!!) I have formatted an SD-Card to an ext4-filesystem and put another Linux on it. After mounting the filesystem and files without problems I want to execute: chroot /data/local/mnt /bin/bash with /data/local/mnt is the Linux root-folder. Execute the line above leads to the message: chroot: can't execute '/bin/bash': Permission denied I have checked the permission of /bin/bash and also of /data/local/mnt and remounted nearly every path which are related to that folder with exec and rw permission. So maybe you know some special rights-associated files or folders I forgot, but I think the problem is something else... After readed that some of the [Linux-on-Android project-users](http://forum.xda-developers.com/showthread.php?t=1585009) had some trouble with executing the init.sh because of selinux I set it to permissive: root@C6903:/ # setenforce 0 and checked it: root@C6903:/ # getenforce Permissive (Of course) chroot does not work. So I checked the message buffer of the kernel for selinux-avc-deny-messages and BINGO: root@C6903:/ # dmesg | grep denied ... [58575.652383] type=1400 audit(1470337082.042:10188): avc: denied { read } for pid=18553 comm="busybox" name="mmcblk0p23" dev="tmpfs" ino=9821 scontext=u:r:ric:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file op_res=0 ppid=4602 pcomm="ric" tgid=4602 tgcomm="ric" [58575.653740] type=1400 audit(1470337082.042:10189): avc: denied { open } for pid=18553 comm="busybox" name="mmcblk0p23" dev="tmpfs" ino=9821 scontext=u:r:ric:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file op_res=0 ppid=4602 pcomm="ric" tgid=4602 tgcomm="ric" [58575.655002] type=1400 audit(1470337082.042:10190): avc: denied { ioctl } for pid=18553 comm="busybox" path="/dev/block/mmcblk0p23" dev="tmpfs" ino=9821 scontext=u:r:ric:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file op_res=0 ppid=4602 pcomm="ric" tgid=4602 tgcomm="ric" These are just 3. You can have some more if you want! So 1. QUESTION: **Why does selinux denies something when getenforce returns Permissive???** But I thought first that could be fixed anyway by allowing all these denied permissions with: supolicy --live "allow source_class target_class permission_class permission" FOR EXAMPLE: root@C6903:/ # supolicy --live "allow ric rootfs file execute_no_trans" which returns: Patching policy ... -allow:ric:rootfs:file:execute_no_trans=ok - Success Well (of course) it did not work AND I get a denied message for the exact same case for a bunch of cases. So 2. QUESTION: **Why does allowing policies not change policies to be allowed???** (Of course) I am not 100% sure if the denial of executing chroot is related to selinux and it would be very easy to find it out if I could just set it to permissive.... So 3. QUESTION: **How to solve this problem?** In [Graeme Hill's Dev Blog](http://graemehill.ca) article [Compiling a permissive Android kernel](http://graemehill.ca/compiling-permissive-android-kernel/) he says: >There is a command called setenforce which toggles modes, and there are some apps on the Google Play store which do the same thing, but none of them will work until we modify the kernel. 4. Question: **Is that related to every device with Android 5.X or differs from manufacturers?**

I have a large (1.3GB) binary file on internal/emulated storage of an Android device running KitKat (4.4.2, API 19); I want to truncate this file to a slightly smaller size (1.2GB), without copying/transferring it all over again. Device is rooted, and I have adb + shell access. On Linux I could have just run truncate --size=1.2G path/to/file; however the shell pre-installed on the device is BusyBox v1.21.0-jb bionic, which doesn't seem to contain a built-in truncate command. Based on [BusyBox changelogs](https://busybox.net/) , truncate was only added in 1.24.0. What are my options? * Device storage has only ~400MB left, so making a dd-style copy of required size (and then deleting the original) is not an option. * Could not find an alternative command that would behave in this way (remove trailing content from file / shrink it, in-place). * Tried copying and running the truncate binary from another device (Android 8.0); however it wasn't compatible (gave an error CANNOT LINK EXECUTABLE: empty/missing DT_HASH in "./truncate" (built with --hash-style=gnu?)) (FWIW in the end, found that the binary was actually a toybox multi-call binary). All other devices at my disposal don't seem to contain truncate command. * Tried to find a standalone truncate binary online - which I can install without touching the existing busybox installation - but could not find any pointers.. or at least any indication that such standalone binaries exist for Android at all * Tried few common file browsers (device built-in file explorer com.rhmsoft.fm, ES File Explorer) but could not find a suitable action/option. I would prefer to avoid installing a complete app/apk for this purpose alone, but would go with it if that's the only option; anyways, I'm quite doubtful if such an option would be available in APK form at all.

In my /system/bin/ I have a executable named toybox, and various other directory entries in that directory symlinked to the toybox, eg basename and [. How do I uninstall toybox? Context: I believe it's messing with advanced root detection of Citi banking (my Revolut app is working just fine with Magisk's SafetyNet Fix)

It is confusing that there are so many tty files in the /dev directory... By the way, what does each file in /dev stand for? Do they stand for physical devices which are part of my Android device? For example, which file stands for the raw storage device in the /dev directory?

I am trying to create system users on an Android x86 virtual machine, but the binaries adduser and addgroup don't exist (neither useradd or usermod). I installed BusyBox to get access to these utilities but when trying to run addgroup to create a new system group I get error addgroup: /etc/group: No such file or directory. When trying to run adduser with an existing system group I get error adduser: unknown group net_bt_admin. The only way to create users I found so far is through pm create-user, but these are android level users, how can I create users quivalent to shell or system default users?

I have a drone remote that has android in it. It has an internal telemetry server that is publishing data on localhost:14445 via UDP. When I open the hotspot from this device and connect to it with my computer I'm getting the usual 192.168.43.xx type of IP address. I can ping internal IP addresses of the remote (other than 192.168.43.xx form, for example, devices attached to eth0 interface with IPs like 192.168.144.xx) so I have some sort of access to internal IP's from the hotspot. But I cannot communicate with the internal UDP port I mentioned before. As Wireshark shows, something is blocking the UDP connection between hotspot and internal IPs. I tried port forwarding and it didn't work but I don't know if I did it correctly. I have busybox and root access, please help me. I can give further information upon request.

I have an Android 10 LGK22 No-Rooted without option to do it (so rooting is out of the question/solution). Which is not ridiculously forcing W^X (the option to stop a binary from being executed from a home directory). At least on Termux. However I'm trying to execute a busybox binary from SimpleSSHD's home folder. But I keep getting errors: permission denied. Same happens with Simple-Busybox, can't execute busybox on its own home folder. I know it's doable within the tmp folder, but the default location on my phone /data/local/tmp is not world readable/writable/executable 777. **Is there any subfolder within /data/local/tmp with x permissions or somewhere else to execute a binary from?**

I have successfully been able to copy busybox into system/bin/. I have also set busybox

chmod +g busybox
chmod +s busybox
chmod 4777 busybox

When I run busybox su it says user root not found. How do I add the user in android?. Maybe I will need to write some files in system/etc maybe?

**Question :How to infuse/push/modify/install busybox SU in twrprecovery.img for getting root privilages commands** I want to take backup restore flash change some PM Package management and SM storage Management settings of my android 5.1.1 /6.0 mobile phone through adb shell commands or through twrp terminal without installing twrp or SU or rooting mobile device 1. Firstly I want to take backup of mobile system.img userdata.img through adb pull command and then recover write back adb push My concerns related to first : a. As adb pull reads and copy data but adb push writes on the device b. Will adb push work without rooting mobile phone without root privilages. c. If phone bricked or something gets wrong while rooting and phone is not rooted then will adb push work or not. Steps of commands using for backup of device Adb devices adb reboot bootloader adb pull /dev/block/mmcblk0 mmcblk0.img Adb push mmcblk0.img /dev/block/mmcblk0 mmcblk0.img 2. Using PM package manager on unrooted mobile android 5.1.1 with following commands but error Adb devices adb reboot bootloader adb shell pm set-install-location 2 adb shell pm get-install-location Error of command > /sbin/sh: pm: not found what I understood from above error means that PM binary command file is not available in /sbin/sh/ folder as phone is not rooted so what I think if I put these binary files or install busybox within twrprecovery.img before loading and run temporary pm command so that I don't have to root the device and temporary set the changes in device. If it's possible then kindly share the link for step by step procedure for modifying twrprecovery.img before booting in pc computer windows as I am new novice to adb shell Linux commands 3. Thirdly As whenever I run SM storage manager command adb shell following command on unrooted android 6.0 mobile from it gives following errors Adb devices adb reboot bootloader adb shell sm has-adoptable adb shell sm set -force- adoptable true It gives following errors > /sbin/sh: sm: not found what I understood from above error means that SM binary command file is not available in /sbin/sh/ folder as phone is not rooted so what I think if I put these binary files or install busybox within twrprecovery.img before loading and run temporary pm command so that I don't have to root the device and temporary set the changes in device. If it's possible then kindly share the link for step by step procedure for modifying Twrprecovery.img before booting in pc windows as I am new novice to adb shell Linux commands 4. Now if boot in fastboot mode and run twrprexovery.img or cwgmod recovery.img with these commands and then in twrp or cgmod terminal windows can I run busybox or Super user or PM SM command Adb devices Adb boot bootloader Fastboot boot twrprecovery.img 5. Secondly the whole ideas is that I want to virtually temporary use twrp terminal with busybox or Super user binary to execute services packages like PM (package manager) SM (storage manager) within from twrp recovery menu terminal (loaded in fastboot boot twrprecovery.img mode). Or adb sideload If it's possible technically feasable. If yes then can we modify twrprexovery.img and infuse insert busybox in it before loading or after loading. 6. Thirdly I don't want to install twrp or busybox or any super user binary file inside mobile device and don't want to install anything inside mobile except the changes alteration of settings done after execution of SM PM commands. That is I want to execute PM SM from within twrprecovery.img

**Dear developers,** I have an issue with my script switching from Android 9 to 10 (devices from a Umidigi S3 Pro to a Umidigi F2). I have installed Bosybox App on the first and Busybox Magisk module on the latter. Now the script does not work because the command: list=(busybox find "$dirs" -type f -name *.$ext) returns an empty array. This is the complete script: #!/system/bin/sh echo if test "$1" = ""; then echo "Randomfile script by Uranya v1.4 01.01.2021" echo "Usage:" echo "sh randomfile.sh " exit 1 fi dirs=$1 ext=$2 dird=$3'/' dest=$dird'random' delim1="" delim2="" last='last.txt' # create filename's array IFS=$'\n' list=(busybox find "$dirs" -type f -name *.$ext) # count number of files num=${#list[@]} # generate random number in range 1-NUM let "ran=(${RANDOM} % ${num})+ 1" echo Random from $num files is $ran sour=${list[ran]} sourn=${sour#$dirs} sourn=${sourn:1:${#sourn}} date=$(date +"%Y.%m.%d %H:%M") day=$(date +"%d") hour=$(date +"%H") minute=$(date +"%M") message='---------------------------------------\n'$date' - '$num' >>> '$ran'\n'$delim1$sourn$delim2 if ([ "$day" = "01" ] && [[ "$minute" $dird$last $message else sed -i '1i'$message $dird$last fi echo $delim1$sourn$delim2 # rename the old file cp $dest.$ext $dest'_back.'$ext # copy the file cat "$sour" >$dest.$ext echo File copied as $delim1$dest.$ext$delim2 Can you please help me to understand why this happens, and how to fix it? Thank you very much for your attention!

Hoo roo, Installing Linux Deploy (Linux chroot with root) on Android 9 requires that you install a custom version of busybox . However, due to system-as-root limitations on Android 9, you can encounter problems when attempting to run the custom busybox installer. The community has found a solution to overcome this , but I can't seem to get it to work. My tablet is a rooted Onyx Boox Max 3 that has TWRP installed without a custom ROM, with dm-verity disabled. Running

-l which su

from a terminal emulator returns

1 root root 8 1970-02-11 19:10 /sbin/su -> ./magisk

so confirms that I am using the root busybox.

/system/xbin

after mounting /system as per instructions softlocks the tablet. Have also tried running

-o rw,remount /sbin/magisk/mirror/system_root

which also softlocks. Are there any other options that I can try? Would really love a chroot of Arch on my eink tablet instead of just a proot. Would make for a much smoother experience. Cannot emphasise how desperate I am, my failsafe is a proot using nix-on-droid, but reckon that performance will suffer. Does anyone have any ideas?

The [Debloater module](https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/ "[MODULE][Terminal] Debloater v17.3.2 - Debloat Systemlessly! | XDA Developers Forums") module of Magisk tells me that Busybox isn't detected: root@android:/data/adb # debloat debloat ! Busybox not detected Please install one (@osm0sis' busybox recommended) ========================================= Debloater (Terminal Emulator) v17.3.3(76) by veez21 ========================================= BusyBox not found! ========================================= However I've installed it via Magisk Manager, and I have rebooted after installation. Why is that? Is it a problem? There is a [similar question](https://android.stackexchange.com/q/171751/94084) , but it's because the OP confuses Windows command and Android shell command.

e.g. android busybox command: busybox ls -ls foldername/ outputs are: Jan 1 2015 or Oct 16 14:18 The first one doesn't show time while second one does not show year. How to make the output show complete date time e.g.Oct 16 2019 14:18?

Is there any reason a programmatic or command-line shutdown (or reboot) process in Android 7.1 might randomly result in a hard freeze-up, requiring a long (~8 second) press of the power button to force the shutdown? It doesn't happen every time, but seems to randomly happen infrequently, but frequently enough to be a problem. ***Background Info...*** I'm developing a "kiosk" style tablet, which runs 24/7. It's rooted and I have full control over it. It also has a customization from the supplier to automatically turn on when power is connected. To keep things fresh and responsive, I want to issue a nightly reboot command. The reboot command was originally just a call to /system/bin/reboot -p via my own app "watchdog" kind of service that always runs in the background. *(Yes, I know the -p causes the tablet to turn-OFF, but then our custom auto-boot will turn it back on immediately, if power is connected, resulting in a reboot situation... doing a pure reboot without the -p causes more problems)* Anyway, I've since moved on to experiment with all of the following commands to cause a shutdown/reboot, and none really fix the problem. - /system/bin/setprop sys.powerctl shutdown - /system/bin/svc power shutdown - /system/bin/am start -a android.intent.action.ACTION_REQUEST_SHUTDOWN - /system/bin/busybox poweroff -f - /system/bin/busybox poweroff -d 10 -f One more bit of info... I made an app to shutdown/reboot the device every five minutes. I've been running it on about a dozen devices, and have about 4 or 5 failures every 24 hours.

I can't see the MAC address of my phone when I use command busybox ip link show on my rooted LG phone. Here is screen shot: Does anyone know what seems to be a problem?

Sometimes i investigate foreign phones, where i can't root or install any Apps. But i want to examine the filesystem via adb shell, and view some text-files. Like i usually do with a *nix-shell: with the less or the more command. Both are absent in the shell, that i can access with adb shell. My workaround until now is using the linux tool screen in conjunction with the adb-shell-command cat. (C-a Esc to scroll, '/' to search, Esc Esc to quit Copy-mode)

I'm using a rooted Huawei G7 and i'm trying to install BusyBox, but I keep getting an error. I'm 100% sure this error is because there is some weird write protection on /system. I know this because every time I try to change it to RW in ES File Explorer it changes back to RO when I close the app. I also tried some terminal commands but with no luck so far. EDIT: Here is the full log: u0_a161@hwG7-L01:/ $ su root@hwG7-L01:/ # mount … /dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0 … root@hwG7-L01:/ # mount -o rw,remount /system mount: Read-only file system 255|root@hwG7-L01:/ # mount … /dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0 … EDIT: When I try the mount command, I always get the error Read-only file system. I don't know why, but could it be possible to put /system in RW mode from the recovery menu?

I installed busybox free on my android device. I have super user and stuff. When I click on the busybox widget, it gets me to the configuration utility where I can install / uninstall. It is installed. How can I execute the busybox binary now?

I'm using LG Optimus Black P970 with ICS 4.0.4. After rooting my phone, when I'm writing in the terminal the command busybox iplink show eth0, it shows iplink applet not found. What should I do? Also how do I find /data/misc/wifi?

Phone: Xiaomi Redmi 4 prime Rom (custom): lineage-13.0 Xposed: xposed-v87-sdk23-arm64 Root: SuperSU.Pro.2.82 Right now everything works just fine and those apps that need root privileges to work properly, asking for root permission and after granting, they work fine; There's just one app call Performance Profile (an xposed module) that after running asserts that: **"root access failed or busybox was not found"** I do have successfully installed BusyBox 6.7.3.0 What is the problem with this app? **Update 1**: I uninstalled BusyBox 6.7.3.0 and installed BusyBox 1.26.2 and using BusyBox Checker Pro 2.0 got the following results showing that everything is ok.