Chrome OS is missing or damaged

[Henrik Andreasson]

I have been building Chrome for ChromeOS using these instructions for my Pixel and everything has worked fine.

Today my SDK was updated to (sdk link R38-6052.0.0) and I was able to install the corresponding test image and could start my machine.

Next, I built Chrome and tried to deploy it to the device but after seeing: 13:24:39: INFO: Starting UI... the screen went black and I was never able to restart again.

I tried to reboot => Dev screen (asks for Ctrl-D) but all that happened was a restart and back to the Recovery screen. I then tried to get out of dev mode (pressing Space) but then I got the "Chrome OS is missing or damaged" screen. I was able to download and install a stable image and could then restart my Pixel ;-)

Now I want to enter Dev mode again, but doing 

To invoke Recovery mode, you hold down the ESC and Refresh (F3) keys and press the Power button for at least 200ms (until the keyboard backlight comes on).

I get back to the "Chrome OS is missing or damaged" screen again => ;-(

Any ideas how I can enter a stable state again from which I can enable Developer mode?

[Luigi Semenzato]

The "Chrome OS is missing or damaged" warning is for users who enter that state accidentally.  Ignore what the screen says and press control-D.  We intentionally obfuscate entering dev mode.

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Richard Barnette]

On 7/15/14, 9:01 AM, Luigi Semenzato wrote:
> The "Chrome OS is missing or damaged" warning is for users who enter
> that state accidentally. Ignore what the screen says and press
> control-D. We intentionally obfuscate entering dev mode.
>

The "missing or damaged" screen only shows up the first
time you switch to dev mode. It sounds like Hendrik has
been booting in dev mode for a while, and this is the first
time he's had trouble. It also sounds like he gets the
screen even after typing ctrl-D. Hendrik, can you confirm this?


Assuming the problem persists even after typing ctrl-D, it
means that the image is corrupted. Given the scenario
describe, I think the most likely explanation is that the
test image built and installed with rootfs verification turned
on. A second, less likely explanation is that the SSD has gone
bad.

Regardless of root cause, I think the first thing to try is
to install a different build from scratch, and see what works,
and where it goes wrong.

>
> On Tue, Jul 15, 2014 at 6:29 AM, Henrik Andreasson <hen...@chromium.org
> <mailto:hen...@chromium.org>> wrote:
>
> I have been building Chrome for ChromeOS using these

> <http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/building-chromium-browser> instructions

> for my Pixel and everything has worked fine.
>
> Today my SDK was updated to (sdk link R38-6052.0.0) and I was able
> to install the corresponding test image and could start my machine.
>
> Next, I built Chrome and tried to deploy it to the device but after
> seeing: 13:24:39: INFO: Starting UI... the screen went black and I
> was never able to restart again.
>
> I tried to reboot => Dev screen (asks for Ctrl-D) but all that
> happened was a restart and back to the Recovery screen. I then tried
> to get out of dev mode (pressing Space) but then I got the "Chrome
> OS is missing or damaged" screen. I was able to download and install
> a stable image and could then restart my Pixel ;-)
>
> Now I want to enter Dev mode again, but doing
>

> /To invoke Recovery mode, you hold down the ESC and Refresh (F3)

> keys and press the Power button for at least 200ms (until the
> keyboard backlight comes on).

> /

>
> I get back to the "Chrome OS is missing or damaged" screen again => ;-(
>
> Any ideas how I can enter a stable state again from which I can
> enable Developer mode?
>
> --
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org

> <mailto:chromiu...@chromium.org>

> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>
>
> --
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>

--
--jrb

[Henrik Andreasson]

Thanks for the feedback.

Let me try tomorrow again and I can come back with more details when I have access to the device. 

It started to go wrong the first time when I built the test image and installed with rootfs verification turned on. Was that the wrong choice? The instructions does not state that I should avoid it. 

I am currently in a state where I have restored my Pixel like so: https://support.google.com/chromebook/answer/1080595?hl=en

and then I try to enter Developer mode again. This is when I get the "Chrome OS missing or damaged" screen. I guess I should try Ctrl+D in this state.

[Mike Frysinger]

On Wed, Jul 16, 2014 at 4:26 AM, Henrik Andreasson <hen...@chromium.org> wrote:

Thanks for the feedback.

Let me try tomorrow again and I can come back with more details when I have access to the device. 

It started to go wrong the first time when I built the test image and installed with rootfs verification turned on. Was that the wrong choice? The instructions does not state that I should avoid it. 

if you want to modify the rootfs, then you shouldn't turn verification on

I am currently in a state where I have restored my Pixel like so: https://support.google.com/chromebook/answer/1080595?hl=en

and then I try to enter Developer mode again. This is when I get the "Chrome OS missing or damaged" screen. I guess I should try Ctrl+D in this state.

which is why the documentation says exactly that:

http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/chromebook-pixel#TOC-Entering

-mike