Help! I bricked my HD200 while applying beta firmware

[El Jeffe']

So, I think I just made a big mistake by updating my HD200 to the latest beta firmware. Ever since I received my HD200, I've updated it with the latest beta firmware immediately upon release and I've had great results until tonight. I just attempted to update from 20090616 0 to 20090626 0. After the HD200 rebooted, I noticed that the box was sluggish. Then, I attempted to play a recent recording from my sage box and the video was in slow motion and there was no audio at all. I tried a few more SD and HD recordings and they all looked the same. Not good!
Next, I thought that I'd attempt to roll back to the 16 June 09 firmware. First, I attempted to use the USB recovery method and no dice. The HD200 reported that the USB stick didn't contain a firmware update. So, I rolled back to the latest stable firmware (30 December 08) and tried to roll forward using the USB method. This time, the keystroke combination needed to activate the USB method didn't work at all. I pressed 872 multiple times and...nothing. Next, I tried to move forward to the 16 June 09 version by using the server PC recovery method. Bad idea! I tried the procedure, the lights blinked, I've let it sit for 30 minutes so far and I'm still at a blank screen. Uh oh... Anyone have any ideas?

[El Jeffe']

Well, I waited a little while longer and the HD200 eventually recovered. I guess when they say "This process could take a while", they mean a REALLY long while. I apologize for posting prematurely, but there still seems to be something amiss with the latest beta firmware (at least with my configuration).

[freedml]

With Sage there are things that happen at startup that you don't know are happening which can severely affect performance. Sage really needs to watch and reduce system resource useage of these routines AND give the user some warning that they are going on.