My wife and I bought my father-in-law a Fire TV which worked fine for some time. Then he brought it to my house because it wasn't working any more. I don't know what he did, but all it does is hang at the initial boot screen (black screen, white Amazon logo). Amazon has sent us a replacement Fire TV, but they let me keep the brick. Is there any way to recover this Fire TV? I've read through some of the threads. Tried using a keyboard to enter recovery (didn't work). Haven't tried adb (I don't have a USB-A to USB-A cable).
Thanks!
same issue
i hadn't used my fire tv for a couple months but was working flawlessly the last time I did use it and now no matter what tv I try to connect it to or how many hdmi cables I tried I can't get my fire tv to boot past the initial boot screen of the white Amazon logo it don't make it to the fire tv logo or any other screen it's just a black screen and screens all say no signal. I had rooted it back before I stopped using it with towel root and had adb enabled but after I boot it and it goes past the Amazon logo to the black screen the logo the led on the box is white then starts blinking then turns an amber color and sorta pulses or blinks differently than the while led blinked. Any help would b much appreciated I have been searching all over several forums and websites for days and nobody seems like they r having this issue so I'm totally lost
Stuck on Amazon Logo right out of the box/new
ryanrickard85 said:
i hadn't used my fire tv for a couple months but was working flawlessly the last time I did use it and now no matter what tv I try to connect it to or how many hdmi cables I tried I can't get my fire tv to boot past the initial boot screen of the white Amazon logo it don't make it to the fire tv logo or any other screen it's just a black screen and screens all say no signal. I had rooted it back before I stopped using it with towel root and had adb enabled but after I boot it and it goes past the Amazon logo to the black screen the logo the led on the box is white then starts blinking then turns an amber color and sorta pulses or blinks differently than the while led blinked. Any help would b much appreciated I have been searching all over several forums and websites for days and nobody seems like they r having this issue so I'm totally lost
Click to expand...
Click to collapse
Hi, were you able to fix it, I have same issue, except mine did it right out of the box, brand new, first time plugging it in. any help will be appreciate it.
Mike Power
Related
After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.
hiltoncp said:
After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.
Click to expand...
Click to collapse
You need a factory cable
KF Factory Cable
soupmagnet said:
You need a factory cable
Click to expand...
Click to collapse
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.
hiltoncp said:
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.
Click to expand...
Click to collapse
Yes 'factory' as in the one they use at OEM to install software.
Build Your own factory Cable is also an option if you can solder tiny things.
I attempted a full boot unlock and i might have bricked my fire tv. It is stuck on white amazon logo and black screen .i tried with key board by pressing Alt+print screen+ i but no joy and tried every combination of fire tv remot but no joy. Hope some one can help.
Same here, hope someone can help us
Went and lucked out lastnight with getting one rootable
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
Hello, I have a problem with my Amazon Fire Tv (Not stick)
My problem is when turn on my Amazon Fire Tv it shows me a white Amazon logo and the screen turns black, the remote doesn't work, I tried to use 2 different tvs but no luck, I tried going into recovery mode with a keyboard but leads me in to a dead end that says something like "Amazon Recovery System 3e, your Amazon Fire Tv will restart in a couple minutes and should return to normal operations, if it does not restart you may pull the power to force a restart." Also, the light on the box is pulsing white then sometimes turn to orange and back and forth. This is not rooted or have a custom boot menu, its mostly used for Kodi.
Thanks.
Thats exactly what mine does. No luck here yet love to find solution.
I am getting this same screen!
Still no luck with this issue ?
I have a Gen 2 Fire TV. Completely stock, unrooted, locked boot loader. Only thing I side loaded was kodi. Plus I did those adb commands to hide the ad banner.
I don't know what happened but since last week I can't get my Fire TV to boot. Farthest I can get to is the white Amazon logo. Interestingly I can still connect via network adb. It just stays on the white Amazon logo, then I think it turns off after 2 hours or something (TV would go to the "no hdmi signal" screen). I unfortunately don't have the remote anymore. But I have flirc setup and a usb keyboard.
I tried the alt+print screen+i, but from what I've read this is needed right before the colorful Fire logo, which I can't get to.
I tried what the OP tried from this thread and I got the same errors he got. But mine didn't fix itself by just having it sit for a couple hours. And I'm on the latest version so I can't just wipe it, root, and reinstall the rom.
Curious an update came out last week I believe. I wonder if this issue is related to the update. Like a failed/corrupted update or something.
Any suggestions on what else I can try out? Thanks