yashsingh1/xdaforums huggingface dataset:
[Fire TV General] rbox:
This is how to manually update. WARNING: If this makes your firetv explode or do other harm, I am not responsible. But it should be fine.

Place the update in /cache

Create a text file called command and place it in /cache/recovery. It is very important that this file be in UNIX format and not Windows format. If you don't know what that means, don't bother. The contents should be:

--update_package=FILENAME
--locale=en_US

FILENAME should be the full path to the file, so: /cache/bueller-ota-51.1.1.0_user_511069920-signed.bin Its also important to have a blank line at the end.
[Fire TV General] Resnoid:
Thanks! Any idea if this works for downgrading as well?
[Fire TV General] rbox:
I don't think downgrade will work because the updater-script checks the current build date vs the one in the update.
[Fire TV General] Jugstah:
aboot runs after sbl3 and checks the signature of the kernel (boot.img) before booting it.

The exploit in question would be in aboot, also known as lk.

This is one example of a recent aboot exploit, but I have no idea if this is the one jcase notified amazon of.

If the signature on the kernel hasn't changed, it may also be possible to revert to an exploitable aboot and still boot the newer kernel. This would not be advisable to try unless you have way to flash the correct aboot if your device does not boot (eg working/open recovery or fastboot)
[Fire TV General] zahir32:
This is very helpful. thank you.

It would be even more so if you would post a ready-made "command" file in Unix format for those of us who don't know how to handle Dos2Unix or other converters.

Edit: never mind, I converted my own text file in the end.

2nd Edit: Manual update using this method didn't work for me. I created the command file, converted it to UNiX, put it in cache/recovery, put the update zip in /cache, and rebooted into recovery. The system just hung there on the first "Amazon" loader screen and went nowhere..

Must have an error somewhere in my command file. (I notice that the "command" file gets deleted from its directory after even an unsuccessful attempt.)
[Fire TV General] jonesk1983:
can some one plz give instruction on how to manually update ATV
[Fire TV General] Luxferro:
From what does it get the current build date? If its an text file of some sort maybe we could edit it?
[Fire TV General] rbox:
I'm not quite sure. It doesn't look like the update has a new recovery in it, and the updater-script does a getprop, which would come from the recovery environment. And I don't see any scripts in the system image that would flash a new recovery either. So it might work.

But I do know on certain phones they have downgrade protections which could possibly lead to bricks and it'd be more risky on the firetv. So even if it accepts the update zip, I would recommend against trying it.
[Fire TV General] jonesk1983:
can someone plz give full instruction on how to update AFTV
[Fire TV General] Luxferro:
Yeah, I haven't seen a recovery in any of the OTA images. I dumped it with dd and took a peek inside, but I'm not too experienced with that stuff. I did notice it has an adb binary, but dunno if it actually runs.
[Fire TV General] rbox:
According to the init script adbd is only started when ro.debuggable=1, and it's set to 0.
[Fire TV General] Domunus:
I went ahead and did the update. As soon as I did "pm disable com.amazon.dcp" the update started. Rooted back just fine.

One thing i like about the update is it finally created a Prime Video menu.
[Fire TV General] Luxferro:
I tried changing it in the default.prop in the recovery, and dd'd it back, but it didn't boot the recovery. I guess the unpack/repack tools I used don't actually work correctly. But at least I was able to dd back the original recovery and that still works :)

know of any tools that actually work to decompile the recovery.img and then rebuild the image correctly?
[Fire TV General] rbox:
Not sure if the locked bootloader allows unsigned recovery images. But any android kernel unpack/pack script should do it. I've never tried repacking a kernel/recovery before.

EDIT: So I just tried repacking it myself and I got nothing.

EDIT2: Well that was interesting. If I unpack the recovery image and repack it without changing anything in the ramdisk, it works. So I'm going to have to experiment a little.

I am using bootimg_tools_7.8.13.zip and to repack I am using the command:

mkbootimg --kernel recovery/zImage --ramdisk recovery/ramdisk.cpio.gz --cmdline 'androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2' --base 0x80200000 --pagesize 2048 --ramdiskaddr 0x82200000 -o recovery-new.img

EDIT3: Ok, so if I use the original ramdisk that was unpacked, it works. If I try to repack the extracted ramdisk it fails. I did notice my repacked ramdisk was a lot bigger, so I'm going to try to figure out what the differnece is.
[Fire TV General] jljaries42@gmail.com:
Yesterday morning, I could not induce an update after a hard reboot and reboot into recovery.

When I got home last night, I clicked ' Check for System Update' and it stated to download.

Update installed - Rooted again - Everything is working fine.
[Fire TV General] krasny2k5:
Recovery only runs signed software from amazon, maybe the problem?

Nice to see that someone is working in bootloader!
[Fire TV General] kwiksi1ver:
Can someone confirm that this is actually updating the bootloader? If so I'm going to hold off on the update so I can hopefully keep my vulnerable bootloader so I can flash roms in the future.
[Fire TV General] {ParanoiA}:
Bootimg_tools is what I was using. I think the boot loader will not allow any custom kernels unless maybe you are able to do like [MENTION=2438823]Jugstah[/MENTION] mentioned in post 97 with the flaw in aboot. I'm guessing that may have just been fixed in this update? So you may need to be on 51.1.0.2.
[Fire TV General] mastermind278:
The goal shall be to be able to flash the update without the bootloader being upgraded. Concern however will be will the update work without the bootloader all attached to it. I will try to take a look into it tonight and see if I can figure something out.
[Fire TV General] krasny2k5:
Anyone knows how adapt a bootloader (TWRP o CWR) to new hardware?

Jcase isn´t working in that at all, as he stated here: http://xdaforums.com/showthread.php?t=2705149&page=5, but if anyone build a recovery to our hardware he will assist to make it working.
[Fire TV General] justin6162:
does anyone has the same problem? after update and rooted i constantly gets reboot by itself
[Fire TV General] nhumber:
you would have to contact the devs of TWRP and CWM to see what they say.
[Fire TV General] rbox:
They aren't bootloaders. They are recovery. I am playing around with it. I just need a USB cable.
[Fire TV General] {ParanoiA}:
You don't need to wait for anybody to build twrp. It's open source. You can build it yourself. http://xdaforums.com/showthread.php?t=1943625 The second post tells how to get official support. I don't think it's as easy as that tho. Some of the other Amazon devices don't even have it and they have been around longer than this device.
[Fire TV General] mastafunk:
There a custom cwm builder on their site iirc it just needs our mtd info.

http://builder.clockworkmod.com
[Fire TV General] Luxferro:
I tried that couple weeks ago. apparently they shut it down: http://jenkins.cyanogenmod.com/job/recovery-deprecated/
[Fire TV General] z31fanatic:
I am rooted and I enabled the OTA updates. As soon as I did, the FTV notified me there was an update available. I accepted it and it installed with no problem.
[Fire TV General] alwaysbless:
I did the same but my FTV was not able to find the update -_- I even tried again this morning and still nothing.
[Fire TV General] danknee:
I have four Fire TVs, two updated as soon as I enabled the update app a few days ago, one updated just now, and one is still waiting. I'm sure they just make it eligible for certain boxes as they roll it out.
[Fire TV General] {ParanoiA}:
I'm thinking that it may be possible to boot a modded kernel (at least with default.prop mods) if we could use that aboot exploit mentioned. Only puzzle piece left would be how to forge the signature on it.
[Fire TV General] retroben:
Has anyone found out if the update's bootloader was changed?

I really want to benefit from the performance boost.
[Fire TV General] evilracer123:
It has been done, see: https://github.com/freedreno/freedreno/wiki/FireTV
[Fire TV General] hhardheart:
New update rolling out. Same number (51.1.1.0) different user.
[Fire TV General] Luxferro:
What do you mean by different user?
[Fire TV General] krasny2k5:
bueller-ota-51.1.1.0_user_511069920-signed.bin

Did you take the update? do you know the new user number?

Thanks
[Fire TV General] Luxferro:
I haven't, I'm still on the 2nd OTA waiting for bootloader unlock.
[Fire TV General] hhardheart:
The new update is bueller-ota-51.1.1.0_user_511070220-signed.bin

I bit the bullet and updated. Everything went OK, had to re-root using tr_v3. No visible changes.
[Fire TV General] rbox:
So it's not a "new user". The "user" just signifies the type of build it is, vs for instance userdebug. That number is an internal version number. Hopefully someone like [MENTION=5894280]fireTVnews.com[/MENTION] can get the URL for it.
[Fire TV General] hhardheart:
:good:

Good to know. Indeed it would be good if we can get a copy.
[Fire TV General] retroben:
Waiting for bootloader access status.

Does anyone know what the changes are?
[Fire TV General] rbox:
So that was easier than I thought...

http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.1.0_user_511070220-signed.bin

As for what's been modified... it looks like the frameworks were touched and a small handful of apps were touched. Also it looks like trustzone and webcrypt images were changed. Other than that... it looks like the kernel was changed, although it seems like they are slacking if it's still got that root exploit.
[Fire TV General] fireTVnews.com:
Here is the new update url:

http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.1.0_user_511070220-signed.bin

EDIT: Whoops, saw your post and started capturing the update. Replied without refreshing the thread first and didn't see you already got it.
[Fire TV General] rbox:
It looks like I accidentally posted the wrong URL. Yours is right. I was testing things and I had modified the last digit and forgot about that and that's the URL i posted, haha.
[Fire TV General] fireTVnews.com:
Ah, I was wondering about that.

Also, I can confirm that rooting with towelroot still works with this update. You will lose root after updating, but can re-root just fine.
[Fire TV General] retroben:
Since bootloader unlocking is taking too damn long to be released for Fire TV,someone needs to copy all of the OTA builds and add them as downloads into a thread via favorite site (MediaFire,or another non-backstabbing site) and list the changes while also mentioning the status of bootloader unlcoking capablities.

Maybe just add them to a MediaFire directory page for quickly choosing the wanted version.

Hey JCase,Fire TV on XDA to JCase,when is the bootloader unlocker getting released?
[Fire TV General] nhumber:
maybe go and shoot him a 20$ over paypal for all the work he did and ask him for an status update personally, imo theres no need tho, he was pretty clear when he said, hes working on finishing it up and will release it shortly. seeing as theres nothing publicly available to flash anyways whats the rush?
[Fire TV General] Xavier000:
Another update, here we go again.... Did not block it,, hope wont loose the root!!![emoji35]
[Fire TV General] Xavier000:
Stickmount does not work any more!!!!!!![emoji35][emoji35][emoji35][emoji35][emoji35][emoji20][emoji20]
[Fire TV General] rbox:
They're just cranking these out. What is the build number?
[Fire TV General] Xavier000:
I knew something was wrong, everitime there is an updathe the aftv gets very slow
[Fire TV General] Xavier000:
Keeps getting faster!! But no root!![emoji20][emoji20][emoji20][emoji20]
[Fire TV General] Luxferro:
Post the full build number so we know if you're just talking about yesterdays OTA or not.
[Fire TV General] Xavier000:
http://www.amazon.com/gp/help/customer/display.html?ie=UTF8&nodeId=201497590
[Fire TV General] Xavier000:
51.1.1.0_user_511070220
[Fire TV General] Luxferro:
read back a page and you'll see it was yesterday's news. you made some of us think there was a new one today.
[Fire TV General] Xavier000:
Sorry,, y did not read, well .. How do y root it again???
[Fire TV General] finalheaven:
My god. I didn't even get the older 51.1.1.0 yet.... I'm still stuck on 51.1.0.2. I'm not even rooted. Just states that there are no updates yet...

However, I bought the fire tv less than a week ago...
[Fire TV General] t3ch42:
Download towelroot v3. I had a moment of panic because the version I had(v2) didn't work. Everything still works after that for root.
[Fire TV General] ugabuga:
So whats the word on this update, safe to install?
[Fire TV General] realtuxen:
Yeah it's safe..

Just re-root with towelroot v3, SU, and optionally busybox. Stickmount works fine to.

[MENTION=5903791]Xavier000[/MENTION]: Could you please test things a bit more instead of posting confusing post's every 2 minuttes. :)
[Fire TV General] finalheaven:
My Fire TV still states that there are no updates available for me. I'm still on 51.1.0.2. :confused:
[Fire TV General] jainanshal:
Isn't 51.1.0.2 the latest? That's what comes up on the Amazon website as the current one

http://www.amazon.com/gp/help/customer/display.html?ie=UTF8&nodeId=201497590
[Fire TV General] finalheaven:
That's what amazon is supposedly saying but a lot of people have already received two revisions of 51.1.1.0 and an update to the remote controller as well.

I have received none.
[Fire TV General] realtuxen:
I ended up manually updating to 51.1.1.0 after waiting a few days with no updates..

The latest update bueller-ota-51.1.1.0_user_511070220 came automatically to me as soon as I enabled com.amazon.dcp again.

Don't know if it can be of any help, but as said you can always update manually.

Btw. The remote control update also came automatically even though the above service was disabled. It came after the manual install of the first revision of 51.1.1.0
[Fire TV General] roustabout:
Mine yanked in the update over the weekend, Friday night I think.

I was able to reroot, no problem, got xposed working again.

Something I'm noticing: it seems that the Fire's having a harder time with syncing HDMI to the rest of my system after this update.

I have it connected to a dvd player which hands the output to the tv, and the handshake sometimes requires a power off of both devices before I can see the output from the fire again. I could direct connect to the TV, but greatly prefer to have volume control handled by the dvd player since I'm not ouputting sound through the TV speakers in any event.
[Fire TV General] swakdog:
Decided I wanted the update, so I unblocked updates in my router and when I checked for the update it was available (also the remote update). Both installed without issues and also rooted again without any issues. Thanks to those who post here,
[Fire TV General] losservatore:
The new firmware 51.1.1.0_user_511070220 works a lot better with xbmc than the previous firmware ,no stuttering on 1080p videos ,really smooth ,the only issue is that the audio is a little bit out of sync but you go to the audio offset settings set it till the audio is properly sync then set it as default for all videos and you are good to go.

By the way I'm using xbmc 13.1 Gotham.
[Fire TV General] pvtjoker42:
Anyone else confirm a similar performance increase for xbmc with latest updates? Debating if it's worth the time to update and roll the dice to see if it clears up some issues.
[Fire TV General] Xavier000:
Its faster!!!!
[Fire TV General] losservatore:
I know I'm new here ,the update was accidentally, I did a factory reset on my router and forgot to put the links to block the updates ,the next day I noticed that were some changes on the interface.I look for the firmware version and it did change ,I got freak out but I after I run xbmc I noticed an improvement in performance, you don't have to take my word but you will read more posts like this one.

Lito
[Fire TV General] skeptic_always:
The most important firmware update Amazon could push, IMHO, would be to enable USB storage.

Yes, I know I could root my box and side-load an apk for that, but I don't want to get caught up in a cat and mouse game over rooting devices. Plus the hassle of re-rooting after every update, potential to break things when USB support is firmware updated away, feel like I need to block future updates/improvements, etc.

Even if it means waiting for FireTV 2.0, I will not buy another FireTV until there is a legit method for enough storage for multiple large games. It's too bad really. I'd like to buy one for my kids for their movie/gaming TV, but after installing just a handful of games I had to uninstall one of the big ones just to get rid of the critically low on storage message that kept popping up.
[Fire TV General] rontonomo:
seriously in the time it took you to post this you could have rooted and be ready to go
[Fire TV General] ahoslc:
Root takes all of 30 seconds and like 2 clicks
[Fire TV General] skeptic_always:
It's not about rooting today, it's what may happen down the road. For all we know, next Tuesday a new firmware may roll out that greatly improves functionality while killing all known methods to root the device. Or, Amazon might not care and never close the existing root exploit. I may root my FireTV to let my kids install more games, but I stand by my decision not to buy another one until there is some official way to use significantly more storage.
[Fire TV General] losservatore:
For those that probably do not believe because I'm new with few posts ,I'm a avsforum member with almost 3,000 posts ,just look for the same username ,I can't post a link because I'm new here.

Have a great day...

Lito.
[Fire TV General] ~Craig~:
Ok so I am on the the firmware prior to this with elmerohueso launcher installed and updates blocked,

If I want to update do I just unblock the updates or should I also disable the custom xbmc launcher first?

I assume I would do this by disabling rbox's Xposed module?

Thanks
[Fire TV General] Spykez0129:
I don't even see the need to block any updates. I got 1 that unrooted me, just ran towel root again and I was back in the game.
[Fire TV General] mastafunk:
You will see the need when an update blocks towelroot from rooting..
[Fire TV General] dbdoshi:
LOL, good advice! I personally think that FTV will shut down root before they shut down the ability to side load, because thats the only way that legitimate developers can develop, debug and push them to FTV and Amazon is not about to kill that. XBMC is a much lesser threat than root file access in ES app or using USB storage with FTV.
[Fire TV General] ILLESTNOIZE:
New Fire TV update improves XBMC

Hi,

I was able to update to the "official" Amazon update and I do have to say I have noticed improvements with XBMC. Seems to be faster not laggy when scrolling and looking through content with Fire tv remote. Maybe the remote update goes very well with the official update of the Fire TV. As far as streaming I havent seen any buffering yet. However this is all dependent on your internet speed and the source of the content. 9 times out of 10 it is the source. I will continue to test and report back. Two things I did want to share with the community...

First...

You can install any APK from any source including Drop box and other android markets. You can even install from a website when surfing.

There is a tweak that needs to be performed with one of the "bueller" system apks with assistance from the Settings.apk that can be installed which would allow you to check the "unknown sources" box and with the above mentioned tweak you can install any apk.

Secondly...

I am still experiencing blank screen and green artifacts at top of the screen while in the middle of watching a movie. This typically happens after the first few minutes or so. I have noticed the majority of the time the source is Moviereel. Other than that Im using Elmers XBMC launcher and it works great!! Hoping for a better XBMC apk which would eliminate the blank screen and green artifacts (this does happen all the time with every link). I would also like one that allows us to stream large Remux/DTS HD audio files from UPNP. I belive VIDON who is a supporter of XBMC is working on such a XBMC apk Vidon XBMC for Fire tv. Coming soon also for Android TV. Be on the look out!
[Fire TV General] jae60up:
Aftv update

My amazon fire tv updated with out me knowing now I

No longer have root access and my xbmc is acting up movie stop in the middle

Or I'm just booted out to the amazon home screen. Anyone else having these problems or

Has a solution?
[Fire TV General] z111:
root

my root is still working, i just checked it right now. im on the last firmware that is root able and i have disabled update on the fire tv. since the modem block was not working for me.
[T-Mobile Samsung Galaxy S 5] ppgregory:
My wife is using the touchwiz email app with a pop server and ssl enabled. Data usage has been through the roof. Under Settings it shows that she's used 2gig in the last 20 days for email alone.

I called T-Mobile and they tried to convince me this was normal and tried to put me on an unlimited plan. Wouldn't acknowledge that 2gig + per month is excessive for email.

Anyone have any idea what might be going on?
[T-Mobile Samsung Galaxy S 5] jjlean:
Did she download big attachments? Also, maybe think about turning the retrieval interval down. My email. NEVER uses anything close to that.
[T-Mobile Samsung Galaxy S 5] ppgregory:
No big attachments. Its been consistently around 100mb give or take 20mb daily. She upgraded from the S3. I still have the phone and saw that she would use 65mb or so a month for email. Email settings on both are the same. Both set to check for email every 30minutes.

I just deleted the account and reinstalled to see if it makes a difference.
[T-Mobile Samsung Galaxy S 5] TheArtiszan:
That should fix it.

What usually causes the problem is something gets stuck sending a message and will eat through data very fast.
[General Questions and Answers] Tru Drew:
I was trying to post this on the Echoe rom thread but it wasn't letting for some reason, so I'll ask here.

I'm currently running PAC rom on my S4 M919 and have ran it for a while now and was looking to try something new. So I want some suggestions for a good Jelly Bean based ROM that has great customization. I also came across one that I think I'll try but I need to ask a few things about it.

I want to try Echoe but I don't know what version is Jelly Bean? I don't like KitKat because of the whole not being able to write to external SD card, which is omething I need for my apps to run. If their KitKat versions are able to write to ext storage then I'm fine. I also want to know what are the different versions of Echoe. I don't know if they're special in some way, if they're themed, or what. Also how great is Echoe; when it comes to customization, storage, speed/performance, etc.?

I haven't been able to find a comparable rom to PAC and I would stick with it, but I really want something that is update.
[Droid RAZR M Q&A, Help & Troubleshooting] armoir:
Can anyone point to a 3.4 kernel that works on the M?
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] berzerkus:
Good Evening,

I've got the Virgin Mobile Variant of the S5, which has the exact same model # as the Sprint and Boost (SM-G900P)

I see a lot of stuff on the development pages regarding this model, but I'm guessing it's mainly the Sprint variant. My question is, what do I need to be careful of when it comes to flashing roms/mods/etc based on the SM-G900P. I'm assuming the main difference is the APN's? I'm particularly interested in NE5, as I'm currently on ND2.

I appreciate any knowledge you can share, as I don't see a VM specific forum anywhere.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] emanuelrv:
NE5 TO BOOST VARIANT i received the update yesterday