Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Potential Errors Section to Updating Firmware #187

Closed
wants to merge 1 commit into from
+18 −3
Closed

Add Potential Errors Section to Updating Firmware #187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Loading status checks…
Add Potential Errors Section to Updating Firmware
@death7654
death7654 committed Jul 10, 2024
commit 7cd568393562abfc8b899aa393ecb78626f41e2e
21 changes: 18 additions & 3 deletions src/docs/firmware/updating-firmware.md
View file
Original file line number Diff line number Diff line change
@@ -5,13 +5,28 @@
:::

::: tip
curl is not installed by default for Ubuntu / Ubuntu distros. To install it, run: `sudo apt update && sudo apt install -y curl`
curl is not installed by default for Ubuntu or Ubuntu-based distros. To install it, run: `sudo apt update && sudo apt install -y curl`
:::

1. Run [MrChromebox's Firmware Utility Script](https://mrchromebox.tech/#fwscript).
* In case you forgot, type `cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh` and press Enter.
- In case you forgot, type `cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh` and press Enter.
2. Choose option 1: `Install/Update UEFI (Full ROM) Firmware`, and reboot if successful.

::: danger
**Do not reboot if flash was not successful**
:::

### Potential Errors (Before Flashing)

Check failure on line 19 in src/docs/firmware/updating-firmware.md

GitHub Actions / markdownlint-cli

Heading levels should only increment by one level at a time 

src/docs/firmware/updating-firmware.md:19 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h2; Actual: h3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md001.md

If you get any of the errors found below please try some of these fixes

1. `/dev/mem mmap failed: Operation not permitted
FAILED!
FATAL ERROR!`
- If you get this error in a Full Linux Install **AND** is using GRUB follow the steps below
1. `sudo nano /etc/default/grub` (You can use any text editor)
2. add `iomem=relaxed` to `GRUB_CMDLINE_LINUX` (Most likely at the top of the config)
3. `grub-mkconfig -o /boot/grub/grub.cfg`
4. Reboot and rerun the firmware-utility script
- If you are not using GRUB, please refer to (Arch Wiki)[wiki.archlinux.org/title/Kernel_parameters], for instructions on how to add `iomem=relaxed` to your respective kernel parameter
- If you get this error in a Live Linux ISO, please reflash with another Distro

Unchanged files with check annotations Beta

View file
src/docs/debugging/index.md
3. Upload this file if you need help with troubleshooting.
* Remember to remove WiFi information from dmesg to protect your privacy.

Check failure on line 76 in src/docs/debugging/index.md

GitHub Actions / markdownlint-cli

Ordered list item prefix 

src/docs/debugging/index.md:76:1 MD029/ol-prefix Ordered list item prefix [Expected: 1; Actual: 2; Style: 1/2/3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md029.md
## flashrom

Check failure on line 78 in src/docs/debugging/index.md

GitHub Actions / markdownlint-cli

Ordered list item prefix 

src/docs/debugging/index.md:78:1 MD029/ol-prefix Ordered list item prefix [Expected: 2; Actual: 3; Style: 1/2/3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md029.md
Flashrom is used to read and write from the SPI flash
### Read flash:
View file
src/docs/exiting-developer-mode.md
Backup anything if you have to.
:::
### Reset GBB Flags

Check failure on line 8 in src/docs/exiting-developer-mode.md

GitHub Actions / markdownlint-cli

Heading levels should only increment by one level at a time 

src/docs/exiting-developer-mode.md:8 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h2; Actual: h3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md001.md
If you get this error "WARNING: TONORM prohibited by GBB_FORCE_DEV_SWITCH_ON" or find the "Return to secure mode" button missing, you need to reset your gbb flags.
1. Boot chromeOS.
6. Your done.
### Exiting Developer Mode

Check failure on line 27 in src/docs/exiting-developer-mode.md

GitHub Actions / markdownlint-cli

Multiple headings with the same content 

src/docs/exiting-developer-mode.md:27 MD024/no-duplicate-heading Multiple headings with the same content [Context: "### Exiting Developer Mode"] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md024.md
1. Boot your system to the "You are in Developer Mode" or "OS Verification is OFF" screen.
View file
src/docs/firmware/battery.md
Screws may be underneath the rubber feet that keep the Chromebook from sliding.
:::
3. Gently pry the back off the Chromebook. If you do not have the proper tools a dull knife would be helpful.

Check failure on line 20 in src/docs/firmware/battery.md

GitHub Actions / markdownlint-cli

Ordered list item prefix 

src/docs/firmware/battery.md:20:1 MD029/ol-prefix Ordered list item prefix [Expected: 1; Actual: 3; Style: 1/2/3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md029.md
* On some Chromebooks, the keyboard needs to be removed instead of the back. Be careful as there's a ribbon wire underneath that needs disconnecting first.
4. Unplug the battery connector. You do not need to take the entire battery out of the Chromebook.

Check failure on line 22 in src/docs/firmware/battery.md

GitHub Actions / markdownlint-cli

Ordered list item prefix 

src/docs/firmware/battery.md:22:1 MD029/ol-prefix Ordered list item prefix [Expected: 2; Actual: 4; Style: 1/2/3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md029.md
## Step 2: Boot using AC power, and flash.
There is a 15V USB-C PD requirement for booting without the battery.
:::
2. Boot the chromebook up

Check failure on line 32 in src/docs/firmware/battery.md

GitHub Actions / markdownlint-cli

Ordered list item prefix 

src/docs/firmware/battery.md:32:1 MD029/ol-prefix Ordered list item prefix [Expected: 1; Actual: 2; Style: 1/2/3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md029.md
* If you removed the keyboard, make sure to reattach it for this step.
3. Continue to [Flashing Firmware](flashing-firmware.md)

Check failure on line 34 in src/docs/firmware/battery.md

GitHub Actions / markdownlint-cli

Ordered list item prefix 

src/docs/firmware/battery.md:34:1 MD029/ol-prefix Ordered list item prefix [Expected: 2; Actual: 3; Style: 1/2/3] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md029.md
View file
src/docs/firmware/recovery-mode.md
- Some devices may need to hold down the `Fullscreen` button (four corners icon) instead of the `Refresh` button.
<img src="/recovery/recovery-keyboard-hint.png" width=500>

Check failure on line 30 in src/docs/firmware/recovery-mode.md

GitHub Actions / markdownlint-cli

Images should have alternate text (alt text) 

src/docs/firmware/recovery-mode.md:30:1 MD045/no-alt-text Images should have alternate text (alt text) https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md045.md
### Chromeboxes
Find the recovery button hole. A reference of what to look for is below.
<img src="/recovery/recovery-chromebox-hint.png">

Check failure on line 36 in src/docs/firmware/recovery-mode.md

GitHub Actions / markdownlint-cli

Images should have alternate text (alt text) 

src/docs/firmware/recovery-mode.md:36:1 MD045/no-alt-text Images should have alternate text (alt text) https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md045.md
When you do, use something like a paper clip to hold the button down, then turn on the device. This should bring your system into recovery mode.
You can stop holding down the button at this point.