meefik / busybox

BusyBox for Android
https://meefik.github.io/busybox
GNU General Public License v2.0
1.46k stars 258 forks source link

Can't install #78

Open ghost opened 5 years ago

ghost commented 5 years ago

After giving root access, I tried installing, but failed.

Output:

### BEGIN INSTALL
Remounting /system to rw . . . fail
### END

What can I do?

ixaxaar commented 5 years ago

Same problem tried 1.30.1 and 1.29.2.

Specs:

$ uname -a
Linux localhost 4.4.179-Xiaomi_SDM660-LA.UM.7.2.r1-06900+ #1 SMP PREEMPT Tue May 7 14:19:19 UTC 2019 aarch64
# cat build.prop                                                      

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PQ2A.190405.003
ro.build.display.id=lineage_jasmine_sprout-userdebug 9 PQ2A.190405.003 16 test-keys
ro.build.version.incremental=16
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2019-04-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Tue May  7 14:08:46 UTC 2019
ro.build.date.utc=1557238126
ro.build.type=userdebug
ro.build.user=akshaykakatkar
ro.build.host=android
ro.build.tags=test-keys
ro.build.flavor=lineage_jasmine_sprout-userdebug
ro.build.system_root_image=true
ro.build.ab_update=true
ro.product.model=Mi A2
ro.product.brand=Xiaomi
ro.product.name=jasmine_sprout
ro.product.device=jasmine_sprout
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=Xiaomi
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=jasmine_sprout
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=jasmine-user 9 PKQ1.180904.001 V10.0.3.0.PDIMIXM release-keys
ro.build.fingerprint=google/taimen/taimen:9/PQ2A.190405.003/5310204:user/release-keys
ro.build.characteristics=nosdcard
ro.lineage.device=jasmine_sprout
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=kryo
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.lineage.version=16.0-20190507-UNOFFICIAL-jasmine_sprout
ro.lineage.releasetype=UNOFFICIAL
ro.lineage.build.version=16.0
ro.modversion=16.0-20190507-UNOFFICIAL-jasmine_sprout
ro.lineagelegal.url=https://lineageos.org/legal
ro.lineage.display.version=16.0-20190507-UNOFFICIAL-jasmine_sprout
ro.lineage.build.version.plat.sdk=9
ro.lineage.build.version.plat.rev=0

Lineage OS 16 custom build with su addon.

Is arm64 not supported?

k3dar commented 5 years ago

same problem, i think is problem with Android 9 system-as-root, where /system is not mountpoint, sollution will be detect this, or have option for "command to remount system" in settings... i think default is "mount -o remount,rw /system" but here is need (minimal for me Android9 HU) "mount -o remount,rw /dev/root /"

EDIT: i look in busybox/app/src/main/assets/all/scripts and in install.sh and remove.sh is "mount -o remount,rw /system" but i before make mistake, corrected+complete change for install/remove.sh for me is:

busybox ln -s /dev/block/by-name/system /dev/root
busybox mount -o rw,remount /

if i make this change in installed Bussybox app (path /data/data/ru.meefik.busybox/files/scripts), then busybox binary is installed ok(is in /system/xbin), Bussybox app/Information show v1.30.1-meefik as installed, but (also after reboot) if i run "busybox", then is still used default/system version, if run /system/xbin/busybox then is run ok correct busybox version v1.30.1-meefik...

"which busybox" show "/system/bin/busybox", in $PATH is "/system/xbin"

i think problem is with non existing "/system/addon.d"(this is also say while in Busybox app install) which is in install.sh used for "redirecting" busybox to xbin, but if i'm correct this is dir used by Magisk, but i have rooted using SuperSU

kocjs commented 4 years ago

Same as OP here. Official Lineage OS 16, MotoX4

@k3dar can you please provide a detailed instruction on how to install. Please fix.

k3dar commented 4 years ago

Same as OP here. Official Lineage OS 16, MotoX4

@k3dar can you please provide a detailed instruction on how to install. Please fix.

as i write install busybox app, then in path /data/data/ru.meefik.busybox/files/scripts change in two skript install.sh and remove.sh

from: mount -o remount,rw /system to:

busybox ln -s /dev/block/by-name/system /dev/root
busybox mount -o rw,remount /

but still is problem with primary use stock busybox from /system/bin/busybox and for running this is need call /system/xbin/busybox - but maybe this problem is only with using SuperSU and with Magisk be ok, try and see ;-)

2011 commented 4 years ago

Same problem (using 1.30.1) - and I have Magisk, and not SuperSU. Does this issue still exist in 1.31.1 (F-Droid doesn't have anything later than 1.30.1 - I have poked them, and asked them to provide the latest version)?

mspacek commented 4 years ago

93 fixed this for me on my Android 9 phone.