Exploitee.rs

Below is a method to flash the old "un-neutered" HC recovery onto the new userdebug build. This will allow you to update by USB to the official HC build that Google will hopefully release in the coming weeks. The method below requires that you have installed adb from the android sdk. Please make sure to enter the commands below after entering the directory that the recovery.img was extracted to (or to change the "adb push recovery.img /tmp/recovery.img" command to "adb push /path/to/recovery.img /tmp/recovery.img").

Warning: Using any recovery other than a properly signed recovery will brick your box, only use the recovery supplied. You also may to ensure you have a good network connection to your revue before continuing.

Recovery:
http://www.mirrorcreator.com/files/14TS ... .zip_links
Note: recovery.img(sha1) = 14c31dc6db2d8f9ec15f94f2f929dbb68142d16c

Step 1.) Get IP Address of Revue (settings->network->status).
Step 2.) Enable adbd (settings->applications->development), then check "Remote Debugging".
Step 3.) Add the IP Address of the computer you are connecting from ("Debugger Ip Address in settings->applications->development).
Step 4.) Connect to adb from computer using the following (Replacing <ipaddresshere> with your ip) adb command:

adb connect <ipaddresshere>

Step 5.) Restart adbd as root by executing the following:

adb root

Step 6.) Reconnect to adbd on the revue using:

adb connect <ipaddresshere>

Step 7.) Paste each line of the following (one at a time).

adb push recovery.img /tmp/recovery.img
adb shell flash_image recovery /tmp/recovery.img

Successfully running the last line should output something similar to the following: When accessing recovery to update to a future build, you can just use the "adb shell reboot recovery" command and the Revue will reboot into recovery mode.

Posted on the wiki: http://www.gtvhacker.com/index.php/Upda ... ug%22_leak

Edit: Fixed old multiupload link.

Awesome. Worked great for me. Thank you

Will we still be able to receive the the update OTA,or is this the only way?.

is there any reason to do this until the official update comes out and we see if we can get OTA?

Don't get me wrong, this is awesome and I greatly appreciate the work. because of this I will probably bite the bullet and update.

THANKS

Thx for this!!!

Can some one post "sha1" of Honeycomb 3.1 UserDebug Leak???

for mp-signed-ota_update-b58801.15d88c27-t.zip file...

The reason for this, is if there are any releases that come out, or say for some unforeseen reason it doesn't do the OTA, then you can still flash it manually and get it back on track. That's my look on it. It should take an OTA update, but who's to say it will or it won't. I look at it as insurance

EvgeniX wrote:Thx for this!!!

Can some one post "sha1" of Honeycomb 3.1 UserDebug Leak???

for mp-signed-ota_update-b58801.15d88c27-t.zip file...

The sha1sum for that file is: 15d88c27df46338c10715f120b1e4b4ce757bfe3

cj_000 wrote: The sha1sum for that file is: 15d88c27df46338c10715f120b1e4b4ce757bfe3

Thx!! now all ready to flash...

gdeeble wrote:The reason for this, is if there are any releases that come out, or say for some unforeseen reason it doesn't do the OTA, then you can still flash it manually and get it back on track. That's my look on it. It should take an OTA update, but who's to say it will or it won't. I look at it as insurance

gdeeble is correct, we'd prefer to have a way for people to have the option to upgrade from the UserDebug build. Currently in the UserDebug build the recovery menu will never display due to the fact that the code to display it has been removed. This method flashes an old recovery onto the build (since UserDebug comes with root), and allows you to once again have the ability to update manually through usb. Our guess was that people were gonna be pretty angry if they were stuck on UserDebug when the official HC update is released from Logitech (Hopefully this following week).

Thanks,
Zenofex

I guess I didn't make my question clear enough.

Is there any reason to flash this NOW? as opposed to waiting to see if the OTA updates anyway? Then if it does not update over OTA couldn't we then flash this and flash the update manually?