re-add note about updating stock as best practice
This commit is contained in:
parent
66132efc9f
commit
1c29145c51
@ -162,6 +162,11 @@
|
|||||||
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a
|
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a
|
||||||
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id
|
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id
|
||||||
and the hardware is the same.</p>
|
and the hardware is the same.</p>
|
||||||
|
|
||||||
|
<p>It's best practice to update the device before installing GrapheneOS to have
|
||||||
|
the latest firmware for connecting the phone to the computer and performing the
|
||||||
|
early flashing process. Either way, GrapheneOS flashes the latest firmware early
|
||||||
|
in the installation process.</p>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section id="enabling-oem-unlocking">
|
<section id="enabling-oem-unlocking">
|
||||||
|
@ -155,6 +155,11 @@
|
|||||||
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a
|
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a
|
||||||
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id
|
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id
|
||||||
and the hardware is the same.</p>
|
and the hardware is the same.</p>
|
||||||
|
|
||||||
|
<p>It's best practice to update the device before installing GrapheneOS to have
|
||||||
|
the latest firmware for connecting the phone to the computer and performing the
|
||||||
|
early flashing process. Either way, GrapheneOS flashes the latest firmware early
|
||||||
|
in the installation process.</p>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section id="enabling-oem-unlocking">
|
<section id="enabling-oem-unlocking">
|
||||||
|
Loading…
x
Reference in New Issue
Block a user