yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Sus_i:
I don't know what you mean. You can pull the whole bootlog, thats why it is so big...

There is the boot-fastboot.sh script in the kamakiri zip and there are at least two options in twrp too.
[Fire TV Original Android Development] tomislavv:
When device is connected to computer it is not recognized so boot-fastboot.sh does nothing. I know different reboot options in twrp, how to select 'reboot to hacked bl' without otg+keyboard ? I guess there is no way. None of my firesticks were accessible via computer when connected with usb otg btw.
[Fire TV Original Android Development] Sus_i:
There is also a command for twrp via adb, not only the button in the GUI... you can find the command in this thread.
[Fire TV Original Android Development] tomislavv:
Cannot connect to computer (not detected) when booted to TWRP, that is the problem.
[Fire TV Original Android Development] Sus_i:
Your stick is entirely fine.
[Fire TV Original Android Development] Sus_i:
Btw, just forgot, we can select that button, unplug the OTG, connect an USB cable and boot to hacked fastboot. There must be a reason why that 'reboot to hacked bl' button is there, isn't it? ;)
[Fire TV Original Android Development] tomislavv:
Ok, got it !
[Fire TV Original Android Development] wwwkkk:
i`ve got the same (the stick is not recognized) and thats of course the batch only works for newer Firmware up to 6281. If the Firmware ist too old, you must use the Mantis v1.2 and this works fine.

On the other hand, the kamakiri 2.01 made an error on to new Firmware.... but i fixed it and write the solution in this thread later
[Fire TV Original Android Development] wwwkkk:
Hi there. the kamakiri-mantis batch got problems with to newest Firmware and exit with the message:

Downgrade rpmb

downgrade failure, giving up

then, the batch reboot the stick.

I tried maybe a hundred times, but the batch allways exit at this point

then i took a look at the batch and tried something by myselfe:

i edit the script main.py and removed the lines:

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

dev.reboot()

raise RuntimeError("downgrade failure, giving up")

log("rpmb downgrade ok")

dev.kick_watchdog()

the script runs to the end and the stick reboot in patched fastboot mode.

then i started the fastboot-step.sh and the twrp was successfully writen.

Once i reached that point, i push the file kamakiri-mantis-v2.0.1.zip to the stick an flashed it.

dont know, that maybe helps anyone

***use at your own risk***
[Fire TV Original Android Development] tomislavv:
Thanks, appreciate it.
[Fire TV Original Android Development] Sus_i:
What are you talking about? ;)

Kamakiri 2.0.1 worked fine for @tomislavv
[Fire TV Original Android Development] tomislavv:
Thanks a lot for this tip. Now I can run fastboot-step.sh successfully. But that doesn't help my main problem not being able to access stick via usb unfortunately.
[Fire TV Original Android Development] alexloco83:
Hi Everibody

I have a Fire Stick TV 4K locked in Amazon Platform (no way to first time activate)

Is there any way to ""unlock"" that and put in use?

Thanks for your help
[Fire TV Original Android Development] wwwkkk:
I've tried a stick with installed 6268 and this stick was not recognized by the kamakiri Mantis 2.01
[Fire TV Original Android Development] Sus_i:
Yes, you are right, (y)

early preloaders aren't vulnerable to the new kamakiri :)

EDIT: but in theory it should work also for sticks (with low serial, sitting on fireOS <= 6.2.7.7) with a short nevertheless... haven't tried it though ;)
[Fire TV Original Android Development] gojannz:
Hello everyone! I have a TCL Alto 8+ FireTV edition soundbar, i disassembled and tried unlocking the bootloader using the instructions found in this thread. Script ran but it gave an error that says "wrong device detected"

[2022-03-28 21:09:06.234120] Waiting for stage 2 to come online...

[2022-03-28 21:09:06.497381] All good

[2022-03-28 21:09:06.650407] Check device_type_id

[2022-03-28 21:09:06.650868] Wrong device detected: A2WV8TTM37P2CB

I searched throughout this thread and didn't see any post related to this device. This is still a Firestick 4K and under the name Mantis with OS 6.2.6.5 (NS6265/2158), serial number starts with G0715B0. Any help or suggestions would be greatly appreciated.
[Fire TV Original Android Development] Sus_i:
You may be able to disable/edit the device check lines in the main.py script, but nobody knows if your device is a real mantis stick, could be that you brick it because flashing little-kernel or tz images for mantis may not work for your specific version...
[Fire TV Original Android Development] gojannz:
Thank you for the reply, correction: firmware is 6.2.6.5. It still works, prime video won't launch with any custom launcher, it looks like it force closes the app. No issues with stock launcher. That's the reason why the bootloader unlock and to update firmware to a later version, without losing custom launcher.
[Fire TV Original Android Development] Sus_i:
There isn't a 6.2.6.5 OS for mantis and using or flashing mantis images with kamakiri can brick your device...

You can try it nontheless (edit the kamakiri main.py, match device_check_id with your device id A2WV8TTM37P2CB), but I guess thats a bad idea. If something goes wrong, lets say the kamakiri-flashed LK isn't suitable to your device, you don't have any backup for an unbrick... Maybe dump the GPT first and then take a backup from the partitions, infront of an unlock attempt.
[Fire TV Original Android Development] :
Pulled my device out of storage and checked the OS version. It is 6.2.8.1 (NS6281/3385).

I paged down to updates, and apparently the update has already been downloaded and will "automatically begin the next time your Amazon Fire TV Stick 4k is not in use." The pending update is 6.2.8.7 (NS6287/3768).

Edit: never mind, it updated before I could run kamakiri 2.0.1.
[Fire TV Original Android Development] :
I obtained a different non-updated device and was successful using kamakiri 2.0.1!!

I was curious what the bootloader might be spitting out (if anything) over the uart while the preloader exploit was being executed. Especially since the exploit apparently uses some uart-style connection over usb.

I thought it would be relatively trivial to tack solder a couple of wires to the uart pads. I'm somewhat embarrassed to admit that it took me the better part of two hours to solder and run wires to the uart pads and punch through a header in an unpopulated area of the board by the antennas. It is just an awkward spot to do delicate soldering.

I'm ready to solder wires to vcc, vccq, gnd, dat0, cmd, and clk so that I can downgrade my other updated device. My board revision has a bga SoC, unlike the first post in this thread. Have these locations been identified for my board revision in some other post in this thread? Also, the best way to hold the SoC in standby/reset while doing r/w operations on the emmc?
[Fire TV Original Android Development] Sus_i:
(y)

For the old style bootrom-step UART used 115200 baud, while for the new preloader based bootrom-step it should be 921600...

looks nice and clean from here :)

Picture from OP doesn't show the SOC, it shows the connectivity chip for wifi, bt and so on. ;)

Somewhere on the board should be the xtal of the SOC...
[Fire TV Original Android Development] :
Thanks for the info about the baud rates and the tips about the emmc.

I think I'll save the project of direct writing the emmc for another day.

All of the mantis devices in stock at my local target have nice stale firmware. So, I just went and bought another one, rather than trying to downgrade my other device. The only downside is that target is selling them at full list price.
[Fire TV Original Android Development] EvoGT2k3:
Hi there. Are there any hopes for a stick with serial number "G070VM201.."? Firmware is below 6.2.8.1.
[Fire TV Original Android Development] Sus_i:
Yes, kamakiri 2.0.1 will work fine...

Works without shorting, see the instructions in this thread:

[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
[Fire TV Original Android Development] gojannz:
Thank you for your suggestion, bootrom-step.sh was able to run and finished without any errors. Fastboot-step.sh gave an "assertion pad" error, though. I'm not good with Linux so i tried using Windows to fastboot flash the twrp.img file manually from the Kamakiri folder and works. Pushed and installed pre-rooted ROM using TWRP adb commands. Now running on mantis-6.2.7.7 without any issues. Thanks again!
[Fire TV Original Android Development] wadams1:
out of nowhere it seems my firestick has lost the ability to support otg, cant see thumb drives and mouse doesnt work in twrp

anyone else ran into this?
[Fire TV Original Android Development] Sus_i:
Thats fine :)

@k4y0z

FYI, unlock works for the 'TCL Alto 8+ FireTV edition soundbar' too :)

Device ID is A2WV8TTM37P2CB if you like to add support to kamakiri.
[Fire TV Original Android Development] Chem23:
Just bought a 4k with the hope of following this guide successfully. Serial starts with G070VM242.

Will this approach work and anything else i need to do or avoid doing before i get started?

Thanks :)
[Fire TV Original Android Development] Sus_i:
Keep it offline... ;)
[Fire TV Original Android Development] Chem23:
Thanks! Other than not letting it update to a newer firmware, am I all good to go with VM242 serial? Will i need to use the shorting method too?

Thanks
[Fire TV Original Android Development] Sus_i:
Kamakiri 2.0.1 will work fine (fireOS must be lower than 6.2.8.7).

Works without shorting, see the instructions in this thread:

[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
[Fire TV Original Android Development] Chem23:
Thank you :) I'll get cracking!!!#

one sec - isn't the 4k mantis? That guide appears to be for the sheldons.##

Sorry if i'm not understanding this correctly!
[Fire TV Original Android Development] Sus_i:
Use Kamakiri 2.0.1.zip for mantis and follow the guide for sheldon... (because mantis OP guide needs an update).
[Fire TV Original Android Development] Chem23:
Gotcha!! Thanks again
[Fire TV Original Android Development] :
So to clarify: If my 4k is on 6.2.8.7 this wont work?
[Fire TV Original Android Development] pcwawa:
Deleted the KFTV Luancher that came with 6.2.8.7 using TotalCommander, no root required, simple and brutal, and the third party Luancher works again.
[Fire TV Original Android Development] :
How long has it stuck? Do you have updates blocked? If not wont it just come back?

Can you post some steps? Which version of TC?

"brutal"? how so?

I had my updates blocked and Amazon somehow got 6.2.8.7 on me anyway
[Fire TV Original Android Development] pcwawa:
The third party luancher still worked after restarting my FireTV Stick 4K, and then I blocked Amazon's upgrade URL on my router. I think Amazon will have new ways to upgrade my stick in the future, we'll see.
[Fire TV Original Android Development] :
Wait....so it was working BEFORE you removed KFTV? and you are on 6.2.8.7?

Mine wont let me delete KFTV
[Fire TV Original Android Development] pcwawa:
Before I removed KFTV Luancher using TotalCommander, although my ATV Luancher would work, it would not be associated with the home button of the remote control. Now I can run ATV Luancher through the home button of the remote control.
[Fire TV Original Android Development] :
Ok makes more sense but I cannot get total commander (3.20) to find that app and uninstall it....can you provide more details? Only option I get is to "delete" the file in system/priv-app folder.

It doesnt show up in installed apps.

When I try it with MiExplorer it says uninstall failed
[Fire TV Original Android Development] Sus_i:
Yes, unlock won't work.

Seems it uninstalls only KFTV Launcher 'updates' + delete app data...

So this may only work for 6.2.8.7 if all 'component updates' via fireOS updater are installed too... maybe the reason why it fails for some people, cuz the app itself on system/private is secure (without root), updates not.
[Fire TV Original Android Development] :
The only problem for me on same 6.2.8.7 is KFTV does not show up in Installed apps for some reason. The system apps are not viewable. My Home version was lower than his so I am allowing the updates and see if that helps visibility of system apps.

I tried to delete KFTV from system/priv-app and was denied

UPDATE: took updates to get Home Version to the same as in pictures. KFTV appeared in installed apps and I successfully deleted it, BUT it still is there and mapped to the home button. I do not get an option to use Wolf even if I try and enable it through Launcher Manager from TechDr

UPDATE 2

I have let as many updates as I ac....and even though KFTV is still deleted and not in Installed Apps the Stock Launcher still lives. When I use MiExplorer it is in Apps but I cannot delete
[Fire TV Original Android Development] mea_pulpa:
Registered just for thanking you .

Simple and effective . This actually works ! My firestick updated to 6.2.8.7 even though I had updates blocked (most likely because I use nordvpn all the time which renders the block useless) , so I was suddenly stuck on the default amazon manager .

After your trick :

I reboot my 6.2.8.7 firestick : automatically launches wolf

I press home key : launches wolf

I love it .

Now is there a way to block amazon url access/updates , while using nordvpn ?
[Fire TV Original Android Development] :
What Home Version are you on? I still cant get mine to work =(

Do you use Launcher Manager?
[Fire TV Original Android Development] jorges4lu2:
Hi,

After a successfully root on a 6.2.8.1 4k stick I have Netflix frozen every time I try to open it.

I've read that I have to update the tz in order to fix Netflix, but where can I find the tz for my 6.2.8.1 4k stick? How do I flash that tz?

Thanks in advance
[Fire TV Original Android Development] Sus_i:
You can go to this thread:

https://xdaforums.com/t/fire-tv-stick-4k-mantis-prerooted-stock-images-6-2-8-1_r3.3983091/

download and flash 6.2.8.1r2, which will ipdate the TZ for you...
[Fire TV Original Android Development] mea_pulpa:
I followed @pcwawa screenshots exactly . There is no launcher manager needed for his solution .

My stick is on 6.2.8.7 .

6.2.8.9 is being downloaded by my firestick as we speak . :/
[Fire TV Original Android Development] jorges4lu2:
Thanks

Could you tell me if I have to wipe something on TWRP or just flash that .zip?
[Fire TV Original Android Development] :
No clue why mine doesnt work unless I took an update that blocks this too...Let me know if you can still do it on 6.2.8.9?
[Fire TV Original Android Development] Sus_i:
No wipe necessary... :)
[Fire TV Original Android Development] :
Doesn't the customized twrp recovery for this device disregard any attempt at updating tz via twrp install?

I had to pull tz from 6.2.8.1r2 and copy in to the unlock folder and re-run bootrom-step.sh in order to get tz updated. At least that is my best guess.

Can twrp install really update tz?
[Fire TV Original Android Development] Sus_i:
Yes, thats true.

That works too. :)

If the stick is really on 6.2.8.1 and if it's for sure that there isn't any other OS version flashed (i.e. the TZ needs to match with the OS), then flashing the 'prerooted 6281r2' from rbox will do the trick too.

If the update bin contains special flash commands (like the 6281r2 from rbox), then yes. :)
[Fire TV Original Android Development] mea_pulpa:
Read here for a solution to block updates while still using your own vpn (works for me at least) .

https://xdaforums.com/t/block-future-updates-6-2-8-9-incoming.4430497/post-86737497
[Fire TV Original Android Development] EngineerMind:
What method/app did you use to block the updates?
[Fire TV Original Android Development] Sus_i:
Seems the update block for user0 isn't as reliable as the pm disable command via root.

It's also used for fire tablets, now and then someone hit the forums because it updated never the less.

Can't tell why this is happen, I guess there is a way for the system to enable the user0 disabled apps again.

I always root my devices and all is fine :)
[Fire TV Original Android Development] SecOps:
Hey community, new to the Fire TV unlocks. The guide here is a little unclear for one who does not want to read up on 94 thread pages. Is there any way I can

disable OTA

? I followed the aftvnews guide on how to disable through router though I was still able to ping on a computer to the websites they wanted blocked (via ICMP). Took apart the mantis too and saw a different chip manufacturer inside ("SEC 907" top lettering, and hard text to read without proper lighting). Did not do anything with the pins that the guide asks for. It's reassembled, but I don't want to plug it into the TV and have it start automatically updating. The mantis is currently on

6.2.8.7

.

Figured I should have disabled OTA first before doing anything on the inside as that's what the guide (1st page thread) strongly recommends.
[Fire TV Original Android Development] Sus_i:
Easiest way for non-rooted fireTVs is to use this guide/DNS:

Block updates. DNS way. No root needed

Here is instructions of how to block Updates on a Fire TV. Important! Recently a Fire TV update released, it blocks any way to disable auto updates, except this one Some ISP are replacing client DNS requests by their own answers, in that case...

xdaforums.com
[Fire TV Original Android Development] xieve:
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)

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)

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.

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

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.
[Fire TV Original Android Development] azsde:
Hello everyone

How can I determine if I can root and use TWRP on my recently bought fire stick 4k max ?
[Fire TV Original Android Development] Sus_i:
The kamakiri microloader must be installed first, then the boot-recovery and boot-fastboot scripts will work... We can use them 'without' a short. :)
[Fire TV Original Android Development] Dak1llah:
Hello folks, I am long time lurker on XDA, hence making a account only now.

I usually dont have anything smart share, and I am finding all of the guidies quite helpful, I'f I get stuck I fly throught the thread as well. Went throught this one with ease. :)

However, I stumbled upon the issu with the FireTV stick. It's been in my drawer for past 2 years, and now it just shows the FireTV logo, I've tried all of the suggested troubleshooting but none worked.

So I was OK, let's try to root it and play with custom build, but no luck.

I can do short trick and run ./bootrom-step.sh, and once that is done when I run ./fastboot-step.sh it start with the message "waiting for any device" for an eternity, think it's been a few hours now and no joy.

I tried accessing the device via ADB but no job there, it does not list the device. Altho if my memory servers me well, I had debugging and installation of unkown apps enabled last time, since I was sideloading the apps via my andorid phone.

Would anyone have any suggestions by any chance?
[Fire TV Original Android Development] :
Does the microloader need to be installed only once in order to use boot-recovery.sh and boot-fastboot.sh?

I couldn't seem to get forced fastboot working in a new session by merely running boot-fastboot.sh, even though bootrom-step.sh had been successfully executed in a previous session.

I could get forced fastboot working if I repeated bootrom-step.sh in a new session, of course.

What is being forced in forced fastboot? Is the native bootloader not coded in such a way that recognition of an unlocked status would ever allow native unforced fastboot to flash partitions without being forced? Or is it that the microloader never loads if native unforced fastboot is used because no bootable image is executed in such case?
[Fire TV Original Android Development] Sus_i:
Common issue, you need to update the fastboot package to the most recent version. If you search this thread, you find the pacman command for use with the fireISO.
[Fire TV Original Android Development] Sus_i:
Yes ofcourse, once is enough

Run boot-recovery or boot-fastboot script, then connect the sticks usb.

No, the bootloader isn't really unlocked. Kamakiri placed only a payload to unlock, which will run at every boot, on top of the boot process. I.e. the 'locked' jump to the kernel gets replaced by the paylload, which will then jump 'unlocked' to the android kernel.
[Fire TV Original Android Development] Dak1llah:
Thank you for the quick reply, I really appreciated that.

So I done that, but there's another error, please see attached - I swapped the USB ports, as well as cable and used CLK and CMD to short, but same thing, any ideas?
[Fire TV Original Android Development] Sus_i:
You need to connect the fireISO system to the internet, then run the fastboot update via pacman command, then the fastboot-step... :)
[Fire TV Original Android Development] Dak1llah:
So I did this twice, just for the good measures:

rebooted FIreOS, after sucessefull bootrom-step and pacman command, I did fastboot-step, but it goes into endless "waiting for any device".

I tried to run ADB devices tool, but it does not list the device there, alto bootrom command sees it, wondering if this bad boy is gone for good, e.g. has some other faults.
[Fire TV Original Android Development] SweenWolf:
fastboot and adb are different things, if you execute ./fastboot-step.sh then it should open fastboot.

And the command to check the device is

fastboot devices

and not

adb devices