Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back from 1 to 10+ pages to re-sync the thread and this will then show the latest posts. Thanks, Mike.
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

[Flashing Help] Galaxy A5 Not Booting after a failed Odin flash

  • 25-11-2017 6:16pm
    #1
    sw33t_r3v3ng3
    Registered Users, Registered Users 2 Posts: 537 ✭✭✭


    I may have soft bricked my Galaxy A5. (2015 version)
    I flashed the stock 4.4.4 firmware through odin to get my phone back to stock, and all went well. I used the device for a few days and decided I wanted android 6.0.1.
    So i downloaded the firmware, connect to odin.. And here's where I messed up..
    I got everything set up in odin (including ticking the Auto Reboot feature, this will be important later), pressed the big start button and away she went.
    However, It wasn't all happy days. The flash failed, no big deal I thought. When Odin fails it usually just stops whatever it's doing within a few seconds. I waited 30 seconds before unplugging the device. When I disconnected it, It was still on download mode (The auto reboot feature was ticked if you remember from earlier - Shoul have rebooted when odin failed). Since It was in Download mode I tried restarting with the power button etc. It never booted.

    I assume the motherboard is dead, but I'm not sure.
    It wont boot into OS, Recovery or Download mode. The only thing it will do is vibrate if I hold down the power button for 10 seconds.

    Any ideas as to what's wrong with it?


Comments

  • #2
    DopeTech
    Registered Users, Registered Users 2 Posts: 6,897 ✭✭✭DopeTech


    sw33t_r3v3ng3 wrote: »
    I may have soft bricked my Galaxy A5. (2015 version)
    I flashed the stock 4.4.4 firmware through odin to get my phone back to stock, and all went well. I used the device for a few days and decided I wanted android 6.0.1.
    So i downloaded the firmware, connect to odin.. And here's where I messed up..
    I got everything set up in odin (including ticking the Auto Reboot feature, this will be important later), pressed the big start button and away she went.
    However, It wasn't all happy days. The flash failed, no big deal I thought. When Odin fails it usually just stops whatever it's doing within a few seconds. I waited 30 seconds before unplugging the device. When I disconnected it, It was still on download mode (The auto reboot feature was ticked if you remember from earlier - Shoul have rebooted when odin failed). Since It was in Download mode I tried restarting with the power button etc. It never booted.

    I assume the motherboard is dead, but I'm not sure.
    It wont boot into OS, Recovery or Download mode. The only thing it will do is vibrate if I hold down the power button for 10 seconds.

    Any ideas as to what's wrong with it?

    Use Samsung smart switch to put back on factory software. Used it a few times on the 2016 version. Should work with 2015 also.

    https://www.buymeacoffee.com/dopetech.ie



  • #3
    sw33t_r3v3ng3
    Registered Users, Registered Users 2 Posts: 537 ✭✭✭sw33t_r3v3ng3


    Sir Dosser wrote: »
    Use Samsung smart switch to put back on factory software. Used it a few times on the 2016 version. Should work with 2015 also.

    I will try that, but the phone isn't being recognized by my pc so it's unlikely it will fix it.


Advertisement