yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] nooknut:
[MENTION=241865]Scott[/MENTION], I had this issue on one of my units. I called Netflix CS one night and explained the issue. After supplying some info from the netflix app, they remote reset my device binding on my account. Once done, a simple reboot and everything was peachy.
[Fire TV Android Development] rbox:
The first beta is total crap. I haven't gotten the URL for the 2nd update yet, so I can't say. But I've heard it's not better. Regardless, I'm not going to release a prerooted until Amazon starts pushing the final version. Just to make sure nothing changes between the beta and that one.
[Fire TV Android Development] goodbye hppalm:
Thank you for the hard work rbox
[Fire TV Android Development] mdpauley:
[MENTION=3991724]rbox[/MENTION] would you mind sharing your ROM making process?
[Fire TV Android Development] rbox:
I extract the update, compare it to previous ones, add in root, modify the updater script, unpack the kernel, remove the bricking tool, repack it, remove any miscellaneous "bad" files, and then package it back into a zip.
[Fire TV Android Development] KLit75:
Im also now hearing that you cant move kodi thumbs to external. I assume this applies to gen 1 running os5 eventhough gen 2 uses an sdcard instead of usb. For me it means going back to using stickmount or other method to mount the usb drive. Since ive kind of got things working the way i like now im not sure upgrading would be smart... anyone have an idea of whether amazon might fix this? Supposedly it has to do with lollipop.
[Fire TV Android Development] iniro:
Hello,

I updated from 51.1.6.1_516010220 to latest 51.1.6.3_516012020 but now kodi is not as stable like with last rom. Anyone more? It will be another newer rom soon?

Thx thx thx for your efforts.

Edited: And now my kodi cant enter sleep mode with screensaver. Screen gets black but aftv white leds does not turns off.
[Fire TV Android Development] jarayn:
My Kodi is exactly the same as it was before.
[Fire TV Android Development] hazard666:
How's it not stable? You haven't given any details. For the issue of not entering sleep mode, go into appearances > screensaver settings and go into the setting for the add on then test the configuration. It should ask for root permission. I'm willing to bet it either lost root permission or you upgraded Kodi. This happens every time you upgrade Kodi.
[Fire TV Android Development] iniro:
Yeah! I did it. Enter in kodi screensaver settings and give root permisions, screen gets black but led stills is white forever.
[Fire TV Android Development] KLit75:
If you set screensaver time to never, it will sleep. Of course this means you lose the screensaver so for my livingroom TV I either remember to put it to sleep manually or i just leave it on. Its really not a concern for me if i leave it on, probably goes weeks without sleeping and ive had this aftv since spring of 2014.
[Fire TV Android Development] hazard666:
I don't even use the sleep mode screensaver anymore. Just set power save mode to 30 minutes and that way I can still use a traditional screensaver. In case you guys want to go that route.
[Fire TV Android Development] iniro:
How to set power save mode? In Kodi? In AFTV settings?
[Fire TV Android Development] sirxdroid:
On mine that runs an older ROM from about a year ago, I just disabled the screensaver, no other changes, no power saver settings in Kodi and it goes into power saver mode on its own. I found that if you enable the screensaver it stays on all the time.

Things may have changed in newer ROMs though.
[Fire TV Android Development] iniro:
Then you disabled kodi's screensaver and nothing more? I will try it tonight. How much minutes spends entering power saving mode?
[Fire TV Android Development] sirxdroid:
I think I just let kodi dim the screen. It takes 30 min. to go in standby but don't quote me on it. Mine didn't use to go into standby and discovered it was the screensaver keeping it awake.
[Fire TV Android Development] hazard666:
The way that I do it is via the power saver settings within Kodi. You can keep your screensaver or turn it off but I set the power saver to 30 minutes, that way it turns off after 30 minutes of inactivity.
[Fire TV Android Development] dillfever:
rbox can I flash an older custom rom of yours over your latest that I have installed... I need usb storage....tanks dill oh ya and stickmount doesn't seem to work...
[Fire TV Android Development] rbox:
What version are you on and what version do you want to flash to? I don't think anything changed with USB storage...
[Fire TV Android Development] dillfever:
I'm on 51.1.6.3 I just flashes it I was on your 51.1.4.1_fixed ut wanted the latest.....anyhoo after it rebooted and finished flash there was a message about my usb to disable it or just continue I continued it seemed to mount at first than no go, checked in systems and no usb mounted.....was going to go back to what I had on, cause usb worked fine.....
[Fire TV Android Development] rbox:
Yes you can go backwards, but I was recommend a factory reset. But if you are going to factory reset, you may as well try it with the version you're on right now to see if it fixes it. You could also try booting with it unplugged and plug it in and see if that fixes it.
[Fire TV Android Development] dillfever:
k will boot it without the usb first then I'll factory with this f/w before thinking of going back.....just on my way out will update ya later.....thanks dill
[Fire TV Android Development] dillfever:
went back to 51.1.4.1 for now, booting without usb did nothing, will wipe and re-install 163 after I backup some apk's......dill
[Fire TV Android Development] dillfever:
ok installed latest with full wipe and all is good now, usb storage is detected now everything seems good, setting it up now....tanks rbox.....
[Fire TV Android Development] Legolas2:
Issue w/ Netflix

HI Jedi

Did you have this issue resolved w/ Netflix? I have a similar issue, but on much older version of pre-rooted FW.

Quoting my own query from:

http://xdaforums.com/fire-tv/help/aftv-1st-gen-rooted-trouble-netflix-t3287632
[Fire TV Android Development] ImCoKeMaN:
Have you updated the netflix app itself? "Update" doesn't show up in most recent, but it does show up if you browse to netflix from the Apps menu.
[Fire TV Android Development] JediSooner:
Nah, I gave up and went back to Apple TV.
[Fire TV Android Development] YoColdRain:
[MENTION=3991724]rbox[/MENTION] , just want to know whats your stance on supporting fire tv 1st gen... is there a hope for 5.x release?
[Fire TV Android Development] rbox:
As soon as I get the update url. I will start working on it.
[Fire TV Android Development] deepasadish:
I am on the latest rbox prerooted rom (obviously with unlocked bootloader, rbox boot menu and clockworkmod).

The at&t uverse app won't run because the device is rooted - says something like - "device is not secure".

I have tried root cloak, etc - but nothing works.

I want to "cleanup for permanent unroot" in supersu, and then uninstall it.

If I do that, can I always get root back, by simply flashing supersu from recovery?

Worst case, can I get root back by reflashing rbox prerooted rom?

Any suggestions/alternatives? Thanks.
[Fire TV Android Development] crapshack:
Anybody have any idea if OS 5 will have 24p playback working in Kodi? Or the realistic chance of that ever happening?

I know the 24p menu is hidden in OS 5 and has the option for 24p. But I'm not clear on if it actually does anything or if Kodi can use that feature for 24p mkvs, mp4s, etc.

Is there still a lot of development that needs to happen? I imagine that auto-switching between 24p and 60 is a long way away.
[Fire TV Android Development] DigiRay:
Hi RBox

I sent you a PM you might find interesting. Hope you don't mind
[Fire TV Android Development] jim16127:
AWESOME SAUCE!!! Excellent work DigiRay! Elias' tip for capturing the URL must have paid off!
[Fire TV Android Development] DigiRay:
Sure did. I kinda had an idea of what needed doing, just wasn't too sure. But it worked and it's been passed on to boss man and that's the important thing :)
[Fire TV Android Development] krawhitham:
I hate to be that guy, but I'm going to do it anyway

Any update on when the prerooted OS5 for Gen 1 units will be released?
[Fire TV Android Development] freezer2k:
+1

That would be awesome!
[Fire TV Android Development] KLit75:
I hate having to be that guy, who follows the rules, and doesn't ask for etas. ;)

It took amazon several months to get OS5 to gen 1, I think a little patience is warranted here. Regardless, in my observation questions like that don't help.
[Fire TV Android Development] xm41907:
Rbox has the OS5 image. He's working on getting TWRP working right according to the last stuff I read about it. I'd rather him get it right than rush it, even if I'm anxious as well.
[Fire TV Android Development] deepasadish:
Please pardon if this question is stupid and makes no sense:

Is it possible to release a custom rom that is not rooted, but simply with amazon updates disabled?

i.e., i want unlocked bootloader (we already have this), TWRP/CWM for recovery (we have this too), but the ROM is fully stock with updates disabled. the presence of TWRP/CWM as recovery gives us the option to root by flashing SuperSU if needed.

I am asking this because some apps don't work if root is detected. thanks.
[Fire TV Android Development] rbox:
With the 5.0.5 update, it'll be pretty easy to not install su. Just need to delete it out of the zip.
[Fire TV Android Development] deepasadish:
well, i was thinking about this and this might become a problem:

since your roms don't come with amazon updates disabled, without SU we can't disable those? so i guess we must be rooted? thanks.
[Fire TV Android Development] rbox:
With fireos 5 you actually don't need root to disable updates. But I do modify recovery to actually not process the Amazon updates.
[Fire TV Android Development] xenyz:
To elaborate on how to do this, see here.
[Fire TV Android Development] busventinc:
Rbox for the 1st Gen box will we be required to keep the boot menu or will there be something new in the works along with twrp and the new rom for OS5 thanks for what you do rbox it is much appreciated....

Looking forward to the new goodies us 1st Gen users are getting...
[Fire TV Android Development] rbox:
There is a new bootmenu based on twrp. And unfortunately the comic sans font is gone :(
[Fire TV Android Development] YoColdRain:
glad the font is gone. :p felt it was very amateurish for top notch work you actually do for the community...
[Fire TV Android Development] jarayn:
Damn. I saw the new posts and thought it was going to be a release.

For some reason I'm really looking forward to this update even though I don't think it's all that different.
[Fire TV Android Development] deepasadish:
[MENTION=3991724]rbox[/MENTION]: please consider this a request - if it is not too much trouble - please release the custom rom without rooting (as close to stock as possible) and provide flashing supersu as an optional step if rooting is desired. thanks.
[Fire TV Android Development] mattgyver:
Does the new bootmenu support the gen1?
[Fire TV Android Development] rbox:
With the new way I create the images, once I release the 5.0.5 image, all you need to do is delete the su directory from the zip before you flash it, and it will not contain root.
[Fire TV Android Development] Iamandrewj:
I've looked at all of your posts and have checked daily on Reddit and this site.

What exactly is holding back the release of pre rooted OS 5?
[Fire TV Android Development] rbox:
For one, people constantly asking about the status. For two, finding the time to be able to properly test everything.
[Fire TV Android Development] jarayn:
Lol
[Fire TV Android Development] rbox:
Currently the only method for downgrading requires root.
[Fire TV Android Development] AFTVnews.com:
You have to already be rooted in order to downgrade. There is no way to downgrade or root version 51.1.3.0 at this time.
[Fire TV Android Development] Kramar111:
Anybody have same situation on bueller-51.1.3.0_513011520-rooted?
[Fire TV Android Development] AFTVnews.com:
I just checked for you and mine is working as expected. On pre-rooted 51.1.3.0_513011520 and 6.0.5.1.1 ClockworkMod recovery.
[Fire TV Android Development] schneid:
I'm fine too.
[Fire TV Android Development] rbox:
I just updated the OP with 51.1.3.0_513011820.
[Fire TV Android Development] {ParanoiA}:
[MENTION=5728225]Kramar111[/MENTION] maybe you need to do a software update to the remote too
[Fire TV Android Development] Kramar111:
Problem was with nonUS locale in 51.1.3.0_513011520. In 51.1.1.0_511070220 all working fine (locale does not matter).
[Fire TV Android Development] alex1301:
I've found something interesting at codeaurora

https://www.codeaurora.org/projects...tion-leads-to-signature-forgery-cve-2014-0973

Will this help us to gain root with the new firmware?
[Fire TV Android Development] {ParanoiA}:
Yes that is known but the ones that know how to implement it aren't sharing too much about it. I've been trying to do some homework on it trying to find out how to boot a custom kernel. Everything I can find just talks about how it's possible but it's a little above my current pay grade.
[Fire TV Android Development] mastafunk:
For those of us that blocked updates early in the game, can we get a flashable image of the "remote update" that we missed... or is that included in the latest firmware?
[Fire TV Android Development] wunderdrug:
It's included with the regular firmware updates. You will see the remote update in the Settings/Controllers (or something like that) menu.
[Fire TV Android Development] rbox:
That has long been fixed.

I plan on implementing a feature in recovery that will modify custom kernels to allow them to boot. I'm shooting for releasing a new version this weekend but that probably won't have it, so maybe the next release after that.
[Fire TV Android Development] {ParanoiA}:
Sounds good. Thanks for all your work. I'm doing it mostly for the learning experience.
[Fire TV Android Development] mastafunk:
Im not seeing anything in there.... how can i verify that i have the latest remote firmware... I blocked everything when i first got the unit in April in anticipation of further development.. flashed the latest firmware when these pre-rooted images became available, just concerned i may be missing the remote update.
[Fire TV Android Development] {ParanoiA}:
It is in the remotes gamepad setting. Go in there and you will find the update. It worked for me
[Fire TV Android Development] Y314K:
Thanks for all the hard work rBox...

Was wondering if using the PreRooted Stock Images can get your device de-listed on Amazon. Wondering because of this post over at AFTVNews...
[Fire TV Android Development] calvano915:
Tested music on one of mine that has prerooted 51.1.3.0_user_513011520 and it plays "purchased music" fine. I didn't check today but every time I go to my devices page in amazon account all three that I own that are all on this prerooted version show up. Sounds isolated to me...
[Fire TV Android Development] Y314K:
Thanks for confirming. That is what I thought. Plan to go to the latest PreRooted FW on mine even before setting up XBMC & other apps.

Update: You were right. I was able to do the update to the latest PreRooted & my account is still fine. Now I can start the process of installing and running XBMC & other apps. Was able to update my remotes FW too.
[Fire TV Android Development] rocket31337:
I'm wondering if we can somehow add location services to the firetv since we can load custom roms. Thanks for all the hard work on this!
[Fire TV Android Development] jmerrilljr2:
Are you serious?
[Fire TV Android Development] mjbxx:
Must be a sense of sheer entitlement going on here. Should just be thankful that [MENTION=3991724]rbox[/MENTION] is taking the time necessary to make root possible for all Fire TV/Stick products.
[Fire TV Android Development] ldeveraux:
That would be enough to put me off development for good...
[Fire TV Android Development] bula1ca:
Thanks god you are not rbox.

Kidding aside, I am sure rbox knows that 99% of us on this site appreciate his hard work.

rbox,

it is hard to ignore these "demanders" but do not let them bother you, when is ready is ready if it is ready.
[Fire TV Android Development] deepasadish:
for those who are impatient, here is a [although 2+ weeks ago!] status from here: http://www.aftvnews.com/the-current-state-of-fire-tv-fire-tv-stick-rooting/

<quote>

I can’t and won’t speculate on an exact timeframe, but will say that being able to root Fire OS 5 with KingRoot will delay things a bit. Rbox told me yesterday that he has TWRP fully working on the Fire TV 1 with an unlocked bootloader. Unlike those that rooted on pre-51.1.1.0 devices, Fire TVs that use KingRoot to root Fire OS 5 will have a locked bootloader, so rbox wants to make it so TWRP can be installed on those devices with the same package. He has figured out how to detect if the device has a locked or unlocked bootloader, so now he needs to port over the method he developed for the Fire TV 2 of installing TWRP on a device with a locked bootloader over to the Fire TV 1. Once TWRP is working on both locked and unlocked Fire TV 1’s, the pre-rooted ROM is trivial.

</quote>
[Fire TV Android Development] mattgyver:
The first rule of Fight Club: don't talk about Fight Club.

The first rule of XDA: don't ask about ETAs.

(^.^)

Thanks for everything you've done thus far, [MENTION=3991724]rbox[/MENTION]. You've done some great work on the gen1 fire TVs!

Sent from my TARDIS
[Fire TV Android Development] BigMatza:
Rbox, I'm looking forward to your TWRP + pre-rooted 5.0.5 for AFTV1. I'm using your current TWRP + 5.0.5 for my AFTV2, and things are going swimmingly. You are a god, my friend!

I have a quick question about my AFTV1, for when it comes time to take this upcoming TWRP+5.0.5: I'm currently on "51.1.4.0_514006420+updated"-- the highest pre-rooted release possible before the "Boot Menu" is required. When your TWRP+5.0.5 is released, will the "Boot Menu" flash become a thing of the past? Will this all be part of the complete TWRP+5.0.5 package?

Thanks,

BM
[Fire TV Android Development] Y314K:
It's already answer here: http://xdaforums.com/showpost.php?p=65759115&postcount=572

You can see a pic of it here via AFTVNews: [IMG="AFTVNews BootMenu Pic"]http://www.aftvnews.com/wp-content/uploads/2016/02/fire-tv-2-root-boot-menu-recovery.png[/IMG]

Can't wait either for the update/upgrade... Hope it's in the testing face now... :cyclops:

Thanks for all your hard work [MENTION=3991724]rbox[/MENTION] ..
[Fire TV Android Development] rbox:
Yeah. It'll all be integrated into the ROM. Recovery and bootmenu.
[Fire TV Android Development] kwiksi1ver:
Wow that menu looks nice. I like the lack of comic sans. Here's to hoping the development for it goes smoothly.
[Fire TV Android Development] albert.r:
+1. Professionally looking boot menu. Not that I care much about looks... Waiting patiently for TWRP release for pre-rooted AFTV1's. Thanks rbox for all your work!

-albertr
[Fire TV Android Development] Y314K:
All in one install thru Rom sounds great. Really simplifies initial install & updates. Less folks getting stuck on one of the steps. At least that is the thought.

I enjoy using comic sans font on things. It's a nice fun font. But this bootmenu is looking great.

Since it uses the same look as TWRP. It will really give our FTV's a full theme look. At least at bootup when going into recovery. Very Pro looks & function.

I do wonder if a keyboard will still be required or if FTV's remote option can be cooked into TWRP ?
[Fire TV Android Development] KLit75:
Sure does look awesome! But I hate seeing this thread pop up with a new post once again being let down.

Just so we're clear this isn't a demand from a self entitled jerk..(maybe just a regular type of jerk) who gets irritated when he sees posts that are repetitive. Normally I'd ignore it but because I have an interest in this thread (like MANY others) I check daily for new posts.

Let's see what we've covered (again)--rbox does excellent work and the recovery on gen 2 looks amazing!

--the new bootmenu seems to be a huge improvement!

--custom recoveries, especially on a device like AFTV, are incredibly hard to produce.

***But luckily for us we have one guy that can deliver. Take him out of the equation and we'd be waiting forever! Let's just patiently (and quietly) wait for that to happen. If you're looking for something to write, do it in the paypal message box when you donate to rbox.
[Fire TV Android Development] rbox:
So I did look in to how the WiFi direct remotes work, and I believe I can get them to work in recovery. That'll be something that comes later.
[Fire TV Android Development] Y314K:
Great, but just to clarify. It is very likely that only the FTV 2Gen remotes will work. Not the non-WiFi direct Gen 1 or FTVS remotes that came before the WiFi direct remotes. Still a BIG step for v2 of the TWRP recovery.

:good: :victory: Thanks RBox...
[Fire TV Android Development] NxtGenCowboy:
Hey [MENTION=3991724]rbox[/MENTION]

Which OS version are you currently working with?
[Fire TV Android Development] jpeg42:
I jump a little bit every time someone posts here and I get an instant notification. And now I am guilty of the same thing. Can we agree to leave this thread for rbox to update when he is ready please?

There is a Q&A thread for discussion here:

http://xdaforums.com/fire-tv/help/qa-prerooted-stock-images-t2919379
[Fire TV Android Development] BigMatza:
I just wanted to say I'm now guilty of this too. But I do feel better getting it out in the open. Does anyone else have any random thoughts they'd like to share?
[Fire TV Android Development] busventinc:
Rbox is working very hard and life gets in the way as well plus amazon keeps coming out with update after update it is no wonder he has not been able to posted anything. So to everyone who is impatient. Give the guy some slack greatness takes time... Thanks Rbox much respect...
[Fire TV Android Development] Y314K:
See my rambling below...

Most long time XDA'rs know & appreciate how much [MENTION=3991724]rbox[/MENTION] virtually single-handedly has done, is doing & will do in the future for the FTV community. And I think RBox has a great attitude when it comes to knuckle head ?'s & ETA. Which as a non-develeoper I've asked [MENTION=3991724]rbox[/MENTION] in the past. I do bet it gets frustrating. Yet in true XDA style. He has always been very open with info & in discussions.

:victory:

That said, here is a knuckle headed ?, Although it comes from a practical side with the new Amazon disabling escalation. And not from an ETA side.

An AIO option for all 1st Gen devices is ideal specially on the developers end. Less branching of releases. And great for noobs that don't read before modding stuff. But seeing how now Amazon has up their game specially when it comes unrooted devices. I am wondering if devices with fully unlocked bootloaders should have it's own branch for TWRP & PreRooted Roms. For one the problems on the unrooted/locked bootloader end can change at a much higher pace then on the rooted/unlocked bootloader side. I was wondering if you are re-assesing if the AIO is the best option overall with the new more aggressive Amazon stance. I am probably unaware of some of the things that come into play. I guess I am basing my opinion on a rumor that TWRP for 1st Gen Rooted boxes with Unlocked Bootloaders was for the most part fully working. But most of the work will need to be done on the locked bootloader &/or unrooted detection.

Guess basically my ? is to branch or not to branch locked bootloaders vs non locked bootloaders. Although is not like branching or not branching them will create more hours in a day.

Just wanted to pick your brain about your thought process how you decide how to approach the development. Specially in such a complicated version of device. Where just about everybody can have a different starting point to update of FireOS 5.

Thanks for everything [MENTION=3991724]rbox[/MENTION] . Would be funny to just get a single word response to all this Blah, Blah, Blah..:silly: