Ok so basically yesterday my phone barely wanted to start up. It started up - worked for about 30 seconds and froze until I had to pull out the battery.
Happened repeatedly with 2 different batteries, so I got pissed and formatted it. After formatting, it started up, but has been EXTREMELY slow.
Like up to the level that downloads download at 30 kilobytes per 10 seconds. And everytime I touch something it takes like 5 seconds to respond. Tried changing rom - now it's stuck on the LG starting screen.
Any help?
Related
TL;DR, phone dropped on the floor, flat on screen, no damage except for a ratling noise in the bottomleft corner of the phone where the vibration is, which i didnt notice until after i dropped the phone. Charged a few times, but refused alot of the times, now it doesn't charge anymore.
Right now, every time I connect the phone to a charger, it starts showing the red LED, vibrates non-stop, until after 15 minutes it stops vibrating, giving fast pulses of vibration to slower pulses, and for the last 30 minutes, while connected to my laptop, it gives off a medium-soft vibration every 5 seconds, slowly degrading to every 20 to 30 seconds after half an hour.Interestingly aswell, it vibrates very strong for the first 30 seconds, than vibrates normally for the next 15 minutes before it stops vibrating. It's very consistent in this behaviour
Full story:
I bought the phone April 2013, and it was working fine until somewhere November 2013.
The percentage of the battery wasn't consistent at all. It was jumping every few seconds between e.g. 70, 73, 67. 60, 70, 71... sometimes it fell down to 23%, next thing happens, the system gives me a pop-up "Shutting down". It shuts down normally, I boot it up normally, and that's pretty much how it went. I made backups, continued with the use. Sony Customer Care tells me that I should update it/reset to factory settings.
I connected the phone for an update, and as the phone is updating, it shuts off because of the problem stated above (even with cable...).
Phone bricked, sent it April 2014 for service because I had a different phone and I was too lazy to send it back.
3 weeks ago I got my phone back, fully working (Yaay, right?). 2 weeks ago, I was sitting, doing my natural business and put the phone on a shirt I had at the window. The slippery phone pretty much slides from anything that's soft and has the slighest angle, so my phone starts sliding super slowly, and 10 seconds later it hits the floor screen down.
It fell so perfectly flat on the screen, on the perfectly flat tile, that the screen is still perfectly clean and there is no sign of damage. But, the phone was off (it was on before it fell). Shocked, I boot the phone, and it boots, with a sense of relieve I continue using it. However, I did hear a rattling noise from the bottom-left corner where the vibration is located (vibrator... hihi).
Here's where the new problems start...
Day 1, I shut down my phone on 15% so I save battery for later, for pics and such. Suddenly when I try to boot it, it tells me the battery is too low (a few red led flashes). 1 hour later, it turns on with only using the power button.
Day 2, I use the phone normally, phone drops to 2% and just waited until it would shut down by itself. It didn't, stayed like this until 1%, to where I have shut it down and plugged into the USB cable.
Day 3, The phone didn't show any LED, and when I would reconnect it to the AC charger, it would show the red led for about a minute and go off again. Phone stopped charging... Later I tried the car charger, still nothing. A few hours later I tried the car charger again and suddenly it started charging again to the full 100%.
Day 5, I had the phone in my pocket, and had to drive for about 60km. The phone was at 30%, and I found it to be turned off, showing me the battery is low through the red led. 60km was about 30 minutes, so I sensed something was wrong here. It didn't charge again, nor through PC or AC charger, not even the car charger.
Day 6, I tried the car charger, and again, it started charging, got it again to the 100%. I'm just browsing in the afternoon at 51%, and my screen turns black. I press the power button to light the screen, but it blinks 3 times red. I put the phone in the charger, nothing... Later that evening I put it again in the charger and left it for an hour, and the red LED finally showed! Well, the red LED was lit for at least 12 hours and the phone didn't respond to anything.
Day 7, It did vibrate 3 times when it tried the Power Button + Volume down, but blinked red again and no response.
Day 8, I started pressing the phone gently, and it started to vibrate on pressure. Pressing = vibration, release pressure = vibration stopped. What?? It could keep this up for about 5 minutes before it stopped.
For the last few days i try charging it occasionally, but the only progress that I got, is that the phone started vibrating non-stop when it was connected to a power-source, and the red LED was lit. First it would stop vibrating when I pressed the sides of the phone in a certain way, and just lay there silently with the red led. Now it just vibrates non-stop and there's no helping it.
Right now, every time I connect the phone to a charger, it starts showing the red LED, vibrates non-stop, until after 15 minutes it stops vibrating, giving fast pulses of vibration to slower pulses, and for the last 30 minutes, while connected to my laptop, it gives off a medium-soft vibration every 5 seconds, slowly degrading to every 20 to 30 seconds after half an hour.Interestingly aswell, it vibrates very strong for the first 30 seconds, than vibrates normally for the next 15 minutes before it stops vibrating. It's very consistent in this behaviour.
So, I found this thread:
http://forum.xda-developers.com/xperia-z/help/hardware-fix-xperia-z-charging-booting-t2760911
I contacted Sony Support, they said there are no VOID indicators in the phone, as they will be able to tell if there has been a person in the phone. There's an unauthorized service nearby who can order OEM Xperia Z parts, so I doubt it they will notice. When I asked if I would still have warranty after the unauthorized service, but they would be unable to tell because he/she used OEM parts, they simply said "You will lose your warranty", because they probably couldn't contradict it.
Judging from the symptoms, do you assume it's a dead battery, or could it be someting completely else? It dropped, something rattles and it gave me a hard time charging it, but still it worked. Note that I used the phone intensively for 6 hours before the screen went black at 51% (fairly the same as using your phone to 0% and suddenly it just turns off).
I don't feel like losing my phone for 30 days again, nor getting my data wiped (ALWAYS BACKUP, I was too stuborn not to, even though I had plenty of chances...), and i'd rather just pay a few bucks to get my battery replaced (about 50 dollars). The time and data is worth it, there is a shop servicing Sony Xperia's after warranty, so at least someone who knows how to fix these phones.
The back-cover is not water resistant anymore as the glue detached because of the excessive heat from the processor. So I might just open up the phone and see whats going on anyway?
I've had my Gear Live for about 3 weeks. All of a sudden today I noticed that the watch was getting hot. I looked at it and it was stuck on the boot screen (the one that says "Samsung Gear Live"). It just sat like that for a few minutes, getting hotter and hotter, and then it would shut down. If I press the power button it will do the same thing. I've tried charging it up (in case the battery was low, even though it was only off of the charger for about half the day), but it's still doing the same thing.
Anyone else experience this? Anything I can do to get to to boot up again?
Edit: I just found out how to reboot into the bootloader, but when I try to reboot into recovery it hangs for a few seconds, goes dark, flashes the boot logo for a split second, and then apparently turns off.
enormous said:
I've had my Gear Live for about 3 weeks. All of a sudden today I noticed that the watch was getting hot. I looked at it and it was stuck on the boot screen (the one that says "Samsung Gear Live"). It just sat like that for a few minutes, getting hotter and hotter, and then it would shut down. If I press the power button it will do the same thing. I've tried charging it up (in case the battery was low, even though it was only off of the charger for about half the day), but it's still doing the same thing.
Anyone else experience this? Anything I can do to get to to boot up again?
Edit: I just found out how to reboot into the bootloader, but when I try to reboot into recovery it hangs for a few seconds, goes dark, flashes the boot logo for a split second, and then apparently turns off.
Click to expand...
Click to collapse
I'm definitely no professional at this, and I'm just taking a wild guess. If you have it on constantly, I'd just let the battery run out and keep it off for about two days or so.
Just received my OTA upgrade.
Everything went well up to the point were it says - Android is starting. It counts up to 51 and then says Starting Applications and then immediately (shown for half a second) - Shutting Down.
This goes on and on every time I restart the watch.
In addition, it gets so hot that I think it will melt.
Any ideas how to fix that?
super_joe said:
Just received my OTA upgrade.
Everything went well up to the point were it says - Android is starting. It counts up to 51 and then says Starting Applications and then immediately (shown for half a second) - Shutting Down.
This goes on and on every time I restart the watch.
In addition, it gets so hot that I think it will melt.
Any ideas how to fix that?
Click to expand...
Click to collapse
I'm experiencing the same issue. I hope that someone has some ideas on how to fix it.
Let it rest for an hour. Then try again. Works for me.
Sent from my A0001 using XDA Free mobile app
As above. I think it's heat related. I had similar when I was flashing the stock images from scratch. I let it cool down then boot it up again and it was fine after that.
I am sorry, but nothing helped.
Sit and Wait didn't help. Waited over night, same result the other day.
I also wiped the watch from Recovery. For just one time the watch started and demanded more at least 20% power, so I charged it and moved on with the configuration, but all of a sudden the watch turned off.
Since then, after several wiping tries, I had a new behaviour. Watch started with the 4 colored dots, after about 2 min just turned off without showing any other display.
Any other ideas?
super_joe said:
I am sorry, but nothing helped.
Sit and Wait didn't help. Waited over night, same result the other day.
I also wiped the watch from Recovery. For just one time the watch started and demanded more at least 20% power, so I charged it and moved on with the configuration, but all of a sudden the watch turned off.
Since then, after several wiping tries, I had a new behaviour. Watch started with the 4 colored dots, after about 2 min just turned off without showing any other display.
Any other ideas?
Click to expand...
Click to collapse
@super_joe any luck?
The sit and wait method ended up working for me as well.
I too had the same issue. After restarting the watch it kept shutting down. Then as last attempt I kept the watch on charging cradle and charged the watch. While charging the watched booted normally. Then found out battery was at 3%. But oddly before update it was 98%.
Anyways now it's working normally.
there is no consistent way to charge the watch anymore without overheating?
I have the same problem
Same problem here. after running fine with LeeDroidV2. But after the battery died it wouldn't fully start anymore.
Thought it was heat related too so I put it on the A/C fan. Still switches off. Gonna flash stock and will report back
I can't get it to work. It says "Starting Apps" after loading them (38 of 38) and the "shutting down" Just flashed stock 5.1.1. Any ideas?
finally back alive! I don't know what the problem was. When it finally booted without shutting down, the battery was at 2%. Even though it was on the cradle for 2hrs.
The first Moto G started off fine, though fairly constantly laggy (which I blamed on the low/mid specs of the phone.) Then it started getting quite warm while using it, then it started turning off with 5-10% battery left and would not turn back on, even after charging, unless you tried to turn it on 4-5 times. The first few tries, the white LED would just blink with no other sign of life from the phone. Soon after, the camera stopped functioning, so I decided to send it into Motorola for repair/replacement. I couldn't get the phone to factory reset normally, so I factory reset the phone using fastboot. Upon reboot, it took FOREVER to boot back into Android. I honestly thought the phone was bricked it took so long. Once it got booted, I shut it down, boxed it up, and sent it on it's way.
Replacement phone came and all was good again. Camera worked, phone didn't seem laggy this time, and phone charged and discharged like it should. This lasted about a week. The phone started getting warm during use again. The phone shut off at 22% battery and would not charge a single percent on the charger or turn on for at least a half hour. I decided to prep this replacement to go back to Motorola to try again, and again had to factory reset using fastboot. Again, the reboot after factory reset took FOREVER. I wanted to know how long this actually took, so I timed it. I've seen phones that take 5-10 minutes, but this Moto G takes the cake at 20 WHOLE MINUTES.
I am seriously considering jumping ship to something completely different if this is just how this phone is. Very disappointing for it being such a highly rated phone on several websites. Is this normal or did I get 2 lemons in a row?
Stock ROM, un-rooted. After 4 to 5 hours of run time, whether in use or idle, the phone shuts down. If you go to re-start it, you are greeted by three short vibrations after the first one, and it will NOT boot. If you press the little re-set key by the SIM slot, it re-boots perfectly like nothing ever happened and after 4 to 5 hours, this repeats again. Everything works PERFECTLY with this peculiar exception. Any ideas?