Related
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
autonami said:
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
Click to expand...
Click to collapse
Sounds like the power button may be stuck which is a known issue with this phone. Here is a thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1931310
autonami said:
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
Click to expand...
Click to collapse
I've come to find out if the phone crashes this will happen, it's normal behavior believe it or not. If you will be patient and wait for about 7 to 10 minutes, the phone will finally reboot. The next reboot will be normal time again. This might be the device's way of protection, IDK.
cwyman said:
Sounds like the power button may be stuck which is a known issue with this phone. Here is a thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1931310
Click to expand...
Click to collapse
thanks, this did the trick. but i think it may have been more so the volume up button. there is a metal piece that surrounds the volume button on the board, somehow it was coming off, pushed it back on and mashed the buttons a bunch, came right on.
autonami said:
...it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly...
Click to expand...
Click to collapse
This is almost certainly caused by a bad/stuck power (on/off) switch. It's a very common problem on all the US-carrier Galaxy S2 models. (Sprint, Boost, Virgin, Telus, T-Mobile, AT&T, etc. I don't think Verizon sold the SII)
You can check the switch by gently touching the physical switch (plastic cover/"button" removed) with a toothpick/pen/etc. As a "snap-action" switch, it shouldn't activate until you hear/feel it "snap" closed. If it's activating with a light/slight/tiny touch, the switch is bad. On my Sprint GS2, even the slightest brush against the power button caused it to wake the phone. Sometimes it would stick "on", and then the phone would reboot. I bought a new switch, soldered it in, and have no problems since.
If you don't have insurance coverage and are out of warranty, you can replace the switch yourself. Several eBay sellers offer replacement power switches for the SGH-T989 Galaxy S2. (about ten bucks)
Or, if you don't have mad soldering skills, several offer mail-in repair service as well, and most seem to have great feedback.
Two days ago, my T-Mobile Samsung Galaxy S3 dropped out of my coat pocket as i was running for the bus. I picked it up and saw the screen was cracked along the top left and bottom left hand side. Everything was working for the past two days and i figured i'll just wait till Christmas to get a new phone. This morning i took my phone off the charger and turned it on. The Samsung logo flashed, and then the boot animation for Slimrom (the custom rom i'm currently running on) flashed for about a second but then the screen went black. I did a battery pull but the weird thing is whenever i put my battery back in, even without touching the power button, it boots up by itself but then the screen goes black again. I can access TWRP and download mode but they both go black after a few seconds as well. I was able to successfully turn on my phone and have it fully function for about 15 minutes after putting it back on the charger, but it quickly blacked out again. It also keeps randomly booting up by itself which is weird. Im guessing this is a problem with the screen itself, but could it be a software issue because the device keeps booting up by itself? If it is the screen, will i have to buy a new one or is it not worth it? I've also tried using a different battery and i have the same issue so it can't be that. Any help is appreciated!
Sounds like an issue with the power button, it probably got stuck somehow either when you dropped it, or after you dropped it. Do a simple search for power button and you will find ways to fix it!
Holy crap i didn't even think of that! It makes total sense since every time i even tap my power button, even for just a second, it turns on. I've read around that clearing the cache or a factory reset could work. Is this true?
Unlikely, unless it's a software issue but it's always a possibility. Slam the phone against something to try to get the power button back into place, or open it up and try to see if you can fix it yourself, or replace it
The problem seems to be gone. I haven't had any issues for two days now. All i did was press the power button really hard multiple times. Thanks for you help man!
Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.
SirDigitalKnight said:
is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.
Click to expand...
Click to collapse
It just goes blank. No notification at all. It's been on for 20 percent now. But I am sure it will turn off again. Maybe it's because it gets hot. I dunno.
bustanut666 said:
Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
Click to expand...
Click to collapse
Did the watch suffer any kind of mechanical shock ?
Cst79 said:
Did the watch suffer any kind of mechanical shock ?
Click to expand...
Click to collapse
Not that I know of or anything very severe. I have pumped it on a wall before but that's it. Never dropped or anything. Just seemed like after the updates it when crazy. And I've tried almost every solution I've read on these forums.
So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.
bustanut666 said:
So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.
Click to expand...
Click to collapse
That sounds like it is trying to update or download the apps to the watch... which it sounds like you have 12 installed on your phone.
Have you tried deleting ALL the apps from you phone (only the 12 apps for the moto 360) and then uninstall Android wear and factory reset the moto 360 and then download Android wear to your phone and pair the 360 as a new watch and test it for a while and see how it works?
I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)
ykazimir said:
I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)
Click to expand...
Click to collapse
I never connect the bluetooth to listen to music. It just shuts down.
Maybe you are doing something that causes it to overheat. Do you leave it on for prolonged periods of time?
Been having this same issue. The Moto 360 powers off and when I press the power button to turn it back on I see the splash "M" image then it turns off. The only way to get it to stay on is to put it back on the dock and when it turns on it says shows the updating apps screen. Any fixes?
I haven't figured out fix. Because of this I barely use my watch anymore. Sucks.
Sent from my SM-G900V using Tapatalk
yep, haven't used my 360 in 6 months because of this problem. it's a shame really. my warranty went out like a week ago too :/
Same thing has been happening to me as well. Not doing anything on the watch, it just goes into sleep of death and I have to put it back on the charger. Battery level is usually above 60 or 70 %.
Same issue!!!
Guys even I had same issue, my watch will heat up suddenly and turns off. I've to put it in dock to turn it on again. This issue never occurred after stopped using some of the new watch faces which allows dim option. I'm currently using some of the old watch faces which are working fine. May be these new watch faces are not working fine with latest update. Now I don't face any problem and battery life is also great.
Try this solution and let me know.
Watch faces has nothing to do with it. My watch will not fully boot into android wear unless it's on the dock no matter which watch face I am using. Even the minimal face.
Sent from my SM-G900V using Tapatalk
Anybody able to find a fix? This is so annoying
I'm having the same problem. I purchased a used Moto 360 off eBay for $120 and it turns off randomly even when the battery is pretty high for example it just turned off randomly at 80%. Then when I try to turn it on it boots up till the M logo or sometimes to the colorful part but then turns off again. It also only turns back on by putting it on the charging dock. Also it shows the Installing App 1 of 1 at startup and then suddenly shuts down again. I am extremely annoyed and frustrated because of this as I spend $120 on this watch and now I get this which makes it unusable and a waste of money. Please tell me guys if any of you find a solution!
Unfortuanately, mine is doing the exact same thing. I thought I had it working again, but as soon as I tried to give GPS permission to Google Fit (wouldn't run without it), it spun there and just went black. I literally just took the watch off the charger, so it isn't that. Now, if I hold the power button or press it multiple times, it tries to boot up, and will stop before it even gets past the normal Android boot animation. Sometimes, it won't even get past the Motorola boot animation. Now, when I put it on the charger, it seems to load perfectly fine, and even gets past the 'Starting apps' phase. Again, once it loads back up, my watch shows +90% battery. I've tried a factory reset, unpair/repair, and still no go.
Found a pattern
My app does the same but i have at least a pattern when it happens. It seems like it is as soon as there has been an update either in Android ware app or in soem app that has an wear application.
Hello, i faced a serious problem this evening, just after i finished a call phone, the screen of the phone went Blue and then it went off, i started to put it on again and then it showed the screen with LG and then it went black no boot at all. i removed the battery and i tried again and still the same, so i tried to remove the battery and put it again and plug it with the computer, it went on with charging battery and then suddenly went to blue screen again.
So i tried to put the recovery mode with power down and on/off and it worked i got the recovery mode screen with factory reset but it was only with factory reset, i tried it and then i put yes and it reboot and then after LG screen, it went black again....
so i tried to put download mode with usb cable but it wont, always i got the blue screen. what should i do, where is the problem exactly for people who had the same problem ? the batterye ? the motherboard ?
anyone to help ? i changed the battery and it wasnt coming from it, and the phone showed others anormalies like sometimes u can charge the battery and you see the % and sometimes it goes blue screen and shut down. anyone had the same issue before ?
My LG G3 randomly started giving this problem for 3-4 days till it went completely bad. It just wouldn't get past the Blue Screen. Since I had to take a backup before taking any further action, I have been able to get it up and running for very short durations by keeping the cell phone in the freezer for an hour or so. Yes. I am not kidding. After it freezes, I can get it up on about 5th or 6th attempt. Sometimes even more. Be mindful that the battery is now showing a red humidity marker due to the freezer.
I am thinking of asking LG to repair it. What a piece of crap. Its only 18 months old for me.
Hi all
I restarted my watch using settings menu. Then left the watch on charge and went away. Next day found watch to be dead with black screen. I hard reset it by holding button for 10 seconds. It seemed to start but then gets stuck on start up ( at different places and different booting time, every time) Have not able to complete boot it once.
Then I thinking I am very clever, went into the boot menu and deleted cache and data. It seemed to load a bit longer than last times and actually went on to connect with phine and started update but got stuck on 20 out of 27 apps.
So every time it gets stuck, it black screens and the only way to bring it out of this state is to hold down the button for 10 seconds. It does not black screen in FASTBOOT menu. I am not sure if there is any warranty left on this watch as it was bough second hand and till now had been working really well for about 3 weeks.
I have installed adb drivers but it doesn't show up on the PC. May be because i didn't do the developer options step before I am guessing. Anyway I have no idea what is happening to the watch and if it is even recoverable or not.
Any one seen this before? any ideas what I should do?
Thanks so much
One thing that gives me confidence that battery is not dead is that if I leave it in the fastboot menu screen then disconnt the carger it stays there.
I tried sideloading Android Wear 1.4 image. It fails at 57 or 58% , always
Just a note to anyone with similar problem. My watch sorted itself out after a few days. I think , if you leave your watch on charge and don't touch it for two days then it somehow help. I am not sure how it started working. My suspicion is that the watch either had water in it that dried out over two days or the charge had somehow gone so low that it needed a very long charge to stabalize. Anyway, it works now.