yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Sus_i:
This is a very user friendly solution, don't be afraid ;)

Temp bricking mean that the preloader gets wiped, so the box will stuck in bootrom mode... Then you can run the bootrom script from amonet 'without opening the box and without any shorting'

The whole process gets a lot easier and faster, only an usb a-a cable is needed.

But the preloader gets only wiped if your images (preloader, LK and TZ) on the box are too new, i.e. updated via the stock recovery via OTA to 5.2.7.3 or newer. In this case the bootrom step is necessary because all these images and the rpm-block need a downgrade.

Anyways, since you box is prerooted long ago and since rbox never updated the TZ/LK/PL images in his sloane roms (they are not included, I just had a look into 5.2.7.3 and 5.2.7.6 prerooted), your box wont need a temp bricking (or an usb a-a cable) at all ;)
[Fire TV Android Development] Han-Droid:
thank you so much for your nice help! I am not in a rush and I won't risk to brick my box during the holidays. I will get into that in a couple of days :-) I will probably write down a fool-proof step-by-step bullet-point list. Still not sure about those scripts...so...I might be asking you again, soon! haha!

merry x-mas or whatever you'll enjoy!
[Fire TV Android Development] Bertonumber1:
Nothing to worry about mate, half the works done given the fact you're already rooted. Just as @Sus_i says the temp bricking is all part of the magic.

As long as you follow the steps to the letter you'll be okay.

I've bought a few of these boxes for the house and each one is unlocked via this method.

Regards
[Fire TV Android Development] teamfresno:
I've been coming to this thread for the past year; only looking at the first page to see if there's an updated pre-rooted rom. I finally checked the last few pages a few days ago and saw that there was a method to unlock the boot loader since January of this year! Haha I've been on 5.2.7.6 pre-rooted. Finally took the dive and did it. It was pretty straight forward. Only had to ask about the swipe to allow modification as I have never seen that screen before. The longest part was reinstalling all my apps. Thanks @Bertonumber1 for helping me with my question on there(just figured out my pw for my actual account) and @Sus_i for hanging out around here also and helping.

I saw the new interface on the new version and didn't like it, so I just flashed stock 5.2.7.6 and magisk.
[Fire TV Android Development] wadisnake:
hey there, is there any easy way to update my sloane with latest rbox prerooted image ? i mean using shell ? i am pretty i used to update using adb/shell but can't find how it was done

thanks
[Fire TV Android Development] Bertonumber1:
Yes if you have adb folder on pc you can enable USB debugging on sloane.

Connect a USB a to USB a cable and adb push the rooted rom to sloane /sdcard.

Reboot your sloane to recovery

Then open a cmd prompt on pc

type :

adb devices

You should see if you're connected to the device.

Then :

adb shell

twrp wipe system

twrp wipe cache

twrp wipe data (if you want to start fresh, if not forget this)

twrp install /sdcard/nameofyourrom.zip

twrp wipe dalvik

twrp wipe cache

reboot

OR you can place your firmware /magisk on a EXT memory card and use twrp to install it that way by selecting EXT storage during install.

Make sure to still wipe system and cache before flashing though.

Regards
[Fire TV Android Development] smumar143:
Hi

Pls help me . I m using firetv2 having 5.2.8.0 os, pls guide me which ROM should I flash for getting root
[Fire TV Android Development] fleisch80:
Try no root firewall .

Select start up option at boot , then go to apps , or add rules ,

Select same or similar Amazon ota and similar as you mentioned above ,

select block all from those sources.

There you go .

Go to settings and update , try updates .

Should completely block the box from calling home to Amazon assholes .
[Fire TV Android Development] fleisch80:
does anyone have access to sloanes 5.0. roms

specifically any with 5.0._ r1 . cant get anything other than r1 releases to work for me.

thanks so much .

cf.
[Fire TV Android Development] fleisch80:
most likely . you already need to open the box , and perform the unlock , flash method .

if root dont work thru software methods , then yes you need the hardware unlock method that flashes a recovery ,

then lets you install the o.s.

its a hardware chip exploit that you need linux to do it with.
[Fire TV Android Development] fleisch80:
Do you have any 5.0.5 r1 roms.

I can't find anywhere . how did you drop below 5.6 .
[Fire TV Android Development] fleisch80:
Anyone has a working rom above 5.0.5.1 , but that still used the original type menus and

screen .

This is frustrating.

C.f
[Fire TV Android Development] mamcho:
So im new to the prerooted world. How do i uninstall supersu and replace it with magisk?
[Fire TV Android Development] Sus_i:
Instead of a supersu prerooted rom flash a stock rom, then magisk.

Works only if you did the unlock before...

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Fire TV Android Development] mamcho:
Thanks for the advice. Where do i get stock images? And wont i lose rbox Recovery boot menu then? i like the ability to chose between twpr and fire os.

EDIT: Found ota full package in the unlock thread.
[Fire TV Android Development] mamcho:
Yesterday i did the unlock from scretch wiped everything and installed the stock Image 5.2.7.2 plus magisk 23.0. But the image wont boot. All i get is the white Amazon Logo. Tried diffent stock roms. Twpr still works tho. BL is still unlocked. Any ideas how to get out auf this? Is it a softbrick?

ps: sorry for the double post.

Edith: Hardware failure it was.
[Fire TV Android Development] Hannover2k:
Looks like a new image was released today. My non-rooted Sloane device just installed a software update. Are you going to be adding the new version to the list?
[Fire TV Android Development] louisdid:
Hi Everyone,

I have an old fire tv 2 rooted with 5.0.4 (536116920) firmware. I would like to upgrade to the latest prerooted stock images and would appreciate any advice how to proceed. The warning about flashing 5.0.5 and earlier scares me and dont want to brick the box. Thank you in advance for your assistance.
[Fire TV Android Development] Bertonumber1:
Hi there,

I'm sure if you want to update to the latest magisk "prerooted" images You will have to do the unlock from the Unlock Root TWRP Unbrick Firetv 2 sloane thread, this is because you are currently using the old method (superSU and locked bootloader) and you have really old firmware.

Follow the OP from the unlock thread carefully and you'll be okay.

If you need any help one of the other senior members like sus_i will hopefully chime in and correct me if I'm wrong here.

Kind Regards
[Fire TV Android Development] louisdid:
Thank you very much for taking time to answer my question and point me to the right direction. Thank you again.
[Fire TV Android Development] Han-Droid:
Ok, I must admit I am stuck somewhere in dummie-land deep in the rabbit hole---

Would anyone confirm the following procedure as WORKING? Thank you soooo much! :-)

GOAL: update latest RBOX FIRETV2-System (pre-rooted and equipped with TWRP) to the LATEST Firmware PLUS adding Magisk

1. Download Stuff:

-- OS 5.2.8.8 ( update-kindle-full_sloane-36.6.7.6_user_676742620.bin ) from "here" on xda

-- Magisk 25.2 ( https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk )

2. renaming Stuff:

-- update-kindle-full_sloane-36.6.7.6_user_676742620.bin to update-kindle-full_sloane-36.6.7.6_user_676742620.ZIP

-- Magisk-v25.2.apk to Magisk-v25.2.zip

3. Moving these two ZIP-files to FTV2 (external SD-Card, root dir)

3. rebooting FTV2 and entering TWRP

4. Flashing in TWRP

-- flash update-kindle-full_sloane-36.6.7.6_user_676742620.ZIP

and directly after that

-- flash Magisk-v25.2.zip

5. reboot to System

Will this work? In fresh system: when starting magisk-app, what are the next steps to finish fresh-flashing and fresh-rooting?
[Fire TV Android Development] Sus_i:
No, that won't work at all, because you need to unlock the bootloader as a first step infront of flashing a stock rom...

Go to this thread and download the latest amonet for solane:

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/post-84343353

-Push it to sdcard,

-flash it with twrp

-reboot to the 'new twrp a.k.a. not--the-rbox-bootmenu-twrp' (see the unlock thread for details).

Do a format data (under advanced wipe), then flash the stock rom and magisk.

Instead of flashing amonet via twrp, you can also follow the unlock thread post #3, a.k.a the step1/2 thing, but I would do the flash via TWRP as it's much easier...

Don't worry, there isn't much that could go wrong if you flash amonet via the rbox twrp, since you still have the rbox bootmenu twrp (until you decide to flash a stock rom) AND the new twrp on the recovery parttion. ;)
[Fire TV Android Development] hafren:
So I dug out my old rooted sloane it has TWRP v3.0.0-5 and firmware 5.2.1.0. I can only remember using the AFTV guide and file sloane-5.2.1.0-rooted_r2 to root so am unsure if I have magisk or need it? So as a noob I have some questions

Do I need to update firmware to have full app functionality?

I think my root is from Rbox using Prerooted images - how can I confirm?

Do I need to change to amonet sloane? What benefit is there in this newer method?

Do I need Magisk - I'm not sure what it does?
[Fire TV Android Development] hafren:
Anyone able to help with my post #962?
[Fire TV Android Development] Sus_i:
That point is clear, since there is 3005 twrp on the box.

You may switch to the unlock via amonet, because you can flash any new stock rom, there is no need to wait for prerooted roms.

You need magisk (root access) only if the bootloader is unlocked via amonet and if you like to do things like disabling updates, switch launcher or something like this.

Since your box is already twrp'ed, boot into twrp, push the latest amonet-sloane zip and a stock rom to the sdcard and flash the amonet.zip via twrp. Almost done at this point... if all went fine your box boots into a new twrp version (but you still have the old twrp with bootmenu on the box, until you flash a stock rom). Flash magisk only if you flashed a stock rom in the first place...
[Fire TV Android Development] Sus_i:
@hafren

Also make sure that you flash stock roms only via the new twrp, not via 3005 twrp...
[Fire TV Android Development] hafren:
@Sus_i So this is my plan:

1. Download Stuff:

-- amonet-sloane-v1.1.zip from here

-- stock OS 5.2.7.8 ( update-kindle-full_sloane-36.6.6.4_user_664657620.bin ) from here

-- Magisk 25.2 ( https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk )

2. renaming Stuff:

-- update-kindle-full_sloane-36.6.6.4_user_664657620.bin to update-kindle-full_sloane-36.6.6.4_user_664657620.ZIP

-- Magisk-v25.2.apk to Magisk-v25.2.zip

3. Moving these two ZIP-files & amonet-sloane-v1.1.zip to FTV2 (external SD-Card, root dir)

3. Boot FTV2 and enter old TWRP

4. Install

-- amonet-sloane-v1.1.zip

5. FTV2 boot into new twrp

Install

-- update-kindle-full_sloane-36.6.6.4_user_664657620.ZIP

and directly after that

-- flash Magisk-v25.2.zip

5. reboot FTV2

If everything works can you advise how I disable OTA updates?
[Fire TV Android Development] Sus_i:
Yes, should be ok...

At the reboot the old bootmenu comes up maybe, doesn't matter, it's gone as soon as you flash a stock rom.

If you get some mount errors in the new or old twrp, try to boot the new twrp and do a 'format' data (advanced wipe section).

Flash magisk later if you like... you can also skip the initial update in the first place.
[Fire TV Android Development] hafren:
@Sus_i Installed amonet-sloane-v1.1.zip and new twrp (3.3 I think) rebooted and I get screen "keep system read only?" Do I keep read only or swipe to allow modifications?
[Fire TV Android Development] Sus_i:
If you like to use a mouse or keyboard/touchpad do the swipe... ignore it if you want to use twrp commands via adb shell...
[Fire TV Android Development] hafren:
@Sus_i So I'm using mouse & keyboard so in swiping I'm not keeping system partition read only?
[Fire TV Android Development] Sus_i:
Yes, the swipe is ok...
[Fire TV Android Development] hafren:
@Sus_i Thanks for you patience and continued help. That prior screen fooled me but the new twrp completed successfully. I then flashed stock OS 5.2.7.8 and rebooted. I saw a b&w Amazon followed by the animated fire tv but it is now stuck at the colored amazon firetv logo. I removed power and still stuck at the colored amazon firetv logo. How do i get back into/boot the new twrp and what do I need to do to fully boot?
[Fire TV Android Development] Sus_i:
You can always use the boot-recovery.sh script from the amonet folder, run the script with sudo, connect the box via usb + power on... Should boot into twrp within seconds.

In TWRP wipe cache, dalvik and 'format' data. Maybe flash the fireOS rom again. The box should boot fine, maybe it takes a bit time at the first boot but you should get the initial setup at some point...

You can also try to flash magisk too, see if there is a difference.
[Fire TV Android Development] hafren:
@Sus_i Another day of learning but no progress. I used adb 6+ years ago when I 1st rooted the ftv2 but now to use sudo I believe I have to have a linux os. I tried to create a usb with rufus and a fireOS iso without success. Even If I can make a fireos usb how do i get amonet onto the usb? Is there away to get twrp via adb commands? Appreciate any help you can give me
[Fire TV Android Development] Sus_i:
The easiest is if you download the fireIOS from here and use rufus to flash it to an usb storage stick.

Releases · amonet-kamakiri/fireiso

ISO with patched kernel for kamakiri and amonet. Contribute to amonet-kamakiri/fireiso development by creating an account on GitHub.

github.com

Then boot this stick on a PC, add a network, download amonet to desktop, extact it to a folder... open the folder until you see the scripts and then do a right click 'open a terminal' and run sudo ./boot-recovery.sh

Boot it like in this vid here:
[Fire TV Android Development] hafren:
@Sus_i Well a little step forward- managed to create a fireISO usb. Copied amonet to root and ran sudo ./boot-recovery.sh Communication started but ends with sending FACTORYM see pic I've no idea what this means or what to do next. I typed twrp and it responds command not found
[Fire TV Android Development] Sus_i:
That is ok, what happend on your TV? Any sign from TWRP? B/W or colorful logo?

Command would be adb devices and in case you see a serial, then adb shell.

But you would need to apply a special command from the unlock thread within 10 seconds, if you want to use adb shell / twrp commandline, or usb connection gets lost.

So what can you see at your TV?

Maybe try the boot-recovery script a few times...

What color shows the fireTV LED? White or yellow flashing?
[Fire TV Android Development] hafren:
There is no image on TV

I have tried boot-recovery ~10 times same result. Led is flashing white

If I close sudo, disconnect usb cable and power on box I get white logo then B/W and colored but doesn't progress to firetv home screen
[Fire TV Android Development] Sus_i:
But after the amonet.zip flash, the box booted up to the colorful logo, isn't it?

What screen shows if you boot without the script?

Make sure you disconnect power and usb cable after each try.

You can also try the boot-fastboot.sh script, see what logo shows on the tv and whats written down in the corner ... then type fastboot devices and if there is a serial, try running sudo ./fastboot-step.sh
[Fire TV Android Development] hafren:
YES - After i flashed amonet.zip (Post #972) I immediately flashed stock OS 5.2.7.8 and rebooted. I saw a b&w Amazon followed by the animated fire tv then colored amazon firetv logo

Today after sudo ./boot-recovery.sh there is no image on TV

If I boot without any script I get white logo then B/W and colored but no progress to firetv home screen

Yes I disconnect power and usb cable after each try. and wait maybe 2 minutes

Ok will try sudo ./boot-fastboot.sh and report tv screen then fastboot devices (No sudo?) and if a serial then sudo ./fastboot-step.sh
[Fire TV Android Development] rbox:
Thanks! I'll release a new preroot and a new recovery package later today.
[Fire TV Android Development] Kramar111:
[MENTION=3991724]rbox[/MENTION]

clean 5.0.5_r3 w/o hub - not worked

5.0.5_r3 with newer ramdisk w/o hub - worked

keyboard Rii mini II (2.4 GHz Wireless USB)
[Fire TV Android Development] Sajhid:
I understand what the prerooted firmware is for, but what is the recovery package for and how to use it? Sorry too many question but i don't know anything about firetv rooting.

Thank you
[Fire TV Android Development] bula1ca:
Recovery package (http://xdaforums.com/fire-tv/development/firetv-2-recovery-t3309780) is part of the pre-rooted image, no need to install it separately.
[Fire TV Android Development] elliwigy:
Hey,

My issue was different.. my k400 plus worked great but i needed the $ so I returned it after the first pre rooted rom/recovery..

I wanted to update to latest but was trying to use adb mouse but wasnt aware it only worked over ethernet.

I used my nieces cheap little usb mouse and the cache/bootmenu_recovery to default into twrp then flashed 5.0.5_r3 pre rooted img then used twrp file manager to delete the cache file..

at first like others mouse didnt work but unplugged/plugged back in andit worked a treat lol

The keyboard I never got to work wasa Microsoft Wireless 2000 keyboard and mouse combo.. has anyone successfully used this one?

I believe it is a usb/bluetooth so not straight usb...
[Fire TV Android Development] androidfux:
This updated ramdisk fixed the keyboard problems also for me.

Thank you very much, [MENTION=3991724]rbox[/MENTION] :)
[Fire TV Android Development] rbox:
The latest ramdisk should fix it. If your FireTV is booting properly right now, you can just wait until I release a new recovery/prerooted. Or you can try copying it to /system/recovery manually.
[Fire TV Android Development] rbox:
The recovery package was initially meant for just installing recovery when people were rooted but didn't have recovery. But I realized as I update recovery, it's easier to just use that to install recovery than to install a new prerooted rom. So it's really up to you what you want to do. As new versions of recovery come out, you can just install a newer prerooted rom, or you can use the recovery zip to install the new version.
[Fire TV Android Development] elliwigy:
should fix the adb mouse?

edit: Im pretty sure my keyboard/mouse is simply not compatible as it never worked from the start.

edit 2: unlessyou have adb mouse working over usb to pc theresno point for me toswitch now asI wassuccessful in using the mouse after one unplug/plug back in as you stated.
[Fire TV Android Development] Sajhid:
What is bootloader and would you guys recommend unlocking it (if able to) or is it not worth doing?
[Fire TV Android Development] elliwigy:
not possible atm to my knowledge
[Fire TV Android Development] gazdaman.:
Most likely because they changed something in the platform.xml file they shouldn't have and not due to changing this permission.
[Fire TV Android Development] elliwigy:
i dont think it was simply a factory reset.. they might have somehow wiped system and/or rom..

if the system isnt there to boot it will essentially be bricked..

either a wrong wipe was done or it wiped something it shouldnt have
[Fire TV Android Development] zeroepoch:
It's signed so no way to unlock it unless we could somehow generate the unlock code. Also we haven't even looked into where that would even go. No easy exploits we could find.
[Fire TV Android Development] elliwigy:
unfortunately i have a g925v and am used to locked BLs thanks to Verizon..

twrp is more than i got on my vzw s6 edge
[Fire TV Android Development] rbox:
5.0.5_r4 includes TWRP 3.0.0-4 which should fix the keyboard issues some people were seeing.
[Fire TV Android Development] Sajhid:
By using this, will it wipe all the data back factory setting? Also If I do want to factory reset the box without losing the root, shall I just a factory reset with TWRP?

Thanks.
[Fire TV Android Development] deanr1977:
No it won't wipe your data, all your files, music, kodi or what ever will still be as it was before, as far as I know from what I've read, if you factory reset from settings you won't lose root (if I'm wrong someone correct me) but you will activate updates again so you would need to reblock updates, if you wipe from twrp you will wipe your rom/recovery & system, so the only safe way to wipe would be to wipe in twrp then "dont reboot!" but then install the rom & recovery first, then reboot. But why would you want to do a factory reset anyway?
[Fire TV Android Development] go2xraj:
5.0.5_r4 worked great and no issues of keyboard
[Fire TV Android Development] Sajhid:
What i meant was, sometimes the box might start playing up and I want to format it to a fresh state with no data left on it, but obviously not losing the Root. Is there a way of doing this?

---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------

You recommend upgrading to this? Thank you
[Fire TV Android Development] Sus_i:
In case you get twrp up, format data
[Fire TV Android Development] hafren:
Tried 3 times sudo ./boot-fastboot.sh and get white amazon logo then nothing on TV (led flashing white). No reply to fastboot devices
[Fire TV Android Development] Sus_i:
Ok, sry, but if the two scripts aren't working, you may need to open up the box, do the unbrick via shorting.

Goal is to get twrp up and format data.

See post #2 for details:

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/post-84343351
[Fire TV Android Development] hafren:
OK I left it running for 10+ minutes and now I have colored amazon logo
[Fire TV Android Development] Sus_i:
You can wait a hour or so to see what happens, maybe the OS decides at some point to boot the recovery.
[Fire TV Android Development] hafren:
@Sus_i Well I've finally got the sloane setuo to unbrick using post #2 and have hit the next roadblock, I'm using Fireiso 2.0, on a laptop, and after typing sudo apt update I get sudo: apt: command not found. What can I do now?
[Fire TV Android Development] hafren:
@Sus_i

So finally success. With the help of a digital microscope my 70 yr old eyes could short DAT0 and after ignoring post 2 instructions (apt updates & modemmanager) went to bootrom-step.sh. Unfortunately that didn't work - so after some time I removed the usb hub (connecting FireISO laptop, usb mouse, usb keyboard) and plugged FireISO laptop direct to FTV2 and success loaded twrp 3.3.1-0. Formatted data, wiped cache & dalvik. Reboot created same issue I had with original update of twrp (post 972) with fireos stalling at colored logo. Decided that update-kindle-full_sloane-36.6.6.4_user_664657620.ZIP (Fireos 5.2.7.8) must be corrupt so used boot-recovery.sh back into twrp formatted data, wiped cache & dalvik again then loaded fireos 5.2.7.4 and magisk. Now final success fireos started oobe but now I need to know how to block updates before I can turn on adb.

I read on mantis forum there is a NOFOTA.zip that twrp can load. Can that be used on sloane? Where can I download it. Appreciate your help on the last leg of this long journey.
[Fire TV Android Development] Sus_i:
You can use this guide to skip the update, then use pm disable command to disable all ota apps.

How to Skip Software Updates during Initial Setup or Factory Reset on a Fire TV, Firestick, or Fire TV Cube

Since the latest software update for Fire TV devices is blocking the ability to use custom launchers, you may want to avoid updating a new or factory reset Fire TV.

www.aftvnews.com