diff --git "a/e\345\274\200\345\217\221.md" "b/e\345\274\200\345\217\221.md"
new file mode 100644
index 0000000..bd8b1b2
--- /dev/null
+++ "b/e\345\274\200\345\217\221.md"
@@ -0,0 +1,306 @@
+[中文](开发.md)
+
+# Developer Guides
+
+## BusyBox
+
+Magisk ships with a feature complete BusyBox binary (including full SELinux support). The executable is located at `/data/adb/magisk/busybox`. Magisk's BusyBox supports runtime toggle-able "ASH Standalone Shell Mode". What this standalone mode means is that when running in the `ash` shell of BusyBox, every single command will directly use the applet within BusyBox, regardless of what is set as `PATH`. For example, commands like `ls`, `rm`, `chmod` will **NOT** use what is in `PATH` (in the case of Android by default it will be `/system/bin/ls`, `/system/bin/rm`, and `/system/bin/chmod` respectively), but will instead directly call internal BusyBox applets. This makes sure that scripts always run in a predictable environment and always have the full suite of commands no matter which Android version it is running on. To force a command _not_ to use BusyBox, you have to call the executable with full paths.
+
+Every single shell script running in the context of Magisk will be executed in BusyBox's `ash` shell with standalone mode enabled. For what is relevant to 3rd party developers, this includes all boot scripts and module installation scripts.
+
+For those who want to use this "Standalone Mode" feature outside of Magisk, there are 2 ways to enable it:
+
+1. Set environment variable `ASH_STANDALONE` to `1`<br>Example: `ASH_STANDALONE=1 /data/adb/magisk/busybox sh <script>`
+2. Toggle with command-line options:<br>`/data/adb/magisk/busybox sh -o standalone <script>`
+
+To make sure all subsequent `sh` shell executed also runs in standalone mode, option 1 is the preferred method (and this is what Magisk and the Magisk app internally use) as environment variables are inherited down to child processes.
+
+## Magisk Modules
+
+A Magisk module is a folder placed in `/data/adb/modules` with the structure below:
+
+```
+/data/adb/modules
+├── .
+├── .
+|
+├── $MODID                  <--- The folder is named with the ID of the module
+│   │
+│   │      *** Module Identity ***
+│   │
+│   ├── module.prop         <--- This file stores the metadata of the module
+│   │
+│   │      *** Main Contents ***
+│   │
+│   ├── system              <--- This folder will be mounted if skip_mount does not exist
+│   │   ├── ...
+│   │   ├── ...
+│   │   └── ...
+│   │
+│   ├── zygisk              <--- This folder contains the module's Zygisk native libraries
+│   │   ├── arm64-v8a.so
+│   │   ├── armeabi-v7a.so
+│   │   ├── x86.so
+│   │   ├── x86_64.so
+│   │   └── unloaded        <--- If exists, the native libraries are incompatible
+│   │
+│   │      *** Status Flags ***
+│   │
+│   ├── skip_mount          <--- If exists, Magisk will NOT mount your system folder
+│   ├── disable             <--- If exists, the module will be disabled
+│   ├── remove              <--- If exists, the module will be removed next reboot
+│   │
+│   │      *** Optional Files ***
+│   │
+│   ├── post-fs-data.sh     <--- This script will be executed in post-fs-data
+│   ├── service.sh          <--- This script will be executed in late_start service
+|   ├── uninstall.sh        <--- This script will be executed when Magisk removes your module
+│   ├── system.prop         <--- Properties in this file will be loaded as system properties by resetprop
+│   ├── sepolicy.rule       <--- Additional custom sepolicy rules
+│   │
+│   │      *** Auto Generated, DO NOT MANUALLY CREATE OR MODIFY ***
+│   │
+│   ├── vendor              <--- A symlink to $MODID/system/vendor
+│   ├── product             <--- A symlink to $MODID/system/product
+│   ├── system_ext          <--- A symlink to $MODID/system/system_ext
+│   │
+│   │      *** Any additional files / folders are allowed ***
+│   │
+│   ├── ...
+│   └── ...
+|
+├── another_module
+│   ├── .
+│   └── .
+├── .
+├── .
+```
+
+#### module.prop
+
+This is the **strict** format of `module.prop`
+
+```
+id=<string>
+name=<string>
+version=<string>
+versionCode=<int>
+author=<string>
+description=<string>
+updateJson=<url> (optional)
+```
+
+- `id` has to match this regular expression: `^[a-zA-Z][a-zA-Z0-9._-]+$`<br>
+  ex: ✓ `a_module`, ✓ `a.module`, ✓ `module-101`, ✗ `a module`, ✗ `1_module`, ✗ `-a-module`<br>
+  This is the **unique identifier** of your module. You should not change it once published.
+- `versionCode` has to be an **integer**. This is used to compare versions
+- `updateJson` should point to a URL that downloads a JSON to provide info so the Magisk app can update the module.
+- Others that weren't mentioned above can be any **single line** string.
+- Make sure to use the `UNIX (LF)` line break type and not the `Windows (CR+LF)` or `Macintosh (CR)`.
+
+Update JSON format:
+
+```
+{
+    "version": string,
+    "versionCode": int,
+    "zipUrl": url,
+    "changelog": url
+}
+```
+
+#### Shell scripts (`*.sh`)
+
+Please read the [Boot Scripts](#boot-scripts) section to understand the difference between `post-fs-data.sh` and `service.sh`. For most module developers, `service.sh` should be good enough if you just need to run a boot script.
+
+In all scripts of your module, please use `MODDIR=${0%/*}` to get your module's base directory path; do **NOT** hardcode your module path in scripts.
+If Zygisk is enabled, the environment variable `ZYGISK_ENABLED` will be set to `1`.
+
+#### The `system` folder
+
+All files you want to replace/inject should be placed in this folder. This folder will be recursively merged into the real `/system`; that is: existing files in the real `/system` will be replaced by the one in the module's `system`, and new files in the module's `system` will be added to the real `/system`.
+
+If you place a file named `.replace` in any of the folders, instead of merging its contents, that folder will directly replace the one in the real system. This can be very handy for swapping out an entire folder.
+
+If you want to replace files in `/vendor`, `/product`, or `/system_ext`, please place them under `system/vendor`, `system/product`, and `system/system_ext` respectively. Magisk will transparently handle whether these partitions are in a separate partition or not.
+
+#### Zygisk
+
+Zygisk is a feature of Magisk that allows advanced module developers to run code directly in every Android applications' processes before they are specialized and running. For more details about the Zygisk API and building a Zygisk module, please checkout the [Zygisk Module Sample](https://github.com/topjohnwu/zygisk-module-sample) project.
+
+#### system.prop
+
+This file follows the same format as `build.prop`. Each line comprises of `[key]=[value]`.
+
+#### sepolicy.rule
+
+If your module requires some additional sepolicy patches, please add those rules into this file. Each line in this file will be treated as a policy statement. For more details about how a policy statement is formatted, please check [magiskpolicy](tools.md#magiskpolicy)'s documentation.
+
+## Magisk Module Installer
+
+A Magisk module installer is a Magisk module packaged in a zip file that can be flashed in the Magisk app or custom recoveries such as TWRP. The simplest Magisk module installer is just a Magisk module packed as a zip file, in addition to the following files:
+
+- `update-binary`: Download the latest [module_installer.sh](https://github.com/topjohnwu/Magisk/blob/master/scripts/module_installer.sh) and rename/copy that script as `update-binary`
+- `updater-script`: This file should only contain the string `#MAGISK`
+
+The module installer script will setup the environment, extract the module files from the zip file to the correct location, then finalizes the installation process, which should be good enough for most simple Magisk modules.
+
+```
+module.zip
+│
+├── META-INF
+│   └── com
+│       └── google
+│           └── android
+│               ├── update-binary      <--- The module_installer.sh you downloaded
+│               └── updater-script     <--- Should only contain the string "#MAGISK"
+│
+├── customize.sh                       <--- (Optional, more details later)
+│                                           This script will be sourced by update-binary
+├── ...
+├── ...  /* The rest of module's files */
+│
+```
+
+#### Customization
+
+If you need to customize the module installation process, optionally you can create a script in the installer named `customize.sh`. This script will be _sourced_ (not executed!) by the module installer script after all files are extracted and default permissions and secontext are applied. This is very useful if your module require additional setup based on the device ABI, or you need to set special permissions/secontext for some of your module files.
+
+If you would like to fully control and customize the installation process, declare `SKIPUNZIP=1` in `customize.sh` to skip all default installation steps. By doing so, your `customize.sh` will be responsible to install everything by itself.
+
+The `customize.sh` script runs in Magisk's BusyBox `ash` shell with "Standalone Mode" enabled. The following variables and functions are available:
+
+##### Variables
+
+- `MAGISK_VER` (string): the version string of current installed Magisk (e.g. `v20.0`)
+- `MAGISK_VER_CODE` (int): the version code of current installed Magisk (e.g. `20000`)
+- `BOOTMODE` (bool): `true` if the module is being installed in the Magisk app
+- `MODPATH` (path): the path where your module files should be installed
+- `TMPDIR` (path): a place where you can temporarily store files
+- `ZIPFILE` (path): your module's installation zip
+- `ARCH` (string): the CPU architecture of the device. Value is either `arm`, `arm64`, `x86`, or `x64`
+- `IS64BIT` (bool): `true` if `$ARCH` is either `arm64` or `x64`
+- `API` (int): the API level (Android version) of the device (e.g. `23` for Android 6.0)
+
+##### Functions
+
+```
+ui_print <msg>
+    Print <msg> to console
+    Avoid using 'echo' as it will not display in custom recovery's console
+
+abort <msg>
+    Print error message <msg> to console and terminate the installation
+    Avoid using 'exit' as it will skip the termination cleanup steps
+
+set_perm <target> <owner> <group> <permission> [context]
+    If [context] is not specified, the default is "u:object_r:system_file:s0"
+    This function is a shorthand for the following commands:
+       chown owner.group target
+       chmod permission target
+       chcon context target
+
+set_perm_recursive <directory> <owner> <group> <dirpermission> <filepermission> [context]
+    If [context] is not specified, the default is "u:object_r:system_file:s0"
+    This function is a shorthand for the following psuedo code:
+      set_perm <directory> owner group dirpermission context
+      for file in <directory>:
+        set_perm file owner group filepermission context
+      for dir in <directory>:
+        set_perm_recursive dir owner group dirpermission context
+```
+
+For convenience, you can also declare a list of folders you want to replace in the variable name `REPLACE`. The module installer script will create the `.replace` file into the folders listed in `REPLACE`. For example:
+
+```
+REPLACE="
+/system/app/YouTube
+/system/app/Bloatware
+"
+```
+
+The list above will result in the following files being created: `$MODPATH/system/app/YouTube/.replace` and `$MODPATH/system/app/Bloatware/.replace`.
+
+#### Notes
+
+- When your module is downloaded with the Magisk app, `update-binary` will be **forcefully** replaced with the latest [`module_installer.sh`](https://github.com/topjohnwu/Magisk/blob/master/scripts/module_installer.sh). **DO NOT** try to add any custom logic in `update-binary`.
+- Due to historical reasons, **DO NOT** add a file named `install.sh` in your module installer zip.
+- **DO NOT** call `exit` at the end of `customize.sh`. The module installer script has to perform some cleanups before exiting.
+
+## Boot Scripts
+
+In Magisk, you can run boot scripts in 2 different modes: **post-fs-data** and **late_start service** mode.
+
+- post-fs-data mode
+  - This stage is BLOCKING. The boot process is paused before execution is done, or 10 seconds have passed.
+  - Scripts run before any modules are mounted. This allows a module developer to dynamically adjust their modules before it gets mounted.
+  - This stage happens before Zygote is started, which pretty much means everything in Android
+  - **WARNING:** using `setprop` will deadlock the boot process! Please use `resetprop -n <prop_name> <prop_value>` instead.
+  - **Only run scripts in this mode if necessary.**
+- late_start service mode
+  - This stage is NON-BLOCKING. Your script runs in parallel with the rest of the booting process.
+  - **This is the recommended stage to run most scripts.**
+
+In Magisk, there are also 2 kinds of scripts: **general scripts** and **module scripts**.
+
+- General Scripts
+  - Placed in `/data/adb/post-fs-data.d` or `/data/adb/service.d`
+  - Only executed if the script is set as executable (`chmod +x script.sh`)
+  - Scripts in `post-fs-data.d` runs in post-fs-data mode, and scripts in `service.d` runs in late_start service mode.
+  - Modules should **NOT** add general scripts during installation
+- Module Scripts
+  - Placed in the module's own folder
+  - Only executed if the module is enabled
+  - `post-fs-data.sh` runs in post-fs-data mode, and `service.sh` runs in late_start service mode.
+
+All boot scripts will run in Magisk's BusyBox `ash` shell with "Standalone Mode" enabled.
+
+## Root Directory Overlay System
+
+Since `/` is read-only on system-as-root devices, Magisk provides an overlay system to enable developers to replace files in rootdir or add new `*.rc` scripts. This feature is designed mostly for custom kernel developers.
+
+Overlay files shall be placed in the `overlay.d` folder in boot image ramdisk, and they follow these rules:
+
+1. Each `*.rc` file (except for `init.rc`) in `overlay.d` will be read and concatenated **AFTER** `init.rc` if it does not exist in the root directory, otherwise it will **REPLACE** the existing one.
+2. Existing files can be replaced by files located at the same relative path
+3. Files that correspond to a non-existing file will be ignored
+
+To add additional files which you can refer to in your custom `*.rc` scripts, add them into `overlay.d/sbin`. The 3 rules above do not apply to anything in this folder; instead, they will be directly copied to Magisk's internal `tmpfs` directory (which used to always be `/sbin`).
+
+Starting from Android 11, the `/sbin` folder may no longer exists, and in that scenario, Magisk randomly generates a different `tmpfs` folder each boot. Every occurrence of the pattern `${MAGISKTMP}` in your `*.rc` scripts will be replaced with the Magisk `tmpfs` folder when `magiskinit` injects it into `init.rc`. On pre Android 11 devices, `${MAGISKTMP}` will simply be replaced with `/sbin`, so **NEVER** hardcode `/sbin` in the `*.rc` scripts when referencing these additional files.
+
+Here is an example of how to setup `overlay.d` with a custom `*.rc` script:
+
+```
+ramdisk
+│
+├── overlay.d
+│   ├── sbin
+│   │   ├── libfoo.ko      <--- These 2 files will be copied
+│   │   └── myscript.sh    <--- into Magisk's tmpfs directory
+│   ├── custom.rc          <--- This file will be injected into init.rc
+│   ├── res
+│   │   └── random.png     <--- This file will replace /res/random.png
+│   └── new_file           <--- This file will be ignored because
+│                               /new_file does not exist
+├── res
+│   └── random.png         <--- This file will be replaced by
+│                               /overlay.d/res/random.png
+├── ...
+├── ...  /* The rest of initramfs files */
+│
+```
+
+Here is an example of the `custom.rc`:
+
+```
+# Use ${MAGISKTMP} to refer to Magisk's tmpfs directory
+
+on early-init
+    setprop sys.example.foo bar
+    insmod ${MAGISKTMP}/libfoo.ko
+    start myservice
+
+service myservice ${MAGISKTMP}/myscript.sh
+    oneshot
+```
diff --git "a/\345\274\200\345\217\221.md" "b/\345\274\200\345\217\221.md"
new file mode 100644
index 0000000..7aa3fa3
--- /dev/null
+++ "b/\345\274\200\345\217\221.md"
@@ -0,0 +1,332 @@
+[英文](e开发.md)
+
+# 开发者指南
+
+## BusyBox
+
+Magisk 附带了一个完整的 BusyBox 二进制（包括完整的 SELinux 支持）。可执行文件位于 `/data/adb/magisk/busybox` 。Magisk 的 BusyBox 支持运行时可切换的“ASH独立外壳模式”。这种独立模式的意思是，当在 BusyBox 的 `ash` shell 中运行时，无论 `PATH` 设置为什么，每个命令都将直接使用 BusyBox 中的 applet。例如，像 `ls`、`rm`、`chmod` 这样的命令将**不使用** `PATH` 中的内容（在 Android 上，这些命令默认情况下分别为 `/system/bin/ls` 、`/system/bin/rm` 和 `/system/bin/chmod` ），而是直接调用内部 BusyBox 小程序。这确保脚本始终在可预测的环境中运行，并且无论在哪个 Android 版本上运行，都始终具有完整的命令集。要*强制命令不使用BusyBox*，必须使用完整路径调用可执行文件。
+
+在 Magisk 环境下运行的每一个 shell 脚本都将在启用独立模式（Standalone Mode）的 BusyBox 的 `ash` shell 中执行。对于与第三方开发人员相关的内容，这包括所有启动脚本和模块安装脚本。
+
+对于想在 Magisk 之外使用“独立模式”功能的开发者，有两种方法可以启用它：
+
+1. 将环境变量 `ASH_STANDALONE` 设置为 `1`\
+   示例：`ASH_STANDALONE=1 /data/adb/magisk/busybox sh <script>`
+2. 使用命令行选项切换：\
+   `/data/adb/magisk/busybox sh -o standalone <script>`
+
+为了确保所有后续执行的 `sh` shell 也以独立模式运行，选项1是首选方法（这是 Magisk 和 Magisk app 内部使用的方法），因为环境变量继承到子进程。
+
+## Magisk 模块
+
+Magisk 模块是放置在 `/data/adb/modules` 中的文件夹，结构如下：
+
+``` txt
+/data/adb/modules
+├── .
+├── .
+|
+├── $MODID                  <--- 文件夹以模块的 ID 命名
+│   │
+│   │      *** 模块 ID ***
+│   │
+│   ├── module.prop         <--- 此文件存储模块的元数据（metadata）
+│   │
+│   │      *** 主要内容 ***
+│   │
+│   ├── system              <--- 如果 skip_mount 不存在，将挂载此文件夹
+│   │   ├── ...
+│   │   ├── ...
+│   │   └── ...
+│   │
+│   ├── zygisk              <--- 此文件夹包含模块的 Zygisk native 库
+│   │   ├── arm64-v8a.so
+│   │   ├── armeabi-v7a.so
+│   │   ├── x86.so
+│   │   ├── x86_64.so
+│   │   └── unloaded        <--- 如果存在，则 native 库不兼容
+│   │
+│   │      *** 状态标志 ***
+│   │
+│   ├── skip_mount          <--- 如果存在，Magisk 将不会挂载您的 system 文件夹
+│   ├── disable             <--- 如果存在，模块将被禁用
+│   ├── remove              <--- 如果存在，模块将在下次重新启动时删除
+│   │
+│   │      *** 可选文件 ***
+│   │
+│   ├── post-fs-data.sh     <--- 此脚本将在 post-fs-data 中执行
+│   ├── service.sh          <--- 此脚本将在 late_start 服务中执行
+|   ├── uninstall.sh        <--- 当 Magisk 删除您的模块时，将执行此脚本
+│   ├── system.prop         <--- resetprop 将此文件中的属性作为系统属性加载
+│   ├── sepolicy.rule       <--- 其他自定义 sepolicy 规则
+│   │
+│   │      *** 自动生成，请勿手动创建或修改 ***
+│   │
+│   ├── vendor              <--- $MODID/system/vendor 的符号链接
+│   ├── product             <--- $MODID/system/product 的符号链接
+│   ├── system_ext          <--- $MODID/system/system_ext 的符号链接
+│   │
+│   │      *** 允许任何其他的文件/文件夹 ***
+│   │
+│   ├── ...
+│   └── ...
+|
+├── 其他模块
+│   ├── .
+│   └── .
+├── .
+├── .
+```
+
+### module.prop
+
+这是 `module.prop` **必须遵守的**格式
+
+``` properties:line-numbers
+id=<字符串> <string>
+name=<字符串> <string>
+version=<字符串> <string>
+versionCode=<整数> <int>
+author=<字符串> <string>
+description=<字符串> <string>
+updateJson=<链接> <url> (可选)
+```
+
+- `id` 必须匹配此正则表达式：`^[a-zA-Z][a-zA-Z0-9._-]+$`（译者注：也就是由字母、数字、点 `.` 、下划线 `_` 和减号 `-` 组成，且开头必须为字母）\
+  示例: `a_module` <Badge text="✓" /> ，`a.module` <Badge text="✓" /> ，`module-101` <Badge text="✓" /> ，`a module` <Badge type="danger" text="✗" /> ，`1_module` <Badge type="danger" text="✗" /> ，`-a-module` <Badge type="danger" text="✗" />\
+  这是模块的**唯一标识符**。模块发布后，您不应更改它。
+- `versionCode` 必须是**整数**。这用于对比版本，以便检查更新。
+- `updateJson` 应该指向一个 URL，该 URL 下载提供信息的 JSON，以便 Magisk app 可以更新模块。
+- 上面没有提到的其他字符串可以是任何**单行**字符串。
+- 确保使用 `UNIX (LF)` 换行类型，而不是 `Windows (CR+LF)` 或 `Macintosh (CR)`。
+
+更新的 JSON 的格式：
+
+``` json:line-numbers
+{
+    "version": string,
+    "versionCode": int,
+    "zipUrl": url,
+    "changelog": url
+}
+```
+
+### Shell 脚本 (`*.sh`)
+
+请阅读 [启动脚本](#启动脚本) 部分，了解 `post-fs-data.sh` 和 `service.sh` 之间的区别。对于大多数模块开发人员来说，如果您只需要运行引导脚本，`service.sh` 应该足够好了。
+
+在模块的所有脚本中，请使用 `MODDIR=${0%/*}` 获取模块的基本目录路径；**不要**在脚本中硬编码模块路径。\
+如果启用了Zygisk，则环境变量 `ZYGISK_ENABLED` 将设置为 `1` 。
+
+### `system` 文件夹
+
+要替换/注入的所有文件都应放在此文件夹中。此文件夹将以递归方式合并到真正的 `/system` 中，也就是说：真实 `/system` 中的现有文件将被模块 `system` 中的文件替换，模块 `system` 中的新文件将被添加到真实 `/system` 中。
+
+如果您将名为 `.replace` 的文件放在任何文件夹中，而不是合并其内容，则该文件夹将直接替换实际系统中的文件夹。这对于交换整个文件夹非常方便。
+
+如果要替换 `/vendor` 、 `/product` 或 `/system_ext` 中的文件，请分别将它们放在 `system/vendor` 、`system/product` 和 `system/system_ext` 下。Magisk 将透明地处理这些分区是否位于单独的分区中。
+
+### zygisk
+
+Zygisk 是 Magisk 的一项功能，它允许高级模块开发人员在每个 Android 应用程序的进程中直接运行代码，然后再进行专业化和运行。有关 Zygisk API 和构建 Zygisk 模块的更多详细信息，请查看 [Zygisk 模块示例](https://github.com/topjohnwu/zygisk-module-sample) 项目。
+
+### system.prop
+
+此文件遵循与 `build.prop` 相同的格式。每行由 `[key]=[value]`组成。
+
+### sepolicy.rule
+
+如果您的模块需要一些额外的 sepolicy 补丁，请将这些规则添加到此文件中。此文件中的每一行都将被视为策略语句。有关如何格式化策略语句的更多详细信息，请查看 [magiskpolicy](tools.md#magiskpolicy) 的文档。
+
+## Magisk 模块安装程序
+
+Magisk 模块安装程序是打包在 zip 文件中的 Magisk 模块，可以在 Magisk 应用程序或第三方recovery（如 TWRP）中刷入。最简单的 Magisk 模块安装程序只是一个打包为 zip 文件的 Magisk 模块，此外还有以下文件：
+
+- `update-binary`：下载最新的 [module_installer.sh](https://github.com/topjohnwu/Magisk/blob/master/scripts/module_installer.sh) 并将该脚本重命名或复制为 `update-binary`
+- `updater-script`：这个文件应该只包含字符串 “`#MAGISK`”
+
+模块安装程序脚本将会设置环境，将模块文件从 zip 文件提取到正确的位置，然后完成安装过程，这对于大多数简单的 Magisk 模块来说应该足够好了。
+
+``` txt
+模块module.zip
+│
+├── META-INF
+│   └── com
+│       └── google
+│           └── android
+│               ├── update-binary      <--- 您下载 module_installer.sh
+│               └── updater-script     <--- 应只包含字符串“#MAGISK”
+│
+├── customize.sh                       <--- （可选，稍后将详细介绍）
+│                                           此脚本将来源于 update-binary
+├── ...
+├── ...  /* 模块的其余文件 */
+│
+```
+
+### 自定义
+
+如果需要自定义模块安装过程，可以选择在安装程序中创建名为 `customize.sh` 的脚本。在提取所有文件并设置默认权限和 secontext 后，该脚本将由 update-binary 脚本*提供*（未执行！）。如果您的模块需要基于设备 ABI 进行其他设置，或者您需要为某些模块文件设置特殊权限/secontext，这将非常有用。
+
+如果要完全控制和自定义安装过程，请在 `customize.sh` 中声明 `SKIPUNZIP=1` 以跳过所有默认安装步骤。这样，您的 `customize.sh` 将负责自行安装所有内容。
+
+`customize.sh` 脚本在 Magisk 的 BusyBox `ash` shell 中运行，并启用了“独立模式”。以下变量和函数可用：
+
+#### 变量
+
+- `MAGISK_VER` (string): 当前安装的 Magisk 的版本字符串（例如 `v20.0` ）
+- `MAGISK_VER_CODE` (int): 当前安装的Magisk的版本代码（例如 `20000` ）
+- `BOOTMODE` (bool): 如果模块在 Magisk app 中安装，则为 `true`
+- `MODPATH` (path): 模块文件应安装的路径
+- `TMPDIR` (path): 可以临时存储文件的地方
+- `ZIPFILE` (path): your module's installation zip 模块的压缩文件
+- `ARCH` (string): 设备的 CPU 架构。值为 `arm` 、`arm64` 、`x86` 或 `x64`
+- `IS64BIT` (bool): 如果 `$ARCH` 是 `arm64` 或 `x64` ，则为 `true`
+- `API` (int): 设备的 API 级别（安卓版本）（例如，Android 6.0 的 `23` ）
+
+::: tip 提示
+您可以在 [这里](https://source.android.google.cn/docs/setup/about/build-numbers#platform-code-names-versions-api-levels-and-ndk-releases) 找到所有 Android 版本对应的 API 级别
+:::
+
+#### 函数
+
+``` bash
+ui_print <msg>
+    打印 <msg> 到控制台
+    请避免使用“echo”，因为它不会显示在第三方 recovery 的控制台中
+
+abort <msg>
+    打印错误消息 <msg> 到控制台并终止安装
+    请避免使用“exit”，因为它会跳过终止清理步骤
+
+set_perm <target> <owner> <group> <permission> [context]
+    如果未指定 [context]，则默认值为“u:object_r:system_file:s0”
+    此函数是以下命令的简写：
+       chown owner.group target
+       chmod permission target
+       chcon context target
+
+set_perm_recursive <directory> <owner> <group> <dirpermission> <filepermission> [context]
+    如果未指定 [context]，则默认值为“u:object_r:system_file:s0”
+    此函数是以下psuedo代码的简写：
+      set_perm <directory> owner group dirpermission context
+      对于 <directory> 内的文件：
+        set_perm file owner group filepermission context
+      对于 <directory> 内的文件夹：
+        set_perm_recursive dir owner group dirpermission context
+```
+
+为方便起见，您还可以在变量名称 `REPLACE` 中声明要替换的文件夹列表。模块安装程序脚本会将 `.replace` 文件创建到 `REPLACE` 中列出的文件夹中。例如：
+
+``` sh
+REPLACE="
+/system/app/YouTube
+/system/app/Bloatware
+"
+```
+
+上面的列表将对应创建以下文件：`$MODPATH/system/app/YouTube/.replace` 和 `$MODPATH/system/app/Bloatware/.replace` 。
+
+### 注意
+
+- 使用 Magisk 应用程序下载模块时，`update-binary` 将**强制替换为最新的 [`module_installer.sh`](https://github.com/topjohnwu/Magisk/blob/master/scripts/module_installer.sh)** 。 **不要尝试在 `update-binary` 中添加任何自定义逻辑**。
+- 由于历史原因，**请勿在模块 zip 中添加名为 `install.sh` 的文件**。
+- **不要在 `customize.sh` 末尾调用 `exit`** 。模块安装程序脚本必须在退出之前执行一些清理。
+
+## 启动脚本
+
+在Magisk中，您可以以两种不同的模式运行启动脚本：**post-fs-data** 和 **late_start service** 模式。
+
+- post-fs-data 模式
+  - 此阶段会阻塞。启动过程在执行完成，或过 10 秒前暂停。
+  - 脚本在装入任何模块之前运行。这允许模块开发人员在安装模块之前动态调整其模块。
+  - 这个阶段发生在 Zygote 启动之前，这几乎意味着是 Android 的一切
+  - **警告**：使用 `setprop` 将导致启动过程死锁！请改用 `resetprop -n <prop_name> <prop_value>` 。
+  - **仅在必要时在此模式下运行脚本**。
+- late_start service 模式
+  - 此阶段为非阻塞。脚本与引导过程的其余部分并行运行。
+  - **建议大多数脚本在此阶段运行**
+
+在 Magisk 中，还有 2 种脚本：**通用脚本**和**模块脚本**。
+
+- 通用脚本
+  - 放置在 `/data/adb/post-fs-data.d` 或 `/data/adb/service.d` 中
+  - 仅当脚本设置为可执行文件时才执行（`chmod +x script.sh`）
+  - `post-fs-data.d` 中的脚本以 post-fs-data 模式运行，`service.d` 的脚本以 late_start service 模式运行。
+  - 模块**不应在安装过程中添加常规脚本**
+- 模块脚本
+  - 放置在模块自己的文件夹中
+  - 仅在启用模块时执行
+  - `post-fs-data.sh` 以 post-fs-data 模式运行，而 `service.sh` 以 late_start service 模式运行。
+
+所有启动脚本都将在 Magisk 的 BusyBox `ash` shell 中运行，并启用“独立模式”。
+
+## 根目录覆盖系统
+
+由于 `/` 在 system-as-root 设备上是只读的，因此 Magisk 提供了一个覆盖系统，使开发者能够替换根目录中的文件或添加新的 `*.rc` 脚本。此功能主要为第三方内核开发者设计。
+
+覆盖文件应放在 boot 映像 ramdisk 的 `overlay.d` 文件夹中，并遵循以下规则：
+
+1. 对于 `overlay.d` 中的每个 `*.rc` 文件（ `init.rc` 除外），**在 `init.rc` 之后**，如果在根目录中不存在，将读取并连接，否则将**替换现有文件**。
+2. 现有文件可以替换为位于相同相对路径的文件
+3. 与不存在的文件对应的文件将被忽略
+
+要添加您在自定义 `*.rc` 脚本中引用的其他文件，请将它们添加到 `overlay.d/sbin` 中。上面的 3 条规则不适用于此文件夹中的任何内容；相反，它们将直接复制到Magisk 的内部 `tmpfs` 目录（以前是 `/sbin` ）。
+
+从 Android 11 开始，`/sbin` 文件夹可能不再存在，在这种情况下，Magisk 会在每次启动时随机生成一个不同的 `tmpfs` 文件夹。当 `magiskinit` 将其注入 `init.rc` 时，`*.rc` 脚本中的 `${MAGISKTMP}` 都将替换为 Magisk  `tmpfs` 文件夹。在 Android 11 之前的设备上，`${MAGISKTMP}` 将简单地替换为 `/sbin` 。因此在引用这些附加文件时，`*.rc` 脚本中**永远不要硬编码 “`/sbin`”**。
+
+下面是如何使用自定义 `*.rc` 脚本设置 `overlay.d` 的示例：
+
+``` txt
+ramdisk
+│
+├── overlay.d
+│   ├── sbin
+│   │   ├── libfoo.ko      <--- 这两个文件将被复制到 Magisk 的
+│   │   └── myscript.sh    <--- 的 tmpfs 目录中
+│   ├── custom.rc          <--- 此文件将被注入到 init.rc 中
+│   ├── res
+│   │   └── random.png     <--- 此文件将替换 /res/random.png
+│   └── new_file           <--- 此文件将被忽略，因为 /new_file 不存在
+├── res
+│   └── random.png         <--- 此文件将被 /overlay.d/res/random.png
+|                               替换
+├── ...
+├── ...  /* 其余的 initramfs 文件 */
+│
+```
+
+这是 `custom.rc` 的示例：
+
+::: code-group
+
+``` sh:line-numbers [中文汉化]
+# 使用 ${MAGISKTMP} 引用 Magisk 的 tmpfs 目录
+
+on early-init
+    setprop sys.example.foo bar
+    insmod ${MAGISKTMP}/libfoo.ko
+    start myservice
+
+service myservice ${MAGISKTMP}/myscript.sh
+    oneshot
+```
+
+``` sh:line-numbers [英文原版]
+# Use ${MAGISKTMP} to refer to Magisk's tmpfs directory
+
+on early-init
+    setprop sys.example.foo bar
+    insmod ${MAGISKTMP}/libfoo.ko
+    start myservice
+
+service myservice ${MAGISKTMP}/myscript.sh
+    oneshot
+```
+
+:::
+
+## 参考链接
+
+- [Magisk Developer Guides](https://topjohnwu.github.io/Magisk/guides.html)（官方）
+- [Magisk 开发者指南](https://e7kmbb.github.io/Magisk/guides.html)