yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] bibikalka:
Have an unlocked Fire 4K 1st gen where MMC flash appears to have gone bad:

Fire stick 4K first gen, EMMC appears bad

So I have this 1st gen BL unlocked Fire 4K stick purchased at the end of ~2018. I unlocked it with the shorting method back in time (~2021). Anyway, recently it just went dead - no display at all. I re-ran the unlock, using the more advanced...

xdaforums.com

Re-ran kamakiri again this morning - it goes through ./bootrom-step.sh with good messages, but then does not reboot to fastboot. Pre-existing TWRP does boot as before, I can reboot to fastboot from there manually, but cannot reboot to "hacked BL", it goes back to recovery.

I can tweak bootrom-step.sh to upload cache/userdata images to the device (will be painfully slow), not sure it'd save it though.

Any more ideas?
[Fire TV Original Android Development] Bullet Saloon:
Can anybody kindly tell me the new way to mount my exFat usb drive to my 2nd gen Firestick. I'm rooted and on software 6.2.8.1.

I have Stick Mount 3.50 working on two of my sticks, but now on my third, the additional compatibility files that stick mount automatically downloads and installs at first run no longer connects. (dead server). Without those additional files, stick mound won't work.

Thanks
[Fire TV Original Android Development] hasobist:
Hello!

Hope this helps:

'[KERNEL][FireTV Stick 4K] Custom Kernel For AFTV 4k - 6.2.9.4' https://xdaforums.com/t/kernel-firetv-stick-4k-custom-kernel-for-aftv-4k-6-2-9-4.4005087/

Cheers!
[Fire TV Original Android Development] Bullet Saloon:
I have the [KERNEL][FireTV Stick 4K] Custom Kernel For AFTV 4k - 6.2.8.1 installed on my sticks.

My usb doesn't mount on this last stick because Stick Mount can't download and install the add-on files any longer.

Are you saying I should install 6.2.9.4 if I'm not running that version? Thanks for your help
[Fire TV Original Android Development] hasobist:
Hello !

Try clear /data,cache of the said application,reboot to recovery clear /dalvik cache,cache and reboot,give it a try again.

If ain't works Titanium backup from your other stick where the app is working and restore in the one with problem.

Check the logs of the app as well ,may be missing something.

Cheers!
[Fire TV Original Android Development] Bullet Saloon:
Thank you. I'll see about Titanium Backup. I've never used it on my Firesticks but I'll see if I can find it.
[Fire TV Original Android Development] hasobist:
Hello!

If the latest ain't works for you go with the older versions.

Cheers!
[Fire TV Original Android Development] Bullet Saloon:
Props to hasobist for helping me. Thank you sir. :-)
[Fire TV Original Android Development] hasobist:
Hello!

Wonderful to know it worked for you .

Happy to help always........

Thank you

Cheers!
[Fire TV Original Android Development] SweenWolf:
Yes there is, use the bugged version of kamakiri, it will not give you any option for TWRP.

It is actually fairly easy and easier is to brick your stick.

There are posts on XDA about how to do it, you'll have to use Fastboot. (I think one was written by me and one by suzi)

I have attached a version of kamakiri in which the lk has a bug. so twrp will not show you the boot menu even if you have attached an OTG. This is also a TWRP flashable zip. BUT FIRST PLEASE THINK OF WAYS TO GET INTO TWRP IN CASE ANYTHING GOES WRONG WITH YOUR SYSTEM (YOU CAN USE CLH OR ADB IF YOU REMOVE TWRP BOOT MENU, BUT HOW WILL YOU ACCESS THEM IF YOU ARE STUCK IN BOOTLOOP)

FLASH AT YOUR OWN RISK.
[Fire TV Original Android Development] Bullet Saloon:
I have a 2nd gen FireStick Ultra 4k has GO7OVM201... and 6.2.8.0 preinstalled when I got it new. (It was the first stick I've seen that didn't need a short to run ./bootrom-step.sh. It also came with a brown inner case instead of black?)

It was working fine for a while, but I must have messed it up bad by flashing different roms. Now it is stuck on black screen with just white Fire TV logo

I have wiped dalvic/art, data, system, and cache.

I have run the gpt-fix in kamakiri.

I have changed the data and system format to ex2 and back to ex4 all to fix possible partition corruption.

I have flashed original stock rom and didn't lose twrp recovery.

Nothing so far has made a difference...still black screen with fire tv logo.

Has anyone had this issue? Any suggestions?

Thanks
[Fire TV Original Android Development] story:
I have two Firesticks (Mantis) from few years back and they were short hacked. They've been working fine for me for past few years. I was forced to factory reset one of them and things aren't as smooth. I am waking up to the FireTV in recovery by inself in TWRP. I have root access and Fire OS 6.2.8.9

What's new in 2024?
[Fire TV Original Android Development] Bullet Saloon:
I think my Vendor Partition is corrupt. I tried restore from working backup....no go.

I tried fastboot format /vendor and got error....Formatting not supported for file system with type "
[Fire TV Original Android Development] bibikalka:
My 2018 mantis has gone bad too - probably flash memory. Could not write anything to /data or /cache

Fire stick 4K first gen, EMMC appears bad

So I have this 1st gen BL unlocked Fire 4K stick purchased at the end of ~2018. I unlocked it with the shorting method back in time (~2021). Anyway, recently it just went dead - no display at all. I re-ran the unlock, using the more advanced...

xdaforums.com

You could try mtkclient to re-write /vendor:

GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool

MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.

github.com

It needs python3.8 to run properly, so install that. See here:

How to downgrade python from 3.10 to 3.9 on Ubuntu, WSL

I need to downgrade python for a project. Unable to downgrade from 3.10 to 3.9 on Ubuntu, Windows Subsystem for Linux.

stackoverflow.com

Basically, mktclient wants python 3.8, so one adds another python version on Ubuntu, and then uses this command to add modules to it : "python3.8 -m pip" instead of the direct "pip" one.

Then it is missing a module too:

ModuleNotFoundError: No module named 'Cryptodome' · Issue #1 · DP-3T/reference_implementation

Unable to run example_run.py

github.com

So the command to fix that was

"python3.8 -m pip install pycryptodomex"

Update:

With python3.8, here is how you build it - notice the different command from the github:

git clone https://github.com/bkerler/mtkclient
cd mtkclient
python3.8 -m pip install .

Then continue with the rest of github instructions.

To run the gui, do this:

python3.8 mtk_gui
[Fire TV Original Android Development] story:
I have two fireTV 4K and both busted passed 2 days. One is always used and one is in the basement almost never used. I had to replace one busted one with the basement one.

It died overnight.
[Fire TV Original Android Development] hafren:
I just bough a new 4k firestick but unlike my existing ones this is made in Vietnam and has a Serial code # G4N0VM... Is this a mantis version and vulnerable to unlock/root?
[Fire TV Original Android Development] hasobist:
Hello !

If the stick is bootable, you can check the details of the same in settings,with no access to internet to avoid updating the same.

Cheers!
[Fire TV Original Android Development] bibikalka:
Interesting, some of us were wondering what these different serial #'s meant. Many pages back one of the users unlocked this type of a serial number - read a few posts below the initial one:

[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...

xdaforums.com

Any idea when it was manufactured?
[Fire TV Original Android Development] bibikalka:
So I did kamakiri on a dead one like the one you got. It revived the stick for a couple of weeks - then /data went bad. So try kamakiri-mantis-v2.0.1.zip with the updated instructions, and see what you get. Remember, you no longer need to open it to run kamakiri:

[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...

xdaforums.com
[Fire TV Original Android Development] SK4G:
I have a FTV Stick on 6.2.7.1 firmware. Notably, it is missing the new Fire TV interface introduced in later updates.

How can I get the new interface? is it still not recommended to update to newer versions due to blowing the efuse?
[Fire TV Original Android Development] hasobist:
Hello!

If your stick is unlocked,the patched 6702 is the latest by Skel40 safe to flash followed by SweenWolfs patch for accessibility,Launcher support and other features to be unlocked.

Just go through the instructions in OP of the respective threads.

Cheers!
[Fire TV Original Android Development] hafren:
@hasobist So went through OOBE using Ighor's dns update blocking and settings show os at 6.2.9.8 (6298/4760) ftv home v6450027.1. Enabled adb & shut down. Reboot trial showed installing security updates so pulled plug. Maybe Ighor dns blocking was ineffective. Any advice if I can unlock/root?
[Fire TV Original Android Development] SK4G:
@hasobist Thanks for the info. I updated to the firmware you suggested and everything is working great
[Fire TV Original Android Development] hasobist:
Hello!

Wonderful it worked for you!

Thank you.......

Cheers!
[Fire TV Original Android Development] hafren:
@hasobist @bibikalka

So went through OOBE using Ighor's dns update blocking and settings show os at 6.2.9.8 (6298/4760) ftv home v6450027.1. Enabled adb & shut down. Reboot trial showed installing security updates so pulled plug. Maybe Ighor dns blocking was ineffective. Is there anyway to get twrp and magisk on this?
[Fire TV Original Android Development] hasobist:
Hello @hafren !

By any chance is your stick unlocked?

The sticks running firmware version 6281 and lower can be unlocked.

Cheers!
[Fire TV Original Android Development] bibikalka:
It's possible you killed it when you pulled the power on it while updating. I had an update slip through - even though I am blocking things on my router just like Ighor does.

What sort of serial number to you have, can you give the first few symbols including something like ...VM223 ?
[Fire TV Original Android Development] hafren:
I'm hopeful it's not dead or if so I'll return it. Anyway my serial is G4N0VM14311xxxxx and I was hoping to unlock based on my earlier questions but am now unsure as its on os 6.2.9.8. Is it possible to get TWRP on it?
[Fire TV Original Android Development] hafren:
Its a new sick so it wouldn't be unlocked that is why I asked my question, post 2562, hoping for advice on how I could get twrp on it. As mentioned it reports os 6.2.9.8 so am unsure if there is any unlock method I could apply.
[Fire TV Original Android Development] hasobist:
Hello @hafren !

Give the unlock a try,there's nothing to lose besides with the new unlock you ain't need to open the stick as well.

Download kamakiri 2.0.1 from the unlock Firetv 4k thread and follow the instructions of Sheldon unlock Firetv 3rd gen.

Let me know the reults.

Cheers!
[Fire TV Original Android Development] ViktorSl:
Hello @hafren !!

Post #3 says kamakiri ain't work above 6.2.8.7. It unpossible to unlock.

Cheers!!
[Fire TV Original Android Development] Bullet Saloon:
I set up a new stick from scratch, running 6.2.8.1 rooted with magisk 27.0. Everything is set up perfect, except every time I install Kodi my stick bootloops with the animated swirl and gets hung up there? Kodi works perfect on my system, until I reboot.

Any suggestions will be appreciated.

Thanks
[Fire TV Original Android Development] Bullet Saloon:
I got it. I had to use an older version of magisk (24.2) to set it up right. All good now. (y)
[Fire TV Original Android Development] k4y0z:
It's not really clear why this has fixed the issue, the only difference in the script is that it dumps boot0 after writing it and before rebooting.

The original script reboots right after flashing boot0.

So it might have been some kind of issue with flushing.

About the green screen, that does sound like a HDMI or HDCP issue.

I would recheck all the cables first.
[Fire TV Original Android Development] k4y0z:
[MENTION=1047674]aasoror[/MENTION] [MENTION=5665338]kigba[/MENTION]

If one of you could please try with the attached zip, if it still works.

Instead of dumping boot0 this one just adds a delay of 5 seconds before rebooting.

If that works, I can update the OP.
[Fire TV Original Android Development] aasoror:
I checked direct hookup to 3 different displays one of which was used for the initial setup (two 1080p and one 4K, and in all cases the display reports receiving matching signal).

Will look into flashing the pre-rooted firmware image and doing a factory reset to see if it makes a difference.

thanks for all the help k4y0z.
[Fire TV Original Android Development] X04D:
So I did something that I now know is stupid (from reading another thread). After installing MM, I updated Magisk, and now my FireTV gets stuck on a black screen with "FireTV" on it. None of my computers detect it with adb devices, anymore. Any ideas?
[Fire TV Original Android Development] hyperblu:
Anyone have the factory recovery images? I'm having the Amazon license error issue. Apparently Amazon checks their content against their BL's to see if they're signed because I can't for the life of me figure out what is causing this. I'll have to remove twrp, revert back to stock image and go through the updates before running the exploit.

---------- Post added at 04:12 AM ---------- Previous post was at 04:07 AM ----------

I'm fairly certain that Amazon content is "fused" to the bootloader when it runs updates. Running a prerooted rom won't pop the fuse, per say, but if it updates and notices the bootloader or recovery has changed, fuse is blown and content is cut.
[Fire TV Original Android Development] k4y0z:
https://d1s31zyz7dcc2d.cloudfront.n...dle-mantis-NS6265_user_2157_0002852679044.bin

No reason to remove TWRP.

Not sure what makes you so certain of that.

My stick has updated fine with TWRP installed and still can access amazon content.

I haven't used prerooted ROM though.
[Fire TV Original Android Development] hyperblu:
Not on prerooted rom. I ran the exploit before I set the stick up, which inadvertently caused me to update before it finished. Amazon content has license errors on all amazon content now.

I've done a factory reset and went through setup all over again, same issue. I've tried deregistering the stick and same issue.

---------- Post added at 04:29 AM ---------- Previous post was at 04:22 AM ----------

I may not have been very clear on my last statement. I'm saying when a signed factory image is being installed it checks against the previous bootloader/recovery to see if it has changed and pops the fuse if it has, unless this is just an isolated incident that is solely this single update that made changes to something it needed from the bootloader.
[Fire TV Original Android Development] k4y0z:
I doubt this has anything to do with the bootloader.

As I've said previously my stick has updated fine with TWRP and Magisk installed and prime still works fine.

Try installing the stock file I linked to and do a factory reset.
[Fire TV Original Android Development] aasoror:
I think it works.

Also the green screen was fixed by flashing the prerooted firmware (I guess the stock firmware was corrupted or something).

---------- Post added at 10:36 PM ---------- Previous post was at 10:34 PM ----------

There might be more into it, several reports on the pre-rooted firmware thread about prime video failing with a license issue, yet several other confirmations that it does work fine.
[Fire TV Original Android Development] hyperblu:
This also only seems to happen when there is a pending update from Amazon. If you're up to date, you're good.
[Fire TV Original Android Development] rbox:
It looks like i'm getting the LICENSE_ERROR as well on Amazon content. I was on version 6.2.6.3 or something like that originally. Then flashed my prerooted 6.2.6.5. My rom doesn't include anything in the images directory. Is it possible tz needs to be updated? It looks like you said you've flashed the full 6.2.6.5 and everything is fine?

I find some errors in logcat:

I'm getting the 6.2.6.6 right now. Let me see...
[Fire TV Original Android Development] k4y0z:
Did you try it?

As said, I am not using the pre-rooted firmware, so I can't say much about it.

Then why don't you install the update?
[Fire TV Original Android Development] hyperblu:
Thank you rbox.

Like I said, the exploit is the only thing I've done. Had I let the stick fully update before applying the exploit, I'm sure this would all work fine assuming I stick to prerooted ROMs afterward. This is why I'm wondering if I have to remove twrp and go back to stock recovery, allow it to update, then run the exploit and continue on with prerooted ROMs.

---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------

K4y0z, I'm fully up to date now. After the update would install and reboot, twrp would patch it, and reboot up-to-date. But I'm assuming minus a few things. It acted really strange when trying to update, would say it was going to reboot, go back to home screen, I go back and it says it was one version higher, then blip back to "finishing updates". Just weird all together.

I didn't install the update because I applied the exploit on the very first time it was plugged in before it even set up. I figured unlocked was "unlocked" and I could go back and forth between ROMs as I please... Generally, that would be the case, but something didn't crossover with the updates.

---------- Post added at 05:00 AM ---------- Previous post was at 04:51 AM ----------

@rbox do you have a PayPal? I sent [MENTION=7104332]k4y0z[/MENTION] a donation and tomorrow is payday and you whipped up a prerooted rom quickly, so... ? As always, y'all's efforts are greatly appreciated.

---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------

@rbox do you have a PayPal? I sent [MENTION=7104332]k4y0z[/MENTION] a donation and tomorrow is payday and you whipped up a prerooted rom quickly, so... ? As always, y'all's efforts are greatly appreciated.
[Fire TV Original Android Development] rbox:
Thanks! There is a Donate To Me button on the left side of my posts.
[Fire TV Original Android Development] hyperblu:
[MENTION=3991724]rbox[/MENTION] I mean you have to be up to date before running the exploit. If you have a pending update and you allow it to go through post exploit, it triggers the license issue.
[Fire TV Original Android Development] k4y0z:
Yes I am on stock 6.2.6.5 with Magisk 20.0 and prime is working fine.

Your log seems to suggest issues with DRM but my TZ is the same that is being used by the unlock.

You can try updating preloader and tz, although I can't guarantee that the unlock will still work and you may have to redo the unlock.
[Fire TV Original Android Development] rbox:
Well something broke. I tried flashing 6.2.6.6 and I just get stuck on the white firetv logo. twrp through OTG cable still works so i tried flashing 6.2.6.5 back, still the same thing. I tried factory reset, still the same thing. adb is alive although both shell and logcat complain. I'll have to look at it more later.
[Fire TV Original Android Development] k4y0z:
This is strange, I just let the 6.2.6.6 update run through (OTA) and everything still works fine, including prime.

Did you flash the stock 6.2.6.6 or did you modify it?

When you flashed back 6.2.6.5 did you reinstall magisk?

If your system is modified it will probably not boot without magisk because of dm-verity.
[Fire TV Original Android Development] rbox:
I modified it. Magisk was supposed to automatically flash, but now that I think about it, I wasn't paying attention and it's possible it didn't flash. dm-verity does sound like a problem, because it seems like /system isn't mounting based on the errors adb was giving me. This gives me something to work with. Thanks.
[Fire TV Original Android Development] hyperblu:
So how would one go about loading this .bin file? Where does mantis store them? Cache? Which folder?
[Fire TV Original Android Development] bibikalka:
So whatever happened to the new remote and the older ROMs below 6.2.8.0 ? Is there a way to make the remote pair or keep paired? Some config files to save on the new version, and push back to the older one?
[Fire TV Original Android Development] Skel40:
I looked at two priv-app packages for remotes, com.amazon.tv.turnstile, and com.amazon.fireinputdevices. Turnstile is for the remote version while the fire input is for pairing the remote. It would be possible to test under these two in replacement to the older version.
[Fire TV Original Android Development] bibikalka:
Sounds like I could user upgrade these, pair the remote, then remove updates. And see if that works. Will test soon!
[Fire TV Original Android Development] bibikalka:
It's the weirdest thing! I had mantis 6.2.9.2 which I paired with the new style remote. Then I cloned a 2.7.7 stick onto this one, everything, including /data and /cache, with dd. And, about 60 sec after booting up this cloned 2.7.7 it found its previously paired remote without any problems.

I did not have to replace anything anywhere - same ol' 6.2.7.7 . I wonder if Amazon keeps remote info in the cloud as well as on the device itself.
[Fire TV Original Android Development] pezzni:
Seems like I have everything in my environment right -- using FireISO 2, serial number's right (GO70VM159xxxx) and I'm on 6.2.6.5 but it seems lole kamakiri doesn't want to work for me (trying without shorting btw). I plug in the stick, run ./bootrom-step.sh and am stuck on "Waiting for device."

Anything else I should try?
[Fire TV Original Android Development] hasobist:
Hello @pezzni !

Download the Kamakiri 2.0.1 from Firetv 4k thread and follow the instructions from the Sheldon,firetv 3rd gen unlock thread.

Try the rear end USB ports of PC.

It takes more than a try,keep it going.

Hope it help.......

Cheers!
[Fire TV Original Android Development] pezzni:
Yeah, I did follow the directions in that thread. Haven't tried using a different PC yet or different ports -- was using my laptop.
[Fire TV Original Android Development] hasobist:
Hello @pezzni !

Just type lsusb and check the stick is recognised.

Cheers!
[Fire TV Original Android Development] pezzni:
Yeah it is (it can even listen to ADB commands when its fully booted up)...
[Fire TV Original Android Development] hasobist:
Hello @pezzni !

If it's not updated to firmware >6280 should be fine.

Try unlocking again !

If it fails with fireISO try using a USB bootable Ubuntu works as well.

Cheers!