Nick: Guest14 E-mail: none Board: Enguarde Contents: ChromeOS Device Firmware Utility Script [2023-01-29] (c) Mr Chromebox ********************************************************* ** Device: (multiple device matches) (ENGUARDE) ** Platform: Intel BayTrail ** Fw Type: Full ROM / UEFI ** Fw Ver: MrChromebox-4.19.1 (01/29/2023) ** Fw WP: Disabled ********************************************************* ** [WP] 1) Install/Update UEFI (Full ROM) Firmware ** [WP] 2) Restore Stock Firmware ** C) Clear UEFI NVRAM ********************************************************* Select a menu option or R to reboot P to poweroff Q to quit 2 Restore Stock Firmware Standard disclaimer: flashing the firmware has the potential to brick your device, requiring relatively inexpensive hardware and some technical knowledge to recover. You have been warned. Do you wish to continue? [y/N] Y VERY IMPORTANT: Your device has reached end of life (EOL) and is no longer supported by Google. Returning the to stock firmware **IS NOT RECOMMENDED**. MrChromebox will not provide any support for EOL devices running anything other than the latest UEFI Full ROM firmware release. Do you wish to continue? [y/N] Y Do you have a firmware backup file on USB? [y/N] Y Connect the USB/SD device which contains the backed-up stock firmware and press [Enter] to continue. Devices available: 1) Generic Mass-Storage (1.88 GB) Enter the number for the device which contains the stock firmware backup: 1 (Potential) Firmware Files on USB: stock-firmware-ENGUARDE-20230308.rom Enter the firmware filename: stock-firmware-ENGUARDE-20230308.rom Restoring stock firmware flashrom dc8caac9-dirty on Linux 6.1.12-1-MANJARO (x86_64) flashrom was built with unknown PCI library, GCC 11.3.0, little endian Command line (10 args): /tmp/flashrom -p internal --ifd -i bios -N -w /tmp/usb/stock-firmware-ENGUARDE-20230308.rom -o /tmp/flashrom.log Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer get_mtd_info: device_name: "intel-spi", is_writeable: 1, numeraseregions: 0, total_size: 8388608, erasesize: 4096 Opened /dev/mtd0 successfully The following protocols are supported: Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Added layout entry 00000000 - 007fffff named complete flash Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific). Reading ich descriptor... done. Assuming chipset 'Baytrail'. Added layout entry 00000000 - 00000fff named fd Added layout entry 00200000 - 007fffff named bios Added layout entry 00001000 - 001fffff named me restore_power_management: Re-enabling power management. Using region: "bios". Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. disable_power_management: Disabling power management. disable_power_management: Failed to open /run/lock/power_override/flashrom.lock for writing: No such file or directory Reading old flash chip contents... 0x200000-0x7fffff:R done. fix_erasers_if_needed: kept all erasers ChromeOS Device Firmware Utility Script [2023-01-29] (c) Mr Chromebox ********************************************************* ** Device: (multiple device matches) (ENGUARDE) ** Platform: Intel BayTrail ** Fw Type: Full ROM / UEFI ** Fw Ver: MrChromebox-4.19.1 (01/29/2023) ** Fw WP: Disabled ********************************************************* ** [WP] 1) Install/Update UEFI (Full ROM) Firmware ** [WP] 2) Restore Stock Firmware ** C) Clear UEFI NVRAM ********************************************************* Select a menu option or R to reboot P to poweroff Q to quit 1 Install/Update UEFI Full ROM Firmware IMPORTANT: flashing the firmware has the potential to brick your device, requiring relatively inexpensive hardware and some technical knowledge to recover.Not all boards can be tested prior to release, and even then slight differences in hardware can lead to unforseen failures. If you don't have the ability to recover from a bad flash, you're taking a risk. You have been warned. Do you wish to continue? [y/N] Y Downloading Full ROM firmware (coreboot_tiano-enguarde-mrchromebox_20230129.rom) VPD extracted from current firmware Disabling software write-protect and clearing the WP range Installing Full ROM firmware (may take up to 90s) Error running cmd: /tmp/flashrom -p internal --ifd -i bios -N -w coreboot_tiano-enguarde-mrchromebox_20230129.rom >/dev/null 2>&1 -o /tmp/flashrom.log Press enter to view the flashrom log file, then space for next page, q to quit flashrom dc8caac9-dirty on Linux 6.1.12-1-MANJARO (x86_64) flashrom was built with unknown PCI library, GCC 11.3.0, little endian Command line (10 args): /tmp/flashrom -p internal --ifd -i bios -N -w coreboot_tiano-enguarde-mrchromebox_2023 0129.rom -o /tmp/flashrom.log Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer get_mtd_info: device_name: "intel-spi", is_writeable: 1, numeraseregions: 0, total_size: 8388608, erasesize: 4 096 Opened /dev/mtd0 successfully The following protocols are supported: Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Added layout entry 00000000 - 007fffff named complete flash Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific) mapped at physical address 0x00 00000000000000. Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific). Reading ich descriptor... done. Assuming chipset 'Baytrail'. Added layout entry 00000000 - 00000fff named fd Added layout entry 00200000 - 007fffff named bios Added layout entry 00001000 - 001fffff named me restore_power_management: Re-enabling power management. Using region: "bios". Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. disable_power_management: Disabling power management. disable_power_management: Failed to open /run/lock/power_override/flashrom.lock for writing: No such file or d irectory Reading old flash chip contents... 0x200000-0x7fffff:R done. fix_erasers_if_needed: kept all erasers fill_sorted_erasers: found 1 valid erasers 200000..20ffff 1000 x 16 eraser 0 Erasing and writing flash chip... 0x200000-0x200fff: Elinux_mtd_erase: MEMERASE ioctl call returned -1, error: Unknown error 524 ERASE_FAILED FAILED! Uh oh. Erase/write failed. Your flash chip is in an unknown state. Get help on IRC (see https://www.flashrom.org/Contact) or mail flashrom@flashrom.org with the subject "FAILED: "!------------------------------------------- ------------------------------------ DO NOT REBOOT OR POWEROFF! restore_power_management: Re-enabling power management. FAILED restore_power_management: Re-enabling power management.