Same here

 

If instead of taking the battery out you hold down volume up and press the camera button at the ! screen- it will take you to a ui that tells you an update error and gives you the option to reboot. The error i got: assert failed: appy_patch_check("MTD:boot:2512896:86ce122fdfab1ca 7aea268575ec692699c8556ab:2502656:e79414a1774b152c 9c3eca09f1be0c6b1b24e889") is the same error I got when I tryed to manually apply the patch two days ago.

You could try to manually apply yourself- there are instructions here: AllDroid.org - View topic - 2.0.1 Update.zip but I don't know how to get the phone to attempt to auto update again- maybe just wait?

 

It will most likely come to your phone again.


also:

My new background.

 

My OTA failed and the Manual update also failed. I am on the phone with VZW right now. Stay tuned.

 

they are telling me to pull my battery but i cant get the dam body glove case off. Have you already tried that? I told them i have done that and nothing happened.

 

Ok so she put me on hold and came back and said the person she talked to said oh tell him his phone got the update.

I said oh so i got the update!! Wow and i was worried i did not!! I then went on to tell them that i did not get the update or i would not be on the phone with them.

Long story short they are sending me a new phone.

 

i told them about some of the other problems i was havening.High pich ringing while on a call maps crashing and now it wont update.

Oh and i tried to go to the store the other day they said they cant do it

 

I also had the upgrade failed and called verizon. they had me remove the battery a couple of times. when that didn't work, they said i needed a new phone. the new phone will not come with and updated OS so i'll need to retry it with the new phone.

 

I talked to the a Verzion rep after my failure -and waiting about 8 hours for it to resend my update. I found my answer here:

AllDroid.org - View topic - 2.0.1 Update.zip

Applied my update and all seems to be working great -I'm now running 2.0.1

 

My update did not work either. The night prior my battery was very low so I turned off the phone. Friday morning after turning it on, I received the upgrade message about 5 minutes later. (Battery still low.) I delayed the install. It popped up 5 minutes later. I proceded to install.

The force close message then came up. I closed it but nothing else happened. Did a few battery pulls and power cycles. It hasn't been sent again. (Manual update screen says I'm up to date, but still showing the 2.0 version and old unlock screen.)

I'll wait a few more days, then call the number. I haven't had any problems with my phone, so I'm not in a hurry.

I'm probably a bit anal, but I'd rather get the update directly from verizon than manually from the 3rd party site. (version control, trust, etc.)

My wife has the same phone. It worked flawlessly on hers. She claims it's faster, but I don't see much of a difference. I'm going to do some side by side tests.

 

My update didn't work either, and neither did manually updating. Several calls to Verizon ended up getting to Motorola support, and they sent be back to Best Buy to replace the phone (which was a fun 3 hour session pleading my case...)

I have yet to see a fix for the assert failed: appy_patch_check("MTD:boot: error. Everyone seems to have had to replace their phone. Where it fails at checking the current system, I'm pretty sure that the base OS already installed on these phones has some sort of problem and fails whatever check the update does. Even a restore of the phone wasn't fixing my problem.

The update thread is so buried now, and I'm too lazy to find it, but you can read my struggle there.

 

My issue seems a bit different than yours. I didn't get the assert failed message you've listed above. My install didn't even start. I'm just going to wait around and maybe the customer service folks will learn a bit more on how to fix it rather than replace it. I don't really want to go through the hassle of installing everything on a new device, etc. Plus, 2.0 works fine for me. Maybe I'll just wait until the next OTA update.

 

I had this on my phone however after rename my corpcal.bak back to the original corpcal.apk my phone then upgraded fine and is now happily running 2.0.1.

Have you rooted your phone and renamed anything or deleted anything?

 

My phone too failed the OTA update. The manual update wouldn't work either... I had the exact problem as Campah. Finally called support today and after nearly two hours on the phone they resorted to sending me a replacement. Reseting the phone to the factory settings would cause the update to download but I always got the triangle with exclamation mark. Nobody I spoke to on the support line ever heard of the problem that just a few of us are having.

Anyway, my Droid worked great otherwise... hopefully the replacement does too.