New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 669575 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2016
Cc:
llozano@chromium.org
█ laszio@chromium.org
█ yunlian@chromium.org
cmt...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Remote flash does not work after recovering from a bad chromeos image

Project Member Reported by manojgupta@chromium.org, Nov 29 2016 
If a bad chromeos image is installed, after rebooting it recovers itself by switching to an old working image after several failed attempts to boot.

However, remote flash does not work anymore after recovery.

Comment 1 by cmt...@chromium.org, Nov 29 2016

Labels: Build

Comment 2 by lloz...@google.com, Nov 29 2016 

I think we need to put more info in this bug.
What is the image version?
add a cat of /etc/lsb-release here.
what is the output of cros flash when it fails. I think there is a verbose command. It would be good to add it here.

how was the "recovering to" image generated? is it dev or test? (should say in /etc/lsb-release)

Comment 3 by manojgupta@chromium.org, Dec 6 2016 

Does not happen with official image R57-9034.0.0

Comment 4 by manojgupta@chromium.org, Dec 6 2016

Status: WontFix (was: Untriaged)
Closing for now since 1) it is hard to reproduce and 2) Official images work.
►

Sign in to add a comment