Related
Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.
JJBerryere said:
Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.
Click to expand...
Click to collapse
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.
theminikiller said:
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.
Click to expand...
Click to collapse
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
You download the full stock ROM from Google, and use fastboot to flash it. Here is a guide on how to do it. http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers
greg17477 said:
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers
Click to expand...
Click to collapse
Tried this, didn't work.
My phone has basically been flashing red for awhile now and it doesn't turn on at all.
Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20
anupampb said:
Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20
Click to expand...
Click to collapse
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.
JJBerryere said:
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.
Click to expand...
Click to collapse
Your farther does not really worry enough for your health
https://en.wikipedia.org/wiki/Lithium-ion_battery#Safety
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.
So I'm not sure what the **** happened, but my 6p decided to brick itself after the latest update. It's essentially in a perpetual bootloop. When it does manage to boot up, it bootloops again a few seconds later. I tried reflashing 7.1.1 and 7.0 multiple times. Nothing worked. It's running completely stock software, so I'm not sure what exactly could be the problem. Has anyone else experienced this problem? Either way, I haven't had good luck this year with tech... Galaxy Note 7, EVGA GTX 1080, and now a bricked 6p... I think I may have a curse or something.
Call Huawei and they will fix your phone at no cost. Don't even try to fix it !
Try Wugs first to go back to full stock.......fully automated......Let it try to fix the problem.....
Kind of sounds like you didn't update your vendor files......
http://forum.xda-developers.com/showthread.php?t=3258493
Sent from my Pixel XL using XDA Premium HD app
This is a known bug. Happened to me a month ago. I decided to ditch the Nexus 6p and get an LG V20. I called Huawei and they were going to do an RMA at no cost but the fact that I opened my phone to check if the power button wasn't the cause of the bootloop they said the warranty was voided. They wouldn't let me pay cash for any repairs.
Let me tell you my story and somehow my Nexus is working again. I'm now one my 1+3 though. So I was enrolled in the beta program. Bootloader unlocked, stock recovery. When I updated to dp2, twice my device rebooted and got stock at the Google logo. No access to recovery only bootloader. Then the next day literally, the OTA for final 7.1.1 was released. I decided to sideload the OTA. Magically, my Nexus came back to life. This would be short lived. About 48 hrs later. I was in the camera, and bamm, it froze then boot loop from hell. My Nexus was in the same pickle as dp2. After researching online, no fix. I was on my new phone and figured it was a goner. I left it charging constantly and would never turn on. Then the full image came out. Figured I'd try it out. Flashed it to no avail. Still stuck. Again I wrote it off upset but life goes on. 2 nights ago when I could not sleep, I had a strange idea. Lemme flash back to 7.0. so I downloaded the image from Google and flashed it. Same result. I then had an appifany, now your mileage may vary, I realized I had been charging my Nexus with my 1+3 dash charger. I switched it to the stock brick I have plugged in elsewhere. It was still bootlooping but I left it plugged in. Yesterday morning when I awoke, I noticed something different, my Nexus was on the charging screen when the unit is turned off, hence showing the battery logo @ 100%. I then held my power button and lo and behold, it turned on and greeted me to 7.0 setup. I nearly **** the bed. I skipped most the setup as I didn't care. Set up my wifi, and it went to the home screen. Instantly popped up with an OTA to final 7.1.1. So I proceeded to download it. Now I didn't recheck my phone untill I got back from work, but when I did, my phone was still on, OTA downloaded and ready for install, a little over 600 meg update. Before going to bed, I hit restart and upgrade. It when through the update without a hitch. My phone has been. Working for 24hrs, no crashs or bootloops. Fingers crossed this does not reoccur but my Nexus thus far is fully running with no reoccurrence. I wonder if this issue has something to do with what it's plugged into. I have no explanation as to why or how but that's what I'm pointing my finger at as not every USB c power brick and cable is made equal. Maybe a fluke, it may rebrick itself , but for now it's back in action sitting on the sideline. I will update if it rebricks itself.
Sent from my ONEPLUS A3000 using Tapatalk
icedmayhem said:
Let me tell you my story and somehow my Nexus is working again. I'm now one my 1+3 though. So I was enrolled in the beta program. Bootloader unlocked, stock recovery. When I updated to dp2, twice my device rebooted and got stock at the Google logo. No access to recovery only bootloader. Then the next day literally, the OTA for final 7.1.1 was released. I decided to sideload the OTA. Magically, my Nexus came back to life. This would be short lived. About 48 hrs later. I was in the camera, and bamm, it froze then boot loop from hell. My Nexus was in the same pickle as dp2. After researching online, no fix. I was on my new phone and figured it was a goner. I left it charging constantly and would never turn on. Then the full image came out. Figured I'd try it out. Flashed it to no avail. Still stuck. Again I wrote it off upset but life goes on. 2 nights ago when I could not sleep, I had a strange idea. Lemme flash back to 7.0. so I downloaded the image from Google and flashed it. Same result. I then had an appifany, now your mileage may vary, I realized I had been charging my Nexus with my 1+3 dash charger. I switched it to the stock brick I have plugged in elsewhere. It was still bootlooping but I left it plugged in. Yesterday morning when I awoke, I noticed something different, my Nexus was on the charging screen when the unit is turned off, hence showing the battery logo @ 100%. I then held my power button and lo and behold, it turned on and greeted me to 7.0 setup. I nearly **** the bed. I skipped most the setup as I didn't care. Set up my wifi, and it went to the home screen. Instantly popped up with an OTA to final 7.1.1. So I proceeded to download it. Now I didn't recheck my phone untill I got back from work, but when I did, my phone was still on, OTA downloaded and ready for install, a little over 600 meg update. Before going to bed, I hit restart and upgrade. It when through the update without a hitch. My phone has been. Working for 24hrs, no crashs or bootloops. Fingers crossed this does not reoccur but my Nexus thus far is fully running with no reoccurrence. I wonder if this issue has something to do with what it's plugged into. I have no explanation as to why or how but that's what I'm pointing my finger at as not every USB c power brick and cable is made equal. Maybe a fluke, it may rebrick itself , but for now it's back in action sitting on the sideline. I will update if it rebricks itself.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Dude this is really interesting. I am therefore holding off of updating to 7.1.1 and still using 6.0.1. Although 7.1.1 is very tempting to me. Keep us posted regarding your Nexus 6p's bootloop and workings on this thread please
Wow alot of people are having issue with the 6p... Google need to fix things asap
icedmayhem said:
Let me tell you my story and somehow my Nexus is working again. I'm now one my 1+3 though. So I was enrolled in the beta program. Bootloader unlocked, stock recovery. When I updated to dp2, twice my device rebooted and got stock at the Google logo. No access to recovery only bootloader. Then the next day literally, the OTA for final 7.1.1 was released. I decided to sideload the OTA. Magically, my Nexus came back to life. This would be short lived. About 48 hrs later. I was in the camera, and bamm, it froze then boot loop from hell. My Nexus was in the same pickle as dp2. After researching online, no fix. I was on my new phone and figured it was a goner. I left it charging constantly and would never turn on. Then the full image came out. Figured I'd try it out. Flashed it to no avail. Still stuck. Again I wrote it off upset but life goes on. 2 nights ago when I could not sleep, I had a strange idea. Lemme flash back to 7.0. so I downloaded the image from Google and flashed it. Same result. I then had an appifany, now your mileage may vary, I realized I had been charging my Nexus with my 1+3 dash charger. I switched it to the stock brick I have plugged in elsewhere. It was still bootlooping but I left it plugged in. Yesterday morning when I awoke, I noticed something different, my Nexus was on the charging screen when the unit is turned off, hence showing the battery logo @ 100%. I then held my power button and lo and behold, it turned on and greeted me to 7.0 setup. I nearly **** the bed. I skipped most the setup as I didn't care. Set up my wifi, and it went to the home screen. Instantly popped up with an OTA to final 7.1.1. So I proceeded to download it. Now I didn't recheck my phone untill I got back from work, but when I did, my phone was still on, OTA downloaded and ready for install, a little over 600 meg update. Before going to bed, I hit restart and upgrade. It when through the update without a hitch. My phone has been. Working for 24hrs, no crashs or bootloops. Fingers crossed this does not reoccur but my Nexus thus far is fully running with no reoccurrence. I wonder if this issue has something to do with what it's plugged into. I have no explanation as to why or how but that's what I'm pointing my finger at as not every USB c power brick and cable is made equal. Maybe a fluke, it may rebrick itself , but for now it's back in action sitting on the sideline. I will update if it rebricks itself.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Update:. 12/28. 0212 hrs. Even though I'm using my 1+3 as my daily driver, my 6p still works. No bootloops, random reboots, or freezing in os. Tested with calling, SMS, camera, downloads, etc. Haven't modified or flashed anything since, but then again I prefer stock nowadays. Can't say I'm not surprised although.
Sent from my ONEPLUS A3000 using Tapatalk
so many people encountering issues and bricks by updating from stock M i guess? to Nougat.
i have never once had an issue downgrading back to MM and upgrading back to Nougat, because of custom roms i guess?
i am not a stock'ish guy.
but i know there are many who just want the phone as it is, no mods etc.
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.
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