-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OnePlus 12 / Android 15: Patcher fails instantly #8553
Comments
Please upload the image, the app log and installation log saved from magisk app |
magisk_log_2024-11-15T12.07.27.log The bootloader is not yet unlocked. |
Do you know how to use adb or terminal apps? Try extracting |
|
with termux I at least get past
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:
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. |
You need to move the file into partitions other than |
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.) |
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 butDebug version adds no further info.
Same Magisk version on on another device (Nord 2, Android 13) claims to process it fine.
The text was updated successfully, but these errors were encountered: