yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Ipse_Tase:
rbox and aftvnews: THANK YOU for all the work, truly amazing.

As a Ouya user I can tell you the level of frustration builds up to the point where users give up and move on if there are no breakthroughs or attempts to crack the box.

Let me ask you one thing though: the custom recovery does NOT touch the bootloader, right? I didn't see any mention of changing it, so can we safely assume that Netflix HD will still work after the upgrade to the pre-rooted image?
[Fire TV Android Development] CLran619:
its exactly like i said. id put the zip onto my flash drive and it would not recognize it had an update zip or anything for that matter on the flash drive. like it was blank.

ive been flashing since the lg optimus v in 2011. modded many devices so ik what im doing as far as flashing roms and recoveries.
[Fire TV Android Development] rbox:
Correct. It doesn't touch the bootloader or any of the firmware. The one sticky point would be if the Netflix app is updated and it requires an update to one of the firmwares I'm not flashing, like the TZ. Until that happens, I wouldn't worry.
[Fire TV Android Development] kairnage:
If it isn't showing have you tried another flash drive? How is the one you are using formatted?
[Fire TV Android Development] MadFlava:
I pushed the latest pre-rooted image to internal storage, booted into CWM and flashed it. Box just finished rebooting and looks good.

Thanks so much for all your hard work
[Fire TV Android Development] CLran619:
none of it matters anymore as i got rid of it. getting a new one which should arrive 2maro. thanks anyway to rbox and whoever else tried to help
[Fire TV Android Development] Hacktacular:
Thanks rbox...donated! 89T84117PM795363P
[Fire TV Android Development] gehx:
I have recovery installed on my ftv. I also have a powered usb 2.0 hub which I have my wireless kb connected to and my 8GB thumbdrive. The thumbdrive is formatted as FAT32. cwm recovery isn't seeing the thumb drive. What might be the problem?
[Fire TV Android Development] rbox:
It was plugged in before recovery started? I haven't tested USB storage functionality in a while, I can double check it tonight.
[Fire TV Android Development] gehx:
yes it was plugged in before recovery started. how are the nandroid's suppose to be stored, on internal storage? sorry for my ignorance, I thought the modified cwm recovery was suppose to see the thumb drive connected to the hub...am i suppose to use a USB HDD instead of a thumb drive? Also, what filesystem should it be formatted in?
[Fire TV Android Development] rbox:
It should work either internal storage or external. Any USB storage device will work. I think it needs to be fat32.
[Fire TV Android Development] alwaysbless:
Nice work rbox! Havent been around these ways in a while but its nice to see someone still working on this thing. Imma install this tonight and hopefully someday we may even get a custom rom! (crossing fingers)
[Fire TV Android Development] nyder:
Rbox, installed your CWMR, have a suggestion and an observation.

Okay, the suggestion is to move the borders in about 10 spaces or so. I can't see the right half of anything of your menu's because of overscan on my TV (have to have AFTV do a 3% scale to see everything). That would be greatly appreciated so I can see what is going on.

The observation was that if you use a mouse while in the recovery, it goes wild and even starts clicking on stuff (not sure as I can't see what the first word or 2 is, so I don't know what is going on). Granted now I know not to use the mouse, but just letting you know.

Oh, as far as I can tell, the top and bottom it's only cutting off half the lines that are there, so they don't need to go in as far.

hmm, this is a problem because for whatever reason, it failed to do the update I did, and I can barely see the reason why, think it says failed to verify whole-file signature. hmmm, do I need to use the CWM to do the released firmwares or can I do it the normal way?
[Fire TV Android Development] rbox:
Ah, I was wondering about the overscan people. I did have a thread a few days ago asking about resolutions and people had mentioned about overscan. I'll see what I can do about adding a "safe zone" around the edge where it doesn't write any text. As for mouse... it's supposed to ignore them but it might not be. I'll check on that.
[Fire TV Android Development] nyder:
When I try to do an update to the official bueller-ota-51.1.1.0_user_511069920-signed firmware, I keep getting a "failed to verify whole-file signature"

This has happened twice in a row, and I have updated my AFTV with this firmware before. Any ideas what the problem is? I'm doing this firmware because I am having Link2SD problems and the person helping me is on that firmware, so we were trying to match up to work out my issues.

Any ideas on what I do?
[Fire TV Android Development] rbox:
If you are using the stock recovery with the stock updates, please start a new thread. This thread is for cwm recovery.
[Fire TV Android Development] nyder:
I am using your cwm recovery. I just installed it, seems to be working fine. That is why I mention the overscan above? I am running your CWM. Now, because I am running your CWM I can not use the http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ method of updating my firmware back up to the one I mentioned in an above post. I keep getting that error. Never got this error on the stock recovery.

So yes, this is a CWM post and it's not letting me update when I was able to use the same file to update before.

Okay, I get what is going on, because of the overscan, I wasn't able to see what was printed very well, but apparently I had an option to install the untrusted zip file, which is seems to have failed on. hmm, guess I will try to install this firmware like you do for your prerooted ones.

Okay, when trying to install stock firmwares, you get this error:

!less_than_int(1404177321, getprop("ro.build.date.utc"))

error in /data/media/0/rom.zip

Status 7

Then i tell it to ignore signatures, and it runs some more, then I get failed to verify whole-file signature.

Then it asks if you want to install untrust.zip and then when you highlight it and hit enter, it fails on you with the error I put above.

This is on both stock firmwares. Get the same from using CWM to install them, or by doing the old way.

Going to try your prerooted one now
[Fire TV Android Development] rbox:
As the OP states:

Which is why I was confused as to if you were using CWM or stock recovery.
[Fire TV Android Development] nyder:
ah, well I am an idiot then. =) No wonder it wasn't working, lol.

Okay, sorry for wasting your time.
[Fire TV Android Development] mongolx:
when I try to push recovery.img i get;

failed to copy ‘recovery.img’ to ‘//recovery.img’: Read-only file system

downgraded to 51.1.0.2_user_510058520,
[Fire TV Android Development] nyder:
sounds like you didn't do the SU command first. Or you don't have machine rooted.
[Fire TV Android Development] mongolx:
machine is rooted with busy box.

rooted it again started supersu............... This is command input

C:\SDK\sdk\platform-tools>adb push recovery.img / sdcard/

failed to copy 'recovery.img' to '//recovery.img': Read-only file system

following guide on

http://www.aftvnews.com/how-to-inst...-recovery-on-the-amazon-fire-tv/#comment-7218
[Fire TV Android Development] nyder:
Okay, if you type adb push recovery.img / sdcard/ then yes, that will fail.

adb push recovery.img /sdcard/ won't fail.

If that was just a typing error when you posted here, you are going to have to wait for someone will more knowledge then me to answer it.
[Fire TV Android Development] toe-rag:
will we be able to backup/restore using this?

I would love to be able to clone my AFTVs ..

I have 4 of them... one now with your CWM Recovery installed.

If I install on all, will I be able to create an image on the one I want to clone, and restore that image to the other 3?
[Fire TV Android Development] jocala:
If you're doing the push as you show you've got an imbedded space.

adb push recovery.img / sdcard/

Try:

adb push recovery.img /sdcard/

Your push is pushing recovery.img to /, the filesystem root.
[Fire TV Android Development] toe-rag:
Screen calibration issue 52" Bravia (Sony)

Much of the text is OFF screen on the left side, and when running, installing .... off the bottom.

is there a way to calibrate and save those settings?
[Fire TV Android Development] rbox:
It would probably work. I don't know if there are any device specific things in /data that would mess it up.

You're the second person to mention this. It's already on my list of things to do. I'll probably be releasing a new version this weekend, and I'll try to get this in it. But it would help if you quantify "much". A picture would be best.
[Fire TV Android Development] toe-rag:
[IMG="TOP Left"]https://dl.dropboxusercontent.com/u/9834004/IMG_3928.JPG[/IMG]

[IMG="BOTTOM Left"]https://dl.dropboxusercontent.com/u/9834004/IMG_3929.JPG[/IMG]

[IMG="Whole Screen Left"]https://dl.dropboxusercontent.com/u/9834004/IMG_3931.JPG[/IMG]
[Fire TV Android Development] collindv:
Has anyone successfully backed up to a USB drive? I can't figure it out. I am using a powered hub and have tried 4 different USB drives. I am booting with them attached to the hub. The only options I see in CWM under "backup and restore" all pertain to the "sdcard"
[Fire TV Android Development] rbox:
If you connect over adb, do you see a /dev/sda? I only have an unpowered hub and I know the only way I was able to get it to see the usb storage was not using a hub and plugging it in directly. But if it works while the OS is booted, there is no reason it shouldn't work in recovery. I may have broken something. It's on my list to double check the functionality.
[Fire TV Android Development] toe-rag:
nope .. I tried the same, then looked for the file, to no avail? didn't really know what to look for and where. I have an issue with seeing all the text so it's hard to see what's happening. I'm afraid to really do anything cuz I can't see what is being written to the screen to respond.

I assumed it was writting to the root of the AFTV sdcard folder yet there wasn't a file to be found -- there. Plus I got a android graphic with a red explaination point- in the center of the screen, so I'm assuming it failed?

[IMG="red error?"]https://dl.dropboxusercontent.com/u/9834004/IMG_3930.JPG[/IMG]
[Fire TV Android Development] collindv:
Unfortunately I only have a wireless connection so I can't connect via adb. The drive is mounted fine when the os is booted as I can explore it via es explorer.

I also have the over scan issue where the text is cut off on the sides, top and bottom.

---------- Post added at 07:25 PM ---------- Previous post was at 07:21 PM ----------

The default backup location seems to be /data/media/clockworkmod/backup.

I believe also that the exclamation android means it failed (likely not enough space). I am having the same issue.
[Fire TV Android Development] mongolx:
I had issues with loading recovery and rooted zip. I think issue was moving apps and files to usb. Did factory wipe rooted pushed recovery wiped again loaded rooted zip without problems. Just be careful don't let it update to new software.
[Fire TV Android Development] chadamir:
Is there a way to navigate or install without a keyboard? Maybe using adb shell input keyevent? I could not get that working.
[Fire TV Android Development] rbox:
There is, but because I haven't added in input hotplug support yet it's a little tricky. You need to have 2 adb shells open. In the first one run:

/sbin/recovery-input

In the second one, run

killall recovery

Recovery should restart and you should be able to use recovery-input to control it. Let me know if you have any questions with it.
[Fire TV Android Development] chadamir:
I put in recovery-input and it says that i can use up for up etc. Then I went to the second window and typed killall recovery. It restarted. Hitting keys in the shell didn't do anything subsequently nor did it work if I typed recovery-input again.
[Fire TV Android Development] rbox:
You switched back to the shell you originally ran recovery-input from? Starting it again isn't going to work because you have to restart recovery anytime you start a new one.
[Fire TV Android Development] Demonoid111:
Hey Rbox, do you think you can take a look at doing something like this for the HDX?
[Fire TV Android Development] chadamir:
yep. it shows previously typed commands at the bottom and they change when I hit up or down as though it were at a command prompt. Have you gotten this to work?
[Fire TV Android Development] rbox:
If you are seeing previous commands you aren't sending them in to the window you started recovery-input from. Open 1 window, run adb shell, then run /sbin/recovery-input. Open a 2nd window, run adb shell, run killall recovery, close that window, switch back to the first window, and using the arrow keys should work. Yes, I used this a lot while testing things.
[Fire TV Android Development] rbox:
What do you mean?
[Fire TV Android Development] chadamir:
It's definitely the window I ran recovery-input in. I'm running it from dos. I'm not sure if that matters. It's the arrow keys correct?
[Fire TV Android Development] rbox:
OK. I just tried it in Windows and it looks like it doesn't work. This really was just a quick test program I wrote for me to use that I never removed. I'll see what I can do about fixing it for Windows but probably won't get to it for the next version.
[Fire TV Android Development] mjbxx:
Fairly sure that [MENTION=5677639]Demonoid111[/MENTION] is referring to the Kindle Fire HDX.
[Fire TV Android Development] AFTVnews.com:
/sbin/recovery-input works for me using OS X Terminal

As for mounting a USB drive, neither a powered nor unpowered hub worked. There was no indication that a drive was connected.

Plugging the drive directly into the Fire TVs USB port (and using /sbin/recovery-input) was better, but not functional. The "mounts and storage" menu listed "mount /storage/usbdisk/", however selecting it resulted in the message "Error mounting storage/usbdisk/ !"

Also, /dev/sda does not exist.

Here are images of the log (not sure how to export it):

Image 1 - USB drive inserted directly into USB port, then rebooted into recovery, then immediately went to advanced > log

http://i.imgur.com/w0kFJcm.jpg

Image 2 - Backed out of log screen, went to "mounts and storage", selected mount /storage/usbdisk/", backed out and went back to log screen

http://i.imgur.com/Yz8o09a.jpg
[Fire TV Android Development] rbox:
Well for starters, to pull the log off adb pull /tmp/recovery.log.

It's good to know that it's actually semi working and I'm not just crazy. I'll have to try to figure out why it's not working at all if a hub is plugged in. I think when I tested it, I formatted the drive directly as fat32 and didn't partition. How is yours set up?

I'm not going to be home until Friday night, but I'll definitely look at this some more then.
[Fire TV Android Development] AFTVnews.com:
As far as formatting, it's pretty odd. The one I started testing with (and the one I took those screenshots with) is a 64GB single NTFS partition. I wanted to try FAT32 but I didn't want to format this drive (too much data to offload), so I continued testing with a 4GB drive with a single FAT32 partition. CWM wouldn't see that drive at all. I then formatted the 4GB drive to NTFS and CWM still didn't see it. Then I formatted it to exFat, and CWM saw it the same way it saw the 64GB NTFS drive.

It's possible the 4GB drive has issues as I haven't used it in a while, but I stopped messing with it at that point. I'll try different drives later when I have the time, so that I can rule out my 4GB drive being the problem.
[Fire TV Android Development] tavery:
My FAT32 single partition, 32GB drive acts exactly as your 4GB drive does, through a powered or unpowered hub.
[Fire TV Android Development] jmandawg:
Same here, no go with usb stick and hub.
[Fire TV Android Development] gazdaman.:
I am on 51.1.0.1

Can I install recovery on this FW?
[Fire TV Android Development] schneid:
Seems so:

http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
[Fire TV Android Development] gazdaman.:
Cheers for that
[Fire TV Android Development] Demonoid111:
As far as I know, the Kindle Fire HDX and the Fire TV suffer from the same bootloader limitations. They're both qualcomm devices which have extremely secure bootloaders. Right now, the Kindle Fire HDX doesn't have any reliable form of custom recovery other than Safestrap.

So, as far as I know, you managed to bypass the bootloader issue for the Fire TV. Since the two devices are similar, can you see if the same is possible for the HDX? How'd you do it?
[Fire TV Android Development] rbox:
I don't have an HDX. But in theory if it's downgradable or its a device that hasn't been updated, it would probably have the bug in it.
[Fire TV Android Development] mastafunk:
So was the bootloader just not actually locked but appearing so in <51.1.1 firmwares. Doesn't seem like we are exploiting anything just dumping a new image to the recovery partition. If the boot loader were actually locked wouldn't it prevent us from booting these modified pre rooted images?
[Fire TV Android Development] rbox:
The bootloader only checks recovery and boot, not /system. The prerooted images have the stock kernel, so the signature is good. The recovery image has special stuff done to it to allow it to boot. But the bootloader is still very much locked.
[Fire TV Android Development] Velda2222:
Did you use the signature fudging described in CVE-2014-0973? If so do you have a script you use to fudge the signature and would you be willing to share it?
[Fire TV Android Development] rbox:
At this time I'm not distributing my method, sorry.
[Fire TV Android Development] Velda2222:
No worries. Maybe you'll change your mind later down the road. :)
[Fire TV Android Development] rbox:
6.0.5.1.0

I have updated the OP with 6.0.5.1.0. It seemed like some people needed overscan, so I have added it. It's not the best right now, but I can make it adjustable if people so desire. I've also fixed USB storage, so I'd like to know if people can actually get it working with hubs or if connecting it directly is required. Finally, someone asked about adb sideload, and I have gotten that to work as well.

I'd also like to thank everyone who has donated. It's much appreciated.
[Fire TV Android Development] gehx:
rbox thanks for this!! i can actually read the txt now. It doesn't seem to recognize my thumb drives, i've tried 2, both formatted fat32. Connected w/ wireless kb dongle to a powered usb hub. the only storage listed in backup is /sdcard.
[Fire TV Android Development] rbox:
With a hub the keyboard is working but the storage isn't? That's interesting. Can you connect with adb shell, run

dmesg > /sdcard/dmesg.txt

and

ls /dev/block

and then

adb pull /sdcard/dmesg.txt

and

adb pull /tmp/recovery.log

and put all that on a pastebin site like pastebin.com? If the keyboard worked on a hub I would have expected the USB storage to work as well.
[Fire TV Android Development] gehx:
adb won't connect. Also, i'm using a wireless keyboard with dongle connected to the hub if that matters. The keyboard has worked in both revs. of your recovery, just not usb storage (for me anyway).
[Fire TV Android Development] rbox:
adb will only work over ethernet. The ip should be the same as when you are booted into the OS.
[Fire TV Android Development] gehx:
That's how my box is setup, wired.
[Fire TV Android Development] rbox:
Odd,

adb connect ipaddr

should work.
[Fire TV Android Development] gehx:
C:\Users\gehx>adb connect 192.168.1.6
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.6:5555
[Fire TV Android Development] rbox:
And I assume it works when you are booted into the OS? Can you ping that ip? It's possible your router is giving it a different IP address. Does your router have a status page that shows all the active computers?
[Fire TV Android Development] gehx:
so weird, when it's in recovery the ip is .8

anyway here are the paste's you req'd:

dmsg.txt

recovery.log
[Fire TV Android Development] rbox:
OK. It looks like it is seeing the device, but it's path is probably different because it's behind a hub. From adb shell run this:

find /sys -name '*sda*'

.
[Fire TV Android Development] gehx:
/sys/devices/platform/msm_hsusb_host/usb4/4-1/4-1.1/4-1.1:1.0/host0/target0:0:0/
0:0:0:0/block/sda
/sys/devices/platform/msm_hsusb_host/usb4/4-1/4-1.1/4-1.1:1.0/host0/target0:0:0/
0:0:0:0/block/sda/sda1
/sys/block/sda
/sys/class/block/sda
/sys/class/block/sda1
[Fire TV Android Development] rbox:
Yup. Thanks. Exactly what I thought. I'm compiling a new version right now.
[Fire TV Android Development] gehx:
You're welcome, your work is much appreciated! Looking forward to the new build.
[Fire TV Android Development] rbox:
I updated the OP with 6.0.5.1.1. /storage/usbdisk should show up for you now.
[Fire TV Android Development] roligov:
I can confirm that after the new update I can see my USB flash drive which is connected to a hub. I also installed the latest pre-rooted firmware that same usb flash drive! Thanks Rbox!
[Fire TV Android Development] toe-rag:
UPGRADE to latest recovery ... 6.0.5.1.1

I didn't see any install instructions to upgrade to the latest version?

the requirement on the original install was to downgrade if version was too new.... Is that still required? as I'm running the latest pre-rooted image.

what is the proccedure?

Found it ... skip step #1

---------- Post added at 07:47 AM ---------- Previous post was at 07:01 AM ----------

I've been able to do a successful backup to external USB. Thanks rbox!

I can now see the entire screen, no need to have it user resizable at least from my experience. (Thanks again!)

my question is now that I have this backup, if restored to another AFTV will it be a clone of the donor? I noticed that it said it did NOT backup applications?

and that there are still unknowns as to being device specific --

any guidance before I try this restore to another AFTV would be appreciated.

and oh yeah the file name/folder is that a date stamp just WAY off?

[IMG="image1"]https://dl.dropboxusercontent.com/u/9834004/Web_Images/IMG_3938.JPG[/IMG]

[IMG="image2"]https://dl.dropboxusercontent.com/u/9834004/Web_Images/IMG_3939.JPG[/IMG]

[IMG="image3"]https://dl.dropboxusercontent.com/u/9834004/Web_Images/IMG_3940.JPG[/IMG]
[Fire TV Android Development] rbox:
It said it's skipping backup of applications from .android_secure. I don't think the Fire TV uses that, so just ignore it. Applciations are stored in /data, and that was backed up. As for restoring onto another device. I'd say go ahead and try it and see what happens. Worst that can happen is something is broken and you just need to factory reset it.

As for the time being wrong... That's a common issue on qualcomm devices. I know certain phones use a workaround in the kernel, I'll see if I can get that working.
[Fire TV Android Development] toe-rag:
Well I did a restore.. Everything came back up fine, however it truely was a clone it thought it was the donor - as far as the connection to my amazon account, I don't know why because the serial number I thought defined everything.

Anyway long story short, I had to de-register both AFTVs & I did a factory restore on the clone ... before I got things back to normal. I don't think I'll do that again. Easier rebuild from scratch; as I have that down pretty much, and just do an XBMC restore to clone the UI experience and to get all my addons installed quickly.:)

I was surprised to see that after starting the factory restore - the CWM recovery popped up, I guess that IS the recovery now? It came back up 51.1.3 rooted as I hoped. rebuilt everything manually - and I'm back up and running.

I was so comfortable with the process, that I installed CWM and 51.1.3(pre-rooted) on all the rest (4) of my AFTVs.

Thanks again for all your hard work on this. I'll do individual backups of each shortly -
[Fire TV Android Development] gehx:
thanks rbox! works great, just backed up both of my boxes :)