No updates available

273 views
Skip to first unread message

Ponche

unread,
Sep 13, 2014, 7:28:27 AM9/13/14
to chromium-...@chromium.org
Hi,

I just reinstall Chrome Os after having tried Ubuntu. It was a bit difficult to do, but it works well. 

Only one problem remains: impossible to update the system or to switch to other channel. 

The version of the OS is currently stuck on 36. I found some stuff about the policy in Chrome Os, but when i go on chrome://policy all of them are disabled...

Is there anyway to solve this issue?


Thankls !

Ponche

unread,
Sep 13, 2014, 9:41:09 AM9/13/14
to chromium-...@chromium.org
Btw, here is the update_engine.log


0913/063026:INFO:main.cc(166)] Chrome OS Update Engine starting [0913/063026:INFO:omaha_request_params.cc(173)] Current Channel set to stable-channel from LSB file in rootfs [0913/063026:INFO:omaha_request_params.cc(159)] Target Channel set to stable-channel from LSB file [0913/063026:INFO:omaha_request_params.cc(196)] Download channel for this attempt = stable-channel [0913/063026:WARNING:libpolicy.cc(29)] Could not load the device policy file. [0913/063026:INFO:real_device_policy_provider.cc(113)] No device policies/settings present. [0913/063026:INFO:payload_state.cc(998)] Payload Attempt Number = 0 [0913/063026:INFO:payload_state.cc(1006)] Full Payload Attempt Number = 0 [0913/063026:INFO:payload_state.cc(1018)] Current URL Index = 0 [0913/063026:INFO:payload_state.cc(534)] Current download source: Unknown [0913/063026:INFO:payload_state.cc(1044)] Current URL (Url0)'s Failure Count = 0 [0913/063026:INFO:payload_state.cc(1033)] URL Switch Count = 0 [0913/063026:INFO:payload_state.cc(1125)] Update Timestamp Start = 9/13/2014 13:30:26 GMT [0913/063026:INFO:payload_state.cc(1200)] Update Duration Uptime = 0s [0913/063026:INFO:payload_state.cc(1241)] Current bytes downloaded for HttpsServer = 0 [0913/063026:INFO:payload_state.cc(1266)] Total bytes downloaded for HttpsServer = 0 [0913/063026:INFO:payload_state.cc(1241)] Current bytes downloaded for HttpServer = 0 [0913/063026:INFO:payload_state.cc(1266)] Total bytes downloaded for HttpServer = 0 [0913/063026:INFO:payload_state.cc(1241)] Current bytes downloaded for HttpPeer = 0 [0913/063026:INFO:payload_state.cc(1266)] Total bytes downloaded for HttpPeer = 0 [0913/063026:INFO:payload_state.cc(889)] Number of Reboots during current update attempt = 0 [0913/063026:INFO:payload_state.cc(1278)] Num Responses Seen = 0 [0913/063026:INFO:prefs.cc(27)] rollback-version not present in /mnt/stateful_partition/unencrypted/preserve/update_engine/prefs [0913/063026:INFO:payload_state.cc(1493)] p2p First Attempt Timestamp = 1/1/1601 0:00:00 GMT [0913/063026:INFO:payload_state.cc(1478)] p2p Num Attempts = 0 [0913/063026:INFO:update_check_scheduler.cc(77)] Next update check in 2m38s [0913/063026:INFO:prefs.cc(27)] attempt-in-progress not present in /var/lib/update_engine/prefs [0913/063026:INFO:p2p_manager.cc(214)] Neither Enterprise Policy nor crosh flag indicates that p2p is enabled. [0913/063026:INFO:update_attempter.cc(1484)] Not starting p2p at startup since it's not enabled. [0913/063048:INFO:dbus_service.cc(170)] Attempt update: app_version="" omaha_url="" flags=0x0 interactive=yes [0913/063048:INFO:update_attempter.cc(820)] New update check requested [0913/063048:INFO:gpio_handler.cc(587)] GPIOs not engaged, defaulting to normal mode [0913/063048:INFO:update_attempter.cc(178)] Reporting daily metrics. [0913/063048:INFO:update_attempter.cc(208)] Uploading 36d16h40m18.018804s for metric Installer.OSAgeDays [0913/063048:INFO:metrics.cc(100)] Uploading 36d16h40m18.018804s for metric UpdateEngine.Daily.OSAgeDays [0913/063048:WARNING:libpolicy.cc(29)] Could not load the device policy file. [0913/063048:INFO:update_attempter.cc(284)] No device policies/settings present. [0913/063048:INFO:update_attempter.cc(469)] Scattering disabled since scatter factor is set to 0 [0913/063048:INFO:p2p_manager.cc(214)] Neither Enterprise Policy nor crosh flag indicates that p2p is enabled. [0913/063048:INFO:update_attempter.cc(303)] p2p is not enabled - disallowing p2p for both downloading and sharing. [0913/063048:INFO:omaha_request_params.cc(56)] Initializing parameters for this update attempt [0913/063048:INFO:update_attempter.cc(414)] update_disabled = false, target_version_prefix = , scatter_factor_in_seconds = 0s [0913/063048:INFO:update_attempter.cc(421)] Wall Clock Based Wait Enabled = 0, Update Check Count Wait Enabled = 0, Waiting Period = 0s [0913/063048:INFO:update_attempter.cc(428)] Use p2p For Downloading = 0, Use p2p For Sharing = 0 [0913/063048:INFO:update_attempter.cc(435)] forced to obey proxies [0913/063048:INFO:update_attempter.cc(438)] proxy manual checks: 1 [0913/063048:INFO:prefs.cc(27)] delta-update-failures not present in /var/lib/update_engine/prefs [0913/063048:INFO:update_attempter.cc(1130)] Updating boot flags... [0913/063053:INFO:subprocess.cc(46)] Subprocess output: Starting Peppy firmware updater v4 (bootok)... - Updater package: [Google_Peppy.4389.86.0 / EC:peppy_v1.5.129-cd1a1e9] - Current system: [RO:Google_Peppy.4389.86.0 , ACT:Google_Peppy.4389.86.0 / EC:peppy_v1.5.129-cd1a1e9] - Write protection: Hardware: ON, Software: Main=off * invoke: flashrom -p host -i RW_SECTION_A:_dup2_temp_from -i RW_SECTION_B:_dup2_temp_to -r _dup2_temp_image Firmware update (bootok) completed. [0913/063053:INFO:update_attempter.cc(1325)] Scheduling an action processor start. [0913/063053:INFO:action_processor.cc(36)] ActionProcessor::StartProcessing: OmahaRequestAction [0913/063053:INFO:prefs.cc(27)] last-active-ping-day not present in /var/lib/update_engine/prefs [0913/063053:INFO:prefs.cc(27)] last-roll-call-ping-day not present in /var/lib/update_engine/prefs [0913/063053:INFO:prefs.cc(27)] install-date-days not present in /var/lib/update_engine/prefs [0913/063053:INFO:omaha_request_action.cc(383)] Not generating Omaha InstallData as we have no prefs file and OOBE is not complete. [0913/063053:INFO:prefs.cc(27)] previous-version not present in /var/lib/update_engine/prefs [0913/063053:INFO:omaha_request_action.cc(428)] Posting an Omaha request to https://tools.google.com/service/update2 [0913/063053:INFO:omaha_request_action.cc(429)] Request: <?xml version="1.0" encoding="UTF-8"?> <request protocol="3.0" version="ChromeOSUpdateEngine-0.1.0.0" updaterversion="ChromeOSUpdateEngine-0.1.0.0" installsource="ondemandupdate" ismachine="1"> <os version="Indy" platform="Chrome OS" sp="5841.98.0_x86_64"></os> <app appid="{E6710DFC-3EC0-42AE-8095-733FDEA6AF18}" version="5841.98.0" track="stable-channel" lang="en-US" board="peppy-signed-mp-v2keys" hardware_class="X86 PEPPY TEST 4211" delta_okay="true" fw_version="" ec_version="" > <ping active="1" a="-1" r="-1"></ping> <updatecheck targetversionprefix=""></updatecheck> <event eventtype="3" eventresult="2" previousversion="0.0.0.0"></event> </app> </request> [0913/063053:INFO:libcurl_http_fetcher.cc(84)] Starting/Resuming transfer [0913/063053:INFO:libcurl_http_fetcher.cc(95)] Using proxy: no [0913/063053:INFO:libcurl_http_fetcher.cc(53)] We are connected via wifi, Updates allowed: Yes [0913/063053:INFO:libcurl_http_fetcher.cc(225)] Setting up curl options for HTTPS [0913/063053:INFO:libcurl_http_fetcher.cc(505)] Setting up timeout source: 1 seconds. [0913/063053:INFO:prefs.cc(27)] update-server-cert-0-3 not present in /var/lib/update_engine/prefs [0913/063053:INFO:prefs.cc(27)] update-server-cert-0-2 not present in /var/lib/update_engine/prefs [0913/063053:INFO:prefs.cc(27)] update-server-cert-0-1 not present in /var/lib/update_engine/prefs [0913/063053:INFO:prefs.cc(27)] update-server-cert-0-0 not present in /var/lib/update_engine/prefs [0913/063053:INFO:libcurl_http_fetcher.cc(306)] HTTP response code: 200 [0913/063053:INFO:libcurl_http_fetcher.cc(375)] Transfer completed (200), 284 bytes downloaded [0913/063053:INFO:omaha_request_action.cc(822)] Omaha request response: <?xml version="1.0" encoding="UTF-8"?><response protocol="3.0" server="prod"><daystart elapsed_days="2812" elapsed_seconds="23454"/><app appid="{E6710DFC-3EC0-42AE-8095-733FDEA6AF18}" status="ok"><ping status="ok"/><updatecheck status="noupdate"/><event status="ok"/></app></response> [0913/063053:INFO:omaha_request_action.cc(577)] Set the Omaha InstallDate from Omaha Response to 2807 days [0913/063053:INFO:omaha_request_action.cc(611)] No update. [0913/063053:INFO:metrics.cc(122)] Sending 1 for metric UpdateEngine.Check.Result (enum) [0913/063053:INFO:prefs.cc(27)] metrics-check-last-reporting-time not present in /var/lib/update_engine/prefs [0913/063053:INFO:action_processor.cc(83)] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction [0913/063053:INFO:omaha_response_handler_action.cc(48)] There are no updates. Aborting. [0913/063053:INFO:action_processor.cc(69)] ActionProcessor::ActionComplete: OmahaResponseHandlerAction action failed. Aborting processing. [0913/063053:INFO:action_processor.cc(74)] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction [0913/063053:INFO:update_attempter.cc(868)] Processing Done. [0913/063053:INFO:update_attempter.cc(948)] No update. [0913/063111:INFO:update_attempter.cc(1120)] Already updated boot flags. Skipping. [0913/063142:INFO:dbus_service.cc(170)] Attempt update: app_version="" omaha_url="" flags=0x0 interactive=yes [0913/063142:INFO:update_attempter.cc(820)] New update check requested [0913/063142:INFO:gpio_handler.cc(587)] GPIOs not engaged, defaulting to normal mode [0913/063142:INFO:update_attempter.cc(168)] Last reported daily metrics 54.566799s ago. [0913/063142:INFO:update_attempter.cc(282)] Device policies/settings present [0913/063142:INFO:update_attempter.cc(350)] Networks over which updates are allowed per policy : all [0913/063142:INFO:update_attempter.cc(469)] Scattering disabled since scatter factor is set to 0 [0913/063142:INFO:p2p_manager.cc(214)] Neither Enterprise Policy nor crosh flag indicates that p2p is enabled. [0913/063142:INFO:update_attempter.cc(303)] p2p is not enabled - disallowing p2p for both downloading and sharing. [0913/063142:INFO:omaha_request_params.cc(56)] Initializing parameters for this update attempt [0913/063142:INFO:update_attempter.cc(389)] Channel settings are delegated to user by policy. Ignoring ReleaseChannel policy value [0913/063142:INFO:update_attempter.cc(414)] update_disabled = false, target_version_prefix = , scatter_factor_in_seconds = 0s [0913/063142:INFO:update_attempter.cc(421)] Wall Clock Based Wait Enabled = 0, Update Check Count Wait Enabled = 0, Waiting Period = 0s [0913/063142:INFO:update_attempter.cc(428)] Use p2p For Downloading = 0, Use p2p For Sharing = 0 [0913/063142:INFO:update_attempter.cc(435)] forced to obey proxies [0913/063142:INFO:update_attempter.cc(438)] proxy manual checks: 2 [0913/063142:INFO:prefs.cc(27)] delta-update-failures not present in /var/lib/update_engine/prefs [0913/063142:INFO:update_attempter.cc(1120)] Already updated boot flags. Skipping. [0913/063142:INFO:update_attempter.cc(1325)] Scheduling an action processor start. [0913/063142:INFO:action_processor.cc(36)] ActionProcessor::StartProcessing: OmahaRequestAction [0913/063142:INFO:omaha_request_action.cc(428)] Posting an Omaha request to https://tools.google.com/service/update2 [0913/063142:INFO:omaha_request_action.cc(429)] Request: <?xml version="1.0" encoding="UTF-8"?> <request protocol="3.0" version="ChromeOSUpdateEngine-0.1.0.0" updaterversion="ChromeOSUpdateEngine-0.1.0.0" installsource="ondemandupdate" ismachine="1"> <os version="Indy" platform="Chrome OS" sp="5841.98.0_x86_64"></os> <app appid="{E6710DFC-3EC0-42AE-8095-733FDEA6AF18}" version="5841.98.0" track="stable-channel" lang="en-US" board="peppy-signed-mp-v2keys" hardware_class="X86 PEPPY TEST 4211" delta_okay="true" fw_version="" ec_version="" installdate="2807" > <updatecheck targetversionprefix=""></updatecheck> <event eventtype="3" eventresult="2" previousversion=""></event> </app> </request> [0913/063142:INFO:libcurl_http_fetcher.cc(84)] Starting/Resuming transfer [0913/063142:INFO:libcurl_http_fetcher.cc(95)] Using proxy: no [0913/063142:INFO:libcurl_http_fetcher.cc(53)] We are connected via wifi, Updates allowed: Yes [0913/063142:INFO:libcurl_http_fetcher.cc(225)] Setting up curl options for HTTPS [0913/063142:INFO:libcurl_http_fetcher.cc(505)] Setting up timeout source: 1 seconds. [0913/063143:INFO:libcurl_http_fetcher.cc(306)] HTTP response code: 200 [0913/063143:INFO:libcurl_http_fetcher.cc(375)] Transfer completed (200), 265 bytes downloaded [0913/063143:INFO:omaha_request_action.cc(822)] Omaha request response: <?xml version="1.0" encoding="UTF-8"?><response protocol="3.0" server="prod"><daystart elapsed_days="2812" elapsed_seconds="23503"/><app appid="{E6710DFC-3EC0-42AE-8095-733FDEA6AF18}" status="ok"><updatecheck status="noupdate"/><event status="ok"/></app></response> [0913/063143:INFO:omaha_request_action.cc(611)] No update. [0913/063143:INFO:metrics.cc(122)] Sending 1 for metric UpdateEngine.Check.Result (enum) [0913/063143:INFO:metrics.cc(144)] Sending 49.355441s for metric UpdateEngine.Check.TimeSinceLastCheckMinutes [0913/063143:INFO:metrics.cc(160)] Sending 49.35575s for metric UpdateEngine.Check.TimeSinceLastCheckUptimeMinutes [0913/063143:INFO:action_processor.cc(83)] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction [0913/063143:INFO:omaha_response_handler_action.cc(48)] There are no updates. Aborting. [0913/063143:INFO:action_processor.cc(69)] ActionProcessor::ActionComplete: OmahaResponseHandlerAction action failed. Aborting processing. [0913/063143:INFO:action_processor.cc(74)] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction [0913/063143:INFO:update_attempter.cc(868)] Processing Done. [0913/063143:INFO:update_attempter.cc(948)] No update. [0913/063304:INFO:prefs.cc(27)] certificate-report-to-send-update not present in /var/lib/update_engine/prefs [0913/063304:INFO:prefs.cc(27)] certificate-report-to-send-download not present in /var/lib/update_engine/prefs [0913/063304:INFO:update_attempter.cc(168)] Last reported daily metrics 2m16.753204s ago. [0913/063304:INFO:update_attempter.cc(282)] Device policies/settings present [0913/063304:INFO:update_attempter.cc(350)] Networks over which updates are allowed per policy : all [0913/063304:INFO:update_attempter.cc(469)] Scattering disabled since scatter factor is set to 0 [0913/063304:INFO:p2p_manager.cc(214)] Neither Enterprise Policy nor crosh flag indicates that p2p is enabled. [0913/063304:INFO:update_attempter.cc(303)] p2p is not enabled - disallowing p2p for both downloading and sharing. [0913/063304:INFO:omaha_request_params.cc(56)] Initializing parameters for this update attempt [0913/063304:INFO:update_attempter.cc(389)] Channel settings are delegated to user by policy. Ignoring ReleaseChannel policy value [0913/063304:INFO:update_attempter.cc(414)] update_disabled = false, target_version_prefix = , scatter_factor_in_seconds = 0s [0913/063304:INFO:update_attempter.cc(421)] Wall Clock Based Wait Enabled = 0, Update Check Count Wait Enabled = 0, Waiting Period = 0s [0913/063304:INFO:update_attempter.cc(428)] Use p2p For Downloading = 0, Use p2p For Sharing = 0 [0913/063304:INFO:prefs.cc(27)] delta-update-failures not present in /var/lib/update_engine/prefs [0913/063304:INFO:update_attempter.cc(1120)] Already updated boot flags. Skipping. [0913/063304:INFO:update_attempter.cc(1325)] Scheduling an action processor start. [0913/063304:INFO:action_processor.cc(36)] ActionProcessor::StartProcessing: OmahaRequestAction [0913/063304:INFO:omaha_request_action.cc(428)] Posting an Omaha request to https://tools.google.com/service/update2 [0913/063304:INFO:omaha_request_action.cc(429)] Request: <?xml version="1.0" encoding="UTF-8"?> <request protocol="3.0" version="ChromeOSUpdateEngine-0.1.0.0" updaterversion="ChromeOSUpdateEngine-0.1.0.0" installsource="scheduler" ismachine="1"> <os version="Indy" platform="Chrome OS" sp="5841.98.0_x86_64"></os> <app appid="{E6710DFC-3EC0-42AE-8095-733FDEA6AF18}" version="5841.98.0" track="stable-channel" lang="en-US" board="peppy-signed-mp-v2keys" hardware_class="X86 PEPPY TEST 4211" delta_okay="true" fw_version="" ec_version="" installdate="2807" > <updatecheck targetversionprefix=""></updatecheck> <event eventtype="3" eventresult="2" previousversion=""></event> </app> </request> [0913/063304:INFO:libcurl_http_fetcher.cc(84)] Starting/Resuming transfer [0913/063304:INFO:libcurl_http_fetcher.cc(95)] Using proxy: no [0913/063304:INFO:libcurl_http_fetcher.cc(53)] We are connected via wifi, Updates allowed: Yes [0913/063304:INFO:libcurl_http_fetcher.cc(225)] Setting up curl options for HTTPS [0913/063304:INFO:libcurl_http_fetcher.cc(505)] Setting up timeout source: 1 seconds. [0913/063306:INFO:libcurl_http_fetcher.cc(306)] HTTP response code: 200 [0913/063306:INFO:libcurl_http_fetcher.cc(375)] Transfer completed (200), 265 bytes downloaded [0913/063306:INFO:omaha_request_action.cc(822)] Omaha request response: <?xml version="1.0" encoding="UTF-8"?><response protocol="3.0" server="prod"><daystart elapsed_days="2812" elapsed_seconds="23586"/><app appid="{E6710DFC-3EC0-42AE-8095-733FDEA6AF18}" status="ok"><updatecheck status="noupdate"/><event status="ok"/></app></response> [0913/063306:INFO:omaha_request_action.cc(611)] No update. [0913/063306:INFO:metrics.cc(122)] Sending 1 for metric UpdateEngine.Check.Result (enum) [0913/063306:INFO:metrics.cc(144)] Sending 1m23.460426s for metric UpdateEngine.Check.TimeSinceLastCheckMinutes [0913/063306:INFO:metrics.cc(160)] Sending 1m23.460127s for metric UpdateEngine.Check.TimeSinceLastCheckUptimeMinutes [0913/063306:INFO:action_processor.cc(83)] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction [0913/063306:INFO:omaha_response_handler_action.cc(48)] There are no updates. Aborting. [0913/063306:INFO:action_processor.cc(69)] ActionProcessor::ActionComplete: OmahaResponseHandlerAction action failed. Aborting processing. [0913/063306:INFO:action_processor.cc(74)] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction [0913/063306:INFO:update_attempter.cc(868)] Processing Done. [0913/063306:INFO:update_attempter.cc(948)] No update. [0913/063306:INFO:update_check_scheduler.cc(77)] Next update check in 46m18s

Sonny Rao

unread,
Sep 13, 2014, 1:07:19 PM9/13/14
to sluit...@gmail.com, Chromium OS discuss
hardware_class="X86 PEPPY TEST 4211"
that looks wrong, like an invalid hwid

did you get updates before installing Ubuntu?
Also did you overwrite your firmware somehow?
> --
> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to chromium-os-dis...@chromium.org.

Ponche

unread,
Sep 13, 2014, 1:35:09 PM9/13/14
to chromium-...@chromium.org, sluit...@gmail.com
Hi

Thanks for your answer.

I installed all updated for CrOs before installing Ubuntu (as far as i remember, it was version 37)

To install Ubuntu, i used this tutorial http://www.circuidipity.com/c720-sidbook.html
Then,  to restore the original firmware i used this: https://johnlewis.ie/extracting-the-shell-ball-rom-using-a-chromeos-image/

I also put the gbb_flags to 0

Ponche

unread,
Sep 13, 2014, 1:43:42 PM9/13/14
to chromium-...@chromium.org
Here is the bios info found in chrome://system



vendor | coreboot version | Google_Peppy.4389.86.0 release_date | 04/30/2014 size | 8192 KB ro bios version | Google_Peppy.4389.86.0 Boot switch status: Recovery button: released Developer mode: not enabled RO firmware: protected Boot reason (0): normal Boot firmware: A Active EC code: RW Raw log: arch = x86 # Platform architecture block_devmode = 0 # Block all use of developer mode clear_tpm_owner_request = 0 # Clear TPM owner on next boot clear_tpm_owner_done = 0 # Clear TPM owner done cros_debug = 0 # OS should allow debug features dbg_reset = 0 # Debug reset mode request (writable) ddr_type = unknown # Type of DDR RAM debug_build = 0 # OS image built for debug features dev_boot_usb = 0 # Enable developer mode boot from USB/SD (writable) dev_boot_legacy = 0 # Enable developer mode boot Legacy OSes (writable) dev_boot_signed_only = 0 # Enable developer mode boot only from official kernels (writable) devsw_boot = 0 # Developer switch position at boot devsw_cur = 0 # Developer switch current position disable_dev_request = 0 # Disable virtual dev-mode on next boot ecfw_act = RW # Active EC firmware fmap_base = 0xffe10000 # Main firmware flashmap physical address fwb_tries = 0 # Try firmware B count (writable) fwid = Google_Peppy.4389.86.0 # Active firmware ID fwupdate_tries = 0 # Times to try OS firmware update (writable, inside kern_nv) hwid = X86 PEPPY TEST 4211 # Hardware ID kern_nv = 0x00000000 # Non-volatile field for kernel use kernkey_vfy = sig # Type of verification done on kernel key block loc_idx = 3 # Localization index for firmware screens (writable) mainfw_act = A # Active main firmware mainfw_type = normal # Active main firmware type nvram_cleared = 1 # Have NV settings been lost? Write 0 to clear oprom_needed = 0 # Should we load the VGA Option ROM at boot? platform_family = Haswell # Platform family type recovery_reason = 0 # Recovery mode reason for current boot recovery_request = 0 # Recovery mode request (writable) recovery_subcode = 0 # Recovery reason subcode (writable) recoverysw_boot = 0 # Recovery switch position at boot recoverysw_cur = (error) # Recovery switch current position recoverysw_ec_boot = 0 # Recovery switch position at EC boot ro_fwid = Google_Peppy.4389.86.0 # Read-only firmware ID savedmem_base = 0x00f00000 # RAM debug data area physical address savedmem_size = 1048576 # RAM debug data area size in bytes sw_wpsw_boot = 0 # Firmware write protect software setting enabled at boot tpm_fwver = 0x00010002 # Firmware version stored in TPM tpm_kernver = 0x00020001 # Kernel version stored in TPM tried_fwb = 0 # Tried firmware B before A this boot vdat_flags = 0x00000c42 # Flags from VbSharedData vdat_lfdebug = Check A result=12 Check B result=0 Firmware index booted=0x00 TPM combined version at start=0x00010002 Lowest combined version from firmware=0x00010002 # LoadFirmware() debug data (not in print-all) vdat_lkdebug = Calls to LoadKernel()=1 Call 1: Boot flags=0x00 Boot mode=1 Test error=0 Return code=0 Debug flags=0x00 Drive sectors=31277232 Sector size=512 Check result=4 Kernel partitions found=1 Kernel 1: GPT index=2 Start sector=20480 Sector count=32768 Combined version=0x00020001 Check result=19 Debug flags=0x01 # LoadKernel() debug data (not in print-all) vdat_timers = LFS=313520739,339008950 LF=339112865,485472470 LK=727804850,977949734 # Timer values from VbSharedData wpsw_boot = 1 # Firmware write protect hardware switch position at boot wpsw_cur = 1 # Firmware write protect hardware switch current position


Hope it could help...

Many thanks

Ponche

unread,
Sep 13, 2014, 6:13:42 PM9/13/14
to chromium-...@chromium.org
In fact, my Acer C720 is now recognized as "X86 TEST peppy 4211" as the model...

Sonny Rao

unread,
Sep 14, 2014, 4:08:34 AM9/14/14
to Maxime Sluiters, Chromium OS discuss
What I mean is, did you ever receive an auto-update? I'm trying to
determine whether you've always had this hardware ID or not. If you
have, chances are you've not gotten an auto-update in the past either
and you probably need to return the machine since it has an incorrect
ID.

On Sat, Sep 13, 2014 at 3:13 PM, Ponche <sluit...@gmail.com> wrote:
> In fact, my Acer C720 is now recognized as "X86 TEST peppy 4211" as the
> model...
>
> --
> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to chromium-os-dis...@chromium.org.

Ponche

unread,
Sep 14, 2014, 6:38:05 AM9/14/14
to chromium-...@chromium.org, sluit...@gmail.com
Well actually i remember that my hwid before installing Ubuntu was different. 

Ponche

unread,
Sep 14, 2014, 10:45:05 AM9/14/14
to chromium-...@chromium.org, sluit...@gmail.com
Hi,

FInally i managed to rewrite original hwid, using this https://code.google.com/p/chromium/issues/detail?id=222462 (post 8) and the orignal C720 hwid.

Now, everythings work great !


Thanks for your help 

Sonny Rao

unread,
Sep 15, 2014, 3:00:15 PM9/15/14
to Maxime Sluiters, Chromium OS discuss
Ok, if you're able to write that then you must have removed the
write-protect on the spi flash and overwritten it. Basically, I would
say our advice is "don't do that" because of problems like this and
the possibility of bricking the machine, but I'm glad you were able to
fix it. I would recommend re-enabling the write protect.
> --
> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to chromium-os-dis...@chromium.org.
Reply all
Reply to author
Forward
0 new messages