From 47d18bb896f4c9e273aa502936ba498607876509 Mon Sep 17 00:00:00 2001 From: topjohnwu Date: Sat, 4 Apr 2020 01:48:28 -0700 Subject: [PATCH] Fix typo of boot methods --- docs/boot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/boot.md b/docs/boot.md index ae41fb88a..4701e876d 100644 --- a/docs/boot.md +++ b/docs/boot.md @@ -42,7 +42,7 @@ Method | Initial rootdir | Final rootdir From documents online, Google's definition of SAR only considers how the kernel boots the device (**Initial rootdir** in the table above), meaning that only devices using **Method B** is *officially* considered an SAR device from Google's standpoint. -However for Magisk, the real difference lies in what the device ends up using when fully booted (**Final rootdir** in the table above), meaning that **as far as Magisk's concern, both Method 2 and 3 is a form of SAR**, but just implemented differently. Every instance of SAR later mentioned in this document will refer to **Magisk's definition** unless specifically says otherwise. +However for Magisk, the real difference lies in what the device ends up using when fully booted (**Final rootdir** in the table above), meaning that **as far as Magisk's concern, both Method B and C is a form of SAR**, but just implemented differently. Every instance of SAR later mentioned in this document will refer to **Magisk's definition** unless specifically says otherwise. The criteria for Method C is a little complicated, in layman's words: either your device is modern enough to launch with Android 10+, or you are running an Android 10+ custom ROM on a device that was using Method A.