TreyStyles
New Member
- Joined
- Oct 3, 2010
- Messages
- 14
- Reaction score
- 0
Reboot stuck on "M" screen. Message alerts work!
OK. I've seen a bunch of posts about people having their DX being stuck on the "M" screen. But I haven't seen anything like mine. Please read on...
When I reboot my phone I intermittently get stuck at the "M" screen. But it seems like everything else is booting up behind it normally.
I hear the Droid voice which is a part of the boot up process, the phone vibes as if it is booting up normally, and I even get message alerts and hear calls come through. But it's stuck on the "M" screen.
Then I pull the battery. I let it boot up and it either gets stuck again, or boots normally with no rhyme or reason. Sometimes I have to pull the battery 5 or 6 times before it boots up normally.
This has happened since my initial boot on day I received my DK.
A VZW rep said for me to do a factory reset. I did it, and the first time I booted up it was stuck on the "M" screen again. So that obviously didn't fix it. 2 battery pulls later it was fine.
Any ideas???
Could this be a hardware issue???
OK. I've seen a bunch of posts about people having their DX being stuck on the "M" screen. But I haven't seen anything like mine. Please read on...
When I reboot my phone I intermittently get stuck at the "M" screen. But it seems like everything else is booting up behind it normally.
I hear the Droid voice which is a part of the boot up process, the phone vibes as if it is booting up normally, and I even get message alerts and hear calls come through. But it's stuck on the "M" screen.
Then I pull the battery. I let it boot up and it either gets stuck again, or boots normally with no rhyme or reason. Sometimes I have to pull the battery 5 or 6 times before it boots up normally.
This has happened since my initial boot on day I received my DK.
A VZW rep said for me to do a factory reset. I did it, and the first time I booted up it was stuck on the "M" screen again. So that obviously didn't fix it. 2 battery pulls later it was fine.
Any ideas???
Could this be a hardware issue???
Last edited: