Sadly probably not. A small patch limited to flash readiness and minor security update ..
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!
OFFICIAL FRG22D OTA patch is here. DOWNLOAD NOW!
- Thread starter cereal killer
- Start date
Sadly probably not. A small patch limited to flash readiness and minor security update ..
furbearingmammal
Super Moderator
Yup. Very simple thing to do, but if it doesn't fix the issues you'll need to take the phone back to Verizon.
First things first, make sure you have 60% battery if your phone is plugged into a power source (USB/computer or wall charger) or 80% battery if it's not.
Download this file:
http://androidoverdrive.com/pete/OEM/9046f5a3ec09.signed-voles-ota-45394.zip
Rename it update (if it asks you about changing the file extension, add .zip) so you have a file named update.zip even if you can't see the .zip. Mount your phone to the computer via USB Mass Storage. Copy the file to the root of the SD card -- the first window you open when you open the phone on the computer (there will be lots of folders, including one named Download) -- and then reboot your phone.
As soon as your Droid shuts down, but before the M appears, press the X on the keyboard and hold it until a triangle with an ! appears in it. Release the X.
At this point:
Press the volume up and camera button at the same time.
Using the d-pad (the square thing next to the keyboard) select “apply update.zip” and press the middle of the d-pad (gold-looking button).
Your phone will now attempt to install the update.
When it finishes, use the d-pad to select “reboot phone”.
Your phone will reboot with Android 2.2 unless something went wrong. If anything goes wrong, like a bootloop, you'll need to do a factory hardware reset. We can help you with that as well if needed. If something MAJOR happens to your phone, Verizon will replace it as long as you don't tell them you were trying to manually update your phone. The reason for this is, while this is appropriate (Why else would that option be there at all?), some people think it voids your warranty. Why take the chance?
Good luck and let us know if it works or if you need more help!
DesktopDevin
Active Member
Still waiting here, I usually get the update exactly at midnight of the Saturday night following of when the update starts.
That pattern has been broken with this update.
I thought it would come early because it is such a small update and thus not take as much time to get out to the phone.
Guess I was wrong but no big deal. :blink:
Hey Fur,
Thanks for putting the manual install info all in one place.
Sorry if this has been asked previously, but if we manually install, will the OTA attempt to overwrite it, or will it just not attempt? This is key for me, as Verizon *could* update the patch before they push it, and if so, I'd want the latest.
Thanks for putting the manual install info all in one place.
Sorry if this has been asked previously, but if we manually install, will the OTA attempt to overwrite it, or will it just not attempt? This is key for me, as Verizon *could* update the patch before they push it, and if so, I'd want the latest.
I manually updated both times the day they were posted on this forum and vzw hasn't hit me with any new updates.
PhoenixGTR
Member
I lost patience and did the manual update; no problem.
I am curious if another form of the OTA eventually turns up, though, like the patch and full versions of the 2.2 update B.
Sent from my Droid using Tapatalk
I am curious if another form of the OTA eventually turns up, though, like the patch and full versions of the 2.2 update B.
Sent from my Droid using Tapatalk
Did your Droid come with a restart button? With mine, after I shut it down, I had to turn it back on, while holding down the X key.
Im a dudette....and i'm sick of verizon's bull kaka.. don't need to be told manual is available. Its not about that. Snark elsewhere, svp.
You're not alone, Sal, and you're right, it's not about knowing there's a patch available to download manually.
It's been nearly 52 hours since a report came in that "I have an OTA update sitting on my phone this morning..." The image that accompanied it is and was also avaliable elsewhere in internal VZW/Moto/Google documents. That report was received only here in this thread and not in any other thread or forum anywhere. No one else anywhere on the Web has reported getting a live FRG22D OTA from VZW servers. Something smells fishy.
What I can say is what others who have loaded this patch have said. It runs nicely. In my mind it runs better than any leak that I've run before, and although I'm not convinced yet that it is *the one and only* official build that will be used by VZW in their OTA sends, I am convinced it's something official since it is on Google's open website... And I'm extremely glad to have it on board for now.
Again, though, it's not about that.
We still don't know a lot about the actual VZW OTA. This is like every other OTA that Verizon has done, it's a step forward and a few steps backward for a while as they get every piece together. As a career software developer, I have to admit that I'd rather pull something out of production and get it right, then deploy it to 3 million users in a bad state and get that many complaints -- even though delaying or pulling an OTA out of production is extremely embarassing. My user support people would hang me if I knowingly let serious problems be installed on this many users' systems.
From my standpoint, I've got plenty to play with while we all wait to see what happens. But I still need convincing, and the only way that will happen is when I see the VZW OTA servers churning out thousands of final Froyo updates to the Droid1 community. And then I'll want to see what that update has in it.
TheCrusher
Member
Are you suggesting that this person just grabbed an image from Verizon documentation and posted it here to annoy us? Seems unlikely. It seems to have Battery Status Pro running, and I doubt any official documentation would include extra apps.
Now if you were to suggest that someone would spend hours playing with Photoshop to make a convincing fake, and post it here just to annoy us, then I might be on board with your conspiracy theory.
furbearingmammal
Super Moderator
Let's not start with the paranoia and conspiracy theory stuff, folks.
furbearingmammal
Super Moderator
If the ping that's used to read your phone for updatability is different enough that it sees your version as "wrong" it will attempt to overwrite it. However, the worst this would really do if you're running stock is realign you with the official build and follow it with the other update. I haven't heard of anyone getting an OTA push after installing this update, unlike the one P3Droid released. That non-stock kernel he put in it seems to have been what was causing the foul-up.
So, in short, if the update is updated you'll get the new update because anyone who got the old update would require an update to their phones so they're running the latest official build. Hence another update would hit them.
SnoDrtRider
Member
Took the words right out of my mouth FBM... sort of.
I was going to post that if you do manually update using the "Official" file off of Googles servers and for some reason VZW changes the file to a different one in the push you can rest assured that once someone gets a true OTA straight from VZW there will be a hundred developers checking out the code to see if it is in fact the same as the one we are using currently (From Google) then it would just be a matter of updating again should the actual release be close enough that it would not automatically get pushed to a manually updated phone.
Or is that what you just said?