Bogus file ownership won't prevent you from booting in single-user mode. And once you boot in single-user mode, you're running as root so you can change file ownerships back.
I suppose he could have tried remounting the device read-only, and then using dd to directly update the inode table to change ownership, but, if he was already root, he could have just chown'ed it again.
As root, typed in chown -R nobody:nobody / some/dir/somewhere/
Ended up having to re-image the system. We still give him a hard time about it.
Now I'm wondering if he could have tried to find a more creative solution as displayed in TFA.
Thoughts?
Edit: He hard killed the box right after he typed that in.