According to the article, that wouldn’t work. I didn’t try it, of course, but according to the article:
“After the crash, the main program, bdpprog, is terminated by the kernel,” said Gray. “Since bdpprog is the main program, its termination results in a reboot by init. Even less fortunately for Samsung, the code for parsing the logging policy XML file is hard-coded to run at every boot. The result is that the player is stuck in a permanent boot loop as has recently been experienced by thousands of users worldwide.”
Because of the monumentally stupid idea of parsing a downloaded XML file unconditionally at every boot, there seems to be no way to recover the devices from the boot loop using normal means – such as a USB stick, CD or network – because the crash happens too early in the boot sequence.
He describes generally the kind of low-level access needed to prevent the sequence from happening. From the repair notice I got, it sounds like once Samsung’s techs were able to access the machine before the XML file ran, it was simply a matter of doing a factory reset with the new code.