Droid X self-rebooting - Bad News, 'it's not a problem.'

[friedsonjm]

Bad News - I am on my third 'Droid, the first on bricked on the first software update (the famous 'M' problem), the second one developed a screen failure, and this their one - you guessed it - likes to reboot itself several times a day.

I've been working with a 'Senior' Customer Service Supervisor, who patiently listed to my complaints, and my pointing out the 63 pages (so far) of this discussion on the Motorola board, and my wish for a NEW phone, not another rebuilt - i.e., I don't want someones else's probem a third time.

She first checked Verizon Wireless's records, which showed a 'few' such complaints. She then contracted Motorola, which told her they have had very few such complaints, so few that they don't recognize it as in issue, and it is NOT being worked! Now, I'm tempted to post her direct number here, but in all fairness, she is still working on the issue, so I'll give her more time.

I suggest, however, that we collective are NOT making a big enough issue over this problem, and that Verizon Wireless and Motorola need to hear from us a bit more often. If you call Verizon Wireless customer service, don't stop with the first level of support - ask for a supervisor, insist on it if need be, be polite but firm - you need a WORKING phone, and you need to find out what Motorola is doing about the problem. Its not a cheap phone, its not a cheap service, and we are collectively NOT getting our money's worth.

[pool_shark]

I've only had my X two weeks but it has only rebooted once.

[crb79]

---

friedsonjm wrote:

Bad News - I am on my third 'Droid, the first on bricked on the first software update (the famous 'M' problem), the second one developed a screen failure, and this their one - you guessed it - likes to reboot itself several times a day.

I've been working with a 'Senior' Customer Service Supervisor, who patiently listed to my complaints, and my pointing out the 63 pages (so far) of this discussion on the Motorola board, and my wish for a NEW phone, not another rebuilt - i.e., I don't want someones else's probem a third time.

She first checked Verizon Wireless's records, which showed a 'few' such complaints. She then contracted Motorola, which told her they have had very few such complaints, so few that they don't recognize it as in issue, and it is NOT being worked! Now, I'm tempted to post her direct number here, but in all fairness, she is still working on the issue, so I'll give her more time.

I suggest, however, that we collective are NOT making a big enough issue over this problem, and that Verizon Wireless and Motorola need to hear from us a bit more often. If you call Verizon Wireless customer service, don't stop with the first level of support - ask for a supervisor, insist on it if need be, be polite but firm - you need a WORKING phone, and you need to find out what Motorola is doing about the problem. Its not a cheap phone, its not a cheap service, and we are collectively NOT getting our money's worth.

---

It may be worth it to take the device, the battery, and the charger into the Store and have all 3 items tested.  It could be possible that all 3 of those issues were a result of a faulty battery.  A battery tends to swell a litte when it goes bad, and this swelling could also account for your screen issue as the battery can cause pressure to the back of the LCD.

As for "rebuilts" or refurbished units, most of these are units that the owner decided they didn't like the phone, or it had a faulty hardware piece that was replaced.  Once a device has multiple failures it's just scrapped.  It's only cost effective to refurbish a phone that has 1 or 2 minor issues.  

Hopefully they can get to the bottom of your issue for you.

[droidsw]

It's not the existence of rebooting that is being ignored, but rather the cause of it. That sounds convoluted, but if you read the rebooting-related threads in this forum, or others, you will find that rebooting is almost always linked to something like apps, corrupted files, incomplete updates, SD card issues and even external issues like routers.

There are a lot of helpful posts in related threads in this forum and the Moto forum.

Rebooting is not an uncommon issue among all smartphones, android and IOS. Glance in on the forums of other phones.

My comments won't solve your issues. I wanted to throw my X out the window as I troubleshot my rebooting problem. I eventually figured it out and went back to liking the phone again.

I suggest you scan other threads in this forum, or wait for a member named wildman to reply. He will stick with you and take you through more technical troubleshooting. Good luck.

[Cody21]

I have had my DROID X since Sept 6th and have only encountered maybe 4 reboots. Each and every time it was attributed to an APP that I had installed.

In trying to troubleshoot the problem, I booted into SAFE MODE to see if the problem went away or resurfaced. I ran in that mode for a full day and the rebooting vanished. Of course I did NOT attempt to run any of my 3rd party APPS that I downloaded. Just used the stock apps that come with the phone -  just to help rule out a stock APP or the OS. When I was able to run long enough to satisfy for myself it was not the phone's stock OS or APPS, I rebooted and wrote down a list of my DL'd apps and just uninstalled a bunch at a time - like the last 5 - and "tested" for a period of time to satisfy whether it rebooted. If it DID, I uninstalled another 5 ... etc. Once it stabilized, I noted which "set" of APPS weree backed out last and wnet ahead and reinstalled the earlier ones I backed out ... then slowly added the last 5, or not.

I have never had to go to the "final" step of a full RESET - and I assume you have?

This phone is a COMPUTER more than just a phone. Unlike the iPhone, we can get ourself into trouble with the inherent flexibility  & configurability of the DROID X more than an iPhone user can since the iPhone is locked down. Of course there CAN be hardware problems causing your problems, like battery, SD card, etc...  But going through 3 phones? Strange, imho.

Anyway, this is my experieince and not ruling out that you've just been less than lucky. ... hope you can get your issue figured out or get a phone that you're happy with.

[galaxie500fb]

the droid x is locked down by motorolas use of an encrypted bootloader. With an iphone it can be jailbroken to allow full access whereas thats not possible with the x.

[AuroLo]

I got my X when it came out. Still have the same one. My only problem with it is this. Its constantly re-booting itself. It happens alot when I am texting my sister, she's on t mobile, but does happen other times also.
I wish I knew what the problem was. I love my X

[droidsw]

galaxie500fb, what does the locked bootloader have to do with random rebooting and how can unlocking it solve it?

I'm not being a jerk. I really would like you to explain. Thanks.

[galaxie500fb]

Actually my comment was directed at this statement here. "

This phone is a COMPUTER more than just a phone. Unlike the iPhone, we can get ourself into trouble with the inherent flexibility  & configurability of the DROID X more than an iPhone user can since the iPhone is locked down. Of course there CAN be hardware problems causing your problems, like battery, SD card, etc...  But going through 3 phones? Strange, imho."  

The droid x has an encrypted bootloader and hasn`t been broken yet and possibly never will. It`s easier to jailbreak a iphone than it will ever be to unlock an x. This is where I get myself into trouble voicing an opinion other than the ones who frequently post here. It`s my opinion that  it`s Motorola`s version of the android os that causes so many problems with this phone. The locked bootloader prevents a user from uninstalling the motorizon version and wont allow for a vanilla os free of blur or bloat.

Why do some many apps off the apple apps store work perfectly on an iphone, itouch, ipad but yet there are so many apps that cause problems on an android phone? I believe its as simple as the integration of the original android os and a particular manufactures customization. What works perfectly on my droid x won`t work on my fiancee`s lg ally and vice versa. There is more I want to add but then this post would be deleted for the terms of service. I will say that I have voided my warranty and all of the previous problems I have had I don`t any more. I`m very happy with my phone and expect to keep using it past the end of my contract. This phone has great hardware but it`s severely limited by the os which can`t be done away with with a locked bootloader.

[BigFellow]

I just made a post regarding my Droid X and erratic behavor, the same kind of issues that you have experienced.  Help!

[responsibility]

I just recieved my 3rd replacement in one week original phone lost connectivity, second had screen blotches this one reboots every 3-5 minutes. Same app on all three phones, and verizon refuses to make it right other than sending out refurb junk. Any solutions?

[superbaz]

I've had my droid for a coupe days and found it rebooting 3 times so far.  The problem that I'm finding is that if an app is accessing the sd card when you unplug the usb cable, it reboots.  Maybe this is linked to everyone elses problems, maybe not.

But it's worth looking into for Motorola to see why it doesn't just error out instead of rebooting.  And I think this isn't just a droid x issue.  I'm willing to bet it's an android issue as well.  It's both together.  The whole thing about disconnecting the sd card from the system while the usb cable is plugged in is pretty stupid for a multitasking environment.

[Macg3nius]

  What else can verizon send out but what the manufacturer offers?  If you want results 

call the manufacturer yourself and deal str8 cut out the middle man.   Yelling at verizon

n forcing them to give you a "new" device bc they should be loyal to you, drives the price

up on the rest of us.    When you buy a printer you wouldnt ask microsoft to replace it just

because they support it. 

[droidsw]

galaxie, I generally choose to speed read through posts in threads in other forums when "that" is discussed because it doesn't interest me.

But, I get the gest of what you're saying and I respect anyone with that much enthusiasm about making their phone better.

[CKrx]

I had the same rebooting problem that began about a week after I recieved my first Droid X.  Replacement phone had the same issue after about 3 days.  On my third Droid X now for about 4 months and no problems at all.  Sounds like incredibly bad luck to have two "bad" phones, but that was the case for me.

Customer service via phone and in store were very helpful and offered exchanges with no complaint.  The only headache was waiting for the new phones to arrive.

Don't settle for a phone that constantly reboots; get a replacement that works properly.