My Chromebook Pixel will not let me enable Developer Mode ... Please help !

[wakari...@gmail.com]

Hello all,

I'm trying to get my Chromebook Pixel to run in developer mode.  When i reach the recovery screen,  I press Control - D and nothing happens.  I press it over and over and nothing.  I purchased a C720P as a gift for someone for christmas,  and the Dev mode procedure worked on the first attempt !!! Really frustrating.  I just ran through the recovery process with a USB,  to see if that would help,  tried to invoke Dev Mode again and nothing.

Why wouldn't control - d work ?  any ideas ?

all help is really appreciated.  Thanks in advance.

[Sheridan Rawlins]

This happened to me once upon a time.  You have to keep pressing Escape/Reload until a bit after the screen loads.  Then release and press ctrl-d.  I'm not sure the exact timing, but you have to keep it held down.

I hope this helps…

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

[Luigi Semenzato]

The known problem with releasing Escape-Reload-Power too soon is that
the pixel may not enter recovery mode, but that's not the case here.
I just tried on my pixel, and it was sufficient to wait until the
keyboard backlight turns on.

After that, I had no problem with control-D. I am on the Dev channel.
Could you try a few more times, and if it doesn't work, would you
report your version numbers from about:help?

Thanks!

[wakari...@gmail.com]

I tried a few more times,  to no avail.

Here are my version #'s

Version 31.0.1650.67

Platform 4731.101.0 (Official Build) stable-channel link

Firmware Google_Link.2695.1.133

[Luigi Semenzato]

OK, we discussed this off line and I opened crbug.com/331632. It may
be a known root cause but I had not seen this particular outcome.

tl;dr: to reproduce, start in the OFF state, hold ESC and RELOAD, tap
POWER briefly, keep holding ESC and RELOAD for a few seconds. When
the recovery screen appears, control-D has no effect.

[Will Fernandez]

Thank you all ...

Holding the power button down until the keyboard backlight came back on worked.

Now running in dev mode !

[Mike Frysinger]

well, our current documentation says:

To invoke Recovery mode, you hold down the ESC and Refresh keys and briefly hold the Power button (if you hit it too fast it won't work).

http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/chromebook-pixel

for user-facing documentation, seems like that already covers this case ?

considering the Pixel has long shipped at this point, i don't think it'll ever see a fix ...

-mike

On Sat, Jan 4, 2014 at 12:33 AM, Luigi Semenzato <seme...@chromium.org> wrote:

[Mark Hayter]

I updated Luigi's bug.

Partner bug 15705 (internal only) indicates that on Pixel esc+reset+power must all be pressed for a minimum of 200ms. If the "tap the power key briefly" is less than 200ms then the flag that indicates untrusted EC (EC_IN_RW) can mistakenly get set and the system will enter recovery (assuming ESC+RELOAD are held long enough) but will not trust the Ctrl-D keystroke.

This is a quirk on the Pixel. Our documentation should be updated to indicate briefly==">200ms".

Im a little surprised we didn't document this since it was a bug that took a while to sort out.

An immediate second tap on power is also supposed to fix.

(It is possible the 200ms number was increased later to work around an EC Silicon bug, but I don't remember if that affects this case)

Mark

[Mike Frysinger]

i've rephrased it to:

To invoke Recovery mode, you hold down the ESC and Refresh keys and

hold the Power button for at least 200ms (until the keyboard backlight
comes on). If you don't hold it for long enough, then it won't work.
-mike

[Conrad Cline]

I know this is an old threat, but I am, experiencing the same issue on the Asus C300M. I have done developer mode many times before, and installed crouton the system multiple times. My kids kept resetting the system and erasing the install. Last time they did it, I just stopped trying to keep it installed. Now, I want to install it again, but CTRL+D does not work. I cannot get into dev mode. I can get into recovery just fine, but no CTRL commands work. 

Did a new bug crop up? 

[Mike Frysinger]

are you quoting someone or asking a new question ?

-mike

On Sat, Jan 10, 2015 at 6:12 PM, Conrad Cline <phoeni...@gmail.com> wrote:

I know this is an old threat, but I am, experiencing the same issue on the Asus C300M. I have done developer mode many times before, and installed crouton the system multiple times. My kids kept resetting the system and erasing the install. Last time they did it, I just stopped trying to keep it installed. Now, I want to install it again, but CTRL+D does not work. I cannot get into dev mode. I can get into recovery just fine, but no CTRL commands work. 

Did a new bug crop up? 

--

[Conrad Cline]

asking a new question

[Max Butterfield]

Same problem here on a toshiba 2

Install Ubuntu kde via crouton and got off to a good start install some applications.

Had a problem with konsole terminal not working (opening blank and window freezing) so decided to have a fresh start. Rebooted in recovery mode and ctrl-D isn't working.

Tried the above methods, nada.

[Max Butterfield]

Solution -

Instead of Esc+Refresh+Power, just hit Refresh+Power.

From here you can continue to boot in developer mode with ctrl+D or hit space and wipe clean.

[Flanker]

just hit Refresh+Power, was not working.

在 2015年1月23日星期五 UTC+8上午1:34:37，Max Butterfield写道：

[Dario Dorando]

Try it with this:
"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). If you don't hold it for long enough, then it won't work.

To enter Dev-mode, you first invoke Recovery, and at the Recovery screen press Ctrl-D (there's no prompt - you have to know to do it). It will ask you to confirm, then reboot into dev-mode."

Good luck :)

--

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

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[nestor novatore]

heya. i too am having problems entering developer mode. i am using a samsung 5 550, which has a reset button on the bottom instead of esc + f3. when i hold that button and power i go into recovery mode. from there, when i press ctrl - d nothing happens.

[Luigi Semenzato]

On Tue, Apr 26, 2016 at 11:48 PM, nestor novatore <serap...@gmail.com> wrote:
> heya. i too am having problems entering developer mode. i am using a samsung
> 5 550, which has a reset button on the bottom instead of esc + f3. when i
> hold that button and power i go into recovery mode. from there, when i press
> ctrl - d nothing happens.

This confused me on one occasion, and it turned out that I was already
in developer mode. Is that the case for you?

Otherwise, press TAB at the recovery screen, and it should show you
the "recovery reason". In this case it should be "recovery button
pressed". If that's not the reason, control-D has no effect.

[Richard Barnette]

(resend from the proper address)

> On Apr 26, 2016, at 11:48 PM, nestor novatore <serap...@gmail.com> wrote:
>
> heya. i too am having problems entering developer mode. i am using a samsung 5 550, which has a reset button on the bottom instead of esc + f3. when i hold that button and power i go into recovery mode. from there, when i press ctrl - d nothing happens.
>

Early model Chromebooks, including the Samsung 5 550, have a
separate physical switch. Details can be found with a Google
search for "samsung series 5 550 chromebook developer mode".

[PI Guy]

Hold [Ctrl]+D until screen blacks out

[zon]

hello guys,

thanks for all the information.

I am having the same issue here. Tried everything you posted but did not work.

I have a samsung xe500c21, Samsung series 5, from 2011. Everything was good right after doing the physical switch: a screen showing the computer is entering the dev mode and wait for a couple of seconds. After thouse couple of minutes the computer is showing "Chrome OS verification is turned off". I press Ctrl+d and nothing happends. As I said, also tried all combination of keys you posted, but nothing happend.

Any ideas?

------------------------------------

[Michal Suchanek]

Hello,

in my experience the latest firmware tends to break in developer mode
sometimes and needs to be reinstalled.

Used to work more reliably with earlier revisions.

> ---
> You received this message because you are subscribed to the Google Groups
> "Chromium OS dev" group.

[Savannah]

Hi, 

I have the same model, and am having the same problem - have you found anything that helps?

[Chris]

Hello humans,

I have the same problem. I have used the dev-mode years ago to dualboot Linux and it worked perfectly.

This time I wanted to use the dev-mode again after the support of the Series 5 ran out.

And at first all went well: switch on, boot, state deleted, reboot, the ASCII chromebook with finger and "Chrome OS verification is turned off".

Then almost nothing: CTRL-D does not work, CTRL-C clears the screen to black with a cursor where I can type, but I don't get reactions for commands (ls, reboot) and no prompt. Just the cursor. And I can toggle through 4 "screens" with CTRL-ALT + "F1" to "F4", all empty. CTRL-ALT-T does not work.

I have tried pressing the recovery button on the chromebook-screen - nothing. And I have reset the EC with the other button. Also nothing.

I have reinstalled chromeOS with the official procedure via the chrome-plugin and an USB stick.

Anyone seen the "empty console" before? Any idea what to do with that?

I don't want to use a chromebook with an outdated software nor just thrown the damn thing away.

Is there a way to obtain downrev firmware to go to a version where the dev-mode still works?

Simply booting a self-made image will not work because I am on stock-FW, right?

Cheers!

chris :)

[Dominik Behr]

You see empty frecon console with no agetty output because login is poasibly disabled. You should see white acreen with measage about either powerwash or something else about dev mode on first console lots of spew logs from scripts on console 2 and 3.

Maybe dev mode is disabled in corp policy for you, it should then quietly disable it and reboot. I am not sure if there is any UI during that.

[Chris]

Hi Dominik,

console 1 is white and has the sad ascii-chromebook with the finger saying Chrome OS verification is turned off., consoles 2-4 are black and empty. No logs nowhere. CTRL-C clears the screen to black, even console 1.

The book was never under any corp policy. It came from the trusted tester program from Google

The book, I noticed, is German. Any idea how I change the language in the BIOS? Maybe it will work better when it thinks it is a US computer. I would not expect to set ChromeOS to English, then switch to dev-mode and have that setting survive.

So any down-rev FW that i can flash or some secret key-combos to resettify something?

Schönen Dank erstmal,

Chris :)

On Mon, Nov 6, 2017 at 6:11 PM, 'Dominik Behr' via Chromium OS dev <chromiu...@chromium.org> wrote:

You see empty frecon console with no agetty output because login is poasibly disabled. You should see white acreen with measage about either powerwash or something else about dev mode on first console lots of spew logs from scripts on console 2 and 3.

Maybe dev mode is disabled in corp policy for you, it should then quietly disable it and reboot. I am not sure if there is any UI during that.

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

---
You received this message because you are subscribed to a topic in the Google Groups "Chromium OS dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-os-dev/-aAusdRe0LY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-os-dev+unsubscribe@chromium.org.

[Dominik Behr]

You can change language on "BIOS" dev-mode and recovery screens by
pressing left and right arrow keys.

CTRL-C probably killed the script that was running power wash
(clearing stateful partition).
Normally you should see white screen with warning about developer mode
followed by white powerwash screen with rotating icon and text
starting with "Preparing system for developer mode".

Please make sure you are running latest Chrome OS before switching to
dev mode. At one point we had some issues when switching recovery
scripts to use frecon, so maybe you are experiencing problems with old
release?
I just tried dev to normal mode and back switch on my Lumpy (Samsung
series 5 XE550C22) using latest dev channel build and it worked fine.
--
Dominik

>> chromium-os-d...@chromium.org.
>
>

[Chris]

Arrow keys on my "sad chromebook with finger" screen does nothing. For the first 30 seconds (i used a stopwatch - suspicious, eh?) it seems to ignore them (and ctrl-d btw), and then it prints them out as "^[[C" and "^[[D" on the top of the screen, together with all other keys i hit.

CTRL-C here does not kill clearing the stateful partition, that step has already run successfully (or maybe not?) before. I clearly remember it showing something that looks the stats of 'dd' or "wget" or something on the top of the screen, then reboot. THEN we get into this funny state.

I have regularly updated the book in the past and even restored it with the chrome-app + USB Stick once during this process. 

If you want I'll send the book to you (are you in Munich?). With no security patches this thing has become a brick to me. Maybe you can figure out what's wrong with it and help others. Even if you manage to fix it I might not even need it back - tho it would be nice.

Is there a way to obtain an older FW, which might not have this problem yet? I once successfully put it into dev mode in 2011/2012-ish.

Cheers!

chris :)

>> chromium-os-dev+unsubscribe@chromium.org.
>
>

[Bryce Chidester]

Greetings all,

Apologies for replying to an old thread but alas I've found myself in the exact same pickle as others here (Chris, Zon, Nestor) and I'm really hoping someone can shed some more light on things.

In short, I had the same idea as Chris: Now that official support has ended, why not run devmode and fiddle about.

The quick run-down:

* Samsung Series 5 XE500C21

* Developer mode worked fine when I first purchased it, and as recently as about 3-4 years ago when I last tried.

* Enabling the "Developer Mode" switch runs through the wipe process without issue, it reboots, and then I'm left with a white screen, ASCII-art laptop with a sad face, a Chrome logo in the top-left, and the text "Chrome OS verification is turned off." No other text, not the "Press Ctrl-D to continue" or anything about recovery.

* I can switch it back to Normal and it boots fine once again.

* I've tried recovery (several times now) using the hardware recovery switch. No errors reported. I've tried this both in and out of developer mode, the only difference being a warning that the device is in developer mode in the recovery dialog.

* I let it sit for days hoping "something" might be happening but no change.

* Out of desperation, I even tried resetting the EC, no change.

* I verified (from a normal boot) that there are no Enterprise policies applied to this device, much less any that would preclude devmode. (I use it with my own domain, but I don't have a subscription for Chrome device management)

* As others have observed, there's essentially no response to anything on that screen. Ctrl-C clears it, characters show up, but it doesn't appear that anything is happening. Powering it off requires holding the power button 5+ seconds.

So please, ancient ones (https://xkcd.com/979/), tell me of a solution! Or at least a clue as to what's happening (or not).

>> chromium-os-d...@chromium.org.
>
>

[Mike Frysinger]

i think you're talking about x86-alex.  that has a dedicated physical developer mode switch that controls dev-mode vs non-dev-mode.  whether you want to be in dev mode or non-dev mode, please make sure you've flipped the switch to the correct orientation before trying anything else.

http://dev.chromium.org/a/chromium.org/dev/chromium-os/developer-information-for-chrome-os-devices/samsung-series-5-chromebook

-mike

https://groups.google.com/a/chromium.org/group/chromium-os-dev

[Bryce Chidester]

Hi Mike,

Yes that's correct, the "SAMS ALEX BETA-US" device. And yes I'm familiar with the developer mode switch. Like I said, I've toggled it before in the past, I've toggled it many times over the past weeks trying to make for a successful transition to devmode. And yes, the Chromebook is entering devmode as confirmed by the "Chrome OS verification is turned off." message (among other aspects).

Thank you for taking the time to reply.

[Ruben de Pedro Cibanal]

Hi everyone!

I have the same issue with the "Chrome OS verification is turned off." messag.

Samsung Series 5 XE500C21

Enabling the "Developer Mode" switch runs through the wipe process without issue, it reboots, and then I'm left with a white screen, ASCII-art laptop with a sad face, a Chrome logo in the top-left, and the text "Chrome OS verification is turned off." No other text, not the "Press Ctrl-D to continue" or anything about recovery.

I can switch it back to Normal and it boots fine once again.

Someone solved it?

[Bryce Chidester]

> Someone solved it?

No.

[Mike Frysinger]

you're supposed to just press Ctrl-D.  there probably isn't a message telling you to do so.

if that doesn't work, sorry, but i don't have any other suggestions.

-mike

[Denny Lockhart]

Bryce,

On the Alex, in addition to flipping the physical switch you have to run a few commands in the terminal for a second level of access, see below:

Developer-mode BIOS 

If you want to make modifications to the Chrome OS filesystem or boot your own version of Chromium OS, you'll need to activate the second level of developer access. You do this by running a special command from the command line shell, available after the device boots to the 'select language' screen by pressing Ctrl-Alt-"→" (Ctrl-Alt-F2). You first log in with the username 'chronos' (if you've set a shell password, you'll be prompted for it). Then you switch to the 'root' account, and run the command to install the developer-mode BIOS. For example: 

 

localhost login: chronos
chronos@localhost $ sudo bash
localhost chronos # chromeos-firmwareupdate --mode=todev

See the link below for other details:

1. https://www.chromium.org/a/chromium.org/dev/chromium-os/developer-information-for-chrome-os-devices/samsung-series-5-chromebook#TOC-Developer-mode-BIOS

Hope this helps,

~Denny

[Ruben de Pedro Cibanal]

sad face :-(

El viernes, 31 de enero de 2020, 21:07:31 (UTC+1), Bryce Chidester escribió:

> Someone solved it?

No.