OnePlus 12 / Android 15: Patcher fails instantly
Device: OnePlus 12 Android version: 15 Magisk version name: v28.0 Magisk version code: 28001 (D)
Trying to patch the init_boot.img (in the Download folder) from OxygenOS-CPH2581_15.0.0.204(EX01) (already installed & running) instantly aborts with nothing but
- Device platform: arm64-v8a
- Installing: 070719db (28001)
- Copying image to cache Killed ! Installation failed
Debug version adds no further info.
Same Magisk version on on another device (Nord 2, Android 13) claims to process it fine.
Please upload the image, the app log and installation log saved from magisk app
magisk_log_2024-11-15T12.07.27.log magisk_install_log_2024-11-15T12.06.04.log init_boot.zip
The bootloader is not yet unlocked.
Do you know how to use adb or terminal apps? Try extracting lib/arm64-v8a/libbusybox.so from the magisk apk, set execute permission by chmod +x, execute the file, and see if any error occurs?
OP595DL1://sdcard $ ls -al | grep libbusybox
-rw-rw---- 1 u0_a278 media_rw 1710600 2024-11-17 14:49 libbusybox.so
OP595DL1://sdcard $ chmod +x libbusybox.so
OP595DL1://sdcard $ ./libbusybox.so
/system/bin/sh: ./libbusybox.so: can't execute: Permission denied
126|OP595DL1://sdcard $ ls -al | grep libbusybox
-rw-rw---- 1 u0_a278 media_rw 1710600 2024-11-17 14:49 libbusybox.so
chmod has no effect?
with termux I at least get past chmod, but then
~/lib/arm64-v8a $ ls -al | grep libbusy
-rwxr--r--. 1 u0_a486 u0_a486 1710600 Dec 31 1979 libbusybox.so
~/lib/arm64-v8a $ ./libbusybox.so
error: "/data/data/com.termux/files/home/lib/arm64-v8a/libbusybox.so" has unexpected e_type: 2
edit: ah that's a Google Play termux limitation
edit2: But I can't install the dev's recommended F-Droid or GitHub version, or rather, after installing termux fails with "Unable to install bootstrap"
I think Magisk breaks for the same reason:
Termux processes will get killed on shell startup or even bootstrap installation second stage may fail. Disabling phantom process killer will not work and that is a separate issue. There is no known fix and affects both OxygenOS 15 And ColorOS 15. Related BBK electronics brands like Realme, etc may be affected too.
OnePlus and Realme has also recently started killing processes running under proot on older Android versions, apparently by detecting syscalls.
My fault for buying this device, apparently.
edit: I suppose somebody could try patching the A15 img on a device still running A14, but I'm very afraid that kernel alteration then would brick the A15 device.
OP595DL1://sdcard $ ls -al | grep libbusybox -rw-rw---- 1 u0_a278 media_rw 1710600 2024-11-17 14:49 libbusybox.so OP595DL1://sdcard $ chmod +x libbusybox.so OP595DL1://sdcard $ ./libbusybox.so /system/bin/sh: ./libbusybox.so: can't execute: Permission denied 126|OP595DL1://sdcard $ ls -al | grep libbusybox -rw-rw---- 1 u0_a278 media_rw 1710600 2024-11-17 14:49 libbusybox.so
chmodhas no effect?
You need to move the file into partitions other than /sdcard. If you are using adb, you can use /data/local/tmp.
Ah, I read the issue you mentioned and someone mentioned it is fixed in a recent system update. Maybe you can try applying an OTA if any?
Unfortunately, I'm already running the latest version.
Same issue here. I'm on the latest version, Android 15, on a OnePlus Pad 2, NA. Latest version incremental release is OPD2403_15.0.0.202(EX01). Magisk fails to patch the image file.
Settings > Developer Options > Allow External Commandos (or something.)
You need to move the file into partitions other than
/sdcard. If you are using adb, you can use/data/local/tmp.
... So did you try patch with file in internal storage?