New firmware update for aftv!!

Search This thread

Xavier000

Senior Member
Jun 14, 2014
71
2
Stickmount does not work any more!!!!!!![emoji35][emoji35][emoji35][emoji35][emoji35][emoji20][emoji20]


Sent from my iPhone using Tapatalk
 

Xavier000

Senior Member
Jun 14, 2014
71
2
I knew something was wrong, everitime there is an updathe the aftv gets very slow


Sent from my iPhone using Tapatalk
 

Xavier000

Senior Member
Jun 14, 2014
71
2
Keeps getting faster!! But no root!![emoji20][emoji20][emoji20][emoji20]


Sent from my iPhone using Tapatalk
 

finalheaven

Member
Aug 17, 2008
10
0
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...
 
Last edited:

trongthuan0311

Senior Member
Sep 28, 2010
118
13
I used to block Ota throught Method 1 and now it is unblocked. Today i just check update, but i get a massage said : update error
My device in 51.1.1.0_user_511069920, used to root, factory reset after try a root and block Ota
Im wondering if someone help me
 

realtuxen

Senior Member
Jun 17, 2014
209
90
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
 
Last edited:

roustabout

Senior Member
Feb 12, 2011
825
212
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Got it! I've been pumping my Fire TV traffic through Wireshark AND dumping logcat in real time all morning.

    Software Update URL is: http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.1.0_user_511069920-signed.bin

    The file gets downloaded directly to /cache, so you could try putting it there and restarting to see if that triggers it to install.
    3
    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?

    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:

    Code:
    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.
    2
    Mine updated. Here's the new stuff I notice.

    A Prime Video tab has been added above movies. Sections include

    recently added prime tv
    recently added prime movies
    recommended prime tv
    recommended prime movies
    hbo on prime instant video
    prime member exclusives
    top tv on prime
    top movies on prime
    kids tv on prime
    prime tv genres
    prime movie genres

    Freetime has been added below video library. You have the ability to hide it if you're not interested.

    Music has been added above photos. Gives you access to everything in your Cloud Player. Voice search works. Doesn't include Prime Music content. Every section has a shuffle all songs feature.

    Settings. Display And Sounds has been moved to it's own section.
    Parental Controls has a 'create a freetime profile' thing added.
    Amazon Appstore settings has been added under Applications. You can turn on or off Automatic Updates and In-App Purchases
    Quiet time finally has an explanation 'Turn on to hide all application notifications'

    And that seems to be it :good:
    2
    do we know if amazon updated the AFTV bootloader?

    I only saw in this thread that root is possible in the new update, but not a single word about bootloader. We know that there is a exploit out there to unlock AFTV bootloader, so i think that until we have confirmation that amazon didn't patch recovery i suggest not update the box...
    2
    Got it! I've been pumping my Fire TV traffic through Wireshark AND dumping logcat in real time all morning.

    Software Update URL is: http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.1.0_user_511069920-signed.bin

    The file gets downloaded directly to /cache, so you could try putting it there and restarting to see if that triggers it to install.

    I think the best way to try to manually update it would be to put the download in /cache/ then adb reboot recovery. The recovery only seems to look for an update file at /cache, so that will probably manually update it.

    edit: I'm not going to try it just yet, since I'm not sure if I want to update just yet. But I may try this with the older OTA and see if it allows us to flash back to older builds as well.
    edit2: I didn't work for me with the first OTA (seeing if I could downgrade). recovery said update was not successful. One thing to note, if you chmod 777 cache, upon next reboot it will be reset back to stock permissions.