GT_Neo第三方内核Citrus-LimeShock-V1.6.ZiP

---------------------------------------------------------------------------------- AnyKernel3 - Flashable Zip Template for Kernel Releases with Ramdisk Modifications ---------------------------------------------------------------------------------- ### by osm0sis @ xda-developers ### "AnyKernel is a template for an update.zip that can apply any kernel to any ROM, regardless of ramdisk." - Koush AnyKernel2 pushed the format further by allowing kernel developers to modify the underlying ramdisk for kernel feature support easily using a number of included command methods along with properties and variables to customize the installation experience to their kernel. AnyKernel3 adds the power of topjohnwu's magiskboot for wider format support by default, and to automatically detect and retain Magisk root by patching the new Image.*-dtb as Magisk would. _A script based on Galaxy Nexus (tuna) is included for reference. Everything to edit is self-contained in __anykernel.sh__._ ## // Properties / Variables ## ``` kernel.string=KernelName by YourName @ xda-developers do.devicecheck=1 do.modules=1 do.systemless=1 do.cleanup=1 do.cleanuponabort=0 device.name1=maguro device.name2=toro device.name3=toroplus device.name4=tuna supported.versions=6.0 - 7.1.2 supported.patchlevels=2019-07 - block=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot; is_slot_device=0; ramdisk_compression=auto; ``` __do.devicecheck=1__ specified requires at least device.name1 to be present. This should match ro.product.device, ro.build.product, ro.product.vendor.device or ro.vendor.product.device from the build.prop files for your device. There is support for as many device.name# properties as needed. You may remove any empty ones that aren't being used. __do.modules=1__ will push the .ko contents of the modules directory to the same location relative to root (/) and apply correct permissions. On A/B devices this can only be done to the active slot. __do.systemless=1__ (with __do.modules=1__) will instead push the full contents of the modules directory to create a simple "ak3-helper" Magisk module, allowing developers to effectively replace system files, including .ko files. If the current kernel is changed then the kernel helper module automatically removes itself to prevent conflicts. __do.cleanup=0__ will keep the zip from removing its working directory in /tmp/anykernel (by default) - this can be useful if trying to debug in adb shell whether the patches worked correctly. __do.cleanuponabort=0__ will keep the zip from removing its working directory in /tmp/anykernel (by default) in case of installation abort. __supported.versions=__ will match against ro.build.version.release from the current ROM's build.prop. It can be set to a list or range. As a list of one or more entries, e.g. `7.1.2` or `8.1.0, 9` it will look for exact matches, as a range, e.g. `7.1.2 - 9` it will check to make sure the current version falls within those limits. Whitespace optional, and supplied version values should be in the same number format they are in the build.prop value for that Android version. __supported.patchlevels=__ will match against ro.build.version.security_patch from the current ROM's build.prop. It can be set as a closed or open-ended range of dates in the format YYYY-MM, whitespace optional, e.g. `2019-04 - 2019-06`, `2019-04 -` or `- 2019-06` where the last two examples show setting a minimum and maximum, respectively. `block=auto` instead of a direct block filepath enables detection of the device boot partition for use with broad, device non-specific zips. Also accepts specifically `boot`, `recovery` or `vendor_boot`. `is_slot_device=1` enables detection of the suffix for the active boot partition on slot-based devices and will add this to the end of the supplied `block=` path. Also accepts `auto` for use with broad, device non-specific zips. `ramdisk_compression=auto` allows automatically repacking the ramdisk with the format detected during unpack. Changing `auto` to `gz`, `lzo`, `lzma`, `xz`, `bz2`, `lz4`, or `lz4-l` (for lz4 legacy) instead forces the repack as that format, and using `cpio` or `none` will (attempt to) force the repack as uncompressed. `customdd="<arguments>"` may be added to allow specifying additional dd parameters for devices that need to hack their kernel directly into a large partition like mmcblk0, or force use of dd for flashing. `slot_select=active|inactive` may be added to allow specifying the target slot. If omitted the default remains `active`. `no_block_display=1` may be added to disable output of the detected final used partition+slot path for zips which choose to include their own custom output instead. ## // Command Methods ## ``` ui_print "<text>" [...] abort ["<text>" [...]] contains <string> <substring> file_getprop <file> <property> set_perm <owner> <group> <mode> <file> [<file2> ...] set_perm_recursive <owner> <group> <dir_mode> <file_mode> <dir> [<dir2> ...] dump_boot split_boot unpack_ramdisk backup_file <file> restore_file <file> replace_string <file> <if search string> <original string> <replacement string> <scope> replace_section <file> <begin search string> <end search string> <replacement string> remove_section <file> <begin search string> <end search string> insert_line <file> <if search string> <before|after> <line match string> <inserted line> replace_line <file> <line replace string> <replacement line> <scope> remove_line <file> <line match string> <scope> prepend_file <file> <if search string> <patch file> insert_file <file> <if search string> <before|after> <line match string> <patch file> append_file <file> <if search string> <patch file> replace_file <file> <permissions> <patch file> patch_fstab <fstab file> <mount match name> <fs match type> block|mount|fstype|options|flags <original string> <replacement string> patch_cmdline <cmdline entry name> <replacement string> patch_prop <prop file> <prop name> <new prop value> patch_ueventd <ueventd file> <device node> <permissions> <chown> <chgrp> repack_ramdisk flash_boot flash_dtbo write_boot reset_ak [keep] setup_ak ``` __"if search string"__ is the string it looks for to decide whether it needs to add the tweak or not, so generally something to indicate the tweak already exists. __"cmdline entry name"__ behaves somewhat like this as a match check for the name of the cmdline entry to be changed/added by the _patch_cmdline_ function, followed by the full entry to replace it. __"prop name"__ also serves as a match check in _patch_prop_ for a property in the given prop file, but is only the prop name as the prop value is specified separately. Similarly, __"line match string"__ and __"line replace string"__ are the search strings that locate where the modification needs to be made for those commands, __"begin search string"__ and __"end search string"__ are both required to select the first and last lines of the script block to be replaced for _replace_section_, and __"mount match name"__ and __"fs match type"__ are both required to narrow the _patch_fstab_ command down to the correct entry. __"scope"__ may be specified as __"global"__ to force all instances of the string/line targeted by _replace_string_, _replace_line_ or _remove_line_ to be replaced/removed accordingly. Omitted or set to anything else and it will perform the default first-match action. __"before|after"__ requires you simply specify __"before"__ or __"after"__ for the placement of the inserted line, in relation to __"line match string"__. __"block|mount|fstype|options|flags"__ requires you specify which part (listed in order) of the fstab entry you want to check and alter. _dump_boot_ and _write_boot_ are the default method of unpacking/repacking, but for more granular control, or omitting ramdisk changes entirely ("OG AK" mode), these can be separated into _split_boot; unpack_ramdisk_ and _repack_ramdisk; flash_boot_ respectively. _flash_dtbo_ can be used to flash a dtbo image. It is automatica