[Q] Galaxy S4 Bricked?!?!? HELP!!! - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

So this is my first post because I can normally find what I'm looking for, except for in this case.
First off my phone, Galaxy S4 Model SGH-I337 running Android 4.2.2 rooted. No custom rom installed, i.e. Cyanogenmod. I recently bought some new batteries and a new charger which I had been using for about two weeks before my problem arose.
I came home one night plugged my phone in to charge and woke up to find it unresponsive. I tried a battery pull and found my phone turns on for about 3 seconds showing the samsung custom screen with the padlock only to shut off again. Same thing happens not matter how many times I perform a battery pull. I tried plugging into my computer but the phone is not detected.
I tried a battery pull and booting into safe mode and debugging mode but the phone just shuts off after 3 seconds no matter what.
I'm not sure if this is a true hard brick since when I perform a battery pull the phone starts and the buttons seem to work, at least enough to enter safe or debugging mode.
I have not seen any threads where the phone momentarily turns on after battery pull only to shut off quickly.
Has anyone run into this problem before and is there anyway to fix it???

billbusby said:
So this is my first post because I can normally find what I'm looking for, except for in this case.
First off my phone, Galaxy S4 Model SGH-I337 running Android 4.2.2 rooted. No custom rom installed, i.e. Cyanogenmod. I recently bought some new batteries and a new charger which I had been using for about two weeks before my problem arose.
I came home one night plugged my phone in to charge and woke up to find it unresponsive. I tried a battery pull and found my phone turns on for about 3 seconds showing the samsung custom screen with the padlock only to shut off again. Same thing happens not matter how many times I perform a battery pull. I tried plugging into my computer but the phone is not detected.
I tried a battery pull and booting into safe mode and debugging mode but the phone just shuts off after 3 seconds no matter what.
I'm not sure if this is a true hard brick since when I perform a battery pull the phone starts and the buttons seem to work, at least enough to enter safe or debugging mode.
I have not seen any threads where the phone momentarily turns on after battery pull only to shut off quickly.
Has anyone run into this problem before and is there anyway to fix it???
Click to expand...
Click to collapse
The phone didn't brick itself. So, if you didn't do anything to it and just found it that way (as you said), I would think it is a hardware problem either with the phone or the battery. Have you tried a different battery? If you rule out a defective battery, I would say it is a hardware problem with the phone.

This used to happen to skyrockets due to stuck power button
Sent from my SGH-I337 using Tapatalk

RK said:
This used to happen to skyrockets due to stuck power button
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
This right here ^
My friend has a T-Mobile GS4 and same thing happened to him. It would only turn on when he would pull the battery and put it back in, but it would turn off soon after. Turns out his power button was jammed. He went and go it replaced.
Try this: Pull your battery and put it back in. If your phone turns on momentarily without you pressing anything then the power button is the problem.

Are you able to enter download mode..or recovery?
Sent from my GT-I9500 using Tapatalk

mrao said:
Are you able to enter download mode..or recovery?
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
No i can't enter either because the phone shuts off after 3 seconds no matter what I do

PurpleBottle said:
This right here ^
My friend has a T-Mobile GS4 and same thing happened to him. It would only turn on when he would pull the battery and put it back in, but it would turn off soon after. Turns out his power button was jammed. He went and go it replaced.
Try this: Pull your battery and put it back in. If your phone turns on momentarily without you pressing anything then the power button is the problem.
Click to expand...
Click to collapse
Is there any way I can take the phone apart and fix this? I don't think returning the phone is an option since my phone is rooted.

billbusby said:
Is there any way I can take the phone apart and fix this? I don't think returning the phone is an option since my phone is rooted.
Click to expand...
Click to collapse
Your exact problem just happened to me. Were you able to fix it? I'm dying to know!

billbusby said:
Is there any way I can take the phone apart and fix this? I don't think returning the phone is an option since my phone is rooted.
Click to expand...
Click to collapse
There's disassembly guides/videos if you want to try, you could search that and just take a look at the mechanism.
Sent from my SGH-I337 running Light ROM

Related

I think I'm bricked?

I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.
You fool.
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312
overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up
KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.
So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7
abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.
Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before
First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it
Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.
abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way
dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?

hard brick help?

in my face, my phone turned off on me.
im on mf9
rooted.
samsung logo comes up for a second, then disappears.
download mode appears for a second, then disappears.
battery icon appears for a second, then disappears.
ran through a bunch of threads here, even looked at other phones with similar problems.
been at this since the morning, its now 4:30.
looking for some help.
phone does not stay on, and does not go into download mode.
was working PERFECTLY the day before.
Thanks
BreakTheLaw said:
in my face, my phone turned off on me.
im on mf9
rooted.
samsung logo comes up for a second, then disappears.
download mode appears for a second, then disappears.
battery icon appears for a second, then disappears.
ran through a bunch of threads here, even looked at other phones with similar problems.
been at this since the morning, its now 4:30.
looking for some help.
phone does not stay on, and does not go into download mode.
was working PERFECTLY the day before.
Thanks
Click to expand...
Click to collapse
Sounds like a hardware issue almost.
I would maybe try connecting the phone via USB to pc. Pull battery and and replace. Then try booting into download mode. Open Odin and check if the device is recognized.
Sent from my SPH-L720 using Tapatalk
doesnt sound like a brick... truth being, its almost rare " hard bricking " samsung galaxys.. soft bricking is very common.. i bricked a HTC EVO a few years ago... symptoms: press power.. blue light blinks and the shuts off.... pop out batt, plug in, usb to pc....all do nothing....
sounds like somehow there is a batt problem.... TAKE OUT BATT... LAY it on a super flat serface.. now try and spin it!!! or does it rock around like its uneven?... means the batt is swollen in the middle and is no good... that maybe ur prob.
Sent from my SPH-L720 using xda app-developers app
chris-allen said:
doesnt sound like a brick... truth being, its almost rare " hard bricking " samsung galaxys.. soft bricking is very common.. i bricked a HTC EVO a few years ago... symptoms: press power.. blue light blinks and the shuts off.... pop out batt, plug in, usb to pc....all do nothing....
sounds like somehow there is a batt problem.... TAKE OUT BATT... LAY it on a super flat serface.. now try and spin it!!! or does it rock around like its uneven?... means the batt is swollen in the middle and is no good... that maybe ur prob.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
thanks.
battery spins like a turntable.
both my batteries spin like a stripper actually.....
i have used 3 different computers, countless usb cables and ports.
i used my friends battery to make sure it wasnt my batteries, phone still doing the same thing.
its so odd.
it was working perfectly fine.
now when i put the battery in, it automatically turns on, but only for a split second.
then it turns off.
i know its not suppose to turn on automatically, but i cant even get it into download mode because it shuts off within seconds.
im at a loss
Well.. if you have insurance, call them and tell them the device just stopped working... they will fedex you another overnight.. all for a 100.00 deductable....thats a way out.
Sent from my SPH-L720 using xda app-developers app
I have seen similar stories from people that had defective power buttons. what if you hold the vol down button when you insert the battery, does it behave differently?

AT&T S4 Shuts off after 3 seconds

Hello All,
My S4 constantly shuts off after 3 seconds. Lets say the phone is off, and I just plug the usb cable into, the battery icon comes on, but then it shuts off after 3 seconds. If I try to go into download mode, its get there, but then shuts off.
I had the MDL Firmware on it with Loki and it was working fine. Now I just want to flash back to stock, but the phone wont stay on long enough. I also tried different batteries.
Any idea on whats wrong or how I can successfully flash back to stock
First thing I would check is to see if your power button is stuck......
dmc2359 said:
First thing I would check is to see if your power button is stuck......
Click to expand...
Click to collapse
Doesn't seem like it is.i can press the power button and I can feel it push back
mischief4l said:
Doesn't seem like it is.i can press the power button and I can feel it push back
Click to expand...
Click to collapse
Are you using the cable and wall plug that came with the phone?
paying it forward !!!!!!
mischief4l said:
Hello All,
My S4 constantly shuts off after 3 seconds. Lets say the phone is off, and I just plug the usb cable into, the battery icon comes on, but then it shuts off after 3 seconds. If I try to go into download mode, its get there, but then shuts off.
I had the MDL Firmware on it with Loki and it was working fine. Now I just want to flash back to stock, but the phone wont stay on long enough. I also tried different batteries.
Any idea on whats wrong or how I can successfully flash back to stock
Click to expand...
Click to collapse
i had the same problem last week all week forum after forum seems like i keep ending up in virision forums .... any way my s4 I337 at&t was going to a battery symbol with no charge ....... could only boot into odin but like you said 3 secs .....after hours f trying to figure it out i gave up tossed my s4 on the living room floor and some how my USB cord was laying just right and it stayed on ....after playing with the connection that goes into my phone (origanl cord from at&t /samsung i relized i had a bad connection........ i used my teeth to clamp the middle tighter ...... secure connection phone stayed on threw out the flash process about ten mins .............. hope it helps this is what i flashed ...... http://forum.xda-developers.com/showthread.php?t=2621279 if im long winded i apoligize but this is the first ive had a response to help some one
DeadlySin9 said:
Are you using the cable and wall plug that came with the phone?
Click to expand...
Click to collapse
I actually charge my batteries in a standalone charger and I my gf has an S4, so the batteries are confirmed to be at 100%.
ardonie said:
i had the same problem last week all week forum after forum seems like i keep ending up in virision forums .... any way my s4 I337 at&t was going to a battery symbol with no charge ....... could only boot into odin but like you said 3 secs .....after hours f trying to figure it out i gave up tossed my s4 on the living room floor and some how my USB cord was laying just right and it stayed on ....after playing with the connection that goes into my phone (origanl cord from at&t /samsung i relized i had a bad connection........ i used my teeth to clamp the middle tighter ...... secure connection phone stayed on threw out the flash process about ten mins .............. hope it helps this is what i flashed ...... http://forum.xda-developers.com/showthread.php?t=2621279 if im long winded i apoligize but this is the first ive had a response to help some one
Click to expand...
Click to collapse
Thanks I will try this out
mischief4l said:
Hello All,
My S4 constantly shuts off after 3 seconds. Lets say the phone is off, and I just plug the usb cable into, the battery icon comes on, but then it shuts off after 3 seconds. If I try to go into download mode, its get there, but then shuts off.
I had the MDL Firmware on it with Loki and it was working fine. Now I just want to flash back to stock, but the phone wont stay on long enough. I also tried different batteries.
Any idea on whats wrong or how I can successfully flash back to stock
Click to expand...
Click to collapse
Have you found a solution? I experience something similar: phone shuts down after the Galaxy S4 logo, or 3 sec after it enters download mode using a jig connector.
A way to repair
mess18 said:
Have you found a solution? I experience something similar: phone shuts down after the Galaxy S4 logo, or 3 sec after it enters download mode using a jig connector.
Click to expand...
Click to collapse
I suppose I have found what the problem is: after I have slightly hit the phone over my hand palm, I've realized it returned to function normally. But after a couple of hours the problem has return. So I tried to do that again and suddenly the vibrator stopped working. I make it short: several more attempts gave me a combination of improper functioning with or w/o the vibrator. So I had removed it completely and the phone started working OK. I have put it back and now the phone works OK. I believe the problem was in a bad contact with the vibrator. I'll keep playing with the phone for several days, and if it's OK I declare repair is 100% succeed.

S4 randomly bricked?

I was running Goldeneye 3x for a few weeks, and just last night, i started to get a few random reboots. I thought nothing of it, then this morning, my phone doesn't turn on. I thought okay dead battery, put it to charge, but nope, no led, no response from the phone. There is no button combination that gives me a response. The only thing that gives me a response is taking the battery out, putting it back in. It gives the Samsung logo with the unlocked lock symbol and "custom" under it, and after about 2 seconds, it goes dead again. Maybe its a dead battery? What are my options? What should I look into?
Thanks
edit: got a new battery from fry's today, no difference, still won't turn on and still getting the same response from the phone
Garen21 said:
I was running Goldeneye 3x for a few weeks, and just last night, i started to get a few random reboots. I thought nothing of it, then this morning, my phone doesn't turn on. I thought okay dead battery, put it to charge, but nope, no led, no response from the phone. There is no button combination that gives me a response. The only thing that gives me a response is taking the battery out, putting it back in. It gives the Samsung logo with the unlocked lock symbol and "custom" under it, and after about 2 seconds, it goes dead again. Maybe its a dead battery? What are my options? What should I look into?
Thanks
Click to expand...
Click to collapse
Since you can't get into safestrap, will it allow you to reboot into download mode? You could try ODIN back to stock?
guut13 said:
Since you can't get into safestrap, will it allow you to reboot into download mode? You could try ODIN back to stock?
Click to expand...
Click to collapse
Nope, can't boot into download mode either
Garen21 said:
Nope, can't boot into download mode either
Click to expand...
Click to collapse
I'd try another battery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'd try another battery.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ya that's what I'm planning on doing, just waiting to run into someone who has an S4 lol
Could it be a broken power button (the internal button not the outside one)? or a messed up usb port? A different battery gave the same results as my original battery

S7 Bricked? Won't boot, doesn't appear to charge

As title states, have a sm-g935f running stock firmware that won't boot.
Had issues with it freezing and rebooting so re-flashed stock firmware, has run fine for approximately 3 weeks now when suddenly, whilst installing swiftkey it froze, then turned off. Had roughly 50% charge at this point. Have googled for hours now, tried different button combinations for varying lengths of time to try to boot. Have left it to charge for 2 hours and have just had another crack at it. Charge indicator does not appear on screen when plugged in, led at top of display does nothing at any point.
I'm out of ideas at this point, really could use the expertise of the greater xda community now, this is my only phone and its unusable right now leaving me connectivity-ly stranded.
Thanks in advanced for the help guys :cyclops:
Can u boot into Recovery mode?
No, it does nothing at all. It won't even attempt to turn on
So brick it is.
Boot it into Download mode by pressing Vol Down + Home key and Power Key. Then open Smartswitch app click preferences and click emergency recovery follow the steps then
I also had this problem. Basically you need to follow SjDU. If you cannot get into download mode. Try and leave the phone uncharged for 24 hours. Then charge for about 30 min and try to get into download mode.
AndrOmega said:
So brick it is.
Click to expand...
Click to collapse
Why thank you, so helpful
Thanks guys, ill leave for 24 hours, i just have no way of knowing whether its uncharged or not, it really gives nothing at all regardless of what i do. Not even a slight vibrate when i plug it into a charger or pc.
regardless, ill leave it and report back
Thanks
Hi,
It seems to me that it's really dead, give a try at leaving it uncharged for a few hours and then trying again.
However I wouldn't hold my expectations up, I had a similar problem with the Galaxy S4, phone was constant freezing after a Stock flash (I was using custom ROM before), then tried to restart the phone, phone got stuck and removed battery. Turned out bootloader died and I had to flash it again using JTAG (S4 was pretty easy to open up).
I hope that you won't need to use a JTAG Flash, since it needs to open the device and obviously S7 is pretty hard to get to the circuit. An easy option is trying an USB JIG to get to download mode (that is, if your phone has charge - hence you will need to try first the option others suggested - and a working bootloader), you can easily find this device for less than 5 dollars on eBay.
Hope you get your beloved device working again.
All the best,
~Lord
Sent from my Galaxy S7 Edge using Tapatalk

Categories

Resources