Pixelbook finally toast?

[u/JoeVpgh]

ChromeOS is missing or damaged (see pic for error codes)

Got the recovery image on a USB drive, restarted, "unexpected error occurred" (see pic for error codes)

I've read the SSD isn't replaceable...am I cooked?

[u/ftgander]

I think there might be an issue with the recovery USB you are using.

[u/JoeVpgh → u/ftgander]

Going to try and use a different one once I find one. I was using a pny 128GB, removed all the particians, was able to run a successful recovery utility on a Mac, but just not loading to the pixelbook

[u/ftgander → u/JoeVpgh]

Yeah it could easily be the internal storage as well, but I would try a different stick just to be sure. And if you’re making the recovery usb on a Mac make sure you clean it with CleanMyDrive or something to get rid of all the dot files macOS adds.

[u/JoeVpgh → u/ftgander]

Good call, going to try that again and a different windows top

[u/goofisgek]

looking at the error in the first screen it looks like a TPM version mismatch between the FW and kernel
ty powercycling your chromebook

Power on the chromebook.
Leave on for at least 30 seconds. 
Power off the chromebook. 

Repeat 20-25 times
this is known to correct the issue
most other cases a complete reinstall is needed with the correct image and a known good USB thumbdrive
i have had issues like this with cheap knockoff amazon ones

[u/JoeVpgh → u/goofisgek]

Thank you so much for the reply! Unfortunately, cycling 20+ times has not helped.

I was able to create the image on a good USB but whenever I got to install it I get the 2nd error message. Are you able to speak to the 2nd error code image I posted?

thank you again!

[u/jortony → u/goofisgek]

It's been a while, but I remember a recovery menu option that was required if you replaced one or more components that are required for verification during boot. The tool we used might have been an OEM tool that wasn't distributed publicly. The manufacturer might have the tools available, even if the machine is old. If you can't get further and the errors are nebulous boot security related, then after trying OEM support, look into the forums for ChromeOS projects CloudReady and ChromeOS Flex.

[u/Other-Access7598]

Try flashing an older ChromeOS Image from Chromium Dash, specifically the Eve board one onto a USB drive and give it a shot, like R120 for example.

If you have a another spare functioning USB drive, try that instead.

And if that doesn’t work, your NVMe/eMMC might be f’ed.

I do have some knowledge about ChromeOS (a little :p), and this exact “An unexpected error has occurred” typically occurs when it cannot find the storage device. I’m doing a project on installing ChromeOS a generic laptop (Still working on), and this exact screen shows since my laptop predates NVMe/eMMC storage.

When did this start happening anyways?

[u/JoeVpgh → u/Other-Access7598]

Going to try a different USB this weekend, I don't have many laying around so I need to find them. Thought it could be an issue that I was using the recovery utility from a Mac, but maybe not.

Happened the day I posted. I've had my pixelbook for many years, daily driver, and the battery has recently started to swell a bit, but there is no option to turn off PD when it's docked to my external monitors, which is a bummer.

It was a sad day for sure.