yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] imtiajmeah:
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://xdaforums.com/showthread.php?t=2796067?
[Fire TV Android Development] rbox:
As the post says... the prerooted images are only for use with my recovery. So yes, you have to downgrade and install it.
[Fire TV Android Development] zahir32:
Read Again

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.
[Fire TV Android Development] mjbxx:
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.
[Fire TV Android Development] Zetup-EXE:
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 :)
[Fire TV Android Development] rbox:
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.
[Fire TV Android Development] krasny2k5:
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!
[Fire TV Android Development] AFTVnews.com:
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.
[Fire TV Android Development] mastermind278:
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.

root@android:/ # pm list packages -d
pm list packages -d
package:com.amazon.dcp
root@android:/ #
[Fire TV Android Development] nhumber:
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.
[Fire TV Android Development] collindv:
I am wondering the same thing.
[Fire TV Android Development] Y314K:
Great.. All 3 options.. Unlock Bootloader/Install Recovery/Install Firmware are under the "ROOT" menu above on adbFire...
[Fire TV Android Development] DEREKTROTTER:
yes thanks i saw that

so no need to push the firmware zip manually first? does adbfire do it?
[Fire TV Android Development] Y314K:
I only cache install CWM's (That means installing directly from app instead of sideloading first). And both apps can auto do it. When dealing with FW I have always done a manual sideload of the FW to the /SDCard/Download folder (Can take a few minutes to finish). Then I use the app to boot in to CWM (On adbFire it is under File/Reboot Recovery). And manually do the install zip from CWM. That way I can make sure there are no cache problems while installing the new FW. You do have to delete the the FW zip from /SDCard/Download afterwards to clear that space (around 400Mbs). Both apps can do this thru cache (Not sure if the folks that had problems where doing the manual guides) but since I kept reading some folks had problems when using the cache to install FW I never tried it... I think with the way I've been doing it I don't have to worry of cramming the cache area with the big FW file... I might start doing the CWM updates this way too...
[Fire TV Android Development] DEREKTROTTER:
first hiccup, trying to push the firmware. Its been stuck like this 10 minutes not sure if its transferring very slow or what

connected over wifi
[Fire TV Android Development] Y314K:
Only done the sideload/push on AFTV Utility. And it can take a good deal of time... Not sure how adbFire will let you know when it's done.. But be patient. On AFTV Utility there is a little blinking input line while it uploads...
[Fire TV Android Development] DEREKTROTTER:
could do with a better way to sideload the firmware rom.

Ive unlocked bootloader + installed the latest CWM which boots up fine.

The rom i transferred said action aborted when i went to install it, guessing it didnt transfer properly.

attempting again, cant believe how slow this is

any way to see its transfer speed? not sure if very slow or crashed

been doing this for over 40 minutes, gets to the end then starts again.

so slow
[Fire TV Android Development] DEREKTROTTER:
success!!

> bootloader UNLOCKED

> latest CWM installed

> latest pre-rooted rom installed.

Everything working fine so far, can now access my amazon UK prime content.

Next thing is to get XBMC set up, not sure which version to go for. Probably SPMC as it can be used as default launcher.

How do you actually shutdown the fireTV using the menu or remote? Isnt there a way?
[Fire TV Android Development] Y314K:
Never had that problems with the AFTV Utility. FW usually takes about 2-4 minutes to fully load & it's always been fully uploaded. adbFire does have a SSH server option that can speed uploading a lot...

http://xdaforums.com/fire-tv/development/busydrop-1-0-ssh-busybox-fire-tv-t2910548 / http://www.jocala.com/busydrop.html

I think the SSH server is already part of the current adbFire. Under Root you can see the Install SSH option... It might be required that you instal the adbFire version of BusyBox. Which means you need to uninstall any prior busybox you have already install at time of root first...

FireTV is made to never be shutdown. It just goes to sleep after 15 minutes. The only way to turn it off is to unplug the power. That is just the way it was build... Now that you are rooted there are different ways like a launcher or some XBMC wallpapers or SPMC settings that can help with that. But be careful. Read the latest posts in those options thread. Since some can fight with others when both are trying to do the same thing. But you should be able to get the FireTV to sleep when you want it...
[Fire TV Android Development] mcsephoenix:
Sorry if this has been asked and answered but I have asked it several times without a reply... If install a ROM will I have to then reinstall everything else I currently have on my FireTv? Will I lose all my apps and all my xbmc settings? I am currently rooted running the original FireTv version and I am happy with my settings. I would love to have screen mirroring though so I am tempted to bite the bullet. I know I can backup my xbmc settings so i am not overly concerned about that.
[Fire TV Android Development] collindv:
No. If you don't manually wipe anything everything will still be there. Just make sure to do a backup in cwm just in case if emergency.
[Fire TV Android Development] retroben:
AN UNLOCKED BOOTLOADER?!!!

Where is the AOSP,AOKP,or CyanongenMod and other complete mods for Fire TV?!

Or is that option a ruse to trick me painfully?

Sorry,I got really obnoxius with that first part.
[Fire TV Android Development] rbox:
The same place they were before the unlock. This doesn't allow anything extra than was already possible with the last latest version of CWM.
[Fire TV Android Development] nhumber:
any issues running a previously patched kernel with the bootloader unlocked? (im assuming not since the amazon kernels have been patched by you and they seem to be ok)
[Fire TV Android Development] rbox:
The patching is irrelevant with the unlock.
[Fire TV Android Development] r3pwn:
With the release of the Lollipop sources, in combination with the partial bootloader unlock, someone could, if they wanted to, build a version of Android TV for the Fire TV. Correct me if I'm wrong.
[Fire TV Android Development] rbox:
Well it has nothing to do with the unlock. Recovery had all the ability before the unlock. Regardless... yes, in theory it is possible. In reality, it takes someone who knows a lot about porting cross versions. The Fire TV is made for 4.2. I easily compiled 4.2 from CAF sources and it was booting. I also tried the same for 4.4 CAF and failed miserably. But past that. If someone were to get Android 5.0 compiled and booting, mix in some of the proprietary apks from google for the Nexus Player, it would probably work.
[Fire TV Android Development] deepasadish:
even a 4.2 plain old android (with playstore!) will be much better than this fire tv gui.
[Fire TV Android Development] krasny2k5:
Hi there

First thank rbox for his amazing work!

Edit: fixed my problem by reading http://xdaforums.com/fire-tv/help/stuck-clockworkmod-recovery-mode-loop-t2924435

Thank you!
[Fire TV Android Development] Skater4599:
I've updated to this latest version with the fixed netflix, but I've had nothing but problems with new version of netflix. I've downgraded back to release before new netflix and am trying to get it working but now its giving the same ui-502 error. Is there anything in the latest update that would have caused this? Anyone else tried this and had any success getting back to older firmware/netflix?

Thanks in advance
[Fire TV Android Development] rbox:
When 51.1.4.0 first came out I used the old netflix just fine. Once I fixed Netflix, I've been using the new one pretty much every day and no problems.
[Fire TV Android Development] Skater4599:
I've had no such luck with the new netflix, it gives a lot of connection errors when loading and when starting a video, then if the video starts there is no sound 70% of the time, I have to reboot it then sound comes back.

Any suggestions? It seems like all partitions did not get formated or something either cause my cache and userdata was still there for xbmc and the screensaver is missing some photo's just shows an X instead of an image, not a big deal but just makes me think something else is up. I did a wipe data/factory reset in CWM
[Fire TV Android Development] Skater4599:
[MENTION=3991724]rbox[/MENTION] - What was the ultimate fix for Netflix on this new firmware? Did they end up changing the tz which netflix relies on? I ask cause I'm curious if there is anyway to undo it and roll back for now. I'm still having major issues with the one fire TV i updated, while the other two running the old netflix work just great still, I've tried everything I can think of, factory reset the thing many times in CWM, different firmware versions etc. Cannot get the old netflix working, for now its back on the latest update, but netflix is still a pretty consistent issue. It rarely plays any video, when it does audio will cut out randomly frequently, and can't start up often, I've even had it log me out and I had to re sign in with my netflix account, running diagnostics in the app it says everythings fine and gets to all 4 netflix servers etc.

If the tz or any other partitions were changed is there any way to undo it, at least for the time being or am I stuck on this firmware and hopefully another update fixes the issue?
[Fire TV Android Development] rbox:
I wound up just including the entire bootchain minus the bootloader in the latest update. If you want, you can just reflash them all from 51.1.0.2. You can take a look at my prerooted 51.1.3.0 vs 51.1.4.0 to see what extra images it flashed and just flash them all from 51.1.0.2.
[Fire TV Android Development] Skater4599:
Great I will try this when I get home!

Just to be clear, I could just flash the entire 5.1.1.0.2 and update incrementally to 5.1.1.3.0 and it should be back to stock/rooted? Or do I need to open up the updates and only flash the images that were changed/added in 5.1.1.4.0?

Sorry for my ignorance, I just dont want to ruin my rooted FTV :D hard to find rootable ones anymore
[Fire TV Android Development] rbox:
You can't flash stock images with CWM installed. You just need to flash the firmware images from 51.0.1.2. When I get home I can whip up an update.zip that will do it.
[Fire TV Android Development] Skater4599:
That would be amazing! Thanks so much for all you do rbox.

the Fire TV would be nowhere without all you do on it, you rock!
[Fire TV Android Development] Skater4599:
I tried this out last night myself, I'm sure I did something wrong, but I did find the missing/included diff images that you had added, and I took 5.1.1.3 as a base and added in the ones you added taken from 5.1.1.0 stock, However I'm not sure it flashed them, I put them in the zip but I have no experince creating a CWM flashable zip so I probably missed a step or 10 lol. It flashed but it was no different than your stock rooted 5.1.1.3, even same netflix error.
[Fire TV Android Development] rbox:
I sent you a PM with a link for the CWM zip...
[Fire TV Android Development] Skater4599:
Got it, I can't thank you enough rbox. I'll flash it first thing tonight when I get home, truly appreciated! :highfive:
[Fire TV Android Development] Skater4599:
Just wanted to chime in, I installed the zip you sent me and IT WORKS! Thanks again rbox, you rock!
[Fire TV Android Development] jarayn:
Same, no issues with netflix daily use.
[Fire TV Android Development] schneid:
Standing by for 51.1.4.1:

http://www.aftvnews.com/fire-tv-software-update-version-51-1-4-1-coming-soon/
[Fire TV Android Development] Skater4599:
This is what I've seen with others too, but for some reason my specific Fire TV with my setup/TV/connection, whatever it was seemed to be the perfect storm for the new netflix app, even though the interface was much better for whatever reason the old app just functions better. I would never really recommend rolling back unless you had the same problems but this way my wife will stop asking me to fix netflix/the fire TV in our front room lol.:good::good:
[Fire TV Android Development] rbox:
Just waiting on the update URL. I think all it brings is support for the controller app though.
[Fire TV Android Development] Y314K:
http://xdaforums.com/showpost.php?p=56889248&postcount=2
[Fire TV Android Development] rbox:
Yup, saw it. I'll make an update zip tonight.
[Fire TV Android Development] rbox:
I just updated the OP with 51.1.4.1. Please note, these updates now require FireTV Boot Menu.
[Fire TV Android Development] o-I-c:
As always excellent, Thanks rbox

In and working as per the intention of the product.:good:

Used the boot menu to load zip

Android man is drunk again belly on his head sorta.:cool:

Amazon loaded updates and reboot, had a yellow flashing

light I believe due to FiredTV launcher 1.10 taking over hit home

button, went to Amazon menus yellow light went blue all ok.

Netflix working well

Cheers
[Fire TV Android Development] nhumber:
i had a problem here, install went well, rebooted and everything was well.. started xposed to reinstall it, it installed and restarted but now im bricked.. i get nothing, no power light at all.. unless its possible that somehow on that power cycle the power adaptor gave out.. cant get my hands on another wall plug till tomorrow. has anyone reinstalled exposed on todays update?
[Fire TV Android Development] cd2022:
I use the CWM to flash instead of boot menu now my unit won't turn on, has no light. Please help!
[Fire TV Android Development] nhumber:
i would say anyone who has updated and installed it sucessfully should hold off on rebooting their device..
[Fire TV Android Development] cd2022:
The initial update was successful, only when I rebooted to recovery to re-install the usbmount that's when it bricked. No power light at all.
[Fire TV Android Development] nhumber:
right but i had the boot menu installed and functioning perfectly, so something in this update must have written something to the boot partition.. bricking me and well your bricked too it seems.. but i think that was to be expected since you didnt have the boot menu in place.
[Fire TV Android Development] rbox:
So it looks like the exact same thing happened to me. I did the reboot for xposed and it was just dead. I left it unplugged for a few minutes and still nothing. I'm going to pull the download.
[Fire TV Android Development] nhumber:
its possible it has nothing to do with xposed even so if anyone has flashed but hasnt restarted you should DD the bootmenu.img back to the boot partition before rebooting if possible.
[Fire TV Android Development] rbox:
Unfortunately it has nothing to do with the bootmenu. It's not even turning on. The first thing that happens is the Amazon logo prints, and that's from the bootloader.
[Fire TV Android Development] nhumber:
not a whole lot of options im taking it.
[Fire TV Android Development] o-I-c:
All working well.....went to update expose model power off and thats all folks

Now this will test, keep us informed

Does this mean pull a part and creative paper clip placement ?

No worries it happens

Cheers
[Fire TV Android Development] nhumber:
doubt ill be replacing this, ill put wires anywhere i gotta to get er going again :D for now i might replace it will a nexus player.. or get a box with linux support of out the box.
[Fire TV Android Development] rbox:
[MENTION=6102015]cd2022[/MENTION], did you have bootmenu installed? I was thinking it had something to do with a kernel update, but if you didn't have bootmenu, you would have still been running the old kernel.

Update: So it looks like it's not totally dead. It's in some kind of Qualcom recovery mode because when I plug it in to USB a whole crapload of things show up on my computer.
[Fire TV Android Development] cd2022:
Yes, I had the boot menu installed and unlocked, but when flashing I went to boot recovery by habit.
[Fire TV Android Development] rbox:
That's the only way to flash... bootmenu isn't for flashing. I can't explain it, but booting the OS must have tweaked something somewhere, and now the sbl is refusing to boot. They may have blown a fuse or something. It's showing up on USB for me and I can get access to the entire eMMC, so I just need to figure out what to do. I could probably flash the updated bootchain, but I'm betting the old bootloader won't work like that.
[Fire TV Android Development] o-I-c:
Something blown can always be fixed

Lets know, ideas, things to try.

Cheers
[Fire TV Android Development] Kramar111:
Do you need some help from newbee?

like testing or something else

View attachment USBViewAll_FireTV.txt
[Fire TV Android Development] mastafunk:
So i downloaded everything last night with the intent to do it this morning.. woke up and did it.. unit is running fine.. but i am scared to reboot.. should i just DD the boot.img back to boot partition? What is the safe thing to do here..

????
[Fire TV Android Development] nhumber:
same here, let us know how you make out rbox, and if you need anything or i can help, shoot me a pm.

---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------

no your unfortunately in the same boat.. do not reboot. its before the boot.img so theres nothing to do yet, wait for rbox to let u know if theres something you could try.. if he somehow figures out a fix you might have to brick but in the mean time might as well get some use out of it.
[Fire TV Android Development] mastafunk:
hmmm.. what about dd'ing an older /system and /boot

Im just worried i will have a power outage... anything i could potentially do now to avoid a possible permanent brick would be prudent.
[Fire TV Android Development] nhumber:
well a fix will probably involve something like this.. but its not that.. its the bootloader not loading.. but first i think it needs to known exactly what happened.. like rbox said maybe they blew a fuse or maybe they added something into the system that modified something on bootup, gotta be bootloader related.. im sure once the day gets going well get an answer.. a fix is another story. but im hopeful.
[Fire TV Android Development] mastafunk:
Mine sat at the updating screen a bit before it booted.. something was going on..
[Fire TV Android Development] cd2022:
Doesn't look like there was a fuse inside, according to this source:

https://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856

Output from power adapter is 6.22VDC
[Fire TV Android Development] nhumber:
ya its not that kind of fuse.
[Fire TV Android Development] mastafunk:
I think we are talking about an efuse not an actual fuse...
[Fire TV Android Development] rbox:
So I tried everything I could last night, updating the bootchain, reflashing old stuff. Nothing could wake it up. I'm going to have to consult with some people tonight to try to figure out what they did. The good part is it does actually turn on and boot into the quallcomm recovery mode, it's just figuring out how to fix it.
[Fire TV Android Development] mastafunk:
So dd'ing a stock recovery/boot did not help?

Assuming if something changed in the bl perhaps putting the newest recovery/boot would do it? It would leave us updated and unrootable but thats better then unusable.. (I really wish i had it plugged into a UPS, first power outage and im in trouble)
[Fire TV Android Development] rbox:
The problem is it's not even making it to the bootloader, let alone the boot image. The way the bootchain works on Qualcomm to my knowledge is there is a Primary Bootloader (pbl) in the processor. It then loads sbl1, which loads sbl2, which loads sbl3, which loads the application bootloader (which is the one can't update). In the middle somewhere it loads tz and rpm also. It's getting stuck either in pbl or one of the sbls, I'm not too sure. You know the application bootloader has loaded when you see the Amazon logo. When you turn it on, nothing happens on the TV output, but it comes alive on the USB port for the Qualcomm download mode.
[Fire TV Android Development] to0:
Don't go doing this without rbox's, or someone more familiar with the device than me's, blessing, but it may be worth a try to re-enable automatic updates and let it do the official upgrade.

The download mode with access to the eMMC is very interesting, however. If we were able to get into that mode manually, it could mean root access for everyone.
[Fire TV Android Development] mastafunk:
That wont work as our custom recovery wont do the official update..
[Fire TV Android Development] to0:
Good point, do we have a stock recovery.img anywhere? I like to think that I backed mine up prior to flashing CWM, but I'm not at home to check right now.
[Fire TV Android Development] mastafunk:
Doesnt matter cause when the box goes to reboot it won't..
[Fire TV Android Development] nhumber:
thanks Rbox
[Fire TV Android Development] mastafunk:
Heres a thought... could we backup a working (older rootable firmware) stock firetv using dd on all relevant partitions, then restore it using dd .. unless there is some tricky efuse checking that should let us boot as all partitions should pass any sort of non-hardware checking they are doing.
[Fire TV Android Development] rbox:
I've already tried reflashing all the partitions. The one thing I didn't try was flashing an updated application bootloader.
[Fire TV Android Development] mastafunk:
Im getting antsy and am probably gonna reboot this thing sooner then later... im trying to think of anything i could do differently that could help us identify a direction for our search since im in a different state then you guys.. If it was an efuse of some sort mine has not been thrown yet as i havnt rebooted, (unless it was thrown during that upgrade screen). Im thinking about dd'ing the updates boot.img to the boot partition, and instead of directly rebooting, doing a "reboot recovery" from the shell.. see if it will boot recovery in this odd state we are in...

Any ideas of things i could do different to help since im still booted and running..............