yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] zeroepoch:
Nope. Only 1 of the 3 is still working and it's running 5.0.4 still, but it doesn't really matter since it uses rbox's boot hacks to basically soft reboot into Ubuntu very early in the boot. One is electrically damaged so no hope there. The other if I was ever able to figure out how to turn on the flash from the backup preloader and switch to the boot area of the flash I suppose it could be recovered. Or if I had some sort of hardware flash connection. It just wasn't worth the effort to explore fixing it beyond a few hours of attempts since I only need 1 working device which I already had. Although if I could figure out how to flash a preloader when it's busted you could recover any device with bad or mismatching flash contents. In fact it would always be rootable since the backup preloader can not be changed. Another option might be if you knew the key for the download agent mode you use that to run the correctly signed preloader for your version. So there are definitely options for recovering or rooting still but it's much harder than what I did before. If someone was seriously willing to take an attempt at working with the backup preloader I'd send it to them.
[Fire TV Android Development] ATronixx:
Hi I am using the unbrick.img to unbrick my FireTv2. I had TWRP sucessfully installed and did a advanced wipe and attempted to install the custom ROM. I accidentally hit reboot without OS and now Im stuck on amazon logo. I attempted to run the unbrick_firetv2.bat (Windows 10) and i get stuck on:

Handshake complete!

Flashing unbrick image unbrick+ramdisk.img...

Mediatek Inject, git version fa8d8f

Locating the partition...

Reading 000000200: 0%

I left it on this all night and it never read anything. I read some info on how to fix this on Ubuntu but I can't get it to work on Wndows 10. I have been trying to fix this all night. Any ideas?
[Fire TV Android Development] Mellow129:
Several weeks ago I got the blinking white LED and Blank Screen.

To get here I rooted 5.2.1.1 with Kingroot. Installed TWRP, Flashed 5.0.5.

Guessing I've tripped the verification.

I can still use mediatek_inject

Assuming I could find the 5.2.1.1 stock boot.img, TZ, and LK and write them with the mediatek_inject could I pass the preloader and get back to a factory OS?
[Fire TV Android Development] ATronixx:
Still not reading the Fire TV 2. Ive tried everything. Is there someone who would be willing to help?
[Fire TV Android Development] theistus:
Do you have a link to the ubuntu guide/information you referred to? I'd be interested in this, as I have a box in similar condition.
[Fire TV Android Development] ATronixx:
https://xdaforums.com/fire-tv/orig-development/firetv-2-recovery-installer-t3309785/page4

I'm not sure if this will solve your issue. I've tried unbricking on both Linux and Windows to no avail. I believe I have wiped the partitions maybe and that's why it won't read. Still working on a solution but I'm at a relative dead end until I can find a way to recreate the partition tables. Not even sure if this is possible with mediatek inject. Either way I hope this helps.

Quote:

[MENTION]@pshempel[/MENTION]
[Fire TV Android Development] arashd2:
Unable to unbrick Fire TV 2

Have been running a rooted (with sloane image 5.2.1.0) fire TV for months when it suddenly bricked on me (locked on white amazon logo). Tried your recommended recovery method and it partially works: I can get to teamwin 3.0.0.-5 recovery screen and can successfully install a new sloane image. But after reboot the box is still stock on the white amazon logo. I've tried loading the latest 3 images 5.2.4.0, 5.2.1.1, and 5.2.1.0 but none seem to work. What do you think is the problem?
[Fire TV Android Development] rbox:
factory reset
[Fire TV Android Development] ATronixx:
Use TWRP to wipe Cache/Davlik. Should do the trick.
[Fire TV Android Development] the_chinaman:
I've got exactly the same problem as arashd2. Stuck on the white amazon boot logo. TWRP is still there and can be accessed.

Only rebooted the box as I had to unplug it temporarily. Turned it back on and on reboot it was stuck on the amazon logo. Since then I have wiped it (all types) reflashed, wiped again. Still won't get past the amazon logo. It's been 40 minutes so far after the last flash and still no movement.

Anyone got any suggestions?

---------- Post added at 06:20 PM ---------- Previous post was at 06:08 PM ----------

I don't know if it is relevant, but I can ping the box, but cannot connect with adb.
[Fire TV Android Development] the_chinaman:
(goodnews) UPDATE

My box had been sitting for over an hour so I re-flashed and wiped again - in fact a few times. Still no progress past the white Amazon logo.

The front lights were blinking white, and from reading other posts, it was suggested that orange lights could be to do with the HDMI. As I can see TWRP no problem and the white logo so I left my cables alone. I have a sound bar and the AFTV goes into that and then the soundbar goes to the TV.

As nothing was happening no matter what I did, as a last resort, I took the HDMI out of the soundbar and put it straight in the tv, and as soon as I had switched over the HDMI source on the TV, the setup page was there in all it's glory!

So, I think my Amazon was booting fine all the time but for some reason the HDMI through the soundbar was only showing the logo. I then remembered that a couple of months ago I rebooted and had problems and ended up fiddling with all sorts of things including the cables to get it going again.

I suspect that once booted, it is fine through the soundbar but during bootup, there is a glitch.

Anyway, hopefully this will help others.
[Fire TV Android Development] hotblast:
unbrick FTV1

Have you found an equivalent process for the FTV1?
[Fire TV Android Development] blueduster:
Is there any chance of getting this to work with 5.2.1.1 in the future.. I see as of now this will not install recovery.I have a firetv2 os 5.2.1.1 rooted stuck at the logo.Was installing recovery and it rebooted ,leaving it bricked.
[Fire TV Android Development] Arctic Monkey:
Hi There,

OK I',m here having bricked my device :(

and so may I enquire about whether this method well work on a rooted Fire TV 2 which did have TWRP installed (v 3.0.0-1).

I hope so and look forward to a quick a reply.

Thanks.
[Fire TV Android Development] zeroepoch:
It mainly depends on what version of the preloader you have. If you can connect to the preloader and it's receiving the image then you should be able to get TWRP going again and flash a new full ROM.
[Fire TV Android Development] maxizan:
just won't work :(

hi guys,

kinda going nuts with the ftv2.after i rooted i deleted it again.after a new start i stuck in a loop.it stops with the animated amazon logo.now i try to get it to work again with this method but it stays still at 0% in the cmd saying locatiing the partition ... reading 000000200: 0%

any idea on what's going on? driving me crazy any help would be much appreciated.

thx in advance and greetz
[Fire TV Android Development] zeroepoch:
Could either be a USB cable or a host issue (Linux works better) but it might be a bigger problem which is the preloader does not have the commands it needs anymore. If that's the case you are stuck.
[Fire TV Android Development] 1jimmy007:
I have the white amazon logo too

Any links to the unbricking hardware mm would be great... I have 1 fire tv1 box that's stuck on white amazon logo. Alt+i+print screen no good.
[Fire TV Android Development] Arctic Monkey:
Hi Zeroepoch, thanks for the reply, however I'm not sure what you mean by 'preloader' ?

Is this the TWRP? If so I can confirm that I have version 3.0.0-2 and I can access the main boot menu of TWRP, however if I try to run the Amazon Fire TV2 from the boot menu, I get the continual loop of Amazon 'white logo' and then the boot menu option again.

Please help.
[Fire TV Android Development] roffle:
similar situation for me

i don't know about the other guy, mine was one that I had successfully unlocked the bootloader on

I got an AtoA usb cable and it still shows up in fastboot

I was trying to follow this guide

http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc2

i am able to send the flash recovery recovery.img command and it shows successful but after that in the tutorial it says "Your Fire TV should now boot into ClockworkMod recovery" it doesn't, it still stays on the white amazon logo but still accessible by fastboot

any ideas?
[Fire TV Android Development] zeroepoch:
Do you have an AFTV 1 or AFTV 2? Based on the mention of fastboot, unlocking, and the guide you linked to it's probably an AFTV 1. If that's the case this unbrick image won't work on that device since it's meant for an AFTV 2. You need to get the plain recovery image and flash that. I don't know where the latest version of that is off the top of my head but it's on these XDA forums. Make sure it's the AFTV 1 not 2 recovery.img file.
[Fire TV Android Development] roffle:
mine is an AFTV 1

and yes, I know that the image posted in the first post of this thread is for an AFTV2

BUT since the other guy brought up issues with a 1st gen and rbox responded; I thought I'd get rbox's take on my issue with my ATFV1 since he's one of the main devs
[Fire TV Android Development] Servet83:
Hi [MENTION=3991724]rbox[/MENTION]

Trying to flash boot.img the fourth time after successfully finishing unbrick.img. Flashing boot using mediatek inject commands stucks at around 50% esch time. Am i doing something wrong for now? What method can i try?
[Fire TV Android Development] Servet83:
[MENTION=3991724]rbox[/MENTION]

Trying to flash the boot.img by using above method. Alsways stucks around 50%...any ideas?

Sending 2 Screenshots...
[Fire TV Android Development] Volcom1600:
Were you ever able to get this fixed same issues with not being able to read the partition???
[Fire TV Android Development] First_Degree:
Anyone know if this process could work to unbrick my Fire TV 2?

I unfortunately selected reboot, after accidentally ticking "System" prior to wipe. I've been stuck at the white Amazon logo since...

I was on 5.2.1.0 prior to rooting with Kingroot. I installed TWRP, and had just installed rbox's pre-rooted 5.2.4.0 Rom. Was trying to do factory reset...inadvertently ticked System...went to reboot, and when I realized what had happened, it was too late. Ugh :mad:

Do you think I have any options, or am I S.O.L.?
[Fire TV Android Development] zeroepoch:
It should work. Rbox's unbrick image basically writes a new minimal system image so you can boot back into recovery. After that you just flash the prerooted ROM as normal. As long as your preloader was not upgraded which rbox avoids.

UPDATE: Actually since you were at 5.2.1.0 before you might have just missed the cut off where they disabled the preloader method.
[Fire TV Android Development] scottpaper:
I rarely post, but just had to in order to say thank you for helping me save my Fire TV 2! Like a dummy I tried to flash Magisk in TWRP, thinking if something went wrong I could just enter TWRP and fix it. Well, that didn't work. Fire TV would boot to white Amazon logo and reboot to white Amazon logo in perpetuity with the white LED changing to yellow. I was able to recover by flashing the boot image I extracted from one of the pre-rooted ROMS Rbox uploaded, and then flashing the recovery files in the first post.Can't thank you enough!
[Fire TV Android Development] adam_ky:
Rbox.. I love u man..

I bricked my box here while back... Got a warranty replacement actually... Amazon never sent a truck for the pickup so I emailed them and they said just to keep it.. so I was like well I'll try to fix it again I guess.

So when I first bricked it, I tried your unbrick and it completed but wouldn't boot to recovery so I did it again.. and got some file size Target error..

So anyways this time from the windows pc.. I unzipped all the files again then took ownership of all files in folder..

It worked! It didn't when I did image the first time but that may be due to the ownership.. anyways this time I did the image+ramdisk

.got it working...

You are a ****ing beast!

Now I got my rooted box back up and going.. which is awesome cause the replacement they sent is latest version.

Just wanted to say thanks for your work!
[Fire TV Android Development] Texanpal:
RBox, you are the man and should run for president. Because of you I was able to unbrick my box that was stuck in Fastboot mode (white A logo).
[Fire TV Android Development] netgar:
I get error unmount/cash: not found

I did factory reset in TWRP and stocked on loop, I have no clue how can I restore it...

Any help?
[Fire TV Android Development] TV33:
i couldnt find the information if this will work with "non-rooted" FireTV Gen1 with latest FireOS 5.2.4.2
[Fire TV Android Development] XDA_h3n:
Um.

So yeah I accidentally wiped /system when I tried to flash another firmware to see if I could port over to the Fire TV; it had failed but still wiped my system partition.

I have used the unbrick tool with the preloader drivers on 3 laptops, with all of them failing at the same stage; ubuntu couldn't perform handshake but the other two Windows laptops did perform a handshake but it would just get stuck at 0%.

Which image filename do you want to use? <unbrick.img|unbrick+ramdisk.img> unbrick.img
Waiting for preloader...
Found port = COM4
Handshake complete!
Flashing unbrick image unbrick.img...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 0%

I have left it for about two hours and it won't budge, it would get stuck at reading 0%.

I guess this is hard bricked; gosh, I have recovered many times with this tool but it's not cutting it anymore now :eek:

Might be moving away from the FTV 4k as my main living room streamer now and probably find a newer device. If I do have some spare time, I may figure out how to solder a connection to flash, but it isn't looking great...
[Fire TV Android Development] ryknow27:
Hello everyone,

I like others here made the mistake of rebooting my Fire TV 2 after doing a full wipe. I found this thread and decided to give it a try. It worked for me as I was able to get into TWRP once again however, I forgot to put a pre-rooted rom on the sdcard and thinking it would boot to recovery again, I pulled the sdcard out and placed the rom on it and then put it back in the fire TV and pulled the power so it would recognize the sdcard again but then it would not go back to recovery. I tried the unbrick.img 2 more times and it still would not go back to recovery. I am now in the process of writing the unbrick+ramdisk.img to see if that makes a difference or not. Is there something I am missing?
[Fire TV Android Development] ryknow27:
Just an update...the unbrick+ramdisk.img did the trick and all is well now. Thanks rbox for this!
[Fire TV Android Development] zeroepoch:
That's usually what happens when the preloader has been updated and the protocol changed. The read command stops working because it just waits for something on the serial port and nothing ever gets sent back. It's possible that it could be driver or cable issues, but not likely if you tried 3 different systems.
[Fire TV Android Development] XDA_h3n:
Yeah I was thinking the same thing, the preloader must have been updated at some point by the system which may have blocked this technique, as it has been used to previously install custom recovery.

I doubt it is the cable as it performs the handshake and it's a relatively new cable which has only been used once for the purposes of installing TWRP for the box. I have tried the Windows 7 and 10 Mediatek preloader drivers on all systems and all failed at the same point.

It's safe to assume the protocol has changed but the preloader is still present. I might have made the results worse as TWRP would bootloop and I had access to adb shell, I thought I might create a system partition and that caused TWRP to no longer boot (essentially the /system partition being wiped). Now TWRP doen't boot at all and it just gets stuck on the black and white Amazon splash screen, probably safe to assume its not going to get recovered any time soon.

Flashing a TWRP image into /boot doesn't work either, stuck at the same reading so yeah, Amazon probably blocked this protocol.

I am going to lastly consider opening this thing apart but can only see disassembly guides for the Fire TV 1 and not this model; probably the same though.
[Fire TV Android Development] zeroepoch:
It's a pain to open unless you don't care if it gets some scratches. You basically need a putty knife to separate the lid.
[Fire TV Android Development] starmagoo:
Hey guys. Short question: Which Version do I should flash after I unbrick my FTV2 with this unbrick-image? Bevor I was on 5.2.4.2_r2.
[Fire TV Android Development] starmagoo:
After flashing the unbrick image the TWRP starts but with the error massage "Failed to mount '/cache' (Invalid argument)".

[IMG="Screenshot FireTV2"]http://up.picr.de/31377154km.jpg[/IMG]

Any ideas whats wrong? :(

EDIT:

Wipe Cache again helps!
[Fire TV Android Development] Renegade1504:
Hello rbox,

many thanks for this awesome work.

Had a boot loop after trying to install magisk. After flashing boot.img and unbrick image and rom everything is working normally again.

You made my day.

Greetings

15Reno04
[Fire TV Android Development] droidvoider:
AFTVnews.com or rbox if you find a solution to the updated preloader please let us know. I believe I have here a Fire TV 2nd gen, "Sloane ", with an updated preloader. It is stuck at the initial white Amazon logo with a white flashing light. It won't respond when I try the unbrick method it just says "waiting for preloader". Nor does ALT + i + print screen get me to recovery mode. The person I got it from says they wiped everything in TWRP then rebooted it.

Has anyone tried returning these to Amazon out of warranty? I can have him just try to return it or hang on to it to see if we get past this. I can try to solder to the chip like the old Fire TV stick method too.
[Fire TV Android Development] DhiJay23:
Did you able to get your fixed? Im having the same issue here and what happen was, I tried to update the software and my power interrupted the updating process so when the power went back on and plugged the AFTV2 it only give me the same white amazon logo and went to blank screen with blinking orange light and goes power on and with just the same white amazon go. I tried the method above but this is what I got.

Tried the unbrick.img and unbrick+ramdisk.img but still does the same thing.
[Fire TV Android Development] BRICK0044:
I have one that does exactly what yours is doing.
[Fire TV Android Development] DhiJay23:
Hopefully we can get something to fix it.
[Fire TV Android Development] crs77:
-Dumb ass question removed. Sorry
[Fire TV Android Development] warpcoil:
I have the same exact issue as yours. Did you ever get it fixed ??????
[Fire TV Android Development] laidbackcloud:
I am having the same issue. When I plug aftv2 , after white logo it goes to black screen and then loses HDMI connection. The box just blinks white over and over again. If I remove Ethernet connection, it will also blinks orange.

If I had to guess it's that old update Amazon released awhile back a year or two ago that messed up box.

Anyone have any ideas how to fix this?
[Fire TV Android Development] DhiJay23:
until now im waiting for a fix and looks like where pretty much hitting a very big road block here and our device is done for good.
[Fire TV Android Development] laidbackcloud:
It's not happening. Aftv2 is few years old now. Not much support on it. If you want try to clean HDMI port with circuit cleaner/switch cleaner. You can get them at 5$ at Walmart or 10$ at auto store.
[Fire TV Android Development] tomprc:
I bricked my FireTV 2 with the latest 5.2.6.6 prerooted ROM. Does it mean I am completely out of luck because the unbrick method doesn't work on newer ROM?

My system had 5.2.6.6 and TWRP 3.0.5 installed and working fine.

I pretty sure I didn't do anything wrong. Was playing with the TWRP3.0.5 to wipe data multiple times in order to get the latest play store works. On the last time, I wiped data, system, internal storage and reboot. Boom! Bricked.

My guess is that there is a bug in the TWRP code to corrupt the partitions when I did this. Any last sort solution?
[Fire TV Android Development] BagiMT:
Unbrick should work fine. Used it a few month ago when I wiped system by accident. No issues with unbrick and box is back to normal now running the 5.2.6.6 rom.
[Fire TV Android Development] NiKTaMeR:
Don't panic if the first wipe doesn't work, took me 6 !

2nd most important post (after the OP of course) is this !

And it is in a tiny edit when it should be in bold all caps !

I was just about to give up when the flash of the prerooted image kept spitting mounting errors as shown in the cited post ! Took me 3 Wipe Dalviks and 3 more Wipe (Data, System, Cache, Dalvik, Internal Storage) before everything mounted correctly and I was able to flash the image to completion.

My AFTV had been sitting in a drawer for the last year and half ! Thanks a lot to Rbox and starmagoo.
[Fire TV Android Development] Brianmtl:
Please help

Hey, my non rooted 2nd gen box was doing an update and then said update failed. Now it’s stuck on white amazon logo. What’s the best way to try and fix this?

Thanks
[Fire TV Android Development] sacsfin3st:
So, I am rather new to all this and I have a fire tv box 2 that is stuck in a boot loop. it shows the white amazon logo then goes to TWRP. if I leave it to boot normally, it shows the white amazon logo then goes back to TWRP. I have all the files in this post in one directory on my pc. How exactly do I use this?

I run unbrick_firetv2.bat and type in unbrick.img, plug in USB from pc to fire box, power the fire tv box (it is not connected to tv) from there it sits saying waiting for preloader.

Managed to figure out this issue.. now when I boot up the fire tv box, it goes straight to TWRP. From here can I flash sloane-5.2.6.7-rooted_r2.zip or do I need to perform any other cmds first?

Thanks in advance for any help
[Fire TV Android Development] falk0069:
working with mediatek_inject

Hi,

I'm trying to unbrick a firetv2 that my father bricked. He was trying to unroot it by apply the OTA firmware. I'm not sure what version he was at. I'm running into the issue where it just hangs at this point:

Locating the partition...
Reading 000000200: 0%

So, I've just been playing with directly calling mediatek_inject. I get the handshake.py to work and the com-port opens and stays open. But then when calling mediatek_inject only a few bytes are exchanged and it hangs waiting for a read. Does this seem like an unrecoverable brick? Here are a few lines from the output while using 'strace':

root@ubuntu:/home/ubuntu/Desktop/try2# strace ./mediatek_inject.linux firetv2 /dev/ttyACM0 unbrick.img /system -
...
write(1, "Locating the partition...", 25Locating the partition...) = 25
write(1, "\n", 1
) = 1
write(1, "Reading ", 8Reading ) = 8
write(1, "000000200: 0%", 15000000200: 0%) = 15
select(4, NULL, [3], NULL, NULL) = 1 (out [3])
write(3, "\321", 1) = 1
select(4, [3], NULL, NULL, NULL) = 1 (in [3])
read(3, "\321", 1) = 1
select(4, NULL, [3], NULL, NULL) = 1 (out [3])
write(3, "\21#\0<", 4) = 4
select(4, [3], NULL, NULL, NULL) = 1 (in [3])
read(3, "#", 4) = 1
select(4, [3], NULL, NULL, NULL) = 1 (in [3])
read(3, "\0", 3) = 1
select(4, [3], NULL, NULL, NULL) = 1 (in [3])
read(3, "<", 2) = 1
select(4, [3], NULL, NULL, NULL

I've tried changing the partition to an invalid one and the output is exactly the same. So, it apparently hanging during locating of the partition. It seems hopefully that it is at least responding but looking pretty grim that it is only a few bytes. Any suggestions? Or anyone know where one can find more documentation on the mediatek interface?
[Fire TV Android Development] falk0069:
I'm pretty sure I figured out the issue is due to the 5.2.1.0 update breaking the mediatek interface. It looks like the read/write operations were removed as mentioned here:

http://www.aftvnews.com/software-ve...a-to-a-usb-cable-on-fire-tv-2/#comment-280355