What to do with Samsung Galaxy A3 that went completely dead and won’t turn on (easy steps)
When a phone turns off by itself all of the sudden without any apparent cause or reason, there’s could be something wrong with the hardware. At least, that’s the first thing that comes to mind especially if it becomes completely dead and would no longer turn on or respond. However, I personally encountered issues wherein a phone stops responding but the problem is a result of a firmware crash. This could be just the case with some of our readers that owner Samsung Galaxy A3 units who reported similar symptoms.
In this post, I will walk you through in troubleshooting your phone and since it’s not the first time I encountered this issue, I already know a solution or two that could bring your phone back to life. That is if your phone doesn’t have any signs of physical and/or liquid damage because if there is, then that’s a different story. So, if you’re one of the owners of this device and are currently having similar issues, continue reading as this post may be able to help you, somehow.
Before anything else, if you have other issues with your device, try to browse through our troubleshooting page as we’ve already addressed several issues with this device. Odds are that we’ve already published a post that tackles similar problems. Try finding issues that have similar symptoms with what you currently have and feel free to use the solutions we’ve suggested. If they don’t work for you or if you still need our help, then fill up our questionnaire and hit submit to contact us.
How to fix Galaxy A3 that became completely dead and won’t turn on
While this may seem like a very serious problem because your phone is not responding already, most of the time it’s just an issue with the firmware. Well, at least, that’s we need to rule out before you decide to bring your phone to a local shop to have a technician take a look at it. With that said, here’s what I suggest you do about it:
First solution: Perform the Forced Restart
This is to address the possibility that this could be just another case of the firmware crash. If you’ve tried pulling out the battery of your basic phone before to make it respond again, well, that’s exactly the reason why you would need to do this only that your Galaxy A3 doesn’t have a removable battery. So, instead of pulling the battery out, you just need to do a combination to simulate battery pull…
- Press and hold the volume down and the power keys at the same time for 10 seconds or more.
If you can successfully do this, you may see your phone booting up normally and that could be the end of the problem. However, if your phone is still not responding even after doing this, then try doing the following:
- Press and hold the volume down button and don’t release it.
- Press and hold the Power key while holding down the volume down button.
- Keep both keys held down together for for 10 seconds or more.
In other words, you’re basically doing the first procedure only that you’re making sure the power key is pressed and held after the volume down button because doing it otherwise won’t give you the same result.
After making sure you’ve done everything correctly and your phone is still not responding, then try doing the next procedure.
RELATED POSTS:
- How to fix a Samsung Galaxy A3 that gets stuck in boot loop, won’t continue booting up [Troubleshooting Guide]
- How to fix your Samsung Galaxy A3 that entered bootloop and can’t start [Troubleshooting Guide]
- How to fix Samsung Galaxy A3 that has a black screen and won’t respond but soft buttons are lit [Troubleshooting Guide]
- “Unfortunately, Google Play Services has stopped” keeps popping up on Samsung Galaxy A3 [Troubleshooting Guide]
Second solution: Charge your phone and do the Forced Reboot again
One of the symptoms of a firmware crash is your phone won’t respond when connected to its charger. And while having a drained battery isn’t really a serious issue, there are times that if you allow your phone to run out of juice, some services and hardware components may crash and that could be the case here. To address it, here’s what you need to do:
- Plug the charger to a working AC outlet. Use a wired charger for this.
- Using the original cable, connect your phone to its charger.
- Regardless whether your Galaxy S9 shows the charging signs or not, leave it connected to its charger for 10 minutes.
- Now, press and hold the Volume Down button and don’t release it.
- While holding it down, press and hold the Power key.
- Keep both keys held down for 10 seconds or more.
If your phone indeed drained its battery and its firmware crashed, then it should be booting up now after you’ve done this procedure. However, if it remained unresponsive and you haven’t noticed any improvements, then it’s time to bring it back to the store or shop so that a technician can check it up for you.
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:
- “Unfortunately, Contacts has stopped” error keeps popping up on Samsung Galaxy A3 [Troubleshooting Guide]
- What to do with your Samsung Galaxy A3 (2017) that keeps showing “Unfortunately, Phone has stopped” error [Troubleshooting Guide]
- How to fix your Samsung Galaxy A3 (2017) with error “Unfortunately, Camera has stopped” [Troubleshooting Guide]
- What to do with your Samsung Galaxy A3 (2017) that keeps showing “Unfortunately, Phone has stopped” error [Troubleshooting Guide]
- “Unfortunately, Contacts has stopped” error keeps popping up on Samsung Galaxy A3 [Troubleshooting Guide]
Had the phone A03s about a year and this is the first time it shut down and wouldn’t come back on. Did the forced restart and all seems back to normal. Thank you very much