Hey guys,
I was watching a video on the FTV and the video went off and the screen started to flicker. I unplugged it and restarted it and it goes to the Amazon logo screen then goes black and starts to blink again. I also tried a reset by the remote and nothing.
I changed out my cables to make sure that wasn't the problem,and it wasn't. The cables that are used for the FTV was used on another piece of equipment and it worked fine.
Suggestions? Any thing else to try?
It's less than a month old and it it's just fried,then I'll take it back and get another one. Thanks
are you rooted and using kodi as your launcher? i had this problem yesterday it was like kodi changed to a resolution that my tv didnt recognize if i held the home button it brought up sleep, screen mirror, and settings i chose settings wiped kodi data and all was good again.
Related
nothing exactly meaningful, just wanted to mention in case other people had similar experience.
well also it may have implications after the next OTA / post-root-if-that-happens
for reference: to be safe, for a while now I have had both of the known IPs blocked on my router.
- maybe a week ago, tried to scroll into Home->Recent and got a solid blue screen for 5-10 seconds. didn't touch the device, it auto-reboots, then everything ok. version number unchanged still etc_02.etc like we all have.
- few days after that, Prime TV was playing and kept playing fine, but usb went sideways. reconnecting usb, power looked ok but still nothing. tv app kept playing 100% fine just no HID. stupidly did not try the remote. recycled power, and got stuck at (white-logo)amazon screen. power-off, wait a while, tried a few more times and always stuck at (white-logo)amazon screen.
-- removed the 2 blocked URLs from my router and booted, everything back to normal. (version number still same etc_02.etc)
wasn't even going to bring all of this up, who knows I may have a flaky KFTV, but then
- today got the solid blue screen again trying to scroll Home->Recent*. as before, box eventually rebooted itself, without having to do anything, and everything normal again. (and this with both IPs still re-unblocked)
if nothing else reminded me to re-block both URLs lol. but it is a very small and random sample size so far.
semi-weird: the first blue screen, and the usb breakage, both very hot days here, it almost could have been temp-related (but box did not feel warmer than usual) - but then blue screen today is bad weather / cold here, so yeah probably not.
*since it happened same way both times, could easily just be some bug about Recent, or in the KFTV Launcher
tarvoke said:
nothing exactly meaningful, just wanted to mention in case other people had similar experience.
well also it may have implications after the next OTA / post-root-if-that-happens
for reference: to be safe, for a while now I have had both of the known IPs blocked on my router.
- maybe a week ago, tried to scroll into Home->Recent and got a solid blue screen for 5-10 seconds. didn't touch the device, it auto-reboots, then everything ok. version number unchanged still etc_02.etc like we all have.
- few days after that, Prime TV was playing and kept playing fine, but usb went sideways. reconnecting usb, power looked ok but still nothing. tv app kept playing 100% fine just no HID. stupidly did not try the remote. recycled power, and got stuck at (white-logo)amazon screen. power-off, wait a while, tried a few more times and always stuck at (white-logo)amazon screen.
-- removed the 2 blocked URLs from my router and booted, everything back to normal. (version number still same etc_02.etc)
wasn't even going to bring all of this up, who knows I may have a flaky KFTV, but then
- today got the solid blue screen again trying to scroll Home->Recent*. as before, box eventually rebooted itself, without having to do anything, and everything normal again. (and this with both IPs still re-unblocked)
if nothing else reminded me to re-block both URLs lol. but it is a very small and random sample size so far.
semi-weird: the first blue screen, and the usb breakage, both very hot days here, it almost could have been temp-related (but box did not feel warmer than usual) - but then blue screen today is bad weather / cold here, so yeah probably not.
*since it happened same way both times, could easily just be some bug about Recent, or in the KFTV Launcher
Click to expand...
Click to collapse
This started to happen to me about a week ago did you ever get it sorted out.
Hello,
Got an AFTV at staple the other day. I tried to follow the aftvnews guide "How to setup a new AFTV...".
Apparently my AFTV was pretty old since the initial unplug/plug trick did not work and the box was always stuk on waiting to download the update. I finally let the update run through and ended up with Firmware 51.1.0.2_user_510058520.
After that I tried to root the AFTV. For this I used adbFire. I was able to connect to the box (no internet connection at that time) and click on the Towelroot option. I did click on "Make it ra1n" and wait for a very long time. I never saw any message indicating that it succeded or failed. With the remote I ended up going back to the previous menu. I tried to install SuperSu but that did not work. Su was not installed. After rebooting the box, I get the back and white Amazon logo and then the screen goes black. The TV shows the selected input as if the AFTV is not sending any signal. I tried to plug the internet cable (with the 2 domains blocked) and the AFTV finally goes from the Orange blicking led to the Blue one but it's still stuck after the amazon back and white logo. I did try the ALT-I-PrntScr (which had worked previously when I was trying to prevent the update to install, I managed to get into recovery and do a factory reset ,so I know the keyboard itself is OK). But this time ALT-I-PrntScr only get the box to restart and brings me back to the Amazon black and white logo that disappear after a minute.
Nevertheless, I can still access the box from an adb shell, adbFire can connect to the AFTV. But since I no longer see any menu on the screen I can't attempt to reroot from adb fire.
A reboot recovery does not work as it's not authorized.
su command is not found , so it would confirm supersu did not install (properly). What's weird though is that if I do a ps, I see a process "u0_a1 6199 328 476352 18640 ffffffff 00000000 S eu.chainfire.supersu"
Any idea how I can unstuck the box ?
Thank you.
Some info for people in the same situation, the issue was that Towelroot needs internet access to complete.
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I have the same exact issue right now, probably that same update yours downloaded from 2 weeks ago:
https://forum.xda-developers.com/fire-tv/general/fire-tv-stuck-amazon-logo-adb-t3809305
This guy had the same problem too, and he has a big list of things to try, none of which worked for me:
https://forum.xda-developers.com/fire-tv/help/fire-tv-remains-stuck-amazon-firetv-t3561797
Mine's unrooted on the latest version, so I guess I can't root and reinstall rom. I'd hate to have to throw this away it's only 2 years old. I have a 5 year old Roku that still runs great.
"Perfect" timing I guess with Prime Day coming up?
Edit: couple more guys having the same issue recently, sounds like a mass bricking going on
https://forum.xda-developers.com/fire-tv/help/firetv-box-white-amazon-logo-blank-t3472867
https://forum.xda-developers.com/fire-tv/help/fire-tv-stucks-white-amazon-logo-t2889867
https://forum.xda-developers.com/showthread.php?t=2799779&page=7
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
johnusesandroid said:
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
Click to expand...
Click to collapse
I wish I had the same luck like you but i tried different tv's, all the ports availble and different HDMI cables but still no luck.
Anyone able to find a solution to fix it? or should I just throw it out?
DhiJay23 said:
Anyone able to find a solution to fix it? or should I just throw it out?
Click to expand...
Click to collapse
Sorry you weren't able to fix. Before you throw away, try contacting support. Not because they can fix it, they most probably can't. When I had problems with mine, I contacted them and they gave me a $15 credit off of a new one because I was out of warranty. This was a couple days before Prime Day so I was able to snag a new one for really cheap. Plus my old one started working again, so I now have 2 Fire TVs
Hi All,
I recently unplugged my AFTV2's HMDI cable and then when replugging it, i cannot get video signal back.
I try to restart, and it doesn't get past the Amazon logo. No colour logo at all. It seems bricked form unplugging the HDMI cable?
To make things worse, this is the 3rd box I have had with this problem.
Any ideas what could be causing it? It has Firestarter and KODI installed.
Thanks
Same Here
That is interesting.
About an hour ago exchanged a 3 day old Fire TV at Best Buy for a new one because of this exact behavior. I thought it was defective. It worked for a couple of days, my kid unplugged it and re-plugged it a few times because the screen had gone black, and afterwards nothing. Booted to white logo, then went straight to black screen. I could connect to it with ADB, but it would no longer output video except for the initial white amazon logo at startup.
Also was running Firestarter and Kodi, nothing else (latest firmware, no root)
b1nuzz said:
Hi All,
I recently unplugged my AFTV2's HMDI cable and then when replugging it, i cannot get video signal back.
I try to restart, and it doesn't get past the Amazon logo. No colour logo at all. It seems bricked form unplugging the HDMI cable?
To make things worse, this is the 3rd box I have had with this problem.
Any ideas what could be causing it? It has Firestarter and KODI installed.
Thanks
Click to expand...
Click to collapse
galvanash said:
That is interesting.
About an hour ago exchanged a 3 day old Fire TV at Best Buy for a new one because of this exact behavior. I thought it was defective. It worked for a couple of days, my kid unplugged it and re-plugged it a few times because the screen had gone black, and afterwards nothing. Booted to white logo, then went straight to black screen. I could connect to it with ADB, but it would no longer output video except for the initial white amazon logo at startup.
Also was running Firestarter and Kodi, nothing else (latest firmware, no root)
Click to expand...
Click to collapse
Have you tried entering recovery and doing a factory reset?
See this thread here
I got this type of behavior and in fact it was my TV just unplug it and plug it back
My set up was originally through an amp, but I now have it plugged directly in to the TV. It makes no difference.
I only unplugged it because I was trying to solve the issue where all the blacks are crushed.
Amazon help just keep saying they are faulty and will replace them, but when I push them to try and offer a better solution as to why it keeps happening, they just tell me it won't happen again.
Dull.
gazdaman. said:
Have you tried entering recovery and doing a factory reset?
See this thread here
Click to expand...
Click to collapse
No matter how many times I try, and believe me, it's a lot of times, I cannot get it to activate recovery.
I also can't get it be seen with ADB. It's recognised on the network, but ADB can't connect.
Just to close this.
It was my AVR putting voltage down the HDMI and causing the unit to brick.
Nothing to do with the AFTV.
Sent from my iPhone using Tapatalk
My Firestick is 100% stock. The other day it froze. I tried to reset with remote and nothing happened and after unplugging and plugging back in it came back unable to connect to WiFi or any remotes.
Amazon has been less than helpful wasting an hour of my time trying to reset and pair the remotes. The final icing was when they offered to sell me a new one at 20% off (my device is 1 yr old)
It loads up the home screen titles, then after awhile it says unable to connect to network. From there it goes into a screen saver but has no images.
It looks like everything essentially got turned off including ADB.
Am I pretty much SOL? All I think it needs is a factory reset but seems there is no way to do that without a remote?
Thanks in advance for any help.
Hockeyplayr999 said:
My Firestick is 100% stock. The other day it froze. I tried to reset with remote and nothing happened and after unplugging and plugging back in it came back unable to connect to WiFi or any remotes.
Amazon has been less than helpful wasting an hour of my time trying to reset and pair the remotes. The final icing was when they offered to sell me a new one at 20% off (my device is 1 yr old)
It loads up the home screen titles, then after awhile it says unable to connect to network. From there it goes into a screen saver but has no images.
It looks like everything essentially got turned off including ADB.
Am I pretty much SOL? All I think it needs is a factory reset but seems there is no way to do that without a remote?
Thanks in advance for any help.
Click to expand...
Click to collapse
Is this the only remote you have to try ? Or do you have any other fire devices with remotes you can try ?
First of all I'd try unplugging the power half way through the boot, try it a couple of times to try envoke the optimising screen, this happened to one of mine before and the remote paired after I got the optimising screen up, think I unplugged power 2 or 3 times for this to happen. Failing that you could try pairing the remote with an android device, while your firestick is off then unplug batteries and power up your firestick replace batteries and try again holding the home button for 30 seconds, I know it says 10 seconds but that never worked for me.
sconnyuk said:
Is this the only remote you have to try ? Or do you have any other fire devices with remotes you can try ?
First of all I'd try unplugging the power half way through the boot, try it a couple of times to try envoke the optimising screen, this happened to one of mine before and the remote paired after I got the optimising screen up, think I unplugged power 2 or 3 times for this to happen. Failing that you could try pairing the remote with an android device, while your firestick is off then unplug batteries and power up your firestick replace batteries and try again holding the home button for 30 seconds, I know it says 10 seconds but that never worked for me.
Click to expand...
Click to collapse
I have tried 3 different remotes. Have not tried the resetting during boot. Should I do it during the amazon logo or the firestick logo?
Thanks
Hockeyplayr999 said:
I have tried 3 different remotes. Have not tried the resetting during boot. Should I do it during the amazon logo or the firestick logo?
Thanks
Click to expand...
Click to collapse
I'd do it with the fire stick logo, well that's when I did it, if after a few times it don't go to the optimising screen it can't hurt to do it on the Amazon logo. Let me know if you have any luck.
sconnyuk said:
I'd do it with the fire stick logo, well that's when I did it, if after a few times it don't go to the optimising screen it can't hurt to do it on the Amazon logo. Let me know if you have any luck.
Click to expand...
Click to collapse
Well it went through the system optimization but still no luck connecting to WiFi or a remote. Thanks for the suggestion though, better than anything Amazon has offered. Just kills me that there is no mechanical way to factory reset the stick (something similar to the optimization trick).
Hockeyplayr999 said:
Well it went through the system optimization but still no luck connecting to WiFi or a remote. Thanks for the suggestion though, better than anything Amazon has offered. Just kills me that there is no mechanical way to factory reset the stick (something similar to the optimization trick).
Click to expand...
Click to collapse
Ah ok, if you are 100 percent sure you have ADB switched off then I'm afraid there is nothing you can do as far as I'm aware.
If you had ADB switched on then enabling otg and using usb hub you could of plugged a keyboard in and navigated with that into settings and returned it to factory settings.
I fixed this problem by going on my Samsung TV settings and enable anynet+ (hdmi-cec). This allows you to use your TV remote instead of amazon remote. Then all good got back online and so on. Already happened twice and its very frustrating don't know what to do. See if you TV got something like that, which allows you to use its remote. Good luck
Hi i was upgraded to oreo when its released and using until today but i had a issue about netflix yesterday and today. basically netflix app opens automatically and if i try to exit , its opening app again and again , yesterday i solved that issue with rip off the power cable and waited 5 mins then plugged the cable and its solved but now its not worked and i rip off the power cable again and pluged back then when the tv boots up i did factory reset before netflix app opens. well... weirdly after the factory reset on Welcome (language selection) setup screen netflix opens again i did rip off the power cable again and waited for some minutes then its solved but i did factory reset again. also im sure that remote buttons are didnt stuck cause i dont see and led blinking on tv and i also tried to remove batteries on the remote and tried to remote with android tv remote app on my phone. until now after the factory reset it soft rebooted itself by randomly but nothing about netflix until now. so i wonder whats causing this issue cuz its pretty sucks .