Develop Bugs

New Firmware 51.1.4.0+ and OLD netflix app

I was wondering if anyone knows of a way to block amazon forcing you to update to latest netflix after upgrading the firmware?
Thanks to rbox I have all the necessary components to keep the file structure/firmware of 51.1.0.2 and be on latest 51.1.4.1, of course new netflix does not work on that, I removed and sideloaded an extracted netflix apk from older firmware for the FTV but amazon has something forcing you to update, it pulls up a message saying required update. Any way around this? I think the state i have my FTV in if I could launch the old netflix it would work, but I can't launch it without the amazon nag.
The reason I need to keep the old netflix is for some reason my FTV's do not play well with the new version at all, many errors/skips/fails to launch/logs me out etc. I tried latest 51.1.4.1 and still same issue. It's odd too cause I bought a new FTV from staples and rooted it and upgraded it before doing anything to 51.1.4.1 with new netflix and it works way better on that unit than any of my other ones. not sure why
Also, the new netflix will not put my FTV to sleep mode automatically after timing out. The old one would allow it to go to sleep mode while new netflix logs out of the user profile but leaves the app open and it sat overnight on netflix, This doesnt work very well for me. Any help/insight is appreciated!

Skater4599 said:
I was wondering if anyone knows of a way to block amazon forcing you to update to latest netflix after upgrading the firmware?
Thanks to rbox I have all the necessary components to keep the file structure/firmware of 51.1.0.2 and be on latest 51.1.4.1, of course new netflix does not work on that, I removed and sideloaded an extracted netflix apk from older firmware for the FTV but amazon has something forcing you to update, it pulls up a message saying required update. Any way around this? I think the state i have my FTV in if I could launch the old netflix it would work, but I can't launch it without the amazon nag.
The reason I need to keep the old netflix is for some reason my FTV's do not play well with the new version at all, many errors/skips/fails to launch/logs me out etc. I tried latest 51.1.4.1 and still same issue. It's odd too cause I bought a new FTV from staples and rooted it and upgraded it before doing anything to 51.1.4.1 with new netflix and it works way better on that unit than any of my other ones. not sure why
Also, the new netflix will not put my FTV to sleep mode automatically after timing out. The old one would allow it to go to sleep mode while new netflix logs out of the user profile but leaves the app open and it sat overnight on netflix, This doesnt work very well for me. Any help/insight is appreciated!
Click to expand...
Click to collapse
It's two separate apps, so if you leave the new one installed, the old one will still work. Unfortunately it won't show up in the main apps list and you'll have to open it like other sideloaded apps.

rbox said:
It's two separate apps, so if you leave the new one installed, the old one will still work. Unfortunately it won't show up in the main apps list and you'll have to open it like other sideloaded apps.
Click to expand...
Click to collapse
Just tried that, it does show up as a seperate as you said, the problem is when I launch it, I get an amazon popup that says "Launch newer Netflix Instead. you have installed a newer version of Netflix. This old version is no longer supported. Please uninstall and launch the new version instead. And two options, uninstall now or uninstall later"
Also looking at manage all apps list now it only shows the old netflix, I think it overwrote the newer version or something.

Skater4599 said:
Just tried that, it does show up as a seperate as you said, the problem is when I launch it, I get an amazon popup that says "Launch newer Netflix Instead. you have installed a newer version of Netflix. This old version is no longer supported. Please uninstall and launch the new version instead. And two options, uninstall now or uninstall later"
Also looking at manage all apps list now it only shows the old netflix, I think it overwrote the newer version or something.
Click to expand...
Click to collapse
That's odd. Originally, before I fixed Netflix... I let it update to the new Netflix, I used it and it didn't work, and then I did 'adb install' to install the old one, and went to the apps list and it "just worked". It could be that they've since updated something to prevent that from working... Why not just flash 51.1.3.0?

rbox said:
That's odd. Originally, before I fixed Netflix... I let it update to the new Netflix, I used it and it didn't work, and then I did 'adb install' to install the old one, and went to the apps list and it "just worked". It could be that they've since updated something to prevent that from working... Why not just flash 51.1.3.0?
Click to expand...
Click to collapse
My other FTV's are on 51.1.3.0 for that reason, I had just flahsed this one with latest 51.1.4.1 in hopes new netflix would work any better than it did on 51.1.4.0, but it seems not much changed (for me). I wanted to keep the new firmware for some of the features, remote on phone, sleep button, prime music and whatever bug fixes etc they've done in the background, also moving forward I don't want to be forever stuck on 51.1.3.0. But it'll have to do for now I guess.

@rbox do you still happen to have the APK you adb installed that showed up seperately? I wonder if it's just my .apk I have

Skater4599 said:
@rbox do you still happen to have the APK you adb installed that showed up seperately? I wonder if it's just my .apk I have
Click to expand...
Click to collapse
It's the same one you have, it hasn't been chagned in forever. Just pull it off one of your other boxes.

Ok, yep same place I got the one I have. I just re-pulled it and the /data/data folder just to see, same thing.
Thanks for the help/input rbox

I hope this is the right thread for this -
I just updated to the pre-rooted 51.1.4.1_514013920 firmware. The new netflix app won't play anything. I tried uninstalling it, deleting it from the cloud, rebooting, and reinstalling. Still nothing.
Any ideas? I was fine with the old app if someone could point me to the APK. I unforunately don't have any other devices with the old APK.
I appreciate any help.
---------- Post added at 11:08 PM ---------- Previous post was at 10:15 PM ----------
sjwaste said:
I hope this is the right thread for this -
I just updated to the pre-rooted 51.1.4.1_514013920 firmware. The new netflix app won't play anything. I tried uninstalling it, deleting it from the cloud, rebooting, and reinstalling. Still nothing.
Any ideas? I was fine with the old app if someone could point me to the APK. I unforunately don't have any other devices with the old APK.
I appreciate any help.
Click to expand...
Click to collapse
Nevermind. I ended up wiping and installing 51.1.4.0 because I don't think I ever did that. Then I reinstalled the boot menu and flashed .1 and everything is working.
I'll leave this here just in case anyone else makes the same bonehead mistake. Thanks for the hard work rbox, appreciate the rooted firmware releases.

AFTV1 Downgrade issue

I've seen that some people were able to successfully downgrade AFTV1 after rooting with Dirtycow. I'm able to get root, but downgrade doesn't seem to work and I don’t know what I’m doing wrong.
I have an amazon fire TV V1 with 51.1.4.0_User_514006420 software version. I downloaded the 51.1.0.2_user_510058520 update, renamed it to update.zip, followed the guide (here: http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/) for changing the ROM. When I do adb reboot recovery I get this message:
“System update was not successful. Your amazon fire tv will restart in a few minutes and should resume normal operation.”
When it restarts, it’s still on the same version I had. I’ve tried pushing the stock recovery image like the bottom of the upgrade/downgrade guide suggested, but it doesn’t seem to work. Does someone have any other ideas on how to get this to work?
I checked that the update checks out with the md5 hash. I just can’t get it to work. What should I try to do next? Is there a better guide? I'd like to install a pre-rooted ROM.

On the off chance that Amazon changed the 51.1.0.2 image they are serving, try downloading and using the one from here. Then follow my guide here to install it. You should also check the md5 hash value of the 51.1.0.2 image AFTER it has been transferred to the FTV1 by following this guide.
If you still have problems, copy and paste your entire ADB/shell text here so I can see if you did anything wrong.

@AFTVnews.com thanks for the response! I checked the md5 and it seemed to have matched. I re-ran through the steps an it appears I may have put command in cache instead of cache/recovery. It pushed successfully.
Now... it seems like that version of AFTV is strange. It has a lock screen and my aftv remote won't allow me to unlock it. Here is an image of what I see: Locked Amazon fire TV Screen so I can't open it to run towel root. Any ideas?
Update: I was able to get passed the lock screen by clicking a bunch of buttons on the remote at the same time. I'm rooted again! I'll continue the guide! Thanks for your work on this!
Update2: I'm running the latest version of the rooted software. Thanks for the guides!

uofirob said:
@AFTVnews.com
Update2: I'm running the latest version of the rooted software. Thanks for the guides!
Click to expand...
Click to collapse
Awesome. Glad it worked out.

Last night, I stopped after the custom latest rooted version of the ROM was installed. I keep getting "Amazon is unable to connect to the service" when going to the different menu options. Do I have to disable my firewall rules on my router, or was it just an oddity?
AFTVnews.com said:
Awesome. Glad it worked out.
Click to expand...
Click to collapse

I confirmed that I'm still getting the unable to connect to service last night. Should I just do a factory reset? Would that help? At this moment, the only way for me to launch apps is to go through System -> Manage Applications and it's really annoying. I was able to confirm that Kodi was able to connect to the internet, so I know that it's not the connection.

uofirob said:
I confirmed that I'm still getting the unable to connect to service last night. Should I just do a factory reset? Would that help? At this moment, the only way for me to launch apps is to go through System -> Manage Applications and it's really annoying. I was able to confirm that Kodi was able to connect to the internet, so I know that it's not the connection.
Click to expand...
Click to collapse
Since you're rooted and on the latest prerooted ROM, you should remove the domain blocks on your router/firewall. It sounds like that's the issue. Just be sure you have done method 1 at the very least from my update blocking guide. You can also do method 5 to be extra safe.

I tried removing the firewall blocks but I still get "We are currently unable to contact our servers." Should I re-add the firewall blocks and factory reset?
UPDATE: I was able to resolve this by signing in to my amazon account. Apparently for some reason it signed me out. Thanks for all of your help!
AFTVnews.com said:
Since you're rooted and on the latest prerooted ROM, you should remove the domain blocks on your router/firewall. It sounds like that's the issue. Just be sure you have done method 1 at the very least from my update blocking guide. You can also do method 5 to be extra safe.
Click to expand...
Click to collapse

Netflix always exits randomly since I upgraded to the latest version！

Hi,
I have several fire TVs, one of them is rooted. since upgraded to the latest version, when I play netflix, after a while , netflix always exit randomly.
why?

any hint?

I'm having the same issue since I downloaded the latest version and it's not just Netflix. I'm having issues with tubi.tv doing the same thing. Also Netflix has problems loading or playing a title. It's especially frustrating and irritating when you watching a show and it starts buffering. It goes to 25%, stops and I have to back out then go back in. It happens quite frequently since I downloaded the new version.

blackantt said:
any hint?
Click to expand...
Click to collapse
Melina69 said:
I'm having the same issue since I downloaded the latest version and it's not just Netflix.
Click to expand...
Click to collapse
Guys, please specify device, root, FW, etc.. Of you don't include specifics then it becomes a guessing game.
Netflix can be fanikie. When it acts up on me. On my latest FW PreRooted FTV1. I just go to the apps setting. Then do an App Stop & clean the cache. I leave Data alone. Since I prefer to not have to input the log in info. I also have the Apps auto update turned off. So I control when it updates. I only update if none of my other tricks work. As a last resort.

I didn't realize there was more than one kind of Amazon Fire TV. I have no idea what the specifics are. Netflix has never done this before until I downloaded the latest version. I don't believe the automatic updates is on since I never had to update it before. I don't know how to stop and clear cache. Never had to do that either. Maybe my version is different than yours. But I went to settings to see if I could figure it out.

Melina69 said:
I didn't realize there was more than one kind of Amazon Fire TV. I have no idea what the specifics are. Netflix has never done this before until I downloaded the latest version. I don't believe the automatic updates is on since I never had to update it before. I don't know how to stop and clear cache. Never had to do that either. Maybe my version is different than yours. But I went to settings to see if I could figure it out.
Click to expand...
Click to collapse
Now that there are TV's there are 5 type of FireTV devices.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201640900
You can clean the cache from the App Settings. In the Apps Management menu.

blackantt said:
Hi,
I have several fire TVs, one of them is rooted. since upgraded to the latest version, when I play netflix, after a while , netflix always exit randomly.
why?
Click to expand...
Click to collapse
Is it the rooted FireTV that exists randomly? My rooted AFTV1 box refuses to load now. I've uninstalled the app several times, prior to that cleared cache and data and nothing. It asks for my login info, accepts it, and then ultimately kicks me out with zero error messages.
If I saw the last update correctly, it was updated mid-June and I used Netflix last week. I thought I was the only one this was happening to, but it appears to be happening to others. I wonder if it's a root issue?

null0pointer said:
Is it the rooted FireTV that exists randomly? My rooted AFTV1 box refuses to load now. I've uninstalled the app several times, prior to that cleared cache and data and nothing. It asks for my login info, accepts it, and then ultimately kicks me out with zero error messages.
If I saw the last update correctly, it was updated mid-June and I used Netflix last week. I thought I was the only one this was happening to, but it appears to be happening to others. I wonder if it's a root issue?
Click to expand...
Click to collapse
If you are on FireOS 3 then yeah. Netflix probably made their latest Neflix app incompatible with old Android versions.

Y314K said:
If you are on FireOS 3 then yeah. Netflix probably made their latest Neflix app incompatible with old Android versions.
Click to expand...
Click to collapse
I'm on the newest pre-rooted Fire OS available and the newest version of Netflix. It worked last week, so I'm not sure what is happening this week to cause the outage.
I'm likely to rollback root to stock OS anyway as several OTT TV providers do not work like Vue. They refuse to run when they detect root.

null0pointer said:
I'm on the newest pre-rooted Fire OS available and the newest version of Netflix. It worked last week, so I'm not sure what is happening this week to cause the outage.
I'm likely to rollback root to stock OS anyway as several OTT TV providers do not work like Vue. They refuse to run when they detect root.
Click to expand...
Click to collapse
If you're bootloader is unlocked. You might want to wait in case we can get Magisk HideRoot working. Near future project. Don't try it now. But heads up.
For now just turn off apps auto update & install a prior version of Netflix.

Y314K said:
Guys, please specify device, root, FW, etc.. Of you don't include specifics then it becomes a guessing game.
Netflix can be fanikie. When it acts up on me. On my latest FW PreRooted FTV1. I just go to the apps setting. Then do an App Stop & clean the cache. I leave Data alone. Since I prefer to not have to input the log in info. I also have the Apps auto update turned off. So I control when it updates. I only update if none of my other tricks work. As a last resort.
Click to expand...
Click to collapse
for my pre-root and regular fire TV I, when I upgraded to 5.2.4.1 . they all have this trouble (exit randomly in Netflix). hope someone can debug it.

[SOLVED] New HULU and HBO App Playback Failure Fix AFTV2 (sloane)

Update: This issue has now been confirmed solved for the Hulu, HBO Go, and HBO NOW app update error.
There are 2 ways to remedy the issue:
1. The prefered method is to update to the newest ROM. Rbox has issued an updated version of his ROM 5.2.4.2_r2. You can get a copy at the forum post here 5.2.4.1_r2. This updated version fixes playback errors in the new Hulu app as well as HBO (Go and Now) issues. Be sure to follow normal flashing instructions. Note - 5.2.4.2_r1 will NOT work for the new Hulu app (4.x.x).
2. If, for some reason, you do not want to flash an updated ROM. For the quick and dirty solution, post #12 gives instructions on correcting the problem. Note that this method only reverts to an older version of the app (3.x.x) and will not allow the new Hulu Live TV service functionality or the multiple accounts functionality. The same will need to be done for the HBO apk as well.
Original Post:
I'm surprised I'm the only one so far posting about this, but maybe I'm the only one experiencing problems.
The new HULU app updated automatically for me yesterday and immediately rendered playback impossible. Any show, movie, etc. comes back with a playback failure error code cdn-3-xxxxxxxx where the "x"s at the end change to different alpha numeric characters at any time. Here is what I have tried so far with NO POSITIVE RESULTS (in addition to speaking with HULU customer service support desk). I am on a rooted box using TWRP and rbox's system files (sloane).
Uninstalled and reinstalled app
Restarted AFTV
Unauthorized app via HULU website and re-authorized
Restarted router, cable modem, and AFTV (even a long term restart as requested by HULU tech support)
Updated AFTV software version (originally I was on 5.2.4.0 - then I updated to 5.2.4.2)
Wiped cache (Factory Reset)
As stated above, none of these worked.
HULU support gave me no way to uninstall the app and go back to an older (working) version, so I am currently stuck without a working version of HULU.
Here's what I'm interested in finding out from the community:
Has anyone experienced the same problems I have and then been able to get the app working correctly? If so, what method worked for you?
I can probably find an old version of the app online, however, I need to be able to block or turn off the update somehow... is there a method of turning the app update similar to how we stop the AFTV from updating automatically?
Any assistance would be appreciated. I'd really like the old version of the app back, since the newer version is crap.

This should be an old version of the apk you can try to sideload: https://www.dropbox.com/s/xw9rv2nxet2lchu/com.hulu.plus-FireTV-3.2.a.apk?dl=0

Thanks Sizzle, but I fear without a method of stopping the update I will shortly be left in a similar situation as I currently am in. Would you happen to know how to stop the automatic update of the hulu apk?

chadster1976 said:
Thanks Sizzle, but I fear without a method of stopping the update I will shortly be left in a similar situation as I currently am in. Would you happen to know how to stop the automatic update of the hulu apk?
Click to expand...
Click to collapse
FireOS 5 UI in Settings/Applications/Appstore/ you can turn off the "Automatic Updates" for all apps. In the future you will get notifications about Updates. You will be able to ignore them or apply them.

Can you confirm that the apk I provided is the older version? I've already upgraded and everything works fine on my Fire TV 1.

Sizzle - I will have some time this afternoon or early evening to implement the rollback and turn off the updates that Y314K provided instructions to earlier. I will post back with results when complete.
Thank you again for the assist.

Yup... I posted this as an issue on aftv news. If your rooted the new Hulu version will not work on your Amazon Fire TV. Please let us know if this method fixes the problem.
Sent from my Nexus 6P using XDA-Developers Legacy app

tekno4ever said:
Yup... I posted this as an issue on aftv news. If your rooted the new Hulu version will not work on your Amazon Fire TV. Please let us know if this method fixes the problem.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
The wife is not happy with Hulu not working and honestly she needs a stock always working AFTV box.
Happy Wife Happy Life! After searching a few different ways I'm unable to find a stock nonrooted 5.2.4.2 zip.
Might anyone know where I can download to flash via TWRP?

I can report same issue, it also effects newer versions of HBO GO

I've got a rooted fully unlocked bootloader FireTV 1 and am using version 4.0.0.342 as reported by Titanium Backup with no problems. What specifically shouldn't I be able to do? My hulu account is ad-free. Perhaps you guys are running an adblocker and do not have an ad-free hulu subscription?
Here's the 4.0.0.342 apk from my Fire TV: https://www.dropbox.com/s/mgvqg1ugzhrjpr5/com.hulu.plus-FireTV-4.0.0.342.apk?dl=0
Here's the old 3.2.a version from my other FireTV: https://www.dropbox.com/s/xw9rv2nxet2lchu/com.hulu.plus-FireTV-3.2.a.apk?dl=0

I am looking into this. If it is what I think, it would only be effecting the Fire TV 2 and has nothing to do with root.

Sizzlechest said:
Can you confirm that the apk I provided is the older version? I've already upgraded and everything works fine on my Fire TV 1.
Click to expand...
Click to collapse
Ok - Here are my findings. I attempted to install the 4.0.xxx version on both of my AFTV2 (sloane) boxes. Neither box would play videos (although the app booted and appeared to run correctly initially). Both are rooted with one running 5.2.4.2 and the other running 5.2.1.1.
After unsuccessful attempts of trying out the v4 app on both boxes, I uninstalled the apk, then rebooted.
Installed 3.2.a and success! Both units work as they should.
Although they are not the newest version of the app, I am able to play back video - so that is a plus
This version will not have the new Hulu Live or the separate account access to the app.
For anyone else experiencing this problem, here is the process I would recommend to solve this:
1. Download earlier version (3.2.a) of Hulu app (see Sizzlechest's link posted earlier)
2. Uninstall current non-working Hulu app.
3. Make sure your app automatic updates are set to OFF by going to Settings>Applications>Appstore>Automatic Updates - OFF
4. Reboot Device (may not be necessary, but what does it hurt?)
5. Connect to device via adb
6. Install Hulu 3.2.a.apk via command "adb install com.hulu.plus-FireTV2-3.2.a.apk" - keep in mind this only works if you did not rename the apk from Sizzlechest when you downloaded it.
7. Profit
You will need to re-logon to the Hulu app.
Thanks for everyone's help on this one! A real community effort.
Looking forward to rbox's discoveries on this subject. Thanks for all of your hard work on this and all of the other projects you've been a part of.

Sizzlechest said:
I've got a rooted fully unlocked bootloader FireTV 1 and am using version 4.0.0.342 as reported by Titanium Backup with no problems. What specifically shouldn't I be able to do? My hulu account is ad-free. Perhaps you guys are running an adblocker and do not have an ad-free hulu subscription?
Here's the 4.0.0.342 apk from my Fire TV: https://www.dropbox.com/s/mgvqg1ugzhrjpr5/com.hulu.plus-FireTV-4.0.0.342.apk?dl=0
Here's the old 3.2.a version from my other FireTV: https://www.dropbox.com/s/xw9rv2nxet2lchu/com.hulu.plus-FireTV-3.2.a.apk?dl=0
Click to expand...
Click to collapse
Sorry, forgot to address this Sizzle.
I DO have the add-free version of Hulu, but not the newer Hulu Live subscription. I am not running any adblocker software.

Okay. I have a theory on why both Hulu and HBO are not working. Like I said this is going to be a Fire TV 2 only thing. If someone is willing to try a fix, please PM me. Do note, this might brick the box. I really don't know. And if it bricks, it'll be super dead. But, there is a slim chance the unbrick program could revive it, so I would prefer someone who has a box that was rooted with my preloader instructions and not KingoRoot. But, if you don't care, and you didn't use the preloader instructions, and want to try anyway, there definitely won't be any way to recover it. I will say this again. If you try this fix, there is a chance it might brick the box. Just want to make that clear.

Is there a specific apk version (link) for hbo now that people have had success installing?

ducksoup18 said:
Is there a specific apk version (link) for hbo now that people have had success installing?
Click to expand...
Click to collapse
Sorry Duck, but I am not aware of the HBO Now app - I use Prime channels for my HBO subscription.
In the case of the Hulu app, I had to revert to the previous whole number version of app in order for it to work - V4.x.x.xxx --> V3.x.xxx
My suggestion is to just try some different versions in a fairly methodical way and see what works. It's fairly easy to install and uninstall via adb and only takes a few min.
Also, be sure to turn off automatic updating in the Appstore (different than updates for system), otherwise your app will just update itself again to the newer version and you'll be stuck.
Hopefully rbox will use his magical powers and get us an answer to all of our troubles soon. :fingers-crossed:

Thanks for the reply @chadster1976. Was able to get things to work by downloading an earlier version of HBO Now from the same place you guys suggested. Thanks again! Was able to watch GOT lastnight again on my main TV.
https://forum.xda-developers.com/showpost.php?p=73144047&postcount=412

rbox said:
Okay. I have a theory on why both Hulu and HBO are not working. Like I said this is going to be a Fire TV 2 only thing. If someone is willing to try a fix, please PM me. Do note, this might brick the box. I really don't know. And if it bricks, it'll be super dead. But, there is a slim chance the unbrick program could revive it, so I would prefer someone who has a box that was rooted with my preloader instructions and not KingoRoot. But, if you don't care, and you didn't use the preloader instructions, and want to try anyway, there definitely won't be any way to recover it. I will say this again. If you try this fix, there is a chance it might brick the box. Just want to make that clear.
Click to expand...
Click to collapse
I'm willing to test as I have spare AFTV devices just in case. Just sent you a PM @rbox

So I downloaded @rbox 5.2.4.2 deleted the SU directory inside the zip as instructed, then wiped everything possible 3x upon which I cleanly reinstalled 5.2.4.2 and Hulu still does not work on my non rooted AFTV 2 Box. Direct TV Now works perfectly without installing HideMyRoot so maybe this is truly just a Hulu issue on AFTV 2 Boxes. @AFTVnews.com

tekno4ever said:
So I downloaded @rbox 5.2.4.2 deleted the SU directory inside the zip as instructed, then wiped everything possible 3x upon which I cleanly reinstalled 5.2.4.2 and Hulu still does not work on my non rooted AFTV 2 Box. Direct TV Now works perfectly without installing HideMyRoot so maybe this is truly just a Hulu issue on AFTV 2 Boxes. @AFTVnews.com
Click to expand...
Click to collapse
Not sure Tekno. I was on chat 3 separate occasions with the Hulu tech support team and they claimed this had only been a rare occurrence... Take that however you want to... The extent of their assistance was resetting everything - including router, modem, etc. Then the final thing they suggested was a factory reset. I eventually did try that after updating to the latest firmware version from rbox. Needless to say that did not work. They couldn't help me with downgrading to the previous working version of the app, which is why I started this thread here on XDA.

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom menu issues

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom - 573210720
Menu selections starts at top (Filmstruck) goes down to browse, then settings. Going back up, it goes to browse, then to Criterion Channel. So can not access Watchlist or Search, and can only access Filmstruck after first opening the app. If you have already gone down a menu selection, you can't go back up to it. I don't remember which version this issue started with but I tried going back a couple rom versions with the same results.
Can anyone else confirm this on theirs or have any idea how to fix it? I have 2 FTV1 boxes and an FTV Stick 1, all rooted. I'd hate to have to go back to stock for one app but since I'm paying for the service (Filmstruck) I may have to.
Video of how it is not working https://youtu.be/uz_JEjfbv18

For what it's worth I did try older versions of the app as well as side loading the app from my kindle fire HD 8 tablet (rooted) where it works just fine. Also works fine on my phone running android nougat and PC. The side loaded app would just start to open and then close.

New versions for Amazon and Google Play - no fix
So there was an update to the Filmstruck app 3.1.1 on Amazon Appstore and 3.1.0 on the Google Play Store. Same results exactly. Both versions work fine on the tablet. Both versions have same exact menu navigation issues on the FTV 1. I'm about to throw in the towel and just give up being rooted and go back to stock. I'd really like to confirm that would be the solution before I go that route though. Can anyone else confirm they do or don't have this issue on their rooted FTV1 or if it works fine on unrooted? Right now all I can do is play it on my tablet and cast to the TV which is pretty frustrating. Thanks in advance for any thoughts on this.

Works fine on new unrooted FTV STick 2
OK, the suspense was killing me so I went and bought a Fire TV Stick 2 for testing. Opened up network so it would take updates if it needed them, set it up, installed the Filmstruck app, and everything worked perfectly. (Except I couldn't adjust the video scaling, but that's just because I have an old TV)
So I guess this confirms there is an issue with the Filmstruck app and the latest prerooted rom versions for the FTV1 and FTV1 Stick.

Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.

drewb0y said:
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
Click to expand...
Click to collapse
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.

Y314K said:
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Click to expand...
Click to collapse
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.

drewb0y said:
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
Click to expand...
Click to collapse
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.

Y314K said:
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Click to expand...
Click to collapse
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!

drewb0y said:
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
Click to expand...
Click to collapse
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...

Fixed
Y314K said:
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Click to expand...
Click to collapse
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!

I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.

drewb0y said:
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
Click to expand...
Click to collapse
drewb0y said:
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
Click to expand...
Click to collapse
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.

Y314K said:
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Click to expand...
Click to collapse
Gotcha. It seemed to load just fine without the MD5.

Well it worked for a few weeks and then back to the same behavior as before. Going to try unrooting again.