Hey guys, I was using my phone today as per usual but for some reason, the app I was using crashed and then the phone shut off. The phone then went into a boot loop and I thought it'd be an easy fix to just reformat the phone/factory reset, however, these solutions didn't work.
So I went to Factory Image for Nexus and installed 7.1.2 (N2G48B, Jul 2017) with the script and line by line but there is still no success. The phone just turns on, has the "Google" boot screen then turns back off. I am unable to get into recovery and nothing that I tried worked.
I tried looking around for a fix and there are some wacky solutions that people have used and had some success like using a heat gun on it and letting it die out but I feel like that's unsafe.
I also tried this but it also didn't work.
Can anyone help me with this issue?
(Also my 6P is out of warranty so I'm pretty much screwed)
vraj1470 said:
Hey guys, I was using my phone today as per usual but for some reason, the app I was using crashed and then the phone shut off. The phone then went into a boot loop and I thought it'd be an easy fix to just reformat the phone/factory reset, however, these solutions didn't work.
So I went to Factory Image for Nexus and installed 7.1.2 (N2G48B, Jul 2017) with the script and line by line but there is still no success. The phone just turns on, has the "Google" boot screen then turns back off. I am unable to get into recovery and nothing that I tried worked.
I tried looking around for a fix and there are some wacky solutions that people have used and had some success like using a heat gun on it and letting it die out but I feel like that's unsafe.
I also tried this but it also didn't work.
Can anyone help me with this issue?
(Also my 6P is out of warranty so I'm pretty much screwed)
Click to expand...
Click to collapse
Most of the users facing same issue. Till date no solution for this. It's due to mother board problem. Since it's out of warranty your situation is more worse.
Related
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,
I got a nexus 6p several weeks ago and the wifi was fine until it took several google updates and then it went to the birds. I've tried going back to 7.1.1 in the hopes of fixing the issue. The random reboots have stopped happening pretty much. So not sure where to go from here.....I have a RMA with Huawei, but still waiting on shipping label. We all know how long this will take.........
Any help is highly appreciated
The random reboots are a bad sign. Usually that means the phone is on its way towards the boot loop of death. If you went back to 7.1.1 flashing everything individually like in the XDA guide then I would try again using the flash-all.bat command instead. It's extremely easy for something to go wrong if you flash everything individually. Google made flashing with the flash-all.bat command pretty much idiot proof which is why I think that method is almost always preferable to what XDA suggests. If you actually did flash with the flash-all.bat command and the bad WiFi issue persists you probably have a hardware issue with your phone. You can also go under settings / Google / Networking and see if there is a WiFi Assistant toggle. If there is set it to the opposite of what it's currently set at and see if that makes any difference.
Well since reinstalling 7.1.2 using Nexus Root Toolkit the phone has only restarted once. Now the wifi is solid when bluetooth is off. But as soon as I turn bluetooth on the phone goes crazy.
Hello! Okay so this is a weird issue with my phone. It started in November and i had to switch to an older galaxy s5 which is pretty slow for today's standards. Anyways one day while it was charging it started to reboot and didn't stop. I didn't think much of it. I took the phone apart to make sure it wasn't shorting out or anything. I reset everything on the phone. I replace about half the phone. I really need the phone to work because I need the speed. So the full problem the phone would turn on and boot but right when it going to the lock screen it would restart. Sometimes it boots all the way but it crashes and reboots about 1 minute of use. I cannot find a solution. I tried flashing a the original rom and it still didn't work. I put the boot loader back to stock. I tried to reflash the kernel, that also didn't work. If watched a ton of tutorials but no one seems to have the same problem.
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
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!