the output shown before running vboot_twostop looks normal to me. it's how i've configured my device. but when i run vboot_twostop, it tails into the normal payload and i get the dev mode screen. i suspect you've broken your firmware so it crashes when it tries to run.
you did make a backup of your firmware like that page (and pretty much every one out there) told you to right ?
if you get a SD card, you should be able to install linux onto it and then boot it. if it has a uImage, it'd be something like:
set bootargs root=/dev/mmcblk0p1 rw loglevel=7
ext2load mmc 0:8 ${loadaddr} uImage
bootm
then you can get a root prompt to try and recover the firmware.
note: no ARM chromebook has SeaBIOS as it makes no sense -- SeaBIOS emulates a legacy x86 BIOS. you're on a CPU, so there is no such system. if anything, u-boot (what you're already in) is the "legacy" boot mode.
-mike