yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Legolas2:
Hi Bertonumber1

I am trying to be extra-cautious here and to ensure I don't brick-it. :). Is my understanding correct?

The last update to pre-rooted left me w/ two copies of icons in settings menu :)

Download and rename update-kindle-full_sloane-36.6.5.2_user_652614020.bin to update-kindle-full_sloane-36.6.5.2_user_652614020.zip

Transfer above .zip to FTV2 /sdcard/download folder using adbLink

Reboot FTV2, boot into TWRP recovery

Wipe in TWRP

Install .zip file from /sdcard/download folder

Clear cache/Dalvik in TWRP ( After this step should reset/unroot w/ v5.7.2.3_r1)

Reboot

Log-in to Amazon account

Enable adb

Connect via adbLink and open adb Shell

su

manage_recovery (type "yes" to restore stock recovery)

Reboot

Check for updates, and should be able to update to latest version (v5.2.7.7 ?)

Please confirm/correct my the above steps. Wondering if step-10 above can be done prior to Step-3 above.

This could help anyone else who would like to do the same.

Thanks again.
[Fire TV Android Development] Sus_i:
Hi^^

You see, if you do step 5, how would you call su in step 10?

This can't work at all, flashing a stock rom kills root + TWRP ;)

If you do it this way, you have a box with a disabled recovery, unable to update ever again (until you re-root it to get TWRP back). Factory reset will also not work anymore.

Enable the stock recovery should be the first step, try booting in it with 'adb reboot recovery' is the second.
[Fire TV Android Development] Legolas2:
Glad I checked :). So, will update steps to:

Download and rename update-kindle-full_sloane-36.6.5.2_user_652614020.bin to update-kindle-full_sloane-36.6.5.2_user_652614020.zip

Transfer above .zip to FTV2 /sdcard/download folder using adbLink

Connect via adbLink and open adb Shell

su

manage_recovery (type "yes" to restore stock recovery)

reboot recovery

Wipe in TWRP

Install .zip file from /sdcard/download folder

Clear cache/Dalvik in TWRP ( After this step should reset/unroot w/ v5.7.2.3_r1)

Reboot

Log-in to Amazon account

Enable adb

Reboot

Check for updates, and should be able to update to latest version (v5.2.7.7 ?)
[Fire TV Android Development] Sus_i:
Seems fine. (y)

You see, step 3-3 is only a security measure, to make sure that the manage_recovery command worked as expected. Watch on your TV if the stock recovery comes up, if you run 'reboot recovery' in adb shell. If yes, unplug power and reboot to TWRP with the bootmenu. It may work without 3-3, but it can't hurt anything if you do the check.

Good luck^^
[Fire TV Android Development] Bertonumber1:
Seems a lot of folk are unrooting and returning their Sloane to stock these days :sick:

I wonder whats happening if it's just because certain apps don't work with root....

I don't use apps like peacock TV or prime so the root/debloat aspect of things doesn't bother me.

As long as a handful of apps I use work and vlc/MxPlayer Pro work on the Sloane I couldn't really care. @rbox done well prerooting these roms IMO
[Fire TV Android Development] Sus_i:
I guess most people return to stock, because they are going to sell the box...

and some people got problems and didn't realize that those are much harder to fix without twrp. ;)

If someone needs an app that won't play because of root detection, easiest is to uninstall (delete) all the supersu stuff on /system. That wouldn't kill twrp, so you have still su access with TWRP and all apps working fine.
[Fire TV Android Development] Bertonumber1:
Double post
[Fire TV Android Development] Legolas2:
Hi

When I ran the Step 3-3, it was stuck on the recovery screen, and I was concerned that I messed up... a power-cycle, followed by the rest of the steps has me at Stock. In my case, I realized that I don't really use ANY of the features that are possible by using a root device, so the hassle of updating was not worth it.

I am still having one issue.. I am still at v5.7.2.3 (my other unrooted FTV2 is at v5.7.2.6), and when I check for updates it is stuck checking for updates. I also ran the " pm unhide com.amazon.device.software.ota" in adb shell, but still with same behavior. Is there anything else I can try before having to do a "factory reset"?

Thanks in advance.
[Fire TV Android Development] Bertonumber1:
Hey,

Try enabling the apks

pm enable com.amazon.device.software.ota

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

pm enable com.amazon.tv.forcedotaupdater.v2

Reboot

Then goto :

Settings>about>update

Check updates

It should download latest software

goto terminal and type manage_recovery and disable by type yes

If your goal is to erase root and twrp then just reboot and let the update install.

(Further Note) Most Sloane have the current fireos 5.2.7.6...... only some have the 5.2.7.7 update.... Mines is on 5.2.7.4 and I can't get it updated any further.
[Fire TV Android Development] Legolas2:
Thanks Beronumber for the instructions... I get the below Error messages...

shell@sloane:/ $ pm enable com.amazon.device.software.ota

Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=25630, uid=2000, package uid=32080

1|shell@sloane:/ $

1|shell@sloane:/ $ pm enable com.amazon.device.software.ota.override

Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=25650, uid=2000, package uid=32080

1|shell@sloane:/ $ pm enable com.amazon.tv.forcedotaudater.v2

Error: java.lang.IllegalArgumentException: Unknown package: com.amazon.tv.forcedotaudater.v2

1|shell@sloane:/ $

Also, here is the list of disabled packages. The OTA package is disabled and unable to enable it:

shell@sloane:/ $ pm list packages -d

package:com.amazon.amazonvideo.livingroom.firetv

package:com.amazon.device.software.ota
[Fire TV Android Development] Bertonumber1:
Yes this is because you are not #root to disable system apps.

Try typing : pm enable-user --user 0 com.amazon.device.software.ota

Is TWRP still present?
[Fire TV Android Development] Sus_i:
Thats fine (y)

Nope. I guess you didn't wipe data, isn't it?

Do a factory reset in the settings. Just at the reboot the box looks for updates.

? ;)
[Fire TV Android Development] Bertonumber1:
@Sus_i do you have link to 5.2.7.6 (or 5.2.7.7) full Sloane.bin? I know you have it stashed somewhere :p

I've been trying to grab it from ota but it's not in /cache or anywhere

enabled updates, let it download & cannot locate it, even tried packet capture to try and get direct link to no avail. WTF :unsure:
[Fire TV Android Development] Sus_i:
Here is 5.2.7.4 and 5.2.7.6 for sloane:

Fire OS 5.2.7.4 (656638420)
https://d1s31zyz7dcc2d.cloudfront.net/7758ad70f668023cc93ddee2655c6226/update-kindle-full_sloane-36.6.5.6_user_656638420.bin
md5Sum=b1c0e32eb4aa24aab1129fc80f4ae9b1

Fire OS 5.2.7.6 (659654620)
https://d1s31zyz7dcc2d.cloudfront.net/c5b513d2116f5ad2942426ab79bb437b/update-kindle-full_sloane-36.6.5.9_user_659654620.bin
md5Sum=c6d932094c29f23e228148ebe53244b9

I didn't received a 5.2.7.7 until now and I don't want it at all (could be that they are trying to patch the BROM exploit via eFuse on sloane too, lets see what happens).
[Fire TV Android Development] Bertonumber1:
:confused: don't like the sound of that but it's to be expected isn't it, theyll probably have peeps watching this thread, it's sad but true mate.

Anyway cheers again for the link :cool:
[Fire TV Android Development] Sus_i:
Nothing to worry about, just a bit precaution ;)

Idk if it is even possible to disable BROM/DLmode without updating preloader / LK images...

Seems too that the PL hasn't got an update since 5.2.7.0.

A patch for sloane should be rather unlikely, I guess.
[Fire TV Android Development] Bertonumber1:
Yeah I think it is such an old device now they're gonna be concentrating more on the newer junk they've released.

Do you think it would be possible to upgrade the Sloane to m/mallow or nougat with OTA? Would it be possible for them with the board it currently has.

It's got to be noted their pushing all the best OS and decent launchers to all the wrong devices... Eg The Lite Edition.... and let's not even talk about how poor mantis has been left out too.
[Fire TV Android Development] bruinsrule:
Now that you have the update bins captured, does this mean we can get a prerooted rom soon?
[Fire TV Android Development] 0815hoffi:
For what.

What is the advantage of prerooted rom?

I have never understood.

STOCK + MAGISK is the same.... i think
[Fire TV Android Development] Legolas2:
Yes, I don't have su permissions anymore. The above command doesn't work, and didn't see it in the help. Modified it to below, and get the same message.

1|shell@sloane:/ $ pm enable --user 0 com.amazon.device.software.ota

Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=8903, uid=2000, package uid=32080

I guess a factory-reset is the way forward :)
[Fire TV Android Development] Bertonumber1:
Ah what the hell, why not eh?
[Fire TV Android Development] 0815hoffi:
Amazon patched this also on Fire TV Stick Tank with 5.2.7.6 :-(
[Fire TV Android Development] Sus_i:
Idk, maybe annoy the developer of the prerooted-roms a bit ;)

For mantis and tank it is the same, except the added addon.d support.

The prerooted-rom's for bueller, montoya and sloane are working with a 'locked bootloader' (as Magisk isn't avialable on locked devices).

You get a pure stock rom with root access, TWRP and an easy way to backup/restore almost all system modifications (like gapps or any other system installs) via addon.d support out of the box.

Besides that, the prerooted-rom took always care of the eFuse thing, preventing a blown eFuse on the rare unlocked first-gen fireTV boxes called bueller (they are trying to trigger the qualcomm eFuse with every OTA update since 2015, in order to kill all unlocked bueller boxes).
[Fire TV Android Development] Bertonumber1:
I'm aware the Samsung SOC in the Sloane has the possibility of being eFused, I didn't know they were continually trying to do this with Bueller as well.

Yesterday I flashed the 5.2.7.6 onto Sloane from twrp and Successfuly put the box back to normal OS , I cannot get back into twrp so I am going to have to do the short method again. Just wanted to see what was happening in respect of the newer OS.

You're absolutely bang on , with regards to 5.2.7.7 update, I think anyone who receives this OTA and let's it update/install will end up with an unmodifiable box.
[Fire TV Android Development] rbox:
I updated the OP with 5.2.7.6_r1. I can't for the life of me get 5.2.7.7 to download.
[Fire TV Android Development] tw39515:
thanks for keeping sloane alive @rbox
[Fire TV Android Development] bruinsrule:
Ditto that. Rbox rocks!!
[Fire TV Android Development] Bertonumber1:
@rbox

I don't think many ppl have 5.2.7.7 (I couldn't find it anywhere) but if you have the time, perhaps enable updates from 5.2.7.6 you could grab #adb logcat and pull it from cloudfront.

Ps, Excellent work and thanks again for your continued attention on the Sloane (y)Respect
[Fire TV Android Development] Legolas2:
Thanks for all your help. I finally did do the "factory reset", and it went through multiple cycles of FW update and I am now at 5.2.7.6.
[Fire TV Android Development] jaydee 77:
@rbox

Thanks for the newest update of your prerooted ROMs for FireTV2 (sloane). (y)

My FireTV2 (Sloane) is on prerooted ROM 5.2.7.3. What is new with ROM version 5.2.7.6? There are any important changes in the last updates or are they just trying to annoy rooted users.
[Fire TV Android Development] cmmike:
I was on 5.2.7.3 and couldn't stream from the ESPN app at all. Said my FireTV wasn't up to date. The latest update (5.2.7.6) solved the streaming problem I was having with ESPN+ and a few other TV network apps.
[Fire TV Android Development] Bertonumber1:
how are the custom launcher working on 5.2.7.6 ? do you have it working ?
[Fire TV Android Development] 0815hoffi:
He has a rooted FireTV ;-)

With root you can still disable the Launcher
[Fire TV Android Development] cmmike:
I don't use a custom launcher so I can't say.
[Fire TV Android Development] Bertonumber1:
The reason i ask this hoffi was i found disabling launcher in this version causes problems as the rootsettings tend not to work on this device somehow mate. I ended up going back to 5.2.7.3 because of that
[Fire TV Android Development] Seattleweather:
Is it possible to root 5.2.7.7?
[Fire TV Android Development] Bertonumber1:
Yeah it sure is.. I had 5.2.7.6 then flashed the 5.2.7.7 update and rooted with magisk.
[Fire TV Android Development] Seattleweather:
Thanks. I will follow up this link then. https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/.
[Fire TV Android Development] First_Degree:
Been a while since I've updated the ol FTV 2.

Seeing this other thread, and have a couple questions:

-Is rbox no longer doing pre-rooted images for sloane (looks like no activity since late Dec on XDA)?

-Is there something with the 5.2.7.7 update which impacted the ability to "pre-root"?

Just trying to catch up and appreciate all the effort from rbox and others in this thread over the years! Thank u!!
[Fire TV Android Development] jaydee 77:
rbox is still active from time to time and is giving us prerooted ROMs for our old FireTV Box 2 (sloane).

rbox wasn't able to catch the 5.2.7.7 update. See this post from rbox.

https://xdaforums.com/t/firetv-2-sloane-prerooted-stock-images-5-2-7-6_r1.3309783/post-84176157
[Fire TV Android Development] Sus_i:
I've got the stock 5.2.7.7 for sloane about a week ago...

https://d1s31zyz7dcc2d.cloudfront.net/b9f7c8f9a8a4ba1f34da8ce7a8077474/update-kindle-full_sloane-36.6.6.2_user_662663720.bin
[Fire TV Android Development] jaydee 77:
Hopefully @rbox is reading this and got some motivation and time to build a prerooted a ROM for us.
[Fire TV Android Development] Deelaroc:
I hope so. I’m getting frustrated with my FTV2 wanting to constantly update to 5.2.7.7 and cannot watch YouTube videos or that. I get maybe 10 minutes and then no “network connection” when I know it wants to update.
[Fire TV Android Development] ldeveraux:
What? Disable check for update! I thought that was standard in rbox's ROMs anyway.
[Fire TV Android Development] mwahahaa:
How did you root with magisk? I thought the bootloader had to be unlocked to use magisk or you would brick the device.
[Fire TV Android Development] Sus_i:
You're right...

Here is the unlock:

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Fire TV Android Development] Yeahmään:
hi is there a working link? would be great

update: found https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.3.0_user_630508620.bin
[Fire TV Android Development] Bertonumber1:
Yes head to original android development section of amazon firetv and check out the "unlock root twrp unbrick" Sloane thread for the unlock, I'm lazy and can't he assed looking up the link for you. I'm sure you'll find it 😎
[Fire TV Android Development] HbbS:
I have updated to the latest rbox firmware. But I'm getting an annoying issue.

When I try to launch an app using the "Show all apps' I'm only getting an empty 'your apps & channels" and a loading icon.

Does anyone here knows how to fix this?:
[Fire TV Android Development] Toothless_NEO:
Hello I just wanted to let you know that a lot of the mediafire links are down.
[Fire TV Android Development] stillwater77:
Warning: I flashed 5.2.7.7 stock from here over prerooted 5.2.7.6_r1 in TWRP which bricked my device. Had to go through unbrick procedure involving opening the device and shorting some pins.
[Fire TV Android Development] ottoguy:
I'm on the pre-rooted 5.2.7.6 using TWRP. I still get pop-ups saying it will update soon and you have 60 seconds to press ignore. If I don't ignore it reboots into a boot loop until I unplug it.

I've tried disabling com.amazon.device.software.ota from an su adb shell and it gives a java error "

Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=10114, uid=2000, package uid=32013"

I've tried uninstalling com.amazon.device.software.ota.override and com.amazon.device.software.ota; it gives an error "Failure [DELETE_FAILED_INTERNAL_ERROR]"

Is there something I'm missing? Is there a way to block the update popups and subsequenet reboot?
[Fire TV Android Development] Deelaroc:
Yes this is the exact same problem I’ve been having. The only way it fixes this is updating to a higher firmware I found, as I’ve had this problem before but was able to update it to the highest available firmware that was also rooted. And I’ve always installed rooted roms so the update feature should be already disabled.
[Fire TV Android Development] Bertonumber1:
Hey there,

Are you rooted or unlocked and if so... What method are you using the old method or new unlock method on your Sloane?

Try using :

pm disable-user --user 0 <nameofamazonpackage>

OR

pm disable--user --user 1 <nameofamazonpackage>

I'm using 5.2.7.6 also and faced the problem you have.. I solved it with changing the commands around a little in remote adb shell.

Should be okay 5.2.7.6 is still a relatively new firmware.

Regards
[Fire TV Android Development] Deelaroc:
Actually now I get this as of today 😂 All I’m trying to do is watch Prime as I have the membership. And yes it’s a rooted AFTV 2.
[Fire TV Android Development] Bertonumber1:
This update error maybe the nag when it's not wanting to work with root but try this first :

Amazon Prime Update apk

https://d1s31zyz7dcc2d.cloudfront.net/7d3ae0e67799c5203e4082b98b6a2b83/Firebat-livingRoom-release-signed_26071110.apk

If you have Magisk installed, Goto settings>magisk hide and select prime video before opening the prime app for the first time.

If you've already opened it then just clear the apps data and reboot.

As far as I know, amazon prime video will not work on a rooted device. I do not use prime but one of the other guys who know about it will be happy to advise you.

Due to these apps performing a root/bootloader check they won't function properly (some not at all)

Peacock TV and Netflix can be troublesome with root also.

The reason I asked what version of root, or if your unlocked is because magisk hide ( magisk manager apk) can sometimes get the apps to work (depending on firmware)

If you really want to use these apps properly you're best Installing them on a non-modified device.

Regards
[Fire TV Android Development] Deelaroc:
Actually now I get this as of today 😂 All I’m trying to do is watch Prime as I have the membership. View attachment 5378749

I don’t have magisk, I’ve had this rooted pre 5.05 also, so it’s rooted the old way and I’ve been updating the rbox roms ever since. Prime did work before, the only workaround I have is to start a prime video with another device and it will show up on most recent on the box. Then it will play.
[Fire TV Android Development] sanjonny:
I have been on RBOX 's pre rooted 5.2.6.6 since he released it a long time ago....and also started getting this same warning and boot, though I could just hit wait and the fire tv still works okay, but it will go thru the same if left unattended for awhile. I know that rbox blocked updates, but somehow it seems this one got thru to something to at least cause the error. It was also giving me a corrupted, but nothing is corrupted and it has been going on since the most recent update stuff got sent a month or so ago. I have recent tried to disable using the regular commands just the ota version of the update with su shell and the command seemed to work. Will see if it fixed the problem or not. Kinda surprised after a few years that something hidden in amazon seems to have leaked thru. Will update once i find out if that was all that was needed. The good news is that rbox rom didnt download the update or if it did, it didnt install it, but there have been many updates and nothing snuck thru in the past. And no I didnt factory reset, i know that can cause this to be renenabled.
[Fire TV Android Development] mwahahaa:
Is this device at end-of-life now? I haven't heard of any version updates here for a while. Mine continues to serve me well, albeit with the occasional glitch or performance issue.
[Fire TV Android Development] Sus_i:
If you unlock the box..:

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

you can just start flashing stock OTA files instead of waiting for an updated prerooted one...

5.2.8.0 is the latest stock rom.
[Fire TV Android Development] smumar143:
Can I root 5.2.8.0
[Fire TV Android Development] Sus_i:
Yes
[Fire TV Android Development] smumar143:
Thanks
[Fire TV Android Development] Sus_i:
If it's really the second fireTV box called sloane (box with the sdcard slot), then this works for all firmware versions:

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Fire TV Android Development] Han-Droid:
Am I understanding it right that 5.2.8.0 is not available (pre-rooted roms by rbox) unless your FTV2 is stock and unrooted? ...and to GET 5.2.8.0. you have to follow the procedure described in the unbrick-Threads??

Request: could someone else than RBOX be so nice and make a rooted 5.2.8.0 for the FTV2, please?
[Fire TV Android Development] Bertonumber1:
**provided you are already unlocked)

Its better to just grab a 5.2.8.0 update bin and rename it to .zip

Flash it then flash Magisk after it before rebooting.

Im using 5.2.7.4 as i dont like the new interface, i only update webview and appstore apks.

But i did have 5.2.8.0 on my sloane before resorting back.

**Edited **

Regards
[Fire TV Android Development] Sus_i:
No, the bootloader must be unlocked in order to use the stock rom together with systemless root (magisk).

You see, if your sloane box is rbox-prerooted (but bootloader locked), you need probably only a flash of the amonet-sloane zip from the unlock/unbrick thread (for unlocking), reboot into TWRP for a format data and a stock rom flash. In case you need the fireOS rooted, flash the latest magisk.zip too. Follow the unlock thread for details:

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

Since your box is supersu rooted, you can also use adb for unlocking if you like, take a look here:

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

P.S. This is the method I would prefer...
[Fire TV Android Development] Bertonumber1:
I thought he were already unlocked 🙄
[Fire TV Android Development] Han-Droid:
well I get a "root@fireTV:/ # " but "

To double check, you should now run the command: cat /proc/cmdline

If your bootloader is fully unlocked, you will see androidboot.unlocked_kernel=true among the printed text."

shows no such text...dunno then...

[Source: https://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked/
[Fire TV Android Development] Sus_i:
All sloane fireTVs (4k box with sdcard slot) coming from rbox prerooted are bootloader locked/supersu rooted and the twrp recovery runs from a ramdisk on system.

The new solution is bootloader unlocked/magisk rooted with a new TWRP flashed to the recovery partition (therefore we can flash stock roms and magisk without the need of updated prerooted roms. Thats probably the reason why rbox stopped developing his roms for sloane).

Give the third posting from the unlock thread a try... ;)
[Fire TV Android Development] Han-Droid:
I see... thanks for clarifying this! Well, since I read "temporarily bricking the device", I prefer to stay at 5.2.7.6 unless a newer version is absolutely required. This all does NOT read like a "I'm gonna quickly flash the new rom to my ftv" ;-)