The drivers for them will have to be included by Logitech in order for them to work. HC straight from Google would not add this needed support.

Had it happen to me from time to time. Not in a while however. Seems to clear itself up, so I'm assuming it's something on the other end rather then my device.

Disconnect everything from the Revue except the USB stick containing the update file and try recovery again. Remember that the key sequence is different to enter recovery after the first update. It's ALT-L now. If you can get in there again, try to reflash.

What specifically is the issue you are having with the TV & Movies? Also regarding the Market, I have had that same issue with apps never installing. It's hit or miss really. Got to remember, this was a beta leak and was meant to help discover/squash bugs.

That actually makes perfect sense. When the zip files are created, they're signed with a digital key that is verified by the system to ensure it hasn't been altered or tampered with. By you repacking it, the key was not present and therefore you received the error.

I've had the same issue and it's present in the 3.1 leaked builds. When the FC prompt comes up, select wait and usually after 15-30 seconds, the commands will become responsive again. I have actually had better luck using the Android remote app posted on here. Works 99.99% of the time.

Just to note that a few were removed in the 3.1 UDB leak.

gdeeble wrote:That would probably be due to the fact that they thought they could win by removing "recovery" from the leaks. That would be my guess.

They didn't remove it. They just removed the ability for user input while in recovery.

Interview with Rishi Chandra, Product Director of GTV, posted here that says users of the leaked versions will not be able to update and will have to buy another Revue. Referring to the OTA. Can't imagine it's locked from updating completely being that recovery is available.

Love the app btw. Running the 3.1 UDB and the IR commands are very laggy at times using the keyboard. Results in a lot of FC's. For some reason though, the remote app works 99.99% of the time.