Issue metadata
Sign in to add a comment
|
[ZGB] Device stuck on "Chrome os verification is turned off" screen |
||||||||||||||||||||||||
Issue descriptionChrome OS Platform: ZGB Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Auto update to M56(9000.26.0) (2) Reboot the device after successful update. Expected Result: Should see login/start screen after reboot. Actual Result: Always seen "Chrome Os verification is turned off" screen. Seen same issue with recovery install too. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) always. What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jan 9 2017
,
Jan 13 2017
+dhendrix in case this is something to do with lower layers in the FW
,
Jan 14 2017
Can you press the TAB key at the screen and copy what the GBB flags are set as? I am wondering if GBB_FLAG_FORCE_DEV_SWITCH_ON got enabled somehow. Another possibility is if the developer switch got switched on somehow (ZGB is one of the very old designs with a physical switch for dev mode). Please check that the developer mode switch is set to "normal mode": http://www.chromium.org/a/chromium.org/dev/chromium-os/developer-information-for-chrome-os-devices/acer-ac700-chromebook#TOC-Developer-switch If the switch is set to the correct position, boot and try running "crossystem devsw_boot" and "crossystem devsw_cur" from VT2 to see if software and hardware agree. (cc'ing Randall and Bill as well since they might remember some details about this device)
,
Jan 17 2017
That looks like the OS-side dev warning screen, not the dev firmware. ZGB was one of a couple devices where normal and dev firmware were actually different images. So I don't think it's the GBB. That also means pressing Tab won't do anything at that screen. If you press Ctrl+D, does it get past that screen?
,
Jan 24 2017
May be a dup of issue 479964
,
Jan 25 2017
Is this issue seen on M56 beta?
,
Jan 25 2017
Asked abodeti@ to verify channel where this appears. Linked bug was on dev channel.
,
Jan 25 2017
,
Jan 25 2017
Reproduced this issue on M56-Beta(9000.66.0).
,
Jan 25 2017
,
Jan 25 2017
Can we reproduce this on other ZGB, or just this one device?
,
Jan 25 2017
Also, to confirm, what position is the physical dev switch in? Is the bug that you expect to be in normal mode, and all of a sudden the OS thinks you're in dev mode? Or is the bug that you expect to be in dev mode, and all of a sudden now you can't get past this screen?
,
Jan 25 2017
Also, what happens once you're at the screen. Does it sit there forever, or does it eventually boot?
,
Jan 25 2017
Its always stuck at recovery screen.
,
Jan 25 2017
Also happens on all zgb devices
,
Jan 25 2017
,
Jan 25 2017
Assigning to dbehr@ following up on comment 6. Please pass along to the right owner if not you, thanks.
,
Jan 25 2017
Do you mean the "Chrome OS is missing or damaged" screen, or the one you screen-captured? What is the position of the physical developer switch? Does the behavior change if you move it to the other position?
,
Jan 26 2017
device switched from developer mode to normal mode, and issue is no more reproducible on M56-Beta(9000.72.0.
,
Jan 26 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by abod...@chromium.org
, Dec 20 2016