yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] rbox:
I'm not blocking dcp. If you had dcp blocked already, it will continue to stay blocked as long as you don't factory reset. But like I said in the other post, I have put protections against accidently flashing a stock update, so it's not the end of the world. But leaving dcp blocked is the best solution just because it won't be constantly trying to download updates.

Yes, 51.1.0.1 is fine. I probably should have specified that. I just assumed everyone was already on 51.1.1.0.

So right now it's not capable of flashing custom kernels, that will be fixed in the next update. Once I have that, I'll probably release my janked up stock AOSP build. It's garbage, but why not. haha.
[Fire TV Android Development] to0:
So is there no wiping required when installing these stock images?
[Fire TV Android Development] toe-rag:
That is where I'm at... are you planning on a release from that version? (51.1.1.0.)

I've just ordered the $74 sale priced AFTV from Staples - that may be my test platform depending what it comes with. However I would like to do my other (2) AFTVs at some point - and it would be nice not having to do the downgrade step -- ??
[Fire TV Android Development] jocala:
Superuser.apk

Since you're injecting su into xbin yourself, is there another reason you're keeping Superuser.apk in /system/app?

I had it set up to grant all su requests since I didn't want to grab the keyboard all the time. For some reason after installing the 51.1.10 pre-root image, Superuser.apk kept popping up with grant requests, but wouldn't let me edit settings for grant all.

Anyway, I nuked /system/app/Superuser.apk and /data/data/eu.chainfire.supersu

and all is well.
[Fire TV Android Development] rbox:
Correct. No wipe necessary.

If you are on 51.1.1.0 you must downgrade. If you are on 51.1.0.2 or earlier you can skip it.

I had Superuser.apk for the pop ups, but if you don't want it, its not necessary. I'm not quite sure why it wasn't working for you. I tried it and I got a popup, clicked the checkbox and that was it. Why do you need a keyboard? The standard remote works fine for accepting the dialog...
[Fire TV Android Development] jocala:
Does it? For some reason I thought it didn't. Anyway, thanks. Great work you're doing :)
[Fire TV Android Development] sarcoptic:
So what happens if we do a factory reset in clockworkmod before installing the prerooted rom? Will the fire tv still run the initial setup without issue and leave su alone?
[Fire TV Android Development] rbox:
It would be the same as doing the factory reset with the stock rom. So everything should be fine.
[Fire TV Android Development] sarcoptic:
Thanks for the info and kudos to you for kicking some ass!!!
[Fire TV Android Development] sarcoptic:
Also curious to see how your AOSP build turns out. Does amazon have kernel source out as well? Sorry never really done much development but I can see this thing turning into the ultimate android tv box and long surpassing the crappy rockchip and allwinner solutions.
[Fire TV Android Development] rbox:
Yes, they provide source. But really, excluding the UI differences, under the hood their OS is pretty much Stock Android CAF. So you could boot CAF or CM with their stock kernel. I have a pure AOSP CAF build which is pretty broken and has no bluetooth or networking, that I'll try to prepare to be released.
[Fire TV Android Development] sarcoptic:
My main interest in this would be seeing if its possible to get VC-1 playback working 100% or even get bitstreaming for DTS-MA and TrueHD through XBMC. I am using the fire tv as more of a media player box and that is really the only things missing :)
[Fire TV Android Development] wunderdrug:
SuperSU with Pre-Rooted 51.1.3.0

I just installed the pre-rooted 51.1.3.0 provided here. After doing so, I noticed that I can no longer launch SuperSU from the Settings/Applications menu. I see the application in the list, but the "Launch Application" option does not show up. However, SuperSU does appear to function correctly: for instance, I am still able to see the Deny/Grant popups. Is anyone else having the same issue? Thanks!
[Fire TV Android Development] collindv:
I also upgraded from 51.1.0.1 to 51.1.3.0-rooted. I was able to launch SuperSU and see which programs had been granted superuser permissions without a problem.

The problem I am having is that stickmount no longer seems to mount my USB drive. I get a TOAST message saying that it mounted, but the files are not there when I check in ES explorer. When I click unmount I get the exact same message saying that it is mounted.

Anyone else seeing this?
[Fire TV Android Development] toe-rag:
I'm running 51.1.3.0-rooted and stickmount is mounting my USB stick fine ..

and my SU app only shows a force stop option, no launch -- but everything is working with SU privl.

[IMG="usb stick"]https://dl.dropboxusercontent.com/u/9834004/usb_ext.PNG[/IMG]
[Fire TV Android Development] jmandawg:
edDo you know what happend to /system/etc/install-recovery.sh? I flashed 51.1.3.0_513011520 and it's not in there anymore.

I want to hook a mount command into an initscript as early as possible to mount over top of data/data is there another init script i can hook into?

I'm not sure what order they execute in.

edit: nevermind i got it working by renaming my script install-recovery.sh and was able to successfully mount my partition over /data/data and /data/app but it keeps crashing when i try to install a new app.
[Fire TV Android Development] rbox:
That file came from towelroot I believe. I don't install it because Clockwork wants to screw with it.
[Fire TV Android Development] Zetup-EXE:
How about Downgrade to a rootable Firmware (from aftv news)?

Cu...
[Fire TV Android Development] pbanj:
wife just told me it was acting funny and not working.
[Fire TV Android Development] Divine_Madcat:
Hard to say really. If possible, i would -

1) Make sure Netflix is streaming right at all (try it on a computer or phone.. just a different device. If not, you may have a problem with your ISP or router)

2) Reboot the FireTV (i have seen way too many hairpulling issues fixed with a good reboot)

3) Failing that, try to recreate the issue, so you can give us more details (sadly, its a bit difficult to help without an actual symptom. Blocky video is one thing, vs the application force closing all the time).
[Fire TV Android Development] pbanj:
oh i know i was just trying to see if other people where having issues like its a known issue or if it was just my box being funny
[Fire TV Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION]... Never found a response to this... SU seems to work fine but once I upgrade to a PreRooted FW the Launch Application option disappears from the SuperSU app. Is there a way to recoup this... If I remember correctly I even upgraded to the latest Pro version on one of my FTV's but the Launch option was still missing. I would like to be able to go into the grant menu to see what apps I've granted full access to the FTV. Has anybody tried to reinstall the original version that was install at the time of root ???
[Fire TV Android Development] rbox:
You could try deleting the supersu.apk from /system/app and then installing the supersu recovery zip file he provides
[Fire TV Android Development] Skater4599:
I found this too, I was able to fix it by moving it from /system/app to /data/app. The included version 1.94 i believe does work, but if you try to upgrade to newer it still has same issues, just an incompatibility. I have not tried to upgrade to the latest (2.38 or something now) but last I checked the latest did not work even in /data/app. But the current version 1.94 does work in /data/app. :good:
[Fire TV Android Development] mroneeyedboh:
How can you move it from one place to the other?
[Fire TV Android Development] Y314K:
Humn.. Is this the file you mentioned ??

Is there a risk of unRooting the unit when doing this ?? Will I need to go back and grant access to everything again starting with BusyBox ?? Need to understand that more before trying...

---------- Post added at 12:22 PM ---------- Previous post was at 12:15 PM ----------

Seems the version I installed is v2.16 ... What version do you have install [MENTION=3991724]rbox[/MENTION] ??

So are you saying it's as easy as using ES Folder Explorer to move the SuperSU APK from /System/app to /Data/App ??? Will doing this mess up with any of the needed binaries to maintain Root ??
[Fire TV Android Development] Skater4599:
I used file manager but ES file explorer works the same way, you just have to grant it root permissions and mount /system as r/w first. Simple as moving it and no it does not break anything needed for roots or any binaries. very simple fix.

an alternative I read works but have not tried it myself is to use superuser app, but personally i like the SuperSU app and since its so easy to fix I chose to do it this way.
[Fire TV Android Development] Y314K:
Do you have a thread link for this fix.. Would like to read more about it before trying it out...
[Fire TV Android Development] Skater4599:
Sorry I don't, this is just something I did/found that works. But there was a thread on this similar situation, let me see if I can find it and I'll edit my post.

Edit: Here you go, this is where I had originally started looking into it on my FTV's

http://xdaforums.com/fire-tv/help/supersu-t2926119

hope it helps
[Fire TV Android Development] Y314K:
Trying to delete the APK... I already copy it to Data/App but never had to mount /system as r/w.. Right now is only mounted for r. Is this done thru ADB or ?? Tried ADBFire App & thru ES Folder Explorer but it's still only in read mode.. Any help on this would be appreciated..
[Fire TV Android Development] Skater4599:
The only reason to mount /system as r/w is because it needs to MOVED /data/app and not copied, if supersu.apk still exists in /system/app it will still not show a launch option. After moving to /data/app click on it to install it, it should show up, no reboot required. I did this yesterday on all 3 of my FTV's
[Fire TV Android Development] Y314K:
If I install it in /Data/App will that delete it off /System/App ? I choose move to on ES Explorer this time but it seems to just copy the APK to Data/App while still leaving the copy behind.

Who's File Manager are you using. Something doesn't feel right on ES Explorer...
[Fire TV Android Development] Skater4599:
I'm using one by "Cheetah Mobile" from the app store. Ill PM you a link to the apk on dropbox i use, its a free app. I think it used to be from rhythm software or something, either way i'll send it to you, if its leaving a copy behind its probably not moving and only copying due to /system not being mounted r/w. But just a guess with ES File Explorer, I've never used it.
[Fire TV Android Development] Y314K:
For some reason the ES Explorer Root Explorer part has never worked right for me... Wonder if it might be because I don't have the Android Settings.apk installed on my FireTV's yet.
[Fire TV Android Development] IBNobody:
I posted what I had to do to fix it in the other thread.

http://xdaforums.com/fire-tv/help/supersu-t2926119/page3#post57531992

You basically just need to use ADB to wipe out the Superuser.apk that rbox adds to his images.
[Fire TV Android Development] Y314K:
Seems the reinstalled SuperSU took out the old one. It asked me if it could take it out to avoid conflicts.
[Fire TV Android Development] drumst1x:
Like many others, I too noticed that SuperSU doesn't allow you to open it anymore. I'm wondering, is there any advantage to installing SuperSU into system/app instead of data/app? If the answer is no, is it possible for the images to install it, instead of in system/app, directly into data/app? I'm not sure if a custom rom can put anything anywhere other than in system, but just a thought I'm having.

Feel free to correct me if any assumptions are wrong :)

As always, rbox, you're doing a great job over here :)
[Fire TV Android Development] death_entry:
My FireTV is running version 51.1.4.0_user_514006420, can I do anything with this? Root / downgrade etc?
[Fire TV Android Development] Y314K:
Just block future updates & hope for a new method of root in the future.

http://www.aftvnews.com/start/

---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------

RBox is working on this issue.. Hopefully it will be resolved on the next PreRooted FW release... For not moving it to /Data/App is the only recourse...
[Fire TV Android Development] Irish Cream:
I saw on AFTV news that one of the updates may cause XBMC/Kodi not to work... is this true? I wanted to upgrade to a pre rooted firmware but I need Kodi!! :)
[Fire TV Android Development] AFTVnews.com:
That was just a bug with one of the software versions that some UK Fire TVs shipped with. (51.1.4.0_user_514005520) All of rbox's pre-rooted ROMs work with XBMC and Kodi.
[Fire TV Android Development] heyredy141:
[MENTION=3991724]rbox[/MENTION] would we be getting the prerooted stock image for the latest fire tv update?
[Fire TV Android Development] jpeg42:
Just curious what is in there that would be beneficial?

http://www.aftvnews.com/fire-tv-update-51-1-4-2-also-adds-no-new-features-or-ui-changes/

Looks like it was just fixes to the firetv stick if anything.
[Fire TV Android Development] heyredy141:
It heard it fixes something with regard to upscaling videos to 1080p. But not sure if it is fire TV stick specific issue.
[Fire TV Android Development] pbanj:
I think it may fix the issue with Netflix/prime video playback not working when leaving xbmc/kodi running with a video paused. My box still does it but my stick which is on the newest fw doesnt
[Fire TV Android Development] krawhitham:
Will you be doing a release for 51.1.4.3?
[Fire TV Android Development] rbox:
Does it provide anything over what I already have? Ever since they started putting the fuse stuff I err on the side of caution and unless it's something obviously fixed, it's better to just stick where we are.
[Fire TV Android Development] o-I-c:
+ 1 and thanks for all you have done.
[Fire TV Android Development] deepasadish:
fully agreed. don't fix it if it ain't broke!

i guess the path forward is to make a Custom ROM (like CM) that is free of issues!
[Fire TV Android Development] Skater4599:
I agree, Wish we knew more about what amazon changed etc. I've had issues ever since they updated netflix app, the old app would allow the FTV to go to sleep, but the new app it will just log me off of that user and keep the FTV on, I don't like this cause sometimes I'll fall asleep and don't want it to stay on all night! I'm curious if this has been updated/fixed yet. Anyone else can confirm? Or maybe this only happens for me and it works even not on latest firmware?
[Fire TV Android Development] gamer765:
Since the Fire TV is now unlocked, maybe now we can update our bootloaders with the full unlock and use the newer kernels without fear of getting bricked or maybe even more.
[Fire TV Android Development] MadFlava:
Can anyone else confirm this? Not doubting him but Im just amazed there isnt a thread somewhere blowing up about this.
[Fire TV Android Development] rbox:
No. The unlock is dependent on a bug in the bootloader. Basically the bootloader checks the unlock code on boot to verify if it's good. That only passes on the old bootloaders. If you were to update the bootloader, it would not longer think the unlock code was valid.
[Fire TV Android Development] gamer765:
Seems like you don't know who I am. I'm a certain someone who deals with Pandora. Google me.
[Fire TV Android Development] rbox:
This is the unlock from the HDX. jcase already confirmed it works on the Fire TV. There is some discussion in the partial unlock thread.
[Fire TV Android Development] gamer765:
Yup, I tested it myself and posted proof that it works.
[Fire TV Android Development] MadFlava:
Nope.. I dont. Maybe you should Google me too.
[Fire TV Android Development] KLit75:
I've had issues on one of my aftvs since downgrading from 51.1.4.1 w boot menu to 51.1.4.0 no boot menu. It boots up to a snowy/static screen to hanging Amazon yellow and black. Figured out if you pull the usb drive it will boot normally and it performs very well. It just won't sleep and there's no way for it to sleep because on home screen "Display" takes you to "screensaver" but clicking on it just flashes a blank window with no options and only the home button gets me out.

It's VERY possible this issue is related to issues I had with a launcher and pushing advanced settings that enable thumbs to usb. This also involves deleting textures13db in kodi but I don't see the link there. I've done it many times before.

I'm hoping for a theory on what might've gone wrong and also I'm uncertain of what I should do here? I believe flashing boot menu then the latest firmware will be ok but I'm holding off because I'm not certain what's going on here. I think it'd be smart to have rbox boot menu but a little worried my next move could mess things up to the point where I can't access recovery. Any ideas would be greatly appreciated.
[Fire TV Android Development] nilisco:
This made me laugh. Gamer765, internet badass, totally well known.

Any news on updates to the prerooted stock images? I'm assuming there are patches/fixes even if nothing is in the changelog, or has someone actually diffed the binaries and discovered nothing has really changed?

Appreciate the hard work.
[Fire TV Android Development] rbox:
I just updated the OP with 51.1.5.0.
[Fire TV Android Development] Skater4599:
Thanks rbox! Does your xposed module v1.3 still work on this update to hide menu items and use Kodi as the launcher?
[Fire TV Android Development] rbox:
It appeared to still work.
[Fire TV Android Development] Sizzlechest:
Do you disable the automatic update or do we need to do that after we install it?
[Fire TV Android Development] ~Craig~:
Thanks for posting 51.1.5.0, Quick question to anybody who knows.

Now that this includes USB support do we need Stickmount anymore? Do I need to uninstall it before updating?

I have heard that it only supports FAT32 which is no good (4GB file limit) so I guess I have kinda answered my own question in that I still need Stickmount as my drive is NTFS :eek:

Basically what I should ask I guess is can we have this pre-rooted version (which has USB support) and still have Stickmount installed?

Thanks

Craig
[Fire TV Android Development] death_entry:
Wish I could flash this on my UK pre efuse unrootable version ;(
[Fire TV Android Development] goes_like_hell:
[MENTION=3991724]rbox[/MENTION]: Thanks for your doings ! Great job !!!

I have here an fully rooted firetv with rbox-boot-menue and i want to update to 2820

Do i have to block updates after updating like that "pm disable com.amazon.dcp " and is this permanent ?

Sorry for that kind of newbie-questions.

regards

goes like hell
[Fire TV Android Development] will4958:
Installing new update

For those of us who applied the MountDataToUSB option, do we need to apply the revert flash before updating to the newest update? Also, do we flash this in Recovery? I know this may sound like a noob question, but just wanted to be sure.
[Fire TV Android Development] Skater4599:
[MENTION=486208]Goes[/MENTION] like hell - Yes you will want to disable the dcp after upgrading to this just like all the others, also you will need to reinstall xposed framework as rbox has stated before. While custom recovery provides a failsafe even if you don't disable dcp it will download and try to update which is just a waste.

I've never used MountDatToUSB option, but I think it would be up to you keeping in mind amazon's official USB support only supports 128GB max of FAT32 ONLY, is this enough for you?

Yes this is flashed in recovery, make sure and read the OP and second post providing amazing guides by AFTVNews. Everything you need to know is there! :D rbox and AFTVNews are awesome like that!
[Fire TV Android Development] will4958:
Thanks for the quick reply. Actually, I'm using an 80 gig drive with a 50 gig ext4 partition, and one at around 30 gigs or so, so the 128 gig limit wouldn't be a problem. I'm only using the drive for any games I download. I think I read this new update uses the FAT32 file system, so I could just make a backup of my apps and reformat the drive to a FAT32. I'm familiar with flashing new ROMs in recovery mode, done it more than a few times on every Android phone I've had, but I'll ask the user who posted the tools for those who didn't want to wait for Amazon to unlock the USB port what he thinks is best as far as removing the MountDataToUSB and other such flashables. Thanks again for the help.
[Fire TV Android Development] dbaseii:
I have plugged in a 2tb drive and all seems to be working.
[Fire TV Android Development] drumst1x:
First, thanks for the update, [MENTION=3991724]rbox[/MENTION]! Your hard work and speed with updates are much appreciated, as always.

Next, I want to second this question. I'm in the same situation, have a 2 TB ext HD formatted to NTFS containing files > 4GB (HD movies). Does anyone know if stickmount still works after this update? Not sure why it wouldn't but would like some confirmation.

Thanks! :)
[Fire TV Android Development] Skater4599:
This is good to know, thanks for the usefull info!

I am going to install this tonight on one of my rooted FTV's. Stickmount is something im curious about also, I can't imagine why it would not work still also but who knows right? I'll report back if someone hasnt already later.

I'm also looking into rbox's xposed module, I want to know if the long press home menu to sleep/mirror/etc is overwritten with the xposed module.
[Fire TV Android Development] will4958:
Got a question I should've asked ealier... with this new update and its ability to let us use external storage devices, does it give you the option as to where you want to download an app, more or less similar to Windows? Has anyone tried to mirror a non-Fire HD Android device with the new update, and if so does it work? And lastly, has anyone confirmed that side-loading apps no longer works with the new update?
[Fire TV Android Development] dbaseii:
I can confirm that side loading still works. Apk's can also be loaded from external drive.
[Fire TV Android Development] patt2k:
Would love to have newest pre-rooted but I am afraid I can brick another FTV lol.
[Fire TV Android Development] Skater4599:
From what I've read here, it does give you the option where you want to download the app to internal or USB, it also has the option to move to USB storage, similar to android phones and move to sd card option. Mirroring seems to be hit or miss on the older updates, it worked once for me then failed 95% of the time after that (This is my personal experience, YMMV), there were also bugs with windows 8.1 miracast that have been confirmed to be working, but the best bet is to just test.

Sideloading works 100%, its been confirmed
[Fire TV Android Development] nijhawank@yahoo.com:
@rbox list of changes from stock fw

hi [MENTION=3991724]rbox[/MENTION] would it be possible to get a list of changes that you perform to the stock 51.1.5.0 to get this prerooted rom. I ask this to understand specifically do you have to recompile the kernel from the available amazon source or do you use stock kernel but just patch protections and/or inject the su stuff. Or if you use stock kernels from an earlier version of rom and if this the case, does using an earlier kernel results in loosing some of the kernel layer enhancements like improved graphics, performance and so on.

Thanks in advance.
[Fire TV Android Development] rbox:
I use the stock kernel but unpack, remove the fuse stuff, and repack it. As for the ROM itself, I remove all the firmware and the recovery patching stuff.