Is it possible to download and flash Chromebook firmware.

[Nom De Plume]

A recent update failed because the updater failed to flash the firmware. I thought I should at least try to manually flash the firmware if I can get the updated firmware. If the updated firmware is absolutely necessary for the update, is it possible to somehow mark the firmware as acceptable so the update can complete? 

[mattias jonsson]

use the restore tool on a windows or linux or osx computer with chrome browser

use the tool with a usb stick

På 7 augusti 2018 6:48:49 em Nom De Plume <david....@gmail.com> skrev:

A recent update failed because the updater failed to flash the firmware. I thought I should at least try to manually flash the firmware if I can get the updated firmware. If the updated firmware is absolutely necessary for the update, is it possible to somehow mark the firmware as acceptable so the update can complete? 

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss
---
You received this message because you are subscribed to the Google Groups "Chromium OS Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

[Nom De Plume]

I have already done a restore. I was in Canary and the update failed. I restored and then tried updating to Canary again. It fails again. I did update to Dev but updating to Canary fails. The update to the OS completes but there is a firmware update and it fails, which rolls back the OS update.

[Mike Frysinger]

the firmware updater is in the rootfs and can be run by anyone using `chromeos-firmwareupdate`

if it's only failing in Canary, it might be a bug in the Canary channel ...

-mike

On Tue, Aug 7, 2018 at 12:48 PM Nom De Plume <david....@gmail.com> wrote:

A recent update failed because the updater failed to flash the firmware. I thought I should at least try to manually flash the firmware if I can get the updated firmware. If the updated firmware is absolutely necessary for the update, is it possible to somehow mark the firmware as acceptable so the update can complete? 

--

[Nom De Plume]

Thanks Mike. I tried the updater and it fails as well. There have been 3 Canary updates since this update issue was reported.https://bugs.chromium.org/p/chromium/issues/detail?id=870816 and they always fail at the firmware update. 

[Mike Frysinger]

I triaged it slightly. hopefully that's enough to get someone to check.

-mike

--

[Nom De Plume]

Mike

Since it looks like this is an isolated issue, can you suggest how I might get past the firmware update failure?

The Canary update OS succeeds but the last step is to update the firmware so it rolls back. 

If I run chromeos-firmwareupdater it fails.

running it with

chromeos-firmwareupdate -d --mode autoupdate --force

i get this but I don't think it has changed anything???

 (DEBUG) /tmp/tmp.twauwQQSf1/bin/crossystem works fine.
 (DEBUG) Using programs in /tmp/tmp.twauwQQSf1/bin.
 (DEBUG) cros_acquire_lock: Set lock file to /tmp/chromeos-firmwareupdate-running.
 (DEBUG) No PD firmware bundled in updater, ignored.
Starting Google_Elm firmware updater v4 (autoupdate)...
 - Updater package: [Google_Elm.8438.140.0 / EC:elm_v1.1.4818-e120dd6]
 - Current system:  [RO:Google_Elm.8438.19.0 , ACT:Google_Elm.8438.140.0 / EC:elm_v1.1.4818-e120dd6]
 (DEBUG) preserved HWID as: ELM D4A-C2A-G3A-A2B.
 - Write protection: Hardware: ON, Software: Main=ON
 (DEBUG) cros_check_compatible_platform image=Google_Elm platform=Google_Elm
 (DEBUG) No keysets folder.
Firmware update available: Google_Elm.8438.140.0. 
 (DEBUG) preparing main firmware images...
 (DEBUG) trying to read main firmware from system EEPROM...
 * invoke: flashrom -p host -r _current/bios.bin
 (DEBUG) cros_compare_file(_gk1_strip, _gk2_strip): b836ad2b24e871b05064340dbbec984e, b836ad2b24e871b05064340dbbec984e
 (DEBUG) tpm_fwver: 65537
 (DEBUG) data_key_version: 1
 (DEBUG) firmware_version: 1
 (DEBUG) fw_key_version: 65537
 (DEBUG) preamble_flags: 0
 (DEBUG) invoking: crosfw_update_main(RW_SECTION_A)
 * invoke: flashrom -p host --fast-verify -w bios.bin -i RW_SECTION_A
 (DEBUG) cros_compare_file(_current/main/RW_LEGACY, _target/main/RW_LEGACY): 2fdd6851b32ae931637d4845c037b550, 2fdd6851b32ae931637d4845c037b550
 (DEBUG) RW_LEGACY not changed.
Firmware update (autoupdate) completed.

On Tuesday, August 7, 2018 at 11:48:46 AM UTC-5, Nom De Plume wrote:

[Mike Frysinger]

sorry, but i haven't looked at the bug at all

-mike

--