I abandoned my X back.in March because of constant rebooting. It was the third refurbished that vzw sent me. Even from stock it would reboot. There was a large thread on the moto forum about it. I would like to reactivate it, just wondering if there had been a fix. Anyone?
Sent from my ADR6400L using xda premium
Your best bet would be to SBF the device.
Sent from my DROIDX using XDA App
Ok, I SBF'd the phone. Now, instead of rebooting, the screen will go to sleep. When you press the power button, only the hard keys light up and do not go off. Eventually, the phone will shut down completely and need a battery pull. Any thoughts? I sbf'd with 2.3.340
Phone has not rebooted since the one incident. I think (fingers crossed) that the problem is solved.
Mine is still doing it, I just SBF'd to Liberty3v2 from rooted .621, wiped and formatted everything (I'm pretty sure), and I've still had a few reboots just since yesterday.
Any ideas? Any other threads I should check out?
Related
Is anyone having problems with your phone randomly shutting off?
Does anyone have any solutions?
Sent from my DROIDX using XDA App
Ive had maybe one or two random soft reboots happen since getting my phone.
I haven't had one in quite a bit now though.
Really mine shuts off atleast twice a day
Sent from my DROIDX using XDA App
You using a task killing app? If so how aggressive are you with it? Seems like task killers affect this phone WAAAAY more than on my Nexus One.
Random shut off for me = once a week
Yes I have it but ive never played with the settings just downloaded the app and went on from there.
Sent from my DROIDX using XDA App
Also my droid x usually freezes alot when I only have 2 apps running. Have any tips? I've only dropped the phone once but its was about 1 foot away from the ground need help!!
Sent from my DROIDX using XDA App
Mine doesn't freeze but will reboot twice a week our so on its own
Sent from my DROIDX using XDA App
I have had this happen to me twice. I was more on the line of thinking that it is an app that I installed. I hadnt thought it was the task killer set to killing an app that would do this. I will turn off Auto Kill and also do an inventory of apps that I installed since I noticed the shutdowns.
-McMex
If I bring my phone to verizon what would they say?
Sent from my DROIDX using XDA App
I used a task killer on my Nexus One because old habits die hard. So when I moved to the Droid X I still had this habit. I quit using ATK this last Friday and havent had a single glitch or reboot since.
Could this be the case for others with reboot issues? Maybe, Maybe not.
If you have a task killer installed try uninstalling it for 2-3 days and see what happens.
I have never used a task killer but I had the same issue. A factory reset nor an .sbf restore from a brick changed it. My new phone just shipped yesterday as a replacement.
Sent from my DROIDX using XDA App
I was having atleast 2 reboots a day and when I deleted my task killer last week I haven't had any problems my phone is actually faster with out it. I think the task killer stops programs to make your phone run effectively.
Sent from my DROIDX using XDA App
Im bringing my phone to verizon today and see what they tell me thanks alot guys
Sent from my DROIDX using XDA App
I have been having the same issue. My phone will just rest to the animation screen not the motorola M. At first I thought it was chomp sms causing it cause a few times as sms texts would come in it reset. So I removed chomp but issue was still there so I wondered if set cpu was the issue cause I am ROOTED. So I remove that. Issue is still there. I done two factory resets and no help.
I do not see this being a hardware issue...... Tho if it is please someone enlighten me....
Reason is if it is software then I can wait til 2.2 or custom rom...
Please any help or insight would be great. My exchange period with verizon is ruining out. Don't want to return a item with proper hardware.
Please assist thank you.
Sent from my DROIDX using Tapatalk
Any help at all?
Sent from my DROIDX using Tapatalk
I haven't ever used a task killer on the x, and still had the same issue. It got slowly worse, up to 2 or 3 reboots and 2 or 3 freezes (battery pull required) per day. Verizon shipped me out a new phone, and I just got it yesterday.
edit: the speaker's a good bit better, too. Not great, but definitely distinctly louder than my original one.
Any idea if I was to un root it if it would matter? Or if rooting did cause this... Is the damage done then?
Sent from my DROIDX using Tapatalk
Maybe this might be the issue
Too Xtreme said:
Is anyone having problems with your phone randomly shutting off?
Does anyone have any solutions?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hi guys. I was on the Motorola Droid X page, under owner support, and came across this:
"The battery charger shipped with this device is a high rate charger specifically designed for your DROID X.
Other chargers might take longer to charge your battery, cause your calls to fail during charging, or cause your phone to continuously power cycle."
I know that I had been using my BB Storm 2's charger with my DX since they both use the same connectors, unaware that the charger actually made a difference. I also noticed the shut-down/restart issue, and had called VZW about it twice, prompting the tech to send me out a new one. I only found this tidbit by chance afterwards. Maybe myself and others might be doing the same, and unknowingly creating a power issue...just my $0.02
tankyard said:
Hi guys. I was on the Motorola Droid X page, under owner support, and came across this:
"The battery charger shipped with this device is a high rate charger specifically designed for your DROID X.
Other chargers might take longer to charge your battery, cause your calls to fail during charging, or cause your phone to continuously power cycle."
I know that I had been using my BB Storm 2's charger with my DX since they both use the same connectors, unaware that the charger actually made a difference. I also noticed the shut-down/restart issue, and had called VZW about it twice, prompting the tech to send me out a new one. I only found this tidbit by chance afterwards. Maybe myself and others might be doing the same, and unknowingly creating a power issue...just my $0.02
Click to expand...
Click to collapse
I believe the site is: motorola-global-portal.custhelp.com/app/answers/detail/a_id/48599/p_country_code/US
So 4 times now i've let the battery fully discharge and charged the phone overnight, turned it on the next morning and its in recovery? First thought was it was because when I was having issues with the market but my market app has been working without any problems since removing updates.
Is there a setting I need to change or is there an underlying problem that is rearing its head.
Running GB rooted, never had any ROMS pretty much just rooted thats it.
Sent from my DROIDX using XDA App
I believe it's supposed to do that. I think it's a sort of fail safe system that comes from the hijack process used in the Droid 2/X Bootstrapper.
Sent from my DROIDX using XDA App
Interesting because it never did that before for the whole time i've been on GB.
Sent from my DROIDX using XDA App
I got my Xoom back last week and have been trying all weekend to figure out this problem.
If i set it down for 20 minutes and come back, it shows no network connection. Airplane mode cycle doesnt fix it, and i cant toggle wifi... it just sticks on turning on/off. Only way to get back to 3g/4g is to reboot.
I rooted when i first got it back, then got the new OTA to "D" and re-rooted. Everything works great except for this sleep bug.
HOWEVER... First thing I did after i rooted when getting it back was to load the Tachi OC GPU Kernel. It has been on there the whole time, and it didnt get overwritten by the OTA. Im wondering if that could be part of the problem, but i cant find the latest stock kernel that should be on the device to test. I wish i had an SBF of the latest OS.
Anyone else experiencing any of this?
That kernel is probly causing it. I would try and put a new kernel on and see what happens. These things have power consumption issues now.
Sent from my Xoom using xda premium
This is how I rooted from stock. Mine and my wife's. No issues with connections so far.
http://forum.xda-developers.com/showthread.php?t=1242241
Sent from my Xoom using xda premium
hammer4203 said:
This is how I rooted from stock. Mine and my wife's. No issues with connections so far.
http://forum.xda-developers.com/showthread.php?t=1242241
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I followed that too. Root is on and working.
I opened box from moto, powered on and activated SIM. Then rebooted and pushed the recovery via fastboot. Then rooted using that method and applied the Tachi OC kernel.
You have done all my exact steps (What Ghz do you OC too btw?) and yours will sit on the desk for untouched for say an hour, and when you come back you are still connected to 4G? if so, then i have a bunk new 4G radio.
I don't. But I don't think I'm running the tachi oc.
Sent from my Xoom using xda premium
Okay my girlfriend's atrix reboots almost ten times an hour.....during a phone call it reboots sending/receiving texts or just sitting there probably getting background data. I had her get a new battery cause she had some **** off brand in it....didn't work...now she told me she washed her last atrix and got it replaced so im thinking she got her sim wet and that's why its rebooting or its hardware end....phone is completely stock not rooted...any ideas? Thanks in advance
Sent from my DROID3 using Tapatalk
Unlock it root it and a custom rom fixed mine it did the same thing not as much as hers but still had a lot of random reboots on stock gb .now maybe one random reboot a month
Sent from my MB860 using xda premium
I wouldn't be so fast to unlock the bootloader. A phone that reboots that often most likely has hardware issues. Stock ROMs have issues, but not that radical.
Feed her a nice dinner and get her to come clean as to the evil thing she did to her phone. If there really have been no mishaps, get a warranty replacement. My advice is to not do anything to the phone that would make getting a replacement difficult.
Good Luck
Lol she told me what happened with her first one she gott replaced she washed it....so she got a new one that one rebooted...then she got another and its also rebooting
Sent from my DROID3 using Tapatalk
I would tell u to download a gingerbread fruit cake, moto-fastboot, and do a complete wipe including system, data, webtop, preinstall, cache and boot. (Boot=kernel) then do a fastboot reboot into recovery and flash the 2.3.4 fruit cake. If u need detailed instructions on how to do this and where to get files pm me.
Sent from my MB860 using Tapatalk
Ten times a day is a frigging lot. I used to have random reboots with group but it was more like twice a day. Sometimes it would not boot up again until I did a battery pull......but flagging to Gingerbread solved all these errors. No random reboots or any problem at all since.
Sent from my MB860 using XDA App
Jibraldor said:
Ten times a day is a frigging lot. I used to have random reboots with group but it was more like twice a day. Sometimes it would not boot up again until I did a battery pull......but flagging to Gingerbread solved all these errors. No random reboots or any problem at all since.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sorry, what does "flagging to GB" mean?
Sent from my MB860 using xda premium
rlillard said:
Sorry, what does "flagging to GB" mean?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I meant to write Flashing to gingerbread. Sorry for the typo, I am Swyping from my phone.
Sent from my MB860 using XDA App
Funny thing is she's on the gb ota...she's outta town for the weekend I think on Monday we are gonna try a new sim that doesn't work.....another replacement....ill keep you all updated incase there's another case of this!
Sent from my DROID3 using Tapatalk
I thought "flagging" to be British slang.
The conclusion I would make from reading this thread is that while many if not the majority of frequent and seemingly random reboots are failed h/w, another failure mode is corruption of the installed kernel and/or support utilities (collectively called the OS). Re-flashing any of the various ROMs will clear the problem.
If f/w corruption is the actual problem,flashing anything requires unlocking the bootloader. If a replacement phone is an option, I would do that rather than risk unlocking the boot loader and then not being able to return it.
My nexus 10 is dying with displayed charge at or around 70%. I had lost the tablet and it was dead for months. Idk if that is relevant or not. It did take a full charge a few times after finding the tablet before the above stated issue occurred. The charger I'm using should be in good shape as it charges my Galaxy S4 w/o issue. Running CM 10.1.3 (Stable).
Thoughts? Thanks in advance.
Update: now the device is dying while showing charge level in the high 90% mark. Device now dies mid-boot even plugged in. Before it would stay on so long as I kept it plugged in. It will stay on if I go into cwm. That's the curious part.
Sent from my SGH-I337 using XDA Premium HD app
After doing some research I'm going to guess calibration to be the issue. What to do if calibration is so out of wack it thinks its charged when it's dead?
Update: I ran calibration after I managed to get it to 100%. A few minutes later it died. Curiously I put my tablet in recovery mode and it has stayed on for at least an hour now. However when I try to boot into CM it dies. Every retry it dies a little sooner in boot.
Maybe you could go back to stock via fastboot. If that doesnt work I think tour battery is dead.
Sent from my Galaxy Nexus using XDA Premium HD app
Actually I've been letting it sit idle in recovery mode. Its had at least 4 hours to drain now. Haven't been able to kill it yet so I am extra confused. I read the charge with an app and it was at 4400. The tablet is perfectly happy in recovery. I wiped my system partition and reflashed CM. This seemed to have an affect to a degree. Once the dalvik cache was rebuilt the tablet died again and went back to the odd behavior I mentioned. I would prefer to not return to stock unless it is absolutely necessary. I will if I have to but I would like to see if anyone else has seen this issue or has an idea on how to TS it as is.
For the Android junkie this would be a fun issue to trace down. I simply don't have the education. I just created my developer console account and am going through the documentation to create my first app. Clearly outside of Google Fu I'm relatively useless.
Sent from my SGH-I337 using XDA Premium HD app
Try wiping the battery stats from recovery, if yours lets you.
Have you tried wiping/factory reset and starting with a clean install? As part of all the rebooting, you may have corrupt file(s).
SmokinCharger said:
Have you tried wiping/factory reset and starting with a clean install? As part of all the rebooting, you may have corrupt file(s).
Click to expand...
Click to collapse
I think in going to have to. I've proved the battery is charged and CWM knows it. I'd like to do a titanium backup to preserve my game data but I don't see how if the darn thing dies mid-boot. May have to bite the bullet on this one
Sent from my SGH-I337 using XDA Premium HD app
dibblebill said:
Try wiping the battery stats from recovery, if yours lets you.
Click to expand...
Click to collapse
It didn't so I just wiped the whole /system partition (I believe that's where the battery bin exists) and flashed CM back. No good.
Sent from my SGH-I337 using XDA Premium HD app
my tablet died at 60,but it dont died since i flash other custom roms....
Sent from my Nexus 10 using XDA Premium 4 mobile app
hunforfee1 said:
my tablet died at 60,but it dont died since i flash other custom roms....
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why thank you. I'll have a look.
Sent from my SGH-I337 using XDA Premium HD app
Flashed full factory image
I used the image found here to completely wipe and reset all partitions and make the thing like it just came out of the box with no trace of mods left (that I'm aware of). It happily booted in and I got about halfway through initial setup and it died and returned to the same behavior.
What do I do now?