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

[tito_puente]

Hello guys, I purchased my firestick 4k in the August of 2019 and have been updating it ever since, I rooted my phone with magisk and so i thought why can't i do the same with my firestick and that's how i found this thread. I'm on the latest update and hence i want to know if Amazon blocked this method, below I've attached the details of my firesticks software, i want to know if this process works with fireos 6.2.9.3 has it been patched @Sus_i , @Joe Ghost ?
Thank you,
RDY

As far as I know its not possible to root if the firmware is 6.2.9.0 or higher.

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

NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...

forum.xda-developers.com

If I'm wrong please somebody tell me!

 

[Sus_i]

As far as I know its not possible to root if the firmware is 6.2.9.0 or higher.

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

NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...

forum.xda-developers.com

If I'm wrong please somebody tell me!

6.2.8.0 or later patchs the shorting method and 6.2.8.7 or later patchs also the new non-shorting method.

 

[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

 

[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.

 

[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

 

[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:

I did this successfully yesterday. Here are a few solutions I found:

1. I didn't need to short the pins; the script unlocked the bootloader just fine on its own. This Fire TV Stick 4K was purchased last week.
2. I could not build the live USB drive with Rufus in Windows. When I booted from the drive it gave some error about "IO charset ascii not found". FAT32 and NTFS were the only filesystem options in Rufus and neither of them worked. So I made the drive in Linux and it worked perfectly and took like 2 minutes. Imaging a USB drive in Linux is ridiculously easy, you literally copy the ISO file to the USB device with one command.
3. You don't need an OTG cable. I got this ROM on the Fire Stick by using "adb push" to copy the G070VM0984752N1Q folder to /sdcard/TWRP/BACKUPS/, and then doing "twrp restore" from that backups directory in the adb shell. Then I used this fantastic guide to control the Fire Stick through ADB in order to pair the remote.

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".

I had the Fire Stick plugged into the computer and used ADB for everything. First copy the files with "adb push". Type "adb help" to see the exact usage - in this case it's "adb push -p <local> <remote>" where <local> and <remote> are the G070VM0984752N1Q and /sdcard/TWRP/BACKUPS directories, respectively. It should show you the progress of the files being copied. Then use "adb shell" to gain access to the Fire Stick's terminal, and then within that, "cd" to the BACKUPS directory and run "twrp restore SDB G070VM0984752N1Q". "twrp" command usage is here. Hope that helps

Minor typo in this part where the switches should come after the backup name. eg: "twrp restore G070VM0984752N1Q SDB"

 

[nomobytes]

Important information

Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)

TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
<snip>

Contributors
k4y0z, xyz`
Source Code: https://github.com/amonet-kamakiri/

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.

 

[nomobytes]

https://d1s31zyz7dcc2d.cloudfront.net/dcac621f9d94c1992980e2c3d5098f16/update-kindle-mantis-NS6294_user_4339_0008356164484.bin

 

[Joe Baliu]

6.2.8.0 or later patchs the shorting method and 6.2.8.7 or later patchs also the new non-shorting method.

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

 

[estradz21]

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

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

 

[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.

 

[Sus_i]

Is there any way to recover the device.

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.

 

[crazzzzy]

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.

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.

 

[Sus_i]

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.

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).

 

[Joe Baliu]

While searching for a solution, I read forums in several languages. Russians say that most likely players with serial numbers starting with 190 (after VM) have problems. G070VM190. VM170, VM180 and all previous "series" reported still can be rooted!

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?

 

[Sus_i]

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?

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

 

[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.

 

[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?

 

[llarr]

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.

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.

 

[the_cj]

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.

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.

[Guide] [ROM] (mantis) Fire TV Stick 4K Prerooted Android TV Rom (6.2.7.6)

After so many trial and error, I've finally saved the latest version of my system with TWRP backup. I want to share this personal setup with you guys since it required a lot of work to debloat, install add-ons, apps, kernels and tweaks. This is a...

forum.xda-developers.com

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,