can't boot from USB or enter dev mode

[Steve Kobes]

I was able to deploy a build onto my Pixel a few weeks ago with these instructions but something has stopped working since then.  At the "OS verification is OFF" screen, if I press Ctrl-D, the logo appears briefly, but then it takes me back to the "OS verification is OFF" screen.  If I press Ctrl-D a second time the whole screen goes black forever.

I tried to reinstall the test image by flashing https://storage.cloud.google.com/chromeos-image-archive/link-release/R42-6750.0.0/chromiumos_test_image.tar.xz onto a usb drive, but I'm unable to boot from it - when I hit Ctrl-U it just beeps twice.

After seeing the other recent thread about booting from usb, I also disabled automount on my workstation, with great difficulty (actually I killed /usr/lib/udisks2/udisksd and renamed it to prevent it from starting again).  But this didn't solve the issue.

So at this point I'm a bit stuck.  Any suggestions?

Thanks,

Steve

[Yuly Novikov]

Try recovery.

If recovery in dev mode doesn't work, try turning dev mode off, then recovery.

--
--
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

[Steve Kobes]

Can you clarify?  Recovery is the screen you get from holding Esc + Refresh + Power, that says "Chrome OS is missing or damaged"?  What would I do at this screen?  Neither Ctrl-D nor Ctrl-U seems to have any effect here, but after a while it says "The device you inserted does not contain Chrome OS".

[Mike Frysinger]

i wonder if you're running into:

http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/workaround-for-battery-discharge-in-dev-mode

-mike

On Wed, Feb 4, 2015 at 5:04 PM, Steve Kobes <sko...@chromium.org> wrote:

--

[Steve Kobes]

Interesting, yes that's possible since it has not been plugged in for 2-3 weeks.

Sounds like "recovery" is a process as well as a mode. :)  If I don't care about wiping the disk, would I be able to just follow https://support.google.com/chromebook/answer/6002417 to get a clean slate, and then go back into dev mode following http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/chromebook-pixel ?

[Richard Barnette]

On 2/4/15 2:35 PM, Steve Kobes wrote:
> Interesting, yes that's possible since it has not been plugged in for
> 2-3 weeks.
>
> Sounds like "recovery" is a process as well as a mode. :) If I don't

Yeah, "recovery" is a process, a mode, a kind of bootable image, a
separate part of the firmware, and probably a few other things, too.

> care about wiping the disk, would I be able to just follow
> https://support.google.com/chromebook/answer/6002417 to get a clean
> slate, and then go back into dev mode following
> http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/chromebook-pixel
> ?
>

Yes, the recovery process is expected to recover any hardware
that's functioning properly, even if it's currently or
previously in dev mode. Given what you're trying to do, you'll
find it more convenient to recover in dev mode, that'll spare
you the time it takes to through the dev mode conversion process.

> On Wed, Feb 4, 2015 at 2:22 PM, Mike Frysinger <vap...@chromium.org
> <mailto:vap...@chromium.org>> wrote:
>
> i wonder if you're running into:
> http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/workaround-for-battery-discharge-in-dev-mode
> -mike
>
> On Wed, Feb 4, 2015 at 5:04 PM, Steve Kobes <sko...@chromium.org
> <mailto:sko...@chromium.org>> wrote:
>
> I was able to deploy a build onto my Pixel a few weeks ago with
> these instructions

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

> but something has stopped working since then. At the "OS
> verification is OFF" screen, if I press Ctrl-D, the logo appears
> briefly, but then it takes me back to the "OS verification is
> OFF" screen. If I press Ctrl-D a second time the whole screen
> goes black forever.
>
> I tried to reinstall the test image by flashing
> https://storage.cloud.google.com/chromeos-image-archive/link-release/R42-6750.0.0/chromiumos_test_image.tar.xz
> onto a usb drive, but I'm unable to boot from it - when I hit
> Ctrl-U it just beeps twice.
>
> After seeing the other recent thread about booting from usb, I
> also disabled automount on my workstation, with great difficulty
> (actually I killed /usr/lib/udisks2/udisksd and renamed it to
> prevent it from starting again). But this didn't solve the issue.
>
> So at this point I'm a bit stuck. Any suggestions?
>
> Thanks,
> Steve
>
> --
> --
> 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

[Steve Kobes]

Thanks everyone, I got it working now.

I used the recovery tool to recover the device, after which it was still in dev mode, but booted up after hitting Ctrl-D.  I was then able to get a root shell and re-enable booting from USB (or maybe it was already enabled, I'm not sure).  Then I re-flashed the test image to the USB stick and Ctrl-U worked.

Oh another thing I learned the hard way: when you boot from USB, do NOT click "Enable debugging features", even though debugging features sounds like a cool thing to enable.  It will fail and then chromeos-install will fail.

        chromiu...@chromium.org <mailto:chromium-os-dev@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

[Chris Masone]

+David Pursell Is enabling debug features expected to work when booted from USB?

[Mike Frysinger]

On Wed, Feb 4, 2015 at 6:27 PM, Steve Kobes <sko...@chromium.org> wrote:

Oh another thing I learned the hard way: when you boot from USB, do NOT click "Enable debugging features", even though debugging features sounds like a cool thing to enable.  It will fail and then chromeos-install will fail.

[ +dpursell ]

that is not the intention :)

-mike

[Steve Kobes]

Hmm, I forgot the exact error but it was something like "post install failed" and then it started doing some kind of hardware check.

[David]

Shoot sorry, they aren't expected to work from USB so we should definitely not make them available in that case. I'll file a bug report.