Dave Bagnall
Lurker
Hi all - new to the forum.
I have a galaxy A3 2016, it's about 6 months old. On xmas eve it just randomly rebooted and seemed it couldn't get past the boot screen - it was vibrating too, one vibrate then two vibrates repeating.
I booted it into recovery mode and saw the error DM-Verity verification failed in red - i did a factory reset from the RC mode menu and it seemed to work ok.
Then on Xmas day it rebooted again and started the vibrating thing, looking online i've found this is called a bootloop - it then just started again and booted to the lock screen, where it refused to accept my PIN number, although I was entering it correctly. I did another factory reset from recovery mode and then decided to flash the ROM using smart switch in case there was a corruption somewhere - this went ok and the phone worked ok for about a day, then suddenly it rebooted itself again, and refused to accept my pin again - i tried the wipe cache option and this cleared the error and my PIN could be entered OK.
At this point I am starting to think I have a hardware memory issue.
It then rebooted again and appeared dead - eventually I got it into recovery mode and in addition to the DM Verity message i have the message E: failed to mount /efs (Invalid Argument) - so I got it into download mode and tried to flash the rom again which seemed to go ok, but the phone boots into recovery mode only now - see attached photo.
Am I correct in assuming this is a hardware issue somewhere? Or is there something else I can try, without risking the warranty.
Any help appreciated.
I have a galaxy A3 2016, it's about 6 months old. On xmas eve it just randomly rebooted and seemed it couldn't get past the boot screen - it was vibrating too, one vibrate then two vibrates repeating.
I booted it into recovery mode and saw the error DM-Verity verification failed in red - i did a factory reset from the RC mode menu and it seemed to work ok.
Then on Xmas day it rebooted again and started the vibrating thing, looking online i've found this is called a bootloop - it then just started again and booted to the lock screen, where it refused to accept my PIN number, although I was entering it correctly. I did another factory reset from recovery mode and then decided to flash the ROM using smart switch in case there was a corruption somewhere - this went ok and the phone worked ok for about a day, then suddenly it rebooted itself again, and refused to accept my pin again - i tried the wipe cache option and this cleared the error and my PIN could be entered OK.
At this point I am starting to think I have a hardware memory issue.
It then rebooted again and appeared dead - eventually I got it into recovery mode and in addition to the DM Verity message i have the message E: failed to mount /efs (Invalid Argument) - so I got it into download mode and tried to flash the rom again which seemed to go ok, but the phone boots into recovery mode only now - see attached photo.
Am I correct in assuming this is a hardware issue somewhere? Or is there something else I can try, without risking the warranty.
Any help appreciated.
