I can't recover my chromebook

[Raphael Kanakotov]

Hello everyone, today I encountered the problem "wasp chrome is missing or damaged". I created a system image using a chromebook recovery utility, but when I tried to restore the system, I was told that the system was out of date, I was trying to install a stable channel. I have already tried installing the Dev version, but in the end the option is the same. When I try to install with Dev mode enabled, but again without result. Please help me... My HWID "DROID"

[Mike Frysinger]

fairly certain HWID of "DROID" is incorrect and you need to start with fixing that.  it kind of implies you changed the firmware.

-mike

On Mon, Feb 24, 2025 at 10:48 AM Raphael Kanakotov <harienko...@gmail.com> wrote:

Hello everyone, today I encountered the problem "wasp chrome is missing or damaged". I created a system image using a chromebook recovery utility, but when I tried to restore the system, I was told that the system was out of date, I was trying to install a stable channel. I have already tried installing the Dev version, but in the end the option is the same. When I try to install with Dev mode enabled, but again without result. Please help me... My HWID "DROID"

--
--
ChromiumOS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss

[DennisLfromGA]

Raphael,

 
Thanx for posting here.

Since you're original post on the forum I've run into one other user with an 'octopus / blooglet' device, one with a 'hatch / akemi' device, and one with a 'nautilus / nautilus' device all giving the error message "You are using an outdated ChromeOS recovery image." 

One of the users above was able to look at the recovery.log file and found the error stating 'the firmware wants kernel version 5 when the recovery image has kernel version 4.' so I think that's key in likely all of these issues. I don't know if something changed in the Chromebook Recovery Utility extension or if it's the recovery images themselves that's causing this error, hopefully a dev will drop by and help out.

~DennyL

[DennisLfromGA]

Mike,

I had the advantage of seeing Raphael's screenshot showing an 'octopus' board with a 'droid' HWID so I'm pretty sure they're using the correct recovery image.

name=Acer Chromebook 314 (CB314)
hwidmatch=^DROID [A-C][0-9][^N]-.*
file=chromeos_16093.86.0_octopus_recovery_stable-channel_mp-v35.bin

~DennyL

[DennisLfromGA]

UPDATE: 

Two users, one with an 'octopus / blooglet' device and one with a 'hatch / akemi' device were both able to successfully complete a recovery with the oldest stable M125 recovery image for their devices so that may be a workaround for this issue.

You can find downloads of earlier versions for your devices at either of the sites linked below:

• https://chromiumdash.appspot.com/serving-builds?deviceCategory=ChromeOS
• https://cros.tech/

After downloading them use the Chromebook Recovery Utility extension's 'Use local image' option for the recovery.

And hopefully, they will update on their own after the recovery to the latest stable version.

~DennyL