yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] KTac:
I was delighted after a long frustrating night of battling with what looked like a bricked Fire TV, to wake up and find this very helpful reply. Thank you, thank you thank you, bula1ca! Those drivers were the missing piece of the puzzle. I followed a newer root guide from the one you linked which doesn't require the USB A to A cable so I never saw anything about needing special drivers up until now. I ran the script again after installing the drivers and when I powered up the Fire TV, lo and behold, the script started chugging right along. I jumped in the shower and when I got out the image was finished being pushed to the Fire TV. With my last few minutes before I had to run out to work I rebooted and was delighted to see the TWRP splash screen. I re-flashed the 5.0.5.1 pre-rooted ROM, rebooted and was delighted to see the colorful Amazon logo followed by the beginning of the setup wizard. I'm very glad to be able to pick things up again after work and not have to worry about trying to return/exchange this thing. Big thanks to rbox as well for putting all this together.
[Fire TV Android Development] bula1ca:
Glad I could help. Many here help me as well so many times.
[Fire TV Android Development] stereotypeuk:
Hey, first post here because the advice has been so spot on up until this point that i've not found anything i needed to post about.

Firstly, many thanks for the effort involved in bringing us this and other tools :)

So, the problem i'm having is that i'm able to run unbrick.img, and get into the recovery, however when I installed the rooted image i've used for my other fire tv (this one that i'm having issues with was running stock os) i'm still being returned to the white logo where the device just hangs. I tried running the unbrick again in order to clear all the caches and wipe data before reinstalling the rooted os again, but still no dice.

Any suggestions gratefully received...

Chers :)
[Fire TV Android Development] zeroepoch:
It takes a while to clear the cache (which is a good idea). How long did you wait or did you reboot though twrp when it finished?
[Fire TV Android Development] stereotypeuk:
I did wait for the cache to clear fully in twrp. I also did an advanced wipe and basically cleared everything besides the mounted sd card. After that, I've rebooted through twrp.

As far as I can tell there's nothing else i can delete or clear before restoring the rooted image, and it's still hanging at the white logo boot screen whenever i attempt to boot into the system as opposed to recovery.

I have no idea what has caused the brick in the first place either. It's a vanilla box which has been running fine since February and then literally between turning it off and on yesterday this has happened. I'm thinking it's possibly beyond borked...
[Fire TV Android Development] zeroepoch:
That is quite unexpected to just randomly happen between boots. It's not necessary to wipe system if you did that. It could be risky. I assume you flashed the preroot after all the wiping and before rebooting? That's the only possible issue I can see. If you wiped system of course there would be nothing to boot. Not sure what else to suggest. Could just be bad hardware. Maybe also check the checksum on the files again?
[Fire TV Android Development] Fruchttiger00x0:
Sounds very similar to my problem, doesn't it?

http://xdaforums.com/fire-tv/help/fire-tv-2-stuck-b-boot-logo-flashing-t3396296

Is it neccessary to disable the ramdisk after flashing the prerooted rom? Sorry for that dumb question but I have no idea who to fix that
[Fire TV Android Development] Fruchttiger00x0:
!! Problem solved

It was the god damn HDMI cable -.-

Behind the boot logo it was waiting for paiing the remote

Maybe it could help some of you guys too

Kind regards
[Fire TV Android Development] roligov:
Some how ruined the /cache partition while trying to erase it. Device stuck in a boot loop. Flashing new rooted firmware didn't help. Flashing unbrick.img now then will report back if it was a success or failure.
[Fire TV Android Development] Fruchttiger00x0:
Yes, happened to me more then once. But only because I was not patiently while wiping via twrp GUI ^^

Anyway, Cache is not that big thing. I guess you see some errors like invalid args while mount the partition?

Here is an option:

In twrp -> advanced -> terminal

Make sure you are root

id

umount /cache

mkfs.ext4 /dev/block/mmcblk0p14

exit

reboot
[Fire TV Android Development] roligov:
Yeah thanks that fixed my cache issue :)
[Fire TV Android Development] Darkestred:
**edit woo hoo its at %40. Back to bed only to...

I tried installing xposed on a firetv 2. I believe i took the wrong xposed file and went to install it. Rebooted after install. Got the amazon logo. Then it flashes and hangs. Then reboots. I decided to run the uninstaller. Uninstalled. Decided to take the suggestion to wipe davlik. Thought otherwise, but did it. Formatting...for 10, 15 minutes. Nothing. Rebooted. didn't really boot, but can get into recovery. Decide to try the unbrick method. Gets to write 38% and stops.

I am doing this for an employee of mine. Will do research later tomorrow as im tired and have to be up in 3 hours. If anyone had this happen would love to read the cliffs.

I have it running again. Going to bed. It's at 7%. Can't wait to wake up to it stuck at 38%.

I'm thinking i can maybe use one of those pre rooted roms.
[Fire TV Android Development] fireman928:
still no way to get it to handshake on rbox newest rooted version and to run the unbrick? I am on rbox newest rooted version and i was in the process of installing google play when the fire just shut down and now just boots to the white amazon logo light on the box is white and just dims and goes bright like its sleeping. any ideas
[Fire TV Android Development] zeroepoch:
What do you mean by no way to handshake? Does it just not handshake or is something else going on after it handshakes? If it some how updated itself to the latest version, which shouldn't happen with the rbox rooted image (but nothing is 100%), then you're out of luck.
[Fire TV Android Development] fireman928:
I installed the updated rbox rooted ROM. I'm sure I'm out of luck. I bought another one with a geek squad warranty and rooted the new one and gonna leave on the older ROM.
[Fire TV Android Development] woundedfish:
Could unbrick image be used to root??

Hi everyone. Super super long time lurker here, I have rooted and flashed many devices with all of your help! I learned long ago as you all advise to just read everything before posting. This always lead to me not needing to post because you guys always had the answers. Up until now that has been the case. I sit here with my brand new AFT 2, chomping at the bit to root it, to be stuck not able to do a blasted thing because it OTA update to 5.2.1.0 when i let it sit. My reason for posting in this thread is to ask if this unbrick method could be used basically wipe the entire box and reload everything to an earlier OS version and root (or flash a prerooted ROM)? Thanks in advance for any all answers and help!
[Fire TV Android Development] zeroepoch:
It's not a bad idea and I thought about that as a solution for a new device. Assuming it's old enough that the preloader still is vulnerable you could overwrite /system with the unbrick image, boot to TWRP, and then install the latest release from [MENTION=3991724]rbox[/MENTION] (not older than current installed version due to anti-rollback). Although if it's new you should still be able to use the root installer that patches /system to enable TWRP. It's sort of the same result, but it would be less to write and be quicker. I'd just recommend to keep it off your wired network and not join any wireless networks until you're past installing the latest release from [MENTION=3991724]rbox[/MENTION]. Precautions are built into the rooted image that break OTA updates to keep it from doing that.
[Fire TV Android Development] woundedfish:
Thanks for the reply *zeroepoch, I appreciate the help. But rbox's root thread says it'll only work if I'm prior to 5.2.1.0. My box updated to 5.2.1.0. You're saying there's hope!? Is the root installer your talking about not the rbox one?
[Fire TV Android Development] zeroepoch:
Sorry... I didn't realize you are already on 5.2.1.0. Right now there is nothing you can do to root until a new kernel exploit is found.
[Fire TV Android Development] woundedfish:
Its cool. I just appreciate what you're doing here for everyone, myself included. I'll just try and patiently wait for the next exploit to be found.
[Fire TV Android Development] red_indian:
Thanks for sharing this method! I thought I fried my box there for a moment. Was able to unbrick it using this method. Used the unbrick.img with ramdisk.img on microSD. Was able to boot into the TWRP and flashed the pre-rooted 5.2.1.1 image. Then did a full cache wipe and rebooted... and she's back!

For those on Windows where the progress indicator randomly stops at different percentages. I had this at first also. Then I tried another USB port and a USB-hub and it worked flawlessly!
[Fire TV Android Development] davekaz:
Will this work for a bricked aftv 1 that has not power light and shows up in windows as an f drive?
[Fire TV Android Development] zeroepoch:
No only works on the aftv2.
[Fire TV Android Development] scottyw:
Is there an equivalent process for the FireTV 1?

I have an aftv1 on stock which only boots past the colour logo then gets stuck on 'optimizing.....'

The keyboard trick doesn't work as the keyboard doesn't appear to be getting power from the usb, no led light.

Help!!
[Fire TV Android Development] overflyer:
Guys I messed up really bad. I wiped my Fire TV 2 and then accidently rebooted. Now im stuck forever at the first silvergrey amazon logo. Is the method provided here able to fix this?
[Fire TV Android Development] quangon:
cache.img

Hi, I'm having similar problems to jim16127 so tried to get the cache.img file but the download link is dead. Please could it be reupped? Thanks.
[Fire TV Android Development] rbox:
What errors are you seeing?
[Fire TV Android Development] quangon:
Not so much that I'm seeing errors, I go thru Unbrick and get into TWRP, I then install latest Sloane (it says successfully), reboot and just get white Amazon logo again. I can then only Unbrick again so back in TWRP I do Advance Wipe on Cache and Data and try again but still white logo. Next I've wiped all but sdcard & USB, still with same result. I've also tried 5 different versions of Sloane but with no difference. I'm hoping the cache.img may fix it enough so that I don't have to repeat unbrick and allows the rooted firmware to complete?

Any ideas would be appreciated.
[Fire TV Android Development] rbox:
The cache.img is only for that particular error. As for what you're seeing... should be working, especially if you advanced wipe on data.
[Fire TV Android Development] moukazwina:
I have just finished the entire guide on how to root my Fire TV 2. However now it is completely bricked. I have already tried the recovery method with USB A-to-A cable and all I am getting is the message "waiting for preloader".

I am completely puzzled as to what has happened.

I was on version 5.2.0 or 5.2.1 I am not sure which one it was.

All the Fire TV is doing now is having the white light blinking at a fairly slow rate.

Can someone please help? I am not ready to throw away my Fire TV device. It would be a real pity to do it.
[Fire TV Android Development] fireman928:
I am no expert on this but I don't think the unbrick method works for those versions. I don't really remember but I to had bricked mine before when I was on those versions and I did some research and read a lot on this thread and if I remember I read it only worked on the 5.0.2 or lower or something like that. Again I know I can not help much and this was not much help, but just sharing one of my previous experiences. I had a geek squad warranty on mine so I just returned it and got one that had 5.0.2 on it
[Fire TV Android Development] moukazwina:
Indeed this is not helping at all. Unfortunately I used a YouTube video where there were no warnings whatsoever about the version the Fire TV needs to be on. I now have wasted $95 on a Fire TV that was working fine just to root it. What a waste of money and time. On top of it all is the aggravation that there were NO warnings on the YouTube guide.
[Fire TV Android Development] quangon:
If it has only got to "Waiting for preloader" I wouldn't have thought it had done anything at all, basically just means it hasn't started the process. Have you tried the ALT, PrtScn + i combination on an attached USB keyboard?. That should get you into recovery mode and if you're lucky get back normal operation.

---------- Post added at 05:19 PM ---------- Previous post was at 05:05 PM ----------

Quote:

Originally Posted by quangon

Not so much that I'm seeing errors, I go thru Unbrick and get into TWRP, I then install latest Sloane (it says successfully), reboot and just get white Amazon logo again. I can then only Unbrick again so back in TWRP I do Advance Wipe on Cache and Data and try again but still white logo. Next I've wiped all but sdcard & USB, still with same result. I've also tried 5 different versions of Sloane but with no difference. I'm hoping the cache.img may fix it enough so that I don't have to repeat unbrick and allows the rooted firmware to complete?

Any ideas would be appreciated.

The cache.img is only for that particular error. As for what you're seeing... should be working, especially if you advanced wipe on data.

Yes I definitely did advanced wipe on data. One thing I do notice is that when the FTV2 is on the white Amazon logo the lights flash on the front of the box, usually white but I get 4 orange flashes at regular intervals. I Googled and it was suggested that it's to do with either the HDMI cable (so I've now tried 3 different ones with no effect) or that the box is trying to update so I've connected to Ethernet and this stops the orange flashes but continues to flash white.

Only other update I have is that I can get back to TWRP by pressing ALT, PrtScn + i combination. Also I left the box on and attached to Ethernet overnight to see if it would update but no luck.

Any other ideas anyone has would be appreciated, I'm very stuck cos everything seems to go through the procedure perfectly apart from getting past the white logo.
[Fire TV Android Development] paulsavo:
Is there any recovery images like this for ftv 1as im bricked
[Fire TV Android Development] jumoji:
I originally have a set that got stucked at white amazon logo. Used the unbrick.img and could get into twrp. Flashed pre rooted 5.2.4.0 but still get stuck at white amazon logo. So, i tried to flash pre rooted 5.0.5.1. Now, its seems that it cannot even boot (no hdmi signal, slow flashing white light on the ftv) and cannot get into twrp. Used the unbrick.img again but still cannot boot or go into twrp. You think i could flash the whole stock image using the preloader method to get it working? Any link to full images?
[Fire TV Android Development] clarke.hackworth:
My firetv2 has the same symptoms (no hdmi signal, slow flashing white light). I was on a pre-rooted build (5.2.1.1 then 5.2.4.0). I then tried to install 5.0.5, which is when everything got screwed up. Now no hdmi signal and I can't get to TWRP. I am working with the unbrick image, and recovery images. So far no luck in any combination. I will report back if I get it working, please also do the same.
[Fire TV Android Development] jumoji:
From this thread on unbricking Fire HD: http://xdaforums.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797. It seems that the black screen is caused by wrong bootloader. Can anyone provide TEE1, boot and twrp images? I am not sure what version is suitable though.
[Fire TV Android Development] jcsnider:
Same boat as those above me. Fire TV2. ROM download was corrupted or something went wrong. (Maybe because i was trying to downgrade from 5.4 to 5.0.5?) Anyways the device shows signs of life in the form of a pulsing white light but not HDMI output.

Because I was originally on 5.4 I guess this guide doesn't apply to me? I tried it anyways. No change. I'm thinking cache might contain files from 5.4 and crashing 5.0.5 but I'm not sure how to clear it with only preloader. The cache.img previously mentioned in this thread is now a dead link else I would give it a go. Open to advice/suggestions. I should have read up more before jumping right into this. Thanks for all of your hard work!
[Fire TV Android Development] clarke.hackworth:
[MENTION=3991724]rbox[/MENTION] Can you provide or point me to TEE1, etc images for different versions of the AFTV2 ? If we had the images we may be able to revive these devices with black screen bricks.

---------- Post added at 03:41 PM ---------- Previous post was at 03:36 PM ----------

I was investigating more. I noticed that the sloane-5.0.5-rooted_r4.zip image I had flashed contains an images directory with lk.bin and preloader images. As suggested previously it sounds like a version mis-match issue. There maybe another partition that also needs to be updated. Or if we had the preloader and lk from a newer version we may be able to put the new versions back on.
[Fire TV Android Development] zeroepoch:
I think [MENTION=3991724]rbox[/MENTION] tried to avoid updating the preloader or lk with his pre-rooted ROMS because, #1 there is an anti-rollback mechanism, and #2 the preloader hack was removed in the latest versions and could no longer be used. I could be wrong but you might already be running the older preloader if the unbrick is working at all.
[Fire TV Android Development] rbox:
What [MENTION=1239919]clarke.hackworth[/MENTION] said is correct. If you started on a version that wasn't rootable with the original method with the mediatek_inject, and then you tried to downgrade to 5.0.5, that probably would brick it. Those old versions included preloader and little kernel. And if you were to flash the old ones, it would be very bad. Does the unbrick actually work, or does it sit there and do nothing?
[Fire TV Android Development] jumoji:
For me, the unbrick process complete successfully, but when i power on again, there was nothing on the screen. The ftv does have a slow pulsing light.
[Fire TV Android Development] rbox:
You can try downloading the update package for the version you used to have from aftvnews.com's list. Extract the lk.bin and tz.img from it. Use mediatek_inject to flash them to the lk partition and the TEE1 partition.
[Fire TV Android Development] clarke.hackworth:
I have used mediatek_inject to flash lk.bin and tz.img to the /lk and /TEE1 partitions respectively from both of the following packages.

update-kindle-full_sloane-36.5.3.7_user_537175520

update-kindle-full_sloane-36.5.3.7_user_537174420

I even tried flashing the associated boot.img, reflashing the unbrick+ramdisk, and recovery images after that.

Nothing has worked. I still get no image and the white flashing light on the device. Possible steps to try next:

1. flash logo. I can't seem to find a logo from the old images. So I can't yet.

2. flash pre-loader image. Which partition does the preloader get flashed to?

Can anyone provide anymore insight or ideas?
[Fire TV Android Development] rbox:
Unfortunately, the preloader is in a special section of the MMC and I don't know how to write to it.
[Fire TV Android Development] jumoji:
Similar to clarke.hackworth, I have tried tz, lk and boot images from 5.0.5.1 and still black screen. The difference is that now i get orange light on the ftv instead. Hopefully, somebody else have better luck.
[Fire TV Android Development] inthesouth:
i think i bricked the firetv

Can anyone help me? I think I brick my fire tv box. I am trying the unbrick method but it seems to not work. I have plugged it into windows 10 with a male to male usb cable. Windows detects it for about 1.5 seconds and then it dissappears. It does this everytime the unit is cycling the boot with the white light blinking on the amazon unit. I have tried the usb keyboard method alt+i+printscreen. That will not get the unit into recovery either. Remote will not work either and the amazon unit to get into recovery either. Before this had happened I rooted it with kingo root and then tried to install a custom rom on it. Is this permanently bricked or are there other ways to get this unit to wakeup? Also, when plugged into adb fastboot that will not see the item is there. No communication at all. Please, I would appreciate any help at all. Sincerely.:confused: By the way it was version 5.2.1.1
[Fire TV Android Development] rbox:
Windows generally sucks at working well with the unbrick program. Lots of people have discussed what they have done to make it work better.

You said "Before this had happened I rooted it with kingo root and then tried to install a custom rom on it."

What did you do to brick it?
[Fire TV Android Development] inthesouth:
Not quite sure.

I f-ed it up. It was my first time. I successfully rooted it and everything seemed to be going well. Followed all the instructions and wiped delvic etc and etc as instructions said but when i went to reboot it went into this stuck restart procedure with no tv display thru hdmi. Nothing responds. Currently i have a $100 a white led light that blinks in a black plastic case.

Kingroot 4.1

Fire tv2 recovery zip file

Not sure if i was supposed to or not but did not make a fire tv 2 recovery on sd card but was in folder on unit itself internally within the fire tv unit.

Then loaded sloane 5 pre rooted rom.

After that i got a great door stopper.
[Fire TV Android Development] rbox:
Then either read through the thread about the people discussing using Windows, or use Linux.
[Fire TV Android Development] inthesouth:
i will try that

Thank you. I will let you know later the results.
[Fire TV Android Development] zeroepoch:
This cracked me up but I know that feeling. I shorted one of mine trying to get the serial port working inside and another flipping a bit intentionally in the preloader area. The third had been running Ubuntu for about a year.
[Fire TV Android Development] inthesouth:
I am curious.

Were you successful art getting each of them back to life or only the last one running ubuntu?
[Fire TV Android Development] Resonate:
I have the same issue. Used kingroot, went into TWRP and tried to install stock 5.0.5 so i can use firestarter. Took the image and now black screen no HDMI output at all. When plugged into windows you can hear it connecting and disconnecting every 15 seconds or so as if its constantly rebooting. Was running 5.2.1.1 originally.
[Fire TV Android Development] inthesouth:
same here

Any ideas on how to fix it yet? I have no clue and I have tried many things to no avail.
[Fire TV Android Development] clarke.hackworth:
I am in the same boat.

I got another FireTV2 and pulled all the non-system partitions from it. I have flashed all on my bricked (no hdmi) FireTV2. No luck. Either we need those partitions from a pre 5.2.0 FireTV2 or hardware hacking may be required to reflash the preloader with the newer version.
[Fire TV Android Development] Resonate:
No it's screwed :( tried both the i brick images no beans. Amazon bringing me a new one. I'll keep that stock lol.
[Fire TV Android Development] rbox:
5.0.5 had the old firmware. You need to reflash it with the new firmware. You can get it out of any update zip that [MENTION=5957312]AFTVnews.com[/MENTION] posts on the site. The problem is, it's in a protected area of the flash I don't know how you're going to flash it.