Stuck on M? No REAL Solution

Discussion in 'Droid X Tech Support' started by wrightperspective, Sep 23, 2010.

  1. wrightperspective
    Offline

    wrightperspective New Member

    Joined:
    Feb 14, 2010
    Messages:
    315
    Likes Received:
    1
    Trophy Points:
    0
    Location:
    ATL
    So here is what is going on. I got the M during reboot after the 2.2 update. After a long battery pull it started working. But now every time the phone shuts down I get the M, just sitting there when I power back up. The phone actually will ring when I get a call or text. I even turned the phone off by pressing the power button and pressing on the screen where the Turn Phone Off would normally display - so that means the phone thinks the screen is up - but it isn't - all I have is the M.

    I called Verizon and even went into the store to no avail. We tried factory reset, wiping the cache and anything else we could do. Their solution is to send me another phone, now. I even called Motorola and they had no solution. The problem is that I am worried that I may have the same issue with that one, which will be here Friday.

    So, I want to find out how many other people have this problem. You may not even know about it because you never shut your phone down. So, try turning your phone off and then turning it back on and let me know if you get stuck with the M (If you dare risk it). If it gets stuck, you can pull the battery for a little while and put it back in and it should be good. I just want to know how widespread this problem is.
  2. Yohimbe35
    Offline

    Yohimbe35 New Member

    Joined:
    Feb 3, 2010
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Southern Michigan
    Stuck on M

    I went to the Verizon store this morning and they said it happened to alot of people. They are shipping to me next day air a replacement phone. It was short and sweet. About 5 minutes in the store.
  3. wrightperspective
    Offline

    wrightperspective New Member

    Joined:
    Feb 14, 2010
    Messages:
    315
    Likes Received:
    1
    Trophy Points:
    0
    Location:
    ATL
    You got next day? Man - they sent mine 2-day so I won't have it until tomorrow. If anyone gets a replacement today because of this issue, please let us know if you have the issue on the replacement, too.
  4. evetro76
    Offline

    evetro76 New Member

    Joined:
    Sep 23, 2010
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    0
    Happened on Droid 1

    The same exact thing happened to me on my Droid 1. I updated to 2.2 OTA (same exact time as two others). They completed theirs no issue and mine got stuck on the M screen. Tried waiting for an hour, tried taking the battery out, even called verizon and they talked me trhough a factory reset.... nothing. Needed to get a replacement Droid.

    Recently upgraded to the Droid X, and just updated to 2.2. No issues yet.
  5. marcogiudice
    Offline

    marcogiudice New Member

    Joined:
    Jan 11, 2010
    Messages:
    199
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Jupiter, FL
    that sucks!
  6. rmcomer
    Offline

    rmcomer New Member

    Joined:
    Dec 4, 2009
    Messages:
    80
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Sacramento, CA
    I had the same problem with my original X, no matter which 2.2 leaked rom I tried, 9 outta 10 reboots, I'd get stuck on the dreaded 'M'. I had other problems so I got a replacement about 2 weeks ago. The replacement reboots perfectly, even when I had root and installed leaked 2.2's.

    I SBF'd back to 2.1 before the release of OTA 2.2 and haven't had any 'M' problems.
  7. TheJester34
    Offline

    TheJester34 New Member

    Joined:
    Jul 24, 2010
    Messages:
    185
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Dunlap, TN
    ^^Same here with the SBF. Did it before I updated (had some stuff still on the phone from when I was previously rooted and forgot to take some theme stuff off. Kept failing). Works great. I'm wondering if it was something to do with the phone being rooted (like, how many people that have this problem were rooted)? Or maybe it was just a flaw, idk
  8. dxuser
    Offline

    dxuser New Member

    Joined:
    Jul 14, 2010
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    0
    I had this problem on a non rooted phone. Called Verizon yesterday and got a tracking # today for a refurb arriving tomorrow. Really sucks. Scared to upgrade the new one.