yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] pfhastie:
As above, I am now trying to running the "unbrick_firetv2" option - in order to do so I need to install the MTK65XX USB Drivers on a Windows 7 PC, but my FTV2 is not recognised. It seemed to register once, but starting searching Windows for updated software. I had to pull it out, but it no longer seems to register no matter what USB port I try. The USB port seems to be working otherwise as I am still able to use my USB keyboard to reach TWRP recovery.
[Fire TV Android Development] pfhastie:
Just to bring closure to this tale of woe, I was finally able to install the Sloane 5.2.4.2 update, but I was unable to do so using my existing 5.0.5 installation. I tried every variable I could possibly think of, but it wasn't having it. I had to install the 5.2.4.2 update over my existing installation, THEN run a factory reset via the TWRP wipe menu.

It'll take me a couple of weeks to get back to where I was apps & settings-wise, but at least I have Alexa working etc. I'll suppose I'll avoid updating in the future unless Amazon release some very hot-to-trot update (which seems unlikely).

Thanks for the psychic influence, and goodnight.
[Fire TV Android Development] Han-Droid:
For what it's worth...I had this nasty optimizing apps thing on my phone. I thought it was stuck but it took ages to come across “optimizing app 1 of 1“.

My solution was to use the shady Lucky Patcher!

“delete all ODEX files“ was my saviour! :)
[Fire TV Android Development] ubducted:
Hi there.

Im in desperate need of help. I am very new to my Fire Tv 2 and am afraid i have ruined it. I bought it with TWRP already installed and wanted to go back to just having the Fire Tv2 stock with no root and so I choose ti factory wipe through TWRP and i also tried to wipe cache dalvic and system with out really knowing what I was doing. Now im stuck with just the amazon logo and am still able to get into TWRP.

how do i just get back to a completely stock Fire TV2?

please help
[Fire TV Android Development] chris-89:
That's very good that you still be able to get into TWRP.

Follow this guide to get back stock fire TV 2:

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

BTW.: Why want you switch back to stock? I prefer the rooted one.
[Fire TV Android Development] ubducted:
Thank you for the reply.

The guide you directed me to says "Download pre-rooted ROM version 5.0.4_r2"

snd when i head over to download that ROM the first line in the download page says "WARNING: DO NOT FLASH 5.0.5.1 OR EARLIER IF YOU STARTED WITH VERSION 5.2.1.0 OR LATER"

I have tried to flash 2 different ROMS 5.2.4.2_r2 and 5.2.1.0_r1 and the TWRP says it installs but when I reboot it just flashes the white Amazon logo twice then loads to TWRP.

should I follow the guide and try and flash 5.0.4_r2?

Thanks for your help

---------- Post added at 03:22 AM ---------- Previous post was at 02:35 AM ----------

EDIT

after i try and flash the 5.2.1.0 rooted r1.zip file i get the following.

Installing zip file '/usb/sloane-5.2.1.0-rooted_ri.zip'

checking for MD5 file...

skipping MD5 check no MD5 file found

copying system image...

installing recovery...

installing superSU...

copying firmware and kernel...

All done!

script succeeded: results was [ALL Done!]

updating partition details...

failed to mount '/data' (invalid argument

...done

thanks for your help
[Fire TV Android Development] chris-89:
Okay don't follow the guide and don't flash 5.0.4_r2!

Your data partition is corrupted.

In TWRP choose Wipe-> Advanced Wipe -> Choose data ->

then go to "resize or repair filesystem" -> and there "repair filesystem".

The next step depends on you.

1. If you want root ( What I prefer and suggested) then flash the latest pre-rooted ROM from rbox.

2. If you want a stock fire TV 2 then flash the 5.2.1.0-rooted r1.

Then when you have access to the fire OS connect with ADB.

Type in "su". Then type in "manage_recovery".

When your stock recovery is disabled, it will look like this:

Checking current stock recovery status… NOT STOCK

Checking for reason… DISABLED

Stock recovery is currently disabled,

Would you like to enable it?

Type ‘yes’ to enable it, anything else to quit

When you type yes you will get back the stock recovery.

Then you you can search in fire OS for updates and install these. Now you are on stock.

I DIDN'T TRY STEP 2, BUT IT MIGHT WORK.

SO DO IT AT YOUR OWN RISK.

I hope I could help :good:
[Fire TV Android Development] XDA_h3n:
[MENTION=3991724]rbox[/MENTION]

Hi there, update whenever you are ready ;)

Here is the update url for 5.2.6.0 for the Fire TV 2

This is from the UK, I don't know if this does include the voice search update...

Fire OS 5.2.6.0 (587444320) - Full system image
[Fire TV Android Development] XDA_h3n:
After flashing this on my Fire TV, there is only the live channel update and the changed ad banner with screen magnification.

I believe there is no voice search in this firmware, for at least the UK region.
[Fire TV Android Development] Han-Droid:
now... I'm the third guy who'd like to know this.

i am still on 5.0.5. since I did not come across a "GO" for the latest ROM allowing the old blocking techniques.

is it possible to put a block in the pre-rooted images?

i think that is better for the majority of users. and since it is rooted the users can revert to the updateable settings if they want to..... :)
[Fire TV Android Development] XDA_h3n:
There is no need to implement such changes to the build.prop as when the update does get downloaded, it won't flash via the custom recovery.

Why?

Firstly, the update files received via OTA are .bin; when these are changed to .zip these are flashable in TWRP (Do NOT try without flashing Xposed and some sort of SuperSU flashable zips).

Secondly, when it tries to install the update, it tries to reboot to recovery, which is not possible as the boot menu has replaced this scheme, meaning you would have to physically have a keyboard to press the right arrow key, which the general OS cannot do, therefore it timeouts and goes back to the normal os stating it has failed.

This is useful for me personally to grab update files, however, for the general rooted user, you can block them with your higher version build.prop modification, or via your router in url filtering or even disable the package that performs the ota.

I believe this is true as I did once have an update tried to install overnight on an older rbox pre-rooted release and it simply failed when I woke up in the morning to check the device settings.

Yep, if you read the OP:

The stock recovery is disabled, so it cannot flash the OTA files, unless you've used the command mentioned to enable stock recovery and disable the custom recovery. The custom recovery does not flash the .bin files (I assume; as it couldn't find them neither install them) and it requires for you to physically enter the recovery with the keyboard.

This is the precaution in case it does install if you forgot to block the updates with some form of modification.
[Fire TV Android Development] Han-Droid:
Thank you very much for clarifying this :good:
[Fire TV Android Development] yazyazoo:
Installed this last night. This morning my FTV was in TWRP. I assume my Amazon update block at the router isn't working? Is there a new method of blocking updates?
[Fire TV Android Development] XDA_h3n:
Um that's strange, mine just usually reboots as normal and then I wake up finding it has failed in the software update settings menu...

If you are using the router blocking method, Asus-Wrt Merlin did not block https for me; some third party router firmwares such as DD-Wrt does block https for some reason.

Your router may not be blocking the OTA server (as it may only be blocking http requests and not https), there was a change somewhere in Fire OS 5 where the OTA server is receiving obfuscated https links.

You can manually change the build.prop following the guide on aftvnews.com, you still need to be rooted though, check the software update menu and check the install date and if there is any details about the update failing. If it has failed, you are still on the same firmware and are rooted.

Starting with 5.0.5.1_r1, there was a change to the custom TWRP recovery to disable flashing Amazon updates. If you were before this version, you may have had problems with this...
[Fire TV Android Development] Rexapu:
Pre-rooted

Are we going to see a pre-rooted version of Fire OS 5.2.6.0 (587444320) any soon?
[Fire TV Android Development] fcisco13:
Relax bro, no rush, let the man do his thing when he can, when he want. Everything is working fine, enjoy.
[Fire TV Android Development] BIOYAM:
I have always used the above suggested guide on AftvNews.com, by utilizing the "ES File Explorer Method" and have never had any issues (as of this posting!) ..... Just an FYI to all concerned.

Also [MENTION=4266035]XDA_h3n[/MENTION], thanks for the clarification of "if blocking is necessary" that you posted prior to this..... much appreciated.:good:
[Fire TV Android Development] rbox:
I updated the OP with 5.2.6.0.
[Fire TV Android Development] DanteXXL:
Thanks mate!

Forgive me if it's been answered before but: Can it be dirty flashed on top of the previous version?
[Fire TV Android Development] XDA_h3n:
Yes you can ;); that's how Amazon does it :D

I bricked my box a few days ago (the unbrick image isn't working), so whatever you do:

DO NOT WIPE THE SYSTEM PARTITION. (and possibly the cache partition).
[Fire TV Android Development] BIOYAM:
Thanks for the heads up..... and it sucks that you bricked your box.

One question though, if you or [MENTION=3991724]rbox[/MENTION] could chime in, I'd appreciate it ......

My V2 box is running the prior release (5.2.4.2_r2). I installed Xposed and did the mod that [MENTION=1449438]Y314K[/MENTION] posted : "FireStarter/AppStarter Boot & Key Mapping thru XPosed Edge Pro".

Did any of you folks do that mod and do a dirty flash update to v5.2.6.0_r1 successfully?

Thanks in advance for your help.
[Fire TV Android Development] XDA_h3n:
Yeah I did before I bricked the box.

Don't worry I'll be upgrading to the newer fire TV as they have given me a 15% discount voluntarily. I might even move onto the shield but looks cheaper to get another fire tv
[Fire TV Android Development] BIOYAM:
Excellent, thanks for the confirmation. :good:

Nice..... I'm crossing my fingers for you that root comes soon :fingers-crossed:

Yep, the shield is the ultimate box but comes along with a hefty price-tag. Even though unless you are going to be using the shield for gaming, I would guess that video/audio experience is pretty much gonna be the same.
[Fire TV Android Development] chris-89:
Thank you for the update [MENTION=3991724]rbox[/MENTION] !!!

I have a problem after i installed the rom.

In the section "My apps & games" the kodi icon is broken.

So i removed kodi and the "broken Icon" is still there.

I installed kodi again and still the same.

Then i tried to change the order in the app drawer (I moved kodi to the second position), so normally now in the "my apps & games" section the order must change too. But nothing happens. So it's not a kodi related bug. Its a bug in the "my apps & games" section.

I also tried to wipe dalvik/cache and reinstall the rom. The bug is still there.

Does anybody have the same problem and solved it or does anybody got an idee how can i fix it?

Attached there are some screenshots of the problem.
[Fire TV Android Development] XDA_h3n:
This happened to one app for me before.

A simple deregister and register of the Amazon account may fix it.
[Fire TV Android Development] chris-89:
Thanks that fixed it :good:
[Fire TV Android Development] rodalpho:
I recently flashed my FTV2 to 5.2.6.0 and made the mistake of wiping cache/dalvik, causing a bootloop. Needless to say, DON'T wipe cache/dalvik on the FTV!

Anyway, the fix is to go to a shell in TWRP and run

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

These instructions were in an old Rbox recovery thread but not in this newest one. That's where I got it from. Hope this helps someone else!

https://xdaforums.com/fire-tv/development/firetv-2-recovery-t3309780
[Fire TV Android Development] Lochy19:
I tried to use the google play after update but just show a black screen for few seconds and then back to the launcher, I already tried to reinstall it using the guide that works in the previous version (5.2.4.0), but the problem persist, someone else have this problem? thanks in advanced.
[Fire TV Android Development] playingbball20:
If it is what I think it is, lol. Download the newest version of the files:

com.google.android.gsf.login_7.1.2-25_minAPI23(nodpi)

com.google.android.gms_11.9.43_(240-174880994)-11943240_minAPI21(arm64-v8a,armeabi-v7a)(nodpi)

com.android.vending_8.4.19.V-all_0_FP_175058788-80841900_minAPI14(armeabi-v7a)(240,320,480dpi)

These are the ones I installed on the fire tablet, so I would imagine these would work... You might need a diff dpi though. Those are the latest apks
[Fire TV Android Development] tekno4ever:
Anyone else getting a new OS update popping up on AFTV2?
[Fire TV Android Development] Opa_Apo:
First of all: thank you for your work on those images rbox :)

Now to the question. I downloaded the newest image (5.2.6.0_r1) and the corresponding checksum. After the download was complete I generated the checksum on my computer and compared with the original. They were the same but after coping it on the fire tv, TWRP throws an md5 error and stops. It does not matter if i copy it on usb-stick and then use ES File Explorer or Total Commander or if I use adb push. In all cases TWRP reports wrong checksum. Does anybody has a suggestion?
[Fire TV Android Development] BIOYAM:
I'm not sure what is happening, but here is a suggestion:

Copy the file using your computer to a USB stick or SD Card.... do a MD5 checksum. If they match, stick your media into your Fire TV2 and install using TWRP, DIRECTLY FROM THAT MEDIA... (no need to copy a second time)..... Remember that you will need a USB hub to use the thumb drive simultaneously with a keyboard, but if you use an SD card, then you are set).

Hope this helps!

---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------

I'm not getting that message, but I am using these blocking instruction from ATVnews (I actually used Method 5 using ES File Explorer within Fire OS :

http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/

Also, there is a recent thread (Dec 2017), on how to do the same using a similar method here:

https://xdaforums.com/fire-tv/general/fire-stick2-run-avoiding-otas-youtube-t3718556
[Fire TV Android Development] Opa_Apo:
Thank you for your help BIOYAM. Unfortunately your method gave me the same error but I found the problem. The md5 file here has just the checksum inside, while TWRP expects the checksum and the name of the file afterwards, so the correct sloane-5.2.6.0-rooted_r1.zip.md5 file looks like this:

84eedbb2e9fd4b57679747ecb8fae797 sloane-5.2.6.0-rooted_r1.zip

From there everything worked like a charm. Thanks again :)
[Fire TV Android Development] BIOYAM:
Excellent...... glad you figured it out.
[Fire TV Android Development] Han-Droid:
Didn't someone say blocking is not needed if twrp is installed? Update would fail.

No twrp means that blocking is required, right?
[Fire TV Android Development] BIOYAM:
Because of the way TWRP requires a manual update intervention, it cannot update the firmware automatically. However, you will still get an "update required" message within Android. Blocking the actual update using the above procedure, blocks the update path to Amazon creating a second level of protection.......... Also, in the procedure is a change that will make the machine not download the update even if it does detects it, by setting a Custom Software Version Number.
[Fire TV Android Development] Han-Droid:
Thanks for clarifying this. So, basically I'm safe but with additional procedures it's "more elegant"
[Fire TV Android Development] tekno4ever:
After getting OS update notifications constantly on 5.2.6.0 my fire 2 box started randomly rebooting after declining said update numerous times for a few weeks. I finally installed the 5.2.6.1 update, rebooted confirmed new OS version & then 12 hours later it reverts to 5.2.6.0 automagically while requesting that I update to 5.2.6.1. frustrating it is. Especially when watching something and it randomly reboots.
[Fire TV Android Development] santamanga:
If you get update notifications, why don´t either disable updates and their search ivia #su #pm disable com.amazon.device.software.ota

and delete the update package you have already downloaded?

or: edit your build.prop to a ro.build.number as high as 999 999 998 - which I guess, should save you from A LOT of future updates?
[Fire TV Android Development] black7:
Anyone having problems with HBO Go on 5.2.6.0_r1? App launches fine, I can register my account, I can browse but when playing any video I get an error. I don't even see the "HBO" intro video at all. I've factory reset my box, re-installed 5.2.6.0_r1, reinstalled the app, but still no go. Any help would be appreciated. TIA!
[Fire TV Android Development] d3adpool:
I'm having the same issue with HBO go. Showtime anytime won't play videos either. Hopefully rbox releases a preroot soon.
[Fire TV Android Development] ryknow27:
rbox, thank you for the update and thank you for all of your hard work and dedication to all of us Fire TV users!:D

---------- Post added at 02:09 PM ---------- Previous post was at 01:52 PM ----------

I can't exactly remember if this is the only thing I did when I had that issue but if you don't already have it, try using "Hide My Root". I was having the same HBO Go issue as well as DirecTV Now not working. I did a fresh install of the rom, installed the apps I wanted, including Hide My Root, and then before starting DirecTV Now or HBO Go, I opened Hide My Root and then clicked "Hide SU Binary" and then logged into the apps and they worked.

Hope it helps.:fingers-crossed:
[Fire TV Android Development] BIOYAM:
[MENTION=3991724]rbox[/MENTION],

Thank you, Gracias, Merci, Grazie, Danke sehr !!!!!

:D
[Fire TV Android Development] d3adpool:
It must've been something else you did. I tried hide my root 4 and not only did it not work, but I lost root as well. Un hide su binary wouldn't work so I had to reinstall the prerooted rom. Thanks for trying to help tho.
[Fire TV Android Development] ryknow27:
OK, I think I remember what I had to do to get HBO Go working now. The fix I mentioned earlier was only for DirecTV Now. For HBO Go, I'm 99% sure I had to use an older version of the apk and sideload it and turn off automatic updates for all apps. I don't remember which version it was but I do have two different versions downloaded on my PC right now, "9.2.0.4" and "9.1.0.11". Maybe it was one of them??
[Fire TV Android Development] d3adpool:
Thanks. I installed 9.1.0.11 android tv version and that works great!
[Fire TV Android Development] ryknow27:
Sweet!:highfive: Glad it worked for you!
[Fire TV Android Development] d3adpool:
Yes, now I'm having the same issue with showtime anytime :mad:
[Fire TV Android Development] ryknow27:
Ah well, not sure about that one. Sorry. Is it doing the same thing HBO Go was doing?
[Fire TV Android Development] d3adpool:
pretty much, it gives an error message on any video or stream played. It's not a big deal tho. Thanks again for your help.:good:
[Fire TV Android Development] errut:
Rooted AFTV 2 : i just tried to update to 5.2.6.2 prerooted. Installed it with TRWP, wipe dalvik cache,which stuck at formatting cache. Pulled Power and ATFV is now in Bootloop. Error Message "could not mount cache".

I still can enter TRWP Recovery. My Question: is recovery possible without loosing Root? Or should i apply a different method. Please help.
[Fire TV Android Development] chris-89:
Longer ago i made the same mistake. It doesn't stuck at formatting. It takes a very very very long time. Trust me.

Now you must repair the filesystem in TWRP.

Wipe-> Advanced Wipe-> select cache-> then click "Repair or Change File System"->then click "Repair File Sytem"

Then you can wipe dalvik and cache again. But wait. It really takes a long time.
[Fire TV Android Development] cline2:
I have Fire TV 2 rooted with 5.2.1.0. Can I use pre-rooted 5.2.6.2.r1 to update my Fire TV 2?
[Fire TV Android Development] ryknow27:
I don't see why not. Every time there is a new update, I do it with no problems.:)
[Fire TV Android Development] errut:
[MENTION=1481552]chris-99[/MENTION]

Thanks for your support, but it is still not working: it keeps telling cache could not be mounted (invalid argument), could not repaired, error 8
[Fire TV Android Development] chris-89:
Then try that way:

Wipe-> Advanced Wipe-> select cache-> then click "Repair or Change File System"->then click "Change File System"->ext4
[Fire TV Android Development] errut:
I Wenz back Go the previous Version and Applied above Procedere and it was successfull.

thank you very much.
[Fire TV Android Development] cline2:
So I download 5.2.6.2_r1.zip and flash it via TWRP?

Is update still blocked??

Thanks.
[Fire TV Android Development] ryknow27:
That is how I did it. I'm not sure if the automatic updates stay blocked or not. I usually just run this code, "pm disable com.amazon.device.software.ota" via ADB after every update just to be certain.
[Fire TV Android Development] tekno4ever:
It's not blocked by default... You must manually do it via ADB or in your home wireless router via the Amazon Fire TV News website in the "how to" section
[Fire TV Android Development] cline2:
I already blocked it via terminal.

su

pm diable com.amazon.device.software.ota

like ryknow27 said. It worked
[Fire TV Android Development] cline2:
Curious is it possible to flash SuperSU 2.82 on it??
[Fire TV Android Development] cline2:
Never mind I flashed 2.82 sr5 and it works. No more notification.
[Fire TV Android Development] Lochy19:
Someone has tested the google apps (play store, etc) in the [5.2.6.2_r1] image? I tested in the previous one, but not works :(
[Fire TV Android Development] acm25:
So does anyone know if HBO Go works properly with the new 5.2.6.2 image? I saw a few pages ago that some people were having problems with it on 5.2.6.0.

I'm still on 5.2.4.2 which specifically had a fix for HBO Go. I'd like to update but not if there's an issue.
[Fire TV Android Development] jaydee 77:
Is Magisk working instead of SuperSU as root solution. I'm wondering because of the locked bootloader.
[Fire TV Android Development] acm25:
I went ahead and updated to 5.2.6.2. No issues with the latest version of HBO GO.
[Fire TV Android Development] Bracket-:
Does root actually work for anyone on 5.2.6.2_r1? I did a clean install (factory reset + format all except /system in twrp) and attempting to use something such as mount in adb shell after su results in permission denied. Might attempt downgrading when I have time again.

edit: I'm an idiot and forgot that you're required to grant su access through the fire tv.
[Fire TV Android Development] Seattleweather:
once Firetv 2 is rooted and TWRP is installed, can I uninstall KingRoot? and just keep SuperSU?
[Fire TV Android Development] vladm7:
[MENTION=7828313]Seattleweather[/MENTION] - yes
[Fire TV Android Development] Warrior1988:
Anyway of using /proc/self/exe to exploit working root?