Version: 5978.103.0

A Chromebook reseller is attempting to perform auto-update on a number of Peppy touch (Acer C720P) Chromebooks from FSI (R37) to current stable (R51). If they recover from USB (R49), then it will auto-update to R51 just fine.

This seems related to  issue 394061  where firwmare update failed. Is there any way to get auto-update from FSI working on these devices? 

ec_info.txt
vendor               | ti
name                 | Unknown-10de
fw_version           | peppy_v1.5.130-a1f12b7

************************************

/var/log/update_engine/update_engine.20160616-222635:

Starting firmware updater (/tmp/au_postint_mount.J4ACWh/usr/sbin/chromeos-firmwareupdate --mode=autoupdate)
Command: /tmp/au_postint_mount.J4ACWh/usr/sbin/chromeos-firmwareupdate --mode=autoupdate
Starting Google_Peppy firmware updater v4 (autoupdate)...
 - Updater package: [Google_Peppy.4389.93.0 / EC:peppy_v1.5.132-c77d95f]
 - Current system:  [RO:Google_Peppy.4389.89.0 , ACT:Google_Peppy.4389.89.0]
 - Write protection: Hardware: ON, Software: Main=off
One-time RO+RW update from unstable EC firmware.
Try to update with recovery mode...
autoupdate(recovery): update RO+RW
 Execution failed (1): flashrom -p host -r _vpd_temp.bin
 Messages:
flashrom v0.9.4  : faaccd7 : Apr 06 2016 06:44:18 UTC on Linux 3.8.11 (x86_64), built with libpci 3.1.10, GCC 4.9.x 20150123 (prerelease), little endian
Cannot stat /run/lockCould not acquire lock.
ERROR: Failed to read current main firmware.
ERROR: Execution failed: ./updater4.sh (error code = 1)
Finished after 1 seconds.
Failed Command: /tmp/au_postint_mount.J4ACWh/usr/sbin/chromeos-firmwareupdate --mode=autoupdate - Exit Code 1
Firmware update failed (error code: 1).
Rolling back update due to failure installing required firmware.
Successfully updated GPT with all settings to rollback.
PostInstall Failed
 

Deleted: debug-log_20160616-225857 (1).zip 574 KB

debug-log_20160616-225857 (1).zip 574 KB Download