Nokia Lumia 520 Error: Unable to find bootable option

Anonymous
2014-05-27T02:14:49+00:00

My Nokia Lumia 520 unexpectadly shut down and reebotted as i proceeded to pause my music. now the only reaction i reiceve from it is a black screen which says Error: Unable to find bootable option. Press any key to shut down.

if anyone has only proven solutions in fixing this issue, please let me know.

Thanks.

Windows for home | Other | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-12-30T12:28:20+00:00

Hi,

The "Unable to find bootable option" is comparable to a defective hard drive in a computer: It will still do the initial start-up and then be unable to do any more. The recovery tool still recognizes the phone when connected, but is unable to install the operating system in the phone when it comes to that. Again comparable to booting a PC on the install DVD and then be unable to complete the install.

The phone needs mechanical repair. If it is out of warranty, then is is also beyond economical repair, unfortunately.

If it is still in warranty, then please consult the point of sale.

--

Hans

Was this answer helpful?

100+ people found this answer helpful.
0 comments

146 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-03-18T09:43:56+00:00

    My "Unable to find a bootable option"-problem was solved, after I had tried to use all kinds of tools and softwares, by sending the phone to warranty repair shop, where they changed the whole motherboard of the device. I don't think those softwares help with this problem, if the motherboard has an electronic failure.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-03-17T23:16:50+00:00

    Hi Everyone, 

    I know this is an old post, but I had this exact issue on my Lumia 930 (Lumia ICON) if you're in the states, and my solution was as follows:

    -Whenever I plugged in my phone to the computer, the provided software by Microsoft was unable to detect my device, but my computer, while unable to access any files, did make its 'ding' signal, indicating that it sensed that a device was plugged into the computer.

    -So I had come this far. My phone was still in a constant loop displaying an enlarged Nokia Logo followed by that exact error message. Now What?

    -I saw online that the Microsoft Device Recovery Tool, NOT the Nokia Software Recovery Tool, allows you to mess around with the firmware on the device (not sure if I'm using the right terminology, and I apologize accordingly if I am not; however, just keep in mind that I do have a probable solution).

    -In order to bypass the whole 'plug in your device thing', I plugged a friend's phone into the computer (make sure it's the same model as your phone), which brought up the options bar in the program. I then was able to quickly (not sure if time matters here) switch from his phone back to my bricked phone (the program should remain unchanged)

    -At this point, I was able to choose the reinstall software option, which, after downloading a very large file (don't be weary of this process, it took me 25 minutes to download, and I'd like to think I have relatively good wifi). After the program had downloaded the file, it started the whole 'putting device in recovery mode', at which point my phone's screen flashed red with the Nokia Logo and a progress bar.

    -The program did it's magic, and low and behold, my previously bricked phone had been reset to factory settings, and turned on normally, no enlarged Nokia logo, and no error message.

    -I hope this fix works for you as it did for me.

    -Kevin

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-02-27T19:54:31+00:00

    My Nokia phone is saying unable to find bootable source

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more