so ive checked high and low and cant seem to find anything to help with my issue..i have a gt i9500 and this morning it randomly started restarting but it would always boot back up, but a little while ago it shut off and wont go past the samsung galaxy s4 screen ive tried battery pull but as soon as i insert the battery it turns on without me even pushing the powerbutton. it wont go into recovery mode and when i try to enter download mode it wont lit me hit the up button to enter. i am rooted running hassanrom for over a month now with no isses, can any one help
tgobr2005 said:
so ive checked high and low and cant seem to find anything to help with my issue..i have a gt i9500 and this morning it randomly started restarting but it would always boot back up, but a little while ago it shut off and wont go past the samsung galaxy s4 screen ive tried battery pull but as soon as i insert the battery it turns on without me even pushing the powerbutton. it wont go into recovery mode and when i try to enter download mode it wont lit me hit the up button to enter. i am rooted running hassanrom for over a month now with no isses, can any one help
Click to expand...
Click to collapse
got it to boot flashing stock rom hopefully fixes
tgobr2005 said:
so ive checked high and low and cant seem to find anything to help with my issue..i have a gt i9500 and this morning it randomly started restarting but it would always boot back up, but a little while ago it shut off and wont go past the samsung galaxy s4 screen ive tried battery pull but as soon as i insert the battery it turns on without me even pushing the powerbutton. it wont go into recovery mode and when i try to enter download mode it wont lit me hit the up button to enter. i am rooted running hassanrom for over a month now with no isses, can any one help
Click to expand...
Click to collapse
It could be the battery itself. They do go bad. Check it to see if it has any bulging.
Related
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.
Hi all, first post!
I recently purchased an unlocked international version of the Galaxy Note 4 from Amazon. Loving the phone so far, I rooted it on the first day since it didn't come with any warranty anyway.
My question is regarding recovery mode. I read that by clearing the system cache from the recovery mode menu, battery life drastically improves. I mean battery life on the Note 4 is pretty good as it is but who doesn't want more battery life?
Anyway, when I turn off the phone and enter recovery mode by holding down power, home and volume up, I get the green android bot on my screen, and all that happens is the robot flashes once every few seconds, that's about it. Nothing else happens, no menu, nothing.
I tried searching online but couldn't find any answers so I thought I'd try here. Any help as to why this is happening and how to successfully get to recovery mode would be great. Thanks
Bluelondon said:
Hi all, first post!
I recently purchased an unlocked international version of the Galaxy Note 4 from Amazon. Loving the phone so far, I rooted it on the first day since it didn't come with any warranty anyway.
My question is regarding recovery mode. I read that by clearing the system cache from the recovery mode menu, battery life drastically improves. I mean battery life on the Note 4 is pretty good as it is but who doesn't want more battery life?
Anyway, when I turn off the phone and enter recovery mode by holding down power, home and volume up, I get the green android bot on my screen, and all that happens is the robot flashes once every few seconds, that's about it. Nothing else happens, no menu, nothing.
I tried searching online but couldn't find any answers so I thought I'd try here. Any help as to why this is happening and how to successfully get to recovery mode would be great. Thanks
Click to expand...
Click to collapse
When the flashing "thing" happens.. try pressing and releasing the volume up + down button.. or try pressing them alternately.. It MIGHT do the trick and allow you to access the menu.. You can try... Thanks
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 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 ?
Hello, so i've had this Note 4 for about 2 years, i had no problems with it thus far until recently ( 3 hours ago actually) i was just texting and browsing Instagram and out of no where the screen froze, it became unresponsive and the screen went black and started constantly vibrating so i quickly pulled the battery out and put it back in again, tried to start it again and it got stuck on the Samsung logo, i went for recovery mode and tried to look up latest cashe log and it froze right there too and restarted, pulled battery out and in again, tried to get into Recovery mode for a second time and a dm-verity verification failed error on the lower left corner popped up, i selected "Restart phone" and it got stuck on the Samsung logo again, battery in-out, tried to get into Recovery mode for a third time to do a factory reset but this time it got stuck whilst trying to boot onto recovery, and i had to out-in battery again, tried several times to get into recovery and it didn't work, i just gave up and started searching, then after 14 minutes i decide to give it another try and it normally booted up! i inserted in my PIN and browsed the apps for about 2mins but it froze, again, and the whole cycle kept repeating i let it cool down for 15mins and it boots up normally but freezes again after a few minutes of usage, i noticed that it insanely overheats before freezing (especially right above the SIM card area) and the four CPU cores are showing 2469MHz and on 100% (But that's also the case when the phone just boots up right?), Now i basically can't access recovery mode and i'm stuck with a Freeze-Reboot looped and i'm left with no other option but a full Stock ROM flash, the thing is i can't even get into recovery to do a full wipe before flashing in the ROM, can i just flash in again a TWRP recovery? and is there any way to fix this without having to do a full Stock ROM flash (i Tried the wake lock app it didn't work) and i'm on Android 5.0.1, this has JUST happened today and never before. i'm hoping this isn't a hardware issue.
UPDATE: i have just noticed something rather interesting, the phone immediately freezes and goes nuts with the reboots and failed recovery modes instantly after i connect it to a wifi network, and exactly when it's attempting to "send report", a sending report sign shows up in the notification bar and it immediately screws up the phone until i do another Factory reset, i just did another one without connecting to a wifi network and i've already gone 40mins with it without any issues but perhaps it's just because it's not on heavy usage?
Sounds like you have the eMMC issue.
You can try and reflash with Odin. Get the right version from Sammobile.
Do yu get to download mode in any of the scenarios you describe?
Try WakeLock again and select the level to 4
Having the same issue
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Cybrid013 said:
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Click to expand...
Click to collapse
If you have the Snapdragon version - it's highly possible to have the emmc problem. Which is a bummer and the phone is like dead.
Unless you can buy another 910C motherboard and swap it.
Sorry.
What is short name for emmc?
jjoeshua said:
What is short name for emmc?
Click to expand...
Click to collapse
embedded multimedia controller
Just been having a very similar problem. I posted this elsewhere, but it may be helpful:
"My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilĂ ! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1."
Also now downloaded a eMMC bug check that says my eMMC chip is 'sane'. Guess we'll see