Updating to future USB updates from HC "User-Debug" leak

[publicanimal]

Cool, thanks. I'm not a developer, but I've been rooting and ROMming Android devices for a while (Motorola Droid + Motorola Xoom), these were both relatively "unlocked" devices and easy to modify. I don't really understand what it means for an update.zip to be "signed", but I know that there are some apps available that do apk/zip signing.

I am wondering if it would be possible to edit the user-debug update.zip by adding a /system folder to it and putting the su binary in /system/bin and the Superuser.apk in /system/app. Then edit the updater-script file in META-INF to extract the files from the /system folder at the end of the update. Now would it be possible to use one of these zip signing apps to sign the update.zip and install it in recovery to achieve root?

I almost tried this myself but made myself stop since I don't really have enough expertise and I would rather not brick my Revue. It's frustrating not being able to achieve full root access since I am used to having it on all of my Android devices.

EDIT: I'll note that a less crude solution would be to "root" the system.img and/or boot.img from the update.zip, then add the rooted images to the update.zip and re-sign it. But I'd be way out of my league when it came to doing that. So I guess my ultimate question is whether or not it's possible to duplicate the signature needed to re-sign a modified version of the update.zip. I'm guessing that it's not, otherwise this already would have been done, but I'd like to keep my naive dream alive that I can root this thing without a hardware mod.

[zenofex]

Cool, thanks. I'm not a developer, but I've been rooting and ROMming Android devices for a while (Motorola Droid + Motorola Xoom), these were both relatively "unlocked" devices and easy to modify. I don't really understand what it means for an update.zip to be "signed", but I know that there are some apps available that do apk/zip signing.

When I say the update.zip is signed I mean that the .zip file has a special hash in the comments section that is generated by getting a sha1sum of the .zip file contents, then using that sha1sum hash along with a RSA private key to generate a new hash which is then used to verify the .zip file has been unchanged. The box uses the private key along with a public key which is on the box to retrieve the sha1sum and then compares that to the actual sha1sum of the .zip. If both the sha1sums match then the update is allowed to proceed with further signature checks (which are done on each file inside the .zip).

In other words, unless there is a problem with the revue's implementation of the signature checks or we have the private key. Using this method to "root" the revue will not work.

Thanks,
Zenofex

[Epimetheus]

The official Android 3.1 OTA update will come soon.. I'd advise everybody to wait on this update. Yesterday, I've installed the beta and now I'm not sure if I'll receive the official update... Please be patient another week and you'll have it

http://www.logitech.com/en-us/smartTV/revue

http://blog.logitech.com/2011/12/07/log ... ech-revue/

[publicanimal]

The official Android 3.1 OTA update will come soon.. I'd advise everybody to wait on this update. Yesterday, I've installed the beta and now I'm not sure if I'll receive the official update... Please be patient another week and you'll have it

http://www.logitech.com/en-us/smartTV/revue

http://blog.logitech.com/2011/12/07/log ... ech-revue/

Thanks for letting us know. For those of us who were impatient, thanks to this thread we'll still have a path to the official update. I'm curious to find out whether or not the official OTA supports the sideloading of apps.

[pbiancardi]

So at this point if we want the official update we have to wait for it to be posted here, follow these instructions to get back recovery mode, then install the official update same way we installed the debug?

[publicanimal]

So at this point if we want the official update we have to wait for it to be posted here, follow these instructions to get back recovery mode, then install the official update same way we installed the debug?

You are correct sir.

[micl9]

Hey All - Official update is out!
Now we just need it to be posted

[manoller]

Anyone try to update yet?

[hellasleeper]

Have not gotten the update option to populate yet. Waiting for the OTA official release to be uploaded on the net somewhere so I can update manually. How will I access recovery menu with this image that I pushed into the box? Any word on the manual update being ready online soon?

[parrotheadmjb]

Have not gotten the update option to populate yet. Waiting for the OTA official release to be uploaded on the net somewhere so I can update manually. How will I access recovery menu with this image that I pushed into the box? Any word on the manual update being ready online soon?

No word on the manual update being online; it hasn't hit any revues yet. Gotta hit a revue with OTA, somebody has to snatch the update.zip then upload it; we're waiting for logitech to push the update... nothing to do til then.

this should get you into recovery

$ adb connect <revueIPhere>
$ adb reboot recovery