Bootloader Unlock and TWRP Released for Fire TV Stick 4K Series

A newly published development release brings bootloader unlocking, root access, TWRP custom recovery, and unbrick tools to several Amazon Fire TV Stick 4K models running Fire OS 8.

The release was announced in a new XDA Developers thread. On XDA, karat and mantra identify the two supported device families. They include the Fire TV Stick 4K Max 2nd Gen, Fire TV Stick 4K 2nd Gen, and Fire TV Stick 4K Plus.

This is a more substantial development than gaining temporary root access inside a running Fire OS session. A bootloader unlock changes what the device can start, while TWRP provides an independent recovery environment for maintenance and software testing.

This article is news and security information. It does not include installation steps, downloads, exploit commands, test-point locations, instructions for disabling security protections, or methods for blocking Amazon updates.

Compatible devices

Amazon’s current device table lists the supported products as Fire OS 8 devices based on Android 11.

Fire TV Stick 4K Max 2nd Gen from 2023 has build model AFTKRT, 16 GB of storage, and the codename karat.
Fire TV Stick 4K 2nd Gen from 2023 has build model AFTKM, 8 GB of storage, and the codename mantra.
Fire TV Stick 4K Plus from 2025 has build model AFTMA08C15 and belongs to the mantra family.

The 2023 Fire TV Stick 4K and the 2025 Fire TV Stick 4K Plus use different build models within the mantra family. The 4K Max uses karat and is a separate target.

The release is not intended for older Fire TV Sticks that happen to have a similar retail name. In particular, the first-generation Fire TV Stick 4K Max uses the codename kara, not karat. Files built for one codename should never be assumed to work on another.

This goes beyond temporary GhostLock root

The new release follows the arrival of GhostLock temporary root for the karat model by only two days, but the two developments solve different problems.

GhostLock is a local Linux kernel exploit. It can create a root shell while Fire OS is running, but that elevated session ends when the device reboots. It does not unlock the bootloader, disable verified boot, or install a custom recovery by itself.

The new XDA release extends the work into the MediaTek boot chain. The public amonet project now has an active mt8696-karat branch, which GitHub lists as updated on August 18. The project is designed for low-level BootROM, preloader, and Little Kernel research on MediaTek-based Amazon devices.

That difference matters. Root access controls a running operating system. A bootloader unlock allows modified boot components to be accepted before Fire OS starts. It can support persistent research tools and a custom recovery, but it also increases the consequences of writing an incorrect image.

What TWRP changes

TWRP is a touch-oriented custom recovery used across many Android devices. It runs separately from the normal operating system and can provide access to maintenance functions when Fire OS cannot start normally.

For these Fire TV models, the important point is not the touch interface. A streaming stick has no built-in display or touchscreen. The value comes from having a recovery environment that can start outside the main Fire OS installation and communicate with a connected computer.

That can give researchers a controlled place to inspect partitions, transfer supported images, collect diagnostic information, and repair some software failures. It also creates a foundation for future custom software work if developers choose to pursue it.

TWRP support should not be interpreted as a promise that every familiar Android recovery feature is complete. Fire OS 8 uses modern verified-boot and dynamic-partition arrangements. Support for backups, encryption, over-the-air updates, and partition mounting can vary by device and recovery build.

An unbrick path is important but not unlimited

The inclusion of unbrick tools addresses one of the largest limitations described when GhostLock appeared. Temporary root alone offered no public recovery route if a researcher damaged critical low-level firmware.

An unbrick workflow can restore a compatible device after certain bootloader or software failures by communicating with it below the normal Fire OS layer. That makes controlled research more practical and can save hardware that would otherwise appear dead.

It is not a universal safety net. Damaged storage, electrical faults, incorrect hardware work, or an unsupported firmware layout can remain unrecoverable. A recovery tool also cannot make an image intended for a different Fire TV model safe to flash.

The developers behind amonet give direct warnings that bootloader modification can permanently brick a device. Owners should treat the new release as experimental device research, not as a routine Fire TV setting or a one-click consumer feature.

Firmware compatibility still matters

The presence of karat and mantra in the release title does not mean every historical and future Fire OS build will behave identically.

Boot-chain tools depend on exact device layouts, signed firmware components, and security behavior that Amazon can change through updates. The XDA thread and its linked project files remain the source of truth for currently tested versions. Compatibility claims from old videos, mirrors, or repackaged downloads can become obsolete quickly.

The release also combines several distinct capabilities. A supported path to initial root access does not automatically prove that every TWRP function works, and a working recovery build does not guarantee that every modified Fire OS image will boot.

Users should be especially wary of third-party packages advertised as a simplified “jailbreak.” Low-level tools have enough access to replace trusted boot components. A modified archive can add malware, steal account data, or leave the device unable to start even when the original open-source project is legitimate.

What this means for ordinary Fire TV owners

The release is not evidence that an untouched Fire TV Stick can be remotely unlocked simply because it is connected to the internet.

These tools are intended for deliberate local use on specific hardware. Owners who do not perform device research should leave ADB debugging disabled, avoid unknown recovery or root packages, and continue installing official Fire OS updates.

Amazon’s published security policy lists these models for software security updates through at least December 31, 2030. Future updates could close an initial access method or alter compatibility with the unlock process. They can also contain unrelated security fixes that matter more to everyday owners.

Anyone experimenting with an unlocked Fire TV should also remember that streaming services may rely on device integrity and content-protection systems. Unlocking the boot chain or modifying system software can affect playback, account security, update behavior, and warranty support even when Fire OS still starts.

Why the release is notable

The second-generation Fire TV Stick 4K family had no public bootloader unlock or custom recovery when it launched in 2023. Recent research moved quickly from a temporary kernel root on karat to a broader boot-chain release covering the karat and mantra device families.

The result is a more durable platform for security research. Developers can now investigate startup behavior and recovery outside the limits of a single temporary root session. Support spans the premium 4K Max and the standard 4K hardware family.

The next questions are whether the recovery builds mature, whether custom operating-system projects emerge, and how Amazon responds in later Fire OS releases. Until those answers are clear, the safest description is also the most accurate one. This is an important research release for experienced developers, not a general recommendation to modify a working streaming device.