yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] c3po_droid:
Wondering about your issues I also updated to the new 5.2.6.7 r2.

1. Being on the 5.2.6.6 I firstly tried whether Alexa is working (or has a general server problem) --> it is working... tested voice playback control and weather

2. I pushed rboxes 5.2.6.7 r2 onto my FTV2 and installed it

3. After finishing the insallation, there are as always two buttons: left=wipe dalvik and cache ; right=reboot system. I pressed as always "wipe dalvik and cache" and it took as always about 5 to 10 minutes.

4. I rebooted to system

5. verified that I was on build 623530020

6. Checked if alexa is working: Yep it does without any issues so far. Weather, playback control via voice. The Fire TV works kind of the same (good) way as before.

I have to mention that my FireTV 2 Box has the wifi-direct (proprietary) voice remote. Hence I cannot speak for your (perhaps) bluetooth voice remote.

Regarding bootloops and the other cache issues that you mentioned in the last weeks... Is it possible that you messed around with your system? Disabled apps/packages, installed eXposed or heavy/instable stuff like this? My system is kind of untouched... the only thing that I did on fire tv is:

1. Rooted and always installed rbox pre-rooted roms

2. made update blocking with build.prop and pm disable com.amazon.device.software.ota

3. I did nothing else like fiddling and searching for "suspicious" amazon apps and disabling them etc.

---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------

But you still can enter the twrp recovery?
[Fire TV Android Development] rainman74:
I guess it's the Xposed framework. Once that was enabled, Alex stopped working on this latest firmware. But this can also be a coincidence :confused:

Yes, of course!
[Fire TV Android Development] c3po_droid:
Funny thing is... when I first thought about capturing the amazon updates, I thought there is only the Xposed method and I couldn't even install Xposed (retrospectively I am happy about this). Here's my report about my unsuccessful attempt to install Xposed: https://xdaforums.com/showpost.php?p=77665017&postcount=4

It was completely incompatible to my FireTV, although others (many guides on the internet describe the same steps and success, but that was in the past) I have the impression that Amazon somewhen switched its Fire TV 2 Box system to arm64 bit kernel with 32bit libs, whereas it was arm64 bit kernel with 64bit libs before, and that is why xposed installation perhaps worked for people in the past. But that's just a guess.

Well... anyway... I think that xposed might be your issue indeed. Perhaps there is a way to revert the system somehow to a more clean state, like as if you have a stock system that you just rooted with rboxes method and installed recent pre-rooted roms. Like without any trace of xposed and so on.

At least: As I said... there is not even a slight issue here on 5.2.6.7. r2, that I encountered so far.
[Fire TV Android Development] TalNum:
Also thinking this is in regard to Xposed. After flashing the latest ROM I noticed I lost all Alexa functions too. Also looks as though the Xposed Installer app has now disappeared from the apps list? I can verify it is still installed but just not appearing anywhere within the Fire TV.
[Fire TV Android Development] c3po_droid:
Sounds not so good. I think I once attempted to wipe system partition as well. It is absolutely not recommended as far as I know, though if I recall it correctly - which means that I really did it some months ago because of pure stupidity - I installed the a new pre-rooted rom right after wiping system partition. As long as there is no reboot inbetween, it could work. At least it did for me, if I really did it. But I'm not quite sure if I really did this. My device is at least fully functioning, so perhaps I only thought about doing it haha.

What about wiping data? Shouldn't that delete Xposed and revert the device to Factory Defaults? There was an article at aftvnews how to reset the Fire TV to factory out of TWRP. I think if you do this, then Xposed would be gone and you could reinstall the last (or any other) pre-rooted rom and boot again. Just the apps and everything would be gone. If there are pictures or files on the internal storage, you can simply pull them with ADBLink/ADBFire and its file manager.
[Fire TV Android Development] TalNum:
I was thinking of just flashing the Xposed uninstaller from TWRP if a suitable workaround isn't found. I was mainly using it for Root Cloak, but since I have ditched the streaming services that check for root, I haven't relied upon it as much as of late. Still stinks that Xposed could potentially be unavailable moving forward.
[Fire TV Android Development] Axecaster:
What was the downgrade bootloop due to xposed or will the device not downgrade after a certain fire os version number?
[Fire TV Android Development] c3po_droid:
[MENTION=3549022]Axecaster[/MENTION]

It is not certain that Xposed is responsible for this. Though since I have a working FireTV after the update and have never had Xposed on my system I can say, that I could downgrade from 5.2.6.6 down to 5.2.4.2 without any issues. So I doubt that there are issues with downgrading to older versions. But I think one should not downgrade below FireOS 5... who knows what could happen then, as downgrading to FireOS 3 is a major step.
[Fire TV Android Development] rainman74:
I can definitely no longer downgrade from 5.2.6.7r2 to 5.2.6.2 even if I wipe system before! The firmware seems to have changed something on the partitions...

The only good news is that with 5.2.6.7r2 the cache partition is now filled correctly again.
[Fire TV Android Development] c3po_droid:
Nothing changed here cache-wise, unfortunately.
[Fire TV Android Development] AFTVnews.com:
I did some testing and the issue is greater than simply losing Alexa functionality. The issue is causing the Alexa system app com.amazon.vizzini to repeatedly crash, then restart, then crash, .... forever. The never-ending crash/restart loop of the app is taxing the system and hurting performance.

I tried disabling the app with "pm disable com.amaozn.vizzini" but it seems to instantly get re-enabled. The crash loop happens on both _r1 and _r2 versions of 5.2.6.7. It does not happen on 5.2.6.6. It only happens when Xposed is installed. Uninstalling Xposed stops the crash loop. So the best options right now are to either downgrade to 5.2.6.6 and keep Xposed or stay on 5.2.6.7 and uninstall Xposed. The biggest feature lost when downgrading is support for the Fire TV Recast, since that requires 5.2.6.7.
[Fire TV Android Development] mnlv:
I think i bricked my FTV2. I was running a prerooted from a year ago and wanted to put on the latest prerooted. Wiped data/cash/... in twrp and installed the latest zip. It gave error 7. When rebooted, it is only showing a black screen with white amazon logo.

Dont know how to get to twrp again to install a differnt rom.
[Fire TV Android Development] MicrosoftBug:
Anyone know if it's possible to swap SuperSU for Magisk? It would probably eliminate any need for Xposed since Magisk can natively hide root.
[Fire TV Android Development] jaydee 77:
Magisk can replace SuperSU, but Magisk does NOT substitute Xposed. Xposed modules can do a lot more than Magisk modules.
[Fire TV Android Development] MicrosoftBug:
Are there any guides for successfully replacing SuperSU with Magisk on the AFTV2?
[Fire TV Android Development] jaydee 77:
As far as I know Magisk need an unlocked bootloader to be installed. So no Magisk for FireTVs. :(
[Fire TV Android Development] rainman74:
Does anyone have any idea how to fix this and still stay on the new firmware? :confused:
[Fire TV Android Development] cline2:
Version 5.2.6.8 is out. Hope someone uploads it for rooted.
[Fire TV Android Development] pelim:
Updated download link for version 5.0.5_r4

Would anyone have the pre-rooted image of version 5.0.5_r4? The Mediafire link has already expired. Thanks so much!
[Fire TV Android Development] rbox:
I reuploaded it and fixed the link.
[Fire TV Android Development] netgar:
Quick question. I have prerooted Amazon TV 2 with latest Sloane ROM. I didn't block updates. If Amazon will send a update, will I loose root? If yes, will my box be still usable? I mean soft brick or something?

Thx
[Fire TV Android Development] chris-89:
[MENTION=3991724]rbox[/MENTION] ...when you have some time to make an prerooted Rom :)

Here is the full image url from Fire OS 5.2.6.8 (630508620):

https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.3.0_user_630508620.bin
[Fire TV Android Development] rbox:
I updated the OP with 5.2.6.8_r1
[Fire TV Android Development] ryknow27:
Thank you so much for taking the time to do this! It is nice to have updated ROMs.:D
[Fire TV Android Development] jaydee 77:
Anyone tried 5.2.6.8_r1 and could state if xposed is properly working?
[Fire TV Android Development] DVO99:
I just updated to this latest version and upon reboot (everytime), the UI would work for a few minutes, then freeze, reboot, and repeat. Any idea as to what is going on?
[Fire TV Android Development] t3ch42:
Just updated and had this happen to me a few times... was able to block updates, but still is occurring.
[Fire TV Android Development] rbox:
What version were you on before you flashed it?
[Fire TV Android Development] t3ch42:
I just had to look back at the versions. Was going to say the last one, but I don't believe I updated to 5.2.6.7_r2 in December, so it must have been the 5.2.6.7_r1 from Nov.

I believe the random rebooting has stopped now though. I hadn't messed with it for a few days but when I turned on the TV tonight, found it was still showing the same screen in spmc where it had been left
[Fire TV Android Development] SystematiQ:
I second this question.
[Fire TV Android Development] yattahey:
"would work for a few minutes, then freeze, reboot, and repeat"

Had this happen today also, even after uninstalling all old non-working installs from before including es explorer & xposed. Thought I was pretty much cleaned out, junk and all. Went ahead and installed 5.2.6.8_r1 dirty, ie no wipe what so ever. Fail, freeze, reboot repeat. Reboot back to recovery. This time live dangerously, wipe cache and dalvik/art, install 5.2.6.8_r1. Fail again - same freeze, reboot, repeat.

This time, get serious load 5.2.6.6 onto microsd, boot to recovery, wiped cache & dalvik again (leave the system and data and storage alone). This time it came up, data was there, no freezes or locks. Will be wiping caches again in a bit because there are some items a little wonky yet, but for the most part it appears to be working.

My comments here are if this were happening in my android phone, I'd nuke it and wipe it slick, flash to stock and start all over again. Anybody ever done this with FireTv2? Is it even possible?

What on earth could be left in there if I'm wiping every wiping the caches (not the data or and storage) and Rbox wipes the system and reinstalls , kernel, recovery, supersu, pre rooted rom? Have the partitions been jiggered over time?

Later: Found that certain functions on the remote and the keyboard have ceased to function. Fix: Unpaired all bluetooth items, remotes, keyboards, etc. Re-pair them all. All remotes and such are again working!
[Fire TV Android Development] c3po_droid:
[MENTION=3560283]yattahey[/MENTION]

It ist most probably because of xposed again... Like some months ago.
[Fire TV Android Development] m1steron:
Same here although mine seems related to having the micro SD card inserted as if I remove it, it doesn't reboot. I thought the card slot may be faulty so I tried the SD in a card reader, connected to the Fire TV's USB port, but the same problem occurs. I have used different SD cards and USB sticks but the problem persists.

Any ideas?
[Fire TV Android Development] el7145:
Hello all,

I just downgraded from 5.2.6.9 (stock) to the latest pre rooted 5.2.6.8...for some reason superuser app wont open, i couldnt get it to open on 5.2.6.9 either

anyone have any suggestions?
[Fire TV Android Development] c3po_droid:
[MENTION=4556232]el7145[/MENTION]

Since you've apparently applied the brand new rooting method to the recent 5.2.6.9 rom to gain root, you'll probably need to wait for some modifications from rbox to achieve compatibility. It is already a bit suspicious that you needed a modified twrp recovery for your rooted device, so the super user issue is probably another side effect related to your special case. I guess only rbox can see through it, as he made the necessary adjustments to the twrp recovery for your device.
[Fire TV Android Development] rbox:
The superuser app has never worked. Root still functions and you get the popups and such, you just can't enter into the app.
[Fire TV Android Development] mattvirus:
i'm having same issue on multiple AFTV2.

One was running 5.2.4.0, another box was running 5.2.1.1... before updating, the others i'm not sure.

rooted via new mediatek exploit (adb push via USB cable, loaded recovery from SD card, rebooted recovery, fully wiped, installed rooted 5.2.6.8.

on reboot, everything looks correct at first, but after a few minutes the AFTV crashes/reloads/restarts the setup process.

I'm working through the issue now, trying a few older
[Fire TV Android Development] mattvirus:
It seems to have something to do with the remote.

completely re-wiped AFTV2 running 5.2.6.8rooted firmware (no remote paired) boots 5.2.6.8 just fine.

-mouse works fine

-keyboard works fine

-pair an AFTV remote -- everything seems fine.

-reboot --> crashes like crazy, can't get far enough into the menu to un-pair the remote with a keyboard before it crashes again

rolled back to 5.2.6.7

-mouse fine

-keyboard fine

-paired remote all good

- reboot -- everything A-OK.

I"m going to stay on 5.2.6.7 for now.

-------EDIT---------

another AFTV2 with same behavior on 5.2.6.8 (crashing during setup, etc)

-completely wiped, formatted data, etc

-installed 5.2.6.7

-zero issues
[Fire TV Android Development] urbanman2004:
Using the new exploit, I was able to root my AFTV 2 with TWRP and flashed the 5.2.6.8 rom from this thread. However, I attempted to flash Magisk afterwards, and now my AFTV 2 is stuck in a reboot loop as recounted here. Any helpful ideas as to what direction I should take from here would be gratefully appreciated.
[Fire TV Android Development] rbox:
5.2.6.7 comes with new firmware. I believe that fixes the crashing. Flashing 5.2.6.7 and then flashing 5.2.6.8 should fix it.
[Fire TV Android Development] BostonDan:
Magisk can't be used on the Amazon fire TV (or fire sticks) as it requires updates to the bootloader. Being rooted is not the same as having an unlocked bootloader.

I'm not sure if there is a way to get back into the bootloader to flash a firmware, or if you can get back into twrp and wipe the system and reinstall.

Wish I could be of more help.

Cheers,

B D.
[Fire TV Android Development] BIOYAM:
[Question] :

Was anyone successful with installing Xposed in the most current pre-rooted stock image: v5.2.6.8_r1?

TIA.
[Fire TV Android Development] alixyz:
I was running stock 5.2.6.8 and after rooting, I installed the pre-rooted 5.2.6.8 but Alexa stopped working (without xposed framework installed). My goal is to have 5.2.6.6 with xposed running but for now focused on just getting 5.2.6.6 running with Alexa and no xposed framework.

Here are my results when testing the pre-rooted ROMs with no xposed framework:

5.2.6.8 - Alexa doesn't work

5.2.6.7 - Alexa works, but as expected, stops working after xposed framework is installed.

5.2.6.6 - Alexa will not work

5.2.6.3 - Bootloop

5.2.6.2 - Bootloop

Any ideas on why Alexa won't run on 5.2.6.6 without xposed framework? I haven't performed a factory reset but have cleared Cache, is a factory reset required?

Update:

Performed a full wipe (Data/Dalvik/Cache/System) and installed 5.2.6.6 with xposed framework and Siri is now working :)
[Fire TV Android Development] urbanman2004:
I understood what I did wrong after the fact, but the good news is I have another AFTV2 being shipped to me tomorrow ;)

---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------

I know I'm being lazy, but in a brief statement could you inform me as to what's the underlying purpose for Xposed framework.
[Fire TV Android Development] g422:
With xposed framework installed one can get xposed edge installed which allows you to remap remote buttons to your liking amongst other things edge can do
[Fire TV Android Development] urbanman2004:
Oh nice, that's awesome. I got a question then. There are some apps such as the "Snes9x EX+" emulator for Android that won't allow me to browse anywhere other than the internal storage directory for compatible files for the app to read. Would Xposed allow me to browse external storage devices connected that I have connected to the AFTV to select compatible files?
[Fire TV Android Development] g422:
im in process of trying to find out with retroarch myself I will find out let ya know
[Fire TV Android Development] urbanman2004:
Hey, thanks. I would do it myself, but I'm waiting for my replacement AFTV2 to arrive tomm via USPS, but could try installing the app for me, and letting me know if it works. I included it as an attachment
[Fire TV Android Development] g422:
atm i cant gotta go bed in min for work tomorrow, however tomorrow i can try for you and let ya know. also plan on writing a lil guide on installing xposed installer and edge and guide for edge
[Fire TV Android Development] urbanman2004:
Not a problem, I appreciate the gesture though. Once you make that guide to Xposed let me know, and I can link it to my guide as well.
[Fire TV Android Development] daver:
firestick gen 2 5.2.6.8

hi

i have a rooted 5.2.6.8 firestick gen 2

can i flash this rom using the twrp

is it compatible?
[Fire TV Android Development] alixyz:
Unfortunately, I don't believe you can use this image which is for "sloane" (Fire TV 2). For the Fire TV Stick 2 you will need "tank" images but I haven't seen any prerooted images out there for it yet. Part of the reason that no prerooted images have been created yet, is that until last week the Fire TV Stick had never been rooted. Hopefully someone will invest the time to create it soon.
[Fire TV Android Development] daver:
firestick gen 2 5.2.6.8

ok thanks anyway..hope someone provides an image for the firestick gen 2 ..;)
[Fire TV Android Development] rbox:
If you already have rooted 5.2.6.8, what do you think you need to flash?
[Fire TV Android Development] alixyz:
Hi rbox, first of all THANK YOU for all the time you've put into this!

I'm not sure about daver's original intent was but I for one see two benefits.

1. If there is a 5.2.6.6 build, we can use xposed framework on the Firestick 2

2. Have a safety net to reinstall a ROM incase the system partition is goofed up.
[Fire TV Android Development] rbox:
1. I don't have any 5.2.6.6 original ROM images. I only have 8 and 9. So that's not going to be possible unless someone can get the ROM url.

2. I believe in one of the threads about the Firestick 2 root, they were talking about flashing the stock rom image.

3. I plan on making pre rooted roms, but I'm still working on it.
[Fire TV Android Development] alixyz:
Thanks rbox. For now I'm thrilled to experiment with my Fire TV 2 devices :)
[Fire TV Android Development] daver:
hi sorry

what i am looking for is rom where we can use google play services and get rid of all the amazon crap(debloat)

and use kodi and some other tv apps..remove blacklisted app restrictions if that is possible...

thanks
[Fire TV Android Development] rbox:
My roms are 100% stock with the exception of added root. I don't add anything extra.
[Fire TV Android Development] cyclops13:
Is the auto update disabled in these pre-rooted roms?

EDIT: Apologies. I see that in the OP its clearly mentioned that stock recovery is disabled by default so that the update does not goes through. However its also recommended to disable the updates, whats the best way to go about it?
[Fire TV Android Development] alixyz:
Follow Method 1 from the below link

http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/#root
[Fire TV Android Development] gotluck:
cheers!! this worked beautifully! rooted on 5.2.6.6 with xposed FireTV2 with working alexa. Rootcloak module works for PS Vue root detection.
[Fire TV Android Development] m1steron:
Update: All fixed now :o
[Fire TV Android Development] c3po_droid:
[MENTION=8052006]m1steron[/MENTION]

Please share how or what fixed those issues for you now.
[Fire TV Android Development] m1steron:
Try this first, purley theoretical:

1. TWRP Factory reset your device > advanced wipe > “Dalvik / ART Cache”, “Cache”, “Data”, and “Internal Storage.”

2. Install sloane-5.2.6.0-rooted_r1.zip and reboot. Check this i working correctly then install sloane-5.2.6.7-rooted_r1.zip followed by sloane-5.2.6.7-rooted_r2. Check again, then update to the current released build sloane-5.2.6.8-rooted_r1.

If this doesn't work then perhaps try what I did, obviously at your own risk!

From what I remember I decided to do a TWRP factory reset and install version sloane-5.2.6.0-rooted_r1.zip.

This went fine but I continued to get the random freeze and reboot issue, even before I finished the initial setup.

In my frustration I decided to use the unbrick image instructions using the option unbrick+ramdisk.img. After several hours I was back in TWRP so installed sloane-5.2.6.0-rooted_r1.zip. This worked perfectly with no random reboots. I don't know if it was related to the unbrick+ramdisk.img or whether this is coincidental. I had previously tried using just the unbrick.img but continued to get freezing and reboot issues.

Some days later I systematically installed each released rbox update until I was on the latest version (February 10, 2019 - 5.2.6.8_r1) with no problems at all.

On a side note a good app for disabling the OTA update or other service/s through your rooted FIRE TV device:

https://play.google.com/store/apps/details?id=us.dappollonio.appdisabler&hl=en_US
[Fire TV Android Development] errut:
Thanks, worked
[Fire TV Android Development] Eyedoctor2:
Can you please provide a link to rooted 5.2.4.2_r2 for Fire TV 2 ? The link on the OP appears to be broken. I am on the latest rooted firmware but am having problems mounting NTFS and using the google store. My Fire TV 1 is on 5.2.4.2_r2 and both these are working well and Firestarter too.

Thanks in advance!
[Fire TV Android Development] rbox:
You were a few days late. I just cleaned out my images. haha. I just reuploaded it for you.
[Fire TV Android Development] Eyedoctor2:
Lol...

Would you anticipate any problems in my rolling back from 5.2.6.8_r1 to 5.2.4.2_r2 ? I do know that if I decide to go back to 5.2.6.8 I will need to first flash 5.2.6.7r2 but I don't know if there will be any DRM firmware related problems.

Thanks again!
[Fire TV Android Development] rbox:
That particular version comes with updated firmware to match that version, so you should be good.
[Fire TV Android Development] bennyasf:
Will the newest be updated?
[Fire TV Android Development] jim16127:
[MENTION=3991724]rbox[/MENTION] I successfully rooted the latest version 5.2.6.9 and flashed your latest prerooted rom immediately afterward. All worked well. Then I flashed Prerooted rom 5.0.5r4 and now my fire tv will not boot or show anything at all. It appears to be a bootloop based on the white light on the box. It illuminates...flickers a few times then turns off for a few seconds before repeating. Is there anyway out of this?

EDIT... after reading and rereading the warnings. I think I understand. Once I've updated to factory 5.2.1.0 or later, then I can't go back to a firmware before 5.2.1.0! I was understanding it...as long as it came from factory with a firmware prior to 5.2.1.0 then I'm good. I obviously was wrong!

All that being said. If one were to break this rule...

WARNING: DO NOT FLASH 5.0.5.1 OR EARLIER IF YOU STARTED WITH VERSION 5.2.1.0 OR LATER

Is there any way to rectify it? Or should I consider it bricked and move along? Thank you for your tremendous support!