Nokia 822 ERROR: Unable to find boot option

My 822 says "Error: Unable to find bootable option. Press any key to shut down"
This happened last night after installing a Verizon update.  The phone worked prior to the update.  The phone quit working solely because of the update from Verizon.  What can be done to fix the phone?

    bjurstrs,
I am so sorry to hear that your device is no longer working after the update. Thanks for trying a factory reset. We should look into replacement options. Please private message us so we can review your account.
LindseyT_VZW
Follow us on Twitter @VZWSupport.

Similar Messages

  • Nokia 822 ERROR: Unable to find bootable option.

    My 822 now says, "ERROR: Unable to find bootable option. Press any key to shut down."
    This occurred earlier today immediately upon installing a Verizon update. The phone worked perfectly before the update.
    What is going on? I certainly am not going to accept responsibility for this failure, or replacing this phone.
    Before you ask, the phone is in perfect condition otherwise. Never dropped. Never seen even a drop of water (or any other liquid).
    One thing peculiar I did notice was that the update took over an hour to download, which seems like quite a long time considering data transfer rates.
    So, what can be done?
    To recap:
    1) My phone worked perfectly. It was in perfect condition.
    2) An update was installed (which Verizon recommended (and I'd go as far as to say forced))
    3) Now the phone is completely inoperable, only giving the error message listed above.
    Help please?

    Hi Joel, the sim card has been removed and reinstalled multiple times with no effect. And yes, only the the original Verizon software was on the device. To be clear, the phone was attempting to install a Verizon-forced update when it died. I would rather have not had the update because the phone was working perfectly, but Verizon does not give the option to decline updates, only delay them. It should be noted that with the help of Verizon associate (Lovesa) the Nokia Software Recovery Tool was attempted, but even that did nothing. 
    I have now done at least 8 hours of research on this and it is obvious this is a widespread and known issue with the 822. There appears to be absolutely nothing that can be done to revive the phone at this point. After viewing literally hundreds of posts on the "unable to find bootable option" error no one has found a fix. This issue is well documented. 
    Why Verizon would force an update that ruins users phones is beyond me. And to take no responsibility is, in my view (and most likely the law's view), criminal. To be completely honest and forthright, I am so upset about this situation Verizon is now losing a 15 year loyal customer. 

  • My 822 now says, "ERROR: Unable to find bootable option. Press any key to shut down." Just happened after my phone froze. Everything I've searched says to replace the phone.  I have no phone in or out, no alarm....what is going on with this?  I see others

    My 822 now says, "ERROR: Unable to find bootable option. Press any key to shut down." Just happened after my phone froze. Everything I've searched says to replace the phone.  I have no phone in or out, no alarm....what is going on with this?  I see others have the same problem.

    Just got the same error message today.  My phone went to the black screen of death with the error message at the top.  Contacted Verizon via chat.  Was online for 1 hour and 15 minutes only to find out that nothing could be done which I could have told them based upon what I had read on this site.  Of course my phone is out of warranty since I have had it for 1 1/2 years and I am not eligible for an upgrade.  How convenient!  I was told to contact Nokia which I did and they gave me a download to try to reset everything.  It looked like it was working but after almost 3 hours it got to the end and nothing happened.  It just froze even though it said it was done.  I rebooted the phone and am back at the same black screen of death.  Guess I have to buy a used phone and then will have to reconsider whether or not to stay with Verizon going forward.  I have not had any issues with the phone in the past - keep it in an otter box, never dropped, never got wet, etc.  But all of a sudden it goes haywire like this that seems like either a hardware or software problem but something completely out of my control and all I get is sorry, you're out of warranty!

  • Nokia Lumia 822 ERROR: Unable to find a bootable option.

    My phone was working perfectly, and then all of a sudden it began to perform slowly.
    And so, I shut the phone off.
    Now I am getting an error message of "Unable to find a bootable option. Press any key to shut down."
    Why has this happened to my phone, and what is the remedy?

    Unfortunately the phone is DOA.  The memory chip that stores the boot information and OS went bad.  I'd suggest you contact Nokia support over VZW to get a replacement. Phone us - Nokia - USA

  • Nokia 822 error unable to reboot message to press any key to shut phone down.

    Windows Phone error unable to reboot message to press any key to shut phone down. No screen available to press, help.

        Thats definitely not good, respond. We are here to help get your phone working again. Have you tried a forced reboot by chance? Please hold down the Power keys for about 10 seconds. Do you recall anything that may have been processing when this occurred? Any new updates prior?

  • Nokia Lumia 620 "Error: Unable to find bootable op...

    Hello
    I'm in need of some help with my Nokia Lumia 620. It is 21 months old.  It was running on Lumia Denim (WindowsPhone8 (8.10.14219) according to the Hardware/Software Info on my account on windowsphone.com)
    Today the screen suddenly went black when I tried to open the email app and started to display the message "Error:  Unable to find bootable option. Press any key to shutdown"
    I have tried removing the battery and replacing it after ten mins.  I still get the error.
    I have tried removing the battery and sim card and replacing the battery after ten mins.  Still no joy.
    I have tried to perform a HARD reset. This doesn't work as as soon as the power button vibrates and I press the volume down button the phone shuts down, the exclamation mark never appears.
    Please could you point me in the right direction for solving this and getting my phone up and running

    Hi, deffers90. Welcome to Microsoft Mobile Community. Since all the possible troubleshooting steps didn't help, consider sending the phone to our Care Points for assessment as suggested by @93tid. Everything will be deleted once the phone undergoes repair. To look for the nearest Care Points within your area, see: Local support. Keep us posted.

  • Nokia Lumia 520 Error: Unable to find bootable opt...

    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.

    Hi, srikanth93. 
    If you are pertaining to Lumia phones that has the Windows Phone 8.1 software, yes, those are supported by the Nokia Software Recovery Tool. You can verify this info here: http://www.microsoft.com/en-ph/mobile/support/product/lumia520/faq/?action=singleTopic&topic=FA14298.... If the recovery tool is installed on your computer & it's still not recognizing your phone, try to uninstall it and install again. By the way, have you tried coordinating this with a different Nokia Care Point for a second opinion? 
    Note that the link will direct you to the local support page of the Philippines. If you're from a different location, go here: http://www.microsoft.com/en/mobile/support/locations/. 
    Best of luck and welcome to the Nokia Support Discussions. ;-)

  • Nokia lumia 520 error unable to find a bootable option

    pls help as lost all my apps and contacts it turned on fine then last week I should add so lol I installed a update however yesterday it wouldn't let me access any messages or calls just kept turning to home screen arrrrgghh xmas day lol then it just turned
    off and displayed this message at top off the screen{ERROR Unable to find a bootable option. Press A\any key to shut down all my contacts banking pdfs and photos were on this phone can a\ny one help me by telling me what to do................

    Unfortunately the phone is DOA.  The memory chip that stores the boot information and OS went bad.  I'd suggest you contact Nokia support over VZW to get a replacement. Phone us - Nokia - USA

  • [SOLVED] - Arch Boot Error: Unable to find Root Device /dev/sdb1

    I had Arch running perfectly using /dev/sdb1 (versus Disk Label or UUID) and decided to do a update.  After the Update I can't boot
    to a running system, and I get this error message:
    ERROR: Unable to find root device /dev/sdb1 
    You are being dropped into a recovery shell.
    Is there an easy way to convert to UUID or Disk Label since the latest Upgrade doesn't allow me to continue to use /dev/sdb1 ??
    I'd prefer not to have to rebuild both USB Flash Drives to get functional systems.
    Any Help is greatly appreciated.
    Suggestions?
    Larry
    Last edited by lkraemer (2012-02-21 15:14:02)

    Check your grub and read https://wiki.archlinux.org/index.php/UUID#By-uuid
    Edit:
    https://bbs.archlinux.org/viewtopic.php … 0#p1059160
    https://bbs.archlinux.org/viewtopic.php?pid=1059338
    https://bbs.archlinux.org/viewtopic.php?id=135288
    Last edited by karol (2012-02-21 01:07:21)

  • Error: "Unable to find a working IR device" in Windows Vista 64-bit, Audigy 4

    I have Audigy 4 Pro with the RM-500 remote that came with it.
    The remote is not working in Vista 64-bit (Enterprise).
    It is definitely not a hardware problem because everything works in Windows XP Professional SP3. When I dual boot into Vista, the remote doesn't control anything in Windows but the red light on the I/O external box is blinking so it's definitely receiving input.
    When I run "Entertainment Center Settings", I get the error "Unable to find a working IR device" and all the options are greyed out.
    <img title="err" width="300" style="width: 300px; height: 69px" src="http://img379.imageshack.us/img379/238/2278203yd.jpg" height="69" alt="err">
    <img width="459" title="err2" style="width: 459px; height: 393px" src="http://img379.imageshack.us/img379/388/2850392ep2.jpg" height="393" alt="err2">
    Has anyone gotten the remote working in Windows Vista 64-bit's? Thank you for your help.
    Regards,
    Lawrence

    _ I am having this exact same issue on vista business 32 bit. Everything else on the external box works perfectly fine, except the remote. The remote does work however with intelliremote, but I cannot justify paying the money for such simple functionality. Any fix on [email protected]

  • I'm unable to find configuration option under sett...

    Hi, I m unable to find configuration option under settings menu. please help. I am using Nokia X2 dual sim
    Moderator's Note: Post was moved and changed the title into a subject-related title. 

    Hi, what would you like to configure?

  • [SOLVED] ERROR: Unable to find root device '/dev/sda3'

    Earlier I updated the kernel to my arch system and found this error while trying to boot. I hate to post this because there are so many topics like it, but I've been looking for hours for a solution to this problem and can't find one.
    Here is the output:
    Booting 'Arch Linux'
    root (hd0,1)
    Filesystem type is ext2fs, partition type 0x83
    kernet /vmlinuz-linux root=/dev/sda3 ro
    [Linux-bzImage, setup=0x4200, size=0x2ff2d0]
    initrd /initrd @ 0xfd17000, 0x2c878c bytes]
    Probing EDD (edd=off to disable)... ok
    Decompressing Linux... Parsing ELF... done.
    Booting the kernel.
    :: Starting udevd...
    done.
    Waiting 10 seconds for device /dev/sda3 ...
    ERROR: device '/dev/sda3' not found. skipping fsck.
    ERROR: Unable to find root device '/dev/sda3'.
    You are being dropped to a recovery shell
    type 'exit' to try and continue booting
    sh: can't access tty; job control turned off
    My partition layout is like this:
    swap: /dev/sda1
    boot: /dev/sda2
    root: /dev/sda3
    extended: /dev/sda4
    home: /dev/sda5
    I have two hard drives, but i'm sure /dev/sda is the one with my OS.
    Here are some things I've tried:
    This was at the very bottom of the pacman wiki
    # mkdir /mnt/arch
    # mount /dev/sdaX /mnt/arch (your root partition)
    # cd /mnt/arch
    # mount -t proc proc proc/
    # mount -t sysfs sys sys/
    # mount -o bind /dev dev/
    # mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
    # chroot .
    # pacman -Syu udev mkinitcpio
    # mkinitcpio -p linux
    I've also tried performing the above, downgrading the kernel, updating my mirrorlist, reinstalling the kernel, and rebooting as mentioned here.
    I've alsa tried a few other things that I've read, but can no longer remember.
    Any help would be greatly appreciated! Thanks.
    Last edited by colton7909 (2012-05-25 02:09:36)

    Thank colton
    Same problem here, but on a mac book (not mine eyh )
    So, for those how have the problem (or need a live usb for mac or uefi systems),
    1) with a 32bits system
    - download gparted live cd
    - use it for the step 3
    2) with a 64bits system:
    - you need the gparted live cd too: mount it and copy the EFI directory somewhere; then umount it;
    - download a 64bits system (system rescue cd, as colton said is enough, follow the instructions for installation on their website first);
    - mount you live usb, install the 64bits system;
    - copy EFI system on the key
    - edit the grub.cfg in EFI/boot/ , add the following before the other entries:
    menuentry "System Rescue" {
    set gfxpayload=keep
    linux /syslinux/altker64 nomodeset efi
    initrd /syslinux/initram.igz
    3) repairing...
    - boot the broken computer with the live usb
    - mount the partition on which your system is (e.g. /dev/sda1 on /mnt)
    - chroot it, init the system as needed (mount /dev, /proc, etc. the easier way is using init scripts)
    % chroot /mnt /bin/bash
    % /etc/rc.sysinit
    % mkinitcpio -p linux

  • AutoPatch error: Unable to find job when restart

    OS is RHEL 5.7, and Oracle ebs R12.1.1 installed with patch applied 6078836, 11072566, 8576725...
    Problem summary: AutoPatch error:Unable to find job when restarting, and FND_INSTALL_PROCESSES table does not exist
    In the NLS patch update with 4 merged patches,
    while 16 workers are running to create rdf files as below, it made my Putty (v0.60) crashed. Below example is succeeded case taken from the log of one worker to let you know which task was on-going...
    Source: /d01/oracle/SID/apps/apps_st/appl/pa/12.0.0/reports/SF/PAXPCTCE.rdf
    Successfully generated report "PAXPCTCE.rdf".
    Generated 1 files successfully.
    Generated 0 files with non-fatal warnings.
    Generated 0 files with fatal errors.
    adrepgen is exiting with status 0
    End of adrepgen session
    Date/time is Wed Sep 07 2011 15:22:44
    Eventually, I had to run adctrl for changing job status <Failed>, and re-run adpatch. Then it ran several assigned jobs completed successfully.
    Then again, it made my Putty crash, and repeated few times like that.
    When there are 69 jobs remaining, autopatch error occurred.
    There are now 69 jobs remaining (current phase=A1001):
    0 running, 69 ready to run and 0 waiting.
    Reading completed jobs from restart file (if any).
    AutoPatch error:
    Unable to find job when restarting.
    When adctrl was checked to see worker status [1],
    Enter your choice [1] : 1
    Error: The FND_INSTALL_PROCESSES table does not exist.
    This table is used for communication with the
    worker processes, and if it does not exist, it
    means that the workers are not running,because
    the ad utility has not started them yet.
    How can this be resolved?
    Can I just re-run the patch as if it runs newly by ignoring the previous session of adpatch when asked the continuation of the previous session at the adpatch?
    Will this help?
    Thanks as always for the help.
    - SH

    Error: The FND_INSTALL_PROCESSES table does not exist.
    This table is used for communication with the
    worker processes, and if it does not exist, it
    means that the workers are not running,because
    the ad utility has not started them yet.
    How can this be resolved? If the table does not exist, then you cannot fix it.
    Can I just re-run the patch as if it runs newly by ignoring the previous session of adpatch when asked the continuation of the previous session at the adpatch?
    Will this help?Correct -- This is the only option you have.
    Thanks,
    Hussein

  • Graphics Error: Unable to find suitable font!

    I am trying to use the program rasmol (that displays molecules), and I get the error:
    Graphics Error: Unable to find suitable font!
    I installed rasmol by
    pacman -Sy rasmol
    today for version 2.7.3-2
    also did I do a system upgrade today:
    pacman -Suy
    the section "Files" in /etc/X11/xorg.conf contains:
           ModulePath   "/usr/lib/xorg/modules"
            RgbPath      "/usr/share/X11/rgb"
            FontPath     "/usr/share/fonts/misc"
            FontPath     "/usr/share/fonts/75dpi"
            FontPath     "/usr/share/fonts/100dpi"
            FontPath     "/usr/share/fonts/TTF"
            FontPath     "/usr/share/fonts/Type1"
            FontPath     "/usr/share/fonts/cyrillic"
            FontPath     "/usr/share/fonts/encodings"
            FontPath     "/usr/share/fonts/util"
    I have added all directories in /usr/share/fonts to be sure and restarted X.
    I tried installing all font packages that I could find, but the error is still the same:
    #pacman -Q | grep font
    font-bh-ttf 1.0.0-2
    fontcacheproto 0.1.2-1
    fontconfig 2.3.2-6
    fontsproto 2.0.2-1
    gsfonts 8.11-3
    libfontenc 1.0.2-1
    libxfont 1.1.0-1
    libxfontcache 1.0.2-1
    ttf-ms-fonts 1.3-8
    xorg-font-utils 1.0.1-1
    xorg-fonts-alias 1.0.1-1
    xorg-fonts-encodings 1.0.0-1
    xorg-fonts-misc 1.0.0-2
    #pacman -Q | grep ttf
    font-bh-ttf 1.0.0-2
    sdl_ttf 2.0.8-1
    ttf-bitstream-vera 1.10-4
    ttf-cheapskate 2.0-4
    ttf-isabella 1.003-2
    ttf-junicode 0.6.5pre20051126-2
    ttf-ms-fonts 1.3-8
    I removed the fonts.dir and fonts.scale in /usr/share/fonts and /usr/share/fonts/TTF and did mkfontscale and mkfontdir
    to replace them.
    restarting X and retrying to run rasmol still gives the same error.
    I have tried to search google for the error message but all I could find was the source code that probably produced the message:
    http://www.bernstein-plus-sons.com/soft … c/x11win.c
    and some redhat binary file that gives some fonts seemingly along with the error message:
    http://www.bernstein-plus-sons.com/cgi- … smol_16BIT
    ...Options^@Colours^@Display^@File^@Graphics Error: %s!^@-*-*-bold-o-normal-*-14-*^@-*-serf-bold-o-normal-*-14-*^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@-*-helvetica-bold-o-normal-*-14-*^@Unable to find suitable font^@%x %s^@Comm....
    which might be an indication for which fonts I need.
    Could anyone please give me some assistance to get the program working,
    perhaps by giving advise on how to install the abovementioned fonts
    or anything else that I have failed to do.
    I would really appreciate it , thanx

    Hey,
    i too get the same error that no suitable fonts could be found. I installed all the fonts mentioned in this thread. My Section "Files" looks like this:
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/artwiz-fonts"
    FontPath "/usr/share/fonts/speedo"
    FontPath "/usr/share/fonts/cyrillic"
    FontPath "/usr/share/fonts/encodings"
    FontPath "/usr/share/fonts/util
    EndSection
    Still the error occurs. Does somebody know how to fix this?
    greetings koelle

  • Error: Unable to find all subVIs from saved VIs.

    TestStand 2010 SP1, LabVIEW 2011, WinXP
    Trying to build a deployment in TestStand.
    During the build, I get the now-infamous popup:
    Title: "Save Modified VIs?"
    Text: "An error occured while trying to read the dependencies of your VIs; a possible cause for this problem is VIs not saved in the current version of LabVIEW. Would you like to save any modified VIs now?"
    I select "yes", and the build then fails with errors in the log pane of the "Build Status" window.  The error is:
    Error: Unable to find all subVIs from saved VIs, either a subVI is missing or the VI is not saved under the current LabVIEW version.
    The missing file path is:  etc, etc.
    I go to said missing path.  The VI is in fact present.  I open the VI and do "Save All", try again.  Same thing.  Then, I try a Mass Compile on the test VI directory.  Attempt to build again, same error.
    Note that I do call some VIs dynamically, but those are all present in my workspace, and are not found in this error.
    Is there a debugging option or log file or some kind of trace I can do to dig into this and find out the state of things causing the error?  Please help me out here.
    -Andy

    One quick way to narrow down the issue is to change your LabVIEW adapter to Run-Time engine and then try and run the sequence in the Sequence Editor.
    Also, triple check your search directories and make sure you're not pulling in VIs from an unexpected location.
    When you see that dialog it's already too late to save so trying to Save at that point never works.
    Another tip is to ignore which VIs it says are not saved in the current version and instead look at the subVIs that those VIs are calling. You can run into this if you have two subVIs loaded with the same name.
    CTA, CLA, MTFBWY

Maybe you are looking for