heya guys,
I'm on stock FW on my GS4S i9505 and yesterday morning i update to 4.3 OTA.
It was working all day just fine without issues or lag for the matter.
Today morning when i woke up, my phone was plugged into the charger and was turned off.
I turned it on by couple of mins later it would freeze and wont unlock, just black screen with a red light flashing on the top left of the phone.
I had to pull out the battery and put it back everytime i wanted to try and boot it.
I did that 3 times within 10mins and the 4th time it just stopped turning on all together.
Anyone has this issue and maybe can give tips on how to fix this if possible?
Thanks in advance.
re: auto updates
Smokie Smokerson said:
heya guys,
I'm on stock FW on my GS4S i9505 and yesterday morning i update to 4.3 OTA.
It was working all day just fine without issues or lag for the matter.
Today morning when i woke up, my phone was plugged into the charger and was turned off.
I turned it on by couple of mins later it would freeze and wont unlock, just black screen with a red light flashing on the top left of the phone.
I had to pull out the battery and put it back everytime i wanted to try and boot it.
I did that 3 times within 10mins and the 4th time it just stopped turning on all together.
Anyone has this issue and maybe can give tips on how to fix this if possible?
Thanks in advance.
Click to expand...
Click to collapse
You will need to go to SamMobile.com and download the official odin flash firmware
for your phone's exact model and flash it using Odin.
That will get the phone into good working condition with the stock 4.2 firmware.
After that you can use the phones built-in updating system again and most likely it
will work just fine. Just be sure that the battery is at least half full before the phone
starts the auto-update process.
Perhaps you installed some app or game from the playstore which did not play nice
with your phone and caused the 4.3 update to get stuck or it could have been the
battery if it did not have enough charge in it.
You should try to get the phone into download mode to see if it can be Odin flashed.
Hold the volume down key at the same time while holding the the power key down
for 20-30 seconds and see if it goes into download mode.
If it does you have nothing to worry about.
NOTE: before trying download mode be sure to remove the battery for 5 seconds
and replace it, making sure the phone is in a power off state before trying to boot
it into download mode.
Misterjunky said:
You will need to go to SamMobile.com and download the official odin flash firmware
for your phone's exact model and flash it using Odin.
That will get the phone into good working condition with the stock 4.2 firmware.
After that you can use the phones built-in updating system again and most likely it
will work just fine. Just be sure that the battery is at least half full before the phone
starts the auto-update process.
Perhaps you installed some app or game from the playstore which did not play nice
with your phone and caused the 4.3 update to get stuck or it could have been the
battery if it did not have enough charge in it.
You should try to get the phone into download mode to see if it can be Odin flashed.
Hold the volume down key at the same time while holding the the power key down
for 20-30 seconds and see if it goes into download mode.
If it does you have nothing to worry about.
NOTE: before trying download mode be sure to remove the battery for 5 seconds
and replace it, making sure the phone is in a power off state before trying to boot
it into download mode.
Click to expand...
Click to collapse
Thanks for the reply dude.
I'd love to do that, but i dont see how this is possible since the phone doesnt boot up at all anymore.
Any ideas?
Maybe your battery is dead? Because it's known issue on Galaxy S4 phones.
Try another charger.
I tried with my wife's S4 battery and my colleague's S4 battery.
Also tried with 3 different charges that came with the S4, no dice... :/
I had to take it back to the store, it was under warranty still.. they are sending it back to Samsung and will get it back in 2-3 weeks, same phone repaired or a refurb i guess.
After doing more search and with the help of some falks from #Android @ EFNET, we came to the conclusion that its an issue with the EMMC chip just like the first generation of Note 2 and S3.
What's pissing me off is that Samsung fixed the issue on Note 2 with a new patch of phones, so newer phones didnt have the EMMC issue as far as i can tell. SO why the hell would they still use it for the S4 is beyond me.
Just a word of advice, if this happens to anyone, make sure you run a backup as soon as it boots back up the first time.
In my case, it booted 3 times by removing the battery and putting it back and froze 3 times, there was no 4th.
If i tried to backup the phone the first or second time it booted, i could still have my data to be restored on the new repaired phone.
This should be marked as closed unless some other people with the same issue want to discuss it here.
Related
This has started to happen (from what I've noticed.) I replaced an LCD on an S4. Worked fine no problems, tested and turned it off and prepared it for sale. I turn all my phones on for the photo and noticed it would hang on the Samsung logo and wouldn't boot into recovery only download.
I thought it needed restoring via Odin and would freeze at "Get PIT for Mapping..." I thought great, the eMMC randomly died on me. Then, I tried to turn it on the next day and it worked, updated & left it turned on until the battery was low and turned it off.
Now, it's doing the same again.
I highly doubt anybody on here will know as it looks like people focus on iPhones but does anybody have a clue why this might be happening?
Thanks
Urban Designs said:
This has started to happen (from what I've noticed.) I replaced an LCD on an S4. Worked fine no problems, tested and turned it off and prepared it for sale. I turn all my phones on for the photo and noticed it would hang on the Samsung logo and wouldn't boot into recovery only download.
I thought it needed restoring via Odin and would freeze at "Get PIT for Mapping..." I thought great, the eMMC randomly died on me. Then, I tried to turn it on the next day and it worked, updated & left it turned on until the battery was low and turned it off.
Now, it's doing the same again.
I highly doubt anybody on here will know as it looks like people focus on iPhones but does anybody have a clue why this might be happening?
Thanks
Click to expand...
Click to collapse
Maybe you can wait in 15 minute. it happens today make a upgrade firmware to Lollipop, The logo Samsung stuck in 15 minute. and later work well.
Abcastillo said:
Maybe you can wait in 15 minute. it happens today make a upgrade firmware to Lollipop, The logo Samsung stuck in 15 minute. and later work well.
Click to expand...
Click to collapse
It's already on Lollipop, fully updated
Reboot to recovery and wipe cache,it should work?
If not,then unmount cache[emoji57]
Sent from my GT-I9505 using Tapatalk
Hello everybody,
I have a rooted S4 LTE (I9505) and the phone was working perfectly for a year and a half, with different roms. I've been running the same rom for about half a year now with no problems. A couple of days ago i gave it to a friend and we did the factory wipe you can do from settings. At that point everything was still working fine. Now to the problem: He was playing a game on the phone and he drained the battery completely so the phone shut down. He charged the phone for about 10 to 15 minutes then tried turning it on. There was the standard Samsung logo and after that wide white horizontal lines started to appear from top to bottom. When they got to the end of the screen everything turned green. After that he turned it off and tried the standard things you try; removing the battery etc. After that i got the phone back at a bar we were at. I turned it on and the green lines appeared, so i turned it off and tried booting download mode and it worked. So i turned it off and tried booting recovery thinking it was a rom issue ( Crashed rom or something, idk.), but it wouldn't. So i tried booting download mode again with no success. Then i left it for a couple of hours and somehow managed to get to download mode. After that the phone shut down as my battery was too low, so i charged it and now there's those green lines again, but this time with no Samsung logo, just the lines...
Does anybody here know what the problem would be?
Sorry for the long description but i wanted to explain everything. xD
I can add pictures if you want me to
Thanks for your help in advance,
Brezo
Almost positive that this is a hardware issue, primarily a bad GPU.
Strephon Alkhalikoi said:
Almost positive that this is a hardware issue, primarily a bad GPU.
Click to expand...
Click to collapse
But when i got into download mode everything was fine. And i think that uses the gpu aswell. Please correct me if i'm wrong
Download mode doesn't require the GPU to do its work, which is why both it and the recovery function normally while Android falters. However, to be certain, flash stock firmware via Odin. If this is a software issue the green lines will go away.
Strephon Alkhalikoi said:
Download mode doesn't require the GPU to do its work, which is why both it and the recovery function normally while Android falters. However, to be certain, flash stock firmware via Odin. If this is a software issue the green lines will go away.
Click to expand...
Click to collapse
Okay. Thanks for the reply I'll post an update when I flash stock firmware.
Hi everyone, after trying everything I could to fix this phone I don't know what to do anymore so I'm here asking for other options.
So the story is, I was just using my phone as I usually would that day and it just randomly turned off and won't turn back on anymore.
(it randomly turned off before a couple of times but it would always turn back on)
- It won't go into recovery mode or any other of the 'modes' (I tried all the different combinations of pressing the keys).
- It's not a battery issue as I've tried my battery on my brother's phone (he has a Note 4 too) and it worked fine and I tried his battery on mine and it wouldn't work.
- I tried the 'drain' method (removing the battery and holding the power button for a minute or more).
- I tried using multiple cables to charge my phone nothing worked.
I didn't drop my phone, wet it, root it or anything and it was working fine the day it happened until it just powered off by itself. When I plug it in my laptop it would make
a sound indicating I've plugged something in but nothing happens. It was version 5.1.1 model SM-N910F.
TLDR; Is there a way to somehow recover the files in the internal phone memory?
This is happening to me as well, also started in February. I'm suspecting a hardware issue. Tried it ALL but rooting. In the past 30 minutes my phone has booted and rebooted itself till it died. If someone can confirm it is a hardware issue. Maybe it's time to unite and get it fixed for free. ~Tamarnouche
Recovering data from a brain dead phone may not be possible, as it probably need some internal component replacement which may erase the data(Mostly). Have u tried connecting it to pc? Better give it to service immediately. Good Luck.
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
HXOY said:
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
Click to expand...
Click to collapse
I have the same problem with my Note 3. Only if I keep the battery out for a long (over 24 hours) time I can see the boot logo. So if you find a solution to this kindly don't forget to tag me, will really appreciate it.
I was wondering..
I came across this Forum group since I was looking for boot problems with my SM-N910T3
I hope flashing pit will resolve this..
I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.
Randomly phone boot directly into Download mode with error;
ddi: mmc_read failed
Often I have to pull battery and hold down /power / home for 10 sec to boot up again.
Thanks
Here is the story,
I flashed Marshmallow on my note 4 n910w8 via odin (I had 5.1.1). After it was done I noticed that the phone got laggy and warm. It would sometimes not boot/restart or it would shut down after it freezes for sometime. I would get the download page with mmc_read failure in red, I would pull out the battery and try again.
What I did:
*Unrooted the phone through SuperSu and flashed Twrp throughout (because it gave other errors and I had to do it again and again after each attempt)
*I tried flashing through twrp but I got the "no md5" error
*Flashed the stock ROM 6.0.1 with PIT since it gave the PIT error on odin
*Wiped cache/data/factory reset multiple times.
*I used both Kies and Smartswitch and was not successful (either read or write failure)
*Flashed the stock 4.4.1 (the original, It could not boot up once) so I returned to the stock 6.0.1
*The phone boots up 3 out 5 times and I was able to watch a full movie on Netflix and browse the web and google maps. But as soon as I locked it, It shut off and did not power up (until i took out the battery and let it cool down).
Where I went:
*A Samsung repair agent here in Montreal said that most of the time it is the Mob and that it would cost 300-400$ CAD to replace
*I went to other repair shops, a few hinted that it might just a matter of reprogramming the Mob and that it involved a risk of bricking the phone for good.
N.B: It is not under warranty and I'm not on contract, It is my own phone.
My question(s): Is there something else I could try? Is there someone who fixed the issued (Assuming it is not hardware) maybe and unbrick fix or something? And also, it there anyway to thoroughly wipe out the old installations so I could start anew?
Also I consider myself pretty knowledgeable. Or I at least learn quick. Do not hesitate to suggest something coarse for me to try. Worse comes to worse, Ill sell it on eBay for part, since it it in mint condition.
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
The Sponge said:
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
Click to expand...
Click to collapse
Thank you very much for your reply, I take it you have the same problem? I will try Wake Lock. And also I'm way ahead of you in the freezing game. Leave for 10mins in the freezer and you can basically flash anything. Also, do you a custom ROM would help?
Hi all,
My galaxy s5 is stuck in a reboot loop. It started doing this today around 12:18pm and I can't get it to stay on long enough to back up my data. I took it to AT&T and they basically did nothing but tried a different battery and booted into safe mode. Neither of those options worked. I took it to best buy and the tech installed the latest updated and flashed the ROM (I believe). Still didnt work. She believed the issue was with the battery but didnt have any new ones there to test so I went to batteries plus and tested a brand new battery, still is rebooting. I am home now and just wiped the cache in recovery mode, still not working. Is there anyway at all I can get this phone to turn on long enough to backup my data? Any other commands I can try to clear whatever is causing this? I was not using my phone when this happened. It died at 15% which I didnt make too big a deal of because I know the battery has been weakening, but when I charged it up for a bit then turned it on, this problem started. When I turned it on, I had a text message coming through and then it restarted. As I was able to get it on for a bit that same text kept coming in over and over again so I thought maybe something with the messaging app and I disabled that all together but the problem remains. I hope someone can help me out here. Thank you.
SOLVED: Samsung Galaxy S5 Reboot Loop
I figured out a workaround and I take full credit because this creative solution was no where to be found on the internet nor did AT&T, Samsung or Best Buy offer any other alternatives aside from wiping the device. This is what I did:
I booted back into Recovery mode and looked through the logs for any indication of what was happening. My assumption was that it was a driver error and so scrolling through the logs I saw an error that said something like fail psy battery. I immediately think maybe its the drivers for power so I thought I'd see how it would respond if I put it in Ultra Power save mode. Thankfully the phone stayed on just long enough for me to put it ultra power save which did work. The phone stopped the reboot cycle it was stuck in but I still was not able to back anything up since the Ultra power save disabled the USB drivers and port. I let it charge up overnight in ultra power save and said I would try regular power save mode in the morning to see if that would also work but this time allow me mass storage access. Well, that worked! I put it in power save and I am backing everything up now as I type. I've got all my pics and now just letting samsung switch do its thing to perform full backup. YAY! I WIN! Hopefully this helps someone else that may have this problem and have tried everything else that is recommended for solving this issue.
-Natasha
Chicago, South side born and raised
Don't really get it, what cause the boot loop in the first place? And you are flashing back to which rom?
I don't know what caused. I wasn't using the phone when it started. I hadn't downloaded any new apps and I wasn't messing around with the OS or system files. The phone battery died at 15%. I plugged in the charger and disconnected when it was at about 28%. I powered the phone on and there were a number of text messages coming through from my friend I was going to lunch with. I opened that message and noticed the text was duplicating itself then it rebooted. Each time I powered it up and got in for a bit that same text was coming through or trying to over and over again. So, I don't know what caused it but I have all of my data backed up and I am going to wipe it now.
Also, the Best Buy tech flashed the ROM so I am not sure which version or anything like that.
Aimara said:
Don't really get it, what cause the boot loop in the first place? And you are flashing back to which rom?
Click to expand...
Click to collapse
samsungGs5 said:
I don't know what caused. I wasn't using the phone when it started. I hadn't downloaded any new apps and I wasn't messing around with the OS or system files. The phone battery died at 15%. I plugged in the charger and disconnected when it was at about 28%. I powered the phone on and there were a number of text messages coming through from my friend I was going to lunch with. I opened that message and noticed the text was duplicating itself then it rebooted. Each time I powered it up and got in for a bit that same text was coming through or trying to over and over again. So, I don't know what caused it but I have all of my data backed up and I am going to wipe it now.
Also, the Best Buy tech flashed the ROM so I am not sure which version or anything like that.
Click to expand...
Click to collapse
which os phone on ? lop or MM ?