Does anyone have a spare backup copy of the firmware image

156 views
Skip to first unread message

james cheng

unread,
Apr 10, 2023, 12:41:42 AM4/10/23
to ChromiumOS Discussion

Hi Community,

Does anyone have a spare backup copy of the firmware image for

Acer Chromebook 311 11.6" chromebook ARM Cortex A73 CPU / 4G RAM / 32G eMMc

The link for the product is https://www.amazon.ca/dp/B09P1XPX6F?psc=1&ref=ppx_yo2ov_dt_b_product_details.


.Or if anyone has this Chromebook and use flashrom on their Chromebook and get a copy of the firmware for me. I would really appreciate your effort.


The reason i am asking is because I don't want to cost another 150 CAD for this. I made a mistake and didn't know that Google has encryption which encrypts all the file system in the ChromeOS and I could not extract the firmware from where I saved in the mounted partition /var folder


Some discoveries:

I think the processor is actually A53 with ‎Integrated ARM G72 MP3 Graphics. And I think it is mt8183(mediatek) SOC. The board codename is jacuzzi, although mine has juniper firmware loaded for both EC and AP BIOS, i think they are the same.

1, The EEPROM is 25Q64J and it doesn't seem i can use Ch341a for this.

Step I have tried:

1, Build Coreboot with edk2 payload from coreboot official github.

2, Compiling the coreboot with depthcharge(ran emerge-jacuzzi coreboot -> emerge-jacuzzi depthcarge and emerge-jacuzzi chromeos-bootimage) from google official chromebook and flashing it using homemade Suzy Q cable(Thanks Jack https://www.youtube.com/watch?v=WGsyXlgSxFk&t=29s&ab_channel=JackRosenthal) and flashrom.

EC shows [1.170391 MKBP not cleared within threshold, toggling]

[2.240188 MKBP: the AP is failing to respond despite being powered on]

CPU UART shows a "system halt"


Nothing has powered up from the display after this.

Vadim Bendebury

unread,
Apr 10, 2023, 11:52:44 AM4/10/23
to cheng...@hotmail.com, ChromiumOS Discussion
Do you by any chance have the output of `cat /etc/lsb-release` collected on that device when it was still booting up Chrome OS?

Or maybe a photo of the back panel with all information on it? It's hard to find  matching firmware based on the Amazon link above.

-vb


--
--
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

james cheng

unread,
Apr 10, 2023, 12:48:07 PM4/10/23
to ChromiumOS Discussion, Vadim Bendebury, ChromiumOS Discussion, cheng...@hotmail.com
The device is in a bricked state and unable to issue commands like "cat /etc/lsb-release". But if I remember correctly,  the OS files should be using something like "32 bits ARM eabi binaries". 

The picture of the back panel are in the attachment

-jc
Image.jpeg
Image1.jpeg

Peter Marheine

unread,
Apr 10, 2023, 8:21:22 PM4/10/23
to cheng...@hotmail.com, ChromiumOS Discussion, Vadim Bendebury
The Acer CB311-11H is a "kenzo". You can download a recovery image from https://chromiumdash.appspot.com/serving-builds?deviceCategory=ChromeOS (search for "kenzo" and use one of the "Recovery Images" links on the right side), which contains firmware.

The recovery image is a GPT disk image; if you mount the ROOT-A partition, then you can extract files from the chromes-firmwareupdate zipball:

> gdisk -l chromeos_15329.44.0_jacuzzi_recovery_stable-channel_mp-v7.bin
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk chromeos_15329.44.0_jacuzzi_recovery_stable-channel_mp-v7.bin: 7392260 sectors, 3.5 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): 4693C16C-61A3-8942-AD41-6E344E622DD6
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 7392226
Partitions will be aligned on 1-sector boundaries
Total free space is 4073 sectors (2.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1         7020544         7392211   181.5 MiB   8300  STATE
   2              69         1048644   512.0 MiB   7F00  KERN-A
   3         1286144         7020543   2.7 GiB     7F01  ROOT-A
   4         1048645         1114180   32.0 MiB    7F00  KERN-B
   5         1282048         1286143   2.0 MiB     7F01  ROOT-B
   6              65              65   512 bytes   7F00  KERN-C
   7              66              66   512 bytes   7F01  ROOT-C
   8         1118208         1150975   16.0 MiB    8300  OEM
   9              67              67   512 bytes   7F02  reserved
  10              68              68   512 bytes   7F02  reserved
  11              64              64   512 bytes   7F03  RWFW
  12         1150976         1282047   64.0 MiB    EF00  EFI-SYSTEM
> sudo losetup -o $((1286144 * 512)) /dev/loop0 chromeos_15329.44.0_jacuzzi_recovery_stable-channel_mp-v7.bin
> sudo mount -o ro /dev/loop0 /mnt
> 7z l /mnt/usr/sbin/chromeos-firmwareupdate
7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,72 CPUs Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz (
50654),ASM,AES-NI)

Scanning the drive for archives:
1 file, 24065082 bytes (23 MiB)

Listing archive: /mnt/usr/sbin/chromeos-firmwareupdate

--
Path = /mnt/usr/sbin/chromeos-firmwareupdate
Type = zip
Physical Size = 24065082
Embedded Stub Size = 6286

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2023-03-08 08:24:20 D....            0            0  images
2021-09-15 09:50:26 .....       524288       224957  images/ec-cozmo.ro-2-0-8998.rw-2-0-8998.bin
2022-10-24 13:40:10 .....       262144       178038  images/ec-burnet.ro-2-0-2769.rw-2-0-2769.bin
2023-03-08 08:24:24 .....      8388608      1794540  images/bios-willow.ro-12573-342-0.rw-12573-342-0.bin
2021-11-04 03:46:18 .....       524288       239452  images/ec-pico.ro-2-0-9001.rw-2-0-9001.bin
2021-03-02 14:57:56 .....       262144       171340  images/ec-cerise.ro-2-0-2672.rw-2-0-2672.bin
2022-10-24 05:40:12 .....       262144       176973  images/ec-juniper.ro-2-0-2769.rw-2-0-2769.bin
2021-09-29 17:54:02 .....       524288       239438  images/ec-pico.ro-2-0-9000.rw-2-0-9000.bin
2023-03-08 08:24:24 .....      8388608      1787683  images/bios-cerise.ro-12573-209-0.rw-12573-209-0.bin
2020-04-01 14:28:30 .....       262144       171654  images/ec-jacuzzi.ro-2-0-2509.rw-2-0-2509.bin
2023-03-08 08:24:24 .....      8388608      1801342  images/bios-juniper.ro-12573-342-0.rw-12573-342-0.bin
...

It looks like kenzo uses the juniper firmware, so your firmware image is bios-juniper.*.bin.

Vadim Bendebury

unread,
Apr 10, 2023, 9:00:24 PM4/10/23
to Peter Marheine, cheng...@hotmail.com, ChromiumOS Discussion
Thank you for chiming in, Peter, I was still trying to figure out what board CB311-11H was.

In addition to your recommendation, maybe a faster way to get access to firmware images once the root partition is mounted is to run

mkdir /tmp/unpack
/mnt/usr/sbin/chromeos-firmwareupdate --unpack /tmp/unpack

and then look for the bios in /tmp/unpack/images directory

-vb

james cheng

unread,
Apr 10, 2023, 11:31:39 PM4/10/23
to ChromiumOS Discussion, Vadim Bendebury, cheng...@hotmail.com, ChromiumOS Discussion, Peter Marheine
Nice insight, I am finally able to unbrick this laptop and booted up to the recovery screen. The issue turns out to be the EC firmware and I still need to figure out where it went wrong in the upstream source. Thank you, Vadim and Peter, for your suggestions. And I appreciate your time for posting. I will update you if I have any findings. :)

-jc
Reply all
Reply to author
Forward
0 new messages