I did the update. Everything seemed fine. When it rebooted, it will not pass the Moto logo. I have tried removing the battery and turning it back on. I can not get past this.
Anyone have any ideas?
I have not left the battery out for more than a minute or so. I have had it out now for a couple of minutes and will wait a few more to put it back in.
How does one do a factory reset?
How long? I have left it on the moto logo screen for 15 minutes.
Tried to do the factory reset. Nothing. Sits at the same moto logo.
I know what you mean now. I just shut off my phone after playing with froyo 2.2 for a bit and now it doesn't seem to want to start back up. It's sitting at the moto symbol. Hmm, I'd be careful about shutting off your phone after updating. Doesn't seem to like to start twice.
Anyone else with this problem?
Ok, I couldn't get it to do anything while it was stuck on the motorola screen except engage or disengage screen saver mode. I unplugged the phone and pulled the battery. After replacing the battery it started up with no problem. I shut it down again and it did the same thing. Freezes at the moto symbol. After battery pull it started up again no problem. did 2 more shut downs and start ups and had no problems either time. Weird. I can only suggest trying the battery pull a couple of times before giving up.
So I had the same problem and kept getting the motorola symbol. After restarting a bajillion times I finally got it to boot up. Thought it was running funny so I turned off the phone. The motorola symbol problem reaccured, and again after a bajillion resets got it to work again. Now I had taken out my SD card and decided to replace it. What do you know *blam* motorola symbol screen again. This time a bajillion resets didn't work so I took out the SD card did a full memory wipe and restarted it. IT WORKED! The update seemed to have taken nicely just had to reset up my phone with all my apps and photos. Well I did save most of them on my SD card. So I turn off the phone put the SD card back again excited to finally be enjoying 2.2, but wait what is this? MOTOROLA SYMBOL SCREEN!!! Blah now I have wiped my phone for nothing and prepping to rip Verizon a new one as nicely as possible. Hope they tell me something useful when my whole business is run off a phone that useless in its current state I am kind of screwed.
Ok this isnt fun, I just rebooted after installing a app and now the phone will not go pass the Droid Logo, it just cycles off and on over and over again. Can someone give me the instructions to do a hard reset on a device at boot up and see if this helps?
Wildman, look around on some of the Android sites for something called recovery mode. I think it involves holding down the camera button, volume button, and powering up the phone. But I've seen it discussed in the context of (that dirty little R word that gets removed when it's brought up, but to whom it mat concern, I'm not advocating that here, okay??). So do some digging and see if that might help you.
Otherwise, yer headed to the Verizon store. Or a phone call to Tech Support. I hate to hear that, too, considering all the hubbub around here about the update lately (reading posts that are singing the update's praises can't be helping, either, eh?...)
Good luck, let us know how you make out,
Geri O
I just got off phone with tech and he got me going... Did a Hard reset and all is good. Heres the instructions
1. Hold Home Button and press power
2. Screen will show a Android with a triangle with astrick
3. Let Go of Home Button and Power
4. Press Search Button (Far Left Button)
5. A blue menu will show at top of page, scroll to Format Device
6. Select Yes to verify
7. Allow format to complete (Information at bottom of page will go through a few steps)
8. Once Format is complete Blue Menu will show at top again, select Reboot
9. Sometimes phone hangs after rebot and will take a while but if no responce after 5 - 10 minutes, pull the battery and reinsert. (Device usually starts fine after this)
I left mine on the moto logo screen for the last 8 hours. Can not even do the hard reset. Even if I hold down the hold button when I turn it on, all I get is the moto logo.
Did the OTA update and it 'bricked' after install with Motorola logo and power on/off button not effective.
waited about 20 minutes to let it finish in case it was slow...
Tried numerous times to power off (20 minutes while getting ready for work)
Drove to work (25 minutes)
Read this forum decided to pop battery.
After battery pop rebooted and was a bit sluggish at first (maybe 2minutes)
Now seems to be working fine...
seems like I may need to do a power cycle to see if the same problem recurrs
4-5 minutes have expired while investigating operations
Selected Power Off after pressing power off button and getting airplane and other power options
waited 35 seconds
Pressed power on key
after 35 seconds got key press *PING* system went to screen saver at one minute
1min 45 secs can't power off popping battery again
Loop 5 times
End loop
Gave up tried the following defined in Bronze Contributor II post (but modified to match circumstances) to reboot
4. Press Search Button (Far Right Button)
5. A blue menu will show at top of page, scroll to wipe cache (tried system reboot) didn't work
9. Sometimes phone hangs after rebot and will take a while but if no responce after 5 - 10 minutes, pull the battery and reinsert. (Device usually starts fine after this) After wiping cache I waited 15 minutes
Still not working, will continue to mess with it as time allows at work. More later...stay tuned... it was working once, I should think I can ultimately get it working again.
I have the same problem - if I turn it off and then on I just get the M foreverever. In my case removing and reinserting the battery clears the problem. I've had to do it three times because I wanted to see if the phone would restart properly with a top button push but it doesn't, ever. I think it would be a good idea to leave them on until Verizon puts out a fix.
Another thing I figured out is that if you are using the new option under Settings/Privacy that says "Back up my data", this feature can cause a number of issues to keep returning even after a hard reset because if your issue was a setting or a app that caused your issue, when you hard resetthe device this feature will restore all the settings and app back on device after restore that will automatically bring issue back.
This feature is a nice ideal but until you are sure that everything is compatible it may not be wise to enable this feature because it will make issues go away after hard reset but also cause issue to return shortly after because the system will restore the other files that usually caused the original issue.
I can't even get the restore page to open. I hold down the home button and pressed the power button and also pressed home and held down the power button to no avail. Has verizon or motorola actually came out to say how to fix it exactly?
I went to the local VZW store because it still wouldn't work after the factory reset. I then spent an hour and a half waiting so that they could spend 10 minutes looking at my phone and tell me there's nothing they can do.
The Droid X is still back ordered, so they have to mail a new phone to my house.
Very frustrating when it's your only phone. Somebody needs to review their QA process.
OK, same issue for me. Stuck on Motorola logo. Tried removing battery for a couple of minutes and power, same thing. Tried removing battery couple of minutes then hit "home" key and "power" and still the Motorola logo.
Phone has NOT been rooted. What am I missing to get the reset to work?
Scotslad007 wrote: OK, same issue for me. Stuck on Motorola logo. Tried removing battery for a couple of minutes and power, same thing. Tried removing battery couple of minutes then hit "home" key and "power" and still the Motorola logo. Phone has NOT been rooted. What am I missing to get the reset to work?
I am hoping someone can mark this as SOLVED soon and everyone gets their phones working again.
Scot...make sure you hold the home key when pressing power. continue to hold it until the triangle appears.
Follow the previous posts about what to do after.
I have gone through this routine endless times trying different "roms" and leaked versions on my original droid and my DX before finally settling in with the OTA.
Your update likely took and is fine and your phone should hopefully boot after you do the factory reset/wipe.
If that fails....someone here said vzw is getting a new phone for them.
Dj.
oh yeah....and, unplug your USB before doing all this.
Do you have to take your battery out for a certain period of time before the Power + Home key startup?
I've tried it multiple times and got the reset screen one time and wanted to first just try and "reboot" that didn't work so I was going to get more aggressive with a cache wipe. Now I can't get back to the menu.
So I have tried leaving the battery out for 3 mins. Then hit the Home first (while holding this down) + hit power. Once moto logo is up I release the power and continue to hold home until the reset menu appears?
Same Issue.
Not Rooted.
Did a reset of cache and tried to reboot but with no luck.
This is slightly rediculous. Wonder if this was the issue that cause the delay to the very last day of summer.
Just dump this POS and go to the EVO. I've had it with both Verizon and Motorola!
decker2k01 wrote: Just dump this POS and go to the EVO. I've had it with both Verizon and Motorola!
Really? That's what you have to add on your only post here? That's reasonable! Not too many people can/will just jump ship to sprint, who's coverage areas are as sad or worse than Tmobile. Sprint and EVO who have just as many issues with their device as anyone on any other carrier.
Maybe you can explain what makes the X a "POS" and what Verizon and Moto did to you? Maybe that would have elicited a bit more of a thoughtful discussion and replies to your very well thought out post Decker.
dj.
Hey guys, I have had the exact same problem as you. Update, reboot, lets me see it is at 2.2. I go to install some of the nice apps I used with 2.1 reboot my Droid X then...crap....I get the M symbol...nothing more.
I think that person who posted that some of the apps we have installed from the Market are not playing nice with 2.2.
I took my X to Verizon today, and the tech guy told me I needed to reinstall the 2.2 software manually (I would if could locate an official down load file). I updated mine without the battery being full charged. He thinks it could have caused a software glitch that is causing these problems?????
I think that their are several apps that are not playing nice with 2.2???? Or at least it seem so.
I have my phone back up and running "well" but I am afraid to cycle the power for fear it will not reboot. So for the mean time I am just keeping it on 24/7 and charging it as needed. I am an RN and I use my phone a lot daily for calls, txts and emails. I get my work emails a lot of them every day and have to be able to respond back.
Could it be that the OS didn't install properly due to not having the battery fully powered up. I was out having dinner and drinks when I got the notification that I had an update. Didn't realize it was Froyo 2.2 until after I accepted the update (duh).
Anyone know how to get the software to manually update the phone? I mean the official software. I'm not root and don't plan to either. I'm thinking maybe if I reinstall the OS by transferring the update.zip to my SD card it might fix the problem???
What do you guys and girls think???
GHuestis
Curtterp mentioned something in another post that has me wondering. I downloaded the update via WiFi and had none of these problems. I'm just wondering out load if anyone who is experiencing the boot problem downloaded over WiFi. I don't know why it would matter but it's just a thought. Gator
I pulled mine via WIFI and am having this issue.
I can not get into the reset menu. I know the phone is booting. I have used my wife's as a visual aid and I can shut the phone down, etc..
I am going to keep playing with this. I am hell bent on beating this. (Mainly because I had to go back to using my old Omnia.)
gator1 wrote: Curtterp mentioned something in another post that has me wondering. I downloaded the update via WiFi and had none of these problems. I'm just wondering out load if anyone who is experiencing the boot problem downloaded over WiFi. I don't know why it would matter but it's just a thought. Gator
I think if the update package didnt download correctly that the checksums wouldnt match and the install would be aborted. There is no way an incomplete sbf would even start installing.
So, the issue is probably(don't quote me) not related to the actual downloading of the package. For the people who had issues downloading over 3G the wifi as PCW points out is a good alternative.
As for the poster who says to re-install the update manually...well, I think that verizon rep was wrong. Without rolling back to 2.1 (.604) first you will not be able to install the same update over the existing one. I've tried with the "leaked" version that was officially signed. I imagine if you did have the .sbf (update.zip) for this new release, you wouldnt be able to reinstall it.
My thoughts....wright or wrong.
demmo86rt wrote:I'm gonna try and find out if the RUU has been released, at least it would be a fresh start.
demmo, if you do please make sure to post some instructions or links.
also, do you know if the RUU will be executable using RSD or is there another process.
I think that may be overly complicated for average users though. An update.zip pre-prepared would be better.
I've been having the same problems. I did the battery pulls. I did the SD card pulls. I even did a factory reset. So then I took it to my local verizon store. I explained my problem, told them what I had tried to rectify it. They performed their own battery pulls, their own SD card pulls and even their own factory reset. A second battery pull AFTER the second factory reset the phone finally fully booted. Later that day I turned my phone off to see if it would boot properly after turning back on. I did not. i contacted technical support and they said a phone would be shipped out to me by middle of next week and that they have had no complaints about this particualr problem.
However, i am concerned that I will be charged a restocking fee for the new phone. I have the TEC insurance plan and am at no fault for the defects experienced by my phone. I don't think i should be charged for this service. I've already payed good money for my phone, which does not work, why should i pay more for one that does?
Verizon said nothing to me about having to pay. I don't think I would worry. If I hear anything I will let you know.
Just got this email regarding the restocking fee...
Mr. Hepler, please be assured, you will not be subject to a restocking fee for exchange your device due to a manufacturer's defect. Since you are within your Worry Free Guarantee 30-day timeframe, we will replace your device with a new Motorola Droid X. The only time you will incur the restocking fee is in the event you exchange your device for another make/model or different color device, as these devices cannot be resold as new.
After your 30 days, please remember, your manufacturer's warranty provides an equipment replacement option for up to one year from the date of purchase. Verizon Wireless will provide you with a certified like-new wireless device identical to the one you have in exchange for returning the qualifying defective device. This exchange does not cover physical or liquid damage, installed handsets, batteries, accessories, or antennas.
Certified like-new wireless devices pass over a 100-point quality check before they can be offered as replacements. Since these devices have the latest software version, they often perform better than the device currently being used.
Additionally, a review of your account indicates we have placed an order for another device.
So that works out then.
"certified like-new wireless device"
It had better be perfect too. My phone looks BRAND NEW. The original plastic protection came off, the invisisheild went on. It was then installed in a protective case.
My phone was supposed to be here today. The driver left a note on the door, but I did not know he was here. I have to go pick it up at 6:15 at FedEx.
I want to share another possible workaround to get the phone past the stuck logo, but I'm not entirely sure what I did.
I tried everything mentioned in this thread and nothing worked for me, so I'm waiting on my replacement phone, like others. But in the mean time, I stumbled on a way to get my phone up and running yesterday, and thought I'd try to reproduce it so I could post something that worked for sure. But instead, I ended up having the logo stuck back on all day yesterday with every attempt. So I tried one more thing this morning and it's going, so without reseting my phone ever again, I thought it might be worth sharing what I think I did this time.
1. After pulling the battery, leave the phone off for 20 minutes, without a power cable.
2. Plug in the wall charger. If you do not see the battery charging icon after the logo, go back to step 1.
3. Leave the phone off, but plugged in, for another 20 minutes.
4. Turn on the phone.
I'm not sure of the 20 minutes, but I know that there were multiple occasions where I didn't wait and things didn't work. I'd be happy to troubleshoot this more when my replacement phone arrives. For all I know, maybe I was just lucky with the umpteenth reboot like others. My phone also has the issue where I couldn't bring up the boot menu, or at least see it, and I never did a factory reset.
I actually tried the above and had no luck getting it to go.
BUT... My new phone is here and it is pristine condition wise and working fine. It did however arrive with 2.1 on it and I am not willing to update it at this time.
DO NOT APPLY 2.2! Received my replacement DX today after the first one got stuck at the M logo after applying the 2.2 update. Applied the 2.2 on the new device and stuck on M logo again. Can't believe Motorola and Verizon allowed this update to be released. It is seriously flawed and should be pulled until it is fixed!!!
dakota_96 wrote: DO NOT APPLY 2.2! Received my replacement DX today after the first one got stuck at the M logo after applying the 2.2 update. Applied the 2.2 on the new device and stuck on M logo again. Can't believe Motorola and Verizon allowed this update to be released. It is seriously flawed and should be pulled until it is fixed!!!
Wow! I'll definitely have to heed your warning. Thanks.
I would be interested in knowing if you installed any applications before the update. But like you said, it's unbelievable that this update could be released, so I won't be taking another chance on it anyway.
Got it fresh from the carton, nothing done to it, went straight to update and updated fine. Synced Exchange email, Google account, and facebook. Shut off DX after that and stuck on M logo. Therefore, I did nothing to it that a normal DX can handle. Since then various combinations of battery removal, reboots, have been able to let me boot. Nothing consistent though. If you do upgrade, and you booted fine, just don't turn it off. Very poor QA by Motorola!!!! Thankfully I have my old HTC Incredible, otherwise my business and life would be in shambles!!
This is miserable after days of not having a phone I just found they are sending me a device that was already "activated and returned." Now my "new" Droid X will be someone else's Lemon. All thanks to a software update.
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!!!!
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!!!
Worked for me too. Too freakin' weird.
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 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 tabTouch SettingsTouch About PhoneTouch System UpdatesIf the phone updates, or does not update try dialing *228 send and option 1 on the phone.Disabling Safe modePress 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.
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.
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.
Hi All,
I have had the same problem....tried the hard reset, soft reset, battery pull....I took it back to verizon and the manager said some applications do not do well with the 2.2 update. I told him that I did have the droid 2 before the droid x and he said despite the 2.2 updates these were different phones. I tend to believe the guy....my droid x would work fine after a hard reset cleaning the cache and erasing everything. Then I would add apps and it would suddenly hang on the M screen. So I have gradually added apps and then shut down and restart trying to identify the culprit. So far....so good with no hang up.....If I get to an app that I believe hangs the phone I will keep you all up to date.
After multiple reboots, clear cache's, and battery pulls with no luck, I was just about to give up. I tried to turn it on the normal way and it worked. This whole thing is pretty ridiculous, and I will still be reporting this to Technical Support. But if you keep trying, there is a light at the end of the tunnel. Not rooted user.
I have tried removing the battery and turning it back on. I can not get past this.
