I've had my 16GB N7 for about a year. After some initial experimentation with ROMs I went back to stock and left it there. The device isn't used too much, generally streaming music and for web browsing.
About a month ago the device began locking up and rebooting maybe once every few days. This seemed to happen most when video was played or music was streamed. I didn't do anything about it, just ignored the trouble and made a mental note that I ought to wipe the device and start fresh.
Then a couple of weeks ago, I picked up the device and it was displaying the "Google" bootloader screen. As I watched, the screen went blank for a moment, then the bootloader screen again. This repeated 5 or 6 times before I force-powered the device off and on. This time it got past the bootloader screen to the Nexus 'X' screen, then to the lock screen, and then froze and rebooted. From that point on, the device would boot to the lockscreen, crash, and reboot - eventually ending up just loading the bootloader over and over, never showing the 'X', just the 'Google' logo.
So I flashed TWRP and did a factory reset, cleared the cache, etc. No difference. Device was completely unusable. Crash on lockscreen.
I wiped all partitions and did a restore from factory images. This bought me a week. Crashes began on day 2, and by day 8 the device was back to looping on the "Google" bootloader screen.
I wondered if maybe there was some problem with Google's factory image (unlikely, but worth a shot. I did a full wipe and installed CM10.1M1. This bought me about a week of use.
As it stands now, the device gets past the bootloader, gets to the CyanogenMod' splash screen, spins for a while, freezes, reboots, repeat.
So, two different ROMs, same random crashes escalating into a completely unusable system within about a week of light use. No abuse, no water damage, no drops, this tablet has been babied.
Questions:
Am I special, or has anyone else seen this behavior?
Is there any way to determine the health of the SSD?
Does anyone have any idea what might be going on here?
What should I do now?
Thanks.
Hey, just to ask you mate.
Does this happen alot in Chrome?
I have an Issue, caused by different things but always the same causes :
Either multiple tabs open
Video playing in full screen
Trying to close a tab with a video/flash in it.
My Tablet FULLY and I mean FULLY Crashes, so I have to hold power to restart.
Then all back to smooth silky nexus.
I hope this isn't a sign that I'm going down the same road you are.
Does this sound a similar issue?!
Definitely can't be the SSD, as there is none. What you mean is the NAND Flash, but without actually seeing it troubleshooting this via a forum isn't especially feasible. Heck, it could very likely be the SoC, but who knows?!
Unless you were handed a pre-release model, your period of ownership is closer to six months than it is a year (the N7 has been on the market for roughly 7 1/2 months). This is good news for you, as it's still covered by warranty. Restore to stock and RMA it.
The symptoms you describe could be caused by any number of root causes.
If you have any time left on the warranty, I would strongly encourage you to return it to pure stock (including stock recovery), relock the bootloader, factory reset... and get the RMA process started.
Those eMMC flash memory chips are supposed to have a wear-leveling controller, but I suppose that doesn't preclude problems from occurring, nor does it guarantee the controller algorithms are implemented in a bug-free fashion. It is sort of impossible to know if the OP's troubles are common or rare; there have been a few similar-sounding reports here, but there are millions of devices in circulation.
The OP's post surely motivates me to have a pure-stock ROM backup waiting in the wings. Any hint of the same kind of trouble on my N7 while the warranty is still good, and it's going back to Asus under RMA.
good luck
you're not alone
This clearly is a common problem as now my tab has started doing the exact same thing 2 years after a motherboard replacement however unfortunately I have bootloader 4.23 and therefore can't flash anything to my device. My question is what exactly causes it?
Related
Ok guys. I don't post often since I can usually find my answers by lurking the forums....but I'm at my wits end here. My 2012 Wi-Fi nexus 7 all of a sudden started acting funny one day. It would freeze u randomly, then reboot, then get stuck in a boot loop for about 10-15 minutes, then boot up, then freeze after about 1-2 minutes of use and repeat the whole process. This was on stock 4.4.2. I've since tried using the toolkit to reflash stock, fix bootloop, unlock and root...all of which I was able to do. None of which helped my issue. Although flashing AOKP DID seem to fix it for about an hour.
Anyway, I gave up on it for about a week and came back to it this morning. Although it wasn't even going to te google boot animation, just stuck on the google logo. So I reflashed stock 4.4.2 again. Now I'm back to square 1. So it boots and will function for maybe about a minute or 2 (or less) before freezing and rebooting.
Is this device shot? I'm out of Google AND ASUS warranty now
I posted something in the big help thread yesterday (probably a mistake). Mine is doing exactly what you describe in terms of working for about 2 minutes before freezing, then rebooting. Mine is 100% stock 4.4.2. Never rooted, unlocked, etc. I have the adb stuff, but I haven't even attempted anything, because it seems so unstable. I don't want a partial flash to screw it up even worse. I feel slightly better knowing that someone else is dealing with exactly the same thing in a similar time frame, so maybe it is a software thing, not a totally dead unit.
Well I may have made some progress. Since the warrenty is up anyway, I decided to crack it open. I noticed the GPU was getting extremely hot for just sitting at the home screen. So I enabled developer options and turned on some monitoring options (the fact that it stayed on long enough to do this is a miracle in itself).
Right now I have some overlay monitoring on including cpu usage and gpu rendering (on screen as lines). I also checked the "stay awake" while charging option. It's been on about 2 minutes so far, although graphics performance is horrible atm. Almost like project butter is disabled and it's running at half power....that could just be the monitoring overlay though. We'll see what happens...
*Update*
It made it 21 minutes, but it did reboot again. On restart, the OS smoothness is back to normal, and it does seem like it goes longer stretches without restarting now, however the issue is obviously still there. I should add that the back cover is currently off. which is starting to make me think this has to do with cooling
9629464420
Okay....I just admitted defeat with this issue. Just ordered a replacement board for $30 because the resets are still happening. Upon reset, I can actually hear a part of the main board buzzing for about 5 seconds (not the speakers). Not to mention that prior to this issue, I was having a lot of wifi connectivity issues anyway. Hopefully the board arrives before my long bus ride to new york...
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Powergreb said:
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Click to expand...
Click to collapse
That is strange...I haven't had that kind of behavior on my Nexus 6-works without a problem-never freezes or reboots...now I know the Amazon app would do something to my Nexus 6 I don't know what but when I install it-my phone with reboot randomly or shut down...ever since I uninstalled it-no issues-for months.
Try running safe mode and see if it does it again-that way you will know if it is an app that's causing the issues. This is how it's done: http://www.greenbot.com/article/2923927/how-to-restart-your-android-phone-into-safe-mode.html
You can always try a factory reset as well....have you tried updating to the most recent factory image from Google?
Powergreb said:
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Click to expand...
Click to collapse
I've been experiencing the black screen freeze frequently since getting the phone only a couple days ago. No other lockups however. Also running pure stock.
I too have the same issue. Screen goes blank and lock ups. Also running pure edition...
Same. Interestingly, in my case, it seemed to happen most frequently when using Hangouts.
I have another post that describes random reboot and I believe they are related. Long story short. I believe either the factory reset + software update fixed it, or it's a hardware problem problem. While I wait for the replacement, I only had one random reboot. Of course the new phone is rock solid. It's only been a couple of days. I would have a few by now if I'm still on original phone _ original firmware.
Powergreb said:
I have another post that describes random reboot and I believe they are related. Long story short. I believe either the factory reset + software update fixed it, or it's a hardware problem problem. While I wait for the replacement, I only had one random reboot. Of course the new phone is rock solid. It's only been a couple of days. I would have a few by now if I'm still on original phone _ original firmware.
Click to expand...
Click to collapse
I'm having the same issue. So no random freeze leading to reboot with ur rma device?
Sent from my Nexus 6P using Tapatalk
What I'm trying to say is don't panic and RMA your device. Do a factory reset and make sure you're on the latest firmware. Mine was OK after the first self-reboot during setup after factory reset but has been good while waiting for the RMA to arrive. To answer your question, the new device has been perfect but it's only been 48 hours.
I am facing a similar issue with my Nexus 6P, can anyone please help me with it?
On any rom, whatsoever, I get reboot when I turn the Google Maps Navigation On.
After few minutes, phone just reboots
I havent yet tried stock, any idea how can I find the root cause? I have cleared data for maps, also I have tried to uninstall maps with TiBackup and installed fresh from Play Store
Powergreb said:
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Click to expand...
Click to collapse
Yup same stuff going on over here with mine. It locks up and reboots even after clearing cache and rebooting only a few hours earlier. Have done 2 factory resets and am on the latest OTA update. I also noticed that I have to clear the cached data every day, sometimes multiple times a day to keep device running smoothly. This really concerns me with a device that's less than 2 weeks old. I also have only a handful of basic apps( Fb, YouTube, Spotify). Really thinking about returning it. When the phone runs right its great, but all the issues make me nervous. Might be time for a Note 5? I am just getting used to this phone and would hate to leave it though. Interested to see if the first major marshmallow update fixes these problems.
Jcomstock said:
Yup same stuff going on over here with mine. It locks up and reboots even after clearing cache and rebooting only a few hours earlier. Have done 2 factory resets and am on the latest OTA update. I also noticed that I have to clear the cached data every day, sometimes multiple times a day to keep device running smoothly. This really concerns me with a device that's less than 2 weeks old. I also have only a handful of basic apps( Fb, YouTube, Spotify). Really thinking about returning it. When the phone runs right its great, but all the issues make me nervous. Might be time for a Note 5? I am just getting used to this phone and would hate to leave it though. Interested to see if the first major marshmallow update fixes these problems.
Click to expand...
Click to collapse
Mine actually had one random freeze and reboot after factory reset then nothing for 48 hours after that. Of course I rma'd mine and I'm glad I did. Screen is on the colder side with even volume speakers on the second unit. Sending my original one back.
Sent from my Nexus 6P using Tapatalk
I'm just about ready to RMA. I've tried factory resets, cache wipes and just recently updated to the latest stock MDB08M. It was fine for a day or two but now the lockups are increasing.
As others have said, by any other metric this is one of the best phones I've had. This freeze/reboot thing is getting annoying and even if it isn't happening to every user it's happening to enough to be of some concern.
I'm facing app closures, my gmail app keeps crashing, it happened on my graphite nexus 6p, and now same thing on my frosty 6p. Its not just gmail, it's also chrome now. Maybe i should have not restored from my previous device.
what's this?
I came to this thread expecting a lot more of a technical discussion (the site is called xda DEVELOPERS after all).. but instead all i see is "oh my phone is crashing.. i'm gonna RMA this sucks) posts.. moving on to android enthusiasts on stack exchange thank you very much
upgrading to 6.0.1 fixed it!
upgrading to android 6.0.1 fixed it!!
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.
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
waqar747 said:
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
Click to expand...
Click to collapse
Sounds like a bad flash. The new flash removed the issues, so you're good to go.
Guess what guys, the problem returned after about 3-4 weeks. Appeared randomly while using FB. Phone went into bootloop and overheating again, and even when it restarted properly, it would go into the same cycle when I started using apps like messaging, whatsapp and facebook.
I booted in recovery and cleared the cache after about 25 reboots. One thing I noted was that recovery initially showed an update running, which got stuck first, and then completed after another reboot and entering into recovery. Has been stable for the past 24 hours now, like it never happened. I can't figure out what the issue could be, since now I can do whatever I want and it won't overheat like before or reboot.
Feels like a software issue since it disappears like it was never there. Hardware rarely does that. Is there a possibility that storage of some sort is bad at some point, and when data is written over that point, the problem appears. I'm shooting in the dark but can't figure it out otherwise.
Yup.
Seems you have memory issues.
Go to Samsung service and replace memory chip.
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.