Galaxy S4 i9500 Bootloop without Recovery Mode - Galaxy S 4 Q&A, Help & Troubleshooting

Hi,
The problem I have is really very common to most Samsung Galaxy users, but I haven't found any solution to my particular problem. Well, basically my Samsung Galaxy won't get out of bootloop. It just won't go beyond Samsung Galaxy SIV I9500 screen. The phone never did this before this. The phone did, however, rebooted occasionally by itself when running normally.
My phone is rooted, but it runs the official version of Lollipop for Galaxy S4. I had to factory reset my phone one day, and I decided it to reset from the Recovery Mode. After successfully resetting the phone, it booted as usual. Soon after it suddenly turned off, and went into this complete bootloop and would not stop until I remove the battery. Whenever I insert the battery back in, the phone starts by itself, without me pressing any button, and goes in the bootloop again. I can only enter the Download Mode that too for a couple of seconds. When entering the download mode I don't have to press the power button.
Is there any solution to this? I am assuming that my power button suddenly failed. The power button is definitely not stuck. I have opened the entire phone and cleaned the motherboard, and rechecked, it still showed the same problem.
Really appreciate any kind of help.

Hardware issue. Lightly tap the side of the S4 against a table and see if that temporarily frees up the button. Regardless of the end result, you'll need to replace the power button.

Hi,
No need power button to boot in recovery.
Just hold Home+Volume up should do the trick.

@Yoanf_26: How do you expect the phone to get into recovery without turning it on? Volume up and Power are all that's needed to get into recovery. It's the Home button that is optional.

Try a different battery (ask a friend or something if possible). I had similar issues on an i9100 lately. It could only boot to download/recovery mode and was even producing write errors. Looked like brickbug first but was bad battery indeed. It starts slowly with weird behavior and you think you've just messed the rom and just need to reset but it gets worse and worse until you're stuck with download mode only. If you have a spare battery in range its worth a try for sure.

Strephon Alkhalikoi said:
@Yoanf_26: How do you expect the phone to get into recovery without turning it on? Volume up and Power are all that's needed to get into recovery. It's the Home button that is optional.
Click to expand...
Click to collapse
Hello.
I already to start my S4 without power button must just with Volume up and home.
I test with Volume up with power, and my S4 start to recovery.
Differents methods are good to start to recovery. May not for all S4

Guess what? You have a faulty power button, because being able to start the device in any mode without the power button is simply not possible. I tried it just now. Also, if Samsung themselves require the power button to enter recovery or download mode it's illogical to not need it on what is (broadly) the same device.

My power button is good. I test with a custom recovery.
May be not possible with stock. I don't test with stock.

I'm not running stock anything on my I9505. TWRP 2.8.7.0 and CM 12.1 Optimized (currently) installed here. To access Download Mode requires Volume - and Power (Home optional). Accessing Recovery requires Volume + and Power (Home optional, again). Safe Mode requires pressing Volume - and Power, and holding down Volume - throughout the boot process.
As you can see, all functions require power. The fact yours doesn't is not normal.

Maybe, but my S4 is good.

If you think so, who am I to try and persuade you otherwise? When you do encounter an issue with that button, just think back to this thread rather than making a post about it. That way we can both avoid the inevitable "I told you so" that will come out of my mouth.

Related

[Q] Download mode boot loop

Hi, I'm hoping someone can advise on a strange issue I have with my phone. If I power down the phone then it powers back up in download mode. If I take out the battery then put it back in, the phone will automatically power up in download mode.
While in download mode, if I hold the power down for 5 seconds to shut down the phone then quickly hold vol down + home + power then the phone loads to the "Warning!! a custom OS can cause critical problems in phone and installed applications" screen. From here, I can press vol down to "Cancel (restart phone)", after which the phone boots normally and everything appears to be fine. All the buttons work perfectly and there doesn't appear to be anything else wrong at all. However, powering down will again cause the phone to go into download mode.
The phone was previously rooted, but while trying to repair the issue I have flashed a stock firmware and tried a factory reset. This doesn't appear to have changed anything though.
In download mode the Binary Status is now Samsung Official and the System Status is Official too (which I'm hoping means I won't be refused a warranty repair). I think the phone may have got a little damp at the Reading festival last weekend, but I find it strange that nothing else appears to be wrong with the device apart from this weird boot loop.
Any suggestions to try something before I take it back to the shop would be appreciated. Thanks in advance for any help or advice.

Problem with Volume Button, Software or Hardware?

Hello! Got a problem with my Galaxy S 4. Removed T-Mobile brand, flashed the stock ROM MH5 and unlocked the device by code.
Do not know if the problem existed before, at least following phenomenon occurs: after a certain time (depending on how long the battery was out - more on that below) the volume down button no longer responds - initially Vol button respnds normally, suddenly the volume turns down and I can only press volume up, volume down does not respond anymore - when I reboot the device, it always boots in the mode where I can push vol up to install a custom Rom or volume down for restart - but neither Vol up nor Vol down respond. If I restart the device with volume up + Home + Power button, I can not get into recovery but in Safe Mode.
Only when I take out the battery and wait (approx half an hour), the unit boots normally and the error occurs again after some time...
I also made a factory reset - no success. Somebody knows this phenomenon? Thank you.
Maybe
liquidspace said:
Hello! Got a problem with my Galaxy S 4. Removed T-Mobile brand, flashed the stock ROM MH5 and unlocked the device by code.
Do not know if the problem existed before, at least following phenomenon occurs: after a certain time (depending on how long the battery was out - more on that below) the volume down button no longer responds - initially Vol button respnds normally, suddenly the volume turns down and I can only press volume up, volume down does not respond anymore - when I reboot the device, it always boots in the mode where I can push vol up to install a custom Rom or volume down for restart - but neither Vol up nor Vol down respond. If I restart the device with volume up + Home + Power button, I can not get into recovery but in Safe Mode.
Only when I take out the battery and wait (approx half an hour), the unit boots normally and the error occurs again after some time...
I also made a factory reset - no success. Somebody knows this phenomenon? Thank you.
Click to expand...
Click to collapse
Try replacing the battery with a different one then see if it works. if not do this:
Download the stock MH5 ROM from SAMMOBILE
Open Odin
Flash this ROM with Odin
make sure that only Auto Reboot and F. Reset Time are the only options ticked
I personally havent had this problem but it might help
EDIT: This sounds like a software issue but if it keeps happening it may infact be a hardware issue with the device itself
Thanks, but I already flashed Stock MH5 and now MH7 T-Mobile branded - when the device is off for about an hour, the S4 boots normally and the Volume up and down works fine, two minutes later Vol down doesn´t respond anymore...it´s weird
I still don´t belive it - tried the battery from a mate´s S4 - mine works fine again, no Vol button errors or startup problems...can somebody explain this to me...crazy ****...

Soft bricked my T280 and so confused!!

I recently updated my Samsung Galaxy Tab A T280 to the latest firmware and I lost my root. So this afternoon I re-rooted it. Or I attempted to, anyway. Everything seemingly went fine, and I booted into TWRP just fine. I went to flash the ROM and I also selected wipe cache/davlik cache to be done as well, and tapped reboot. My device then turned off and when it started the reboot, it got stuck on the Samsung Galaxy Tab A logo screen and would not move or power off by holding the power button (I tried for a LONG time by using a rubber band to hold it down so I didn't have to, with no luck), and every other combination of buttons wouldn't do a thing, except for holding power + vol down, which made it turn off and back on, but it wouldn't finish rebooting and it just got stuck at the Samsung Galaxy Tab A logo again. So then I thought that maybe plugging it into a charger might not be a bad idea, and after holding down power + vol down again, it turned off and turned on and showed a battery with a charging symbol. I've had it plugged in for an hour and it does not show a charge or do anything except for go back to that boot logo if I unplug it from the charger and again hold down power and volume down separately.
I know it's not hard bricked because it is somewhat responsive so I think there's a chance to fix it, hopefully. I just want it to turn on and fully reboot into anything or in any way that will allow me to be able to fix the issue. My computer will not recognize the device so ADB is not an option right now unless I'm wrong.
Thanks a lot guys, I am so confused and could really use some advice.
What firmware did you install
Try to install original firmware via software "Samsung Smart Switch" on your PC with connected tablet.
I too recommend that you try installing the last firmware that you were on via Odin. Also, when you hit that screen lock issue after a firmware flash, where only the Samsung logo appears do this:
1. press and hold Home + volume up and volume down along with power button (that's all 4 buttons). Hold it there for at least 20 seconds and it should power off.
2. Once the device powers off keep holding the buttons but let go of the volume down button.
3. Once the tablet starts to power back up again release the power button and then in about 1 to 2 second release the rest of the buttons.
This should get you back into recovery. You should at least be able to restore any backup, that you should have already, on your external micro SD.
Good luck.. : )
"Chance Favors the Prepared"
the above post is 100% right. Reboot back into recovery and you'll be good to go. Also twrp has a option to reboot back to recovery so this doesn't happen, just a fyi for future knowledge. Best of luck..
You tried to flash a rom with twrp?
You need to flash stock firmware with odin.

A5 2015 (SM-A500FU) bootloop, can't go in recovery or download mod!

Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Dharmost said:
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Click to expand...
Click to collapse
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
D4ND310 said:
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
Click to expand...
Click to collapse
I didn't dip the smartphone into a cup of liquid, i just took a piece of cotton, poured a bit of nail pain remover (don't know the exact name in english, sorry) on it and then scratched the part where the chewing gum was on (on the soft touch back key, which works 100% fine).
I am trying using the method you described, but it seems i can't go into recovery. Maybe i'm not quick enough! will keep trying. If you have any other suggestions i will be glad to hear that!
You could try to make a USB jig, or buy one off of eBay. They're really cheap. Its basicly just a resistens that force the phone to download mode. It have worked fine for all my Sammy's including A310 so it probably works for A (15) series as well.
Just put it in USB connector and press power for a few secs and you should be in download mode.
Just an idea if everything else fails
Sent from my Honor 5X using Tapatalk
go to samsung
A hardware problem could NEVER be fixed by software ways... Unfortunatelly...
It seems that liquid made some changes on your PCB (maybe dissolved some isolators inside??)...
Anyway, go to service or replace it!
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Dharmost said:
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Click to expand...
Click to collapse
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
babyyeobo14 said:
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, but still couldn't get into recovery. I think the home button is really broken, therefore i need to access recovery in another way.
Cause i flashed the stock samsung firmware twice with odin and i can't still start the phone properly, every guide says that a wipe of cache and dalvik solves the situation. But i need to get into recovery for that.
I can't go into recovery with normal procedure probably because the home button is not working, and all the guides about adb commands say that you need to plug in your phone when it has fully started. So i either need a way to force the device into recovery with my computer, or a firmware that once flashed doesn't give me bootloop

Can't get into recovery to save my life!

Guys, I'm wanting to get into recovery mode to wipe my Dalvik cache but for the life of me I can't get to it. I'm doing up+power+home and I go to screen saying 'Downloading do not restart target'. I guess this is download mode. How do I turn this off?
For kicks I tried down+power+home and it asks me if I want to enter download mode. Also tried up+down+power+home but this just does a normal boot.
I know this is probably something really basic but I just can't get in. I did have KingRoot installed a while back. Could this have caused the problem? Any help is greatly GREATLY appreciated. Thanks!
Hold power and volume down, then press volume up when the OS warning screen appears = download mode.
Hold power and volume up = recovery.
Don't bother with the home button. You don't need it. Should the key combinations not work correctly, you may have bad buttons on the motherboard.
Thanks for the quick reply. I double-checked my volume buttons and they work as they should (up = louder; down = softer). I tried power + up and still get the download mode screen. I even tried adb to boot into recovery and it brings me to that same 'Downloading do not restart target' screen.
Prior to writing my post above I tested my S4 to make sure I was giving correct information. Both key sequences worked on my S4.
The only thing I can think of is that you have a hardware issue with your volume down button. To test, try pressing and holding power without touching a volume button. If you enter OS warning mode without pressing a volume button, then your volume down button is worn out and needs to be replaced.
My reasoning is this.
Button failures are the most common issue with the Galaxy S4.
You instantly enter download mode by pressing power and volume up while being unable to enter recovery at all. This means you're skipping a step in accessing download mode, which wouldn't happen if all the buttons were working correctly.
Maybe, but shouldn't my phone go into recovery when I send the command to enter recovery from adb? It just reboots and goes to downloading. My buttons work fine when using the phone when android is up so I'm doubting that it is a hardware issue.
It should, but something is interfering with that. I'd go back to stock using Odin, simply to ensure all parts of the firmware match. Then see if you can get into the stock recovery with the key combo. If you are able to, then you can restore TWRP and flash a custom ROM. Otherwise the device needs to be looked at.
Thanks for the reply. I'm running the stock os without root. All I really want to do is wipe Dalvik cache. Can I do that from adb?
Yep.

Categories

Resources