Hi guys,
So I finally flashed cyanogen mod stable build onto my Sprint Galaxy s3. Everything has been fine the last couple days. However, I was just using it normally, and it shut down all of a sudden. No smooth shut down, just turned off completely.
It now will not even turn on. I take the battery out, put it back in, it flashes the Samsung graphic for a second and shuts off. The battery is fully charged. I plugged it into my computer, saw the charging screen (again for 1 second) before it shut off again.
Is this bricked for some reason, even though everything was working fine for multiple days?
And more important, how can this issue be fixed?
Hopefully that is enough of an explanation, but please feel free to ask for any more clarification.
Hope you can help!
It's called sudden death syndrome. Your power button is messed up. Common issue with the S3. Try blowing some compressed air into the power button and playing with the button.
Sent from the future via Tapatalk 4
Related
went to hit the power button to use my phone and nothing happened... not sure if it was froze or if the power button stopped working... i held it down and nothing... was sitting at a black screen...
had to pull the battery to get it working again... has anyone had this happen? is the phone actually on and the power button stopped responding or did it shut down and the power button stopped responding?
4.0.2 unlocked... not rommed... adw launcher
I had that happen once. I went to pick it up and turn it on, and it was just dead. like it just powered off by itself.
Sent from my Galaxy Nexus
It's called the Black Screen of Death. Usually happens when a custom kernel doesn't play nice with your phone.
I was on stock 4.0.2. No root.
Sent from my Galaxy Nexus
Yeah it's happened to me anywhere from 3-5 times these past few weeks. Either that or it will just reboot itself randomly. I'm not complaining though... it's nowhere near as bad as my Nexus S was. Lol
Sent from my Galaxy Nexus using xda premium
this happened to me twice today for the first time ever, am on a custom rom but havent updated in a few weeks... Im seriously thinking its Chrome for android...as thats the only thing i changed recently (google voice updated too). and i seriously havnet used my phone lately other than using Chrome.
It happenned to me once since I've had my nexus. Don't even think about why
Happened to me today, screen was blank but the LED notification was blinking. Asked my fren to call me and it was ringing meaning the phone was still on. Had to remove the battery and put it back in and then it was fine.
Mine turned off on its own last night, it was when I plugged in my charger while it was turned off at the mains.. very strange.
are any of you on 4.0.4?
hopefully not
I haven't seen any shut downs or random reboots on 4.0.4 yet. It's been less than a week though, so we'll see.
Sent from my Galaxy Nexus
The only time my phone has ever shut off with the power taking 5 or so seconds to work has been because of a music app Slacker.
It shuts my phone down randomly. I think it is not fully compatible with ICS.
Hi,
My phone has been working fine since I did S-off and installed a LeeDroid 2.3 ROM a year ago. This wednesday I had to install another ROM because of boot loop problems with the previous one. I used VJ CM10.1 v5.3 which worked amazing for almost 2 days. Yesterday at night while the phone was charging I couldn't unblock it (black screen) and the orange led kept light event without usb cable. I removed the battery and since then the phone only vibrates continuously when I turn it on. Even without battery if I use an USB cable it starts vibrating inmediatly, of course with any screen response (in the dark you can see a very light attempt to start the screen but nothing else). The PC don't detect anything when I plug it and I can't use any key combination to get to Recovery.
I wasn't doing anything dangerous, only charging but the ROM was only 2 days old. Does anybody now what is happening or how could I fix it? Sorry if It has been responsed but I think not (It's no the 7 vibrations problem).
I can provide more information if needed.Thanks a lot.
Take out the battery, hold the power button for 10 seconds, then try to boot.
abaaaabbbb63 said:
Take out the battery, hold the power button for 10 seconds, then try to boot.
Click to expand...
Click to collapse
Same result. It only vibrates. I'm considering hardware fault (is 2 years and half old) but as I changed the ROM this week seems to be somewhat related.
Before we come to a conclusion, let's try all the stuff we can.
Does the phone boot in hboot?
No, all key combinations apparently have the same result.
The last thing i'd like you to try is putting your phone in the freezer with the battery taken out. Who knows, maybe it will boot afterwards.
If not, then send it to a service.
Thanks a lot, I will try. By the way, I've started saving money to buy the Nexus 4
AW: [HELP] Screen off, vibrating continuously
You will love the N4
Anyway good luck on saving the life of your desire!
Sent from my Nexus 4 using xda app-developers app
Thanks a lot. I tried everythink sooo after more than two years of Desire (including broken screen) it's time to move on to N4.
My htc google nexus has same problem, Continuous vibrates and wont turn on
Pls help, I am facing same problem, :crying:
Same problem any help guys?
Hello, last night as I was sleeping, I noticed my phone randomly rebooted. Thinking it was because of a kernel issue, I ignored it. I woke up, left my house, and another reboot. Half an hour later, constant reboots; boots up, goes to the lock screen, reboots, etc. I came home today, my pc does not recognize any phone connected. When I plug into the wall, I get a red notification light for a few seconds, then the light dies. During the constant reboots, I could go into download mode, but after a few seconds, it reboots. I never was able to get past the Samsung boot logo after recovery mode. I unplugged battery and replugged, nothing.
I was on rooted Jellybam 4.2.2, Ktoonsez kernel. I cannot remember the last time I flashed anything, but it was atleast a few months.
My microsd also died a few days ago.
Life sucks; any comments?
EDIT:
on second note, I just replugged battery and quickly went to download mode, and it lit up, then died after a second or two.
For some reason, when I put in my battery, the phone turns on.. I thought it only does that if the phone was uncharged for a few moments..
Could my internal sdcard be fried?
You don't have a brick if your phone still turns on.
Check to make sure the battery is good
And also check and make sure the power button isn't stuck.....
Those have been the culprits for many "bricks" for a while now.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jayRokk said:
You don't have a brick if your phone still turns on.
Check to make sure the battery is good
And also check and make sure the power button isn't stuck.....
Those have been the culprits for many "bricks" for a while now.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I switched the battery with a back up, same problem.
How do i make sure the power button isnt stuck..? It clicks when I press it.
EDIT:
I just took the phone apart and freed the power button so the display and the motherboard are laying side to side with only the display connected to the motherboard.
The phone still turns on automatically when i plug in the battery.
jayRokk said:
You don't have a brick if your phone still turns on.
Check to make sure the battery is good
And also check and make sure the power button isn't stuck.....
Those have been the culprits for many "bricks" for a while now.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I think it might be the power button thats some how stuck, but I cant figure out why.
I opened the phone and everything seems fine..
I spam pressed the power button out of boredom and my galaxy booted up fine, then died again.
EDIT: wow, i kept spamming the power button and now it boots up fine..
please delete this thread
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.
Hey All,
I'm currently on the CM11 04/22 nightly, and have made it all the way up to the 04/27 nightly to try and resolve this issue and have not been able to. Basically - the sudden death issue has been hitting me very hard - I can't use my phone at all.
I understand the 04/11 nightly is stable and doesn't have this issue, howevery CyanogenMod does not have this on their website.
Does anyone have this install available? (CM-11-Nightly-20140411-D2LTE.zip)
Thanks so much in advance
SLiK
please explain what you mean by sudden death? thanks
rkant18 said:
please explain what you mean by sudden death? thanks
Click to expand...
Click to collapse
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
SLiK786 said:
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
Click to expand...
Click to collapse
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone: https://www.youtube.com/watch?v=3Glllc7bEJs
Good Luck
imcol said:
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone:
Good Luck
Click to expand...
Click to collapse
I'm fairly confident that this isn't the power switch. And if it were I'm not sure how comfortable I would feel breaking the power switch off.
The thing that begs me to think this is a software issue is that I'll have 45% battery, the phone will die, and then I'll try to turn the phone on again only for it to tell me I have 1% battery left. I'll put the phone on charge (after it dies again) and it will say charging - 45%.
Anyway I've rolled back a few updates and it seems to be fairly usable now...
Try cleaning the USB port real well and don't use a cheap cable. Use a needle and make sure there is no lint packed in there. These things can cause the phone to cycle itself even when not plugged in. I've fixed several doing exactly what you describe.