Android Booting Shenanigans

While we&#x27;re on the topic of rooting, only Google, Sony, Xiaomi, Asus, Motorola, OnePlus, Samsung (Exynos only, breaks eFUSE) are bootloader unlockable.<p>Of the above, only Google has what I would consider &quot;proper&quot; software support.<p>At this point, I refuse to buy anything that I can&#x27;t bootloader unlock and does not have proper software support because of planned obsolescence stemming from a lack of software updates.<p>Blacklisted for not being able to bootloader unlock: Huawei, Vivo, Samsung (Qualcomm), Nokia, Pixel (Verizon US variant).

I have zero background&#x2F;knowledge about this topic, so forgive me if it&#x27;s a stupid question; but the article is very confusing to me.<p>In the terminology section, it says<p><pre><code> initramfs: a section in Android’s boot image that the Linux kernel will use as rootfs </code></pre> And<p><pre><code> SAR: System-as-root. That is, the device uses system as rootdir instead of rootfs </code></pre> In Boot Methods section, it says something like<p><pre><code> The kernel uses initramfs as rootdir .. </code></pre> So far, it has<p>* initramfs as rootfs<p>* system as rootdir (or &quot;rootfs as rootdir&quot; if no SAR)<p>* initramfs as rootdir<p>I get that the whole point of this article is about &quot;A as B&quot; for some booting shenanigans, but this mapping relationship doesn&#x27;t make sense to me. rootfs somehow appears in both ends.<p>Also, for method A and C, it says &quot;uses initramfs as rootdir&quot; but the table lists &quot;rootfs&quot; instead of initramfs?

I love the simplicity of the site but a meta &quot;light dark&quot; color-scheme tag would go a long way.