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

[slack5]

My fire stick 4k is not stuck in black screen. It boots up but it never passes the fire tv animated logo.
I never altered the 4k firmware,IMagisk is not available.
I believe I already tried fastboot factory reset but if I realy did it didn't help I will definately try it when I get home (just to makse sure i tried it).

Is there someone who could generate Fire Stick 4k Scatter file?
I need it because I would try to do some tests in Spflash read contents from my stick.

 

[slack5]

You should try to Factory reset by fastboot command.

There is no fastboot factory reset command.
I did try fastboot -w but it didn't help.
I believe I will have to flash sysyem partition in order to make my Fire Stick 4k work again.
Ufortunately I am not able to find appropriate system.img file that is meant to be flashed via fastboot or Spflash.

 

[stevebgfra]

Hello,

My new firestick is on 6.2.8.9, and the kamikir ISO is stuck on waiting for boot downloader when running `./bootrom-step.sh`, with the aluminium fold in place. (never rooted before).

Should I conclude I won't be able to root?

(just wanted to support my xbox 360 wired controller)

thx

 

[anphabvn]

Hello,

My new firestick is on 6.2.8.9, and the kamikir ISO is stuck on waiting for boot downloader when running `./bootrom-step.sh`, with the aluminium fold in place. (never rooted before).

Should I conclude I won't be able to root?

(just wanted to support my xbox 360 wired controller)

thx

Yes. you cant root now

 

[Bertonumber1]

Hi guys,

Major problems, three mantis and a lite device offline.
Tried reflashing firmware with magisk and the device won't pass setup at all. Can pair the remotes then get a message saying unauthorised and then I get pinged back to pairing remote again. Thought maybe disabling OObe but obviously can't get to adb etc.

Wondering if some new root/bootloader detection maybe prevalent with this new launcher telemetry / firmware. Has anyone else found any problems ie no WiFi, unable to pass setup stage etcetera.
Would see the point of possible user error with one device.... but four of them exactly same time?

Any help appreciated.

Kind regards

 

[anphabvn]

Hi guys,

Major problems, three mantis and a lite device offline.
Tried reflashing firmware with magisk and the device won't pass setup at all. Can pair the remotes then get a message saying unauthorised and then I get pinged back to pairing remote again. Thought maybe disabling OObe but obviously can't get to adb etc.

Wondering if some new root/bootloader detection maybe prevalent with this new launcher telemetry / firmware. Has anyone else found any problems ie no WiFi, unable to pass setup stage etcetera.
Would see the point of possible user error with one device.... but four of them exactly same time?

Any help appreciated.

Kind regards

twrp factory reset?

 

[Sus_i]

I believe I have tried all possible ways mentioned in this thread in order to unlock the Bootloader an install TWRP and revive the system by flashing. Unfortunately nothing seems to work.

I don't know if you tried the bootrom-step from kamakiri 2.x (run the script and then connect the stick without a short, see post #1953 for details), but in case this won't work for you, spflashtool won't work too.

 

[Bertonumber1]

twrp factory reset?

Twrp Format data, then newest firmware 6.2.8.9
followed by Magisk. Sends oobe into a loop. Like I said above. Pair remote OK, then when connect WiFi it let's you enter WiFi password and then says " loading...." then "unauthorised"
Before sending you back to remote pairing.

It's new to me.. I only updated to newest firmwares as some apps stopped working on the older firmware (6.2.7.1 the best imo).

Regards

 

[anphabvn]

Twrp Format data, then newest firmware 6.2.8.9
followed by Magisk. Sends oobe into a loop. Like I said above. Pair remote OK, then when connect WiFi it let's you enter WiFi password and then says " loading...." then "unauthorised"
Before sending you back to remote pairing.

It's new to me.. I only updated to newest firmwares as some apps stopped working on the older firmware (6.2.7.1 the best imo).

Regards

Use filemanger of twrp delete OObe

 

[anphabvn]

Twrp Format data, then newest firmware 6.2.8.9
followed by Magisk. Sends oobe into a loop. Like I said above. Pair remote OK, then when connect WiFi it let's you enter WiFi password and then says " loading...." then "unauthorised"
Before sending you back to remote pairing.

It's new to me.. I only updated to newest firmwares as some apps stopped working on the older firmware (6.2.7.1 the best imo).

Regards

" loading...." then "unauthorised"
Wrong wifi pass or your device is blacklisted

 

[anphabvn]

If you have Mantis 4k Stick and cant use stock rom try this test rom

https://xdaforums.com/t/rom-work-in...-1-for-fire-tv-stick-4k.4083703/post-87079683

 

[totbl]

Could someone check something for me please? I'll attach a photo and could you tell me if the part I have circled is exposed like mine is? Because I had a small fine piece of steel that like an idiot I mislaid and I'm wondering could its absence be the cause of my bluetooth issues? Could be barking up the wrong tree altogether as I'm out of my comfort zone here.

A few notes on general unbricking as well as tips specific to bootloops, potentially "blacklisted" devices and "unable to update" and similar errors. (Also, using the device without logging in)

1. The latest release of kamakiri includes two undocumented utilities that allow you to boot into the recovery or fastboot when you short the contacts shown in the main post. already have the kamakiri microloader installed. (boot-recovery.sh and boot-fastboot.sh)
2. You can circumvent the entire OOBE (Out Of the Box Experience) and even skip the Amazon account login like this: After installing Magisk (I strongly recommend the pre-rooted images), boot into TWRP and do the following:

   $ adb shell
   # echo "#!/bin/sh
   resetprop persist.service.adb.enable=1
   resetprop persist.sys.usb.config=mtp,adb
   sleep 30
   settings put global development_settings_enabled 1
   settings put global adb_enabled 1
   settings put secure install_non_market_apps 1" > /data/adb/service.d/enable-usb-debugging.sh
   # chmod +x /data/adb/service.d/enable-usb-debugging.sh

   This will create a shell script at /data/adb/service.d that should automatically enable ADB, disable debugging authentication and installation of apps from unknown sources on boot. With this, you can sideload other APKs (adb install <file>) and start them (adb shell am start <package name>). I provide no warranty that this works or does not damage your device. Use at your own risk. The provided script is a messy hack and needs cleaning up (most of the code is probably not needed). The device will potentially work less-than-ideal with this hack applied.
3. You can disable the OOBE, this way your launcher should appear on boot and home button press:

   adb shell pm disable com.amazon.tv.oobe

4. I strongly recommend installing GAPPS with this module, as the market and the Amazon login don't seem to work at all for me (although I'm not sure whether this is due to my own device, maybe it's blacklisted or broken in some way).

Edit: cleaned usb debugging script up a bit
Edit 2: included a script that installs the USB debugging enabler script automatically. This is meant to be used from a Linux system such as fireiso. Note that this still only works when booted into TWRP with Magisk already installed.

Hey. How do I install this script? I'm on Linux Mint and booted into TWRP connected via USB.

I get errors when inputting commands you posted above and an error while trying to install the script.

Prerooted image. I'm locked out as this is blacklisted unfortunately.

Any help with be greatly appreciated.

 

[MartK87]

Before I go buying this, will it work with ANY 4k fire stick? Can people please link some ebay links of the exact confirmed working models? Would be really helpful. I realize theres certain serial numbers to avoid but i guess thats a gamble with buying one.

 

[slack5]

I tried to find the scatter file for Fire Stick 4K but could not find it anywhere.
I am asking if someone who already rooted the 4k could upload the scatter file here.

 

[MartK87]

As usual... people been as much use as an ashtray for a motorbike. Ill take the gamble and just get the 4k 3rd gen

 

[Sus_i]

I tried to find the scatter file for Fire Stick 4K but could not find it anywhere.
I am asking if someone who already rooted the 4k could upload the scatter file here.

We don't use scatter files for the 4k stick, so you would need to dump the gpt 'with kamakiri' and then write a scatter file yourself... And again, if kamakiri won't work for your stick, spflashtool won't work too.

 

[slack5]

We don't use scatter files for the 4k stick, so you would need to dump the gpt 'with kamakiri' and then write a scatter file yourself... And again, if kamakiri won't work for your stick, spflashtool won't work too.

In that case I am afraid I will have to go EMMC way. I have access to Z3X Easy Jtag box so I will investigate a bit towards flashing the FS4K via testpoints. I believe I would need to flash the appropriate preloader only. After that Kamakiri's solution should be working?

 

[Sus_i]

In that case I am afraid I will have to go EMMC way.

What happens if you try kamakiri with and without shorting? Errors?

I believe I would need to flash the appropriate preloader only. After that Kamakiri's solution should be working?

Then kamakiri 2.x should working, yes.

 

[slack5]

What happens if you try kamakiri with and without shorting? Errors?

Then kamakiri 2.x should working, yes.

I tried kamakiri 2 without shorting and I do get errors.
I will try with shorting.

 

[Sus_i]

I tried kamakiri 2 without shorting and I do get errors.

What kind of errors?

I will try with shorting.