FireTV 1 (bueller) Prerooted Stock Images [5.2.7.3_r1] - Fire TV Android Development

Here are prerooted stock images for use with my recovery. Note that these contain addon.d support, so any 3rd party things you install to /system need an addon.d script to be retained between flashes.
If you are currently on FireOS3 and CWM you MUST install TWRP recovery from the link above before using these.
Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it.
Changelog and Downloads:
July 4, 2020 - 5.2.7.3_r1 (md5sum: 92824186b5eec7e86792897bfb9593b7)
December 7, 2019 - 5.2.7.2_r1 (md5sum: 8dd08a41900a75794f28c455e173141f)
June 29, 2019 - 5.2.7.0_r1 (md5sum: 97b9ffef275d7dffcae085b2325aa9cc)
March 30, 2019 - 5.2.6.9_r1 (md5sum: 2f00ee478118ccf034b70236357ee0a3)
November 27, 2018 - 5.2.6.7_r1 (md5sum: cc455830d78f2d545760f1705dbe4f63)
October 7, 2018 - 5.2.6.6_r1 (md5sum: de48df30cadf9f88865698d3a3e514ef)
June 24, 2018 - 5.2.6.3_r1 (md5sum: c4fcecc0d3dda3f5c58ba9bbc1fddbdc)
January 28, 2018 - 5.2.6.2_r1 (md5sum: facfcc900ac21e70023b6fbf7259b5b0)
October 8, 2017 - 5.2.6.0_r1 (md5sum: 126fffd4f2384a483792b336b0c89b83
July 3, 2017 - 5.2.4.1_r2 (md5sum: ee25fe57cce08dce6c5962871916c7e3
May 1, 2017 - 5.2.4.1_r1 (md5sum: 64451a8f88cb5a3fff53f14c80ba2267)
January 31, 2017 - 5.2.1.2_r1 (md5sum: 4a01e9a4e6bdcb98da97d2438bf5066d)
September 3, 2016 - 5.2.1.1_r1 (md5sum: 4c4cc2b9dc01cf8397905712b8c91ae3)
July 4, 2016
5.2.1.0_r1 (md5sum: c465bbbddaf3254f805bddbf2d162637)
5.0.5_r2 (md5sum: 32c869fff5e39a5c0d2f5f48b3a10ef5)
This includes the same 2ndinit as before and TWRP version 3.0.0-7. This version of TWRP has support for 720p and fixes the crashing/looping.
May 20, 2016 - 5.0.5.1_r1 (md5sum: 5398851cb37ecd6c5df80abe1cc85447)
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - 5.0.5_r1 (md5sum: 924dadb59d73083704844bb27f189449)
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
Everything below here is FireOS3.
September 7, 2015 - Added 51.1.6.3_516012020 (md5sum: fcf1a8ddf2f3bc93280af03dcf408ac8)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
August 20, 2015 - Added 51.1.6.2_516011120 (md5sum: 3fd1cc67fdd3351b470d09cff586fbf8)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
July 21, 2015 - Added 51.1.6.1_516010220 (md5sum: 61ae1e646c970faf137e9a31d64a1316)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
July 9, 2015 - Added 51.1.6.0_516009820 (md5sum: a1b550d1a7b21a348ca6bd0d7127427c)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
May 24, 2015 - Added 51.1.5.3_515040320 (md5sum: a12852edbe6dc24146533f43e0ae4a05)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Apr 15, 2015 - Added 51.1.5.0_515030720 (md5sum: de2ab7f2d3072e10d3e592b73ca52750)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Mar 26, 2015 - Added 51.1.5.0_515020820 (md5sum: b7005dd3cc0b6a15dae21b0170aeae85)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Nov 21, 2014 - Added 51.1.4.1_514013920+fixed (md5sum: 4429327daeed0df852731d81fa9b1f54)
Starting with this update, this requires FireTV Boot Menu.
You also must ensure you have already flashed 51.1.4.0.
Nov 19, 2014 - Added 51.1.4.1_514013920 (md5sum: 348c8b23d785177f7dfd45cc2ef19626)
Oct 30, 2014 - Added 51.1.4.0_514006420+updated (md5sum: b1b48348cb56c0b83a3affc9fd06e07e)
This fixes the Netflix problem from the original 51.1.4.0. After flashing and rebooting, you might get a hung black screen. If that is the case, just pull the power and plug it back in. Also, Netflix might be broken for International people using DNS unblocking. Please let me know if it works/doesn't work for you when using DNS unblocking.
Oct 29, 2014 - Added 51.1.4.0_514006420[/URL] (md5sum: 98074ae3dead5c12ce77d735c2126b80)
Oct 02, 2014 - Added 51.1.3.0_513011820 (md5sum: 8a7b02691760abf11db4c1c583c20d8f)
Sep 20, 2014 - Added 51.1.3.0_513011520 (md5sum: 2dbd022eacbad0b001753d7519f0ad1b)
Sep 19, 2014 - Added 51.1.1.0_511070220 (md5sum: f98fe5b7de4acb5d2dfa4d8586179b98)

---

Here are some guides with step by step instructions:
How to install ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to update ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-update-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to remotely control ClockworkMod on the Amazon Fire TV using ADB
http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/
How to install a Custom ROM Image on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
How to update a Rooted Amazon Fire TV to the Latest Version Without Losing Root
http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/
How to Revert back to Stock Recovery and Stock Software
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/

---

..

---

@rbox when flashing the pre-rooted image, does it also rebuild/replace the recovery?
I'm just curious how these work, and if CWR would then need to be 'dd' again. I did a quick compare between the pre-rooted image and the stock, and the only differences I see are su binary, superuser.apk, and the removal of every file from the root of the zip but:
boot.img
NON-HLOS.bin
prod_cert_swap.sed
sed

---

Luxferro said:
@rbox when flashing the pre-rooted image, does it also rebuild/replace the recovery?
I'm just curious how these work, and if CWR would then need to be 'dd' again. I did a quick compare between the pre-rooted image and the stock, and the only differences I see are su binary, superuser.apk, and the removal of every file from the root of the zip but:
boot.img
NON-HLOS.bin
prod_cert_swap.sed
sed
Click to expand...
Click to collapse
No. It doesn't touch the recovery. These images are basically just the regular image with the bootloader and nonessential images pulled out. And as you can see, it comes with su.

---

rbox said:
No. It doesn't touch the recovery. These images are basically just the regular image with the bootloader and nonessential images pulled out. And as you can see, it comes with su.
Click to expand...
Click to collapse
Doesn't android typically rebuild & flash the recovery partition from boot.img and /system/etc/recovery-resource.dat when it detects it's been changed? I was just curious when that normally would occur on a stock FireTV, and what prevents this from happening on your pre-rooted images. I haven't used any prerooted images. Already had root and just dd'd your cwr_recovery.img. CWR asks you if you want to disable the stock recovery process. As a test I picked no, and CWR didn't get replaced. So should I assume that Amazon doesn't run any scripts at boot that check the recovery and rebuild/flash it?
To make a long story short. I was just curious if your pre-rooted images disabled the recovery replacement, since I still saw the recovery-resource.dat used to build them in the zip. But I guess FireOS doesn't do that at boot
edit: I guess that may have been disabled by towelroot, since the install-recovery.sh is being used to start the /system/xbin/daemonsu --auto-daemon &

---

Luxferro said:
Doesn't android typically rebuild & flash the recovery partition from boot.img and /system/etc/recovery-resource.dat when it detects it's been changed? I was just curious when that normally would occur on a stock FireTV, and what prevents this from happening on your pre-rooted images. I haven't used any prerooted images. Already had root and just dd'd your cwr_recovery.img. CWR asks you if you want to disable the stock recovery process. As a test I picked no, and CWR didn't get replaced. So should I assume that Amazon doesn't run any scripts at boot that check the recovery and rebuild/flash it?
To make a long story short. I was just curious if your pre-rooted images disabled the recovery replacement, since I still saw the recovery-resource.dat used to build them in the zip. But I guess FireOS doesn't do that at boot
Click to expand...
Click to collapse
51.1.3.0 was actually the first version to include an updated recovery. If you look in the stock 51.1.3.0 image, you'll see a recovery directory with recovery-from-boot.p and install-recovery.sh. I removed that from my image. The install-recovery.sh is the one that updates the recovery.
I'm not quire sure why it asked you about disabling stock. I'm guessing you booted into it, did nothing, and then rebooted. The only thing I can guess is whatever you had installed already had a /system/etc/install-recovery.sh script there. That doesn't seem to be included in the stock update images. Maybe the stock recovery writes it if it doesn't exist... Either way, I think people have said the install-recovery.sh script that came with stock didn't do anything. And then when you install one of my updates, it definitely doesn't come with it.

---

Also, I just uploaded 51.1.3.0.

---

rbox said:
51.1.3.0 was actually the first version to include an updated recovery. If you look in the stock 51.1.3.0 image, you'll see a recovery directory with recovery-from-boot.p and install-recovery.sh. I removed that from my image. The install-recovery.sh is the one that updates the recovery.
I'm not quire sure why it asked you about disabling stock. I'm guessing you booted into it, did nothing, and then rebooted. The only thing I can guess is whatever you had installed already had a /system/etc/install-recovery.sh script there. That doesn't seem to be included in the stock update images. Maybe the stock recovery writes it if it doesn't exist... Either way, I think people have said the install-recovery.sh script that came with stock didn't do anything. And then when you install one of my updates, it definitely doesn't come with it.
Click to expand...
Click to collapse
The contents of my install-recovery.sh had to do with the su daemon. So i assume it was from towelroot. edit: actually probably one of the variations of superuser?
Basically I was curious what changes you were making so the stock recovery wasn't being flashed back, just in case I wanted to mess around with later revisions that aren't rootable and might flash the stock recovery back and leave me w/ an unrootable system. Like 51.1.3.0. But I see that you just created a pre-rooted 51.1.3.0 Anyway, it was more of a curiosity than me wanting to have the latest version.

---

Upgrading to Pre-Rooted 51.1.3.0_513011520
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?

---

imtiajmeah said:
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
Click to expand...
Click to collapse
As the post says... the prerooted images are only for use with my recovery. So yes, you have to downgrade and install it.

---

Read Again
imtiajmeah said:
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
Click to expand...
Click to collapse
Regarding these images, the OP states clearly: "These will not work with the stock recovery". You will not be able to update to them without first installing CWM.

---

rbox said:
As the post says... the prerooted images are only for use with my recovery. So yes, you have to downgrade and install it.
Click to expand...
Click to collapse
For the sake of clarity and semantics, is the "Pre-Rooted Stock Software" the same as "Pre-Rooted Stock Images"? The word Images is throwing off my understanding.

---

Hi there,
Just one question i didn't find an answere.
Can i use this stock images on German fire TV?
Thx. For a quick reply

---

Zetup-EXE said:
Hi there,
Just one question i didn't find an answere.
Can i use this stock images on German fire TV?
Thx. For a quick reply
Click to expand...
Click to collapse
I wasn't aware that anyone had gotten the German Fire TV, so... I'll just whip out my crystal ball...
All signs point to it coming with 51.1.3.0, which is unrootable. So... no.

---

Awesome work rbox!
I´m on pre-rooted 51.1.3.0 by now. As soon as i can i´ll keep donating to you! This is exactly why i bought my FTV!
Thanks!

---

mjbxx said:
For the sake of clarity and semantics, is the "Pre-Rooted Stock Software" the same as "Pre-Rooted Stock Images"? The word Images is throwing off my understanding.
Click to expand...
Click to collapse
Yes, they are the same.
Stock Image, Stock Software, Stock ROM, Stock OS, and Stock Package all mean the same thing. The only important distinction to remember is that there is a difference between a Recovery image and the rest of the software that runs on the Fire TV.
"Pre-Rooted Stock Images" do not include the recovery image within them, whereas the official 51.1.3.0_user_513011520 update from Amazon does include a recovery image. rbox has stripped out the recovery image from the official update because if he didn't, installing his pre-rooted version would overwrite ClockworkMod recovery.

---

I assumed this was done, but I wasn't 100% sure so I verified that the updating mechanism has been blocked on these prerooted images.
Code:
[email protected]:/ # pm list packages -d
pm list packages -d
package:com.amazon.dcp
[email protected]:/ #

---

mastermind278 said:
I assumed this was done, but I wasn't 100% sure so I verified that the updating mechanism has been blocked on these prerooted images.
Code:
[email protected]:/ # pm list packages -d
pm list packages -d
package:com.amazon.dcp
[email protected]:/ #
Click to expand...
Click to collapse
i was just about to ask the same thing, thanks. now im just wondering if i can install cwm from 51.1.0.1 as i've been blocking updates since day one or if i should just update to 51.1.0.2 and then install cwm.

---

nhumber said:
i was just about to ask the same thing, thanks. now im just wondering if i can install cwm from 51.1.0.1 as i've been blocking updates since day one or if i should just update to 51.1.0.2 and then install cwm.
Click to expand...
Click to collapse
I am wondering the same thing.
Sent from my SCH-I545 using Tapatalk