yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] daffung:
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.

when i got it it was stuck to amazon white amazon logo,

so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)

i figured i install this

http://xdaforums.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240

i was able get to recovery!

and applied pre rooted firmware, but after completion,

i think its beyond bricked..

no screen, my led flash drive does not even flash or blink anymore when i put it on boot...

i can still handshake still apply the unbrick method

my question is after applying this brick.img

would i suppose to get a screen? and boot up

but still the same no screen nothing... not even white amazon logo...

or this is done..

thanks
[Fire TV Android Development] rbox:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
[Fire TV Android Development] vrl2:
Many thanks, rbox -- unbrick_firetv2.bat worked for me in bootcamp. Selected unbrick+ramdisk.img, then rebooted into TWRP. Initially when I installed prerooted 5.0.5_r2, setup gave me a screen (after remote pairing and language selection) that it was checking for updates. The setup then halted with an error window that it could not connect to Amazon's server, and that I should power off and reset the AFTV. I then flashed prerooted 5.0.4_r2, completed the initial setup, and reflashed prerooted 5.0.5_r2 (which let me get around the update error).

Again, thanks for all your work!!
[Fire TV Android Development] daffung:
i wonder what caused that bricked.. , ( well it was already bricked, when amazon send it to me it was stuck at white amazon logo, then only when i applied the pre rooted firmware, thats when it stop showing screens from there..wouldn't it fix the problem already since i was able to get to recovery.....

id try the sd card 1 last thing il probably go to walmart and try that, if nothing fix it i guess its total beyond brick..
[Fire TV Android Development] Takeoo111111:
Hi,

thank you very much for your great work [MENTION=3991724]rbox[/MENTION]!

Just a note:

I think, in the bash script, there is a "2" in the last line that doesn't belong there?

And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...

But everything works fine (using ramdisk)!

thx
[Fire TV Android Development] rbox:
Thanks. I fixed it all.
[Fire TV Android Development] daffung:
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
[Fire TV Android Development] rbox:
Well try the unbrick image and see if it works.
[Fire TV Android Development] daffung:
yup,

sucessfully flashed unbrick.img, and had sd card ramdisk-recovery.cpio.lzm.

still the same...

no boot, no screen, not even white screen?

and no signal from hdmi
[Fire TV Android Development] harlekinrains:
I am afraid I have to report a brick on 5.0.5r3 -

Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black and then back to the Video in Kodi twice and then - a dreaded blackscreen.

Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...

(Switched TVs and HDMI cables - just in case (no HDCP problem.. ;) ))

Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.

Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).

And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really... ;)
[Fire TV Android Development] rbox:
The unbrick image just puts enough on system to be able to get to recovery. If you can already get to recovery, it won't get you anything. The disabled stock recovery isn't going to effect anything while running android. All it does it prevent the bootloader from running it. I can't really explain it if you did an advanced wipe of data.
[Fire TV Android Development] harlekinrains:
Hardware Issue probably. Thanks for the fast response. :)

Cheers.

(I'll do another advanced wipe - just for kicks.. ;) )

edit: Went through with another full wipe - rebooting the device afterwards (= softbrick for sure, because not even TWRP is accessible and there is no OS on the device) - which at that point got "parked" on the white amazon logo indefinitely. (Perfect for the "I aint know nothing" returning the device approach. ;) Just in case Amazons 5.0.5 turns out to brick a few more Fire TVs... ;) As long as rbox didnt modify the kernel, I'd say its Amazons fault. :) ) Then went through the unbrick procedure in this thread - which worked as described (TWRP was installed on the device and autobooted on the powercycle after the unbrick script had finished). Then installed 5.0.5r1 again and rebootet - just to be met with the same error profile as before "dark screen" - not even the animated amazon logo (just the white one in the beginning).

This time - on a better TV screen it was visible though, that the screen showed a small horizontal line, and then flashed in a lighter black color twice, before going back to full TV black. So yes the problem seems to lay somewhere on the video signal path. Its curious though, that TWRP still got (and gets) displayed... :)
[Fire TV Android Development] Hoggels:
Works perfect. Thx :D
[Fire TV Android Development] er1000:
Can someone help me? I followed all the steps in the guide and when the unbricking program is writing the filesystem, it always gets stuck at 17%. Maybe I am doing something wrong?
[Fire TV Android Development] jim16127:
I am in a boot loop. Goes to amazon white logo. Light on FireTV2 turns orange then reboots into custom recovery but it automatically starts trying to mount partitions (one of them is cache) and it fails on all of them. Then moves along to the white amazon screen again and repeats the entire process. I ran the unbrick.img and the problem persists.

I'm currently in the process of running unbrick+recovery.img method to see if it makes any difference. Should it? Is there anything that I may be overlooking?

I'm fairly sure that the reason this happened is from checking ALL the check boxes in the format/wipe section of the custom recovery. After that these issues happened. Does that mean permabrick?
[Fire TV Android Development] falk0069:
I've been doing a bunch of research the past week or so and I'm pretty sure the only way to recover it is to do a hardware attack. Basically the mediatek bootloader loop hole is closed and we cannot write to the emmc anymore. I'm planning on doing a hardware read of it but I doubt I'll be successful, but I figure I got a brick anyways. I'm referencing this post on how to do it:

https://xdaforums.com/fire-tv/development/ideal-downgrade-fire-tv-os-via-hardware-t3814911

If you check out the youtube videos, you will see that it isn't for fainthearted. I'm planning on picking up the reader here: shop.exploitee.rs and hoping I can access the emmc directly and rewrite the /system partition that I believe got wiped.
[Fire TV Android Development] ddoouubbllee:
Hi there,

Will it work on a 4K Firestick?

Thanks!
[Fire TV Android Development] Kevlar.Engineer:
HELP, Think I may have Bricked AFTV 2 4K :(

Dear All, This is my first post on XDA, I have an Amazon Fire TV Gen 2 4k Box which was working perfectly with Kodi last week.

I decided to reset to factory setting from within the menu on screen, it rebooted and ran the set up, I went through sign into Amazon and now am stuck on the page that says "welcome to Prime" (see photos). I cannot go past this screen or even to the home screen of AFTV.

[IMG="Stuck on this screen"]https://images.hotukdeals.com/comments/full_screen/TsuGE/37123642.jpg[/IMG]

I contacted Amazon tech support who had no solution... :(

However, they did tell me that the software version is "5.2.1.1" and they cannot see the box online.... but could ping it to get diagnostic data....

I tried soft reset (removing and replacing power cable) & hard reset (hold right key and back key)

My Noob question is how am I able to wipe everything and install an upto date rom?

Is the box bricked??

Any help or walkthroughs will be greatly appreciated.

Thank you in advance :)

[MENTION=5957312]AFTVnews.com[/MENTION]

[MENTION=3991724]rbox[/MENTION]

[MENTION=4245516]daffung[/MENTION]

[MENTION=6833079]jim16127[/MENTION]

[MENTION=3411776]zeroepoch[/MENTION]

[MENTION=7978019]inthesouth[/MENTION]

[MENTION=1239919]clarke.hackworth[/MENTION]

[MENTION=4266035]XDA_h3n[/MENTION]
[Fire TV Android Development] Kevlar.Engineer:
UPDATE ≥>>≥>>>≥>>>>>>

Good and bad news, left it for 1 day plugged in and I believe that Amazon Tech pushed an update to it.....

So the good is it's working now with the most recent update.... The bad is I can;t root it as this update does not allow it :(

Thanks to all that contributed ideas during my time of panic. (y)
[Fire TV Android Development] bilitte22:
We re all in the same boat.Here is my output.

kubuntu@kubuntu:~/Desktop/New Folder$ sudo '/home/kubuntu/Desktop/New Folder/unbrick_firetv2.sh'

/home/kubuntu/Desktop/New Folder/unbrick_firetv2.sh: line 3: cd: too many arguments

Which image filename do you want to use? <unbrick.img|unbrick+ramdisk.img>

unbrick+ramdisk.img

Waiting for preloader...

Found port = /dev/ttyACM0

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, in open

self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)

OSError: [Errno 19] No such device: '/dev/ttyACM0'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "./handshake.py", line 89, in <module>

dev = serial.Serial(port, BAUD)

File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__

self.open()

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open

raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))

serial.serialutil.SerialException: [Errno 19] could not open port /dev/ttyACM0: [Errno 19] No such device: '/dev/ttyACM0'

Flashing unbrick image unbrick+ramdisk.img...

cat: comport.txt: No such file or directory

Mediatek Inject, git version fa8d8f

error: ./mediatek_inject.linux <device> <comport> <source file> <target file> <selinux context>
[Fire TV Android Development] PhoenixMark:
Well I've got a pulsing white light dead device. It responds to the unbrick completing at 100% but changes nothing in its status. So it's available as a testing device at this point...
[Fire TV Android Development] ForForkSake:
Do you think we need a new recovery... It must be something specific to those who have bricked.. Having installed V7... My twrp froze at 0% for hours after trying to install pre rooted rom. Couldn't adb or anything...

Now I've tried every combination of unbrick with v6 recovery just incase, various drivers, two different cables, windows 10, two different Linux distros... And it either freezes at flashing 00000200% or the same error as above.

[MENTION=3991724]rbox[/MENTION] help please :silly:
[Fire TV Android Development] Semitope:
In the same boat as those with the 0% on reading and I have the recover 3e page when booting with no options. Hope someone knowledgeable looks into this.

Mine was a second hand fire tv 2nd gen that was ditched after bricking and amazon refused to help. Rather than buy another amazon fire tv they went with apple because they thought the fire tv would brick itself again later. I object to both but from what I have been reading, avoid amazon is a good idea. Trying to see if I can salvage it.
[Fire TV Android Development] urbanman2004:
Unfortunately, you're in the same boat as me and everybody else as recounted here and here and here and here
[Fire TV Android Development] rbox:
If the unbrick isn't working, its most likely because the bootloader has been updated to the version that disabled it.
[Fire TV Android Development] Semitope:
no chance anyone finds a way around the new bootloader?
[Fire TV Android Development] ForForkSake:
Ahh I see

So it's a brick? Damn it.
[Fire TV Android Development] Lochy19:
So, what else we can do? is there another way to unbrick it? thank you so much for your help!
[Fire TV Android Development] ForForkSake:
That's what I'm wondering. Is there anything we do?evrb if it involves taking it apart / solder etc
[Fire TV Android Development] ForForkSake:
[MENTION=3991724]rbox[/MENTION] mine became a brick after I rooted stock 5.2.6.9 with the new mk su and your v6 twrp

Booted into Twrp and it froze on 0% whilst installing pre rooted 5.2.6.8

I left it over night but still frozen

Unable to access it via adb, so my only option was power off... And that's when the amazon white logo bootloop began

Any suggestions or is it well and truly bricked?

Thanks for your assistance, do you have a PayPal for donations?
[Fire TV Android Development] rbox:
Well if it started erasing the system partition, then theres no twrp to boot back in to, so there's no way to flash it back. I haven't heard of anyone else having it freeze at 0%, but if you coudn't adb, then it sounds like it just crashed. There is a donate to me link on the left side of my posts.
[Fire TV Android Development] ForForkSake:
I was being an idiot and didn't have the ethernet plugged in, was using wifi for some reason on the fire tv.... so it potentially was able to adb.... i was installing from an sd card, that's where is froze, could have been an sd card issue...

but yea now it just doesn't boot at all past the amazon logo,

the device is detected as mediatek preloader for a second....

but any flashing gets stuck on

Reading 000000200: 0%

only cost me £40, so not the end of the world I suppose.

Ok, i'll be sure to donate at the end of the month, reminder set. thanks for your support.
[Fire TV Android Development] slyevo:
I have exactly the same issue, apart from I formatted the system with the intentions of installing the custom rom but low and behold, we had a power cut (something tripped the mains) now I too have a brick.
[Fire TV Android Development] ForForkSake:
I'm trying to get amazon to replace but they need the DSN.

Unfortunately I fit off ebay unboxed.

Anyone know how to find the DSN on a brick?
[Fire TV Android Development] slyevo:
If I had twrp installed but wiped the system partition, have I lost the ability to boot into twrp all together or would it work with the keyboard trick (if I bought a keyboard)
[Fire TV Android Development] ForForkSake:
Delete
[Fire TV Android Development] Lochy19:
Anybody has any update about this? It's really sad :(
[Fire TV Android Development] Sus_i:
If you did an amazon login with this fireTV before, you can find the serial at the amazon website, take a look at your Account -> Digital Services and Device Support -> Manage Devices.

Since this box is most likely vulnerable to the amonet mtk exploid, a hardware unbrick/root solution should be possible, if someone with knowledge and time ports the 2gen FireTVStick root/unbrick solution... and a pad for the CLK line must be found too, don't know wether this pad is known. Maybe someone with a bricked box and a desolderd emmc can trace the clk emmc pad to a reachable pad, point or resistor at the board. With known pins for CLK, CMD, DAT0 etc, an emmc reader should work for unbricking too.

OK, maybe it's to much work (and offtopic, sorry), don't know :D
[Fire TV Android Development] ForForkSake:
Haha, well I'll be happy to send mine to someone.

I have a solder iron but no emnc or clue as to most of what you just mentioned lol
[Fire TV Android Development] diodanny:
i have the same problem
[Fire TV Android Development] tech3475:
Thanks for the image, I've sent a few bucks your way for saving me from my stupidity.

The only thing I might suggest is maybe adding to the first post maybe mentioning that those who originally used the USB A-A method and only used your images still have the old preboot and maybe include a script to reflash the boot partition (which was the issue in my case).

I know this is mentioned elsewhere in the forum (although I guessed it), but I could imagine someone missing this information.
[Fire TV Android Development] ForForkSake:
So I have a feeling I was initially stock 5.6.8 or 5.6.9

Used mtksu and in recovery flashed the pre rooted rom but upon flashing the system.img it crashed....

But because I now have the new preloader... It hangs when trying to flash anything at 0.00200000%

Can I not flash the boot.img which would have been on my fire tv 2?
[Fire TV Android Development] tech3475:
I'm no expert, but probably not.

AFAIK the newer preloader blocks NAND access, at least for what 'we' want, so you wouldn't be able to write a new boot partition/downgrade the preloader.
[Fire TV Android Development] ForForkSake:
Amazon get kicks out of bricks, bunch of pricks. Why ??

I
[Fire TV Android Development] tech3475:
Considering that they hate rooting to begin with, it's not too surprising.

What I don't get is why more companies don't include recovery modes since even OFW updates can cause bricks, similar to the iPhone or the 3DS/Switch.
[Fire TV Android Development] ForForkSake:
They are probably happy to just replace. No way will these be under warranty now.. I'll still see what they can do for me

---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------

Yes got it from here. Cheers... Not sure what they will actually do for me... I'll see tomorrow
[Fire TV Android Development] bodomalo:
This thread is extrem longe to read, 22 pages

IS the solution from page 1 from 2016 still working?

Can someone unbrick a Fire TV box 2nd generation (its in a boot loope) - system is not changed, it just crashed and has a hdmi problem now (does not show anything, only the white amazon logo)
[Fire TV Android Development] mtidmarsh:
To help save my sanity, I wondered if someone may be able to confirm something for me and perhaps either stop me from wasting my time or point me in the right direction?

My (Sloane) rooted Fire TV 2 is no longer booting, it just freezes on the white Amazon logo and is unresponsive.

I have attempted numerous times to follow the steps in this post, but to no avail, despite trying on three different pc's.

When I run the 'unbrick_firetv2.bat' file, it just stops at "Waiting for preloader..."

I don't know whether this is because the FireTV doesn't have USB Debugging enabled (even though it hasn't booted that far) or if perhaps because the drivers are incorrect, or if it's just because it's totally goosed.

I am running Windows 10 and have installed the MT6577 drivers.

When I connect the Fire to the PC, it recognises is as MTP USB Device under 'Portable Devices' rather than either FireTV, or ADB device. Can someone tell me whether this is in fact the problem? (in MTP mode and not ADB) or should that work fine and it is another problem?

If I start the ADB server and look for devices, it doesn't find any.

I have tried to removing the MT6577 drivers and installing the Universal ADB driver but when I connect the Fire TV, it still shows up at MTP USB Device.

I'm going round in circles and not sure whether it's just driver related, or whether it really is the device and I just need to give in and get over it!

Thanks,

Matt
[Fire TV Android Development] tech3475:
The Preloader is completely different to ADB and runs before Android, so it wont matter.

To be clear you're running the bat file, plugged in the Fire TV via USB and only then turning on the Fire TV?

Also, bear in mind this will only work if you have an older versions of the preloader, in my case I originally hacked via the preloader method and only ever used rbox's ROMs.
[Fire TV Android Development] mtidmarsh:
Thanks for the quick response.

So the fact that I cannot connect via ADB is completely unrelated then as it wouldn't have got this far in the boot cycle...

Yes that's exactly the order I'm doing unfortunately.

Do you know whether there is anything else I can try, or an alternative method? (is there a working method for a later preloader in case this is the issue?)

Thanks,

Matt
[Fire TV Android Development] tech3475:
Reading earlier posts from when mine was semi-bricked, the error a newer preloader produces is that it wont write to NAND.

IIRC, if you successfully enter preloader mode you shouldn't see the Amazon logo.

Do you hear the 'connect' sound on your computer when you plug device into your computer and turn it on? Has the A-A cable worked with other devices?

AFAIK, the only other method is a hardmod which I think someone else posted on this site.
[Fire TV Android Development] mtidmarsh:
Yes I do hear the 'connect' sound from the computer when I turn on the Fire TV.

I think this the cable that I have successfully used previously (it's USB3 - that won't make any difference will it?)

I have just tried it on a laptop (same cable) and I have got slightly further (but not much!), I now get to this point:

Waiting for preloader...

Found port = COM4

Handshake complete!

Flashing unbrick image unbrick.img...

Mediatek Inject, git version fa8d8f

Locating the partition...

Reading 000000200: 0%

But it sits at 0% and doesn't progress. I have the lzma and recovery images on FAT32 formatted SDCard in the FireTV.

Not sure if the above proves anything more or gives anything else to try?

Thanks again for your help...

Matt
[Fire TV Android Development] tech3475:
Try the slower method, but if that doesn't work then AFAIK it likely means you have the newer preloader which blocks this.

Unfortunately there's no other method I'm aware of besides a hardmod as of now.
[Fire TV Android Development] mtidmarsh:
Sorry, can you explain what the slower method is, or point me to a post?
[Fire TV Android Development] tech3475:
It’s where you use “unbrick+ramdisk.img”.
[Fire TV Android Development] mtidmarsh:
Ah got you (sorry was being thick) - yes have tried that too, still sticks at 0%.

Could it be anything to do with the sdcard? (tbh, i've tried 2 different cards, both fat32 and the required files are in the root of each).

From the sound of things, I now have a square black drinks coaster don't I?!
[Fire TV Android Development] tech3475:
Unfortunately, hardmod aside, for now it does.
[Fire TV Android Development] mtidmarsh:
Understood. Thanks for your time tho.
[Fire TV Android Development] ForForkSake:
Anyone have the old preloader.img file? Some good news on the horizon if it works just need the old preloader...
[Fire TV Android Development] rbox:
I have mostly every version of stock firmware. Please let me know what version of stock firmware contains the "old preloader" you need.
[Fire TV Android Development] ForForkSake:
Thanks [MENTION=3991724]rbox[/MENTION].

I can't install the unbrick image because my preloader doesn't allow it

.. I think I had 5.2.6.7 before I bricked it... But with the help of a few members in the firestick 4k root thread. We successfully found a short... Basically any preloader that will allow me to subsequently use your unbrick image

.. Please ?
[Fire TV Android Development] rbox:
This is the preloader from 5.0.5.

http://www.mediafire.com/file/4jfpzq26t4ul794/sloane-5.0.5-preloader.img/file
[Fire TV Android Development] ForForkSake:
Hehehe thank you
[Fire TV Android Development] ForForkSake:
https://xdaforums.com/fire-tv/devel...i-rollback-t3986303/post80588511#post80588511

People. The day is here. Unbricking of ATV2 :svetius: :laugh: