Droid X Powered off and wont turn back on!

[Domino]

I was going about my buisness on my X when suddenly the phone made the little ring noise and powered down. I had noticed prior that the battery level was telling me 15%, but we all know about the battery calibration issues. I figured it just died so I plugged it in and it's showing me the green LED. I gave it about 5 mins and it still won't power back on. Any suggestions?


EDIT (SOLVED): When I was charging my phone I realized that I was charging it from my computer via USB, but I suppose the phone had to be on to make the USB charge connection to the computer, and it had died so it wasn't pumping any juice into it. I just plugged it into the wall and the display turned on. The thing had just drained battery, sorry guys. I'm relieved though!

Thanks

[Ads]

[Abe21599]

put it on the charger for 2 hours and in that time DO NOT touch the phone - just let it charge for the 2 hours.

and make sure its the wall charger

[maltman83]

If there are ANY apps running while you're try to charge through a computer with USB, the battery will actually still discharge because the computer does not put out enough amperage to charge the X. Wall plug is the best, unless you kill all apps, USB it, and leave it.

[tennapop]

When I was charging my phone I realized that I was charging it from my computer via USB, but I suppose the phone had to be on to make the USB charge connection to the computer, and it had died so it wasn't pumping any juice into it. I just plugged it into the wall and the display turned on. The thing had just drained battery, sorry guys. I'm relieved though!

My phone started to die, so I plugged it into the computer and got the green led issue you did. Thanks for posting your fix. I was about to loose my s--- thinking my phone f---ed up the first day I had it.

[Foil]

Thanks! You probably just saved me 30 minutes! And at 1:30 am, those 30 minutes are pretty valuable!

[coyfish151]

Nothing I read here fixed it for me. In the end, it was simple user error. After pondering over it for quite some time, I realized the green light is only supposed to come on when the droidx is plugged into a computer. Realizing that, I thought the only explanation was there was something wrong with the cable/ac adapter i was using that caused the droidx to only read a power signal of a usb port and only charge it to the point where it died right after it booted. Immediately after making sure my phone's side was secure, I checked the usb end of the cable and low and behold it was not securely plugged into the ac adapter. After I made sure the cable was plugged securely into the adapter and tried to plug my phone in again, I no longer had a green light, but instead had the charging animation I would normally see while my phone is off and charging. I realize it was completely my own fault that I let it go under 5% and didn't realize my damn adapter wasn't secure until 2 hours later, but at least I did it without those bastards at tech support lolol. Hopes this helps those who got this far down ^_____________^COY

[myvalk]

Thanks! You probably just saved me 30 minutes! And at 1:30 am, those 30 minutes are pretty valuable!

saved me a bunch of time too. thanx.
why dont they realize these kind of problems and fix them before they leave china?

[darthquantus]

Bunch o' noobs. Me too, eh. I get the green light, no response, thought WTF. As my right hand goes for the "landline" to call verizon, my left hand does a search in droidx forum. Good job lefty, good job.

[unit43]

here i was at work thinking " oh crap gotta send back another droid x". i as well had my phone plugged into the computer thinking it was chargeing while doing my own thing fumbling thru apps when i got " the black screen of death" or so i thought. was about to call verizon and have them send me my third droid x. the last one i had the only way i could talk to people was either via bluetooth or speaker phone....needless to say that got old quick. but thanks to this post i think i will make it another day.

[mikeinrichmond]

problem solved, thank you Domino for posting what the fix was....