FireTV 2 (sloane) Unbrick Image

Search This thread

mtidmarsh

Member
Mar 4, 2009
10
0
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.

Sorry, can you explain what the slower method is, or point me to a post?

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.

It’s where you use “unbrick+ramdisk.img”.

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?!
 

tech3475

Senior Member
Nov 4, 2013
90
10
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?!

Unfortunately, hardmod aside, for now it does.
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
Anyone have the old preloader.img file? Some good news on the horizon if it works just need the old preloader...

I have mostly every version of stock firmware. Please let me know what version of stock firmware contains the "old preloader" you need.
 

CFKod

Senior Member
Thanks @rbox.

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 ?
 
Last edited:

rbox

Recognized Developer
Apr 22, 2011
1,776
2,606
  • Like
Reactions: CFKod and Kramar111

CFKod

Senior Member

CFKod

Senior Member
Damn it... darn addon.d script got me... flashed prerooted rom and magisk kept auto installing directly after ... put uninstaller on micro sd... twrp wouldn't detect sd... so reloaded theme as tried remounting .. reload theme restarts ... i got distracted and I missed the cue to select twrp...

Hello black and white Amazon logo ?

Shorted again... for the last time . Today lol
Magisk removed....rbox rom installed.. life is good again
 

TessTickles

Member
Dec 16, 2019
12
0
Hi I am not new here, been on years - just not for a while and lost access to my email account (forgotten password) so had to start again :(

Anyhoot - I have a Fire TV gen 2 that is bricked (amazon log on a loop).

Does this fix sort a standard factory Fire TV back to working standard or is it basically loading a third party firmware to get ove the problem. i have read the thread but can't seem to get the answer for this question.

Thanks
 

errut

Senior Member
Mar 28, 2016
109
4
Amazon Fire TV
AFTV2 with the latest Sloane prerooted Image: Bootet to TRWP and tried to wipe System, which did not work, Made hard Reboot and now i find only the Amazon Headline and nothing is moving.
My Question: is the AFTV irrevocably damaged or is there any chance to recover ?
 

tech3475

Senior Member
Nov 4, 2013
90
10
AFTV2 with the latest Sloane prerooted Image: Bootet to TRWP and tried to wipe System, which did not work, Made hard Reboot and now i find only the Amazon Headline and nothing is moving.
My Question: is the AFTV irrevocably damaged or is there any chance to recover ?

Software only?:
If you rooted with the USB method and only ever stuck with rbox, you may be able to use this method like I did.

If you didn’t use the USB method, the issue will be the preloader version, as newer versions block this method.

If you’re willing to open it up, this may work:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
 

errut

Senior Member
Mar 28, 2016
109
4
Amazon Fire TV
Thanks for your advice. I realy don`t remember how i did it, but I rember that the device had a sw-version which allowed to root it.
I hope I find your method here.
Is this post 1?
How to connect AFTV2 and PC via USB?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    This will help you unbrick a bricked FireTV 2. You must download the following:

    Extract all 3 zip files to the same directory.

    You must decide if you want to use unbrick.img or unbrick+ramdisk.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+ramdisk.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.

    Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.

    First, it will ask you which file you want to use, unbrick.img or unbrick+ramdisk.img. You must type the name of the image you want to use.

    Make sure the USB cable is connected and turn on the FireTV 2.

    Then it will start reading from the FireTV. Then it will prompt you with a warning:

    Code:
    No target file specified.  Is this a partition image?
    If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
    Write partition image? <y|n>

    Type a 'y' and hit enter.

    It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
    4
    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?

    That's odd.... what do you mean it automatically starts trying to mount the partitions and fails? Where does TWRP show that? If you are getting the orange light it sounds like maybe you wiped your boot partition and it's not actually going to TWRP but stock recovery?

    Extract the boot.img from the prerooted ROM and place it in the directory with the unbrick files. Run handshake and reboot to get it to handshake, then run this:

    Code:
    mediatek_inject firetv2 YOURCOMPORT boot.img /boot -

    Replacing YOURCOMPORT with whatever handshake said your comport was. That should rewrite the boot image.
    2
    When going into advanced wipe after running those 2 commands. I included an attachment with the error updates.

    UPDATE: So after reading "/dev/block/platform/mtk-msdc.0/by-name/cache is apparently in use by the system; will not make a filesystem here!" I figured I should try to wipe system. It worked! So then I tried to wipe data and cache. They both worked! I'm not sure if that means I'm home free but the errors are gone. I haven't rebooted yet though.

    Well try to reboot and see what happens.
    2
    After using your cache.img the FireTV booted to TeamWIN. I selected Advanced Wipe ticked the cache and data then clicked the swipe bar in the bottom right to start the process. The picture shown is what happened next. I was still in the boot menu though. So I did it again received the same errors and clicked reboot. It warned me that I don't have an OS. Now I'm in the same boot loop again.

    I'm currently running your cache.img to get out of the boot loop again.

    Any other ideas for me to try?

    Connect via adb shell and run these 2 commands:

    Code:
    mke2fs /dev/block/platform/mtk-msdc.0/by-name/userdata
    mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
    2
    Okay, I followed those instructions. Here is the updated errors. They're similar but different.

    You're getting that after doing advanced wipe AND rebooting? That's not right...