yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] BigMatza:
Way to flame that last "naggy" post, which happened on March 14.
[Fire TV Android Development] krawhitham:
http://www.aftvnews.com/pre-rooted-5-0-5-1-rom-for-the-amazon-fire-tv-2-released/

http://www.aftvnews.com/pre-rooted-5-0-5-1-rom-for-the-amazon-fire-tv-2-released/
[Fire TV Android Development] PuntoG:
@Iamandrewj!!! Dude! :mad: DON'T BE MESSIN' WITH MY [MENTION=3991724]rbox[/MENTION]!!! WE ALL LUVVVVSSS US SOME RBOX (And not in that cheap, street corner kinda way either. It's true love.) Personally, he's one of my very few "digital crushes."

"What exactly is holding back the release of pre rooted OS5," is that you didn't do it ya durned self! Bye Felicia...

[MENTION=3991724]rbox[/MENTION], take yo time honey. Those who know you and love you know you're worth the wait. I will be sending yet another donation your way as a token of my appreciation. If I ever see you in person, you'd best believe I'm gonna give you a sloppy wet kiss. Hell. I might even lick your cheek..LOL.

Seriously. Thanks so much for all you do with so little appreciation.
[Fire TV Android Development] rbox:
I need a single person to run cat /proc/cmdline as root on a box with a locked bootloader. If there is any serial numbers, you can remove it if you like.
[Fire TV Android Development] PuntoG:
Sure do wish I could help! I have some 1st gens but they're either rooted with unlocked bootloaders, or un-rooted on 5.0.5.1.
[Fire TV Android Development] mbsans:
This is the output from a rooted FireTV-1 and it's still on 5.0.5. Thanks a lot rbox.

root@bueller:/ # cat /proc/cmdline

androidboot.hardware=qcom user_debug=22 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 androidboot.selinux=enforcing androidboot.emmc=true
androidboot.serialno=xxxxxxxxxxxx009D androidboot.prod=1 androidboot.baseband=apq

root@bueller:/ #
[Fire TV Android Development] PuntoG:
Small Donation

[MENTION=3991724]rbox[/MENTION], I just sent you a small donation. I really do think the world of you. You have made the Amazon FireTV so much fun. Without you, it would be just another boring Set-Top Box in a sea of boring Set-Top Boxes.

I hope I didn't embarass you by my post yesterday, but that guy asking what the problem was really chapped my hide. 24 hours later and I'm still irritated with him. I think everyone here understands you have priorities higher than making free tools for us. And even if you didn't, no one has the right to rush you because you don't owe any of us anything. In fact, it's the other way around. So take your time and don't let ANYONE stress you out. WE NEED YOU!!!

Peace to you my friend, and may the force be with you.
[Fire TV Android Development] rbox:
Thank you. And thanks to everyone who has donated to me.

It's all good, haha. Thanks for the words. I can confirm that I have TWRP and bootmenu fully working and a 5.0.5.1 prerooted rom completed. I just need to do some more testing. Unfortunately, based on the number of people who have needed to use the unbrick image on FireTV2, I need to put in extra testing to ensure the numbers of bricks are kept down. Unfortunately for people with locked bootloaders, I have no recovery method for bricks.
[Fire TV Android Development] Y314K:
Great to hear you are starting the testing phase. Thanks a lot for sacrificing your weekend to get things done. Really appreciate it. :good:

Guess I was way off on my ? regarding splitting the project by bootloader state. As for minimizing the amount of bricking. After a good testing phase. Probably having Elias aka AFTVNews release some video/picture guides for the different devices & starting points @ the same time as you release the files. And putting links on the OPs #1 post should minimize the user error bricking. At least some. ;)
[Fire TV Android Development] Emmes:
so right now my ftv is on 5.0.5, i didnt update it to 5.0.5.1 because i thought there will be problems to unlock the bootloader with your upcoming twrp. Will there be a solution for unlocking bootloader at 5.0.5 at all? Or even twrp or root?
[Fire TV Android Development] bigwillie1:
That's great news. Are there any prerequisites needed to flash TWRP/bootmenu/ROM like a USB keyboard / USB mouse? Or is it possible to use the bluetooth remote from the FireTV1 in TWRP/Bootmenu and adb through wifi from a computer?

Is there no recovery method for FireTV1 devices that are allready bricked? Or is there no recovery method even after flashing your TWRP/Bootmenu/ROM successfully and brick it later on using FireTV1 devices with a locked bootloader?
[Fire TV Android Development] Sizzlechest:
[MENTION=3991724]rbox[/MENTION]: I'm in a bit of a pickle. I'm a cord cutter and rely on Hulu heavily. I can no longer watch Hulu with any of my rooted Gen 1 FireTVs. All of my units are fully unlocked. Can I be a beta tester or something? I'm desperate to get Hulu working again and I suspect it's going to require me to get the latest firmware.
[Fire TV Android Development] fr0st420:
I have the same problem with hulu. It lags and skips alot. Plus both my firetv units try and update to the latest rom all the time so my units are always on because they sit in recovery.
[Fire TV Android Development] YoColdRain:
when you say, you can no longer watch Hulu, what does it mean? it force closes? reason why I'm saying is because it happend to me with youtube app. but forcing firetv to actual restart fixed it.
[Fire TV Android Development] Sizzlechest:
A restart of the FireTV isn't going to fix his, neither will a uninstall and reinstall of the Hulu app. The "app" still plays video, but it's nearly impossible to navigate the menu with the remote or using a USB mouse. I suspect the latest update must be incompatible with the old FireTV firmware.
[Fire TV Android Development] qwer777:
I experience this as well. Pretty much every action is one behind visually. Like you hit left, the selection stays where it is, you hit down, it then shows the selection move left. Then you hit up, the selection moves down, hit OK, and it briefly shows the one to the left of the initially selected item(the actual selection with this set of movements) before opening it.
[Fire TV Android Development] guido1138:
[MENTION=3338723]Sizzlechest[/MENTION]

I had the same issue, and like you also believe it's an incompatibility between my older AFTVv1 custom ROM and the recent Hulu update to 2.5.a. But many thanks to [MENTION=3244446]elmerohueso[/MENTION] , since two years ago he uploaded an archive of his FireTV APKs, which included Hulu 1.9.8. I've tried this APK on my rooted AFTVv1 and it works, but being old obviously has some bugs. Google this to find the post: "Amazon FireTV apps - Ripped for your pleasure"

I'm still hoping to find the Hulu version just prior to the latest 2.5.a, but at least I'm in no hurry now and can wait for the [MENTION=3991724]rbox[/MENTION] release to be thoroughly tested.
[Fire TV Android Development] falk0069:
Try visiting apkpure.com. They maintain several past releases of apks.
[Fire TV Android Development] Y314K:
To bad there are no APKPure's for FTV Apps. There must be someone out there that Has the prior version of Hulu that turned off Auto-Updates. I turned Auto-Update off but I had not installed Hulu.
[Fire TV Android Development] qwer777:
Thanks to a spare fire tv that I haven't used since last June, I have version 2.1.a of Hulu here. Not sure if that's the most recent one before 2.5.a or not as I can't find any version history. Seems to work great for me. [MENTION=1449438]Y314K[/MENTION] You mentioned auto-updates. Is there something I need to do to make sure this version doesn't automatically update to the broken one for me?

EDIT:Link should be fixed!
[Fire TV Android Development] Y314K:
Yes, We can manually control updates for FTV apps...

Go to "FireTV Settings/Applications/Appstore" & set "Automatic Updates" to OFF.

I also recommend you turn off "In-App Purchases". I only turn it on just for single use. I do not leave it as a persistence setting. I also turn off "Collect App Usage Data".

I always make sure I mark ALL apps & games from Amazon or otherwise as a Favorite since I have close to 500 FTV apps on my Apps Library. That way I can quickly find them. Then in the future when you want to see if there is an update of an app just go to the "Apps/Your Apps Library" & check if under each of the installed/favorites app there is an "Update" available. Before you do any update. You can use ES File Explorer to backup the current version of the app you are planning to update. Just a very easy & fast way of keeping a backup & trying out the next version of your app.

This link is just to show you pictures of what it will look under an app once an update is available:

http://www.aftvnews.com/how-to-update-an-app-on-the-amazon-fire-tv-or-fire-tv-stick/

Thanks for posting the Hulu version you have available. :good: But a Decryption key is needed for anybody to be able to download it.
[Fire TV Android Development] kip_dynamite:
Would you guys mind opening a hulu thread? Thanks
[Fire TV Android Development] krawhitham:
I get this when trying to download the Hulu file
[Fire TV Android Development] qwer777:
I'd be happy to! Not sure what section that would go in though.

Updated my post with the correct link.
[Fire TV Android Development] Sizzlechest:
The link above still doesn't work, but the Hulu thread here has the right link: http://xdaforums.com/fire-tv/help/hulu-stopped-correctly-gen-1-rooted-t3363016
[Fire TV Android Development] qwer777:
That's weird. They are the exact same link.
[Fire TV Android Development] jpeg42:
The apps section??

http://xdaforums.com/fire-tv/themes-apps

I have NO idea what any of this has to do with rbox and the prerooted stock images.
[Fire TV Android Development] qwer777:
You're right. It has nothing to do with it. Made a new thread here for further replies.
[Fire TV Android Development] LiquidXed:
Sorry
[Fire TV Android Development] falk0069:
Assuming we have a fully unlocked bootloader, is it now possible to download the latest signed bueller.bin from amzdigitaldownloads.edgesuite.net and apply it via CWM and then apply root after that? If this isn't possible or breaks something, I'll continue to wait for the official pre-rooted version. I know rbox is really busy and I appreciate his work; but if this is now something we can do ourselves, it would be one less thing he'd have to worry about.
[Fire TV Android Development] KLit75:
Making prerooted images for OS3 was possible (though pointless now because every one of them is available.) But Im pretty sure this requires a new recovery.

My best guess is if you suceed the rom will fail to flash. And worse case is you might really mess up your aftv.

If it were just a matter of creating prerooted roms Im certain they would've been released by now.
[Fire TV Android Development] TROJAN4EVR:
Are you on 51.1.6.3_516012020?
[Fire TV Android Development] danielcbit:
[MENTION=3991724]rbox[/MENTION] I Have a Fire TV 1 with a fully unlocked boot loader running 51.1.6.3_516012020, if you need, I can test the new pre-rooted images you are cooking :D
[Fire TV Android Development] redbuddh@:
Aren't we to the point where no one else should post in this thread until rbox does?
[Fire TV Android Development] ldeveraux:
No, it's a discussion thread. Why would people stop interacting just because there's no update from the op?
[Fire TV Android Development] schneid:
I thought danielcbit was offering a sacrificial lamb that might perish in the process. Seems generous to me. I imagine the biggest hurdle in modding is permanent bricking. Lab rats are cheap but AFT's not so much.
[Fire TV Android Development] jpeg42:
No it is a development thread. The discussion thread can be found here:

http://xdaforums.com/fire-tv/help/qa-prerooted-stock-images-t2919379

The point of the thread is for OP to update his development. And for other developers to contribute. And I assume the mods have just left because this type of "discussion" would not be allowed in any other development section on XDA.

Honestly, at this point, saying you will be a "tester", or you are stuck because you can't install hulu, is no different than bugging the developer asking for an ETA.
[Fire TV Android Development] qwer777:
Perhaps I'm misunderstanding how XDA works, and if so please educate me, but what you linked to was for questions and answers, with a separate tab for discussion that leads back here. Doesn't that make this the discussion thread?
[Fire TV Android Development] jpeg42:
Sure:

http://xda-university.com/as-a-user/a-new-users-guide-to-xda-developers

This thread would be a nightmare if ever single discussion about FireTV 1 root was posted here.

But I am done preaching, the mods or OP can do what they like. I just hate getting a notification about hulu installation discussions. And I don't want to check back here daily for updates.
[Fire TV Android Development] YoColdRain:
Yea, lets just keep this as discussion thread specific to prerooted stock images and not HULU apk.
[Fire TV Android Development] LivinOne:
[MENTION=3991724]rbox[/MENTION] just curious as it has been over a month since you last post. If you think the release will happen very soon or are there problems with the ROM on AFTV1? Not pushing , just curious since my AFTV1 is laggy and often needs reboot - hoping OS5 will resolve, thus waiting to try OS5 before resorting to buying a new AFTV2 box. thanks.
[Fire TV Android Development] rbox:
I was testing the bootmenu/recovery installer and noticed the bootmenu wasn't loading... And then I noticed I broke su. So I booted into recovery and noticed a problem with selinux, so I'm trying to sort through that right now. I'll try to release it before the end of the month.
[Fire TV Android Development] mrchrister:
thanks for the update! looking forward to tell my firetv to play radio stations on tunein
[Fire TV Android Development] rbox:
I updated the OP with the FireOS5 5.0.5 and 5.0.5.1 ROMs. These require TWRP to install.
[Fire TV Android Development] mrchrister:
I can confirm it works! Updated FireOS3 to TWRP and then installed the new image. One thing I encountered: I pulled the USB out of the FireTV to connect a mouse, which results in TWRP not starting up. I had to plug the stick back in to make TWRp boot up. The rest of the installation worked flawlessly!
[Fire TV Android Development] rbox:
Not quite sure what you mean "the usb"... I don't have any usb storage plugged in and everything works fine.
[Fire TV Android Development] mrchrister:
sorry, i mean the 8gb stick i had plugged in at the back. without it, it would not launch twrp
[Fire TV Android Development] rbox:
Not really sure, TWRP has no dependence on any usb sticks...
[Fire TV Android Development] mrchrister:
yeah doesn't make sense to me either... but then again, my firetv has been full of garbage from all sorts of projects (like entware and android bash). Anyways, after having the USB plugged in on boot, I was able to install the newest FireOS image. Thanks so much!
[Fire TV Android Development] deepasadish:
Thank you [MENTION=3991724]rbox[/MENTION].

1. Would you recommend a clean wipe before installing the latest fireos 5? I guess this means the ftv runs the initial setup process again?

2. based on earlier discussions in this thread, if I delete the su folder from the zip, I should be unrooted.

It appears I would be first one to test such a setup, since almost everyone installs your ROM to be rooted :). Do you have any specific advice/suggestion/precaution. I have noticed that some stock roms always overwrite with stock recovery on every boot if unrooted. Any such nasty surprises in the firetv ROM? Thanks.
[Fire TV Android Development] 949BFN:
I installed the update, but must have messed up something - it seems that I've lost root and TWRP recovery. No more SU app and trying to disable auto updates, fails. Don't know what I did. At first I thought I uploaded the incorrect rom to the FTV (I downloaded the stock rom some time ago to update another FTV and thought I must have mixed the 2 up in my over-eagerness to update the rooted FTV, but that does not seem to be the case.). Before I did the update, I had done the full (and latest) boot loader unlock and that worked fine.
[Fire TV Android Development] Y314K:
Had u used any of the different USB mount scripts out there on your FTV1 at anytime. Some of them move parts from internal storage over to the USB.
[Fire TV Android Development] nikolaus2007:
[MENTION=3991724]rbox[/MENTION]

Does this work for Fire TV Stick as well in any way or will there be another procedure for the stick?
[Fire TV Android Development] rbox:
You don't need a wipe, it should support seamless upgrades from 3 to 5.

Yes, if you delete su, it should not be rooted.
[Fire TV Android Development] ldeveraux:
I was on os3 and had an unlocked bootloader. I updated CWM to TWRP, then installed the 5.0.5.1 prerooted image. Everything went well so I deleted the zip file from /sdcard/. Was I not supposed to do this? For some reason I can't even get the FireTV to power on anymore. Not sure if it's the fire or the power supply...
[Fire TV Android Development] rbox:
Are you 100% sure you had a FULLY unlocked bootloader and were on the LATEST version of CWM?
[Fire TV Android Development] ldeveraux:
I'm 95% sure, I had followed aftvnews guide to unlock when it was first released, and I updated a few months ago. I installed twrp fine, then the os fine, everything booted, plex worked well. I unplugged to move it back to the tv and now nothing. No lights, no boot.
[Fire TV Android Development] deepasadish:
that seems very similar to the efuse problem a long while ago.
[Fire TV Android Development] rbox:
If you unlocked when it was first released, then that wasn't the full unlock. And if you updated "a few months ago"... what did you update? It sounds like you were not fully unlocked and you were not on the latest version. And it probably said "flashing kernel for locked bootloader" when you installed the ROM.
[Fire TV Android Development] NxtGenCowboy:
I know mine was unlocked and apparently my wife did a factory reset for some reason... Seems as tho mines no longer powering on now.
[Fire TV Android Development] rbox:
Was it FULLY unlocked and were you on the LATEST version of CWM?
[Fire TV Android Development] NxtGenCowboy:
Yes. I have another one here I'm going totry as well

---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------

Which version do you want exactly on it, I'll double check this other unit before I update it.
[Fire TV Android Development] rbox:
Please pay attention to the end of the flash when it says what type of kernel it is flashing. If it says locked bootloader, so not reboot it.
[Fire TV Android Development] rbox:
The latest, 6.0.5.1.4a.

Also, from within FireOS, run cat /proc/cmdline and make sure it says unlocked_kernel=true.
[Fire TV Android Development] NxtGenCowboy:
Yes I will.

My last unit,After it flashed, it optimized and booted. Was working fine. Then did a factory reset and then it seems as though it won't even power on now.
[Fire TV Android Development] rbox:
That sounds like the efuse and you weren't fully unlocked.
[Fire TV Android Development] NxtGenCowboy:
Well that isn't good. Double checking this other unit now.
[Fire TV Android Development] ldeveraux:
I completely missed the line to check for unlock before flashing TWRP. Regardless, I believe I had unlocked it at some point recently. I know I was on the latest OS and the latest CWM. Would TWRP install and boot properly if it wasn't unlocked? Would the 5.0.5.1 image also boot properly? These were both successful, not until I powered off did it fail. :( Is this a hard brick if so? I'm guessing I can't recover from this...
[Fire TV Android Development] rbox:
You know, I guess TWRP wouldn't have been unless it was fully unlocked. If you plug a USB cable in and turn it on, does your computer see a hard drive?
[Fire TV Android Development] ldeveraux:
Huh, good thing I still have the A-A cable from the FireTV 2 root! yeah, using the A-A it's a drive with a folder named "image" inside. So it's getting power, just not booting?
[Fire TV Android Development] rbox:
It's blown the fuse. You're going to need Linux to fix it.
[Fire TV Android Development] NxtGenCowboy:
I know my firstunit had the bootmenu v1 and latest recovery 6.05.1.4a. Like I said it worked/booted after I updated, when the factory reset option was used, is when it didn't boot/show any life. I'll plug it in and see again in aminute.

My 2nd unit is eon The latest, 6.0.5.1.4a and 51.1.6.2_user_516011120 and fully unlocked(cat /proc/cmdline does state androidboot.unlocked_kernel=true) . I'll flash the newer OS in a minute
[Fire TV Android Development] ldeveraux:
That's fine I'm no stranger to Linux. I don't have to solder to the EMMC though, right? That's a huge pain. Is there a tutorial for this? Couldn't find one on AFTVnews...
[Fire TV Android Development] NxtGenCowboy:
My first box is in the same boat. I do see it as a HDD. And I am on linux.. OpenSuSe
[Fire TV Android Development] rbox:
Unbrick

For those with FireTV1 with unlocked bootloader that rebooted after flashing 5.0.5 and it won't turn on, you can recover it, but it won't be unlocked anymore. But you'll still have root and bootmenu/twrp.

Plug it in with USB to a LINUX computer and turn it on. It should show up as a hard drive. Make sure to unmount anything that automatically mounted.

Download the 5.0.5 update package: http://amzdigitaldownloads.edgesuit...te-kindle-bueller-51.5.3.7_user_537174420.bin

Inside the images directory is all the firmware.

NON-HLOS.bin = partition 3

sbl1.mbn = partition 4

sbl2.mbn = partition 5

sbl3.mbn = partition 6

tz.mbn = partition 7

rpm.mbn = partition 8

emmc_appsboot.mbn = partition 9

Aso in the top level is the kernel:

boot.img = partition 10

You need to dd these images to each of the cooresponding partitions. If the firetv showed up as /dev/sdb on your computer, then to dd the NON-HLOS.bin partition you would do:

dd if=NON-HLOS.bin of=/dev/sdb3

It is extremely important that you do not write something to the wrong partition, and you write every single image (8 of them) to the correct partitions.

After all the partitions have been written, type

eject /dev/sdb

replacing sdb with whatever device the firetv showed up as.

After doing this, it *SHOULD* boot up.
[Fire TV Android Development] doctorjei:
I am in the same boat as 949BFN. Started with recovery, fully unlocked, rooted, on OS3. After updating, no recovery, no root. :/ A difference from 949BFN - I was on CWM (latest) and skimmed over the recovery section which mentioned TWRP. Don't know if that makes a difference. But too late for me at this point, anyway. Still boots up fine.

I am happy to try things if there are any suggestions. I am on 5.0.5.1 now.
[Fire TV Android Development] rbox:
Are you implying you did not use TWRP to install?
[Fire TV Android Development] doctorjei:
Right. That is clearly my mistake. I used CWM.
[Fire TV Android Development] rbox:
Why do I even bother writing instructions if people don't read them? You can download the TWRP image and flash it with fastboot.
[Fire TV Android Development] doctorjei:
Hey, I'm sorry. I missed it. I appreciate the help.
[Fire TV Android Development] Petesky:
Are updates from amazon blocked on these images or do I still need

to block them
[Fire TV Android Development] rbox:
It's supposed to prevent automatic updates, but you should always block them regardless.
[Fire TV Android Development] ldeveraux:
I attached my dead FireTV to my RPi running Raspian, there were 6 mountable partitions, 3 were automatically mounted. I unmounted them. 'lsblk' found 20 partitions under sda, and I ran the sudo dd for each of the partitions you mentioned. For me, there was no effect, the FireTV still wouldn't boot at all. I can still attach to the Pi so the partitions are still there, but won't boot as a FireTV. I hope someone else has better luck than me. :(
[Fire TV Android Development] rbox:
That's weird. Are you sure it actually wrote all of them? I would have expected it to be completely dead or work if you had successfully written the new appsboot.