Many anticipated the roll out of Android 6.0.1 #Marshmallow update and #Samsung #GalaxyNote7 owners are among them. Android M is expected to bring new cool features as well as fix some issues that have been bugging owners for so long. The problem is, the update seems to cause another set of problems than fix old ones, which is very disappointing to owners that have been dying to get some support and help.

We have readers who contacted us about some issues with their Note 7s and the most common of all is that the device shuts down on its own and when the owner tries to turn it back on, it won’t. I will address this issue first so continue reading below to understand why it occurs and learn how to troubleshoot your device in case this occurs to you.

There are other problems I included and I ask you to go through each of them in case you have similar concerns and to make it easier for you, here’s a short list of the problems:

Galaxy Note 7 shutdown and won’t turn back on after Marshmallow update

Galaxy Note 7 is stuck on the logo after the Marshmallow update

Galaxy Note 7 keeps rebooting on its own after the Marshmallow update

For those who have other concerns with their Galaxy Note 7, make sure you visit our troubleshooting page as we have already addressed hundreds of issues before and after the Marshmallow update. Find issues that are similar or related to yours and use the solutions we suggested. Should you need more assistance, you can always contact us by completing our Android issues questionnaire. Make sure you include important information about the problem so we can help you better.

GALAXY Note 7 SHUTDOWN AND WON’T TURN BACK ON AFTER MARSHMALLOW UPDATE

Problem: Hello. I am hoping you guys can help me out with my problem. I have the Note 7 phone I bought last year. It has always been working so well and I never had any problems with it until recently when an update arrived. It wasn’t the first time I updated my phone and all other updates prior to it have been successful that’s why I was confident to download it, not that I have an option not to. Anyway, shortly after the download, the phone just shut off on its own and when I tried to turn it back on, it didn’t. Thinking the battery was drained, I put it on charge but no results. In fact, I left it plugged in for a couple of days now but the phone just won’t charge and won’t turn on. Is it time to buy a new phone already or is there something I can do about it? I hope you can shed some light to this problem. Thanks. — Jinky

Troubleshooting: Hi Jinky. It is possible that the recent major update caused this problem, after all, firmware updates may corrupt some caches and data that may result to unpredictable performance of your device. So, we’ll have to troubleshoot it so that we will know what really the problem is and that we can find a solution for it. To begin our troubleshooting, here’s what we need to do:

Step 1: Do the Forced Reboot procedure

The Forced Reboot procedure will rule out the possibility that your phone’s firmware crashed and that it prevented the device from powering on and charging.

Press and hold the Volume Down button and Power key together for 10 to 15 seconds. If there’s enough battery left to power up your phone, it should boot up normally provided that our suspicion on the system crash is true.

We often think the charging process is all about the hardware but the firmware also plays a big role in making sure current flows through the circuit and to the battery. It is also responsible in measuring up whether the battery is already full or still need to charge more.

Therefore, if the firmware crashed, it will prevent the phone from charging and that the Power switch may not be enough to power up the device.

Step 2: Plug in your phone to charge

Assuming your device didn’t respond to the Forced Reboot procedure you did in the first step, it’s possible your device doesn’t have enough battery to power up its components and load up all services and the firmware.

So, this time try to plug in your phone. I understand you already did try this but you haven’t done the first step yet. This time if the phone still won’t respond when plugged in, do the Forced Reboot procedure again while it’s charging. If the charging indicators won’t show up after this, then it’s possible the device has some hardware issues we don’t know about.

In this case, it’s better that you send the phone in for further checkup and repair. You may also try our Note 7 not charging troubleshooting guide to see if you can bring it up to charge.

On the other hand, if the phone did show the charging indicators (charging icon on the screen and LED light), leave it plugged in for another 10 minutes and attempt to turn it on normally.

You do this if your phone is still not responding after doing the second step but charges when plugged in. It’s possible some third-party apps are causing the problem and by doing this step, you’re putting the device in diagnostic mode wherein all pre-installed apps and services are loaded during startup. Here’s how you boot your Note 7 in safe mode:

Turn off your Galaxy S6.

Press and hold the Power key.

When ‘Samsung Galaxy S6 Edge’ appears, immediately release the Power key and then press and hold the Volume Down button.

Continue holding the Volume Down button until the phone finishes the restart.

When you see Safe Mode on the lower left corner of the screen, release the button.

If it booted up successfully, then it’s time you find the apps that cause the problem and disable or uninstall them. The challenging part of this procedure is actually finding the culprit. Start your search from the most recently installed apps. If you really don’t have a clue which apps are causing it, then I suggest you backup your data and then do the master reset.

However, if the phone can’t boot in safe mode as well, then try the next step.

Step 4: Boot your phone in recovery mode

Booting your Note 7 in recovery mode will power up all the components but won’t load the usual Android interface, services and apps. Assuming the problem is with the firmware, your device may be able to boot up in recovery mode and from there, you can do things that might just fix the problem for you like delete the system cache or do the factory reset.

The moment your device boots up in recovery mode, you can rest assured the hardware is fine and that the problem is with the firmware. So, in this case, I suggest you do delete the system cache first and attempt to reboot your device into standard mode:

Turn off your Galaxy Note 7.

Press and hold the following three buttons at the same time: Volume Up key, Home key, and Power key.

When the phone vibrates, release the Power key but continue to press and hold the Volume Up key and the Home key.

When the Android System Recovery screen appears, release the Volume Up and Home keys.

Press the Volume Down key to highlight ‘wipe cache partition.’

Press the Power key to select.

When the wipe cache partition is complete, ‘Reboot system now’ is highlighted.

Press the Power key to restart the device.

After wiping the cache partition and your phone still won’t boot up successfully, boot it in recovery mode again and this time choose ‘wipe data/factory reset’ to reset your phone. If all of these procedures failed, however, then it’s time you brought the phone to a shop an have it checked.

GALAXY Note 7 IS STUCK ON THE LOGO AFTER THE MARSHMALLOW UPDATE

Problem: I received the notification about an update. I really don’t have a choice but to download it so I did. It was successful or so I thought, then the phone rebooted after the installation of the new firmware. After that, it just won’t boot up to the home screen, instead, it’s stuck on the logo which doesn’t allow me to do anything except reboot it. Apparently, the new update ruined my phone and I just don’t know what to do about it. Can you guys help me out? Thanks. — Joel

Troubleshooting: Being stuck on the logo after a firmware update more often has something to do with corrupt system caches or data but since we don’t know which of them is the problem, let’s go after the things that don’t affect the performance that much–the system cache. So, in this case, this is what you’re going to do:

Wipe the cache partition to delete all caches by booting the phone into recovery mode. This might be just what you need to fix this problem but if it can’t, then the next step will.

Perform the master reset by booting the phone back in recovery mode. This will delete all your data and files so make sure you back them up before you do this.

If these procedures fail, then there’s one more thing to do, although it might be a bit complicated for you–manually flash or install the firmware. There is a popular flashing tool called Odin, which you can download free from the internet. Once you’ve downloaded it, download the firmware that’s currently on your phone and then run Odin from a Windows PC and start the flashing.

I am not going to put the step-by-step tutorial here because the process is very risky. So, if you can’t relate to what I’m saying here, most probably you haven’t done this before so I suggest find a technician who can help you with it. There’s a chance you will mess up your phone than fix the problem.

GALAXY Note 7 KEEPS REBOOTING ON ITS OWN AFTER THE MARSHMALLOW UPDATE

Problem: My Galaxy Note 7 updated recently to Marshmallow and it let me use it for a couple of days and then the problem started. I’m not doing anything with it and then it reboots on its own. It seems random but it keeps rebooting to the point that I may lose my messages when I’m composing when it reboots. I’m worried that my device may have been damaged. Please help me fix this problem so I can use my phone. — Julie

Troubleshooting: I understand that the problem started after the Marshmallow update, which actually points out that the firmware may have something to do with it. If we jump right into the pit headfirst thinking it’s the new firmware that has issues, then we may end up losing all your data and files without fixing the problem. Let’s to take is slow in troubleshooting this issue and let’s do some safe procedures first before jumping into some complicated steps. So, here’s what I think you should do:

Boot your device into safe mode first to see if it still reboots. If it does, then the problem could be in the firmware. However, if the problem is fixed, then find the app that’s causing the issue or backup your data and files and do the reset.

In case the problem still occurs in safe mode, try booting your device into recovery mode and then delete the system cache by choosing the option ‘wipe cache partition.’

If wiping the cache partition didn’t fix it, then you are obliged to do the reset to see if the problem remains and if so, the firmware may need to be reinstalled and if you don’t know how to do it, then let a tech do it for you.

I hope it helps.

We are always open to your problems, questions and suggestions, so feel free to contact us by filling up this form. This is a free service we offer and we won’t charge you a penny for it. But please note that we receive hundreds of emails every day and it’s impossible for us to respond to every single one of them.

But rest assured we read every message we receive. For those whom we’ve helped, please spread the word by sharing our posts to your friends or by simply liking our Facebook and Google+ page or follow us on Twitter.