yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] yan2xme:
run the command while turning on usb debugging and reboot to recovery? and connect it to my computer to push and install it? thanks

please pardon me for some silly questions that maybe very easy to you guys...
[Fire TV Original Android Development] Sus_i:
No problem. Here is a newbie guide ;)

https://xdaforums.com/t/newbie-guid...root-and-install-addons-firestick-4k.4015273/
[Fire TV Original Android Development] rpmuploads:
I did 'idme copy' because I don't kown how to wipe. I had already tried to flash kd/dkb partitions with a copy from another device, but the 'fastboot flash kb ...' throws the error 'partition does not exist.
[Fire TV Original Android Development] Rortiz2:
the partition table is case-sensitive, try with "KB" (with caps).
[Fire TV Original Android Development] jerian01:
hi everyone,

so i performed the exploit all went well. i would like aa good rom to load o my 4k. Can anyone recomend one?
[Fire TV Original Android Development] Bertonumber1:
Short answer is No.

Currently we only have prerooted or manual rooted stock amazon fireos firmware. There is a Lineage 14.1 rom which is WIP (work in progress) however this is unlikely to be further developed anytime soon.

There are a few Android TV builds kicking around which you can install as Magisk Addons this will give you an android tv feel, there is also Google services available.

Furthermore there is a build combining both the above which you can restore via a TWRP backup... This can be found here :

https://xdaforums.com/t/guide-rom-mantis-fire-tv-stick-4k-prerooted-android-tv-rom-6-2-7-6.4208859/

Regards
[Fire TV Original Android Development] jerian01:
thank you for the quick replly. Iwould like playstore ad chrome
[Fire TV Original Android Development] Bertonumber1:
No problem, all of this is included Google playstore and lots of other stuff you can install brave browser (adfree version of chrome) yourself or if you prefer the original you can stick with that.

If your unlocked already just head to the link I've provided and download the zip extract it to TWRP >BACKUPS on the 4K STICKS /sdcard and then restore the backup.

Regards
[Fire TV Original Android Development] jerian01:
thank you brotther will try.
[Fire TV Original Android Development] jerian01:
Brother the download somehow fails. Can't download that file
[Fire TV Original Android Development] bibikalka:
@k4y0z @kenmac96 @I_CRAFT @kenmac96 @marcge 63 @h1ghfrequencywavform @Androoit @navin23

VM190 serial / blocked BootROM

Can anybody with a failed BootROM attempt (serial containing VM190) run this command and post the output:

adb shell
cd /proc/idme
for f in board_id manufacturing serial; do echo $f; cat $f; echo ""; done

The idea is to figure out if board_id has changed between the working/non-working versions.

Here is my output for a working 4k stick (X is obfuscation):

board_id
2902001400130018
manufacturing
P071HG0584XXXXXX
serial
G070VM08844XXXXXX
[Fire TV Original Android Development] Bertonumber1:
Perhaps contact the OP??
[Fire TV Original Android Development] jerian01:
Also another thing. Can this procedure work on the FS tank 2? I have two there that are bricked stuck on the logo. How can I debrick them? Any info is appreciated
[Fire TV Original Android Development] Rortiz2:
Please do a quick search before asking such questions. You are looking for https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/
[Fire TV Original Android Development] jerian01:
My appologies, for any disturbances caused
[Fire TV Original Android Development] Bertonumber1:
Bollocks, you think I would post a dead link?? Link is working fine mate.
[Fire TV Original Android Development] jerian01:
thank you got thru
[Fire TV Original Android Development] jisgore:
i'm having an issue, hopefully you guys can help me.

I followed the guide and successfully installed TWRP. I did a factory reset with dalvik, cache and system because I didn't have enough space to pass the files to restore the backup from the other post. i was able to get to the point i could use adb at this point, but after that the fireTV is stuck at fireTV white logo.

I can still get into TWRP when i have the OTG cable connected. I tried mounting the sdcard from TWRP but my PC doesn't detect it, not even from the adb command line or sideload.

Before when the Fire Stick was connected without the OTG cable I could see it on the command line. Not anymore.

If i connect a USB HUB with the mouse and a usb with the files from the backup while using the OTG cable will TWRP detect the usb as well? If this is not an option how could i solve this?
[Fire TV Original Android Development] bibikalka:
Connect OTG/mouse first, hit OK to enter TWRP. Then pull out the mouse, connect the USB hub, plug in the mouse, and an SD card reader into the hub. So you'll be in TWRP with the mouse and your storage. The reason to do it like this if the hub connect is too slow, and the 5 sec TWRP window passes. But yes, with a hub it should recognize all attached USB devices.
[Fire TV Original Android Development] Bertonumber1:
Please note this build requires you wait at the amazon logo for some time before the rom loads at first boot. this can be upto 10 minutes on the white amazon logo.

There is no problem, the guy who posted the backup used skel40' build.prop tweaks which in turn disable the boot animation. This means it causes the effect of what appears to be a brick when it isnt . Just leave it to boot up and all should be good .

you can disable this by reediting the build.prop easily
[Fire TV Original Android Development] Volectorus:
I just picked a 4k from target, and assumed this was an older unit, but

its not responding with the short . is this potentially a newer unit with out an exploit?

G4N0VM07050410BE
[Fire TV Original Android Development] Bertonumber1:
Your device is vulnerable to amonet. This means it can be unlocked/rooted.

Make sure youre applying the short correctly...

Best to use a piece of rolled up tin foil for this.
[Fire TV Original Android Development] Volectorus:
Great! I have done 3 others in the past and have not had one this stubborn yet. Usually I can get it in a few tries, but I was at it for a good 15 mins before I had to leave for work.

The part that's throwing me off is when it's not responding at all when shorted

The download for the tools did hang when downloading, so I'll start from scratch again.

Do we have a compiled list of variants on the firestick 4k that are unlockable yet? I saw lists for non 4k, but couldn't track one down for the 4k.
[Fire TV Original Android Development] Volectorus:
Still no dice, I suspect the serial number is misleading ad might be a newer release. It's not responding when shorted. Just waiting for bootrom
[Fire TV Original Android Development] Bertonumber1:
What is the serial number when you run adb devices ?

Let the stick boot normally and enable adb in settings>developer options .

Then in command line - terminal run:

adb devices

It has to be a shorting problem or cable/USB problem.

Let us know what serial is

are you using the newest fireiso?

regards
[Fire TV Original Android Development] coop5796:
Hello, so I have been fighting with attaching the foil. I finally used a small plastic tool to bend the corner of the aluminium housing to where I could get a better look. I then realized I don't seem to have a data 0 section like the picture. I do have the other capacitors for clock and cmd. As others had previously mentioned I have a sandisk in previous post for the chip above these capacitors. My serial number is not above VM190. It however does not appear to show up as a usb device when shorted. Not sure if they are any way to unlock the bootloader? I bought this stick in Feb 2021. I am thinking maybe i got another revision and with a slightly different board. It appears to be the 2018 model though so I don't get it. Not sure how helpful this picture will really be. Was hoping I could throw a custom rom on this. Any help would be appreciated. If anyone does have any ideas.
[Fire TV Original Android Development] Bertonumber1:
@coop5796 Yes your stick looks identical to mines but they all do, don't they? I've had several mantis like yours that didn't want to short so

I wouldn't give up just yet..

Make sure you have tested different amonet zips from OP (extract them straight to fireiso desktop and run terminal within)

Be sure to use the most recent version of fireiso. Also try other USB ports and cables before ruling the exploit out.

What serial is displayed in terminal when running :

adb devices

You should've used the metal shield you have bent back to wedge the aluminium foil in between, as this acts as a perfect gnd point.

I can only suggest you try and short it by bending the shield back to where it was, wedging the foil inside while you do so.

Try making sure you short the resistor before the shield (so you cover all them) ,

I have always wedged the foil in to cover the resistor on view before the shield so it covers each one....

(not too tightly or you won't be able to remove it in time for the **remove short ** prompt)

Also try using a gnd point outside of the stick like the Hdmi

Then run:

./bootrom-step.sh

Regards

Edit : This serial number being above 190 **** is just an assumption. IT SHOULD NOT be used as a bona fide way of indicating if a stick is vulnerable or not. It is just a guideline and estimation of the time when amazon began churning out devices which had dl mode disabled.
[Fire TV Original Android Development] Michajin:
I am pretty sure about all of the firestick4k's bought in the last 6+ months have the bootrom disabled. I don't know of any real custom roms for this, just mods for the launcher. I would suggest you look for a used one on a auction sight if you want access to unlock.
[Fire TV Original Android Development] Cook80:
Hi here is my output from my firestick4K which i am not able to root....
[Fire TV Original Android Development] Androoit:
I confirm the misleading serial number. Amazon seems to try to confuse us or started a new production line

I tried rooting a device, bought around one month ago on Amazon.de

serial: G4N0VM0710****UX

Device doenst show up at all while shorting using lsusb. Kamakiri doesnt respond to it.

I rooted multiple devices and tried it different times with this stick, so i can say for sure its not a short or a cable connection problem.

Must be a patched device. If patched over the air (e-fuse) or produced this way i cant tell. Software Version was 6277 user 3033, was on latetest OTA update.
[Fire TV Original Android Development] Androoit:
board_id

2902001400130018

manufacturing

P4N25G021****ANL

serial

G4N0VM0710****UX

I was not able to root this device. Doesnt show up on lsusb while shorted. Device bought around mid-february 2021 on amazon.de
[Fire TV Original Android Development] Bertonumber1:
Yeah you need a device around 2019 latest October / December 2019 . After that date (approx) then you are into the new hardware revised editions. If you are looking for an exploitable device then your best bet is to try and source one from places like fleabay or craiglists . Pretty difficult tryna source these cheap as people tend to sell them for funny money in respect of the 4K .

Regards.
[Fire TV Original Android Development] chamicals:
Hello everyone. I rooted my fire stick 4k and used with Magısk and Google Play Store ROM and When I looked Magisk it needs update and updated it. I chose update from recovery

Then fire stick does not boot and (when booted first show recovery screen) does not show recovery screen

and I try to re rooted with folio and Linux things but not start fire stick when i plug the computer but when I plug TV's USB it's boots up and same issue

do you have any idea why does not start fire stick when I plug in USB PC ? tried two laptops windows linux
[Fire TV Original Android Development] Bertonumber1:
Ouch, you mean you chose "update" in the manager app? Then selected recovery installation?.

If this is so... Then you have bricked the device and will have to do the unlock steps in OP over again.

When using Magisk Manager to update Magisk zip version you ALWAYS have to boot to TWRP and flash the latest Magisk zip there.

The reason we have to use TWRP to flash Magisk zip is because Magisk Manager will patched the wrong partitions as it does not know the special twrp config (which boot/recovery partition) for mantis .

So redo the unlock and remember to use twrp to update in future :)
[Fire TV Original Android Development] chamicals:
in future i will never update magisk. thanks for reply but what do u think about why doesnt boot firestcik when pluhg usb power on pc on the other hand when plug tv"s usb it boots up
[Fire TV Original Android Development] Androoit:
According to my experience this is not entirely true. I bought 2 FTV Sticks 4K on late December 2020 directly from Amazon and they were shipped with VM180 and VM170. Maybe they started with other countrys then germany and changed the manufacturing process step by step.
[Fire TV Original Android Development] Androoit:
Power supply is to weak, USB on Laptops doesnt always delivers enough power for a flawless use. Try another USB port maybe 3.0 or greater or get yourself a USB Hub with an dedicated power supply. According to specs USB 2.0 should be able to deliver up to 2.5 W but thats not true on all devices. FTV 4K stick draws more then 3 Watt when powered on. voltage drop under load is also to consider
[Fire TV Original Android Development] Volectorus:
sorry for the late response, that serial number was pulled from ADB " G4N0VM07050410BE"

I was using the latest exploit and iso.

I managed to find a 160 from Office Depot, and was able to get it unlocked in about 5 to 10 mins
[Fire TV Original Android Development] elia866:
Hi Guys!

When I launch the command

./fastboot-step.sh

I got this error. Can you help me ?

Thanks!
[Fire TV Original Android Development] mc_crash:
So is rooting a fire tv 4k stick received from amazon in 03/2021 basically bunk for now? I also had the same issues as others in regards to the device not being detected when it was shorted.
[Fire TV Original Android Development] mc_crash:
G4N0VM0705331CVB is my device serial
[Fire TV Original Android Development] mc_crash:
Strangely, I found some sort of spring loaded button soldered onto one of the sides of the board, does anyone know what that button might be for?
[Fire TV Original Android Development] mc_crash:
I guess buttons isnt the correct term, but this is what they are
[Fire TV Original Android Development] mc_crash:
Nvm those are antenna contact points
[Fire TV Original Android Development] Bertonumber1:
Never saw this before,

It doesn't look as though its been professionally attached it looks kinda melted where it's been placed.

Maybe this stick has been with someone else and this is a way of shorting.......

Idk....... if its on the board maybe a button for recovery mode. Like a mask mode of sorts like we see in normal android tv boxes but this is purely speculation @k4y0z @Sus_i have you seen this before? This button.

I'm intrigued

With regard to the serial, I wouldn't go with using the serial as a judge to decide a vulnerable device, especially on a forum where amazon devs take note on a lot of exploits etcetera.

This serial number 190 bs was just a rough estimate of when Amazon began shipping out unmoddable devices that have dl mode /bootrom disabled
[Fire TV Original Android Development] mc_crash:
I'm not at the fastboot stage, unfortunately. I'm one of the people that can't get the the bootrom_step1.sh script to detect the device after shorting clk, as dat0 doesnt seem to be on my board.

But glad the photo might be an avenue of investigation
[Fire TV Original Android Development] Bertonumber1:
Sorry mate I was looking at a post further up there.
[Fire TV Original Android Development] bibikalka:
Anybody tried Magisk v21.4? In the search, I see a lot pointers to v20.4, but nothing on 21 ...

Comments?
[Fire TV Original Android Development] Skel40:
It's most likely due to the compatibility. You'd have to use a mouse after installing 21.4 because Magisk hasn't updated the Fire TV's remote layout to their version. It still partially works so I recommend using 20.4
[Fire TV Original Android Development] Sus_i:
Wait what? That can't be true... ;)

i.e. the fireTV remote works still fine (you don't need a mouse at all).

Magisk v21.4 works like a charm for me :)
[Fire TV Original Android Development] Bertonumber1:
Google magisk releases github.... Should be on bottom of first page or top of second.

Regards
[Fire TV Original Android Development] EgonVLC:
FireTV 4k from May 2020 here, serial number V160. Can't root: wont appear when shorted. Typical error when not shorted. Any chance of rooting for me?

I just want to downgrade to 6.2.7.6, later versions messed with audio (recompression to DD+, loss of PCM Multichannel)
[Fire TV Original Android Development] Sus_i:
A second-hand stick with an old serial number 'and' an old OS version is the best bet now...

Probably all 4k sticks (old stock and second hand sticks too) get bootrom blocked with the latest update, 6.2.8.0.
[Fire TV Original Android Development] EgonVLC:
Indeed!

Amazon blows eFuse on Fire TV Stick to prevent downgrading to old interface

The new Fire TV interface is currently rolling out to most Fire TV models via the latest operating system update. While there has never been an official way to roll back a Fire TV software update, Amazon seems to especially want the new interface update to be a one-way path.

www.aftvnews.com
[Fire TV Original Android Development] higogo:
Hi there,

I have a FireStick 4k, one of those that serial # starts with G070VM1190xxxx.

Is this one of those that can't be unlocked?

It is stuck on Amazon white logo screen.

I tried adb but I get unauthorized.

Tried OTG cable with keyboard and no luck.

Device is not rooted.

Any suggestion?
[Fire TV Original Android Development] HarmfulMushroom:
Looking forward to testing this out later on, thanks for the share!

Coincidentally, looks like they're back on sale on Amazon, just in time for this release!
[Fire TV Original Android Development] kigba:
no Unfortunately. No HACKED FASTBOOT on TV. Yes, I connect the stick to the TV with the power supply. But the TV writes - "there is no signal." In the menu for selecting inputs, TV hdmi active, if you remove the stick, the hdmi input becomes inactive. As a result, the type of "classic" brick.

connected the stick in windows - the Mediatek com port appeared. Periodically falls off and connects again with a frequency of less than 1 minute. Connected Putty - nothing in the console, black window. A space on the keyboard causes a "!" And nothing happens.
[Fire TV Original Android Development] LuCkyCn:
I did the same thing. I used a paper clip and it sorted right away. Not sure why people are cutting it ?
[Fire TV Original Android Development] puppinoo:
Amazing

Just to say thanks. Rooted my 2 Sticks 4k. Quick question: I live in Italy and one of the sticks is imported from US. Can I turn it into an italian one (Actually everything seems to work except alexa).

Thanks again for this excellent job.

Pino.
[Fire TV Original Android Development] hyperblu:
I literally snipped back a small notch to get a straight shot down to the test point. Nothing was damaged nor did it affect the shield snapping back on. Everything went back together as it should.
[Fire TV Original Android Development] GabbyWC:
This is some great work happening here. Is anyone willing to film and upload a video of the full unlocking procedure for this device on to YouTube? The pictures of the less risky shorting methods are helpful but a high definition video that shows how best to open the device and perform the shorting procedure would be even better.
[Fire TV Original Android Development] hyperblu:
The cover pops off with just your fingernail. The heatsink snaps on to the shield that is soldered to the board. To remove the heatsink, you want to gently pry back the metal tabs that mesh with the shielding to hold it in place.

I found the best access was toward the HDMI port. Once you have some of the heatsink tabs pried outward, you can simply lift up and pry the heatsink off with your fingers. Bend the heatsink tabs back in their original position after removal so they will snap back over the shield that is attached to the board.

---------- Post added at 02:56 AM ---------- Previous post was at 02:50 AM ----------

If the other stick is the 4k version, you should be able to create a backup image of the Italian one and load that image to the US version using twrp. Assuming the internal components are the same, I don't see why that wouldn't work.

---------- Post added at 03:45 AM ---------- Previous post was at 02:56 AM ----------

This is not my lucky day. Couldn't find my OTG cable for TWRP. Found it, dug out my Rii keyboard, battery is dead, look for ancient mini USB wire, don't have one, dig out my Anker wireless keyboard, no adapter... FML.
[Fire TV Original Android Development] rbox:
I'll look in to it.
[Fire TV Original Android Development] vetmike:
Does anyone have a stock image available?

I bricked my Firestick 4k installing Magisk the wrong way (DO NOT install the boot patch from Magisk Manager!). I had to reinstall recovery/TWRP and need to reinstall the OS next I believe.
[Fire TV Original Android Development] vetmike:
Great to hear, thanks for your work [MENTION=3991724]rbox[/MENTION]! I used your ROMs on the tank Firestick and they worked flawlessly.
[Fire TV Original Android Development] GabbyWC:
Thank you for the detailed instructions. I think I can visualize what you've described here but having a video as a guide to disassemble the unit would still be ideal.
[Fire TV Original Android Development] Sus_i:
me too ;) found my logitech k400 keyboard with dead batteries, one of them leaked out, ruined the internals...

Remember that warning from OP:

You may do the shorting/unlock with the two scripts again, i.e. restore the kamakiri patched boot.img.

That will fix your stick, no need to flash a new system :good:
[Fire TV Original Android Development] Vency77:
Sorry if I missed it but does this work for the non 4k version of the latest stick?
[Fire TV Original Android Development] ForForkSake:
About to purchase one of these, thanks for your hard work.

Do you know of anything similar for Amazon Fire TV 2 box (Sloane)

Mine froze in TWRP as system was formatted and a new rom installing.....

I have the updated preloader, which isn't allowing [MENTION=3991724]rbox[/MENTION] unbrick img.

so hangs on the white amazon fire tv logo as nothing to boot into.

Its now a brick, so I don't mind soldering/desoldering just not sure where to start and if it's even possible in this situation...
[Fire TV Original Android Development] Sus_i:
You may take a look here :good:

I asked something similar ;)
[Fire TV Original Android Development] k4y0z:
There is nothing ready to use, but since it's the same SOC as suez the bootrom-part from amonet-suez should work:

https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639

You will need to find the right spot for shorting and modify the scripts to flash the proper LK,PL and TZ.

You can use it to downgrade to an earlier version.
[Fire TV Original Android Development] ForForkSake:
Awesome. Hopefully try it this evening. Will let you know how I get on
[Fire TV Original Android Development] c3po_droid:
Very helpful and interesting post, thank you very much!

So... since you had some ntfs success by using StickMount, this implies that FireOS has actually the ntfs-3G library included, if I'm not mistaken. Reading a bit about StickMount it seems to me that it uses the systems ntfs-3G driver, instead of prividing its own. If that is correct, than a simple mount script might work for ntfs, as soon as somebody figures out how to initialize it automatically. But is it actually a fact that FireOS has (a dorming) ntfs capability out of the box then?
[Fire TV Original Android Development] Skel40:
It's exploitable. If you have VM1900 or higher, it's patched. I have about 3 Fire TV 4K's one of them with 1600 and 1594