Add login and filesystem tips to firmware instructions #229
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I followed the instructions to flash an Acer Chromebook 14 CB3-431, and I encountered a few errors I need to work around. This PR includes those extra steps. They are: - Having to login into VT-2 after switching to it - Double-checking the URL of the script when executing it (there is a typosquatter on mrchromebook.tech btw) - Moving to a working directory in a writeable partition if necessary
| @@ -16,7 +16,9 @@ To convert your machine from Google's firmware and ChromeOS to Coreboot and AltO | |||
| 1. [Enable developer mode](developer-mode.md). | |||
| 2. [Disable write protect](write-protect.md) (If flashing UEFI). | |||
| 3. Run [MrChromebox's firmware utility script](https://mrchromebox.tech/#fwscript) within VT-2 (`ctrl` + `alt` + `f2` (right arrow)). | |||
| - Type `cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh` and press Enter. | |||
| - If you don't see a command prompt, but a login prompt in the style: `home login:`, type-in "root" | |||
| - Type `cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh` and press Enter. Make sure to use `mrchromebox.tech` as domain, with **box** before the dot. | |||
There was a problem hiding this comment.
You are supposed to log in as chronos
| - Type `cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh` and press Enter. | ||
| - If you don't see a command prompt, but a login prompt in the style: `home login:`, type-in "root" | ||
| - Type `cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh` and press Enter. Make sure to use `mrchromebox.tech` as domain, with **box** before the dot. | ||
| - If the command fails with `Read-only file system`, and you are sure that you followed the [write protect steps](write-protect.md), you must change your working directory. Use `lsblk` to list all mounted file systems and find one with write permission. Then, replace the `cd` in the commad with `cd XXX`, where `XXX` is the path to the writeable file system. |
There was a problem hiding this comment.
Logging in as chronos avoids this since ~ is writeable and executable. Firmware write protection has nothing to do with chromeos' rootfs being read-only. This is overcomplicating the process for no good reason.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I followed the instructions to flash an Acer Chromebook 14 CB3-431, and I encountered a few errors I had to work around. This PR includes those extra steps. They are:
I edge with conditionals, because it's likely the errors are limited to the specific device I flashed.