Kindle Fire Root! [New][6.2.1][Windows/Mac/Linux]

After Amazon updated Kindle Fire to version 6.2.1, the older root method stopped working.  But no worries, there’s a new root method in town, this one is also very easy to do and works on Windows, Mac and Linux.

Update, for 6.2.2, please see new root method here.

For 6.3.1, see updated root method here.

Here’s a video tutorial for Windows you can watch while rooting:

And for Mac and Linux:

Step 1. Go to Settings->Device.

Step 2. Make sure your system version is 6.2.1 or later.  If not, press on “Update your Kindle” to update.

Step 3. Make sure “Allow Installation of Applications” is ON.

Step 4. Download and unzip to a folder.  My recommendation is to put it somewhere like C:\KindleFireRootNew.


Step 5. Connect your Kindle to your computer via a micro-USB cable.

For Windows, you will have to install drivers. (For Mac and Linux, skip this step)

Open up Device Manager and double-click on Kindle (with exclamation mark) to update driver.

You can find drivers in the KindleFireRootNew folder under usb_driver directory.

Step 6. For all Windows, Mac, and Linux, you need to copy the file adb_usb.ini inside the usb_driver folder into .android folder in your user directory.  If .android directory doesn’t exist, just make a new folder called .android.

Step 7. Next, you are going to copy the file kindlefireroot.apk file inside the KindleFireRootNew folder to the root directory of your Kindle Fire’s internal storage.


Step 8. Go to the Amazon App Store and install app called “ES File Explorer”.

Step 9. Find and install the kindlefireroot.apk file.

Step 10. Open the app after installing and choose “Root”.  This will temporarily root your Kindle Fire so you can install permanent root files/apps.

Step 11. Go open up a command prompt/terminal and browse to the KindleFireRootNew directory.

For Windows, if you extracted the files to c:\KindleFireRootNew, type the following:

cd \KindleFireRootNew

Step 12. Type the following:

For Windows:

adb root
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install Superuser.apk

For Mac:

./adb-mac root
./adb-mac remount
./adb-mac push su /system/xbin/su
./adb-mac shell chown 0.0 /system/xbin/su
./adb-mac shell chmod 06755 /system/xbin/su
./adb-mac install Superuser.apk

For Linux:

./adb-linux root
./adb-linux remount
./adb-linux push su /system/xbin/su
./adb-linux shell chown 0.0 /system/xbin/su
./adb-linux shell chmod 06755 /system/xbin/su
./adb-linux install Superuser.apk

For Linux, make sure you have super user access by typing “sudo -i” before typing in the commands.

This will “root” your Kindle Fire.  You can actually stop here but I recommend you to go to the next steps to install TWRP Recovery, which will allow you to install/backup/restore ROMs and also “unroot” your Kindle Fire when needed easily.

Step 13. Type the following:

For Windows:

adb shell
idme bootmode 4002

For Mac:

./adb-mac shell
idme bootmode 4002

For Linux:

./adb-linux shell
idme bootmode 4002

Step 14. Your Kindle Fire should reboot and hang on the Kindle Fire logo.  For Windows, you will have to re-install drivers, so do Step 5 again.  Mac and Linux users can skip this step.

Step 15. Next type:

For Windows:

fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img

For Mac:

./fastboot-mac -i 0x1949 boot twrp-blaze-2.0.0RC0.img

For Linux:

./fastboot-linux -i 0x1949 boot twrp-blaze-2.0.0RC0.img

This will install TWRP recovery on your Kindle Fire.  Wait until it finishes installing and select “Reboot”.

After rebooting, type the following:

For Windows:

fastboot -i 0×1949 oem idme bootmode 4000
fastboot reboot

For Mac:
./fastboot-mac -i 0×1949 oem idme bootmode 4000
./fastboot-mac reboot

For Linux:
./fastboot-linux -i 0×1949 oem idme bootmode 4000
./fastboot-linux reboot

Step 16. Your Kindle Fire should now reboot.  After rebooting, your Kindle Fire should be rooted, you can verify by running a rooted app like I did below:

Also, you can now access TWRP Recovery anytime by rebooting then holding Power button when the option screen comes up.

Having trouble?

I highly suggest you to watch the tutorial videos I made before trying to root your Kindle Fire in the beginning of this post.

Huge credits to user Jcase at XDA and Team Win for their TWRP Recovery.

Want to stay updated on latest Kindle Fire Root news?
Sign up for our Kindle Fire Root Newsletter here so you don't miss a single tip and get personal help via e-mail!
First time to rooting and custom ROMs? Please see our Kindle Fire FAQ FIRST!
Want to contact me?
Add me on:
Categories: Kindle Fire Root.

Recent Android News from

202 Responses to Kindle Fire Root! [New][6.2.1][Windows/Mac/Linux]

  1. Pingback: How to Root Kindle Fire! |

  2. Jason Kane says:

    my kindle is stuck at the Yellow triangle, When entering CMD fastboot -i 0×1949 oem idme bootmode 4000 i missed the space inbetween bootmode and 4000. it just froze, i cant get the driver to work again because the kindle will not do anything but the triangle. what can i do?

    • Jacob says:

      ive got the same problem =/

    • Fernando gonzalez says:

      The same thing happened to me. I kinda freaked, the way i fixed it was turning off the kindle fire and turning it back on.
      then on cmd I loaded the root folder again. cd \KindleFireRootNew
      and then I typed the last process again and it worked the second time
      >fastboot -i 0×1949 oem idme bootmode 4000
      Hopefully it works for you like it did me

      • Devon says:

        I did this and Command Prompt says “”

        • Devon says:

          I did this and Command Prompt says “Waiting for device”

          • Daniel says:

            The same thing here, but I got it to work. For some reason at this step sometimes the PC can’t find the Kindle. Just kill the command prompt box and go back to Start and then Search and type cmd. But before you type the line again, you have to move the driver one more time. Then it will recognize it when you hit enter. So repeat step five if step 15 fails. Then do the second half of step 15.

          • joebetta says:

            I got “waiting for device ” for the longest time and thought my kindle was bricked forever! I also tried fixing it by reloading the drivers, but my device was always undetectable!

            Fortunately, I was able to see how other Mac users solved the problem. First i turned my kindle off after connecting it with the micro usb cable. In terminal I went back to the place where the fastboot directory is with root control (sudo -i) . It looked like this:
            Xxxxx-macbook:kindlefirerootnew root# ./fastboot-mac -i 0×1949 reboot
            It stayed at rebooting for a long time, so I was scared it wouldn’t work, but then I turned the kindle off and in again one more time and BINGO! It rebooted and I got superuser! Hope this works for others too!

  3. kevin says:

    your tutorial worked awsome except at the end i forgot the 4000 and now im stuck with the fire sign and cant do anything any idea how to fix this or did really mess up.

  4. Jacob says:

    when i try to use to root it in the command prompt
    it says file not found

  5. Michel says:

    Everything worked fine, until I reached step 15
    ./fastboot-linux -i 0×1949 boot twrp-blaze-2.0.0RC0.img
    where I got:

    error: invalid vendor id ’0×1949′

    now Kindle is stuck on the start page

    • Santhosh Srinivasan says:

      exactly same problem for me too. Can’t get the TWRP image file to load.

      • Garrett says:

        same here…
        error: invalid vendor id ’0×1949′
        stuck on “Kindle Fire” screen.
        Any ideas?

        • Mike says:

          Same here :( Need help please

          • kindle_user says:

            I finally got mine to work:

            Windows XP could not load the driver (it did not even recognize it as a kindle). I had to use my Windows 7 machine to finish step 15.

            I did the following steps:
            1. loaded the compressed files onto the widows 7 machine and made sure to put the adb driver into my user folder.
            2. Connected my kindle to the computer
            3. Updated the driver per instructions above
            4. Opened Command Prompt and re ran step 15. I used a “x” not “*” or any other character.
            5. Manually powered down the kindle

            The kindle then restarted and was rooted.
            FYI it took about 2 min to restart.

        • jass says:

          try replacing the character “×” with the letter “x” on your keyboard in adb_usb.ini.

    • alexhoracio says:

      same here, what can I do?

  6. kevin says:

    mines says waiting on device

  7. kevin says:

    got mine to work ya

  8. Jay says:

    Same here. mine’s stuck on the start page too. Any resolution on this issue?

  9. medguru says:

    Everything worked fine, until I reached step 15
    ./fastboot-mac -i 0×1949 boot twrp-blaze-2.0.0RC0.img
    where I got:

    error: invalid vendor id ’0×1949′

    now Kindle is stuck on the start page “kindle fire”

    what to do? did i brick it?

    • Santhosh Srinivasan says:

      Do not copy paste 0×1949 from the website, but rather type it in terminal. I found out that’s what was causing the invalid vendor id error as when you copy paste the x is different from what you type in. It worked perfectly fine after this change.

      • medguru says:

        i quit the terminal and now the device is not recognized by my mac. I opened the terminal again and tried to do everything from the start.. when i get to ./adb-mac root i get an error: device not found

        I even tried the fastboot -i 0×1949 oem idme bootmode 4000 and i get command not found..

        i am just Stuck on KindleFire screen

        Any help is highly appreciated..Thank you

  10. NIck says:

    This is all well and good ,but as i am in Oz i have no access to amazon app store so i cant download the file manager. Any suggestions.
    Cheers Nick

    • alexhoracio says:

      send the file to your email, then download it from your kindle using the web browser, it worked for me.

    • Alan G says:

      Go to and create an account on your Kindle based on a US address and credit card (supplied) you cannot buy anything but you can download free apps. I’m in Canada, same problem.

    • Rodrigo Silv says:

      vc n precisa dele, joga o arquivo apk no kindle e abre ele pelo quickoffice que ja vem no kindle, explorar internal storage vc vai v o aplicativo lá e é só instalar

    • Daniel says:

      You can use the file browser in Quickoffice. Click the app and when it opens, click browse near the bottom. Find the app you want and tap it and install. I couldn’t access the Amazon market either, so I eventually found this internal browser and it works fine. Don’t open any of the stuff other than Quickoffice.

  11. attma92 says:

    FOR INVALID VENDOR ERROR, go back and manually type 0×1949, don’t just copy and paste.

    • medguru says:

      my device is now disconnected.. i tried to do everything from the start and when i reach ./adb-mac root , i get a response ” error: no device found”

      how do i do it? i have tried resetting using the power button – no help.. please advise

    • alexhoracio says:

      I did that and still got the same problem

    • ryan says:

      i had the same problem try entering ” x ” insted of ” * ” and i got mine to work

  12. Drew says:

    Well… I was good until step 15 part 2. Loaded everything fine, but is just eternally rebooting. If it is just rebooting, shouldn’t it be safe to manually hold down the power, then turn it on? I’m hesitant to do so because one of the executables is running the reboot, so I don’t want to interfere with any processes it is trying to do. There are now “unbrick/unroot” programs and instructions floating about that will essentially just reinstall stock firmware (software?), but I am unsure if one would be able to access the device through usb on the hazard looking screen. Oooh this is a pickle.

    • iDuck says:

      i got a bit further, but no further than this step (the eternally rebooting screen with a fire hazard icon on it and below “press power button for recovery”). it’s now stuck on this screen. is there a way out? note: i have disconnected the usb

      • iDUck says:

        i believe my Kindle fire is truly bricked. on Step 15 i typed “fastboot -i 0×1949 oem idme bootmode 4000″ on command line, it said “waiting for device” for a long time, and then the Hardware Manager appeared again, looking for the device driver. I tried re-installing driver for ?kindle, but windows won’t recognise the driver (adb_usb.ini) nor find its location. still stuck with the fire hazard icon logo. at least the computer recognises the kindle, but further than that, its stuck.

  13. Garrett says:

    After step 15 I got the, error: invalid vendor id ’0×1949′
    Now Kindle is stuck on the “Kindle Fire” screen and it doesn’t mount to my Mac. Tried a Hard Reset, but just keeps just showing the “Kindle Fire screen.

  14. chuck says:

    got to the last step and now the computer wont recognize the kindle. Any suggestions? Stuck on the loading page. thanks

  15. Fatih says:

    Hey, thanks for totarial i did mine and it works perfect. I advice to people who can not use amazon apps because of non Us users, you can use quickoffice the export apk files.
    I rooted but now i do not know how to install android market on my device, does anybody now it?

  16. Seh says:

    Iv followed your first steps for the root but when it comes to the part where I type ./adb-mac root it says it doesnt find my device. Help

  17. Michel says:

    well I made it worked after lots of retrying
    I let KF battery power deplete
    restarted the computer
    and retried with the same commands but typing the vendor ID (as suggested..thank you)
    and it works

    Thank you :)

    • Jay says:

      Hey Michel so did you start from the very beginning or which step did you restart from? Was your kindle charging while you were retyping everything? Also, how do you type the “x” in i 0×1949 what’s the shortcut for it? (sorry for the dumb question)

      • Michel says:

        I continued from step 15 part 1
        fastboot -i 0×1949 boot twrp-blaze-2.0.0RC0.img

        what I did first when it hung the first time was to disconnect it and wait until the charge was depleted. then recharge it. it did not work.
        I did it again and it did not work
        I restarted the computer and bingo…it worked

        Good luck

    • Kushtrim says:

      Please can you explain where to get vendor ID and where to change

  18. Joe Corporon says:

    When I bought my Kindle the other day all 8gb of space were available for apps or Amazon content. Then it updated and only 1.17gb were available for apps, with the rest reserved for Amazon content only. That sucks in my opinion. If I root my Kindle will I then be able to use all the free space for whatever I want, or will I still be stuck with the limits that went into effect on the last update?

    Also, is there a way to stop the automatic updates so the root doesn’t get wiped out in the next update?

    • Joe Corporon says:

      When I bought my Kindle the other day all 8gb of space were available for apps or Amazon content. Then it updated and only 1.17gb were available for apps, with the rest reserved for Amazon content only. That sucks in my opinion. If I root my Kindle will I then be able to use all the free space for whatever I want, or will I still be stuck with the limits that went into effect on the last update?

      Also, is there a way to stop the automatic updates so the root doesn’t get wiped out in the next update?

  19. Jay says:

    Went past step 15. Now it gets stuck on yellow triangle. Tried holding the power button, but just turns off. Any suggestions?

  20. medguru says:

    i quit the terminal and now the device is not recognized by my mac. I opened the terminal again and tried to do everything from the start.. when i get to ./adb-mac root i get an error: device not found

    I even tried the fastboot -i 0×1949 oem idme bootmode 4000 and i get command not found..

    i am just Stuck on KindleFire screen Any help is highly appreciated..Thank you

  21. Jay says:

    Everything worked fine until I got to this step fastboot -i 0×1949 oem idme bootmode 4000…now the command window just says “waiting on device”…I’m stuck here

    • Andrew J says:

      Here is the fix…I was able to sort it out.
      1. Reinstall/update drivers on the kindle in “my computer”
      2. Close/reopen the cmd prompt
      3. Type in cd /kindlefirerootnew
      4. Type in fastboot -i 0×1949 oem idme bootmode 4000

      • Mike says:

        Hi Andrew J,
        im having the problem my device is not being installed anymore after Step 15. The driver seems not to fit anymore?

        Ive red the comments very precise. No idea for that?

        • alexhoracio says:

          Same happened to me, windows doesn’t detect the kindle anymore so I can’t install the drivers as the tutorial shows, what can I do?

  22. Ryan Crabtree says:

    I got it to go through all the way until the final reboot. I did a hard reboot and it fired up but no triangle What’s the triangle? What do I do now?

  23. me says:

    Please Help!!!!!

    When i try to download ES file ….., i get a error “There was an error purchasing ES File Explorer. Please click here to add an address to your account (this will open your browser) and try again.”

    • Eva says:

      It’s because you need an Amazon account with a credit card number (even if you just download free apps). Try making one using “” It’s not real name or credit card numbers, it just fools Amazon into thinking it is real.

  24. Ferri says:

    Thanks! It finally worked. It scared me a little because the final rebooting took forever that I had to do it manually. And I kept seeing that yellow triangle. But gave it some time and everything started up as per normal :)

  25. Jason says:

    Yes, I am having the same problem where my mac no longer recognizes the kindle after it reboots to the kindle fire title screen. I have tried restarting the computer and the kindle and it doesn’t help. I am going to try running the battery down but this seems quite problematic. Would appreciate any ideas!

  26. geedoh says:

    Using a Mac, stuck on step 6. Where do i create the “.android” folder?

  27. przemcool says:

    For the guys with yellow triangle problem after step 15 (fastboot -i 0×1949 oem idme bootmode 4000 -vendor error)
    I menaged to turn my KF on. The whole process of rooting I did on my desktop computer with Win XP SP3.
    After step 15 my computer didn’t recognize my KF. I tried to continue rooting on my laptop with the same WIN XP SP3 – and the result was the same (vendor error). Then I remembered I had instaled on my old HDD WINDOWS 7. I changed drive, turned my computer on and when WIN 7 found new device I simply installed one – like in step 5. (vendor problem didn’t appear).
    I was glad, I could pass the rest steps :-). Good luck.
    (sorry for my poor english)

  28. Jack says:

    I don’t know what has gone wrong but step 1 – 13 went really smoothly and i had no problems, but when i came to step 14 that went fine but at step 15 the computer did not recognized the command and now my kindle is a brick and my computer only recognizes it as an unknown device and i can’t do anything about it.

    Any help on how i can recover it, Please.

  29. Pingback: rabble rabble rabble » Blog Archive » Customizing the Kindle Fire with 6.2.1

  30. Monkeygirl says:

    In step 5, my KF is categorized as “Portable Devices” instant of “Other Devices”. Not allow me to install the driver. Please help.

  31. Sam says:

    for those who stuck at step 15, where a triangle icon shown and never disappear no matter what you did,
    I have found the problem that makes this happened.
    Please try to reinstall the driver for your kindle fire, THE DRIVERS FILE IN STEP 5 IS USELESS at this point, right click the device shown up as kindle fire -> update driver -> choose manually -> ‘previous installed driver listing’ (or sth like this, i don’t know the exact name in english as currently im using a chinese version windows) -> ANDROID PHONE (sth like this again.. can’t remember exactly the name)
    then follow the steps where you stucked, DONE!
    HOPE THIS HELPS!!!!!!!!!!!!!!!!!!!!!!!

    • Mike says:

      it seems like i doesn`t have this previous file anymore. At least i can`t press this button.

      • Mike says:

        oh gosh now it just reboots every 2 sec with the triangle. If I cut the usb cable it just turns off.

        Is there a possibility to cancel this progress and maybe unroot all these?

        • alexhoracio says:

          after entering the last code (fastboot -i 0×1949 oem idme bootmode 4000) when it reboots. disconect the usb, connect the wall charger and power of your kindle, it worked for me.

          • Mike says:

            You also had these reboot every 3 seconds, and it worked?

            When i plug into electric socket it keeps restarting like hell.

  32. P says:

    I’m stuck at the Kindle Fire screen after failing at Step 15.

    What are my options now?

    • P says:

      I’ve been able to update my drivers but am now stuck. My windows machine does not recognize my Kindle because it’s in an infinite reboot.

      • Kike says:

        same problem here… did you find any solution?

        • Beau says:

          You guys find anything here? My Kindle is got stuck at the reboot after putting on the unrooting program. Now all I have is the yellow triangle screen and the computer will not recognize the Kindle anymore. The screen says to press power button for recovery but it won’t go into any menu, just frozen. I have to hold power button to get it to turn off.

  33. jetpilot2112 says:

    I’m stuck at an earlier stage than most… when I type “./adb-linux devices” i STILL get “no permissions” .. even with root access. WTF???

    • Milton says:

      I found the answer on another thread. you must run ./adb-linux kill-server then ./adb-linux start-server. I was having the same problem and it was nothing a little research couldn’t solve!

  34. Fanta says:

    Everything worked fine, until I reached step 15, For Windows:
    fastboot -i 0×1949 boot twrp-blaze-2.0.0RC0.img
    error: invalid vendor id ’0×1949′
    now Kindle is stuck on the start page

    Is there any solution??

    • Alan G says:

      I have exactly the same problem with my mac.
      …..Home$ ./fastboot-mac -i 0×1949 boot twrp-blaze-2.0.0RC0.img error: invalid vendor id ’0×1949′
      now the kindle is stuck on the start page.

  35. chris says:

    If your pc is having trouble recognizing the device, use SuperOneClick to force install the driver………Just google it, follow instructions to install it. Then connect your kindle, select Unroot, it will prompt to install the drive, say yes to that and the windows warning. Then continue with the process in cmd. Worked for me. Hope this helps

  36. Jackson says:

    y does this guy ignore step 6 in both videos? how can i create a “.android” folder on my mac? and where???

  37. Ali says:

    hi guys
    my kindle got stuck , and the computer doesn’t recognize the kindle anymore.
    Did anyone find a fix to this problem.

    • Beau says:

      I have the same problem. My Kindle is got stuck at the reboot after putting on the unrooting program. Now all I have is the yellow triangle screen and the computer will not recognize the Kindle anymore. The screen says to press power button for recovery but it won’t go into any menu, just frozen. I have to hold power button to get it to turn off. Were you able to find out anything with your problem?


  38. Pingback: Kindle Fire 6.2.1获取root权限的方法 | Inning In Chaos

  39. Devon says:

    I am still having problems with the first CMD command we have to do, the one with the driver install! I installed the driver and I can see it in Device Manager, but when I run the “adb root” command it says “error: device not found”??? Any thoughts on how to fix this?

  40. Rodrigo Silva says:

    i’m stuck at step 12, i list the devices, and none comes up so i can’t root… i’m doing it from a mac

  41. Eva says:

    Hey guys. I’m on a Mac. I get to step 11 where it says, “browse to the KindleFireRootNew directory.” I assume this means the directory on my computer and NOT the Kindle, correct? When I try to root adb-mac, it says the file isn’t found. Weird, because the file is in there. Anyone else having this problem?

  42. Terry says:

    I’m attempting to do this on a Mac. I’ve tried entering in ./adb-mac root but no devices are found…hm…any ideas? I tried the sudo -i command so I’m the root user…didn’t help, I’m still stuck. Thanks!

  43. Bayard stryker says:

    Got my mac to install step 15. Copy and paste ./fastboot-mac -i 0×1949 boot twrp-blaze-2.0.0RC0.img into the terminal. Use the backward arrows to go to “0×1949″ delete this and retype in manually. You should see “” in the terminal. I held down the power key for 12 seconds and turned it back on (still plugged in) then it installed.

  44. Zach says:

    Ahh! Everything worked fine until step 15. I c/p “./fastboot-mac -i 0*1949 boot twrp-blaze-2.0.0RC0.img” into the terminal and I get “-bash: ./fastboot-mac: No such file or directory”. Has anyone else had this problem??

    • Zach says:

      Meant to type “./fastboot-mac -i 0×1949 boot twrp-blaze-2.0.0RC0.img” with an x. And have tried retyping this portion. No luck.

  45. Jos eCua says:

    Thanks so much for taking the time in putting up this tutorial. I’m using a previously rooted kindle fire, but due to the 6.2.1 update my android market stopped working so i thought I’d try to re-root again. I seem to be stuck at step 14. And am unable to detect my kindle fire even after installing the drivers. So I am now unable to continue to the next steps and my kindle fire is stuck on the kindle logo screen. When I try install the drivers it seems to go smoothly and shows up in the device manager, however when in command prompt, and i type “adb devices” nothing shows up. Please help, I’ve tried installing the driver on different computers and. Hope you can help me through this problem or at least show me a way to revert my kindle back to its usable state. Thanks for your time man, hope to hear from you soon.

  46. Martin says:

    I got problem on Step 15
    fastboot -i 0×1949 oem idme bootmode 4000
    Command Prompt says “Waiting for device”

    My PC cannot detect my Kindle and hang on the first page.

    I tried
    1. Reboot my PC and KF and repeated to load the driver from my PC using WinXP. It still did not recognize it as a kindle.
    2. I changed to use Win7 another PC, same result

    My Kindle is stuck on the start page. Any solution to solve the problem?

  47. David says:

    I got mine rooted perfectly. My initial problem was that I could not create the folder .android in win 7. Had to get some info online, then create the folder by going to command prompt and typing mkdir .android. Then the device was visible to windows 7. Weird not being able to name a folder with leading dot (.) from GUI mode.
    Thanks for the Root instructions; you guys ROCK !!
    – David

  48. Paulo says:

    Martin i was using my old PC with XP and stop in the same place.
    Solution was other pc with Win7 booting KF until show kindle on device manager, installed drive to put Android Adb Interface, then wrote the 2 instructions below:

    fastboot -i 0×1949 oem idme bootmode 4000
    fastboot reboot

    All is ok now

  49. Tammy says:

    Using Windows 7 I successfully followed instructions up to 15 but now my computer does not recognize my Kindle (unknown device) and the kindle is performing infinite reboots! I tried the command ‘fastboot -i 0×1949 oem idme bootmode 4000′ which did nothing to help the issues. Could the author of this tutorial or someone who had the same problems please help me? My brand new Kindle Fire is completely dead right now…

    • Tammy says:

      additional info: I even connected Kindle Fire to another computer running Windows 7 and tried to update the drivers and now the 2nd computer is not recognizing the device…

  50. Paulo says:

    Tammy, same problem, but please read my above answer.
    The solution was boot the KF until show kindle on device manager, next put the drivers to stay Android Adb Interface and next on cmd line write the remaining instructions

    Hope this helps

  51. Tyler says:

    The file will NOT download. Is it still up and working for others?

  52. Martin says:

    Urgent Help! I tried many methods by connecting my stuck Fire to Window XP and 7, it was still not able to detect my kindle fire. My Kindle fire keeps on the page showing yellow triangle with a fire symbol inside the triangle. Also, the bottom of the screen shows “press power button for recovery”……I tried many times, but it was still fail. I am very upset on it……

    Wish can have a workable solution to solve it. Many thanks.

  53. Kenny Ngai says:

    Sorry, I have a question.
    When i type in “./adb-mac root”, it said that “error: device not found”,
    What can i do? Anything step i miss? Please help~ :P

  54. Daniel says:

    I tried to update the driver to Android ADB interface, but the computer responded with “driver not compatible with the device’. I am using Win Vista. Any solutions?

  55. ben says:

    cant install driver after step 15. now kindle is stuck on yellow triangle with fire…and the power button for recovery does nothing…i have tried using SuperOneClick but that doesnt work ..ive tried installing the usb driver so many different ways..and still nothing…now kindle is dead…unable to unroot it..

    does anyone have any way around this??

    • cplee70 says:

      The yellow triangle seems to be part of the boot up sequence now. When you see it, just wait awhile. The Kindle Fire word will appear soon enough and the device will proceed to boot up properly.


  56. Pingback: Unlocking the Fire « strablet

  57. Keith says:

    I was good until Step 15. Next type:

    For Windows:

    fastboot -i 0×1949 boot twrp-blaze-2.0.0RC0.img

    i then kept getting error message & have lost my commang post & kindle fire is stuck on screen & im not sure what to do now?

  58. Mahmood says:


    my KF hang on the KF logo and i can’t re-install drivers..i go to device manager but i don’t see KF drivers is unknown :( !!

  59. therinken says:

    I have a bricked kindle that is on a loop from attempting to install ICS 4.0 Launcher … without first rooting … so when i follow some of your steps for mac/linux i get “adbd cannot run as root in production builds” which i guess makes sense since i never installed the rooter … so, my question is if there is a way to install the .apk onto or into a bricked fire …..

  60. mark says:

    step 14 hangs on the yellow triangle with fire logo and wont go further to kindle fire logo… pressing the power button only reaches up to the yellow triangle , is there any way to recover from this?

    • DutchMark says:

      I had the same. I powered it down by holding the off button for a long time. Then waited a while and turned it on. After a while I got a primitive TWRP screen. I chose ‘reboot’ and after a while the Kindle started normally again.

      Good luck. Be patient.

  61. Miranda says:

    I first tried this on Windows, but my the PC couldn’t find the KF in the command prompt even though it showed up in devices under android devices AND portable storage. I figured I had a driver issue, so decided to try it out on Ubuntu/Linux. I got stuck on step 12 with the very first command. I get a “command not found message.” I know I am in the right directory, so what gives? I wonder if I am doing the sudo part incorrectly, I’ve tried using just sudo, and sudo i, but I get the same results. Any help would be much apreciated. Thanks!

  62. Elmer says:

    My install hung up toward the end when this line was ran, “fastboot -i 0×1949 boot twrp-blaze-2.0.0RC0.img”
    That small x between 0 and 1949 has to be deleted and a new X inserted.
    It also needs to be changed in this command also “fastboot -i 0×1949 oem idme bootmode 4000″
    Just delete the small x and re-type it again

  63. Miranda says:

    So…went back and tried it through windows again. Everything went pretty smoothly, but there were a few times when I panicked, thinking I had bricked my kindle.

    Every single time the device rebooted during the process (step 15 and on) I had to reinstall the drivers. However, I couldn’t choose the drivers through a driectory/folder. I had to install the driver by choosing from a list. So, if you get stuck and get a device not found message, try going into the device manager, rt click the unknown device (kindle) > Update Driver > choose from list > adb devices > adb composite device (pick the most recent one, I think it’s something like Hope this helps!

  64. Adam says:

    I was doing fine (I think). Typed in “fastbook reboot” and then got the yellow triangle. I’ve tried different suggestions of powering down. Tried to restrace my steps and try again, but I’m getting “error: device not found”. I’m working on a mac and can’t seem to get to TWRP recovery or anything. Just a yellow triangle. HELP!!!!

    • Adam says:

      I tried going back through the steps but Terminal keeps saying “error: device not found”. When I run System Profiler on Mac it shows Kindle when connected and on. How do I get Terminal to recognize?

      • Adam says:

        Had my KF off. I entered “./fastboot-mac -i 0×1949 oem idme bootmode 4000″ and got “Error: could not get pipe properties”. Then “”. I powered on the KF. Same error popped up a couple of times, but eventually “… Okay” came up. Entered “./fastboot-mac -i0x1949 reboot”. I got “usage: fastboot [ ] ” with lists of options. I typed “reboot”. But got “Operation not permitted”. I’m stuck.

  65. George says:

    I am at step 15 and every time i type in the command it get : cannot load ‘twrp-blaze-2.0.0RC0.img’, help me i have no idea what to do.

  66. Eric says:

    ATTENTION ROOTERS :: It’s extremely likely the majority of you will never use the TWRP recovery program so do yourselves a favor and stop after Step 12. If you’ve watched the videos and followed the steps (and whatever corrections have appeared previously in this thread) your KF will be rooted after Step 12 and you’re good to go. If you don’t know what TWRP is or what it’s good for—Don’t bother installing it and save yourselves the grief that seems to be plaguing everyone from Steps 13 onward. All you really need/want is a rooted KF. Skip the recovery. You won’t know the difference and you’ll be much happier for it. Good luck.

  67. Elmer says:

    Better put that ROOT on hold for the time being.
    I see Kindle just upgraded to 6.2.2 and that wipes ROOT out.

  68. Giorgi Kandelaki says:

    It seems after upgrade to 6.2.2, root does not work again.
    After installing and running kindlefireroot.apk, at Step 12. When I run
    ./adb-mac root
    it says
    adbd cannot run as root in production builds
    Looks like BurritoRoot application (kindlefireroot.apk) didn’t have effect any more.
    Or may be I am doing something wrong? But I think I followed instructions carefully.

    By the way, can I somehow disable automatic updates of my KF? It’s kind of annoying, rooting Kindle every time it upgrades.

    • Alex says:

      I ran into the same problem, then l checked out the comments and got intimidated to go on worried that my KF would be bricked. A response/solution to this problem would be greatly appreciated!

  69. ben says:

    i typed in chmod 755 * on my mac. and that worked fine. but then in the next step where i placed “mac” in for “linux”, and entered. it something about unkown command or file not found

  70. Elmer says:

    I rooted my Kindle Fire, with 6.2.2 update, without any problems at all. Hopefully no more updates for a while.

  71. john says:

    have trouble getting past command: adb root –> comes back with:

    adbd cannot run as root in production builds

    any idea on a work around or if im doing anything wrong using 6.2.2 and windows vista

  72. john says:

    having same issue let me know of work around plz thank you

  73. Sean says:

    Cannot get step 12 to work. “push su…” continuously fails. Also, typing ./adb-mac or just ./adb doesn’t work, but typing adb without the leading ./ or trailing -mac works. I am on a Macbook Pro. Any help would be much appreciated, I would really love to actually use my Kindle Fire. The only internet I have easy access to is a tether from my phone, & Fire doesn’t support ad-hoc without rooting. I am also very tired of apps that DO NOT NEED an internet connection force-closing with a message about needing an internet connection.
    Amazon, you suck.

    • Suresh Karuppannan says:

      Don’t use -mac commands. Instead if you already have android sdk, go to platform-tools directory and use that adb command(If you already have android SDK setup). It worked for me !!

      sMac:platform-tools suresh$ ./adb root
      sMac:platform-tools suresh$ ./adb remount
      sMac:platform-tools suresh$ ./adb push ~/Downloads/KindleFireRootNew/su /system/xbin/su
      sMac:platform-tools suresh$ ./adb shell chown 0.0 /system/xbin/su
      sMac:platform-tools suresh$ ./adb shell chmod 06755 /system/xbin/su
      sMac:platform-tools suresh$ ./adb install ~/Downloads/KindleFireRootNew/Superuser.apk

      • Sean says:

        Thank you Suresh! At first I thought it wouldn’t work, but I copied & pasted your instructions, & realized I was missing a space between some of the commands.
        Now my Fire is worth something! Thank you all!

        Does anybody know what stops working when the FIre is rooted? I’ve read that the instant video quits working, but can you still download books? My internet is too slow for videos anyways, so I don’t even care about that part.

  74. Suresh Karuppannan says:

    Hey thanks man.. It worked very well for me :D !! Initially I too got stuck up on yellow triangle problem. I used my Macbook. Then I restarted the KF manually then long pressed the power button. It put me on TWRP app. Then went to Reboot and selected PowerOff. After switching on KF, now it starts normally and my macbook detects very well !!

  75. Elmer says:

    To Re-Root your KF after upgrading too 6.2.2
    Search and find BurritoRoot2.Bin on the internet.
    Make sure your KF has the Android driver and do this….it worked for me

    1 adb push BurritoRoot2.bin /data/local/
    2 adb shell chmod 777 /data/local/BurritoRoot2.bin
    3 adb shell /data/local/BurritoRoot2.bin
    4 adb root
    5 adb shell id
    if uid = 0 continue, if not start over
    6 adb remount
    7 adb push su /system/xbin/su
    8 adb shell chown 0.0 /system/xbin/su
    9 adb shell chmod 06755 /system/xbin/su
    10 adb remount
    11 adb install Superuser.apk (skip this step if its already installed)

  76. joncdel says:

    After rooting my device, my battery icon has a question mark in the center. When I check the status under “device” it shows 0% and also the power light does not light up when it charges. Anyone else have this issue and have a fix? Would it work to select “return to Factory Settings” under settings or to reinstall the 6.2.2. update? Any help would be awesome! Thanks!

    • joncdel says:

      I tried to restore it to factory settings, both by navigating to “device” and by copying the 6.2.2. file from Amazon’s site, but when tap on it, I get a message that the battery has to be at 40% to install. But even after having it plugged in to the charger all night, the battery level is still showing 0%. I’ve tried to reroot and the AndroidPolice / Rootzwiki app (I think it was BurritoRoot2 or 3…not sure… I’ve become disoriented in this process) said that it was rooted. I’m really not sure where to go from here. (I contacted Amazon customer service and explained the battery issue, but since it was rooted, can’t get a replacement.)

      Any advice that can be given would be great! Thanks in advance!

    • joncdel says:

      When I tried to install TWRP, it ran to the point where it was activating Fastboot (4002) and here is what is what it says (between the @@@@@):

      write 4002 to offset 0×1000
      The Kindle has been told to reboot in Fastboot mode.

      downloading ‘boot.img’ … FAILED (data transfer failure (unknown error))
      finished. total time: 2.109s

      Then “Read me”
      If we get stuck here a long time, check the ADB drivers in windows.
      Fastboot uses a different device than ADB, so make sure it is installed as an ADB device. If you see “kindle” in device manager, you need to install the drivers. You can also try running install_drivers.bat in the drivers folder.

      Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
      Do NOT touch the kindle at all if we are stuck.
      Setting Normal Bootmode.

      Please wait..
      *daemon not running. starting it now*
      *daemon started successfully*
      *daemon not running. starting it now*

      Now on my Kindle, the Kindle Fire screen appears for about 2 seconds then goes black for about 2 seconds. The power light blinks too and is on when the screen show “kindle fire”.

      Is there any hope of a next step or have I destroyed the device?

      • Elmer says:

        The first time I used SuperOneCl;ick, my KF froze and nothing showed even when I connected the USB cable. I went back to Device Manager and made sure the Android Drivers was installed. When you get to selecting the driver make sure you select the 2nd option down. Until then mine just said Kindle with a ? mark. By selecting the correct driver again, it all came back to life.

        • joncdel says:

          Unfortunately, my kindle power up far enough for the computer to know that something is connected by USB. The Kindle screen just blinks the “kindle fire” screen that appears when starting it up, then it goes blank, so I’m not able to even get the Kindle with a ? in Device Manager. Any other thoughts? (Thanks for replying Elmer!)

          • joncdel says:

            sorry for the typo…meant to say “…my kindle won’t power up…”

          • Elmer says:

            When my KF crashed, sometimes it showed the Kindle in the Device Manage and sometimes it didn’t. I would continue disconnecting from the PC until it finally showed as “Kindle?”. I then decided to re-apply the Android driver and it kept refusing until I chose 1. Update Drivers, 2. Browse my Computer for software, then 3. Let me chose . At that point I chose the folder under Android that says Extra/Google/usb_driver. That folder contains the file named “android_winusb_inf”. By installing that driver it worked for me. Hopefully it will be of some help. Keep in mind, my KF didn’t show in the DEVICE MANAGER until I disconnected a few times and then it started to show. At that point you might try what I mentioned above. THANKS!

        • joncdel says:

          I’ve made some progress! I have been able to get my Kindle fire to open to TWRP. But I can’t get the update file. When I connect my Kindle, the drive G: shows up under “My Computer” but when I click on it, it says “Please insert a disc into drive G:” I don’t know how to get the file to my kindle so that I can select it under Install on TWRP.

          (Thanks for all your input! You’ve been really helpful!)

          • joncdel says:

            I have since been able to transfer the file to the Fire by using:

            C:\KindleADB>adb push /sdcard/

            On the Kindle, I tapped Install and choose the file ( then tap Flash, this is what it says:

            –Verify md5 for /sdcard/

            –No md5 file found, ignoring

            –Instal /sdcard/ …
            E: Cannot load volume /misc!
            E: failed to mount /sdcard (Invalid argument)
            E: Can’t mount /sdcard/
            E: failed to mount /sdcard (Invalid argument)

            Not sure where to go from here. :-\

  77. Colin says:

    Hi I have tried to Root the Kindle Fire following your steps. Having set the Kindle Fire for other apps, downloaded the software for both PC and Kindle, copied drivers and usb files accordingly. Run the ES explorer and installed kindlefireroot.apk selected agree, you rock, and root then exit. Unfortunately each time I get to the Command window step 1 and 2 change directory the run “abd root” I have the the result —
    *daemon not running. starting it now *
    *daemon started successfully *
    adbd cannot run as root in production builds

    Can anyone please help. What can I do /need to do to get past this point?


    • Elmer says:

      It appears your KF may still be listed as a Kindle under Device Manager. If so then update the driver that changes it to an Android. In my case that driver was C:\Android\extras\google\usb_drivers\android_winusb.inf
      Its only my guess, since I’m not seeing your device manager and based on the message it gave.

  78. hwealth says:

    the same question

    *daemon not running. starting it now *
    *daemon started successfully *
    adbd cannot run as root in production builds
    Can anyone please help ?


    • Quando says:

      Same problem, need help. I’m using Mac

      Quan:/ root# cd kindlefirerootnew
      Quan:kindlefirerootnew root# ./adb-mac devices
      List of devices attached
      5E60000600000001 device

      Quan:kindlefirerootnew root# ./adb-mac root
      adbd cannot run as root in production builds
      Quan:kindlefirerootnew root#

  79. Tom says:

    From reading online it looks like this version of root was disabled with the update to 6.2.2 can you do another tutorial for the 6.2.2 version or at least update the to contain burrito root 3?

    • Elmer says:

      After the 6.2.2 update I rooted with Burrito Root 2. Burrito Root 3 is available. DO a search, some sites do have it. I used the below commands from the CMD prompt.

      From the directory containing your files:
      adb kill-server
      adb devices

      1 adb push BurritoRoot2.bin /data/local/
      2 adb shell chmod 777 /data/local/BurritoRoot2.bin
      3 adb shell /data/local/BurritoRoot2.bin
      4 adb root
      5 adb shell id
      if uid = 0 continue, if not start over
      6 adb remount
      7 adb push su /system/xbin/su
      8 adb shell chown 0.0 /system/xbin/su
      9 adb shell chmod 06755 /system/xbin/su
      10 adb remount
      11 adb install Superuser.apk (skip this step if its already installed)

  80. rahul says:

    hey please tell me… i have to install android sdk on pc also????

    • Elmer says:

      Yes, DL and install in a folder. I installed all the files in a folder named Android and that way I could find it quick. As long as you know where the filers are located, you can go to the START, type CMD and then cd\, then “cd Android” and run your files.

      • rahul says:

        hey thanks elmer…..please tell me also any other source to get ES file explorer?…as i cant access the same through amazon…..i m living in uae….

  81. Filip says:

    Hello, every steps is OK, but steps 15-16. when i write this fastboot -i 0×1949 boot twrp-blaze-2.0.0RC0.img
    so the command line said waiting for davice…help me

  82. oh no says:

    i cant even download the first thing i think this thing sucked

  83. Pingback: kindle fire 进行时 » 鹰之家

  84. tarryn says:

    I have used the method – i had to stop prematurely, i am unable to access my kindle device on my pc, when i open my command prompt and type in the commands – i get a message saying that the device is not found – please help

  85. Maddi says:

    Help me please…
    I got stuck at Step 10. I opened BurritoRoot3, hit Install then Open. But a box came up that says, “Please run /data/local/tmp/BurritoRoot3.bin –root through abd to start the process? example: abd shell /data/local/tmp/BurritoRoot3.bin –root” The only option is to tap “exit.” That takes me back to the ES app.

  86. Moises Rivera says:

    Hi – Are you going to create a new video to root the 6.3.1 system version of the Kindle Fire?

  87. nick says:

    i tried to root mine
    now it wont go past the kindle logo screen
    what do i do
    im freakin out
    i think i messed the thing up to where it wont work anymore

    • nick says:

      i tried one other root than this and it went good for a while now when i turn it on it wont go past the kindle screen.
      i left it on all night one time and nothing
      i havent tried to unroot or anything cause i dont know that much on that. im scared if i do it it will mess it up.
      i was thinkin about sendin it in and gettin a new one
      ^^^^^^^^about that could they find out if i rooted it or not
      please reply i need help

      • admin says:

        Make sure you do ALL of Step 15, otherwise you will end up in the bootloop state. Just do Step 15 again.

  88. adam says:

    i lost the files to do this and im trying to do it all over again
    i did the driver thing back when it was a regular kindle fire
    the driver got lost and it wont recognize so i can fix it
    wat do i do

  89. Eric says:

    Hey Max, as long as you’re not vetting my posts, which are meant to help these guys by pointing them to XDA where people might actually help them, let’s talk plainly: Clearly me doing so has gotten you reengaged; so Yay for everybody, right? You didn’t publish me, which is fine, but at least you’re responding—somewhat—to these well meaning but clueless noobs. How about you actually go in here, clean up your video and instructions (which could stand some precision), update everything and stop the chain of chaos going on here. Reshoot the vid. Put clear, cogent instructions out. And add whatever useful stuff has come into the chain. OR, let people like me point them to XDA (or wherever) if that’s what they need. Believe me, I’d prefer that you took on the prospect of making this perfect than pointing them elsewhere. But right now, they’re thrashing around in good measure because your presentation up there is somewhat sloppy. Clean it up; clear it up. Do them all a favor. (Sorry if this seems at all dickish. I’m sure it must, but it’s not meant to be. You’re actually really aces for putting this up at all. All it needs is a good tightening and scrubbing.) Best wishes.

    • admin says:

      I will have an update real soon, I just been very busy with many devices. It would be easier if Amazon stopped their co(k-blocking. I believe this root method still works so that’s why I left it here but I will re-confirm this week.

  90. Eric says:

    Thanks for not merely writing me off as a dick and responding in such good will, Max. And I repeat what I wrote earlier: You’re aces for having posted this in the beginning at all. A big service to everyone out there. Thanks again. And good luck with it.

  91. Juan Pablo says:

    Hi, can I use the last video you make to root mi KF if my system version es 6.3.1??

    Thanks a lot!

  92. thaihammonds says:

    i dont know how to extract files from the mac computer . help O.o

  93. Dennis says:

    Got a 6.3.1 and got the same problem as other had mention here’s the error:

    I got stuck at Step 10. I opened BurritoRoot3, hit Install then Open. But a box came up that says, “Please run /data/local/tmp/BurritoRoot3.bin –root through abd to start the process? example: abd shell /data/local/tmp/BurritoRoot3.bin –root” The only option is to tap “exit.” That takes me back to the ES app.

    Do you have a fix for this?


  94. Brady says:

    Will this work on 6.3.1? I know this question was asked on June 6th, but no response yet. Let us all know. We are impatiently waiting. ;) Thanks again for all of your effort on this project.

  95. Cliff Wade says:

    Every time I try to run the kindlefireroot.apk from within the Kindle itself I get the following error and can’t for the life of me get past it.

    When I click on OPEN after I install it, this is what I get:


    Please run /data/local/tmp/BurritoRoot3.bin –rot through adb to start the process?
    example: adb shell /data/local/tmp/BurritoROot3.bin –root

    Then it gives me an option to EXIT and nothing else.

    I don’t get the little screen you get that has the option to “ROOT”.

    Can you PLEASE help me get past this. I’m trying to do this root method via Fedora 17, not that that should make any difference.

  96. aaron says:

    i keep getting stuck at burriot root 3 with an erro saying “pleaserun /data/local/tmp/ButtiotRoot3.bin –root through abd to start he process?” im not too tech savvy any sugggestions?

  97. Zobiesky says:

    Same problem:

    Please run /data/local/tmp/BurritoRoot3.bin –rot through adb to start the process?
    example: adb shell /data/local/tmp/BurritoROot3.bin –root

    I have 6.3.1 version, is there a procedure to root this version on linux?

  98. Pingback: How to Root Kindle Fire 6.3.1! |

  99. I am writing this from the perspective of being a long-time experienced Kindle user vs. someone brand new. From an overall perspective, considering the pricing of the Kindle with Special Offers (“KSO”) at $69 vs. higher amounts for the different flavors of Kindle available today, this one is a hands-down bargain. If you have wanted to get your kids a Kindle to encourage reading as well as sharing of books but hesitated because $139 to $400+ is a lot of money to risk with a child, maybe at $69 this is your price point.

  100. Hey! I simply wish to give an enormous thumbs up for
    the good information you’ve here on this post. I might
    be coming again to your blog for more soon.

  101. Whats up! I simply would like to give a huge thumbs up for the
    nice data you have got here on this post. I will
    probably be coming back to your weblog for extra soon.

  102. Anal says:

    Hello! I just want to give a huge thumbs up for the
    great information you have here on this post.
    I can be coming back to your blog for extra soon.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Related News and Resources