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

[SoftwareRat]

A Fire TV Stick 4K with Fire OS 6.2.9.3 is rootable?

 

[Wolfforlunch]

Hi Folks,

Thanks for your guide and efforts. I would appreciate some help with the following, if anyone has some spare free time to help me out:


-I don’t quite understand how to it’s possible to have the Fire Stick connected to the computer, while also having a mouse connected to it to interact with twrp. I have an OTG cable, with a micro-usb end that connects to the stick, and the other end which splices into two USBs, one for connection to a power source and one data USB that is connected to a USB Hub. (This set-up has been tested and worked before with connecting external HDDs and such on Amazon’s OG OS.)

-When I get to the fastboot stage, I try to use the adb shell to push Magisk to the device, it pushes fine, but when I try to install it, it gives me an error saying no bootable device found. I can see on the TV screen that there is an option to allow overwriting or read-only, but since I can’t have the stick connected to an OTG mouse AND the laptop at the same time, I can’t interact with twrp through TV. if I unplug the stick from the computer, while still connected to the TV, and connect it to an OTG mouse, it boots up and shows a twrp screen with a reboot countdown and when it gets to 0, it just gets stuck there and nothing happens, also OTG mouse does not appear to interact on this screen to press ‘cancel’ on reboot.

Any and all help would be greatly appreciated in advance! Sorry if this question has been answered before, I have spent countless hours searching the forum but my research skills are at newb-lvl at best.

Cheers!

 

[Sus_i]

-When I get to the fastboot stage, I try to use the adb shell to push Magisk to the device, it pushes fine

If 'adb push' works fine, run 'adb shell' then 'twrp install...' or something else... Maybe type 'adb devices' first and if there is the serial, run adb shell

 

[Wolfforlunch]

If 'adb push' works fine, run 'adb shell' then 'twrp install...' or something else... Maybe type 'adb devices' first and if there is the serial, run adb shell

Thanks for your reply, really appreciate it. I have ran ‘adb devices’ and can confirm there is a serial. ‘Adb shell’ runs fine as well, but ‘twrp install’ will give an error saying something like ‘[amonet] remove boot batch
[amonet] failed to remove boot patch…’ followed by multiple other lines saying failed, failed, failed…

 

[Sus_i]

Thanks for your reply, really appreciate it. I have ran ‘adb devices’ and can confirm there is a serial. ‘Adb shell’ runs fine as well, but ‘twrp install’ will give an error saying something like ‘[amonet] remove boot batch
[amonet] failed to remove boot patch…’ followed by multiple other lines saying failed, failed, failed…

Take a picture from the error messages... never saw this kind of error.

 

[emkorial]

Just another FYI for any other unfortunate souls trying to make this work ...

IF you are using the Ethernet adapter to try and skip updates, you cannot connect to ADB when the Fire Stick is plugged in through the Ethernet adapter. Because of course you can't

 

[Wolfforlunch]

Take a picture from the error messages... never saw this kind of error.

Although here I was trying mantis, but it’s the same exact ordeal with Magisk.

 

[emkorial]

So I got the Fire Stick connected. I could not get ADB working when connected through the Ethernet adapter, so I just did direct USB Connection

I rebooted into recovery, wiped data, wiped cache, wiped dalvik, flashed ROM. Rebooted. As promised I got the OOBE for the fire stick.

I paired the remote, connected to my Wifi network, and then it displayed the "checking for updates screen for a moment, and then just skipped it entirely and went right to the login screen. No download progress bar, I didn't kill the connection, it just skipped right over it. Maybe the ROM has that screen disabled?

So I get it all set up, turn on ADB debugging, and connected to ADB. I go into adb shell to delete any cached update file (in case it downloaded one in the background) and disable OTA. But when I enter su, I get permission denied. I checked the applications list, and Magisk is not installed! I thought pre rooted ROM's would have it preinstalled. I flashed the 6.2.6.6 rooted image from https://forum.xda-developers.com/t/...is-prerooted-stock-images-6-2-8-1_r3.3983091/ which specifically says Magisk will always be installed. But it wasn't.

I redid the entire process, and same thing. No Magisk. Some googling led me to this page (https://miguelmota.com/blog/rooting-a-fire-tv-stick-4k/#rooting-with-magisk) which had the Magisk download and instructions on how to flash it with TWRP. I followed those instructions, and was able to get su working. I then cleared the update cache and disabled the OTA updates

One thing I noticed is the Magisk version is different from what it was before. Before I wiped I wrote down the APK versions of everything I had on the stick, previously Magisk was version 7.3.5-de969a9d, now it say version 7.5.1. Does that matter?
So at this point I should have a totally clean 6.2.6.6 stick with nothing on it whatsoever.

 

[Wolfforlunch]

I was able to get the twrp and the OTG mouse working, but I am still unable to install Magisk…it also said something about TWRP theme version is different than stock, or something of the sort.

 

[Sus_i]

I was able to get the twrp and the OTG mouse working, but I am still unable to install Magisk…it also said something about TWRP theme version is different than stock, or something of the sort.

Seems something is messed up with your gpt.
Take a look into this thread and search for 'gpt fix'
You may need to run kamakiri again with this gpt fix...

 

[Wolfforlunch]

Seems something is messed up with your gpt.
Take a look into this thread and search for 'gpt fix'
You may need to run kamakiri again with this gpt fix...

Sir, you have outdone yourself. That did the trick. I’m giving you a virtual hug

 

[Joe Ghost]

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.

 

[savvyyy]

Hi, one of my unrooted sticks ignored the blocked updates and now is on the latest version. Are there any solutions to root it ? Tried the this guide but I get the "RuntimeError: ERROR: Serial protocol mismatch, expected 0001 got 2001".
Thank you

 

[redeyedjedi]

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.

Seriously? A stick you ordered on Amazon, or bought in a store? I'm curious where you found the older stock, I need to buy another since my dog decided to chew my remote. Right now, the sticks are cheaper than the remotes, I just wanna buy a rootable one.

 

[Joe Ghost]

Seriously? A stick you ordered on Amazon, or bought in a store? I'm curious where you found the older stock, I need to buy another since my dog decided to chew my remote. Right now, the sticks are cheaper than the remotes, I just wanna buy a rootable one.

Yep from Amazon like normal. It said copyright 2020 on the box - not sure if that matters.

 

[yellow101]

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.

Hi, How were you able to flash with out OTG? I dont have OTG and im stuck in TWRP.

 

[Joe Ghost]

Hi, How were you able to flash with out OTG? I dont have OTG and im stuck in TWRP.

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

 

[RDYRDY]

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

 

[dallimjp]

I'm having a hell of a time getting the pins sorted. My fire stick looks very similar but the pins aren't even close to the same position.

Can anyone tell me which pins to short?

 

[Sus_i]

I'm having a hell of a time getting the pins sorted. My fire stick looks very similar but the pins aren't even close to the same position.

Can anyone tell me which pins to short?

Just grab one of the capacitors near the edge of the eMMC with tweezers, i.e. bridge both sides.
You can also put a bit of tinfoil between the shield and the part on there.

Anyways, do you know that shorting method gets blocked via update 6281 or later?

There is also a new method which works without to short anything (same method as for sheldon), but this gets also blocked via fireOS 6287 or later.