yashsingh1/xdaforums huggingface dataset:
[Fire TV Q&A, Help & Troubleshooting] wastate2014:
I have had this issue on Android TV also. I ended up clearing the cash and restarting along with a reboot of the network? But it has been happening on and off for awhile.
[Fire TV Q&A, Help & Troubleshooting] KLit75:
Well that fix lasted 2 full days but now it's back. Outside chance my tinkering (trying to get samba working properly) cause it but that's a little far fetched. It's not the hdmi cable. I'm actually using a brand new one that came with the Wii U.

The bedroom aftv also had trouble playing Netflix last night.

Specs-wise this is the best set top box I ever owned. When it's running well it's awesome. But overall it's easily the least stable streamer I've ever had...and that's a long list of devices. Got a old roku xd (maybe 15 bucks on eBay) I plug it in and can count on it to work all the time. It's not as fun as aftv but thinking about putting it on the side of bedroom aftv so my wife doesn't get angry when she wants prime or Netflix.
[Fire TV Q&A, Help & Troubleshooting] lowbee:
I am watching this thread hoping you guys would find a reason/solution for this issue. I am emphatic to the problems you are having but am also a little surprised at them because I am NOT running into any of this issues with any one of my 3 FTV's. Fingers crossed

All of my FTV's are rooted and they run XBMC, Netflix, Amazon Prime. I don't even bother shutting XBMC down or rebooting the AFTV. Netflix just works. O, btw, I am running pre-rooted 51.1.4.0_514006420 firmware on all of them. Once in a while (maybe once every 10 days) Netflix will have the error message saying "We're having trouble playing this title right now. Please try again", all I do to get it to work again is to exit the app then restart Netflix or sometime I may need to login again and that's it.

Good Luck and hope you find a solution. Have you try rebooting your router ?
[Fire TV Q&A, Help & Troubleshooting] wastate2014:
I do not think it is Fire TV? The fact that I have had it on more than one device proves that. Somehow the authorization cache is getting corrupted? When I clear the data and reauthorize it seems to correct it until it corrupts again? My network reboot is just a extra step to be sure. The only other thing I can think of , It seems to be associated with devices that remain on(standby only?)
[Fire TV Q&A, Help & Troubleshooting] Neo3D:
I don't see how that would help but it's worth a try. We have Netflix running perfectly fine on these devices, which are on the same home network:

desktop HTPC

m17x R4

m14x R2

Samsung Note 4

Samsung Note 3

Samsung Note 10.1 2014

Inspiron 3147

PS3

Asus Chrome Box

The ONLY device we have EVER gotten this error on is the AFTV. So, I'm inclined to think it's an issue with the AFTV.
[Fire TV Q&A, Help & Troubleshooting] Neo3D:
Bollucks! I tried rebooting my router and it still gives me the same error :(

This is very frustrating. Netflix works perfectly fine on all of our other devices except for this AFTV. Makes me wonder if Amazon has some deliberate bugs in it so you are forced to use Prime, which works perfectly.
[Fire TV Q&A, Help & Troubleshooting] ashsha7877:
So after seeing so may folks having issue with netflix, i decided to try and i did not have any issues.

However, this morning when i tried to watch a free episode on prime i get "Unknown error", i got the same error message when i tried to watch a movie trailer so few min later i tried again to watch the episode and it worked fine but now when i try to watch a movie trailer i get messages "Your internet connection is really slow, blah blah, blah" with the open watch later or keep watching, when i select keep watching i get cursor that keep going in circle but the preview never plays.

i did test my speed and i am getting at least 18mbps download and 11mbps upload speed, not the fastest but it is more than fast enough to watch full HD movies.

There is definitely something wrong, probably some firmware bugs, i am running pre-rooted 51.1.4.0_514006420 updated.

Thank you
[Fire TV Q&A, Help & Troubleshooting] Neo3D:
Thanks for testing! Good to know I'm not the only one with problems.

I'm running 51.1.4.1_514013920fixed
[Fire TV Q&A, Help & Troubleshooting] ECEXCURSION:
I'm also having the same issue. Also running that version of code.
[Fire TV Q&A, Help & Troubleshooting] dillfever:
I'm on the same F/W as u Neo but I'm running SPMC and the netflix that I side loaded(white) works just fine, the netflix that was already on the box(red) never worked gave me the I don't own the app crap.....but like I said netflix works fine.....dill
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
I'm having this problem on the same prerooted firmware as well. My unrooted AFTV works fine. I'm beginning to think it is the firmware causing it.
[Fire TV Q&A, Help & Troubleshooting] KLit75:
For me it's as much prime as it is Netflix. Last nite I came here to report the Netflix "tiny screen" error but someone beat me to it & started their own thread. Prime has stopped working on both devices (clear data 3 times and unplugging replug).

Today just scrolling the aftv homescreen it rebooted itself. This was a first. I did, awhile back, forget to disable updates after a factory reset and it booted to cwm, but this time it just rebooted.

I'm running the latest rbox firmware with unlocked boot loader on one and the firmware just before the latest on the other. I purposely set my keymaps to not stop playback with the back button but make sure to not only quit the video but also force stop xbmc before loading Netflix or a prime video. And over months I've become accustomed to rebooting the bedroom aftv before using it. Both boxes have had multiple factory resets. I can't make sense of it.

The craziest part is xbmc has been perfect. It works way better than the 2 paid services. Sorry I'm just kinda stating problems with no solution. I'm hoping with more info someone might get an idea.
[Fire TV Q&A, Help & Troubleshooting] ellecsor:
Same issue here. I had to force stop TVMC in order to get Netflix to work.

So what is the proper way to exit TVMC? I normally just pause the video and hit back or home.
[Fire TV Q&A, Help & Troubleshooting] KLit75:
I've tried just about everything I can think of. I ALWAYS force quit kodi first but two days ago I got "fast reboot" it simulates a reboot, stopping and restarting processes. I still have issues.

It seems to happen MUCH more if the device sits idle for awhile (don't matter if it sleeps or not) I can play kodi and netflix back to back all nite with no issues. Come back to it hours later and I can guarantee netflix and/or prime won't play.
[Fire TV Q&A, Help & Troubleshooting] ellecsor:
Interesting. I'll test it out over the next few days. So far I know for sure Netflix won't work if I just hit the back or home button out of kodi. If I force stop or press the power/exit button in kodi (which I just discovered now), Netflix will work.
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
My Netflix doesn't work even if I reboot. I can't get it to work at all.
[Fire TV Q&A, Help & Troubleshooting] rontonomo:
If you just pause the video you will most likely get the error, you need to make sure to always stop what ever is being used in xbmc before launching into netflix. also another GREAT tip would be to get a timer and set it to automatically power cycle the device every night when you are sleeping. It seems there is a memory leak in xbmc on AFTV and leaving it on to long causes all sorts of issues (such as but not limited too stuttering during playback of hd content). Also to fix error problems clear cache and data each 3 (YES YOU MUST DO IT 3 TIMES) in amazon video app. If you do these things you should not run into any problems.
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
I've tried clearing the data/cache for Amazon Video and rebooting. This didn't seem to do the trick. I've cleared the data for Netflix. I've uninstalled and reinstalled Netflix. I've also uninstalled Netflix, removed it from cloud, and reinstalled it. I disabled AdAway thinking for some reason that might have been causing my Netflix issues, but that didn't seem to fix it either. I haven't sideloaded any other applications other than Kodi, and primarily use this for Kodi, Amazon Prime Video, Netflix, Twitch, and Hulu. Everything else works just fine. As a note, Netflix works fine on my 2nd AFTV which is not rooted and is on the latest stock firmware. Netflix also works fine on all three of the computers in my home. I use Netflix frequently, and not being able to watch it in my living room with my wife and daughter is a hassle.

Does anyone have any other advice for how I might go about resolving this issue? Nothing I've done seems to work... It gets between 1-10% loading the video, and then says "We're having trouble playing this title right now. Please try again."

As stated before, I'm running the latest prerooted stock firmware available from this thread:

http://xdaforums.com/fire-tv/development/prerooted-stock-images-t2882337. I confirmed that the md5 for the 51.1.4.1_514013920+fixed firmware matches the md5 of the zip that I used to install the prerooted firmware both before installing it on my AFTV, and just now to be 100% sure.

I'm really at a loss and could use some guidance from others. Thanks in advance for any consideration.
[Fire TV Q&A, Help & Troubleshooting] lowbee:
I have 3 AFTV's all rooted running firmware version 51.1.4.0_514006420+updated and I never have any problem with Netflix and/or Amazon Prime, so it might worth a try to roll-back to an older version of the firmware.

edited: I run XBMC 13.2 with the power saving option enabled to shutdown XBMC after 60 minutes of inactivities, not sure if this is related
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
Thanks. I will try downgrading this weekend and will post the result here.

Before I do this, correct me if I'm wrong... All I need to do is flash the zip file in recovery, correct?
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
Downgrading to that firmware resolved my issue with Netflix. I'd recommend anyone having issues to try it.
[Fire TV Q&A, Help & Troubleshooting] lowbee:
Glad to hear it works out for you. Wait a few days to see if the problem is completely gone then report this to [MENTION=3991724]rbox[/MENTION] so he can find out what happened to his latest custom ROM with regards to Netflix.
[Fire TV Q&A, Help & Troubleshooting] Macpatto:
Guys,

I can tell you that downgrading from the pre-rooted rom 51.1.4.1_514013920+fixed to a this earlier rom version 51.1.4.0_514006420+updated.

Fixed the problem of Netflix, but it broke the ability for me to see my pics and music, but that's no a priority for me right now.

Any how, its worth the try to get in touch with Rbox and letting him know to take a look to the latest pre-rooted rom and fix the bug for Netflix.

Hope that helps for everyone now to be able to watch Netflix.

Good luck everyone !
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
Since I don't have 10 posts, I'm unable to post into the developer's forum. I sent rbox a PM requesting for him to look at this thread for the details of the problem we are experiencing. If anyone else can post in the development thread (http://xdaforums.com/fire-tv/development/prerooted-stock-images-t2882337), it would probably be a good idea.

Thanks everyone for your help on this.
[Fire TV Q&A, Help & Troubleshooting] Macpatto:
Guys,

I can tell you that downgrading from the pre-rooted rom 51.1.4.1_514013920+fixed to a this earlier rom version 51.1.4.0_514006420+updated.

Fixed the problem of Netflix, but it broke the ability for me to see my pics and music, but that's no a priority for me right now.

Any how, its worth the try to get in touch with Rbox and letting him know to take a look to the latest pre-rooted rom and fix the bug for Netflix.

Hope that helps for everyone now to be able to watch Netflix.

Good luck everyone !

UPDATE:

THIS MY SOUNDS STRANGE BUT!!

I have just reverted back to pre-rooted rom 51.1.4.1_514013920+fixed and for some reason that I can't explain. Netflix started to work with out hassle.

So, if anyone wants to try that and see if works for you, then it must be something to do when the rom.zip it is push to sdcard the first time?. Who knows..

Good luck!
[Fire TV Q&A, Help & Troubleshooting] KLit75:
Just some questions that may seem irrelevant but could potentially make things clearer...

--why did you switch back if it was working in your unedited post?

--how long have you been using the current firmware?

For me it seems to happen less frequently so I'd probably need at least 2 days to test it. Another potential piece of info that might be useful is the Netflix ninjas app apparently is giving people trouble on other platforms. Reviews are sometimes misleading particularly for such common apps, but from memory I heard what I felt was a disproportionate amount of negative ones.
[Fire TV Q&A, Help & Troubleshooting] Macpatto:
The reason I switched back was cause 51.1.4.0_514006420+updated broke the ability for me to see my pics and music. And be honest I didn't test it long enough on that rom., just about a day or so... and I have been on the latest rom for 4 months in which I was't able to use Netflix then..

The Netflix I am using is the one with the White Logo from Amazon, and it was the same before.

As I said, for some strange reason reverting back seemed to solve the problem.
[Fire TV Q&A, Help & Troubleshooting] KLit75:
Yeah. That's actually what I figured, after that fact. If you remember it'd be great to report back in like a week to see if it still works. Sometimes I'll go a few days without the error but sometimes it's multiple times daily. On the other hand, is that one of the versions that doesn't require boot menu? I'm just wondering if we can temporarily get rid of it. If it's needed for something like android tv I'd put it back but for my needs all it does is add more time to boot on a device that I reboot frequently.
[Fire TV Q&A, Help & Troubleshooting] Macpatto:
Ok, I will report back in about a week if there's any changes..

As for he Boot Menu.. I guess you can always remove from the latest rom. But, according to Rbox, its necessary when there is an update to a newer pre-rooted rom.
[Fire TV Q&A, Help & Troubleshooting] jaaaay:
Hello,

I just wanted to post and give you an update as to what I have found so far today after running into the same issues as others here.

My setup yesterday ( I upgraded 2 FTV to 51.1.4.1 yesterday and started having issues with netflix)

2 FTV running bueller-51.1.4.1_514013920-rooted+fixed - netflix would not play videos as described.

1 FTV running bueller-51.1.4.0_514006420-rooted+updated neflix plays video just fine.

Please note that on both FTV's that I upgraded to 51.1.4.1, netflix told me I had to upgrade to the latest version, so I did. The one running 51.1.4.0 was already running Netflix version 1.1.1 build 125. The only other thing I did was install kodi-helix on both of the 2 upgraded FTV's and restore from backup of the 1 FTV for kodi config using FTV .38.

First FTV with 51.1.4.1:

Uninstalled Webkey ( it installed binaries on first start-up) as this was the only other app I installed and ran on the 2 FTV's, still no Netflix .

Downgraded FTV from 51.1.4.1 to 51.1.4.0 - Netflix plays as soon as I boot it up.

Upgraded back to 51.1.4.1 Netflix still works as expected.

Then I re-installed Webkey.. installed binaries, setup service, and remoted in.. Netflix still works fine.

Second FTV with 51.1.4.1:

Uninstalled Netflix and re-installed.. still no Netflix

Downgraded FTV from 51.1.4.1 to 51.1.4.0 - Netflix plays as soon as I boot it up.

Upgraded back to 51.1.4.1 Netflix still works as expected.

Didn't touch webkey this time, still setup and working with autostart.

Third FTV with 51.1.4.0

This already has Netflix version 1.1.1 build 125

Upgraded to bueller-51.1.4.1_514013920-rooted+fixed Netflix plays just fine.

That is what I have so far.. I will update later to see how things go...
[Fire TV Q&A, Help & Troubleshooting] lowbee:
Hum, makes me wonder if those people who are having Netflix problem have skipped the 51.1.4.0_514006420-rooted+updated version and went directly to 51.1.4.1_514013920-rooted+fixed
[Fire TV Q&A, Help & Troubleshooting] Neo3D:
I think that may very well be the issue! I will test this myself and update with results.
[Fire TV Q&A, Help & Troubleshooting] KLit75:
The rooting/downgrading process on my 2nd aftv was so tedious its hard to remember the exact process but on the 2nd aftv Im running 51.1.4.0 and I have issues, especially with prime. In fact just 5 mins ago I cleared data 3 times and unplugged. To be honest, I'm not certain clear data does anything rebooting doesn't at this point.

Its possible I skipped 51.1.40 on my other aftv but my point is it doesn't matter because I have issues with both. I'm running the latest on the other unit.

Btw--on a quasy related subject, what's the earliest firmware we can revert back to when boot menu is installed? Not that anyone would want to but can we go back anywhere we want when boot menu is present? Do we need to worry about having an unlocked bootloader and going back to previous versions? I'd assume not but since the later versions require boot menu and an unlocked bootloader I sort of worry about issues arising if you go the other way.
[Fire TV Q&A, Help & Troubleshooting] Neo3D:
*** SOLVED!! ***

Netflix finally works!

Thank you to jaaaay & lowbee for their collaborative effort in helping to solve this issue!

Here's how to fix your Amazon Fire TV:

Downgrade to 51.1.4.0_514006420-rooted+updated

Launch Netflix and make sure it works

Upgrade back up to 51.1.4.1_514013920-rooted+fixed

Launch Netflix and make sure it works
[Fire TV Q&A, Help & Troubleshooting] Macpatto:
Neod3D..

That's exactly what I did and Netflix is working good.. Now, we have to wait few more days or weeks and see if that it is a total solution to the problem.

I am wondering if others that are still on http://www.mediafire.com/download/lg1l5q00x1lq9b4/bueller-51.1.4.1_514013920-rooted+fixed.zip will solve the problem by re-pushing the rom.

Or if its necessary to do the Downgrade and Upgrade steps.
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
Just FYI to everyone here, rbox agreed in a PM to me that going straight to the latest firmware without flashing the earlier one could potentially cause these types of issues. Seems to be a confirmed fix. Thanks everyone.
[Fire TV Q&A, Help & Troubleshooting] Macpatto:
Well, I can tell you that I've followed every single step on how to root, flash, downgrade and upgrade roms one after the other according to Rbox and all the AFTNEWS starters guides and I get the error.
[Fire TV Q&A, Help & Troubleshooting] chaoticyeshua:
Have you tried flashing back to 51.1.4.0_514006420+updated? After doing that, Netflix started working fine for me. I even upgraded back to 51.1.4.1_514013920+fixed last night and it worked still after that.

I don't think I noticed this when originally installing the prerooted firmware, but rbox says in the first post here that you need to install 51.1.4.0_514006420+updated before installing 51.1.4.1_514013920+fixed. It doesn't say what will happen if you don't, but he seemed to imply in the PM to me that not doing so could have caused this problem.

Edit: rbox's PM to me, for reference...
[Fire TV Q&A, Help & Troubleshooting] Neo3D:
Thank you for confirming this! Does anyone know the owner of:

http://www.aftvnews.com/

The owner should include in his guide this discovery that you have to:

NOT SKIP this ROM version and install it: 51.1.4.0_514006420-rooted+updated

Launch Netflix and make sure it works

Now, upgrade to 51.1.4.1_514013920-rooted+fixed

Launch Netflix and make sure it works
[Fire TV Q&A, Help & Troubleshooting] Macpatto:
Yes, off course I did instal 51.1.4.0_514006420+updated before updating to 51.1.4.1_514013920+fixed.

My comment was that I've followed all the steps in 1st place and did not get lucky with Netflix.

But, this is I've done on this post few days back and yes it worked.. http://xdaforums.com/showpost.php?p=58554103&postcount=37.

Netflix working good and steady so far..
[Fire TV Q&A, Help & Troubleshooting] KLit75:
I'm actually having issues other than Netflix on 51.1.4.1

I posted recently at length. Like you I'm pretty sure I followed the guides to a tee but don't recall reading the updates needed to be incremental. This is my older aftv and it's possible I skipped the prior release OR saw 51.1.4.0 was having issues and I skipped to 51.1.4.1 (the timing would've been right around late november but I can't recall exactly)

My concern was boot loader but apparently it can remain unlocked even if you go back to a version that didn't have unlocked option.

I'm thinking the cleanest way to correct issues for me MIGHT BE to go all the way back to the earliest firmware, then update from there. BUT, if that's even possible (or advisable) I worry about things like the new Netflix not being compatible.

So unless someone chimes in...here's what I'll do...

Leave boot loader unlocked and flash 51.1.4.0

Are you guys wiping dalvik cache & cache before flashing? Is this something that should be done when you upgrade, downgrade ...both?

I just want some reassurance because this aftv has been displaying concerning behavior then it runs perfect without any intervention from me!
[Fire TV Q&A, Help & Troubleshooting] Neo3D:
I did not do any of that.

My cousin gave me her AFTV and we rooted it, using the incremental upgrade path and her Netflix and Amazon TV both work fine. The whole thing runs fast, smooth and stable! Kodi runs awesome on this thing!
[Fire TV Q&A, Help & Troubleshooting] KLit75:
Thanks for the reply. But in your scenario, you're starting from scratch. If I bought one tomorrow, knowing what I know now, I would probably start low then keep flashing one after another until I finally have the latest.

I'm going backward first.

You know I think I'll just flash 51.1.4.0 And see how things go. That version runs pretty well on my other aftv (minus the netflix issue) Then wait a couple of days and if all is well flash the next one.

If after that I'm having issues I'll probably do a cwm factory rest (again) then flash from the first firmware all the way to present. There'd be know chance of missing anything important if I go that route. I just don't know it's necessary and still a bit unclear on how far I should go back.

Actually--I got onboard with rbox firmware very early so If I missed anything it was most likely one of the later updates (probably 51.1.4.0)
[Fire TV Q&A, Help & Troubleshooting] KLit75:
I just flashed 51.1.4.0. Now both my aftvs are on the same firmware. So right after installing it I tried Netflix and it worked fine (not surprising since it was just rebooted for the firmware install)

10 minutes later my wife tells me Netflix isn't working on the living room aftv. I expected it to be " Netflix is unable blah blah" error. But it wasn't it was an internal player thing--a new one! So I handed her the apple tv remote and told her to use that. I'm done for awhile.

Think I'll wait a few days to see how you guys make out before upgrading again.

Perhaps keeping Netflix in the cloud while we change firmware then install it when it completes? Just a thought, but this is waaay too much work to fix something that no other device gives me issues with.
[Fire TV Q&A, Help & Troubleshooting] gopichandpai:
Attention [MENTION=5957312]AFTVnews.com[/MENTION]
[Fire TV Q&A, Help & Troubleshooting] AFTVnews.com:
Thanks for bringing this to my attention, however my ROM download page has always said "You MUST first install Pre-Rooted ROM version 51.1.4.0 before installing this version." next to the 51.1.4.1 listing. Also, my starters guide has always instructed you to explicitly install 51.1.4.0 before installing the latest 51.1.4.1 pre-rooted ROM.
[Fire TV Q&A, Help & Troubleshooting] cdmove:
I downgraded my ftv to 51.1.4.0_514006420-rooted+updated and Netflix still doesn't work. Is there anything else I can do?