Manual Update Still Receives OTA?

[ShiningMilotic]

I manually updated my motorola droid to android 2.2 FRG01B, will I be able to receive the OTA update for FRG22D?

 

[Thornfullessrose]

Yes.

 

[CegAbq]

I manually updated about 2 weeks ago; last night at 9:20 pm 22D was automatically pushed to my Droid.

 

[Bandersnoot]

I manually updated about 2 weeks ago; last night at 9:20 pm 22D was automatically pushed to my Droid.

How do you know it was updated?

I did a manual Froyo update a few weeks ago, and this morning the OTA update seemed to fail. Last line of the boot screen said it aborted. About phone looks like it did yesterday.

 

[CegAbq]

How do you know it was updated?

I did a manual Froyo update a few weeks ago, and this morning the OTA update seemed to fail. Last line of the boot screen said it aborted. About phone looks like it did yesterday.

Because the phone told me I had an update ready, asked me if I wanted to update now or later (I told it later because I was in the middle of something). When I was ready, I went to Settings, About Phone, System Updates & checked update now; it updated, and automatically rebooted, then my build number was changed to FRG22D

 

[rcaine]

I did the first upgrade manually on both of our droids on about August 10 (three days apart to make sure it works). That was the B update. I manual did my phone Friday to the D update. This evening my wife's Droid (still on B) got the notice the update was available. I did the OTA update on her phone. Afterward I compared the two phones and they have identical version information. Have not seen any noticeable changes between B and D but I expect there are many bug fixes and it is now more stable.

 

[Eugene]

I got the notice too but mine failed on installation as well.

 

[KSutherland]

still waiting on my OTA. my wife has already got her's i thought i would wait this time ... lol

 

[CegAbq]

still waiting on my OTA. my wife has already got her's i thought i would wait this time ... lol

I've done every other update manually, but decided I'd wait for the OTA for this one - and fortunately it worked.