Fire Emblem Heroes: comprehensive list of issues (and possible fixes)

February 2nd, Nintendo finally launched Fire Emblem Heroes on Android and iOS, the very first Fire Emblem game on smart devices. Unfortunately, it looks like some issues came uninvited, and could be ruining the fun of heroes who just want to save the world. In this post, we are going to list the various issues encountered by players, as well as potential fixes.

NB: this page is still being updated with more details and/or fixes. If you see an issue is missing, or if you have a fix to share, make sure to let us know in the comments or on Twitter! If the fixes listed below doesn’t work for you, you might have to contact support. Don’t forget that Nintendo will release Software updates, so make sure you have the latest version if you’re having any trouble with the game.

If you want to report an issue, make sure to provide the following info: details on device (OS, specs), country, when the error occured, what you were doing or trying to do when the error occured, what you did to try and fix the issue (reboot device, reboot the game, etc.), and any other bit of info you think might help! Also, make sure to check out the official FAQ first! For more details about the game itself, this post is the one you’re looking for!

Update: the latest update for Fire Emblem Heroes is now available. Click here for more details! If this first udpate fixed the issues you were experiencing with the app, make sure to let us know in the comments!

NB: as of Ver. 1.5.0, Nintendo is completely blocking users with rooted device and/or non-stock ROM. Check out below for more details!

Error #1 – “A communications error has occured. Support Code: 803-0003)” [Added on February 2nd]

  • Devices impacted: all devices
  • Cause: servers overloaded due to launch
  • Fix: wait and try again

If you’re trying to download additional data, you might the following error: “A communications error has occured. Support Code: 803-0003)”. This is due to the servers being overloaded, and there’s unfortunately nothing that can be done at the moment… you just need to wait and try again later!

Error #2A – Cannot link Nintendo Account [Added on February 2nd]

  • Devices impacted: all devices
  • Cause: servers overloaded due to launch
  • Fix: wait and try again, or try another browser.

If you’re trying to link your Nintendo Account, you might encounter an error. This is due to the servers being overloaded, and there’s unfortunately nothing that can be done at the moment… you just need to wait and try again later, or try with a different browser.

Error #2B – Cannot link Nintendo Account [Added on February 2nd]

  • Devices impacted: all devices
  • Cause: unknown
  • Fix: none at the moment, try again later?

If you’re trying to link your Nintendo Account, you might encounter an error, with the browser redirecting you to a mysterious https://null/connect/1.0.0/authorize/ URL. Unfortunately, it’s not clear what’s causing this, but not all users are impacted. It looks like Nintendo might need to fix this in an upcoming update, or simply try again later.

Error #3 – Cannot get past main screen (Support Code: 803-3001 or 803-3101) [Added on February 2nd]

  • Devices impacted: Android-only?
  • Cause: unknown
  • Fix: unknown

This error seems to be due to security check, that devices with custom ROM and/or root will fail (but the exact cause remains unknown, as of writing).

A possible workaround consists in deleting the following file (you need to use a root browser to find the file, have access to root in the first place):

data/data/com.nintendo/zaba/shared_prefs/deviceAccount:.xml

Just make sure you know what you’re doing, and simply delete the app if you don’t. Make sure to also delete cache, just in case. Unfortunately, there does not seem to be a permanent workaround for now, as there’s no way to know if/when the error will pop up again after deleting the aforementionned file.

If you do use that workaround, make sure to link a Nintendo Account beforehand, or you will lose your progress!

See issue #11.

Error #4 – Game crashes at start-up [Added on February 2nd]

  • Devices impacted: Android and iOS
  • Cause: unknown
  • Fix: unknown

Unfortunately, Fire Emblem Heroes instantly crash at launch for some users (like this one). Cause for said crash is unknown at the moment, but a limited number of users seem impacted (so far).

On iOS, some users (including Mido) have reported that doing a factory restore fixed the issue: obviously, this is not something to take lightly, and you should try this possible solution only as your last resort (and of course, don’t forget to back up all your data beforehand). If you don’t feel confident, better to just wait and see if the first update for the game ends up fixing the issue or not.

Update: Nintendo is seemingly aware of the issue, and already working on a patch to fix it. It should be available sometime next week!

Error #5 – Download of the second batch of additional data fails at 89% [Added on February 3rd]

  • Devices impacted: Android and iOS
  • Cause: unknown
  • Fix: unknown

Some users are encountering issues when downloading the second batch of data, and more precisely when the download reaches 89%. Unfortunately, the cause of this issue is not known at the moment, but many users are reporting it so it’s likely Nintendo will push a fix pretty soon.

Error #6 – Unknown error (Support Code: 803-3021) [Added on February 5th]

  • Devices impacted: Android and iOS
  • Cause: unknown
  • Fix: unknown

Unfortunately, not much is known about this error, other than it pops up after downloading the extra data.

Error #7 – Issue with system clock (Support Code: 803-3009) [Added on February 7th]

  • Devices impacted: Android-only?
  • Cause: system clock
  • Fix: unknown

This issue seems to pop up when the system clock cannot be set automatically via the mobile network. If your device DOES have such an option, then make sure to set it so you get network-provided time.

If your device does not have such an option, it seems you are out of luck. Since the game has various time-sensitive events, and gameplay systems based on real-time systems, preventing users from cheating by modifying the clock on their device is pretty much a requirement for Nintendo.

Error #8 – No bonus for using the Bonus Characters in the Arena [Added on March 6th, Updated on March 9th]

  • Devices impacted: all
  • Cause: unknown
  • Fix: update to Ver. 1.1.1

This issue pops up if you quit the app mid-battle, in the Arena. Nintendo is aware of the issue, and is currently looking for the cause of the glitch, in order to fix it. In the mean time, make sure you do not quit the app mid-battle (unfortunately, you’re out of luck if the app crashes…). and has already released an update to fix it.

Error 9 – Cannot run the game because the User Agreement or Privacy Policy has changed (support code 804-3400) (added on March 23rd)

  • Devices impacted: all devices
  • Cause: new User Agreement / Privacy Policy
  • Fix: Click here to log to your Nintendo Account, and then accept the new User Agreement and/or the new Privacy Policy.

Error 10 – Purchased orb do not appear immediately in-game (added on March 31st)

  • Devices impacted: iOS only
  • Cause: unknown
  • Fix: none. Just wait a bit and try again later. Try restarting the app.

Right now, a minor issue is impacting the iOS version of Fire Emblem Heroes. When purchasing orbs, it may take a while for them to appear in-game: this is a known issue, and there is nothing wrong with your purchase (no need to repurchase anything). Just wait a little bit and try again later, after restarting the app.

Error 11 – App crashes at start-up (no error code) (added on July 6th)

  • Devices: Android
  • Cause: security check
  • Fix: none. You can install Magisk on your device to bypass security check, but do it at your own risk!

Since Ver. 1.5.0, Nintendo completely blocks access to rooted users, or those using non-stock ROM (those not provided by your device manufacturer). Unfortunately, there is absolutely no workaround, other than using a tool called Magisk. Unfortunately, that tool doesn’t work on an emulator, so if you’re using one to play Fire Emblem Heroes, you’re completely out of luck…

Error 12 – No log-in bonus (no error code) (added on July 6th)

  • Devices: all
  • Cause: unknown
  • Fix: download and install the latest update.

This issue has a workaround: quit and re-launch the app, or simply go back to the title screen. You should then get your Log-in bonus normally.

Error 12 – When a Hero with both Spd Feint and a Rally skill moves and uses that Rally skill on a Hero with stats that have already been boosted, the Hero with Spd Feint sometimes disappears and cannot be controlled anymore (no error code) (added on May 25th 2018)

  • Devices: all
  • Cause: unknown, but only occurs when you tap to move a Hero
  • Fix and workaround: to be fixed in the Ver. 2.6.0 update. In the mean time, you can drag your Hero instead of tapping to move them. Check out this post for more details!

twittergoogle_plusredditmail

Lite_Agent

Founder and main writer for Perfectly Nintendo. Tried really hard to find something funny and witty to put here, but had to admit defeat. Also known as Maintenance Guy by some. Twitter: @lite_agent

49 thoughts on “Fire Emblem Heroes: comprehensive list of issues (and possible fixes)

  • 2 February 2017 at 23 h 49 min
    Permalink

    To fix the 803-3001 error, you’ll need to delete some files in the shared_prefs folder of the game data. I just delete everything in it and redownload my Nintendo account-bound save data.
    Make sure your bind your save data to a NIntendo account to not lose it when you do that!!

    • 3 February 2017 at 1 h 30 min
      Permalink

      If you’re re-rolling or the link system isn’t working when you try ( as it has been doing for many people ) then doing this would result in the loss of that account, and potential 5 star units.

      • 3 February 2017 at 7 h 01 min
        Permalink

        Yeah, linking Nintendo Account first is highly recommended if you’ve already started playing. Will add that to the post.

      • 3 February 2017 at 21 h 17 min
        Permalink

        Yes, which is why I said to make sure to link your account before doing this. I lost my first account due to this error :(

    • 3 February 2017 at 7 h 01 min
      Permalink

      But doesn’t the error crop back up again after a while? It certainly has from what I’ve seen.

      • 3 February 2017 at 21 h 19 min
        Permalink

        It does. I haven’t found out what causes this error, but it happens like whenever my wifi connection resets. So I’ve been deleting the deviceAccount.xml file like 5-6 times per day.

        By the way, you don’t need to clear the cache, it’s something I saw in a video but it seems like it is absolutely not needed (and it’s dumb cause it delete all downloaded data. One single file deletion fixes the issue :)

        • 3 February 2017 at 23 h 36 min
          Permalink

          How do you delete that specific section of files on an Android? The only methods I can see are deleting the app entirely or deleting the cash. Or clearing the data, which is basically uninstalling.

          • 3 February 2017 at 23 h 42 min
            Permalink

            Do you have root access? If yes, use a root browser. If you don’t, then there’s not much you can do at the moment (and I don’t recommend rooting a device just for that).

        • 3 February 2017 at 23 h 40 min
          Permalink

          Deleting the cache really shouldn’t delete all downloaded data, just the cache (about 1.95MB on my device right now).

          About the wifi reset bit, it might be a clue. Finding more and more reports of non-root users being impacted. The more I learn about that error, the more puzzled I am, to be honest.

          • 4 February 2017 at 0 h 39 min
            Permalink

            I agree, but the one time I did it along with the file deletion, it removed everything. It’s probably an isolated incident since the other times it only cleared the actual cache.

            As for the accursed 3001 error, it’d be great if Nintendo would put up an error code guide. The file to delete only contains session information, so how could it get corrupted so easily…

        • 4 February 2017 at 19 h 33 min
          Permalink

          It looks like Nintendo is aware of the issue and already working on a fix. Hopefully, the update will be available on Monday.

          • 5 February 2017 at 5 h 24 min
            Permalink

            Good to know thanks.

  • 3 February 2017 at 23 h 44 min
    Permalink

    it keeps saying my phones clock is off and support code 803-3009

  • 3 February 2017 at 23 h 44 min
    Permalink

    Yup, been finding more and more reports of this. Looks like a rather widespread issue, that should hopefully been fixed soon. Not much to do at the moment.

  • 4 February 2017 at 5 h 59 min
    Permalink

    i get sent back to the home screen within 10secs or less or as soon as i hit start took me a few hrs to get pass the country and link account option before getting sent back to home menu :(

  • 4 February 2017 at 18 h 39 min
    Permalink

    My brother’s playing on his Lenovo tablet and he’s enjoying it. I’m playing on my Samsung phone and the game crashes every other turn in a battle, meaning that we can’t fight each other (the only reason I downloaded it)! Honestly, it takes me 10 minutes to complete what should be a 1 minute battle, because I constantly have to reload the game after the black crash screen fades.
    If the game doesn’t work on my phone, it shouldn’t show up on Google Play (like Pokemon Go, which also doesn’t work).
    Frustrating!!!

    • 4 February 2017 at 19 h 33 min
      Permalink

      It shows up in Google Play if you meet the system requirements, and the only real requirement is the OS version. I assume you’re running Android 4.2 or more recent, right?

      • 5 February 2017 at 11 h 22 min
        Permalink

        I have Android 5.1 and it’s saying that its not compatible with my device once I tried to delete it so I could do a reinstall, I had the error code 803-3001

        • 5 February 2017 at 14 h 11 min
          Permalink

          Rooted device, I assume? Play Store page will say device is incompatible if root is detected.

    • 5 February 2017 at 14 h 11 min
      Permalink

      First time I’m hearing about that one… when does it happen?

      • 6 February 2017 at 1 h 28 min
        Permalink

        Hello, i’m having the same sort of problem, people say its because we play on rooted phone or emulator, any idea of what is goin on?

      • 6 February 2017 at 2 h 29 min
        Permalink

        I have that same problem and my phone isn’t rooted. It’s a Samsung Galaxy Grand Prime SM-G531H and for me i can’t download it via the App Store. The error pops up after i download the update to play the game. After that it wont let me play the game. I’ve linked it to my Nintendo ID which is connected to my Google and I even tried to delete the cache and constantly redownload everything but still doesn’t work.

  • 7 February 2017 at 15 h 30 min
    Permalink

    Getting 803-3009 (system clock) error on android Samsung SM-T230. There is no option to set: Automatic time update in options as this device is WiFi only .. Any idea how to bypass this error?

    • 8 February 2017 at 5 h 40 min
      Permalink

      I have been trying to find a solve for this i use a Samsung Tab 7 But apparently there are no fixes for it

  • 8 February 2017 at 2 h 52 min
    Permalink

    I keep getting kicked out of fights on My tablet

    • 8 February 2017 at 12 h 27 min
      Permalink

      As in, kicked out to game’s main menu, or directly out of the app?

      • 9 February 2017 at 0 h 42 min
        Permalink

        Directly out of the app as in whenever I try to fight any units, the game turns black and I find myself on my home screen

        • 9 February 2017 at 16 h 48 min
          Permalink

          Looks like crashes caused by underpowered device. What are you using?

          • 9 February 2017 at 20 h 39 min
            Permalink

            LG-V400 tablet

          • 9 February 2017 at 20 h 55 min
            Permalink

            I’m using an LG-V400 tablet that I have owned for a year now

  • 10 February 2017 at 20 h 39 min
    Permalink

    Error 803-3009, my device does cannot set time based on mobile network, isn’t there any way around this?

    • 11 February 2017 at 17 h 41 min
      Permalink

      Unfortunately, there doesn’t seem to be. Have you tried contacting support to see what they had to say about that error?

  • 12 February 2017 at 22 h 15 min
    Permalink

    i played for a few days and linked my nintendo account, but then all, of a sudden two or three days ago i keep getting a communication error with support code 803-3100 and i cant find any information on it anywhere. it wont even load the start page now ( i would periodically get the error before but get to the start page, and it would go away if i cleared the cache from my apps page, not from in the game, or force stopped the game and restarted it) i play on a compatible android, have no clue if the error is even a server side error or a client side one, or what it could even be about. any one have any idea?

  • 22 February 2017 at 5 h 53 min
    Permalink

    I have an issue with crashing, but only in combat? I have an old iPhone 4 if that helps. Thank you for your assistance <3

    • 22 February 2017 at 13 h 45 min
      Permalink

      Does it happen all the time? Looks like crashes that happen when the device is not powerful enough (like mine). The iPhone 4 isn’t really the most recent phone out there, so wouldn’t surprise me.

  • 27 February 2017 at 14 h 12 min
    Permalink

    Incidentally if you get 803-3101 On Samsung Galaxy phones; you can just restart your phone and run the application again – likely its due to a error when the application is trying to patch itself.

  • 14 June 2017 at 18 h 49 min
    Permalink

    the second batch of files sometimes its 495 sometimes its 585 or withini that range and everytime i try it crashes…every..fucking….time…ya guy got any clues fer that?

    • 16 June 2017 at 8 h 15 min
      Permalink

      First time I’m hearing about that particular issue. Have you tried fully deleting + redownloading the app?

  • 31 May 2018 at 23 h 07 min
    Permalink

    Updated my LG phone with the new update for Fire Emblem that was supposed to fix error 803-3101 errors. Thing is, it caused it on my phone. Before this update, the game (for the most part) loaded fine. Only other thing I think it might be is due to me resetting my router last night (meaning the game thinks I’m offline when I’m not — wireless is set to be on via my phone, so when it showed up error wise… was at a loss, since there are no communication issues).

  • 12 June 2018 at 16 h 07 min
    Permalink

    i can’t find the reason or solution for this. when i’m on mobile data and i try to start the game, it always just… stays on the first loading screen, not even getting to the title screen. if i start the game with wifi and then continue to play with data it works perfectly, but if i start the game with data it stays like this. it very rarely decides to go past the screen into the game, but not in a reliable fashion. i dont understand what it has trouble loading, since my data works great.

  • 12 June 2018 at 17 h 10 min
    Permalink

    Is anyone still having the error 4 issue? I still have it, and It doesn’t seem like Nintendo fixed it at all…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.