yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] LocoMexican:
Try this:

1. Use the "short" (brick) method.

2. Run gpt-fix.sh. This should put you into TWRP.

3. Using TWRP, install Amonet-Sloane v1.1.

4. Using TWRP, "format" (not wipe) data.

5. Using TWRP, install your stock (not pre-rooted) ROM.

6. (a) If you want superuser permissions, using TWRP, install Magist.

(b) If you do not want superuser permissiions, do not run Magist.

7. Re-boot system.

If you want to revert to straignt stock, try this:

1. Use the "short" (brick) method.

2. Run gpt-fix.sh. This puts you into TWRP.

3. Using TWRP, "format" (not wipe) data.

4. Using TWRP, install the stock ROM of your choice.

5. Reboot system.

Good luck.
[Fire TV Original Android Development] 010u:
After flushing sloane-5.2.7.0-rooted_r1.zip

update-kindle-full_sloane-36.6.4.8_user_648594820.zip etc.

I flashed and restarted without Magisk (just in case), but it didn't start. I'm expecting that boot.img etc. was rewritten with sloane-5.2.7.0-rooted_r1.zip, but with stock ROM such as update-kindle-full_sloane-36.6.4.8_user_648594820.zip, boot.img etc. Will all return to stock?
[Fire TV Original Android Development] 010u:
thank you for your answer.

Before executing "7. Re-boot system"

Currently, I am ADB to TWRP again.

postscript:

After all, even if you flash Stock and restart it,

The OS did not boot.

After the white Amazon logo, the lamp on the base keeps blinking white,

The screen is blacked out.

https://xdaforums.com/t/unbrick-root-twrp-fire-tv-2-sloane.3986303/post-80619235

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/post-81713585

If you id me print referring to the above, the following will be displayed.

#idme print

board_id: ffffff0000000000

serial: 0

mac_addr: 0

mac_sec: 0

bt_mac_addr: 0

product_name: 0

productid: 0

productid2: 0

bootmode: 1

postmode: 0

bootcount: 258

manufacturing:

eth_mac_addr: 0

device_type_id: 0

unlock_code: unlock_code:

sensorcal:

4800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

wifi_mfg: 0

bt_mfg: 0

KB: KB:

30 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

DKB:

30 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

dev_flags: 0

fos_flags: 0

usr_flags: 0

# dd if = / sdcard / idme.bin of = / dev / block / mmcblk0boot1

dd: can't open'/sdcard/idme.bin': No such file or directory

It seems that it is being played from the network due to problems with the mac address and serial.

Is there a solution to the problem?

Thanking you in advance.
[Fire TV Original Android Development] Sus_i:
Flash the lineage rom ;)
[Fire TV Original Android Development] 010u:
postscript

After launching lineage 12.0, I was able to log in with ADB from USB. After all, the screen does not appear. .. .. Is it possible that TWRP is reflected and the OS is not reflected?

thank you for your answer.

I have various stock ROMs

I tried Lineage 12.0 and some Rooted.

Currently, Rooted5.2.7.6r1 is finally flushed.

However, the situation is the same for Lineage 12.0 and this time Rooted.

Amazon Logo> Normal boot or TWRP> Normal boot> Amazon Logo> Black out (Signal failed ??)

I waited for a while in Black out and pressed and held the home button on the remote control to pair. Then, the lamp of the terminal goes out and turns on every time the remote control button is pressed.

My guess is that the OS is up, but the video isn't being output properly. (TWRP and Amazon Logo are reflected)

Many apologies.

Do you have a solution to the problem?

Please give me some advice.
[Fire TV Original Android Development] Sus_i:
I don't know whats going on with your fireTV.

It seems that it is seriously messed up, like your blank idme data shows.

But even if idme stuff is gone, you should still have a picture on your TV, at least for lineageOS and in twrp too.

I remember that my idme data was gone too back then, but fireOS was booting, it showed an empty stock launcher and stuff like the serial, LAN/WIFI/BT was f*cked up.

You know, it's Black Friday in a few days, you may get a new one ;)
[Fire TV Original Android Development] Sus_i:
Fire OS 5.2.8.0 (671761720)

https://d1s31zyz7dcc2d.cloudfront.net/66a9e40e40f468a0fd861084a90c328f/update-kindle-full_sloane-36.6.7.1_user_671761720.bin
[Fire TV Original Android Development] abdi7451:
Hi, all. Please forgive the extremely n00bish questions. I've tried to read over the thread in it's entirety, along with scouring other leads on XDA.

I have a Sloane FireTV. It has always been stock. Never unlocked, never rooted, never bricked, never had TWRP or any other recovery. In other words, it is vanilla.

It has been updated to the latest FireOS, version 5.2.8.0.

Am I understanding this correctly:

It is not possible for me to unlock and root this device without downgrading it to some version of FireOS before 5.2.7.3. And in order for me to downgrade it through ADB, I would need for it to be rooted already. Since it isn't rooted already, it is not possible at all for me to unlock and root this device.

I've enabled USB debugging, plugged it into my computer with the A-A cable, ran

daruur@cumulo ~/d/a/amonet> sudo ./step-1.sh
[sudo] password for daruur:
Testing root access...
Trying to use mtk-su to get temp root...
Pushing root files bin/mtk-su: 1 file pushed, 0 skipped. 168.9 MB/s (65144 bytes in 0.000s)
bin/minisu.img: 1 file pushed, 0 skipped. 1983.9 MB/s (1048576 bytes in 0.001s)
bin/busybox: 1 file pushed, 0 skipped. 1812.3 MB/s (989184 bytes in 0.001s)
Failed critical init step 1
Failed critical init step 1

Any and all help/guidance is greatly appreciated.
[Fire TV Original Android Development] Rortiz2:
Since your firmware is too new (and you can't root with mtk-su nor any other SW root method) you'll need to open up the device to short it and follow the directions of the second post.
[Fire TV Original Android Development] abdi7451:
Update, was able to short it successfully. Have it unlocked, with TWRP installed, and got Magisk with root working! On 5.2.8.0 still.

Thank you for all your hard work!
[Fire TV Original Android Development] yozh:
Hello,

I flashed 5.2.7.6 on my box and was able to get to unrooted, but its still not updating to the latest firmware. Any ideas why ?
[Fire TV Original Android Development] Sus_i:
Nice guide (y)

A dd backup of boot1, edited with a Hex Editor works too and is the only way to fix KB (which is a 1:1 copy of the data on KB partiton).
[Fire TV Original Android Development] DanielF50:
Ah, good to know!

I don't have a dd backup of any of my sloanes idme otherwise I'd clear it out and upload a blank one. I might be able to get one later and update the post though 👍
[Fire TV Original Android Development] yozh:
Any help would be really appreciated.
[Fire TV Original Android Development] Sus_i:
I guess you missed the note in the prerooted rom thread!?

With a disabled stock recovery, the box wont update at all.

You can try to boot the recovery:

adb shell
reboot recovery

Take a look on the TV what happens...
[Fire TV Original Android Development] DanielF50:
Updated post with blank backup of IDME & instructions of how to dd it - hopefully it's a little more straightforward with that file included 👌
[Fire TV Original Android Development] yozh:
oh, I guess I must of. Let me try and see what happenes.
[Fire TV Original Android Development] tietze11:
Hi,

so when I have rooted my fire tv 2nd gen (sloane) with these instructions, is there any way to mount a ntfs hard drive? That would be really my goal here. Tried out the Paragon Root Mounter Tool, but it just shows the drive as "undefined or not supported".

If this doesn't work with the stock rom, is there a custom one that supports it & also the streaming apps netflix, prime video & disney plus? I was only able to find custom roms for the 4k stick and not for the fire tv 2.

Thanks in advance

EDIT:

I actually got it working, the new Paragon Root Mounter Tool doesn't work on the Fire TV, as well as the NTFS Mounter Tool that someone here on XDA has developed and hosted. But what does work is the old version of the Paragon NTFS Tool, but specifically version 1.26, tried out older ones and they didn't work.

So what is working is this App: Paragon NTFS & HFS+ Version 1.26

I got it from here: https://apkgit.com/download/com.paragon.mounter_1.26_free
[Fire TV Original Android Development] :
Hey everyone. Some help here please! Can't log onto my old account. Forgot the password. I was on rbox pre-rooted 5.2.7.6. I booted into TWRP and flashed amonet1.1.. It restarted and I'm not on the TWRP screen where you could wipe/format. I'm on a screen that says "Keep System Read only?" It's asking me to either click on Keep Read Only(greyed color) or Swipe to allow modifications(Blue colored)."

At the moment, I can't even select any of them. I can't even use my USB keyboard. I tried unplugging and another keyboard and still nothing. How do I go about that?

I opened up a terminal and it connected to firetv. I typed adb shell and it gives me

` # <[6n

Where do I go from here? I'm just leaving the screen as is for now. Don't want to unplug or do anything. Thanks in advance.

EDIT TO ADD: I plugged my mouse in and it does work. I could click on a few things. I'm just not sure if I should click keep to system read only or Swipe to allow..

Also I tried clicking the back button, it wouldn't go back. I clicked the home button and nothing also. I clicked on the "file/log" button and it shows a errors. Not sure if that means anything, but this is what it says..

Failed to mount '/data' (No such device)

Unable to recreate /data/media folder.

Updating Partition details...

Failed to mount '/data' (no such device)

...done

unable to mount storage

Failed to mount '/data' (no such device)

Full SELinux support is present.

Unable to mount /data/media/TWRP/ .twrps

MTP enabled
[Fire TV Original Android Development] Bertonumber1:
Yes swipe to allow modifications amd then format data.

Then reboot recovery and adb push your firmware and chosen root su / magisk (recommend magisk).

After flashing the above it is optional to wipe cache/ dalvik before rebooting system.

Regards
[Fire TV Original Android Development] :
Thanks so much for the super quick reply @Bertonumber1
[Fire TV Original Android Development] smumar143:
hi

pls help me.

i m on 5.2.8.0 using firetv 2 sloane, i never rooted.

pls guide me from where i should start, i mean basic steps for rooting the device.

thanks
[Fire TV Original Android Development] Sus_i:
https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/post-84343351
[Fire TV Original Android Development] jonj80:
Hi guys, I've identified my FireTv Box to be 2.Gen as it has a micro SD card slot. The current OS on it is 5.2.7.2.

The box is untouched. Nothing rooted.

I this the right thread to start? How to root the box? I use a linux and win pc.
[Fire TV Original Android Development] Sus_i:
You can use/try the mtk-su method via adb from post #3

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/post-84343353
[Fire TV Original Android Development] jonj80:
Thanks for your reply. But this tutorial is more confusing than helping cause it's sending me to different steps from different tutorials.

Wouldn't it be easier to make a tutorial where every step is placed in one thread? As a noob I would say the words unlocking and rooting have the same meaning.

In your mentioned link posting #3 it is said to NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.

Ok, but preparing to what point? The whole #2?

Should I doall this stuff first? https://xdaforums.com/t/rapid-temporary-root-for-hd-8-hd-10.3904595/post-78988627

And then go on step 2 on #3?
[Fire TV Original Android Development] Sus_i:
There are more than one way to unlock the bl and without an unlock you can't permanent root with magisk.

But you can root via rapid-temp-root a.k.a. mtk-su, see post #3. This is your important first step. As soon as you've got root access, you can run the two scripts from #3 and it's almost done...

Your OS doesn't need a temp-bricking, i.e. no linux environment required, you may ignore that part. You need Mtk-su and adb access, then it will work without any hassle, like to open the box or to short smd parts on the mainboard.

You don't need a better guide, you need to follow the few steps from #3 and it's done ;)
[Fire TV Original Android Development] vanchienbmt:
Hello , i have firetv2 running fireos 5.2.8.0 i'm finding method root and flash custom rom but not found, please tell me any method downgrade fireos simple or method root and twrp, thank you all
[Fire TV Original Android Development] vanchienbmt:
please tell me solution do it, i have same problem thanks you
[Fire TV Original Android Development] atdog69:
Hi, I hope I'll find some help here.

Got a rooted Sloane, don't know the last Version used but it will do a boot loop once plugged in. I see the white ama*on logo then short after that the box went into TWRP allowing me to flash files and all. Nothing works. I am no specialist and I am not familiar with Linux (tried on a usb stick but don't see the firetv as I don't know how to find the system settings for activating the com port) so I am stuck after following a lot of flashing images and wiping data and stuff. What I never been able to was to wipe the CACHE folder. I think this must be the answer? I used an A to A USB cable connected to my Windows PC, used adb to connect to the box. Trying diffrent methods of flashing recover images only to see that the box get stuck on "Reading 000000200: 0%". Tried various unbricking methods. Nothiung. I even don't know if the box is bricked? Or if the bootloader is missing?

TWRP is accessible so I think it is rooted to the day...?
[Fire TV Original Android Development] atdog69:
One more thing I forgot: Flashing amonet-sloane-v1.1zip works fine without errors but when the box rebooted, it shows the white ama*on logo (with ORANGE LED always on) then after a few seconds reboots again, then showing AGAIN the white ama*on logo (this time the white pulsing LED) before it reboots a 2nd time going back to the TWRP Boot Menu. When I then follow the guide at the OP saying "Then go to Wipe > Format Data and type "YES"." I got hundreds of red errors saying "Error opening 'data/...' (I/O Error) followed by Failed to mount '/system' (Invalid argument) .
[Fire TV Original Android Development] vanchienbmt:
NOTE: If you are on firmware 5.2.7.3 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)

please guide downgrade fireos, please
[Fire TV Original Android Development] atdog69:
You mean I should flash lower versions...already tried that too (different versions like 5.2.6.8) -> stuck in bootloop with the white ama*on logo followed by TRRP menu :-/

Is it correct that I can't wipe that 'cache'? I think there's something going wrong with?
[Fire TV Original Android Development] atdog69:
And by the way, Rortiz2 wrote in Post #13 "If the zip flashed fine forget about the downgrading part"

And that flash did work for me recently...

But I didn't know what he means with the 2nd sentence "Are you able to boot unlocked TWRP using boot-recovery.sh?"

How do I check that? Can I do this with Windows?
[Fire TV Original Android Development] Sus_i:
You may use the boot-recovery.sh from the amonet zip in order to get into the 'new unlocked twrp'

Instead of the script you can also boot the 'old' twrp via bootmenu, then open adb shell and run the 'reboot recovery' command.

As soon as you boot the new twrp, 'format' data, then flash a new fireOS update-bin.zip + magisk.zip.
[Fire TV Original Android Development] Sus_i:
All you need to know is written into the second post of this thread:

Unlocking with non-rooted Firmware

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/post-84343351
[Fire TV Original Android Development] vanchienbmt:
sorry but i'm newbie, have you any videos for this method please

Thank you
[Fire TV Original Android Development] Sus_i:
No, sry, there isn't a video at all, you need to read the guide from the second post
[Fire TV Original Android Development] vanchienbmt:
but my fire tv is normal with this method i need open my device ?
[Fire TV Original Android Development] atdog69:
Hi Sus_i, thank you for your help. So when I use 'reboot recovery' (i can pick that in the adbLink gui from the Reboot-menu too) the box went to the white ama*zon logo but then with the ORANGE solid LED. After a few seconds it reboots to the (i think what you called) 'old TWRP'.

How and when do I have to use the 'boot-recovery.sh'? I have it extracted. To what directory must this go?
[Fire TV Original Android Development] Sus_i:
You need linux for the script, ubuntu or something like that... Extract it with ubuntu, open a terminal in the folder, type sudo su, then run ./boot-recovery.sh followed by connecting the usb a-a cable and the power supply of the box at the same time. The box should boot the new twrp. See the OP for details.

Anyways, if adb reboot recovery wont work for you, your unlock wasn't successful and something is messed up or damaged. So you may boot the old twrp, go to wipe, advanced wipe, format data. Then reboot to the old twrp, flash a prerooted rom from rbox. Then flash the amonet zip again. If you get some error messages, report back.
[Fire TV Original Android Development] Sus_i:
Ofcourse, you need to open the box up and you need an usb a-a cable...
[Fire TV Original Android Development] vanchienbmt:
solved, when i read 28 page this post i can do it.

Simple method, with newest firmware need open fire tv and do it with second post, run script on linux and connect DATA0 with GND and view on screen running script, all done

thanks @Sus_i very much.
[Fire TV Original Android Development] atdog69:
Hi Sus_i, tried with Ubuntu (booted from USB-Stick) When running the command ./boot-recovery.sh, the following was shown:

.root@ubuntu:/home/ubuntu/Downloads/amonet# ./boot-recovery.sh

Traceback (most recent call last):

File "handshake2.py", line 4, in <module>

from common import Device

File "/home/ubuntu/Downloads/amonet/modules/common.py", line 6, in <module>

import serial

ModuleNotFoundError: No module named 'serial'

As I said before I am totally unfamiliar with Linux, and can't find any sytem settings to activate the com port.

So I went back to Windows trying to do what you suggested with the old TWRP.

You wrote go to wipe, advanced wipe, format data.

I believe you mean "format data" next to the button "advanced wipe" right?

Or do you mean to wipe "data" (checking "data" and then Swipe)?

Anyway there are different errors every time. After trying to flash a prerooted rom I got this (but it had worked before!? As well as the amonet-sloane-v1.1. But when I reboot afterwards I'm going to the bootloop again. White ama*n followed by TWRP.....

On the screenshot it just hangs on "Copying" but it doesn't advance...

How do I know if it boots into the "new TWRP"? Does it look different to the old one? Does the white ama'*on logo show up first after booting there too?
[Fire TV Original Android Development] Sus_i:
I guess there is something wrong with you eMMC storage, probably a faulty GPT.

You can try to flash a new GPT (grab the gpt-bin file from the gpt-fix zip in the OP) with adb shell if you like:

adb push gpt-sloane.bin /data/local/tmp/
adb shell
dd if=/data/local/tmp/gpt-sloane.bin of=/dev/block/mmcblk0 bs=512 count=34
exit

Then reboot into TWRP and try to format data.

If the box is still messed up (partition errors in twrp), your next option is to use the method from the second post, i.e. 'unbrick'

You need an usb a-a cable and to open your box for this...

Instead of the bootrom-step.sh you may use the gpt-fix.sh, in order to fix the GPT (you need to merge the gpt-fix zip into the amonet zip as a first step).

If you get some errors, copy/paste the terminal content. If you get into the new TWRP, make sure to format data...
[Fire TV Original Android Development] atdog69:
No luck again...:

adb push gpt-sloane.bin /data/local/tmp/

gpt-sloane.bin: 1 file pushed, 0 skipped. 22.4 MB/s (17408 bytes in 0.001s)

adb: error: failed to copy 'gpt-sloane.bin' to '/data/local/tmp/gpt-sloane.bin': remote Read-only file system

Above from PC , the pic from box terminal...

I think there's no way but to open it...?

UPDATE:

Maybe I got a step forward? I get rid of that data folder i/o error as it seemed to be that 'system' did not mount automatically after booting. I did this after going into TWRP recovery:

installed amonet

(auto reboot)

mount system

installed prerooted rom 5.2.6.8

installed amonet (again) ALL OF THE ABOVE WITHOUT ANY ERRORS (besides the 'mount cache' (invalid argument)' error

(auto reboot)

adb reboot recovery (from adbLink menu (PC))

box reboots to white amaz*n logo with static ORANGE LED

seconds later goes to white amaz*on logo with pulsating white LED

followed by going to (I think old) TWRP

Then (if I let it 'Boot normally' and not go into 'Launch Recovery')

there will be the boot loop again with the white amaz*n logo (white LED) and TWRP screen rotatoring
[Fire TV Original Android Development] Sus_i:
Nope.

The eMMC chips on sloane are known to fail quite often...

You can do this:

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

then give Rortiz2 a PM, he can tell you if your eMMC is a cursed one.
[Fire TV Original Android Development] atdog69:
Thank you Sus_i, pm'ed Rortiz2, if the eMMC is bad I don't need to go further...
[Fire TV Original Android Development] Sus_i:
Try the bootrom-step, until you get a message about rebooting into fastboot...
[Fire TV Original Android Development] atdog69:
Well I did that already? It's step No. 2 (at post #2) ?

2. Start the script:

Code:

sudo ./bootrom-step.sh

It should now say Waiting for bootrom.

Maybe you meant fastboot-step?

I now find out the problem above with file not found. I had to install fastboot first.

Now I can run the fastboot.sh script. But then after "Press Enter to continue"

all I'll get is < waiting for any device >

I think it's about that gpt error I got with the shorting method?

Traceback (most recent call last):

File "main.py", line 146, in <module>

main()

File "main.py", line 84, in main

raise RuntimeError("bad gpt")

RuntimeError: bad gpt

Is there anything to repair that? I already flashed the gpt-fix (via TWRP) but it seems not to have done anything...
[Fire TV Original Android Development] Sus_i:
The bootrom-step script needs to run up to the end, otherwise the unlock isn't in place...

Try again and again until you reach the reboot fastboot message...
[Fire TV Original Android Development] atdog69:
So I can ignore that bad gpt message as it could vanish by trying?

I have an old boot.img, from 1st rooting my device. Could that be helpful?

I think I have that problem with the bootloop.

When I use "lsusb" it always showed up in Preloader mode, can't get rid of that...
[Fire TV Original Android Development] Sus_i:
Yeah, it could, i.e. it will be messed up if the script errors out in between...

No...

Preloader is the first boot stage just after bootrom, so you can ignore that.

Try the bootrom-script again...
[Fire TV Original Android Development] Rortiz2:
Your box is completely dead. The script erased the Preloader (header) and you said it still boots, so the eMMC went into read-only mode.
[Fire TV Original Android Development] atdog69:
Hm, ok. So " your box is completely dead" means there's no way to fix it? Yes I got some errors about read-only too.

But the eMMC looks intact but in read-only mode?

Sorry for the questions I really can't follow as I am no specialist in linux/android stuff.