yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] moeduss:
I thought about that but didn't want brick, if I factory reset do I need to start the whole process of root and boot loader unlock all over again?
[Fire TV Android Development] rbox:
Factory reset has nothing to do with root or bootloader.
[Fire TV Android Development] moeduss:
Ok thank you.

---------- Post added at 11:56 PM ---------- Previous post was at 11:28 PM ----------

Worke perfect, thank you.
[Fire TV Android Development] purav17:
For some reason I do not see my FTV when i connect it to a linux machine. It has been bricked and I am trying to revive it. Any advice?
[Fire TV Android Development] pshempel:
Seems I am in the same boat as some of you here. I have a unlocked boot loader for now a year and had the old CWM and boot manager installed

After installing TWRP I had issues with the boot loop some have had here and I installed the test image that worked great. During the first install of the TWRP, I had boot into the old fireos and it worked just fine. I had booted a number of times with no issues trying to get past the boot loop.

Once I was past the boot loop I installed to the pre-rooted bueller-5.0.5.1-rooted_r1.zip, I also did a wipe prior to installing, since I had a bit of some hacks done on the older OS did not want the old cruft left behind.

I booted up into the system, logged into my account and watched the Amazon startup clip. I rebooted the system and now there is nothing, it won't power on, no lights.

I plugged it into the USB on my (LINUX) box and don't even see a USB device when doing lsusb. Not sure how to fix this. Without recovery not much I can do except do the hardware method (soldering required)

Unless someone can share a fix I will research a way to reload recovery again via hardware.

I am going to try the emmc approach to fixing this since it does look to me as if it is bricked at this point.

:(

Thanks, I have another v1 that I am going to work with, but this one does not have an unlocked boot loader. We will see what happens to this one.

[MENTION=3991724]rbox[/MENTION] - if you want this system for post mortem let me know so I can send it over for you to look at.
[Fire TV Android Development] busventinc:
[MENTION=3991724]rbox[/MENTION] everything went smooth for me and now my box is upgraded thanks for everything you do my box is still rooted and working great..
[Fire TV Android Development] purav17:
Follow the instructions by Rbox ...Link below. I got my dead FTV working with that.

http://xdaforums.com/showpost.php?p=66961740&postcount=676
[Fire TV Android Development] pshempel:
rbox, now after dd'ing all of the images to my ftv, is has gone into download mode,

lusub shows

Bus 003 Device 026: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Is there any other way to recover from download mode now?
[Fire TV Android Development] rbox:
If it's not showing up as a storage device anymore, then you didn't follow all the directions, and it's bricked.
[Fire TV Android Development] davekaz:
Same thanks so much rbox
[Fire TV Android Development] smartymcfly:
I am just wondering if it is even worth updating from rooted OS3 to the rooted OS5? What does it add to the FireTV that isn't available FireOS3?

I haven't seen anything other than people having problems when updating and the software actually being less functional than it was on FireOS3.

Please enlighten me.
[Fire TV Android Development] realtuxen:
alexa is the biggest difference I think. read up on aftvnews, elias documents every little new feature good, bad or hidden.
[Fire TV Android Development] sirxdroid:
And also that sideloaded apps now show up on the Home screen. Potential Live TV in the future too, though that may not be too interesting.
[Fire TV Android Development] schneid:
I did it I think by side loading settings.apk that I think i found here. Had to do it to use a weather app.

Maybe this one:

http://xdaforums.com/fire-tv/help/android-settings-apk-t2850772
[Fire TV Android Development] eerolltide06:
I'm assuming installing this wipes all currently installed apps, is that a correct statement? Or does it just update and keep all the apps as is?
[Fire TV Android Development] rbox:
The prerooted images just touch /system. It doesn't change /data.
[Fire TV Android Development] kLONkRIEGER90:
Is it possible update from 720 (german) to 820 and then install the prerooted version of your 820 (51.1.3.0_user_513011820) ?

Or how you root the 820 F/W

Greetings
[Fire TV Android Development] rbox:
You can't root 51.1.3.0.
[Fire TV Android Development] kLONkRIEGER90:
:'( damn, can I downgrade the version? with your tutorial? or not ?

THX and Nice work :) !!!
[Fire TV Android Development] rbox:
All this information is on XDA. It just takes you know... reading. Downgrading requires root...
[Fire TV Android Development] roligov:
Is it safe to do a factory reset with a pre-rooted firmware? I have the custom recovery menu so I'm not to worried, just wondering if a factory reset could possible break either recovery for firmware?
[Fire TV Android Development] rbox:
Yes it is safe. All it does is wipe /cache and /data.
[Fire TV Android Development] Y314K:
So if we where to do a Factory Reset from a PreRotted FW & CWM Recovery installed we would still have root & dcp disabled ? Please clarify the following....

1. We do not need to go back to Stock FW or Recovery to do a proper Factory reset, right ?

2. Will the "disabling dcp" mod need to re-done or will the Factory Reset keep the dcp disabled ?

3. We will need to go thru the same steps as on first boot (setup Amazon account) except the PreRooted FW will not check for FW updates ?

4. We will need to turn off USB Debugging on again ?

5. We will need to sideload/reinstall SuperSU, BusyBox & any other thing he have used in the past except for TowelRoot since the device is already rooted ?

6. I wanted to upgrade to SuperSU Pro & BusyBox Pro. Guess doing a Factory Reset would help to make sure the upgrade to Pro was done right ?

Did I miss anything...
[Fire TV Android Development] rbox:
You never have to go to stock anything for anything.

The disable state of packages is kept in /data, so if you factory reset, you lose that and you have to redo it.

Yes, you have to do everything including watching the stupid video. If will check for updates. Thats why you should always use the latest prerooted version. But recovery will refuse to flash it, so you can't accidently flash the stock rom.

All settings are stored in /data. Anything setting you have made, dcp, adb, whatever. Has to be redone.

The prerooted roms are called prerooted because... well they come with supersu. Anything you put in /system like busybox will stay, but you will lose the busybox apk that was installed.

Factory reset has nothing to do with any of that.
[Fire TV Android Development] Y314K:
Thanks a lot for the clarifications...

Just to make sure...

1. The only way to loose root & CWM with any PreRooted flashed FTV is to manually/deliveredly reflashing STOCK Recovery & then flashing Stock FW or letting it update ?

2. The only thing that will be gone will be the sideloaded APK's but any programs install in /System like busybox will be in the Programs list and usable. What about any of their saved settings ?

By the way. FTV's are going back on sale at Staples tomorrow. Plan to get one maybe two more.

Really hope there is a new TowelRoot soon so we can stop worrying about getting the last rootable batch of FTV's...
[Fire TV Android Development] rbox:
Yes. If you go out of your way to do stupid things, bad things will happen.

ALL SETTINGS ARE IN /data.
[Fire TV Android Development] spyder3:
Why are the ROMs called pre-rooted? That word doesn't make sense to me. I would understand calling them "custom" or "rooted", but "pre-rooted" is effing with my brain.
[Fire TV Android Development] rbox:
Well it's not custom because it's 100% stock Amazon, just with some firmware taken out and root put in it. I suppose "rooted" would work too. But when I came up with the idea of doing this when I first started working on recovery, "prerooted" was the first word I thought of. They are rooted before you get them, so it's pre-rooted. Like how when you get a new computer and they say something is "pre-installed" on it.
[Fire TV Android Development] schneid:
Doing a Factory Reset from Rbox Recovery

For those of you that fear this, fear not. My AFTV was rebooting during movies. Very annoying. Tried lots of things but no joy so i decided to start over. I had Rbox Recovery and latest pre-rooted 820. Yes I was already rooted.

I booted into Recovery and selected Factory Reset and confirmed choice. It deleted data and cache.

When complete, I restarted the system.

It rebooted and stalled at finding remote.

I unplugged it to get a cold boot.

It came up asking me to press Play/Pause ( >|| ).

It began checking for updates. Scary but it it gave up quickly.

Asked me to log on to my account, pick language, and watch a movie.

So it seems to work safely. Updates don't work - good but all your custom apps and settings are gone - bad but that was my goal.

SU is working as i can connect with ADB and the two utility apps.

Don't know yet if my problem got fixed.

Bottom line. You can Factory Wipe Rbox's ROM's from his recovery without loosing root or being vulnerable to Amazon Updates.
[Fire TV Android Development] rbox:
You didn't get an update because you are on the latest version. You still need to block dcp or else the next time an update comes it'll try to download and flash it and it'll be annoying.
[Fire TV Android Development] schneid:
Okay. I did do the block thing with one of utility apps and also have it blocked on the router. Just did a whole movie without a crash. Now I can start trying to break it again.

Does this mean an update attempt will fail but will be be a PIA?

"or else the next time an update comes it'll try to download and flash it and it'll be annoying."
[Fire TV Android Development] rbox:
Depending on what you block on the router, it'll always be trying to check for updates in the background. If you block dcp, thats all you need and you'll be golden. If you don't block anything, and it notices there is an update, it will download it, reboot to recovery, and then just sit there. And then you'll have to reboot, and then it'll probably do the same thing over.
[Fire TV Android Development] spyder3:
That makes sense to me now. Sorry, I kept reading pre-rooted and thinking "before root". I knew that wasn't the case, but my OCD was pinging. lol

Are there any new features available on the newer firmware versions as opposed to 5.1.1.1.0? Or is it just root blocking stuff?
[Fire TV Android Development] schneid:
Things I've noticed:

1. Allows DD 5.1 over HDMI for those with receivers that choke on DD+.

2. Allows 1080P 24fps via secret keystrokes. Picture definition is visibly better to me.

Cons:

Cannot get PlayStore to work.

I use NovaLaucher via Rbox mods as Home Screen. Used to be able to use Widgets but no more. None will work.
[Fire TV Android Development] smartymcfly:
Secret keystrokes?
[Fire TV Android Development] ldeveraux:
Plex works the way it's supposed to now...
[Fire TV Android Development] schneid:
Ne sure to read to bottom for "Update". Guess its always been there.

http://www.aftvnews.com/how-to-access-hidden-resolution-options-on-the-fire-tv/

Changes framerate too. I have real 1080p 24fps. To me seems to be BD quality.
[Fire TV Android Development] veeroohre:
Bootloop

I'm on 5.0.5 r1 with a locked bootloader. Unfortunately when starting I'm in a bootloop when loading the OS. So after seeing the Amazon splash screen my FireTV1 reboots. Booting into TWRP works without a problem. Once I managed to boot into the OS. But I cannot repeat it.

Can someone help me? I search in this thread but I only found the bootloop problem when wanting to boot into TWRP. Thanks in advance!
[Fire TV Android Development] veeroohre:
Thank you for the link. Didn't help though. Nothing in it regarding my problem.
[Fire TV Android Development] rbox:
So bootmenu works, and the colored logo shows, but then it reboots? Do a factory reset.
[Fire TV Android Development] veeroohre:
Exactly. I'll try it although the last time I did this I really had difficulties to prevent an update. When I blocked the download URLs via OpenDNS FireTV denied to continue in the start wizard. Any advice for this problem?
[Fire TV Android Development] rbox:
If you install the current version, it should probably work. I don't know if they are pushing out the super latest.
[Fire TV Android Development] veeroohre:
I try to avoid the last version because I like FireStarter and see no added value in this firmware.

By the way: Is there a way to make an nandroid backup (like on smartphones) shortly after the wizard finished and flash it again when having problems.
[Fire TV Android Development] rbox:
You can always flash the latest, set it up, then block updates, then install the old one you want. It should handle downgrade just fine.

Do the setup, then reboot into recovery, and do a backup.
[Fire TV Android Development] evaporic:
When I open ES File Explorer and try to enable ROOT access on this ROM it says "ES File Explorer has been granted Superuser permissions" then : " Sorry test filed. This feature cannot run on your phone''

I've tried different versions of the app and different versions of root explorer but I can't seem to be able to overwrite or modify /system/usr/keylayout files.

Do I need to flash something else in recovery?
[Fire TV Android Development] assyriska:
I get the same error message on "ES File Explorer"....now I'm using TotalCommander and it is working very well.... so just use Total Commander ^^
[Fire TV Android Development] d3adpool:
i'm getting that same error message. It was working fine a few days ago, i rebooted my ftv and it kept looping from amazon screen to home screen. I had to reinstall rom and now this is what I'm getting.
[Fire TV Android Development] Jimmy8881:
try installing busybox, could be related
[Fire TV Android Development] evaporic:
Neither Total Commander nor busybox resolved the issue :confused:
[Fire TV Android Development] d3adpool:
You don't have root access with Total commander? That did solve my problem, with root access to the internal harddrive at least.
[Fire TV Android Development] evaporic:
Even though total commander says I have root access I am not able to modify files in system/usr/keylayout. I have the same issue with root explorer and file explorer ES
[Fire TV Android Development] Squalll13:
Just reporting some notes and my experience. Just installed the latest pre-rooted stock images 5.0.5.1_r1.

- Was from FireOS 3 before with a fully unlocked bootloader.

- Installed TWRP. Went into TWRP splash screen blinking/bootloop. Flashed the test8 fix. Looks like it's fixed

- Installed 5.0.5.1_r1. Wiped cache and dalvik cache after installation and it's working fine for now.

- Went ahead and disabled OTA updates with pm disable (not sure if it was disabled by default by the rom)

Noticed that when I go to shell, it now shows shell@bueller instead of going straight to root. If i type "su" then it goes to roo@bueller. Does this mean that I lose my fully unlocked bootloader for some reason? (checked it with cat /proc/cmdline, it says "Permission denied"

Another thing I've noticed is that I had an app running before called funkysamba that lets me map the FireTV as a network drive on my PC. I can still see it on my PC but can no longer access /sdcard for some reason.

Other than that its working fine for now. Thanks for all your hard work rbox
[Fire TV Android Development] sirxdroid:
Look forward to a pre-rooted 5.2.x for FTV1 so I can finally move from FireOS3.
[Fire TV Android Development] ldeveraux:
You can't install 5.0.5.1?
[Fire TV Android Development] sirxdroid:
I can but I'm assuming 5.2.x comes out "soon" so don't want to redo it again. Not sure whether I'd be able to upgrade the ROM without losing my data (Kodi setup, etc.)
[Fire TV Android Development] mezdev:
You can easily back up Kodi data ( File Explorer and zip and copy to usb or dropbox) I can give you quick guide if needed.;)
[Fire TV Android Development] sirxdroid:
Sure, I think adbFire can do it too.
[Fire TV Android Development] mezdev:
...................ES File explorer /sd card/Android open Data then highlight until ticked (org.xbmc.kodi for Kodi) (com.semerpax.spmc16 for SPMC) press menu button (3 parallel bars) and select compress and choose the formatt and level prefered by you.

once complete you can copy to dropbox if you have it set up in file explorer or to extenal storage connected to usb port.

To restore that file just delete the (org.xbmc.kodi for Kodi) (com.semerpax.spmc16 for SPMC) folder and move the zip into the Android/ data section to where you deleted and decompress and away you go.

You can obviously omit the zip part but I back up my personal build to zip on a regual basis and I can always restore to my last working copy if I mess up :p
[Fire TV Android Development] krasny2k5:
Hi there!

I updated my fire TV to 5.0.5.1_r1 and everything went right. But after sometime I found out that the box randomly reboots by itself and enters in the recovery from time to time. I have the updates disabled.

Anyone knows why?

Thanks!
[Fire TV Android Development] LiquidXed:
Same here..
[Fire TV Android Development] RavenII:
Just curious...how is the 5.2.1.0 rooted? King root? I'm asking because I've heard that King root is no good...
[Fire TV Android Development] xenyz:
Can you be more specific on how you've disabled updates? It does sound like they are still being downloaded and trying to be installed...

King root is the only known root exploit that's working on the latest FireOS. It's used in this case to install a new custom recovery by [MENTION=3991724]rbox[/MENTION] and then to flash a pre-rooted system image with SuperSU instead of King Root.

Generally, it's a good idea to wait for rbox's pre rooted image, but in this special case, there is no way to block updates on 5.2.1.0 without root access, so currently the best move is to bite the bullet and root with King Root, and install the older 5.0.5.1_r1 that's currently available, or disable updates and hope that King Root isn't doing something shady (risky).

If you do nothing, it's more than likely a new software release will patch the root exploit and you'll miss the window to enjoy a rooted FireTV.
[Fire TV Android Development] rbox:
I updated the OP with an updated 5.0.5 and a new 5.2.1.0. This includes the new version of TWRP for 720p and fixes for the crashing/looping.
[Fire TV Android Development] LittleBill21:
Installed TWRP .7 and the latest 5.2.1.0 on a 1080p with 0 issue.

the issue i am having though is my home screen is blank and i get errors of we can't to our servers, i can go to managed applications and start my stuff from there, but is this expected?
[Fire TV Android Development] rbox:
Sounds like your internet connection is down.
[Fire TV Android Development] LittleBill21:
its not, i did have updates blocked, which the fire box tried to access, but i did unblock it and still seeing the issue.

shouldn't i be seeing installed apps? when i say blank i mean blank there is nothing on any of the menu items expect the system settings one. also sshd server no longer allows me to sftp, which is a big deal for me. also logging into adb shell i now log in as shell, and have to su to root, is this expected?

update: had to reregister my amazon account now, everything is flowing.
[Fire TV Android Development] rbox:
What version were you on before? Every version of OS5 has required su in adb shell...
[Fire TV Android Development] LittleBill21:
i came from OS3 latest, do i need to keep updates disabled?

any idea why SFTP is not working? ssh is working fine

im using app

Rooted ssh /sftp server, sorry i can't link yet

llama apparently doesn't work on 5.x and i got my app installer working again.
[Fire TV Android Development] Axecaster:
OS3 > OS5 upgrade for AFTV1

Is a factory reset good (or even necessary) for post-update cleanup? What's the best way to perform a factory reset on an older firmware version and get through the amazon account login without forcing an automatic update to download? Just verifying since I read differing reports about auto updates still installing through TWRP.
[Fire TV Android Development] Skater4599:
Really want to thank rbox again for the updates and his work, its MUCH appreciated. I own both FTV1 and FTV2 and use rbox roms on all of them!
[Fire TV Android Development] LittleBill21:
[MENTION=3991724]rbox[/MENTION],

please explain one thing to me, why can't i access anything on the sd card, when logged in as root? in shell i can access everything fine?
[Fire TV Android Development] Nesmaster75:
Thank you for everything, rbox! It's been a little while since I turned this thing on, but I'll be putting it to use tonight!
[Fire TV Android Development] rbox:
It's always best to make sure updates are disabled. As for things not working in OS5, there are quite a few posts discussing all the various things that do and do not work. This thread is not really focused on those kinds of things, so feel free to post in the Q&A or General section if you have problems with specific apps.

No, factory reset isn't really needed. But you can always install the latest version and then factory reset to your hearts content without worrying about updates if you think you need to.

This has bothered me for some time now. It has to do with a setting in SuperSU. I just updated the OP with a link to a TWRP flashable zip file to fix it.
[Fire TV Android Development] notsed:
I finally upgraded now that all the kinks were worked out (thanks rbox!) but at the moment there are too many little quirks with OS5 that I don't like. For the simple way I use the box I'd really like to go back to the way I had it.

Has anyone tried going back to CWM and OS3 from TWRP and OS5? Think it's safe to try?
[Fire TV Android Development] LittleBill21:
for us stupid people, simply drop into recovery and install this just like a rom? then reboot?
[Fire TV Android Development] lightning413:
Yes, install from recovery just like a rom.

[MENTION=3991724]rbox[/MENTION] Any idea why I have to disable and re-enable ADB debugging everytime I restart the FTV?

ADB connects but shows the device as offline until I do so.
[Fire TV Android Development] LittleBill21:
i see this as well...

---------- Post added at 04:17 PM ---------- Previous post was at 04:04 PM ----------

fix worked like a charm.
[Fire TV Android Development] rbox:
USB or ethernet? I never have ethernet problems.
[Fire TV Android Development] lightning413:
Ethernet
[Fire TV Android Development] notsed:
To answer my own question: you can downgrade. I used this guide then this guide replacing "dd if=/sdcard" with "dd if=/data/media/0" in the commands like so:

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

dd if=/data/media/0/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot

Then I rebooted to recovery and tried to overwrite OS5 with OS3, but that didn't work (no surprise). I did a factory reset in CWM and installed 51.1.6.3_516012020 and everything went well.
[Fire TV Android Development] cd2022:
^This also fixes the issue I had with Samba connectivity from PC. Thanks rbox.