• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

People about to do update

I have not received notification of the OTA yet, but I am attempting to get things set up to share when I do. I downloaded HTC Sync, and my phone is mounted.
This SDK thing seemt to take quite a while to set up though.
 
good luck, now its a waiting game...come on verizon
any confirmations from eris owners in arizona (phoenix specifically) getting an update????
 
So I downloaded SDK and it was failing to retrieve some URL. So it said to go in to settings and force it.
I did that, and setup seemed complete until now I am waiting as it downloads revisions...whatever that means. But it seems like it will be a long process. Im pretty annoyed right now, as I know I will find this program useless otherwise once the OTA is shared.
 
Seems that way. Or at least not long after anyway. I think everyone will have OTA by the time this stupid SDK gets finished installing on my PC.
 
I think Im giving up on this SDK crap. It was downloading and installing all these revisions for Android 2.1 and 2.0 and 2.0.1, and got to downloading things that were obsolete. I cllicked cancel there thinking I shouldnt need that obsolete stuff, and apparently the setup wont finish without everything.
So I went back in hoping I could re-start from where I left off since things were already installed, but it started downloading everything from scratch again.
Sorry people, but Im going to leave it to someone else. I dont have the patience.
 
Ok, thread break! Everyone go read a different thread for a little bit and calm down.

I don't really want to close this one.
 
The thing is that there still seem to be less than 10 people on these boards that have received the OTA.
Of those people, some received it before clear instructions were ever posted on how to share. Others understandably just didnt read through every page of these threads, and didnt know about logging at all.
And now myself, admittedly I ran out of patience with SDK. Not only because it was taking a long time to download and install unnecessary things on my computer, but the fact that I have no idea what I am doing with the program made it that much more frustrating.
Either way, I am stuck waiting for the OTA. It is of no benefit to me to share with anyone. I gave it a shot, but I am bowing out of the efforts.
 
When I saw the topic title, I immediately sang it in the style of AC/DC "For those about to rock"

So, to those about to update - WE SALUTE YOU! LOL.
 
T2noob said:
This is what we'll be looking for.

Quote:
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:

W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!

Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:


https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
Click to expand...

Ok looking at that known address containing the older update couldn't someone make educated guesses or brute force what they would use as the address for the new update? Now even though the components of that address don't really make sense to me im sure some of you might be able to pull information from that address that could be translated to what the newer one might be. Then again I could just be grasping at straws lol
 
Coolblue272 said:
Ok looking at that known address containing the older update couldn't someone make educated guesses or brute force what they would use as the address for the new update? Now even though the components of that address don't really make sense to me im sure some of you might be able to pull information from that address that could be translated to what the newer one might be. Then again I could just be grasping at straws lol
Click to expand...

The part we don't know is the replacement for "7b1e5cca". It's a hexadecimal 32-bit number, so there are 4,294,967,296 possible combinations. I don't think brute force will be fast enough to find it. The one thing we know about that code (assuming it's exactly like the previous ones) is that it's equal to the first 8 characters of the SHA-1 hash for the ZIP file. Unfortunately, without the ZIP file, we don't know the SHA-1 hash. And of course, if we had the ZIP file, we wouldn't need to find it.
 
nope...we may need the other part too...to replace the 104882 part. OR they could have a completely new name for it and location for that matter.

And I said nope because I tried the other path with your replacement and it came up not found.
 
ghoover said:
nope...we may need the other part too...to replace the 104882 part. OR they could have a completely new name for it and location for that matter.

And I said nope because I tried the other path with your replacement and it came up not found.
Click to expand...

I'm assuming the 104882 would be replaced with 165907. That's the CL number in both cases. Anyway, I tried with "165907.8a03cb9a" before I figured out that the 7b1e5cca from the MR2 link was actually from that file's SHA-1 hash, which we don't have for MR3.
 
You must log in or register to reply here.
Back
Top Bottom