yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] rbox:
I would recommend unmounting everything first, then doing the dd, then running sync 3 times, then you should be safe. Unfortunately, you're going to need to replace it all with the firmware from 51.1.4.1. You have good firmware on there now, so dd'ing back the same stuff won't really do anything, it's not corrupt, which is usually the case when this happens. The problem is they blew a fuse which prevents anything but the 51.1.4.1 bootloader from working. The end result should be a 51.1.4.1 /system with su, but the inability to boot CWM or bootmenu, or update (since you'll loose root). The extremely important part is to make sure you get everything including recovery and boot.

I know the new firetv control app is there. And there is a 'sleep' item in the menu, but that might have come in with 51.1.4.0.

Yes, the store I got it from still had firmware 51.1.0 on it, which is the original stuff it shipped with. When you plug that in, it'll be forced to update, so if you have the domains blocked, it'll just sit there forever. So you'll have to unblock, let it update, and then pray it's updating to 51.1.0.2. Then after it reboots into recovery, reblock the domains. Then when it boots again, you should be golden.
[Fire TV Android Development] Kramar111:
[MENTION=3991724]rbox[/MENTION]

I'm alive!

Got bueller-ota-51.1.4.1_user_514013920-signed with su :)

Thank you very much!
[Fire TV Android Development] nhumber:
Woo hoo good job man. Anything u did different than your plan from the other post besides rbox suggestions? Might make a cable and fix mine tonight.
[Fire TV Android Development] Kramar111:
No, just use bueller-ota-51.1.4.1_user_514013920-signed + recovery-stock-51.1.3.0.img variant (dd if=recovery-stock-51.1.3.0.img of=/dev/sdc11, not recovery-stock-51.1.0.img)
[Fire TV Android Development] nhumber:
Thanks. did u check if updates are still blocked via pm disable? And thanks to rbox for all his work he's put into the box and helping everyone here!!!
[Fire TV Android Development] Kramar111:
I have not tested. Just type "pm disable com.amazon.dcp" in adb shell :)
[Fire TV Android Development] dillfever:
thanks rbox installed your bootmenu sweet.....then booted to recovery and installed your 51.1.4.1-fixed another sweet.....everything is working great,tanks again and here's a little donation for all yuor hard work....dill 05U054341S225930J
[Fire TV Android Development] rbox:
Thanks!
[Fire TV Android Development] deepasadish:
51.1.4.1 works great. Thanks rbox.
[Fire TV Android Development] ImCoKeMaN:
Does screen mirroring work for others on the 51.1.4.1 version? I just tested and my S5 and nexus 7(2013) both were not finding the fire tv for screen casting when I had it enabled on the firetv. wasn't sure if this is a root thing or not.
[Fire TV Android Development] jarayn:
yeah mirroring works on the latest.

note 2
[Fire TV Android Development] forall4xhd:
It's possible have a root for the latest version fw 51.1.4.1?
[Fire TV Android Development] ImCoKeMaN:
You have to have rooted with the original firmware, but if you are already rooted, or find a device that can be rooted you can load the image from the OP. Be sure to follow all instructions though as it requires a sequence - root, bootloader unlock, CWM, bootmenu.img then the this latest rom can be loaded.
[Fire TV Android Development] cd2022:
Can you help a noob out with the files you used to unbrick, "sync" and "unmount" stuffs. Better yet can you write a guide of some sort? I'm using Fedora, would it work too?
[Fire TV Android Development] nhumber:
in the last 3 pages there's posts with EVERYTHING u need and how to do it, fedora works too. I can confirm. If u have a specific question on a part u don't get, someone will try and help
[Fire TV Android Development] cd2022:
Thanks, I'm not too clear about where to find the files that he used: boot.img( is this the bueller-ota-51.1.4.1_user_514013920-signed renamed? ,NON-HLOS.bin

Is this the stock recovery as found in AFTVnews.com : 51.1.3.0_user_513011520.?

And these files need to be in the fedora environment?
[Fire TV Android Development] Kramar111:
Hmm...

My English is very bad, so excuse me

Maybe AFTVNews.com publish adapted guide?

But i'll try.

Only if your Fire TV does not power on and detected in GNU/Linux with ID 05C6:9006 (QHSUSB_DLOAD 9006) (connected thru USB A-A cable)

1. Download 51.1.4.1_user_514013920 "your's version" Stock Software and 51.1.3.0_user_513011520 "your's version" Stock Recovery from http://www.aftvnews.com/software/ or http://www.aftvnews.com/software-fireos3/ to any folder (for example, /tmp/123)

2. Extract boot.img, sbl3.mbn, sbl2.mbn, sbl1.mbn, tz.mbn, splash480p.img, splash1080p.img, emmc_appsboot.mbn, splash720p.img, NON-HLOS.bin, rpm.mbn from bueller-ota-51.1.4.1_user_514013920-signed.bin "your's version"-signed.bin

3. Run terminal and execute

ls -l /dev/sd*

find which of sd* have 20 partitions and substitute sdc to sd"your letter" in dd commands

4. Unmount all sd"your letter" volumes (if mounted)

5. Back to terminal and execute as root

dd if=/tmp/123/boot.img of=/dev/sdc10
dd if=/tmp/123/sbl3.mbn of=/dev/sdc6
dd if=/tmp/123/sbl2.mbn of=/dev/sdc5
dd if=/tmp/123/sbl1.mbn of=/dev/sdc4
dd if=/tmp/123/tz.mbn of=/dev/sdc7
dd if=/tmp/123/splash480p.img of=/dev/sdc13
dd if=/tmp/123/splash1080p.img of=/dev/sdc15
dd if=/tmp/123/emmc_appsboot.mbn of=/dev/sdc9
dd if=/tmp/123/splash720p.img of=/dev/sdc14
dd if=/tmp/123/NON-HLOS.bin of=/dev/sdc3
dd if=/tmp/123/rpm.mbn of=/dev/sdc8
dd if=/tmp/123/recovery-stock-51.1.3.0.img of=/dev/sdc11
sync
sync
sync

6. If dd's & sync executed without errors, unplug USB cable from computer, power off and power on Fire TV.

[MENTION=3991724]rbox[/MENTION] if i wrong somewhere, please correct me
[Fire TV Android Development] cd2022:
AWSOME! Will give it a go as soon as I get home. Many thanks.
[Fire TV Android Development] Kramar111:
Please wait while rbox or anybody more experienced than me look at my "guide"
[Fire TV Android Development] rbox:
That seems correct.
[Fire TV Android Development] nhumber:
How did you make out? We still have no way to get the newest recovery onto the box that i can see.. what we need is an image of it.. but as of right now, thats not possible until someone roots the newest stock firmware... or merges the new recovery changes into the old recovery, but that probably wont work since i think boot will fail since its not signed. so for now we are all ( the ones who bricked with amazons newest update) stuck on 51.4.1.1. pm disable sticks through the whole update/brick/unbrick, and xposed works as it should. so it could be worse i guess.. at least we have root which enables xposed and external drive support and what not. good enough for me for now, ill be grabbing another box next trip to the USA so if its still old stock ill put together my files for running Fedora on the FireTV and start working on trying to get xbmc to work flawlessly with DD, DTS and refresh rate support..

Thanks again to rbox for the fix instructions.!!
[Fire TV Android Development] cd2022:
It's a daunting task for me as I'm not quite familiar with Linux, I need to install it on a stand alone PC so as not to confuse myself with all mounted volumes from the FireTV box. I've got the tools and instructions, thanks to Kramar111!
[Fire TV Android Development] PuntoG:
Nuttin but love...

I don't know how you find it within you to give this community so much love. I for one, have sent some love back your way in the form of a small donation. :highfive:

Thanks rbox dude for all you do. It is deeply appreciated. Without you, the Amazon Fire TV would not be something I and many others have grown to love.
[Fire TV Android Development] rbox:
Thanks to you and everyone else who has donated. It started out as a "well, I can do this, so why not?" and then after everyone loved it, I just decided to keep doing it.
[Fire TV Android Development] nhumber:
good to hear, if it makes it easier.. just download the live CD version of fedora, login as root to make it even easier. plug usb key with files needed into PC. copy to any folder, unplug that usb key. open a terminal and run ls -l /dev/sd* , you'll get a list of all the partitions. then plug the fireTV into the PC and rerun ls -l /dev/sd* and youll see all 20 of the fireTV partitions, so theres no way to mess it up. whole process only took 5 minutes tops. kramar111 instructions work perfect.
[Fire TV Android Development] cd2022:
I connected the usb key and fireTV thru a hub but I can't see the list after the command as expected, some firetv partitions mounted as a volume with a long string of hexa-dec id.
[Fire TV Android Development] nhumber:
yes if you look in file manager or a file browser you will see a few of the partitions show up in there.. but thats ok what does terminal return when you run ls -l /dev/sd* ?
[Fire TV Android Development] cd2022:
OK i had figure it out, the file system structures is not quite like in DOS or Windows environment. I need to learn to copy files from 1 drive to another before attempting the process.:o
[Fire TV Android Development] laidbackcloud:
Will this work for amazon fire tv stick?
[Fire TV Android Development] Y314K:
No.. Root is required. And this FW/PreRooted FirmWare is for Rooted FireTV's with CWM/Custom Recovery.
[Fire TV Android Development] laidbackcloud:
Thanks for reply.

So after its rooted, can I install google play services and would you have link for how to root and install play services?
[Fire TV Android Development] jmerrilljr2:
http://www.aftvnews.com/how-to-trick-google-play-store-into-allowing-all-apps/
[Fire TV Android Development] Y314K:
After root most FireTV guides would probably need just minor tweaks or probably nothing changed at all for them to work on the FireTV Sticks..

This would be the guide to follow for Google Play Services... But as you can see you need Root since you need SuperSU & some XPosed FrameWork, etc...

http://www.aftvnews.com/how-to-install-the-google-play-store-on-the-amazon-fire-tv/
[Fire TV Android Development] max0r4axor:
Play Store Issue

I have an issue where play store doesn't show any paid apps is there a work around for this.
[Fire TV Android Development] mroneeyedboh:
how can you delete the prerooted images that are on the SD card? I cant find them in Es File explorer.

I can see them here in CWM though...
[Fire TV Android Development] niphoet:
You should be able to delete them using adb shell.
[Fire TV Android Development] Divine_Madcat:
So, i hope nobody minds if i ask a stupid question, but i do have to ask (even us Mods do it from time to time. ;) )....

Over the weekend, i managed to get a rootable one, and have done my share of tweaking; rooted, on the latest "rootable" SW version, XBMC set as launcher, etc etc. Problem is, AFTER i get it set the way i like it, i find this thread, and see that with more work, i could be on the latest build. Thus, my question - is it worth tearing things down again, unlocking the bootloader, installing the CWM, etc, to be on the latest baseline? Admittedly, i am happy with the experience, but there is that nagging part of me that knows i am not using the latest and greatest, and wondering if there are fixes i am missing out on.

For you up to date users, in my shoes.. would you go through the hassle?
[Fire TV Android Development] mjbxx:
Definitely worth the hassle involved by being up to date on the prerooted firmware. AFTVnews has just put out a handy Starters Guide. Don't let the name mislead, as this guide actually acts as a checklist to see where you are and where you want to be.
[Fire TV Android Development] Divine_Madcat:
Well, i went through it last night, and it actually wasn't as bad as i thought. One annoying issue i DID get though - i wanted to start fresh on my XBMC install... what a nightmare. I had the advanced settings to point to the external thumbdrive (with stickmount). Despite reading the movies fine, it wouldn't load any of the artwork.

Finally got it, i think.. but blah. That said, overall the system feels snappier, so i think its a win all around.
[Fire TV Android Development] kywildcat:
File Manager>Profile Directory>Database> and delete textures13.db Reboot xbmc and your artwork should load

What method did you use to upgrade without losing root, and what version were you on before you upgraded? I'm wanting to upgrade from 51.1.1.0_user_511070220 to 51.1.4.0_user_514006420 to get screen mirroring
[Fire TV Android Development] Divine_Madcat:
I had done that a few times, but it never seemed to take. Not sure what i did different the last time, but i am happy so long as it stays working...

As for upgrading.. i actually just followed the guide suggested for me. I too started from 511070220; did the downgrade, then unlocks, cwm, upgrade, boot menu, and upgrade again, and everything otherwise went without a hitch. It doesn't wipe user data at all, so all the apps and what not were there.. On the downgrade, you had to rerun towelroot, but after that, you stayed rooted using the pre-rooted images..
[Fire TV Android Development] o-I-c:
Its Alive

Thanks to rbox and Kramar111 for there assistance in the rebirth of my sneaky Amazon brick.

After getting more familiar with how Linux does it stuff

It is finally Alive

Thank You Gents :cool:
[Fire TV Android Development] cd2022:
OK, first snag: When I run "unmount /dev/sdf" i get "bash: unmount : command not found"

I then did " # unmount /dev/sdf" nothing returns.

I then did " dd if=/path/to/boot.img of=/dev/sdf10" I get "Permission denied"

What am I missing?

I'm at root of /run/media/liveuser/(hexa-decimal string of ftv id/
[Fire TV Android Development] Animux:
The command is called umount and the hash sign should show you to execute the commands as root, but you should not enter it or your commands will be ignored.
[Fire TV Android Development] cd2022:
Woo hoo! I'm alive!

Many thanks to rbox, Kramar111 and people who lend a helping hand.

I had CWM and boot loader before the thing went south, now that it works I don't see CWM and the boot loader when I booted into recovery, is it possible to re-install them? The firmware show 51.1.4.1_514013920 but I don't know if it's stock or pre-rooted rom.
[Fire TV Android Development] darker_slayer:
Hi rbox

Thanks for all the great work on the Fire TV!

On your latest update that doesn't require the boot menu. No issues thus far, but only a short run of it

I hope you don't mind me asking, but why is the boot menu required for your pre-rooted stock images from the current one going forward? I can't see the menu being a feature I ever wanted, and really only a hindrance at this point
[Fire TV Android Development] rbox:
The #1 reason I created it was to guarantee people can always get to recovery. If for whatever reason your /system gets corrupt, it is very difficult/impossible to get back in to recovery. There has been a few people so far that have, albeit stupidly, wiped out /system and then were unable to get back to recovery. If you choose to skip that protection, you can just dd the included boot.img to the boot partition. Or just skip that all together everything should still function, but you'll be booting with an older kernel. I don't test that and can't guarantee that will work, which is why I at least recommend dd'ing the kernel.
[Fire TV Android Development] darker_slayer:
Thanks for the reply. So your saying skipping it altogether should work, but no guarantees as your not going to test your releases that way. I'm good with that, thanks again
[Fire TV Android Development] kraqh3d:
The unmount command is "umount" without the "n". Next you have to umount each partition individually. You cannot umount the disk. This means you need to do umount/dev/sdf1, umount /dev/sdf2, etc, for all the /dev/sdfX partitions. And last, you're likely getting that permission denied error because you need root access to use dd to write directly to a device like that. How you elevate yourself to root in live linux environments varies. You can try "su" from a shell to get into root. If it asks for a password, you're stuck. Sometimes there are options in the live environments menu to set the root password so that you can use su. I've also seen where there's a "root shell" option in the menu.

** a mod can delete this if you want. i was seeing that an old message as unread and i didnt notice the responses before replying.
[Fire TV Android Development] Divine_Madcat:
Pardon me for asking, but how is it a hinderance. Having just went through the process of updating myself, the boot menu add on wasn't that big of a deal. And aside from adding another 10 seconds or so to a boot, it is still an input free process (unless you want to get to recovery).

Why do i care? Having gone through the process myself, had i read something like this, it might have given me pause (and frankly, might have missed out). Call me picky, but misinformation that can effect new users kinda gets under my skin. But, if you have a genuine reason to think of it as a problem, i am very curious..
[Fire TV Android Development] darker_slayer:
It wouldn't be a big deal for me if I were the only one who was going to use it or if it was going to stay in my house

Giving it as a gift this year, it becomes a big deal in my opinion. In my previous post, I can't see how it would be misunderstood as me saying it was a hindrance for everyone, but in case there was any doubt let me restate: "It's really more of a hindrance for me, IMO"

One extra step in boot isn't a big deal, nor are the ten seconds. Having an extra step that can fail is a big deal for me when I'm gifting the device. Always times out and boots? Maybe so, but I don't think anyone would guarantee it always works. If in the strange obscure case the timeout failed then a USB keyboard is needed to get past the screen that was unnecessary to begin with for my usage

In all, thanks rbox and thanks aftvnews. Thanks for the reply clarifying the stock images don't have a hard requirement for the boot menu. I truly appreciate the info

Me stating my opinion is providing misinformation for new users . . . [emoji23]
[Fire TV Android Development] mjbxx:
Yes! Negativity can surely breed misinformation to new users who have a rooted Fire TV and think twice about moving forward. Not sure what the big deal is about having the extra 10 seconds that the rbox Boot Menu adds to starting the Fire TV. I will be gifting a few rooted Fire TV's knowing that all who receive will be covered at this time against Amazon's efforts to deny us of its benefits.
[Fire TV Android Development] darker_slayer:
This is getting pretty ludicrous. If me not liking something "breeds misinformation" to some poor lost user they probably didn't have the reading comprehension to have successfully rooted the device or found their way to xda-devs in the first place

To clarify, I don't see what the big deal is if I

don't

want to have the extra 10 seconds, potential to be stuck in a situation where the timeout didn't timeout, or to have my family call me to ask if I knew what a recovery or kernel was and whether anything was wrong since it looks fine, blah, blah. It shouldn't be a big deal at all. It's my opinion. I can't see a shred of misinformation, I can just see a bunch of xda fanboys whining about something utterly nonsensical
[Fire TV Android Development] mjbxx:
Wow! And because you "

don't

want to have the extra 10 seconds" that may be what leads to a bricked Fire TV. Then have at it. I'll leave you to your opinion.
[Fire TV Android Development] nhumber:
giving end users who know nothing an option to get to recovery isnt always a good idea either and not waiting the extra 10 seconds hasnt led to any bricked FireTVs, not using the boot menu and using the boot menu have the same risks for everyday users(Very very Little) it was mostly made for devs to make sure they werent screwed when TESTING new kernels/Roms. Really it seems theres about the exact amount of members here bricking now with the boot menu as there were members bricking before the boot menu... i guess if you cant follow instructions then your doomed to fail either way... sad... but true...
[Fire TV Android Development] bula1ca:
As simple as it: DO NOT USE IT!

In my opinion this is what will save your ass if anything goes wrong with programming down the road. If you do not like it do your own images and load them at your convenience or shut up before you piss off a guy that gives to all of us a lot of his spare time so we can all enjoy the new features released through a new firmware.
[Fire TV Android Development] nhumber:
wow, relax, Rbox isnt going to get upset about it, go back a page and he explains what to do to NOT USE it... good to hear you are using it tho and its giving you that peace of mind (i was using it also, but can see where not having it could be better for some)
[Fire TV Android Development] AFTVnews.com:
I completely agree. When I first saw that the boot menu would be required for rbox's future updates, for a second I considered writing an alternate guide on how to update without the boot menu. But then I realized it would make people see the boot menu as a negative thing ("If there's a guide to avoid it, then it must be bad, right?"), when in fact it's great and should be used by everyone.

Sure, people have and will continue to complain that there's a new (one-time) additional step to upgrading, but I think it's a great idea to require the boot menu. It's for their own good. The number of people that will be saved from bricking by it in the future will be far greater than the tiny amount who have issues installing it. It's important not to seed misinformation by discussing ways to avoid the boot menu.
[Fire TV Android Development] darker_slayer:
From your perspective I completely understand this. It would definitely be seen that way from the vantage point of a new person following along in your excellent guides

I've got to disagree here. Though I concede that it's great and there are obvious benefits to using it, I just disagree that it should be used by everyone / all the time / every scenario / etc

Okay you are the third person to say this, but the first one I've taken seriously. I can't for the life of me understand how my question was "seeding misinformation"

I'm not talking about a guide post describing how, not saying it's better/worse, nor recommending it . . . this was just one unimportant forum member (myself) at xda asking an important member (rbox) for details and him providing them for me
[Fire TV Android Development] AFTVnews.com:
Forgive me, I was not trying to imply that you were seeding misinformation. By my statement I meant that the AFTV community as a whole should be careful not to seed the idea that bypassing the boot menu requirement is a good idea. Saying it should be "used by everyone" was wrong on my part. I understand your reason for not wanting to use it and I think posing your question to rbox was perfectly fine.
[Fire TV Android Development] pbanj:
install went great, thanks.

is anyone having netflix issues?
[Fire TV Android Development] dc211:
Can someone remind me where I can check my firmware version? The FireTV seems a lot easier to brick then most devices and I just want to confirm what is currently installed. Is the Amazom rom being called the firmware?

I'm currently running CWM Recovery 6.0.5.1.4a & Pre-rooted 51.1.4.0_514006420.
[Fire TV Android Development] Divine_Madcat:
I haven't seen anything specifically, but it might help if you actually detail the problem you are seeing. ;)
[Fire TV Android Development] ahoslc:
How long before you think someones starts deving some real roms?
[Fire TV Android Development] roligov:
Well the custom recovery has only been out a day, so I would say give it a few weeks/months.