yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Kramar111:
If it in 9006 mode - use "your's version" of software.bin and all will be fine

---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------

What PID/VID of FireTV in Device Manager?
[Fire TV Android Development] hotblast:
bricked AFTV v1 under device manager

under device manager is:

Device USB\VID_1949&PID_0401\70900303428200RL requires further installation.
[Fire TV Android Development] Kramar111:
Install ADB (Android Device Bridge) https://dl.google.com/android/repository/platform-tools-latest-windows.zip

and drivers for Fire TV https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-to-fire-tv-device

or https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing (newer drivers)

Connect to your Fire TV through USB A-A cable and run in command line (cmd.exe)

adb devices

What do you see after that?
[Fire TV Android Development] hotblast:
There is no list displayed. thanks,

C:\Users\xie_g>adb devices

List of devices attached
[Fire TV Android Development] Kramar111:
try http://www.nirsoft.net/utils/usb_devices_view.html
[Fire TV Android Development] hotblast:
thanks Kramar111 for your help. Without your encouragement, i would give up on this.

I followed your instruction and used the USBDeview. Attached is the screen shot.
[Fire TV Android Development] hotblast:
more screen shot on USBDeview
[Fire TV Android Development] Kramar111:
[MENTION=6334632]hotblast[/MENTION]

in cmd.exe run

adb version

you need 1.0.39
[Fire TV Android Development] hotblast:
thanks for pointing out

C:\Users\xie_g\Downloads\platform-tools-latest-windows (1)\platform-tools>adb version

Android Debug Bridge version 1.0.39

Revision 5943271ace17-android

C:\Users\xie_g\Downloads\platform-tools-latest-windows (1)\platform-tools>adb devices

List of devices attached

adb server version (32) doesn't match this client (39); killing...

* daemon started successfully *

---------- Post added at 01:32 AM ---------- Previous post was at 01:27 AM ----------

C:\Users\xie_g\Downloads\platform-tools-latest-windows (1)\platform-tools>adb kill-server

C:\Users\xie_g\Downloads\platform-tools-latest-windows (1)\platform-tools>adb start-server

* daemon not running. starting it now at tcp:5037 *

* daemon started successfully *

C:\Users\xie_g\Downloads\platform-tools-latest-windows (1)\platform-tools>adb devices

List of devices attached

C:\Users\xie_g\Downloads\platform-tools-latest-windows (1)\platform-tools>adb version

Android Debug Bridge version 1.0.39

Revision 5943271ace17-android
[Fire TV Android Development] Kramar111:
[MENTION=6334632]hotblast[/MENTION]

What PID/VID (full line) of FireTV in Device Manager for now (after driver's update)?

Is USB debugging was set to on before all this happend?
[Fire TV Android Development] hotblast:
Device USB\VID_1949&PID_0401\70900303428200RL requires further installation.
[Fire TV Android Development] hotblast:
debug was enabled by bricked.
[Fire TV Android Development] Kramar111:
Try manual update driver (in Device Manager right click on ADB device, Update driver and select something like I manually select folder with drivers)

Did you try https://xdaforums.com/showthread.php?t=2799779 ?
[Fire TV Android Development] procter:
[MENTION=3991724]rbox[/MENTION]

Is there a similar flashable script to mount external usb (ext4 format) as the internal storage for ftv gen1? Previous script was for fos3 and cwm recovery. Thanks in advance.
[Fire TV Android Development] procter:
I want to ask a related question. Just updated to FOS5 pre-rooted with TWRP recovery, and I think the mounting external usb for internal storage does not work any more (was developed in FOS3 and CWM recovery), so I followed the instruction to move kodi’s data to external usb (fat32), and I also noticed that the ftv popped out a msg saying “when needed, external storage will be used to install apps” and I do see “move to usb storage” in all those apps’ setting. Is there a specific reason we should not move all the apps to usb storage? Back in fos3, we had to use several steps to “merge” external usb with the internal storage so that we can use more space to install apps and stuff. Thanks a lot. [MENTION=5957312]AFTVnews.com[/MENTION]
[Fire TV Android Development] Y314K:
I know your asking about the more broad script that they use to run on FireOS 3. But I think this might help you in the mean time.

http://www.aftvnews.com/how-to-rest...-after-updating-to-5-0-5-on-1st-gen-fire-tvs/

You can find other storage guides here:

http://www.aftvnews.com/tag/guide/

I would probably advice you to go to that mods thread where the code was release. And kindly request [MENTION=2205195]jmandawg[/MENTION] or if someone else can update the script.

https://xdaforums.com/fire-tv/general/mounting-external-usb-to-data-t2889319

As for your ? The builtin “move to usb storage” function on FireOS 5 only moves partial parts of the App. If I am not mistaken. They let the apps maker decide what can be sent to the USB. That is why there is a guide on how to send all of Kodi over to USB: http://www.aftvnews.com/how-to-partially-or-entirely-move-kodi-data-to-external-usb-storage/.

If your using a USB3 USB device. Then there shouldn't be any reason why not to move over apps to USB. But you'll notice that in most cases you are only sending some part of the app. Not the full app. Since App makers for games & other apps structure their apps to contain the biggest parts of their app in different parts. Data vs Cache vs etc.

It is very easy to test this out as it is very easy to move & move back your data between the internal & USB using the Manage Apps option. Try it.

Last note:
[Fire TV Android Development] fr0st420:
Version 5.2.4.1*(Build 573210520)-

First discovered on 4/5/2017

Notes and Known Changes

Adds new interface to Fire TV 1 and Fire TV Stick 1

Data usage monitoring added

Video quality setting added

Voice search for YouTube (using "Search In Apps") added

Adds Alexa in UK and Germany
[Fire TV Android Development] Y314K:
Unless you have a link of the update for RBox. All your doing is posting info that we already knew before last weekend via AFTVnews.com .
[Fire TV Android Development] procter:
Thanks a lot for the reply, [MENTION=1449438]Y314K[/MENTION]

I have always been wondering about the android built-in "move to storage", and your last reply explained it. Back in the olden days, when I was using some crappy android entry-level phones, I had to use the paid version of Link2SD in order to free up my internal storage. I only vaguely remember the sales pitch why not using the built-in "move to storage" function. BTW, is it possible to just sideload Link2SD plus and "link" the apps to external storage? I saw the button in firetv utility app (link2sd) but not seeing too much discussion. Just wonder if there's any other concerns about that. I can use app2fire to move the link2sd to firetv I suppose?
[Fire TV Android Development] Y314K:
np, that script was the best merging of both external & internal memory. So hopefully it just needs some tweaks & it will get updated. As for Link2SD. I don't remember seeing any posts about it on FireOS 5. In theory it should work. Since it works on Amazon tablets. And hopefully they left everything needed in all their Rom's. But some testing will need to be made. Hopefully we can still split the USB stick like we can on SDCards Fat32/ext4.

I know Elias over at AFTVNews.com plans to add a vote for guide/vids request option. Bet Link2SD will probably be highly sought/voted.
[Fire TV Android Development] procter:
Want to ask a box related question (not directly related to FTV though), looks like the Android MM added this function to format SD card as internal storage. I put in a Toshiba Class10 Micro SD to an android 6.0.1 tv box and formatted as internal storage, however, I feel that the running speed of several apps is slowing down (tested Kodi). In the olden days, we use Link2SD to do the same (more or less), is this something we should always do on a box? Thanks.﻿
[Fire TV Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION]

Got 3 2 ?'s I need help with.

1 - Do Amazon stock Rom's use/include "DM-Verity" &/or "ForceEncrypt" ?

2 - If they do, are "DM-Verity" &/or "ForceEncrypt" still use/included in the PreRooted Rom's ? Even for us with fully unlocked BootLoaders ?

3 - Have you been able to get a link to the latest update for the FTV1's. Been thinking of maybe letting my FTV1 try to update thru my laptop using WireShark. Thinking that even if it downloads the update. TWRP should still stop the installation ? But if you already got a link or will be getting it soon, then never mind.

I see that Elias already linked to the update @ AFTVNews.com: http://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/
[Fire TV Android Development] rbox:
No verity or encryption in stock rom.
[Fire TV Android Development] Y314K:
As always Thanks for the quick reply. As you might of guess I am looking into using one of my fully unlocked FTV1's to possibly test most aspects of MagiskSU & the Magisk Manager App. Specially the per App Root Hide option. Also Magisk is the only Systemless option fully compatible with Lollipop v5 & above. I will be making a more detail thread probably later today/tomorrow but wanted to verify those two parts. I will also be sharing/posting the ProRooted Boot Images for the Magisk developer. Seems to be step one to verify device compatibility. Of course I bet he will need your input as our FTV Guru. I am not sure how wide is the gap between Android's Lollipop file structure & FireOS 5 file structure.

Will try to first get things tested with a fully unlocked bootloader FTV1 but I am hopeful that most/some of the important options can also be made to work on the other FTV1's & other FTV devices that are not lucky to have an unlocked boot-loader. Should be less complicated now that all FTV(S)'s will finally be on the same FW version again.

Let me know if you have any thoughts about this & feel free to PM me if you prefer I don't continue to hijack this thread.

:good: Thanks again for all you do for us...
[Fire TV Android Development] AFTVnews.com:
I always send the update to rbox directly when I get it, so no need to let him know I published it. For anyone wondering, I haven't captured the Stick 1 or Fire TV 2 update yet.
[Fire TV Android Development] chrisexv6:
Not sure if this question belongs here, feel free to kick scream and yell if I should move it!

Running the latest pre-rooted image, I cannot for the life of me get the Netflix app to work. Ive tried reinstalling, sideloaded different (older) versions, etc. It always gives me ui-800-3 error. I can go to the More Details screen and the network tests pass just fine, but the app seems like it never even tries to get to Netflix before erroring out. Within 5 seconds of opening the app it brings me to the error screen. All of the troubleshooting steps Ive found on the net havent resolved the issue.

Logcat didnt show very much going on when I click to open Netflix, no kernel dumps or anything.

I have a non-rooted gen 1 FireStick thats running Netflix just fine, so Im thinking its not a network issue on my end.

Thanks in advance.

-Chris
[Fire TV Android Development] Y314K:
I assumed you had. I just included the link in my update as a reference as to why I had put a strike to ? 3. BTW, someone seems to have posted the captured update file (not Amazon link) in the FTV2 PreRooted ROM thread.
[Fire TV Android Development] AFTVnews.com:
Thanks for the heads up on the update file. It's up to rbox if he uses it, but I'd be more comfortable getting the URL so we know it's unmodified. I'll contact that guy with instructions on how to grab the URL..
[Fire TV Android Development] suussi:
Everytime i start my firetv after standby its in twrp mode. It seems after some time wen there is new firmware version it tries to update but cant and gets into twrp. I had this problem sinds some firmwares ago. I blocked updates on router siden even tried with adb command but still no luck. Any help to stop it from going to twrp as its a pain in the ass to always pull out powercord to reboot it. Hope someone can givbe me a solution untill i can flash the new prerooted firmware
[Fire TV Android Development] Kramar111:
[MENTION=6021967]suussi[/MENTION]

adb shell su -c pm disable com.amazon.device.software.ota
[Fire TV Android Development] Y314K:
np, new heads up. FTVS1 Amazon update link has now been posted in the (Montoya) PreRooted ROM thread. I think that's all of them for now. Minus the never rooted FTVS2. Although it's weird it skipped a build version. It goes from 03220 to 10520.
[Fire TV Android Development] AFTVnews.com:
Thanks for the new heads up. I've added it to my update page and sent it to rbox. It skips because rbox never publicly released the 5.2.1.2 ROM for the Stick, so all rooted Stick owners are on 5.2.1.1, which means they'll go straight to 5.2.4.1 now. That's why that guy got the 5.2.1.1 to 5.2.4.1 update URL. It doesn't make a difference as far as ROM creation is concerned.
[Fire TV Android Development] eliadrin:
Same happens to me, I have AFTV1 box fully rooted and after standby it goes to recovery screen in TWRP. I have to unplug the box and pug it right back in, in-order for it to boot normal again.

I tried all blocking update methods (in AFTVnews guide and the line code Kramar111 suggested below)to no avail, any ideas ??
[Fire TV Android Development] suussi:
I tried his line of code and it did work for me! All previous attempt didnt help. Dont know why this time it did :)
[Fire TV Android Development] Y314K:
My best guess especially if you have been mostly blocking updates on your Rooted TWRP'd FTV(S) thru your Router &/or OpenDNS is that it might had already chambered the update in one of both possible places. And TWRP is the only thing stopping it from installing. It tries to install when idle & TWRP loads while blocking the update.

You can use a Root File Explorer like ES File Explorer to verify & fix this by looking in "/cache/" & "/sdcard/Android/data/com.amazon.device.software.ota/files/" for .bin files. This can also be done from within TWRP's File Manager. All info per 2.3 section of this guide:

http://www.aftvnews.com/how-to-stop...ire-tv-or-fire-tv-stick/#downloaded-rooted-on

That is why the only best method to block updates is both Method 5 & Method 1 combined all the time.

http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
[Fire TV Android Development] eliadrin:
Thank you both for your response,

I opened that folder and found no .bin file in it (it was all empty) I ran the command to delete the content (from the tutorial) to be safe but it is still booting to recovery every time.
[Fire TV Android Development] Y314K:
So it's booting to TWRP. What PreRooted FW where you at before ?

Does it get to the ROM at all ?

Did you do the Method 5 blocking yet ?

Are you still blocking thru router/OpenDNS ?

In the past I had problems when blocking updates thru router/OpenDNS. I did method 5 & ran with no router/OpenDNS blocking.

You might need to reflash a PreRooted ROM & do Method 5 to get back normal. Then you can do Method 1.
[Fire TV Android Development] rbox:
I updated the OP with 5.2.4.1_r1.
[Fire TV Android Development] jpearn:
[MENTION=3991724]rbox[/MENTION] thanks for the update. Installed fine, however there is no UI for SuperSu now, if I launch from ES File Explorer the screen flashes. Is that an Amazon feature ? !
[Fire TV Android Development] eliadrin:
As always your help is greatly appreciated!
[Fire TV Android Development] boudicca99:
twrp'ed fine here too. Alexa finally on the firetv. Although not a fan of the new gui.
[Fire TV Android Development] Y314K:
np, take your time. There is no rush to update or rush thru. The most important 2 steps is to do the Method 5 & Method 1 update blocking & verify. Then take off any router/OpenDNS blocking. Then see if that takes care of the rebooting to TWRP. Check the two cache addresses again for .bin files in TWRP's File Manager just in case.

After that update to latest. You'll need to redo Method 5 right after flashing the latest update. And you will probably need to do Method 1 again if you wipe more then cache & dalvik when updating. It does Not hurt to send the Method 1 command if you ever feel the need to.

PM me if you like. But I think you got the hang of things.

---------- Post added at 06:27 PM ---------- Previous post was at 06:17 PM ----------

Is a known issue since FireOS 5 & FireOS 3 for FTV(S)'S do not include a theme engine like regular Android builds.

Solution:

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

I go onto more detail on my last post here:

https://xdaforums.com/showpost.php?p=71704440&postcount=15

You really only need access to it once.
[Fire TV Android Development] jpearn:
Installed latest v87 framework and Holo Themer 3.0 and all is good, thanks !
[Fire TV Android Development] Y314K:
np, I would highly advise you at least unactivate it when you don't need it. And even uninstall it if you don't foresee it being use on the short term since is not constantly needed. And it's better to make sure it doesn't cause any reboots.

Only install it for each use. Very simple to do. Just back up the APK & leave it in a folder in the FTV's SDCard/ probably in SDCard/Download
[Fire TV Android Development] procter:
[MENTION=1449438]Y314K[/MENTION] [MENTION=5957312]AFTVnews.com[/MENTION]

I did something stupid just now and bricked the ftv1. Mine was on the previous rooted ROM 5.21, with unlocked bootloader and twrp recovery. Everything works well but this morning I decided to install the new rom. Had a brain fart moment that I went in the recovery, did the advance wipe (cache, data and dalvik) before installing the rom. After that, I could not use my keyboard to goback to previous page to install the ROM, so I ended up moving my cursor down to the reboot toggle. It then got stuck on the Amazon white logo, with the light on the box "breathing" slowly (no orange or red light).

So I went ahead to see if I can somehow get into the recovery mode, the key combo (alt+i+print screen) did not work for me (well, my keyboard's print scrn was actually a combo key that gets enabled by pressing"FN", so I'm not exactly sure if I need to do alt+i+FN+print scrn or not, nontheless, did both not in recovery).

I then found a crappy old usb a- usb-a cable and connected the ftv to my laptop. First of all, the PC is not detecting firetv as "adb device", so I could not access adb via usb let alone fastboot. What else should I try?

Thanks a lot.
[Fire TV Android Development] Y314K:
First of all not I am not associated with [MENTION=5957312]AFTVnews.com[/MENTION]. We all just know that is the best place for guides. Here only Elias aka [MENTION=5957312]AFTVnews.com[/MENTION] is from there. I just try to help using his great guides.

As to flash a ROM after any wipe. All you had to do was clicked on the house icon on the bottom of that TWRP menu. That would of gotten you to the beginning where you could choose to "Install" a ROM. I am not sure why your having that problem since you did not wiped the most important part where the ROM resides. Which is System. Try leaving it on for a long while to see if it gets past the white logo with time like it has for some. I am trying to remember if the Advanced Wipe includes System. I don't think it does. So trying to remember/figure out your options.

Don't do it yet. But have you powered down the FTV yet ? Just wondering where you are at exactly. If you did not wiped System then you should be fine. And time or a power down might do the trick. If System was wiped then fastboot will probably be your only answer.

I have never had to deal with fastboot & the A-A cable method so not sure how that goes. There are a bunch of posts regarding that here. There are probably some [MENTION=5957312]AFTVnews.com[/MENTION] too. But not sure you have to use that Method just yet.
[Fire TV Android Development] procter:
Thanks for the reply, [MENTION=1449438]Y314K[/MENTION]. I probably did wipe the system since I left only "internal storage" unchecked for that wipe. I think it was indeed bricked, powered down and back up for numerous times as I was trying out different options, such as usb keyboard combo key or A-A cable to fastboot, just cannot pass the white Amazon logo.
[Fire TV Android Development] Y314K:
Yeah, that's another brick in the wall.

Try this guide although is shows the old CWM. I think it is still valid. Just adjust it for TWRP.

http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/

But I am just going from what I've read.

For reference to anybody else:

- You never restart a device after wiping System without reflasing a ROM. Just leave it on & in that menu until you know you've/how flashed a ROM.

- You never wipe System if you are going to flash a ROM. Since the mechanism for flashing the ROM will take care of System.

- You can TWRP recover as long as you don't wipe System & reboot.

- The 3 row of Icons on the bottom of TWRP are universal menu buttons. Hitting the HOME Icon will always get you to the main menu.

- Never wipe System unless you are RBox or RBox told you too. It should never be needed.
[Fire TV Android Development] procter:
Thanks, I was in a brain fart moment, normally I would just do wipe data/factory reset before rom installation I was following that guide. The combo key trick did not work (and did it even work with twrp recovery, all success stories are for stock recovery). I was hoping the adb via usb or fastboot would work, but my old A-A cable seemed not doing the trick, computer not detecting new device. I will try another cable. Hopefully it was the cable that caused the not detecting problem..
[Fire TV Android Development] Y314K:
Your not the first. So scour the comments here & specially the TWRP thread. There are success stories of using the A-A cable Method to comeback from this. At least to get a booting device. Not sure if Root survives. Good luck, let us know how it goes.
[Fire TV Android Development] procter:
Today is one of the bad days. So to update, I was able to fastboot, reflash the recovery with my wife's super slow laptop and the same A-A cable. For some reason, my own laptop just would not recognize the connected firetv. Using another computer, saw the android device in device manager and jumped a few hoops to get the adb driver loaded. Tried adb, no device recongized, but fastboot was able to recognize, and eventually I loaded back up the 5.2.1 ROM, coz for some reason the 5.2.4 ROM file wasn't pushed completely (adblink).

However, I went back to configure the internet and stuff and used adblink to push the 5.2.4 ROM again via wifi, left the room and came back to see no signal on TV, no white LED, feels like the power is lost. Tried different power outlets, the same, no led, no booting, no logo. Connected with A-A cable back to my wife's computer, this time fastboot command did not come back with anything. I was puzzled, but do not have a spare 6.25v-2.5A output adapter to confirm if it's the power adapter or it's the box itself. Tested the output of the power block, seems to be normal, around 6.2v.

Searched the forum and saw a few posts talking about efuse bust as well as emmc raw writing. Agrrrr! Wasted half a day and still got back a brick.
[Fire TV Android Development] Y314K:
Sorry to hear that. Just learn & move on. It happens to all of us.

One of the reasons I always mention using USB Sticks for any important flashing on a FTV1 is that I can include a MD5 file for TWRP to check the ROM's integrity before it tries to flash it. You can always add a MD5 file to wherever you upload the ROM too.

As for the eFuse part. Only time will verify that.