- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
- [MagiskBoot] Support extracting boot image from payload.bin
- [MagiskBoot] Support cpio files containing character files
- [MagiskBoot] Support listing cpio content
- [MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation
- [Daemon] Make daemon socket a fixed path in MAGISKTMP
- [resetprop] Support printing property context
- [resetprop] Support only printing persistent properties from storage
- [resetprop] Properly support setting persistent properties bypassing property_service
- [MagiskSU] Support -g and -G options
- [MagiskSU] Support switching mount namespace to PID with -t
- [MagiskPolicy] Fix patching extended permissions
- [MagiskPolicy] Support more syntax for extended permissions
- [MagiskPolicy] Support printing out the loaded sepolicy rules
- [App] Support patching boot image from ROM zips
- [App] Properly preserve boot.img when patching Samsung firmware with init_boot.img
Unclear. To me, you get the payload.bin from roms you download, but that don’t necessarily expose boot.img, but I don’t see how there would be a way for magisk to find a payload.bin on your rom on its own, it’s just another more convenient way of getting a boot.img.