Tried to sideload the google play store. Fire tv crashed and seemed to go into a boot loop. When it plugs in, there is a solid orange light, after about 10 seconds it will flag white once (looks as if it’s rebooting) and then go back solid orange.
No amazon logo and no signal. I’ve tried leaving it plugged in for a day. Also tried unplugging it for a couple days. Any thoughts or help on this?
Sounds like it's bricked. Should be recoverable if you're willing to open it up.
i got a fire tv 2 with a similar issue from trying todo the "unbrick with short" method. my devices had already had that process done successfully but along the road i did a disco at a bad time and now whenever i do the unbrick via short method i get a fail because the script says theres a GPT partition or something.
I had this happen with a firestick 2nd gen(tank) but i eventually found a comment that led to altering the script to format the partitions back to MBR.
I HAVE NOT FOUND THE SAME FOR THE FIRETV 2.
idk
bogart1117 said:
i got a fire tv 2 with a similar issue from trying todo the "unbrick with short" method. my devices had already had that process done successfully but along the road i did a disco at a bad time and now whenever i do the unbrick via short method i get a fail because the script says theres a GPT partition or something.
I had this happen with a firestick 2nd gen(tank) but i eventually found a comment that led to altering the script to format the partitions back to MBR.
I HAVE NOT FOUND THE SAME FOR THE FIRETV 2.
idk
Click to expand...
Click to collapse
The amonet gpt-fix for the FireTV2 box isn't public (til of today), you may ask in the unbrick thread for it
Been awhile Sus
Sus_i said:
The amonet gpt-fix for the FireTV2 box isn't public (til of today), you may ask in the unbrick thread for it
Click to expand...
Click to collapse
You helped me before in the unbrick thread. i got it workimg and then did some stupid mistake on the software side and never recovered. I was just snooping and found this and love the irony of you popping up with the answer.
Well thanx for the heads-up. Let me know if you come across the new gpt/mbr script in case I haven't stumbled into it.
bogart1117 said:
You helped me before in the unbrick thread. i got it workimg and then did some stupid mistake on the software side and never recovered. I was just snooping and found this and love the irony of you popping up with the answer.
Well thanx for the heads-up. Let me know if you come across the new gpt/mbr script in case I haven't stumbled into it.
Click to expand...
Click to collapse
Yeah, I was a bit surprised to see your posting
This gpt issue should be solvable, just go ahead to the sloane unbrick thread and tell it Rortiz2... :good:
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
JonDaniels said:
Tried to sideload the google play store. Fire tv crashed and seemed to go into a boot loop. When it plugs in, there is a solid orange light, after about 10 seconds it will flag white once (looks as if it’s rebooting) and then go back solid orange.
No amazon logo and no signal. I’ve tried leaving it plugged in for a day. Also tried unplugging it for a couple days. Any thoughts or help on this?
Click to expand...
Click to collapse
What kind of FireTV box is it? The first one or the second?
Related
Hi Guys,
I've been rooting android devices for a while now, and this is the first time I've had to post up a question like this... Can't seem to get the Kindle Fire 8.9 to power on. Tried holding power down for over a minute, not dice. 20 seconds, no dice.... I've done a search and can't seem to find anyone else with a 8.9 in this situation. I reached out to SkOrPn and he mentioned for the 8.9 there is NO factory cable to push into fastboot.
Hopefully someone can shed some light?
Thanks.
mcgrathpatj said:
Hi Guys,
I've been rooting android devices for a while now, and this is the first time I've had to post up a question like this... Can't seem to get the Kindle Fire 8.9 to power on. Tried holding power down for over a minute, not dice. 20 seconds, no dice.... I've done a search and can't seem to find anyone else with a 8.9 in this situation. I reached out to SkOrPn and he mentioned for the 8.9 there is NO factory cable to push into fastboot.
Hopefully someone can shed some light?
Thanks.
Click to expand...
Click to collapse
Did you brick it? Sounds like you did.
seokhun said:
Did you brick it? Sounds like you did.
Click to expand...
Click to collapse
Sure seems like I did... I was hoping someone could confirm I did or may have a solution.
If I did it's my first brick! Kind of funny actually. I bought it at best buy.... Hopefully they won't give me too much **** trying to return it.
mcgrathpatj said:
Sure seems like I did... I was hoping someone could confirm I did or may have a solution.
If I did it's my first brick! Kind of funny actually. I bought it at best buy.... Hopefully they won't give me too much **** trying to return it.
Click to expand...
Click to collapse
If you're in warranty, you're good to go. If not, you can always go the factory cable route, see the thread in my signature for the 8.9" #6 and Step 2.
mcgrathpatj said:
Hi Guys,
I've been rooting android devices for a while now, and this is the first time I've had to post up a question like this... Can't seem to get the Kindle Fire 8.9 to power on. Tried holding power down for over a minute, not dice. 20 seconds, no dice.... I've done a search and can't seem to find anyone else with a 8.9 in this situation. I reached out to SkOrPn and he mentioned for the 8.9 there is NO factory cable to push into fastboot.
Hopefully someone can shed some light?
Thanks.
Click to expand...
Click to collapse
Sorry to tell you this but if a KFHD is not powering up even when charged, It's hard bricked, But don't panic.
May i ask what tool you used to root your device, Because it seems to me that you used Kindle Fire Utility KFU, I know this because failing the rooting process can cause a bootloop but will not hard brick your device the way it happened, Only a damaged bootloader can cause the device not to power up, KFU attempts to install FFF bootloader which is designed for the original kindle fire and will damage the bootloader of any 2nd generation device and hard brick it.
What you need to do right now
Ship your device ASAP to Christian Bryant (XDA username Prokennexusa), At
Xerocomm, Inc. - 1684 Northstar Drive - Petaluma CA 94954.
I talked to him and he said if you ship it now it'll be done by the end of the week.
Chris receives many kindles so make sure you send him an email at [email protected]
Good luck
Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Sorry I'm not likely to have a fix, but are you sure you unlocked boot loader before attempting to install the boot menu? This could be the cause for the brick.
Are you able to boot to recovery? If so you might be ok. I VERY TENTATIVELY say that if you can get into recovery from there either a factory reset or reflashing a prerooted fw might help BUT if you're able to get there PLEASE don't proceed till someone with more experience chimes in!
I will say that there's hope if you can get to recovery... probably? But this never happened to me.
Have you tried restarting with usb keyboard attached and pressing the print alt screen? Good luck.
Phill360 said:
Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Click to expand...
Click to collapse
hi,
I am not an expert on this matter but you should provide detail info exactly what you did to your Fire TV, the exact steps and sequence so folks can help you better.
In the meantime, check these all link out before you do anything. It seems few folks has some success see link 2 and 3 as always try it on your risk. I hope someone else can provide a better solution.
http://www.aftvnews.com/top-ways-to-brick-your-fire-tv/
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
http://forum.xda-developers.com/showthread.php?t=2799779
http://www.aftvnews.com/factory-reset-on-amazon-fire-tv-and-fire-tv-stick-explained/
btw, if you are using amazon fire tv for xbmc as it seems most folks are using it for, i would just get Raspberry PI, it is awesome never had to worry about bricking the damn thing, sure it slower than fire tv but i have use it and i love it, it plays 1080 and 3d movies and no buffering either.
I also fire tv but i am always scared this thing will brick as it seems many folks have this problem.
Thank you
KLit75 said:
Sorry I'm not likely to have a fix, but are you sure you unlocked boot loader before attempting to install the boot menu? This could be the cause for the brick.
Are you able to boot to recovery? If so you might be ok. I VERY TENTATIVELY say that if you can get into recovery from there either a factory reset or reflashing a prerooted fw might help BUT if you're able to get there PLEASE don't proceed till someone with more experience chimes in!
I will say that there's hope if you can get to recovery... probably? But this never happened to me.
Have you tried restarting with usb keyboard attached and pressing the print alt screen? Good luck.
Click to expand...
Click to collapse
Thanks for the reply Klite, I didn't unlock the bootloader before installing the menu so that must have caused the brick.
I'm only able to see the Amazon logo, it does not reach the Fire TV Logo. I have plugged in a USB keyboard but i can't seem to get to recovery.
ashsha7877 said:
hi,
btw, if you are using amazon fire tv for xbmc as it seems most folks are using it for, i would just get Raspberry PI, it is awesome never had to worry about bricking the damn thing, sure it slower than fire tv but i have use it and i love it, it plays 1080 and 3d movies and no buffering either.
I also fire tv but i am always scared this thing will brick as it seems many folks have this problem.
Thank you
Click to expand...
Click to collapse
Hi Ashsha
I do mainly use my FTV for Kodi, I did previously use a Raspberry Pi but i bought this to replace it as i wanted something more powerful due to the problems i was having with stutters during play back.
Thanks for the links too, i did try them but i have had no luck so far.
Does anyone know if it possible to unbrick my FTV via USB using Fastboot or ADB?
Phill360 said:
Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Click to expand...
Click to collapse
Phill360 said:
Does anyone know if it possible to unbrick my FTV via USB using Fastboot or ADB?
Click to expand...
Click to collapse
That's a very good question. I know it's pretty much essential to unbrick a kindle fire but can't find any info specific to aftv. But you're motivation to get an answer is greater than mine. Do you have one?
I'd be confident in trying it with a phone or tablet but I just don't know enough about the variables (like could you do more damage sending power to somewhere that has an external power source)
My best advice is to be patient, keep looking for possible fixes online, but I'd caution not to experiment. Instead keep coming back here to get thoughts on possible fixes that might work. At the very least your thread will stay high in the forum search results giving you a better chance of having the right xda member to notice it.
KLit75 said:
That's a very good question. I know it's pretty much essential to unbrick a kindle fire but can't find any info specific to aftv. But you're motivation to get an answer is greater than mine. Do you have one?
I'd be confident in trying it with a phone or tablet but I just don't know enough about the variables (like could you do more damage sending power to somewhere that has an external power source)
My best advice is to be patient, keep looking for possible fixes online, but I'd caution not to experiment. Instead keep coming back here to get thoughts on possible fixes that might work. At the very least your thread will stay high in the forum search results giving you a better chance of having the right xda member to notice it.
Click to expand...
Click to collapse
If you didn't follow the directions and didn't unlock, then it is bricked and the only way to fix it is the hw mod to write to the mmc. If you have an A to A plugged in, on boot it'll stop in the bootloader and fastboot will work, unfortunately there is no commands you can actually run that will do anything. If you don't have an A to A plugged in, it will try to load the boot image. Since you didn't unlock, it won't boot the image, and it'll just die.
if all else fails, you can always go to amazon for replacement, remember amazon fire tv hasn't been a year old yet and you still have warranty for it, thats what i did with mine, i acted i didn't know what i was doing and suddenly it wouldn't load or boot up, etc.. u will need to know ur email adress or account thats associated with ur fire tv.. op korz .. they will do it... 100%
rbox said:
If you didn't follow the directions and didn't unlock, then it is bricked and the only way to fix it is the hw mod to write to the mmc. If you have an A to A plugged in, on boot it'll stop in the bootloader and fastboot will work, unfortunately there is no commands you can actually run that will do anything. If you don't have an A to A plugged in, it will try to load the boot image. Since you didn't unlock, it won't boot the image, and it'll just die.
Click to expand...
Click to collapse
Thanks for the reply rbox.
So what your saying is my Fire TV is dead.
I might just move on then to a new device like the Razor Forge TV when that comes out.
daffung said:
if all else fails, you can always go to amazon for replacement, remember amazon fire tv hasn't been a year old yet and you still have warranty for it, thats what i did with mine, i acted i didn't know what i was doing and suddenly it wouldn't load or boot up, etc.. u will need to know ur email adress or account thats associated with ur fire tv.. op korz .. they will do it... 100%
Click to expand...
Click to collapse
I'd love to return my FTV under warranty but i live in Australia and can't be bothered paying for postage to get it replaced
Just wondering if anyone has worked out a way of fixing this type of Brick?
Not sure was version of the software on, I'm hoping that it might be on 51.1.6.1 or 54.1.2.1
thanks
Phill360 said:
Just wondering if anyone has worked out a way of fixing this type of Brick?
Not sure was version of the software on, I'm hoping that it might be on 51.1.6.1 or 54.1.2.1
thanks
Click to expand...
Click to collapse
Depending on how much of the instructions you actually followed, and if your bootloader is 51.1.0.2 or older, there is a method that @AFTVnews.com is working on a writeup for that should recover it. But if the bootloader wasn't downgraded to 51.1.0.2, then it's dead.
Hi there. I've two fire tv's. One is on FW 51.1.0.2 and rooted. I havent installed anything except kodi.
No partial bootloader, no ClockWorkMod. Nothing.
I've bought the second one 4 days ago. And I've started to follow AFTV news sites guide.
I've succesfully updated it to the fw version 51.1.4.0. When i tried to install Rbox's boot menu to my second fire TV
I've accidentaly installed it to my first fire tv (the one with fw 51.1.0.2). And its bricked. It hangs on white amazon logo.
Any advice?
Do you have a wireless keyboard? If so, while its booting, try this by holding the alt, prt scr and i button. Try hitting those buttons four to five times and the system should boot up in clockwork mod.
I've tried with 3 different USB keyboards. No luck.
Berrybare said:
Do you have a wireless keyboard? If so, while its booting, try this by holding the alt, prt scr and i button. Try hitting those buttons four to five times and the system should boot up in clockwork mod.
Click to expand...
Click to collapse
He did not have CWM installed on this box, so it is no way getting back in now.
I guess so.
my adb server directly connected to my first FTV.
When i realize I've panicked and restarted.
Stuck at white amazon logo... So there is no hope?
ninefingers_heh said:
I guess so.
my adb server directly connected to my first FTV.
When i realize I've panicked and restarted.
Stuck at white amazon logo... So there is no hope?
Click to expand...
Click to collapse
Sorry to say, but i dont think theres anything you can do.
You might contact amazon for a replacement. Technically they dont have to replace it because you knowingly tampered with the box but from what ive read about how great customer service is...i have a theory that theyd be willing to take a loss on the hardware in order to keep that amazon store in your house. And the new update really takes a lot of the benefits of rooting away.
I live in Turkey. And also it's a second hand unit.
I bought someone who went to USA for a short time.
I'll put the box away and cross my fingers for a solution. Thanks.
Hey guys,
So it's been a while since updated my rooted FTV2 but decided to updated it to the latest prerooted image found on XDA. It had some freezing issue and I wiped the system and rebooted (didn't know I shouldn't reboot after a wipe). Now the fire tv is stuck on the white amazon logo with the black background. I can't access TWRP.
Is it bricked? Is there anyway I can restore it (considering I had TWRP on it before)? I tried connecting it via a USB A-A and on my Mac, with the android file transfer application, it would show could not connect to device. I tried listing the devices through "fastboot devices" but nothing shows up.
Is there any hope? Thank you.
DVO99 said:
Hey guys,
So it's been a while since updated my rooted FTV2 but decided to updated it to the latest prerooted image found on XDA. It had some freezing issue and I wiped the system and rebooted (didn't know I shouldn't reboot after a wipe). Now the fire tv is stuck on the white amazon logo with the black background. I can't access TWRP.
Is it bricked? Is there anyway I can restore it (considering I had TWRP on it before)? I tried connecting it via a USB A-A and on my Mac, with the android file transfer application, it would show could not connect to device. I tried listing the devices through "fastboot devices" but nothing shows up.
Is there any hope? Thank you.
Click to expand...
Click to collapse
It has been discovered that It is almost impossible to completely brick these devices by software only.
There is always a way to revive these devices and methods to recover them are becoming easier.
So don't throw them away and keep an eye on the other thread, there is hope.
.:HWMOD:.
hwmod said:
It has been discovered that It is almost impossible to completely brick these devices by software only.
There is always a way to revive these devices and methods to recover them are becoming easier.
So don't throw them away and keep an eye on the other thread, there is hope.
.:HWMOD:.
Click to expand...
Click to collapse
Thank you for the reply. I will definitely not throw them away. It was my fault that I didn't re-read all the warnings (lesson learned). Hopefully something comes up for it soon.
DVO99 said:
Thank you for the reply. I will definitely not throw them away. It was my fault that I didn't re-read all the warnings (lesson learned). Hopefully something comes up for it soon.
Click to expand...
Click to collapse
I did the same thing last night, not paying attention. I have two FTV2 though, managed not to mess up the other one. Here's hoping one day we can bring them back to life. :highfive:
Seriiez said:
I did the same thing last night, not paying attention. I have two FTV2 though, managed not to mess up the other one. Here's hoping one day we can bring them back to life. :highfive:
Click to expand...
Click to collapse
Haha, yeah it sucks. The worst part is in Canada there is only fire tv sticks, so I'm kinda stuck unless I get another android tv box.
Me too,
i tried to install Gapps, but with no success, the AFTV gen2 was rooted and working nice.
To eliminate the leftovers i tried to restore a /System and /Data backup with TWRP, but the system was wiped and the partitions was not maked again.
now i have a brick, with no fastboot and only amazon black&white logo
Any Ideas?
Hello
I have a Fire TV box 2nd gen (not stick).
Yesterday the hdmi signal suddenly showed white noise for 2-3 seconds. Then the menu again. (Then I think it froze, not sure...) I remeber I turned it off, took it from power and tried to boot again. But it did not.
It shows the white amazon logo for a moment, then "no signal" on any TV or HDMI I try.
The white LED is pulsing slowly.
I tried << and UP to change resolution, nothing.
Customer service thinks there is a HDMI-HDCP Problem(?) and white LED means it tries to boot.
Question:
Is there any way to re-set the whole thing, make a clear fresh installation via USB?
Or is this thing a brick now?
(I did many things, turned it off for hours, let it try to boot for 1 hour. Changed HDMI cables and HDMI slots and changed from TV to a beamer ..it just always does the same. I have no idea if the remote really reacts on << [UP] cause there is no light indicator)
What I did not do: Connect via USB to a computer (cant find a old standard USB cable at the moment)
Thanks
Bodo
bodomalo said:
Is there any way to re-set the whole thing, make a clear fresh installation via USB?
Click to expand...
Click to collapse
Take a look into this thread... Maybe you find in this 'unbrick thread' an answer
Sus_i said:
Take a look into this thread... Maybe you find in this 'unbrick thread' an answer
Click to expand...
Click to collapse
I guess that means no....
That thread is too long to read everything, the solution is first from 2016, and the last message 22 pages later from June 2019
bodomalo said:
I guess that means no....
That thread is too long to read everything, the solution is first from 2016, and the last message 22 pages later from June 2019
Click to expand...
Click to collapse
I guess that nobody reads the thread for you
From what I've read, a pulsing light and stuck at amazon logo/black screen is a brick, maybe a hardware failure.
You can place your question in detail in the suggested thread, maybe you get there an answer. Or sell the item on ebay
The exact same thing just happened to me this morning. Worked perfect last night.... then turn it on this morning and nothing... after power cycling just the white Amazon logo then goes black then slow pulsing light. Tried to reset via the remote with the back & forward and held until orange light then it just went back to doing the same thing.
Dominic
I just ran into this issue myself. My 2nd Gen is running a rooted rom and has worked fine for a couple years but tonight we were watching some Hulu and the screen went blank in the middle of a show. I did a power cycle and it boots to the TWRP boot screen, then I get the white amazon logo. After which, the TV loses signal. The device seems to boot for a short while before getting the pulsing white LED.
I can still go into TWRP and access everything so I've performed a full reset which changed nothing. I also downloaded and installed an updated ROM July 4, 2020 - 5.2.7.3_r1 but it responds exactly the same after the update.
Fortunately I have a spare Fire TV 2 (thanks ebay) so I was able to swap things over pretty quick. This also confirmed the power adapter was not the issue as the replacement seems to be working fine with the same adapter. I also tested the original one with a 15.5v, 3.4amp adapter and no change. I feel like maybe the video processor may have burned up at this point.
Still open to any suggestions though.
Hannover2k said:
I just ran into this issue myself. My 2nd Gen is running a rooted rom and has worked fine for a couple years but tonight we were watching some Hulu and the screen went blank in the middle of a show. I did a power cycle and it boots to the TWRP boot screen, then I get the white amazon logo. After which, the TV loses signal. The device seems to boot for a short while before getting the pulsing white LED.
I can still go into TWRP and access everything so I've performed a full reset which changed nothing. I also downloaded and installed an updated ROM July 4, 2020 - 5.2.7.3_r1 but it responds exactly the same after the update.
Fortunately I have a spare Fire TV 2 (thanks ebay) so I was able to swap things over pretty quick. This also confirmed the power adapter was not the issue as the replacement seems to be working fine with the same adapter. I also tested the original one with a 15.5v, 3.4amp adapter and no change. I feel like maybe the video processor may have burned up at this point.
Still open to any suggestions though.
Click to expand...
Click to collapse
Idk if it helps, but I would try a format data in wipe section of TWRP.
Could be that the eMMC died, i.e. at an unknown point, the storage switches to readonly, especially if the eMMC is a samsung chip.
Booting TWRP still works, in that case.
This happend to @Rortiz2 fireTV2 development box, maybe ask him for details.
What kind of errors are in the recovery log?
Sus_i said:
Idk if it helps, but I would try a format data in wipe section of TWRP.
Could be that the eMMC died, i.e. at an unknown point, the storage switches to readonly, especially if the eMMC is a samsung chip.
Booting TWRP still works, in that case.
This happend to @Rortiz2 fireTV2 development box, maybe ask him for details.
What kind of errors are in the recovery log?
Click to expand...
Click to collapse
I don't know how to get to the logs but happy to post if you can tell me.
On another note, I noticed the replacement device, while just recently connected and has also been rooted, tried to download the 5.2.7.4 update today. Typically my rooted devices never updated so this is a new discovery. I pulled the plug on it before it finished downloading but I'm worried I'll loose root if it updates. There's no pre-rooted ROM for 5.2.7.4 yet so I'm afraid to plug the power back in for fear it will update and unroot/brick like the 1st one.
Hannover2k said:
I don't know how to get to the logs but happy to post if you can tell me. .
Click to expand...
Click to collapse
Boot into TWRP, click mount and mount system, start the filemanager (in advanced tab), then go to /tmp, in there should be a recovery.log file, copy this file to your ext. sd or adb pull it to your PC.
Edit your serials in the file and upload it on mega, gdrive or so.
Hannover2k said:
On another note, I noticed the replacement device, while just recently connected and has also been rooted, tried to download the 5.2.7.4 update today. Typically my rooted devices never updated so this is a new discovery. I pulled the plug on it before it finished downloading but I'm worried I'll loose root if it updates. There's no pre-rooted ROM for 5.2.7.4 yet so I'm afraid to plug the power back in for fear it will update and unroot/brick like the 1st one.
Click to expand...
Click to collapse
For the sloane (aka fireTV second gen box), the prerooted rom installer disables the stock recovery, so nothing should happen if you let the ota updater do its thing...
But its best to disable the ota process with that:
Code:
adb shell
su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
exit
exit