Replacing ChromeOS and booting Breath

[RodBarnes]

The Installing to Storage section on the Wiki page is pretty clear on the process -- one just runs the identified script install-to-internal-storage. After having done that, I expect that a Ctrl-D at the "OS Verification is OFF" screen will boot Breath. Assuming that is correct, I have some questions:

1. Does the device then have to remain in developer mode? I think going back to non-developer would fail because the OS verification would not like what it finds?
2. If the device must remain in developer mode, is there a way to cause it to auto-boot the new image of Breath instead of always having to hit Ctrl-D? Maybe via the GBB flags as is done by MrChromebox's firmware_utility.sh, which allows setting the GBB flags to specify the default boot device and the delay before proceeding without a keypress (2s, 30s).

[MilkyDeveloper]

1. The device needs to remain in dev mode for however long the user wishes to boot Breath. Enabling dev mode, assuming you have a recovery USB plugged in, would wipe the system to stock.
2. I was once wondering the same thing. I've came to the hard conclusion that you have to open your chromebook and disable write protect (documented on the CR50 section of MrChromebox's website) to disable the keypress. However, this project has a "bootlock" mechanism in which the system will always try to stay awake. This causes slightly more battery drain but prevents the system from automatically shutting off. Bootlock is enabled by default.

[RodBarnes]

I read the "Bootlock" section in the docs. So, under Breath, the device never really shuts down but remains booted but in S3 unless I say "Power Off"? Is that correct? And, in the latter case, a power on would still require the Ctrl-D to boot to Breath, correct?

Since I have already disabled WP on my device, in theory, it should be possible to set the GBB flags to change the boot defaults and then it should boot to Breath without requiring a key press on my part. Not everyone can or will want to disable WP but for those who do and have, it would make the boot nicer than always having to hit Ctrl-D to boot.

Once, I am ready to install to storage, I'll give this a try and report back.

[nplawes]

Did you ever get to try this? I did it for my old ChromeBook running GalliumOS, which worked a treat...

I've already installed my OS to internal storage and would also like to be able to reboot without doing a Ctrl-D... my machine is on 24x7 used as a remote display, blanking when not in use, but automated updates etc are better when no user intervention is required :-)

I've not disabled WP yet - hopefully it's done with the debug cable rather than taking it apart.

[nplawes]

And then it dawned on me that after 30 seconds it boots into developer mode ChromeOS, which is what linux has replaced, so I don't need to make changes to make it re-bootable unattended.

Presumably there will be trouble if I hit the SPACE bar and turn OS verification on again. At that point presumably I need to recover ChromeOS and start again. From what I remember I think this can be disabled with GBB flags. Again from memory, disabling WP needs some interaction from crosh, which will also require recovering ChromeOS, so I will probably wait until I break it :-)