so...we all waiting patiently (and not so patiently) for the update to finally come. zenofex posted the location to the .zip containing the update.
here is my question. why did it brick so many 2.1 revues? like..this was the official update. wasn't it geared for 2.1?
also...how is it that the users on the debug build that DID NOT FIX THE RECOVERY were able to update ota? not because logitech was trying to block them or something but without a properly working recovery...how did the update flash with a botched recovery.
one more question. did the ota flash a new working recovery or is it the same recovery that came on the first 3.1 leak?
question pertaining to the way the update got rolled out.
Moderator: Revue Mod
-
- 1.6 Donut
- Posts: 146
- Joined: Mon Aug 08, 2011 8:14 pm
- GTV Device Owned: Logitech Revue
- Location: New Jersey, SEVEN3II
question pertaining to the way the update got rolled out.
HTC one s - cm10 jellybean unofficial
T-mobile g1 - cm6
T-Mobile g2- andromadus ics beta
T-Mobile hd2- cm9 by tytung
HP touchpad- CM9 alpha 2
Logitech revue- OTA downgrade 3.1
Member xda forums
T-mobile g1 - cm6
T-Mobile g2- andromadus ics beta
T-Mobile hd2- cm9 by tytung
HP touchpad- CM9 alpha 2
Logitech revue- OTA downgrade 3.1
Member xda forums
Re: question pertaining to the way the update got rolled out
I think that the user needed to update the User-debug before the final update if they were to use that method.