Skip to content

Instantly share code, notes, and snippets.

@SayantanRC
SayantanRC / chrome-os-brunch-recover-after-failed-update.md
Last active May 24, 2021 13:46
Chrome OS - Brunch - Recover after a failed update

Chrome OS - Brunch - Recover after a failed update

In case if update fails / is not applied correctly when following https://github.com/sebanc/brunch#update-only-the-brunch-framework the following steps can be done to recover the brunch installation.

NOTE: These steps are from the developer sebanc himself.

Requirements

  1. A linux environment (installed or from live USB). Also knowledge of linux terminal and usage of dd.
  2. The latest chrome os recovery image from https://cros-updates-serving.appspot.com/.
@SayantanRC
SayantanRC / chrome-os-brunch-resize-image.md
Last active June 25, 2023 06:40
Chrome OS - Brunch - Resize image

Chrome OS - Brunch - Resize image

WARNING: This can completely destroy your Chrome OS installation. Please take a backup.
Also note, after successful resize, brunch will rebuild the rootfs on first boot.

Needed

  1. Linux environment (installed / live USB)
  2. Some knowledge on using the dd command. Optional, but good to have.
  3. The program GParted.
@SayantanRC
SayantanRC / chrome-os-force-enable-developer-mode.md
Last active October 4, 2022 00:36
Force developer mode in Chrome OS

Chrome OS - Force enable developer mode

Requirements

  • Chromium os already installed or if you are using brunch then the chrome os image should be prepared first.
  • A USB drive, bootable with Ubuntu (or any other linux distro)
    OR, a standalone Ubuntu installation
  • Some basic idea about mounting and working in terminal

Common steps

  1. Boot into Ubuntu
@SayantanRC
SayantanRC / chrome-os-crostini-error-20.md
Last active September 15, 2021 14:30
Chrome OS - Crostini fails to start with vmshell error 20

Chrome OS - Crostini fails to start with vmshell error 20

This I found out to be an sshd problem. Somehow the systemd service cros-sftp of the container was not working.
All the below steps are from crosh terminal.

Start the container from crosh

From crosh terminal (Alt+Ctrl+T):

vmc start termina
@SayantanRC
SayantanRC / chrome-os-this-setting-is-managed-by-device-owner.md
Last active March 17, 2021 05:11
Chrome OS - "This setting is managed by device owner"

Chrome OS - "This setting is managed by device owner"

This may permanently damage your Chrome OS installation, or cause problems in future. Proceed with caution and take a backup.

Sometime after updating Chrome OS, some options in settings may get locked out with the label "This setting is managed by the device owner". If you have root access, continue with the guide. If not and you are dual booting, check out Force developer mode on Chrome OS to see how to edit the shadow file to get root access.

  1. Open crosh (Alt+Ctrl+T). Type shell. A new green coloured chronos prompt appears. Type sudo su to get into red coloured root shell. Enter password if necessary. Alternately you can also open tty by Ctrl+Alt+F2, login as root and proceed.
  2. A basic search of the files with "owner" in their name can be done as below. This step is optional, but good to know. It may take a long time. You may jump to the next step without p
@SayantanRC
SayantanRC / CustomControlsConstants.kt
Last active February 22, 2021 14:53
Constants for Power Menu Controls API
class CustomControlsConstants {
companion object {
// gist url: https://gist.github.com/SayantanRC/1ae3f93147dbfd405be79acfeeafad2e
/** Input fields i.e data expected from the caller app to create the control:
* SECTION 1 to SECTION 3
*/
/** Output fields i.e data sent back to the caller app by this app: