Bricked Chromebook Lenovo 500e after attempting ChromeOS system recovery with wrong image

System Details

  • Device: [ROBO360]
  • OS: [ChromeOS]
  • Firmware Type: [RW_LEGACY]
  • Firmware Version: [Google_Coral.10068.82.0]
  • Internal storage type: [eMMC]

Summary of the Issue

I used a Chromebook (Robo360) with Linux installed on it. But after installing Full UEFI with MrChromebox script this specific model didn’t manage very well low battery situations - it depleted to zero and then didn’t want to boot nor charge. So I recovered the ChromeOS from USB, it went well. Then I played with it a bit, messed up a bit, then wanted to start fresh again and run recovery again, but this time I used Chrome recovery tool to prepare USB, chose “Lenovo 500e” and it seems to have been a wrong image (there are some others 500e…).

Now it is in a bootloop (screen lights up for a second, goes black, repeat). I can only enter recovery screen, it allows me to introduce a recovery USB, the process seems to recover with success (correct image this time, ROBO360), but it doesn’t help.

OS verification is off. Can’t enter developer mode, legacy boot, anything except Recovery.

Is there anything I could do now?

I read a post from MrChromebox about modyfing chrome install script in the recovery image, but the post is from 8 years ago.

Thanks

it’s simply not possible to recover using the wrong image, the recovery system will reject if it’s not an exact match

Thank you for the answer. Then it must be something else, the issue appeared directly after recovering the image prepared with chrome recovery tool, which recommended to “search for ROBO360”, but it wasn’t available on the list, so I chose Lenovo 500e. Previous restoring with manually prepared USB worked fine. Since then I tried recovering again from different USB sticks, with no success.

ROBO360 is in the list, the recovery utility is just stupid - sometimes you have to add a space or a dash for it to find the correct image.

I would try an older recovery image:

just search for robo360

Maybe I wasn’t very clear, but I got the correct ROBO360 recovery image and flashed it, few times actually, but it is still in bootloop after successfully recovering the image.

and again, I’m suggesting you try an older image

Sorry for not specifying it, I had tried few of the images. the oldest being recovery image 118. With that oldest one I got a message about recovering out of date Chrome OS image being allowed because verification is off, but then after few minutes “an unexpected error has occurred”, no more details. The newer ones (including recovery image 120) didn’t result in that error, but didn’t fix the problem either.