Magisk
Magisk copied to clipboard
Magisk Init Issue on Amlogic Platforms
Google ADT-3 on Android 13 - Magisk install breaks boot
Full UART log: https://hastebin.com/share/eqefinaney.yaml
[ 5.330887@3]- magiskinit: Failed to mount preinit metadata
[ 5.330887@3]- failed with 19: No such device
[ 5.405135@1]- magiskinit: opendir .magisk/preinit failed with 2: No such file or directory
The above appears to be the operative failure.
https://download.ods.ninja/Android/.hidden/boot.img - this is the problematic stock boot image
Said Image post-patch: https://download.ods.ninja/Android/.hidden/magisk_patched-26100_ml2Js.img
Device: Google ADT-3 (ADT-3/deadpool) Android version: 13.0 - same happens on 12.0 Magisk version name: Stable Magisk version code: v26.1
@osm0sis if you have any ideas on this lmk, I have UART on the test-case.
I will say this, Magisk worked on 12, and the only change boot image side was been the this device swapped to first_stage_ramdisk in 13 (needs fstab in said Ramdisk).
Hmm, does the device have a /metadata partition?
The magiskinit stuff is way beyond me, so someone else will have to take a look.
no:
boot bootloader0 cache data env logo misc recovery rsv tee
bootloader bootloader1 cri_data dtbo frp metadata param reserved super vbmeta
Any luck with 26301?
nope, still busted - same error
no:
boot bootloader0 cache data env logo misc recovery rsv tee bootloader bootloader1 cri_data dtbo frp metadata param reserved super vbmeta
Sorry, isn't it?
You need to re-upload the log
@canyie yes, sorry, it does have one.
And as for the log, sadly I don't have a copy.
Will be a bit before I can get another as I'm moving.
But I included all references relevant to Magisk in the post itself - the only large change from 12 (where it worked) to 13 is that 13 has/requires a first stage Ramdisk & fstab on this device.
Other than that 13 kernel source and vendor are almost identical.
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files