yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] rbox:
The warning is in BIG RED LETTERS because it will result in a brick.
[Fire TV Android Development] jim16127:
That's depressing! :crying:
[Fire TV Android Development] Renegade1504:
You can try this : https://xdaforums.com/fire-tv/development/firetv-2-unbrick-image-t3313349
[Fire TV Android Development] ryknow27:
[MENTION=3991724]rbox[/MENTION] Thank you for the update!!:)
[Fire TV Android Development] MicrosoftBug:
Anyone tried the latest update with Xposed? Does it work properly??
[Fire TV Android Development] brandonp213:
Ok it says flash 5.2.6.7 before flashing latest ,does it matter if r1 or r2 I assume it wouldn't make a difference can someone confirm please
[Fire TV Android Development] mjh8812:
do these prerooted stock images block future updates being pushed from Amazon automatically or do i need to do it manually after they are installed (ie adb services disable method)?
[Fire TV Android Development] real-bluebean:
Just read first post...
[Fire TV Android Development] BIOYAM:
I tried, and it didn't work. The last one to be successful (for me), was v5.2.6.6_r1

---------- Post added at 07:37 AM ---------- Previous post was at 07:35 AM ----------

They are essentially both the same, but I would go with r2, since it would have fixes since r1.

---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------

Even though the OP mentions that stock recovery is disabled by default, it is still adviced to manually block OTA software updates. A good guide can be found here:

http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/#root
[Fire TV Android Development] Michajin:
i am on the latest with xposed installed. I installed it from the apk.

---------- Post added at 01:23 PM ---------- Previous post was at 01:23 PM ----------

Anyone know why

com.amazon.amazonvideo.livingroom.firetv

is disabled? just curious... I don't remember disabling it, but both my firetv2 had it disabled? I have updated to the latest...
[Fire TV Android Development] gokmenm:
fire tv 2 brick

Hello there.

Amazon fire tv 2 box (2015) my device does not work.

Emmc is broken. not repaired.

The warranty period is over.

I need an emmc dump file.

Please locate this file.

I want the original preloader.

Please.

Or is it possible to find the original mmc in firetv2?
[Fire TV Android Development] zroice:
hey guys, just installed 5.2.6.7_r2 on my very old (i think 5.0.5) firmware - it finished successfully, also said it updated the firmware, but now the firetv doesnt boot.

Stuck at the boot logo - already wiped it but still the same.... =(

Did i forget anything? the recovery is still working fine.

--- will try with data format first i guess?

EDIT: format data did the job apparently - BUT will auto update/stock recovery still be disabled after format data??
[Fire TV Android Development] diodanny:
looking for way to fix

ihave the same problem but it coan possible to fix only changing the boot.img but i don find the way anyone have mtk scatter or flash direct emmc?
[Fire TV Android Development] DanielF50:
Just got a OTA for 5.2.7.0 come down - decided to let it download but didn't install & uploaded the OTA here for [MENTION=3991724]rbox[/MENTION] (or anyone else), if needed :good:
[Fire TV Android Development] BIOYAM:
..... Nevermind !!!
[Fire TV Android Development] ryknow27:
Thanks!:good:
[Fire TV Android Development] MicrosoftBug:
Anyone tried the new firmware with Xposed?
[Fire TV Android Development] BIOYAM:
[MENTION=3991724]rbox[/MENTION],

In your OP, you quote: "NOTE: If you were at 5.2.6.6 or below, you MUST flash 5.2.6.7 before going to 5.2.6.8 or later."

If I am on your rooted v5.2.7.0_r1, can I not go back to v5.2.6.6_r1 (via TWRP) without causing issues?

Thanks in advance for your time.
[Fire TV Android Development] ryknow27:
I have actually done this more than once. I tried the last 3 firmwares but keep going back to 5.2.6.6 because Alexa does not seem to work on any newer firmware. Just flash 5.2.6.6 via TWRP and reboot and all should be good. Just be sure to block updates using "pm disable com.amazon.device.software.ota" in adb shell so it does not update.:D
[Fire TV Android Development] BIOYAM:
Thank you for this confirmation...... I too prefer 5.2.6.6_r1..... Just missing stuff I don’t use anyways. Alexa is much more important to me too.

And yes, I always block the updates as you describe. In addition, I edit the build.prop after full root (using something like ES File Explorer, and change the line “ro.build.version.number=“, changing the version number to “987654321”.
[Fire TV Android Development] ryknow27:
Just curious but, what is the purpose of editing the build.prop?
[Fire TV Android Development] BIOYAM:
I got the tip from FTVnews a while ago..... It is suppose to fool the fireTV into thinking that it is currently running version 987654321. Which is higher than the version waiting to be updated, so the FTV never downloads it. I am not sure if it still actually works, but it is a simple edit & if it provides a third level of protection, why not? ..... ;)

Hope this helps.
[Fire TV Android Development] TalNum:
Just a quick FYI, as I wasn't sure if you were aware of this.

If you have also flashed the Xposed framework within TWRP, it seemingly causes Alexa to enter a never ending crash loop. If you run back to page 67 or so of this thread, you'll see a brief conversation on this. I lost Alexa functionality post 5.2.6.6 and it was due to Xposed; once I flashed the uninstaller, normal Alexa functionality returned. If Xposed is very important to you, it looks as though you are limited to 5.2.6.6 firmware or prior. I would just hate to see someone damage their device from this crash loop because they were unaware of this.
[Fire TV Android Development] ryknow27:
Thank you for the info! I am currently running 5.2.6.6 so I can have the full Alexa functionality and still use Xposed with the Xposed edge module. Hopefully someone will be able to figure out the crash loop so we can upgrade and use Xposed.:p

---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------

Oh cool, thanks!
[Fire TV Android Development] Rincewind2011:
Hello,

How can I disable the Amazon Blacklist Thing?

for fire starter...

The comnand pm enable de.belu.firestarter works until the device reboots.

And "pm disable com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService" is not working anymore.

Thx
[Fire TV Android Development] Rincewind2011:
I figured out that the the settings program was renamed to

.v2

So the new commandline is:

Disable the blacklist by running the command:

pm disable com.amazon.tv.settings.v2/com.amazon.tv.settings.v2.tv.AppDisableService

This again survives a reboot. And I can (re) enable the FireStarter app.

Greets
[Fire TV Android Development] chris-89:
[MENTION=3991724]rbox[/MENTION]

When you have some time...

mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.4.6_user_646581820.bin mPackageVersion=646581820 mPackageVersionName='Fire OS 5.2.7.1 (646581820)' mManifestId=-87110543 mMetadata={binaryType=full, md5Sum=d154afb53ef9de48de8b5f9de2dbfb19},
[Fire TV Android Development] rbox:
I updated the OP with 5.2.7.1.
[Fire TV Android Development] TalNum:
Always appreciate the hard work, rbox!
[Fire TV Android Development] lasikie:
If I’m currently on 5.2.7.1 unrooted is it possible to install this to gain root access?
[Fire TV Android Development] kwiksi1ver:
Yes. It's a hardware exploit and can't be patched.
[Fire TV Android Development] lasikie:
One of the first instructions requires root access though which I can’t get as I’m on 5.2.7.1 unless I’m missing something obvious.
[Fire TV Android Development] kwiksi1ver:
Nevermind, I'm in the wrong thread. I thought this was the fire stick Gen2 (tank) thread. I don't know much about the Sloane device sorry.
[Fire TV Android Development] JethroC:
[MENTION=3991724]rbox[/MENTION]

Any chance of an updated rooted image for 5.2.7.2?

Much appreciated :)
[Fire TV Android Development] DanielF50:
Edit: nvm, this was a device specific issue.
[Fire TV Android Development] rbox:
Mine isn't trying to get 5.2.7.2 yet. So I can't get the URL.
[Fire TV Android Development] trickyrick:
FireTV sloane Stock Image

Can I use this on FireTV 1st Gen
[Fire TV Android Development] Rortiz2:
Oh come on... Just do a quick search:

"Prerooted Stock Images for FireTV 1st Gen"

No... You can't use this images. You are searching for this:

https://xdaforums.com/fire-tv/development/prerooted-stock-images-t2882337

Cheers.
[Fire TV Android Development] JethroC:
No problem. I've been on it for over a week now but it may not be the same for others
[Fire TV Android Development] ForForkSake:
Nah still 5.2 7.1 here

Does the security patch situation not worry anyone?
[Fire TV Android Development] Nick_Logsdon:
What su binaries is the rooted ROM using

Hey, first time poster.

I have successfully rooted my fire TV gen 2 (thank you for the ongoing support for it btw) but I'm curious on who's su binaries was this from? What I mean is is it chainfire you used? And if so have you had any negative repercussions Downloading the "newest" chainfire apk and updating it's binary?

Thank you
[Fire TV Android Development] ForForkSake:
Ignore.. See latest post
[Fire TV Android Development] ryknow27:
Has anyone tried using Xposed with 5.2.7.1? I know Alexa wasn't working with anything above 5.2.6.6 with Xposed installed.
[Fire TV Android Development] alixyz:
Here is the workaround which I had found few months ago but don't recall where I found it. It's not a clean solution but gets the job done.

1. Install Halo Themer

2. Locate SuperSU and change the Theme to Material Dark.

SuperSU still won't have a launch option from FireTV Launcher but will work if launched from another tool.

3. Either long press on SuperSU from Halo Themer (or other methods) to launch SuperSU
[Fire TV Android Development] Sus_i:
Can you explain that?

Installed/sideloaded as user app, accessing supersu settings is possible?
[Fire TV Android Development] ForForkSake:
Woops... It does indeed install, I assumed it worked but clearly does nothing without his superuser binaries.

However.. I did manage to get rid of the update binary notifications by running osm0sis UnSu script followed by supersu system mode 2.82 SR5 in TWRP.
[Fire TV Android Development] Sus_i:
Thanks for clarification. I think stop notifications should also work without the UnSu Script, with only flashing latest beta. I'll try that if I get time.
[Fire TV Android Development] c3po_droid:
here you are:

mPackageVersion=648594820,

mPackageVersionName='Fire OS 5.2.7.2 (648594820)', mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/93628b8d72ae4ee527ba885a182de77e/update-kindle-full_sloane-36.6.4.8_user_648594820.bin,

mMetadata={binaryType=full,

md5Sum=4c9c5a589050f58363c0b58b3f95e0a5},

Thank you so much for everything you're doing for Sloane and Mantis :)
[Fire TV Android Development] cyclops13:
I have a FireTV 2 box with TWRP and on Fire OS 5.2.6.8 (630508620). What would be the best way to unroot it and update to latest version?
[Fire TV Android Development] Bevnrick:
Removing root a requirement ? So much easier to use these images to just update to the latest version [5.2.7.1].
[Fire TV Android Development] cyclops13:
Its rarely used so I thought I might as well just sell it. And before selling I thought unroot and restoring stock firmware will be the best option.

But looks like its not rootable anymore with the latest firmware? If thats the case I am wondering if I should just eBay it as rooted hoping to get higher bid! :D
[Fire TV Android Development] ForForkSake:
Course it's rootable.. now we have a short it can be downgraded to whatever you'd like
[Fire TV Android Development] cyclops13:
Thats amazing, thanks for sharing even-though we have to open it up.

So is there anyway to unroot it safely?
[Fire TV Android Development] ForForkSake:
Just upgrade to stock

[MENTION=3991724]rbox[/MENTION]. . Its trying to update itself to 5.2.7.2 daughter neatly pressed update... Lol I better stop it
[Fire TV Android Development] sokrin:
crossing fingers for the latest pre-rooted image!
[Fire TV Android Development] elliwigy:
so youre saying i need to hook them together with a ethernet cord?

And I have a usb/bluetooth dongle but doesnt work..

i had the k400 plus which did but had to take it back unfortunately..

if worst comes to worst theres a goodwill around the corner that surely has old keyboards/mouseslaying around..
[Fire TV Android Development] rbox:
I'm saying you can only do recovery adb over ethernet.
[Fire TV Android Development] elliwigy:
I see.. well looks like a paperweight until i can get a usb keyboard lol.

I wish there was specific instructions somewhere on the internet lol..

i thought was as easy as adb connect, adb shell and mouse as was advised lol

all good though ill try n get one later today
[Fire TV Android Development] bula1ca:
I have the same exact issue and I have a K400.

K400 works under 5.0.5r1 with v3 (3.0.0-2) recovery but as soon as I install V4 (3.0.0-3) stops working, plugged in a wired keyboard as well - no response from USB port at all.

Not sure why but I tried everything I can think about 9including numerous power off/on) so I had to go back to above set-up after installing and un-installing v4 (5.0.5 r1 or r3) few times today. May help you to get it up and running again - install 5.0.5r1 and then revert recovery to v3.
[Fire TV Android Development] rbox:
Yeah, I'm not sure. I just use a FLIRC and never have problems. I had some issues once while I was screwing around with things, but I think unplugging/replugging fixed it. I haven't been able to duplicate any issues since then though. I tried a few times.
[Fire TV Android Development] Axecaster:
Also experiencing the unresponsive k400 keyboard with the recovery included in 5.0.5 v3, 3.0.0-3
[Fire TV Android Development] rbox:
For those having trouble with the keyboard, and haven't already tried to fix it by flashing down to something else, please try this ramdisk:

http://www.mediafire.com/download/8pv85anwb4phhcv/ramdisk-recovery.cpio.lzma

Place it in /system/recovery
[Fire TV Android Development] bula1ca:
I hope this may have other that have the same issue:

a) Current set-up: 5.0.5r1 and recovery 3.0.0-2, using a K400 keyboard, wireless dongle is inserted directly in the usb port. - no issues

b) Re-installed recovery v4 (3.0.0-3) and keyboard stopped responding.

c) Copied ramdisk-recovery.cpio.lzma to .system/recovery, rebooted, unplugged - keyboard is not responding

d) Installed a power USB hub, plugged k400's dongle into it now keyboard is working fine again, re-booted few times and it works every time

e) re-flashed recovery v4 again (using 1st page posted zip file) and no issue - keyboard works every time

Not sure why keyboard worked with dongle plugged directly into USB port in v2 and V3 and not with v4 however at least I can use it now.
[Fire TV Android Development] rbox:
Flash 5.0.5_r3 and reboot. See if it works. If it doesn't work, then try replacing the ramdisk, and seeing if it works.
[Fire TV Android Development] bula1ca:
Tried few things, please see above. I would appreciate your thoughts on it. Thank you for all your work.

---------- Post added at 09:20 AM ---------- Previous post was at 08:48 AM ----------

a) Flashed 5.0.5_r3

- dongle inserted directly in USB port - no responce.

- dongle inserted in a power USB hub - keyboard works

b) Copied ramdisk-recovery.cpio.lzma to .system/recovery, rebooted, unplugged

- dongle inserted directly in USB port - no responce.

- dongle inserted in a power USB hub - keyboard works
[Fire TV Android Development] gazdaman.:
Hi [MENTION=3991724]rbox[/MENTION]

Would you consider enabling External storage write access in future root images with a modified platform.xml file?

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_r" />

<group gid="sdcard_rw" />

<group gid="media_rw" />

</permission>

Cheers
[Fire TV Android Development] Sajhid:
Hi guys newbie here, I have successfully rooted my firetv2 with the guide provided here. Since I used the prerooted rom 5.0.5 r1, will i be able to use the 5.0.5 r3 and flash it just by using TWRP in recovery mode?

Thank You
[Fire TV Android Development] ImCoKeMaN:
Isn't there a thread where people were bricked after a factory reset when doing that? It sounds like a fine mod for someone to include as a recovery zip, but I'm not sure that should be default as these are intended to be stock rooted roms, not custom roms.
[Fire TV Android Development] bula1ca:
Yes, that is the correct way.
[Fire TV Android Development] Sajhid:
So I just put in a USB or Microsd card and use that from recovery and need any adb commands?

Thanks
[Fire TV Android Development] deanr1977:
Yes put on your usb, open recovery, select install, find location of your zip, select it, press swipe to install, once finished then press reboot.

Press that thanks button If this helps
[Fire TV Android Development] rbox:
http://www.mediafire.com/download/sejm1hndii4i7pi/ramdisk-recovery.cpio.lzma

[MENTION=6169935]bula1ca[/MENTION], [MENTION=3549022]Axecaster[/MENTION], and anyone else who is having keyboard troubles

Please flash 5.0.5_r3. Verify your keyboard is NOT working, and then replace the ramdisk with the one above. It should fix it...

[MENTION=3812611]elliwigy[/MENTION]

Were you able to get it working? When I was in the situation where the keyboard was not working, I noticed if I unplugged it for like 5 seconds and plugged it back in, it would work. Also, people were noting that if you used a USB HUB it would also work.
[Fire TV Android Development] bula1ca:
I posted my findings in post#70, hope it helps

---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------

Sorry you probably missed my previous post (#70)

a) Flashed 5.0.5_r3

- dongle inserted directly in USB port - no responce.

- dongle inserted in a power or no power USB hub - keyboard works

b) Copied ramdisk-recovery.cpio.lzma to .system/recovery, rebooted, unplugged

- dongle inserted directly in USB port - no responce.

- dongle inserted in a power or no power USB hub - keyboard works
[Fire TV Android Development] rbox:
I did see that when you first made it. This is a NEW image. Did you try this new image?
[Fire TV Android Development] bula1ca:
Good job, sir! Works with dongle plugged directly in he USB port now, no need for hub.
[Fire TV Android Development] ForForkSake:
I just did the adb command to stop it instead . Hapoy days
[Fire TV Android Development] smumar143:
Can I root my firetv 2 , mistakenly i updated to 5.2.7.2
[Fire TV Android Development] DanielF50:
https://xdaforums.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
[Fire TV Android Development] m1steron:
Thanks for update. Installed and working great.

Quick question: do you have a solution for the Premier League streaming issue. I receive the message "Update required. An updated version of the app is required for this content. Error Code: 8056"

Any ideas?
[Fire TV Android Development] smumar143:
Pls share the link of recovery and install recovery files , as I am a bit confused about the files. I want to root 5.2.7.2 fire TV 2
[Fire TV Android Development] m1steron:
Anyone?

You can check to see if this happens on your Fire TV by using the voice search. Say 'Premier League' and try to play one of the matches.
[Fire TV Android Development] chappatti:
2018 OP links are not working. Mediafire cannot find files. I have tired multiple browsers.....:(:(

Any one have mirrors, please? I need to install 5.2.6.7 before going to the latest.

Thanks!
[Fire TV Android Development] rbox:
I fixed the link for 5.2.6.7_r2.
[Fire TV Android Development] chappatti:
Thank you, sir !!!!!!
[Fire TV Android Development] roligov:
[MENTION=8052006]m1steron[/MENTION] I had this same issue. It looks like some APK's were not updated when they firmware was updated. First time I've tried to stream the football on my rooted firetv 2. I've just managed to resolve this on my end.

Solution to error code 8056:

- Update rooted AFTV2 to sloane-5.2.7.2-rooted_r1.zip

- SSH or adb shell into device and run:

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

"pm unhide com.amazon.device.software.ota"

Then on firetv 2 go search for update...it will say it's updating system components. This won't update your firmware since you already on the latest as of posting this. It will download a bunch of APK's and install them, here is an ls -alh of my /cache dir on the firetv...Look at the dates of those files, all new:

It's working for me now, going to watch Man City vs Wolves game.

When you done remember to block updates again:

- SSH or adb shell into device and run:

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

"pm hide com.amazon.device.software.ota"

[MENTION=3991724]rbox[/MENTION] Can anything be done to include updates to system components in future updates?
[Fire TV Android Development] 95braves:
adb Shell?

MacBook-Pro:~ braves95$ adb connect 10.0.1.19

already connected to 10.0.1.19:5555

MacBook-Pro:~ braves95$ adb shell

error: device offline

I was able to load the rooted firmware from the same add telling me its offline. Wondering how to get into the shell to verify SU? the amazon fire tv 2 does get me a notification that SU needs to be updated.

MacBook-Pro:~ braves95$ adb kill-server

MacBook-Pro:~ braves95$ adb start-server

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

MacBook-Pro:~ braves95$ adb connect 10.0.1.19

connected to 10.0.1.19:5555

MacBook-Pro:~ braves95$ adb shell

error: device offline

MacBook-Pro:~ braves95$ adb devices

List of devices attached

10.0.1.19:5555	offline

MacBook-Pro:~ braves95$ /Users/braves95/Downloads/Android-4/ADB-Install-Mac.sh

This will install ADB and Fastboot on your computer.

Root Permissions required. Please type your password.

Password:

Changed directory to /Users/braves95/Downloads/Android-4

Moving ADB

mv: Mac/adb_Mac: No such file or directory

ADB Moved to /usr/bin/adb

moving Fastboot

mv: Mac/fastboot_Mac: No such file or directory

Fastboot moved to /usr/bin/fastboot

You may now run Android Debug Bridge and Fastboot commands

Have a nice day.

MacBook-Pro:~ braves95$ adb shell

error: device offline
[Fire TV Android Development] roligov:
[MENTION=10414021]95braves[/MENTION] Just go to manage apps and look for the "Super SU" app. If it's there then you rooted.

You can also install "Terminal Emulator" (https://play.google.com/store/apps/details?id=jackpal.androidterm) on the fire tv and run "su". You should get a root warning on FireTV Screen, just accept.

Lastly you can install "SSH Droid" (https://apkpure.com/sshdroid/berserker.android.apps.sshdroid) on your FireTV, ssh into your firetv and run "su". You should get a root warning on FireTV Screen, just accept.
[Fire TV Android Development] 95braves:
SU

It does show up in the APPS section. The apps you want me to download is that on the AFTV2 or on my phone and then side load them to the AFTV2?
[Fire TV Android Development] roligov:
If the Super SU app is there then you are rooted. Yes you can either download them directly to the FireTV with "Downloader" (https://troypoint.com/install-downloader-android-tv-box/) or install on phone and send to firetv with something like AGK Fire (https://play.google.com/store/apps/details?id=com.googletv.sideloader&hl=en_GB) or Apps2Fire (https://play.google.com/store/apps/details?id=mobi.koni.appstofiretv&hl=en_GB).
[Fire TV Android Development] 95braves:
SU

Ok got kodi installed using the side loader. What I wanted to do was verify it wont install updates unless I install the firmware myself.
[Fire TV Android Development] m1steron:
Thanks for this but in the end I took a more drastic option and factory reset the device. Seems to have worked.