I brought a new amazon fire tv box. I am not looking to root. I booted it up, it updated. I connected to my network. Downloaded Netflix tried to watch Netflix and it gave me a error. So I unplugged the box to reboot. Plugged it back up and nothing. The unit won't power on. So I did an RMA and got a new one.
Got the new one, powered it up, took the update, downloaded Netflix, same error on not playing. Used the remote to put unit in sleep mode. And now the unit won't come back on. Did I get two bad units? Is there any hope in getting this thing to boot back up?
Any thoughts?
nighthawk777 said:
I brought a new amazon fire tv box. I am not looking to root. I booted it up, it updated. I connected to my network. Downloaded Netflix tried to watch Netflix and it gave me a error. So I unplugged the box to reboot. Plugged it back up and nothing. The unit won't power on. So I did an RMA and got a new one.
Got the new one, powered it up, took the update, downloaded Netflix, same error on not playing. Used the remote to put unit in sleep mode. And now the unit won't come back on. Did I get two bad units? Is there any hope in getting this thing to boot back up?
Any thoughts?
Click to expand...
Click to collapse
That is some strange stuff...netflix errors are common but a reboot almost always fixes it. I don't know what's going on but amazon actually has great customer service so make a call and more than likely they'll either walk you through it or possibly send you a new one.
i have the same issue, it stopped working after a day. No power LED no nothing.
I was holding "select and play" in an attempt to restart the box because i encountered sluggish performance on Kodi.
Afterwhich, i am not able to turn it back on again despite changing socket points and random clicking on the remote.
While i am waiting for a new set from Amazon, is there anyone who has encountered the same issue but have managed to power up the box??
I am in the exact same position ....
- new out of the box
- updated as part of the install process
- side-loaded Kodi with a "success" message
- rebooted as instructed with play and select for 5 seconds ....
- nothing, dead, no reboot, nothing, no light. Seems completely dead.
As the person above - let me know if you anyone has a thought.
brickspeed said:
I am in the exact same position ....
- new out of the box
- updated as part of the install process
- side-loaded Kodi with a "success" message
- rebooted as instructed with play and select for 5 seconds ....
- nothing, dead, no reboot, nothing, no light. Seems completely dead.
As the person above - let me know if you anyone has a thought.
Click to expand...
Click to collapse
I was reading the feedback on Amazon fire tv product page, apparently we are not the only ones.
Based on the users' feedback, seems like Amazon engineers have acknowledged that it's a known issue. SCARY.
I have the exact same thing, there is definitely a bad batch going around.
My Fire TV arrived on Monday, 2/16/15. I plugged it in and took an update as part of the setup. I installed several apps and logged in to accounts, watched about 3 hours of stuff on it that night. The next day it was dead as a door nail. No lights, no amount of button mashing on the remote made any difference. I have a replacement being sent out. The AFTV is currently out of stock, I'm curious if this is related.
I read another person complaining another site. Do we have anything resembling a common link? It seems so far this is effecting non-rooted aftvs with the latest update but not all aftvs. Are all of these units relatively new? Purchase date?
I just want to figure out if it's hardware or software related. I purchased another one after Xmas and no issues so far.
Just got mine, set it up, used it maybe for 2 hours, unplugged, connected to the TV and same thing. Dead.
Haha same thing happened to me. Got Kodi and everything installed. Unplugged the Fire TV and now it's bricked.
same happened to me.
got my unit today installed kodi fine. Was using the llama method to get a kodi icon added to the home screen. needed a reboot and used the select+play method on remote and now it won't turn back on. Contacted amazon and they are sending me a new replacement.
teng247 said:
got my unit today installed kodi fine. Was using the llama method to get a kodi icon added to the home screen. needed a reboot and used the select+play method on remote and now it won't turn back on. Contacted amazon and they are sending me a new replacement.
Click to expand...
Click to collapse
Anyone who have gotten their replacement units, may i know if you guys encounter the same issue again?
I am still waiting for my replacement set.
I'm guessing from the symptoms mentioned that it is their recent efuse blow up related. Maybe recent update did not update bootloader for some reason. If that so then box is not booting bootloader and sits in qualcomm recovery mode in which you can hook up it with usb "male a - male a" cable to pc and have full emmc access for flashing correct bootloader.
Add me on the list for a broken 1 day use on the AFTV. I sideloaded Kodi and was using it last night. Put it in sleep mode and then went to sleep myself. Woke up this morning and no lights/repsonse or anything on the box. Contacted Amazon customer support. One for the first few questions they asked is if I had sideloaded anything. I of course denied I did such a thing in case they try to back out of warranty issues. Customer Service Representative talks to her supervisor and instead of issuing a replacement unit they are sending me a new power adapter instead. Customer service rep states that her supervisor says from their experience that is usually the issue. I tell her with my voltage tester that i am detecting current running through the line. They still insist on power adapter.
Just to see if there is commonality among the AFTVs, did you guys get your boxes during the Sling TV promotion? Maybe a bad production batch?
How would side load affects the ability to power the box?? *puzzled*
There are so many users who did it, why does the issue only occurs recently.
An Amazon customer service told me this is not a common issue, but I have been seeing more and more of such cases.
All,
I have rooted at least 10 boxes, none fo my family or friends have report this issues. Of course, all these AFTV has Rbox pre-rooted firmware installed so i am going to guess folks who have reported this issues are non rooted boxes running the latest Amazon firmware.
It would ideal, If users who have reported this could provide the following info, this will help to identify a patter.
1) Serial number (it generally starts with 70900xxx)
3) Purchase date
4) Box purchased from?
4) Is your box rooted? If so what is have you installed (boatloader unlock (partial or fully) CWM, prerooted rom, ect)
5) what firmware is the box running (Amazon stock or Rbox), please provide the actual firmware version.
6) Was the firmware ever updated, if so from what version to what?
6) Sideloaded app
7) how long did you use the box before it went dead.
Thank you
tylerxm84 said:
How would side load affects the ability to power the box?? *puzzled*
There are so many users who did it, why does the issue only occurs recently.
An Amazon customer service told me this is not a common issue, but I have been seeing more and more of such cases.
Click to expand...
Click to collapse
Not a "common issue" is pretty subjective. What matters is its happened to several people in a short span of time, and xda members account for a tiny percentage of aftv owners. I contacted amazon for a different issue recently and what I realized was that rep giving support has never actually used a fire TV.
I don't think its the efuse like another person mentioned here unless it blew and had unintended consequences. Efuse, I think, is supposed to put it in an "obscure recovery mode". The box should power on. It'd still be useless but the fact that it does nothing makes me think its not efuse related.
For curiosity sake I'd like to hear what happens if they try a different power supply. Not amazon stock as that's been tried. But that might be academic, those boxes seem dead and unrecoverable. Since amazon will surely send a replacement, I'd open it up and see if there's anything noticeable. You won't find a blown efuse since that's not visible to the naked eye.
KLit75 said:
I don't think its the efuse like another person mentioned here unless it blew and had unintended consequences. Efuse, I think, is supposed to put it in an "obscure recovery mode". The box should power on. It'd still be useless but the fact that it does nothing makes me think its not efuse related.
Click to expand...
Click to collapse
How you identified than box is not powering on? Front white led indicator initialized when bootloader is loaded, if bootloader blacklisted by efuse there will be no light on front panel.
Ck-NoSFeRaTU said:
How you identified than box is not powering on? Front white led indicator initialized when bootloader is loaded, if bootloader blacklisted by efuse there will be no light on front panel.
Click to expand...
Click to collapse
You could very well be right. Just from reading vaguely about refuse, it renders the device useless but you would see something on the screen. I didn't think the light indicated boot loader. I thought it was an indication of power and it turns white when an internet connection is established. As far as I know...exactly how a blown refuse manifests on aftv has yet to be described.
KLit75 said:
You could very well be right. Just from reading vaguely about refuse, it renders the device useless but you would see something on the screen. I didn't think the light indicated boot loader. I thought it was an indication of power and it turns white when an internet connection is established. As far as I know...exactly how a blown refuse manifests on aftv has yet to be described.
Click to expand...
Click to collapse
I had first hand experience with a blown efuse. After certain pre-rooted ROM was loaded, it was ON,After the first reboot, unit had no LED light, nothing on screen. Using A A USB cable I can see the file structures of the unit, I was able to partially recovered (lost root) afterward.
These new units show the exact symptoms, dead after first reboot.
Unit won't come back on
I have the same problem. I am on my second unit. It powered up correctly, I re-registered, and I re-selected my favorites, I watched one show. I finished and turned it off. Now, nothing! I cannot turn it back on. This was the same problem with the first unit. I've tried all the basic hardware fixes - new batteries, new HDMI, etc, but still nothing. I have followed all the basic troubleshooting suggestions from Amazon. Still nothing. Can someone please suggest the right fix?
Related
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 Guys,
i bought a Fire TV today and i think i already ****ed up.
I unpacked it, plugged everything in and got no signal on my TV. I saw that the remote was working since the light on the AFTV responded to my inputs. Tried changing channels on my TV but nothing worked. Then i figured to restart the AFTV and see again. Did that 2 or 3 times and nothing.
Turns out the HDMI cable wasn't fully plugged in. Stupid i know, but happens i guess.
So now i got the signal and the AFTV said the update failed and it should restart in a few minutes. OMG i think i unplugged it while it updated? Oh god no.
It never did restart on its own. I waited at least 15 min. Then i unplugged it again like the screen said and now it is stuck in the boot animation logo. 45 min in and nothing happens.
So i think i bricked my brand new AFTV. Is there anything i can do or do i have to send it back. Cant reach amazon support and support page says nothing about this. I m so mad right now.
Plugged in a usb keyboard and got into recovery mode. Recovery mode says the device will reboot in a "few minutes". It doesn't. I'm stuck.
CaptainFlakes said:
Plugged in a usb keyboard and got into recovery mode. Recovery mode says the device will reboot in a "few minutes". It doesn't. I'm stuck.
Click to expand...
Click to collapse
I think if you hit escape or something you should be able to get to the recovery menu. You could try doing a factory reset.
No i can't do anything in the amazon recovery. It just says the AFTV will restart. But it doesn't.
Why don't you just phone Amazon? They are usually VERY helpful and will help you out
Arkadian1 said:
Why don't you just phone Amazon? They are usually VERY helpful and will help you out
Click to expand...
Click to collapse
Yeah they did. They send me replacement. Just hoped to avoid that. But there seems no way to properly reset the device.
Thx for the help guys.
CaptainFlakes said:
Yeah they did. They send me replacement. Just hoped to avoid that. But there seems no way to properly reset the device.
Thx for the help guys.
Click to expand...
Click to collapse
That's best I don't work for Amazon, but I can't deny that their customer service is second to none!
Useful to know, though... never unplug a Fire TV when it is updating
I did it once with an iPad... I managed to sort it out, but it wasn't the easiest thing in the world to accomplish.
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
Hi,
I have an issue with a FireTV Box. We bought it pre-rooted at the beginning of the year but didn't get on with it all that well.
We have since factory reset it, which in turn got rid of Kodi & now the box just appears to be as if we purchased it directly from Amazon.
Just recently the box doesn't appear to boot up. When I apply power to it, it switches on, the TV briefly (for about 3 seconds) displays the white Amazon logo and then everything disappears. Just a blank screen.
The screen is still receiving a signal from the box as it doesn't enter sleep mode etc. The box also appears to have booted (not sure what into) but i can see it/ping it over the network.
I have tried a factory reset (at least i think i have - right button & back button for 10 seconds) but without visual confirmation on-screen its hard to tell. Not sure if this combination of button presses actually initiates a reset, or it simply brings up the factory reset dialogue box whereby I would need a screen to confirm that option. I have also tried the button combination to switch between screen resolutions - this did do something in that the TV detected the resolution change, but through each change there was still only a blank screen - when i say blank, i mean black. Nothing at all displayed.
It appears I can't do anything with it. I have tried plugging it in to different TV's around the house, and using different HDMI cables.
I have searched and read many posts, but I'm unable to find something/someone who's had the same issues as me.
Hope someone can help!
Thanks in advance.
mrmcmint said:
Hi,
I have an issue with a FireTV Box. We bought it pre-rooted at the beginning of the year but didn't get on with it all that well.
We have since factory reset it, which in turn got rid of Kodi & now the box just appears to be as if we purchased it directly from Amazon.
A
Just recently the box doesn't appear to boot up. When I apply power to it, it switches on, the TV briefly (for about 3 seconds) displays the white Amazon logo and then everything disappears. Just a blank screen.
The screen is still receiving a signal from the box as it doesn't enter sleep mode etc. The box also appears to have booted (not sure what into) but i can see it/ping it over the network.
I have tried a factory reset (at least i think i have - right button & back button for 10 seconds) but without visual confirmation on-screen its hard to tell. Not sure if this combination of button presses actually initiates a reset, or it simply brings up the factory reset dialogue box whereby I would need a screen to confirm that option. I have also tried the button combination to switch between screen resolutions - this did do something in that the TV detected the resolution change, but through each change there was still only a blank screen - when i say blank, i mean black. Nothing at all displayed.
It appears I can't do anything with it. I have tried plugging it in to different TV's around the house, and using different HDMI cables.
I have searched and read many posts, but I'm unable to find something/someone who's had the same issues as me.
Hope someone can help!
Thanks in advance.
Click to expand...
Click to collapse
Have you tried pressing up and rewind at the same time on the remote and holding it for 5 seconds?
Try that (Hold it for 8 seconds t9 make sure)
This will cycle through resolutions incase your on an unsupported resolution.
sconnyuk said:
Have you tried pressing up and rewind at the same time on the remote and holding it for 5 seconds?
Try that (Hold it for 8 seconds t9 make sure)
This will cycle through resolutions incase your on an unsupported resolution.
Click to expand...
Click to collapse
Thanks for the reply. Yes, I have tried that, I think i mentioned that in original post but probably didn't make myself clear. When i tried that, i could see the TV changing something on-screen (ie a message appeared telling me what the screen resolution was) but this message was generated by my TV, not the AFTV device. The screen remained blank the whole time. At no point did anything appear on the TV generated by the AFTV box.
I'm at a loss with this now.
To summarise:
Blank screen after white Amazon logo (I can see approx the first 3 seconds of boot process on-screen)
I can't factory reset as i cant see the option on the screen
I have tried plugging device into different TV's
Tried different HDMI cables
Tried button combination to change screen resolution
All TV's that i plug the AFTV box into first display the resolution of 1920*1080 60 for the first 3 seconds of boot, switches to 480 thereafter which is when screen goes blank
mrmcmint said:
Thanks for the reply. Yes, I have tried that, I think i mentioned that in original post but probably didn't make myself clear. When i tried that, i could see the TV changing something on-screen (ie a message appeared telling me what the screen resolution was) but this message was generated by my TV, not the AFTV device. The screen remained blank the whole time. At no point did anything appear on the TV generated by the AFTV box.
I'm at a loss with this now.
To summarise:
Blank screen after white Amazon logo (I can see approx the first 3 seconds of boot process on-screen)
I can't factory reset as i cant see the option on the screen
I have tried plugging device into different TV's
Tried different HDMI cables
Tried button combination to change screen resolution
All TV's that i plug the AFTV box into first display the resolution of 1920*1080 60 for the first 3 seconds of boot, switches to 480 thereafter which is when screen goes blank
Click to expand...
Click to collapse
Is it fire tv 1 or 2?
Honestly not sure, it's the one without an optical connection if that makes any difference.
Thanks
mrmcmint said:
Honestly not sure, it's the one without an optical connection if that makes any difference.
Thanks
Click to expand...
Click to collapse
So it the fire tv 2 box.
Can you tell me what firmware version it was on before the trouble started?
If it is not on the very latest, you always have the option of using an A-A usb lead and recovering it, the guide is on here:
http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
sconnyuk said:
So it the fire tv 2 box.
Can you tell me what firmware version it was on before the trouble started?
If it is not on the very latest, you always have the option of using an A-A usb lead and recovering it, the guide is on here:
http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
Click to expand...
Click to collapse
Hi,
Thanks for this, i'll have a read.
I have no idea what version of fw it was on, I really never messed with it other than the factory reset.
If there's any way i can find that out, i'll post it on here.
Thanks again
Write it off.
Its only so fun to support people that bought prefab boxes because they had the label "free stuff" on it, then don't know what they bought, or what firmware they were on.
Long story short - if you are on an older firmware - you might be able to recover, using the USB A to A (male to male) cable brick recovery method.
If you are on a newer firmware - this is not an option (didn't doublecheck it, but I'm quite sure).
Also - none of this may be possible, or fix your issue - depending on the cause of the issue. I had mine give out on the second day of using it - with the same error profile. I had a custom recovery on there by theat point - I could reflash the stock rom successfully - same error profile. Wiped TWRP and took the box back (of course I didn't pay shady thirdparties for the privilege of "free stuff").
Other people have reported, that taking the box off power for a view hours "magically cured" an issue like this in some cases - I'd be sceptical it does, but you can try it.
If the animated (colorful) Amazon boot logo doesnt show up, the OS isn't even booting - so something is messed up on the HW or the partition level, or on the file system level. Hard to diagnose, hard to fix remotely. The only way you "might" be able to "talk to the device" is the USB A to A (male to male) unbrick method - try that if you want to. You'll find the tutorial on XDA.
harlekinwashere said:
Write it off.
Its only so fun to support people that bought prefab boxes because they had the label "free stuff" on it, then don't know what they bought, or what firmware they were on.
Long story short - if you are on an older firmware - you might be able to recover, using the USB A to A (male to male) cable brick recovery method.
If you are on a newer firmware - this is not an option (didn't doublecheck it, but I'm quite sure).
Also - none of this may be possible, or fix your issue - depending on the cause of the issue. I had mine give out on the second day of using it - with the same error profile. I had a custom recovery on there by theat point - I could reflash the stock rom successfully - same error profile. Wiped TWRP and took the box back (of course I didn't pay shady thirdparties for the privilege of "free stuff").
Other people have reported, that taking the box off power for a view hours "magically cured" an issue like this in some cases - I'd be sceptical it does, but you can try it.
If the animated (colorful) Amazon boot logo doesnt show up, the OS isn't even booting - so something is messed up on the HW or the partition level, or on the file system level. Hard to diagnose, hard to fix remotely. The only way you "might" be able to "talk to the device" is the USB A to A (male to male) unbrick method - try that if you want to. You'll find the tutorial on XDA.
Click to expand...
Click to collapse
Yep, understand all your points. This is merely a last-ditched attempt at some sort of success before it gets thrown out. I wouldn't have bought it in the first place - wife found it on a popular social networking site and had bought it before i had any input. Agreed about the 'shady' nature of the device - who knows what is on here. If i could completely wipe the device and make it so it was like we had bought it directly from Amazon, I would. If i wanted something similar, I would have built it on a raspberry pi probably, but more for fun and learning curve than anything else. That said, I do understand why people would want to root their own AFTV devices and play with them - they have more control this way, and I quite like the hardware.
You mention the colourful Amazon boot logo - this never appears. But... It must be booting into *something* as i can ping the device on my network. It's almost like it has fully booted and is ready for action, just that the 'graphics chip' or drivers die and it fails to display anything on the screen. Another reason I suspect it has successfully booted into *something* is because the button combinations work to scroll through the screen resolutions. Whether it needs to have booted fully to enable that feature, I don't know.
I'll have a go at the above guide when i'm home and see what happens - at this point there is absolutely nothing to lose - only time.
At least you are open about it and willing to learn. Have to give you props for that.
The issue with "give us money for free, casual" (last posting about this) is that you dont get support with it. Usually. ("I found it on facebook - it told me it would give me free for only 99.99...") So what happend to this community initially is that it got the "frenzy fun - bought for simple and free and it worked yesterday" crowd during the entire popularity peak of this device.
The Kodi community lost Android maintainers to the "i think we can make money here as well" pull and resulting internal conflict (and thats fair, but...), had to push through a public statement about its zero tolerance policy on piracy addon support, because they were swamped (30 postings a day - with people that never read anything but the tagline sold to them by shady thirdparties) with people looking up "Kodi" and then going on to solicit "help requests" from a dev community "facebook style ("my girlfriends old mother, ...")".
Reddit was full with bad advice, some of which was popularized by bloggers that saw it as a commercial opportunity (mostly talking about the youtuber scene, but not exclusively).
Kodi was removed from the Amazon Appstore on grounds of "public perception" (thanks "free and easy for a onetime payment of 99.99 crowd") alone - Amazon was allowed to start heavily overreaching and deciding what apps people would be allowed to use on the device (almost no one even had an issue with anything they did (ruined the basis of existence for the homebrew scene (if you are an app developer - how about you submit the app to our store?), by stripping out basics that we needed (which is why you probably won't be able to recover the device - even if it is recoverable ("is it running recent Amazon software"?)) - people just were afraid to loose free and as a result complacent to the actions that took place - people shushed you if you had nothing but cursewords for Amazon actively destroying the ecosystem - because as long as they left piracy working - "maybe it wasnt that bad") and what apps would have to be disabled (the ones that reduced their advertising effectiveness) - and the most popular people at that time were the bloggers that decided, that the crowd should enjoy "easy and free" (as in advertisment supported, as far as they were concerned), all the way until Amazon switched the rails and led them just as "easy and free" back into the subscription model again. Bloggers and all.
The subscription model needs channel exclusivity (or backroom deals) and heavy DRM safe guards, so If thats what people wanted all along, why did they cosy up with the hacking scene? (Which is strongly linked to consumer and device rights ideals, the open source ethos, ....) Those are two basically contrary vantage points.
You factory reset your Fire TV, right? It was easier that way - right? Using Plex - also, very easy. Its right there on the frontpage. Just sign into your account, pay the monthly fee...
So two lessons
- Never underestimate a crowd pulled by the sentiment of "free" to be able to ruin a community and leave only ashes.
- If they get pulled back into a subscription model again - let them. They want easy - they don't know how. They pay 10 USD a month and they get someone to talk to them for that, on the other end of a phone line.
But why should the hacking community ever provide product support essentially "for Amazon?" We arent responsible if a device becomes defect on its own. We arent the ones that told you to buy from a shady source that eliminated the warranty and "gesture of good will" exchange options. We are just the ones the "free and easy crowd" would never pay 50 bucks an hour (or more), because it probably would turn out to be more than they paid for the entire set up device (automated) in the fist place. The one that was supposed to give them free.
So this becomes a charity. (If people are in it to learn, it becomes a learning environment.. - but everyone just wanted easy - so...)
And what do you do with charities as a majority group? You try to exploit them. In some cases. Nature of the beast I guess..
harlekinwashere said:
At least you are open about it and willing to learn. Have to give you props for that.
The issue with "give us money for free, casual" (last posting about this) is that you dont get support with it. Usually. ("I found it on facebook - it told me it would give me free for only 99.99...") So what happend to this community initially is that it got the "frenzy fun - bought for simple and free and it worked yesterday" crowd during the entire popularity peak of this device.
The Kodi community lost Android maintainers to the "i think we can make money here as well" pull and resulting internal conflict (and thats fair, but...), had to push through a public statement about its zero tolerance policy on piracy addon support, because they were swamped (30 postings a day - with people that never read anything but the tagline sold to them by shady thirdparties) with people looking up "Kodi" and then going on to solicit "help requests" from a dev community "facebook style ("my girlfriends old mother, ...")".
Reddit was full with bad advice, some of which was popularized by bloggers that saw it as a commercial opportunity (mostly talking about the youtuber scene, but not exclusively).
Kodi was removed from the Amazon Appstore on grounds of "public perception" (thanks "free and easy for a onetime payment of 99.99 crowd") alone - Amazon was allowed to start heavily overreaching and deciding what apps people would be allowed to use on the device (almost no one even had an issue with anything they did (ruined the basis of existence for the homebrew scene (if you are an app developer - how about you submit the app to our store?), by stripping out basics that we needed (which is why you probably won't be able to recover the device - even if it is recoverable ("is it running recent Amazon software"?)) - people just were afraid to loose free and as a result complacent to the actions that took place - people shushed you if you had nothing but cursewords for Amazon actively destroying the ecosystem - because as long as they left piracy working - "maybe it wasnt that bad") and what apps would have to be disabled (the ones that reduced their advertising effectiveness) - and the most popular people at that time were the bloggers that decided, that the crowd should enjoy "easy and free" (as in advertisment supported, as far as they were concerned), all the way until Amazon switched the rails and led them just as "easy and free" back into the subscription model again. Bloggers and all.
The subscription model needs channel exclusivity (or backroom deals) and heavy DRM safe guards, so If thats what people wanted all along, why did they cosy up with the hacking scene? (Which is strongly linked to consumer and device rights ideals, the open source ethos, ....) Those are two basically contrary vantage points.
You factory reset your Fire TV, right? It was easier that way - right? Using Plex - also, very easy. Its right there on the frontpage. Just sign into your account, pay the monthly fee...
So two lessons
- Never underestimate a crowd pulled by the sentiment of "free" to be able to ruin a community and leave only ashes.
- If they get pulled back into a subscription model again - let them. They want easy - they don't know how. They pay 10 USD a month and they get someone to talk to them for that, on the other end of a phone line.
But why should the hacking community ever provide product support essentially "for Amazon?" We arent responsible if a device becomes defect on its own. We arent the ones that told you to buy from a shady source that eliminated the warranty and "gesture of good will" exchange options. We are just the ones the "free and easy crowd" would never pay 50 bucks an hour (or more), because it probably would turn out to be more than they paid for the entire set up device (automated) in the fist place. The one that was supposed to give them free.
So this becomes a charity. (If people are in it to learn, it becomes a learning environment.. - but everyone just wanted easy - so...)
And what do you do with charities as a majority group? You try to exploit them. In some cases. Nature of the beast I guess..
Click to expand...
Click to collapse
Oh i agree completely - i wouldn't have the time nor the inclination to support these DIY boxes, let alone support them remotely on a voluntary basis with someone who hasn't got a clue what they're doing at the other end. I fully appreciate that. For the record, there are no lessons learnt here for me (although for others that read this there might be) - I was already aware of this and have exactly the same opinion as you Like I said - I never would have bought it in the first place. I'm just grateful to anyone who takes the time to reply to me & others with similar issues.
I'm back home, i'll see if i can find the right cable, I know I have one somewhere from an old 2.5" HDD caddy I had lying around. If I can't bring this thing back to life & get rid of all the third party stuff, its heading for the bin. Next stop Amazon to buy a retail item with warranty & support.
Did you ever find a resolve for this? I have the same problem right now. It will work on my TV, but not through my projector (which it has now since day one 6 months ago).
If you can ping the box then try to adb connect to it. If you can connect then adb reboot it to recovery
same problem. can't connect with adb
The Problem is with the TV
i think the problem is with the TV i have two TV's this happens on my Sony TV but works well on my Other TV
my sony TV already has some problem, some devices recognize the TV some don't.
one amazon tv box fix
on my amazon tv box 3rd gen i think. my device would kinda start but then blank. i got my tv remote not fire tv remote. element tv remote i pressed menu then display and changed from user to dinamic and then movie and pc and then i was able to see my fire tv screen. problem is compatability with the tv i think.
Check cable. In My case direct Connect to projector working but when conneced to 7m hdmi cable projector showing only logo Amazon then black screen.
I have to reinstall my firmware each time this happens. Good thing for TWRP recovery!
My FireTV is stuck in boot. I get a black screen with white amazon logo (no orange colours). The white light slowly flashes on the front box, and eventually my TV eventually gets a no signal response.
The device registers the remote, (every click gives the white light comes on) but I am unable to go into recovery (Right button + Back Button). Opening up ADBLink, I am able to connect to the device by IP address, and I can reboot the device remotely and I can enter reboot recovery. When I enter reboot recovery, the FireTV reboots and in red writing I get
"Your Amazon Firetv will restart in a few minutes, and show resume normal operation, If it does not restart please unplug the power cable and plug it back in to force a restart. If you need assistance please contact support at Amazon" .
However nothing happens, and when I restart I get stuck at the white amazon logo.
I have tried 3 separate keyboards and tried ALT + Print screen, or ALT + i + Print Screen, or ALT+ Home, or ALT + i + home. None of them worked.
It has the stock OS installed (Dont know which version but assume the latest update), and the only action beyond normal operation has been the sideloading of a couple of common APKs. (No rooting, bootloader it locked). As it is out of warrrenty Amazon are little help (15% discount on next FireTV purchase).
Is there anything I can do, or is my box now a paper weight ?
If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.
rainman74 said:
If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.
Click to expand...
Click to collapse
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious
abfmdf said:
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious
Click to expand...
Click to collapse
Good luck to you! :fingers-crossed: