Can't boot developer mode on Samsung Series 5?

[Justin]

Not sure if this is the right forum, I apologize if it's not.

I was planning to poke around on my new Chromebook, and when I boot
with the developer switch on I always get the "Chrome OS is missing or
damaged" screen. I tried creating a recovery USB stick, and while
booting that (with the dev switch still on) it said it was setting the
system up for devel mode, but when I reboot I still get the "missing
or damaged" screen. Haven't found any references to this - found
several sites saying essentially "put the switch on and reboot"

It's image chromeos_0.12.433.114_x86

Has devel mode been effectively disabled on the new Chromebooks?

[Sonny Rao]

See this:
http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/samsung-series-5-chromebook

but basically you need to hit control-D or wait 30 seconds at that point.

Sonny

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

[Steve Pirk]

Guys, they have made it easier to dual boot than on the Cr-48. Holy Open System Batman! lol

Thanks for the link sonnyrao - I buzzed the dev mode page. I think Google just sold some more Chromebooks ;-]

-- steve

[Justin Osborn]

Ahh, thanks Sonny, I'd seen that page but missed that critical bit.

[adrian.d...@gmail.com]

I tried waiting and hitting control D and it's still stuck on"Chrome
OS is missing or damaged" screen...

thanks

[Sonny Rao]

If you flip the dev switch back to normal, does the screen go away or persist?

[adrian.d...@gmail.com]

The screen goes away and the laptop functions normally.

thanks

On Jul 1, 8:59 am, Sonny Rao <sonny...@chromium.org> wrote:
> If you flip the dev switch back to normal, does the screen go away or persist?
>
> On Thu, Jun 30, 2011 at 6:36 PM, ad...@berkeley.edu
>
>
>
>
>
>
>
> <adrian.druzgal...@gmail.com> wrote:
> > I tried waiting and hitting control D and it's still stuck on"Chrome
> > OS is missing or damaged" screen...
>
> > thanks
>
> > On Jun 25, 5:06 am, Justin Osborn <jdosb...@gmail.com> wrote:
> >> Ahh, thanks Sonny, I'd seen that page but missed that critical bit.
>
> > --

> > Chromium OS discuss mailing list: chromium-os-disc...@chromium.org

[Sonny Rao]

This is strange, it sounds like you're actually seeing the recovery
screen and not the normal "we're in dev mode" screen. Did dev mode
ever work correctly? If so, did you ever run the
"chromeos-firmwareinstall --mode=todev" command to enable developer
mode firmware?
Could you also do one more thing and switch to developer mode, and
when you see the missing or damaged screen, hit the tab key. You
should see a reason code come up, please send that to us.

Thanks
Sonny

> Chromium OS discuss mailing list: chromium-...@chromium.org

[Lasse]

I have/have had the same problem (it may have fixed itself while
writing this).

I have updated ChromeOS and switched to the developer channel, so it's
14.something now, but otherwise, it's as it was when it came out of
the box. I have done nothing except switch the switch to dev-mode, and
it gives the recovery screen when I boot and follow the instructions
on the screen. The recovery reason was 0x01.

When it boots, it first starts with an ASCII-art "laptop + hand with
finger on the space key" image and a warning ("Chrome OS verification
is turned off. Press space to begin recovery"). When I press space, it
quickly shows "Your system is transitioning to Developer Mode." etc.,
and then almost immediately goes to the recovery screen and hangs.

Now, while writing this, I didn't press space on the first screen but
let it time out, after which it showed the "Your system is
transitioning ..." message, which timed out too after 30 seconds, and
this time it actually continued with "Preparing your system for
developer mode. Please wait 5 - 10 minutes ...". I.e., it seems to
work.

I.e., my suggestion is to not press space on the ASCII-art warning.

Best of luck.
/L

[ShankarGanesh K]

>
> Now, while writing this, I didn't press space on the first screen but
> let it time out, after which it showed the "Your system is
> transitioning ..." message, which timed out too after 30 seconds, and
> this time it actually continued with "Preparing your system for
> developer mode. Please wait 5 - 10 minutes ...". I.e., it seems to

I do tried on developer mode [1], but i booted with my own image on
usb built as per [2]

[1] http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/samsung-series-5-chromebook
[2] http://www.chromium.org/chromium-os/developer-guide

[Richard Barnette]

On Aug 8, 2011, at 1:58 AM, Lasse wrote:

> I have/have had the same problem (it may have fixed itself while
> writing this).
>
> I have updated ChromeOS and switched to the developer channel, so it's
> 14.something now, but otherwise, it's as it was when it came out of
> the box. I have done nothing except switch the switch to dev-mode, and
> it gives the recovery screen when I boot and follow the instructions
> on the screen. The recovery reason was 0x01.
>
> When it boots, it first starts with an ASCII-art "laptop + hand with
> finger on the space key" image and a warning ("Chrome OS verification
> is turned off. Press space to begin recovery"). When I press space, it
> quickly shows "Your system is transitioning to Developer Mode." etc.,
> and then almost immediately goes to the recovery screen and hangs.
>
> Now, while writing this, I didn't press space on the first screen but
> let it time out, after which it showed the "Your system is
> transitioning ..." message, which timed out too after 30 seconds, and
> this time it actually continued with "Preparing your system for
> developer mode. Please wait 5 - 10 minutes ...". I.e., it seems to
> work.
>
> I.e., my suggestion is to not press space on the ASCII-art warning.
>

Right, pressing space will in fact send you to recovery, like the
screen says. It's not well documented, but you can bypass the
30 second wait on the screen with CTRL+D.

Enjoy!

> Chromium OS discuss mailing list: chromium-...@chromium.org

> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?
> hl=en

-- jrb

[Steve Pirk]

/Agree - Once you get the ascii art warning, just hit the ctrl key and the "d" key at the same time [ctrl-d], and the device will boot normally. On the Cr-48 hardware reference Chromebooks, you get a nice full screen graphical warning.

-- steve

Chromium OS discuss mailing list: chromium-os-discuss@chromium.org

View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb

--
Chromium OS discuss mailing list: chromium-os-discuss@chromium.org