yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] hildebrau:
So, I just updated my three rooted FTV1's to 5.2.6.3_r1. All of them were on 5.2.4.1 previously. I therefore have TWRP installed.

My third unit failed on me, however. It turns on, shows the white Amazon logo, then the TWRP boot menu, followed by the animated color amazon fireTV logo. That's where it sits and animates forever. I did see it reboot (probably a watchdog process) one time; but it ended up back at the same spot.

I then fired up TWRP and advance wiped the top four options, and adb pushed the latest bueller-5.2.6.3-rooted_r1.zip back onto it and installed it again. I let it reboot and no change.

I left it on over night and found it in the same spot in the morning. I left it unplugged (to cool down; though it was not hot) all day and just plugged it in again. It is stuck in the same spot again.

I'm technical and willing to try any ideas. I wouldn't think it would be this difficult.

Any ideas? Thanks community!

adb connect 192.168.1.173

adb reboot recovery &

adb kill-server

adb connect 192.168.1.173

adb push bueller-5.2.6.3-rooted_r1.zip.md5 /sdcard/

adb push bueller-5.2.6.3-rooted_r1.zip /sdcard/

adb shell recovery -update_package=/sdcard/bueller-5.2.6.3-rooted_r1.zip &

adb kill-server
[Fire TV Android Development] hildebrau:
I read some more postings and decided to try formatting the system folder/mount with TWRP also. I noted the many warnings to make sure you load the pre-rooted image before rebooting out of TWRP if you format the system folder. I was careful.

This time, it moved onward with the boot process! YAY! It wants me to pair my fire tv remote. That's the next hiccup, as that doesn't appear to be working. Back to google!

Hope this helps someone else, perhaps.
[Fire TV Android Development] krawhitham:
PING
[Fire TV Android Development] oppman29:
Anyone know how to install open_gapps-arm-5.1 on bueller-5.2.6.3-rooted_r1 . I get insufficient space.

not sure how resize the internal partition to allow more space
[Fire TV Android Development] ldeveraux:
See Step 11 (Optional) in this thread below. It worked for me, assuming I installed the Pico GAPPS package.

https://xdaforums.com/fire-tv/general/root-enable-leanback-laucher-t3783504
[Fire TV Android Development] oppman29:
That steps ask to remove all these apps from system to make room ,

I use amazon music app .. but will give a try removing the other ones

thanks for the help!!!

*****************

adb shell su -c mount -o remount,rw /system

adb shell su -c rm -r /system/priv-app/WhisperplayCore

adb shell su -c rm -r /system/priv-app/WhisperplayInstall

adb shell su -c rm -r /system/priv-app/com.amazon.amazonvideo.livingroom

adb shell su -c rm -r /system/priv-app/com.amazon.avod

adb shell su -c rm -r /system/priv-app/com.amazon.bueller.music

adb shell su -c rm -r /system/priv-app/com.amazon.bueller.photos

adb shell su -c rm -r /system/priv-app/com.amazon.shoptv.client

adb shell su -c rm -r /system/priv-app/com.amazon.tahoe

adb shell su -c rm -r /system/priv-app/com.amazon.tv.csapp

adb shell su -c rm -r /system/priv-app/com.amazon.tv.livetv

adb shell su -c rm -r /system/priv-app/com.amazon.vizzini

adb shell su -c mount -o remount,ro /system
[Fire TV Android Development] navin23:
Firetv help

Krama1,

can you tell me where I can find the recovery stock image file in the last step? I was able to followed all the other steps and the files copied.

I downloaded the files below and changed the extension to zip to browser through the file. I only see a recovery folder with a file name "recovery-from-boot.p" and etc folder but no recovery.img file. Thanks

dd if=/tmp/123/recovery-stock-51.1.3.0.img of=/dev/sdc11

bueller-ota-51.1.3.0_user_513011520-signed.bin

bueller-ota-51.1.4.1_user_514013920-signed.bin
[Fire TV Android Development] NxtGenCowboy:
Anyone able to package up 5.2.6.6
[Fire TV Android Development] rbox:
I updated the OP with 5.2.6.6.
[Fire TV Android Development] NxtGenCowboy:
Thank you!!
[Fire TV Android Development] Rathin1980:
Hi Rbox, hopefully you can help. I think I corrupted the fire tv 1 by installing xposed and some back and forth apks. not sure what happened but i am not getting fastboot and the fire tv shows up as flash drive inside PC using USB cable. I am trying to follow this post to unbrick since fastboot is not working. the link you shared here is broken. is there another link that you could share that has the image?

also, please note the screenshot for disk details and see if this is the same issue I am having.

thanks in advance, Rathna
[Fire TV Android Development] Rathin1980:
Okay, I have managed to find the bin from another link and followed the steps. it back back alive so thats good. but I am still not getting fast boot and booting to recovery goes to amazons and not the bullers. I tried copying the twrp 3.0.0.7 img to sdcard and i am trying to do this:

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

but i get permission denied. I tried su but after su I get cannot find directory. any help or insights here? thank you .
[Fire TV Android Development] Rathin1980:
I know I can edit the post but I think replying to it shows the pain and challenge i am going thru hour by hour... I think I finally bricked it for good. Now when I plug to PC all I am getting is a HS-USB QDLoader 9008 COM Port. I see several thread for other devices where people were able to flash certain image and comeback. is there such thing for Fire TV or should I just give up? I really wanted to solve this problem and would be willing to do screen share if rbox is up for the challenge. I do have another working fire tv which went thru 5.2.6.6. update fine so we could use that to pull any img if needed.
[Fire TV Android Development] krasny2k5:
How can I hide root from the system?

I think magisk is not compatible with amazon systems.
[Fire TV Android Development] iniro:
Hi rbox,

Thx for help us to revive our aftv.

I follow your steps and now aftv is working again.

Now I can flash the latest version that you added to op?

Thx again for your work!
[Fire TV Android Development] Rathin1980:
[MENTION=3991724]rbox[/MENTION] is there a way to recover from 9008 comm port or no?
[Fire TV Android Development] krasny2k5:
It seems that 5.2.6.7 is available.

thank you for your hard work [MENTION=3991724]rbox[/MENTION]
[Fire TV Android Development] Rathin1980:
Can anyone help me with the programmer files for QFIL? or any help or guide with using [MENTION=3991724]rbox[/MENTION] fire tv 2 unbrick tools here? looks like those are my only options for this QDLoader 9008 situation I am in right now.

https://xdaforums.com/fire-tv/development/firetv-2-unbrick-image-t3313349
[Fire TV Android Development] mcsephoenix:
I'm having problems ever since I moved to 5.2.6.6 everything seems to work fine but after a few hours I'll switch source back to my firetv and it's in TWRP. I hit reboot system and it comes back up fine. Any idea what is going on or how I can troubleshoot and fix this?
[Fire TV Android Development] NxtGenCowboy:
That would be the auto update trying to run. Upgrade via TWRP to the latest release(in OP). Or block the updates(a quick Google will show you how)
[Fire TV Android Development] mcsephoenix:
Thanks for the quick reply [MENTION=757782]NxtGenCowboy[/MENTION] , I thought I had updates blocked at the router I'll have to look again. I checked the OP like you said and don't see anything about updating via TWRP. Can you point me in the right direction I just be missing something. I certainly don't want to lose root because of some update. Thanks

edit: I disabled the updates via adb so hopefully that does the trick. I am still curious what you were talking about updating via TWRP I am already at 5.2.6.6.
[Fire TV Android Development] oppman29:
There is a newer version now... OS 5.2.6.7... mine was doing the same , once I blocked updated it all worked like a charm again .
[Fire TV Android Development] r17d17:
After some borked attempt to do all the rooting/unlocking dance (with an old FireTV which layed unused on the shelf for some years) I seemed to have it bricked, but to be in Qualcomm recovery..

So I've executed exactly the procedure above. Now I'm stuck at the color logo boot animation with the led "breathing".... ADB shell access is working, but no root here.

Any chance to get past this point? Could I root via command line or something else?

Edit: Found out which version I'm actually on:

adb shell getprop ro.build.version.release => 5.1.1

adb shell getprop ro.build.version.fireos => 5.2.1.2
[Fire TV Android Development] glate:
I recently installed the latest rom and it’s been working fantastic. Only one issue - every time I come back to the TV it has booted into recovery. If I power cycle it will boot into system without issue.

It has never done this on any of the previous ROMs and I have no idea where to begin. Any suggestions?

Edit: doh I now see the messages above. My bad. Will block updates.
[Fire TV Android Development] oppman29:
does anyone know how to increase the system partition, I want to be able to install GAPPS but there is not enough space in the new rom. I also dont want to uninstall amazon components that disable alexa and other things... so uninstalling its not an option,

Thanks
[Fire TV Android Development] Kramar111:
[MENTION=465446]oppman29[/MENTION]

I did this on FireTV 2 (sloane)

Needed TWRP and gdisk (binary)

In short

Boot in TWRP

Backup /system in TWRP

Run gdisk

Backup GPT

Delete /system and /cache partitions

Re-create /system and /cache with new sizes (aligned on 16384 boundaries for AFTV2)

Assign labels for newly created partitions

List partitions and compare result with idea

Write changes to disk

Back to TWRP

Format /cache (or device will be bootloped)

Restore /system from TWRP backup

Check filesystem for /system and resize it for real partition size

That's all :)

But be very carefull, operation is dangerous!

For now a don't have FireTV 1 and can't be more detailed about it.
[Fire TV Android Development] Emmes:
need some help

i was dumb enough to wipe system and rebooted twrp afterwards, now i'm stuck at the white amazon logo

is there a dd command to flash and boot into twrp and then flash the prerooted firmware? or is there any other solution? i cant even remember on which prerooted firmware the fire tv is.

thanks in advance
[Fire TV Android Development] assyriska_ff:
If you have a device with an unlocked bootloader, you can run in fastboot and flash the new firmware. If you have a partial bootloader your device is bricked like mine. :crying:
[Fire TV Android Development] Kramar111:
[MENTION=4965959]Emmes[/MENTION]

[MENTION=3076447]assyriska_ff[/MENTION]

Is device visible on Device manager on Windows through USB A-A?

If yes, type VID/PID.
[Fire TV Android Development] rbox:
I updated the OP with 5.2.6.7_r1.
[Fire TV Android Development] mcsephoenix:
Thanks I will give it a try today, I have been curious to try the new Live TV options out.
[Fire TV Android Development] notsed:
Is anyone else running into a problem with 5.2.6.7 (thank you rbox) of the system partition being too full to install xposed (error 1)? Any recommendations on what can safely be removed to free up enough space?
[Fire TV Android Development] godlike1984:
anyone has 5.2.1.2_r1 afaik its the last fw without the 24p playback stuttering issue thanks
[Fire TV Android Development] TomandJonna:
Need Help Please

Hello rbox...need some help please.

Have rooted my 1st generation Fire TV (OS 5.0.5) with Kingroot. I followed the WRONG aftvnews tutorial for installing twrp and executed the dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery command. I then tried to fix things by executing the "sh /data/media/0/bueller_recovery_v2.zip" command and received back "/data/media/0/bueller_recovery_v2.zip[1]: syntax error: 'newline' unexpected

I can't get into twrp at all and don't know what to do at this point. The box boots up fine, but I'd like to install a custom rom which I understand I cannot do without twrp working.

Please help if you can. Thank you in advance. Tom
[Fire TV Android Development] guido1138:
Just wanted to say thanks [MENTION=3991724]rbox[/MENTION] for all your efforts. I've been using your images successfully since day one.

Since installing 5.2.6.7_r1, I've noticed some instability leading to infrequent reboots, which seem to be related to some video streaming apps I use. I never saw this with any previous versions so it's puzzling.

I did notice that AFTVNews recently posted download links for the latest 5.2.6.9 release, so if time permits and you have a chance to update the OP, it would be very much appreciated. Thanks again!
[Fire TV Android Development] rbox:
I have uploaded 5.2.6.9.
[Fire TV Android Development] Y314K:
Notice the same problem on my end on all my FTV1's on 5.2.6.7_r1 (PreRooted running without SuperSU). Hope the new update fixes this. Will post how it goes. Gonna do a clean install myself to test the update.

TY for the years of great & speedy work/releases. Really appreciate it.

Was wondering...

- Any chance of being able to switch to Magisk on the FTV1's like the FTVS2's use ? At least for us with totally unlocked bootloaders. And can others unlock their bootloaders using any of the new root methods. Or might it not be needed to switch to Magisk ?

- Some of us need to run PreRooted without SuperSU since some streaming apps block rooted devices. But Magisk can hide root & includes XPosed modules built in. And we can update PreRooted ROMs without loosing any system changes. So was wondering if you could look into this.

- Any drawbacks on this ? I know FTV1's are old. But they still work just as well as any newer device.

Let us know ur thoughts. I would be willing to test this.
[Fire TV Android Development] rbox:
I know people have wound up bricking their devices by installing Magisk, but if you have an unlocked bootloader you could try it and see. Installing Magisk should remove SuperSU and it should persist through ROM flashes.
[Fire TV Android Development] Y314K:
Right, most of them did it on locked bootloader devices & while a bit drunk. If I remember correctly.

Which version of Magisk should one try. Latest stable or Beta. Would we need to send the FTV1 bootloaders over to the Magisk Github requesting support for it ? Will probably try it out once I get my hands on a USB-A cable to be able to unbrick my FTV1 if things go south.

Anybody else with a fully unlocked bootloader plan on trying this ? Post here or PM me.

Plan to work on the steps order & will post for feedback here once done with the right order for best possible result.
[Fire TV Android Development] rbox:
Based on my experience with it with the Fire Stick 2, it should "just work". The latest should be fine. If it goes bad, you just need to fastboot in to recovery. Although it's been so long, I don't remember how you get fastboot to work. Probably would want to figure that out first.
[Fire TV Android Development] Y314K:
Great, will test it out this week. Might get delayed since I might be changing ISP. Will first update my daily used FTV1's the regular way first. And will use one of them for all Magisk tests. I can probably use the old AFTVNews unbrick guides if there are any problems. Never needed to in the past. Since I always bug you & Elias & others before trying to do testing stuff until I understand what I am doing.

(FOR FTV1'S with UNLOCKED BOOTLOADER ONLY)

- Download latest PreRooted Rom & latest Magisk Zip installer.

- Remove SuperSU folder from latest PreRooted Rom. And put both Rom & Zip on USB stick.

- Start TWRP & wipe Dalvik, Cache & Data (If you wipe System - DO NOT REBOOT WITHOUT INSTALLING A ROM)

- Flash SuperSUless PreRooted Rom but don't reboot or make sure you reboot back to TWRP.

- Flash Magisk Zip. Make sure there are no errors. Do not reboot, yet.

- Do the Method 5 update blocking method thru TWRP. TWRP has root access to get it done. Done this from TWRP for over a year without any problems right after updating a Rom.

- Reboot to Amazon & run first setup. Magisk app should be part of Zip install although it might need an update.

Did I get anything wrong ?
[Fire TV Android Development] rbox:
You don't need to remove su. The magisk installer is supposed to automatically remove SuperSU. Otherwise seems fine. And then after that, just flashing a regular prerooted rom update should automatically do the right thing as well. Although 5.2.6.9 and newer is the only rom version that automagic-ness will work on. The magisk installer won't install it's preservation script on anything older.
[Fire TV Android Development] Sizzlechest:
I've tried to install Magisk many times and it doesn't work. I have a fully unlocked bootloader. I extract the boot_unlocked.img file from rbox's zip file and push it to the /sdcard directory. If you flash that img file, you will have a clean boot without SuperSU. Installing Magisk and rebooting causes a bootloop. You'll need the USB A-A cable to fix it.
[Fire TV Android Development] Y314K:
You installed everything thru TWRP ? Can you please give more specifics.

I was gonna ask [MENTION=3991724]rbox[/MENTION] if our FTV1's might need a TWRP update for Magisk/AutoPatching to work right.
[Fire TV Android Development] Sizzlechest:
Sure. I use this method to flash a better version of SuperSU since the one rbox includes has an issue reading /sdcard when root is active. Doing this with either the SuperSU or Magisk installer is safer on a clean boot. No issues with SuperSU or Magisk detecting and removing the SuperSU already installed:

Extract boot_unlocked.img from rbox's firmware.

Push boot_unlocked.img to /sdcard directory.

Push Magisk installer to /sdcard

Boot FireTV to TWRP.

Flash the boot_unlocked.img from TWRP. You will have to change from .zip to .img. MAKE SURE YOU DON'T ACCIDENTALLY FLASH IT AS RECOVERY.

The bootloader is now clean. No SuperSU is installed. Install Magisk using TWRP. (You will have to change back from .img to .zip)

Reboot.

This will result in a boot loop. You will not be able to get back into recovery using your keyboard. You will have to use a USB A-A cable and use the following command on your computer:

fastboot flash boot boot_unlocked.img

You will have to repeat the steps above to flash SuperSU to get root back.

I'd love for Magisk to be available since it can be hidden from apps that won't run if the device is rooted.
[Fire TV Android Development] Eyedoctor2:
Rbox: So after getting my Fire TV 2 box up to date I thought I would do the same for my Fire TV 1 box. In AMAZINGLY stupid fashion I managed to brick it. System partition was too full and I tried a weird combination of wiping and restoring and ended up on the white Amazon screen. It does not respond to adb commands except reboot recovery. When it does it reboot to recovery it goes to the Amazon recovery error screen with no options on it except to unplug. I tried the keyboard combo here at least 30 times but no go https://xdaforums.com/showpost.php?p=54976459&postcount=26.

It shows up in Windows device manager as 3 AFTV-1 entries and 3 AFTV-86 entries. It shows up as a usb drive under disk management.

I am attaching a screenshot of the Linux live drive screen. The necessary files to write to the different partitions are on the 256 gb Liteon windows disc in c:\temp\firetv folder.

What's my next step or am I toast?
[Fire TV Android Development] rbox:
If your bootloader is locked, which I'm assuming it is if you have stock recovery, it's bricked.
[Fire TV Android Development] Eyedoctor2:
I had TWRP recovery before this all happened. I have previously done this same fix with Linux so my bootloader must be locked.

Thanks as always for your help.
[Fire TV Android Development] Eyedoctor2:
Rbox: Does a tool like this exist for Fire TV 1 https://xdaforums.com/fire-tv/development/firetv-2-unbrick-image-t3313349

Would it help in my situation?

Thanks again
[Fire TV Android Development] rbox:
No
[Fire TV Android Development] Animux:
Shouldn't it be possible that 2ndinit from your recovery boot menu starts Magisk before starting the normal init from the FireOS? That wouldn't be "systemless" (because Magisk could be on the system partition), but it would enable all the extra features of Magisk for all the people with (partially) locked bootloader (hopefully it can handle that /system is already mounted at this stage). We would only need to ensure, that the MagiskManager will never try to patch the bootimg.
[Fire TV Android Development] rbox:
I think there is a conflict because magisk replaces init, and my 2ndinit replaces init, and it looks like I have a hardcoded call to SuperSU in there, as well. In theory, Magisk might work on everything, but it would be very tricky. So for starters, if you disable the boot menu, does Magisk work?

I have no clue if this is going to work, but it should. Starting from the 5.2.6.9 zip, you'll need to remove from META-INF/com/google/android/updater-script everything between these 2 lines (including these 2 lines):

ui_print("Installing recovery...");

set_metadata("/system/app/SuperSU.apk", "uid", 0, "gid", 0, "mode", 0755, "capabilities", 0x0);

Flash that, and verify it boots and everything works. You should not see the bootmenu. Then boot in to recovery with adb and flash Magisk and see if that works.

Alternatively, if you dont want to edit the updater-script, this is less clean, but should product the same results. Flash 5.2.6.9. Stay in recovery. Ensure /system is mounted. In adb shell, run these 2 commands:

rm /system/bin/e2fsck

mv /system/bin/e2fsck.real /system/bin/e2fsck

Exit adb shell, make sure to unmount system, and then reboot.
[Fire TV Android Development] xenyz:
Has anyone else noticed some stuttering video playback issues on the latest firmware (5.2.6.9_r1)?

I was on 5.2.6.3 since last summer and never bothered with an update until I had some free time this week, and after the update immediately noticed a subtle lag or stutter or slight pause in video playback two or three times a minute or so. It was very obvious when watching hockey in 720p 60 fps but I also watched a Bluray rip in Kodi and also noticed it in 1080p 23.9/24/30 (whatever, I didn't check :)

Anyway I downgraded back to 5.2.6.3 from last June and everything is fine again. I'm wondering now if it is some weird conflict that a factory reset would correct, or if others who have fresh installed the latest have noticed as well. It's a subtle issue, but once you notice it it's almost impossible to ignore.

I'm so glad I have an unlocked fire tv and also so glad that rbox keeps the old ROMs available to download, as I'd be furious if an update I couldn't revert was applied and made things worse!
[Fire TV Android Development] toysoldier1:
Hello,

I have an issue that I haven't seen anyone here mention yet. I have no issues with TWRP, it boots perfectly and I am able to navigate/install from it. The issue is that my screen goes black the minute the Amazon Fire logo goes off. If I pull the plug and plug it back in, the firetv boots in TWRP and tries to update but again the screen goes to black, from here is nothing but a slow blinking light....Is this an issue with the 720p TVs?

Firetv v1 fully rooted and bootloader unlock

Currently on TWRP 3.0.0-7 on 5.2.6.7

This issue started even before TWRP...It goes back to when I installed 51.1.6.3_516012020

Any ideas what the issue is?

TIA
[Fire TV Android Development] Zero_Shadow:
I also have noticed that pause or even complete stop with 5.2.6.9 in Kodi, im going to downgrade back to 5.2.6.7 and see if that improves matters, thanks for mentioning it xenyz I thought it was just me having this issue.
[Fire TV Android Development] xenyz:
Let me know if you find a later release than 5.2.6.3 that doesn't have this problem. Also, did you happen to clean flash it or was it an update? I'm still curious if a fresh install (or factory reset) would fix it, but I just can't be bothered right now, as 5.2.6.3 is working 100% for me