OTA link

I'm pretty sure that Swype will not work with 2.2, nor will any task killers.

How do you know this? I use Swype, as many on these forums do, too. If Swype won't work on 2.2, I don't know if I want it...

And do I actually need to have a physical SD Card in my phone?

Thanks.
 
I was about to perform this..... but then i noticed my 3g activity was active for quite a bit. When i checked the system update section.... it was showing froyo being downloaded! I installed and now enjoying froyo!
 
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop" . "ro.build.fingerprint") == "verizon/inc/inc/inc:2.1-update/ERE27 /161494:user/release-keys" || file_getprop("/system/build.prop", ro.build.fingerprint") == "verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys"

E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted.

I'm getting this as well

Same here

<Edit> So downloaded the zip again, deleted the old one, renamed it and tried again.... same error as above. I bought my phone from Amazon, not sure if that would have anything to do with it... any ideas??
 
Last edited:
Please! Someone answer this for me (and probably a few other noobs). The suspense is killing me.;)

no its not the same update, nothing will be lost and my apps all were still installed with no need to reinstall, it's the actual OTA that Verizon is pushing you just don;t need to wait
 
Mine worked but you have to be very patient. I think the whole update took about 10 minutes (or longer--still updating!!)
 
Thanks for taking the time to post! Installed Froyo before heading out for work, and everything's working as expected. Love the voice commands and handsfree dialing; now playing with 720p - SWEET!
 
How do you know this? I use Swype, as many on these forums do, too. If Swype won't work on 2.2, I don't know if I want it...

And do I actually need to have a physical SD Card in my phone?

Thanks.

Swype will not work after installing 2.2, but there is an easy fix; uninstall it and reinstall it again.
 
People who are getting an error when trying to update in recovery mode need to rename the update file with a program like ASTRO. If you do this on your computer the file name will not be correct, it will say "update.zip" when actually it is update.zip.zip on your phone.
 
Originally Posted by saywhat
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop" . "ro.build.fingerprint") == "verizon/inc/inc/inc:2.1-update/ERE27 /161494:user/release-keys" || file_getprop("/system/build.prop", ro.build.fingerprint") == "verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys"

E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted.

I'm getting this as well

Thats the trick you cant hide the extensions when you rename it or you get that error it can be update.zip.zip , its got just to be update.zip lol :D rebooting now
 
IF YOU ARE ROOTED THIS WILL NOT WORK. Unrevoked = ClockwordMod Recovery. You must have the STOCK recovery installed to apply the OTA update.

If I am rooted and want to manually apply the update.zip what should I do?? Can I unroot without a PC? I'm glad I saw this as I was just about to give it a go...
 
Worked perfectly. Going to back up a few things, then do a factory reset, and reinstall everything fresh.
 
So the RUU and this OTA are completely different? To update to this OTA do I have to flash back to 2.1 or can I just install over the 2.2 RUU that I have on my phone now?
 
If you have removed any bloatware (i.e. CityID, Twitter, etc) the update won't work. If you moved them to a backup folder (like I did) then move them back to there original locations before applying the update.

Worked fine after I reinstalled my bloatware!
 
Be sure to plug in!

FYI, when you're doing significant update which involves re-writing firmware, you'll want to make sure that you have either PLENTY of juice left in the battery or better, yet, be plugged in. In the middle of the update is NOT where you want to run out of battery...

Thanks teslatech!