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

Search This thread

Sus_i

Senior Member
Apr 9, 2013
1,952
894
Yeah Sus_i the stick isn't dead but I think the clk is. I m not getting any message at all after I run the process, ah well

The black/white logo shouldn't show up with a damaged CLK resistor.

Quick CLK test:
Run the bootrom-step 'without a short', in case the script tells to remove the short, the CLK is probably damaged...

If yes, that is fixable with a simple solder bridge or a short wire... soldered in place instead the resistor.
 
The black/white logo shouldn't show up with a damaged CLK resistor.

Quick CLK test:
Run the bootrom-step 'without a short', in case the script tells to remove the short, the CLK is probably damaged...

If yes, that is fixable with a simple solder bridge or a short wire... soldered in place instead the resistor.
I'm sorry I thought I said there was no screen showing at all now, I've been using a paperclip to do the short, it was thinnest thing I had.
Yeah thought that it would be fixable.
I used to do that in old cb radios etc that had blown. Only this is much more smaller, to the point I can hardly see the component.
I will grab a cuppa then go back to it, been stuck to it since last night. But soldering something that size is out of my league. If anyone wants it before I ditch it they can have it @Sus_i
 

Sus_i

Senior Member
Apr 9, 2013
1,952
894
II used to do that in old cb radios etc that had blown. Only this is much more smaller, to the point I can hardly see the component.
I will grab a cuppa then go back to it, been stuck to it since last night. But soldering something that size is out of my league.

Yeah, its much smaller, maybe use your phones camera and just zoom it a bit ;)
A repair doesn't have to look nice. A small amount of flux, a tinned peace of copper wire and it is almost done.
Here in that posting is a picture of such a repair...
 
Yeah, its much smaller, maybe use your phones camera and just zoom it a bit ;)
A repair doesn't have to look nice. A small amount of flux, a tinned peace of copper wire and it is almost done.
Here in that posting is a picture of such a repair...
Sus_i cheers man, I'll go for it anyway.... may as well just take a dive since we've came this far eh? I will get the solder out shortly and get my crocodile grip/magnifying glass out as well. :eek:
 
I keep getting this error. I am hoping someone has a solution to this for this at the moment. Right now I am uninstalling the previous command and reinstalling it. (did not work)
Here is the code
Code:
nicolas@nicolas-ThinkPad-X140e:~/Desktop/Fire TV/twrp/amonet$ sudo ./bootrom-step.sh 
[2020-06-22 08:46:16.599303] Waiting for bootrom
[2020-06-22 08:51:18.404170] Found port = /dev/ttyACM0
[2020-06-22 08:51:18.425727] Handshake
[2020-06-22 08:51:18.446887] Disable watchdog
Traceback (most recent call last):
  File "main.py", line 158, in <module>
    main()
  File "main.py", line 76, in main
    handshake(dev)
  File "/home/nicolas/Desktop/Fire TV/twrp/amonet/modules/handshake.py", line 11, in handshake
    dev.write32(0x10007000, 0x22000000)
  File "/home/nicolas/Desktop/Fire TV/twrp/amonet/modules/common.py", line 160, in write32
    self.check(self.dev.read(2), b'\x00\x01') # arg check
  File "/home/nicolas/Desktop/Fire TV/twrp/amonet/modules/common.py", line 87, in check
    raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
Sorry if the output is terrible. I don't know how to put it in a box (unless I figured it out)
 
Last edited:
Been having trouble

I keep getting this error. I am hoping someone has a solution to this for this at the moment. Right now I am uninstalling the previous command and reinstalling it. (did not work)
Here is the code
Code:
nicolas@nicolas-ThinkPad-X140e:~/Desktop/Fire TV/twrp/amonet$ sudo ./bootrom-step.sh 
[2020-06-22 08:46:16.599303] Waiting for bootrom
[2020-06-22 08:51:18.404170] Found port = /dev/ttyACM0
[2020-06-22 08:51:18.425727] Handshake
[2020-06-22 08:51:18.446887] Disable watchdog
Traceback (most recent call last):
  File "main.py", line 158, in <module>
    main()
  File "main.py", line 76, in main
    handshake(dev)
  File "/home/nicolas/Desktop/Fire TV/twrp/amonet/modules/handshake.py", line 11, in handshake
    dev.write32(0x10007000, 0x22000000)
  File "/home/nicolas/Desktop/Fire TV/twrp/amonet/modules/common.py", line 160, in write32
    self.check(self.dev.read(2), b'\x00\x01') # arg check
  File "/home/nicolas/Desktop/Fire TV/twrp/amonet/modules/common.py", line 87, in check
    raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
Sorry if the output is terrible. I don't know how to put it in a box (unless I figured it out)

Ok I have been trying to get the script work. The only time I got somewhere until it said there was multiple ports or something like that. Does anyone know a more in depth instructions? or have any tips
 
So after fluffing the last one and fooking the clk resistor. I tried a repair with the phone camera and ended up soldering the 3 resistors together with shaky hands and bad eyesight the main culprit lmao (as well as a massive soldering iron point)This time I will use a thin tiny piece to short the resistor to avoid damaging it(learn by our mistakes right?) I ordered a new firestick, anyone in UK or US there is a special offer on 2nd gens and new from curry's UK they're on sale for £19.95 brand spanking new and they are a backlog of augustish 2019 sticks according to curry's UK. Well worth buying some of these. I'll do it properly this time @Sus_i. I just did not realise I didn't have to keep shorting.
Anyway I will post back with some updated steps and outputs for newbies like myself. Cheers for the help guys. Really appreciated

---------- Post added at 11:09 PM ---------- Previous post was at 10:50 PM ----------

Yes, just get tweezers and get in about it carefully, it will separate and leave another piece which will also come off if you pull carefully.

Thanks. Does this need a specific version or does it work on any FireOS version

It does not matter what os version you have, as long as your firestick is not one of the new chipsets from around December 2019 which have been patched, modified to prevent this modification happening m8. Make sure you isolate the clk resistor with something thin and flexible (a thin piece of copper wire strand or something (I made mistake of using a cable tie about the thickness of a paperclip which resulted in damaging the resistor. Also note, once the boot script step runs and enters the stick
You DO NOT have to keep shorting, this is the mistake I foolishly made like a jackass I kept shorting the resistor with a mega piece of metal m8. Just be careful and you should be OK
 
Last edited:
  • Like
Reactions: CFKod

y0

Senior Member
May 25, 2006
146
15
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.


can we do this all in MAC (catalina 10.15) if so what commands need to be changed ? please anyone ??
 

y0

Senior Member
May 25, 2006
146
15
Ok I have been trying to get the script work. The only time I got somewhere until it said there was multiple ports or something like that. Does anyone know a more in depth instructions? or have any tips

i am on KALI LINUX updated according to the tutorial in the first post... without any error but having exactly same error as yours SERIAL PROTOCOL MISMATCH
 

y0

Senior Member
May 25, 2006
146
15
HURRAY..........


I THINK I HAVE DONE IT BUT WHEN I TRY THE 7TH STEP

our device should now reboot into unlocked fastboot state.

7. Run
Code:

./fastboot-step.sh

I get something unexpected

[root@sysresccd ~/amonet]# ./fastboot-step.sh
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
./fastboot-step.sh: line 5: 1828 Aborted (core dumped) fastboot flash recovery bin/twrp.img
[root@sysresccd ~/amonet]#


now??
 

y0

Senior Member
May 25, 2006
146
15
sorry for another post but i am too excited here i am now i am very close

my TV SCREEN showing this now

UNLOCKED FASTBOOT MODE:(0) XYZ , K4Y0Z . NW

please tell me what now??
 

y0

Senior Member
May 25, 2006
146
15
w00t

root@localhost:~/Downloads/amonet-tank-v1.2.2/amonet# ./fastboot-step.sh
< waiting for any device >
target reported max download size of 134217728 bytes
sending 'recovery' (7318 KB)...
OKAY [ 0.338s]
writing 'recovery'...
OKAY [ 1.119s]
finished. total time: 1.457s
target reported max download size of 134217728 bytes
sending 'TEE2' (1255 KB)...
OKAY [ 0.133s]
writing 'TEE2'...
OKAY [ 0.112s]
finished. total time: 0.245s
...
OKAY [ 0.003s]
finished. total time: 0.003s


Your device should now reboot into TWRP

root@localhost:~/Downloads/amonet-tank-v1.2.2/amonet#

---------- Post added at 09:52 PM ---------- Previous post was at 09:29 PM ----------

BTW I have the latest Firestick in INDIA with version 5.2.7.3 just rooted and flashed with TWRP recovery

If anyone need help in india for rooting of Amazon firestick Binge Edition let me know as I have found it really difficult for me to arrange all for it

Anyways now my question is how to use recovery it’s unable to move in any function I mean I can’t slide it the arrow or do anything with a remote ?
 
  • Like
Reactions: Bertonumber1

abelgarcia94

Member
Nov 28, 2014
21
1
After root, is there any way to completely remove Fire tv launcher and replace it with another launcher.? The only thing I use from Amazon is prime video but could do with out. Just want a simple launcher to run 5 video apps that can be side loaded and installed
 

Sus_i

Senior Member
Apr 9, 2013
1,952
894
Anyways now my question is how to use recovery it’s unable to move in any function I mean I can’t slide it the arrow or do anything with a remote ?

Take a look here...

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------

hey...

just one question.....how can i check if i have an unrootable stick or not.?
sorry im amateurish #:)

Follow the OP and see what happens ;)
There isn't a check without shorting the CLK...
A patched bootrom doesn't show up in lsusb while shorted and the bootrom-script isn't able to find it...
 
Last edited:

y0

Senior Member
May 25, 2006
146
15
Take a look here...

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------



Follow the OP and see what happens ;)
There isn't a check without shorting the CLK...


Ye ok thanks mate what about stopping a default launcher and installing a new one within a recovery I guess BingeEdition won’t let run anything until we delete or move the launcher and I am not sure if the launcher is blocking everything even root confirmations normal mode


Sent from my iPhone using Tapatalk
 

Sus_i

Senior Member
Apr 9, 2013
1,952
894
Ye ok thanks mate what about stopping a default launcher and installing a new one within a recovery I guess BingeEdition won’t let run anything until we delete or move the launcher and I am not sure if the launcher is blocking everything even root confirmations normal mode


Sent from my iPhone using Tapatalk

In short, there isn't a way to do what you want with the binge edition stick fireOS.
Only way to use it without a valid subscription is/was install lineage.
You may take a backup with TWRP before flashing lineage, at least system and data, just in case something goes wrong.
 

y0

Senior Member
May 25, 2006
146
15
In short, there isn't a way to do what you want with the binge edition stick fireOS.
Only way to use it without a valid subscription is/was install lineage.
You may take a backup with TWRP before flashing lineage, at least system and data, just in case something goes wrong.


We can’t get Read ,Write access in TWRP mode?? As I see adb remount command is not working if anyhow we can write to the system atleast I can try to modify the launcher


Sent from my iPhone using Tapatalk
 

Sus_i

Senior Member
Apr 9, 2013
1,952
894
We can’t get Read ,Write access in TWRP mode?? As I see adb remount command is not working if anyhow we can write to the system atleast I can try to modify the launcher

Did you read the third post?

You have two options for interacting with TWRP:
First, otg cable and a mouse... and do the swipe in order to allow r/w access ;)
Second, power up the stick from a PC's usb port and use adb + twrp command line... and forget about the swipe, not needed at all.

As soon you install magisk, you have a third option, the cache recovery commands. See post 3 for reference.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 71
    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.
    12
    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
    10
    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.