diff options
| author | matchboxbananasynergy <107055883+matchboxbananasynergy@users.noreply.github.com> | 2024-02-26 22:54:14 +0000 |
|---|---|---|
| committer | Daniel Micay <daniel.micay@grapheneos.org> | 2024-03-31 15:54:19 -0400 |
| commit | 3cc34aa040c51a51c081953a848cfb85f29ab5f8 (patch) | |
| tree | 63730bf8352a53442a0634d26eefd5a51981dad0 /static/faq.html | |
| parent | c8757edb23d19da420219018035356f3a7aad6c3 (diff) | |
add FAQ entry for bootloader locking reminder during device setup
Diffstat (limited to 'static/faq.html')
| -rw-r--r-- | static/faq.html | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/static/faq.html b/static/faq.html index a46609d0..bcc29fcb 100644 --- a/static/faq.html +++ b/static/faq.html @@ -92,6 +92,7 @@ <li><a href="#ad-blocking">How can I set up system-wide ad-blocking?</a></li> <li><a href="#ad-blocking-apps">Are ad-blocking apps supported?</a></li> <li><a href="#baseband-isolation">Is the baseband isolated?</a></li> + <li><a href="#bootloader-locking-setup">Why am I seeing a message about my bootloader not being locked when setting up the device?</a></li> </ul> </li> <li> @@ -1466,6 +1467,35 @@ is problematic and a HardMAC implementation with most complexity in the isolated firmware could be better than the status quo. An isolated driver would be ideal.</p> </article> + + <article id="bootloader-locking-setup"> + <h2><a href="#bootloader-locking-setup">Why am I seeing a message about my bootloader not being locked when setting up the device?</a></h2> + + <p>If you are seeing this warning when setting up your device after GrapheneOS + has been installed, it means that not all of the installation steps have been + completed. This can be remediated by finishing the installation process and + locking the device's bootloader.</p> + + <p>To do this, follow these steps:</p> + + <ol> + <li>Navigate to the bootloader locking section of the <a href="https://grapheneos.org/install/web">web install + (recommended)</a> or <a href="https://grapheneos.org/install/cli">CLI install</a> + guide on the device you'll be using to lock the bootloader.</li> + <li>If you are at the welcome screen on your GrapheneOS device, tap "Next".</li> + <li>On the resulting screen, tap "Reboot to bootloader".</li> + <li>Connect your GrapheneOS device to the device where you have the install page open.</li> + <li>Follow the steps on the install page to lock the bootloader.</li> + <li>Once locked, you can start setting up your GrapheneOS device, and the warning should no longer be present.</li> + </ol> + + <p>It is important to note that this is something that should be done before + placing any data onto the device, as until this step is completed, the device is + considered to be insecure. Please note that locking the bootloader wipes all + user data on the device. GrapheneOS doesn't provide any support to users running + GrapheneOS with an unlocked bootloader, as this is considered to be an + incomplete installation.</p> + </article> </section> <section id="day-to-day-use"> |