yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] mko64:
I have similar situation, but after new rom it first started and worked ok, sweet new menu etc. Then I tried to start Netflix and it just tried to start it and then go right back to FireTV menu (not even Netflix logo). So I thought I should reboot, and when going to power menu there was some "reboot needed" text, so I rebooted it - and after that no white led, no power, no picture.... :eek: Power supply seems ok, at least without any load (tested with DMM).
[Fire TV Android Development] procter:
Have u figured out the way out? Well, One thing I did not do was to block update via adb while pushing the file, thinking I would do it after flashing the new ROM, was too lazy to do it twice. May not be the reason, but most of the victims were experiencing this while a reboot, I just could not think any occasion of automatic reboot while just pushing a file.

Mine was about 1.5 yr old, so out of warranty and Amazon declined replacement as expected, but I don't feel like getting the ftv2 especially after getting a powerful chinese box for half of the asking price (of a aftv2), and it has pretty good custom rom by this great developer superceleron at freaktab.

Now I'm hating myself getting those unnecessary troubles, it was working perfectly fine with the fos5, kodi was running like a blast with other streaming apps. Want to chop off that itchy hand of mine for being so touchy and creating issues out of nowhere....:crying:
[Fire TV Android Development] Y314K:
Sorry, but I've only read about this problem in passing. I saw you asked ? from someone that has actually dealt with this in a prior thread. That's the way to go.

The FTVS2 is very much a FTV1 without the USB socket although I think OTG works on it. So that might be an option for you. Specially if Amazon ever gets enough supply to have a sale.
[Fire TV Android Development] mko64:
No idea what happened and why. I also blocked updates via abd, but after rom was installed and FireTV was "optimizing system storage and applications".

Yeah, all I wanted was the new GUI, it was working ok with older rom..... doh! :D
[Fire TV Android Development] ariesjunk:
After upgraded to FireOS5, I got a black screen with only the top menu (Home Your Videos Movies TV Apps Settings). Anyone know how to fix it?
[Fire TV Android Development] Y314K:
Sounds like internet problems or if you've been blocking updates thru your Router or OpenDNS. That might cause that. Or if you have a VPN with a KillSwitch running.

If it is Router or OpenDNS blocking of updates. First do Method 1 & then Methods 5 (ES File Explorer version) blocking of updates from the following guide before you remove the Router or OpenDNS update blocking.

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

Not that hard & doesn't take much time.
[Fire TV Android Development] ariesting:
I did block updates thru my router. Will try as soon as I get back home. Thanks.
[Fire TV Android Development] oppman29:
One of things that I lost during the update to this ROM was the ability to run “Fire TV Mods by rbox” exposed module.

This module gives you the ability to remap your home button and replace the home launcher ( I had KODI set up as my home button).

Anyone knows of another method to set KODI as the home launcher working on this rom?
[Fire TV Android Development] Y314K:
You'll need to wait for RBox to update his FTV XPosed Module.

I've never replaced the launcher. And if some of you do not want to wait. Then someone will need to test/try the SPMC with Launcher using what was learned from the AFTV2ATV Project.

http://xdaforums.com/fire-tv/general/project-aftv2atv-t3489239

Since that is the only project that I know of that changed the launcher on PreRooted v5.2.4.0.
[Fire TV Android Development] kbrabble:
Just wanted to say a quick thank you to rbox keeping us first generation fire TV users up to date with pre rooted ROMs! I've installed the latest version, and everything works great.
[Fire TV Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION] ...

Is there a hard coded MD5 hash or some kind of signature in the PreRooted roms ?

I am asking since in the past versions when testing either changing the SU APK or deleted the SU directory all together for the Root check bypass trick (Mostly for TV Provider Apps). I then created a new MD5 file for TWRP to verify the zip. But no matter which MD5 I tried. Original or modified. It would always fail the MD5 check in TWRP. The only way to flash it was to include no MD5 file. So I thought maybe something is signed or hard coded to the PreRooted ROM that makes TWRP fail the MD5 check. And yes, I know how to create a MD5 file. Did the changes to the zip using Winrar v5.30 Beta 2.
[Fire TV Android Development] foshozee:
Manage to brick both my amazon fire tv 1. I do not have access to a linux or knowledge of it. If anyone can help me please pm me, I can send a donation for your time and effort. Thanks in advance.
[Fire TV Android Development] symphonix:
Rbox, thank you for this. I did this and it turns on but stuck at the "AmazonFireTV" logo. Any suggestions what I can do next? I've used the search throughout this thread but could not find what to do.
[Fire TV Android Development] 1jimmy007:
Fire TV 1 stuck on amazon logo.

Will the 5.0.5 restore work? I have a box that locked up on amazon logo trying to unlock boatloader... the box was on our roms..

---------- Post added at 02:50 AM ---------- Previous post was at 02:41 AM ----------

Can I send you my locked up box? It's a fire TV 1, stuck on amazon logo?
[Fire TV Android Development] iniro:
Hi,

I updated to latest version and wipe cache and get stuck bootloop on "optimising system storage and applications..."

What can I do?

Thx!

Edit: If I wipe cache and restart without Internet then it boots well, but when I plug it to Internet it reboots and get stucked on same bootloop.

Edit2: I have ota blocked via build.prop version number and disabling com.amazon.device.software.ota via pm command.

My previous version was bueller-5.0.5-rooted_r2.zip
[Fire TV Android Development] iniro:
Please can someone provide me original settings.apk from bueller-5.0.5-rooted_r2?
[Fire TV Android Development] Y314K:
If you can still TWRP into your device. Try just reflasing the the ROM. That should get u the Settings.APK back. Don't wipe more then Dalvik cache & Cache for now. Also make sure your verifying the PreRooted FW image before flashing.

What stock FW did you root your FTV1 on ?
[Fire TV Android Development] iniro:
My version is bueller-5.0.5-rooted_r2, thx!!

Now I discover that what I need is an settings.apk to manage wii controller. Aftv news tutorial has a link for an older version that doesnt work with bueller-5.0.5-rooted_r2 (kk vs lp)
[Fire TV Android Development] Y314K:
Your best bet would be to ask for it in one of the controller threads. Since they would know what works & what not.
[Fire TV Android Development] procter:
OK. Mine was similar, but instead of 5.0.5, I loaded 5.2.1 prerooted ROM. I was pushing a file via adb wifi and left the room, I did not see any possibility of rebooting while pushing a file, but when I returned the room, the ftv is dead as a brick, no lights and such.

Is it possible to use 5.2.4 update file to replace the 5.0.5 in [MENTION=3991724]rbox[/MENTION] instruction, so that when I lost the unlocked bootloader, at least I can have the fos5? Or generically any update on that instruction at all?
[Fire TV Android Development] flyingdeath:
Thanks [MENTION=3991724]rbox[/MENTION] for the latest update. It worked for me successfully in one go.

I do however have one issue, App Icons seems to have disappeared for me for all the existing applications. Netflix/Youtube/Kodi all seems to be coming up with blank app logo in the list. I can launch them without any issues though. Would be great if someone already knows how to fix it.

Update: A Reboot fixed it

Thanks
[Fire TV Android Development] MTKnife:
A couple of weeks after I installed the new ROM (5.2.4.1_r1), I noticed the Google Play Store was no longer able to update apps, or install new ones. I thought that when I originally installed the ROM, after wiping system, I had re-installed Open GAPPS and Xposed, but now I suspect I just didn't notice error messages that indicated failed installs--the Xposed app is telling me that Xposed isn't installed. I tried wiping system again and reinstalling all three things, but now I'm noticing (though I can't be positive the same thing happened before) that I'm getting an "insufficient storage" error whenever I try to install either Open GAPPS or Xposed.

I've looked at the system partition in TWRP--the first time I looked (can't remember whether it was before or after the wipe and install), all 755MB are used; now (possibly as a result of wiping, possibly as a result of using the "Resize" function--I'm not sure), I've got 640MB used, which apparently still leaves too little to install either Open GAPPS or Xposed. That makes sense for GAPPS, since the file size of the Nano package is about 150MB; however, it makes no sense for Xposed, which is under 10 megs. At any rate, I'm at a loss for how to solve the problem.

I've Googled the issue quite a bit, and come up with very little. Am I the only one having this problem? How can I address it?

I should add, since maybe it indicates a problem with my particular device, that TWRP hangs every time I try to wipe cache, and I end up having to re-format that partition. That might be a general problem, though.
[Fire TV Android Development] MTKnife:
Does no one else have the problem I described above? If not, can you at least confirm that you don't have it?
[Fire TV Android Development] deepasadish:
just wanted to report that 5.2.4.1_r1 is working great for me.

my firetv was getting sluggish - never did a factory reset on it from the fire OS 3 days.

installed 5.2.4.1_r1 [from USB flash drive] (i deleted the su folder from the zip, since I don't need root), made sure it booted up, then booted again to TWRP, wiped Dalvik, Cache, Data, System and Internal Storage. installed again. went through the setup process (requires original remote) and now my firetv feels very fast and clean.

also, re-enabled adb debugging and did "pm hide com.amazon.device.software.ota" (could not do "pm disable com.amazon.device.software.ota" since i didn't install root). not sure if this really blocks updates or not.

thanks rbox.
[Fire TV Android Development] Y314K:
It should block them & so does TWRP. You should be able to flash a regular PreRooted ROM to regain root.

You might be able to do Method 5 thru TWRP without SU. Not sure. Might be worth a try.
[Fire TV Android Development] deepasadish:
thanks. i thought about this and this is what i did - i installed again with "su" folder, disabled update by "pm disable com.amazon.device.software.ota", then installed again without "su" folder. :)
[Fire TV Android Development] Y314K:
Nice, forgot that rooted Method 1 should survive PreRooted ROM reflasing. Thanks for verifying this.

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------

? Where you able to use a MD5 file in TWRPwith the SU less (modified) PreRooted ROM ?
[Fire TV Android Development] deepasadish:
No, i didn't try that at all.
[Fire TV Android Development] procter:
nm
[Fire TV Android Development] bula1ca:
Was this unit out of stream for a while? I just updated a unit that has not been connected for a while and I had to go through a two steps validation to re-register it again......

read here: https://www.amazon.com/gp/help/customer/display.html?nodeId=201819620
[Fire TV Android Development] guga2223:
sleep problem

Hi

I installed the pre rooted 5.2.4.1 r1, and the installation went perfect.

But I am having a problem with the sleep mode...every time fire tv goes to sleep, some time later it turns on and goes to twrp mode...

What can I do?

Thanks
[Fire TV Android Development] ldeveraux:
Not sure about the FireTV, but I've had that happen on the Nexus Player. It means I hadn't disabled updates and the device tries to auto update through recovery. But since you replaced the recovery with TWRP, it can't do it and stalls there.
[Fire TV Android Development] fr0st420:
Anyone use Directv now? I'm getting a error after it's latest update. I think it's due to root. Is there a easy to flash my firetv back to stock?
[Fire TV Android Development] Aobeta:
Mine has been crashing back to twrp too. It's only been happening the last few days though, and I have had this version installed since May. Not sure what's going on, but it's annoying as hell!
[Fire TV Android Development] Y314K:
Might be related to: http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
[Fire TV Android Development] guga2223:
Thanks Ideveraux for the tip

I tried to send this command again: pm disable com.amazon.device.software.ota, and it worked for me.
[Fire TV Android Development] fido14dido:
Same thing is happening to me and I am sure i blocked updates on the device and via router so I'm not sure if / how the update was downloaded. Maybe the new software release with the same version # is making the device think an update was downloaded.
[Fire TV Android Development] Y314K:
That is why it is highly recommended to not only do update blocking Method 1 but Method 5 too.
[Fire TV Android Development] rbox:
I updated the OP with 5.2.4.1_r2.
[Fire TV Android Development] fr0st420:
Flashing now. Thanks for the quick update.
[Fire TV Android Development] realbbb:
Thank you!

BBB

Coloring my Book
[Fire TV Android Development] Sizzlechest:
Does the latest version still cause 24 fps video not to work properly in Kodi?
[Fire TV Android Development] hocus86:
Is it possible to upload 5.0.4_r2 for FTV1 so that we can remove TWRP with a stock update?
[Fire TV Android Development] Y314K:
According to Hovee over at AFTVNews comments related to this update. This update does fix the 24p bug.

http://www.aftvnews.com/new-pre-rooted-roms-for-the-fire-tv-1-2-and-stick-have-just-been-released/

http://www.aftvnews.com/new-software-updates-rolling-out-to-all-amazon-fire-tvs-and-fire-tv-sticks/
[Fire TV Android Development] Petesky:
Why do I need to keep updating supersu after flashing these roms , why not use latest one
[Fire TV Android Development] rbox:
You can just ignore the message. I haven't updated the SuperSU that I put in it because I know this one works.
[Fire TV Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION] , Maybe for the next update? or sooner.

Thanks to [MENTION=7767738]SimLynks[/MENTION]. It seems the latest SuperSU v2.82 has been tested & works perfectly as part of the Playing with Fire Mod. On the latest PreRooted FW.
[Fire TV Android Development] tdfsu:
I've been on rbox's pre-rooted OS5 roms and just updated to 5.2.4.1_r2....but have a problem.

Is there some new trick to get my unlocked FTV (v1) to boot into Nova launcher and have the home button launch Nova? All I can get from the home button is the stock Amazon launcher.

I have xposed and rbox mods v1.4 active. I re-flashed the new arm 87 sdk22 framework, tried flashing the old sdk21 framework, re-installed the alpha xposed launcher, tried the new 3.1.1 xposed launcher...nothing will result in booting to Nova. The xposed launcher says xposed is active and ive rebooted a hundred times trying different things...but it won't boot into Nova.

As a last resort, I installed xposed edge pro and remapped the buttons...and it will boot into Nova, just doesnt work exactly like i would like.

What has changed or what am I doing wrong?

Any ideas...I'm at a loss?

Thank you in advance.

Jason.
[Fire TV Android Development] SimLynks:
rbox mods v1.4 hasen't worked since FireOS3, so at least part of your issue is trying to use a very old non-working Xposed Module. XPosed Edge can do exactly what you want, but you need to get the Pro version. Please see Y134K's thread where he explains this in detail and with a ton of pictures.

[MENTION=3991724]rbox[/MENTION] The main reason I started using more up-to-date versions of SuperSU on the FireTV-v1 is that it completely resolves the /sdcard/ access problems when in a root shell (at least i've never once had that issue again since starting to install newer SuperSU packages around February).
[Fire TV Android Development] Y314K:
We can always flash [MENTION=7767738]SimLynks[/MENTION] tested latest SuperSU v2.82 zip right after the PreRooted ROM. Specially if you use a USB stick for flashing. In order to have the same affect. But make sure you include a MD5 file to verify it's integrity. It's to important to NOT flash a corrupt zip.
[Fire TV Android Development] Y314K:
[MENTION=7767738]SimLynks[/MENTION] I get a

When I test the zip with WinRar but no error when I test it with 7-Zip.

This is the MD5 value I have for it: 47E92D339F6B62246952B0C89921742B - Dose this match yours ?
[Fire TV Android Development] SimLynks:
MD5 = 47e92d339f6b62246952b0c89921742b so yeah I've got the same hash value on my copy as well.

What is exactly is the issue your having with this version? I've been using it for at least a month on the FireTV-v1 and even with all the crazy things i've been doing to my device recently I haven't had a single issue with it yet. Even had Holo Themer v3.0 enabled for extended periods of time without any crashes / reboots (at least infrequent enough I never saw it happen with v2.82)
[Fire TV Android Development] Y314K:
Good to know. It's probably a WinRar problem. I get the errors I listed above when I run the Test option from WinRar when I open to test the SuperSU zip file. This is just a thing I check after moving a file to my USB stick that I am going to flash. Specially when the author did not include an MD5 hash to check against. But a 7-Zip Test does not give me those errors. So must be a false positive. And the SuperSU is fine.
[Fire TV Android Development] Y314K:
Well that was a smooth update for two of my FTV1's.

Made some notes:

- Used TWRP with latest PreRooted ROM, latest SuperSU & latest XPosed Framework in separate folders with their own MD5 files loaded on a USB Flash Drive.

- Cleaned Dalvik Cache & Cache.

- Flashed all 3 zips in the order mentioned above using the TWRP "add zip" to flash option.

- Cleaned Dalvik Cache & Cache again, why not.

- During the first FTV1 update I did have to unmount the USB stick to shorten the SuperSU zips name & to redo the MD5 file since it failed the TWRP MD5 check the first time. Got rid of any spaces & replaced any "-" with "_". Also got rid of the extra numbers past the "2.82" version number to shorten it. Had no problems on the second FTV1.

- Waited for first boot. Loaded right into AppStarter since XPosed modules HDXPosed & Edge Pro where already installed & active.

- Did the BusyBox install from within the BusyBox manager App which was already installed.

- Did Method 5 update blocking thru ES File Explorer (must be redone when ever you reflash a ROM). Method 1 was still active.

- SuperSU never requested to be updated. I did not have to install/run the Holo Themer module. ES File Explorer Root worked at first try.

Easy piece.
[Fire TV Android Development] Petesky:
I'm never able to do method 5 using ES File Explorer, I can change ro.build.version.number to 987654321 but I can never save it, it just refuses so have to do it using TWRP,

thats why I asked about using latest SuperSu in the custom builds , tho I dont even know

if thats what causes it
[Fire TV Android Development] Y314K:
Easy to check.

Open ES File Explorer.

Go to Tools & switch on the "Root Explorer" option.

Give it Root Access if this is your first time or if you've only given it temporary root access in the past.

You will either get a "Sorry, test failed. This feature cannot run on your device" error. Or you will see the Root Explorer Menu.

If you get the "Sorry, test failed. This feature cannot run on your device" error then installing thru TWRP the latest SuperSU link that SimLynks provided in his guide should fix that.

If your problem is different. Then we will need more details.
[Fire TV Android Development] Petesky:
Just tried to alter the ro.build.version.number again , and it worked this time (was able to save change) but that was after updating SuperSu
[Fire TV Android Development] Y314K:
Updating SuperSU does seem to solve a lot of File Manager App probs or bugs on FireOS 5.
[Fire TV Android Development] payzero:
Yesterday I updated my FireTV1 to 5.2.4.1_r2 from stock 51.1.6.3 by going through many steps found on aftvnews using TWRP. Things went well at first and I was able to get kodi loaded and played fine. Then I had a pop up on the screen saying my remote software is being updated. It went fine as well. However, the reboot after that didn't go well. I got no power light on the box. Using USB A2A cable on windows, it shows only directory "image". Did I somehow trigger the efuse? If so, is there a way to recovery it? Do I lose the root on this device for good if it can be recovered? Thanks for your help in advance!
[Fire TV Android Development] sepa10:
Has anyone run into a problem where the FTV1 will self reboot into recovery if it is not used after for a few hours?

I'm currently on 5.2.4.1_r1.
[Fire TV Android Development] Axecaster:
Do you have both method 1 and 5 of this guide configured to block updates?

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

Self reboots into recovery likely indicate an update was downloaded, but could not install as TWRP halts the process. This guide can help remove the downloaded update:

http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
[Fire TV Android Development] sepa10:
To be honest. I don't know if it is blocked or not. It was a looong time ago but I have done several updates since.

I'll give it a look this afternoon.
[Fire TV Android Development] drewb0y:
rbox - FilmStruck issues

rbox - I saw that you have a fix for the FTV2 Hulu and GBO Go issues. Not sure if this is related or not but there are issues with the FilmStruck app on both the FTV1 and FTV Stick 1.

The app runs and then starts at the first menu selection, if you try to go down to the next menu selection it jumps down 2 instead. So it's basically crippled the app. I have tried different versions of the app and even sideloading the apk from my rooted Kindle Fire tablet which works flawlessly. You can do a free trial account to test it out or contact me for login info. The only thing I haven't tried is going back to unrooted, which I am trying to avoid. Could this be a DRM thing just like with the Hulu app?

http://www.aftvnews.com/md5file
[/LIST
[Fire TV Android Development] schneid:
HBO was broken for me. Would load video then quit. Sideloading older APK from Themes and Apps works. In the first bundle of FTV apps.

Hulu just all messed up. I can bore down through menus but can't back out. Might just be Hulu's new interface. Fixed that by canceling. Keep paying, quitting, getting sucked into paying again. Finally realized I wasn't watching anything there anyway. Was excited about their LiveTV but $45.00/mo is not much different than my sat DirecTV.

Really want to cut the cord but pieces to integrate OTA, streaming, and DVR aren't quite all there yet. Don't know why DirecTV won't add DirecTV Now to their boxes. But then, they discontinued OTA tuning and recording. Maybe they're just stupid and want to give away the market to others. I mean they have all the content , 4k, DVR, whole-home distribution, a good interface, national sales and distribution, and ATT's network. Plus they are pretty plug 'n play.

As for FireTV, I imagine my sin is being rooted. i rooted because, well, I always root stuff. I hated FireTV's interface and just wanted Android with Nova Launcher.

Very thankful to Rbox for making my FireTV quite usable for the last three years.
[Fire TV Android Development] fr0st420:
I'm having issues with load times for Directv now. I wanted to test the app out on a non-rooted rom. Is there one available for download? All the guides out there are outdated to return to stock. Thanks for any help.
[Fire TV Android Development] Sizzlechest:
I think there's a solution for that. https://xdaforums.com/fire-tv/help/directv-love-root-users-t3510461