What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

ALERT! 2.2 FroYo Circus continues...FRG01B is Official get it here.

Very tempted but can't bring myself to do this manual update. Not sure why, I have been a computer/software/tech professional since before some posters here were born but just can't do it. It's probably due to the fear of missing something important from Verizon if I don't play by the rules. My phone is an indispensable tool for me. I have no problem being patient, my temptation comes from the idea of having a clean load. And after reading this whole thread and some posts in the android forum I still do not completely understand the genesis and composition of this file. We are told that it is the same file that came in the OTA with some different scripts (created by whom?) to apply the upgrade. We are told that the OTA patches the OS while this file is a complete install. So how are they the same file? Does the OTA contain the complete install but the scripts that come with it pick and choose which files to install while the scripts on the OP file install all the files?
Although I am very experienced with software I am pretty ignorant of Linux and Android so I am just not getting this. I understand the windows analogy but on the other hand I am told that the android OS does not deteriorate over time or leaves garbage behind like windows does, so how then is this "clean install" better than the OTA?
Sorry for all the questions, I have an idle mind right now :)
You're not the first person to wonder, so here's the best answer we can give to you or anyone who asks, without getting into too much technical detail that might confuse or, at the very least, bore the crap out of anyone who reads it:

The larger update, linked to in the OP, was built by Motorola (just like the smaller one) to allow Verizon techs to recover phones corrupted by the earlier install. This is theory, but seems to fit the facts. The signature is the most important part, but more on this later.

The smaller file is the one being pushed out OTA. It works, but has had a higher reported percentage of borked installs, many of which have been corrected by installing the larger file over the smaller one. A lot of people, all more skilled and possibly smarter than me, have looked into the guts of the larger file and have declared it clean of malicious intent; indeed, the signature alone would indicate it's clean. Nobody has yet discovered a way to sign an update.zip so it would work with the stock recovery. Hopefully nobody ever will or a lot of people are suddenly in danger of having their phones hijacked.

It's not the "same" file in the same way brothers or sisters are not the "same" person. However, they do the same thing as far as the end user and Verizon are concerned. They install FRG01B. One does it in a method that leaves less room for trouble while the other requires less bandwidth to push out to the end users, most of whom are still unaware there's an update being pushed, let alone what it is and why it's important.

Patience is important. However, keep in mind that there's no guarantee that the OTA when it hits your phone won't mess it up. Verizon will replace it at that point, yes, but if you push the manual install onto your phone and it messes up, they'll do the same thing because it's all their software. :) The reason for the smaller update being the one pushed out OTA is to minimize the impact to Verizon's 3G network as this is a MAJOR rollout.

Whenever you patch something big like this, as I'm sure you're aware, you modify code inside some files and replace others. The problem comes in when you're trying to modify so many files at the same time that bit errors creep in. Get enough of those and the error correction capabilities are overwhelmed and the system can't keep up. This results in lag in varying severity, and in the worst cases force-closure issues and even boot loops. The "cleaner" install overwrites, installing clean code everywhere instead of leaving parts behind that might have been corrupted at an earlier date for whatever reason. It's "cleaner" and "fresher" and results in fewer "wrinkles" for the end user to do it this way. It just cost Verizon more, and their number crunchers probably figured that replacing X number of phones was cheaper than loss in revenue that would have resulted in rolling out the larger file. This last part is pure conjecture but also fits the facts.

Cleaner, fresher, and fewer wrinkles. This is the first time I've ever heard of FroYo being used as a fabric softener. ;)

If you want to wait, please do. If you have further questions or concerns, please ask. We will be happy to help you as best we can. I hope this has been informative. :)
Thank you for the long explanation, it was indeed informative. What was confusing me was some people saying that this is the same file being pushed OTA but with different scripts. What you are saying is that they are not the same files at all, they are only the same in terms of the end result (installing FRG01B). The origin of this file is still a bit of a mystery; according to John Galt he got it OTA from Verizon. However it is a different OTA file from what everybody else got (exept from maybe one more person that John galt mentions). Note that I am not questioning that fact since he is a trusted member of the android community, it is just the hidden detective in me trying to figure it out. Perhaps the best assumption would be that this file was sent OTA to John Galt by accident or mistake, instead of getting the same file as everybody else he got this special "master" file. I can live with that.
I do not question the legitimacy of the file or the experience of so many forum members who have found it to be good. I will probably give it a try tonight, it is just that my inquisitive mind will not leave me alone on this type of thing, I kind of like tying up the loose ends, one of my many quirks ;)
 
The larger update, linked to in the OP, was built by Motorola (just like the smaller one) to allow Verizon techs to recover phones corrupted by the earlier install. This is theory, but seems to fit the facts. The signature is the most important part, but more on this later.

The smaller file is the one being pushed out OTA. It works, but has had a higher reported percentage of borked installs, many of which have been corrected by installing the larger file over the smaller one. A lot of people, all more skilled and possibly smarter than me, have looked into the guts of the larger file and have declared it clean of malicious intent; indeed, the signature alone would indicate it's clean. Nobody has yet discovered a way to sign an update.zip so it would work with the stock recovery. Hopefully nobody ever will or a lot of people are suddenly in danger of having their phones hijacked.

It's not the "same" file in the same way brothers or sisters are not the "same" person. However, they do the same thing as far as the end user and Verizon are concerned. They install FRG01B. One does it in a method that leaves less room for trouble while the other requires less bandwidth to push out to the end users, most of whom are still unaware there's an update being pushed, let alone what it is and why it's important.

Patience is important. However, keep in mind that there's no guarantee that the OTA when it hits your phone won't mess it up. Verizon will replace it at that point, yes, but if you push the manual install onto your phone and it messes up, they'll do the same thing because it's all their software. :) The reason for the smaller update being the one pushed out OTA is to minimize the impact to Verizon's 3G network as this is a MAJOR rollout.

Whenever you patch something big like this, as I'm sure you're aware, you modify code inside some files and replace others. The problem comes in when you're trying to modify so many files at the same time that bit errors creep in. Get enough of those and the error correction capabilities are overwhelmed and the system can't keep up. This results in lag in varying severity, and in the worst cases force-closure issues and even boot loops. The "cleaner" install overwrites, installing clean code everywhere instead of leaving parts behind that might have been corrupted at an earlier date for whatever reason. It's "cleaner" and "fresher" and results in fewer "wrinkles" for the end user to do it this way. It just cost Verizon more, and their number crunchers probably figured that replacing X number of phones was cheaper than loss in revenue that would have resulted in rolling out the larger file. This last part is pure conjecture but also fits the facts.

Cleaner, fresher, and fewer wrinkles. This is the first time I've ever heard of FroYo being used as a fabric softener. ;)

If you want to wait, please do. If you have further questions or concerns, please ask. We will be happy to help you as best we can. I hope this has been informative. :)

Based on this wonderful explanation, I decided to give it a shot.

Changed name, moved into sd card and followed instructions on installing. First thing I saw was

e:/can't open/cashe recovery command

It then installed and mostly running. Somethings aren't up yet, but the whole thing took about 6 minutes. I verified and have 2.2.

Thanks. :icon_ banana:
 
Adding to the mystery. On PeterAlfonso's blog John Galt said this:
"BTW - more users (including myself again) are getting this same file as an OTA update right now, as we speak. The time stamp on the .ZIP file is 11 Aug 12:53:56 on my phone, but all the hashes match up 100%."
Any chance people are now getting this "complete" install in the official OTA?
 
Adding to the mystery. On PeterAlfonso's blog John Galt said this:
"BTW - more users (including myself again) are getting this same file as an OTA update right now, as we speak. The time stamp on the .ZIP file is 11 Aug 12:53:56 on my phone, but all the hashes match up 100%."
Any chance people are now getting this "complete" install in the official OTA?
Always a chance. :)
 
Thank you for the long explanation, it was indeed informative. What was confusing me was some people saying that this is the same file being pushed OTA but with different scripts. What you are saying is that they are not the same files at all, they are only the same in terms of the end result (installing FRG01B). The origin of this file is still a bit of a mystery; according to John Galt he got it OTA from Verizon. However it is a different OTA file from what everybody else got (exept from maybe one more person that John galt mentions). Note that I am not questioning that fact since he is a trusted member of the android community, it is just the hidden detective in me trying to figure it out. Perhaps the best assumption would be that this file was sent OTA to John Galt by accident or mistake, instead of getting the same file as everybody else he got this special "master" file. I can live with that.
I do not question the legitimacy of the file or the experience of so many forum members who have found it to be good. I will probably give it a try tonight, it is just that my inquisitive mind will not leave me alone on this type of thing, I kind of like tying up the loose ends, one of my many quirks ;)

By mistake/accident/intent of someone on the inside trying to help the community out, we don't know. But it works, works well, and that signature is impossible (we think) to fake. If someone found out a way and gave us an improved tool to update phones rather than seizing control in an attempt to take over the world, well, props to them. After all, world domination is MY bag, Pinkie. :D

As for the rest, I'm glad my explanation has helped a couple of people get it done early. The faster we get this done the faster Verizon can move on to the next update for the Droid, and we all can see what goodies await!
 
finally go that update this morning in nj. i wonder if the circus is finally over. anyone out there that has not received it.
 
I guess someone gets to be first, while someone has to be last. I must be on the last list. No Froyo for me

Me too, although if I don't have it by the end of today, I think I am going with the file in the OP. My friend here at work did it yesterday so that leaves 3 (that I know of) in southeast Louisiana.

No comments on my post from yesterday about another halt to the OTA update and that this will not be done by the 18th as has been mentioned several times before? Can anyone confirm that?
 
ive been reading that it will be done on the 18th for the past week. yesterday i was at verizon and the tech guy said he heard nothing about that and it could take weeks. ive also heard 100,000 updates a day. figure its been what 10 days now. so who knows how many droids are out there. i have been watching this forum for days with updates about 2.2 and i dont recall reading about anyone receiving the update after noon. so you still got a few hours left.
 
Back
Top