yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] :
Ok I am not positive all demo units are even able to be made into working units as they only have a subset of FireOS software because it is all they need. According to Amazon the

Amber LED	The device memory is full.

If the device doesn't have the same size memory capacity as a regular unit it could fill the existing memory so nothing else can be written to it and even if I wanted to just try to get it in fast boot mode, it wouldn't work as the device memory is already full. In normal cases I could run boot-fastboot to get it into fastboot mode right after it completes, but it fails on the demo unit but not on a normal unit.

[jim@Xeon amonet]$ sudo ./boot-fastboot.sh

[sudo] password for jim:

[2021-02-13 19:28:38.380341] Waiting for preloader

[2021-02-13 19:28:39.205895] Found port = /dev/ttyACM0

[2021-02-13 19:28:39.242975] Handshake

[2021-02-13 19:28:39.263096] Preloader ready, sending FACTFACT

[jim@Xeon amonet]$ fastboot devices

On the other normal device it would just display the device as it did when I was unlocking it earlier.

I ordered another demo unit to try and will document the success or failure of going to the process screen recorded so the process can be viewed. Who knows, it just might work next time, but I am not going to count on it.
[Fire TV Original Android Development] Seattleweather:
yes. it's normal.

Give another try based on my experience. Have first terminal, type sudo ./bootrom-step.sh then hit enter. In the meantime, have another terminal, type sudo ./fastboot-step.sh then enter. Do short again. If the bootrom go through well, fastboot should go automatically.
[Fire TV Original Android Development] KB!:
Probably not going to do anything now... when I run the Amonet 1.0.2 bootrom command it starts and then tells me " RPMB looks broken"

So it is probably trash at this point i am guessing.

I probably shorted something out permanently as many times as I have shorted it.

Am I correct in my assumption that with it showing RPMB broken that it is dead at this point???

I only question it because it continues to be detected and lose detection by my laptop constantly, like it is connecting and disconnecting continually every 15-20 seconds.

*** EDIT***

I cleaned the terminals around where I was grounding and tried the flash again...it says reboot to unlocked fastboot... it is back in fastboot mode.
[Fire TV Original Android Development] Seattleweather:
Try to unplug everything, then issue both sudo, hit enter on both. Connect A-A USB, then short then power. Need to plug in to PC directly, not hub. That's what I did twice successful.
[Fire TV Original Android Development] KB!:
I have tried this many many times to no avail.

At this point I am in fastboot mode and am afraid to try the shorting method any more for fear of damaging it further.

I almost didn't get it to go through last time. It kept telling me rpmb looks broken.

I am still waiting for someone to tell me how to flash this stuff manually in windows like @Rortiz2 mentioned.
[Fire TV Original Android Development] LocoMexican:
Thank you all for your help. Tried all the suggestions, but no bannana. I'll follow posts, and see what happens. And, if I get desperate, I still have a ftv2 unrooted with currect firmware that runs fine. Maybe the member who has succeeded 3 or 4 times can outline the specific steps he used. Thanks again for all the suggestions.
[Fire TV Original Android Development] KB!:
@Rortiz2

@Sus_i

Update... I went out and reinstalled all the Mediatek drivers and was finally able to perform the fastboot commands.

I am now in TWRP and I am formatting data, as it says to do in the OP.

It is taking a long time and there is no progress on the bar on the screen.

Here is what the screen shows....

Please advise as to the next step i should take.

My plan is to flash a pre rooted rom to start with to secure TWRP access.
[Fire TV Original Android Development] :
I went ahead and did my last unrooted non-demo unit today and it didn't take long to get done, but I am sill trying to figure out if the Demo units will even work.
[Fire TV Original Android Development] :
Find Rbox's latest compatible ROM to install. https://xdaforums.com/t/firetv-2-sloane-prerooted-stock-images-5-2-7-6_r1.3309783/

put it on a micro sd and install from there
[Fire TV Original Android Development] KB!:
Just did... I installed it then rebooted recovery and made a backup then rebooted system.

It bootlooped at the white Amazon logo several times. I unplugged the power and plugged it back in and now it is booting up, sitting at the optimizing system storage and applications screen now.

Once it boots up completely I will enable adb and I will reboot recovery again and make another backup.
[Fire TV Original Android Development] :
I usually just gives you the option of loading recovery on startup.
[Fire TV Original Android Development] KB!:
It is up and running... finally... thanks for everyone's help.

One more question...

When I make a backup in TWRP, is it normal for it to say

"unable to locate '/boot' partition for backup calculations."

???
[Fire TV Original Android Development] LocoMexican:
Anyone have suggestion on how to load Mediatek drivers on a Rasp pi 2? I pulled out my good fire2 and can't get past inital errors like before, but now the rpi2 shows message of can't find MTP device???? Thinking this might be due to lack of drivers. Running Ubutu on rp2. Maybe I should re-load fresh os with something like Debian or some other linux based os. Thoughts please.
[Fire TV Original Android Development] :
There aren't really any Mediatek specific drivers for Linux to use adb/fastboot. If you can see the box with fastboot, there isn't really anything you should need to change.
[Fire TV Original Android Development] Sus_i:
(y)

Do you use rbox TWRP?

You can use Rogers TWRP too, adb reboot recovery or the boot-recovery script will boot into it fine.

I've shorted my box countless times during tests for Roger. It isn't hard, but you need to be careful. Unlike the 4k stick, sloane won't boot at all with a damage on DAT0.

As k4y0z already said, the LK has to be on a specific version and nobody knows if your demo box OS was on that. The minimal step skips flashing LK and TZ images, so its best if you start again from the beginning. In your case that would be the OS. Update your ubuntu system to a recent version, then do all the steps from OP like this:

sudo apt update

sudo add-apt-repository universe

sudo apt install python3 python3-serial adb fastboot dos2unix

->Type Y if the system asks you to do so.

sudo systemctl stop ModemManager

sudo systemctl disable ModemManager

Then download the amonet zip with ubuntu.

Extract the zip with ubuntu.

Browse in the amonet folder and open up a terminal window.

run: sudo su

then run: ./bootrom-step.sh

Now take your box. Grab a soft flexible copper cable , clamp it on one side to GND. Use the other end of the cable to short the DAT0 resistor. You need to keep this short, until the script tells you to remove it. While shorted, connect the power supply to the box, wait 10 seconds and then connect the USB a-a cable to ubuntu. In case the script tells you to remove the short, remove the short and press enter. If you get an error, copy/paste it here.

If you see that the LED starts flashing between your shorting, the short wasn't proper. You need to cut the power/usb and start again.

Same if the LED starts flashing just at removing the short.

Take your time, do the procedere a few times and it will work.

Post your terminal output if you like.

If it worked for you, don't use the bootrom-step again.

If you are lazy like me, you can leave the power supply connected and 'short' the whole power rail of the box until the DAT0 short is in place :D I won't tell you a pad for this, you need to find it yourself with a meter. Hint: Such a pad isn't far away from DAT0. Quick and dirty, but don't damage something^^
[Fire TV Original Android Development] KB!:
Yes it was in Rbox's TWRP.
[Fire TV Original Android Development] Michajin:
All 3 of my Demo Sloanes are done. The last one i had a few issues where it was stuck in the bootrom if anything showed up (MT6227 phone ), the bootrom step would say complete and rebooting to unlocked fastboot, but it would stay in bootrom. I ran the brick script and then it booted to unlocked fastboot and i was able to flash recovery. All good!

On a side note, i would flash stock and magisk. The prerooted TWRP disables the native recovery, in a emergency from boot you just run the boot-recovery script. I am on the latest ROM with magisk 21.4. A accidental update from Amazon would wipe the prerooted TWRP and leave you to shorting, resets, and restores to get back into the unlocked twrp. My .02$ Enjoy!
[Fire TV Original Android Development] Michajin:
If it helps, after rebooting and resetting a couple times on my Demo box it said it was on 5.2.6.3 ,which is the time from it suggested when it was saying 5.5 (July '18). So it could have used mtk-su (good up to 5.2.6.9). i was completely stuck on my last one. Script ran and said booting into unlocked fastboot, but it did not reboot. I would short it and it was stuck on MT6227 phone (sometimes, other times nothing would show up in lsusb and no lights), unplugging it powering down and whatever, it looked totally bricked. I ran the minimal script and shorted a few times, finally ran it scrpit and it booted into fastboot mode and I was able to finish. It sounds very similar to @LocoMexican issue. Don't know if this helps at all...
[Fire TV Original Android Development] LocoMexican:
Got it going sort of. Running lastest software, but no su and it blocks magist from running. Regardless, it now works as a standard ftv2 instead of a fleabay Alex commercial. I'll post screens later after I figure out how to get them edited with applicable responses. Thanks everyone.
[Fire TV Original Android Development] KB!:
When I tried to install Magisk in TWRP it failed. It isn't that big of a problem as I am running one of Rbox's pre rooted ROMs but just thought it was odd.

It was Magisk 19.5? I believe, can't remember off the top of my head.
[Fire TV Original Android Development] LocoMexican:
Follow-up. Used Amonet 1.01 throughout. Opened two terminals. Ran sudo su in both terminals. Used terminal one for bootrom-step.sh. After a lot of tries ending with errors, I ran bootrom-step-minimal.sh in terminal one. Ran fastboot-step.sh in terminal two. Set up so both were waiting on device.

Then, I set up short on dato. Next I powered device up, waited about 7 or 8 seconds and then plugged usb a-a into my raspberry pi.

Terminal one started doing its thing, including telling me to remove short and enter, which I did. The flash continued all the way to the end. Just as it quit entering scrip, termina two started doing its thing. Unfortunately, I lost the printout for terminal one trying to copy it. Attached is the results from terminal two using flashboot-step.sh.

pi@raspberrypi:~/Desktop/amonet1.01 $ sudo su

root@raspberrypi:/home/pi/Desktop/amonet1.01# ./fastboot.sh

bash: ./fastboot.sh: No such file or directory

root@raspberrypi:/home/pi/Desktop/amonet1.01# .fastboot-step.sh

bash: .fastboot-step.sh: command not found

root@raspberrypi:/home/pi/Desktop/amonet1.01# ./fastboot-step.sh

Press Enter to Continue...

< waiting for any device >

target reported max download size of 52429824 bytes

sending 'recovery_x' (20644 KB)...

OKAY [ 0.742s]

writing 'recovery_x'...

OKAY [ 1.123s]

finished. total time: 1.865s

target reported max download size of 52429824 bytes

sending 'MISC' (0 KB)...

OKAY [ 0.014s]

writing 'MISC'...

OKAY [ 0.017s]

finished. total time: 0.031s

rebooting...

finished. total time: 0.102s

Your device should now reboot into TWRP

root@raspberrypi:/home/pi/Desktop/amonet1.01#

I checked tv screen and it had twrp. In twrp, I formated data, and then flashed amonet 1.01 posted in OP. Next, I flashed Magist.zip. I rebooted recovery a couple of time to see if twrp was still there, then flashed the latest software for fire2 posted in this thread. Finally, from twrp, I rebooted system.

The device booted up and installed new unmodified rom and then seems to run just fine. However, I do not have root access, and when I checked installed programs, it shows Magist. When I try to run Magist, it asks permission and when I say yes, the software blocks the program from actually running. When I reboot the device, it does not go to twrp on boot up. So, as I said, I'm thrilled it is running something other than an Alex commercial, but disappointed with the limitations. I was hoping to use Magist to load some programs I like to use but which require boot access, but no banana.

I want to express my gratitue for all the suggestions posted. You guys are great.
[Fire TV Original Android Development] Bertonumber1:
When you boot up the system for first time you have to go into settings>My firetv>Developer options and enable adb and unknown sources.

Next, Goto "manage installed applications"

and give the magisk manager permissions in the menu.

Click on Magisk and allow him permission to access to storage. If he prompts to perform additional setup hit "cancel"

(Never update the Magisk zip on the ramdisk from within the magisk app always use TWRP)

Now you should have root#. If not, just adb reboot recovery to twrp and flash latest magisk zip again and reboot.

As a quick shortcut to recovery install the powermenu little Vic apk.

This app let's you boot to recovery/reboot from the home screen launcher. Which is pretty handy

Hope this helps

Regards
[Fire TV Original Android Development] comm-ents:
Unfortunately the update overwrote the prerooted version with a standard unrooted version and you would have to go through the whole process again to unlock, but you would have to use the latest prerooted version once it is available so there no updates to mess it up. and then block future updates after that. I decided to just wait for the newest prerooted version so I don't have to go through the process again.

The good thing is that it is a fully functional unit for reasonably cheap.
[Fire TV Original Android Development] Bertonumber1:
Can you not just clear the updated rpmb then flash another zip? I'm sure Rortiz2 has a zip for this.

Always its best to disable ota as soon as possible.

pm disable com.amazon.tv.forcedotaupdater.v2

pm disable com.amazon.device.software.ota

pm clear com.amazon.device.software.ota

pm disable com.amazon.device.software.ota.override

Regards
[Fire TV Original Android Development] Sus_i:
Nope. Nobody needs to do the unlock again at this point.

We don't need the prerooted rom too (which is the rom for the locked bootloader),

we can use the stock rom with magisk (because the bootloader is unlocked).

No need to flash amonet again. ;)

Congratulations

It isn't a problem that the bootmenu/rboxTWRP/the prerooted is gone now.

You did a full unlock, which installs TWRP on the recovery partition.

This mean we can boot anytime into it, with adb reboot recovery or with the boot-recovery.sh script.

The OTA update process can't harm the unlock at all, i.e. the unlock and TWRP is still fine.

All you need to do at this point is run adb reboot recovery, in order to boot TWRP.

Then flash the magisk zip.

Reboot.

Remember, everytime a new rom gets installed/updated, you need to flash magisk again, in case you want root access on the stock rom. Thats all.

You can disable the OTA process too if you like, berto posted the commands above...

Note: Please don't use magisk together with the prerooted rom. It is already rooted by a supersu system install. Use magisk with the stock rom...
[Fire TV Original Android Development] k4y0z:
You are probably using rbox-twrp instead unlocked twrp.

I don't think there's any reason to use an old Magisk release either.

Can you please stop giving nonsense advice?

There is no reason to redo the unlock.

We currently DO NOT recommend using the prerooted ROM together with the unlock.
[Fire TV Original Android Development] KB!:
Ok, I think your right, I believe I was in the Rbox prerooted ROM when I tried it. I was kind of desperate when I finally got the box up and running again after having so much problems so I flashed what I already had on my SD card which was the Rbox ROM.

A couple more questions if I may.

1. Is there any reason not to upgrade all the way to 5.2.7.7 at this point since the bootloader is already unlocked???

I thought i remembered reading something about not going beyond 5.2.7.3 for some reason or another.

2. What is the best method at this point to get rid of the pre rooted ROM and flash back to a stock ROM with Magisk???

Please list the steps like Format Data>Flash Rom (Zip or bin???)>Flash Magisk>etc.

3. Is there a boot menu that is able to be flashed that is compatible with this to get into TWRP???

I realize it isn't necessary, as we can boot through ADB, I was just curious.

4. Also the latest Magisk is ok to use?

Sorry for all the noob questions, I just don't want to screw anything up with this box at this point... lol

I am probably going to do the Unlock on my other box as well once I get this one nailed down.

My other box is already rooted and has TWRP (Rbox 5.2.6.0) so I guess if I read the instructions correctly I just need to flash the Amonet zip>Format Data>Flash Magisk>Flash stock Rom>Profit... is that correct???

Is there any advantage to keep the older 5.2.6.0 software???

Thanks for all your help.
[Fire TV Original Android Development] k4y0z:
5.2.7.7 should work fine AFAIK.

Boot into unlocked TWRP.

Wipe Data

Install Stock-bin (rename .bin to .zip)

Install Magisk

Not currently, we'll have to ask @rbox to make his ROM compatible with the unlock.

Latest Magisk should be fine.

Yes, but flash stock ROM before installing Magisk.

Not that I know of.
[Fire TV Original Android Development] KB!:
So just Wipe Data, Formatting (where you type yes) isn't necessary?
[Fire TV Original Android Development] k4y0z:
No, format is only neccessary after unlocking initially, because the partition table was modified.
[Fire TV Original Android Development] KB!:
Gotcha, thanks again for all the help.
[Fire TV Original Android Development] comm-ents:
Yes. I suppose that I was meaning to say to keep the pre rooted image instead of saying unlock. The issue is that if there is an update, it is kind of hard to get around letting it do the update before you can access the interface until the update is completed. Since I don' t really need to use it I figured I can wait until the latest pre rooted version is available. I would prefer to turn off updates like you do and only upgrade when there is an upgrade that is worth installing.
[Fire TV Original Android Development] Bertonumber1:
Just disable updates, if you want to use magisksu simply reboot to twrp if unlocked and flash magisk after you flash a clean unrooted update.bin.

If you prefer supersu you can do the same (flash clean unrooted and then flash supersu)

With most ota updates (in respect of fireos) you won't notice any difference in performance or an amazingly new striking appearance or even as you state "worth installing"

Unless they push marshmallow/nougat via fota (which I highly doubt).

Apart from that I don't understand why you want to wait for the next prerooted. It's just the same purpose grabbing a stock update bin (renaming it to zip) flashing it, then flashing su whether magisk or supersu.

Simply disable OTA apks
[Fire TV Original Android Development] Michajin:
Have you tried to boot into recovery and verified this? It would have overwrote the pre-rooted twrp but not the stock recovery (that was replaced by TWRP). They are different.. WHat recovery do you goto when you do a adb reboot recovery?
[Fire TV Original Android Development] Michajin:
i have downloaded stock. flashed it and taken al updates. I still have a unlocked recovery...
[Fire TV Original Android Development] KB!:
@k4y0z

Do you have link to the latest Magisk?

I am having issues locating a Magisk zip to download, which is why I tried the 19.x the other day.
[Fire TV Original Android Development] k4y0z:
https://github.com/topjohnwu/Magisk/releases :rolleyes:
[Fire TV Original Android Development] KB!:
Sorry, I was having issues finding it. Thank you.
[Fire TV Original Android Development] KB!:
I some how managed to get myself stuck in a bootloop while attempting to change over to a stock firmware.

I booted recovery via ADB and flashed the newest Amonet 1.1 zip. it flashed and said it would reboot into unlocked TWRP.

When it booted back up it booted backup into Rbox's TWRP recovery not the unlocked recovery. I know this because i had to hit the right arrow on my keyboard to choose recovery. i formatted data by typing yes.

I went ahead and flashed the stock ROM Zip file and then I got to thinking about it not being in the unlocked recovery.

so I went back and formatted data and reflashed the Amonet zip file and it was successful and rebooted again but this time I didn't hit the right arrow to boot into Rbox recovery because I thought that maybe that was why I didn't end up in the unlocked recovery last time.

Now the box boots up to the colorful amazon logo and then goes to the " Optimizing system storage and applications" and it says it will take approximately 10 minutes. It sits there and the progress bar starts going across and when it gets to the other side like it is going to finish it boot loops back to the amazon logo and starts again with the same thing.

At this point I can't connect with ADB from my phone to tell it to reboot recovery.

What are my options to get back into recovery???
[Fire TV Original Android Development] KB!:
@Rortiz2

@Sus_i

@k4y0z

@Michajin

Anybody???
[Fire TV Original Android Development] KB!:
@Rortiz2

@Sus_i

@k4y0z

@Michajin

I can get it to stop and hang at the preloader if I use one of the .bat files from the unbrick thread.

It makes the handshake and goes forward but the minute I try to connect to it with Ubuntu to flash anything it disconnects (you can hear the computer make a noise like the USB was unplugged).

Any ideas short of opening this stupid device back up and shorting????

It seems like as far as it gets into the boot up process that there must be another way.

***EDIT***

Opened device back up and shorted. Had to do some trickery to get it back into fastboot mode.

All seems well now.
[Fire TV Original Android Development] LocoMexican:
Thanks for the info. I was able to get twrp by running the boot-recovery.sh script as you pointed out. Then, from twrp, I installed Magist-v21.4 zIp. (I had already formated data and flashed amonet 1.01 and installed the unmodified latest software version posted in this thread). After installing Magist from twrp, I rebooted system. After the reboot, I was able to get Magist to run after following instruction posted (developer options, etc.) Figured out how to navigate Magist and was able to obtain su access. Also, in this version of Magist in the settings area, there is a prompt next to the settings prompt at top right corner of the main menu which I entered, I was able to reboot recovery. When I tried it, the device immediately rebooted device into twrp. I blocked ota updates by changing build prop version number, and all seems to be running great. I'm a happy camper. Thanks Sus_i and everyone else for the help.

Now that I'm an expert, I'm going to give my second aftv2 a try and see if I can root it. It is in an unmodified condition running current ota update. Hopefully it will be a lot easier than the demo model I've been working on. Thanks again.
[Fire TV Original Android Development] Michajin:
Sorry for the late response, but you should have been able to run the boot-recovery script (it is looking for the preloader). I only flash from recovery personally. You won't ever have to run the amonet script again. Once you have unlocked TWRP you dont need to run the exploit again.