[Q] S4 shuts off after splash, any ideas? - Galaxy S 4 Q&A, Help & Troubleshooting

My S4 has finally kicked the bucket. It turns on long enough to display the "Samsung" splash screen with the padlock icon that says "Custom." After about two seconds it instantly shuts off, and can't be turned back on.
Pull the battery, the phone automatically turns on, shuts off again, rinse and repeat.
At this point I just want to salvage my pictures and music from the phone; is there any way I can mount the internal SD in the state that it's in? I'm sure this power issue is hardware-based; I can't get into recovery or download mode before it shuts off on me.

I was having this same problem recently as well. It happened on two separate occasions with about a week in between. The first time it came back after a few battery pulls and attempts to boot to recovery as well as download mode. The second time I fiddled with it for about an hour with numerous battery pulls and attempts to boot to recovery and download mode. I even swapped batteries to no avail. I don't know why exactly it finally decided to boot, but I haven't had an issue with it since. Maybe keep trying and hope for the best?

Can you boot and stay into recovery or download mode?
If not, then it very well might be a button issue. Have the phone checked out or you can do it yourself with a voltmeter if you have the knowledge and tech. Otherwise take it to a professional. I paid around 15$ to a button replaced. Which kinda seems a lot, considering a set of 4 buttons costs about 5$ and then you can do it yourself since it doesn't appear to be that hard, especially if you've done soldering before.

Related

[Q] LG G2 Won't turn on, cannot get to download mode

My AT&T LG G2 (plain D800) is rooted, and has Xposed installed on it (I'm not sure if this caused the issue or not), but here's what I'm having problems with:
I was playing a game, when all of a sudden the phone froze (no biggie, it's done it before, I've held the power button to force restart it, and it works), but the phone shut off on it's own, and would/will not turn back on.
Tge LG boot logo comes up intermittently when I hold power and volume up, but only sometimes. The phone has only twice now gotten to the AT&T logo, but freezes immediately and shuts down. I've tried literally every combination of holding buttons, for up to 70 seconds at a time, both on the charger, off the charger, and while plugging into the charger.
I cannot get to download mode, I cannot get to TWRP, and can obviously not boot into the phone. I had made no changes in weeks prior to this happening, so I can't see why or how something with my phone being rooted would cause the problem.
I've left the phone charged overnight before performing the actions (the phone won't even show battery percentage), so I don't think it's a dead battery issue. Everything I've read so far seems to say that the battery chip has died and needs to be replaced. Somehow I don't think it's the problem.
I'm fully willing to completely wipe the rom, and everything on it, as long as I can get the phone working again. However I cannot boot into download mode to use ADB or anything.
Is my phone completely bricked? Or is there a chance that the battery chip really is fried? Please help!
Update!
I left the phone charging some more, and decided to try volume up and power (while plugged in). The phone actually went into download mode for about 5 seconds before shutting off again. I tried doing the same steps, but nothing will come up again. It appears to be an issue with the battery on the device. Does anyone else think otherwise? Or will I have to send it in for a new battery? (The phone is less than a year old so I don't want to void the warranty anymore than rooting, which they wouldn't be able to tell since it won't turn on anyways).
Update Again:
I can get the phone to show the LG logo/download mode on a fairly consistent basis, sometimes showing a static screen (colored noise, not monotone), sometimes a blue screen, but it will shut off after 5-6 seconds every time.
Hey, I do not want to announce bad but by your description it seems that did you mother board, go to the lab to make sure, I had something similar and I replaced the motherboard and my phone came on time, check if the device is still under warranty has a good chance to replace you under warranty, good luck.

[Q] Help with potentially bricked S4 [Xposed]

--- This may belong in the Xposed forum, I am uncertain. ---
Hello. Please forgive my ignorance regarding the technical aspects of methods discussed on these forums.
I have a Samsung Galaxy S4 GT-I9505 supplied by Vodafone Australia. This was received today as a replacement for a screen issue I had with my previous S4. On the previous S4, I had rooted using a Saferoot method as read about on this forum. Later I had installed Xposed to use Keepchat and everything was fine. Today I have rooted this replacement phone successfully using the same method, and then moved to install Xposed. The Xposed application required an update, the very first option in the app was red and suggested an update or a reboot, and the reboot did nothing, so I pressed update. The phone turned off but didn't restart. I tried the usual button presses and battery pulls and finally a simple power up using the standard power button started the phone up. It got as far as the lock screen I believe, before shutting down again. It is now unresponsive. It wont turn on, enter the boot menu (multi button holding method) or charge. I believe the battery is quite low at this point, and unable to charge, causing me some consternation. It has now been over 30 minutes with no response.
If anyone could provide a resolution to this issue, I would be extremely thankful.
Regards,
CaleS
Try and ask in this forum my friend good luck
http://forum.xda-developers.com/showthread.php?t=2265477
Hello again.
I have an update on my situation.
I left the phone on charge and it eventually turned on by itself. I played around with it for a while and it seemed OK. Eventually it turned off again. I had to pull the battery to get it to turn back on. After starting up again, getting to the lockscreen, it turned off again. This process repeated many times, until I got frustrated.
The next day I thought I'd try a factory reset via volume up + power, and the device managed to stay on long enough for this to complete. After the phone reset, I used it for a while and again it turned off. The same cycle continued.
Perhaps the phone is naturally faulty, despite my rooting attempt, as it was a refurbished model. I am quite happy to return it for another replacement under warranty, however I may not be able to do it as the device is rooted. I would gladly remove the root using stock firmware and Odin, however the phone resets after a few seconds of entering download mode.
Any advice?
Thanks.
Sounds to me you have a faulty power button. It's somehow stuck that's why it even reboots in download mode. It's a common problem for the S4. Try to wedge it or replace it.
if it is refurbished model it might as well be dead battery.
battery sensor detects "low battery" state and shutdown phone saying battery 0% - to protect battery against fully depleted state (damaging to max capacity or even impossible to charge at some point)
if you power it on again it will boot and say it has like 1% left and you will be able to use it for few more moments, but doing so will degrade your battery.
powering it on, going to lock screen for it to shutdown on its own again sounds like weak power source
imagine above scenario happening several times (previous owner of the phone kept "reviving" it after shutdown due to battery 0%)
that would resulted in battery able to hold only fraction of its standard power - allowing you to just boot your phone before it shuts down.
I had similar situation with my laptop battery (this one was on AC all the time) - battery was so damaged that laptop was shutting down at windows login screen - if booted on battery alone.
When booted on AC and unplugged it said 100% battery, that went down to 0% in a matter of around 2 minutes, when laptop shuts down.

Help Needed! Completely stock phone won't power on.

Today, my wife's completely stock, unrooted, OD2, Sprint Galaxy S4 phone stopped working. It was working earlier in the day (10 minutes prior), but when she went to check the time, the screen was black and it wouldn't respond. Tried holding power button, but nothing. Battery level was at 58%. I know this because I switched her battery with mine (85%). I discovered that after a battery pull, it will show the Samsung splash screen for 2 seconds and then nothing. After pulling the battery, I tried putting it into Download mode and the Download mode screen shows for 2 seconds and then goes black. Same thing with Recovery. I have tried to let it charge, but it doesn't show the charging screen or anything. Does anyone have any ideas on: 1) What might be causing this? 2) How to fix? 3) If permanently bricked, how to get first day of school photos that are stored on phone and not on card?

Samsung S4 VE I9515 wont turn on

Hello,
So let me give you a brief so you'd know everything - a few days ago, I'm gonna call it day 1, I walked under light rain with the phone in my pocket, it worked until the night of
Day 2 - started to lag a bit, it was like I was running some heavy apps and like the ram was insufficient. Restarted the phone, everything seemed normal.
Day 3 - Phone went off while was browsing. So I have to make a note here. I was running cm13 with android m and twrp 2..something and there were occasional reboots by itself rarely prior to Day 1. Also, I was using a supercharger (or whatever it is called, it is a charger that charges faster) for about a month.
So when the phone went off while I was browsing, it started by itself and stuck on the android loading. I restarted, cleared dalvik and regular cache - still stuck on boot. Flashed many times, changed the recovery to twrp, and still was stuck on rebooting and occasionally it didn't turn on. There were random occurrences of errors on flashing roms, which never happened before (for example, "cant mount system or data"). Within the time passing by, the phone started not to turn on when I tried to. By this time rarely got stuck on the first boot screen saying with the text "Samsung S4". Yesterday, Day 4, the phone never turned on, except one time. I don't remember doing anything special. I just pressed and held the power button and it turned on, but went off shortly after the android boot animation appeared.
Also there was times on Day 3, when I was trying to boot into the system, it got stuck on the android booting animation.
On and prior to Day 3, while I was charging, whenever it is on or off - I had the indicator light for charging. Now when I plug it in to charge - nothing happens.
To skip any unnecessary questions, I will make a short QA.
Q: Did you tried to boot into recovery/bootloader?
A: yes, nothing happens
Q: Any sign of life on adb while connected to a pc??
A: no
Q: Is battery dead?
A: I don't think so, but actually I'm not that sure. When I connect a separate led light to it, the led lights up Whatever, if it was a faulty battery when I plug the phone on the charger, it should've worked fine.
Q: Why don't you just buy a new phone?
A: I was planning to buy a new one, but after just 4 months when I have to renew my contract. I don't want to buy a phone off contract.
Q: Are you stupid, if you can't manage to fix it by yourself, why don't you give it to a repair?
A: I truly believe that the professionalism of repairers doesn't exist in my country via old experiences with them.
So in the worst scenario I will loose time by trying to fixing it and for 4 months I will use my old android phone.
In the best scenario, my almost 2 years old phone will revive.
Also, I have a multimeter - I can check the electricity. Just tell me what to check.
Thanks.
edbr said:
Hello,
So let me give you a brief so you'd know everything - a few days ago, I'm gonna call it day 1, I walked under light rain with the phone in my pocket, it worked until the night of
Day 2 - started to lag a bit, it was like I was running some heavy apps and like the ram was insufficient. Restarted the phone, everything seemed normal.
Day 3 - Phone went off while was browsing. So I have to make a note here. I was running cm13 with android m and twrp 2..something and there were occasional reboots by itself rarely prior to Day 1. Also, I was using a supercharger (or whatever it is called, it is a charger that charges faster) for about a month.
So when the phone went off while I was browsing, it started by itself and stuck on the android loading. I restarted, cleared dalvik and regular cache - still stuck on boot. Flashed many times, changed the recovery to twrp, and still was stuck on rebooting and occasionally it didn't turn on. There were random occurrences of errors on flashing roms, which never happened before (for example, "cant mount system or data"). Within the time passing by, the phone started not to turn on when I tried to. By this time rarely got stuck on the first boot screen saying with the text "Samsung S4". Yesterday, Day 4, the phone never turned on, except one time. I don't remember doing anything special. I just pressed and held the power button and it turned on, but went off shortly after the android boot animation appeared.
Also there was times on Day 3, when I was trying to boot into the system, it got stuck on the android booting animation.
On and prior to Day 3, while I was charging, whenever it is on or off - I had the indicator light for charging. Now when I plug it in to charge - nothing happens.
To skip any unnecessary questions, I will make a short QA.
Q: Did you tried to boot into recovery/bootloader?
A: yes, nothing happens
Q: Any sign of life on adb while connected to a pc??
A: no
Q: Is battery dead?
A: I don't think so, but actually I'm not that sure. When I connect a separate led light to it, the led lights up Whatever, if it was a faulty battery when I plug the phone on the charger, it should've worked fine.
Q: Why don't you just buy a new phone?
A: I was planning to buy a new one, but after just 4 months when I have to renew my contract. I don't want to buy a phone off contract.
Q: Are you stupid, if you can't manage to fix it by yourself, why don't you give it to a repair?
A: I truly believe that the professionalism of repairers doesn't exist in my country via old experiences with them.
So in the worst scenario I will loose time by trying to fixing it and for 4 months I will use my old android phone.
In the best scenario, my almost 2 years old phone will revive.
Also, I have a multimeter - I can check the electricity. Just tell me what to check.
Thanks.
Click to expand...
Click to collapse
Probabily the rain damaged a part of your hardware. Did you solve?
If the battery is dead, the phone won't work.
The battery needs to have at least a bit of charge in order for the device to work, even if it is plugged in.
If the battery can't hold the charge, and the device uses more power than it gets, it turns off. I speak from experience.
These devices don't seem to work without a battery. Power goes to the battery, and the phone takes the power from there. Power doesn't go straight to the phone.
Anyway, I don't think a bit of light rain hurts the devices, especially if it was in your pocket. I walked through rain with my device in the pocket many times and no problem.
It looks to me that the hardware is failing. I don't believe that a faulty battery can cause a bootloop. I also don't believe that the power button causes a bootloop.
What I suggest would be:
1) Try going back to stock ROM.
2) Maybe try to get an S4 with a broken screen and switch the motherboards.

Droid Turbo 2 Sudden Shutdown + Boot loop

TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
walter77d said:
TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
Click to expand...
Click to collapse
Try the apps such as Ampere which shows battery info.
I don't think so Non-Turbo charger can lead to affect the battery life but using a cheap charger does.

Categories

Resources