Commit 61dafbe0 authored by topjohnwu's avatar topjohnwu

Fix LV for Boot Method C

parent 474325da
...@@ -35,7 +35,7 @@ Method | Initial rootdir | Final rootdir ...@@ -35,7 +35,7 @@ Method | Initial rootdir | Final rootdir
- Maybe some `(LV < 29)` Android Go devices? - Maybe some `(LV < 29)` Android Go devices?
- **Method C - 2SI ramdisk SAR**: This method was first seen on Pixel 3 Android 10 developer preview. The kernel uses `initramfs` as rootdir and exec `/init` in `rootfs`. This `init` is responsible to mount the `system` partition and use it as the new rootdir, then finally exec `/system/bin/init` to boot. - **Method C - 2SI ramdisk SAR**: This method was first seen on Pixel 3 Android 10 developer preview. The kernel uses `initramfs` as rootdir and exec `/init` in `rootfs`. This `init` is responsible to mount the `system` partition and use it as the new rootdir, then finally exec `/system/bin/init` to boot.
- Devices with `(LV >= 29)` - Devices with `(LV >= 29)`
- Devices with `(LV < 29, RV >= 29)`, excluding exceptions that were using Method B - Devices with `(LV < 28, RV >= 29)`, excluding exceptions that were using Method B
- Google: Pixel 3 and 3a with `(RV >= 29)` - Google: Pixel 3 and 3a with `(RV >= 29)`
### Discussion ### Discussion
...@@ -81,4 +81,4 @@ These types are ordered chronologically by the time they were first available. ...@@ -81,4 +81,4 @@ These types are ordered chronologically by the time they were first available.
Further details on Type III devices: Magisk is always installed in the ramdisk of a boot image. For all other device types, because their `boot` partition have ramdisk included, Magisk can be easily installed by patching boot image through Magisk Manager or flash zip in custom recovery. However for Type III devices, they are **limited to install Magisk into the `recovery` partition**. Magisk will not function when booted normally; instead Type III device owners have to always reboot to recovery to maintain Magisk access. Further details on Type III devices: Magisk is always installed in the ramdisk of a boot image. For all other device types, because their `boot` partition have ramdisk included, Magisk can be easily installed by patching boot image through Magisk Manager or flash zip in custom recovery. However for Type III devices, they are **limited to install Magisk into the `recovery` partition**. Magisk will not function when booted normally; instead Type III device owners have to always reboot to recovery to maintain Magisk access.
Some Type III devices' bootloader will still accept and provide `initramfs` manually added to `boot` image to the kernel (e.g. some Xiaomi phones), but many device don't (e.g. Samsung S10, Note 10). It solely depends on how the OEM implements its bootloader. Some Type III devices' bootloader will still accept and provide `initramfs` manually added to `boot` image to the kernel (e.g. some Xiaomi phones), but many device don't (e.g. Samsung S10, Note 10). It solely depends on how the OEM implements its bootloader.
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment