yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] KB!:
@Rortiz2

I am confused by the install instructions.

I have a Sloane Fire tv that is currently rooted with @rbox prerooted rom 5.2.6.0 with TWRP recovery funtional.

if i read this correctly all I would need to do is flash the .ZIP file in TWRP, wipe data and then flash a stock ROM and Magisk and that is it????

Or would I have to continue with the portion of the instructions that start off with...

" Important information

You have 10 seconds to force TWRP to keep ADB over USB active by using"

???

I like the others am running a Win 10 machine.

Thanks in advance for your help.
[Fire TV Original Android Development] Sus_i:
Almost correct, but don't wipe data, u need to use the 'format data' button...

The thing with the 10 seconds mean, that you've 10 seconds in order to connect to it over adb... (if u like to run some adb shell stuff). As soon this timer runs out, you can still use twrp with a mouse or a keyboard/touchpad, together with an USB hub + storage stick if you like...
[Fire TV Original Android Development] Sus_i:
Yeah, latest stock rom + magisk is fine.

Crucial part is the 'shorting' of DAT0. The box won't boot with a damage over there, until it gets fixed with a new 47k smd resistor.

Shorting isn't easy, because the box sucks power over two lines (power supply and usb).

An usb cable with an interrupted 5v line may work better (taped pin on one side of the cable). ;)
[Fire TV Original Android Development] Rortiz2:
I guess you could root with mtk-su and dump preloader/tz/lk before unlocking and rooting the box.
[Fire TV Original Android Development] Sus_i:
I guess you mean 5.0.5? Current OS is 5.2... ;)

Instead shorting... if your box is on 5.0.5.1 or older, the firetv2_recovery_v#.zip from rbox should work too for rooting... just in case mtk su isn't working somehow on that OS. It will install temp twrp and you should be able to install a prerooted with it. Then use the unlock zip from Roger.
[Fire TV Original Android Development] Michajin:
No, it is 5.5. It only has 2 digits. After getting it out of demo mode I factory reset. After rebooting and the optimization, it went right into a black screen, no setup or anything. It seems there is a barebones of amazon apps on it. I can not find Developer options. If i hold the home i can get into the Menu. the 5.5 has a installed date of July 6th, 2018.
[Fire TV Original Android Development] Rortiz2:
If preloader is old enough you should be able to install rbox's unbrick image. From there boot rbox TWRP and backup preloader/lk and tz.
[Fire TV Original Android Development] KB!:
So just to clarify, what does all the stuff that is flashed in ADB after the "Important Information" part actually do/accomplish?

Also, what is the advantage of Unlocking the boot loader over my current TWRP setup?

Is it more of a permanent unlock/root?

And what advantage does Magisk have over SU?

Thanks in advance.

Sorry for all the questions, I am a newb when it comes to some of this stuff.
[Fire TV Original Android Development] brick00444:
I also bought one of the demo boxes to play with. Haven't received it yet. Keep us informed on your progress. Thanks
[Fire TV Original Android Development] LocoMexican:
Got it. Thanks for the clarification. I'll report my results.
[Fire TV Original Android Development] Sus_i:
Your main advantage of the unlock/twrp is that you can update with stock OTA files.
[Fire TV Original Android Development] LazorBlind:
On top of that you will be able to install custom ROMs if ever one is made. One good example is that Rortiz is working on a port of LineageOS which will bring the sloane up from Android 5.1 to Android 7, so you will have a wider variety of apps you can run on it, for instance Xbox Game Pass which requires at least Android 6. Along with other various tweaks, a new ROM can breathe new life into the Sloane.

The advantage over SuperSU is that Magisk is what is called a Systemless Root. That means that it can give you Superuser/Root features without modifying the /system partition, which some apps will check before running, and won't run if it sees something it doesn't like. On top of that, you can install various modules which can give all sorts of interesting new features and options. Think of Exposed Framework. Best example I can come up with is 1controller. This adds more or less native support for various game controllers that may not be supported by your device out of the box. PS3 controllers are notorious for not working over Bluetooth on Android (I think) 4 and up because the Bluetooth Stack (drivers for lack of a better term) was changed by google in a way that the PS3 controller cant work with. With 1controllrr however,you can make it work with minimum effort.
[Fire TV Original Android Development] KB!:
do you have the .bin file for 5.2.7.0 or anything prior to 5.2.7.3 so i will not have to open the box to short???

also, again just to clarify, if i flash this zip file and magisk in TWRP with a non rooted rom i wont have to mess with any of the ADB stuff.... is that correct???

the instructions confuse me as they seem out of order to me. It says if you are already rooted with custom recovery then you can just flash this zip but then shows ADB script before flashing Magisk.
[Fire TV Original Android Development] Michajin:
Looking for a way to turn on developer options? It doesn't show up in settings on this 5.5 version.... The interface indicates it is 5.2.4.0 or newer. It says it is july of 2018. I don't see a clear way of turning on developer options. I am highly confident in the shorting method, but want to do some playing on this (seems to be a non-release version of fire OS). Anyone have any ideas?
[Fire TV Original Android Development] Seattleweather:
tried today. FireIso is not going to work. It does not have apt at all.
[Fire TV Original Android Development] k4y0z:
Try using aftv2-tools to dump preloader, lk and tz and boot.

Possibly you can also use it to wipe preloader (after dumping it) so you don't need to short.

Once unlocked dump system as well.
[Fire TV Original Android Development] Michajin:
This is what i did after my first issues (my 2nd and 3rd unlocking was done fast and easy). Download and transferred the script, a Stock rom (i used 5.2.7.7 with my last), and magisk onto the a USB. Booted to rbox's twrp in the pre-rooted rom. Ran the script, it boots into unlocked TWRP, formatted DATA (with the YES), then flashed the stock rom and magisk. I opened mine once, but turns out I didn't need to because I could have ran the boot-recovery script. If you have and issue (errors trying to flash after format) click the reboot into recovery.
[Fire TV Original Android Development] LazorBlind:
In that case I would suggest Debian. Personally I use a Raspberry Pi 1 with the latest Raspbian (based on Debian installed.)
[Fire TV Original Android Development] Rortiz2:
The instructions are ok, if you are not able to read them it's not our fault. Important information part has nothing to do with the unlock process...

Once you're unlocked the FireOS version doesn't matter as unlocked TWRP will prevent the zip from updating TZ/LK/PL.

I'm not sure what do you mean with ADB stuff but you should be able to root a non-rooted ROM with Magisk after flashing the unlock-zip (and formatting userdata).
[Fire TV Original Android Development] Sus_i:
Fire OS 5.2.6.8 :

https://d1s31zyz7dcc2d.cloudfront.net/5edbc5484adaf81545c3bdda9ea82618/update-kindle-full_sloane-36.6.3.0_user_630508620.bin

That is 5.2.7.1:

https://d1s31zyz7dcc2d.cloudfront.net/1776a538e62250f6e7efb905234c2113/update-kindle-full_sloane-36.6.4.6_user_646581820.bin

and this is 5.2.7.2:

https://d1s31zyz7dcc2d.cloudfront.net/06a2c45dcc3a2554ef32d52cd396980c/update-kindle-full_sloane-36.6.4.8_user_648595220.bin
[Fire TV Original Android Development] brick00444:
Successfully flashed everything. Went from "Demo" os to 5.2.7.6. What version of Magisk should I use?
[Fire TV Original Android Development] Seattleweather:
Need help to clarify it since I am in the middle of doing this. Please see my Questions in red.

If FireOS is still accessible there are other means of recovery, don't continue. Q: 1. With power and A-A USB or USB only? 2. what are those other means?

If your device shows one of the following symptoms: Q: Again, with power and A-A USB or USB only?

It doesn't show any life (screen stays dark)

You see the white amazon logo, but cannot access FireOS.

If you have a Type 1 brick, you may not have to open the device, Q: Mine boot up normal if I have both power and A-A USB, but did not boot up when I have A-A USB only. What to do next?

My chip also is different than the photo you showed. not sure if it will make difference or not

isusb

Bus 004 Device 009: ID 0e8d:0003 MediaTek Inc. MT6227 phone

I also got error message when I used short method.

user1@user1-ThinkPad-T60:~/Desktop/amonet$ sudo ./bootrom-step.sh

[2021-02-10 19:34:50.193885] Waiting for bootrom

[2021-02-10 19:35:48.578236] Found port = /dev/ttyACM0

[2021-02-10 19:35:48.580145] Handshake

[2021-02-10 19:35:48.584100] Disable watchdog

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

[2021-02-10 19:36:07.197526] 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 164, in <module>

main()

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

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

File "/home/user1/Desktop/amonet/New/modules/load_payload.py", line 112, in load_payload

init(dev)

File "/home/user1/Desktop/amonet/New/modules/load_payload.py", line 9, in init

dev.write32(CRYPTO_BASE + 0x0C0C, 0)

File "/home/user1/Desktop/amonet/New/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

Thanks a lot!
[Fire TV Original Android Development] Michajin:
What method did you use?

Were yours on that weird 5.5 version also?

Thanks (I am going to work on mine this weekend)

I used magisk 21.4 on my other ones without issues...
[Fire TV Original Android Development] brick00444:
I used the shorting method. It took quite a few tries but got 2 of them going. I didn't check the version before unbricking, they booted to the demo loop for alexa though.
[Fire TV Original Android Development] brick00444:
I used "bash -x ./bootrom-step.sh" and "bash -x ./fastboot-step.sh" seemed to work good too.
[Fire TV Original Android Development] Bertonumber1:
Don't forget if you've flashed the unlock and you can't connect with :

adb reboot recovery

You can open a terminal inside amonet and :

sudo ./boot-recovery.sh

This will get you back to unlocked twrp if you are stuck on Amazon logo.

Regards
[Fire TV Original Android Development] brick00444:
Good to know. Thanks and Thank you to everyone that made this all possible. Can't wait to see whats next for "sloane"
[Fire TV Original Android Development] comm-ents:
Tried to unlock a Demo version, but I wasn't able to complete the process and the device only powers on, but never displays anything.

The initial bootrom-step.sh was completed without reporting any errors and proceeded to reboot, but it never loaded fastboot even though it did display the boot logo for a bit before going blank. I have tried to get it to work, but it seems that adb doesn't even recognize it no matter what I tried to do. I am just wondering if it was possible that the software assumes that the version of the OS on the fire tv is complete so that it doesn't install certain resources because it assumes they are already there like the development tools. It would be nice to say that the demo units can be redone as complete units that are rooted/unlocked, but that has not been my experience as I only have a device that now seems to be truly bricked as the procedure didn't go as planned.
[Fire TV Original Android Development] LocoMexican:
How did you do it? Please outline steps you used. Thanks.
[Fire TV Original Android Development] Rortiz2:
Check if there are any scratches on the motherboard. That looks like an HW issue.
[Fire TV Original Android Development] Sus_i:
Give the boot-fastboot.sh script a try...

and check your fastboot setup on PC too, in case there isn't a device.

The box should stay on the b/w logo, while in fastboot mode.
[Fire TV Original Android Development] Sus_i:
Doesn't matter...

In case your box won't boot anymore, DAT0 resistor is maybe damaged.

Check if you get MediaTek Inc. MT6227 phone also without any short.

What steps are unclear? How far did you get?
[Fire TV Original Android Development] brick00444:
I followed the guide to a "T".
[Fire TV Original Android Development] brick00444:
My 2nd one did something similar. I found that if nothing seems to work I would run the ./bootrom-step.sh command and plug power then usb without the short and it said to remove the short even though I didn't have it shorted. It ran the script and was fine.
[Fire TV Original Android Development] comm-ents:
After the initial flash, I tried to reflash, but get the same error and I can't do anything to get past that point.

I could only short again, but couldn't reflash the device after the initial reconfiguration.
[Fire TV Original Android Development] brick00444:
Not sure how many tries it took on the difficult one, but it was a lot of tries with errors before it worked.
[Fire TV Original Android Development] comm-ents:
The boot-fastboot.sh doesn't work because the essentially the device is not recognized. The issue is with the Fire TV and not my computer.
[Fire TV Original Android Development] comm-ents:
It worked just fine in demo mode and up until after the reconfiguration.
[Fire TV Original Android Development] comm-ents:
My experience with the Demo unit so far:

Was able to short and reconfigure without errors.

Was not able to get into fast boot after it rebooted as it appears not to be available.

lsusb didn't recognize the device as being connected either.

Verified i can see another Fire TV 2 connected to USB:

Bus 003 Device 126: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

Attempted to redo by shorting again a re doing the inital script, but it failed in the same way as others have already reported.

The chip on this Motherboard is from Sandisk.

The following was during the 2nd attempt to run the initial script:

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

[2021-02-11 10:04:39.232261] Init crypto engine

Traceback (most recent call last):

File "/usr/lib/python3.9/site-packages/serial/serialposix.py", line 621, 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 "/amonet-sloane-v1.0.0/amonet/modules/main.py", line 143, in <module>

main()

File "/amonet-sloane-v1.0.0/amonet/modules/main.py", line 28, in main

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

File "/amonet-sloane-v1.0.0/amonet/modules/load_payload.py", line 112, in load_payload

init(dev)

File "/amonet-sloane-v1.0.0/amonet/modules/load_payload.py", line 9, in init

dev.write32(CRYPTO_BASE + 0x0C0C, 0)

File "/amonet-sloane-v1.0.0/amonet/modules/common.py", line 157, in write32

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

File "/usr/lib/python3.9/site-packages/serial/serialposix.py", line 655, in write

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

serial.serialutil.SerialException: write failed: [Errno 5] Input/output error
[Fire TV Original Android Development] k4y0z:
Please make sure the device is detected as

Bus 002 Device 013: ID 0e8d:0003 MediaTek Inc. MT6227 phone

and not as

Bus 002 Device 014: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

(See Post #2 for details)

Also please edit your posts if you want to add information instead of double-posting, thanks.
[Fire TV Original Android Development] comm-ents:
The post has already been updated. The reconfigured Demo unit is not recognized on my Linux system while another untouched Fire TV 2 is.
[Fire TV Original Android Development] k4y0z:
If it's not recognized at all, it's a hardware-issue.

EDIT:

The error-message you just posted clearly shows that IT IS recognized...
[Fire TV Original Android Development] Seattleweather:
I am having similar issue. And it is recognized by Linux when I short it and with power on only.
[Fire TV Original Android Development] k4y0z:
Please check what device is being detected, as I've just described here
[Fire TV Original Android Development] Seattleweather:
Bus 002 Device 013: ID 0e8d:0003 MediaTek Inc. MT6227 phone
[Fire TV Original Android Development] k4y0z:
Does it show up as this device if you do not short?

If so, run the script and hit enter, then plugin the device and post the output.
[Fire TV Original Android Development] Seattleweather:
No. lsusb does not show it and bootrom-step is not moving at all (with power and USB)
[Fire TV Original Android Development] k4y0z:
Keep trying then, give it a moment before hitting Enter, after removing the short.
[Fire TV Original Android Development] Seattleweather:
Did on multiple PC and different Linux. All shown the same error messages after I removed short and hit enter.

I did not turn on USB debugging. Should I do that?

did multiple times again, and serial.serialutil.serialException: write failed shown up when i had good short (MT6227 phone)
[Fire TV Original Android Development] comm-ents:
It never stated anything of the sort.

The update stated:

Verified i can see another Fire TV 2 connected to USB:

Bus 003 Device 126: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

It means I only verified I could see a Fire TV 2 on my system when connected via USB. The purpose of the statement was just to verify it wasn't an issue with my Linux system recognizing Fire TV 2 when connected via USB.

I could not and cannot see the Demo Fire TV device after I just flashed listed on my system when connected. Just because it is not recognize doesn't automatically make it an hardware issue. The unit is a Demo unit and so it doesn't even have the same FireOS version that the software is meant to work with.
[Fire TV Original Android Development] Rortiz2:
Yes, I also faced Input/Output errors as well (lot of times). Try to short first and after 5 seconds plug in the A-A cable.
[Fire TV Original Android Development] comm-ents:
It never stated anything of the sort.

The update stated:

Verified i can see another Fire TV 2 connected to USB:

Bus 003 Device 126: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

It means I only verified I could see a Fire TV 2 on my system when connected via USB.

I could not and cannot see the Demo Fire TV device after I just flashed listed on my system when connected.

Doesn't
[Fire TV Original Android Development] k4y0z:
Do as @Rortiz2 suggested and also make sure ModemManager is disabled.

You did say:

And then showed the output of the script, clearly indicating that it detected a device.

This isn't the right mode for using the scripts. Fastboot, ADB, preloader and bootrom all present themselves as different USB devices.

If there is no hardware-fault and no issue with your PC/USB-cable etc then the device will always be detected when shorted correctly.
[Fire TV Original Android Development] LazorBlind:
Just throwing this out there in case its useful to anyone.

I found that doing the short and plugging in the power with USB already connected wasn't working for me anymore. So I tried holding the short, plugging it in with USB disconnected and amonet waiting for bootrom, then connecting USB.

This may be rather difficult when doing it by hand but it seems to be much more consistent.
[Fire TV Original Android Development] Seattleweather:
When to plug in the power? after cable or after cable?
[Fire TV Original Android Development] Rortiz2:
Updated OP with v1.0.1 which includes script permission fixes. If you're already unlocked, you don't need to update to 1.0.1 as no major changes have been made.

I also added ADB instructions (with root) for those who have problems with bootrom.
[Fire TV Original Android Development] Rortiz2:
Follow @LazorBlind instructions.
[Fire TV Original Android Development] G S W:
Can someone please make a video on exactly how to do this without bricking/breaking anything? I’m on Sloan non-rooted 5.2.7.7 everything is updated to latest possible updates. (Can’t stop the MF OTA updates I tried ADB method it didn’t work)

I am too afraid of opening my box and breaking things for good. I cherish this device since 2015 and cannot live without it but so badly want it rooted.
[Fire TV Original Android Development] brick00444:
So did you get it going?
[Fire TV Original Android Development] Bertonumber1:
pm disable-user -- user 0 com.amazon.device.software.ota

pm disable-user --user 0 com.amazon.device.software.ota.override

pm disable-user --user 0 com.amazon.tv.otaupdater.v2

Try this to disable ota, if it doesn't work try pm disable--user --user 1 com.amazon.blah blah

This should disable without root to at least stop further ota, however you are on the latest 5.2.7.7.

Just follow the OP to the letter and you'll be okay.
[Fire TV Original Android Development] G S W:
Thanks, but

I’m already screwed. Just yesterday it OTA updated something called “Components” which didn’t do anything to the firmware, but unsure what it did or if this update broke anything that OP has worked on.

If you could find out anything about this “Components” update that just got released let me know.
[Fire TV Original Android Development] Bertonumber1:
Yeah system components is the second phase of the ota 5.2.7.7 update (6.2.7.7 on mantis). This won't affect the root/unlock/twrp exploit provided you have a device that is vulnerable to amonet.

What is your device showing up on lsusb
[Fire TV Original Android Development] G S W:
Oh thank god, so the Components ruins absolutely nothing. What did it do then?

I have a 2nd gen box Sloane, that’s vulnerable to amonet as far as I’m aware?

I cannot answer your last question because I am too afraid open my box up for root as I might ruin it and brick it for good. I need someone to maybe post a really noobie guide on how to root the Sloane box and a guide/video on opening the device itself because I’m too afraid I’ll break something.
[Fire TV Original Android Development] Bertonumber1:
Ah I see, no the components update is just minor adjustments to /system files. You won't break anything (opening up box / shorting) just be delicate when applying the short, use a thin piece of copper wire (not hard rigid material like paperclips). Use a magnifying glass to locate the dat0 pad and then when instructed with the amonet script just apply the short.

I can guide you through the process if you want via telegram or some other communication platform
[Fire TV Original Android Development] Seattleweather:
Same error message. I also found by doing this reverse order, lsusb won't show MT6227 phone or MT67xx phone anymore.
[Fire TV Original Android Development] G S W:
Yeah man that would be great!

it doesn’t have to be today, whenever you have time we can both work out a set schedule to do it.

Add me on Telegram, @RedanS95

I am waaaay too afraid of doing this for fear of breaking my box for good. I’ve loved this thing since it came out in 2015.
[Fire TV Original Android Development] Bertonumber1:
Have you tried this?

Disconnect DC power from Sloane

Disconnect USB a to USB a

Run sudo ./bootromstep.sh hit enter

Plug the DC power back in and wait 40-60secs

After 40-60 secs Plug USB to USB a back in

Your device should then flash the partitions

Regards
[Fire TV Original Android Development] Seattleweather:
Plug the DC power back in and wait 40-60secs after short? when to remove short? Nothing shown up without short.

Thanks!
[Fire TV Original Android Development] Bertonumber1:
No! Run the script with USB disconnected, plug in DC power and wait 40 secs, and then connect the USB. If it prompts to hit enter then do so.