Database Users

Phone crash after battery died!!

my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..

Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje

Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?

everything was stock on mine, no root.......maybe thats why i could recover it??!!

Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.

I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.

Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions

That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!

I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1

Phone is Broken

Alright, so like many people, I tried to play Pokemon GO. I was playing for about 20 minutes on my break at work, and I noticed that as I was switching between it and other apps, my phone was getting pretty laggy and bogged down, to a point where the phone just froze for a minute, then when the screen turned off. I couldn't turn it on for a further minute or so. Eventually after a few minutes of this, the phone just crashed, Upon trying to restart it, it went to the odin screen, saying "mmc_read error", or something like that. I pulled out the battery and let it sit for a few minutes and tried again. It started to boot, but it was stuck on the phone's model splash screen for several minutes, which its never done before. After the phone finally got booted up, it would freeze often, and I would not be able to turn the screen back on for several minutes at a time. This has persisted all night, crashing and freezing for the remainder of my shift. After I got home I tried restarting it again, and the phone wouldn't turn on at all, so I again pulled the battery and let it sit for a while. I've done this a few times now.
Sorry it's a bit lengthy, but I tried to recreate the events of what's happened as best I could. If you need any other info just ask
I have uninstalled the game from my phone now, the phone is completely stock, no roms, not rooted. I do not recall it feeling too hot as if it had overheated
I really am not experienced with issues like this, and I really would not like to have to buy a new phone

Hmm, that error is supposedly of the EMMC failing, now you will be lucky if it was a one time incident. Now to be quite honest I don't think anyone could tell you that whether the problem will come back or not, and you can't do much anyway. I will say if the phone is running okay now, let it. Or if you are really unlucky then the problem will come back, the EMMC might fail permanently. But if you see one or two more reboot incidents like that, I think its fair to conclude that your phone is done mate.

Currently I can turn on the phone, but after I turn the screen off, it won't come back on again

Oh darn mate. You could try to wipe the phone completely from recovery (TWRP) and then flash the stock ROM. Now please don't blame me if the phone gets dead or something after that, cause my Note 3 died just few months back, and it took me a good couple of months to get over that fact. However one thing is for sure, if your emmc is supposed to fail, or motherboard, then it will no matter what.

Galaxy Note 4 constant freezing & restarting!

Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.

Sounds like your battery is on its way out. Have you tried a new battery?

Already mentioned in post above
tiguy99 said:
Sounds like your battery is on its way out. Have you tried a new battery?
Click to expand...
Click to collapse
QCube said:
I've tried everything, bought a replacement (genuine) battery and not fixed it.
Click to expand...
Click to collapse
Earlier in the week I had an error I've not seen before. Phone restarted and went to black screen sort of looking at a recovery screen with android logo and in the centre of the screen was the message
"Kernal Panic" with some information on the top. This only has happened the one time and hasn't happened since. Took the battery out and restarted again...

Try hardreset or flash via odin

Krprem said:
Try hardreset or flash via odin
Click to expand...
Click to collapse
How do I go about doing either of these....
Still happening and it's driving me insane, It won't last me until the end of my contract (January)

Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.

You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.

QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:

ithehappy said:
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
Click to expand...
Click to collapse
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
phonepie said:
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
Click to expand...
Click to collapse
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
grizzylemon said:
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
Click to expand...
Click to collapse
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!

While upgrading a phone, especially for major upgrades like from LP to MM, OTA method should always be avoided. You MUST do a clean flash of the ROM, otherwise you are bound to have problems. 80% of time people complain because they didn't flash the ROM cleanly, so whatever you want to do now, do it, but if it doesn't solve it (very likely it won't), then kindly flash the ROM via Odin after a full wipe. And if even that doesn't solve it then its hardware.

QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?

phonepie said:
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
Click to expand...
Click to collapse
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016

QCube said:
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
Click to expand...
Click to collapse
Are you able to wedge a folded small piece of paper between the bottom edge of the battery and the phone to make the battery fit tighter? I mean it's not good to have a loose battery. But I can't see how that would cause the screen to stay on. If anything I would think it would cause the phone to shut off or reboot.

QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.

grizzylemon said:
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
Click to expand...
Click to collapse
why don't you reflash you device with supported PIT file and stock F.W ?

QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Aside from the previously proposed wake lock solution, members in the T-Mobile Note 4 threads have experienced limited success with a downgrade to LP from MM.
From my reading, these issues seem to be common across all Snapdragon models, not to say it Exynos is excluded (I don't frequent Exynos threads).
​
himuslg123 said:
why don't you reflash you device with supported PIT file and stock F.W ?
Click to expand...
Click to collapse
I tried that and it didn't work for me. The only surefire solution is a replacement device, but even then there's no guarantee the device won't start acting up in the future.

pls help stuck in download mode
this is the issue I'm getting...I did a complete data wipe using twrp...now stuck on this screen...cant even push files...device not recognized in adb or fastboot mode....
what to do...??
imgur(dot)com/a/gKPaL

Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.

Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.

hathertonwood said:
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Click to expand...
Click to collapse
Wow, that sounds promising. I'm sending mine for replacement, and although I'm not getting a new MB installed, hopefully the incoming unit will be similar in performance to yours.
ithehappy said:
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
Click to expand...
Click to collapse
Your reasoning sounds plausible, but my phone suffered similar issues and I only flashed my unit 2-3 times in the 14 months I had it.

Note4 boots into download mode.

So, here is my problem. I've got an almost four years old Note4. I flashed some custom ROM's after i bought it but then I found an old X-note 4.4.4 based custom ROM and i was using that for more than 2 years. Yesterday around noon i noticed that if I try to use Viber, it takes seconds till it opens, and lags badly. (Before that the phone was working perfectly for years). I deleted it, reinstalled, but the problem stayed the same. After a few hours all the other apps started to do the same, the phone became really laggy. As time went by it got worse and worse, around 8pm it started to freeze, reboot, became almost completely useless. I thought maybe a factory reset and a new flash would help. I did a factory reset, and flashed a completely stock ROM on it. It started well, was working good for an hour or so, and then the same problems occured again. Lag, freeze, reboot.... And then nothing. Did not even restart. I can switch it on every now and then, (like in every 20 minutes), but it boots into odin mode. I thought maybe the battery, but that is less then 2 months old. Anyone any idea what happened? I mean the phone is almost 4 years old, so I'm not really pissed off, the only reason why I wanna keep using the Note4 cuz it's removable battery. I don't like phones with built-in battery, this is why i did not upgrade to Note8 for instance. Any help would be much appreciated. By the way, my device is an SM-N910F.

Well, things got even weirder later. I found my old battery which i replaced 2 months ago, still had some juice in it, i put it in, and the phone started!!! Worked perfectly, for about an hour and a bit, then the same problems occured again, lag freeze reboot, and now it boots itself into recovery if i can start it up at all... All the same story. Anyway, i threw it in the drawer and bought a new phone.

Galaxy S5 with Lineage OS stuck in a bootloop

Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Might Be A Malicious OTA Uptade , My Advice For You , Install Stock Rom

Try installing a different rom and if that works, retry installing LOS. Two years ago i became unable to update/install LOS. RR was an instant success and i kept using that till becoming somewhat instable one year ago, so back to LOS, w/o difficulties(probably a clean install of RR would have solved the problems i had, but i didn' t want to do this two times, if really RR and only that was the culprit).
Of course you can start by reinstalling stock rom in Download Mode, as this will be the last attempt if all previous measures may fail. Then re-root, re-install TWRP etc.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
I Heard That The Last Uptade For Lineage Doesn't Work So Download A New ROM In Your Computer And Put It On A SD-CARD And Boot To Recovery And Clean-Flash It
Oh If You Want To Know My ROM I'm Using : Resurrection Remix.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.

yerrag said:
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
Click to expand...
Click to collapse
Well, this worked for a while. Then, bootloop became more stubborn.
By then, I had already bought a phone to replace it, so I was in no hurry to fix this issue but still, I hate to see a good phone go. Still has a screen that stood the test of time, and at high res, and I love the size of the phone.
So, another Hail Mary. And it worked!
I put the phone, worked in tissue paper, then enclosed in bubble wrap, in the freezer overnight, surrounded by grains of rice in a plastic container, that had been vacuumed by a FoodSaver machine.
The following morning, removed the phone from the freezer and laid it bare, separating the battery from it, and wiped it clear of moisture, and let it sit to evaporate any more moisture from the temperature gradient.
Then started the phone, and the bootloop once again gone.
So, phone saved. But since it's no longer that reliable due to the recurring bootloop problem, it would be my phone to watch streaming movies from Amazon Prime or Netflix, but not my phone for receiving calls and text messages, or for Waze and all.
The lesson I got from this is that with this phone, the circuitry inside has become finicky. To open it up and fix it would be too bothersome, especially with the circuitry being composed of embedded modules. Probably somewhere inside there is a capacitor that has reached its reliable end of life, but still breathing and needing an occasional handholding. So, I just gotta learn to live with this quirk, and this quirk is tolerable for the use I have it for.
So, if you run across this problem, I hope I gave you a workaround for you to remain loyal to a workhorse that served you long enough.