Stuck at M logo after update

[geomstern]

Droid X stuck at M logo

Happened to me, too. Couldn't turn the phone off, either, without taking out the battery. Called tech. Tried hard reset. Couldn't even do a hard reset. Two things:
(1) I discovered by trial and error that if I removed the battery for about 5 minutes, put it back, waited a couple minutes, then turned it on - it worked. However, if I turned it off (using the usual way to do so), I couldn't reboot without repeating tyhe steps just mentioned. Not acceptable.
(2) Verizon replaced the phone via overnight shipment. Supposedly with Froyo already on and checked. I have bot yet deactivated the old one and activated the new one. Hopefully that will work.

 

[sonnyjitsu]

idea

I was having a similar problem until I unplugged my USB cable from the phone, then pulled the battery and restarted. It seemed that unplugging the USB cable did the trick. Hope this helps.

 

[kyblackberet]

update

I'm just gonna keep my 2.1 OS, it works great!

 

[fyrman49]

Same here. Try this everyone. Pull the battery and the memory card for about 1-2 minutes. Reinstall and turn on. Mine is working fine now.

 

[Ricky Babalu]

I'm just gonna keep my 2.1 OS, it works great!

Someone correct me if I am wrong, but I believe once it gets pushed to your phone you have no choice.

 

[djxtreme]

Does anyone know of a non-root app that will back up your installed apps/data?

I'm tempted to do a complete wipe, but even that didn't fix anything when I did the Froyo leaks so I'm uneasy about doing it now without a safety net.

my backup/ my backup pro is really good

 

[roberte1342]

Someone correct me if I am wrong, but I believe once it gets pushed to your phone you have no choice.

The only way I know of is to install the leaked 2.2, someone should make an app that lets you refuse updates.

 

[xelhabb]

This may have already been said but this is an issue I encountered when reverting BACK to 2.1 from 2.2 leaked. You can encounter this same boot-loop error when installing any OS. The phone is far from bricked and actually contains the full OS. What occurred was during the loading process there was a failure in the wiping of the memory and clearing the cache.
Simply hold the power, volume down, and camera button simultaneously for about 3 seconds. When you release them you will get an icon and exclamation symbol in the center of the screen. Press the search button and you will get the boot recovery menu. Use the volume button the select wipe memory / clear cache. Its the 2nd or 3rd choice down somewhere in the center of the list. It will take a minute or two to complete. When done, select the boot recovery option and let your phone boot back up. It will take a few minutes but it will work.
A LOT of phones were sent back to Verizon unnecessarily because of this very minor glitch in the OS upgrade process. I encountered the problem when reverting to 2.1 so I could obtain 2.2 Official. You would think Verizon would get with Motorola so they could guide people through the process. How about simply posting the fix on their website. Sheesh!

 

[ReblTeen84]

I had the same problem. Pulling the card didn't work, left the battery out for an hour at a time - i'd get a good boot one every 10-20 times, no recovery. Even did a hard reset the one time I was able to get into recovery, didn't do anything. Wound up taking it to a VZ store since I was out of state on vacation, they overnighted a new one to the store. Worked fine, installed the 2.2 update before I did anything else as soon as it was activated, works like a charm now except for the battery manager force close issue.

 

[66racer]

I thought I saw a statement from motorola or verizon saying replacement phones will just be issues, Im not sure but thought it was here on androidcentral main update page

 

[davidnc]

Someone correct me if I am wrong, but I believe once it gets pushed to your phone you have no choice.

Yep thats right the only way it won't eventually get on your phone as if your rooted

 

[mcgraw0204]

Stuck at M Logo

Same here, removed the SD Card and it corrected the issue.

 

[ultravisitor]

My X suddenly rebooted itself earlier and got stuck on the M. I've tried SBFing twice and though it appears that the SBF completes fine, I'm still stuck on the M logo. I can't get into stock recovery; I can only get into bootloader mode. Any ideas for help? I've tried removing the sd card and that hasn't done anything.