Closed maxweisspoker closed 3 years ago
I have determined what the issue is. The file "/sbin/.magisk/busybox/busybox" is mounted or copied from the file "/data/adb/magisk/busybox" and it is the following executable shell script:
#!/system/bin/sh
BB=/sbin/.magisk/busybox/busybox
[ -x $BB ] && exec $BB "$@"
exec /data/adb/magisk/busybox.bin "$@"
As you can see, it goes in an infinite loop.
My fix was simply replacing that script "/data/adb/magisk/busybox" with the busybox binary, copied from "/data/adb/magisk/busybox.bin". So now the mounted file "/sbin/.magisk/busybox/busybox" is actually a binary rather than that script. With that fix, my issue no longer occurs and everything seems to work correctly.
I am leaving the issue open, since the bug still exists.
This has something to do with ur device probably cause oneplus 7t, samaung A70 doesn't have any error
Re-run the direct install method in the Magisk app, it seems to me the busybox binary was corrupted
I have determined what the issue is.
Great work! Thanks a lot! One of my devices had the same bug, now it is cured.
Direct install re-run cannot help me, because for some unknown reasons I can only patch boot.img and then reflash it via fastboot on this device.
I have determined what the issue is. The file "/sbin/.magisk/busybox/busybox" is mounted or copied from the file "/data/adb/magisk/busybox" and it is the following executable shell script:
#!/system/bin/sh BB=/sbin/.magisk/busybox/busybox [ -x $BB ] && exec $BB "$@" exec /data/adb/magisk/busybox.bin "$@"
As you can see, it goes in an infinite loop.
My fix was simply replacing that script "/data/adb/magisk/busybox" with the busybox binary, copied from "/data/adb/magisk/busybox.bin". So now the mounted file "/sbin/.magisk/busybox/busybox" is actually a binary rather than that script. With that fix, my issue no longer occurs and everything seems to work correctly.
I am leaving the issue open, since the bug still exists.
This unfortunately isn't working for me. I can't find a folder named /sbin/ on the root of my device. Is there a better guide out there on how to fix this issue?
@yipchow Same here, I just installed the old classic busybox.
I worked around this by "upgrading" (I already had the latest version) to the current version of Magisk via direct install method, then rebooting.
I'm on a Moto G7 Play
with Magisk 24.2 (latest) and stock Android 9
thanks to this issue I found out a similar problem with my magisk/busybox:
channel:/data/adb/magisk # ./busybox
/system/bin/sh: ./busybox: not executable: 64-bit ELF file
I replaced the binary with a working one. the error disappeared.
Device is a Pixel 3 blueline. ROM is stock Lineage OS 17.1, with patched magisk boot img. Upgrade to v22 app and system installation worked fine. Afterwards, I re-installed all Riru apps, just in case they detected the new Magisk version. Root does work, and root apps don't complain, however some select apps, including EdExposed, stopped working. The culprit seems to be something with Busybox. (Note the lines with "busybox failed with 8: Exec format error").
Here is the Magisk log, with some redactions. Let me know if you need further information.