Hey guys,
I have the AT&T retail version of the Moto X, running 4.4.4, locked and running stock firmware, which I got through MotoMaker in December of 2013
A couple days ago my Moto X screen just went black. It was in my pocket and shut off while I was out of the house. This has happened a couple of times before, so I tried to turn it on, but this time it wouldn't. I though the battery had just unloaded. When I got home and I plugged it in, the screen stayed black and the phone would just vibrate randomly. I assumed it was a sort of boot loop issue.
I tried getting into fastboot and noticed that the screen was actually lighting up. It was a weird mix of all the LEDs turned on showing a mix of green, red, and blue, making a noisy, stripped pattern and it was slowly getting brighter and brighter. I downloaded the XT1058 AT&T 4.4.4 firmware and tried to flash everything new except for erasing the user data, which I would really like to rescue somehow.
So the boot loop issue is gone, but when I press the power button, it vibrates once and my computer doesn't recognize the phone.If I put the phone in fastboot mode, the computer does recognize it and it does show up under fastboot devices and in device manager as an ADB Interface. Unfortunately, I didn't know about USB Debugging before all of this and had it turned off. If I unplug the battery, the computer recognizes it as a "USB Input Device" under Human Interface devices.
So I'm kinda stuck and don't know what to do. It kinda sounds like it could be a battery issue to me? I have had some quick drains before, but I just attributed it it to a lot of screen time. Would a weak/dying battery not be able to power the screen like this and not be able to boot the phone completely?
Thanks,
Dan
With a stock Moto X, I would've contacted Motorola a long time ago.
nhizzat said:
With a stock Moto X, I would've contacted Motorola a long time ago.
Click to expand...
Click to collapse
I tried. My phone was out of warranty and they wanted $100.
Related
So I've had my Turbo since it came out and today I think it died on me. I sent one single text to my friend then all of a sudden my screen would not turn on at all. The phone was functioning because I felt vibrations for each notification I received but the screen displayed absolutely nothing. Force rebooted it about 3 times and noticed that it would flash every now and then but it would be a random white flash. Then I tried pressing the power button a few times and the screen would blink and flash partially. Anyone have some help for me? The phone has never been dropped or damaged. Do you think Verizon or Moto could replace it?
STEV307204 said:
So I've had my Turbo since it came out and today I think it died on me. I sent one single text to my friend then all of a sudden my screen would not turn on at all. The phone was functioning because I felt vibrations for each notification I received but the screen displayed absolutely nothing. Force rebooted it about 3 times and noticed that it would flash every now and then but it would be a random white flash. Then I tried pressing the power button a few times and the screen would blink and flash partially. Anyone have some help for me? The phone has never been dropped or damaged. Do you think Verizon or Moto could replace it?
Click to expand...
Click to collapse
can u get into recovery?
the_rooter said:
can u get into recovery?
Click to expand...
Click to collapse
Nope the screen can't display anything so even if I could I wouldn't know. Whenever I press the power button it just gives me a delayed flash. When I force reboot it vibrates and will give me another flash when its powered back on.
If you don't have insurance, Motorola's warranty should cover something like that. Contact them and find out. Must be some weird digitizer issue. Unfortunately these mass produced microelectronic devices occasionally have manufacturing defects.
So my most recent update-
Went to Verizon and of course their shipping me a new one and I have to ship out my unit and if there is any water damage or anything I have to pay full retail. I am 99% sure this wasn't my fault or water damage.
Most recently I connected it to my PC and my PC noticed it as XT1254 but when I went to browse the device through my PC it was blank. No folders or files. I was trying to recover some pictures I had but it was completely blank. So weird. This phone was awesome but I honestly just want to get a Note 4 or something I'm afraid this will happen again!
STEV307204 said:
So my most recent update-
Went to Verizon and of course their shipping me a new one and I have to ship out my unit and if there is any water damage or anything I have to pay full retail. I am 99% sure this wasn't my fault or water damage.
Most recently I connected it to my PC and my PC noticed it as XT1254 but when I went to browse the device through my PC it was blank. No folders or files. I was trying to recover some pictures I had but it was completely blank. So weird. This phone was awesome but I honestly just want to get a Note 4 or something I'm afraid this will happen again!
Click to expand...
Click to collapse
So I just reconnected it to my PC and turned on my device. The display is still not functioning but I was able to unlock it using my pattern code. Then went to browse it through my PC and all my files and folders were there but the display is totally not functioning. This is the weirdest thing I've ever seen. I've been an android user since the OG Droid and I never have problems with devices
My XT1092 powered down by itself at 4% yesterday, so I plugged it into a power bank and left it on its own for a while. At 24%, I tried to power it on, and the device boots, but gets stuck on the final image of the boot sequence for longer than usual, before booting into a black screen. From here, I can do some things, like Moto Display and Voice still work (I can get it as far as opening the camera, but anything else requires me to unlock my device, even tho I don't have a password), and notifications like WhatsApp and Gmail come in fine and can be seen, but the moment I swipe up from Display to unlock it, I can't do anything. Touchscreen is unresponsive in camera interface when launched, but volume to capture and screenshots work. Moto Gestures don't work, except double twist in camera interface to launch front camera. From a thread on reddit, this is apparently not the first time something like this has happened, but it's incredibly frustrating to get this. I've only had my Moto X for 3 months, since April, and in that time, I've had to factory reset it twice and send it in for repairs once due to a faulty power button. I've connected it to a PC in hopes of backing my stuff up, but while PC recognizes XT1092, it says there is nothing on the phone. Wiped the cache twice in an attempt to fix, and boot through fastboot, but once again, no luck. Running stock 5.1, unrooted, locked. Can access recovery menu, so whatever I can access from there is probably my best bet.
P.S. What does reboot to bootloader and view recovery logs mean?
Same thing here. Happened twice to me also. Not sure what causes it.
http://forum.xda-developers.com/moto-x-2014/help/boot-animation-phone-stuck-t3148085
KB Smoka said:
Same thing here. Happened twice to me also. Not sure what causes it.
http://forum.xda-developers.com/moto-x-2014/help/boot-animation-phone-stuck-t3148085
Click to expand...
Click to collapse
The new boot ipscreen doesn't appear on my device, but WhatsApp has warned me of date and time wrong, set to July 1, through Moto Display.
I am having the exact same issue. Has anybody had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a bunch people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
So I can't boot my phone. Previously stable h811, unlocked bootloader running latest 20i Extreme 3.3 MM with G4 Tweaksbox. I have a Qi/NFC sticker on the back, but which has worked flawlessly and was not in use when the phone died. Here's what happened and what I have attempted.
Problem began when phone simply went black. The only thing running was Maps, which had a route displayed but was not in navigation mode. The screen went dark like normal, and when I went to wake the phone, nothing happened. I was in the car and tried plugging in the car charger and did not get a charge light. Pulled the battery and was unable to get a response. The phone and battery were quite warm.
When I got home, I tried a different battery, and the screen turned on to the LG initial boot screen, but nothing else happened.
After many battery pulls and attempts to boot into recovery, I tried it with the phone plugged into the computer. Finally, it showed the charging screen and light, and after several more attempts- pulling the battery and inserting it, then powering on, it appeared to be booting, (boot animation started, but then looped and froze on the initial boot screen (with bootloader state: bootloader unlocked in the upper corner). After another round of attempt/battery pull, it booted all the way up, but at that point I had my sim pulled. Pulled the battery and tried to restart and it froze on the initial boot screen again. Haven't been able to get into recovery at all, can't get into download, can't boot past the initial LG screen. Sometimes it loops, sometimes it just hangs. Nothing I do pressing combos of buttons, plugged into computer or unplugged, seems to change anything. The very farthest I've gotten is the breathe blue light before the boot animation, but then it looped. Now it's boot looping plugged into the computer.
Any ideas? I'm at a total loss.
bdportil said:
So I can't boot my phone. Previously stable h811, unlocked bootloader running latest 20i Extreme 3.3 MM with G4 Tweaksbox. I have a Qi/NFC sticker on the back, but which has worked flawlessly and was not in use when the phone died. Here's what happened and what I have attempted.
Problem began when phone simply went black. The only thing running was Maps, which had a route displayed but was not in navigation mode. The screen went dark like normal, and when I went to wake the phone, nothing happened. I was in the car and tried plugging in the car charger and did not get a charge light. Pulled the battery and was unable to get a response. The phone and battery were quite warm.
When I got home, I tried a different battery, and the screen turned on to the LG initial boot screen, but nothing else happened.
After many battery pulls and attempts to boot into recovery, I tried it with the phone plugged into the computer. Finally, it showed the charging screen and light, and after several more attempts- pulling the battery and inserting it, then powering on, it appeared to be booting, (boot animation started, but then looped and froze on the initial boot screen (with bootloader state: bootloader unlocked in the upper corner). After another round of attempt/battery pull, it booted all the way up, but at that point I had my sim pulled. Pulled the battery and tried to restart and it froze on the initial boot screen again. Haven't been able to get into recovery at all, can't get into download, can't boot past the initial LG screen. Sometimes it loops, sometimes it just hangs. Nothing I do pressing combos of buttons, plugged into computer or unplugged, seems to change anything. The very farthest I've gotten is the breathe blue light before the boot animation, but then it looped. Now it's boot looping plugged into the computer.
Any ideas? I'm at a total loss.
Click to expand...
Click to collapse
Im bricked myself from another issue but i think there is a black screen of death issue with some of the g4s
Try to boot download mode and re flash stock kdz with Lg up tool
You will loose all data though.
Good luck on help here noones helped me at all .
The g4 is just not a good device or user friendly
Sent from my LGMS631 using XDA Free mobile app
Black screen of death here too
Yesterday, I was using Chrome, site loading, screen just went black. I had about 1/2 battery at the time. I figured maybe the battery was just reporting wrong. When I got home, swapped batteries, same issue. I've been able to get into recovery and attempt a factory reset a couple of times (after many frustrating attempts.) The phone seems to only be able to be powered on for about 30 seconds before it goes black again. I'm going to attempt to fix with download mode now. If anyone else has solved a similar issue, any tips would be appreciated.
Hardware appears to be at fault!
Check this out, people!
http://www.androidauthority.com/lg-admits-g4-bootloop-problem-hardware-fault-669603/
Spread the word. Sounds like this is our problem. Apparently affecting mostly models with serial numbers starting 505xxxxx... which is what mine is. Called LG and they issued an RA# and shipping label to send it to them for service. I'm a little concerned since I didn't buy mine through a carrier, but this seems more like something of a soft recall than strictly a warranty issue, so I'm hoping they fix it no questions asked. I'll keep you guys posted on the progress.
Same thing happened to me today. My phone randomly shut off and it won't boot. Its stuck at the Android logo. I wasn't messing around with it. Just normal use (Snapchat, youtube). I tried booting into recovery but it just goes back to the android screen LG logo and keeps looping. I at least want to wipe the phone before I send it (personal info).
Same here. Mine has serial number starting 505, was purchased back at end of 5/2015 with not problems until this. I filled out the warranty repair form on LGs website and they sent me an RMA with label to get it fixed. I sent it in, they sent it back, and the only thing I see is on one sheet they printed out and included in the package said 'replaced board'. However, when I started up the phone it looked like new initialization with xx of yy apps initializing and then it began bootlooping with the LG splash screen. So frustrating!
So, this time I contacted t-mobile via their online chat, and did a warranty exchange through them. They will send me a replacement LG G4 next day ups air and I will send them the defective one for them to claim warranty themselves. We'll see where this goes. I might just take the replacement unit and do a tmobile jump exchange to another device. I wanted to wait for the new line of HTC nexus phones that are rumored for this year (and was loving the LG 4 until it died), but I might need to just jump twice this year and go for something like the new Samsung S7 of new LG G5 now and then again switch to HTC nexus once that comes out.
Sent mine to LG, and they fixed under warranty with no questions asked. Got it back within a week. All good now.
Hi,
I got my Mi A2 about 3 or 4 days ago, and really love it, but today I set it down for a minute after using it, and it worked perfectly fine, and when I picked it up, the screen wasn't responding, so I tried restarting the phone and all it did was light up the screen, but it was all black, and turn off a minute later, but you can tell it would boot up because the phone would respond to me using the fingerprint sensor (by vibrating), and the notification LED would also light up when I went to charge it, along with vibrating when I held in the power button to restart. I tried messing around with it, and the screen turned on once, but was super glitchy and shuttered and jumped around before turning off again. When I boot it into fastboot mode the screen stays on (but the entire screen is all black, but you can tell the screen is lit), and it's recognized by my computer when I use fastboot commands. It's just especially weird, because I have not dropped the phone once, and I have kept the stock firmware and haven't rooted or unlocked the bootloader or anything yet. I can't tell if it's an issue where the device had a faulty screen or if the motherboard is the problem since the screen can turn on initially when booting up, but turns off a second later and won't come back on. I've contacted the seller I bought it from, but I'm wondering if anyone else has had the same issue because I don't want to run into the same thing again.
Thanks in advance!
Seems like the device has faulty hardware. From the facts you mentioned, it can be assumed that the problem lies with motherboard. It's better to get the piece replaced since you have recently purchased it.
one6pa2 said:
Hi,
I got my Mi A2 about 3 or 4 days ago, and really love it, but today I set it down for a minute after using it, and it worked perfectly fine, and when I picked it up, the screen wasn't responding, so I tried restarting the phone and all it did was light up the screen, but it was all black, and turn off a minute later, but you can tell it would boot up because the phone would respond to me using the fingerprint sensor (by vibrating), and the notification LED would also light up when I went to charge it, along with vibrating when I held in the power button to restart. I tried messing around with it, and the screen turned on once, but was super glitchy and shuttered and jumped around before turning off again. When I boot it into fastboot mode the screen stays on (but the entire screen is all black, but you can tell the screen is lit), and it's recognized by my computer when I use fastboot commands. It's just especially weird, because I have not dropped the phone once, and I have kept the stock firmware and haven't rooted or unlocked the bootloader or anything yet. I can't tell if it's an issue where the device had a faulty screen or if the motherboard is the problem since the screen can turn on initially when booting up, but turns off a second later and won't come back on. I've contacted the seller I bought it from, but I'm wondering if anyone else has had the same issue because I don't want to run into the same thing again.
Thanks in advance!
Click to expand...
Click to collapse
I have the same issue. I got the device on Sunday morning by 11. I went to 6X MiUi 9 to MiUi 10 EU (Without firmware update) later returned back to A2 stock, set it up. Then was using the device, like copying files from otg etc. After that while phone was in use, suddenly screen went off with notification led working. I restarted to fastboot, no bunny but device is detected with fastboot commands. Only black slightly backlit (it seems) screen. Suspect issue with Ambient display(It was on) coz 2-3 times screen flickered while using from the time I got it.
I then went back to MiUi 9 to see if it was an issue with rom. I could feel phone turning on, vibrations, notification led etc. MiUi 9 was flashed successfully from Edl again and boot up shows same issue. I confirmed it is a hardware issue.
Returned to A2 stock rom (issue still persists), ordered a replacement device, returned the device on Monday, expecting replacement in 2-3 days as it is shipped now.
hi! I have the exact problem. May i know if you already fixed it ? Thanks
Moto Z3
Verizon
Good morning, all.
So, following an OTA update yesterday morning, the phone is stuck in a boot loop. The boot loop bounces between the startup Moto animation and the Verizon splash, but never gets further. In addition, if the phone is left in this state, it heats up considerably.
I've tried the power + volume down button combo (with and without the SIM and microSD cards) to get into the special boot menu options, but the results aren't promising. No matter which selection I make, no computer will recognize it being connected, so I'm not sure what else I can do.
And, unfortunately, LMSA will not "see" the device connected to the computer.
Is it just dead or am I just unaware of that proverbial "easy button" fix?
Any and all advice/recommendations/suggestions are welcome.
Verizon is sending a replacement, but it sure would be nice to figure out not only exactly why this incident occurred, but a way to prevent it from happening in the future and a way to fix the issue should it arise again.
Thanx. in advance.
Your browser is not able to display this video.
did you ever find a fix I have one that is in the same state