yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] sajid44:
No, I only formatted system.

I rebooted multiple times and tried Alt+prnt srn+I but it is stuck at Amazon white screen. It won't go the the CWM recovery.

Any idea how to fix?
[Fire TV Android Development] jmandawg:
If there is no way to get into recovery you will have to access the emmc via the hardware root method and copy system back over. Wait for rbox to reply, he may have a better solution.
[Fire TV Android Development] sajid44:
OK thanks....I will wait for rbox to reply.
[Fire TV Android Development] rbox:
Doing the printscreen thing enough times *should* trigger it... If /system is formatted it'll still boot the kernel and do it's think and it *should* just sit there being stupid not knowing what to do because it can't start the Android userland. There really is no other way to get in to recovery that we know of. I still believe there is some way to trigger it while it's in the bootloader, because the stock LK source code has one... but I have no clue what Amazon may have done to modify that.
[Fire TV Android Development] spyder3:
Will the install of this or your upcoming TWRP recoveries ever be made possible without downgrading?
[Fire TV Android Development] rbox:
If you have root and are comfortable with using adb shell and dd yes, you can PM me and I can explain how. But it's just easier to have people downgrade, less error prone.
[Fire TV Android Development] {ParanoiA}:
Some keyboards use sysrq instead of print scr. Maybe try that for recovery
[Fire TV Android Development] rbox:
I updated the OP with 6.0.5.1.4. It now works with ext4 usb hard drives. But the biggest thing to note is this now requires that you unlock your bootloader.
[Fire TV Android Development] Y314K:
Great :confused:

So it just leaves it unlock for the EXT4 part to work ? But we should be able to access uploaded files easier.. And be able to clear things better... Am I missing any other benefits...

Will downgrading to CWM v6.0.5.1.3 relock the bootloader ?

Any drawbacks or perils of running with an unlocked bootloader ? Either from Amazon or from 3rd party apps ??

Any other/extra benefits of running an ulocked bootloader ?

Anything else we should know about an unlocked bootloader before flashing it???

Thanks for our continuing work RBox... :good:
[Fire TV Android Development] rbox:
No, the unlock is independent of recovery. But using 6.0.5.1.4 requires you unlock.

Not that I know of.

You'll be able to upgrade to future versions of CWM?

No.
[Fire TV Android Development] Y314K:
How do we unlock or relock our FTV bootloader ??

And will an unlock bootloader help with your Exposed Mods...
[Fire TV Android Development] rbox:
The tool is linked from the post...

No. Unlock only helps with booting kernels and recovery.
[Fire TV Android Development] Y314K:
Ahh.. Now I see it has become the new step one. Had completely missed it.. Thanks again for moving the goal posts for modding a rooted FTV forward.. And for the patience of dealing with us code noobs... Really appreciated.. :good:
[Fire TV Android Development] o-I-c:
Thanks you, All in no fuss :cool:

Cheers
[Fire TV Android Development] imtiajmeah:
Hi rbox

I think the /sbin/recovery-input is missing from CWM Recovery 6.0.5.1.4

Error:

~ # /sbin/recovery-input

/sbin/sh: /sbin/recovery-input: not found
[Fire TV Android Development] rbox:
I just updated the OP with 6.0.5.1.4a which includes the missing recovery-input.

Thanks.
[Fire TV Android Development] o-I-c:
Thanks all good again with 4a

Thanks imtiajmeah i would not have known until i needed to use it :cool:

Some ask why do this upgrade/unlock

A: same reason men climb Mountains, cause its there...

or

B: What Goodies does rbox have up his sleeve.

Thanks All
[Fire TV Android Development] jmandawg:
Just some confirmation everything works. I was able to flash my stock kernel i built the other day, Unfortunately i accidentially wiped my source dir so i have to get it all setup again...

Thanks rbox
[Fire TV Android Development] chrootz:
[MENTION=3991724]rbox[/MENTION] - Hi, I updated cwm recovery latest version with the unlocked bootloader. I tried plug in the flash drive has 2 partitions fat32 and ext4.

It seems cant find my usb flash drive. It didn't show me any options on the cwm recovery. Please help thanks

[color=blue][b][u]USB Storage[/u][/b][/color]
USB storage should be working. When you go to the backup/restore menu, /storage/usbdisk should be one of the options. When you go to the install screen /storage/usbdisk should be one of the updates. FAT32 and ext4 should work. NTFS formatted partitions will not show up as an option.
[Fire TV Android Development] rbox:
I don't know what will happen with 2 partitions. You should only have 1.
[Fire TV Android Development] nyder:
NM, I'm an idiot. carry on.
[Fire TV Android Development] DEREKTROTTER:
Many thanks for this, installed without any problems.

Is there a way to permanently enable USB storage on the fireTV? So i dont have to use stickmount
[Fire TV Android Development] Y314K:
CWM Flashable: Mount external USB storage to /data and /sdcard v3 which can be installed with

[APP] [Windows] Amazon FireTV Utility App v0.30

OR a different option of some of the same script [APP] adbFire 1.14 FireTV Companion Win/Mac/Linux (Read the changelog)

Both methods should allow multiple USB storage now...
[Fire TV Android Development] cybertlc:
If I install these pre-rooted updates, will it wipe the apps/settings installed, or will it keep everything and simply update?
[Fire TV Android Development] Y314K:
If you are doing everything on the rooted side. And not clearing any cache's or formatting any mounted parts under CWM or thru ADB. But just a straight update. Then everything should stay the same. With the one exception that if you go from a 51.1.3.0 FW to the latest 51.1.4.0 FW a new NetFlix gets updated/installed by Amazon after the reboot. And you will need to input your sign-in info again. And one part of RBox's XPosed Mod's (HideAmazonMenuItems) will not work until it gets updated. But the rest of the mods work fine. But that is only if you where using that. Very minor stuff... All other apps/games/etc should stay the same.
[Fire TV Android Development] chrootz:
[MENTION=3991724]rbox[/MENTION] - What is the status on the boot menu addition on CWM recovery to allow us run kexec kernel?
[Fire TV Android Development] rbox:
It's actually something completely separate from recovery, but I just passed all my technical tests and the concepts work. I was able to kexec a kernel and it seems to run fine. Now I just need to put it all together and get the UI finished. I am currently seeking feeback (http://xdaforums.com/fire-tv/help/copying-to-t2933764) for a part of this.
[Fire TV Android Development] rotor00ter:
I remember reading something about being able to adjust the overscan in cwm recovery but I don't see where it says how to do it. For some reason everything is cut off on my screen. Can anyone shed some light on this?
[Fire TV Android Development] chrootz:
[MENTION=3991724]rbox[/MENTION] -

wonderful! I will going test it for you and I will need to buy another flash drive as full time linux image since my usb flash drive contains the file sharing (samba) and storage /data directory stuff this moment. I'll let you know once I pick up new flash drive this afternoon and test run linux kernel.

Again, a ZILLION thank you!!

Amazon FireTV using Tapatalk PRO
[Fire TV Android Development] collindv:
From the op:

Overscan

To accommodate people who need to apply overscan for their TV, I have enabled configurable overscan. By default it is disabled. You can control the amount of overscan either with FastForward and Rewind buttons or the 1 and 2 buttons. It will save it so the next time it reboots it will remember your choice.
[Fire TV Android Development] mroneeyedboh:
Easter Egg??

Says Rainbow mode enabled lol
[Fire TV Android Development] rbox:
Yes, but I didn't add it. That's a CWM feature.
[Fire TV Android Development] mroneeyedboh:
Ahh. Funny none the less.
[Fire TV Android Development] qwertywarez:
I have the same problem. Reboot recovery just reboots and freezes on the white Amazon logo. I'm on 51.1.0.1 . Never been able to enter recovery. Not even on stock.

Rbox, please help.
[Fire TV Android Development] Y314K:
Both Bovoro & CardBoardBox where able to get their units back to normal after having this problem... You can read how here: http://xdaforums.com/showthread.php?t=2796067&page=10
[Fire TV Android Development] qwertywarez:
Thanks for the link Y314K. I must have read that thread about 5 times already & been trying to access recovery for over 1 week. Just about everything found on different forums has been tried. You know of any other way to fix this recovery problem?
[Fire TV Android Development] Y314K:
Some have been able to get back trying to reflash the FW or other ways.. But the bottom line way would be to do the keyboard reset.. http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/

You might have to re-root after that.. Just make sure you are always blocking the IP's thru your router no matter what.. You can do the SuperSU check to see if your still rooted.
[Fire TV Android Development] qwertywarez:
The keyboard reset has been done about many times. It only ends up rebooting the device and freezing again at the white Amazon screen. Also tried different firmwares but the flash never completes since it never reaches recovery.

Any other ideas?
[Fire TV Android Development] Y314K:
Will follow up in your other post...
[Fire TV Android Development] xrecartp:
Frozen at the white logo. I had the same problem until I downgraded to the provided image. Used the toolbox also.
[Fire TV Android Development] qwertywarez:
Xrecartp, thanks for the support. Can you provide more details? Which image are you referring to? I am on 51.1.0.1 so there exists nothing to downgrade to.... When you say toolbox are you referring to AFTV Utility v0.30? I've tried reflashing with about 3 different tools. Was the keyboard combo method of entering recovery used?

What was the detailed step-by-step method you used?

Thanks
[Fire TV Android Development] xrecartp:
"[SCRIPT] [TOOL] Fire TV Firmware restore ota blocker root and more" is what I used.

Download the Stock Recovery file for version 51.1.1.0_user_511070220 from AFTVnews.com/software just in case.

You must unlock the bootloader from what i remember - or else the clockwork recovery wont install. And i think i downgraded anyways to the first available fw because last time i tried, i had the white logo problem when trying to install cwm.

My keyboard didnt work, so i had to use the remote keyboard emulator from my laptop to control cwm- wish i had others to try.

I think there was an option to enter recovery from the script - so thats how i added the zips and flashed to the newest pre rooted images.

Sorry its not a guide- im busy feeding a one and three yr old breakfast. I think if you follow the script tool you"ll be good. Dont forget to block ota updates.
[Fire TV Android Development] qwertywarez:
Retried with the script tool. Still not working.... starting to think that I should have purchased a Minix. FTV sucks so far.
[Fire TV Android Development] xrecartp:
Well, make sure you are rooted first with towelroot 3. And busybox install. Downgrade even if you dont think you have to. Then go from there. Hard to believe that a downgrade doesnt work.

Maybe because im used to custom roms on the tablet- try redownloading your zips\images - im not sure where you are stuck. If you have anything in the usb, unplug it first.
[Fire TV Android Development] qwertywarez:
Did everything you said except I cannot downgrade to a previous firmware since 51.1.0.1 is the first FW released. Tried reinstalling the same FW and I still get the white amazon screen freeze.
[Fire TV Android Development] xrecartp:
You renamed the rom file in the script directory and replaced it? Nothing in the usb? Its hard to troubleshoot without being there.

BTW, with busybox you actually have to run it, and install files from the menu in the progie.
[Fire TV Android Development] qwertywarez:
yup, did all of that...multiple times in fact. Same damnnn white Amazon logo. I'm running out of ideas.
[Fire TV Android Development] xrecartp:
Must be a bad ROM download or something. All I can think of.
[Fire TV Android Development] qwertywarez:
Unfortunately probably not. I cannot even reach the recovery menu of CWM. For it to be a bad ROM I would at least have to be able to install it and have it fail.
[Fire TV Android Development] xrecartp:
No. You have to boot to the downgraded rom first. Start with a clean slate - i had to. Dont even worry bout cwm yet. Then reroot busybox etc... Start over before trying cwm again.

Let us know when you have re downgraded. It'll go slow, but I'll try to help once you reinstall the stock.
[Fire TV Android Development] qwertywarez:
Ok I'll try re-downloading 51.1.0.1 rom to see if it will reinstall over itself. Maybe it is corrupt. Cannot actually downgrade the rom since 5.1.1.0.1 is the lowest public rom available.
[Fire TV Android Development] qwertywarez:
Redownloaded stock 51.1.0.1...

Ok heres what I did:

1) Using ADB shell

Su

Wipe data

2) Using FTV Tool v0.30

Uploaded busybox free (stericson)

3) Using RootJunkys v4 script

Uploaded Towelroot and SuperUser (option #1)

4) On Applications section of FTV

Ran Towelroot, then Make it rain

Ran Superuser, normal install, and set "Grant" as default

Ran Busybox and installed 1.22.1 to system/xbin

5) Using RootJunkys v4 script

First renamed 51.1.0.1 to update.zip and put in main directory

Did Firmware downgrade/restore (option #5)

Once stock recovery and update.zip has been sent, the box auto reboots to recovery

Then it freezes again at the white amazon logo without ever attempting to install update.zip.

Note that I have attempted the same procedure both manually with ADB Shell and by using other tools (ie AdBFire, etc..) with exactly the same results.

What Am I doing different?
[Fire TV Android Development] nhumber:
so you can boot the fire tv fine on 5.1.1.0.1 but you cant get CWM installed?
[Fire TV Android Development] xrecartp:
Have you tried this guide? :

http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/

Am i breaking rules with external link?

Its how i downgraded 1st. If it doesnt work this way i think something is borked. A factory reset may be in order.

Looking at the comments, people fixed their white logo by reinstalling the original recovery.
[Fire TV Android Development] qwertywarez:
Yes it boots... It only freezes at the white amazon logo when booting to recovery (CWM or stock) or doing a factory reset.
[Fire TV Android Development] xrecartp:
Multiple comments in that thread point to reflashing original recovery. *shrug*
[Fire TV Android Development] alwaysbless:
Guys maybe you can help me and this stupid guy from craigslist. I sold my pre-rooted ftv to this guy and de-registered my account after we tested it together and everything and hes claiming now that it doesnt boot at all. I had him bring it by so I can try and be a helpful guy and its stuck on this android spinning guy with a loading bar. I can still connected with adb but when i do reboot recovery it doest go into cwm, instead it just sits at a white amazon logo and then repeats the cycle all over again. If i cannot boot cwm is there a way to do a reinstall still? or would i be better off reinstalling the stock recovery? Thanks
[Fire TV Android Development] qwertywarez:
Thanks for the link. Although I've already gone through this tutorial a couple of times, I think I may have found something as I was reviewing the steps....

Step 7 of "If downgrade fails", has an image of the stock recovery installation which follows this format:

xxxxxx + 1 Records In

xxxxxx + 1 Records out

However when I flash stock recovery it says:

xxxxxx + 0 Records In

xxxxxx + 0 Records out

Should I concude that the recovery flash has failed?

If so, what should I do to force it?

Thanks
[Fire TV Android Development] nhumber:
Your missing the location of the recovery . img file.. It's a syntax error.. Push recovery . img to SD card and follow the "code" from the first post. Should work. Then.
[Fire TV Android Development] qwertywarez:
Heres what I did:

1) adb push recovery.img /sdcard/

2) adb shell

3) su

4) dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Still getting:

20480 + 0 Records In

20480 + 0 Records out

10485760 bytes transferred in 1.556 seconds

Am I forgetting anything....
[Fire TV Android Development] nhumber:
OK I'm not on a pc.. But try this if u want.. This is what I would do.. But like everything. Use at own risk

adb push recovery.img /sdcard/recovery.img

adb shell

cd /sdcard

ls

(verify u see recovery . img in the directory)

su

dd /sdcard/recovery.img of=/dev/block/mmcblk0p11

adb reboot recovery

If this doesn't work then I'd assume your recovery partition has lost its name or something. And I'd look into renaming partition 11 recovery somehow.. Parted works from cwm... But that's obviously not going to work.
[Fire TV Android Development] qwertywarez:
Thanks for the help. Just tried it and unfortunately it doesn't work. Renaming the file mmcblk0p11 is pretty easy however. I installed SSH and WinSCP. It lets me do anything I need. I even deleted as to let the function dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11 recreate it. The file got recreated but still got :

20480 + 0 Records In

20480 + 0 Records out

When AFT rebooted it still stuck at the Amazon logo. Power cycling it rebooted the device normally however.

Any other ideasÉ
[Fire TV Android Development] nhumber:
no other ideas, so for sure when you adb shell to the firetv and goto the sdcard folder the recovery.img file is in that directory? even with a mislabeled recovery partition the above command should have flashed recovery to the right spot.. your getting an error that to me looks like its not finding the recovery.img file in the /sdcard folder. i would assume your recovery partition is just empty now which is why its not booting to recovery. maybe theres another way to do this but i know of none. maybe rbox can offer a suggestion?

what was the next line returned after

20480 + 0 Records In

20480 + 0 Records out
[Fire TV Android Development] qwertywarez:
Yes the recovery.img file was in the sdcard directory. "10485760 byes transferred in 0.425 seconds" was the next line returned.

One thing I noticed however when I logged in with WinSCP is that all files in the /dev/block directory have zero bytes... weird.... but when I click "edit" it actually has stuff in it. The first line of the file has this text "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2" in it..... Maybe that helps?

I deleted all files with WinSCP in the dev/block directory (getting desperate I know).... Everything was there again when I power cycled.

Is it possible that permissions are screwed up somehow? That folder has 20 mmcblk files... Could it be another folder that needs updating?
[Fire TV Android Development] nhumber:
those arent folders, they are partitions, whatever you do, dont mess around renaming stuff there with any program. Sorry i cant be of more help, what i can tell you is the DD command looks to have worked correctly which updated the recovery partition, why its not working, i dont know.
[Fire TV Android Development] {ParanoiA}:
[MENTION=1552060]qwertywarez[/MENTION] if you can still boot normally try dd the original recovery from whatever software version you are currently on. Seems you have no recovery. If you are on 51.1.0.1 you don't need to downgrade at all.
[Fire TV Android Development] qwertywarez:
I've tried DD on both original and CWM recovery. Both freezes on "Boot recovery" command but starts fine when booting normally from power cycle.
[Fire TV Android Development] meg0n00b:
HI, I have the same problem.

I'am now on Prerooted Stock 51.1.4.0_514006420 and have CWM 6.0.5.1.3. When I'am trying to update my recovery to 6.0.5.1.4 or 6.0.5.1.4a I also have freezes when reboot into recovery.

Only CWM 6.0.5.1.3 reboots normaly.

Very strange sitiation.
[Fire TV Android Development] {ParanoiA}:
You have to be unlocked to use the latest version of recovery
[Fire TV Android Development] meg0n00b:
If I already have cwm it does not mean, that I have unlocked bootloader?
[Fire TV Android Development] {ParanoiA}:
No it does not. Read the original post very carefully.
[Fire TV Android Development] hellot1M:
Edit: deleted and moved question to the ghost town. I mean "dedicated Q & A"

Edit edit: ok screw that lol. I'll never get my question answered there. Nobody's been on that in over a month.

Original question:

I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.

When I type "su" in adb shell i get this error "system/bin/sh: su: not found"

I've googled and all I can find is reinstalling the superuser on the phone...

Edit edit edit: never mind :) missed the small print.
[Fire TV Android Development] Y314K:
[MENTION=3991724]rbox[/MENTION] - Is there a way to take screenshots when in the latest CWM ? Can that be something that can be added to the a future build ?
[Fire TV Android Development] rbox:
You can cat /dev/fb0 to a file and then use various programs to convert it. There's some tutorials about doing it. I tried it once a while ago.
[Fire TV Android Development] Y314K:
Would this be done thru ADB ?
[Fire TV Android Development] rbox:
Yes
[Fire TV Android Development] Y314K:
Great, should make better screenshots then the ones created with phones.

Unrelated ?... I had left one FTV on the CWM window for a like 20+ mins. It seems it just rebooted itself & went onto BootMenu & fully rebooted to AFTV UI. Is there a idle timeout trigger build into CWM ?
[Fire TV Android Development] rbox:
No. Kernel may have panic'd for whatever reason.
[Fire TV Android Development] Y314K:
Wonder if it is because of my setup. I run both the FTV & my PC on the same TV thru separate HDMI's. So I change the input to switch between them. I was on my PC for those 20+ minutes when I saw the window letting me know there was new input available. That is how I knew the FTV had rebooted. Switched to it & it was on the BootMenu screen. Can't remember if that had happened before.

---------- Post added at 01:52 AM ---------- Previous post was at 01:28 AM ----------

So connect a FTV booted to CWM. Open a ADB Shell & input: "cat /deb/fb0" Do I need to add the location & name or does it do it by itself ? I would like to save them to the SDCard/Download folder for easy access.
[Fire TV Android Development] AFTVnews.com:
I've also had the Fire TV reboot on me after sitting idle in CWM for a long time.

As for the CWM screenshot, get into shell with

adb shell

then run

cat /deb/fb0 > /sdcard/screenshot.raw

You'll need to pull the resulting file into Gimp or Photoshop to convert it from raw to png/jpg. I haven't actually tried this on the Fire TV, but that's how it's done on other systems.
[Fire TV Android Development] Y314K:
Great... Thanks for the commands... I am guessing for easier transfer of the raw screenshots I can mount a USB stick to CWM & just do the following commands ??

adb shell

then run

cat /deb/fb0 > /storage/usbdisk/screenshot.raw

OR

cat /deb/fb0 > /storage/usbdisk/CWM/screenshot.raw

If I have created a CWM folder in my USB Stick...

---------- Post added at 10:52 AM ---------- Previous post was at 10:33 AM ----------

Tried it this way. But I get an error..

This is using the Shell from within the AFV Utility so I wonder if the ADB included is missing anything....
[Fire TV Android Development] rbox:
/dev/fb0