yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] hwmod:
Fire TV Stick Basic (tank) post 5.2.6.9 incremental updates

I can confirm that the 5.2.6.9 OTA update seems to be in "on-hold" state.

I downgraded my stick to 5.2.6.8 since a week ago and I haven't been able to update to 5.2.6.9 in this week.

Also of note the fact that it seems Amazon is going to start again with incremental updates instead of full package updates.

I notice that after the first-time update to 5.2.6.9 I have received 19 incremental updates (files in .apk format) which I carefully captured just in case.

Attached to this message I uploaded the complete set of the 19 files update grouped in 2 different sets (apk1 and apk2).

The first set was found in the /cache directory while the second set was captured from /sdcard/Android/data/com.amazon.device.software.ota/files/.

Here is the file list preview of contents found in the linked archive:

Length Date Time Name
--------- ---------- ----- ----
19689856 02-17-2019 14:06 apk1/15.17.3.1.0.DigitalMusicAndroid3P-fireOS-partner-release-signed.apk
76775507 02-17-2019 14:07 apk1/AlexaMobileAndroid-2.2.237036.0-prodPhoenix-armeabi-v7a-release-signed.apk
21624784 02-17-2019 14:07 apk1/ATVAndroidFOS5TabletClient-release-prodSigned_241062110.apk
26805735 02-17-2019 14:07 apk1/com.amazon.gallery-fireTablet-release-signed-536543210.apk
13155243 02-17-2019 14:07 apk1/FreeTimeApp-fireos-fireos-release-signed.apk
11480109 02-17-2019 14:07 apk1/MASClientPlatter-tabletFos5-release-signed111.apk
3333353 02-17-2019 14:07 apk1/MayDayApk-fireOs-release-user-signed.apk
11613292 02-17-2019 14:06 apk1/OOBE-armeabi-v7a-release-signed_3.apk
598325 02-17-2019 14:07 apk1/signed_Cloud9ContentService-release.apk
7772927 02-17-2019 14:07 apk1/signed_DadetAndroidClient-fireOS5-release.apk
49037037 02-17-2019 14:07 apk1/signed_KindleForAmazonTablet-fos-release-14.15.136_1224836010_1.3.203908.0.apk
3489261 02-17-2019 14:07 apk1/signed_KindleStoreAPKv2-app-tablet-fireOS5-release.apk
1281070 02-17-2019 14:07 apk1/signed_NIMH-release1.apk
9296991 02-17-2019 14:07 apk1/signed_UnifiedSearchGen7-release_701.apk
6445765 02-17-2019 14:14 apk2/AudibleFireTabletApp-release-signed-2060150110.apk
50597344 02-17-2019 14:14 apk2/com.amazon.cloud9.apk
6495028 02-17-2019 14:14 apk2/com.amazon.cloud9.kids.apk
8032262 02-17-2019 14:14 apk2/FireLauncher5-release.apk
22877139 02-17-2019 14:14 apk2/MShopAndroidPhoneApp-16.0.222504.0-firefly-release-releasesigned.apk
--------- -------
350401028 19 files

Download post_5.2.6.9_incremental_updates.zip for Fire TV Stick Basic (tank)

Have fun.

.:HWMOD:.
[Fire TV Android Development] rbox:
I don't know what the Basic Edition is. [MENTION=5957312]AFTVnews.com[/MENTION], do you know?
[Fire TV Android Development] k4y0z:
From what I understood, the basic-edition is the same hardware but comes without Alexa.
[Fire TV Android Development] rbox:
If it's the same hardware, then it's very likely you'd be able to flash a tank software build on it. But I wouldn't recommend trying that unless there was a stock amazon image you'd be able to flash back to incase something bad happens.
[Fire TV Android Development] 2WhlWzrd:
It also could be that the most notable change to the interface, the app pinning feature. Seems to viewed by a lot of users as an epic fail.

Maybe they are rethinking the change.
[Fire TV Android Development] AFTVnews.com:
Fire TV Stick Basic Edition is identical hardware to Fire TV Stick 2 "Tank". I see no reason why the tank ROM would not work on the Basic Edition stick.

The main issue is that Basic Edition Sticks have different system apps (or possibly just a flag set somewhere with the same system apps), such as Amazon Video, which are meant to be used by international Amazon accounts. If someone flashed a US rom on a Basic Edition stick, there is a chance they will no longer be able to access Amazon Video (and other default services/features) using their international Amazon account. They might not even be able to log into the device with an international Amazon account.

Worst case scenario, as I see it, is if you flash a US tank rom on a Fire TV Edition Stick (codenamed "Dozer", btw), you basically turned it into a US stick and need to now deal with the consequences of using US hardware abroad. I don't know what all of those consequences are.
[Fire TV Android Development] ing.mcp:
thats correct, the basic edition is the international stick so if you have lets say an amazon prime subscription from Mexico, and you use that amazon prime account on a us stick wile been in Mexico it wont work its ip restricted, so unless you are not using any amazon ip related subscriptions i don't recommend using the us rom , (the basic edition its easily recognizable by its smaller controller )
[Fire TV Android Development] MysticFTW:
[MENTION=3991724]rbox[/MENTION] so if I wipe system and then flash this rom and lose root can I just flash magisk to get root back or do I need to redo the unlock method again?
[Fire TV Android Development] rbox:
Just reflash magisk.
[Fire TV Android Development] MysticFTW:
Great thank you.
[Fire TV Android Development] hk73:
Because 5.2.7.3 can not be rooted with kingoroot as mentioned above...... Anyone tried 5.2.1.0 on tank 2? or i'll be the first one?
[Fire TV Android Development] Sus_i:
:D :laugh:

Yeah, you're the first one testing this:

The initial software version on (the early edition) Fire TV Stick 2 from the factory was 5.2.2.0 and isn't vulnerable to kingroot/kingoroot/all the other dirtycow sploits :rolleyes:

You know, this thread is about the prerooted ROM for tank! That is the topic.

It is not a spam thread and it isn't a thread about rooting fireOS in general.

And it isn't a thread to talk about porting xiaomi roms to the f*cking firestick. :rolleyes:
[Fire TV Android Development] hk73:
Dude idk y u acting like that when someone doesn't need ur guessing theory......... and u r frustrated like ... ?........My question is about prerooted rom & further elucidated why i need 5.2..1.0....kindly skim the thread with every post to clear your doubts about what others have discussed...... Also r u admin or moderator of thread?
[Fire TV Android Development] Sus_i:
Omg. This isn't a guessing theory, maybe look up in the net, then you see that there isn't and there wasn't a 5.2.1.0 rom for tank at all! :rolleyes:

No, I'm not a moderator, but it is really annoying, to see your ongoing spam of this thread with offtopic.
[Fire TV Android Development] hk73:
its curiosity - to ask & try!!!! u tried many things & might helped people with ur trials & success but does that mean you mock others on their questions & give names ongoing spam? What u r doing now is ongoing-spaming - trying to prove ur behavior......if u hv logical tried method to bypass enbale su from twrp on whaterver os for tank 2 then talk further otherwise don't guttter space, fritter time & impel others to do so.
[Fire TV Android Development] Sus_i:
No, the first stick called montoya is absolutely different to the tank device (Montoya = broadcom chip / tank = mediatek).

Seems you don't have any clue.

Your 10 last posts in this thread are offtopic.

5 posts about lineage ROM and 5 posts asking questions about old rooting tools, both is not covered in this thread.
[Fire TV Android Development] mrjuniork:
MOD REMARK:

Folks, I kindly ask you to stay on topic and stop this kind of communication. Let us not forget that we are here to help and support each other, This is not the right place for blowing off some steam. I'm sure you know of better ways to do so ;)

Here is a reminder, for what we all signed up for. Please read it again (or maybe even for the first time ;) )

So, once again, let's get back on topic!

[MENTION=8791681]hk73[/MENTION] Let me remind you, that there several other possibilities for getting answers to questions that might go in a different direction than what this thread was originally intended for (Q&A threads for example..), or you might as well start your own thread in order to accumulate some attention for your burning questions. And please, there is no reason for accentuating your posts in different colors. Especially the red one is usually indicating something else ;)

Thx for your cooperation.

Stay safe everyone and if there are any open questions, send me a PM :highfive:

Cheers,

mrjuniork (Forum Moderator)
[Fire TV Android Development] hk73:
Well i understand above about colors, but is it off on the tangent reagarding topic? Prerooted prior to the mentions roms will work or not if someone has tried can help sharing experience is off topic- Really ? Plus Am only one who ask extra kindly go through posts sir.....2) just because someone is knowledgeable means can mock using abusive brash language? Like "Sus_i" did is appropriate? & To impede him is inappropriate- right sir? ------knowledgeable or experienced members have biased advantage to mock new members despite trying something practically advicing theory and abuse rookie users post -------

For your info he even suggested someone utterly wrong info in other threads - i can share if you want.....!!!! I tried & tested & verified that he has given wrong info!!!!!

Sorry to "rbox" for using his space for these but have to apprise others about biased towards senior members!!!!!
[Fire TV Android Development] mrjuniork:
I'll try to be swift.

I didn't mention anything about off-topic, I wrote that "in case it might go in a different direction". As you can see I haven't deleted any posts, which would have been the case if there had been off-topic posts.

My biggest concern has been the form of communication that has developed between the two of you.

So stepped in, simple as that.

Please keep it civil and respectful. The first part of my post was directed to both.

For your info, we all at one point have shared wrong info in one way or another. That happens. No point in pointing fingers at someone.

Have a good one :good:
[Fire TV Android Development] SweenWolf:
Ok, I try to answer some of the questions that I remember you asking all over the forums in one post.

I might not remember them right but here i go.

Do not flash rom of two non similar devices, they may look identical but they aren't.

It doesn't matter if one is running 5.1.x.x or 5.2.x.x

Because basically they are basically android 5.

So these roms will not be identical and will help amazon to push updates to right devices.

About Tata Sky Binge, the popup you are getting, if some dev wants they can remove them easily, because that is basically an app popped up if you launch an app. And that thing is Running FireOS 5 so you cannot disable the app without root, but if you are root you can remove the overlay. And the thing also is only available here (India) and I don't think many devs are even thinking of buying device like that.

About the lineage part, (devs are not paid at xda, they do that as thair passion and when they get time)

Lineage is Open Source, Amazon is not.

Lineage are not supposed to be ported, they are supposed to be compiled. And without porper source code (Which amazon will never provide) there will be bugs and which will make it harder for devs to fix the bugs in the ROM.

And yes, LineageOS or Cyanogenmod is an operating system meant to be used on a mobile and not on TV, so it will be nice if you stop being pushy in that matter.

The reason why you shouldn't post anything unrelated to the topic in a post is because when someone has same problem like you they can search that topic in appropriate forum section and no one will search that problem in an unrelated thread posts. And also if the thread contains posts which aren't related to topics and they wanted to troubleshoot their problems then they will have hard time finding proper post about it.

So if you have any problems like that, create another thread with proper topic so other peeps will also get help from it.

Hope you understand.
[Fire TV Android Development] hk73:
= likewise ?
[Fire TV Android Development] Sus_i:
Hi there.

I don't like it to answer you again, but some of your statements needs to be corrected.

You asked a question about rooting fireOS version 5.2.1.0 via kingoroot and I answered two times that it isn't possible, as this OS version isn't aviable for 'tank' at all. As I said, this stick was released way later with the initial version 5.2.2.0. and if you lookup in the internet, you find the release notes.

If you don't like to get answers, maybe don't ask.

Like I said, my theory isn't a guessing one, it is a fact!

Never ever I had to impelling an user here.

I just answered your question. It isn't my fault, if my true answer is not in your opinion.

I've not commenced mocking and I don't used brash words to you.

I don't know for what kind of reason a moderator needs to stop me.

It was your kind of spelling, the offense words to me in your posts, which have been correct thru the moderator.

Please stop telling lies about me. I'm trying to help people and my thing isn't in making wrong advice to someone, certainly not cocky at all!

If you see something that needs to be corrected, let me know, I'll check and correct it asap if necessary.

In case you mean your posting here: https://xdaforums.com/showpost.php?p=83634161&postcount=24 then I can tell you that my advice worked flawlessly.

Here are some of your lineage questions:

Yes, these are only a few of your posts from this thread.

In my opinion offtopic, all of them. Sorry, that is my opinion, this isn't the lineage thread.

I can't think of how your goal, jailbreaking a 'tatasky binge branded' firestick and an 'illegal disabling of the given DRM's the tataskybinge app', could be related with the absolutely legal rom offered in this thread. Must be also offtopic, at best.

Anyway, Offcourse I've seen the two moderator comments, understand them and I'm fine with it.

I'm also fine with you in case you ignore my postings in the future, I'll doing the same with yours.

Thank you.
[Fire TV Android Development] mrjuniork:
[MENTION=5213625]Sus_i[/MENTION] [MENTION=8791681]hk73[/MENTION]

I think this should be enough now. I have also noticed on ongoing discussion in another thread.

You could take it up with PM so there is no more unnecessary thread cluttering happening. You both made your points.

Peace out :)

Cheers,

mrjuniork
[Fire TV Android Development] sjude68:
Yes they should peace out. This thread is gone long and for anyone searching for something they will have to go through it.

Can the admin delete the bad talk or unrelated discussion and make it clean.

I had a tough time when I was searching another thread for a solution and had to replies within replies - the quote/endquote part.
[Fire TV Android Development] mrjuniork:
No need for that, as posts have already been edited.

Deletion of posts happens for stronger reasons.

XDA is also a place of constructive discussions :good:

Of course, when searching a thread with 100+ posts it could be challenging to find a proper result when there is a lot of clutter, but that's not yet the case here :)
[Fire TV Android Development] Bertonumber1:
Wrong thread
[Fire TV Android Development] HoreaM:
Are there any tutorials on how to debloat 5.2.7.3_r1, but keeping Prime Video functionality? Thanks!
[Fire TV Android Development] Bertonumber1:
Yeah the top list on this thread here is what I used

https://xdaforums.com/fire-tv/general/disable-bloatware-2nd-gen-fire-tv-stick-t3674629

Read OP carefully

To keep prime don't disable the packages in attached photo mate.
[Fire TV Android Development] jerian01:
help please

did the exploit and installed tank 5.2.7.3 rooted and magisk 21.1. every thing proceeded but when i rebooted the stick nothing came up on the screen. It was supposed to show optimizing space. I tried five times same result. what am i doing wrong.? help please
[Fire TV Android Development] Sus_i:
5.2.7.3 may be a downgrade of your stick.

Until a new prerooted is out, you can try installing the stock 5.2.7.6 (rename the bin file to zip):

mPackageVersionName='Fire OS 5.2.7.6 (659654620)',
mRemoteUri=https://d1s31zyz7dcc2d.cloudfront.net/5fd8039db2a0db0bd9d25f03acc245c0/update-kindle-full_tank-288.6.5.9_user_659654620.bin
md5Sum=7a4bf3318e3e408581bc6cf4ea5a89f9}

After that flash magisk and wipe cache + dalvik.

In case your stick blackscreens again, wipe data.
[Fire TV Android Development] jerian01:
can you send me a link to the stock. i have been looking cant find it. thanks
[Fire TV Android Development] 0815hoffi:
https://d1s31zyz7dcc2d.cloudfront.net/5fd8039db2a0db0bd9d25f03acc245c0/update-kindle-full_tank-288.6.5.9_user_659654620.bin
[Fire TV Android Development] jerian01:
Thank you brother!
[Fire TV Android Development] 0815hoffi:
@Sus_i

Have you also the link to 5.2.7.7?
[Fire TV Android Development] Sus_i:
No, not jet. Isn't pushed for now, at least for my fireTVs ;)
[Fire TV Android Development] vprasinos:
It has been mentioned before but I cannot pair the remote after flashing. I unlocked through amonet, I flashed lineage os (remote working) and I decided to revert back to stock. So I flashed 5.2.7.7 (twrp wipe data, system, cache, dalvik) but could not pair. I then flashed 5.2.6.9 because of someone mentioning it here (again before flashing I cleared system, data, cache and dalvik) still nothing.

I have tried switching new batteries, I have tried holding the home button for 10 seconds or 20 seconds or more, I have tried to left cursor+menu for 12 seconds and then take out batteries and then reboot tank and home again, nothing.

Is there something else in the process I am missing? The remote works, in lineage I paired it successfully. Do I need to wipe something else apart from system, data, cache and dalvik?
[Fire TV Android Development] Marcin Kalecki:
Try this way of reseting remote controler:

Make sure fire tv stick is not plugged in. This is very important. Next press and hold for about 10 seconds three buttons from remote.

Left ring button + menu button (to the right from home button - one with three strips) + back button (left to the home button)

That should do it.

Tell us if it worked :)

BR
[Fire TV Android Development] vprasinos:
No it did not. I even took out the batteries after doing the combo motion on the remote as other info suggested. Gonna put lineage back, that was the last time the remote worked with the stick.
[Fire TV Android Development] Sus_i:
Sometimes flashing lineage f'cks up idme data.

Maybe do a quick check in TWRP: mount system, run adb shell and then idme print

Take a look if you can see your sticks serial and the BT + Wifi data, like MAC Address...
[Fire TV Android Development] Marcin Kalecki:
And stick was not plugged in to tv and was not connected do power supply?
[Fire TV Android Development] vprasinos:
Stick was plugged in to TV but not connected to power supply. Why should it not be plugged in to TV when performing the remote combos since the power of the stick was off - unplugged? What difference does it make?
[Fire TV Android Development] vprasinos:
Will check soon...
[Fire TV Android Development] Marcin Kalecki:
I have no idea why should it be unplugged but only complete unplugging worked in my case. I also have this issue with remote worked for me. But stick has to be unplugged from tv and power source. I was trying with stick connected to tv and it did not worked.
[Fire TV Android Development] vprasinos:
Sorry can't run the command "idme print" I get "idme not found". You probably mean "id me print" but then again I get "Usage: id [OPTIONS] [USER]" so wrong usage.
[Fire TV Android Development] 0815hoffi:
Boot twrp

adb shell "mount -o rw /system"

adb shell "idme print"

mantis: / # idme
usage: idme <ARGUMENTS>
help Print this help messages
name <value> set value by idme name
name clear clear the value by idme name
print Shows all existing values
print <name> get value by idme name
dump <file > dumps the idme data in the file
sanity <blbfile> perform sanity on blob file
copy sensorcal Copy sensor calibration data to / data
copy KB <partition> Copy KB data to KB partition
copy DKB <partition> Copy DKB data to DKB partition
mantis: / #
[Fire TV Android Development] vprasinos:
Here's my data

board_id: 0120001040000016

serial: xxxxxxxxxxxxxxx

mac_addr: 440049F3CB49

mac_sec: 8O14OWV3D2MRZ83DEC53

bt_mac_addr: F08173882F66

product_name: 0

productid: 0

productid2: 0

bootmode: 1

postmode: 0

bootcount: 268

manufacturing: PSN=P0714M0482963KAU

unlock_code:

sensorcal:

4800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

wifi_mfg: 0

bt_mfg: 0

KB:

4b 42 50 46 18 26 00 00 28 26

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

DKB:

4b 42 50 4f 88 0b 00 00 98 0b

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

device_type_id: A2LWARUGJLBYEW

dev_flags: 0

fos_flags: 0

usr_flags: 0

Also the remote works because I just paired it with my android tv. That means the remote is bluetooth discoverable. So something is going on with the stick
[Fire TV Android Development] 0815hoffi:
Maybe your remote needs a FW update to work with 5.2.7.7.

How to Update the Amazon Fire TV Voice Remote or Game Controller Software

Both the Amazon Fire TV Voice Remote and Game Controller are capable of receiving software updates. These updates come packaged inside the main Fire TV software update, meaning they are not downloaded separately.

www.aftvnews.com

and 5.2.6.9 is to old.

Try with 5.2.7.2 .

https://aftvhacks.de/downloads/rooting/fire-tv-stick-2/tank-5.2.7.2-rooted_r3.zip

Only a idea.

Because, i was not able to connect the FireTV Lite remote until 5.2.7.7 with Tank.
[Fire TV Android Development] vprasinos:
I just installed Lineage back and the remote can't pair still - it was working before when I instlled ...This is a different case it seems. But thanks for your input.

So you tell me that the tank's data is ok?

I just installed lineage back. The pairing still does not work. But before installing 5.2.7.7 I had lineage again and the pairing worked! So the events that took place were:

Had stock initial image and had blocked official updates.

Then unlocked, installed lineage and paired the remote.

Then tried to update masigk with the app instead I was left with a brick - stupid of me.

Re unlocked and installed 5.2.7.7 could not pair the remote

Wiped and installed 5.2.6.9 since I think that was the last firmware before lineage. Still no pairing

Wiped again and installed lineage back. Still not pairing. The most irritating thing is that I have an OTG cable and tried to operate the stick with an android remote I had and while I can operate it, the back button doesn't work and also when I connect it I get a message from lineage that "bluetooth service has stopped" and I need to press ok. If I don't connect the OTG cable I don't get the message.

What the heck is going on???

Thanks hoffi for trying to help..
[Fire TV Android Development] 0815hoffi:
Yes, I think IDME looks good.

Or what you think @Sus_i

Try to hold homebutton more than 1 minute to pair 🤷‍♂️
[Fire TV Android Development] Sus_i:
Yeah, looks good

@vprasinos Edit or delete your serial out of the idme print...
[Fire TV Android Development] Sus_i:
You're not alone, there are a few reports like this.

Pull the batterys out of the remote and let it alone for a while, over night or so.

Then put fresh batterys in and try to pair it again.

Press the button at least a minute, like hoffi said.
[Fire TV Android Development] vprasinos:
Yes but what I don't get is why my android tv could see the remote and pair with it in a second. So I don't think it's an issue with the remote.

Anyway I will try what you say although I've done it more or less (haven't tried with the batteries out overnight)
[Fire TV Android Development] Sus_i:
I know what you mean. ;)

Someone reported here, that he tried about 100 times to pair the remote but nothing, then he took it to a second fireTVstick and it paired within a second. The remote of the second fireTVstick paired also within seconds with his stick. It's weird...