blob: f4b88b0ac1b465edc93436e94b8926eaf97c4a13 [file] [log] [blame]
<div class='page-heading'>This device uses system-as-root in an A-only partition configuration.</div>
<hr />
<p class="text">If you intend to root your ({{ page.codename }}) device, be advised that Magisk will be installed to the <tt>recovery</tt> partition, not the usual <tt>boot</tt> partition. Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time.</p>
<p class"text">You are therefore strongly advised to first <a href="">root your device with Magisk</a> and then pre-root a TWRP image before flashing it to recovery. The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually.</p>
<p class="text">If you wish to install TWRP without rooting, there are numerous pitfalls to consider. For example, a stock device is protected by Android Verified Boot. This is implemented as a <tt>vbmeta</tt> partition that contains cryptographic digests for verifying the integrity of <tt>boot.img</tt>, <tt>recovery.img</tt> and other partitions/images. Flashing TWRP without first flashing a <tt>vbmeta</tt> image with verity disabled will render your device unable to boot.</p>
<p class="text">Please bear all of the above in mind when considering the installation methods listed below, and refer to the device's TWRP support thread on XDA for detailed information about installation and the associated hazards. Details of the firmware version(s) with which the current TWRP image's kernel is compatible can be found in the TWRP changelog for this device.</p>