Apparently you have to be logged in as root in VT-2 for crap to work, but I’m not sure how to do that. (I did follow the instructions for getting into developer mode precisely. I did not enable debugging features.)
I’ve read this topic which seems to be about the same issue.
The answer specifically points not enabling Chrome OS debugging options, but the Chrome OS docs seem to imply that you do have to enable debugging features in order to login as root.
The problem is that I can’t login as root, and if I follow the instructions on the developer mode article on MrChromebox.tech, it never asks me to set a root password. I’ve tried “test0000” and entering no password at all, but that doesn’t work.
I assume I have to enable debugging features in order to set a root password, but the MrChromebox article explicitly mentions not to do that.
Interesting. After power washing, I was able to login as root without a password, but after I ran chromeos-setdevpasswd I was unable to login as root again, and the password I set didn’t work. (It works for the chronos user)
The chromeos-setdevpasswd script writes to a file in the stateful partition that’s formatted like /etc/shadow. Adding another entry for root seems to work.
You do not need to login as root. If you want to run the firmware-util.sh or anything else, using chronos is enough, but you have to be in the vt2 shell (not crosh) to run sudo as chronos.
crap (the partitioning tool) does not work under sudo as chronos. It apparently requires root login (I’m not sure why)
For that matter, I actually wasn’t able to get crap working in vt2 (both when logged in as root (by changing the passwd file) and through sudo). I just ran it on a live linux usb