yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] fluffi444:
Nevermid... Just noticed that Pretoriano80's Kernel (which I'am at 6.2.7.7 - 3033) as insecure ADB - Therefore no ADB RSA Keys are needed - And no popub came up - Even if file (on FireTV) /data/misc/adb/adb_keys is deleted/renamed.

For testing: With stock Kernel 3033 the RSA PopUp came up again (with deleted /data/misc/adb/adb_keys),

and new file /data/misc/adb/adb_keys is created with correct permissions...

:ROFLMAO: Again we are fiddling at the same place - I wonder why? :)

Even if its not needed for your case anymore - To reset the RSA Key its needed to delete/rename files on the sending and receving side (one side should be enough as well, but to keep it clear... both)

WinPC: C:\Users\<USER>\.android - Files: adbkey + adbkey.pub

Linux/Android/FireTV: /data/misc/adb/ - File: adb_keys

FireISO: /root/.android/ - Files: adbkey + adbkey.pub (of course temporary)

On WInPC its reported that adbkey + adbkey.pub may are saved at other places.

If they are not in mentioned folder search on system drive for them....
[Fire TV Original Android Development] ~iceweasel:
Thanks again. Couple follow ups for the "general education" side...

This worked but was not totally smooth due to fear of stock update sneaking in. First pass was reinstall Magisk (with the wipes of data and cache) so had to setup again. During setup there was a quick checking update which had me fearing something completely downloaded. I've throttled the traffic on stick, but only took a second for the update to download... I believe this was not correct. At the time I ran to the hills and used the boot_recovery script and used twrp to rinstall 6.8.2.1_r3 and then reinstalled magisk. Wasn't sure if this was OK, but given what the progress says I believe it wouldn't matter if mantis was recently installed without running yet. Thinking I'm good.

I'm wondering, when I needed to reinstall magisk the first time, do I need to wipe cache and data partitions? I'm on the fence, but also don't know what exactly is stored in those partitions. When reinstalling mantis I only wiped before the mantis install and didn't wipe a second time before magisk. I think that's all fine because I got everything up fairly easily after this method. Although I still had a deer in the headlights moment when Magisk wanted permissions to update and install due to the note about not updating magisk outside of twrp. Different name for the manager app and base magisk would help me.

Would be fun to have cams on us as we do this, because I'm sure my stress would be entertaining for some. 🤣

I tried deleting the keys, but wasn't sure where exactly they lived. On the stick (I think I was on the stick) I renamed what appeared to be key files in FireOS live /root/.android but that didn't really help and as far as I dug. adbkey and adbkey.pub sure looked like what I needed... I didn't locate any files on the stick, but I really didn't look too hard.

Previous times I've toggled ADB enable in the settings which sometimes seemed to trigger a new handshake and exchange, but I can't tell. I'm still not sure if it's best to leave the persistence check when using the fireos.iso. My gut says keep those temporary.
[Fire TV Original Android Development] Sus_i:
Basically you don't need to wipe anything infront or after a flash... especially not data, since there are all your settings, account, apps and so on stored. If you disable updates this setting gets also stored on data.

One exception is if you want a clean install of a rom, but for fireTV 4k only advised if you are on 6.2.8.0 or later and downgrade to 6.2.7.7 (i.e. from new UI launcher to old UI). Then you would also re-flash kamakiri 2.1 in order to get the old TZ back.
[Fire TV Original Android Development] aleet:
Hi everyone. Need some help. Got a mantis for free. Amazon told me not to return it. I can't register the stick. I ran the scripts and TWRP installed and working. Challenge is I don't have OTG cable. Long story short. Download this thread rom. Instead of TWRP install which I don't have keybd. I ended up adb sideload. Does that means this won't patch the stick like TWRP would?

The boot scripts and sideload all says successful. When the stick ask to login it give me 2 options. Online amazon.com/code or enter my login on the stick.

If I login on stick, it flat out saying something is wrong. If I login from online code, the site says successful but the stick didn't do a thing.

I also tried a ROM here says no efuse. Same behavior. Since I can't pass login. I can't tell which version I am on. All I know is the script worked and it is a VM242 serial. How do I know efuse is burnt or not? I only wish I have OTG do I can try TWRP.

Edit: just found out I can do "trwp" from adb shell, but still after twrp install and wipes, still thou shall not pass registration. Are there LineageOS, AndroidTV, or Ubuntu, so I can repurpose and not e-waste? Retro/Emulator would be so cool.

Thanks
[Fire TV Original Android Development] aleet:
Forgot to mentioned, I do have a vanilla fire stick lite registered. Any files I can grab and transplant to 4k stick? Like a register key, etc?
[Fire TV Original Android Development] ~iceweasel:
I questioned wiping data every time I did it... seemed counter productive unless wanting to roll back to do something like have to walk through initial setup.

I made note of the need to do if I roll back to old UI vers. Appletv is working fine with the latest, and even though I hate the interface and believe my initial problem may have been with my throttled connection for the stick I don't plan on rolling back.

You're a big help, thanks for taking the time to help us!
[Fire TV Original Android Development] Joe Baliu:
Hi,

I have succesfully installed TWRP 3.6.1_9.0 on my Fire TV 4k with 6.2.7.3 os version.

I have also succesfully installed Magisk 25.2. Cache/dalvik was cleaned.

But when I try to run 'su' or 'pm' I get "Not found". I tried 'su' and 'pm' via adb shell and twrp terminal with same results.

Initially I installed Magisk via adb, then retried via twrp UI - but in both cases 'su' and 'pm' are not found.

What could be the issue? Thanks in advance

P.S. when I try 'pm' after mounting system I get 'library "ld-android.so" not found'.
[Fire TV Original Android Development] Finnzz:
You are in TWRP, and already have root. Package Manager isn't available until you boot FireOS.
[Fire TV Original Android Development] redeyedjedi:
I got a 4k stick at 6.2.8.1 and I have gone through the process and rooted it.

What is the proper procedure to get it updated to 6.2.9.4?? I assume the DRM is out of date and Netflix and prime show a black screen. It also seems this root blocks updates, as it just boots to twrp and the update never happens. I am perfectly ok with manually updating but can't seem to find the bins anywhere. Any help here would be appreciated.
[Fire TV Original Android Development] Sus_i:
As you've got a stick with 6281 (already burned efuse = shorting method gone), there isn't a special procedure required, you would just need to flash the rom you like...

If you go to 6.2.9.4 you may flash the TZ too (if there are DRM playback issues or black screens).

Easiest way to do this is take/extract the TZ image from 6.2.9.4 rom and overwrite the TZ image from kamakiri 2.1 folder. Then re-do the bootrom/fastboot-step.

https://xdaforums.com/t/fire-tv-sti...ps-official-cloud-front-direct-links.4088247/
[Fire TV Original Android Development] redeyedjedi:
Done and done. Thanks, this is exactly what I was looking for. Now, is there a semi up to date list of what system apps can be deleted? Time to go looking.
[Fire TV Original Android Development] Sus_i:
Maybe use adb shell pm disable instead, so it's easy to enable again if something goes wrong ;)
[Fire TV Original Android Development] Mfizz:
Hi all, I'm hopeful you can help me. Back in October my firestick out by 5 days warranty got stuck on boot animation with fire TV logo.

My primary goal is to get it working again and root is a bonus. I'm not sure what os version it was on. I had adb debugging enabled, but didn't connect it to any pc.

Will this method help me recover my stick? I have already tried all the official methods with remote, otg cable etc.
[Fire TV Original Android Development] tim.baxter@talktalk.net:
Here's a YouTube vid which shows it all. Enjoy
[Fire TV Original Android Development] tim.baxter@talktalk.net:
It's not that I get bored waiting for the script to run, I just don't know how long to wait for! Can anybody tell me please, exactly which point is supposed to be shorted and to where? Should the script run and inform me immediately that I insert the usb plug into the PC? I wait for seemingly ages and then make ^C to terminate. This what I get. Has the script run or are my terminals still not shorted? Help please!
[Fire TV Original Android Development] fluffi444:
How to short is documented well in thread...

If it shorts correctly AND your stick can be rooted short (

lower

FW than 6.2.8.7) then the script starts immediately withhin milliseconds - after plugging the USB.

With my first stick (updated by mistake to 6.2.9.4 right after first boot) I waited 30 min :) with running bootrom-step.sh.

Untill I start reading and learing much and learned that 6.2.9.4 is not rootable at all!

Sold this to a fried whom do not care about rooting att all - I explained him...

Bought a second one (old modell from 2018 but brand new - shipped with 6.2.3.1 - VM058) and this was rootable via short right away. Here the short was mandatory!

In addition a bought now a third one from private and unopend (for my sister) build 2021 (shipped with 6.2.8.1 - VM101) - This was rootable right away without any short!

So all in all its about build date, serial number (VM***) and most importand FireOS-Version. - Check this all.

There are some ways to boot the stick without initial forced update to find out what FireOS is installed.
[Fire TV Original Android Development] tim.baxter@talktalk.net:
Thanks for that info. Mine is, of course 6.2.8.9! Is there anyway of downgrading? I suppose not.
[Fire TV Original Android Development] fluffi444:
No - sorry - As far as I know there is no way to root or to downgrade with 6.2.8.9.
[Fire TV Original Android Development] Skel40:
The roms I have are also safe to flash as well. I have downgradable roms without the efuse
[Fire TV Original Android Development] Skel40:
I've tried to unlock my 4K again with the 2.0.1 zip @k4y0z provided and my OTG couldn't recognize my mouse in recovery mode. I used the plugin method without pin pointing so can someone help me out?

Edit: ADB doesn't work at all it doesn't detect it after ./fastboot-step.sh boots into TWRP. The hacked fastboot is fine it shows up. Only adb isn't working. I don't know what's going on. The unlock is successful, and right when I try to enter adb device's on terminal on fireiso, nothing.

I managed to fix the OTG issue after flashing 1.2 of the kamakiri exploit. It seems to be recovery related
[Fire TV Original Android Development] cityhunter_1919_xyz:
I had the same symptoms with an unopened 4K obtained from a private sale.

I contacted Amazon and they replied that it was because the serial number of the device had been erased due to a return or some other reason.

I was able to get to the home screen by restoring the data I had backed up on my other 4K, but I can't use the store, so some apps that depend on Amazon are not available.

Some apps that rely on Amazon can be avoided by installing from AptoideTV.
[Fire TV Original Android Development] aleet:
Oh cool. You mean from TWRP restore data partition? Would you know where I can get a copy? I actually do not want Amazon store since we can side load.
[Fire TV Original Android Development] DevanteWeary:
Hey guys,

So I can't even boot the FIREISO200 image.

I've tried three different USB drives with Rufus using the following settings.

Partition scheme: MBR

Target system: BIOS or UEFI

Quick format: off

File system: FAT32

Once I boot the drive, I'm met with this each time:

I'm at a loss, guys.

What should I do?

Thanks for any advice!
[Fire TV Original Android Development] Anphab:
Use rufus write DD image mode
[Fire TV Original Android Development] Anphab:
My Fire Stick is on 6.2.7.7 firmware .

but netflix not working how i can watch netflix without update fw
[Fire TV Original Android Development] andrew93753:
So I dont know what happend, never tried to Root the Stick or somethign else, but my Mantis Stick wont boot past the Black Screen with the Logo on it.

After a couple of Seconds it just reboots itself and stays in the Bootloop forever.

Ive waited several Hours powered on to see if that would fix anything but no.

Bought a cheap USB Keyboard with a Menu Key to get into the Recovery Mode but couldnt make it either.

Tried both Alt + Print + I as well as Ctrl + Alt + Menu + Print + I. I dont know if its the Timing but ive held the Buttons and smashed them but it wont get out of the Bootloop.

Edit: Never connected the Stick to a PC, so no ADB and Firmware should be on the newest Version. The Unlock Script got a expected xxxx Number but got xxxx Number Error.
[Fire TV Original Android Development] DevanteWeary:
Thanks for the reply. Yep, that helped!

However, now I'm stuck at this screen.

It basically waits several section, then goes through this screen over and over again, pausing in between.

As if it keeps retrying to do whatever it's trying to do.
[Fire TV Original Android Development] barc0de1989:
There's your issue. Rufus is great for many things but this isn't one of them. Use Balena Etcher and it will work. I had the same issues you have
[Fire TV Original Android Development] DevanteWeary:
Hey!

I actually tried Etcher before my original post.

As far as I could tell, there were no options. Just select image, select drive, and it does the rest, right?

Well when I tried Etcher, I got the same issue as when I tried Rufus without DD mode.
[Fire TV Original Android Development] cityhunter_1919_xyz:
I want to use the new version (OS 6.2.8.7-), but after flashing the stock-rom with TWRP, will it be possible to boot without problems if I delete these two files?

/system/bin/efuse_check.sh

/system/bin/ewritter

Also, won't TWRP disappear?

Apart from that, I also have a stock (non-TWRP) 4K stick (OS 6.2.9.3), but for some reason it has 1.8GB of system memory.

Thanks to that, it is difficult to fall on heavy sites.

Some time ago I flashed OS 6.2.9.4 from rbox 6.2.8.1 and still had 1.3GB of memory. (I tried increasing the SWAP area, but it was not effective for heavy sites.)

I think that the cause of the increase in memory may be related to some version.
[Fire TV Original Android Development] cityhunter_1919_xyz:
I'm using a normal 4K backup that I have.

Since it contains account information, etc., it cannot be handed over.

(with prime video)

Please get a new unused 4K stick, install TWRP, and create a backup with the initial settings completed.
[Fire TV Original Android Development] rahulbmg:
someone please help. I am getting the error below. And i am not using emulator

[root@fireiso ~/Downloads/kamakiri-mantis-v2.0.1/kamakiri]# ./bootrom-step.sh

[2023-03-16 21:07:23.756547] Waiting for device

[2023-03-16 21:07:33.484969] Found port = /dev/ttyACM0

[2023-03-16 21:07:33.544591] Handshake

[2023-03-16 21:07:33.565564] Load payload from ../brom-payload/pl/pl.bin = 0x3A04 bytes

[2023-03-16 21:07:36.050129] All good

[2023-03-16 21:07:36.543132] Check device_type_id

[2023-03-16 21:07:36.543301] Detected mantis (AKPGW064GI9HE)

[2023-03-16 21:07:36.543375] Check GPT

[2023-03-16 21:07:37.070601] gpt_parsed = {'lk': (1024, 2048), 'tee1': (3072, 10240), 'tee2': (13312, 10240), 'boot': (23552, 32768), 'recovery': (56320, 32768), 'logo': (89088, 7168), 'kb': (96256, 2048), 'dkb': (98304, 2048), 'MISC': (100352, 2048), 'vendor': (102400, 307200), 'system': (409600, 2252800), 'cache': (2662400, 1048576), 'userdata': (3710976, 11562591), '': (0, 1)}

[2023-03-16 21:07:37.070751] Check boot0

[2023-03-16 21:07:37.549660] Check rpmb

[2023-03-16 21:07:37.580679] Downgrade rpmb

[2023-03-16 21:07:37.581025] Recheck rpmb

Traceback (most recent call last):

File "/root/Downloads/kamakiri-mantis-v2.0.1/kamakiri/modules/main.py", line 135, in <module>

main(dev)

File "/root/Downloads/kamakiri-mantis-v2.0.1/kamakiri/modules/main.py", line 74, in main

raise RuntimeError("downgrade failure, giving up")

RuntimeError: downgrade failure, giving up
[Fire TV Original Android Development] cityhunter_1919_xyz:
I was in trouble with the same error before, but I was told by this reply.

Delete the following comments in kamakiri > modules > main.py

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

dev.reboot()

raise RuntimeError("downgrade failure, giving up")

lines 72-74
[Fire TV Original Android Development] rahulbmg:
Thanks it worked
[Fire TV Original Android Development] andrew93753:
Any advice for me?
[Fire TV Original Android Development] cityhunter_1919_xyz:
The possibility of resurrection is to try unlocking with fireISO. If all goes well, you can flash the ROM via TWRP.

I also tried to use the USB keyboard for stock recovery myself, but it didn't work.
[Fire TV Original Android Development] cityhunter_1919_xyz:
Looking at past posts, there was another way, and it worked.

Please refer to #1077 and #1075.

No backup data required.

(I think you should use your favorite rooted rom)
[Fire TV Original Android Development] andrew93753:
But I couldnt unlock the Stick with fireISO because i'm on the newest Update.
[Fire TV Original Android Development] palermorosanero:
can the modification be done on first and second generation firesticks to upgrade from os 5 to os 6?
[Fire TV Original Android Development] ady0000:
Where
[Fire TV Original Android Development] ady0000:
Where to short?
[Fire TV Original Android Development] Sus_i:
other side ;)
[Fire TV Original Android Development] yakovperelman69:
Hello everyone.

I recently bought a new FireStick 4K.

Even though I followed the instructions on how to block Amazon system updates; the device connected to my Wi-Fi without asking me and got OS 6.2.9.2.

2 Question:

-Is there a way to go back with factory reset?

-Has any new method been developed to root OS 6.2.9.2?

thanks all
[Fire TV Original Android Development] manacho1:
I'm using Oracle Virtual Box Manager to run the firestick Iso as a Virtual Machine. I'm not sure if I used the correct settings. I chose Linux for Type and Oracle Linux (64bit) for the Version. When I run the bootrom-step.sh command, it just says waiting for the device. The device is recognized in my windows device manage as AFTVV. Nothing happens when I apply the shunt either. Any advice would be appreciated.
[Fire TV Original Android Development] bloxycola:
a factory reset wipes evverything
[Fire TV Original Android Development] bloxycola:
Mine will just lock up and not play video any fix?
[Fire TV Original Android Development] bloxycola:
Pry it off
[Fire TV Original Android Development] npolite:
For anyone having issues about what to short, just get a piece of electrical wire (nothing heavy guaged) and put it in the area where the shield is located above. That was enough for me to short the connection and apply the root scripts.

Also to pop off the heatsink I inserted an exacto knife where that black glue is and just twisted a bit. That was enough to knock it off.
[Fire TV Original Android Development] Blitzritze:
Does anybody else have the Problem, that after the short the PC dont see the FireTV Stick 4k but its getting hot. I checked the S/N and its says ...VM122...

Edit: I figured it out and my FireOS Version is to high...
[Fire TV Original Android Development] Bullet Saloon:
Booted up fireiso-2.0.0-amd64.iso

Opened terminal in kamakiri folder

Ran cmd ./bootrom-step.sh (Terminal states "Waiting for Device")

Plugged in FireStick 4K (Terminal STILL states "Waiting for Device")

Not sure why the script won't run? This is a brand new 4K firestick out of the box.

Serial is VM088.
[Fire TV Original Android Development] Meierhansen:
Maybe try another USB cable and another USB port?
[Fire TV Original Android Development] Bullet Saloon:
Tried using different usb cables and ports. It shows up on the left side of screen (AFTMM) but the script won't run? Tried different PC, finally the script ran, with errors.

Thanks
[Fire TV Original Android Development] Bullet Saloon:
This FireStick 4K came with OS 6.2.6.5 pre-installed. It now has 6.2.6.8.

AFTMM doesn't show anymore on left side of screen..."Waiting for device"
[Fire TV Original Android Development] Bullet Saloon:
I was able to root this FireStick 4K. I had to short it. When the script told me to remove short and hit enter, I left the short in place. That was the only way I succeeded on this stick.

First ever attempt at this, and it took me a lot longer than it should have. Never give up :)
[Fire TV Original Android Development] boxster03:
Hi thanks for all the devs and contributors in this thread.

4K I bought from Amz in Feb'23 came w/ OS 6.2.9.2. (I used voice menu trick to not update at initial setup) and it has VM142xxx serial#. Anyone know if VM142xx is a later production than VM201xx?

Or is it possible my VM142xx 4K stick somehow managed to update to OS 6.2.9.2 at initial setup despite my disconnecting the internet via voice menu trick before registering w/ Amz?

If I find a lower # than VM20113xx in a store, is it a possibly rootable 4K stick? Is OS 6.2.8.1 rootable ? or does it have to be 6.2.8.0 or earlier?
[Fire TV Original Android Development] Travel_Mate:
Well, as I recently understood that also wireless mouse will do the trick, I decided to try and... Nothing... Created bootable usb with rufus, it boots to a blue screen with choices to load in ram. to continue from usb etc... And started sth without graphic, command line full of errors...So I saw filename is amd64, I'm with intel, could this be the problem?
[Fire TV Original Android Development] Bullet Saloon:
Boxter03 asked: "is it possible my VM142xx 4K stick somehow managed to update to OS 6.2.9.2 at initial setup despite my disconnecting the internet via voice menu trick before registering w/ Amz?"

If it downloaded the update while setting it up, it wouldn't be installed until next re-boot. This adb command will clear what has been downloaded before you reboot >> adb shell pm clear com.amazon.device.software.ota
[Fire TV Original Android Development] ItsBabaYaga:
Just out of curiosity is it at all possible to use this method for non 4k fire tv stick 3rd Gen ?
[Fire TV Original Android Development] Sus_i:
[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

FireOS < 7.2.7.3 required
[Fire TV Original Android Development] insestito:
Hi guys, something new for 4K Max?
[Fire TV Original Android Development] joshyakadamien:
Hey Guys,

First of all, thanks for the development/journey.

As i see it was quite a ride...

I'd like to have myself assured if i grasp it correctly:

since 2.0 version, the script works w <6.2.8.7 without sorting?

have a mantis (VM242) on 6.2.8.1 and would love to have twrp to go to different os es...

Thank you in advance.
[Fire TV Original Android Development] Bullet Saloon:
I had a 6.2.6.8 that wouldn't root without shorting. Not sure your 6.2.8.1 is rootable. I would short it, and try.
[Fire TV Original Android Development] Sus_i:
6.2.8.1 will unlock fine without the need of any shorting...