yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] SweenWolf:
Magisk Manager has a capability of updating system images, which can and in case of mantis will brick the device.

Magisk Manager can update itself (Magisk Manager) but as this is signed by me the app will not update (in case of unpatched system).

Magisk Manager can update the partitions, when you update Magisk itself from the system then your stick will again be bricked (use TWRP to update).

When you restore the images and do a complete uninstall then Magisk Manager again messes with the images.

So i removed these things so no brick can happen. Even I accidentally bricked my stick one time.
[Fire TV Android Development] dennis148:
works brilliantly! thx!

Anyone tried using the new Google TV Launcher apk as Default launcher?
[Fire TV Android Development] bibikalka:
So if I grab 6.2.8.1 and replace com.amazon.tv.launcher (KFTV launcher), com.amazon.tv.settings.v2 (Amazon Settings), and com.amazon.venezia (Appstore) from 6.2.7.7, would I roughly get this ROM? Can I just copy apks to /system, or is there something else involved as well?
[Fire TV Android Development] Skel40:
Yep pretty much because settings in the new interface is for the new launcher and it'll end up being incompatible with the older interface if that makes sense,vice versa for the rest except the app store. I just prefer the older appstore version for the hide cloud apps feature. Don't know why Amazon removed it in the newer update. You basically can copy the apks to /system with ease however you choose
[Fire TV Android Development] bibikalka:
Thanks!!! Is this 6.2.8.1 worth it then? Pros/cons for switching to it, vs staying on 6.2.7.7 ?
[Fire TV Android Development] wiseguyy:
Hi Guys I need help from the Pros here at XDA, a friend of mine added an APK to my firestick max. "Thunder TV" it is linked to a private server service for like all movies and the latest tv shows and movies all new releases and even an entire 4k library as well. The apk is loaded on my laptop under blu stacks but I don't know where to go to request a login code? I was hoping to spread the word here to see if I can get help in opening an account and pay the monthly fee for the service. Any help would be appreciated.
[Fire TV Android Development] SweenWolf:
Thunder TV - More than 25000 Premium IPTV Channels

Get full access to the entire streaming library along with your favorite live sports, breaking news, can’t-miss events, and current TV shows with Thunder TV.

www.thunderiptv.net
[Fire TV Android Development] MB525:
Just to be sure, these "no efuse" roms only avoid the fuse to burn, they do not work on a stick whose efuse is burnt already, right?

I rooted my stick with stock 6.2.8.1 on it and i doubt it would run the old UI. Or would it with this rom?
[Fire TV Android Development] Sus_i:
Maybe you know it already, but it will work also on sticks with burned efuse / patched BROM :)

Should work fine... :)

Maybe @Skel40 builds a new one for us, based on the latest fireOS?
[Fire TV Android Development] MB525:
Nice to know. Thank you!
[Fire TV Android Development] Skel40:
I'll build one with FireOS 6.2.8.9 when we get patches for it for accessibility and root shell unblocking methods
[Fire TV Android Development] Toothless_NEO:
Would it be possible to patch the OTA update apps like this in an older Rom like 5.2.4.1?
[Fire TV Android Development] door_jam:
@SweenWolf

My 4k Firestick just arrived, with stock 6.2.8.1/3387. So far, I have done below except the last step.

- rooted (w/ Magisk 20.4)

- blocked updates using the adb commands (thanks to Sus_i's reminder)

- installed SweenWolfś Patch-6.2.8.1(No FOTA) file using TWRP

- (to be done) install SweenWolf's TZ Update (TWRP)

After these steps, is it more or less safe in terms of efuse & stopping OTA updates?

Or, would flashing rbox´s prerooted 6.2.8.1_r3 now a safer bet for me?
[Fire TV Android Development] SweenWolf:
If you have used Sus_i's command then yeah the OTA's are blocked, i patched the files already so they should not check for any OTA updates but doing both is cherry on top.

You will have to install the TZ update otherwise Prime and Netflix etc will not work (kamakiri downgrades the TZ thats why TZ needs to be upgraded)

You don't have to install prerooted rom.
[Fire TV Android Development] door_jam:
@SweenWolf Thanks so much.

I have just run your TZ update zip. Did the output "unmount of /system failed; no such volume" mean it failed? Below was the full output.

mantis:/ # twrp install /sdcard/TZUpdate.zip

Installing zip file '/sdcard/TZUpdate.zip'

Unmounting System...

[amonet] Load microloader from recovery...

[amonet] Remove boot patch...

[amonet] OK

TZ Updater

Note: Do not flash any stock rom which has efuse in them

Whose version number is 6.2.8.0 or higher

or you will blow your efuse.

Updating TZ...

Deleting efuse burner

unmount of /system failed; no such volume

script succeeded: result was [][amonet] Install boot patch...

[amonet] OK

[amonet] Install recovery patch...

[amonet] ALREADY_INSTALLED

Done processing script file

mantis:/ #

-----------------------------------------------------------------------------------------------------

I am also curious if efuse will be blown in a rooted 6.2.8.1, blocked OTA, WITHOUT your Patch-6.2.8.1(No FOTA), & then flash your TZ Update (TWRP).

Will the updated TZ img trigger the efuse to be blown (without your patch)?

Does TWRP still prevent this happening (without the Patch)?
[Fire TV Android Development] SweenWolf:
You don't have to worry about

unmount of /system failed; no such volume

script succeeded: result was []

its acually my fault, i forgot to put some lines in the scripts for TWRP.

About efuse burner, there are some files in the system that are responsible for burning the efuse.

Which is called by the boot.img and not by system or TWRP, so while booting if the system detects that there is an upgrade to a critical component and wants to block the user from flashing older version it will blow the fuse. Its not like only Amazon is doing this, others manufacturers like samsung is also doing that.

So if your efuse is not blown then you can use bootrom exploit, if your efuse is blown then the exploit is patched.

We remove the efuse burner related files so that we can unbrick over device using bootrom exploit (which is reliable) while messing with it.

As long as TWRP is there it will prevent flashing those critical partitions (unless defined in the script)

And if those partitions aren't updated then efuse will not be burnt. When you update TZ then the sytem can burn the fuse to prevent you from downgrading.
[Fire TV Android Development] Sus_i:
The efuse for new 4k sticks is burned by default/factory...

and for all the older sticks it's gone too if the installed OS is at 6.2.8.0 or later.

So it doesn't make any sense to keep the 'already burned efuse' from burning... ;)

You can install all stock roms without any hassle :)
[Fire TV Android Development] Toothless_NEO:
Would it be possible to fix the Bar at the top action bar while preserving the TV Style permissions layout? I noticed that after installing it the App permissions layout changed to a touch screen layout.
[Fire TV Android Development] SweenWolf:
Package Installer -> Full screen mode (dark)

fosservices.jar -> mouse mode on all apps

NOTE: fosservices.jar requires 6.2.8.9 to work, installing on older version will cause your device to bootloop.

Package installer can be installed on any version of FireOS.
[Fire TV Android Development] Toothless_NEO:
Thank you this version does have the correct TV Permissions dialog. Unfortunately I can't use the mouse fix since I'm using the 6.2.8.1 rom in this thread, is there any way to fix the mouse in older FireOS versions?

Edit: I decided to create a version of the Apk without full screen but with the same color bar fix and TV permissions menu
[Fire TV Android Development] SweenWolf:
{Mod edit: Quoted post has been deleted}

First thing you have to do is check if your USB storage device is good or not, connect it to your PC, try copying stuff to it.

Backup your data from USB drive to your pc, format the drive and attach it to your stick, then copy something from your internal storage to the usb device.
[Fire TV Android Development] anphabvn:
My fire OS is 6.2.8.1 4061

Can i flash this Rom?

edit.. yes i can thank you!!!
[Fire TV Android Development] Pejay:
Hi

I have installed this Rom with newer interface, everything working ok.

I want to do a factory reset to speed things up.

What is the safest way of doing it? Thank you
[Fire TV Android Development] TimmyP:
Thanks for this. Helped me get out of a nasty bootloop after updating magisk in OS (I forgot, its been years).
[Fire TV Android Development] hasobist:
Hello

Below is the reply received when posed the same question by me in the rooting thread hope it helps.

New sticks should have something with VM201... or later.

Series VM20113xxx sticks arrived with 6.2.8.1, earlier serials should be fine.

You can read few queries posted in the rooting thread you'll find detailed answers.

Hope yours is ain't patched by an update and is vulnerable means can't be rooted.
[Fire TV Android Development] hafren:
Can this be modified to work on ftv2 sloane? I think current rom is 5.2.9.0?
[Fire TV Android Development] Toothless_NEO:
I don't see why it wouldn't be able to, though it might be a bit of work.
[Fire TV Android Development] Skel40:
In the next few weeks I'm resuming Fire TV Stick 4K (mantis) rom development and possibly try and getting Fire OS 6.2.9.5 (NS6295/4448) started with the mods from this forum. I've been quite busy lately with little time for any rom projects and my PC previously broke down for a long time now and got a new one recently so creating roms will soon return for this device and the Lite stick.
[Fire TV Android Development] dk1keith:
sorry if this was answered in thread already but will this work on fire stick 4k stock 6.2.9.4? or is 6.2.9.4 un-rootable?

thanks
[Fire TV Android Development] Skel40:
6.2.9.4 is unrootable since 6.2.8.1. The efuse burned since that version and can confirm that the efuse_check.sh is still there so no luck.

Rom development for the (mantis) will soon happen once again as mentioned. My old 4K burnt out and died
[Fire TV Android Development] dk1keith:
That’s what I thought. Thanks for the reply
[Fire TV Android Development] abuttino1:
Magisk is not installed when I flash this.
[Fire TV Android Development] Meierhansen:
After reading the thread title - and full content - I am still a bit confused. So 6.2.9.5 is in the working, and being tested right now?

Thank you for all the great work!
[Fire TV Android Development] Skel40:
My other 4k I bought weeks ago broke down due to the otg extender cable coming completely off and it fried the board. The 6.2.9.5 is still in development and I need to find a rom compiler for both the (mantis and sheldon) devices if anyone knows? I edited out the main forum of 6.2.9.5 until I have time to resume it and I got good news. The patched roms arent really necessary anymore because I posted a guide showing you how to get all blacklisted apps back system and user apps so you're able to get Launcher Manager back, Accessibility Manager back and the disable-user commands work fully so this alternative would suit best for all the (mantis) and other rooted Fire TV users wanting to have control back!!

Guide: https://xdaforums.com/t/getting-all...s-back-any-fire-os-version-root-only.4579645/
[Fire TV Android Development] unfrozencaveman:
One of my firestick 4k sticks is showing sign of burning out. 3-4 years seems to be these devices lifespan. I'm going to try this rom to see if it fixes the random shutdowns.

Replaced another with the new walmart onn 2023 and it's much faster!

Thank everyone involved for keeping this device relevant.
[Fire TV Android Development] Meierhansen:
@Skel40 Just taped my stick to the OTG and the OTG to the charging USB... how could this happen? Sucks!!!

Me very happy with 6.2.8.1_r3_4054_patched-older-interface right now. Understood that newer firmware versions just make it much harder to use the stick in a proper way. Hope we can stay on this firmware for quite a while before they make it impossible..

I did not really understand the "Getting all blacklisted.." guide you posted above. (It is kind of hard to read due to forced line breaks inserted from forum software.)

So you are you writing XML from ' to ' into /data/system/PackageManagerDenyList to open up things and then run the following commands? Or is this ment to be copied in one piece, so all the commands get echoed into the file? Does this even matter for 6.2.8.1_r3?

@unfrozencaveman thx for the info, guess it is time to plug TV and stick into a switchable power strip to avoid wearing down.
[Fire TV Android Development] Skel40:
Yeah honestly it was the manufacturing of it and it came completely loose. So what I meant by blacklisted is all of the packages they block you from using again i.e (Launcher Manager, Fire OS Update Blocker, etc) from working anymore and yes I'm reading and writing the XML file because the file itself lists all the packages that are denied permissions from overwriting anything which compromises the full customizations of what we pay for, for these devices. It can be copied in one piece on command terminal which I did while running Windows 11. No it doesn't matter for 6.2.8.1. The rom is patched before finding out that we can edit the XML so its not needed to input any of those commands as its already patched.
[Fire TV Android Development] RonRamon:
Greetings!, I got a MANTIS to the 3rd world, with activation error due to blacklist. I was able to activate it with a TWRP backup from burcbuluklu, install many iptv apks and tools, physical control did not work for me (if on a smartphone), nor did amazon apps, and play store registered an account, but did not download. but for the rest it worked for me around 4 hours. After that, laucher stopped and system apps began to stop (DeviceControl for example) and I couldn't activate it again...

The furthest I got is to replace the launcher but it is left without the android configuration app.

If anything can help in the development for this device, I have a dump of the firmware in scatter, theoretically flashable, extracted with hydratool. Thanks for your time
[Fire TV Android Development] fr_jason:
Why this is buried so deep amongst the thread?

It might be the only one worth using, as it is the only one that has actually received a recent update.

I can't wait to try it out!
[Fire TV Android Development] Skel40:
Unfortunately during that time of me making 6.2.9.5 I used the wrong program which I edit the rom and it bricked it by adding the .br extension when (mantis) only has Android 7.1 (Nougat) as the API. Only Android 9.0 I think and higher have this extension so very soon I need to find a 4K again and update the rom. In the meantime its super difficult for me to find a rom program used for extracting
[Fire TV Android Development] Skel40:
Hey I'm about to release the latest 6.2.9.5 right now with the correct tool I used. If anyone is able to grab the latest updates soon I'd appreciate that also. This rom I'm about to release does not contain any patches as I don't have any experience in replacing the files so again follow the guide on the op for the packages and other things back. I also removed the ewriter and efuse_check.sh too. This version contains the older interface as a starter so anyone with a (mantis) report back that it works.
[Fire TV Android Development] Skel40:
6.2.9.5_4448 is now available @fr_jason. Read the op to understand the changes I've made to this rom and the basic information to prevent efuse burning!
[Fire TV Android Development] fr_jason:
Thank you for this @Skel40 !!

I had just succeeded in installing 6.2.8.1_r3_4054_patched.zip with the new interface and will try it out for a little while. I've only put Downloader, NordVPN and Cloudstream for the moment.
[Fire TV Android Development] Skel40:
Here's NS6271/93 OTA patched too for the audio bug fix in Kodi? https://xdaforums.com/attachments/6-2-7-1-2493-zip.5439805/
[Fire TV Android Development] Skel40:
NS6297/4655 is available with the same changelog as the 6.2.9.5/4448 version! Its a drive link found on the OP
[Fire TV Android Development] hasobist:
Hello Skel40!

Thank you loads,it's raining updates.

The 6.2.9.5 debloated works like charm, will update to the latest and update you soon.

Can we have the debloated version of 6.2.9.7 old UI?

If possible much appreciated.

Thank you once again!

Cheers!
[Fire TV Android Development] Skel40:
Actually the debloated one should contain the older interface. If not, I'll update it when available. Will be publishing the TZ soon
[Fire TV Android Development] Skel40:
Added the TZ Update for the 6.2.9.7/4655 firmware. Let me know if you guys need it for other firmwares. I'll post them on the OP here and on my debloated version
[Fire TV Android Development] Skel40:
Does the setup wizard go through as it supposed to and does the Checking for updates in settings show "Never" as last checked? Cool! Its the same rom tweaks only higher OS version so appreciate the responses and report back when you can
[Fire TV Android Development] hasobist:
Yeah does work well with the same setting and apps got an update too......

Never tried clearing data as the stick is all set and works well.

If you wish will give it a try😊

Cheers!
[Fire TV Android Development] feetsonfire:
hi i installed 6.2.8.1_r3_4054_patched and now firetv seems to be dead. Black Screen, short data0 gives error. Noting is working. Any suggestions on how to unbrick.

Error when trying to unbrick

/FireTV# ./boot-recovery.sh
[2022-06-25 10:08:12.871822] Waiting for device
[2022-06-25 10:08:58.202505] Found port = /dev/ttyACM0
[2022-06-25 10:08:58.213193] Handshake
Traceback (most recent call last):
File "/root/FireTV/kamakiri/modules/handshake2.py", line 23, in <module>
handshake2(dev,cmd)
File "/root/FireTV/kamakiri/modules/handshake2.py", line 10, in handshake2
dev.handshake2(cmd)
File "/root/FireTV/kamakiri/modules/common.py", line 133, in handshake2
c = self.dev.read()
File "/usr/local/lib/python3.9/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

In windows devices manager shows MT65xx and after 3 4 seconds disappeas then again appears.

dmesg says

kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 1-3: Product: MT65xx Preloader
kernel: usb 1-3: Manufacturer: MediaTek
kernel: cdc_acm: probe of 1-3:1.0 failed with error -22

Please help
[Fire TV Android Development] hasobist:
Hello!

That's surprising and ain't good and ain't worry.

Do you have a USB-OTG CABLE,this way you can boot the stick into recovery by using a usb mouse and gives 5 seconds to click cancel and boot into recovery as you can't use the exploit to do so unlike Firetv tank .

If you can boot ,try wipe data,cache and Dalvik and try dirty flash the Rom again.

Let me know how it goes.......

Cheers!
[Fire TV Android Development] feetsonfire:
I have otg. but not really i dont see anything on screen. When i power on its basically black screen
[Fire TV Android Development] hasobist:
Hello!

To rule out things, check the usb cable of stick and is the USB-OTG connectect properly and to the power adapter of the stick.

Which OS are you using to unlock the stick,is it a VM linux based or a complete setup?

Try and answer all my questiond,helps me gauge things.

Cheers!
[Fire TV Android Development] Skel40:
FYI community!! Downgrading is not possible with these roms when downgrading from 6.2.9.x to 6.2.7.x, etc. It will hard brick!. Do backups and fully clean flash any downgraded rom available that I made as a fresh install. You can still flash the debloated and OTA patched of the same firmware still. Just no downgrading! Also does anyone want a 6.2.7.7/3033 build with more customizations and a stable older interface rather than the incompatible 6.2.8.x+ mess? 6.2.7.7/3033 is my top favorite firmwares to be on.
[Fire TV Android Development] Skel40:
I have the full system extraction for NS6297/4655 for anyone wanting to see the system. I do want to dedicate my time with this project once again and see what patches can be done for OOBE, etc without needing an account and other modifications. The rest are up to the users and the choices they make with the 4K. Recommendations are always appreciated and as well with feedback. The goal with the (mantis) is to have a clean version of the latest firmware without adding unnecessary packages and other things that compromise its performance all to prolong its longevity. This goes for the system packages as stub(s) apks for more storage and other projects to stay organized.
[Fire TV Android Development] Skel40:
NS6297/4655 Final:

ArcusListener is removed

PackageManagerDenyList has been patched

Both UIs are available with easy rom flashing

Downgrading isn't possible (bricks)
[Fire TV Android Development] Skel40:
NS6297/4655 Script Patch Notes

The / directory is inside the rom with all your roms' system files with added apps for your own customization with Adguard, LM, ATV, FireOSUpdateBlocker, etc found in storage/emulated/0. Your .-system.-- is your stock system for you to revert any modifications and undoings. Your / part after extracting is yours to customize. Modify the system/priv-app folder with any apps to your liking and zip the file for flashing when finished. More info on the OP. The 1.3 gb is responsible for your whole /system/ /vendor extractions for tweaking. Use Zarchiver on Android to extract this .zip rom and begin editing
[Fire TV Android Development] bluedisc:
@Skel40 Would it be possible to have a simplified comparison table for us to know which rom to install like gapps comparison table? It is very confusing with so many packages and you have another post of this as well.
[Fire TV Android Development] Skel40:
I added one. I'll update it as I go through development @bluedisc
[Fire TV Android Development] Skel40:
What do you think of having NS6290 as the default starting rom for the patched and the debloated versions? Will start staying organized as soon as I can and keep that version for now until we get more developments on the newer firmware. Will try and study the audio passthrough fix too? @hasobist