How to reset your Samsung Galaxy A5 that no longer responds (easy steps)
We started receiving quite a lot of emails from our readers about an issue with the Samsung Galaxy A5. Many reported that their phones turned off by themselves and would no longer respond after that while others said their devices no longer power up after being left charging overnight. Based on the messages we received, many are really worried that this problem is due to an issue with the hardware which, if that’s the case, would need immediate attention from a technician.
Based on our experience, however, this kind of problem is basically just a minor issue with the firmware. We have already encountered several cases in the past wherein the phone simply just stopped working without apparent reason or cause. More often than not, the problem will be fixed by doing some troubleshooting procedures. In this post, I will walk you through in troubleshooting your device and I will share with you the solution we’ve always been using to fix this problem. So, if you’re one of the owners of the Galaxy A5 that no longer turns on or responds, continue reading as this post may help you one way or another.
For owners who are looking for a solution to a different problem, drop by our troubleshooting page for we have already addressed some of the most common problems with this device. Browse through the page to find issues that are similar with yours and use the solutions we suggested. If they don’t work or if you need further assistance don’t hesitate to contact us by filling up our Android issues questionnaire.
How to reset Galaxy A5 that won’t respond or turn on
You only need to do a couple of procedures to know if this problem is serious or not. During our troubleshooting, if the phone responds, then the problem isn’t serious and you can fix it on your own but after our troubleshooting and your phone is still dead and unresponsive, then there should be some wrong with its hardware and the problem could really be serious. With all that being said, here’s what I suggest you do about this problem.
First solution: Try doing the forced restart procedure
This the first thing you should and this is, actually, the most effective solution to this problem provided that the phone stopped responding due to a firmware crash or a system issue. Well, the most common reason why the phone isn’t responding all of the sudden without any apparent reason or cause is a crash. When it happens, your phone won’t respond to your commands, button presses and even charging. In short, you have a dead phone.
Now, if you’re familiar with the battery pull that we often do if our phones hang, this is the counterpart of that only and we do this to phones with non-removable batteries. In this case, all you have to do is this:
- Press and hold the volume down and power keys together for 10 seconds or more.
If the problem is indeed due to a crash, then your device should already be booting up by now but if it still not, then you may be doing this procedure incorrectly. Try this instead…
- Press and hold the volume down button first and don’t let it go.
- Press and hold the power key while holding down the volume down button.
- Keep both keys held down together for 10 seconds or more.
If your device is still not responding, try doing the same procedure a couple more times to be sure and after which if the problem persists, then move on to the next procedure.
RELEVANT POSTS:
- How to fix your Samsung Galaxy A5 that turned off on its own and won’t turn back on [Troubleshooting Guide]
- Samsung Galaxy A5 Screen Not Working After Getting Wet Issue & Other Related Problems
- What to do if your Samsung Galaxy A5 (2017) keeps showing the “moisture detected” warning [Troubleshooting Guide]
- How to fix your Samsung Galaxy A5 (2017) with “Unfortunately, the process com.android.phone has stopped” error [Troubleshooting Guide]
- How to fix your Samsung Galaxy A5 (2017) with “Unfortunately, the process com.android.phone has stopped” error [Troubleshooting Guide]
Second solution: Charge your phone and do the forced reboot again
If you’ve already tried charging your phone and it didn’t respond, then I understand that you may be hesitant to follow this procedure. This is your last resort. If the problem continues after doing this, then you have no other choice but to bring your phone back to the store or the shop so that a technician can check it for you. Before you do that, I hope you’d try this…
- Plug the charger to a working AC outlet.
- Using the original data cable, connect your phone to its charger.
- Regardless whether the phone shows the charging symbol or not, leave it connected to its charger for at least 10 minutes.
- Now, press and hold the Volume Down button and the Power key together for 10 seconds or more to force restart the phone.
If your Galaxy A5 is still not responding to this procedure, then have a technician check your phone for you because it might really be an issue with the hardware.
Connect with us
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.
Posts you may also like to check out:
- How to fix your Samsung Galaxy A5 (2017) that’s stuck on the boot screen [Troubleshooting Guide]
- How to fix your Samsung Galaxy A5 that turned off on its own and won’t turn back on [Troubleshooting Guide]
- What to do if your Samsung Galaxy A5 (2017) keeps showing the “moisture detected” warning [Troubleshooting Guide]
- How to fix Samsung Galaxy A5 that keeps showing “Unfortunately, Settings has stopped” error [Troubleshooting Guide]
- How to fix your Samsung Galaxy A5 (2017) with “Unfortunately, the process com.android.phone has stopped” error [Troubleshooting Guide]