This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you
As long as the sticks are not updated to 6.2.8.7, you can still use the new kamakiri called 2.0.1, released a few days ago:newbie here i have 2 brand new firesticks with vm241 clearly above 190 does that mean sol or do or can i root some other way besides kamaka? any direction would be great thank you
thanks how do i burn the fire os i tried using rufus using win 11 it burns fine but when i try to boot to usb i get a a file image cannot be authenticated using mbr fat32As long as the sticks are not updated to 6.2.8.7, you can still use the new kamakiri called 2.0.1, released a few days ago:
Works without shorting, explained in this OP![]()
[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
![]()
[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...forum.xda-developers.com
Maybe format your flash drive as GPT partition and FAT32 using Rufus...thanks how do i burn the fire os i tried using rufus using win 11 it burns fine but when i try to boot to usb i get a a file image cannot be authenticated using mbr fat32
tried gpt mbr if i use fat32 i get authenticated failure if i use ntfs i get cant remember i think invalid or something along those linesMaybe format your flash drive as GPT partition and FAT32 using Rufus...
ill try a different usb stick or ext ssd drivetried gpt mbr if i use fat32 i get authenticated failure if i use ntfs i get cant remember i think invalid or something along those lines
oh its not rufus the drive burns succesfully its when i try to boot from the usb in win 11
I had the same problem, the issue lies within rufus for some reason. I tried the portable version of balenaEtcher instead and that allowed me to boot from usb on the first try: https://www.balena.io/etcher/thanks how do i burn the fire os i tried using rufus using win 11 it burns fine but when i try to boot to usb i get a a file image cannot be authenticated using mbr fat32
to funny i just tried etcher same non authenticated error, does etcher format the drive or should i preformat it. with what file system? ill try the link u posted maybe thats the difference although i think thats the one i used cause when i click on your link it doesnt look any different from the one i already have installedI had the same problem, the issue lies within rufus for some reason. I tried the portable version of balenaEtcher instead and that allowed me to boot from usb on the first try: https://www.balena.io/etcher/
also with win 11 i just click on f11 on my hp laptop wins takes me to the recovery optionsto funny i just tried etcher same non authenticated error, does etcher format the drive or should i preformat it. with what file system? ill try the link u posted maybe thats the difference although i think thats the one i used cause when i click on your link it doesnt look any different from the one i already have installed
PS C:\Users\your_user> cd .\Downloads\
PS C:\Users\your_user\Downloads> Get-FileHash .\fireiso-2.0.0-amd64.iso -Algorithm MD5
Algorithm Hash Path
--------- ---- ----
MD5 86D87CA603372033344547793BF7BB07 C:\Users\your_user\Download...
first of thanks for your help would the hash dictage a corupt iso or just verify that its the same file your using? i just used the iso posted on the guide pretty sure it was from github can you post me the exact link u used@squaleca1974 I just checked for you and I actually downloaded the Windows portable version v1.7.7 from their GitHub.
The tool will clone the disk image 1:1 to the USB stick, therefore overwriting any existing file system. Therefore I'm not sure if the previous file system is of any importance. If you want to ensure you start with a clean USB stick, I would format it as a GPT partition with a FAT32 file system, like @Sus_i suggested.
Have you checked the ISO was not corrupted while downloading? Assuming you use a Windows machine, you can open a PowerShell prompt and run the commands below to get the MD5 hash. The hash below is for the ISO I used, which works as described, so if it matches yours it should be okay.
Code:PS C:\Users\your_user> cd .\Downloads\ PS C:\Users\your_user\Downloads> Get-FileHash .\fireiso-2.0.0-amd64.iso -Algorithm MD5 Algorithm Hash Path --------- ---- ---- MD5 86D87CA603372033344547793BF7BB07 C:\Users\your_user\Download...
Finally, I just rebooted my computer and used a hotkey to boot it from the USB stick. Your way should do pretty much the same thing, but you could look up the specific hotkey for your computer and try booting from the USB stick directly like I did.
ok very strange i was going to format the drive afteeer using etch successfully and it shows up in disk management as unlocatable like etch did nothing strangefirst of thanks for your help would the hash dictage a corupt iso or just verify that its the same file your using? i just used the iso posted on the guide pretty sure it was from github can you post me the exact link u usedView attachment 5556865
You're welcome.first of thanks for your help would the hash dictage a corupt iso or just verify that its the same file your using? i just used the iso posted on the guide pretty sure it was from github can you post me the exact link u used
Just reconnect the drive to see if that sorts it. Or use a different USB stick. Then if you want you format the stick first and then use etcher to clone the image on it.ok very strange i was going to format the drive afteeer using etch successfully and it shows up in disk management as unlocatable like etch did nothing strange
adb devices
adb shell
exit
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?