[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)

[Joe Baliu]

Hi,
I have succesfully installed TWRP 3.6.1_9.0 on my Fire TV 4k with 6.2.7.3 os version.
I have also succesfully installed Magisk 25.2. Cache/dalvik was cleaned.
But when I try to run 'su' or 'pm' I get "Not found". I tried 'su' and 'pm' via adb shell and twrp terminal with same results.
Initially I installed Magisk via adb, then retried via twrp UI - but in both cases 'su' and 'pm' are not found.
What could be the issue? Thanks in advance

P.S. when I try 'pm' after mounting system I get 'library "ld-android.so" not found'.

 

[Finnzz]

But when I try to run 'su' or 'pm' I get "Not found". I tried 'su' and 'pm' via adb shell and twrp terminal with same results.

You are in TWRP, and already have root. Package Manager isn't available until you boot FireOS.

 

[redeyedjedi]

I got a 4k stick at 6.2.8.1 and I have gone through the process and rooted it.
What is the proper procedure to get it updated to 6.2.9.4?? I assume the DRM is out of date and Netflix and prime show a black screen. It also seems this root blocks updates, as it just boots to twrp and the update never happens. I am perfectly ok with manually updating but can't seem to find the bins anywhere. Any help here would be appreciated.

 

[Sus_i]

What is the proper procedure to get it updated to 6.2.9.4?? I assume the DRM is out of date and Netflix and prime show a black screen. It also seems this root blocks updates, as it just boots to twrp and the update never happens.

As you've got a stick with 6281 (already burned efuse = shorting method gone), there isn't a special procedure required, you would just need to flash the rom you like...

If you go to 6.2.9.4 you may flash the TZ too (if there are DRM playback issues or black screens).
Easiest way to do this is take/extract the TZ image from 6.2.9.4 rom and overwrite the TZ image from kamakiri 2.1 folder. Then re-do the bootrom/fastboot-step.

I am perfectly ok with manually updating but can't seem to find the bins anywhere. Any help here would be appreciated.

Fire TV Stick 4K Firmware and apps. Official Cloud Front direct links

Fire TV Stick 4K Stock Firmware files, cloudfront.net download links. Firmware (Once downloaded you need to change file name from .bin to .zip) Mirror and builtin app updates: https://gist.github.com/JulyIghor/d3d3dd460527a1d2b5b67954160d4abf...

forum.xda-developers.com

 

[redeyedjedi]

As you've got a stick with 6281 (already burned efuse = shorting method gone), there isn't a special procedure required, you would just need to flash the rom you like...

If you go to 6.2.9.4 you may flash the TZ too (if there are DRM playback issues or black screens).
Easiest way to do this is take/extract the TZ image from 6.2.9.4 rom and overwrite the TZ image from kamakiri 2.1 folder. Then re-do the bootrom/fastboot-step.

Fire TV Stick 4K Firmware and apps. Official Cloud Front direct links

Fire TV Stick 4K Stock Firmware files, cloudfront.net download links. Firmware (Once downloaded you need to change file name from .bin to .zip) Mirror and builtin app updates: https://gist.github.com/JulyIghor/d3d3dd460527a1d2b5b67954160d4abf...

forum.xda-developers.com

Done and done. Thanks, this is exactly what I was looking for. Now, is there a semi up to date list of what system apps can be deleted? Time to go looking.

 

[Sus_i]

Done and done. Thanks, this is exactly what I was looking for. Now, is there a semi up to date list of what system apps can be deleted? Time to go looking.

Maybe use adb shell pm disable instead, so it's easy to enable again if something goes wrong

 

[Mfizz]

Hi all, I'm hopeful you can help me. Back in October my firestick out by 5 days warranty got stuck on boot animation with fire TV logo.

My primary goal is to get it working again and root is a bonus. I'm not sure what os version it was on. I had adb debugging enabled, but didn't connect it to any pc.

Will this method help me recover my stick? I have already tried all the official methods with remote, otg cable etc.

 

[ahsad]

?

 

[ahsad]

?

 

[ahsad]

?

 

[[email protected]]

You guys rock! Unlocked without issues. Rooted with Magisk 19.3.
Note: in my case, correct pin was left side of 3rd smd component from right.
Heatsink can be easely detached with flat screwdriver (just rotate it in points as on the picture

You guys rock! Unlocked without issues. Rooted with Magisk 19.3.
Note: in my case, correct pin was left side of 3rd smd component from right.
Heatsink can be easely detached with flat screwdriver (just rotate it in points as on the picture)

Here's a YouTube vid which shows it all. Enjoy

 

[[email protected]]

It's not that I get bored waiting for the script to run, I just don't know how long to wait for! Can anybody tell me please, exactly which point is supposed to be shorted and to where? Should the script run and inform me immediately that I insert the usb plug into the PC? I wait for seemingly ages and then make ^C to terminate. This what I get. Has the script run or are my terminals still not shorted? Help please!

 

[fluffi444]

It's not that I get bored waiting for the script to run, I just don't know how long to wait for! Can anybody tell me please, exactly which point is supposed to be shorted and to where? Should the script run and inform me immediately that I insert the usb plug into the PC? I wait for seemingly ages and then make ^C to terminate. This what I get. Has the script run or are my terminals still not shorted? Help please!

How to short is documented well in thread...
If it shorts correctly AND your stick can be rooted short (lower FW than 6.2.8.7) then the script starts immediately withhin milliseconds - after plugging the USB.

With my first stick (updated by mistake to 6.2.9.4 right after first boot) I waited 30 min with running bootrom-step.sh.
Untill I start reading and learing much and learned that 6.2.9.4 is not rootable at all!
Sold this to a fried whom do not care about rooting att all - I explained him...
Bought a second one (old modell from 2018 but brand new - shipped with 6.2.3.1 - VM058) and this was rootable via short right away. Here the short was mandatory!

In addition a bought now a third one from private and unopend (for my sister) build 2021 (shipped with 6.2.8.1 - VM101) - This was rootable right away without any short!

So all in all its about build date, serial number (VM***) and most importand FireOS-Version. - Check this all.

There are some ways to boot the stick without initial forced update to find out what FireOS is installed.

 

[[email protected]]

How to short is documented well in thread...
If it shorts correctly AND your stick can be short (lower FW than 6.2.8.7) then the script starts immediately withhin milliseconds - after plugging the USB.

With my first stick (updated by mistake to 6.2.9.4 right after first boot) I waited 30 min with running bootrom-step.sh.
Untill I start reading and learing much and learned that 6.2.9.4 is not rootable at all!
Sold this to a fried whom do not care about rooting att all - I explained him...
Bought a second one (old modell from 2018 but brand new - shipped with 6.2.3.1 - VM058) and this was rootable via short right away. Here the short was mandatory!

In addition a bought now a third one from private and unopend (for my sister) build 2021 (shipped with 6.2.8.1 - VM101) - This was rootable right away without any short!

So all in all its about build date, serial number (VM***) and most importand FireOS-Version. - Check this all.

There are some ways to boot the stick without initial forced update to find out what FireOS is installed.

Thanks for that info. Mine is, of course 6.2.8.9! Is there anyway of downgrading? I suppose not.

 

[fluffi444]

Thanks for that info. Mine is, of course 6.2.8.9! Is there anyway of downgrading? I suppose not.

No - sorry - As far as I know there is no way to root or to downgrade with 6.2.8.9.

 

[Skel40]

Depends on you, if you like the old fireOS launcher use 6.2.7.7 (renamed to zip):

https://d1s31zyz7dcc2d.cloudfront.net/68d33a27765a01a75f9ccc8d11a52791/update-kindle-mantis-NS6277_user_3033_0004597733764.bin

and if you like the new launcher UI then flash rbox 6.2.8.1r2.

Don't wipe anything, rom flash is enough.

If you want to flash a more recent fireOS at some point, make sure you think twice, i.e. keep your efuse from burning: @SweenWolf uploaded a patch somewhere which deletes the efuse burn script and @Pretoriano80 does also similar patches including his awesome custom kernel:

[KERNEL][FireTV Stick 4K] Custom Kernel For AFTV 4k - 6.2.9.4

Warning !!! Use this kernel on your own risk !!! I can't be held responsible for any kind of damage or data loss !!! Features: SDCARDFS exFAT and F2FS support Wireguard Advanced TCP options CIFS and NFS support Insecure ADB v1...

forum.xda-developers.com

The roms I have are also safe to flash as well. I have downgradable roms without the efuse

 

[Skel40]

I've tried to unlock my 4K again with the 2.0.1 zip @k4y0z provided and my OTG couldn't recognize my mouse in recovery mode. I used the plugin method without pin pointing so can someone help me out?

Edit: ADB doesn't work at all it doesn't detect it after ./fastboot-step.sh boots into TWRP. The hacked fastboot is fine it shows up. Only adb isn't working. I don't know what's going on. The unlock is successful, and right when I try to enter adb device's on terminal on fireiso, nothing.
I managed to fix the OTG issue after flashing 1.2 of the kamakiri exploit. It seems to be recovery related

 

[cityhunter_1919_xyz]

Hi everyone. Need some help. Got a mantis for free. Amazon told me not to return it. I can't register the stick. I ran the scripts and TWRP installed and working. Challenge is I don't have OTG cable. Long story short. Download this thread rom. Instead of TWRP install which I don't have keybd. I ended up adb sideload. Does that means this won't patch the stick like TWRP would?

The boot scripts and sideload all says successful. When the stick ask to login it give me 2 options. Online amazon.com/code or enter my login on the stick.

If I login on stick, it flat out saying something is wrong. If I login from online code, the site says successful but the stick didn't do a thing.

I also tried a ROM here says no efuse. Same behavior. Since I can't pass login. I can't tell which version I am on. All I know is the script worked and it is a VM242 serial. How do I know efuse is burnt or not? I only wish I have OTG do I can try TWRP.

Edit: just found out I can do "trwp" from adb shell, but still after twrp install and wipes, still thou shall not pass registration. Are there LineageOS, AndroidTV, or Ubuntu, so I can repurpose and not e-waste? Retro/Emulator would be so cool.

Thanks

I had the same symptoms with an unopened 4K obtained from a private sale.
I contacted Amazon and they replied that it was because the serial number of the device had been erased due to a return or some other reason.
I was able to get to the home screen by restoring the data I had backed up on my other 4K, but I can't use the store, so some apps that depend on Amazon are not available.

Some apps that rely on Amazon can be avoided by installing from AptoideTV.

 

[aleet]

I had the same symptoms with an unopened 4K obtained from a private sale.
I contacted Amazon and they replied that it was because the serial number of the device had been erased due to a return or some other reason.
I was able to get to the home screen by restoring the data I had backed up on my other 4K, but I can't use the store, so some apps that depend on Amazon are not available.

Some apps that rely on Amazon can be avoided by installing from AptoideTV.

Oh cool. You mean from TWRP restore data partition? Would you know where I can get a copy? I actually do not want Amazon store since we can side load.

 

[DevanteWeary]

Hey guys,

So I can't even boot the FIREISO200 image.


I've tried three different USB drives with Rufus using the following settings.

• Partition scheme: MBR
• Target system: BIOS or UEFI
• Quick format: off
• File system: FAT32

Once I boot the drive, I'm met with this each time:

I'm at a loss, guys.
What should I do?


Thanks for any advice!