[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)

Search This thread

Ogriv

Senior Member
Jul 15, 2014
68
3
Yes you have to connect the stick for the script to work. Once you run bootrom-step.sh providing you have a stick that can be done. The script will shake hands with the device , then flash your stick when you "hit enter"

I like your short method BTW :cool:

Thanks for your response!

I finally got to perform the short and got the following:

macbook17s-MacBook-Pro:amonet macbook17$ sudo ./bootrom-step.sh

Password:

[2021-02-27 13:00:49.702105] Waiting for bootrom

[2021-02-27 13:01:42.080182] Found port = /dev/cu.usbmodem641

[2021-02-27 13:01:42.092209] Handshake

[2021-02-27 13:01:42.110557] Disable watchdog

* * * Remove the short and press Enter * * *

[2021-02-27 13:01:53.009710] Init crypto engine

[2021-02-27 13:01:53.194871] Disable caches

[2021-02-27 13:01:53.196899] Disable bootrom range checks

[2021-02-27 13:01:53.305967] Load payload from ../brom-payload/build/payload.bin = 0x4550 bytes

[2021-02-27 13:01:53.310142] Send payload

[2021-02-27 13:01:57.822641] Let's rock

[2021-02-27 13:01:57.827687] Wait for the payload to come online...

[2021-02-27 13:01:58.893716] all good

[2021-02-27 13:01:58.894128] Check GPT

[2021-02-27 13:01:59.236845] gpt_parsed = {'KB': (2048, 2048), 'DKB': (4096, 2048), 'EXPDB': (6144, 35584), 'UBOOT': (41728, 2048), 'boot': (43776, 32768), 'recovery': (76544, 32768), 'MISC': (109312, 1024), 'LOGO': (110336, 7168), 'TEE1': (117504, 10240), 'TEE2': (127744, 10240), 'system': (137984, 1761280), 'cache': (1899264, 512000), 'userdata': (2411264, 12858591), '': (0, 1)}

[2021-02-27 13:01:59.237084] Check boot0

[2021-02-27 13:01:59.465772] Check rpmb

Traceback (most recent call last):

File "/Users/macbook17/Desktop/Firestick Root/Tank Root/amonet-tank-v1.2.2/amonet/modules/main.py", line 158, in <module>

main()

File "/Users/macbook17/Desktop/Firestick Root/Tank Root/amonet-tank-v1.2.2/amonet/modules/main.py", line 98, in main

rpmb = dev.rpmb_read()

File "/Users/macbook17/Desktop/Firestick Root/Tank Root/amonet-tank-v1.2.2/amonet/modules/common.py", line 236, in rpmb_read
raise RuntimeError("read fail")
RuntimeError: read fail

I'm hoping the stick is flashed despite the Runtime Error and proceeded to try the following but got this:

macbook17s-MacBook-Pro:amonet macbook17$ ./adb reboot recovery
-bash: ./adb: No such file or directory
macbook17s-MacBook-Pro:amonet macbook17$ cd /Users/macbook17/Desktop/Firestick\ Root/Tank\ Root/amonet-tank-v1.2.2/amonet/Android\ SDK\ platform-tools
macbook17s-MacBook-Pro:Android SDK platform-tools macbook17$ ./adb reboot recovery
error: no devices/emulators found

At this point I’m either really close or I screwed up my stick (I’m hoping it’s not the later). I tried to find what the runtime error meant but still have to do a ton more reading. Would you happen to know how to fix this or what I can do from this point on?

Thank you!
 

Ogriv

Senior Member
Jul 15, 2014
68
3
Okay going to try this: https://itsfoss.com/create-bootable-ubuntu-usb-drive-mac-os/

will report back once I get it all sorted - Thank you for your response!!

Holy crap, Ubuntu was a ***** to install! (Long story) I finally got it up and running but when I run the script via:
sudo ./bootrom-step
nothing happens HOWEVER after doing some reading I tried:

bash -x ./bootrom-step.sh

and it seemed to work giving me the following results:

[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ bash -x ./bootrom-step.sh
+ set -e
+ cd modules
+ python3 main.py
[2021-03-02 19:23:57.672026] Waiting for bootrom

Silly question but does it matter what command I use to execute the script? (The instructions used ./bootrom-step.sh instead of bash -x ./bootrom-step.sh)

Thanks again!
 
Last edited:

Bertonumber1

Senior Member
May 17, 2020
701
183
Glasgow UK
Holy crap, Ubuntu was a ***** to install! (Long story) I finally got it up and running but when I run the script via:

nothing happens HOWEVER after doing some reading I tried:



and it seemed to work giving me the following results:



Silly question but does it matter what command I use to execute the script? (The instructions used ./bootrom-step.sh instead of bash -x ./bootrom-step.sh)

Thanks again!
Use
sudo ./bootrom-step.sh

Also make sure you've extracted the files to a folder on desktop and open a terminal within

Check that you're using latest distro.
 
Last edited:

Ogriv

Senior Member
Jul 15, 2014
68
3
Use
sudo ./bootrom-step.sh

Also make sure you've extracted the files to a folder on desktop and open a terminal within

Check that you're using latest distro.

Thanks for your response!

I'm getting the following:

[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ sudo ./bootrom-step.sh
sudo: ./bootrom-step.sh: command not found

As far as I can tell I think I've got the latest Ubuntu installed. When I launch software update app it says "software on this computer is up to date"....

I'll see if I can google a solution for this and feel free to shed some light thanks again for the help!

EDIT: I'm going to install Ubuntu again because initially I just did a minimal install, I wonder if that's why sudo isn't working/missing. ugh... I hate Ubuntu! (no offense for Ubuntu lovers out there lol)

EDIT2: Okay, did FULL reinstall with latest updates and still NO sudo! argh!!
 
Last edited:

Ogriv

Senior Member
Jul 15, 2014
68
3
[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ sudo ./bootrom-step.sh
sudo: ./bootrom-step.sh: command not found

edit: wait a minute, it says "command not found" but the bootrom-step.sh is in the directory and I tested sudo.

[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ sudo
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user] [command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-T timeout]
[-u user] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-T timeout] [-u
user] file ...

I don't get it.... :unsure:

Edit: sudo bash seems to work though...

[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ sudo bash ./bootrom-step.sh
[2021-03-03 22:03:14.073101] Waiting for bootrom

What's the difference??
 
Last edited:

Bertonumber1

Senior Member
May 17, 2020
701
183
Glasgow UK
edit: wait a minute, it says "command not found" but the bootrom-step.sh is in the directory and I tested sudo.



I don't get it.... :unsure:

Edit: sudo bash seems to work though...



What's the difference??
You have to

chmod a+x bootrom-step.sh

Then run

sudo ./bootrom-step.sh

Sometimes the permissions get mixed up unzipping. :cool:
 

Ogriv

Senior Member
Jul 15, 2014
68
3
You have to

chmod a+x bootrom-step.sh

Then run

sudo ./bootrom-step.sh

Sometimes the permissions get mixed up unzipping. :cool:

hrrmm... still didn't work... I get this:

[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ chmod a+x bootrom-step.sh
[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ sudo bootrom-step.sh
[sudo] password for ubuntu:
sudo: bootrom-step.sh: command not found
[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$
EDIT: Oh wait, It's finally working - Thank you!

[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ chmod a+x '/home/ubuntu/Desktop/Tank Root/amonet-tank-v1.2.2/amonet/bootrom-step.sh'
[email protected]:~/Desktop/Tank Root/amonet-tank-v1.2.2/amonet$ sudo ./bootrom-step.sh
[2021-03-04 15:53:04.613163] Waiting for bootrom

Going to try rooting in the next little bit, will report back...
 
Last edited:

Ogriv

Senior Member
Jul 15, 2014
68
3
Yeah it should work, only other thing I can say is make sure you're shorting correctly, make sure you're connecting with the resistor and gnd.

SUCCESS! I'M IN TWRP!!

now I need to figure out how to get magisk on there... lol, would you happen to know or point me in the right direction? I'll continue to research in the meantime... thank you again!! :D

Edit: damn, sorry I had to reboot the stick and got out of TWRP and don't know how to get back into it. I read at the beginning of the post to do it via adb but still not sure how it's done. (I need step by step instructions for that)
 
Last edited:

Ogriv

Senior Member
Jul 15, 2014
68
3
Code:
adb reboot recovery

Sorry, I'm a little late to the party and I'm lost, how do you use this command? is there a certain directory the terminal needs to be in? and is this done while the stick is fully booted? I recently flashed TWRP but forgot to connect mouse so I had to reboot and now I don't know how to get back into TWRP.
 
Last edited:

Bertonumber1

Senior Member
May 17, 2020
701
183
Glasgow UK
Sorry, I'm a little late to the party and I'm lost, how do you use this command? is there a certain directory the terminal needs to be in? and is this done while the stick is fully booted? I recently flashed TWRP but forgot to connect mouse so I had to reboot and now I don't know how to get back into TWRP.

To use this command adb must be enabled, let fireos boot normally and go into Settings>MyFireTV>Developer Options and enable "adb/usb debugging" also enable "apps from unknown sources"

As soon as you've done this you can type :

adb reboot recovery (remote adb shell or pc)

If that fails run :

sudo ./boot-recovery.sh

Connect your stick when it says :

**Waiting for preloader**
(not sure if tank amonet has this)

adb push \path\to\Magisk-v2x.xx.zip /sdcard
adb push \path\to\your firmware.zip /sdcard

You can interact via twrp either with an airmouse within the GUI. Or you can use the twrp command line.

Commands you will need (once you have your firmware and magisk on sdcard)

adb shell

twrp wipe /system
twrp wipe data
twrp wipe dalvik
twrp wipe cache

Next :

adb shell

twrp install nameofyourfirmware.zip
twrp install Magisk-v2x.xx.zip

(optional)
twrp wipe cache
twrp wipe dalvik
 
Last edited:
  • Like
Reactions: Ogriv and 0815hoffi

Ogriv

Senior Member
Jul 15, 2014
68
3
To use this command adb must be enabled, let fireos boot normally and go into Settings>MyFireTV>Developer Options and enable "adb/usb debugging" also enable "apps from unknown sources"

As soon as you've done this you can type :

adb reboot recovery (remote adb shell or pc)

If that fails run :

sudo ./boot-recovery.sh

Connect your stick when it says :

**Waiting for preloader**
(not sure if tank amonet has this)

adb push \path\to\Magisk-v2x.xx.zip /sdcard
adb push \path\to\your firmware.zip /sdcard

You can interact via twrp either with an airmouse within the GUI. Or you can use the twrp command line.

Commands you will need (once you have your firmware and magisk on sdcard)

adb shell

twrp wipe /system
twrp wipe data
twrp wipe dalvik
twrp wipe cache

Next :

adb shell

twrp install nameofyourfirmware.zip
twrp install Magisk-v2x.xx.zip

(optional)
twrp wipe cache
twrp wipe dalvik

Sweet, going to try this in Mac OS X terminal, I can't stand Ubuntu (no offense lol)

Will report back... TGIF

Any recommendations for best custom ROM for Firestick 2?
 
Last edited:

Ogriv

Senior Member
Jul 15, 2014
68
3
Sweet, going to try this in Mac OS X terminal, I can't stand Ubuntu (no offense lol)

Will report back... TGIF

Any recommendations for best custom ROM for Firestick 2?

okay, I managed to push the files onto the firestick but I still can't figure out how to control TWRP via command line, I get the following:

[2021-03-05 12:40:41.028663] Waiting for preloader
[2021-03-05 12:40:46.188846] Found port = /dev/cu.usbmodem2640
[2021-03-05 12:40:46.390566] Handshake
[2021-03-05 12:40:46.410677] Preloader ready, sending FACTORYM
macbook17s-MacBook-Pro:amonet macbook17$ adb shell
-bash: adb: command not found
macbook17s-MacBook-Pro:amonet macbook17$ ./adb shell
-bash: ./adb: No such file or directory
macbook17s-MacBook-Pro:amonet macbook17$ ./twrp wipe /system
-bash: ./twrp: No such file or directory
macbook17s-MacBook-Pro:amonet macbook17$ twrp wipe/system
-bash: twrp: command not found
macbook17s-MacBook-Pro:amonet macbook17$

Also tried connecting a usb mouse via a few usb hubs but it ends up controlling my laptop instead of the firestick. I'm guessing I need a special OTG hub for it to work properly then? When using the hub I notice it powers the firestick but doesn't invoke TWRP and terminal is just "Waiting on preloader" unless I connect the firestick directly to my macbook THEN it'll go into TWRP. lol

I'm exstatic I was able to get this far with your help, it is greatly appreciated!

EDIT: I figured it out! I had to cd into my "Android SDK platform-tools" and then I ran ./adb shell and presto I got this:

macbook17s-MacBook-Pro:Android SDK platform-tools macbook17$ ./adb shell
adb server version (29) doesn't match this client (41); killing...
* daemon started successfull

after which I entered the commands for twrp starting with:

twrp wipe /system

which finally gave me this and I was able to see TWRP doing it on my TV too!

~ # twrp wipe /system
Formatting System using make_ext4fs...
Done processing script file

Yippeee! Thank you again for pointing me in the right direction! TGIF

Gonna have fun messing around with the firestick, if all goes well I'm gonna do the same to my other firestick! :D

EDIT: Sorry, embarassing question but how the hell do I get apps on here? I tried pushing .apks to install via TWRP but they didn't install and I don't see any file manager apps after booting into lineage, it's just bare bones android OS. I'll continue researching but if you can point me in the right direction again I'd be very greatful!

EDIT: N/M, I got it ALL sorted out! I ended up ditching Lineage and flashed Fire TV Stick 2 (tank) Prerooted Stock Images [5.2.7.3_r1], everything works great! Installed adaway, magisk, and going to install custom launcher - thanks again!!! :D(y)
 
Last edited:
  • Like
Reactions: Bertonumber1

Bertonumber1

Senior Member
May 17, 2020
701
183
Glasgow UK
okay, I managed to push the files onto the firestick but I still can't figure out how to control TWRP via command line, I get the following:



Also tried connecting a usb mouse via a few usb hubs but it ends up controlling my laptop instead of the firestick. I'm guessing I need a special OTG hub for it to work properly then? When using the hub I notice it powers the firestick but doesn't invoke TWRP and terminal is just "Waiting on preloader" unless I connect the firestick directly to my macbook THEN it'll go into TWRP. lol

I'm exstatic I was able to get this far with your help, it is greatly appreciated!

EDIT: I figured it out! I had to cd into my "Android SDK platform-tools" and then I ran ./adb shell and presto I got this:



after which I entered the commands for twrp starting with:



which finally gave me this and I was able to see TWRP doing it on my TV too!



Yippeee! Thank you again for pointing me in the right direction! TGIF

Gonna have fun messing around with the firestick, if all goes well I'm gonna do the same to my other firestick! :D

EDIT: Sorry, embarassing question but how the hell do I get apps on here? I tried pushing .apks to install via TWRP but they didn't install and I don't see any file manager apps after booting into lineage, it's just bare bones android OS. I'll continue researching but if you can point me in the right direction again I'd be very greatful!

EDIT: N/M, I got it ALL sorted out! I ended up ditching Lineage and flashed Fire TV Stick 2 (tank) Prerooted Stock Images [5.2.7.3_r1], everything works great! Installed adaway, magisk, and going to install custom launcher - thanks again!!! :D(y)
Once you boot up your rom/fireos you can use easy firetools or your pc ( adb link) to install apks. Or you can install something like Downloader apk from amazon store and do it that way.
Me personally I use easyfire tools on my tablet, download the apps I want to tablet and send/install them to the stick. Pretty simple really .

Just goto my firetv>about> network>

In settings and get your device IP address. Once you've enabled adb you can connect with your phone or tablet and install the apps that way.

Hope this helps

Glad you got it working

Regards

Edit: Lineage CM tank 12.1 is work in progress and still is quite buggy. Perhaps stick with rooted stock fireos until further development makes lineage more stable.
 
  • Like
Reactions: Ogriv

Ogriv

Senior Member
Jul 15, 2014
68
3
Once you boot up your rom/fireos you can use easy firetools or your pc ( adb link) to install apks. Or you can install something like Downloader apk from amazon store and do it that way.
Me personally I use easyfire tools on my tablet, download the apps I want to tablet and send/install them to the stick. Pretty simple really .

Just goto my firetv>about> network>

In settings and get your device IP address. Once you've enabled adb you can connect with your phone or tablet and install the apps that way.

Hope this helps

Glad you got it working

Regards

Edit: Lineage CM tank 12.1 is work in progress and still is quite buggy. Perhaps stick with rooted stock fireos until further development makes lineage more stable.

Would happen to know how to TWRP backup to an external drive? My firestick tv 2 doesn't have enough room to make the backup on so wondering what the command would be to back it up directly to my macbook?

thanks again!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hey, thanks for your prompt response! I got it working and discovered the problem was not my method of shorting (using a copper wire) it was because I failed to use "sudo" when executing the "./bootrom-step.sh" command. MAN, is this an Ubuntu thing? such a fussy OS! lol

    I installed TV Launcher but find that sometimes the back button stops working and only way to bring it back is to restart the firestick, you ever experience that? if so, do you know of a remedy?

    Still trying to figure out how to TWRP back up to my macbook via terminal/command line...
    Yeah use atv launcher pro or leanback firetv launcher from :


    Remember to use ftvlaunchx (launcher hijack) apk if using fireos on or below 5.2.7.2(rev2).

    Above that version youre going to have to go down the road of disable firetv launcher and firehomestarter to enable custom launcher.

    Remember to grab hoffis newsettings root apk (markus firetools) to replace the access to the settings menu.
    1
    Installed Marcustools and ATV, WAY more responsive! only problem is Prime Video doesn't launch. When I click it, it just goes back to the ATV launcher. Any ideas? (besides installing another copy of prime video? I've done that before but found it keeps BOTH copies of prime, kinda redundant)
    Yeah I prefer using ATV launcher Pro myself. I don't use prime so can't offer advice. Maybe hide root with Magisk hide?
    Then clear data/cache in manage applications for prime and relaunch it? Idk
    Regards
  • 63
    Read this whole guide before starting.

    This is for the 2nd gen Fire TV Stick (tank)

    Current relase: amonet-tank-v1.2.2.zip

    NOTE: Recent reports indicate a change that disables brom DL-mode
    The change seems to have been introduced with devices that where manufactured in December 2019 or later.
    The change is unrelated to the software-version and results in the device not showing up as a USB device when shorted.
    Unfortunately these devices cannot currently be unlocked.

    NOTE: If you are on version 1.0, don't update to 1.2.1 through TWRP, as there is a bug.
    NOTE: This issue has been fixed in version 1.2.2
    NOTE: When updating from version 1.0, don't install anything else before rebooting



    To update to the current release if you are already unlocked, just flash the zip in TWRP.

    What you need:
    • A Linux installation or live-system
    • A micro-USB cable
    • Something conductive (paperclip, tweezers etc)
    • Something to open the stick.


    NOTE: Ideally you want to update your system to 5.2.6.9 before starting this process, since this flashes the 5.2.6.8 boot.img and people have reported issues with adb-authorization with older firmware.
    Since version 1.2 this isn't required, because instead of flashing the 5.2.6.9 boot.img, your existing boot.img will be patched.
    It is still recommended to first update to 5.2.6.9


    Install python3, PySerial, adb and fastboot. For Debian/Ubuntu something like this should work:
    Code:
    sudo apt update
    sudo add-apt-repository universe
    sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot

    Make sure ModemManager is disabled or uninstalled:
    Code:
    sudo systemctl stop ModemManager
    sudo systemctl disable ModemManager


    NOTE: If you have issues running the scripts, you might have to run them using sudo.
    Also try using different USB-ports (preferably USB-2.0-ports)


    1. Extract the attached zip-file "amonet-tank-v1.2.2.zip" and open a terminal in that directory.
    2. start the script:
    Code:
    ./bootrom-step.sh

    It should now say Waiting for bootrom.

    Short CLK to GND (The metal shielding is also GND) according to the attached photo and plug it in.


    NOTE:

    In lsusb the boot-rom shows up as:
    Code:
    Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone

    If it shows up as:
    Code:
    Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
    instead, you are in preloader-mode, try again.

    dmesg lists the correct device as:
    Code:
    [ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00


    4. When the script asks you to remove the short, remove the short and press enter.

    5. Wait for the script to finish.
    If it stalls at some point, stop it and restart the process from step 2.

    6. Your device should now reboot into unlocked fastboot state.

    7. Run
    Code:
    ./fastboot-step.sh

    8. Wait for the device to reboot into TWRP.

    9. Use TWRP to flash custom ROM, Magisk etc.


    NOTE:
    Only ever flash boot/recovery images using TWRP, if you use FlashFire or other methods that are not aware of the exploit,
    your device will likely not boot anymore (unless you flashed a signed image).
    TWRP will patch recovery/boot-images on the fly.


    NOTE:
    This process does not disable OTA or does any other modifications to your system.
    You will have to do that according to the other guides in this forum.


    Very special thanks to @xyz` for making all this possible and putting up with the countless questions I have asked, helping me finish this.
    Thanks to @hwmod for doing initial investigations and providing the attached image.
    11
    There are three options for interacting with TWRP:
    1. A mouse via USB-OTG
    2. TWRP commandline via adb: https://twrp.me/faq/openrecoveryscript.html
    3. Via /cache/recovery/command

    Example for /cache/recovery/command:
    Code:
    echo "--update_package=/path/to/zipfile" > /cache/recovery/command
    echo "--wipe_cache" >> /cache/recovery/command
    reboot recovery

    Should you somehow end in a bootloop you can boot into hacked fastboot or recovery using.
    Code:
    sudo ./boot-fastboot.sh

    Code:
    sudo ./boot-recovery.sh

    NOTE:This will only work if the boot-exploit is still there.

    Source Code:
    https://github.com/chaosmaster/amonet
    https://github.com/chaosmaster/android_bootable_recovery
    9
    Changelog

    Version 1.2 (25.03.2019)
    • Update TWRP to twrp-9.0 sources
    • Implement downgrade-protection for LK/PL/TZ
    • Add scripts to enter fastboot/recovery in case of bootloop
    • Automatically restore boot-patch when you boot into recovery

    Features.

    • Hacked fastboot mode lets you use all fastboot commands (flash etc).
    • Boots custom/unsigned kernel-images (need to be patched)
    • For the devs: sets printk.disable_uart=0 (enables debug-output over UART).
    • TWRP protects from accidental lk/preloader/tz downgrades
    • Set bootmode via preloader

    NOTE: Hacked fastboot can be reached via TWRP.

    NOTE: Hacked fastboot won't patch your boot/recovery-images, so you can easily go back to stock.
    Use TWRP for autopatching.
    8
    Please read the instructions k4y0z wrote (1st page), then read the extra info below. It was my first time rooting a FireTV Stick via hardware and I had a lot of questions. Although, most answered via post replies throughout this thread. Here is a descriptive version of the rooting process for other beginners from what I learned.

    Any damages or issues resulting from rooting your own device falls on you!

    EDIT: I know this is long, but if you are a beginner DO NOT SKIM THROUGH.

    A Linux operating system is required. Ubuntu 19.04 is recommended and the following instructions are for Debian based systems like Ubuntu.

    The following packages were used (Check for updates):
    Amonet-tank-v1.2.2
    tank-5.2.6.9-rooted_r1
    Magisk-v19.2
    Everything was saved to the Downloads folder.

    Step 0: Open the FireTV Stick
    1. Use a plastic tool like an unused credit card. With a bit of force push the plastic tool into the edge (seam) of the FireTV Stick while slightly popping the side wall outwards until a snap. Continue on all sides until the plastic shell can be separated. Then, remove the motherboard. Disassembly video - Link
    2. On the side with the smaller metal shield, use a thin blunt knife or flathead. Start near the HDMI port above and below the black pad. There are small gaps that can be used to push the metal shield up. Continue around the metal shield until it is removed. Be careful not to scratch the board and leave the metal rim.
    3. Attach the micro USB cable to the FireTV Stick but not to a computer!
    4. Extract “amonet-tank-v1.2.2.zip” in the Downloads folder and open a Terminal on a Linux system.

    Step 1: Update Ubuntu
    Code:
    sudo apt update && sudo apt upgrade -y

    Step 2: Install Dependencies (Ignore if Android Studio is installed)
    Code:
    sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot

    Step 3: Stop and Disable ModemManager
    Code:
    sudo systemctl stop ModemManager
    sudo systemctl disable ModemManager

    Step 4: Short CLK to GND (Please read k4y0z instructions as well)
    1. Navigate to script directory:
      Code:
      cd ~/Downloads/amonet-tank-v1.2.2/amonet/
    2. Start the script:
      Code:
      sudo bash bootrom-step.sh
    3. When the Terminal prompt says "waiting for bootrom" (Easiest with two people)
    4. Place the removed metal shield next to the disassembled FireTV Stick. If it doesn't short, then use k4y0z suggested GND method.
    5. Use a paperclip (etc), and lightly touch the bottom metal piece of the CLK to the metal shield (CLK location, but use metal shield as GND). The CLK is tiny so be careful.
    6. Plug the USB cable connected to the FireTV Stick into the computer while holding the short!!! When I did it, I accidentally lost the short but it still worked (uncommon).
    7. The Terminal prompt will say when to "remove the short and press enter".
    8. Wait until the script finishes. If the script stalls, unplug USB and start the script again and short.
    9. Run fastboot script:
      Code:
      sudo bash fastboot-step.sh
    10. Next step has instructions.

    Step 5: Using Fastboot to install Roms and Magisk
    1. Wait for the FireStick to reboot into TWRP
    2. Push Tank’s prerooted rom zip file onto the FireTV Stick sd card:
      Code:
      adb push ~/Downloads/tank-5.2.6.9-rooted_r1.zip /sdcard/
    3. Push Magisk zip file:
      Code:
      adb push ~/Downloads/Magisk-v19.2.zip /sdcard/
    4. Go into ADB Shell:
      Code:
      adb shell
    5. Install rom:
      Code:
      twrp install /sdcard/tank-5.2.6.9-rooted_r1.zip
    6. Install Magisk:
      Code:
      twrp install /sdcard/Magisk-v19.2.zip
    7. EDIT: STOP! DO NOT WIPE ANYTHING OTHER THEN WHAT WAS STATED OR SKIP WIPING ENTIRELY IF YOU'RE A BEGINNER! You can skip wiping and reboot (#9 & #10) or decide if you want to wipe the cache and dalvik only (advanced):
      Code:
      twrp wipe cache
    8. Code:
      twrp wipe dalvik
    9. Code:
      reboot -p
    10. Unplug USB and plug the disassembled FireTV Stick into a monitor or TV. Use the power brick and handle with care.
    11. The "Optimizing Storage" screen will display and will take 10 minutes to complete.

    Optimizing Storage Screen Hangs Issue*
    Try plugging the FireTV Stick's USB to a different power brick temporarily.

    Otherwise and unfortunately, the following instructions will erase your apps and will force you to re-register your FireTV Stick.
    1. Unplug the FireTV Stick USB from the power brick only and open a Terminal window.
    2. Navigate to script directory:
      Code:
      cd ~/Downloads/amonet-tank-v1.2.2/amonet/
    3. Run the boot recovery script to boot into twrp:
      Code:
      sudo bash boot-recovery.sh
    4. When the Terminal prompt says "Waiting for preloader", plug the USB into the computer.
    5. Go into ADB Shell:
      Code:
      adb shell
    6. Code:
      twrp wipe data
    7. Code:
      twrp wipe cache
    8. Code:
      twrp wipe dalvik
    9. Install rom:
      Code:
      twrp install /sdcard/tank-5.2.6.9-rooted_r1.zip
    10. Install Magisk:
      Code:
      twrp install /sdcard/Magisk-v19.2.zip
    11. Code:
      reboot -p
    12. Plug FireTV Stick into a TV or Monitor and wait for the "Optimizing Storage" screen to finish and re-register your device.

    TWRP Can Be Accessed Anytime via Boot Recovery Script*
    Run the boot-recovery script and plug the FireTV Stick into the computer.

    How to backup TWRP**
    I haven't made a backup yet via the command line. But I assume it would go as follow and if anyone wants to help, please do.
    1. Unplug the FireTV Stick USB from the power brick only and open a Terminal window.
    2. Navigate to script directory:
      Code:
      cd ~/Downloads/amonet-tank-v1.2.2/amonet/
    3. Run the boot recovery script to boot into twrp:
      Code:
      sudo bash boot-recovery.sh
    4. When the Terminal prompt says "Waiting for preloader", plug the USB into the computer.
    5. Go into ADB Shell:
      Code:
      adb shell
    6. Create a TWRP backup (everything):
      Code:
      twrp backup twrp
      OR here is a list of partitions that can be backed up.

    Here is a list of bloatware to disable***
    Be extremely careful. Disabling the wrong thing can break your FireTV Stick! - Link

    1. Enable ADB debugging via FireTV Stick Settings and get the ip address under About.
    2. Connect to the FireTV Stick via Wifi:
      Code:
      adb kill-server
      adb start-server
      adb connect <ip-address>:5555 # Grant access via prompt on TV or monitor.
      adb shell
      su
    3. If su command does not work in shell, then open Magisk app and grant root access to shell (in sidebar menu).
    4. Disable bloat as shown in the link above. Be careful!!
    5
    I have not ported my bootmenu recovery to this device yet. I'll try to work on getting the device added to my build system and see what I can put together. Unfortunately I don't have any time this weekend, I'll see if I can get something going next weekend.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone