Updated, now won't boot

[kujirasan]

Update on the stuck M upon reboot issue. Read in another forum about putting it in a freezer for a few minutes as this might be a temperature issue. Sounds far fetched, but I tried it and it booted up fine. Is thus a temperature problem? My have been luck and coincidence that it worked, but I was desperate and willing to try anything. I'll try it later today to see if it reproducible.

_________________________________________________________________________________________________

THIS WORKED FOR ME AS WELL!!!  Holy crap, it's rediculous that this would be caused by a temperature problem.  What the hell is wrong with the people who coded this update?  Were they testing in a meatlocker or something?

IF YOU ARE HAVING THIS PROBLEM, PUT THE PHONE AND BATTERY IN THE FREEZER FOR 4 OR 5 MIN, TAKE IT OUT AND IMMEDIATELY PUT IN THE BATTERY AND PRESS THE POWER BUTTON AND IT WILL COME UP FOR YOU!!!!  IT WORKED FIRST TIME!!!!

[kujirasan]

I just called up Verizon to let them know that this does in fact look to be a temperature issue and they said that since the don't make the 2.2 update, that i need to give my feedback to Motorola (which i'll do tomorrow when they are open).  The person said that she hadn't heard of this as a solution to the problem.  I asked that she keep this in her bag of tricks for when someone calls in with this issue, since doing a data wipe like they recommend for this issue SUCKS.  By putting the phone and battery in the freezer for a couple min your phone will boot up just like nothing was wrong and you won't have to lose any of your apps or configurations.

I also want to give you the whole story of my upgrade experience which will bolster the temperature / boot theory.

I performed the OTA update for Froyo Wednesday (Sept 22) night, once the install finished the device rebooted (well attempted to anyways).  After many different attempts to get it to boot up all the way with different combinations of battery pulls, wait periods up to 20 min etc with no luck, i called up Verizon Tech support.  They asked me if i tried pulling the battery, yada yada.  Finally they said to hold the power button/home button combination to get to the datawipe selection and execute it (btw, getting to the service screen didn't work for like 10 times like others have said here).  After the data wipe i tried to boot the device again and it was a no-go, the phone was a complete brick.  Verizon's rep sent out a phone as a replacement but it was going to be Friday Sept 24 before i would receive it (and btw, that phone STILL isn't here yet and won't be till Monday, that would totally **bleep** me off if i didn't have my business phone for that long, luckily this worked).  So, i kept trying that night of the 22nd till 1:30am to get it going with no success.  The next morning i woke up on the 23rd and tried it again and if fired up immediately.  I was stunned, it was a miracle in my book!!  My house was about 65 degrees that morning, and i had left the battery out the night before.   Since it worked I immediately tried turning it off and rebooted it, and that worked as well.  All was right with the world after reinstalling all my apps and reconfiguring my device for half a day to get it back to the way i had it.

I thought my problems were fixed until today.  I was driving home and my battery was running low and i didn't have a phone charger.  My phone battery drained completely and when i got home i tried to plug it in and charge it and get it to boot....But the dreaded 'M' screen was back with a vengeance.  Tried all kinds of stuff to get it going again with no luck till i read the post about putting the phone in the freezer.  I thought i'd give it a try since i needed to travel tomorrow morning and the replacement phone had not shown up yet, and wouldn't be here in time for my trip. 

I took the battery out of the phone, put the phone and battery in the freezer for 4 or 5 min, took it out of the freezer, and put the battery back in the phone and held the power button to turn on the phone, and VIOLA!!!! Miracle number 2!!!

So, now that i've thought back on my first experience, i remember that my house was pretty cold that morning and the phone started up just like nothing was wrong in the first place, but unfortunately Verizon had me data wipe my phone the night before so i had lost my apps and configurations.  But Froyo was there in all it's flashy goodness.   

This time around i didn't do a datawipe, luckily because i couldn't get to the triangle android screen for the service menu after like 15 attempts (thank god for that).  So everything is still intact, all my apps are still there and i'm back up and running. 

I really hope that this helps everyone that is experiencing this issue!!!

[minne13]

Worked for me too. Too freakin' weird.

[GShelton]

I still have my "broken" phone, so I will try it. But my new phone is running on my same battery. Not sure if the battery in the freezer will help.

I don't want to turn my phone off right now, so I will use my "broken" phone and my wife's battery.

[Android10]

Hello! This is Noah with Verizon Wireless, I hope you are having a great day. I would be happy to address your post today. 

Try running the device in safe mode, then once you turn the device on, try updating it again. Safe mode may take a moment to power up.  

To start Safe Mode:

Press and hold down the Power Key. 

Touch Power Off. 

Touch OK. 

Press and hold the menu key, then press the power key to power on device 

Continue holding the Menu key until Safe mode appears in the left corner of the screen. 

This may take up to 30 seconds. 

Safe Mode will appear in the bottom *left* corner 

The try updating the device again.

From the main screen, touch menu tab

Touch Settings

Touch About Phone

Touch System Updates

If the phone updates, or does not update try dialing *228 send and option 1 on the phone.

Disabling Safe mode

Press and hold down the Power Key 

Touch Power Off. 

[dakota_96]

---

Android10 wrote:

Hello! This is Noah with Verizon Wireless, I hope you are having a great day. I would be happy to address your post today. 

Try running the device in safe mode, then once you turn the device on, try updating it again. Safe mode may take a moment to power up.  

To start Safe Mode:

Press and hold down the Power Key. 

Touch Power Off. 

Touch OK. 

Press and hold the menu key, then press the power key to power on device 

Continue holding the Menu key until Safe mode appears in the left corner of the screen. 

This may take up to 30 seconds. 

Safe Mode will appear in the bottom *left* corner 

The try updating the device again.

From the main screen, touch menu tab

Touch Settings

Touch About Phone

Touch System Updates

If the phone updates, or does not update try dialing *228 send and option 1 on the phone.

Disabling Safe mode

Press and hold down the Power Key 

Touch Power Off. 

---

Noah, thanks for your input, but it didn't work. When you try to do a system update, it will say "You device is up to date" and no update is necessary at this time. Did the *228, option 1, shut down, reboot stuck at "M" logo. I pulled the battery, reinserted, placed in freezer for almost 5 minutes. Turned on and reboted fine. In my opinion it is temperature related. Either the phone's components is getting too hot, the battery is getting to hot, or 2.2 is executing some kind of thermal protection. This has happened on two DX for me. The freezer, at the moment, is the only solution that work. Seems like I am joking, but its the truth. I must have done it nine times and it has rebooted 100% of the time. May also be a batch of DXes this is affecting. I bought it when it initially came out, and the certified like new replacements you are sending me are likely from the initial batches as well.

[djtonic]

---

dakota_96 wrote:

Noah, thanks for your input, but it didn't work. When you try to do a system update, it will say "You device is up to date" and no update is necessary at this time. Did the *228, option 1, shut down, reboot stuck at "M" logo. I pulled the battery, reinserted, placed in freezer for almost 5 minutes. Turned on and reboted fine. In my opinion it is temperature related. Either the phone's components is getting too hot, the battery is getting to hot, or 2.2 is executing some kind of thermal protection. This has happened on two DX for me. The freezer, at the moment, is the only solution that work. Seems like I am joking, but its the truth. I must have done it nine times and it has rebooted 100% of the time. May also be a batch of DXes this is affecting. I bought it when it initially came out, and the certified like new replacements you are sending me are likely from the initial batches as well.

---

Hey dakota

Safemode on the X boots the phone but disables all downloaded and self-installed aps.  You are already updated to 2.2 that's why there is no update available when you check.  If the phone booted in safe mode but not with a regular boot then the issue isnt with the battery.

Also, the ammount of heat generated with the battery would not cause the phone to freeze and putting the battery in the freezer is not the answer. I know it seems to work for you for some reason, but it really can't be the battery.  (Someone please back me up on this with some technical reason as to why i'm right) 

Also, LiON batteries respond to extreme heat and cold by dimished capacity and charge cycles.  So the more you expose your battery to the freezer the less lifespan it will have.

Dj.

[Armored]

I am new to android and to this forum.  I recently received my phone with 2.1 and updated over wifi to 2.2.  I have been experiencing the same problem where you shut off the phone and when you go to power back on you just get the Motorola M.  I have pulled out the battery for a few minutes and replaced it in order to get the phone to turn on correctly.  I think somebody else noticed that it sounds and feels like the phone is logging on correctly but the screen does not change.  What I did the last time I got the frozen screen with the Motorola M was hit the power button and guess where the screen should have displayed the off option.  The phone actually shut down again. This suggests that the phone is actually logged on but the display is not being displayed correctly.  After I did this the phone completely shut down.  I then powered on again.  The phone did fire up correctly but it came back up in airplane mode.  I am not very technical but perhaps this info will be helpful and I am hoping Verizon will acknowledge the problem and start working on a software patch.  It looks like even if you get a new phone the problem is recurring frequently.  

[dakota_96]

---

Armored wrote:

I am new to android and to this forum.  I recently received my phone with 2.1 and updated over wifi to 2.2.  I have been experiencing the same problem where you shut off the phone and when you go to power back on you just get the Motorola M.  I have pulled out the battery for a few minutes and replaced it in order to get the phone to turn on correctly.  I think somebody else noticed that it sounds and feels like the phone is logging on correctly but the screen does not change.  What I did the last time I got the frozen screen with the Motorola M was hit the power button and guess where the screen should have displayed the off option.  The phone actually shut down again. This suggests that the phone is actually logged on but the display is not being displayed correctly.  After I did this the phone completely shut down.  I then powered on again.  The phone did fire up correctly but it came back up in airplane mode.  I am not very technical but perhaps this info will be helpful and I am hoping Verizon will acknowledge the problem and start working on a software patch.  It looks like even if you get a new phone the problem is recurring frequently.  

---

Armored,

I feel for you and you are correct that even the replacement they send to you may exhibit this stuck M behavior upon reboot. Verizon is pretty clueless about the issue. They might give you a statement like, "it's a known problem, go a Verizon store and they can fix it." That's absolutely false. I've been there. Store personnel will tell you that many have turned in their device for the same issue, they can't fix it, and they will gladly order you a replacement. It goes kinda sour when you need a third or more replacement. They'll try to accuse you of doing something to your phone to cause this problem because to them it is impossible to have that many failures. You just need to be persistent and they will relent. They just don't seem to understand that their is probably a bad batch of DXes that are out they and when they send you a certified like new replacement, you might be getting a part of the bad batch. This is a pretty significant problem. Do a google search and you will see. I just wish they acknowledged the problem and sent me a brand new one instead of making going through certified like new devices. In the meantime, if you really need it to boot, put it in the freezer for a couple of minutes, and it will boot. Must be a thermal issue that Moto or VZW seems to not want to acknowlege. Likely due to the expensive cost of a recall.

[crb79]

From what I've read, the Hanging after update can be cleared up with a battery pull or in extreme cases a data wipe. 

I personally would never subject my phone or the battery to time in a freezer.  It is possible to destroy your battery as both heat and cold will cause your battery to expand and contract.