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.
Related
Where can i find an Android Settings.pak that will work with AFTV or does it have it built in?
Do I need root to sideload it?
Yes, you have to sideload. See attached apk.
dbdoshi said:
Yes, you have to sideload. See attached apk.
Click to expand...
Click to collapse
Thank you for the file.
yes, I know it has to be sideloaded but does the AFTV need to be rooted to use it? Do i need any additonal module to use it?
Not that I am aware of needing any extra module to load the Settngs apk.
As far as root goes, I do not know. I would suppose that some featues of Settings will be disabled and not work if root is unavailable. I installed mine after root, so I have no first hand experience. Do know that even with root, some features will crash when you try to go into them and crash your app as well. But I have not see any harmful impact due to this.
What works and what does not work with the setting apk described here?
What features crash?
Bluetooth
I used the bluetooth to scan for devices and it picked up my Bose Soundock. Very simple. From what I read it won't work with devices which need a PIN
I cannot seem to install this. I have root using adbFire and granted SU, and have unknown sources enabled, but when I use adbFire to install it takes a really long time and never finish.
You can try to install using adb manually. I have installed this a few times and never had issues.
Are you connected to FTV correctly over the same subnet? Thats the first thing I would check. It is a small install and should not taken more than 5 to 10 seconds to install.
dbdoshi said:
You can try to install using adb manually. I have installed this a few times and never had issues.
Are you connected to FTV correctly over the same subnet? Thats the first thing I would check. It is a small install and should not taken more than 5 to 10 seconds to install.
Click to expand...
Click to collapse
It must be the way you uploaded the file here or the way i downloaded it.
I searched and found another post with the file uploaded via a different service and downloaded it and it installed fine.
I found it here for reference:
http://forum.xda-developers.com/showthread.php?t=2714494
Thanks for all of your help!
Is it possible to enable installation from unknown sources, so that you could install APKs from dropbox for example instead of sideloading them?
dbdoshi said:
Yes, you have to sideload. See attached apk.
Click to expand...
Click to collapse
Thank you. Finally got my bluetooth keyboard working with the Fire TV Stick.
I just got a rootable fire tv and decided i'd try the internal storage increase trick. I updated to the latest custom root firmware and installed all my apps before attempting and when I did it had some strange error and quit. Now I am left with what appears to be a fire tv that is rooted but does not know it is. I can mount external usb, all the superuser stuff still works updates are blocked etc. But when I run towel root it says this phone doesn't work... I can't open the super user program its just doing weird stuff. Has anyone ran into this? I really want to try the increasing internal storage trick.
danknasty said:
I just got a rootable fire tv and decided i'd try the internal storage increase trick. I updated to the latest custom root firmware and installed all my apps before attempting and when I did it had some strange error and quit. Now I am left with what appears to be a fire tv that is rooted but does not know it is. I can mount external usb, all the superuser stuff still works updates are blocked etc. But when I run towel root it says this phone doesn't work... I can't open the super user program its just doing weird stuff. Has anyone ran into this? I really want to try the increasing internal storage trick.
Click to expand...
Click to collapse
So you messed up your device trying to do a trick, but it makes you wanna fix your device so that you can try it again? LOL. Did you try reinstalling the rom? Reinstall the custom firmware and report back. It will probably fix everything.
porkenhimer said:
So you messed up your device trying to do a trick, but it makes you wanna fix your device so that you can try it again? LOL. Did you try reinstalling the rom? Reinstall the custom firmware and report back. It will probably fix everything.
Click to expand...
Click to collapse
Well yea it didn't explode so I wanna give it another shot.... I actually was able to get this working but it's still acting weird super user is basically cemented in the device with no way of removing it or opening it and towel root acts like it's an Unrooteable unit. At any case everything else seems to be working fine boots to xbmc shows 800 gig internal storage. Not sure what I did.
I think the su app crashes on mine also when I try to open it. Something with the latest rom from rbox. No big deal as long as it's working. I don't have much reason to open it.
i think its normal,cause u updated to 51.1.4 latest rbox rooted (think also with boot menu and cwm)
Towelroot checks firmware and when its not 51.1.0 it seems that it say, your phone is not supported.
so have fun with your 800gb ft ^-^
schybiorz said:
i think its normal,cause u updated to 51.1.4 latest rbox rooted (think also with boot menu and cwm)
Towelroot checks firmware and when its not 51.1.0 it seems that it say, your phone is not supported.
so have fun with your 800gb ft ^-^
Click to expand...
Click to collapse
Oh ok makes sense. The only reason I checked super su was because its not on grant all mode guess I'll just live with it.
yea, also didn't got su app to work. also annoying notifications on screen but i have to live with.
I have two FTVs both running old 51.1.1.0. Both of them have Kodi 14.2 and both crash shortly after I launch Kodi. They were both working fine and then both stopped working the same day. I thought there may have been an update, but that didn't happen. I can't figure it out and I'm really frustrated with these boxes. I'm ready to sell them and get something better. I can't even update them. Every way I try to update fails.
Any suggestions?
madtork said:
I have two FTVs both running old 51.1.1.0. Both of them have Kodi 14.2 and both crash shortly after I launch Kodi. They were both working fine and then both stopped working the same day. I thought there may have been an update, but that didn't happen. I can't figure it out and I'm really frustrated with these boxes. I'm ready to sell them and get something better. I can't even update them. Every way I try to update fails.
Any suggestions?
Click to expand...
Click to collapse
You have to provide a lot more info regarding your boxes. I am assuming your boxes are rooted or you blocked updates in your router because this is a very old firmware and if so you will not be able to update them over the air without enabling OTA updates.
Start here and read before you do anything (you can still keep root and update to latest OS3 s/w): http://www.aftvnews.com/start/
bula1ca said:
You have to provide a lot more info regarding your boxes. I am assuming your boxes are rooted or you blocked updates in your router because this is a very old firmware and if so you will not be able to update them over the air without enabling OTA updates.
Start here and read before you do anything (you can still keep root and update to latest OS3 s/w): http://www.aftvnews.com/start/
Click to expand...
Click to collapse
They both are rooted. I'm just trying to update Kodi. I thought it would be best to keep the old firmware. I've used the Windows utility app to try and install the new version of Kodi as well as the fire installer on an android phone. Nothing seems to work. This is the way I've always done it. Let me know what other information I can provide.
Not sure why you want to keep an older firmware (newer versions bring fixes and improvements) but that is up to you. Have you installed something on both units that lead to the system crash? It is very weird that both units stopped working at the same time. Have you try to clean cache (not data) and run kodi again? If this does not work do a back up, uninstall kodi, reset firetv, reinstall whatever version of kodi you like and run it (do not restore you back up yet) if all is good (opens up) exit kodi and restore your back up. If it still does not open then something got corrupted in your data files and you will have to reinstall everything from scratch.
bula1ca said:
Not sure why you want to keep an older firmware (newer versions bring fixes and improvements) but that is up to you. Have you installed something on both units that lead to the system crash? It is very weird that both units stopped working at the same time. Have you try to clean cache (not data) and run kodi again? If this does not work do a back up, uninstall kodi, reset firetv, reinstall whatever version of kodi you like and run it (do not restore you back up yet) if all is good (opens up) exit kodi and restore your back up. If it still does not open then something got corrupted in your data files and you will have to reinstall everything from scratch.
Click to expand...
Click to collapse
I've tried clearing cash. The reason I didn't take an OTA update for firmware is because I thought I couldn't root the newer versions.
madtork said:
I've tried clearing cash. The reason I didn't take an OTA update for firmware is because I thought I couldn't root the newer versions.
Click to expand...
Click to collapse
You can still update to latest firmware (using rbox prerooted images). Follow link I posted above and read, read, read before you do anything.
I think the same as bula1ca write down here.
First update to the last availible prerooted rom. Read it here how to do: http://www.aftvnews.com/start/
Another question from my side is: Why did you use kodi 14.2.
kodi 16 jarvis is availible and you can use it as launcher too with a pythin script here from the board.
Feel free to ask your question but please read enough before
Greetings by Idijt
Hey, just wondering if anyone can help, for the past week I've been trying to fix a problem with my Fire tv and have tried various methods to fix this issue. Basically I use Sloane 5.0.5 r4 ROM on my aftv 2, it comes with super su and the root does work as superuser requests pop up to allow or deny. However super su doesn't appear in apps (the GUI management tool) when installed (tried various versions of supersu from 2.4 to 2.7) and I try to launch it, it just takes me back to the home screen. From googling I can see a few others have a similar problem, some people suggesting kingroot(not keen to use that as it doesn't give me the same options as super su) some suggesting rbox will make an update to sort the problem. Although not something I know is definite. The super su works and it's binaries as suggested earlier but the gui tool is nowhere to be seen. Even tried changing sloanes rom and replacing it with another supersu version but this hasn't worked. Just to add more details im running TWRP recovery also!
Thanks.
Aaron-Marcus said:
Hey, just wondering if anyone can help, for the past week I've been trying to fix a problem with my Fire tv and have tried various methods to fix this issue. Basically I use Sloane 5.0.5 r4 ROM on my aftv 2, it comes with super su and the root does work as superuser requests pop up to allow or deny. However super su doesn't appear in apps (the GUI management tool) when installed (tried various versions of supersu from 2.4 to 2.7) and I try to launch it, it just takes me back to the home screen. From googling I can see a few others have a similar problem, some people suggesting kingroot(not keen to use that as it doesn't give me the same options as super su) some suggesting rbox will make an update to sort the problem. Although not something I know is definite. The super su works and it's binaries as suggested earlier but the gui tool is nowhere to be seen. Even tried changing sloanes rom and replacing it with another supersu version but this hasn't worked. Just to add more details im running TWRP recovery also!
Thanks.
Click to expand...
Click to collapse
It's something Amazon does to Android and SuperSU being a system app. I noticed the same problem with the Play Store. You might be able to launch it while in an alternative launcher and/or using adb shell.
Run a adb shell and fire up this one
pm path eu.chainfire.supersu
Just to check the installation path
Hey rbox! Many thanks for your reply, and well done on your effort with this rom, can't fault it except for this minor issue. Been tearing my hair out trying to figure out exactly why it all looks fine and well but won't launch. I was thinking of trying to install play store using xposed, was looking at a guide online and wondered if it would open through play store. Didn't realise I could use another launcher with your rom though. Do you know if there's others you know that understands amazon devices to come up with a fix, update etc? seems like you're the only one to make a rom so far for the aftv so I'm guessing it'll take time until everyone fully understands amazon devices and apply similar Android based roms. Thanks for your advice.
Here's what the path came back as, I did notice there's two different locations for supersu though.
correct me if i'm wrong but as far as i know the supersu (the one that you just found) is the su binary but the GUI (which is responsible for the grant notification) is here: /system/app/Superuser.apk
I'm not 100% sure about it, so maybe someone could light up the dark
once sloane-5.0.5-rooted_r4 is flasheed can we update SU from play store?
Sure but you don't have to. Just take that one http://apps.evozi.com/apk-downloader/?id=eu.chainfire.supersu
Sent from my Nexus 6 using XDA-Developers mobile app
Cool thks but i purchased the pro and thought i could update without breaking anything on the fire
ok i updateed to pro since it was allready purchased, all went well but dont know what it does more since i cant open the app loll, but it works, thats what counts
Habs69M said:
ok i updateed to pro since it was allready purchased, all went well but dont know what it does more since i cant open the app loll, but it works, thats what counts
Click to expand...
Click to collapse
My experience is with Firestick.
1) On main Amazon screen, go to the App line and look accros there.
2) Connect Wukong Remote https://play.google.com/store/apps/details?id=com.wukongtv.wkremote.client.en and you'll see the Apps selection at bottom.
I like to go into Supersu settings and the default to "Grant" and I like to turn off notifications.
king200 said:
My experience is with Firestick.
1) On main Amazon screen, go to the App line and look accros there.
2) Connect Wukong Remote https://play.google.com/store/apps/details?id=com.wukongtv.wkremote.client.en and you'll see the Apps selection at bottom.
I like to go into Supersu settings and the default to "Grant" and I like to turn off notifications.
Click to expand...
Click to collapse
thks cool app but i still cant open super su , dont know after reading some that you even can
Arghhhh. Think I've soft bricked my fire tv or worse! I was re flashing the rom and was cleaning the data before hand, I must of wiped the system and now I'm only seeing the amazon white logo when i turn it on... Tried to install recovery again since I can't even get into recovery but when going through preloader it eventually says error can't find target file. Tried to use fast boot but fire tv isn't connecting to try and install recovery etc that way! You guys got any ideas or have I totally broken the device? ???
Keep calm buddy, als long as the preloader is still working everything is possible. Did you try to Flash TWRP again?
http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
Thank you so much! It saved the day! never will i ever be such a n00b and delete the entire system again. Also big thankyou RBOX for your guide and files to unbrick, they worked a dream. Everything is installed now, hopefully in near future someone manages to get SuperSu opening in the GUI lol im just happy I can actually use my fire tv again though!
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