Hello
I just fresh installed the latest pre-rooted firmware (thanks as always rbox.. beer on me incoming!) and I forgot to do the "yank the ethernet cable" trick to get past the initial update. My router has the domains blocked and previously they were working fine, so I would have expected the check to fail, but it happily went though to the registration screen. Of course there are no updates since this is the latest, so no harm done this time round, but just wondering if any domains may have changed?
Also checking update status in "About" and it says last checked today (normally it just says "Checking now...."). When I click on Check for Updates, it says there was an error. Which suggests nothing has changed, but I'm confused by the above.
The other possibility is that the new firmware doesn't hang on checking for updates, so if it fails it just goes through anyway (good for peeps who are having internet trouble, etc).
Anyone else have this experience? I have updates disabled so not too worried, but just wondering for future reference in case I need to fresh install and a newer update is out.
Cheers
Try downloading the update through aftvnews, it may be your firewall isn't blocking it.
I just discovered my Asus router wasn't blocking the updates until I re-enabled the firewall.
edit:
Or may because you're on the latest update it skipped the update.
eskay993 said:
Hello
I just fresh installed the latest pre-rooted firmware (thanks as always rbox.. beer on me incoming!) and I forgot to do the "yank the ethernet cable" trick to get past the initial update. My router has the domains blocked and previously they were working fine, so I would have expected the check to fail, but it happily went though to the registration screen. Of course there are no updates since this is the latest, so no harm done this time round, but just wondering if any domains may have changed?
Also checking update status in "About" and it says last checked today (normally it just says "Checking now...."). When I click on Check for Updates, it says there was an error. Which suggests nothing has changed, but I'm confused by the above.
The other possibility is that the new firmware doesn't hang on checking for updates, so if it fails it just goes through anyway (good for peeps who are having internet trouble, etc).
Anyone else have this experience? I have updates disabled so not too worried, but just wondering for future reference in case I need to fresh install and a newer update is out.
Cheers
Click to expand...
Click to collapse
Just an observation...you shouldn't need to do the Ethernet trick with custom recovery when updating prerooted firmware. It will check for updates then nothing should happen.
I've been running the same prerooted firmware for a long time so my memory isn't perfect but I thought just updating it wouldn't take you to the registration screen??? Unless maybe this new firmware isn't set up like rbox's. Are you saying you had to setup your account, check adb and unknown sources, reinstall apps, etc? This would occur if you wiped data before installing the update maybe...
Anyways. If it running OK I wouldn't worry much about it.
KLit75 said:
Just an observation...you shouldn't need to do the Ethernet trick with custom recovery when updating prerooted firmware. It will check for updates then nothing should happen.
I've been running the same prerooted firmware for a long time so my memory isn't perfect but I thought just updating it wouldn't take you to the registration screen??? Unless maybe this new firmware isn't set up like rbox's. Are you saying you had to setup your account, check adb and unknown sources, reinstall apps, etc? This would occur if you wiped data before installing the update maybe...
Anyways. If it running OK I wouldn't worry much about it.
Click to expand...
Click to collapse
Thanks for the reply. Yes I did a complete fresh install / format data etc. Wanted to start fresh. I have done full wipe install with rbox's previous firmware in the past and I did have to do the ethernet trick to get to the registration screen. But not with this latest. My guess is Amazon have changed it so that it doesn't just hang if it encounters an error at the stage. Or something else has changed.
My router is definitely blocking the servers. Once I am in KFTV launcher, it shows they are being blocked (updates just says "Checking now..."). So probably nothing to worry about, just wanted to be ready, so to speak, in case I need to do another fresh install in future.
eskay993 said:
Thanks for the reply. Yes I did a complete fresh install / format data etc. Wanted to start fresh. I have done full wipe install with rbox's previous firmware in the past and I did have to do the ethernet trick to get to the registration screen. But not with this latest. My guess is Amazon have changed it so that it doesn't just hang if it encounters an error at the stage. Or something else has changed.
My router is definitely blocking the servers. Once I am in KFTV launcher, it shows they are being blocked (updates just says "Checking now..."). So probably nothing to worry about, just wanted to be ready, so to speak, in case I need to do another fresh install in future.
Click to expand...
Click to collapse
I tested this out. With the latest firmware that was just released by rbox. The update still shows the same error as before. After every update. I ensure that I disable the update service via SU and the update links are blocked on my router anyways. I don't do opendns as I believe in manual physical blocking.
Related
Hey Guys, hope this Question is not too stupid
Just read the amazon is going to update the AFTV 1gen to FireOS5 soon - so i wanted to get the latest OS3 for my Boxes, and disabled the url-blocking.
Anyhow, its now open for two hours, and both dont find any update. Its running on 51.1.6.1_USER_516010220, so there should be definitly a new version available.
Is it likely that amazon stopped pushing new updates, as os5 will arrive soon? Or is it a normal behavior that it doesnt find any new version after a few hours?
Just want to avoid getting updated to os5 too early, but as my version has still some bugs (like bluetooth-delay) i'd love to see it getting updated to the last stable os3...
The operative word is "soon." It's not out yet.
Well - maybe i asked it wrong?
Its not about when the new OS is out - its about why i dont get the latest OS3
Did you try forcing a check in Settings or were you just waiting for it to auto-update?
Did you try rebooting the Fire TV? I'm not sure if you are actually using URL blocking (as you say) or just domain name blocking (as what is typically described here and on various other sites), but if the latter, the Fire TV may have a DNS cache with the "invalid" IP address.
My AFTV got in September the last Update!
Yes thanks - i guess it was the DNS-caching. After leaving it for day as it was, finally a manual check was successful. Cheers!
dafunkydan said:
Yes thanks - i guess it was the DNS-caching. After leaving it for day as it was, finally a manual check was successful. Cheers!
Click to expand...
Click to collapse
I've experienced the same thing. I've powered on an AFTV that has been off for a few months and it doesn't update even though it's on software that is several versions old. I've found that making it forget and reconnect to a network helps get it to find the update. Factory reseting also helps.
Hi everyone,
I do not know if it happened after a specific update, but my FTV 1st gen has started acting weirdly a few days/weeks ago.
It used to be that the FTV would go into hibernate after 10min and when you press any button it would wake up and be ready right away. Within 5sec you could use it.
Now for some reason, when the FTV is in hibernation (both automatic and manual hibernation) the FTV will do a fresh boot when you click a button. So the FireTV logo is shown, the "loading homescreen" message is shown and I have to wait for it to fully boot.
It's as if the FTV actually shut down rather than going into hibernate.
Does anybody know what is causing this and how to fix it? Costumer support of course knew nothing of this problem
anybody?
weird that i am the only one... but my second FTV also works properly. Maybe I will have to try a factory reset
Is this box rooted? If so, have you blocked OTA updates? If no rooted, have you blocked OTA updates in your rooter?
Box may have downloaded an update previous blocking OTA updates and it is trying to update every time you try to re-start it however it fails. That is the only thing I may think about.
The box is not rooted. I also did not block updates. I checked and it is on 5.0.5, last updated in January. Can I somehow check if an update was downloaded and is trying to be installed? Manually chrcking for updates says that I am on the current firmware.
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
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
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.