Database Users

Help! Bootlooping out of the blue for NO reason

So... For no explainable reason my phone has gone into a bootloop, simply from me attempting to restart the phone.
Details of anything I can think of that might be related are below. I need a genius to help me A) figure out WHY this happend, B) help me figure out if there is a way to (non-destructively) get out of this bootloop (i.e. NOT having to do a factory reset), and / or C) tell me if there is a way that I can perform a full system backup using ADB, Fastboot or Odin with a phone that can't get past recovery or bootloader without going into an endless bootloop. I'm not a lazy guy and normally take the time to research problems and figure them out on my own, however at present this is my only activated phone, it's almost 11pm, I have to be up and out the door at 6am tomorrow, I will be judging competitions all day and will not have any opportunity to do anything about this until late tomorrow... In the meantime, I need a functioning PH1!!
My PH1 is the Sprint variant and I have not rooted it nor have I unlocked the bootloader. The only thing I have "done" to the phone is to sideload the latest OTA, NMJ32F (the day it came out, over a week ago, and it's functioned perfectly since that update). My phone has been in use throughout the day today with no difficulties. I went into a building with very spotty service for several hours this evening. On the way home, I noticed that I was stuck in 3G service, despite being in an area I know has good 4G/LTE coverage. I also noticed an unidentified icon on the status bar, a rectangle, which was located (I believe) to the right of the battery icon. It looked like a rectangle, perhaps representing a screen, or a phone? IDK. The other item of note is that I did sign into the guest account on my phone so that my daughter could use the stopwatch for timing competetion events without tampering with anything. She didn't drop it or get it wet or anything along those lines... she used it to time events, returned it to me in perfect shape. I logged out of the guest account, back into my account, rebooted to try to get the phone back into 4G service, and boom, I'm stuck in a frigging bootloop for no apparent reason.... And I'm about to lose my mind over this.
I CAN get into download mode and into recovery mode by holding the appropriate button combinations when it loops, but from there whether I power off and power on again or whether I select reboot from recovery menu, it continues to loop...

Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!

So I am running O beta rooted and last night this happened to me. I ended up going into fastboot and starting OS through there and I had no issue with the reboot bootloop. However, last night I went to bed with a phone @ 75-80% and woke up 6 hours later with a dead phone. Charged and rebooted this morn and everything seemed normal today. It was super wierd

Had to return mine for this very reason. Less than a week in service and went into boot loop. The reboot happened after it lost all battery power (corrupt filesystem?). Several factory resets did nothing to fix it. Removed the SIM. The phone was also fully charged. Did not try ADB as it was brand new and a return was the safest easiest option.

ccopelan said:
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
Click to expand...
Click to collapse
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.

chray1 said:
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
Click to expand...
Click to collapse
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!

fhlutiis said:
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
Click to expand...
Click to collapse
interesting.
If it's your second phone, have you looked at what applications you install?
The probability of getting two bad phones is pretty slim unless there is a major manufacturing flaw.
Not saying it can't happen, but it would be unusual.

Could it be due to Encrypted Data partition?
It once happened to me on a Huawei Mate 2 which I encrypted data and battery dead, then bootloop.
If that's due to corrupt encrypted partition, there seems only other recovery mode can help you get some files back.

How I saved Nexus 6P from bootloop with OEM locked?

I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.

Working but not enough
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Speed1908 said:
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Click to expand...
Click to collapse
---------- Post added at 05:18 PM ---------- Previous post was at 05:09 PM ----------
I just waited like 5 or 10 minutes and my phone started in system. Just enough to activate stuff in developers options!
arkanthos said:
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Click to expand...
Click to collapse

I just had this happen to me. Friday evening, I noticed an update and I usually read reviews prior to downloading, but I clicked anyways. All seemed fine until Saturday night, was in fb, watching a cooking video and clicked on a link for the recipe when my phone went blank and to the Google screen. tried for 2 days to reboot, get into boot-loader, recovery, anything!
Luckily, I have 9 more days on my Square Trade warranty. They required me to take to a fix-it store (all they could try was a battery pull, which was unsuccessful). Square Trade sourced me a replacement, so it came in last night and I am downloading all my apps and trying to get back "to normal".
I did do an Android update, at the urging of my son, since he has the same phone. Now I see one more, that is a small update. Worried if I should download or not?
I just found this forum and haven't yet gone searching for help on it.
This info is good to know.
Thanks and take care!

Thank you save my life again i have no hair dryer and place it on my rick cooking about 10 mins after that it boot slow gooe animated and i format factory and clear cach first try and succeeded

Nexus 6P Bootloop after 4core

I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.

snappycg1996 said:
I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.
Click to expand...
Click to collapse
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.

maxguncel said:
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.
Click to expand...
Click to collapse
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now

snappycg1996 said:
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now
Click to expand...
Click to collapse
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds

maxguncel said:
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds
Click to expand...
Click to collapse
Thank you You too! Day of Thanksgiving he is supposed to get here, but my wife isn't doing too well lol do you know of any way for us to pull data? Adb is failing to see my device when it's in the bootloader, fastboot is working though. I tried once more to flash twrp 4 core and boot it with no luck. Those small cores gave out I guess. I left my phone on overnight bootlooping with no luck. I got most things off, just my actual camera fder I couldn't get and apps which aren't a huge deal.

Sadly this morning I had the same problem. Bootlooping, I even cannot enter into Recovery. Then, suddently, it restarted, but I wasn't home, so I hadn't the chance to save the data. Then, about 3 hours later, it restarted bootlooping and, since then, it's stucked into this bootloop. Even reflashing the modified boot won't work.
Anybody knows how to at least recover the data inside? Even if I have to break the phone (I'm going to buy onther one soon)

hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?

Marxmellow said:
hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?
Click to expand...
Click to collapse
It simply means that the battery is fully discharged. Keep it connected to the current and maybe it restarts working.
I'm in the same situation since yesterday, hoping that at some point it returns working for some time, just to backup some data. I have like 10GB of photos not backupped in it.

When I replaced my battery I reinstalled factory. Start from scratch.
I had the same issue and that's all I did. Booted fine after that. I used the ifixit battery tho, cause if you got a lower cost one it could be the battery itself too

Stock 7.1.2 stuck in boot loop, fix doesn't work, can only get to fastboot

This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance

chmmr said:
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
Click to expand...
Click to collapse
I have the exact same issue. I run the same version operating system as you have an unlocked bootloader otherwise have not modified the typical system install. I did already have the fix applied from an earlier incident but now it is boot looping and won't stop. I have red threads here and there that have advised to apply heat to the phone and that might get it to boot at least to get your data off. Myself I have had no such luck with this technique but perhaps it will work for you otherwise I have since moved on to the OnePlus 6t. A very awesome replacement not to mention at a decent price for more horsepower and storage
Sent from my ONEPLUS A6013 using Tapatalk

Just in case it helps anyone with this phone and issue, I was able to get a couple more boots out of it, enough to rescue some data, by doing the "15 minutes in the freezer in a ziploc bag" trick.
RIP Nexus 6P, shame about the BLOD!

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.