- 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
I’m assuming this is for patching an ota file. Right now I download the factory image and patch the init_boot.img from that, and flash it after I download and flash the OTA. I guess this means I don’t have to download both
Where do you download the factory image from? I can’t find it on the Motorola website, or any trusted source.
I’ve personally got a pixel, and Google makes the factory images freely available. If I remember right my old Motorola had a desktop updater app that you could install if you set the USB mode on your phone to something like “installer” or similar. I could grab OTA files from the cache on the updater.
This is for custom roms mainly. LineageOS for example gives you a payload.bin but not a boot.img.