Develop Bugs

Anyone know how to fix a bricked FTV

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.

[Q] Stuck on the white Fire TV logo

My locked bootloader box is stuck on the white logo. The power went out during updating. I can't get it into recovery mode using any of the available methods mentioned in aftvnews (using the remote, Alt-i-PrntScrn, etc).
Can I solder wires to it and copy stock firmware bueller-ota-51.1.5.0_user_515030720-signed.bin to the EMMc, and somehow tell the box to restart the update from the beginning?

Since no one answered, I guess it's a "no" or "I don't know"?
nguoidien said:
My locked bootloader box is stuck on the white logo. The power went out during updating. I can't get it into recovery mode using any of the available methods mentioned in aftvnews (using the remote, Alt-i-PrntScrn, etc).
Can I solder wires to it and copy stock firmware bueller-ota-51.1.5.0_user_515030720-signed.bin to the EMMc, and somehow tell the box to restart the update from the beginning?
Click to expand...
Click to collapse

Before soldering I would try if the box does have a regular network recovery via LAN connection. So attach a LAN cable and wait if Amazon´s own recovery does fetch again the update.
Of course you must have the update URLs from Amazon enabled and not blocked for this.

nguoidien said:
My locked bootloader box is stuck on the white logo. The power went out during updating. I can't get it into recovery mode using any of the available methods mentioned in aftvnews (using the remote, Alt-i-PrntScrn, etc).
Can I solder wires to it and copy stock firmware bueller-ota-51.1.5.0_user_515030720-signed.bin to the EMMc, and somehow tell the box to restart the update from the beginning?
Click to expand...
Click to collapse
power went out really!? that's an unfortunate timing. Sorry to hear. I bet most of us never think about that when running through the updates.
Have you tried ALT+I+PrintScreen and then home or end and then enter. Play around carefully and try to get it to do the recovery to factory. At least you may try to save your root.

I just tried that many times and I couldn't get into the recovery screen.
navigates said:
power went out really!? that's an unfortunate timing. Sorry to hear. I bet most of us never think about that when running through the updates.
Have you tried ALT+I+PrintScreen and then home or end and then enter. Play around carefully and try to get it to do the recovery to factory. At least you may try to save your root.
Click to expand...
Click to collapse

Can you not return the box to Amazon? If it has not been opened they may replace or repair it if its still in guarantee time.

Fire Phone is doing nothing after flashing CM11 severall times.

Hi,
I put CM 11 on my fire phone. After I dialed a phone number and pushed send, the screen instantly went black. That was enoying so I tried to install the recent CM 11 from 02/16/2016. (Now I know that the display protection might have caused the issue) After the installation I booted the phone. After I had to choose the language in cyanogenmod in the phone was written that the installer was stopped. So I was in a loop of beeing asked for the language.
So I put OS (via adb sideolad) on the fire phone again and installed CM11 and the recent open gapps. Everytime the installer stopped and I was in that loop again.
I tried it with different Open gapps and CM11.
Now suddenly the Fire Phone does not do anything anymore. Just a black screen. I tried several button combinations with several time combinations. Even not the amazon sign appears.
I have two fire phones and am more or less scilled in flashing and installing. But now I do not know how to tread the issue.
I think about opening the Fire Phone and disconnect the battery for some seconds. That move might do something....
Any recommendations? Any ideas? Anybody had similar issues?
Thank you! Have a nice one!
Ingo

Some ideas...
Hi ingo,
welcome to the forums :cyclops:
first of all the following are just some ideas i've got of helping you in your case.
Maybe you already done some of them but anyway
Idea 1. Hold down Power button for about 10 secs or more (to try to reboot to see if the amazon logo appears)
Idea 2. Hold down Power button and Volume down together for about 10 secs or more (maybe we can get out of the boot loop).
Idea 3. Hold down Power button and Volume UP together for about 10 secs or more (maybe we can get out of the boot loop).
Idea 4. Don't charge the phone for about 3 Days and see if it shows something when you then connect the charger (then try to repeat Idea1 to Idea3).
After one of this succeed:
Your issue with CM not going over language selection is already known.
Try to remove SIM and use WLAN to go over the setup....
Or install the one from january (no issue) and then dirty update to the current one
If you killed your SafeStrap recovery you will have to go back to stock, root, safestrap and start over...
That's for now from me.
Report if something changed
regards

Will open the Fire Phone
Hi. Thank you for your answear! I appreciate that!
I checked your ideas already. The first ideas did not work out. I will open the Phone to disconnect the battery for a while. I will see what that may bring.
I will tell about the outcome of that.
Have a nice one.
Best Regards, Ingo

Dont forget: if you still (ok i doubt ) have warranty on the phone that the battery pack is secured inside with a "magic tape" that will break when you remove it...
Good luck

Will find sollution
Thank you for your reply. Warranty. Ahaha.:laugh: Would be funny to try it though.
I ordered the right tools for opebing the Fire Phone (There are two small torx screws).
I saw in the list of devices that there are 6 extra disks shown when I connect the phone to the pc. The PC just can see the content of one of them. I cannot open the files, the PC is not able to open the filetypes (for example adsp.b10)
I will keep on trying!
See you!

I got my new tools. Disconnecting the battery did not make it better. Same situation like before. So right now I do net know the next step.
Of course I tried to charge the phone, I tried different button combinations ......
Its a pitty. I have got two fire phones and it is the one with the 64gb.
I will keep on.. If anybody has a hint please tell me.
Thank you!
Regards Ingo

Anybody got an idea?

ingokabel said:
Anybody got an idea?
Click to expand...
Click to collapse
Hi,
after a while I start to try to fix my fire phone again. I still do not have any clew how to solve the issue.
Any of you?

(Solved) AFTV V1 another brick?

Hi all. I'm giving this one last chance before I toss it because one of my fire sticks seems to be giving up the ghost and the box was/is a superior device to use if I can get it freed up and working again.
I've had this on the shelf for some time. Here is where I sit
Fully Unlocked
Rbox boot installed
I can't for the life of me remember what version of OS/Rom/Recovery was on it?
I believe I have CWM 6.0.5.1.4a.
I believe the rom was a 51.1.6. x x x x?
I honestly don't remember if I had updated the boot menu and rom out of order or what but here is what I'm looking at now.
I power it on and once I get to Rbox boot selection I either
1. choose boot kernal where I get a white amazon logo which does fade away and get replaced by the colorful amazon logo. The LED pulses white
2. choose launch recovery where I get the white amazon logo and the LED glows orange/yellow
I have a USB A-A bridge cable which does nothing for me. I'm never able to list my fastboot device from within ADB. Maybe my USB cable is crap? It does have the installed electronics and software for moving files to and fro.
It has been a good 18 months since I tried breaking it open last and I think I'll ask if anyone has advice before I chuck it.
I should mention I have since married the remote to my other AFTV box. F.W.I.W.
Regards
Gonk

I'm getting somewhere. I've tried some A-A cables and this new one is getting me somewhere.
Following this link at FTVnews I am finally looking at CWM.
But my problem now is how to control CWM without my remote! Install putty via these directions. This allowed me to do data wiping/factory reset and wipe the cache partition.
Next is Resetting with Recovery Model per Rbox guide of the first link.
So now I have a baby OS and trying to get past the mandatory network setup so i can sideload and move on.
This is super great news I brought it back from extinction. I'll update this post with more specifics as I get through it, though all the information IS already available. It's still nice for folks to see it's possible to bring a box back after all hope appeared to be lost.

FireTV box 2nd gen in endless boot - Amazon logo then "no signal"

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