Chromeboot stuck at recovery (NVRAM TPM initialization error)

[jardelsf]

Hi,

I was using mrchromebook UEFI full rom and Windows 11, but I decided to revert to stock rom and use ChromeOS and dual boot with Linux.

I’ve flashed back the original firmware using firmware script utility and all finish ok.

I’ve created the recovery media using Chrome extension and it installed with no errors, but every time it boots it stucks at these “Damage Chrome OS …” screen and a “0x2b / 0x2b Secure NVRAM (TPM) initialization error” message when meta key is pressed.

I’ve tried recovery the image several times and no success. Also tried restart more than 30 times and again, same screen over and over.

I’m thinking to buy a chromeos debug cable and try refresh the uefi firmware.

Do you guys think its possible?

My laptop is a Lenovo Yoga C630 Chromebook Intel i7 (pantheon).

[Xanaxx]

Did u fix it?

[jardelsf]

Not yet.
I’m (struggling) buying a SuzyQable to be able to flash a new UEFI rom.

[jardelsf]

Hello,

I bought a SuzyQable from China; eBay shipping to Brazil was very expensive.

Using this adapter and my Ubuntu system, I managed to reset the CCD to factory settings, so my Chromebook started booting normally again.

All I had to do was disconnect the battery from my Lenovo C630 and use minicom to run the commands:

‘ccd open’
‘ccd reset factory’

I also enabled TestLab:

ccd testlab enabled