My moto X 2013 met an unfortunate demise by being dropped onto concrete. The phone will not boot, and cycles through the power on vibrate, wait about 10 seconds, and then power on vibrate again ad infinitum. I accept its fate, but there are quite a few photos/videos that I would really want to get recovered if possible. Is there any way to do so?
Related
My phone, running CyanogenMod 6.0, has been running very buggy lately, requiring a reboot (which occasionally needs a battery pull) every day or two. It's been acting like this for about a week and a half. Tonight, however, after pulling the battery because the phone froze up again, it refused to boot. I know it has power, because the backlight seems stuck on, but other than that, nothing. No (M), no exclamation mark, nothing. I've tried holding down X, I've tried holding down the Menu button, and still no response, except for one time the screen filled with random noise.
What can I do? If I send it in to Verizon, and they can get it to boot, they'll see a nice flashing CyanogenMod logo, and then they'll declare my warranty void. Is there any possible way to fix my phone, or should I just send it in and pray that it's utterly and truly bricked?
Are you able to boot into the bootloader? "Dpad UP + Power button"
Please let me know!
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.
So last night I had a very strange issue.. I pulled my S8 out of my pocket and it was completely unresponsive. Held down power for ~30 seconds, volume down+power, volume up+power, and even plugged it in to the charger to see if there was any vibration of screen response. Nothing. I have not tried any kind of modding/flashing or anything that could possibly cause a software issue, and the phone was at 80% charge. The only thing I could think of is I was walking outside earlier that day in 75 degree weather with black pants on.. maybe the phone overheated? But if so, why could I not power the phone back on, even into recovery/safe mode?
I was able to get it back on by bixby+vol down+power, then hitting cancel when it asked me if I was sure I wanted to install a custom OS. Very strange. Should I just take this back to T-Mo and swap it out for a new one, or treat this as an unlucky random occurance? I'm still within the 14 day return period.
Thanks in advance!
it is possible to have random lockup, even radiation from space, if it hits right spot could change memory value or state of CPU (that's why critical servers have memory parity bit, to pick out random memory changes and flag them as error asap), but as far as your phone, no one can tell. If it happens more than once in a blue moon, it still could be either some software or hardware. You may have 14 days to return your phone, but if defective you should be covered for 1 yr under warranty? Usually hardware issues get worse with time until it becomes apparent there is a problem. But it is your call.
pete4k said:
it is possible to have random lockup, even radiation from space, if it hits right spot could change memory value or state of CPU (that's why critical servers have memory parity bit, to pick out random memory changes and flag them as error asap), but as far as your phone, no one can tell. If it happens more than once in a blue moon, it still could be either some software or hardware. You may have 14 days to return your phone, but if defective you should be covered for 1 yr under warranty? Usually hardware issues get worse with time until it becomes apparent there is a problem. But it is your call.
Click to expand...
Click to collapse
For now I will probably just hold on to it, don't want to go through the hassle of setting up another phone. It just seems strange that it locked up to the point where I couldn't even turn it on with a hardware reset.. Like you said, I hope it was just a random occurrence. I just don't want to get a refurb if I do need to trade it in under the warranty
Thanks for the info!
To get it to reboot if it ever happens again just boot into stock recovery then select reboot system now.... Bixby button, vol + and power if it doesnt go into anything and stays in that state try just power and vol - then bixby at same time it will go into download mode it will ask to continue press vol+ to cancel press vol- hit vol- and should reboot.... So there u have two options. Num one is going into stock recov and second is download mode and denying it. Also i think for just a plain old hard reset it should work with vol- and power at same time, although in your case seems u were having trouble. One last thing as a last ditch effort and u cannot reboot phone or some weird sh#t is happening put it in download mode and use smartswitch emergecy fw and reflash fw. Pretty easy straightforward just make sure drivers are installed and smartswitch supports the s8 yet
nathpilland said:
So last night I had a very strange issue.. I pulled my S8 out of my pocket and it was completely unresponsive. Held down power for ~30 seconds, volume down+power, volume up+power, and even plugged it in to the charger to see if there was any vibration of screen response. Nothing. I have not tried any kind of modding/flashing or anything that could possibly cause a software issue, and the phone was at 80% charge. The only thing I could think of is I was walking outside earlier that day in 75 degree weather with black pants on.. maybe the phone overheated? But if so, why could I not power the phone back on, even into recovery/safe mode?
I was able to get it back on by bixby+vol down+power, then hitting cancel when it asked me if I was sure I wanted to install a custom OS. Very strange. Should I just take this back to T-Mo and swap it out for a new one, or treat this as an unlucky random occurance? I'm still within the 14 day return period.
Thanks in advance!
Click to expand...
Click to collapse
There are a few things you could try:
1. Fore close the app then reopen.
2. Redo the voice in google
3. Reboot phone (last resort)
I agree with the other guys. When you have trouble with google just hanging there it's more likely a connection to the internet issue. Good luck!
Hi
So my phone has randomly started to die about once every other day. Screen goes black (i have always on screen) and no response from any of the buttons (power button, twice volume down button for camera). I have to hold the power button until it restarts/starts (don't know if it is dead or not). Anyone else has this issue? Only wierd apps that i havent hade before is blockada.
BR
Baddar
Troubleshoot it.
Delete the app and see if it still happens. If it does, flash a raw firmware and completely wipe your device. if it still continues, its a hardware issue and you should exchange the device.
baddar said:
Hi
So my phone has randomly started to die about once every other day. Screen goes black (i have always on screen) and no response from any of the buttons (power button, twice volume down button for camera). I have to hold the power button until it restarts/starts (don't know if it is dead or not). Anyone else has this issue? Only wierd apps that i havent hade before is blockada.
BR
Baddar
Click to expand...
Click to collapse
You're in custom or stock rom?
Im on stock with no modifications.
Phone auto shuts down
Did you find any solution same thing started to happen with me twice in 2 days
The way I fixed it... go to settings, Security & Lock Screen, click on the gear icon next to screen lock, then choose the first option Automatically lock, choose "Immediately" any thing other than that causes the screen to go black. I hope it works!
@Ahmed_x this didnt work for me.
So today i was about to miss my international flight because of this stupid phone deciding to die on me while on charging so no alarm went off.
Wtf is wrong with Asus? How could this have gotten worst with the new update. Are their developers ret**ded?
This phone is being returned unfortunately. Awesome phone but if u cant trust it to give a simple thing as alarm whats the point.
It happened to me twice in three months. The smartphone got stuck/freeze in standby mode: no response from the physical buttons or touch. I use the official android 9 rom.
I managed to restart it with the power button and volume up pressed for 15 seconds.
I hope that with android 10 this will never happen again.
Happened to me today, had to hold volume-down + power for about 10-15s to get it back.
very strange using latest firmware too (WW_Phone-17.0230.2004.60)
[HELP] My ROG Phone always turn off suddenly when charge
Please HELP My ROG Phone 2.
It's been more than a month if the charge will turn off unexpectedly. This situation is experienced until today. So that every time I charge, phone must be in the dead state. I've been very frustrated. Already doing factory data reset, only lasts for one week and back like that again.
Worse, in certain circumstances the handphone suddenly dead and hard to be turned on again. When charging the battery, sometimes the phone likes to not fill. I had to unplug and re-plug the charging cable to return it to normal. Its sucks. I bought this phone in a new condition with the official warranty on January. I already did update to Android 10 when available by the system. This issue occurs after the update.
I had thought the charger that I got from the factory was problematic, until I decided to buy a new charger with the original quality with 30watt power. But it turns out the same.
Same here my phone will turn off while charging. And it will keep rebooting. Sometimes my rog will not charge
My ASUS ROG2 is starting ti piss me iff noe.. Everything I play BR in CODM alwaiz black out..every single game black out. This is not good...Is this normal? Every game has to black out?...
Hello dear community,
Something really strange happened with my device about 1.5 years ago, but since I still keep it in my house, I can't help but wonder what happened and is it fixable.
So, the story: In some sunny day in July/August of 2020 I was browsing through my device, then I locked the screen and few seconds later I remember that I want to check something, so I pull the phone out of my pocket, use my fingerprint or face to unlock it, then just during the screen unlock animation (that takes ~1 second to "expand"), the device froze halfway through and would become unresponsive. By that I mean that the touch did not work, nor the Power/Vol/Bixby buttons. The phone heated up so much that in the span of a few seconds, the metal frame got so hot that it burned the skin of my hard, then a few more seconds after, the screen went black. This was the last time the device had worked in any way.
What have I tried to do to ressurect it:
Turn it on via the power button
Plug it in a PC with Odin - Odin did not pick-up the device
Let it charge overnight
Any possible button combination to get to various screens (fastboot, etc)
What I believe happened: Since I was running a custom ROM I believe that when I unlocked the device, something went wrong in the code and it caused the device to freeze and the heat was produced by frying the SoC or something else. Taking the back glass did not show any visible (and smellable) damage.
What do you think ? Is there something that you can suggest me to try to bring the device back to life ?
Thanks in advance!
If you can't get into fastboot, download mode, recovery mode, etc. Then your phone is probably - in my experience - subject to a physical repair.