From ea0e3a09ef1da9f2819676025f5ecf6cb1a2738d Mon Sep 17 00:00:00 2001 From: LoveSy Date: Fri, 23 Dec 2022 23:05:48 +0800 Subject: [PATCH] Update install.md --- docs/install.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/install.md b/docs/install.md index 588c357e9..26ca2245c 100644 --- a/docs/install.md +++ b/docs/install.md @@ -22,7 +22,7 @@ The result of **Ramdisk** determines whether your device has ramdisk in the boot If you are using a Samsung device that is launched with Android 9.0 or higher, you can now jump to [its own section](#samsung-system-as-root). -If your device has boot ramdisk, get a copy of the `boot.img`.
+If your device has boot ramdisk, get a copy of the `boot.img` (or `init_boot.img` if exists).
If your device does **NOT** have boot ramdisk, get a copy of the `recovery.img`.
You should be able to extract the file you need from official firmware packages or your custom ROM zip. @@ -38,7 +38,7 @@ Quick recap, at this point, you should have known and prepared: 1. Whether your device has boot ramdisk 2. Whether your device has a separate `vbmeta` partition -3. A `boot.img` or `recovery.img` based on (1) +3. A `boot.img`, `init_boot.img` or `recovery.img` based on (1) Let's continue to [Patching Images](#patching-images).