**This assumes that you already have the Android SDK/ADB setup on your computer** These instructions are chronological in the order they should be done.
****WARNING**** You do the following steps at your own risk, and I nor gtvhacker.com hold any liability for any damage that can/may be caused by doing so.
On your PC
01. Hold down the WINDOWS key and press the R key.
02. In the run box that popped up, type CMD then press the OK key.
03. In the terminal windows that opens up, type IPCONFIG and press the ENTER key.
04. Write down your PC's IP ADDRESS (it's called the IPv4 address, and usually starts with 192.168.).
On Your Revue
05. Press the HOME button.
06. Press the MENU button.
07. Navigate down to SYSTEM SETTINGS and select it.
08. Select NETWORK.
09. Navigate down to NETWORK INFORMATION.
10. Write down your Revue's IP ADDRESS (everything before the /).
11. Press the BACK button x2.
12. Navigate down to APPLICATIONS and select it.
13. Navigate down to DEVELOPMENT and select it.
14. Select REMOTE DEBUGGING to where it is CHECKED.
15. Navigate down to DEBUGGER IP ADDRESS and select it.
16. Type in your PC'S IP ADDRESS in the text field, then select SET
17. Navigate down to ALLOW MOCK LOCATIONS and select it to where it is CHECKED.
18. At this time you can navigate out of the Settings menu.
On Your PC
19. In the terminal window, type ADB CONNECT <YOUR_REVUE_IP_ADDRESS>:5555 then press the ENTER key.
(keep in mind that there are spaces between adb, connect, and the start of the ip address. Also, directly after your revue's ip address is a colon (:) then 5555, so an example would be 192.168.1.1:5555)
20. In the terminal window, type ADB SHELL then press the ENTER key.
You should now see a $ with a blinking cursor. You are now navigating your Logitech Revue via ADB!
Edit 01: ****WARNING**** Do not try to reboot into recovery via adb. I tried this, and although it rebooted the Revue, it would not load up (the first splash started flashing sporadically , and took a power pull restart while holding down the sync button on the back to get it back). I don't know if it's using a different recovery protocol or what.
Edit 02: Title edited to be more understandable with the purpose of this post.
Last edited by mrandroid
on Thu Aug 11, 2011 5:50 am, edited 1 time in total.