Sync to master #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Delete zImage
- add flash_generic support for flashing to dynamic/logical partitions larger than stock using phhusson's lptools binary - enable full automated support for flashing custom vendor_dlkm.img (note: must NOT be sparse format; factory images are sparse, but images generated from source are not) Co-authored-by: Chris Renshaw <[email protected]>
Signed-off-by: engstk <[email protected]>
- this supports custom kernel users to continue not having to fastboot reflash vbmeta with --disable-verity and --disable-verification, now that Magisk 24303+ no longer patches avb out of the fstab on-the-fly at boot time - checks for an avb option in the fstab entry for the current partition - if found, it checks if verity or verification is disabled on the top-level vbmeta, and if so, appends a hashtree and FEC data to the partition and updates the hashtree descriptor in the vbmeta partition referenced in the avb option
Signed-off-by: engstk <[email protected]>
- default to replace and fallback to resize when not enough space in super
- both boot for kernel and init_boot for first stage ramdisk access to overlay.d will be needed - remove ramdisk and recovery_ramdisk from detection since devices which use them also use kernel partition and would need to be multi-partition setups either way
- starting with Pixel 7 series, boot_img_hdr_v4 is now even more complicated, adding 2 more new partitions (init_boot and vendor_kernel_boot) so let's attempt to keep it as simple as we can - if init_boot partition is detected split up flash files for boot (kernel), init_boot (ramdisk), and vendor_kernel_boot (dtb) - continue to support current practice of Image* and dtb in zip root by automatically creating a multi-partition AK3 zip setup from these files (ramdisk directory is for the init_boot partition since that's where Magisk and overlay.d will be) NOTE 1: anykernel.sh must still be setup for multi-parition patching - see the updated Example file for parts to uncomment NOTE 2: currently magiskboot still does not support unpack/repack of VNDRBOOT v4 multi-ramdisk format (i.e. vendor_boot v4 and vendor_kernel_boot) so if modifications are necessary in these ramdisks they will need to be prebuilt and flashed whole by including vendor_boot.img and/or vendor_kernel_boot.img in the zip root
…ence DO NOT MERGE if you have already updated your zip properly for your device
- remove whitelist to allow auto-detect for any partition based on by-name filename only - add more error catching for manually specified partition paths - restore Huawei Treble partitions to auto-detect (kernel, ramdisk and recovery_ramdisk)
- restore block=auto covering both ramdisk and boot, with ramdisk list favored to accomodate init_boot - favor mapper/by-name in flash_generic - add block/by-name over bootdevice/by-name in flash_generic to mirror block=auto/<name> path finding behavior
- tidy up flash_generic block display output to match setup_ak - add helpful flash_generic debugging stderr for mapper flashing - hide flash_boot harmless stderr from strings command in TWRP
NOTE: this currently appears to be broken in magiskboot, so continue to use boot_signer for now, but we're ready for when it works ;)
- KernelSU currently requires the Manager app be run after first rooted to dump /data/adb/ksud, and then it will process any pending modules_update.img on the next reboot - the above is problematic since some custom kernels providing KernelSU support will require a working module system to overlay .ko kernel modules needed for feature support and sometimes the ROM won't boot without these matching - work around this KernelSU behavior by dumping ksud ourselves as-needed during the AK3 helper module installation, allowing seamless initial KernelSU kernel support installation with AK3 helper module .ko support See: tiann/KernelSU#945
- they all get overlayed and must be matching compression formats
- fixes custom AVBv1 signing (see: 1dfb2c3) - fixes/improves dtb patching - fixes sepolicy patching on older devices
- avoids conflicts with any utilities that might also be part of busybox
- begin overdue core variable cleanup: bin -> BIN
- overdue core variable cleanup, part 2/x
- all working directory variables - all user set variables - add backwards compat so devs have time to update anykernel.sh - overdue core variable cleanup, part 3/x
- overdue core variable cleanup, part 4/4
osm0sis
force-pushed
the
master
branch
2 times, most recently
from
96566df to
c55d63f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.