yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] jellysweep:
I got myself into a pickle, and I'm not sure how to get out of it guys. Any advice, would be greatly appreciated!

My firetv2 was rooted with twrp 3.0.0-7 recovery on it. Recently, it started constantly restarting to the recovery screen (I now realize this was likely due to the box downloading an OTA without me knowing, and trying to install it, but getting blocked by TWRP). I decided I would upgrade to the newest prerooted rom, since i was on an older version, and see if it fixed the problem. I loaded 5.2.6.2_r1 to a USB stick, booted into recovery, and the firetv refuses to install the rom with error:

updater process ended with ERROR: 255

I wiped cache, dalvik, data, and tried again. Same error.

I tried 5.2.6.0_r1, same problem.

I tried a different USB stick - same problem.

I then did something brash and wiped system, restarted to recovery, and tried both roms / both USB sticks - still throwing the same error 255.

I'm lost. Can anyone give me some direction? Thanks much!
[Fire TV Android Development] jellysweep:
Anyone? Not sure if i should start a new thread instead of posting here. Thank you!
[Fire TV Android Development] santamanga:
Yes, i think you should have started a new thread. But what happens, if you just delete the ota.zip ?
[Fire TV Android Development] jellysweep:
Hmm. I wiped cache, dalvik, and data, before installing the rom. It gave me the same error 255. Shouldn’t the ota have been deleted when I wiped?
[Fire TV Android Development] chris-89:
Try to download the ROM again. Maybe the file is corrupt. And try to install it from mircoSD.
[Fire TV Android Development] santamanga:
I don't have my aftv2 anymore, so i can't recheck twrp for the options,, but maybe you flashed it via installer?

There is a post by rbox about this on page one of this thread. Maybe that will help. Also i don't remember where the update (i think it's update.zip?) are downloaded to. It might be in tmp.

https://xdaforums.com/fire-tv/devel...-prerooted-stock-images-t3309783/post65261630
[Fire TV Android Development] BRICK0044:
I have installed the 5.2.6.2_r1 and everything is great. I'm thinking about selling it to someone but, I want to make sure I'm resetting it right. Do I just go into twrp and do a factory reset and then disable updates again? Just don't want to ruin a good thing. Thanks for any help.

Or should I just reflash 5.2.6.2_r1 and disable updates?
[Fire TV Android Development] tekno4ever:
I unblocked updates via permissions on my wireless router and now I'm getting updates from Amazon about a new Fire OS update/download.... Is there something newer Like 5.2.6.3 being rolled out?
[Fire TV Android Development] BIOYAM:
Version 5.2.6.2 seems to be the latest for the 2nd Gen Box :

https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
[Fire TV Android Development] tekno4ever:
It's not.

http://www.aftvnews.com/fire-tv-upd...e-and-makes-amazon-channels-easier-to-access/
[Fire TV Android Development] BRICK0044:
I have done the same for DirecTV Now, but I can't get root back. Is there a way to root again without completely reinstalling everything?
[Fire TV Android Development] ryknow27:
To get root back, I just flash SuperSU in TWRP again and do whatever I need with it and don't open DirecTV Now again until hiding the binary again in HideMyRoot.
[Fire TV Android Development] BRICK0044:
What version of Supersu did you use?
[Fire TV Android Development] ryknow27:
Sorry for the late reply, I was at work. I use SuperSU-v2.79-201612051815.zip.:)
[Fire TV Android Development] tekno4ever:
Is there a place where I can download a 5.2.6.3 zip without root? AFTV keys offering updates and after installing and rebooting it never sticks just reverting back to 5.2.6.2.

Any help would be appreciated.
[Fire TV Android Development] BRICK0044:
Thank you
[Fire TV Android Development] tekno4ever:
Anyone know?
[Fire TV Android Development] AFTVnews.com:
I captured them and posted them here: http://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/
[Fire TV Android Development] rainman74:
What are the benefits of 5.2.6.3_r1 ?
[Fire TV Android Development] crs77:
Hello, I'm on the latest 5.2.6.3_r1, but bricked...only boots to TWRP and no matter what I flash... it's not working. cache mount error. What I am trying to do is completely restore stock without TWRP... can someone help, point me in the next step?
[Fire TV Android Development] BagiMT:
Try this:

Stuck in a loop?

If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.

If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:

Code:

mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache

https://xdaforums.com/fire-tv/development/firetv-2-recovery-t3309780

In my experience, manually wiping Cash in TWRP results in a corrupted Cache partition. The above command will re-create the partition and everything should work fine. It's even worse if you wipe the System partition as you won't get back to TWRP except with the unbrick images (don't ask me how I know!).
[Fire TV Android Development] crs77:
Hey Thanks, will try when I get in.

As far as 100% stock restore...

I tried enabling the stock recovery to install OTA but no luck, manage recovery adb with SU says Im on stock.
[Fire TV Android Development] BagiMT:
If you really want to go back to stock take a look at this:

http://www.aftvnews.com/how-to-unroot-a-fire-tv-2-and-switch-back-to-stock-updates-from-amazon/

But if there is something wrong with the partitions that won't work and if you get rid of TWRP unbricking will be much harder. I hope it's just a Cache issue.
[Fire TV Android Development] crs77:
Yea, I googled before and came to that link that sends you back here for the old pre rooted roms, but the links are no longer good. I'm looking to fix with your instructions then hopefully find a way to 100% stock.
[Fire TV Android Development] Jackie393:
:silly:
[Fire TV Android Development] Jackie393:
can you help me dump all partition on fire tv os?

please read more in here : https://xdaforums.com/fire-tv/development/ideal-downgrade-fire-tv-os-via-hardware-t3814911
[Fire TV Android Development] worm9110:
Thanks everyone for this thread and thanks rbox for tutorial and images. Updated AFT v1 and v2 boxes yesterday with no problems.
[Fire TV Android Development] s980845:
SuperSU won't launch for me. How do I access the root settings?
[Fire TV Android Development] j04nd03:
Does anyone else here experience random ejects of an inserted microSDXC card since the update to 5.2.6.3_r1? Whenever I reboot the Fire TV, the apps and other content stored on the card can be used for a short while, but after a few minutes there's an onscreen message that the card had been unexpectedly ejected (although it's still safely locked in its slot) and consequently the content isn't accessible any more. After a real reboot (via device settings or by removing and re-inserting the power cable) the card is recognized again, but a few minutes later it's ejected again.

Since both the problem as well as its "fix" are reproducible, I don't think it's a damaged SDXC slot on my Fire TV, but I'm not sure, so if anyone else experiences the same problem, it would be nice to know.
[Fire TV Android Development] ldeveraux:
Is there a tried and true method to replace the preinstalled SuperSU with one that will actually open the app? I have root, no problems there, just looking to gain more control. I tried deleting from /system/app then sideloading the apk, but no luck
[Fire TV Android Development] fcisco13:
Trying to unroot my device but the earlier images are no longer available, if someone has one available (5.0.4_r2) please be kind and share it.
[Fire TV Android Development] acm25:
Will there be a rooted 5.2.6.6 image?
[Fire TV Android Development] vladm7:
first someone needs to capture upgrade image from amazon. if you have link - please post.
[Fire TV Android Development] c3po_droid:
How do you capture it? Is there a how to somewhere of this procedure?
[Fire TV Android Development] vladm7:
https://xdaforums.com/fire-tv/development/how-to-capture-decrypt-ssl-traffic-t3515942
[Fire TV Android Development] c3po_droid:
Thanks! And who and how do I have to contact with the results? I don't think, that rbox is checking this thread very often. Is this the only way to capture the update?

How high is the risk of unrooting during this procedure? Or lets say: how to prevent unrooting?
[Fire TV Android Development] c3po_droid:
So... I tried to capture it a couple of minutes ago. Unfortunately my Fire TV 2 said that there are no updates available (currently installed the last prerooted 5.2.6.3_r1). Will try it in a week or so again.

Edit:

yep... was only able to capture the following build:

Fire OS 5.2.6.3 (606753920)

https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.0.6_user_606753920.bin

md5Sum=3771a434046ccfebd8420b716ca4ad3e

FileSize=544785745

I guess it's the same revision as the last prerooted 5.2.6.3_r1 here. Sorry not to be able to deliver the most recent version :/

The guide you referred to, became quite useless for whatever reason. I posted my experience with it in corresponding thread.
[Fire TV Android Development] chris-89:
Try to edit your build.prop and set build Nr to 606753920.

Maybe then it will download the newest build 617513120.
[Fire TV Android Development] c3po_droid:
Thanks!

that was the first thing I did. It simply won't find it. I even changed the build.prop to an older number (from 5.2.4.0 or so) and then it would download the above one (5.2.6.3). Apparently it's not my turn yet :/. I cannot find any infos about forcing it somehow.
[Fire TV Android Development] playingbball20:
The auto update is probably turned off. You need to re-engage it. This will work with adb...

adb shell

su

pm enable com.amazon.device.software.ota

exit

exit
[Fire TV Android Development] c3po_droid:
Unfortunately not. It is enabled (I enabled it always with adb and also cleared the com.amazon.device.software.ota cache with adb). As I said one post above: I downgraded to an older build and it still offered only the 5.2.6.3 (this also implies that autoupdate is enabled).

Tried it again yesterday... it is still saying that no new update is available. Perhaps amazon stopped the roll-out because of some bugs or so in the meantime and that is the reason that it doesn't get offered for me now.
[Fire TV Android Development] playingbball20:
Gotcha, well doesn't aftvnews usually have the images? Just thinking if you can't get it. I'm not sure if that is too much or not.
[Fire TV Android Development] c3po_droid:
Did you actually get the point of this thread and why people are trying to capture the images, which are not mentioned in the first post? :D

The Thing is: rbox didn't upload in the opening post the prerooted 5.2.6.6 image yet, because nobody has given him the image repectively the Amazon download URL of it so far. AFTVNews usually only mentions rbox's images as soon as he made and uploaded a prerooted rom and not the other way around ;).

So.... I am trying to capture the download link so that rbox can create and upload a 5.2.6.6 prerooted rom with it and if aftvnews wants to make a news out of it, he will then. But before nobody captures it, there will be no news.
[Fire TV Android Development] playingbball20:
Gotcha sorry, just got the end of the tread first. I'll see what I can do, I have 5 of them.
[Fire TV Android Development] c3po_droid:
Well just like I assumed in my second last post, Amazon apparently stopped the roll out because of issues and now started rolling out a new bugfix release 5.2.6.6 with a build value of 617513220:

http://www.aftvnews.com/amazon-fire-tvs-and-fire-tv-sticks-receiving-new-minor-software-update/

heres the diff binary download 5.2.6.3_r1 to the new 5.2.6.6:

mPackageName='com.amazon.sloane.android.os'

mPackageVersion=617513220,

mPackageVersionName='Fire OS 5.2.6.6 (617513220)',

mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/4ab2619082759242d9bf5d69e5864021/update-sloane_full_sloane-606753920-to-617513220.bin

mOobeForceInstall=false,

mManifestId=1781351152,

mMetadata={binaryType=diff,

cache_size=262144000,

max_stash_size=95862784,

md5Sum=256acfe9203f3caae1187ca6e03e6215},

mStartTime=1538083574202},

mRemoteFileSize=125507453,

And here we've got the the full firmware bin of the new

Fire OS 5.2.6.6 (617513220)

finally :

mPackageName='com.amazon.sloane.android.os',

mPackageVersion=617513220,

mPackageVersionName='Fire OS 5.2.6.6 (617513220)',

mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/426a9a28bf0375c5424f279d39a79158/update-kindle-full_sloane-36.6.1.7_user_617513220.bin

mOobeForceInstall=false,

mManifestId=613493814,

mMetadata={binaryType=full,

md5Sum=4ad80d49715021f755d6d648f642b087},

mStartTime=1538086042679},

mRemoteFileSize=567427246,

[MENTION=3991724]rbox[/MENTION]

I hope you can do something with it. I would be happy to see a new pre-rooted 5.2.6.6 rom for my Fire TV 4K :)
[Fire TV Android Development] rbox:
Thanks!

I updated the OP with 5.2.6.6
[Fire TV Android Development] c3po_droid:
[MENTION=3991724]rbox[/MENTION]

Man you are fast! Many, many thanks :)

Wish you a great weekend!
[Fire TV Android Development] chris-89:
First, thank you so much [MENTION=3991724]rbox[/MENTION] for your work :good:

[MENTION=7728312]c3po_droid[/MENTION] How do you capture the full update URL?

With this method https://xdaforums.com/fire-tv/development/how-to-capture-decrypt-ssl-traffic-t3515942

i only see the URL of the update image, Not the full image

or i overlook something.
[Fire TV Android Development] errut:
I tried to update with above prerooted ROM. Now i`m hung in a boot loop. i wiped cache already .

I need some help to get out of this mess. Thank you.

solved, second time wipe cache ok.
[Fire TV Android Development] c3po_droid:
Yep, had the same issue at first. At first I tried to modify

build.prop with an older build number, but that was unsuccessful... Though... I'm not sure whether the Update rom was still in cache, thus this could still be the way to go.

Only idea I came up with (which actually worked immediately), was to downgrade to 5.2.4.x and then it would show me the full rom URL. Don't know whether there is a better way :/

By the way. The linked method with xposed etc. does not work at all for me... I simply access the logcat through adb shell as soon as my firetv starts the download of the Update. And before it starts to install it, I pull the ethernet cable and clear the Cache in recovery afterwards :D
[Fire TV Android Development] vladm7:
updated, no issues.

thank you [MENTION=3991724]rbox[/MENTION] & [MENTION=7728312]c3po_droid[/MENTION].
[Fire TV Android Development] c3po_droid:
Figured out the best method to get full bin/rom right away without downgrading and so on:

boot into trwp and mount /system

connect via adbLink (e.g. Windows) to your FTV and start adb shell in it

Edit/change in /system/build.prob the existing "ro.build.version.number" to this old one: ro.build.version.number=574263120 (its the number from firmware 5.2.4.2)

reboot into system

An update should start downloading in preferences/info

run "logcat" in adb shell (or dump it to internal storage via "logcat -d > sdcard/logcat.txt")

save logcat output and search for: "mRemoteUri=https:"

That's the easiest and fastest way I know now. As I already suspected, my try doing this trick with build.prop didn't work yesterday, because the system had already the incremental update somewhere in cache, hence it did not look for the full rom from amazon servers anymore. Tried this now again and it worked right away. neat method.

I think that a too old "ro.build.version.number" (lets say 3 major updates before the current version) could lead to updates by stages in major updates.
[Fire TV Android Development] chris-89:
Thanks!

Good to know that the build.prop method also works :good:
[Fire TV Android Development] errut:
Question: do I have to block updates?
[Fire TV Android Development] chris-89:
When you use the "custom software version numbers" method, you must redone this after every update.

But when you use "disable com.amazon.device.software.ota" method, then not i think.

I do both methods again after every update.

Is done quickly :good:
[Fire TV Android Development] errut:
It seems that both methods are not necessary anymore with 5.2.6.6 Both don`t work for me.
[Fire TV Android Development] c3po_droid:
How do you notice, that they don't work?

I mean: after reverting the block methods my firetv starts to download the Update immediately. I don't dare to let it install it, hence I'd risk to loose root.

How does this scenario look like on your fire tv?
[Fire TV Android Development] errut:
I understand the chapter in disabling ota,which With its latest post postulates IT.
[Fire TV Android Development] c3po_droid:
I do not understand your answer. What chapter are you referring to?
[Fire TV Android Development] errut:
https://xdaforums.com/fire-tv/general/disable-ota-fire-stick-t3667978/page6
[Fire TV Android Development] c3po_droid:
Okay... to my understanding your linked thread is about unrooted (stock) devices. We here are on rooted devices, hence the methods still work here.
[Fire TV Android Development] errut:
I tried disable com.amazon.device.software.ota but wrong statement.
[Fire TV Android Development] c3po_droid:
1. You need a rooted device

2. You need to type in "su" in adb shell to get super user rights

3. You type in "pm disable com.amazon.device.software.ota"

4. There will be a "success" message then.

5. You will see in your fire tv settings/info/update Menu that the update check fails.

Please post your "wrong" statement. How can someone help you, if you don't write the error message here?
[Fire TV Android Development] errut:
that`s what i get.
[Fire TV Android Development] chris-89:
Because you are not root.

After you type in "su", there must stand:

"root@sloane:"

And then you must type in the disable command.
[Fire TV Android Development] errut:
When i type su, on my tv-screen i am ask to grant permission root, which i did.

On settings/info/update : error could not updated.

The prerooted update was conducted with the download provided by AFTVhacks in the ES-Explorer, the provided script to stop updates in addition.

update: now i managed it
[Fire TV Android Development] cline2:
Updated 5.2.6.6. all good except it doesn't go sleep. Whenever I press one of buttonson remote control to let my tv change input to Amazon automatically but now it doesn't work anymore.
[Fire TV Android Development] mwahahaa:
I'm still on rooted 5.2.4.2 and everything works as I need it to, including firestarter as home page. I haven't been able to clearly figure what what exactly the advantages are of upgrading beyond this point as recent changes appear to be minimal in terms of performance and functioning. Can anyone provide me a good reason I might bother flashing one of the newer updates?
[Fire TV Android Development] c3po_droid:
Next captured full rom: Fire OS 5.2.6.7 (623529620)

Here we go with the next full firmware bin Fire OS 5.2.6.7 (623529620):

mPackageName='com.amazon.sloane.android.os',

mPackageVersion=623529620,

mPackageVersionName='Fire OS 5.2.6.7 (623529620)',

mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/a5f8e2b446529521e21cd38962ac3709/update-kindle-full_sloane-36.6.2.3_user_623529620.bin

mMetadata={binaryType=full,

md5Sum=73a6af37738a9d64a067c8e3c6b64013},

mRemoteFileSize=582898870,

[MENTION=3991724]rbox[/MENTION]

Perhaps you can find again some time to wrap this new rom into a prerooted image :)

My very best regards
[Fire TV Android Development] vladm7:
[MENTION=3991724]rbox[/MENTION] mind posting script that you use to create upgrade file? this way someone else can do that as well...
[Fire TV Android Development] rainman74:
Issues with firmware 5.2.6.6

Waking up from standby does not always work and results in a black screen. I suspect it might be a general problem.

[MENTION=3991724]rbox[/MENTION] Therefore I cannot recommend a firmware higher than 5.2.6.2.
[Fire TV Android Development] rbox:
I have noticed that as well. I wasn't quite sure what the problem was. Thought it was my home theater system acting up. I'll see if I can test the 5.2.6.7 tonight.
[Fire TV Android Development] harlekinrains:
[MENTION=3991724]rbox[/MENTION]: Thank you for the clarification.

Its the only app, I have seen, that has no "launch" prompt in Amazons App menu. Go figure... ;)
[Fire TV Android Development] rbox:
You also have that situation with the play store if you install it. It might have something to do with them being system apps.
[Fire TV Android Development] harlekinrains:
Hmm. Makes sense - in the roundabout and twisted Amazon way of closing down systems... ;)
[Fire TV Android Development] Aobeta:
I was on 5.0.4 r1 and upgraded to 5.0.5 r1 and the keyboards would not work no matter what I did. I would try unplugging the fire tv to reset, reboot from the menu, plugging in the keyboard while it was booting, etc. The keyboards would just not respond at all until the fire tv os was booted. What fixed it was flashing recovery v4 through adb. From there, I upgraded to 5.0.5 r3. Everything has been fine since then.
[Fire TV Android Development] elliwigy:
is there an easy guide to using mouse emulation?
[Fire TV Android Development] rbox:
adb connect, adb shell, type 'mouse', then read what it says to do.
[Fire TV Android Development] pilotbob3:
Had the USB keyboard issue too. Tried it about 5 times, and fifth time worked for me. I had to use a USB hub and add a mouse. Once TWRP did launch, the keyboard did not work, but the mouse did and was able to flash the ROM.
[Fire TV Android Development] elliwigy:
i keep getting a /system/bin/sh: mouse: not found
[Fire TV Android Development] rbox:
It's only for recovery...
[Fire TV Android Development] androidfux:
Thanks, a good hint was to power cycle the fireTV. When I unplug the fireTV and plug it back the keyboard is working fine and I can select to boot into recovery. But after the fireTV has booted and a reboot the keyboard isn't working again.

I flashed then 5.0.5_r3, without success. Same behaviour.
[Fire TV Android Development] elliwigy:
ahh.. last question lol, whats the command you use to reboot into twrp recovery? instead of adb reboot recovery?
[Fire TV Android Development] rbox:
Either type 'reboot' or just power cycle.
[Fire TV Android Development] elliwigy:
ahh ok lol.. just gotta be fast I assume lol
[Fire TV Android Development] bula1ca:
Never mind....
[Fire TV Android Development] rbox:
You can also touch a file /cache/bootmenu_recovery prior to rebooting and it will make the default option in the bootmenu to be recovery. Do note you will have to manually delete the file or else it will always default to recovery.

What "somethin stupid" did you do? Is recovery still working? The easiest thing is to just reinstall the prerooted rom.
[Fire TV Android Development] bula1ca:
I got it working again. I was playing with 5.0.5r3 and recovery v4. Can not get usb to respond with v4. I am back on 5.0.5r1 with recovery v3. Not sure why but will not work for me.
[Fire TV Android Development] elliwigy:
so just create a file /cache/bootmenu_recovery and reboot? nothing needs to be added to the file?
[Fire TV Android Development] rbox:
Nope. Just needs to exist.
[Fire TV Android Development] elliwigy:
ok so i tried that and now im unable to connect at all via adb and stuck on recovery screen lol..

i tried connecting at different times as well as ive tried unplugging/plugging in everything
[Fire TV Android Development] rbox:
So the screenshot is from extremely far away... but the IP address in the top left corner appears to say 0.0.0.0... It only works over ethernet. Can't really explain why the keyboard isn't working. It's just a standard USB keyboard? Starting with it unplugged and then plugging it in afterwards should definitely work.
[Fire TV Android Development] rbox:
Okay, well it seems 5.2.6.7 is broken garbage. The box would reset consistently after sitting on the home screen for a few minutes.