yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Rortiz2:
There is no known way to get rid of permanent write protection (so yeah, there's no way to fix it). I also have a box in the same state (which actually uses Samsung eMMC too) and we already tried a lot of things (we even tried using Samsung backdoor cmds) with no luck.

If you ever manage to dump the ext_csd, you can check the eMMC status with this tool. If the eMMC went into read-only mode, it'll show you the following output:

Permanent write protection,PERM_WRITE_PROTECT,1,R/W,[13:13],0x1
Temporary write protection,TMP_WRITE_PROTECT,1,R/W/E,[12:12],0x0

(0x1 means PERM_WRITE_PROTECT is enabled)
[Fire TV Original Android Development] atdog69:
I think I'll give up now, 4 days of trying is enough.

At last there is one thing I would look into and that's the eMMC status if you can tell me how to "dump the ext_csd" ? I don't even know how to download that tool nor how to use it...
[Fire TV Original Android Development] Rortiz2:
Check PM, I'll send you a special amonet package
[Fire TV Original Android Development] teddy12:
I was able to bring my Fire TV box back to life using the shorting method, the best way I found to successfully short the correct point was to use a medium-sized safety pin which gives you something stable to press onto the metal cover of the adjacent chip and also gives you a sharp point on the other end to short the right place on the circuit board.
[Fire TV Original Android Development] First_Degree:
Couple questions, been a while since I dusted off the sloane:

Currently running latest rbox prerooted.

-Is it possible to unlock the bootloader without using adb? (i.e. do everything from rbox twrp on the device?)

-If so, what are the specific steps to unlock, update and root via magisk? (i.e. install amonet-sloane-v1.1.zip, clear cache/format/etc., then allow update via OTA, then install magisk renamed apk as zip from twrp?); specifics welcome for a dummy like me

-Sounds like 5.2.8.7 stock software update recently was pushed out - any word on issues with this latest version? I don't run custom launcher, but have considered experimenting with a vanilla ATV, but sounds like this update may block that...

-With root, has anyone been able to get this particular device to use the microsd as shared internal storage? I've seen some OTG options for newer revisions (4k stick, etc.), but haven't seen anything for Sloane with microsd. Even when installing apps to sd, still have a ton of stuff taking up space on the internal storage...

Apologies for the newbish nature of this post. Really have only used linux minimally, tried prepping environment (Win 10 PC), doing this with provided instructions via ADB. Was able to connect, and navigate to the correct directory, but had numerous issues executing the scripts (permission denied, etc.)

Appreciate any assistance!
[Fire TV Original Android Development] Sus_i:
Yeah.

First thing I would do (after the amonet flash + format data) is to boot into the new recovery., i.e. not the rbox one. In case you can boot into it, flash also a new stock rom + magisk if you need root.

It's best if you have an usb a-a cable, as a backup option (second post) :p
[Fire TV Original Android Development] First_Degree:
Appreciate the response!

Ok, notes so far (please keep me honest :)):

-step 1: boot into rbox twrp

-step 2: flash the amonet zip from rbox twrp (will likely be from sd card)

-step 3: format internal storage from rbox twrp

-step 4: reboot into new recovery

-step 5: flash new stock rom (from twrp)

-step 6: flash magisk (from twrp)

-step 7: reboot into updated, rooted device

Follow up questions:

-For step 4 above, do I need to trigger recovery via command line/adb from PC? (while connected USB A:A)

-For step 5 above, which stock rom do you recommend? latest (5.2.8.7, or the one just prior)?

-For step 5 and beyond, what post install wipe steps do you recommend? (wipe cache, etc.)

-While probably not the right place, per my original post, is there a way to make the system recognize the sd as shared/internal storage? I typically use adopted/external on Android devices if able, but the limited internal storage on this device has proven challenging

Again, apologies for the newbish questions, but trying to be conservative/thorough.

Thanks again for the support! Much appreciated!!
[Fire TV Original Android Development] Sus_i:
It should work just fine.

BUT it could be that you get some red errors, if you try to mount or format data (just after the amonet flashing). i.e. maybe you can't format data, then reboot into rbox twrp and the format should work...

Yes, but twrp works also over network rj45 port...

Maybe you can use twrp shell too, see the advanced tab, open the shell and try reboot recovery

this is 5.2.8.0, the latest for my box:

https://d1s31zyz7dcc2d.cloudfront.net/9b2e71811433fde29845430067ee4bf8/update-kindle-full_sloane-36.6.7.2_user_672831220.bin

You need to rename the bin-file to zip.

The amonet script edit the gpt and after this, data is a bit smaller, so the format data is important.

Flash a new OS is good, in order to remove rbox twrp, the bootmenu and the supersu install.

You can wipe cache and dalvik too, if you like.

Imo not as intSD, but fireOS will use it as extSD. Idk if there is a workarround for fireTVs.

If something goes wrong, take some pictures and report back ;)
[Fire TV Original Android Development] First_Degree:
Got it done!

Quick notes on the experience:

-Did have to connect a usb mouse to swipe allow modification in the new twrp

-Initial Fire TV setup had to search for updates, so had to disable OTA URL block in router (disabled via shell-su once back in adb)

-Was able to eventually root with Magisk, but was not able to use latest Magisk (v24.1 renamed to .zip) - new twrp would hang at "checking for Digest file..."; they've moved to an apk/app format, and newer builds don't want to install via this version of twrp (Magisk also fails to update via Magisk app; error about about partition size)

Thanks again for the assistance!!

Now I'm off to investigate removing bloat/moving more stuff to the sd card
[Fire TV Original Android Development] Sus_i:
(y)

Another way is to use the command from OP (within 10 seconds), in order to use adb via usb... then the swipe isn't needed.

adb wait-for-recovery && adb shell setprop twrp.usb.mode 0

Take a twrp backup, in case something goes wrong ;)
[Fire TV Original Android Development] Sus_i:
Amaz. just pushed the full update 5.2.8.7 to my box:

Fire OS 5.2.8.7 (674730620) for sloane

https://d1s31zyz7dcc2d.cloudfront.net/92813fdfb10e8ace163fe559c39d5ea0/update-kindle-full_sloane-36.6.7.4_user_674730620.bin
[Fire TV Original Android Development] tw39515:
I followed steps 1 - 7 everything went fine, but upon reboot i cant get past amazon checking for updates and cant get back in twrp. @First_Degree which OTA URL did you block in router.
[Fire TV Original Android Development] Sus_i:
Maybe this is something you can try...

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

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

www.aftvnews.com
[Fire TV Original Android Development] tw39515:
@Sus_i FTW nothing but net. Thanks for coming in clutch again!!!!!!!!
[Fire TV Original Android Development] teamfresno:
Do you guys just flash newer versions of Magisk via TWRP or through the app? I've never used Magisk and it's alerting me to update on the app. Thanks!
[Fire TV Original Android Development] SweenWolf:
If the update is about the app (Magisk Manager) you can update that, but if the update is for Magisk Itself then do not update, your device will break.

update only via TWRP
[Fire TV Original Android Development] teamfresno:
Thanks. I opened the app up and it looks like it's an update for the app. I have v23 installed and v24.3 is the update. That's the newest version of Magisk. I'll probably just leave it alone. If anything instead of updating just the app, I'll probably just flash v24.3 if I end up doing it. Thanks again!
[Fire TV Original Android Development] LocoMexican:
I tried to flash Magisk 24.2 and then 24.3 via TWRP. Neither one got past "checking digest" and would not install. I'm sticking with version 23.0, at least for now.
[Fire TV Original Android Development] Bertonumber1:
Ive found the latest magisk to have problems also stick to v20-23.0

There is also the fact johnwu had decided to remove the magisk hide root feature.

There are several Magisk Alpha alternatives such as shamiko if your interested in hiding root from certain apps that call it.

Regards
[Fire TV Original Android Development] LocoMexican:
I've just set up a new sloan with latest update, magisk and a couple of other apps. I can't stand all the bloat. Please give me a hint on where I might find a custom launcher or other apk that will allow me to disable some of the bloatware. I'll be forever indebted. Thanks.
[Fire TV Original Android Development] Bertonumber1:
Yeah I've wrecked a few devices going through the learning stage haha. At least you'll know next time.

Remember, don't use things like paperclips, use a fine piece of copper or a thin needle to just touch the dat0. We don't need to dig for oil just be gentle and all shall be good

Regards
[Fire TV Original Android Development] Michajin:
I actually used aluminum foil. Trick I learned after breaking the chip off one of the 4k's...
[Fire TV Original Android Development] Bertonumber1:
Yeah @Michajin I found that works well esp with mantis. I always use foil for him as you can just jam it in the shield easily and that gives you a spare much needed hand to run script and plug USB into the laptop. How's things mate?

hope you're okay.

I see Rortiz2 and the boys have the Sloane CM 14 in the pipeline. Hopefully get a decent rom here on this arm64 device as opposed to the usual armv7.
[Fire TV Original Android Development] LazorBlind:
Hell before I put in my button I just used a bit of wire I got out of an old pair of earbuds. Little bit of solder on each end and I taped down the ground side
[Fire TV Original Android Development] Seattleweather:
anyway to do this in window instead of Linux?
[Fire TV Original Android Development] DanielF50:
No, not currently & doubtful there ever will/would be.
[Fire TV Original Android Development] Seattleweather:
Thanks. My sloane has never been rooted before. I guess I have to follow #2 Post first.
[Fire TV Original Android Development] Seattleweather:
Looks like can ben done, but have not tried. https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Fire TV Original Android Development] LocoMexican:
Sus-i, I' back. Having Linux issues with my ancient computer. After d/loading zip and unpacking, and opening a terminal in the folder and setting the environment, the computer does not recognize the command sudo ./bootrom-step.sh. So I never get to "waiting for device". When I try this command in another folder - amonet-mustang - the computer has no problem recognizing the same command from that folder. Am I missing something in the setup? Yours or anyone else's comments are appreciated. Thanks.
[Fire TV Original Android Development] Bertonumber1:
Think there's a windows amonet for tank/4k but not Sloane, he's a different breed 👍
[Fire TV Original Android Development] Bertonumber1:
@LocoMexican

In terminal run:

chmod a+x bootrom-step.sh

Then run the sudo ./bootrom-step.sh

You may have to do this with the other scripts too that you may wish to use. Sometimes the unzipping messes with permissions that's all.
[Fire TV Original Android Development] LocoMexican:
Thanks. That solved the problem, and your right, I have to do this with the other commands. Just hope the downloaded zip file doestn't have problems with the rest of its contents. After the fastboot-step.sh command, I am going to try and flash the actual script through temp twrp with keyboard and mouse. Thanks again for your help.
[Fire TV Original Android Development] G S W:
This looks cool, and looks like it was recently posted in 2021 so thats a major plus, but It looks like you need to already to be rooted for this or am i mistaken? I'm confused on exactly what it does and if its worth the risk of "temporarly bricking" my device. Any help is appreciated..
[Fire TV Original Android Development] LocoMexican:
Now that my computer is working, I would like some clarification. I have a working unrooted device with current ota updates. It works fine, but I want to root it. For clarification, my scheme is to first open the device and temporarily brick it with the short dato method. That should leave me with temp. twrp which I will then use to flash stock firmware older than 5.2.7.3. Then, I should be able to use the existing temporary twrp to flash the downloaded zip from post 1. I assume this gives me root access and unlocked twrp and then I will have to decide whether to update useing Rbox's pre-rooted roms or go with magist and use stock roms. Is my thinking correct on this, or am I missing the big picture? Please comment when you have a chance.
[Fire TV Original Android Development] Seattleweather:
#2 post from the link is for the device without root or TWRP. You need to "temporarly bricking" in order to root it.
[Fire TV Original Android Development] Rortiz2:
If you use the brick method you DON'T NEED to flash the unlock zip through TWRP. Both methods (shorting, flashing zip) will give you full-unlock.

I'd recommend you to flash stock update.bin + Magisk after you unlocked the device as rbox prerooted ROMs will disable "unlocked" TWRP.
[Fire TV Original Android Development] G S W:
what is the best method to acquiring a A Linux installation or live-system. I only have a windows 10 pc available for use.
[Fire TV Original Android Development] G S W:
how risky is this? I'm kinda a noob and if I **** up and brick it for good I'll be sad because the sloan box is the best box ever :( also I notice I must do this in a linxu system, how should I go about getting into a linux system while only having a windows 10 PC?
[Fire TV Original Android Development] LocoMexican:
OK, so I you're saying I do not have to actually flash the d/load file in post 1. If my understanding is correct, then I do not have to flash with the older stock rom, but rather I can just go ahead and flash latest stock rom plus magist? Is this correct? Thanks again for your clarification.
[Fire TV Original Android Development] Sus_i:
lol, have pushed the update on sdcard, but was too lazy to install it. I guess I'll skip it then ;)

Idk which launcher is currently the best, but in this thread you probably find the answer.

[APP][FIRETV][NOROOT] Launcher Manager (Change Launcher without Root)

LAUNCHER MANAGER (FOS 6+) BLOCKED BY AMAZON, USE LAUNCHER MANAGER (MINI) STEPS TO ENABLE CUSTOM LAUNCHER: Before installing version 1.1.8 uninstall any previous version. 1. Download Launcher Manager by clicking or by using short link and...

xdaforums.com

If not, ask SweenWolf or Finnzz
[Fire TV Original Android Development] Bertonumber1:
Hello,

On my sloane i installed ATV launcher Pro. then settings apk by Hoffi (com.markus.settings apk) to access firetv settings as sloane is stubborn once you start disabling launchers on latest firmwares due to adb / accessibility permission revocations.

So you have to play around with different launchers and configs.

I then installed the frowned upon 'luckypatcher' which is actually really good for viewing what apks do what and allowing you to disable/enable with ease.

Once i had installed ATV launcher i used luckypatcher to disable com.amazon.tv.launcher followed by com.amazon.firehomestarter a few seconds after.

I then set about diaabling the usual bloat from the /System/priv-app folder such as 'shopping' 'ags app' 'hedwig-news'.

OFC there is adb you can also use to disable the bloat but i use this luckypatcher as it gives a clearer view to what's on your device. You can also block ads and edit the host file etcetera etcetera. If you need any assistance let me know.

Regards
[Fire TV Original Android Development] LocoMexican:
OK guys, thanks for the direction. I'll start the process and report back in a day or three. Thanks again.
[Fire TV Original Android Development] LocoMexican:
OK, where can I find an "apk" for atv launcher pro? I'm more than happy to pay the $2.99 fee, but it won't d/l to my computer as a apk. Otherwise, I have the "settings" apk and the frowned on "Lucky Patcher" apk as well as the "free" version of atv launcher. And, I have successfully gotten rid of several system apps such as news, free time, photos, voice recorder, and several others. All I need to be a happy camper is the pro version of atv launcher. Suggestions are appreciated. Thanks for the help.
[Fire TV Original Android Development] LocoMexican:
Finally got apk for ATV Launcher Pro, but it doesn't seem to want to work. Has anyone had trouble loading up this apk? If so, what is the trick? Thanks for suggestions.
[Fire TV Original Android Development] Sus_i:
Idk, could be that it needs some (missing) play services.

Isn't there a Wolf Launcher version for fireOS 5?
[Fire TV Original Android Development] LocoMexican:
You're most likely right. I found the apk and tried to install it after I de-bloated the device. I probably deleted a service necessary to run the app. Sooooooo, I'm going to unblock updates, let the unti complete the update, and then try again. I can always de-bloat again. Thanks for the idea.
[Fire TV Original Android Development] LocoMexican:
Re-installed latest update and tried again. Works fine. Thanks for the comment.
[Fire TV Original Android Development] fleisch80:
Hi friend .

I was wondering , to install any rom below 5.2.6 what would I need to do for the flash to be

Successful.

I really want a rom like 5.0.1 back with the old interface , and I don't understand why

the flash is not taking .

Did Amazon in fact use an efuse that was triggered buy an update to prevent the older

os and gui from ever being reinstalled ? .

Any guidance is greatly appreciated .

Thanks so much .

Cf.
[Fire TV Original Android Development] LocoMexican:
Not being an expert, I would 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.

8. Block updates.

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.

6. Block updates.

Not sure if any of his will work, but maybe you will have "success". Good luck.
[Fire TV Original Android Development] vrl2:
The confusing part is that 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 within TWRP (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 amonet-sloane-v1.3? 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?

Is there another option that does not require repeating the short?

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] LocoMexican:
Using the short method, make sure you are making good contact with the correct spot on the chip. With the short in place, and everything else connected to the unit and ready to go, power the unit (plug it in) and wait a few seconds. If the unit's power light comes on (lights up) then you do not have a good short. Unplug the unit and readjust the short contact and power up again. Keep doing this trial and error until you can power up the unit and the power light does not come on. Next, run your script on the computer such that it says "waiting for boot rom" and then, plug your usb to usb into your computer (it should already be plugged into your sloan device). Your computer screen should react with "remove short", at which poiint you remove the short. The script should run from there. Your problem may very well be more involved than this, but this is what i would try first. Remeber, when you first power up the unit, the power light should not come on if you have a good short on the correct spot of the chip.

Once you are in TWRP, Install amonet 1.01. After you install amonet 1.01, be sure you FORMAT (not wipe) the data. Then, click on Install, and install the sloane version of your choice. Finally, install Magist v23 if you want adminstrative privleges. Reboot system and you should be good to go. Good luck.

Hope this helps.
[Fire TV Original Android Development] vrl2:
Thank you for your help!

Yes, I am certain that the light is off when the short is in place .Looks like the short is working . 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")

Thanks.
[Fire TV Original Android Development] LocoMexican:
You might try a different usb port on your computer. Make sure you have your computer's environment set up as described. Also, you might want to try using the gpt-fix in v.1.3. If gpt-fix runs, it should put you into TWRP and you can install from there. Good luck.
[Fire TV Original Android Development] LocoMexican:
My device took an update this p.m. Now has OS 5.2.8.8 (676742620). Had to adb reboot recovery and re-install Magist v23. Everything looks good, except now I have to de-bloat again. I guess practice makes perfect.
[Fire TV Original Android Development] LocoMexican:
Also, I was finally able to capture the update url using logcat. After piecing things together, this is what I came up with if anyone wants to try it.

https://d1s31zyz7dcc2d.cloudfront.net/df01587672db6ee5bb8d462eb9e8c027/update-kindle-full_sloane-36.6.7.6_user_676742620.bin
[Fire TV Original Android Development] Toothless_NEO:
Will this work with Fire OS 5.2.4.1 or is there a minimum version this will work for?
[Fire TV Original Android Development] Rortiz2:
Yes, it will work just fine. Make sure to read both the first and the second post.

If you already have rbox's TWRP, you can just flash the ZIP with it.​
[Fire TV Original Android Development] testbankbuddy:
My version is 5.2.8.8, unrooted. can you downgrade unrooted firetv? Or carry on with this guide without a root prior to this tutorial since my version is too high.

Is it possible to downgrade unrooted firetv 2 sloane
[Fire TV Original Android Development] Rortiz2:
Follow the instructions of the second post (you'll need to open up your device).
[Fire TV Original Android Development] mamcho:
Hi again. i have a second unlocked solane. twrp and fastboot working. wont boot past the amazon logo. OS is flashed and all files are there if i check throu twrp. i tried different os versions with and without root.

USB detection only works for a short amount of time. I can see the internal folder omni/sloane and then its gone. Any Ideas?