Hello,
My firetv1 is rooted and has rbox boot menu, clockwork recovery, and firetv os3 installed. Spmc launcher is installed with android power saving screen saver to turn the firetv off to sleep.
Each morning (or after x hours of sleep), i find the device turned on indefinitely. Turn the tv on and somehow the device booted itself into recovery? Like, how? Rbox boot menu is set to kernal by default so even if it reboots on error, it should boot into spmc... It is starting to be a little freaky.:silly:
I don't know what to do? The screen saver works fine. Goes to sleep after x minutes...
Please help!
Edit: so i observed it for a few minutes.
1. Turn tv and firetv on. Launches spmc just fine
2. after 3 minutes, goes to sleep
3. after x minutes, turns back on?! shows SPMC on screen
4. ?? something happened here within 5 minutes.
5. Recovery on screen.
ssy080 said:
Hello,
My firetv1 is rooted and has rbox boot menu, clockwork recovery, and firetv os3 installed. Spmc launcher is installed with android power saving screen saver to turn the firetv off to sleep.
Each morning (or after x hours of sleep), i find the device turned on indefinitely. Turn the tv on and somehow the device booted itself into recovery? Like, how? Rbox boot menu is set to kernal by default so even if it reboots on error, it should boot into spmc... It is starting to be a little freaky.:silly:
I don't know what to do? The screen saver works fine. Goes to sleep after x minutes...
Please help!
Click to expand...
Click to collapse
It's probably trying to do an update. You're not blocking updates.
rbox said:
It's probably trying to do an update. You're not blocking updates.
Click to expand...
Click to collapse
thank you for the reply. I blocked the update app and have added the url's to my router's firewall. I thought that was it?!
ssy080 said:
thank you for the reply. I blocked the update app and have added the url's to my router's firewall. I thought that was it?!
Click to expand...
Click to collapse
Sure you blocked it? When you go the settings and check for the update it should say like 'checking...' or something like that. Also, make sure /cache and /cache/recovery don't have updates in them.
rbox said:
It's probably trying to do an update. You're not blocking updates.
Click to expand...
Click to collapse
rbox said:
Sure you blocked it? When you go the settings and check for the update it should say like 'checking...' or something like that. Also, make sure /cache and /cache/recovery don't have updates in them.
Click to expand...
Click to collapse
hmm.. I disabled the main launcher so not sure if i can get into the firetv settings, but ill try! thank you for the quick replies
rbox said:
Sure you blocked it? When you go the settings and check for the update it should say like 'checking...' or something like that. Also, make sure /cache and /cache/recovery don't have updates in them.
Click to expand...
Click to collapse
Nothing in those folders. I just did the blocking again and got this via adb:
[email protected]:/ # pm disable com.amazon.dcp
Package com.amazon.dcp new state: disabled
I've flashed OS5 before I came back to OS3, so maybe this unblocked the update. I thought I applied it again, but maybe not. The device has not woken up automatically for ~10 minutes, so I guess I will report back tomorrow.
thank you and good night .
Edit: it must have been the update. Did the patch again and is not waking up randomly.
Thank you!
Related
anyone know how to downgrade firmware on fire tv remote, i updated to latest and now lost features of it
can anyone even tell me were the remote firmware is located
what features did you loose.? I have the latest firmware and it still works with xbmc keymaps
paul.savo said:
anyone know how to downgrade firmware on fire tv remote, i updated to latest and now lost features of it
Click to expand...
Click to collapse
paul.savo said:
can anyone even tell me were the remote firmware is located
Click to expand...
Click to collapse
I think you upgrade FirmWare to 51.1.3.0_513011820 & your remote is not at 100%. That is because you have to do the following after a FW update to also update the remote.
http://www.aftvnews.com/how-to-update-the-amazon-fire-tv-voice-remote-or-game-controller-software/
If not please explain if the lost features are only related to XBCM or ???
no not related to xbmc, actually related to the fire tv itself, i can no longer search for anything, within ftv, it does not recognise that i am searching
paul.savo said:
no not related to xbmc, actually related to the fire tv itself, i can no longer search for anything, within ftv, it does not recognise that i am searching
Click to expand...
Click to collapse
So it sound like you upgraded the firmware. You don't need to downgrade. Just follow the guide I posted above to update the FTV remote to match the latest FW & everything should go back to normal.
FTV controllers are known to loose functions after a FW upgrade until you also upgrade the remotes software to the new revision the new FW brought with it. Very easy to do. Just an extra step of FW upgrading.
1011
i thought that was what i did, i went to the settings picked controller, it gave me an update firmware and i selected it and downloaded but since then i had the problems, i now now longer have thr option to update again as it believes it is up to date, any ideas? i have a 2nd ftv, would it be pissible to copy any folders from it across?
paul.savo said:
i thought that was what i did, i went to the settings picked controller, it gave me an update firmware and i selected it and downloaded but since then i had the problems, i now now longer have thr option to update again as it believes it is up to date, any ideas? i have a 2nd ftv, would it be pissible to copy any folders from it across?
Click to expand...
Click to collapse
That would probably be to complicated...
What Software version (prerooted or stock) is your FireTV @ ?
What Software version is your Remote @ ?
Is you FireTV routed ?
Do you have CWM Recovery installed ?
Will need that info to see what options you have... Could be a bad FW flash.
im just in work so dont have details to hand., fire tv is rooted, i have cwm,
paul.savo said:
im just in work so dont have details to hand., fire tv is rooted, i have cwm,
Click to expand...
Click to collapse
Are you using the pre-rooted FW ?
Also how did you get the new FW to CWM for flashing ? Push to cache (can give problems) or Sideloaded using one of the apss to SDCard & then flashed it from CWM ?
to be honest im not sure i bought it fully rooted with latest firmware and all xbmc/apps installed
paul.savo said:
to be honest im not sure i bought it fully rooted with latest firmware and all xbmc/apps installed
Click to expand...
Click to collapse
So there was a pending update only for the remote which you accepted ?? Did you see the "FireTV Remote update is complete" image ?
http://www.aftvnews.com/wp-content/uploads/2014/09/controllerupdate-09.jpg
Did you power cycled the FTV for 20 seconds (Unplug, wait 20 sec & replug it back in) afterwards ? Are you having only voice search problems or text search problems too ?? Try to give a much info as possible.
It's better to do the soft reboot = simultaneously holding down the “Select” and “Play” buttons on the remote for a few seconds until it reboots. ( http://www.aftvnews.com/how-to-safely-reboot-and-restart-the-amazon-fire-tv/ )
yes i only updated the remote
i followed the procedure in http://www.aftvnews.com/how-to-update-the-amazon-fire-tv-voice-remote-or-game-controller-software/
i may have made a mistake im not sure but it appeared as though it updated as stated in guide.
both voice and text are affected, eg. if i type or say a movie "batman begins" as i type it recognises it and below were i type will be batman begins but when i select it, i then get a return saying somthing like no results returned, but when i do this on my other ftv which i did not update remote it will take me to amazon store and find movie/tv show/music that i searched for
just re your last, i did now power cycle off for 20seconds
paul.savo said:
just re your last, i did now power cycle off for 20seconds
Click to expand...
Click to collapse
Result of he power cycle ??
What version is the remote showing as ??
i gbink its the latest im not at device now im in work ( how can i check? does it show in settings?)
paul.savo said:
i gbink its the latest im not at device now im in work ( how can i check? does it show in settings?)
Click to expand...
Click to collapse
Thought you where at device since you just mention doing the 20 sec power cycle. Another way to reboot is simultaneously holding down the “Select” and “Play” buttons on the remote for a few seconds.
Yes version shows in the settings...
http://www.aftvnews.com/wp-content/uploads/2014/09/controllerupdate-04.png
You can also unpair it and re-pair it (pair = connected to the FTV)
Well no point of continuing to guess around. Post back once you are @ device.
ok thanks, sorry if u thought was at device, i meant when i updated it i did not power off for 20secs, will post version later
paul.savo said:
ok thanks, sorry if u thought was at device, i meant when i updated it i did not power off for 20secs, will post version later
Click to expand...
Click to collapse
When you get home DON'T do the unplug thing. Just do the simultaneously holding down the “Select” and “Play” buttons on the remote for a few seconds until it reboots. Let it finish rebooting & then check search again.
http://www.aftvnews.com/how-to-safely-reboot-and-restart-the-amazon-fire-tv/
does not appear to be remote but device itself, the updated remote works fine on new ftv but when i put the new remote on old ftv i have same issue, both remotes on diff firmware, 349/352
.do you know were search folder located in root menu on device and i could replace with new ftv
The old Netflix app worked fine. I am in Australia, and use UnoTelly DNS service.
I just updated to pre-rooted 51.1.4.1_514013920 fixed and tried the new netflix app. It loads fine, but when I select a title to play, it gets to about 6% buffering and says: We're having trouble playing this title right now. Please try again later or select a different title.
I tried clearing the Netflix data and cache as was mentioned in another post, but no luck.
Anyone else managed to get past this, or have any ideas? Otherwise I guess I will have to downgrade again, which sucks, I like the screen mirroring
modstore said:
The old Netflix app worked fine. I am in Australia, and use UnoTelly DNS service.
I just updated to pre-rooted 51.1.4.1_514013920 fixed and tried the new netflix app. It loads fine, but when I select a title to play, it gets to about 6% buffering and says: We're having trouble playing this title right now. Please try again later or select a different title.
I tried clearing the Netflix data and cache as was mentioned in another post, but no luck.
Anyone else managed to get past this, or have any ideas? Otherwise I guess I will have to downgrade again, which sucks, I like the screen mirroring
Click to expand...
Click to collapse
Were you sure you followed the instruction that tell you to update to 51.1.4.0 before going to 51.1.4.1?
rbox said:
Were you sure you followed the instruction that tell you to update to 51.1.4.0 before going to 51.1.4.1?
Click to expand...
Click to collapse
Yes, I updated to 51.1.4.0 first, boot menu is installed fine, and everything else works as it should.
rbox said:
Were you sure you followed the instruction that tell you to update to 51.1.4.0 before going to 51.1.4.1?
Click to expand...
Click to collapse
Just in case it's relevant, I updated to 51.1.4.0 by doing a restore from backup through clockworkmod recovery, not an install from zip.
modstore said:
Just in case it's relevant, I updated to 51.1.4.0 by doing a restore from backup through clockworkmod recovery, not an install from zip.
Click to expand...
Click to collapse
You need to install with the full zip. Backups don't include firmware.
rbox said:
You need to install with the full zip. Backups don't include firmware.
Click to expand...
Click to collapse
Ahh right. Thanks, I'll install 51.1.4.0 then do boot menu, then the latest zip and hopefully that fixes the problem. Cheers.
rbox said:
You need to install with the full zip. Backups don't include firmware.
Click to expand...
Click to collapse
I installed 51.1.4.0 and tried Netflix once it completed. Netflix loads, but when I try to watch something, it gets to 15% buffering or so and then the app just exits, no message or anything.
I installed boot menu and updated to 51.1.4.1, but still the same issue. I tried clearing Netflix data/cache and re-installing, but no progress.
modstore said:
I installed 51.1.4.0 and tried Netflix once it completed. Netflix loads, but when I try to watch something, it gets to 15% buffering or so and then the app just exits, no message or anything.
I installed boot menu and updated to 51.1.4.1, but still the same issue. I tried clearing Netflix data/cache and re-installing, but no progress.
Click to expand...
Click to collapse
And you're sure you used the updated zip? Getting to 15% is something different though. Usually it stops before it reaches double digits. I do know a few international people were reporting issues with the latest Netflix.
rbox said:
And you're sure you used the updated zip? Getting to 15% is something different though. Usually it stops before it reaches double digits. I do know a few international people were reporting issues with the latest Netflix.
Click to expand...
Click to collapse
Yep, this is the file I used: bueller-51.1.4.0_514006420-rooted+updated.zip
rbox said:
And you're sure you used the updated zip? Getting to 15% is something different though. Usually it stops before it reaches double digits. I do know a few international people were reporting issues with the latest Netflix.
Click to expand...
Click to collapse
In case it's relevant, I have a rule in my router to redirect 8.8.8.8 to my router's IP so it is forced to use my DNS overrides, as I believe the new app hardcodes Google's DNS.
modstore said:
In case it's relevant, I have a rule in my router to redirect 8.8.8.8 to my router's IP so it is forced to use my DNS overrides, as I believe the new app hardcodes Google's DNS.
Click to expand...
Click to collapse
Hrm. Strange. It might be a temporary thing, not sure. Maybe try again tomorrow? You sure the redirect is working? I think google's dns has 2 ips... maybe you need to redirect both.
rbox said:
Hrm. Strange. It might be a temporary thing, not sure. Maybe try again tomorrow? You sure the redirect is working? I think google's dns has 2 ips... maybe you need to redirect both.
Click to expand...
Click to collapse
Yeah, I used to have a Roku before the Fire TV and it required the redirect to be setup and worked fine once it was. The app would do the check on startup and exit if it failed.
It works fine on my computer too.
rbox said:
Hrm. Strange. It might be a temporary thing, not sure. Maybe try again tomorrow? You sure the redirect is working? I think google's dns has 2 ips... maybe you need to redirect both.
Click to expand...
Click to collapse
I grabbed the log of when it happens, in case it gives any insight.
modstore said:
I grabbed the log of when it happens, in case it gives any insight.
Click to expand...
Click to collapse
Something is crashing... weird.
rbox said:
Something is crashing... weird.
Click to expand...
Click to collapse
I don't know if it's just a coincidence, but I de-registered and re-registered the Fire TV to my account and it's working now Thanks for your help rbox.
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 a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all seemed to work ok. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it OK again; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the device.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
navtis123 said:
I have a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all seemed to work ok. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it OK again; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the device.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
Click to expand...
Click to collapse
This is not the 5th gen forum
ask here
http://forum.xda-developers.com/amazon-fire/help
sd_shadow said:
This is not the 5th gen forum
ask here
http://forum.xda-developers.com/amazon-fire/help
Click to expand...
Click to collapse
Thanks sd_shadow, I've done that. Maybe someone could add a note to the forum to make it more obvious this forum is for Fire older than 5th gen only?
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