yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] detroitlions:
I am on 5.2.1.1 and followed all the steps. My only issue is anytime I try to download an app, I get a message "Download Failed". When I try and access Netflix or another installed app it says "App not Found. The app you are looking for could not be found". I am able to access Amazon Prime Videos without any issues. Any advice would be appreciated. Thanks!
[Fire TV Android Development] sjors86:
My fire tv stopped working out of the blue, I see boot menu and after that my screens stays kinda grey. So i'm now trying to flash the lastest rom, i'm currently on CMW 6.0.5.1.4a, I downloaded bueller_recovery_v2.zip and bueller-5.2.1.1-rooted_r1.zip and pushed both to my device.

I tried to run recovery zip, but it fails [IMG="error"]http://i67.tinypic.com/2chlzfa.jpg[/IMG].

Anyone knows what i'm doing wrong and supposed to do now?

ANd how can I install gapps if I get this working eventually?
[Fire TV Android Development] xenyz:
Check your free storage? Otherwise try signing out of your Amazon acct and sign back in, and finally just do a factory reset if nothing else works.

It's not a flashable zip; it's actually a script you run from a root shell. Follow the OP instructions carefully.
[Fire TV Android Development] sjors86:
I can't get into adb shell for some reason, thats why i tried to do it through recovery

[IMG="error"]http://i68.tinypic.com/2q16wxj.png[/IMG]

My fire tv is in recovery, when connected through adb, tried to boot into bootmenu (from recovery), but it's just stuck at "Amazon" then.
[Fire TV Android Development] xenyz:
If you're in recovery and using ADB shell then there is no superuser. I really doubt rbox has tested installing TWRP from CWM.

My best advice is to do the steps properly: find out if you have a locked or unlocked bootloader , use CWM recovery to install Fire OS 3 , use root in Fire OS 3 to install TWRP, use TWRP to install Fire OS 5.
[Fire TV Android Development] sjors86:
"Find out if you have a locked or unlocked bootloader"

How do I do this, as I can't get into bootloader (stuck at Amazon) if I try to start it from cwm recovery.

And I found this:

So I think su should be possible?

"Use CWM recovery to install Fire OS 3"

So this I do install as a zip file from CWM?

"Use root in Fire OS 3 to install TWRP"

what/how do you mean this?

"use TWRP to install Fire OS 5"

Again install zip from recovery?
[Fire TV Android Development] xenyz:
Step one is reinstalling Fire OS 3 and getting it going, so you can follow the other steps properly.

I can't really help much more, you're not at all following the instructions that rbox has worked hard to provide. Everything is there, just slow down, don't skip anything and you should get it going.
[Fire TV Android Development] detroitlions:
Thanks xenyz! Signing out of my Amazon account and back in did the trick.
[Fire TV Android Development] sjors86:
I'm not trying to skip, but just get stuck at certain posts.

I have flashed to FireOS 3, now I need to install TWRP

As stated before I can't run as SU, I get error

"su: not found"

and when I try

"dd if=/data/media/0/bueller-twrp_3.0.0-7.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"

without su, I get another error:

"dd can't open '/data/media/0/bueller-twrp_3.0.0-7.img' no such file or directory"

I did push it to my sdcard as described by the steps

it seems that code in manual isn't correct, should be dd if=/data/media/bueller-twrp_3.0.0-7.img instead of dd if=/data/media/0/bueller-twrp_3.0.0-7.img
[Fire TV Android Development] xenyz:
From what I can see I think you are still trying to install TWRP from CWM recovery adb shell, again I am doubtful this will work as the recovery partition is in use!

You must get superuser working in Fire OS 3 adb shell to install it properly.
[Fire TV Android Development] sjors86:
Nope, the device was allready running twrp by that time, and wasn't able to run su in twrp either (which by the manual, should be able), so I tried the command without su and didn't really get errors. So think that worked, just booted into fire tv and that worked aswell

Just trying to figure out how to get google playstore (gapps) on the fire tv
[Fire TV Android Development] darrenph1:
So I have installed the your latest Prerooted Rom on a AFTV 1. Everything works fine EXCEPT I can't get SU access to work. I see it in the applications but its not working right. Anytime I side load busy box it says there is no SU access. I've tried side loading the SU apk but it just tells me its already installed. Same thing with hidemyroot, it says no SU access. i have installed the sdcardfix through TWRP also. What am I missing?

Thanks!

EDIT: OK I reinstalled the rom via TWRP and all is OK now. Thanks for this!!!
[Fire TV Android Development] jj^2:
Can someone explain why we want to use 5.1.4 version htat has the efuse in the kernerl. AFTVnews did a serial check to version I believe I am on 51.1.1 or 51.1.2 per this information.

NEO3D thanks for adding ubuntu desktop usb info. for us linux newbies. Thx [MENTION=6927761]aftv[/MENTION]news [MENTION=3991724]rbox[/MENTION] [MENTION=763587]Neo3D[/MENTION]
[Fire TV Android Development] filon:
Dear all,

I'm sorry if I'm duplicating a question. Searched but wasn't able to find any meaningful answer.

For a couple of years my FireTV1 was running with a fully unlocked bootloader, latest CWM, rbox Boot menu and 51.1.4.1_514013920 fixed ROM.

With upgrades of SPMC, a video got jittered and I started an upgrade.

I successfully installed TWRP Image 3.0.0-7 and then 5.2.1.0 r1. Everything went smooth and the system was running for a couple of days.

The only problem was missing xposed framework.

So, I downloaded xposed-v80-sdk22-arm64.zip and XposedInstaller_3.1.1.apk to SD card. Updated Busybox. Removed old APK and rebooted to recovery.

From this point on, my FireTV almost dead. No power LED, nothing on TV, not pingable on old IP.

Tried to boot to recovery with ALT-i-PRTSCN, remote buttons combination... No luck.

When connected with A-to-A USB mounting disk with image folder.

Nothing while fastboot devices. ADB to old IP failing.

Is there any way back?

Thanks in advance.
[Fire TV Android Development] filon:
Why not make a disclaimer?

I found rbox's instructions on recovery at Post #676. I appreciate everything rbox doing for us. Just wondering, if so many folks following the step-by-step instructions and failing with soft brick, shouldn't be a disclaimer created in OP?
[Fire TV Android Development] filon:
Successfully recovered.
[Fire TV Android Development] rbox:
Yes. http://www.aftvnews.com/software/ has some notes on each version.
[Fire TV Android Development] jmandawg:
So i'm guessing there's no way to modify these zips before flashing without knowing how to bypass the signature check?
[Fire TV Android Development] rbox:
As long as you don't touch the boot.img you can do whatever you want. The next version of recovery will allow you to flash modified boot.imgs.
[Fire TV Android Development] jmandawg:
Thanks. I just added/modified some files in system/etc and it wouldn't flash... I'll try again, I used winrar, but maybe it changed the compression type when i added files.
[Fire TV Android Development] rbox:
What error are you getting?
[Fire TV Android Development] dbdoshi:
I updated my new FTV to the latest pre-rooted image. One thing I did see was that ADB PUSH is not reliable. I installed the recovery image. Then I rebooted into recovery and tried pushing the rooted image to both /sdcard and /sdcard/download when /sdcard didn't work. Both time the adb gave me a message about the time and the bytes/sec it took to transfer the file. No error indication whatsoever. I had to boot normally, install ES File Manager and use the app to push the zip file to FTV and of course, it installed after that.

Takeaway, if the recovery cannot find the zip file even if ADB doesn't indicate error for the push, don't panic and use some other app to push the zip file (after verifying that the zip file is not present).
[Fire TV Android Development] rbox:
/data (and /sdcard, which is /data/media) isn't mounted by default. So when you do the push, it's pushing it to RAM. And then when you go to install zip from /sdcard, it mounts /data thus hiding what you had pushed to /sdcard which was living in RAM. If you want to push in recovery to /sdcard, you first need to go to the mounts menu and select mount /data. OR you can just use sideload, which is easier.
[Fire TV Android Development] dbdoshi:
Thank you for clearing my confusion! Learned something new today. I guess AFTVNews guide needs to be updated.
[Fire TV Android Development] Y314K:
I like things easy.. So I just used Amazon FireTV Utility App v0.26 http://xdaforums.com/showthread.php?t=2736774 to sideload the FW to /SDCard Download folder. Then I just booted to Recovery with the app & went into /SDCard/0/Downloads to install it from zip. You do need to remember to delete the .zip to get back the 400MB's...

Did it this way because it is easier & because it is safer. (No cache flashing problems)
[Fire TV Android Development] imtiajmeah:
51.1.4.0_user_514006420

Finally the new 51.1.4.0_user_514006420 for us in the UK... Look forward to rbox working his Prerooted Stock magic.
[Fire TV Android Development] puppinoo:
Is it possible to free more space in /root?

Hi,

Thanks for your tremendous work on AFTV.

I've been using your pre-rooted 51.1.3.0_513011520 for a while and I'm happy.

Since I own a Chromecast today I wanted to install this:

http://xdaforums.com/hardware-hacking/chromecast/app-cast-receiver-app-android-t2900726

Unfortunately the .so lib is 35mb and my AFTV says I have just 28mb free left in /root. Is it possible to free more space?

Thanks again and bye.

puppinoo.
[Fire TV Android Development] rbox:
I assume you mean /system... I'm sure there's tons of stuff you can delete.
[Fire TV Android Development] puppinoo:
Thanks,

Since I'm not that expert. Can you give me an example of stuff I can delete wothout compromising the system? (most of all cosmetic stuff I dont need)

Thanks.
[Fire TV Android Development] rbox:
No clue. If you wait until Monday maybe I can take a look at what can be deleted.
[Fire TV Android Development] puppinoo:
Sure.

I'll wait since I'm not in a rush. Not to mention freeing space can probably be useful for other purpouses and other people too.

Bye.

Puppinoo.
[Fire TV Android Development] Y314K:
Not sure if SDCard if part of system storage but have you sideloaded stuff like FW or Apps to SDCard/0/ or SDCard/0/Download/. You might have stuff you used for something that can now be cleared out.
[Fire TV Android Development] puppinoo:
Hi,

Thanks for your advice but I tried to delete stuff from both of those paths and they don't seem to be part of /System/ path since my free space is still 32mb.

Regards.

puppinoo.
[Fire TV Android Development] Y314K:
Also if you have XBMC or some other streaming app. Look in that apps folders. It's been reported that sometimes this apps might download a show or movie & leave it in the system. Instead of deleting it. Use ES File Eplorer to dig around.
[Fire TV Android Development] rbox:
/system is read only and no app can write to it.
[Fire TV Android Development] Y314K:
Ahh.. So would eat space but not from system. So what can cause the system to get full... When most of the big stuff is outside of it.
[Fire TV Android Development] xenyz:
You said it, no problems until you installed an old, incompatible Xposed version on your Fire TV.

If you do this, do it properly and use xposed-v87-sdk22-arm.zip
[Fire TV Android Development] fr0st420:
Is there anyway to stop the fire TV from trying to update? It's a pain resetting it everytime I want to use it.
[Fire TV Android Development] Y314K:
Method 5 can be done from TWRP. But a CHMOD 755 must be done on the newly uploaded build.prop file at the end for it to take affect correctly. Which is not part of the instructions.

Method 1 is always a good secondary option. Both methods are recommended. Don't just do one.

http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
[Fire TV Android Development] n2locarz:
Anyone have Version 5.2.4.0 rooted running on the their Fire TV 1 (Bueller)?
[Fire TV Android Development] Y314K:
It has not been released by RBox so unless u might be a tester for him. It's not out there. I believe RBox will probably wait until the new GUI comes to FTV1's before releasing a new PreRooted ROM. Specially since v5.2.1.2 mostly closes rooting avenue's. It doesn't add anything new.

Forgot v5.2.4.0 has not been released for any v1 devices.
[Fire TV Android Development] radmacks:
Okay I followed all of the instructions step by step and updated incrementally. I was experiencing a memory leak where the AFTV1 would say it was full and show it was full. Cleared everything deleted everything wiped everything no advance xml in kodi. That has seemed to have fixed it.

But now it reboots itself to recovery when left sitting idle. So every time I go to use it, its at the recovery screen. Which is CW 605149. I thought this ROM used TRWP? Should I just try and flash TRWP?
[Fire TV Android Development] rbox:
I updated the OP with 5.2.1.2.
[Fire TV Android Development] KLit75:
Cool! I know this doesn't bring the new UI but do we know if this update can be skipped or is it probably necessary to flash this before we get the next one?

Thanks a lot rbox!
[Fire TV Android Development] AFTVnews.com:
Unless rbox explicitly says so (which he has not for any 5.x updates) you never need to flash subsequent updates. You can jump up or down directly to whatever version you want installed.
[Fire TV Android Development] fr0st420:
Thanks you! My two firetv box's will finally stop booting into the recovery. My wife will be happy!
[Fire TV Android Development] yazyazoo:
Just flashed 5.2.1.2 and stuck on a black screen after reboot.
[Fire TV Android Development] radmacks:
Dirty flashed Jan 31, 2017 and was having a ton of problems with root, Netflix ect. Gave her a full wipe and reinstall and all is well so far except ES File Explorer. Super User pops up and I grant it but it "fails the test" cleared cache on Super User and tried again and still no go.
[Fire TV Android Development] edgardo_0691:
Just flashed 5.2.1.2_r1 and everything work fine. Thanks rbox
[Fire TV Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION] , Have you done any testing of the newer latest stable SuperSU releases since the SuperSU v2.46 that is part of the PreRooted Roms ?

If we wanted to test them. Could you give us some guidance on the do's & dont's.

Some have mentioned that they where able to access the SupeSU settings by installing v2.05 beta APK. And they where able to use the 'disable mount namespace' toggle button. But this still didn't fix the ES File Explorer problem.

I tried the bueller-fixsusdcard.zip & it seemed to make some other File Manager's work better but not ES Explorer & I still can not run the “ls -al /sdcard” in SuperSU Mode successfully thru ADB. Always get the same non SupeSU Mode response.

I know all the SU files are in the "su" folder in the PreRooted Roms. And there is a Module & APK part to it. Trying to understand more about it before testing. Is there any point of testing later versions ?
[Fire TV Android Development] rbox:
Sure. You can replace the su files in the zip with any version you want.
[Fire TV Android Development] Y314K:
Great, will try the latest PreRooted FW version first. And then play around with different SuperSU versions if I still have the same problems.

On a different note. Is there any easy method or program to open & extract files from the ROM's .DAT files on Window's 8.1 ? Trying to get my hand on the "KFTV Launcher.apk" found in either the official v5.2.4.0 FW update or the v5.2.4.0 FW PreRooted Rom. Which I believe lies in the main (system.new) .DAT file.
[Fire TV Android Development] hd0120:
I just flashed 5.2.1.2_r1 and everything works great. Thanks a lot, Rbox.

One small issue.....my wireless keyboard stops working. Any idea why?

Thanks again.
[Fire TV Android Development] pwntrik:
So does this ONLY work with unlocked bootloader? (If I use an A-to-A cable on a locked bootloader does it block writing to the partitions)
[Fire TV Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION]

Can you take a look at this. If the post is correct, then this is the reason why the SuperSu wont open unless it's an old APK version. I just hope a fix can be implemented without having to install XPosed. I usually don't like to install anything other the SuperSU & regular APK's so updates won't accidentally break anything between updates. But even if XPosed becomes a must. This sounds like it should be very helpful.

https://xdaforums.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590#post70927132

I hope having access to the SuperSU options can help with the ES File Explorer bug too.

Do you plan to do any testing with it ? Let us know if we can help.
[Fire TV Android Development] rbox:
I suppose you could decompile the supersu apk and maybe change the default theme in the manifest? Not sure.
[Fire TV Android Development] :
what went wrong?

I was already pre rooted so I went into my system recovery and after uploading the image into a zip i installed so now I am on 5.2.1.2 trying to run some shell commands and for some reason it's giving me an error

shell@bueller:/ $ adb shell

/system/bin/sh: adb: not found

127|shell@bueller:/ $ su

/system/bin/sh: su: not found

127|shell@bueller:/ $

can someone explain what went wrong and how to verify if I am rooted or what do I need to make work this pre-rooted software? Thank you much
[Fire TV Android Development] Y314K:
Looking to do a request to see if the next stable version of SupeSU might be capable of ignoring or using what's available instead of looking for a specific app theme. I know that FireTV's have a GUI's, Launcher parts. But am I right to think it's completely missing a theme option. Of have I just missed it ?

Also want to verify that non opening APK SuperSU bug affects all FTV's on PreRooted FW. Not just FTV1's ?

Maybe we can request for something like if device is any of the AFTV devices then SuperSU.apk can ignore or bypass the theme requirement.

In the past I think I read in this thread that not just the APK is a problem but that something can happen with the binaries that can cause some of the bugs we have reported (ES File Explorer). Is it like a blacklist type of a problem or some other type of blocking or just not right installation ?

Since I plan to request that the APK's them problem is looked at. I want to include the possible binary problem to on the request. Trying to read thru the thread. Any other or more info would be appreciated.
[Fire TV Android Development] Bray90820:
Is there any way to install the Prerooted 5.2.1.2 if I wasn't already rooted
[Fire TV Android Development] pwntrik:
If it's not already rooted and on version higher then 5.0.5 then no. The only way after that requires soldering. You can search aftvnews.com for hardware root method.
[Fire TV Android Development] E--Man:
Hi [MENTION=3991724]rbox[/MENTION] and all, I am on your rooted FireTV OS3 with the boot menu and haven't upgraded to TWRP w/ OS5 just yet. I have been enjoying FireStarter and the home button detection too much to upgrade. I wanted to ask everyone, besides 24p capability are there really any advantages to upgrading to OS5 with TWRP? What can I do with OS5 that I cannot currently do with OS3? Thanks.
[Fire TV Android Development] KLit75:
Can't connect to network

I decided to do a full factory reset, wiped everything but internal. Everything went fine. I set it up, connected to my network. About an hour later it dropped my wifi connection and won't reconnect. I tried forget the network and reconnect but it didn't work. I reset my router eventhough all other devices connect fine. Anyone else experience this? Suggestions?

*I just realized I forgot to block updates though I have no idea if thats the issue. I tried dirty flashing the rom--no go. Now I'm wiping everything again and reflashing it. Hope that works.

***I'm out of ideas

After wiping system and flashing the rom again it still won't connect

I'm would think I screwed up by wiping system in the 1st place BUT it did initially connect the 1st time I flashed the rom and allowed me to set everything up.

Update--well this is just some insanely bad timing. I hooked up an old box because I got tired of banging my head up against a wall and then I read this

http://www.aftvnews.com/fire-tv-and...issues-today-are-due-to-amazon-server-outage/

I've had this box since spring 2014, and today I decide to flash a rom at the precise moment when Amazon servers fail (a 1st that Ive seen)

Sorry for the spam.
[Fire TV Android Development] E--Man:
Anyone???
[Fire TV Android Development] KLit75:
I can't think of much. If you like firestarter Id stay put.

OS5 brings Alexa (not blown away by it, barely use it)

Other changes imho are minor

I am looking forward to the next update because it brings a much needed newer ui...but if you like firestarter maybe thats not a reason to update.
[Fire TV Android Development] nathan1314:
Thanks successfully updated to 5.2.1.2r1.
[Fire TV Android Development] foshozee:
Bricked my aftv 1. Successfully updated but once rebooted no light or anything. From reading looks like I will need Linux to load stock back on. I do not have access to a linux machine or have knowledge of it. If anyone can help me please pm me. Thanks
[Fire TV Android Development] hotblast:
follow-up on your de-brick FireTV instruction

Dear Kramar111,

Your instruction is great. I almost completely recovered my bricked FireTV (v.1), except it is in bootloop right now (see attached image).

Basically I followed your instruction step by step without getting any error message, except i didn't "Unmount all sd"your letter" volumes (if mounted) ". Since I naively thought i need to have a mounted drive to dd--convert and copy files to. My fault. After seeing no error, i unplugged the USB A-A cable, the FTV is in bootloop. I checked the wired connection at router side, there is no light at Female end of Cat5e. I tried to reconnect FTV to linux using USB A-A cable, but my computer no longer to see FTV. I am stuck here, would you help me out.

Thanks,

Gary
[Fire TV Android Development] sybe:
Looks like i am in the same boat as you foshozee. Install worked, no issues. Played a video, tried busybox and su and rhey didnt work. Went to reboot and nothing. No light, no nothing.
[Fire TV Android Development] hotblast:
This is also how i bricked my aftv 1

I am in the same boat. This is also how i bricked my rooted aftv 1. After reboot from the pre-rooted firmware updating, my box has no light and nothing. I tried using a linux box to un-brick it, but got into bootloop situation. I will keep you posted if i made any progress.
[Fire TV Android Development] Kramar111:
[MENTION=6334632]hotblast[/MENTION]

unplug power cord for 10-30 sec and plug it back

which software version you try? your own or from my 2014 year instruction?

did you "sync" 3 times?
[Fire TV Android Development] hotblast:
thanks for your quick response.

I did many times of cold reboot. No help.

I used the version mentioned in your 2014 instruction: 51.1.4.1_user_514013920 Stock Software and 51.1.3.0_user_513011520 Stock Recovery.

Yes, i did 3 times of "sync". No error.
[Fire TV Android Development] Kramar111:
[MENTION=6334632]hotblast[/MENTION]

maybe it's conflict with newer software version

try leave FireTV powered on for long time (up to 24 hrs)

read somewhere it's help
[Fire TV Android Development] hotblast:
i have it plugged in for several days.
[Fire TV Android Development] sybe:
So there is no sure fire way to unbrick the aftv v1?
[Fire TV Android Development] hotblast:
I am in very similar situation with this guy. FireTV can be seen from Windows device, but no longer access its file.

adb and fastboot have no access either. It looks a dead horse right now.

https://xdaforums.com/fire-tv/help/fastboot-recovery-usb-cable-drivers-t2926595