yashsingh1/xdaforums huggingface dataset:
[Fire TV General] brie987:
This is the furthest I have ever gotten but it did not work. I keep getting this:

shell@android:/ $ su

su

root@android:/ # chmod 777 cache

chmod 777 cache

root@android:/ # cd cache

cd cache

root@android:/cache # rm recovery

rm recovery

rm failed for recovery, Is a directory

255|root@android:/cache # mkdir recovery

mkdir recovery

mkdir failed for recovery, File exists

255|root@android:/cache # chmod 777 recovery

chmod 777 recovery

root@android:/cache # cd recovery

cd recovery

root@android:/cache/recovery # echo --update_package=/cache/update.zip > command

ache/update.zip > command <

root@android:/cache/recovery # 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:/ $

Thanks again.
[Fire TV General] vrm4:
I was having the same or similar issue and found a tip that worked for me. If you are using windows make sure that under folder options / view/ advanced settings the box for "hide extensions for known file types" is UNCHECKED. This was preventing the the update zip file from being found as it was still leaving the .bin extension on even after renaming the firmware so it ended up being update.zip.bin. Hope it helps.
[Fire TV General] brie987:
Thanks for the tip but it still does not find the update.zip file at the very end. Everything works great but for the very last line, which is:

shell@android:/ $ su

su

root@android:/ # chmod 777 cache

chmod 777 cache

root@android:/ # cd cache

cd cache

root@android:/cache # chmod 777 recovery

chmod 777 recovery

root@android:/cache # cd recovery

cd recovery

root@android:/cache/recovery # echo --update_package=/cache/update.zip > command

ache/update.zip > command <

root@android:/cache/recovery # 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:/ $

Any other ideas? I have the file in the same adb file and in my C: root file. Im just out of ideas. Thanks again and open to more suggestions. Just for more info I am using ADBFire to accomplish this.

---------- Post added 3rd October 2014 at 12:06 AM ---------- Previous post was 2nd October 2014 at 11:42 PM ----------

YAHOOOOOOOOOOOOOOOOOOOO! Actually this worked! I noticed that when I unchecked the "hide extension..." like you said I saw the actual "update.zip" file but for some reason there was a hidden ".bin" after the file so my update.zip file were in reality was being seen as "update.zip.bin" and so "no such file" was being reported. So I changed the file by removing the .bin and actually changed the adb app I was using, I switched to "Fire TV Firmware Restore Tool" from adbFire and IT WORKED!!!!!!! THANK YOU SO MUCH TO BOTH "VRM4" and "NYDER" for your help and patience. I think this update is much improved from my last firmware so Im glad I stuck with it.. THANKS AGAIN!
[Fire TV General] Kramar111:
You just need one more time type exit and execute it before you run adb push

adb push need to be run not in adb shell, but in windows command line

Sorry for my bad english
[Fire TV General] nyder:
cool, glad you got it working brie
[Fire TV General] mud99:
It appears that amazon must have closed the ability to downgrade the firetv.

I just received my Fire TV, which is running 51.1.1.0_user_511070220, towelrooted, and attempted to downgrade to 51.1.0.2.

The downgrade failed, and I found this error in /cache/recovery/last_log. The last few lines indicate that they are now doing a timestamp check against ro.build.date.utc to make sure that any software that is being installed is a newer version than the current software. Mine has ro.build.date.utc=1404177321, and since 1397598677 is less than that, the assertion in the installer fails. Since the installer appears to be signed by amazon that doesn't leave any options.

Finding update package...

I:Update location: /cache/update.zip

Opening update package...

I:read key e=3

I:1 key(s) loaded from /res/keys

Verifying update package...

I:comment is 1706 bytes; signature 1688 bytes from end

I:whole-file signature verified against key 0

I:verify_file returned 0

Installing update...

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

assert failed: !less_than_int(1397598677, getprop("ro.build.date.utc"))

E:Error in /cache/update.zip

(Status 7)

Installation aborted.
[Fire TV General] rbox:
If it shipped with 51.1.1.0 and wasn't updated to it, that would explain what you are seeing. Up until now, most have shipped with an earlier version. Upon updated to something newer, the recovery partition was not updated. But since yours shipped with 51.1.1.0, the recovery image would have been from that build. To fix this you need to flash an older version of recovery. I would recommend backing up your current one just in case, but it should work no problem. http://www.mediafire.com/download/6q1c96y5tcc4xgc/recovery-stock-51.1.0.img
[Fire TV General] mud99:
Worked perfectly, thanks for the help, copied it over and dd'd it to the recovery block device, downgrade succeeded.
[Fire TV General] rbox:
[MENTION=5957312]AFTVnews.com[/MENTION], you should make a note of this in your guide.
[Fire TV General] no_spam_for_me:
hehehehe

Replace the recovery at 'partition' with dd using an older recovery.img...

(but I think only possible at rooted devices?)

If someone is able to reverse engineer, or something like this, the recovery that could maybe a way to replace it with a version which is able to flash images without verifying update package and maybe also start at 'normal' recovery screen, so you can use unsigned update packages (maybe also from ext)????

-----

EDIT:

OK, fond out that rbox do something like this at/with his CWM-solution...

http://xdaforums.com/fire-tv/development/recovery-cwm-recovery-6-0-5-0-0-t2882336
[Fire TV General] AFTVnews.com:
Definitely. Thanks for the heads up!
[Fire TV General] mud99:
That's basically how CWM works, it replaces the recovery partition.

The standard recovery image appears to consist of an ANDROID header, followed by a linux kernel image, followed by an initramfs image, which itself is a gzipped cpio archive of the recovery filesystem. I don't really understand the bootloader on this thing so not really sure how it decides what to boot and what verification it does on the image. If you use a hex editor and know what to look for, you can see all this pretty easily.

I extracted all the partitions from the flash and will be playing around with them this weekend

I have noticed something odd, I have not been able to play any prime videos, the screen goes blank and I get a message that the video cannot be played. I'm not sure whether this is due to root or some problem on my network, as I did not test it before rooting. Also, streaming in XBMC works great but playing a video off of a USB key with stickmount glitches and doesn't work right, so I have to figure that out. Stickmount is a strange program.

This is my first android device, still learning how everything works.
[Fire TV General] AFTVnews.com:
I have updated my downgrade guide with instructions on how to flash the old recovery image incase you end up with a Fire TV that blocks downgrading.
[Fire TV General] rbox:
This device uses a slightly modified version of LK (little kernel) from Qualcomm. If you are curious how it works you can get the source from Code Aurora. Basically with no external input, it will look for a partition named 'boot' and load that. If it was told to do something else like boot recovery, then it will look for a partition named 'recovery' and load that. Android can write a command to a special location which tells it to boot into recovery. As for verification, it does a SHA256 over the entire image and then compares it to an encrypted version of the SHA256 that is at the end of the image.
[Fire TV General] cardboardbox:
I've followed this guide repeatedly and all I ever get is the white amazon screen after rebooting to recovery. I have 51.1.1.0 and I've done the instructions under "If downgrading fails:" I never get an error, its just stuck.

Any ideas?
[Fire TV General] AFTVnews.com:
Copy and paste your entire terminal/cmd text here.
[Fire TV General] cardboardbox:
C:\FTV>adb connect 192.168.1.15

connected to 192.168.1.15:5555

C:\FTV>adb push recovery.img /sdcard/

2754 KB/s (8802560 bytes in 3.121s)

C:\FTV>adb shell

shell@android:/ $ su

su

root@android:/sdcard # dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdc

c.1/by-name/recovery

f=/dev/block/platform/msm_sdcc.1/by-name/recovery <

17192+1 records in

17192+1 records out

8802560 bytes transferred in 1.305 secs (6745256 bytes/sec)

root@android:/sdcard # rm -f /cache/*.bin

rm -f /cache/*.bin

root@android:/sdcard # rm -f /cache/*.zip

rm -f /cache/*.zip

root@android:/sdcard # rm -f /cache/recovery/command

rm -f /cache/recovery/command

root@android:/sdcard # rm -f /sdcard/recovery.img

rm -f /sdcard/recovery.img

root@android:/sdcard # cd /

cd /

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 <

root@android:/cache/recovery # ls

ls

command

last_install

last_install_check

last_log

root@android:/cache/recovery # cat command

cat command

--update_package=/cache/update.zip

root@android:/cache/recovery # exit

exit

shell@android:/ $ exit

exit

C:\FTV>adb push update.zip /cache

3131 KB/s (415956067 bytes in 129.732s)

C:\FTV>adb reboot recovery

thanks for taking a look.
[Fire TV General] AFTVnews.com:
The only thing that looks off is the "ache/update.zip > command <" but I assume that's just from the command wrapping in your terminal since your cat of the "command" file looks correct.

adb sometimes does a weird thing where the file you push stays in memory and doesn't actually get written to storage. It's possible your update.zip is not ending up in /cache. Hopefully that's all that is happening here.

Try this...

Run these commands again to remove any files left by your previous attempt:

rm -f /cache/*.bin
rm -f /cache/*.zip
rm -f /cache/recovery/command
rm -f /sdcard/recovery.img

Go through all the steps in the guide again, but skip the "If downgrading fails" portion. Now, after you push the update.zip but before you you do the last step where you run "adb reboot recovery", run the following:

adb shell
su
ls -alh /cache

The last command will print the contents of "/cache" and the file sizes. Check that update.zip is there and that the file size looks right. Then cross your fingers and finish off with:

exit
exit
adb reboot recovery

The act of running "adb shell" after you push the file should complete the push process if it was infact keeping the file in memory. Let me know if it works and I'll update my guide.
[Fire TV General] cardboardbox:
Did this but I'm still stuck at the white amazon screen. :( Maybe I'm the first one to have a 51.1.1.0 that can't be downgraded? I'm headed out of town but will try again in a couple days.
[Fire TV General] ultronwar:
Can this be done on the UK fire tv's or does it require an already rooted fire? using the windows 7 method I mean
[Fire TV General] rotor00ter:
UK fire TV's cannot be rooted and therefore cannot be downgraded. You will have to wait until someone figures out a way to root the new firmwares.
[Fire TV General] cardboardbox:
I tried this again but still no luck. Do you think if I were to exchange for a different AFTV I might have more luck?
[Fire TV General] Y314K:
Need the following info...

Rooted w/ BusyBox installed: ?

CWM aka Custom Recovery installed: ?

Version of FW (PreRooted or not) before you tried downgrading: ?

OTA updates blocked: ?

Router blocking two IP update addresses: ?

Which FW version did you choose for the downgrade (Gets renamed to update.zip): ?

Any other info that might be useful: ?
[Fire TV General] cardboardbox:
Sorry for the delay, answers in purple above.
[Fire TV General] Y314K:
k, since you where able to try a second time. Then even on the white screen you can adb to your FireTV.

This is from one of the comments over at AFTVNews.com

Forgot to metion. First power cycle the FTV. Unplug the power for like 2 minutes and replug in before doing anything...

So I would use the Amazon FireTV Utility App v0.28 (Just make sure you input the IP from your FTV) unzipped to the C:\FTV and do a "Install Recovery Image". The image that you would be installing is already in the package in the C:\FTV\Recovery\ named "recovery-stock-51.1.0". Now this would mean that you would be unrooted (and you probably already are) so make sure your IP is blocking both IP's. Then I would try to flash the stock FW again with the app afterwards too. Redownload the FW: 51.1.0.1_user_510055620. And us the app to "Upgrade/Downgrade Firmware". Make sure you point to the right FW image. Then I would do clean cache's & do a Factory Reset from recovery. Make sure you give the app plenty of time to complete the process.

Try first to only do the first part "Install Recovery Image". And see if that cleared things up like it did for Phil. Although it seems you tried two FW's.. So I think u'll need to do that part too. Make sure you document any errors or problems you see. Make sure you have patience with the app & don't close it before it's down doing the task you ask. If successful then you'll need to go thru the rooting process like if it was a new FTV. Let me know if you have any ?'s before you try stuff...
[Fire TV General] bovoro:
I have in a similar situation , I received my aftv today and come with 51.1.1.0_user_511070220 and I tried to install cwm from Amazon fire tv utility 0.28, without downgrading or uploading fw version ,as it . the Amazon just reboot and I wasn't able to enter recovery options like wipe etc etc etc , only get the screen with a picture of a fire tv with the legend the system update was not succefull. I've tried reflash stock recovery with no success ,there is a possibility that was corrupted the recovery partition ?
[Fire TV General] Y314K:
Maybe... But will need more info then that....

Need the following info...

Can you still adb into your FireTV: ?

Rooted w/ BusyBox installed: ?

CWM aka Custom Recovery installed: ?

Version of FW (PreRooted or not) before you tried downgrading: ?

OTA updates blocked: ?

Router blocking two IP update addresses: ?

Which FW version did you choose for the downgrade (Gets renamed to update.zip): ?

Any other info that might be useful: ?
[Fire TV General] bovoro:
Rooted with bussybox

Recovery: unsuccessful cwm and reflashed stock recovery

Fw :original out of box 51.1.1.0_user_511070220

Ota updates blocked at beginning , now enabled same router ip enables now ,and never tried to downgrade since recovery is broken

---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------

I think my mistake was I. Dont do a downgrade
[Fire TV General] Y314K:
Still missing some info. But DO NOT unblock the 2 IP's on your router. Yes on your FTV you needed to downgrade FW first to install CWM.
[Fire TV General] bovoro:
I blocked right now

---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------

I'm trying to downgrade to 5.1.1.0.2 510058520 renamed to update.zip and doing the steps . in step 8 run the command cd /cache/recovery they say /cache/recovery: Not a directory
[Fire TV General] cardboardbox:
I again tried to change recovery but cant. I get the blue screen that says the the system update failed and then the AFTV restarts.

I tried resetting back to factory defaults and then tried again but still no luck.
[Fire TV General] Y314K:
I would go all the way down to 51.1.0.1_user_510055620 . But that is just me. All my FTV's come with that FW.
[Fire TV General] bovoro:
Mmm the recovery in cache is a file or folder , in my cache folder is a file
[Fire TV General] Y314K:
So the factory reset was done within the stock recovery. Does it tell you what version of recovery it is ? Does the stock recovery you are able to go into have the option to install from zip ??

---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------

Thought it was suppose to be a .zip Gonna have to pick [MENTION=3991724]rbox[/MENTION] brain on how to get your FTV's back to normal....
[Fire TV General] bovoro:
I already did a factory reset from stock recovery I'm start from beginning
[Fire TV General] Y314K:
So yours got past the white screen & logo ?
[Fire TV General] bovoro:
Yes I tried a method manual to install recovery.img
[Fire TV General] Y314K:
K, downgrade FW & reroot & install CWM.. You should be set...
[Fire TV General] bovoro:
So I need to do everything again root , busybox , xposed, downgrade , flash cwm and then flash a prerooted img
[Fire TV General] Y314K:
Yes.. It's like you just got the FTV out of the box. Keep blocking IP's.. What FW is your FTV showing is at now ?

---------- Post added at 12:56 AM ---------- Previous post was at 12:55 AM ----------

Are you able to see what is in your /cache/recovery folder ??
[Fire TV General] bovoro:
51.1.1.0 511070220

---------- Post added at 07:02 AM ---------- Previous post was at 06:57 AM ----------

Now seems good no errors in commands I'm sending update.zip now ,this take long , it's possible to send files via usb adb?
[Fire TV General] Y314K:
No, just do it like it says on the first page. Doesn't take hours.. lol Just minutes.
[Fire TV General] cardboardbox:
I have no idea why but I just downgraded, here's what I did:

1. Found this http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/ and beat on my keyboard enough until I got into the stock recovery. From there I foolishly tried sideloading recovery.img. That didnt work and it didnt seem like I could do anything, couldnt adb connect either.

2. So I restarted my AFTV. It got stuck on the second amazon loading screen, went to get ready for bed, came back, still stuck. So pulled the power again and restarted.

3. Just for fun I let AFTV Util try to downgrade firmware again and this time it worked.

4. Rooted again and changed to CWM recovery.

Tmw I'll try upgrading firmware! I cant do anything in CWM with the remote or my keyboard, have to figure that out tmw. Used adb reboot to get out of CWM.

Thanks!
[Fire TV General] Y314K:
I am just glad both of you are on your way to a CWM FireTV... CWM needs a USB keyboard. You can only use the arrows keys, main Enter key & ESC key as back key.
[Fire TV General] sajid44:
Need help

Looks like I have bricked my firetv.

I had CM recovery and pre rooted latest firmware installed.

Somehow XBMC stopped working so I went into CM recovery and foolishly wipe data and format system.

Now when I restart, it is stuck at white amazon screen. It does not even go to colorful firetv screen.

Cannot connect via adb, tried alt, prnt scrn + I but nothing happened.

Please help if it is still possible to debrick.
[Fire TV General] cardboardbox:
I would restart a few more times and keep trying alt + prtscn + i.

The first time I tried it I didnt get it to work either.

---------- Post added at 10:42 AM ---------- Previous post was at 09:55 AM ----------

Keyboard worked today, guess I just had to reboot. I've successfully upgraded to 51.1.4.0. Finally!
[Fire TV General] rbox:
Is Netflix working for you?
[Fire TV General] cardboardbox:
I dont have an account but I can try running the app.
[Fire TV General] rbox:
The problem is with trying to play stuff. Thanks though. I'll just add a warning that Netflix is probably broken.
[Fire TV General] Kaufhanz:
Hi,

im from Germany and my English isn´t the best. My Problem my German Fire TV arrived yesterday with Firmware 51.1.40user514006420 and Kodi crasht if i start it. My Idee was root but Towelroot doesn´t work. Can i manually downgrade by the manuals from Site 1?

With my Firmware nothing will working, playstore, root, kodi.....! :confused:

Please Help
[Fire TV General] Y314K:
XBMC aka Kodi v13.xxx should work. You can even boot directly to it thru LLama even when not rooted. Most have reported best success with SPMC XBMC which I think is in the Amazon Store. Not sure if XBMC with the launcher included would work correctly. And Kodi v14 betas will NOT work. Also PlayStore & Root will not work on any 51.1.4.0 FW. And you can only downgrade if you where already rooted. So that won't work. Try the 1MobileMarket : http://market.1mobile.com/ app store as an alternative to the PlayStore. I think I've seen it on unrooted FTV's. That one should sideload fine.

Uninstall the Kodi you are trying or leave it on there and try this one: http://www.tvaddons.ag/tvmc-android/ It should come preconfigured. If that one works then all other v13.xxx kodi's should work too.

Use this App to easiley sideload install the 1MobileMarket & TVMC-Android XBMC apk's : http://xdaforums.com/showthread.php?t=2736774
[Fire TV General] DaveTO:
I'm currently on 51.1.4.0_514006420 updated prerooted rom and I would like to downgrade to 51.1.3.0_513011520 prerooted. I also have CWM installed.

What would be my general steps in doing this in the easiest way possible?
[Fire TV General] Y314K:
Guessing you want the old NetFlix app ?? Just use the AFTV Utility to sideload to SDCard the PreRooted FW version you want and install it with CWM.
[Fire TV General] DaveTO:
I'm actually trying to get location services to be faked. Everyone on these forums that has gotten the Settings.apk to "enable" the location services on FTV has been on the 51.1.3.0_513011520 and I'm on a later version.

Is anyone here on 51.1.4.0_514006420 and can try to use the settings.apk to enable the location services? Would be awesome if it were possible to "turn on" this without any app, just by editing some files or something.

Otherwise if I want to downgrade, do I just download the prerooted rom for 51.1.3.0_513011520 and use the AFTV utility Upgrade/downgrade section, rename the prerooted 51.1.3.0_513011520 to update.zip? then what?
[Fire TV General] Y314K:
Don't rename it (You only rename it when doing the manual ADB guides)... And try to downgrade to the last 51.1.3.0 PreRooted FW aka "bueller-51.1.3.0_513011820-rooted.zip". Don't go to old on the FW or there might be a possible recovery issue. Just install the FW from the app.. As long as you are going from PreRooted to PreRooted you should be good... And do the "Disable OTA Update" after you downgrade just because...

And be patient since you are moving 400Mb + of data over ADB.. Can take minutes... 2-4 minutes in my case..
[Fire TV General] kywildcat:
I'm starting at “If downgrading fails” and It Errors out on the adb push update.zip /cache command. cannot stat ‘update.zip': No such file or directory. I have never had a successful upgrade and I’m on 51.1.1.0_user_511070220. At the end of this log, i was just trying different directories.

C:\FTV\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb connect *********

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

connected to *********

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:/ #