Kindle Fire Stuck at Boot Logo – Solved!

Brick1 copy

My Kindle Fire suddenly went into a loop during boot. It’s just showing the Kindle Fire logo (with animation) at start up and it just stays there. No home screen, no slide to unlock screen. My Kindle Fire unit was not rooted so I was not expecting anything like a boot loop. If anything messed up the firmware it should be the automatic update from Amazon. Kindle Fire Software Version 6.3 as of this writing.

Again my Kindle Fire was not rooted but I know the base system is Android 2.3 so I decided to do some tinkering about Android. I have some knowledge about Android due to past gadgets that I have rooted with the help of the guys from XDA. They have a dedicated section for Kindle Fire Android Development, good news (for my Kindle Fire)!


Android Debug Bridge is part of the Android SDK which is often used for manual rooting of Android devices. I have my Mac and Windows machine installed with ADB so I can switch from either system to connect to an Android device. In this case with my Kindle Fire, I was able to connect using ADB even it is stuck in the boot logo. That is a good sign.

Issuing a adb shell command gives a “$” prompts which indicates that I’m not rooted. I cannot do much if I’m not rooted so I tried the following methods to root my unit.

Methods I’ve Tried

Kindle Fire Utility

Kindle Fire Utility Screen

One of the popular Kindle tools in XDA is the Kindle Fire Utility. The tool is written using Windows batch file which means its a Windows only method. I’ve tried option 3 which is to “Install Permanent Root with Superuser”. No response from my Kindle Fire and the tool seems to be waiting for my Kindle Fire to respond as well. Hmmm, not working!


SuperOneClick Screen

I’ve tried SuperOneClick before to root my Nook Tablet. Since the SuperOneClick tool is a generic rooting tool, I thought I could try using it to root my Kindle Fire. I’ve clicked root, but again no response. SuperOneClick even went to “Not Responding”. Not working.

Kindle Unbrick Utility

I noticed the tools I’ve used cannot even go into the first step of rooting. Which means the loop happens even before the actual system is booted. I tried searching other tools and I found the Kindle Unbrick utility. I like the name, sounds very helpful in times of desperation.

Kindle Fire Unbrick Utility Screen

I’ve tried the “Stuck at Logo” option. No response again. Maybe I’m missing something, so I went digging further to the commands used by the tool. Found that it is using this command:

FilesandTools\adb shell idme bootmode 4000
FilesandTools\adb shell reboot

Since my Kindle Fire is having a boot loop, it just makes sense that I need to change a mode in the way it is booting. I need to change the boot method to go to fast boot.

Fastboot Mode

There is a post in XDA about Fastboot mode without rooting or cables which have the code needed to run to be able to fast boot to a Kindle Fire.

adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot

The problem is when I issue this command, I still get no response from my Kindle Fire. ADB is not responding as well. What to do now?

The Solution

Since there is a boot loop, I need to get ahead of the Kindle Fire boot step where I can issue the ADB commands before it goes into the loop. I restarted my Kindle Fire while it is connected to my machine through a USB. I left the ADB command prompt open and while the Kindle Fire is restarting I am issuing the adb push fbmode /data/local/tmp command. I got several errors that there was no device. On one of my attempts I was able to get a confirmation that the fbmode file was sent to the Kindle Fire (screen will show bytes transferred).

Lo and behold my Kindle Fire is now in the home screen! The key is to issue the adb push fbmode command before it gets into a boot loop.

This is technique is not documented to my knowledge until now. I’m blogging this technique as my contribution to the Android developers in XDA :) Hope this helps!



  1. darren says:

    how do you issue these commands? like where do you go to type them in and do them? i dont know exactly what happened to my kindle, but about halfway through the “option 2″ in rooting it, my cord disconnected (its a really sketchy cord lol) in “device manager” for windows, it shows up as unknown device, and in kindle fire utiliy, it says “please connect your kindle device”. help soon!!!!

  2. arrien says:

    I have the same question as the commentor above, and the same issue, stuck at boot screen. Where exactly are you imputing these commands, into a 3rd party application or program? or is it a windows command prompt you are imputing these commands into? there’s a bit of confusion on that part because you listed so many different programs you used trying to unbrick, lol.
    otherwise it seems to be a really great article and I’m glad you figured it out! mine has been in this state for close to 2 years now! lol

  3. Charles Meyer says:

    Is there any way you could provide me with step by step instructions on how to do this? I have tried everything I can possibly try to unbrick my rooted Kindle fire, but nothing has worked. This looks promising but it seems like I’m missing some steps? Is there any way you could help?

    • Noel Arlante says:

      Follow the solution i made in the “Solution” section, if you have Android Debug Bridge (adb) installed in your machine

      • Dan says:

        I tried the command several times with no success in finding the device. I typed the command C:\adb>adb push fbmode /data/local/tmp. Is this the correct path? If so, any other ideas to get me out of this damn bootloop? If not, could you direct me to the correct path. Thanks!

        • Tom M says:

          You need to have ADB installed on your PC!!! You cannot just type these commands into your dos-prompt!

          • ruth says:

            i had ADB installed and when i run ADB’s command prompt i pasted the command adb push fbmode /data/local/tmp and it came responded with “error: device ‘(null)’ not found “

          • Noel Arlante says:

            Try to execute the command several times while your Kindle Fire is restarting

  4. Mary says:

    Still have splash screen:(

    • komondor says:

      I had a similar issue I was able to use a clip to hold down the power button while it looped and after a day it actually came up on its own :)

  5. Dr.Gardivior says:

    Its The Goldfish.rc File Its Corrupt!!!

  6. 持っている人を

  7. 親愛なる管理者は、このブログの記事を提供するためのおかげで。私はそれは素晴らしいが見つかりました。私はこの偉大なウェブサイト(上の訪問者の一つであることをうれしく思います

  8. アイブ氏は、レイアウトだけでは、私は再びこのブログに来て作られた、と言うようになりました。しかし、今アイブはyouveは言うようになったものを読むことは、アイブ氏は、世界とそれを共有するようになりました!どのような鮮やかなリードバディを

  9. Santi says:

    When I do adb devices my kindle will show up, however it is listed as offline. Anything I can do?

  10. と私は排他的に非常にジレンマを表現になって、彼はしばしばあなたはどのあなたがすることをように努めて持っています。デザインの経験使用してこれはにもかかわらず鮮やかであることを起こる通常、どのような提案 I ‘M。私は単にこの時点で彼女の遭遇を示すために| ベースのWebインターネット俺の友達の私を送りました。 One 時間あなたのインターネット無視インターネットサイトをすなわち見つかりました自身節約とも求めてされます、それ本当に紙あなたの最新情報を読むためにについて自分自身を教育するために純粋には} {見つかったです!

  11. 。私はちょうどあなたのブログにつまずいたとアイブ氏は本当にあなたのブログの記事を閲覧楽しんでいると言うことを望みました。いずれにしても、私はあなたのRSSフィードを購読され、私はあなたがすぐに再度書き込みを願っています!

  12. このウェブサイトでは、過去にしばらく時間が保存されますが、私のコンピュータがクラッシュしました。私は以来、新しいものを得ている、それはこれを見つけるために私に時間がかかりました!私も実際にもテーマが好き。

  13. SanthanaKrishnan N says:

    I have amazon fire hdx 7. Recently when I updated the OS it stopped working. When I push the power button, “Kindle fire” in white colour text is what I get. And the screen stays there. When I went into recovery mode by pressing “Vol down + power” button, I got the following message

    Fire System Recovery
    Your Kindle doesn’t seem to be able to boot.
    Resetting your device to Factory defaults may
    help you to fix this issue.

    Volume up/down to move highlight;
    power button to select.

    Reboot your Kindle
    Reset to Factory Defaults

    E: failed to mount /cache (No such file or directory)
    E: can’t mount /cache/recovery/log
    E: can’t open /cache/recovery/log
    E: failed to mount /cache (No such file or directory)
    E: can’t mount /cache/recovery/last_log
    E: can’t open /cache/recovery/last_log
    E: failed to mount /cache (No such file or directory)
    E: can’t mount /cache/recovery/last_install
    E: can’t open /cache/recovery/last_install
    E: failed to mount /cache (No such file or directory)
    E: can’t mount /cache/recovery/dropbox_last_kmsg
    E: can’t open /cache/recovery/dropbox_last_kmsg
    E: can’t open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
    E: failed to mount /cache (No such file or directory)

    When I selected “Reset to Factory Defaults” and then “Yes — Erase everything”, a blank screen blinks and again “File system recovery” console comes with the same error message. Is there anyway to repair the tab?

  14. 私はあなたのウェブサイト上でのヒントが好き。私は絶対にここにあなたの意見に同意し、私はあなたが正しい軌道に乗っていることを感じています。私が持っているhuan​​hangrnは、これらの数日あなたのブログ上の記事のカップルを研究し、私が本当にブログのスタイルのように。私は私のお気に入りのブログのリストにそれをブックマークし、すぐに戻ってチェックされます。 Plsは同様に私のサイトをチェックアウトし、私はあなたの意見を教えてください。

Speak Your Mind