Phone Will Not Power On - Sprint Samsung Galaxy S III

I have been following the CM10 preview for quite sometime and, when it was needed, would do a clean install from the recovery.
The most recent build 8/12 I flashed without a clean install and was having some random restarts.
When I tried to call someone it stayed at the call screen and did not make any sounds.
After a couple seconds the screen went black(I thought another random restart) and will not power back on.
When I hold the power button for 2 seconds it will vibrate and the screen will stay black.
I've tried entering recovery mode and download mode but nothing seems to work.
I planned on when I got home doing a clean install and starting fresh but it seems I might be too late.
Is this a brick? Can it be fixed? and what other information is needed? Open to all constructive suggestions.
CWM Recovery
CM10 Preview Build 8/12

Perfect Finale said:
I have been following the CM10 preview for quite sometime and, when it was needed, would do a clean install from the recovery.
The most recent build 8/12 I flashed without a clean install and was having some random restarts.
When I tried to call someone it stayed at the call screen and did not make any sounds.
After a couple seconds the screen went black(I thought another random restart) and will not power back on.
When I hold the power button for 2 seconds it will vibrate and the screen will stay black.
I've tried entering recovery mode and download mode but nothing seems to work.
I planned on when I got home doing a clean install and starting fresh but it seems I might be too late.
Is this a brick? Can it be fixed? and what other information is needed? Open to all constructive suggestions.
CWM Recovery
CM10 Preview Build 8/12
Click to expand...
Click to collapse
Maybe your screen died?
Does it power on without the display or does it try to power on but doesn't?
Sometimes it IS recognizable by ODIN but there is no display, try that.
it all that fails, then you MIGHT have a brick on your hands, which would be very unfortunate.
but give it a try

Wolfbeef123 said:
Maybe your screen died?
Does it power on without the display or does it try to power on but doesn't?
Sometimes it IS recognizable by ODIN but there is no display, try that.
it all that fails, then you MIGHT have a brick on your hands, which would be very unfortunate.
but give it a try
Click to expand...
Click to collapse
No the screen doesnt power on at all. I hold the power button and it vibrates like it would start up.
I havent tried it ODIN yet ill edit when I do. Ill also try to leave the battery out for a couple hours and try it.

Perfect Finale said:
No the screen doesnt power on at all. I hold the power button and it vibrates like it would start up.
I havent tried it ODIN yet ill edit when I do. Ill also try to leave the battery out for a couple hours and try it.
Click to expand...
Click to collapse
yeah go ahead and report back what happened.
Once on my gnex it wouldnt power on but it was still recognizable by ODIN

sounds like a dead battery
Noticed that build of cm10 actin weird as well. That bein said this issue sounds like the battery is dead, not the screen. I would try. To plug it in for a bit. Bet it sits and just vibrates over and over. That how u no the battery is dead. I hate it. That bein said its not bricked

This happened to me as well they plugging it into ur charger and holding the power button if that doesn't work remove the battery for a few and then pop it back it and to to boot into recovery I that my phone was dead as well.
Sent from my SPH-L710 using xda app-developers app

Related

[Q] fml i think im bricked black vibrate errors

So let me start off with I've done research and not just posting up a new thread because I'm lazy. All of the threads that I have looked through all seem to be close but not the same as most people can boot into recovery.
Running Konis elite series III had it about a week with no issues Ive reboot plenty of times and havent had any problems once so ever. Now I think my problem happened yesterday when I needed to clear up some space and deleted the package I installed Konis rom from I figured since it was already installed the package wasnt needed anymore. I noticed later that day my number pad was no longer showing up didn't pay much mind to it figured i just needed a restart. Reboot the phone today at work and low and behold.
Phone gives me 3 vibrates no lights on regular power up.
Vol - power I get 5 vibrates green flashing led (gotta pull batt for it to turn off)
Vol + I get 3 vibrates no lights
The phone just stays black need to take out the battery in order to get the vibrate errors again.
All the threads I read regarding the 5 vibrates say its in diagnostic mode but everyone else is able to get into recovery. I think I am now the owner of an expensive paper weight. -_-
Would pulling the koni rom install file off the sd do this?
What does the vibrate error mean.. being in diagnostic mode is pretty broad how are you suppose to troubleshoot something like that :/
Are you able to get into the bootloader at all?
Are you absolutely 100% positive that you're holding volume down and power? That should take you to the bootloader. I saw someone with a similar problem, but they were just doing volume up instead.
What happens when you try to power the device normally?
And deleting the rom zip from your SD card shouldn't cause any problems. In fact, I can't think of a single way it could cause anything to go wrong. That is the only thing you deleted, right? You didn't delete anything from internal memory?
Sent from my PC36100 using Tapatalk
well i think that the 5 vibrates and green led's are indicative of safe mode. the other i'm not so sure about. if you're holding vol down and power and getting 5 vibrates then maybe there is a prob with your vol buttons. its acting as if your holding the vol up button without hitting it. maybe its stuck or something like that. just guessing though.
yo
Thanks for all the replys.
Nah doesn't let me do anything. I plug it in and it asks for broadcom drivers thats about it.
I made sure that the vol - is being pressed it gives me 5 vibrations and then the green led no recover menus/
A buddy of mine had the same problem after flashing the kingdom rom on his incredible. He sent it to the phone insurance company and they replaced the motherboard. So basically, your kind of screwed.
Well.....unless you can somehow fix it on the evo...... because I know we tried everything on his incredible, and it would just do the exact same thing every time, no matter what.
nvm same deal. it booted up intro recovery one time i erased cache and ran a saved backup on clockworks phone restarted after it finished and back to the same deal. yay.
unregimented said:
nvm same deal. it booted up intro recovery one time i erased cache and ran a saved backup on clockworks phone restarted after it finished and back to the same deal. yay.
Click to expand...
Click to collapse
What do you mean by back to the same deal?? Back to normal or back to the problem?
hardware related..
volume button keeps getting stuck some way some how and whenever the phone turns off its a pain to turn on. 30+ tries taking the batt in and out. When the phone would be turned on the volume would pop up randomly. Figured it was that so i bumped the phone on the desk with the buttons down and it cranked on did it again early today and it cranked up again after a few tries my phones toast. -_-

[Q] Tried Flashing ICS now my Phone is BRICKED HELP!

So I first heard about the ported ICS rom on Galaxys2root.com So I downloaded and flashed the file from there which was about 300mbs. Flashed then got stuck in a bootloop. I was able to restore a backed up rom. I thought it might've been the wrong rom so I found a thread here with ICS ROM. Flashed it... same boot loop problem except the first rom boot halfway to a att boot screen. this one just stayed black. At first power button turned on the phone to a battery screen but then turned black.. no animations followed. Now the phone is not responded to any button pushes. It just vibrates intermittently when I plug it in to my charger. It had maybe 35% battery life when it got caught in the boot loop the second time. I'm thinking since the power button was working at first that maybe the intermittent vibrating is because my battery is now dead and it won't charge? Is that possible or is my phone just fuqed? Some one please help!!!!!!!! p.s sorry for the long post.
uthebest said:
So I first heard about the ported ICS rom on Galaxys2root.com So I downloaded and flashed the file from there which was about 300mbs. Flashed then got stuck in a bootloop. I was able to restore a backed up rom. I thought it might've been the wrong rom so I found a thread here with ICS ROM. Flashed it... same boot loop problem except the first rom boot halfway to a att boot screen. this one just stayed black. At first power button turned on the phone to a battery screen but then turned black.. no animations followed. Now the phone is not responded to any button pushes. It just vibrates intermittently when I plug it in to my charger. It had maybe 35% battery life when it got caught in the boot loop the second time. I'm thinking since the power button was working at first that maybe the intermittent vibrating is because my battery is now dead and it won't charge? Is that possible or is my phone just fuqed? Some one please help!!!!!!!! p.s sorry for the long post.
Click to expand...
Click to collapse
Seems like you messed up on wipes. I had different problem when i didnt wipe well. The link you posted from this forum is not usable ICS. Try to get ur phone on download mode and flash via odin.
http://forum.xda-developers.com/showthread.php?t=1513359
Sent from my SAMSUNG-SGH-I727 using xda premium
Yeah that's what I'm thinking, I read later on in that thread that I was supposed to perform a super wipe. Also I can't get my phone into download mode. It won't even turn on. It just vibrates maybe every 3 seconds when I plug it in to charge. When its not plugged in it won't do anything.
Try using a different cable to get into download mode. Specifically an LG cable. I've heard of this working for other people.
Sent from my SGH-T989 using xda premium
Vibrates is a good thing.have you pulled battery?
Sent from my SGH-T989 using xda premium
Teo032 said:
Vibrates is a good thing.have you pulled battery?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes I've tried pulling the battery. Does nothing except vibrate when i plug it in to charge. still won't turn on. Why is the vibrate a good thing?
uthebest said:
Yes I've tried pulling the battery. Does nothing except vibrate when i plug it in to charge. still won't turn on. Why is the vibrate a good thing?
Click to expand...
Click to collapse
Any kind of response from the phone is a good thing. Worst case scenario is phone literally doesn't do anything or respond to any type of stimulus.
So I'm assuming you know how to access CWM and download mode but just in case there's some confusion, here's how I always access them:
CWM - hold power and volume +/- buttons until phone vibrates then keep holding all (do not let go) until CWM appears. (Others don't have to keep holding after the vibrate, but when I first flashed my phone it wouldn't boot into recovery unless I kept the buttons depressed until CWM actually appeared)
Download - (phone powered off already) hold volume +/- buttons (not power); plug in USB cable (still holding buttons); wait for vibrate (still holding buttons); download mode screen appears (release buttons only after this point)
If nothing else works, you can always try sending it back to Samsung/Tmobile to see if they'll replace it for you. If you can't get it to odin/download mode then chances are good that they won't be able to tell that it was rooted and thus would have no reason to void your warranty.
Also, if I'm not mistaken, raver's AOSP ICS ROM (the second one you flashed) doesn't have boot animation support so it's supposed to stay black on boot. Experimental ROMs especially may take a long time for first boot so you should always not touch it for at least 10 minutes before you try any kind of battery pull or powering off.
there are a lot of threads about people having problems when following instructions on galaxys2root.com
Sent from my SGH-T989 using XDA
Thanks!
I'm Back In The Game!!! The weirdest thing happened. So I went to my friends house and put my battery in his s2 to see if it had any life and it was. I threw it back in my phone and for some reason it booted up to the ROM I flashed. ICS was beautiful on it but I immediately went back to my recovery rom lol. Lesson learned. Thanks guys for the help this was my first time posting a problem on this forum and I love how quick everybody is to help.
uthebest said:
I'm Back In The Game!!! The weirdest thing happened. So I went to my friends house and put my battery in his s2 to see if it had any life and it was. I threw it back in my phone and for some reason it booted up to the ROM I flashed. ICS was beautiful on it but I immediately went back to my recovery rom lol. Lesson learned. Thanks guys for the help this was my first time posting a problem on this forum and I love how quick everybody is to help.
Click to expand...
Click to collapse
Glad to hear it worked out for you. Can be a pretty scary experience. Remember: patience is your friend, especially the first time you boot to a new ROM. If you think the boot screwed up, the best way to ENSURE that it screws up is to power it off/pull battery. Always wait 10 minutes before touching it.

[Q] Soft Bricked or Hard Bricked? (Please, PLEASE help!!!)

I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
dubbz84 said:
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
Click to expand...
Click to collapse
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
GiantJay said:
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
Click to expand...
Click to collapse
Well i just placed the battery back in, it started on it's own without my pressing anything again, and i've been timing the last 5 minutes. but it seems like it will stay a black screen indefinitely. unless i remove the back of the phone, or snap it back into place, or any kind of micro impact movements it seems, when I do that it vibrates like it's first being turned on, and shows the samsung screen, then the samsung galaxy s3 screen, then it will go black again.
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
topherk said:
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Not picking it up on adb.
dante32278 said:
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After the first odin flash i was thinking the same thing. But that's the thing, it won't stay on the download mode screen long enough for me to even try to flash anything else through odin. I'm also noticing when connected to the charger, if i make a slight impact against the phone with my palm, the screen will briefly show the battery icon as if the phone is charging when it is turned off, then the screen will go black again. When it is unplugged, is when it will show the samsung screen, then the samsung galaxy s3 screen, then go black again.
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
To me it sounds like maybe your power button is stuck "down"
If you didn't know, the power button has a fail safe reboot that happens after holding for about 10 seconds. So no matter what, if you phone is frozen or whatever, holding power more than 10s will cause it to reboot. That would also explain why its turning itself on as soon as you pop in the battery.
toolegit said:
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
Click to expand...
Click to collapse
not recently, and if it was ever dropped, it would be in it's case... But i had noticed that while it was in it's power glove case, sometimes i would have to use more than normal pressure on the power button to get the phone to respond. I was wondering if something was stuck, just haven't read anything like that happening to anyone, and when I used the jig the first time the screen stayed on.

I need help s2 acting up

This has probably been resolved or mentioned before so please do not flamed me up. Just needing some quick help.
This is not my device this is a friends. He had a darkside V8 Rom which me and him thought are giving him issues. The phone will literally reboot by itself and vibrate during boot up. Never seeing the home screen again. Only way to remedy this is to take out the battery and if we get lucky it will see the home screen again.
Thankfully I was able to boot into recovery and flash the Milestone AOKP MR1 Build and flashed the gapps. I did this sucessfully. So rebooted the device again to make sure everything will be good. Now the phone will only show the samsung logo and black screen with pulses of vibrations every second. I tried plugging it in and it doesn't even turn on just vibrates. Only when I take out the battery then it will actually turn on,but just the samsung logo followed with the black screen and pulsating vibrations.
Is the phone done? Is it perm bricked? I can't even go on download mode
EDIT: And yes I did a clean flash. I did all the proper wipe cache/dalvik, factory reset etc. etc.
It sounds like a power button issue. Same symptoms.
If you aren't familiar with the phone because it isn't yours;
They tend to start the boot process as soon as the battery is installed without pressing power. You might be missing the chance to put it in download mode, hold the volume button as you put the battery in. If you want to go from ICS to a 4.2.2 ROM you should ODIN to the latest stock ROM first then re-root , there some radio upgrades that can't be flashed from recovery.
Z33type said:
This has probably been resolved or mentioned before so please do not flamed me up. Just needing some quick help.
This is not my device this is a friends. He had a darkside V8 Rom which me and him thought are giving him issues. The phone will literally reboot by itself and vibrate during boot up. Never seeing the home screen again. Only way to remedy this is to take out the battery and if we get lucky it will see the home screen again.
Thankfully I was able to boot into recovery and flash the Milestone AOKP MR1 Build and flashed the gapps. I did this sucessfully. So rebooted the device again to make sure everything will be good. Now the phone will only show the samsung logo and black screen with pulses of vibrations every second. I tried plugging it in and it doesn't even turn on just vibrates. Only when I take out the battery then it will actually turn on,but just the samsung logo followed with the black screen and pulsating vibrations.
Is the phone done? Is it perm bricked? I can't even go on download mode
EDIT: And yes I did a clean flash. I did all the proper wipe cache/dalvik, factory reset etc. etc.
Click to expand...
Click to collapse
Try taking it apart and cleaning around the power button it could just have junk around it that tricks the phone into thinking that you are constantly pushing the button. Option two buy a download dongle for $5 from ebay to force download and see if it stays on long enough to flash a rom. Finally, it possibly is the old faulty power button situation that is known to happen with the S2 to some people which means it will need to be replaced.
Sent from my SGH-M919 using Tapatalk 2
donm76 said:
It sounds like a power button issue. Same symptoms.
Click to expand...
Click to collapse
Agreed. 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 SII phones. (I think the international "i9100" model uses a different type of switch.) You can simulate the issue on a good T989 by holding down the power button when you turn it on - it will reboot and then vibrate every few seconds with a blank screen, until you release the power button.
Some people have had success poking/pulling/cleaning/washing the switch, but replacing it is the only reliable long-term fix.
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). You'll need a steady hand, a fine-tipped soldering iron, and some small solder. A magnifying glass and a bit of paste flux couldn't hurt either.
Or, if you don't have mad soldering skills, a few companies offer mail-in repair service:
- $39: http://www.ebay.com/itm/Power-Switch-REPAIR-SERVICE-T-Mobile-Galaxy-S2-SGH-T989-Samsung-Fix-Bad-Button-/161028469601
- $45: http://www.ebay.com/itm/Power-Button-Repair-Samsung-Galaxy-S-Galaxy-S-II-Galaxy-NOTE-MORE-/320910836052
Did u flash correct gapps after flashing the ROM? If the answer to this question is no it could've caused a bootloop in which case u need to reboot into recovery, do a full wipe ( data, system, cache, dalvik ) then flash the ROM then flash gapps, or the power button issue, either way easy fix
Sent from my SGH-T989 using xda premium

[Q] Help!!! Only on For seconds?

So today my phone started to power it's self off. When I power on it shows the kernel screen for a few secs then powers off. I can boot into Recovery (CWM) and when I select reboot it does the same. If if I boot in to Download Mode, it only stays on a few secs.
Is it the power button? Any ideas?
I'm running the BMS Kernel and C-Rom 6.6. I have had this same rom and kernel for weeks with no issues.
djdoubt03 said:
So today my phone started to power it's self off. When I power on it shows the kernel screen for a few secs then powers off. I can boot into Recovery (CWM) and when I select reboot it does the same. If if I boot in to Download Mode, it only stays on a few secs.
Is it the power button? Any ideas?
I'm running the BMS Kernel and C-Rom 6.6. I have had this same rom and kernel for weeks with no issues.
Click to expand...
Click to collapse
Sounds like your battery is dying. Might wanna look into getting a new one.
BWolf56 said:
Sounds like your battery is dying. Might wanna look into getting a new one.
Click to expand...
Click to collapse
Interesting, I have not had any issue with the battery. I'll look into it. Any way to test without using another battery?
Anything else it could be?
Using CWM built in key test it seems it is the power button, when I touch the power key it reads as if it is being touched multiple times or heklod down. Any Fix without replacing the button?
Not that I know of I have only seen replacing it fixes it
Ive seen several people report that opening it up and jiggling the button can help, but when it does it is only temporary.
djdoubt03 said:
Using CWM built in key test it seems it is the power button, when I touch the power key it reads as if it is being touched multiple times or heklod down. Any Fix without replacing the button?
Click to expand...
Click to collapse
It's fairly easy to replace. You can buy a button off ebay for fairly cheap and look on YouTube to replace it.
Sent from my SGH-I747M using XDA Free mobile app
I agree it sounds like a stuck power button. My experience with this problem first showed in a captivate of my moms. It was very bizarre tho. On stock ROM it would constantly do the vibrate, cycle, vibrate etc. On a custom ROM however, it has had zero problems with the power button. Maybe try that? Not a sure fire fix, just telling what happened with the Cappy. ☺
If this is power button problem you can try (what i did and worked, but it is your choice and you can damage your phone) drop little of oil in power button and press couple time with out battery in phone.
norbarb said:
If this is power button problem you can try (what i did and worked, but it is your choice and you can damage your phone) drop little of oil in power button and press couple time with out battery in phone.
Click to expand...
Click to collapse
That's actually fairly dangerous for your device. I would suggest an air duster if you think it's dirty.
I'm actually having the same problem. It just started his morning.
The phone won't boot normally. I get the kernel boot screen, sometimes a Samsung screen, and then it turns off. 2-3 seconds max.
I can get it into download mode, but after 3-4 seconds, it spontaneously shuts off.
Recovery mode (CWM) is completely stable. I can get in, make back ups, perform a key test, etc. When I run a key test, it shows that the power button is a little sensitive, but not crazy. If I jiggle it some (mostly back a little) it registers a key press, even if I'm not fully pressing it. If I do press it fully, sometimes it doesn't register.
If this is really a button issue, why is recovery stable? Even if I put the phone on a flat surface with nothing that could touch the button, the phone still doesn't stay in download mode (it just shuts off.) When I put the phone in recovery, place it on a flat surface, and perform the key test, the phone isn't registering a key touch.
I've tried 3 different batteries, kept the phone plugged in, popped the battery and held the power button to discharge everything, wiped the cache, wiped dalvik cache, and used CWM touch to reboot (and avoid the power button all together.)
The only think I can think of that's maybe different is that gapps was FC'ing more than normal this morning (before the phone crapped out.)
I'm running StockMOD ROM 4.4.2 R2 with the Ktoonsez Kernel for TouchWiz 4.4.2.
EDIT: Also, when it's plugged in, the LED doesn't light up. I'm not sure that it's actually charging. I do have a wall charger, so I can verify that the batteries I'm using are charged.
Try flashing a different rom from recovery to see if it still happens. Also try a factory reset. If you get as close to stock as possible and it still happens it raises the probability thst its hardware.
If you put the battery in and wait a few moments does it turn on by itself?
Band-aid
@DocHoliday77 I messed with the phone a little later tonight and recovery became unstable. I'm convinced it's a power button problem now. I think the internal mechanism gets stuck and that's the issue.
When I put the battery in, the phone does try to boot by itself.
I used the advice in this post: http://forum.xda-developers.com/showthread.php?p=53915864 and I was able to get up and running again. I opened the phone up, blew some compressed air on the button, tapped the flat side of the button lightly a few times with the end of my screwdriver, and put everything back together. I was able to get back into recovery, and then reboot normally.
I ordered a new power button and I plan on replacing it next week when it gets here, just to be on the safe side.
You guys at xda are life savers!
The booting up on its own after inserting the battery is a classic symptom of the power button going bad. Glad to hear you got it working for now, and that you are ordering a replacement. Everyone ive heard about getting it to work using any number of methods have always found it to only be a temporary solution.
Just a thought, in case it starts up again, maybe remove the plastic piece until you replace the switch. Hopefully that would help prevent it from getting accidentally pressed in your pocket or by bumping it into something. (You could probably still access it with a toothpick or something like that if needed)
I agree it's the power button. I just posted about my little experience on Google+
I tried seriously whacking it on the floor and everything. I wouldn't recommend that but I had no warranty and no funds for repair. Others had said that beating the crap out of it worked so I thought why not lol...
https://plus.google.com/116004961340303353216/posts/ig2ogLeUWJ8
Long story short, my beating it up didn't work but it did wake it up. It falling on the floor however, jarred whatever was stuck and it now works like a charm...good luck

Categories

Resources