yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Y314K:
Has anybody had FTV upgrade & then reboot issues... A couple of folks over at AFTVNews.com has posted partially bricked FTV's after the update + a reboot.. But it seems to be more of the exception then the rule...

I've asked them to post their problem here... One of them was able to alt+i+printscreen in order to downgrade.... So it's not a full on brick like last time... Could be some fluke on their FTV's....

Look for Chris & Ben's post here: http://www.aftvnews.com/pre-rooted-51-1-5-0-fire-tv-custom-rom-released/#comment-116980

And thanks again.. Great lightning fast work RBox....

Update: (Seems to be a problem for folks that had installed non RBox FW before the latest update..)
[Fire TV Android Development] Luxferro:
If you guys have fully unlocked bootloaders, they most likely aren't bricked.

Quoting myself from my aftvnews post:
[Fire TV Android Development] AFTVnews.com:
The issue is not caused by the pre-rooted 51.1.4.3_514020320 ROM, or at least not solely caused by it. There seems to be another factor that I haven't been able to narrow down yet due to the small number of people who are experiencing the issue.

My tester Fire TV had the pre-rooted 51.1.4.1 ROM with rbox's boot menu installed. I then installed realbbb's pre-rooted 51.1.4.3_514020320. I then installed the pre-rooted 51.1.5.0_515020820. Everything is working fine for me. The bootmenu loads as usual, as does recovery and the main Fire TV interface. I've powered down the Fire TV several times without any issues, so there must be another factor involved that's causing the issue. Also, one of the commenters on my site, Chris, says he experienced the partial brick yet he never installed the pre-rooted 51.1.4.3_514020320. He jumped from 51.1.4.1 to 51.1.5.0.
[Fire TV Android Development] bula1ca:
Totally agree. I had no issue at all.

---------- Post added at 04:07 AM ---------- Previous post was at 03:58 AM ----------

What cwr_filename.img are you referring to? Thank you
[Fire TV Android Development] Luxferro:
It was an example for whatever name the cwr recovery image file is.
[Fire TV Android Development] bula1ca:
Thank you. Does this image has to be same CWM version was installed previously or any version will do it?
[Fire TV Android Development] Aobeta:
How to you do a factory reset on one of these pre-rooted versions? I upgraded to Pre-Rooted 51.1.5.0, but I am having some issues, so I wanna see if it will fix it to just factory restore but not lose the root access obviously. Should I do this through cwm recovery, or in the fire tv menu?
[Fire TV Android Development] yazyazoo:
Hi,

I think I just bricked my box. I was on 51.1.4.1_514013920 fixed and was trying to updated to rbox newest rom. I thought that since I had already installed the boot menu before for the 51.1.4.1_514013920 rom that I wouldn't have to do it again.

So I just pushed the newest rooted rom to sdcard and loaded it with CWM without going thru the Boot menu. Is running the boot menu needed Right before any rom install? I thought once you have the boot menu to install before you were free to use cwm on any install.

Anyways I get a white Amazon logo on boot then it hangs with the white LED blinking slowly. Tried to ADB back in but doesn't work.

Is there a way to fix this?

Thanks.
[Fire TV Android Development] freezer2k:
Weird,

Updated to rbox's latest ROM two days ago. Was running 5.1.4.0 prerooted rbox before that.

This is what I did:

1. Reboot to recovery via "adb reboot recovery"

2. Sideload the update via "adb sideload latest_prerooted.zip"

3. Select reboot in CWM

Worked like a charm.

So I did not even enter recovery via the Boot Menu.
[Fire TV Android Development] schybiorz:
also i did so, and it work like charm.

no problems at all. unlocked bootloader still presists. also doing factory reset after update works like it should.

so there might be another problem you guys have.
[Fire TV Android Development] yazyazoo:
I did have to re do my bootloader because when I checked it, I wasn't getting the root response. I updated busy boz and just redid the boot loader unlock. Maybe I should have deleted the old file then flash it again.

UPDATE: OK somehow I got back into CWM! What should I do now? I don't have a recovery .img. Should iI do a wipe and factory reset? I'm going to leave my FTV in this mode until I know what to do.

I have another FTV. Can I somehow get a recovery img from that and clone it to the bricked one? Is the backup in cwm file the correct one to use and then go to bricked one and used restore option?

Thanks.

I still have to try the USB keyboard. I only have the wireless k400 but not sure the exact key presses for recovery.
[Fire TV Android Development] bula1ca:
Install through CWM 51.1.4.0_514006420_updated.zip, this will erase boot menu and all its requirements now take some time and read and re-read before proceeding ahead with updates again.

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

http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/

http://www.aftvnews.com/how-to-install-a-kernel-boot-menu-on-the-amazon-fire-tv/

http://www.aftvnews.com/how-to-install-and-setup-busybox-on-the-amazon-fire-tv/

http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
[Fire TV Android Development] nijhawank@yahoo.com:
Hi [MENTION=3991724]rbox[/MENTION] do you have any plans of making available the latest version prerooted. I understand that it is a minor update but it seems it has quite a number of fixes.
[Fire TV Android Development] rbox:
All I heard about was some tweak to the Pictures. I also heard another update with a version jump is due soon. So unless there is a huge pressing reason for this update, probably not.
[Fire TV Android Development] tony_2018:
Nice work on the updates. Where can I go to find what firmware rev's are rootable? I am going to look for another fire tv device.
[Fire TV Android Development] rbox:
http://www.aftvnews.com/
[Fire TV Android Development] krawhitham:
I'm thinking is also has the X-Ray for Movies and TV Shows feature.

According to Amazon the Fire TV now has that feature, I'm using 51.1.5.0_515020820 and the feature seems to be missing
[Fire TV Android Development] AFTVnews.com:
I was told about the X-Ray feature ahead of time and told rbox it was best to wait on a new pre-rooted version since the X-Ray feature didn't seem to be included in the 51.1.5.0_user_515030720 update. That's what rbox is referring to in his comment. Turns out it was in fact included with the 51.1.5.0_user_515030720 update, but Amazon just left it dormant until today.
[Fire TV Android Development] rbox:
I'll try to do an update tonight.
[Fire TV Android Development] drumst1x:
As always, you both rock :)
[Fire TV Android Development] rbox:
I updated the OP with 51.1.5.0_515030720.
[Fire TV Android Development] will4958:
Cool. Does this build work with the MoveDataToUSB flash? I tried the build just below the one you just posted, and though it offered a few new features such as external storage, it didn't provide a way to install large data packs for games directly to an external source; e.g. Asphalt 8 Airborne's request to download a 1 gig or so data pack and not having the option to choose where it goes.
[Fire TV Android Development] bula1ca:
You need to install it to SD first and then transfer to extUSB (this is an option in settings for every app ).

---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------

Thank you
[Fire TV Android Development] will4958:
I know I can transfer it, and did try before I switched back to the build I was on before when I tried the last build a few weeks ago. It's the way the game is designed that won't let you install the data pack to a different location. On the other hand, I wouldn't mind being proven wrong, since the last time I tried it there were some things I liked about it.
[Fire TV Android Development] sacwoo:
I haven't updated to the latest 0720 yet, traveling and I forgot my keyboard.

With that said, i am on the original 1.5 update and one thing I noticed is when the fire TV is sitting idle, it reboots itself straight into CWM.

I am not sure why and if the update will fix this but is there a log file I can check to see the cause and troubleshoot the issue?
[Fire TV Android Development] LiquidXed:
If im coming from 51.1.4.1_514013920+fixed and want to update to 51.1.5.0_515030720 do i need to update to 51.1.5.0_515020820 first?
[Fire TV Android Development] rbox:
No.
[Fire TV Android Development] LiquidXed:
Thank u
[Fire TV Android Development] dhorlo:
Music menu choice not working

I have a rooted FTV that I just flashed from 51.1.4.1_514013920+fixed to 51.1.5.0_515030720. All seemed to go well but I have no access to the music menu on the FTV UI. Trying to select it causes the selection to jump to the games menu. All others menus seem to work fine.

I primary use my FTV as the platform to run Kodi on. I play my music from within Kodi so I don't mind the loss of the FTV's UI music menu. But I was wondering if anyone else was having this issue?
[Fire TV Android Development] sirxdroid:
When upgrading to a new rooted ROM, is there any user data loss, besides anything that may have been added to /system using adbFire?

And what is the correct procedure please to update the ROM if I'm already on a rooted ROM and have the boot menu installed?
[Fire TV Android Development] Axecaster:
I think my Fire TV Stick also exhibited the music menu jump. Not sure if I'm confusing it with my full/regular Fire TV on the last October update, but I think the issue corrected itself after a while. I'll check again tonight.
[Fire TV Android Development] drumst1x:
I am not sure about data loss, but i think these are all fairly minor updates (version-wise), so data doesn't wipe. Don't quote me on that, though.

As for procedure, check here:

http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
[Fire TV Android Development] Jboo:
Is anyone having issues with their mouse? My usb mouse and my bluetooth mouse are not working. No cursor on the screen. I also deselected USB debugging but no luck. I even did a factory reset from CWM and reinstalled the latest firmware and nothing. Any idea what could be the issue?
[Fire TV Android Development] Jboo:
Delete
[Fire TV Android Development] rbox:
The OP was updated with 51.1.5.3.
[Fire TV Android Development] krawhitham:
Thank You

Do you have a md5sum for it?
[Fire TV Android Development] rbox:
That would have been helpful. I updated the OP.
[Fire TV Android Development] krasny2k5:
Amazing work rbox, thanks!!!!
[Fire TV Android Development] cocoon4u:
update works perfect, thx for your work!
[Fire TV Android Development] dhorlo:
Music menu choice not working (resolved with latest stock image)

FYI

Flashing the latest stock image, 51.1.5.3_515040320, seems to have corrected the FTV UI music menu issue. The music menu is fully functional now for me with this new stock image.

Thanks rbox.
[Fire TV Android Development] notreally:
For me at least, I can longer add Kodi and SPMC to Recent Menu after I uninstall and reinstall/buy app/deregister firetv/register.

Am I the only one? If so, that's enough for me to stay locked in to the old version.
[Fire TV Android Development] ars_92:
Hi guys, I am currently on 51.1.4.0 and have already:

fully unlocked bootloader

installed boot menu

running cwm 6.0.5.1.4a

Im trying to install firmware 51.1.4.1 using cwm, after copying the file to the firetv, but the following error shows

as you can see even the latest firmware shows the same error , but im obviously not trying to downgrade but actually upgrade. What can I do to fix this? I dont think using an older recovery is a good idea right? as I read 51.1.4.1 needs 6.0.5.1.4a installed.

EDIT:update.zip is the 51.1.4.1 file renamed
[Fire TV Android Development] rbox:
You aren't using a file from my OP, that's for sure. You cannot installed signed amazon updates with CWM.
[Fire TV Android Development] ars_92:
Oh god that's what you get for trying to install something 3am in the morning after a long journey cross country.

Im so grateful that the assert saved me from bricking the device lol. I'm surprised that i went thru the process of updating recovery,installing boot menu and and unlocking the bootloader without screwing up lol.

Btw, i can update to 4.1 and jump straight to 5.3 right? Or can i go straight from 4.0 to 5.3?

Btw thx rbox for the hint!
[Fire TV Android Development] rbox:
As the OP says, you have to flash 51.1.4.0, then bootmenu, then you can flash the latest.
[Fire TV Android Development] ars_92:
Update to 5.3 went well,thx again!
[Fire TV Android Development] long2know:
I already have 51.1.4.1 plus bootmenu installed. Is it possible to factory reset and erase /system w/ CWMR prior to flashing 51.1.5.3 without messing things up?
[Fire TV Android Development] rbox:
Well /system is always erased when you flash a new version. And you can factory reset to your hearts content.
[Fire TV Android Development] krawhitham:
Thank You
[Fire TV Android Development] dk1keith:
I had a question about that...I have my internal swapped to an ssd drive. When I revert the swap the internal space only shows 1.3 gigs on the fire tv without any user apps installed. Even when I do a factory reset from CWM recovery it still doesn't show the correct storage? it still shows 1.3 gigs

thanks
[Fire TV Android Development] rbox:
Factory reset in recovery isn't going to touch /data/media,so if you have files in there, that'll take up space. You can do the option to 'Format /data' or 'Wipe /data' or something like that, somewhere in recovery. That'll completely wipe out /data.
[Fire TV Android Development] KLit75:
New update is being rolled out with bug fixes. I posted in Q&A a few days ago that my boxes are behaving strange since the update. But that was also the same time I started using prime. Other than that I haven't done anything to it and mostly just been watching prime/Netflix. Seems no one else around here is having issues with the new firmware. Do you think you're going to make a prerooted ROM? I can always downgrade if I don't pin point the issues...
[Fire TV Android Development] rbox:
I need to wait until the update zip URL is found for it. [MENTION=5957312]AFTVnews.com[/MENTION] usually gets it to me when he finds it.
[Fire TV Android Development] KLit75:
Great! Thanks a lot. Wasn't looking for an eta, just wondering if you were planning to do this version. Haven't read much about other users having issues but when I heard a new version was coming so soon it made me think the problems I've been having were related. Looking forward to it!
[Fire TV Android Development] rbox:
I updated the OP with 51.1.6.1
[Fire TV Android Development] KLit75:
[MENTION=3991724]rbox[/MENTION]

Due to a careless mistake I installed wrong busybox then the busybox free app wouldn't install. Now have root that's not functioning properly.

If I reflash the latest firmware will the supersu apk get overwritten so I can access su setting? Or do I need to wipe/factory reset in cwm?

I think its the latter, but if I have a nearly identical setup on my other AFTV (preroot fw, unlocked bootloader) can I make a backup with titanium on the working aftv , store it on dropbox then restore data to the AFTV I just wiped?

I'm really just looking for the simplest way to fix supersu. If I could open supersu I'm pretty sure I could just grant apps the permissions they need but not 100% certain. Thanks.
[Fire TV Android Development] rbox:
You could try reflashing, but you might need to factory reset if that doesnt work.
[Fire TV Android Development] Squalll13:
Stupid Question.

If I want to clear data/factory reset, I would need to flash a new pre-rooted ROM right (since it gets wiped along with it). But since I need the .zip somwhere to "install from zip". Where do I put it now? I was thinking of external, but there's only 1 USB slot and that's for the keyboard to control the recovery page.
[Fire TV Android Development] rbox:
Factory reset doesn't touch the rom...
[Fire TV Android Development] KLit75:
I'm very surprised this didn't work--factory reset

Busybox still gives " There was a problem opening a shell with root access. this is either being caused by superuser/supersu or by device being improperly rooted..."

What also threw me was at no point has the supersu popped up asking for root rights on anything. I'm almost certain after factory resetting in the past I needed to do this.

Not sure where to go from here. Is there a specific su app and version of it that I can substitute to get access? Or is there something I can delete in system that will make the root requests come up again?
[Fire TV Android Development] rbox:
As I said... you might need to reflash...
[Fire TV Android Development] KLit75:
Oh. My apologies but are you referring to the ROM or supersu zip in recovery? Its been so long I don't even remember if that is something we have to flash. I'll dig into the guide again. Thanks.
[Fire TV Android Development] rbox:
The ROM is the only thing to flash. All my images come with supersu.
[Fire TV Android Development] Squalll13:
Thanks. I guess it was a stupid question indeed.

Last one. Factory/Data reset removes almost everything. Do I NEED to reinstall the superuser apk, towel root, and busybox to maintain my "current" pre-wipe l functionality?

Thanks again for the patience
[Fire TV Android Development] rbox:
My roms come with superuser and has been stated like a billion times, factory reset has nothing to do with root. If you installed busybox in /system, it'll still be there. If it's in /data, it'll be gone.
[Fire TV Android Development] KLit75:
Yep. That fixed it. Thanks again.
[Fire TV Android Development] rbox:
I have updated the OP with 51.1.6.2.
[Fire TV Android Development] mckinsey01@gmail.com:
netflix aip-701 error

I have three fire TV's running the latest pre-rooted ROM ( 51.1.6.2_516011120 ). On one of them, Netflix runs fine, but on the other two whenever I try to play a video I get the aip-701 error (can't play video). I have done factory resets and moved the boxes to the Ethernet link where the working firetv is and I get the same error. They all have the same CWM, boot menu, and are unlocked. The Netflix diag tool shows all green for all servers. I have tried another Netflix user account and even moved the firetv to another house that uses a different internet provider. All other apps work fine and stream video without any problem. In the past I have had no Netflix issues.

I have tried running the bueller-51.1.6.0_516009820-rooted.zip

and bueller-51.1.5.0_515030720-rooted.zip and there was no change.

Any ideas?

Thanks for reading,

Scott
[Fire TV Android Development] deepasadish:
i posted this in Q&A but did not receive a reply:

http://xdaforums.com/fire-tv/help/complete-factory-reset-device-rbox-pre-t3193162

can you please tell me, after installing latest rbox ROM from here, how can I do a clean factory reset and start fresh. basically i want to get rid of towelroot, etc, that I presume are not needed anymore, since your ROMs are prerooted. I would also like to wipe the data partition, if that won't cause a problem. thanks.

on a nexus device (say), i would wipe everything from TWRP and that would do it. what is the equivalent here? thanks.

edit - also, will I have to disable the amazon update apps? thanks.
[Fire TV Android Development] freezer2k:
I _think_ the regular factory reset from within FireOS does still work with the prerooted images, and you will also keep root afterwards.

If I remember correctly, Ive done this several times successfully.

But better have this confirmed.
[Fire TV Android Development] Skater4599:
I had this same question some time ago and was able to find GREAT info on [MENTION=2453972]aft[/MENTION]Vnews site, which if you don't already read, you should its the best site for AFTV. Heres the link

http://www.aftvnews.com/factory-reset-on-amazon-fire-tv-and-fire-tv-stick-explained/
[Fire TV Android Development] JediSooner:
Hey, rbox... will you be uploading pre-rooted 51.1.6.3 soon? I'm anxious to flash this to see if it fixes Netflix for me. I've tried absolutely everything to fix it, but no luck. I tried 51.1.6.2 but had to roll back because of the HDCP blank screen issue. Thanks!
[Fire TV Android Development] rbox:
I just updated the OP with 51.1.6.3 :)
[Fire TV Android Development] JediSooner:
Thanks, I appreciate the quick response!
[Fire TV Android Development] JediSooner:
Has anyone had luck flashing this? I've downloaded from 2 different browsers, pushed by ADB, but get the dead Andy within a few seconds of flashing. rbox, can you check the zip to see if the issue is there? I have to run out, but a little later I'll put the zip on a thumb drive and see if it'll flash after copying it to the sdcard that way.
[Fire TV Android Development] rbox:
I flashed it. Seemed fine. Did you check the MD5? Also, looks like others flashed it fine. Check the comments: http://www.aftvnews.com/pre-rooted-51-1-6-3_516012020-fire-tv-custom-rom-released/
[Fire TV Android Development] JediSooner:
Sounds like it's on my end. I'll check the MD5 and go from there. Thanks!

Update... kinda weird, but the MD5 didn't check out with the zip I downloaded twice from my Surface 3, so I downloaded it with my Note 4 and it worked - MD5 matched and flashed just fine.

Update 2... booted up the first time and I still get the HDCP blank screen! The most recent version that works with my AVR is 51.1.60.

Update 3... downgraded to 51.1.60... no HDCP blank screen issue, but Netflix still won't play. I just revisited this thread, but I followed those instructions to the T after Netflix stopped working out of the blue, but with no luck.
[Fire TV Android Development] jim16127:
Wow still a blank screen issue? Hmmm...your the 1st I've read that it didn't cure it. It definitely cured it for myself. Interesting...would you post the TV make and models that are still giving you issue?

http://www.aftvnews.com/recent-fire-tv-software-updates-causing-blank-screen-issues-related-to-hdcp/
[Fire TV Android Development] JediSooner:
I'll need to get some time to bounce around to a few different TVs in the house, but where it has been playing fine (until the blank screen issues) is connected to my Yamaha HTR-5063 (AVR) and Samsung UN55C7000 (TV).
[Fire TV Android Development] KLit75:
[MENTION=3991724]rbox[/MENTION] sorry if you mentioned this already and i missed it but have you been able to determine if you can make prerooted roms for OS 5?

I feel like aftv 2 isnt worth buying but I am thinking of switching to nvidia. If i can keep root, get the new os and still have prime Id rather stick with aftv.
[Fire TV Android Development] rbox:
Yes. I believe I have everything working quite nicely. Need to fine tune a few more things. I'm probably going to wait until the final version of OS 5 starts rolling out though.
[Fire TV Android Development] mattgyver:
Odd issue - Has anyone else lost root when they updated to 51.1.63? I upgraded, and went to check for busybox updates, and it said it couldn't verify root. I only update using the prerooted images, do in not sure what's going on. I have SuperSU 2.1.4 installed but I can't open it. Anyone recommend a different superuser app?

Sent from my TARDIS
[Fire TV Android Development] xenoglyph:
seems okay over here...
[Fire TV Android Development] KLit75:
Had a similar issue a month ago but it was my doing. I installed the wrong busybox and it messed things up. Long story short, i reflashed rbox's firmware then tried busybox again and it was fine.

Fyi--supersu doesnt open but it works fine. Just be ready for the prompt to grant it access.
[Fire TV Android Development] mattgyver:
I was able to adb shell, too. That's what confused the heck out of me, since busybox went weird. I ended up installing CWM's superuser app. It's working great so far, and the second I installed superuser, I was able to install the latest busybox.

Sent from my TARDIS
[Fire TV Android Development] ImCoKeMaN:
Is OS 5 stable enough for a pre-rooted version now? I'm not really having any issues with my current setup, but always excited for that big upgrade for some reason =)