yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] fleisch80:
I know other people had success doing this process in different iterations , but I would

only use 2 of the files . yes ,use the bootrom .step but after you get the terminal message saying success , while still in terminal what I always use is fastboot.step .

This will complete the process and finish flashing twrp .

I'm not a dev so I can't tell you why some people had success using the other files

after the bootrom.step .

I do know for myself though I always used bootrom.step ,

and while in terminal and after message from finishing step 1 , I immediately enter the

fastboot.step that finishes up the recovery flash.

Also the mediatek exploit ain't perfect .

You could do everything right but still not get it .

sometimes it takes many tries .

I would also try the process with different versions of the package .

Meaning from older package to new.

I also had issues with the newer one.

One more thing , make sure the package containing the files has full root permissions.

If it does not . IT WILL FAIL .

Chris.
[Fire TV Original Android Development] fleisch80:
Yea ,definitely try the older package versions.

I believe there's gonna be an older package that will work better for you.

It all is dependent partly on when your exact unit was manufactured.
[Fire TV Original Android Development] vrl2:
Thanks for getting back to me.

bootrom-step.sh from amonet-sloane-v1.1 worked initially, and after running fastboot-step.sh from the same package, I was able to get into TWRP. However, after performing a wipe (the option that requires typing 'yes') I get nothing but a blank screen and a flashing light.

Should I start over and try shorting it again and running bootrom-step.sh from amonet-sloane-v1.0.0 or amonet-sloane-v1.0.1? Or will I eventually get over the I/O error if I keep re-trying to short it and re-run bootrom-step.sh from the v1.1 package?

I'm just trying to understand why bootrom-step.sh worked initially, but now consistently gives the I/O error.

Thank you.
[Fire TV Original Android Development] fleisch80:
ok. Yes Get twrp reinstalled first .

How I install the rom while in twrp is I copy the zip file to SD card. and also you should have a copy of super su .

Now take that micro SD card and insert it into your fire .

Reboot . while in twrp recovery

Go to wipe , select data

Now choose switch file system to ext2 , select format. use right bar button swipe to complete.

Hit back button , now select ext4 . format in xt4 format.

Hit back bottom .

Now go to install . select from bottom right of menu , install zip from,

select your external SD card from the menu .

choose the ROM file zip.

Select install .

When done , now go back ,select super su and install .

I would try to install ROM this way from micro SD card once you did the procedure to

Flash twrp .
[Fire TV Original Android Development] vrl2:
Thanks for your guidance.

Unfortuantely the first step in installing TWRP -- sudo ./bootrom-step.sh -- keeps giving me the same error. It gets to "Clear preloader header" and then keeps failing with the same error message (attached).

This same script worked earlier, but since that inital success has always given me errors. Is this expected? Should I just keep re-trying?
[Fire TV Original Android Development] Sus_i:
It may be that the eMMC of your box switched itself to read only... (most likely if it's a samsung chip).

Take a look into the new thread, there are some postings about dead eMMCs.

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Fire TV Original Android Development] vrl2:
Thank you for your response.

In XDA forums the function to search within a thread seems not to work for me, so it searched all threads instead of a single thread. So there is not a way for me to go through all 30+ pages of posts in the new thread to find eMMC related posts. Is there a specific way of going forward in this case?
[Fire TV Original Android Development] vrl2:
Looks like the short is working (I'm certain that the light is off when the short is in place). I have run it 15-20 times now. When I run bootrom-step.sh, it no longer works despite the initial successful run.

Sometimes I get to the point where I get the prompt to remove the short -- but it doesn't get much further. If I can get past the handshaking phase, then the furthest it gets is to "Check GPT" at which point it stalls at "Check GPT" with this EMMC read error:

File "/home/ubuntu/Desktop/amonet/modules/common.py", line 199, in emmc_read

It often stalls earlier (usually at either "waiting for bootrom" or if it gets past that, it stalls at "Clear preloader header" or "Init Crypto Engine")

@Sus_i is this the eMMC error that you were referring to? The U1600 chip is a Samsung, like you suggested. Is there any work-around or does this mean the device is dead?

Thanks.
[Fire TV Original Android Development] fleisch80:
Friend. Do you have modem manager disabled per instructions.

Did you remember to give the amonet folder with the files full root permissions with write

access .

I would also try the version of amonet Sloane that has gpx fix .

Run the gpx fix .

Then after that try the files again .

Its extremely important though that the folder of the files are given full root , and

write permissions. What I do is either in mint or ubuntu, in the amonet Sloane folder

I right click and go on properties ,then I give each file in that folder write access.

also make sure when entering commands to start the process that you begin with sudo
[Fire TV Original Android Development] Sus_i:
What happens at the time the script errors out? Does the LED start some flashing? Is the LED dark? What device can you see in lsusb just after the error message?
[Fire TV Original Android Development] fleisch80:
The problem is flashing these devices is not an exact science.

I also been there where your at , extremely frustrated .

honestly , my best advice is try everything any anything you can think of that might make a

difference. Also try the amonet Sloane packages that have those other files. Like the

Gpx fix . try the others also.

I feel for you cause we've all been there.

with the lights , I've had my boxes where no lights would show anything,

but the exploit still unbricked them.

if you can , I would just save yourself a headache and find one on ebay.

usually there about 25.00 , sometimes with shipping.

did you message the devs who made the exploit and files for Sloane ,

They can probably give you some detailed information that may help.

I'm trying to think , I know there was a file in one of those amonet Sloane packages that

resets the chip if your having problems .

definitely reach out to the devs friend.

sorry I couldn't be of more help .

Hey , did you try making another cable . sometimes it can be that also.

Chris.
[Fire TV Original Android Development] mamcho:
Yesterday i did the unlock from scretch wiped everything ans 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. I came from prerooted image btw. Any ideas how to get out auf this? Is it a softbrick?

Edith: it was a hardware failure. Just to let you know
[Fire TV Original Android Development] chaoslimits:
Anyone know why adb reboot recovery doesn't reboot to TWRP? I still have to input a right to get into TWRP.
[Fire TV Original Android Development] Sus_i:
This is the unbrick/root for the boxes with locked bootloader, TWRP possible via bootmenu.

You may flash the unlock via TWRP from here:

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

Then adb reboot recovery will bring up the new TWRP.
[Fire TV Original Android Development] Daimonion777:
Hello Rortiz2,

I have a "small" problem with my Fire TV 2 Sloane.

I've had the Lineageos on my Fire TV Stick 2 for a while. The ROM runs without any problems. I had now decided to install this ROM on my Fire TV 2 Sloane and am now facing a problem.

I installed Lineage Rom and Gapps and after restarting the Fire TV there is a bootloop.

The box will reboot permanently.

I can't get into TWRP either.

Can you help me please
[Fire TV Original Android Development] Bertonumber1:
Hi there,

Some more information please

What procedure did you follow? eg the locked bootloader method or the unlock, root twrp u brick method.

Also what version of Fireos was your box on before you decided to flashed lineage?

Please note the lineage for sloane firetv 2 is very limited because of the bootloader status.

You can now unlock the bootloader with the new method and gain better control of fireos but you CANNOT flash sloane lineage on the unlocked bootloader.

Your situation can be easily fixed by download and flash a stock update.bin (renamed .bin to. .zip) but first there is details.

Regards
[Fire TV Original Android Development] Daimonion777:
Did it now with the script "Unbricking / Unlocking with rooted firmware". I am now in TWRP 3.0.0.5. wanted to do a restore but got an error (Failed to mount ' /data' (Invalid argument) Was previously on FireOS 5.2.6.8
[Fire TV Original Android Development] Bertonumber1:
OK,

So if I understand correctly you followed this thread?

Thread '[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)' https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/

If you haven't I would advise doing the unlock process by following the OP to the letter.

That will take you to unlocked TWRP without the recovery menu.

Then you can flash an updated firmware or "update.bin" of FireOS it's the best way to go imo.

Lineage is very limited on sloane at the moment and will not work on the unlocked bootloader without tweaks.

Let us know where you're at
[Fire TV Original Android Development] Daimonion777:
Good news,

Finally managed to get the system up and running again. Everything works again without any problems.

Thank you for your support 🙂
[Fire TV Original Android Development] Daimonion777:
I was able to install the system now, but after about 1-3 minutes the Fire TV suddenly restarted 🤔
[Fire TV Original Android Development] Bertonumber1:
Hi there,

Make sure when you boot FireOS if rooted to give magisk manager application allow permissions.

If you wish to update magisk always boot to TWRP and flash the latest apk/zip (you can flash the apk also)

Never update via magisk manager app as it won't see the twrp mods and will oversee the adapted boot partition.

If the system rebooted it maybe a data partition problem did you format data or just wipe it.

Start with a clean install

In TWRP format data

Reboot twrp (be sure to reboot to twrp recovery)

twrp Flash your chosen FireOS update bin file.

Let the system boot and do its thing.

Reboot TWRP and flash magisk..

Reboot system.

Again, give magisk manager the allow permissions and you should be OK...

Let us know

Regards
[Fire TV Original Android Development] Rortiz2:
I had the same problem. Initially I thought it was related to high temperatures (because we always reach 40ºC in my country) but it seems it was just some kind of incompatibility problem with /cache & /data. You could try to (manually) format these with make_ext4fs in TWRP (not 3.0.0.5).​
[Fire TV Original Android Development] Daimonion777:
Not twrp 3.0.0.5?

Which TWRP Version should it be?

Do you have a link for that?
[Fire TV Original Android Development] Daimonion777:
TWRP 3.0.0.5 is version 6. Would version 5 work too? Only have one problem, in XDA there is only version 6, with the other versions the download link is inactive.

Otherwise I won't get any further. The device always reboots whether I'm restoring a backup or doing a fresh install.
[Fire TV Original Android Development] Sus_i:
Flash the amonet 1.1 zip file to get the new TWRP:

amonet-sloane-v1.1

Thread:

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Fire TV Original Android Development] Daimonion777:
Is a Linux operating system absolutely necessary here or can you also install/flash it with the existing TWRP 3.0.0.5?
[Fire TV Original Android Development] Sus_i:
If you have rbox TWRP, there is a big chance that it will work just fine.

You may flash the file via TWRP 3.0.0.5 and see whats happen, take pictures if you see an error message...
[Fire TV Original Android Development] Daimonion777:
In order.

Will try that and let you know later if it worked.

Thanks
[Fire TV Original Android Development] Daimonion777:
I have now flashed the file "amonet-sloane-v1.1.zip" with TWRP 3.0.0-5. After rebooting, I saw in TWRP that version 3.0.0-5 is installed. This means that the "amonet-sloane-v1.1.zip file" is version 3.0.0-5 😕. Saw in the forum that there is also an amonet-sloane-v1.3.zip file, would that work too?
[Fire TV Original Android Development] Sus_i:
Forget about amonet-sloane-v1.3.

You see, the TWRP 3.0.0-5 bootmenu thing starts from inside the 'system partition' at every reboot.

But the new TWRP is aviable too, placed on the recovery partition (if everything worked as expected).

In order to boot the new TWRP, try to use the old TWRP via adb rj45 network or usb connection and run 'adb shell' followed by 'reboot recovery'

PS: You may use the new unlock/unbrick thread for questions... because this is the old amonet thread.
[Fire TV Original Android Development] Daimonion777:
Got it now by installing another system backup but TWRP is still at version 3.0.0-5. Also, the Fire TV interface says "Home is currently unavailable". 😕 The box still restarts permanently...
[Fire TV Original Android Development] Sus_i:
The old TWRP is gone as soon as you install a clean stock rom (because the prerooted rom always includes the 3005 TWRP). Don't flash a stock rom until you are sure that the new TWRP works fine!

Home is currently unavailable is maybe because the rom is old af.

Make sure that the new TWRP is there, run adb reboot recovery or try the boot-recovery script from amonet. If all works as expected, grab a stock rom from this thread in the unlock thread, flash it, wipe data and cache. Then the box should work fine...
[Fire TV Original Android Development] Daimonion777:
But how do you get a newer TWRP version installed? The Amonet-sloane-v1.1 is not a newer TWRP version, it looks like. I don't get an error when installing Amonet-sloane-v1.1, but after restarting it is still version 3.0.0-5. I thought that the Amonet-sloane-v1.3 is a newer version.

What is the link from amonet's boot recovery script?

An alternative would be lineage-12.1-20200413 Rome. I've already made it to the setup screen here, but unfortunately I can't connect a Fire TV remote or USB remote here. Cannot complete setup. And with LineageOS version 12.1-20191209 the setup does not start at all after the restart. 😕
[Fire TV Original Android Development] Sus_i:
As I said, the old TWRP starts from a ramdisk on system, which starts on every reboot, as a part of the installed OS = the prerooted rom. This is/was just a workaround because the prerooted rom is created for a locked bootloader, i.e. back then there was no unlock solution aviable.

This is a old amonet file, it used also a locked bootloader = no new TWRP at all!

The amonet 1.1 from the 'unlock' thread (see the link above) is newer than the old one, difference is that it 'unlocks' the bootloader and flashs a new TWRP to the recovery partition. If you flash this zip, you have two TWRP versions installed, if the prerooted rom is still as system installed.

Scroll back, follow the link that says 'sloane and unlock', grab the zip and take a look into it.

Maybe read some of the unlock guide. If you are still confused about the zip files and/or threads and if you can't see/find the new one, compare the date...
[Fire TV Original Android Development] Daimonion777:
Good news,

i got the Fire TV box working again by installing Sloane-5.2.6.7-rooted.zip 🙂🥳.

The box could be set up again without any problems and the device no longer crashes. Of course, the system updates were blocked again.

I want to thank you for your support and your patience.

hp It's a pity that LineageOS 12.1 doesn't run on the box, but the main thing is that the system works again.
[Fire TV Original Android Development] DanielF50:
Just wanted to say thanks to [MENTION=8978978]Rortiz2[/MENTION] for spending so much time this weekend trying to figure out why my box was unrecoverable.

This script has helped it boot back to 5.2.7.1, although I can't get any internet currently due to the lack of MAC address & the serial number has been wiped out somehow, but I'm currently working out those kinks! (though no idea how I'll get the original MAC back :silly:)

As promised, here's a more detailed shot of the pin I had to jump to get my sloane into the bootrom.
[Fire TV Original Android Development] k4y0z:
For retrieving the mac address, check if your router still has it saved.

If not, try if setting a random MAC works.

Also shorting brings you into bootrom DL mode, not preloader.
[Fire TV Original Android Development] DanielF50:
Thanks, I'm going to look through some old backups of my router to find the MAC address, but I'm not sure how I'd restore it, if I find it? It's trying to connect to my current router with 00-00-00-00-00-00, lol.

Yes, sorry that's what I meant :)
[Fire TV Original Android Development] k4y0z:
idme mac_addr <mac_address>

would be the way to set it, <mac_address> being all capitals and no separators.

Check the output of

idme print

For other things you may want to restore, such as bluetooth-mac
[Fire TV Original Android Development] DanielF50:
Thanks k4y0z, but that didn't seem to work at all... All I get is "Segmentation fault"? I think this device is cursed :laugh:

root@sloane:/ # idme mac_addr G070***********
Segmentation fault
139|root@sloane:/ # idme print mac_addr
Segmentation fault
139|root@sloane:/ # idme print
boabdOid:

I have another working, rooted sloane device that I've managed to TWRP restore to this one, but none of the mac/serial etc are transferred with the restore - would there be a way to completely clone the other box, or maybe even change these in amazons pre-init files?
[Fire TV Original Android Development] k4y0z:
The segfault is weird, something is definitely up...

Does idme work on your other device?

The idme data is stored on mmcblk0boot1.

That isn't included in a TWRP backup.

If you are familiar with dd, you could copy that and see what happens, given that it is messed up anyway, allthough you should probably change the macs and serial number.

Serial number may be printed or etched somewhere on the device, maybe someone can tell you where.

Also make sure to have backups (of both devices) before overwriting anything.
[Fire TV Original Android Development] Sus_i:
Hmm, could it be that the non downgraded rpmb is the cause for the weird serial and mac address, i.e. incompatible to the other downgraded stuff?

Edit: What I meant is, maybe it's better to look whats the cause for that!?
[Fire TV Original Android Development] Rortiz2:
I think so.

As k4y0z said. brom-payload code needs to be modified for sloane.

I'mdoing some tests with MAC addresses and other stuff. I'll report later.

Cheers.
[Fire TV Original Android Development] Sus_i:
Whats about the mac and serial from [MENTION=7548783]CFKod[/MENTION]

Serial/MAC ok? Same scripts?

PS: I've picked up a 'stuck at booting' sloane box online for about 12 bucks, I'm going to test this soon :p
[Fire TV Original Android Development] Rortiz2:
His Mac serial is ok. I think maybe an extra test that might we done with Daniel ****ed up the addresses.

PS: Glad to hear that :)
[Fire TV Original Android Development] Rortiz2:
MAC/Serial restored;)

adb shell
su
echo 0 > /sys/block/mmcblk0boot1/force_ro
dd if=/sdcard/idme.bin of=/dev/block/mmcblk0boot1
echo 1 > /sys/block/mmcblk0boot1/force_ro
reboot

Thanks you :)
[Fire TV Original Android Development] k4y0z:
Did you change the macs and serial after copying boot1?

Does idme work now without segfaulting?

You shouldn't have two devices with the same macs and serial.
[Fire TV Original Android Development] Rortiz2:
Yes yes and yes;)

Changed serial with idme after copy boot1.

Thanks again.
[Fire TV Original Android Development] DanielF50:
Yeah, so I pulled the idme from my working sloane, did the above, rebooted to check it was all working & then used idme to change:

mac_addr
bt_mac_addr
eth_mac_addr
serial

I had the original serial number, just not the MAC address', so they're all random - I assume "mac_sec" can stay the same though?

Everything seems to be working fine now though & the device logged into amazon & my wifi perfectly.

Thanks for your help [MENTION=7104332]k4y0z[/MENTION] & [MENTION=8978978]Rortiz2[/MENTION]! I've kinda enjoyed my device being used as a test hahah :laugh:
[Fire TV Original Android Development] k4y0z:
Good to hear it worked out for you.

Not sure what mac_sec is used for, so if everything is working as is, I guess it's fine to leave it.
[Fire TV Original Android Development] Rortiz2:
Yeah mmcblk0boot1 did the trick. I think I'm going to add a backup option for avoid future lost serials/MAC.
[Fire TV Original Android Development] ForForkSake:
How did that even happen?

I am loving this... much better than the fire stick... memory card slot, USB and ethernet..

May pick some cheap ones up too
[Fire TV Original Android Development] genica:
I keep getting this error code and not sure how to fix it

sudo ./step-1.sh

Please, be sure to copy the recovery ramdisk into an usb or sdcard and connect it into the TV

[2019-10-23 00:35:13.771642] Waiting for bootrom

[2019-10-23 00:36:37.270181] Found port = /dev/ttyACM0

[2019-10-23 00:36:37.271089] Handshake

[2019-10-23 00:36:37.272050] Disable watchdog

* * * Remove the short and press Enter * * *

[2019-10-23 00:36:40.726204] Init crypto engine

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 537, in write

n = os.write(self.fd, d)

OSError: [Errno 5] Input/output error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

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

main()

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

load_payload(dev, "../brom-payload/build/payload.bin")

File "/home/ubuntu/Desktop/amonet-mt8173-sloane/modules/load_payload.py", line 112, in load_payload

init(dev)

File "/home/ubuntu/Desktop/amonet-mt8173-sloane/modules/load_payload.py", line 9, in init

dev.write32(CRYPTO_BASE + 0x0C0C, 0)

File "/home/ubuntu/Desktop/amonet-mt8173-sloane/modules/common.py", line 141, in write32

self.dev.write(b'\xd4')

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 571, in write

raise SerialException('write failed: {}'.format(e))

serial.serialutil.SerialException: write failed: [Errno 5] Input/output error
[Fire TV Original Android Development] Rortiz2:
Disabled modem manager?

Are you using an USB 2.0 or 3.0?

Try shorting again.
[Fire TV Original Android Development] genica:
Changing usb ports did the trick, it took a few tries though. Thanks for your help and for making this possible
[Fire TV Original Android Development] genica:
Victory was a little premature, still stuck at the white amazon logo. Trying rbox method now since everything should be downgraded I assume
[Fire TV Original Android Development] genica:
Didn't work. Everything worked up until I tried to update using rbox roms and it froze in recovery. Not thinking the bootloader wasn't unlocked I unplugged it and everything went to ****. I haven't been able to recover it since. No matter what I do I can't seem to boot this into recovery. Any suggestions would be greatly appreciated
[Fire TV Original Android Development] Rortiz2:
Short again and run step-1.sh

Cheers.