yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] tito_puente:
As far as I know its not possible to root if the firmware is 6.2.9.0 or higher.

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-tv-stick-4k-mantis.3978459/post-87553965

If I'm wrong please somebody tell me!
[Fire TV Original Android Development] Sus_i:
6.2.8.0 or later patchs the shorting method and 6.2.8.7 or later patchs also the new non-shorting method.
[Fire TV Original Android Development] potatoloco37:
i used this and it worked first try, without shorting

i have a question though, can i interact with twrp through the remote? or do i need an otg cable for a mouse

edit:if i need an otg cable then recommend a good one please
[Fire TV Original Android Development] DrTrax:
Sorry to ask but I holded my FireTV 4k @ Firmware 6.2.9.1 and waiting for someone to tell that rooting or installing TWRP is possible.

Anyone had luck with an unusual method?

I know that MTK have the MTK mode where you can literally flash anything as long as the bootloader isn't bricked and my Windows PC DOES detect the MTK Preloader VCOM but it shut's off immediately. I remember back with my Elephone, you needed to launch a software which IMMEDIATELY holds this state otherwise it goes straight to boot.
[Fire TV Original Android Development] potatoloco37:
i have no idea what firmware my stick was on since it hasnt been on, but apparently it was on the best version.

also i would recommend keeping the firestick off of the internet or not turning it on at all
[Fire TV Original Android Development] llarr:
I just got around to setting up the stick I got on black friday and was also able to set it up without any need to short the pins or otg. My box said 2021 and was UK stock from amazon. I just followed these posts:

Just to add on point 2.) I was able to build the USB drive with Rufus in Windows. I just had to select "write in DD image mode" at the final prompt instead of accepting the default recommendation of "write in ISO image mode".

Minor typo in this part where the switches should come after the backup name. eg: "twrp restore G070VM0984752N1Q SDB"
[Fire TV Original Android Development] nomobytes:
If you manually update to 6294/4339 you may need to flash tee1/tee2 to the latest tz.img, otherwise your device might hang at the initial FireTV logo. So you can extract it and dd it to /dev/block/mmcblk0p2 for tee1 and /dev/block/mmcblk0p3 for tee2.

Kindly confirm.
[Fire TV Original Android Development] nomobytes:
https://d1s31zyz7dcc2d.cloudfront.net/dcac621f9d94c1992980e2c3d5098f16/update-kindle-mantis-NS6294_user_4339_0008356164484.bin
[Fire TV Original Android Development] Joe Baliu:
Hi,

What is the new non-shorting method (I have VM190 with no updates)? Can't find it.

Thanks
[Fire TV Original Android Development] estradz21:
the updated kamakiri lets you do that now i just did on mine and works perfectly with the sheldon stick method here i just did it all in ubuntu
[Fire TV Original Android Development] crazzzzy:
Hi,

I was on 6.2.9.0 with updates disabled, I tried to update the device using openrecoverscript method to 6.2.9.4 and messed it. It is bootlooping at white fireTV logo.

the system is detecting preloader, but nothing happens.

I connect OTG cable and it is not prompting to load TWRP. I tried the latest kamakiri to recover but nothing seems to work.

Is there any way to recover the device.
[Fire TV Original Android Development] Sus_i:
How do you messed it up? Any error messages?

You can try the boot-recovery and the boot-fastboot script, otherwise you would need to re-do the bootrom-step + fastboot-step.
[Fire TV Original Android Development] crazzzzy:
Thanks for replying,

I put wipe /system command in openrecoveryscript,.

I tried all the above step but none is detecting, though in windows device, it detect preloader.
[Fire TV Original Android Development] Sus_i:
If you see preloader in windows device manager, you should see preloader in linux system too.

So you may try the bootrom-step (without a short) first (there is no reason why this shouldn't work) and then the fastboot-step.

If the bootrom-step works and you get problems booting fastboot, you may need to flash a boot.img with the bootrom-step (how-to somewhere in this thread and in the sheldon unbrick thread).
[Fire TV Original Android Development] Joe Baliu:
I have seen in local store today

G0N0VM224 which is newer release than G0N0VM190, but I also saw G4N0VM1221 - is it pre or post G0N0VM190? What does G4/G0 stand for?
[Fire TV Original Android Development] Sus_i:
Old kamakiri v1.x, i.e. root/unlock 'with shorting' gets blocked by:

-serial numbers starting with 190... or by update higher than 6280.

The new root/unlock method without any shorting (kamakiri v2.x) works on all devices, serial doesn't matter, as long as the installed fireOS is not at 6.2.8.7 or above, i.e. needs to be lower.

It's still very easy to get fireTV 4k sticks at a lower OS than 6.2.8.7, if you do the unlock infront of the setup/logon/update thing. Avoid any boot until the thing is rooted ;)
[Fire TV Original Android Development] the_cj:
Also flashed mine, all good, the only thing I cannot get to work is the remote that came with it (worked before flashing the fire stick), if pressing and holding the home button, the PC sees it and can pair with it.

Luckily I have a 1st gen firestick, now that remote works fine, just typically not the new voice/with TV controls one that came with it.

Any suggestions?

For what it's worth, the 1st Gen Remote identifies as Amazon Fire TV Remote, the new one that came with the 4K stick shows as AR, wondering if the custom rom isn't aware of the identifiers of this new remote, guessing though.
[Fire TV Original Android Development] cityhunter_1919_xyz:
Hi.

I was able to install TWRP on my newly acquired unused 4K with fireiso2.0.0+kamakiri-mantis-v2.0.1 without any problem, but on my old 4K (6.2.8.1) I get downgrade failure.

Is it possible that TWRP cannot be installed on this terminal?
[Fire TV Original Android Development] llarr:
Might help if you say what firmware version you are running. If you flashed something too old it may be that it doesn't support the newer remote.
[Fire TV Original Android Development] the_cj:
Yeah might help, meant to add the version to initial post but must have had brain fade.

[Guide] [ROM] (mantis) Fire TV Stick 4K Prerooted Android TV Rom (6.2.7.6) is the currently installed ROM, bar the remote issue, everything works perfectly.

https://xdaforums.com/t/guide-rom-mantis-fire-tv-stick-4k-prerooted-android-tv-rom-6-2-7-6.4208859/

Evidently I missed the post about other users having issues pairing the remote on page 11, seems I am not alone in this, maybe find an alternate ROM,
[Fire TV Original Android Development] llarr:
I thought it would be straight forward if you have an old style remote. I used that image too and paired newer remote. The issue I had was not having an old remote, had to use adb shell commands to put in my wifi details and then use firetv on my app to control the stick and pair the new style remote.

This guide:

https://xdaforums.com/t/guide-rom-m...-android-tv-rom-6-2-7-6.4208859/post-84435183

Might be that you will have to remove the old remote to pair the new one? You can just skip to final paragraph in that post.
[Fire TV Original Android Development] Sus_i:
If you comment out the recheck in the main.py, your second stick will unlock too (y)
[Fire TV Original Android Development] the_cj:
Ignore that, replied to the wrong comment and unsure how to delete my post.
[Fire TV Original Android Development] cityhunter_1919_xyz:
Thank you.

I was able to find a place in a past post to comment out the rechecks, and we had a smooth TWRP install!

72 if rpmb != b"\x00" * 0x100:

73 dev.reboot()

74 raise RuntimeError("downgrade failure, giving up")
[Fire TV Original Android Development] cityhunter_1919_xyz:
I have a 4K with OS 6.2.9.3 because I accidentally deactivated OTA, but the RAM has increased by 0.5GB.(1.3GB -> 1.8GB)

Did this increase when the version was upgraded?

Also, if I manually UPDATE a 4K with TWRP installed to 6.2.9.3(4), is it possible to keep TWRP?
[Fire TV Original Android Development] fluffi444:
I'm quite new in this FireTV business. But I do have Android rooting knowledge from the older days (Sammy ACE 2 and sony z3 compact).

Even if I should kown it better I pluged my FireTV 4K (E9L29Y) in (bought years ago - ever used before) and it self updated during the day to latest 6.2.9.4... Actually I was not planning to "play" with this device but some spare time and the lack of full NTFS support brought back some rooting whishes... :-)

I'm I right that my device is now not rootable at all anymore?
[Fire TV Original Android Development] Sus_i:
Yes, sadly not rootable.
[Fire TV Original Android Development] fluffi444:
Many thanks for your fast reply. Unfortunately expected - But saves me from another new "project" :cool:

I will live with the simple NTFS solution via ES File Explorer - Even if its not so handy.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
L Guys, I've tried short-circuiting the Fire TV Stick 4K with a paperclip, but I keep getting SERIAL PROTOCOL MISSMATCH, help!!!! has the device been made unrootable? That is the Serial number: G4N0VM12223207PR
[Fire TV Original Android Development] ~iceweasel:
I'm hoping for some feedback from those who know answers to stupid questions... 107 pages of questions and I'm got as far as I could before asking for thoughts.

I've tried to follow the guide here with my (old, 2019) 4K stick but have failed to get bootrom-step to detect the device. I'm grounding the cap indicates as control because my shield base covers the data pad and clock cap. I'm questioning if I'm really grounding cmd, and haven't grabbed the scope to confirm.

I'm struggling to figure out how to ID the installed firmware version without going through the setup. Is it possible to check the firmware version before setting up? My dsn starts G070VM1292 so I've been assuming it's old enough... bad assumption?

I'm looking at the guide for the fire stick 3 / lite because I have one of those too but since the 4k is open I'm wanting to finish if possible but since I don't have a running ubuntu system at home, I'm holding off until I can grab mine from work since I know how that's configured and ready to go.
[Fire TV Original Android Development] Sus_i:
Try the latest kamakiri for mantis and use the script 'without a short' like described here:

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)

Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...

xdaforums.com

@~iceweasel You may try the same...
[Fire TV Original Android Development] Anonym Unbekabnter 2:
ca Praying Mantis or Sheldon? I have Fire TV Stick 4K mantis
[Fire TV Original Android Development] Sus_i:
Follow the guide for sheldon and use the kamakiri 2.1 scripts for Fire TV Stick 4K.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
Okay
[Fire TV Original Android Development] Anonym Unbekabnter 2:
Working this Guide with fireiso?
[Fire TV Original Android Development] Sus_i:
Yes, if you use the fireISO just start with the bootrom-step.

Also the FireOS on the Stick needs to be lower than 6.2.8.7 in order to work.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
So all I have to do is plug the Fire TV Stick into the PC while bootroom-step.sh is running
[Fire TV Original Android Development] ~iceweasel:
Thanks will give that a try, I didn't notice the sheldon script when looking last night guessing you're saying to use the sheldon scripts?

I followed the direction over there and posted a response (similar result with not noticing the device even though Ubuntu did mount the AFTMM device.) During that I tried a OTG cable and found the device does get discovered, but the script fails. I then tried to run this mantis script same results.

So I came back here, using FireOS.iso 2.0 and OTG cable, and it's currently flashing! It looks like I've got the device configured to boot into TWRP!!!

Thanks for your help!! I'm heading off to learn how to correctly get the latest firmware installed from here:

https://xdaforums.com/t/fire-tv-stick-4k-mantis-prerooted-stock-images-6-2-8-1_r3.3983091/
[Fire TV Original Android Development] Anonym Unbekabnter 2:
http://

How exactly does it work? Should I try the Sheldon script and then the Mantis script, will this work on new Fire TV Stick 4K's?
[Fire TV Original Android Development] ~iceweasel:
I'm no expert and really don't know much. I also don't know about your "new" 4k, mine was 3 years old and had never been powered before, so it was in good shape for changes. But what I now understand, is using the Sheldon topic for creating a suitable Ubuntu environment. When Ubuntu is configured correctly, instead of using the sheldon.zip scripts use the mantis.zip scripts from the OP here.

My big "fix" for me was using the OTG cable instead of a normal USB cable. Normal USB cable would identify and "mount" the device in Ubuntu, but the script didn't identify the stick.

So, OTG cable was my key to getting TWRP installed and running. But I've got work to do still because when launched TWRP only gives the option to reboot which isn't what I'm used to with the "boot normal" and "boot recovery" options. I think I nedd to figure out what else I need to install.
[Fire TV Original Android Development] ~iceweasel:
I guess I have another noob question, given I got the "Your device will now reboot into TWRP" I assume TWRP is good to go. Since TWRP only allows me to reboot or cancel I'm a little confused but suspect that may be different once I install a patches OS.

At this point, am I safe to connect the stick, enable wifi and ADB? I'm concerned about an auto update, but did deregister my device. I'm thinking once ADB is active I can reboot into recovery, and because magisk is already installed I can then use adb and twrp to install the latest patched OS. Did I miss anything?

I didn't configure wifi yet, but did add a mouse and cancelled the TWRP reboot and was taken to a screen stating "unmodified system partition" asking if I want to keep the partition read only. I think I should keep it RO. I think I'm off the standard path...
[Fire TV Original Android Development] Anonym Unbekabnter 2:
Aber wie But how to do that? Should I download the Sheldon ZIP and then paste the scripts from the 4K Stick into the Sheldon folder?
[Fire TV Original Android Development] ~iceweasel:
I had the same questions, but after rereading the steps (and feedback) decided the sheldon thread is just for setting up a ubuntu OS for the process instead of using the FireISO OS. But that's what I understood was correct.

The files in the sheldon package are for specific devices, and the mantis for other devices. If I ran the sheldon script I expect it would error out with "wrong device detected" because my device type is AKPGW064GI9HE.

The mantis script did report "Detected mantis (AKPGW064GI9HE)"

Sheldon supports these devices:

device_type_id = dev.idme_read(b"device_type_id").rstrip(b"\x00").decode("utf-8")
log("Check device_type_id")
if device_type_id == "A31DTMEEVDDOIV":
log("Detected sheldon (" + device_type_id + ")")
elif device_type_id == "A265XOI9586NML":
log("Detected sheldonp (" + device_type_id + ")")
else:
log("Wrong device detected: " + device_type_id)
exit(1)

The mantis supports this device:

device_type_id = dev.idme_read(b"device_type_id").rstrip(b"\x00").decode("utf-8")
log("Check device_type_id")
if device_type_id == "AKPGW064GI9HE":
log("Detected mantis (" + device_type_id + ")")
else:
log("Wrong device detected: " + device_type_id)
exit(1)

The zip file contain the files needed to process specific devices, so if you have a 4K stick I'd unzip the mantis zip and run those scripts from the kamakiri-mantis-v2.0.01/kamakiri folder.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
Hm okay
[Fire TV Original Android Development] Anonym Unbekabnter 2:
My Short try. Always the Message SERIAL PROTOKOLL MISSMATCH
[Fire TV Original Android Development] ~iceweasel:
Do you know SMD ceramic capacitors? If you do you may ignore this, if not it could help.

You basically did exactly as I did, but it's tough for me to tell if you're really doing it correctly. The ends of the capacitor are the terminals and you want to be sure to make contact with the end of the capacitor, not the brown ceramic body of the cap. If you're making contact with the right side in this picture, you did exactly what I did, if not make sure you make contact because you're trying to pull that line to ground so the signals sent on that line don't make it to their destination.
[Fire TV Original Android Development] cityhunter_1919_xyz:
If it is simply below fire os 6.2.8.7, there is no need to open the case and short-circuit it. Serial number is also not relevant nowadays. If you use fireiso2.0.0 and kamakiri-mantis-v2.0.1, it works fine.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
Firmware: 6.2.9.4

Ich verwende Fireiso 2.0.0 und Kakamari Mantis 2.0.1

Aber es funktioniert nicht, anscheinend habe ich wirklich eine gepatchte Version
[Fire TV Original Android Development] ~iceweasel:
I'm getting myself in trouble trying things out without really knowing what I'm doing. I have TWRP booting and that was booting to the stock image but haven't enabled ADB since this has never been started before and would need wifi before I can get to menus.

I was playing with connecting to wifi on a heavily protected connection and allow the device ping amazon, but then it looks for updates and I blocked that. So the device then times out and wants to try again. Now I think I'm stuck in the white screen reboot loop... any suggestions?

I guess what I really should be asking is, if I connect to wifi and the update gets detected and/or installed. Is there any reason why I wouldn't be able to install the rooted stock 6.2.8.1_r3 from rbox?
[Fire TV Original Android Development] Anonym Unbekabnter 2:
The right end side of the capacitor right?
[Fire TV Original Android Development] ~iceweasel:
in your picture, correct that's what I did and I was able to get it to work. If you don't make contact with the solder on the end it won't do what it needs to do.
[Fire TV Original Android Development] cityhunter_1919_xyz:
Unfortunately, it is not possible to install TWRP if Firmware: 6.2.9.4 is used. (< 6.2.8.7)

I have recently purchased three unused 4K units and all have worked well. I already had a 4K (os6.2.8.1) and was able to install TWRP thanks to Sus_i.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
The Fire TV Stick updated itself. So has it been patched? I think I got it with firmware 6.2.8.1
[Fire TV Original Android Development] Anonym Unbekabnter 2:
I still have a picture where it was new, it's hard to read, but yes, I can read 6.2.8.1
[Fire TV Original Android Development] cityhunter_1919_xyz:
firmware 6.2.8.1

If you get RuntimeError: downgrade failure,giving up, try the following

kamakiri > modules > main.py

Comment out the following line

72 if rpmb != b"\x00" * 0x100:

73 dev.reboot()

74 raise RuntimeError("downgrade failure, giving up")

↓

#if rpmb != b"\x00" * 0x100:

#dev.reboot()

#raise RuntimeError("downgrade failure, giving up")
[Fire TV Original Android Development] Anonym Unbekabnter 2:
now he unfortunately has firmware 6.9.2.4
[Fire TV Original Android Development] ~iceweasel:
@Sus_i

I know this is dynamic in nature, but following another guide at one point you suggested upgrading before applying TWRP then suggested not doing so. I've currently got TWRP installed on the stick which had never previously been powered. TWRP shows it's still got stock firmware and I'd like to put rbox's r3 rooted on the box but think I need to connect to wiri which will pull an update before I can enable ADB to apply r3 image. Is my next step to connect to wifi and take their update? I fear missing something that will undo my TWRP install or blow an fuse. Thansk
[Fire TV Original Android Development] Sus_i:
Yes, back then there wasn't any problem, update infront of the unlock was fine.

Nowadays amaz. is trying to fix every unlock method via updates, so nowadays every update on a 'locked stock device' will fix/patch all known exploits, no way to unlock left.

Check which OS is running on your stick.

If it's 6.27.7 or earlier, then you would need to flash 6.2.8.1r2 first, then 6.2.8.1r3.

If you've got already a higher OS than 6.2.8.1 on your stick, you don't need to flash the old 6.2.8.1 from rbox.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
and 6.2.9.4 is fully patched?
[Fire TV Original Android Development] Sus_i:
Yes.
[Fire TV Original Android Development] Anonym Unbekabnter 2:
Hm pity, AS I SAID IT WAS UPDATED AUTOMATICALLY XD
[Fire TV Original Android Development] ~iceweasel:
the stick is still basically "new" (never powered/connected before yesterday) so it has whatever was from the factory in 2019. Is allowing Amazon to push the latest safe to do? Thanks.

It's currently downloading the latest from azm, but throttled to about 1k/s so I'm buying time just in case this needs to be aborted. =)
[Fire TV Original Android Development] Anonym Unbekabnter 2:
Yes, I think so too
[Fire TV Original Android Development] Sus_i:
If you care about the shorting method, for later unbricking or re-do kamakiri, then only use rbox prerooted roms. Disable updates.
[Fire TV Original Android Development] ~iceweasel:
Hmmm, so this is my concern and confusion. I think I want/need to keep access to TWRP.

I used shorting method to install TWRP and that's where I'm at, haven't yet connected to wifi. Because I've never connected before, I've not had access to the menus so ADB is disabled. Do I have another option for installing the prerooted r2 (as you said) then r3? I thought I could do that with TWRP, but have never done so in this virgin state.

I guess I should also ask, do you think I should go further back and get the 6.2.6.6_r1 image because of the license erro fixed then?
[Fire TV Original Android Development] ~iceweasel:
I guess going back to the prerooted 6.2.6.6 is no longer an option because the link to mediafire is broken...
[Fire TV Original Android Development] Sus_i:
You don't need to flash a rom at all.

I would install magisk, then boot the stick. Setup the wifi + account, skip update with that:

How to Skip Software Updates during Initial Setup or Factory Reset on a Fire TV, Firestick, or Fire TV Cube

Since the latest software update for Fire TV devices is blocking the ability to use custom launchers, you may want to avoid updating a new or factory reset Fire TV.

www.aftvnews.com

Enable adb, grant su access for the shell, disable updates:

adb shell
su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
exit
exit

Then take a look what OS is installed.
[Fire TV Original Android Development] ~iceweasel:
Thanks, very helpful!!

But I don't understand how to install magisk without first having adb access. Should I just do the wifi/register enable adb then install magisk to then get su access? I think that may work given I can boot to TWRP... or so I hope

I can follow the guide on ftvnews, I was actually trying that on my own but forgot the double button back+menu trick.

The one thing that is confusing is that requires registering, I had unregistered as noted in the newbie guide. No problem with registering after skating around the update?