I have an op3t (still) on oreo, rooted with magisk, Versions are up to date.
Some months ago I noticed that the magisk busybox module is no longer getting updated, when I update. It kept stuck at v1.29.3. It didn't bother me too much since then.
Yesterday I wanted to address the issue and uninstalled the module, in order to install the current one right after (hopefully tricking it to "update" that way). Instead I never manged to install it ever after. There is no /su folder on my phone, /system/xbin contains nothing bb related, and there's also no trace to bb anywhere else, although your installer always tells me that everything "went fine". I didn't even manage to install any other busybox from the PlayStore.
Still one bb seems to exist, in /sbin/. magisk/busybox, but that isn't yours, right? And it's not useable in system, right?
I just checked that /system/xbin is writable by root, but now I'm out of ideas...
"/dev/tmp/su/xbin"Ah! Stupid me did do this before but had no look into it, because I thought there isn't likely too much new info there, while no errors are shown in the magisk "flashing" screen. But obviously that's wrong.
Here you are:Code:- Copying zip to temp directory - Installing Busybox_for_Android_NDK-1.30.1(13020).zip Archive: /data/user/0/com.Povw.HKC.FbYQ8Qe/cache/flash/install.zip inflating: install.sh inflating: module.prop mount: can't read '/etc/fstab': No such file or directory Busybox Installer Script by osm0sis @ xda-developers mount: can't read '/etc/fstab': No such file or directory mount: can't read '/etc/fstab': No such file or directory Mounting... Extracting files... Archive: /data/user/0/com.Povw.HKC.FbYQ8Qe/cache/flash/install.zip creating: META-INF/ creating: META-INF/com/ creating: META-INF/com/google/ creating: META-INF/com/google/android/ inflating: META-INF/com/google/android/update-binary inflating: META-INF/com/google/android/updater-script inflating: README.md inflating: busybox-arm inflating: busybox-arm64 inflating: busybox-mips inflating: busybox-mips64 inflating: busybox-x86 inflating: busybox-x86_64 inflating: install.sh inflating: module.prop Installing... Using architecture: arm64 umount: can't unmount /dev/tmp/su: No such file or directory Using path: /dev/tmp/su/xbin Cleaning... Creating symlinks... Unmounting... umount: can't unmount /system: Device or resource busy umount: can't unmount /data: Device or resource busy umount: can't unmount /cache: Device or resource busy Done!
You clearly have a su.img on your device. Look in /data or /cache and clean up your messy device. :good:
Last edited: