How to manually upgrade or downgrade the Amazon Fire TV

fire-tv-upgrade-downgrade

The Fire TV update is still slowly making its way out to all the devices but, if you’re tired of waiting, here’s how to manually install the update. This same method also works for downgrading to a previous version of the Fire TV operating system. In order to manually upgrade or downgrade, you will need to be rooted with BusyBox installed.

Warning: Do not follow this guide if you have ClockworkMod Custom Recovery installed. If you want to install stock software on a Fire TV running ClockworkMod, you must revert back to stock recovery using this guide.
Update

10/10/2014 As of this week, some Fire TVs are starting to arrive with an updated recovery partition that is blocking downgrades. If you follow this guide and the downgrade fails during the installation, follow the new steps I just added to the bottom of this page.

  1. Download the firmware version you wish to install from the software page
  2. Rename the downloaded file to update.zip
  3. Connect to your Fire TV via ADB
  4. Run the command: adb shell
  5. Run the command: su
    (If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV, select Grant)
  6. Run the command: chmod 777 /cache
  7. Run the command: chmod 777 /cache/recovery
    Note: If you see a message saying “No such file or directory”, then run the following two commands:
    mkdir /cache/recovery
    chmod 777 /cache/recovery
  8. Run the command: cd /cache/recovery
  9. Run the command: echo --update_package=/cache/update.zip > command
  10. Run the command: exit
  11. Run the command (yes, again): exit
  12. Run the command: adb push update.zip /cache
    (This assumes the update.zip file you renamed in step 2 is in the same directory as adb, otherwise enter the full path to the file like adb push C:\full\path\to\update.zip /cache)
  13. Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery

At this point your fire TV should restart and begin installing whichever firmware version you selected.

 

If you get a “Failed to copy … No space left on device” error:
There is likely already a software image in your /cache partition taking up all the space. This partition is independent of the rest of your Fire TV storage space. That is why this can fill up while your Fire TV has plenty of space remaining. To fix this issue:

  1. Run the command: adb shell
  2. Run the command: su
  3. Run the command: rm -f /cache/*.bin
  4. Run the command: rm -f /cache/*.zip
  5. Run the command: exit
  6. Run the command (yes, again): exit
  7. Redo step 12 and 13 above.

 
If downgrading fails:
As of the beginning of October 2014, new Fire TVs have been arriving with a recovery partition that blocks downgrading. If you followed the steps above and your downgrade failed to install after your Fire TV rebooted, follow the steps below.

  1. Download the Fire TV Stock Recovery by Amazon file version 51.1.0 from AFTVnews.com/software
  2. Rename the stock recovery you just downloaded to: recovery.img
  3. Connect to your Fire TV using ADB
  4. Transfer the recovery file to your Fire TV’s /sdcard directory by running this command:
    adb push recovery.img /sdcard/
    (Note: This assumes the recovery.img file you renamed in the above step is in the same directory as ADB, otherwise enter the full path to the file like this:
    adb push C:\full\path\to\recovery.img /sdcard/
  5. Run the command: adb shell
  6. Run the command: su
    (Note: If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV and you need to select “Grant”)
  7. Run the command:
    dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

    clockworkmod-terminal-02

  8. Run the command: rm -f /cache/*.bin
  9. Run the command: rm -f /cache/*.zip
  10. Run the command: rm -f /cache/recovery/command
  11. Run the command: rm -f /sdcard/recovery.img
  12. Repeat the entire downgrade process in this guide.

ShareTweetShare+1

203 comments
  1. Nick says:

    When I try to pull the dropbox content, I get the following:

    Connecting to dl.dropboxusercontent.com (54.235.161.178:80)
    wget: not an http or ftp url: https://dl.dropboxusercontent.com/u/16913146/command

    • Dell says:

      my problem is that i was rooted before and i didn’t block to OTA update, so now i’m no longer rooted and can’t downgrade because of that, if reset to factory setting will it go back to old version
      ??

    • Vaibhav Ghodke says:

      I have the fire tv stick after reset to factory it wont go further the language selection screen i already done the factory reset by holding right button and the back button but always stuck on the language selection screen please do help

  2. BDWalker1 says:

    Nick,

    I had the same issue. I wound up just doing this instead:

    echo “-update_package=/cache/update.zip” > command

    It accomplished the same thing which is creating a file called “command” with the contents “-update_package=/cache/update.zip”

    Bruce

    • AFTVnews says:

      Bruce, that’s a much more elegant method! Thanks for the suggestion. I’ve updated the guide with your method.

      • cd says:

        Beware copy and pasting this command from this page. You’ll get opening and closing quote characters, which are great for a page, but not so much for a script. Your ftv will fail to update after adb rfeboot recovery. Simply omit the quotes in your adb shell:

        echo –-update_package=/cache/update.zip > command

        Other than this issue, the instructions are great. Thanks for putting this together!

  3. mdpauley says:

    I did it slightly different:

    1. Connect to your Fire TV using ADB
    2. Run the command: adb shell
    3. Run the command: su
    4. cd /cache
    5. Run the command: echo “–update_package=/cache/update.zip” > recovery/command
    6. Get the link to the firmware version you want and Run the command: wget firmware_link.bin -O update.zip
    7. Once the update.zip file has finished transferring to the Fire TV, run the command: reboot recovery

  4. Don_black says:

    I did everything but not sure if it is updating I cant type after I did the adb push command so I assuming it is updating. Did I do something wrong.

  5. Don_black says:

    nevermind it was just moving slow.

  6. Don_black says:

    I lost my root access

  7. EditorLiam says:

    I am in the ADB Shell but the SU command does not exist…
    /system/bin/sh: su: not found

    I am using the ADB from the ADT bundle at the OSX link above.

    I used this ADB previous to sideload XBMC.

  8. marcelo says:

    Run the command: chmod 777 /cache/recovery
    No such file o directory …..
    Help Please!

    • max says:

      I’m having the exact issue. Did you ever solve it?
      New device today, updates have been blocked via router since first boot, at version 51.1.0.1_user_510055620.

      Rooted, SU, Busybox all installed. I can chmod /cache and cd to it, but no cache/recovery exists. Rebooting via adb didn’t change the situation (not that I actually expected it). Any reason I shouldn’t just mkdir and proceed?

      • AFTVnews says:

        You probably should just create the directory with the command:
        mkdir /cache/recovery

        My guess is since you’ve never taken an official update, the directory has never been made.

        • max says:

          Just rebooted to 511070220 successfully after creating the directory and continuing the process (adb even stayed connected overnight). I may use linux as my primary OS, but fear of bricking these gadgets always makes me hesitate.

          Thinking through the actual commands, I assume that the /cache/recovery directory is where the old firmware gets backed up during the update process as a failsafe.

          Big thanks for breaking this all down Barney-style for the plebeians. This has been one of the easiest root+update experiences ever.

          • AFTVnews says:

            Great! Glad it worked out for you. Thanks for coming back and posting your results. I’ve updated the guide with your finds so that others don’t run into the same issue.

          • max says:

            As a side note, I did this all with the ADB files in the FTV Side App I installed to sideload the root/su/busybox apps. I didn’t not, and have not, installed the sdk on this PC.

            Open the FTV folder in windows explorer and open a command prompt (shift right-click in the folder > Open command prompt here) and then adb connect .

            I dropped the .bin (renamed update.zip) in the FTV folder as well.

        • Steve says:

          Guys, Im having a similar problem however using mkdir it does not work. I ran the steps are bottom as well and this still happens. I am on 51.1.1.1 with root, supersu and busybox installed. Thanks

          root@android:/ # cd /cache/recovery
          cd /cache/recovery
          sh: cd: /cache/recovery: Not a directory

          2|root@android:/ # mkdir /cache/recovery
          mkdir /cache/recovery
          mkdir failed for /cache/recovery, File exists
          255|root@android:/ #

  9. ilovemymac says:

    It just kept telling me that the system recovery was not successful and was restarting

    • Eric says:

      I had that issue also, turns out when i was doing the push, it was renaming the update.zip from my pc to the original filename “bueller-ota-51.1.1.0_user_511070220-signed.bin”

      Had to manually go and CD to /cache then rename the file back to update.zip using mv command

  10. Jason says:

    After running echo “–update_package=/cache/update.zip” > command. I get the message “Can’t create command: Read-only file system” not sure what I did wrong. I do have root access because I dont get an error when running “adb shell su”

  11. rick says:

    I did the disable it work fine but when I try to enable it its still saying killed adb shell>su>pm enable com.amazon.dcp..can help me with this problem

  12. Toxic says:

    Will the remote be updated as well if you use this manual way of updating?

    Or will you have to update the remote separately?

    • AFTVnews says:

      You will have to update the remote separately as there is currently no way to update the remote manually. Several people have reported that the remote update became available shortly after updating the Fire TV manually. Also, the remote update still comes through with com.amazon.dcp disabled.

      • Toxic says:

        Okay, thanks for the quick reply!

        Just one more question.
        Now that you mentioned the disabled thing, i have my firetv’s ota updates disabled using that pm disable command or something like that.

        Will i have to do anything before manually upgrading?
        Or is it safe to just manually updating even with the ota disabled?

        Sorry for the nooby questions. Just got my firetv 4 days ago.

  13. Vlad says:

    steps 6 and 7 can be combined:
    chmod 777 /cache /cache/recovery

  14. Vlad says:

    steps 8 & 9 can be combined as well:
    echo –update_package=/cache/update.zip > /cache/recovery/command

  15. Vlad says:

    steps 10-13 can be replaced with this:
    wget -O /cache/update.zip NEW_FIRMWARE_URL && reboot recovery

  16. Cyberdude says:

    When in shell, after su, and type chmod 777 /cache, I get the error “unable to open /cache: is a directory.

    What’s up?

    • Cyberdude says:

      Nevermind. Device in another room. Missed the dialog.

    • AFTVnews says:

      Double check that you’ve typed everything in correctly. Also double check that you granted permission when you type ‘su’. When you type ‘su’ and hit enter, you will either get a large pop-up on the Fire TV with asking for permission to proceed, or you will see a small popup near the bottom indicating that adb has been granted permission.

  17. loplo says:

    Can anyone confirm that root is lost after the upgrade?
    If YES, the rooting process is the same as with the original firmware? Something else to be aware?

    • AFTVnews says:

      Root is lost, but it is not blocked. After upgrading or downgrading, just re-root with the towelroot app. The only other thing to be aware of is to make sure you are not blocking the Fire TV’s access to Amazons domains via a modified host file or via a router block.

  18. Byrd says:

    I got root and tried to get a newer software version on the AFTV. Everything went great but 15 min into the push, I get this…

    [I]failed to copy “/sdcard/Download/update.zip” to “/cache/update.zip” : No space left on device [/I]

    I am doing this on an android tablet and it is a brand new FTV with 3+ gigs left

    Any help would be appreciated!!

    Thanks!!

  19. Nathan says:

    When I try to push the update.zip i get

    cannot stat ‘update.zip’: no such file or directory

  20. Joe says:

    Just curious but I found a MUCH MUCH easier way.

    2) Go to Settings > System > About and check to see which version you have. Compare it to the list you compiled on the webpage: http://www.aftvnews.com/software/

    3) If you could use an update, say from 51.1.0.2_user_510058520 to 51.1.2.0_user_512073320 then let it update. It will say updating to version 512073320 in the Settings > System > About > Check for System Update

    4) If it doesn’t seem to be downloading, then click cancel and try again. If this doesn’t work reboot and try again. Stay on this screen until the update is done. You may have to push the “Right” button on your remote once or twice depending on your internet speed to avoid the screensaver. Once download is complete it will give you the option to select to install. Install it.

    5) Once installed turn off automatic updates (once you get the version you want).

    Is there a downside to this – will it skip multiple updates and start updating to the most current update or will it do several updates until it reaches the update ending in 0220 which is where you should stop because anything after isn’t rootable.

    Just curious – Thanks! Btw – this method worked for me for now….who knows what tomorrow brings.

    • Joe says:

      Errr change that from firmware 510058520 to 51.1.1.0_user_511070220 – I put 51.1.2.0_user_512073320 and that is not rootable but I couldn’t edit my post. Sorry bout that.

  21. nicole says:

    how do you downgrade when your system upgraded and can no longer be rooted. :(

  22. Don_black says:

    it said upgrade was unsuccessful what did I do wrong. This is the first time I ever had issues did this on my other box no problems.

  23. Ronald Smith says:

    Just wondering what FTV does if its firmware crashes and the recovery path to Amazon has been locked out on router. Does FTV keep a zipped copy of the firmware on board somewhere it can call up in such a situation? If so, and we could crash it, putting older FW there it might recover itself to old rootable copy. Sorry if this is glaringly obviously a newbie question, I am a newbie at this.

    I would risk a brick if someone has an idea along this line. I want my root.

    • AFTVnews says:

      As far as we know, the Fire TV does not have the ability to rebuild it’s operating system. Factory reset just deletes the user files and does not touch the system files.

  24. Mike says:

    I have a rooted 51.1.1.0 rooted I tried these steps everything went ok up till i did the reboot to recovery. It rebooted has the Amazon in white on the screen but just sits there. Ideas?

  25. Mike says:

    Can the update.zip be removed after its installed?

    • AFTVnews says:

      It should be deleted automatically, but if it’s not, then you can delete it (must be rooted) with the following commands:

      1. adb shell
      2. su
      3. rm -f /cache/update.zip
      4. exit
      5. exit
  26. ask111 says:

    hello am on the latest firmware as I get the root … what should I do…please help

  27. KB says:

    error:more than one device and emulator.

    I get that after using commang ‘adb shell’.
    I exited my first attempt after doing step 12 only to realize that the command had not frozen but was uploading the update file.

    • AFTVnews says:

      This sometimes happens when the Fire TV reboots with ADB connected.

      Run: adb devices

      That will list what’s connected. There is probably more than one device listed. For each line, run: adb disconnect

      Then run: adb kill-server

      Then reconnect adb as normal.

  28. netmind says:

    I’m getting an error when trying at “cd /cache/recovery” – getting “/cache/recovery is not a directory”.

    When I do a ls -al, recovery is there but it doesn’t show as a directory:

    root@android:/cache # ls -al
    ls -al
    drwxrwx— root root 1969-12-31 16:00 lost+found
    -rwxrwxrwx system cache 35 2014-06-27 13:31 recovery

    I am on FW 51.1.0.1_user_510055620. If I just go on with the the remaining steps, I can push the update.zip to the /cache directory, trigger recovery reboot, but then it fails.

    Any ideas? I was tempted to delete and then re-create recovery as folder but don’t know if this would start breaking stuff or bricking me.

    Btw I also installed clockwordmod recovery, which seemed to install but then when it rebooted into that I listed a few errors about not being able to access several subfolders under cache/recovery.

  29. Mike says:

    First off, thanks again for all the help with our device. You always have super easy to understand guides, and i’m psyched to get CWM installed :)

    I see that we’re chmod’ing /cache and /cache/recovery to 777 (rwx for everyone). I don’t ever see us changing it back to whatever it was originally. Does this happen automatically? If not, I was stupid and never checked the permissions before I chmod’ed, and i’d like it to be back to whatever it was… any thoughts on what permissions were and if we need to re-set them back?

    • AFTVnews says:

      Thanks for the kind words. I’m glad you’re enjoying the site. I never really thought about or checked the original permissions. The Fire TV seems to work fine without setting it back, but I’ll try to remember to check on that directory the next time I’m digging around there.

  30. sunrise495 says:

    Do I have to update firmware in order, or can I leap frog over version?

    Just got a FTV from Staples, 9/25/14, and it came with version 51.1.0.1_user_510055620.

    Can I manual upgrade / jump right to version 51.1.1.0_user_511070220?

    Thoughts?

    Thanks

    • AFTVnews says:

      Yes, you can jump to any version you want. The “updates” are actually full complete versions of the operating system. You can install any one you want at any time regardless of what version is currently on the Fire TV

  31. slyice says:

    Did everything now system is in a reboot loop about every-time it reaches about 1/3 of the bar under the android man. Is there any fix?

  32. Andy says:

    I am stuck, I can do everything on this guide, but when it goes to reboot into recovery it says the update has failed and then it reboots. I have tried both the recommended version in this guide and the earliest version I could find ready for download. I have tried both pushing it from the PC and I’ve tried stickmount and letting it pull the update.zip from a USB stick. Has anyone else run into this issue and found a work around? Please reply.

  33. Mike says:

    slyice

    I have the same issue, cant get out of it, i think we are bricked

  34. Stacey says:

    I am having a real hard time getting adbfire’s ADB Shell to do a PUSH.

    I can connect and I was able to start ADB after turning debug ON on the FireTV.
    I was able to Install APK tr.apk and SuperSU apk and get them installed and functional

    One time I was able to get the push to start using the update.zip I put into the adbfw108 directory since there seemed to be no way to use a real path and get it to stat.
    I even tried putting it in the same directories that the examples show.

    But the one time it started to transfer the file but something on the windows laptop was doing weird stuff and its transfer rate was like 255,000 bytes in 15 minutes so I killed it and rebooted the windows Now it is fast again. I can get into the adb shell quickly, before it took about 1 minute to come back to the prompt.

    But now I can not get it to see the file anymore.

    Here is a sample:

    shell@android:/ $ adb shell
    adb shell
    shell@android:/ $ su
    su
    root@android:/ # ls -l /cache
    ls -l /cache
    drwxrwx— root root 1969-12-31 16:00 lost+found
    drwxrwxrwx root root 2014-10-03 18:08 recovery
    root@android:/ # exit
    exit
    shell@android:/ $ exit
    exit
    shell@android:/ $ adb push update.zip /cache
    adb push update.zip /cache
    cannot stat ‘update.zip’: No such file or directory
    1|shell@android:/ $

    1|shell@android:/ $ adb push update.zip /cache
    adb push update.zip /cache
    cannot stat ‘update.zip’: No such file or directory
    1|shell@android:/ $

    1|shell@android:/ $ exit
    exit

    C:\adbfw108\adbfw108>dir update.zip
    Volume in drive C has no label.
    Volume Serial Number is 80C0-0424

    Directory of C:\adbfw108\adbfw108

    10/03/2014 05:56 PM 478,051,952 update.zip
    1 File(s) 478,051,952 bytes
    0 Dir(s) 151,860,760,576 bytes free

    C:\adbfw108\adbfw108>

    I have the same problem trying to push the Vendor_054c_Product_05c4.kl file for the PS4 controller support. It can not find the file. I tried a few different ways hoping the quoting might help. What is wrong?

    shell@android:/ $ adb push Vendor_054c_Product_05c4.kl /sdcard/
    adb push Vendor_054c_Product_05c4.kl /sdcard/
    cannot stat ‘Vendor_054c_Product_05c4.kl’: No such file or directory
    1|shell@android:/ $ adb push C:\Download\Vendor_054c_Product_05c4.kl /sdcard/
    adb push C:\Download\Vendor_054c_Product_05c4.kl /sdcard/
    cannot stat ‘C:DownloadVendor_054c_Product_05c4.kl’: No such file or directory
    1|shell@android:/ $ adb push Vendor_054c_Product_05c4.kl /sdcard/
    adb push Vendor_054c_Product_05c4.kl /sdcard/
    cannot stat ‘Vendor_054c_Product_05c4.kl’: No such file or directory
    1|shell@android:/ $ adb push C:\adbfw108\adbfw108\Vendor_054c_Product_05c4.kl /s
    dcard/
    \Vendor_054c_Product_05c4.kl /sdcard/ <
    cannot stat 'C:adbfw108adbfw108Vendor_054c_Product_05c4.kl': No such file or dir
    ectory
    1|shell@android:/ $ adb push C:/\adbfw108/\adbfw108/\Vendor_054c_Product_05c4.kl
    /sdcard/
    08/\Vendor_054c_Product_05c4.kl /sdcard/ <
    cannot stat 'C:/adbfw108/adbfw108/Vendor_054c_Product_05c4.kl': No such file or
    directory
    1|shell@android:/ $ adb push C:\/adbfw108\/adbfw108\/Vendor_054c_Product_05c4.kl
    /sdcard/
    08\/Vendor_054c_Product_05c4.kl /sdcard/ <
    cannot stat 'C:/adbfw108/adbfw108/Vendor_054c_Product_05c4.kl': No such file or
    directory
    1|shell@android:/ $

    Anyone see what I am doing wrong?

    Hints?

    • Stacey says:

      A little more information…..
      I also tried this from the Amazon FireTV Utility App (FTV Side App Installer) using it’s SHELL button.

      I copied the files I wantd to move into that APPs directory on windows which I had it ad C:\FTV

      This is what I got:

      * daemon not running. starting it now on port 5037 *
      * daemon started successfully *
      connected to 192.168.1.19:5555
      shell@android:/ $ adb push Vendor_054c_Product_05c4.kl /sdcard/
      adb push Vendor_054c_Product_05c4.kl /sdcard/
      cannot stat ‘Vendor_054c_Product_05c4.kl’: No such file or directory
      1|shell@android:/ $

      1|shell@android:/ $

      1|shell@android:/ $ adb push update.zip /cache
      adb push update.zip /cache
      cannot stat ‘update.zip’: No such file or directory
      1|shell@android:/ $

      So why wont it get these files for me?
      I also have the Norton Antivirus and Firewall disabled during these attempts so that it does not cause issues.

      Any ideas?

      • AFTVnews says:

        all of your “adb push…” commands are being run in adb shell. You need to run it from adb. I am unfamiliar with what the utility is doing. I suggest setting up adb and using it directly to run the commands in this guide.

        • Stacey says:

          OK thanks that cleared up some stuff after I played with it a while:

          I did not know there was a ADB I could run directly from a CMD window on WINDOWS7.

          So I did the install as shown in http://www.aftvnews.com/how-to-sideload-apps-to-your-amazon-fire-tv-using-a-windows-pc/ Following Step 1. to Step 4 up to and including 4.2.

          But I had issues when Step 4.1 said to “1.Shift + Right-Click on an empty area of the “platform-tools” folder and select “Open command window here””

          I was not able to get it to ever say “Open command window here”. First I was not doing the SHIFT. THen when I tried the SHIFT and RIGHTCLICK it still did not work. No “Open command window here” displayed.

          So I copied a Command Prompt in that dir and then changed it’s properties to “Start In” the correct directory. Then I created a shortcut and stuck it on the desktop. That fixed it.

          Then I found that the Shift Rightclick does give you the option to Open a command window. You just have to do it exactly right. You have to be careful not to have anything Highlighted first or Shift Rightclick will not show that option!

          Windows!!!!!! just a bit to sensitive.

          Then I ran the adb push and it worked!

          Thanks for your help this will make things go more smoothly in the future.

  35. swissi says:

    Tried to downgrade a new, rooted FTV on 51.1.1.0_user_511070220 to 51.1.0.2_user_510058520 in order to install ClockworkMod. I followed the guide to the letter and did a MD5 hash on the update.zip file in /cache to make sure the file is complete. When initiating the reboot recovery command, the firmware install starts but fails about 30 percent trough the process and FTV just reboots into the old version. In the log I see the following error message:

    “script aborted: assert failed !less_than_int (1397598677, getprop (“ro.build.date.utc”))”

    Does it recognize that the version I’m trying to install is older than the current version and aborts the install?

    Any suggestions what could be wrong and what to try next?

    Thanks for all the great work on this site.

    • AFTVnews says:

      The Fire TV does not care if the image being installed is older than the one currently installed. So that isn’t the issue.
      Sorry, but I’ve never encountered or heard of that error. The only thing I can suggest is to delete everything and try again from the beginning.

  36. canada1 says:

    I tried following the guide but when my ftv reboots it gives me Update was not successful. I even tried the amazon fire tv utility.
    any help please.

  37. tuga says:

    i am need help this works on german amazon fire tv box???

  38. Vaughn says:

    Unable to run su command windows error message /system/bin/sh: sudo: not
    127|shell@android:/ $

  39. WwDesi says:

    okie this thread is misleading guys you can only upgrade and downgrade if you root your AFTV. and if you get error message /system/bin/sh: sudo: not
    127|shell@android:/ $

    That’s means root it first if you updated your fw to newer version you cant root.

    I hope the admin makes it clear that you need root to downgrades and upgrade. if I am wrong please point me to the right way. Thanks

    • AFTVnews says:

      The third sentence on this page says “In order to manually upgrade or downgrade, you will need to be rooted with BusyBox installed.” Not sure how much clearer it can be.

  40. Draven says:

    Can anyone please help? Total noob here!

    I’m on FW 51.1.0.1_user_510055620. I’m trying to upgrade to 51.1.1.0_user_511070220. For the life of me I can’t get this to work. No matter what I do the final outcome after rebooting is “the system update was unsuccessful”.

    When entering “cd /cache/recovery”, I’m getting “sh: cd: /cache/recovery: Not a directory”.
    If I try “mkdir /cache/recovery”, I get “mkdir failed for /cache/recovery, File exists”.

    If I continue, then when I enter “echo –update_package=/cache/update.zip > command
    “, I get “sh: can’t create command: Read-only file system”.

    If I continue after that, the rest looks like it’s working, but once the system reboots, it simply says the update was unsuccessful.

    C:\FTV\MISC\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-2014070
    2\sdk\platform-tools>adb shell
    shell@android:/ $ su
    su
    root@android:/ # chmod 777 /cache
    chmod 777 /cache
    root@android:/ # chmod 777 /cache/recovery
    chmod 777 /cache/recovery
    root@android:/ # cd /cache/recovery
    cd /cache/recovery
    sh: cd: /cache/recovery: Not a directory
    2|root@android:/ # mkdir /cache/recovery
    mkdir /cache/recovery
    mkdir failed for /cache/recovery, File exists
    255|root@android:/ # echo –update_package=/cache/update.zip > command
    echo –update_package=/cache/update.zip > command
    sh: can’t create command: Read-only file system
    1|root@android:/ #

    • AFTVnews says:

      I’m guessing you’re seeing this different behavior because your FIre TV has never updated. My guess is that the first time the Fire TV updates, it sets up the recovery directory.

      You can try deleting the /cache/recovery file by running:
      rm -f /cache/recovery

      Then creating the directory with:
      mkdir /cache/recovery

      But be warned, I have never tried this and do not know what the results will be. You’ll be treading on completely new territory here.

      Personally, I would forget about installing 51.1.1.0 and instead install ClockworkMod which will allow you to install the pre-rooted 51.1.3.0
      Here is my guide on that: http://www.aftvnews.com/how-to-update-a-rooted-amazon-fire-tv-to-the-latest-version-without-losing-root/

  41. Taipan454 says:

    Hello All,

    I am a total noob here and need some help. I have never rooted my firetv and it has updated to the new version. Is there any way to gain root access?

  42. Muller says:

    This is one of the best & useful article for AFTV, thanks.

    Questions:
    1) My AFTV comes with 51.1.0.1_user_510055620 (Date Unknown) and if I’m to use the above method to update to Official Stock Software from Amazon 51.1.1.0_user_511070220 7/9/2014 (last rootable), once updated and should I do a reset, will my AFTV reset to the original 51.1.0.1_user_510055620 (Date Unknown) or 51.1.1.0_user_511070220 7/9/2014 (last rootable)?

    2) If I don’t do the ClockworkMod Custom Recovery, my AFTV will forever stuck with 51.1.1.0_user_511070220 7/9/2014 (last rootable), right?

    Thanks in advance.

    • AFTVnews says:

      1) No, it will not reset to 51.1.0.1. Doing a factory reset will just delete your user files and will not modify the currently installed software version at all.

      2) If you want to keep root and don’t want to install ClockworkMod, then yes, you will be stuck on 51.1.1.0. It’s possible that in the future a new root procedure will be released that works with newer software versions. Without ClockworkMod, that would be your only way of upgrading and keeping root. You would be waiting for a new root procedure.

      • anthony says:

        I’m on 51.1.1.0 which my ftv came with. I rooted it and installed SU, busy box, TR, and some other items.
        The guide suggests downgrade to 51.1.0.2. I have never been able to do this.

        Q. Do I really need to?

        Q. Whats the disadvantage of staying at 51.1.1.0?

        TIA

  43. Maseltrdf says:

    Hey There,

    i´ve readed along the guides and i´m not quite sure so far.
    My AFT ist on current Stock and not rooted…
    Is it possible to go back on an older stock to root and or prerooted Stock out of the current FW ?

    I´m thinking about to root and install CWM as usually i do that on any of my devices ;)

    Tnak you for your help/support so far !

  44. cardboardbox says:

    I’ve gone through all the steps repeatedly but I always get stuck at the first white amazon screen after rebooting to recovery. Giving up for now, head sore after all the banging.

  45. Tony says:

    So when I get to the point where it’s meant to be boot into recovery it just sits there on the amazon logo.
    Is that what is supposed to happen or should I see something else?

    I have the file uploaded and all the permissions set as far as I’m aware.

    Busy box is installed.

    Should I just let it sit?

  46. Seahawks says:

    Need some guidance please. Currently, running 51.1.0.1_user_510055620 (rooted) and want to upgrade 51.1.1.0_user_511070220 – I followed the above steps and the upgrade fails. So I proceed with Step #7 (“if downloading fails”) and receive the following error:

    root@android:/ # dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
    dev/block/platform/msm_sdcc.1/by-name/recovery
    /sdcard/recovery.img: cannot open for read: No such file or directory

    Side note, when I try to install ClockWorkMod I receive the same error message. Step #10 of guide – http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/

    Any suggestions? I appreciate it.

    • AFTVnews says:

      Something is going wrong when you push the recovery.img file to the Fire TV’s /sdcard directory. The file is not getting here. After pushing it, try running the commands:
      adb shell
      ls -al /sdcard

      to see if the file is listed. If not, paste your entire command line history here and I’ll take a look.

  47. modstore says:

    My latest Fire TV wouldn’t allow the downgrade update to run. So I followed the extra steps, but it didn’t work. I get a “No space left on device” error. http://imgur.com/76wW5n8

    And when I tried recovery reboot, it just sits on the white amazon logo now.

    Any ideas? It’s a brand new FireTV so there shouldn’t be anything filling up the space. And I deleted the update.zip from /cache before attempting it.

  48. Tony says:

    I have fireTV ver. 51.1.4.0_user_514006420. I want to downgrade to 51.1.0.2_user_510058520. I tried to followed your instruction step by step but I got problem when I tried to install busybox v1.20.2, it failed. I tried to install all versions from drop down bar, they all failed. I tried to run SuperSU, it said “There is no SU baniry installed and SuperSU cannot install it. There is a problem.” What did I do wrong? How do I correct it? Please help. Thank you.

  49. Andy says:

    [quote]Update
    10/10/2014 As of this week, some Fire TVs are starting to arrive with an updated recovery partition that is blocking downgrades. If you follow this guide and the downgrade fails during the installation, follow the new steps I just added to the bottom of this page.[/quote]

    As of this week? I got mine 2 months ago and it wouldn’t allow me to downgrade running version 51.1.1.0.

  50. ToxicDM says:

    Will i have to re-block the updates if i downgrade?

  51. prodigy7 says:

    Does the stock firmware also works with FireTV shipped in germany?

  52. Wodehouse says:

    I successfully reverted a few FTV’s months back… but am now having issues and wonder if it is related to the issue of new FTV’s being blocked from downgrading.

    Now, when I get to the end of the process and push the zip.update file I get a message that the zip “does not contain AndroidManifest.xml.”

    Am I doing something wrong — or is this message consistent with the blocking on recent FTV’s? All my Fire TV’s arrived from Staples in the past 2 weeks and are on 51.1.1.1 — firmware that IS root-able. However, I would love to downgrade to 51.1.1.0 like I have in the past.

    Thanks!

  53. marc says:

    i noticed on reboot the /cache folder and /cache/recovery are getting their privileges modified. i have used chmod 777 /cache a number of times and went i reboot the box it loses privileges for user and the command file gets erased from /cache/recovery. Any thoughts? The devices is rooted and i did put the update.zip in the folder but the command keeps disappearing.

  54. Nick says:

    AFTV news please help. I just bought a new FTV and it came installed with newest update what steps on the page should I follow to downgrade it to rootable firmware?

  55. ASadani says:

    Can’d downgrade Stuck on Amazon White Recovery Logo help.
    I have the firmware Software Version 51.1.10_user_511070220 and trying to downgrade to 51.1.0.2_user_510058520. so I can install the clockwork recovery.

    on recovery reboot. I get the amazon white logo and it stays there for hours doing nothing. can someone help please.?

  56. Duvell says:

    I followed instructions but always failed when it rebooted into recovery.

    So I followed the instructions to get the stock recovery image. When I ran the dd command it only copied part of the file and gave a write error saying the device is out of space.

    The of parameter of the dd command, /dev/block/platform/msm_sdcc.1/by-name/recovery, is linked to /dev/block/mmcblk0p11 which appears to be only about 100mb.

    /dev/block/platform/msm_sdcc.1/by-name/recovery: write error: Nospace left on device
    20481+0 records in
    20480+0 records out
    10485760 bytes transferred in 1.275 secs (8224125 bytes/sec)

    Am I correct to assume this wrote over the “factory reset” image, and that if I attempted that, I would likely brick the device since the image is not complete?

    Any ideas how to fix this?

    duvell

  57. Duvell says:

    Disregard my plea for help above. I had a brain fart!
    I downloaded the full stock software image instead of the stock recovery image. The recovery image does fit in the partition.

    duvell

  58. Barry says:

    I have my AFTV rooted using towelroot and i ran all these commands to try connect but i do the following i get this error, what am i doing wrong?? thanks

    Daniels-MacBook-Air:~ Barry$ adb shell
    -bash: adb: command not found

    Here is full commands i ran:-

    Daniels-iMac:~ Barry$ /Users/Barry/Downloads/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/adb>adb kill-server

    Daniels-iMac:~ Barry$ /Users/Barry/Downloads/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/adb>adb start-server

    Daniels-iMac:~ Barry$ /Users/Barry/Downloads/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/adb>adb connect 192.168.2.78

    Daniels-MacBook-Air:~ Barry$ adb shell
    -bash: adb: command not found

    • AFTVnews says:

      Did you change to a different computer during the last two steps? It goes from “iMac” to “MacBook-Air”.

      The last step says “command not found” because you’re running the command outside of the Android SDK folder. You need to change to the right directory first. In your case you should run:

      cd /Users/Barry/Downloads/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/adb

      • Barry says:

        I am using my Air now so the command should be

        Daniels-MacBook-Air:~ Barry$ /Users/Barry/Downloads/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/adb>adb shell

  59. Mark says:

    My new FTV has version 51.1.0.1. I rooted it using your guide no problem. I’m now attempting to use this guide to update to version “51.1.4.0_514006420 updated”. I attempted twice, following the instructions exactly and everything appears to go just fine. However, after the last step when it reboots, the FTV displays a message saying something along the lines of “system update unsuccessful”. Then, after a minute or two, it reboots back into 51.1.0.1.

    Any idea what I’m doing wrong? Thanks for your help.

  60. Raub says:

    I got a fire tv rooted with firmware 51.1.1.0_user_511070220. I tried downgrading to 51.1.0.2_user_510058520 so I can install ClockworkMod Custom Recovery. But every time I got the following message after reboot to recovery: the system update was unsuccessful. I even tried lower firmware and I received the same error. Thank you for your help in advance

  61. Mark M says:

    Hello, I am also having an issue trying to downgrade. I am on 51.1.1.0_user511070220 and am trying to downgrade to 51.1.0.2_user_510058520.

    I completed the process but when the Fire TV reboots I am getting the same error as Raub “system update was unsuccessful”. I figured I am dealing with an updated recovery partition.

    I tried the next step Fire Tv stock recovery 51.1.1.0_user511070220. (recovery-stock-51.1.0.img) and end up with the same results.

    I think my problem might be at step #12 Repeat the entire downgrade process in this guide.

    I started at step #6 • chmod 777 /cache and went through #13 adb reboot recovery and still got the “system update was unsuccessful”

    Sorry about the noob questions. Thanks for all your help!

    P.S. is it possible that it did work even with the “system update was unsuccessful” error?

  62. nagyg says:

    same here: I am on 51.1.1.0_user_511070220 and rooted and have followed all the steps including “when update fails” and it wont install

  63. Ted says:

    I did the same thing as modstore did and downloaded the full update of 51.1.1.0_user_511070220 vs the recovery image. I just did a search on the downloads page and grabbed the first hit. There’s two ‘51.1.1.0_user_511070220’ files, recovery and update. One suggestion: Add that tip saying that (yes I glossed over the bolded words) on step 1 of ‘If downgrading fails’. Thanks for the site!

  64. Raub says:

    Thank you very much.It worked. I did not see If downgrading fails:” portion at the bottom of the guide. I should have read it. I guess I was in hurry.

  65. Vladimir says:

    I’m having some trouble downgrading from 51.1.10 to 51.1.0.2. When I tried it the first time it said the fireware could not be installed. So I tried the next steps “If downgrading fails:” portion at the bottom of the guide but came into the error of “/sdcard/recovery.img: cannot open for read: No such file or directory “. Is there a chance I lost root and have to re-root it again? Is there a way to check?

    P.S. When it says to “12.Repeat the entire downgrade process in this guide” does that mean start over on Step 6 or exit out of su and start over entirely?

    • AFTVnews says:

      It sounds like the recovery.img file didn’t get transferred to the Fire TV correctly (step 4). Try downloading it again and pushing it again.

      Starting over at step 6 is fine as long as you make sure you ran the ‘su’ command first.

      • Vladimir says:

        Is SuperSU suppose to start up on the AFTV when I run the commands through it? Because it doesn’t. Because right now the command window sits doing nothing after I do “adb push update.zip /cache”. I cannot type or do anything on the command line.

        • Vladimir says:

          Nevermind, apparently I had hide known file extensions turned on and when I renamed the update file it was “update.zip.bin”. Changed it to update.zip while showing file extentions and everything went through.

  66. kywildcat says:

    Doing everything correctly and get getting cannot stat ‘update.zip’: No such file or directory. I get it at step 12, after completing the additional steps in “If downgrading fails” i needed after upgrade fails. I have never had a successful upgrade and I’m on 51.1.1.0_user_511070220

    C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb connect 192.168
    .0.7
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    connected to 192.168.0.7:5555

    C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb push recovery.i
    mg /sdcard/
    145 KB/s (10485760 bytes in 70.526s)

    C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
    shell@android:/ $ su
    su
    root@android:/ # dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by
    -name/recovery
    dev/block/platform/msm_sdcc.1/by-name/recovery command

    ache/update.zip > command <
    root@android:/cache/recovery # exit
    exit
    shell@android:/ $ exit
    exit
    root@android:/ # adb push update.zip /cache
    adb push update.zip /cache
    cannot stat 'update.zip': No such file or directory
    1|root@android:/ # adb push C:\FTV\update.zip /cache
    adb push C:\FTV\update.zip /cache
    cannot stat 'C:FTVupdate.zip': No such file or directory
    1|root@android:/ # adb push C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platfo
    rm-tools\update.zip /cache
    dows-x86_64-20140702\sdk\platform-tools\update.zip /cache <
    cannot stat 'C:FTVadt-bundle-windows-x86_64-20140702sdkplatform-toolsupdate.zip'
    : No such file or directory
    1|root@android:/ #

    • AFTVnews says:

      You are trying to push the file while still inside “shell”. Notice how it says “root@android” at the start of the lines where you try to do “adb push…”?

      Type “exit” until you’re back at “C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>”

      • kywildcat says:

        Thank you, I will try this later and post the results

      • kywildcat says:

        Ok that worked, but the update system failed any idea why ?

        C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb connect 192.168
        .0.7
        connected to 192.168.0.7:5555

        C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb push recovery.i
        mg /sdcard/
        577 KB/s (10485760 bytes in 17.725s)

        C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
        shell@android:/ $ su
        su
        root@android:/ # dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by
        -name/recovery
        dev/block/platform/msm_sdcc.1/by-name/recovery command

        ache/update.zip > command adb push update.zip
        /cache
        599 KB/s (415956067 bytes in 677.981s)

        C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb reboot recovery

  67. kywildcat says:

    also where do i need to remove all those files i pushed, because the process never completed

  68. nagyg says:

    Draven says:
    I’m on FW 51.1.0.1_user_510055620. I’m trying to upgrade to 51.1.1.0_user_511070220. For the life of me I can’t get this to work. No matter what I do the final outcome after rebooting is “the system update was unsuccessful”.

    YOUR RESPONSE WAS:
    Personally, I would forget about installing 51.1.1.0 and instead install ClockworkMod which will allow you to install the pre-rooted 51.1.3.0
    Here is my guide on that: http://www.aftvnews.com/how-to-update-a-rooted-amazon-fire-tv-to-the-latest-version-without-losing-root/

    Shall I go the same rote, as I am also on 51.1.1.0_user_511070220 and I cannot get the FTV to update?

  69. Dirar says:

    Is it possible to downgrade from an unrooted device that has soft ver. 51.1.4.1_user_514013920? Just bought the device and I want to root it, is that possible?

  70. Zac says:

    So after everythings rooted from 5.1.1.0. su installed and busy box, Whats gained by downgrading down to 5.1.0.2?

  71. SandmanCL says:

    There are so many excellent guides on this site. Thanks for all the hard work ! One thing I’d love to see is a flowchart showing which features are needed to enable others. I own three Fire TVs all running SW version 51.1.1.0_user_511070220 that were rooted early on. Since then a lot of new hacks, tips, and tricks are made available. If someone know if such a chart is available, any pointers would be appreciated ! :)

    The chart I visualize in my head contains an initial stage where you select which OS version you have. If it’s rootable, it should link to a “bubble” with guides for how to root. From there, a bubble showing a box that is already rooted, with links to what rooting enables you. For example, Installing ClockworkMod. And the ClockworkMod bubble would link to another one for unlocking the boot loader, etc.

  72. Ryan says:

    Fire TV came with 51.1.1.0

    Rooted the Fire TV then tried to follow this guide, I got the following:

    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    connected to 192.168.0.82:5555

    C:\FTV>adb shell
    shell@android:/ $ su
    su
    root@android:/ # chmod 777 /cache
    chmod 777 /cache
    root@android:/ # chmod 777 /cache/recovery
    chmod 777 /cache/recovery
    root@android:/ # cd /cache/recovery
    cd /cache/recovery
    sh: cd: /cache/recovery: Not a directory
    2|root@android:/ #

    Any help you can offer is appreciated!

    • SandmanCL says:

      Ryan,
      sounds like /cache/recovery is a file. Try this:

      # rm -f /cache/recovery
      # mkdir /cache/recovery
      # chmod 777 /cache/recovery

      and then proceed

    • Ryan says:

      This ended up solving my problem:

      chmod 777 cache
      cd cache
      rm recovery
      mkdir recovery
      chmod 777 recovery
      cd recovery

  73. Nicky says:

    Keep getting protocol failure

  74. Nicky says:

    So I decided to use wired connections for my “Protocol failure” error and the update went across flawlessly but the downgrade got cancelled so I tried the command “adb push recovery.img /sdcard” but it comes back as cannot stat ‘recovery.img’ no file or directory?

    Can someone please help me

  75. Sam says:

    I saw someone else post a questions about this but did not get an answer. When I run echo “–update_package=/cache/update.zip” > command. I get the message

    “Can’t create command: Read-only file system”

    I am not sure what if any steps I missed. I have root access and can use the su command (and did to create the folder /recovery). Anyone have any thoughts?

    • Sam says:

      Nvm I figured out that I was in ADB shell. But now I am receiving an error when trying to send the recovery.img to the /sdcard/ folder…”No such file or directory”. Based on my success with pushing update.zip I am following the process correctly.

      Obviously the downgrade failed so I am trying to follow the “If Downgrading Fails” process now. Is there a possibility that the 305 hardware revision’s stock software would not include the /sdcard/ folder?

      • Sam says:

        I found this interesting, my unix commands are super rusty but it seems that the /sdcard/ directory is pointing somewhere else?
        I used the ls -al command at root w/o specifing a folder and got the full root folder/file listing.

        lrwxrwxrwx root root 1970-01-01 00:13 sdcard -> /storage/emulated/legacy

        If I push recovery.img into this folder would the shell commands listed in “If Downgrading Fails” work?

        • Sam says:

          Disregard all these comments. Problem was on my end, everything is working great now! Superb instructions, this site is great. I’ll be kicking you a few bucks on payday.

          • Ren says:

            I was stucklast night trying to put the rexovery fike into the sdcard location too. How did you figure it out? Im not very good with linux so i have likely typed the command wrong but i am following the instructions as they are and keep getting the “no such file or directory” error

          • Gavin says:

            I’m having the same issue and getting the same message: cannot stat ‘recovery.img’ no file or directory. How did you get around this?

  76. Swanson says:

    I had to go the full route of the instructions as my downgrading DID fail after successfully pushing the update.zip file… But your instructions were PERFECT!

    I am now back to 51.1.0.2 which is perfect!

    Thanks so much for this site!

  77. Moe says:

    after clicking enter to the adb push update.zip /cache step it its not doing anything
    please help

    • Taz says:

      It takes about 7 minutes to push the 400 meg file over ADB.. It does not have a progress indicator, it just sits there blinking at you until it’s done. Then it’ll say something like “1118KB/s (415956067 bytes in 363.328s)”

  78. Matt R says:

    Not a noob to flashing, but was curious, does downgrading wipe out one’s installed apps? Or does it only touch /system?

  79. Thomas says:

    I’ve tried again and again. I can’t figure out why it’s failing. I’m trying to downgrade to 51.1.0.2_user_510058520 from version 51.1.1.0_user_511070220

    Ever command seems to work but the downgrade fails. Any idea?

    • Kai says:

      same there what do you get? I dont get to the downgrade fails part right after adb reboot recovery I got the white amazon logo and the orange light
      I dont know whats going on I tried many time

      • Thomas says:

        Mine reboots and says that the update has failed. I’m 100% certain I’ve followed all the steps correctly. I am very familiar with unix. I saw someone say they downloaded the wrong files, but I’ve only seen one option. Any help would be appreciated.

  80. Kaie says:

    right after adb reboot recovery I got white amazon logo and oragne light
    I tried this a few time anyone know what’s the problem is?

  81. kix420 says:

    Was having the same issues as Thomas and kai. It worked after 3 attempts, i didnt do anything different, that i can think o, as i copy/pasted all the commands on all attempts…..weird /shm

  82. Mark M says:

    I’m trying to downgrade to 51.1.0.2_user_510058520 from 51.1.1.0_user_511070220.

    I usually get the Download failed error. I tried the “if download fails” section of the directions and it still fails. Does this look correct?

    C:\Users\Mark\Desktop\Fire TV>adb shell
    shell@android:/ $ su
    su
    root@android:/ # dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1
    -name/recovery
    dev/block/platform/msm_sdcc.1/by-name/recovery
    20480+0 records in
    20480+0 records out
    10485760 bytes transferred in 1.535 secs (6831114 bytes/sec)
    root@android:/ # rm -f /cache/*.bin
    rm -f /cache/*.bin
    root@android:/ # rm -f /cache/*.zip
    rm -f /cache/*.zip
    root@android:/ # rm -f /cache/recovery/command
    rm -f /cache/recovery/command
    root@android:/ # rm -f /sdcard/recovery.img
    rm -f /sdcard/recovery.img

    C:\Users\Mark\Desktop\Fire TV>adb push update.zip /cache
    failed to copy ‘update.zip’ to ‘/cache/update.zip’: No space left on device

    ****************************************************************
    C:\Users\Mark\Desktop\Fire TV>adb shell
    shell@android:/ $ su
    su
    root@android:/ # rm -f /cache/*.bin
    rm -f /cache/*.bin
    root@android:/ # rm -f /cache/*.zip
    rm -f /cache/*.zip
    root@android:/ # exit
    exit
    shell@android:/ $ exit
    exit

    C:\Users\Mark\Desktop\Fire TV>adb push update.zip /cache
    failed to copy ‘update.zip’ to ‘/cache/update.zip’: Permission denied

    Can anyone give me some advice on how to fix this or another way to free up some space?

    Thanks Mark

  83. darren gold says:

    does anyone no if i can downgrade to rrotable firmware as i need to ssh some folders over to kodi like sportings streams cause when trying to add the zip threw drop box it says dependancies not me but if i could somehow add the actual plugin to kodi i know it would work as thats the same as it used to say on apple tv
    im running 51.1.4.2_user_514015320

  84. ken says:

    Hello can someone help me. The LED on my Ethernet Lan port that my FireTV is connect has a amber light. I have a Netgear R7000 and all the lan ports LED is white except for the one that the FireTV is connected to. Is this normal?
    Ken

  85. ken says:

    I know this might not be the most appropriate place to ask my question. But I just finished rooting my FireTV and notice my router’s LED for the lan port is orange. I thought I ask here since this page is where I had the most trouble with.

  86. omikorodu says:

    i Can not downgrade from ver 51.1.1.0_user_511070220 to 51.1.0.2.

    What did before attempt to downgrade’:
    1. Rooted the fire tv
    2- installed and launch spersu
    3. busybox free
    4. attempt to downgrade but failed each time.
    below is what am getting

    C:\Android\platform-tools>adb connect 192.168.1.17
    already connected to 192.168.1.17:5555

    C:\Android\platform-tools>adb shell
    shell@android:/ $ su
    su
    root@android:/ # chmod 777 /cache
    chmod 777 /cache
    root@android:/ # chmod 777 /cache/recovery
    chmod 777 /cache/recovery
    root@android:/ # cd /cache/recovery
    cd /cache/recovery
    sh: cd: /cache/recovery: Not a directory
    2|root@android:/ # echo –update_package=/cache/update.zip > command
    echo –update_package=/cache/update.zip > command
    sh: can’t create command: Read-only file system
    1|root@android:/ #

    please help, thanks

  87. MCheryll says:

    Hi everyone!

    My main goal is to be able to also watch movies from my HD on AFTV via USB. The version AFTV is running is 51.1.4.3 Now, I’m aware I can’t root (as of yet?), but, am I able to downgrade to a firmware that I can then root? Or is rooting PART of the requisite of being able to downgrade?

    I should mention, I downloaded all .apk’s and not surprisingly SuperSU is the one taking forever to install. Haven’t tried BusyBox, but I do have XBMC and StickMount installed. StickMount however will not mount any of my HD’s (no error, the app just force closes on me).

    So, I’ll be more than grateful to know if I should just give up the attempt, or otherwise know the starting point of my journey…

    Thank you so much in advance!

  88. vic**or says:

    Hi everyone, my issue is when i do rename the binary file to “update.zip” it turns to a pepper zip, instead of zip file.
    I have windows seven I believe this is affecting to downgrade

  89. migr6n01 says:

    i am trying to downgrade to install clockworkmod from firmware 51.1.1 everything seems to go through but when it reboots, it says installing firmware…then after 3 seconds it says system update was not successfull. it reboots after a couple minutes and brings me back to home screen where i still have full function with root.

  90. jkd says:

    Beware of cut and paste for Step 9:

    while in the /cache/recovery directory
    Run the command: echo –-update_package=/cache/update.zip > command

    should be:
    echo –update_package=/cache/update.zip > command

    notice the — verses the –- you get with a cut and paste for the characters prior to update_package… you need the —

    echo “–update_package=/cache/update.zip” > /cache/recovery/command
    will also work as long as it is –update_package

    Hopefully this solves any issues you run into with failure for the downgrade to apply

  91. Harry says:

    My Box is on 51.1.3.0 and i´ve done a hardware-root.

    Now i wanna try to unloock the bootloader.
    I´ve tryed it once but without effect.

    Now i recogniced that i mayby have to use another stock recovery (I used the 51.1.0).
    Bevor i try the other one (51.1.3.0) i want to know if i am on the right way to use this recovery to install the 51.1.0.2_user_510058520 afterwards?

  92. Bajji says:

    Hi,

    Unfortunately i have upgraded to the latest version – 51.1.5.3_user_515040320. Is it possible to downgrade to previous versions of fire tv firmware?

  93. Y.O. says:

    am attempting to downgrade my rooted (w/BusyBox) Fire TV 51.1.1.0_511070220 to 510058520, in order to eventually install your pre-rooted firmware. However, I continue to get the “downgrade install failed” message upon reboot. I read all of the comments in the downgrade post at AFTVnews, and still can’t figure it out. (I’m using a Mac computer).

    Here is my log:
    User-1s-MacBook-Pro:~ user1$ ./adb push /Users/user1/APK\ Files/recovery.img /sdcard/
    940 KB/s (10485760 bytes in 10.886s)
    User-1s-MacBook-Pro:~ user1$ ./adb shell
    shell@android:/ $ su
    dev/block/platform/msm_sdcc.1/by-name/recovery command <
    root@android:/cache/recovery # exit
    shell@android:/ $ exit
    User-1s-MacBook-Pro:~ user1$ ./adb push /Users/user1/APK\ Files/update.zip /cache
    1017 KB/s (415956067 bytes in 399.180s)
    User-1s-MacBook-Pro:~ user1$ ./adb reboot recovery

  94. Faisal says:

    Dum Question
    I m on this step “Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery”
    Q1 – how do I know update it done ?
    Q2 – I am using MAC ( Terminal )

    Please advice,
    Thanks

    • Y.O. says:

      When the update is done, you will see a line similar to this “1017 KB/s (415956067 bytes in 399.180s)” which shows the transfer rate and size. Then you would run the ADB reboot recovery command.

  95. Juan Manjón says:

    Note: If you see a message saying “No such file or directory”, then run the following two commands:
    mkdir /cache/recovery

    When i type this command, says file already exist, but after says no such file or directory… What’s is wrong here? Is my recovery corrupt?

    Thanks !!

  96. OrbitaLinx says:

    Hi, I just want to know, if i have never had root and I downgrade can I downgrade and root with out a problem? I was given the fire tv second hand so I really had no say in previous updating lol.

  97. Mike House says:

    after I do the pus command, I get

    adb push: C:\Root/adbfw114/adbfw114/ikonotv.icon/B00NEJS7ZO/thumbnail_f589f49e84a15d
    36c1fb602c76bce0789c8d6b3913b857c0edff0a91cfecaf23.png -> Fire/adbfw114/adbfw114
    /ikonotv.icon/B00NEJS7ZO/thumbnail_f589f49e84a15d36c1fb602c76bce0789c8d6b3913b85
    7c0edff0a91cfecaf23.png
    failed to copy ‘C:\Root/adbfw114/adbfw114/ikonotv.icon/B00NEJS7ZO/thumbnail_f589
    f49e84a15d36c1fb602c76bce0789c8d6b3913b857c0edff0a91cfecaf23.png’ to ‘Fire/adbfw
    114/adbfw114/ikonotv.icon/B00NEJS7ZO/thumbnail_f589f49e84a15d36c1fb602c76bce0789
    c8d6b3913b857c0edff0a91cfecaf23.png’: No such file or directory

  98. Mike House says:

    Here’s a copy of everything I did…

    Microsoft Windows [Version 10.0.10565]
    (c) 2016 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>adb version
    Android Debug Bridge version 1.0.32

    C:\WINDOWS\system32>adb kill-server

    C:\WINDOWS\system32>adb start-server
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *

    C:\WINDOWS\system32>adb connect 192.168.0.4
    connected to 192.168.0.4:5555

    C:\WINDOWS\system32>adb devices
    List of devices attached
    192.168.0.4:5555 device

    C:\WINDOWS\system32>adb shell
    shell@android:/ $ su
    su
    root@android:/ # chmod 777 /cache
    chmod 777 /cache
    root@android:/ # chmod 777 /cache/recovery
    chmod 777 /cache/recovery
    root@android:/ # cd /cache/recovery
    cd /cache/recovery
    root@android:/cache/recovery # echo –update_package=/cache/update.zip > command

    ache/update.zip > command adb push C:\Root Fire Tv\update.zip /cache
    push: C:\Root/adbfw114/adbfw114/ikonotv.icon/B00NEJS7ZO/thumbnail_f589f49e84a15d
    36c1fb602c76bce0789c8d6b3913b857c0edff0a91cfecaf23.png -> Fire/adbfw114/adbfw114
    /ikonotv.icon/B00NEJS7ZO/thumbnail_f589f49e84a15d36c1fb602c76bce0789c8d6b3913b85
    7c0edff0a91cfecaf23.png
    failed to copy ‘C:\Root/adbfw114/adbfw114/ikonotv.icon/B00NEJS7ZO/thumbnail_f589
    f49e84a15d36c1fb602c76bce0789c8d6b3913b857c0edff0a91cfecaf23.png’ to ‘Fire/adbfw
    114/adbfw114/ikonotv.icon/B00NEJS7ZO/thumbnail_f589f49e84a15d36c1fb602c76bce0789
    c8d6b3913b857c0edff0a91cfecaf23.png’: No such file or directory

    C:\WINDOWS\system32>adb reboot recovery

  99. There are the self-planned, ‘I could find a hotel whenever I get there’ style;
    there are really cruises and additionally indeed there are
    set holidays. Additionally, bear in mind which these are
    really also the most expensive occasions to go, and also finding Cancun travel deals can be much easier
    within the “off-season” months.

  100. Raub says:

    If your upgrade or downgrade fails, read the end of the guide where it says If downgrading fails:. You need to download and install Fire TV Stock Recovery by Amazon file version 51.1.0. Then start the guide again

  101. This might be super cool. I’ve been appearing right through a bunch on the internet
    and also really liked this excellent variation.

  102. Charli says:

    Indeed there are 3 or even 4 really typical issues that burst on top of all your Chrysler Town and Country and additionally Dodge Van company vehicles.

  103. ThePacketSlinger says:

    So I’m having an issue getting the bueller-ota-51.1.0.2_user_510058520-signed.bin file into the /cache partition. It looks like my cache partition is only 242 MB. It looks like I have followed the directions here to flash the old recovery and I’m seeing it boot to the white Amazon logo.

    I’ve also tried dropping the image.zip to /sdcard/ and did ln -s /sdcard/update.zip /cache/update.zip but to no avail.

    I’m on a 4k rooted ftv running Fire OS 5.0.4 and BusyBox Pro. I’m trying to get a custom recovery installed. Is there no way around this?

  104. NAVJOT says:

    i keep getting “Failed to copy … No space left on device” error:
    iam on AFTV 2 .. Plzhelp

  105. Onzz says:

    Is there an updated version of rolling back software on a fire tv 4K ? My problem is that when I installed the fire tv right out of the box it worked perfect on my older television, but now that it has updated everything displayed on my TV is over blown. The new software that was installed on my firetv messed up my picture format on my older TV. I need to go back to the original software that the firetv 4K was shipped with and to block future updates. Is this possible anymore ?? Can you root these new firetv 4K boxes? Thanks for any info on this matter!!

  106. Niki Campos says:

    I can’t write anything after Exit / Exit, please help, I’m on Mac, stuck on step 12.

  107. Niki Campos says:

    It gives me this after exit exit

    Saving session…
    …copying shared history…
    …saving history…truncating history files…
    …completed.

    [Process completed]

  108. dee says:

    loss of root = ads

    third party ads = Privacy Rape

    this is never acceptable

  109. Watt says:

    Can the downgrade still be done on the latest version?!

    When I do the Su command it comes back with not recognised?!
    Has this been blocked on the latest version or an I missing something?

  110. mark says:

    Hi,

    Sorry for a dump question.

    I have firetv 1 running on 51.1.6.3_user_516012020 (did this pre rooted version long ago from aftvnews procedure).

    How can I upgrade to latest 5.1/5.2 (because netflix is not working)?.

    Thanks

Leave a Reply

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

*