I was rebooting my chromebook because i disabled virtualization (and another but i forget)
and just stopped booting and i throught it was a hardware thing but i check and i didnt see nothing bad i tried to fix it with:
1-booting with battery and charger disconnected (didnt work)
2-booting with battery and charger (didnt work)
3- botting with only charger (didnt work)
i dont know how to fix it
I don’t know how you’d brick it just from changing settings, but changing things you don’t understand is a good way to end up in your current situation
Came here with the same question. Doing it for the first time, I disabled intel_me in UEFI settings and the chromebook was stuck in a loop with black screen and backlight going on and off. Solved it using SuzyQ using Arch Linux host with chromeos-flashrom-git and cbfstool packages. What I did:
flashrom -p raiden_debug_spi:target=ap -r bricked_backup.rom- this will read and save the ROM.
cbfstool bricked_backup.rom layout - look for SMMSTORE size in bytes, divide by 1024 and get the size in kB, in my case it was 512kB.
dd if=/dev/zero ibs=1k count=512 | tr "\000" "\377" > empty_smm.bin - write a file of the same size as SMMSTORE filled with 1’s (‘\377’ is octal representation of decimal 255 which has all 1’s in binary representation).
cbfstool bricked_backup.rom write -r SMMSTORE -f empty_smm.bin- overwrite SMMSTORE region with 1’s.
flashrom -p raiden_debug_spi:target=ap -w bricked_backup.rom - write it back.
Worked for me, maybe it will be useful for someone else.