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

Issue 888550 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 881034
Owner:
Closed: Sep 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

latest snow recovery image appears to be broken

Project Member Reported by semenzato@chromium.org, Sep 24

Issue description

I was contacted by an IT manager (in cc:) who was having trouble re-imaging his snow device with a recovery image.  He solved the problem by downloading an earlier recovery image (he figured out the URL).  This suggests that the latest image is bad.

I am copying the relevant information from his email:

"I own quite old samsung chromebook, exact model snow bara d-j 4243"

"Some time ago I noticed that the chromebook did not want to upgrade any more, despite that it was downloading newer version." (This may be a separate problem?)

"So I decided to do a recovery with the newest image.  I have been stuck on the recovery screen since then."

Error detail:

Starting firmware updater (//usr/sbin/chromeos-firmwareupdate --mode=recovery)
Command: //usr/sbin/chromeos-firmwareupdate --mode=recovery
Starting Google_Snow firmware updater v4 (recovery)...
 - Updater package: [Google_Snow.2695.117.0 / EC:snow_v1.3.139-375eb9f]
 - Current system:  [RO:Google_Snow.2695.132.0 , ACT:Google_Snow.2695.132.0 / EC:snow_v1.3.139-375eb9f]
 - Write protection: Hardware: ON, Software: Main=ON EC=ON
mv: cannot stat 'bios-snow-2695.132.ro.bin': No such file or directory
ERROR: Execution failed: ./updater4.sh (error code = 1)
Finished after 2 seconds.
Failed Command: //usr/sbin/chromeos-firmwareupdate --mode=recovery - Exit Code 1
Firmware update failed (error code: 1).
Rolling back update due to failure installing required firmware.

(full recovery log will be attached)

Then:

"Finally I figured it out. I remembered that the chrome os version that used to work was from 23 June 2018. I googled which version exactly it was and downloaded the image from the google server (that required some creative thinking to figure out the exact url). I created a recovery usb using that image and it worked! I have working chromebook again."


"I tried again to upgrade it from running system and for a moment I saw the message that this chromebook is too old and will no longer be automatically updated. Then after few second the message disappeared and it started downloading newer chrome os. After that nothing happened, the upgrade did not work as before."

 
Attaching recovery log.
recovery.log
193 KB View Download
Cc: reinauer@chromium.org konrad.d...@gmail.com
Stefan can you help me route this?  It seems that the recovery failure is related to a firmware update problem.  Thanks!
Owner: hungte@chromium.org
Mergedinto: 881034
Status: Duplicate (was: Untriaged)
Dupe of 881034 and should have been fixed on ToT.

Please try 11089.0.0 or newer versions.
Shouldn't we remove the bad recovery image ASAP, and use an older one until the new one is ready?
Cc: josa...@chromium.org
Josafat, it appears we're letting people download a bad recovery image.  Should not we replace it with a previous one which works?

(There's probably more information on the bug that this one duplicated, but this one is shorter.)

Cc: bhthompson@google.com
yes, we need to replace the recovery either with newer image of a previous working image

HungTe, could you confirm <=M68 will not have this issue?
The issue is caused by https://chromium-review.googlesource.com/c/chromiumos/platform/firmware/+/668321, so any ranches have it will fail.

From what we've collected so far:

<M68: no issue
=M68: have this issue
=M69: have this issue, a change is created (https://chrome-internal-review.googlesource.com/684849) but need M69 TPM to approve.
=M70: Fixed since 11021.27.0
>=M71: Fixed since 11089.0.0


Cc: cindyb@chromium.org
We have rolled back the 68 recovery images to 67, and Cindy is setting up recovery images for 69 but not yet with daisy derivatives until the next stable which hopefully will have the fix.
This is complete. Recovery image for Daisy is set to M67, all others M69.
Very nice, thanks!

Sign in to add a comment