yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] deanr1977:
Please read what rbox said here -

February 13, 2016 - 5.0.5_r3 (md5sum: 92d08a12d240cf9bf6d25005a65bd82d)

Starting with this update, stock recovery will be disabled to prevent stock updates from being flashed. Please refer to the instructions above for managing stock recovery.

This includes 2ndinit version dee776 and TWRP version 3.0.0-3. Because this comes with a newer 2ndinit version, "do not flash an older recovery package". "Doing so will disable su."
[Fire TV Android Development] androidfux:
I also have this problem. But my two keyboards had never worked. The keyboards are a wired and a wireless one.

I reflashed the recovery using:

sh /sdcard/firetv2_recovery_v4.zip

Unfortunately that didn't help in my case, no reaction on right key press.

But: If I touch the file "/cache/bootmenu_recovery" (to force boot into recovery), then connect via ADB and execute "mouse" the keyboard presses are working, so I can use the recovery using mouse emulation?! Strange.

Any ideas? (Yes, USB debugging is off).

EDIT: Using v5.0.5-r1 and recovery v4 currently.
[Fire TV Android Development] rbox:
So you can follow what [MENTION=4842812]androidfux[/MENTION] said to force it to boot in to recovery and use the mouse emulator.

Unfortunately, there is nothing I can do about this. It has never worked on FireTV, even on FireTV 1. I think it has something to do with something Amazon has done to Android.

I'm not quite sure why people are reporting keyboard problems. I did notice an intermittent problem at one point when I was testing the unbricking image, but I haven't had any problems with any of the 5.0.5 releases. Unfortunately if you try to flash v4 on 5.0.5_r3 it will break su. I will look in to what is different with 5.0.5_r1 and v4.
[Fire TV Android Development] rbox:
I just took a look at 5.0.5_r1 and v4. They both contain identical copies of 2ndinit and the recovery ramdisk. There is no reason one would work better than the other. The only suggestion I could give would be to flash 5.0.5_r3 and see if the problem goes away. Otherwise I could say try to physically unplug the power and plug it back in and see if that makes the keyboard work. But flashing v4 ontop of 5.0.5_r1 is definitely not going to change anything.
[Fire TV Android Development] wdcspurs:
Anyone have issues with getting Netflix to stream in 4k when using the most current pre rooted ROM in this post? I got a 4k tv last week and am able to stream Netflix fine from my Xbox and via the smart tv app, but it just streams 1920×1080p on the firetv2 box. I can get youtube and different Amazon series to stream in 4k. So that rules out the box and cable and tv port. I do have another Fire tv 2 in another room on a 1080 P tv that I'm going to swap out tonight to see if it yields the same result. The picture that streams resembles 4k ( maybe the upscaling) but there are slight issues with the motion and trailing that doesn't exist on the smart tv app or the xbox. So its not the tv either. Just curious if anyone has encountered this? Thanks in advance.
[Fire TV Android Development] ryknow27:
Hey rbox, is there anyway you could tell what supersu version you used in your 5.2.1.1 prerooted rom? I updated it the other day because I hide the binary with Hide My Root so DirecTV Now will work. Well, when I went to unhide it, it would not unhide so I updated to the current version of supersu, but then I could not get my DirecTV Now to work again. I ended up starting all over by flashing the prerooted rom again and all is good now, but just in case I need to unhide the binary again, it would be nice to just be able to flash the supersu without having to start over again.
[Fire TV Android Development] nujackk:
He's using really old version 1.49
[Fire TV Android Development] ryknow27:
Thanks for the reply but I didn't think about looking in the manage applications in the settings. It shows the version to be 2.46.
[Fire TV Android Development] nujackk:
Yeah I'm sorry was half sleep when I replied I meant 2.49 , but 2.46 is actually what I had. I've since updated it so had to go by sleepy memory :)
[Fire TV Android Development] droidvoider:
I can't download from mediafire anymore.. I have downloaded a lot of rbox stuff in the past. Now it seems to start then it says "Not Downloading? try again" You click that and an add pops up but nothing downloads. Going to try from a Windows machine maybe it's some broken ad system.

edit:

I tried with Windows 10, Android 6.01, Android 4.42.. Then I setup my VPN which wasn't installed because this is a clean setup ubuntu, and preseto it is downloading.. (what's the heck?)
[Fire TV Android Development] XDA_h3n:
I copied this over from my device's cache partition; I couldn't seem to sniff the SSL url as it was obfuscated.

[MENTION=3991724]rbox[/MENTION] Whenever you feel like updating this, here is the partial update image ;)

Software Version: Fire OS 5.2.4.1 (Build 573210520)

Changelog

New and Enhanced Features

Fire TV now features a data monitoring tool you can use to get dynamic information about the amount of Internet data your device is using for apps and streaming services. You can choose your preferred video quality for Amazon Video streaming, set data alerts, and view monthly data usage for your apps. To learn more, go to Data Monitoring on Fire TV.

A PIN Protect Prime Photos App option has been added to Fire TV parental controls preferences. With this setting turned ON, you're prompted to enter your PIN before you can open the Prime Photos app for Fire TV. You can use this option if you only want to block access to the Prime Photos app, and your photos/personal videos from Amazon Drive. To learn more, go to Set Up Fire TV Parental Controls.

The new "Recommended by Your Apps" row on the Home screen features content recommendations (e.g. for movies, TV shows, apps, games, music, audiobooks, and news) from supported apps installed on your Fire TV. Select an item from the row to see which app made the recommendation, or press the Menu button on your remote to view available options. The "Recommended by Your Apps" row won't show on your Home screen if you have parental controls enabled for your Fire TV.

update-sloane_full_sloane-565189620-to-573210520.bin

File: update-sloane_full_sloane-565189620-to-573210520.bin
CRC-32: 3fd61a14
MD4: d8f127abd57aac55178ac2b9edb22f0a
MD5: c2d49bdeac55a3b3bb84bf8873f08344
SHA-1: e3e6cb04401b124df7d0bac2b75327cf9c186237
[Fire TV Android Development] chris-89:
Thanks [MENTION=4266035]XDA_h3n[/MENTION] !!! Amazing work:good:

So i hope the next pre-rooted Rom update isn't so far away :victory:
[Fire TV Android Development] XDA_h3n:
No problem.

Guys I just wanted to let you know that for the Fire Tv, there is a issue with the refresh rate not switching; it seems to be kernel bug. Hopefully, our version is not affected by this; but I have not tested this firmware at all.

More info can be found here.

Thanks to [MENTION=5957312]AFTVnews.com[/MENTION] I have also got the Amazon link instead of it being mirrored on my Google Drive.

Here is the full firmware's deobfuscated url:

https://amzdigital-a.akamaihd.net/o...indle-full_sloane-36.5.7.3_user_573210520.bin

File: update-kindle-full_sloane-36.5.7.3_user_573210520.bin
CRC-32: 5fedbf23
MD4: acc4a8242381ecc59aac5c070f481b14
MD5: a855c35e93b83646d98e4dc328ca870d
SHA-1: b3157028a3c3cf64b0f97ad2f9933ce6392fc2f0

Update

If anybody wants to try out this firmware, firstly make a TWRP backup (so that you can restore to incase you experience issues with 24p playback). I'd highly suggest you wait for rbox to update it as it is less risky; you may loose root if you haven't allowed SuperSU to have atleast allowed su before! Ensure that your current rooted applications have been allowed. SuperSU will work but you will need an additional Xposed module for it to open.

If you are impatient and like to observe the changes with this firmware then go ahead, I take no responsibility as this is all risky; though I am sure the prerooted image will come out soon...

Make sure you have used Adb shell with the su command atleast once! This to tell SuperSU to allow permission of adb shell under root permissions after we've updated the firmware.

Before you start, install Xposed Framework and the HoloThemer 3.0 (version 3.0, no other version; it can bootloop the box! Do NOT update this module either!) module, also enable the module.

Download any optional flashable zips for you (Opengapps)

Download the SuperSU flashable zip

Download the full firmware (update-kindle-full_sloane-36.5.7.3_user_573210520.bin) (not the partial one!) and verify the file integrity by seeing if your file has a matching md5 to the one I have published then change the file extension from .bin to .zip

Download the Fire TV 2 recovery script https://xdaforums.com/fire-tv/development/firetv-2-recovery-t3309780

Download Xposed Framework flashable zip (if you have lost it or something)

Place all of these zips on the sdcard of the device

Reboot into TWRP

Flash the firmware image

Do not wipe cache or system, unless you want to deal with a headache...

Flash the SuperSU root package

Flash Xposed framework

Flash Gapps (if needed)

reboot

Once rebooted run

adb shell
su
sh /sdcard/firetv2_recovery_v6.zip

Run any debloating scripts if necessary

(SuperSU may not show it's interface, an xposed module is needed as Amazon is intentionally blocking it through a corrupted holo them)

To fix SuperSU not opening, install the HoloThemer module (version 3.0 ONLY; and DO NOT UPDATE THIS MODULE! Versions above 3.0 bootloop the device for some reason)

Reboot

Through HoloThemer, select the SuperSU app and select the theme to be Material Light or Material Dark

Profit!
[Fire TV Android Development] D-an-W:
Update went well, on now to the Stick1 and AFTV1.

Many thanks rbox
[Fire TV Android Development] fcisco13:
Thank you very much for your hard work.
[Fire TV Android Development] wilde68:
Just updated my FTV2. It was very easy to carry out, just had to wait a bit for the FTV2 to complete the update.

Now have Alexa.

Thank you RBox
[Fire TV Android Development] vladm7:
Thank you!
[Fire TV Android Development] bula1ca:
I can not download any of the files. Had links been removed? Firetv 1 and FireStick links are working.
[Fire TV Android Development] spursatwhl:
Updated perfect thank you rbox
[Fire TV Android Development] XDA_h3n:
Another version seems to have popped up on my fire tv.

Fire OS 5.2.4.2 (574263120)

md5: 8d51a0b2d3fb4a109a6e4b3629fc72cf

(Full system image)

File Integrity

File: update-kindle-full_sloane-36.5.7.4_user_574263120.bin
CRC-32: c848c06e
MD4: 154d3606989a0fb0b7db9ae2518461c1
MD5: 8d51a0b2d3fb4a109a6e4b3629fc72cf
SHA-1: 123aadaf4debb74da980ffb223b990174667dfe6

Changelog:

New and Enhanced Features
This software update includes general improvements and bug fixes.

https://amzdigital-a.akamaihd.net/o...indle-full_sloane-36.5.7.4_user_574263120.bin

[MENTION=3991724]rbox[/MENTION] Whenever you are ready ;)

https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=201497590

Also new updates with the same software version but different build version with the same changelog. The build version is 573210720 for all other devices but the Fire TV 2.

I expect these updates to devices to fix the 24p problems we have been suffering ;)
[Fire TV Android Development] rbox:
I updated the OP with 5.2.4.2_r1.
[Fire TV Android Development] hocus86:
Can 5.0.4_r2 be re-upped or does anyone know of a legit mirror? I would like to remove root and I have TWRP. Thank you.
[Fire TV Android Development] cowfodder:
Anyone else having issues with HBO Now on 5.2.4.2? After updating I can't play anything. I just get an unable to play this video right now message.
[Fire TV Android Development] ryknow27:
I'm on 5.2.1.1 and it has not been working for me for a while now.

I think what may be needed is an older version of the HBO apk.
[Fire TV Android Development] MDon3:
HBONOW no video

I don't think it's the update, as I jumped from 5.2.2 and had the same problem (message). Even with data and cache wipe and uninstall same problem exists.:(
[Fire TV Android Development] Techstro:
My version is 574263120, I am not rooted. Is it still possible to flash pre-root? My main problem is I need a Fire OS version of the app-store. Can I unzip a rom to extract it?
[Fire TV Android Development] tekno4ever:
hey [MENTION=3991724]rbox[/MENTION] might you be able to provide a download link to a non rooted TWRP flashable 5.2.4.2 ZIP aka stock?
[Fire TV Android Development] rbox:
All you need to do is delete the su directory from the zip.
[Fire TV Android Development] ducksoup18:
Any updates on this HBO Now deal? Im getting the same thing.
[Fire TV Android Development] rbox:
Please see https://xdaforums.com/fire-tv/help/...re-error-cdn-3-t3640707#post_message_73143851
[Fire TV Android Development] ducksoup18:
Thanks [MENTION=3991724]rbox[/MENTION]. That looks to be Hulu though. Has someone identified an actual verison of hbo now that does in fact work?
[Fire TV Android Development] rbox:
It helps if you actually read what was linked...
[Fire TV Android Development] ducksoup18:
I did read the entire post. They mention Hulu and HBO Go, not HBO Now which is a different app that im unable to use at the moment. Playback just doesnt work. I've tried uninstalling and rebooting, may remove root completely and go factory as i dont need root much anymore.

---------- Post added at 02:52 AM ---------- Previous post was at 02:37 AM ----------

Followed this fine users direction and installed older version from links here on XDA.
[Fire TV Android Development] tekno4ever:
So I downloaded [MENTION=3991724]rbox[/MENTION] 5.2.4.2 deleted the SU directory inside the zip as instructed, then wiped everything possible 3x upon which I cleanly reinstalled 5.2.4.2 and Hulu still does not work on my non rooted AFTV 2 Box. Direct TV Now works perfectly without installing HideMyRoot so maybe this is truly just a Hulu issue on AFTV 2 Boxes. [MENTION=5957312]AFTVnews.com[/MENTION]
[Fire TV Android Development] tekno4ever:
With [MENTION=3991724]rbox[/MENTION] permission, I am delighted to share with you that after testing his Hulu and most likely HBO Go "fix" I can confirm that I did not brick my device and that my Hulu 4.0.xxx app is working! I dont have HBO Go so I was unable to test that. Since I have Direct TV Now, I can confirm that it also works but only after reinstalling HideMyRoot. [MENTION=3991724]rbox[/MENTION] conveyed that he will be uploading a new version of his 5.2.4.2 Rooted Rom later this evening.
[Fire TV Android Development] fcisco13:
[MENTION=3991724]rbox[/MENTION] really appreciate the time you take to do this bro, thank you very much.
[Fire TV Android Development] rbox:
I updated the OP with 5.2.4.2_r2 which contains updated firmware to fix HBO and Hulu.
[Fire TV Android Development] tekno4ever:
Here's 10 George Washingtons to do with as you please 9YY064323V096594D
[Fire TV Android Development] IBNobody:
(Originally posted in the adblink thread, but I stumped jocala...)

I just redid my AFTV2 with a complete wipe and restore using RBox's unbricking tools. Am running the latest AFTV2 image with root and am using adblink 3.4.

adb is giving me issues when trying to install apks. I would get permission denied errors with adb install. Troubleshooting led me to the fact that /data/local/tmp was protected. I verified that I could create files in /data/local/tmp (echo foo>bar) as root, but would get permission errors as a normal user.

I have no issues on my AFTV Stick 2 that DOES NOT have root. I can create anything in /data/local/tmp just fine.

As root, I attempted to chmod 777 /data, /data/local, and /data/local/tmp with no luck. I also tried making my permissions match my AFTV Stick 2. /data is 775, /data/local is 751, /data/local/tmp is 771.

Is there something else going on with permissions?
[Fire TV Android Development] zeroepoch:
The only other thing involved in this kind of situation is SELinux. Run "ls -lz" to check the context of the directories. Usually those get reset at boot though to maintain security. You can change them with chcon.
[Fire TV Android Development] BIOYAM:
[MENTION=3991724]rbox[/MENTION]

Thank you very much for this pre-rooted v5.2.4.2_r2 image.......... works great!

One question, is it still necessary/advisable to make the change to block Amazon updates in the build.prop (ro.build.version.number=987654321), or is that no longer needed? ...... and if it is still necessary, is this all that needs to be done to protect us from involuntary updates?

Thanks in advance for your help.
[Fire TV Android Development] wohltat:
Hello,

today a "a new software update is available" notification took over a large part of my buttom right screen and I cannot interact with it. Any ideas how to fix this?

*edit*

After 30 minutes I figured out that the update messsage is actually from my Sony TV. LOL.
[Fire TV Android Development] IBNobody:
This got me on the right track!

I noticed that my AFTV Stick 2 and my AFTV2 had different contexts for /data/local/tmp.

root@sloane:/data/local # ls -Z
ls -Z
drwxrwx--x shell shell u:object_r:system_data_file:s0 tmp

The issue was that /data/local/tmp was a system_data_file type on the AFTV2 and a shell_data_file type on the AFTV Stick 2.

root@sloane:/data/local # chcon u:object_r:shell_data_file:s0 tmp
chcon u:object_r:shell_data_file:s0 tmp

root@sloane:/data/local # ls -Z
ls -Z
drwxrwx--x shell shell u:object_r:shell_data_file:s0 tmp

After this, I was able to get adb install to work.

A few questions from a SELinux noob.

1. chcon changes are not permanent. If I reboot, this should all get wiped out. How can I make chcon permanent? (Android has limited SELinux console commands.)

2. Why did this happen to begin with?
[Fire TV Android Development] zeroepoch:
You would need to change the start up scripts or the policy file. Both are pretty non trivial to change. It's very strange that it changes to something that doesn't work after rebooting. Maybe [MENTION=3991724]rbox[/MENTION] knows why. For root to work it has to change this policy but I don't think that path is related to those changes.

Oh you can also disable SELinux. Normally it's done though setenforce or echoing to a certain /sys path but forgot which one.
[Fire TV Android Development] IBNobody:
Yeah, I suspected that I would have to edit the startup scripts to add the chcon command. It appears that it is normal for chcon to not create persistent changes.

What I will likely do is just write a batch file that sends the ADB chcon command and run it when I need to sideload from ADBLink. That way, wiping my AFTV2 in the future won't make me have to reapply any startup commands.

I would still like to know how /data/local/tmp got the wrong SELinux security context - that is definitely a question for rbox. Mainly, I care about this because I worry that there may be other protected folders that would cause unexpected failures.
[Fire TV Android Development] RazorX2015:
hey guys i need help please, i installed this (5.2.4.2_r2) on my fire tv 2 and everything installed and was working correctly however the TWRP screen was messed up like it was two overlapping images so i thought to fix it i had to install the bueller_recovery_v2.zip to my fire tv so i did and now my fire tv is suck on the white amazon logo :( can someone please help me fix this thank you.
[Fire TV Android Development] fcisco13:
You installed the wrong recovery, you know this right?? FTV2 is Sloane, i would try n install the correct one first, but you might want to wait for more knowledgeable input.
[Fire TV Android Development] RazorX2015:
i had the correct one on first but it was not showing up correctly as stated in my first comment
[Fire TV Android Development] rbox:
You could try doing an advanced wipe of data from TWRP. That'll completely wipe /data and then next boot will create everything properly in it.
[Fire TV Android Development] cardboardbox:
Does this mean that all adb install commands will fail without doing this fix? I was able to adb install kodi, but when I tried to install paragon root mounter it didnt show up in the manage apps menu even though the install seemed to be successful.
[Fire TV Android Development] IBNobody:
I can give it a shot and report back to you.

Hmm... That was not the behavior I observed. In order for adb install to work, it first must copy over the APK file to a temp folder. My permission issue prevented the copy.
[Fire TV Android Development] theistus:
Thanks man! worked like a charm! Really appreciate the work you put into this. I'm curious to know what the issue was?
[Fire TV Android Development] BIOYAM:
I would like to know this too..........:D
[Fire TV Android Development] PHATE*73:
About Messed up TWRP and Amazon Stuck Logo Problem

I have the TWRP not displaying properly on my TV upstairs as it is only a 720p SONY Bravia...Once it gets past the TWRP screen, the Amazon Startup Logo and Everything from there Loads fine. *When i hook my FIRE TV 2 up on my downstairs LG 1080p the TWRP "messed up overlapping image problem" DOES NOT OCCUR !! > So i just wondered if you had a 1080p TV hooked up to your FIRE TV BOX...or maybe had it on the wrong RESOLUTION SETTING...?

The other thing i noticed was that you had a "Stuck on Amazon Logo at Power ON" problem (i see you had flashed a BUELLER instead of a SLOANE pre rooted image) but just incase it happens again or to anyone else TRY PUSHING your HDMI CABLE all the way in (TV side also)...my kid moved mine downstairs and my FIRE TV BOX had done this a while back and THAT CURED IT (try a different HDMI CABLE if it persists)

- Hope that helps in some way - ;)
[Fire TV Android Development] pfhastie:
I would be very grateful if anyone is able to offer me a spot of advice.

For the last few months I have been using "sloane-5.0.5-rooted_r4" on my Fire TV 2. Everything was working as it should and I would have been happy to leave it forever, however, having seen Alexa in action, I really wanted to update to the latest version so I downloaded "sloane-5.2.4.2-rooted_r2" and put it in the SD Card on my Fire TV 2.

I backed up my system first using TWRP, then flashed the new ROM and everything seemed to work perfectly (aside from the Firestarter app). I was able to use Alexa and access my apps etc, HOWEVER, when I was happy with the new install I reinstalled my USB hub - which I had removed to use a USB keyboard to access recovery - and the Fire TV cut out. When I started it up again, it would no longer boot into the main Amazon window. Instead it runs through the "Optimising apps" countdown, reaches the Amazon menu for a few seconds, then cuts and repeats the whole start-up process again and again.

Since then, I have tried every possible recovery method I have come across in these forums, restoring my backups, re-running the installation process etc (I even borrowed my friend's Fire TV 2 power cable to test that), but nothing seems to work. Given that I have no issues booting into recovery or restoring my backups and reflashing the ROM, my gut feeling is that something is wrong with the partition table, but that is far as my technical "expertise" goes and I am currently all out of options.

I considered using the "unbrick_firetv2" option (xdaforums.com/fire-tv/development/firetv-2-unbrick-image-t3313349), but I couldn't get my Windows 10 PC to find my Fire TV 2 and didn't persist in trying since the forum advised that if I could reach recovery, running the unbrick command wouldn't help me any more than that.

Does anyone have any suggestions I can try? I assure you I will write back even if the problem is resolved so other users might also benefit from the information.
[Fire TV Android Development] pfhastie:
OK, I realise my post above was rather long. Here is my problem in summary.

I was successfully running "sloane-5.0.5-rooted_r4" on my FTV2. I updated to "sloane-5.2.4.2-rooted_r2" and it worked well until I plugged in my USB port and it restarted, and I am no longer able to get past boot, only access recovery. I have tried restoring backups and reflashing etc, but nothing seems to work.

Any ideas, my borderline genius friends?