yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] C0nvert:
have a bug

when i start the recovery then its like to broken (half and half) screens

i have a hd ready tv

What is this?

after 6 seconds it boots normally into the firmware

but the recovery is unusable
[Fire TV Android Development] rbox:
You probably have a 720p/1080i tv. Many people with these types of TV have seen these problems. Right now, nothing I can do about it.
[Fire TV Android Development] C0nvert:
thank you for your response :)
[Fire TV Android Development] quarky42:
From adb shell, I run su. Then I run: sh /sdcard/firetv2_recovery_v6.zip

I get: [-] Unknown username or uid

I run: su -c "sh /sdcard/firetv2_recovery_v6.zip"

and I get:

"Extracting unzip...

Remounting /system read-write...

Extracting...

Remounting /system read-only...

mount: Device or resource busy"

Any help? I'm just trying to install recovery for the first time.
[Fire TV Android Development] T0m93:
Hello, hopefully you guys can help me :)

i have Always the same Problem Installing TWRP, when i try to do the Script im getting:

Eamounting /system read-write...

mount:invalig argument

Extracting...

checkdir: cannot create extractiom directory: /system/recovery

Read-only filesystem

ln: /System/bin/ext4_resize: Read-only file system

Remounting /system read-only

Any ideas how to fix this???

I tried it with Smanager and via usb Debugging. Same result.

when i try it wirh ADBfire i get SH not found.

I used Zeropoech version of the Root (First Root Method)
[Fire TV Android Development] paradoxiumwind:
You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.

Can't seem to boot in to the recovery after flashing it, or forcing it by creating that file:

[IMG="http://i.imgur.com/uVnNIP4.png"]http://i.imgur.com/uVnNIP4.png[/IMG]

Tried 2 different keyboards and tried holding / mashing the arrow key(s) to get into the recovery but it just doesn't work. Brand new FireTV 2, rooted on Fire OS 5.0.5 (537174420).

After I run sh /sdcard/firetv2_recovery_v6.zip the fireTV just reboots after a while and the console says nothing, I'm assuming it installed fine? as it says nothing about an error.

Thanks,
[Fire TV Android Development] paradoxiumwind:
well because I couldn't boot into recovery using 3 different keyboards or forcing it, the firetv automatically upgraded and now my root is gone and i'm on 5.2.1.0 (550144920). so am I screwed now, no rooting from this version?

not like it matters since the keyboard to boot into recovery didn't work anyway.
[Fire TV Android Development] wdcspurs:
Make sure you have the specified file placed on the "root" of your SD card. Without that, you will not see the opyuon to boot into recovery. If all is done correctly you should at minimum see the twrp splash screen. I have a wireless HP keyboard and mouse that both can control and make selections on the twrp recovery.

5.2.1.0 has already been released rooted. Check the development section. But as you pointed out, not being able to make selections via a keyboard doesn't help the cause.
[Fire TV Android Development] paradoxiumwind:
where should I see TWRP? I just mash right on the keypad when it boots up, should it appear after the initial amazon logo?
[Fire TV Android Development] wdcspurs:
If all is done properly, you do not need to press anything to get to the twrp screen when the box is reset. I attached a pic. When the box is reset, you will see a basic white amazon logo followed by the twrp logo. And then the TWRP boot screen. This screen is in the pic and also is the screen where you have 5 seconds to choose to boot normally or into twrp.

I have 2 rooted boxes and forgot to put the "ramdisk-recovery.cpio.lzma" file on the "root" of the SD card on the 2nd one i did. Without that, it will not boot into recovery. Verify you have that placed on the SD card, not in a folder on there.
[Fire TV Android Development] paradoxiumwind:
yeah I've never saw that screen ever. I guess it never worked properly? but I did was rooted and such..

I am on 5.2.1.0 (550145120) (was a new update the other day) can I still root and use one of the pre-rooted stock images?

thanks guys,
[Fire TV Android Development] wdcspurs:
Yep. I updated mine to the latest and greatest and installed the ROM right after.

---------- Post added at 11:10 AM ---------- Previous post was at 11:09 AM ----------

Did you ever get the recovery working though?
[Fire TV Android Development] paradoxiumwind:
No, I think I must have been installing it incorrectly thinking the firetv had an onboard sd card or something so I'm going to try pushing things from a usb stick and doing it like that.

With my current version now un-rooted, where do I need to begin again? because I got it rooted last time using something called 'kingoroot' but it fails to root now.

Thanks in advance.
[Fire TV Android Development] wdcspurs:
You need to use the method listed for the latest version. Utilizing the USB A to A male cord. I believe that's the only way to do it on the 2 or 3 newest versions. And of course a micro SD card in the fire TV box. Works like a charm.
[Fire TV Android Development] paradoxiumwind:
Ok, so I've got a million SD cards/usb sticks, pick up a USB A to A male card on amazon for £2 and I'll be able to do it?

Actually I might have a converter / adapter, I just need the usb cable to have both standard male A ends right? and I assume one goes in the fire TV box and the other my PC? can you not do it over ADB then in the latest versions?

Thanks again

thanks
[Fire TV Android Development] wdcspurs:
Yes and Yes. Just follow the guide, but make sure yo u have the appropriate files downloaded and setup according tot he guide before starting.I want to say the step using the usb cord takes a little under 10 minutes or so. From there you boot into recovery using a wireless keyboard or mouse and then flash the rom and done. It is really that easy. PM me if you have any questions.
[Fire TV Android Development] bird333:
During a backup is it normal to see this message on the backup screen "Unable to locate '/boot' partition for backup calculations." ? Also the progress bar doesn't fill up as the backup is being made.
[Fire TV Android Development] shaDNfro:
quick question, as Netflix is scrambled, I guess the only solution is to upgrade from 5.0.5 to the newest version now.

If I root via KingRoot, then install the newest TWRP, then flashing this rom: Do I need to block updates afterwards? And will the OS search for updates in the initial set-up process (which can be avoided, but is difficult due to timing)?

I would personally stick with an official ota update, but I cannot blacklist specific https requests on my fritzbox (stupid avm...)
[Fire TV Android Development] paradoxiumwind:
I was unable to stop an auto-update of my box to Fire OS 5.2.1.1 (551203220), am I even more SOL with rooting this now or are there any options available?

Thanks.
[Fire TV Android Development] zeroepoch:
I don't think there is a root option yet that I know of. We're waiting on an exploit I guess and for it to be implemented in KingRoot or similar.
[Fire TV Android Development] paradoxiumwind:
Thanks for the update
[Fire TV Android Development] ¿GotJazz?:
ZIP Archive error with V6?

Hi, [MENTION=3991724]rbox[/MENTION] - FYI, I think that the posted v6 ZIP file is corrupt in some way. When I tried to unzip it using 7Zip, I always see the following error:

The posted v6 ZIP file did pass the MD5 check on my PC, so I don't think it is corrupted - It may have been an error in the ZIP file creation (maybe a file was still open when created?). There are 3 files that are extracted with 7Zip.

The files also do extract using the Windows 7 Explorer OK, but I wouldn't expect Win7 to be very expressive if there was a lower-level error during the extraction process.

Also, the 3 extracted files are binary identical between the 7Zip extraction and the Win7 extraction.

Just letting you know,

¿GJ?
[Fire TV Android Development] rbox:
Depending on the quality of the program you're using, and how it follows the zip standard, determines if it believes the zip is corrupt. I don't really know if according to the standard it is or not, but most programs will extract it. I do know some program on mac will refuse to unzip it. It actually consists of a shell script, followed by an unzip binary, followed by the actual zip file. And, looking at your screenshot, your program is just warning you that there is an offset. It's not an error per se, and having an offset is perfectly valid, because I'm using a standard method of "fixing" the zip to apply the offset.
[Fire TV Android Development] ¿GotJazz?:
FYI - I have a new FTV2. I never turned it on before going through the Custom Recovery / Rooted ROM installation. Not sure why, but I was having a problem getting past the forced Amazon update check on my "virgin" FTV2 when I was connecting via WiFi - it always failed and wouldn't let me do anything.

For whatever reason, once I connected to my wired LAN connection, I was able to get through the update check (it didn't update), and successfully registered my newly rooted FTV2.

Thanks for the awesome work, [MENTION=3991724]rbox[/MENTION]!
[Fire TV Android Development] ¿GotJazz?:
New question: How well does backup/resore work with AFTV2 TWRP Recovery v6?

Now that I have Root & Recovery things working OK, I'd like to backup before I start making new mods and feel comfortable that I can restore where I'm at right now.

Thanks,

¿GJ?
[Fire TV Android Development] otaner14:
Bricked Image After updating to 5.2.1.1.r1

hello

after trying to update rom to 5.2.1.1, my twrp said image failed and now i am stuck

to white amazon logo, and I don't know what to do.

Please if someone can help with any idea I will deeply grateful

AFTV 2 rooted and version 5.2.1.0

please help thanks
[Fire TV Android Development] fdigl:
I appear to not be able to use the keyboard to boot into the recovery. It just times out even with the keyboard plugged directly into the FireTV 2. I'm on 5.0.5.1 and have everything else done, it's just whenever I press the right arrow on the keyboard it doesn't do anything.
[Fire TV Android Development] andyman2000:
So I just received to amazonfiretv gen 2 from amazon.. Looks like version 5.0.3.1. I've kingo rooted them and I am attemping to install the twrp. It doesn't seem to work.

Here are my steps and whats shown on screen.

connected via adblink.

side loaded Kingo root and installed .. confirmed that it works because I have an adb shell and I am able to su -

I then pushed firetv2_recovery_v6.zip to /sdcard

su -

sh ./firetv2_recovery-v6.zip

it does something since nothing is responsive but I get nothing on std out. After 20 - 30 seconds it just reboots itself. I don't get the boot menu and thinks are back online.

I adb shelled back in. I do notice that /system/recovery doesn't exist.

Is this something new? Is there a diff procedure to getting twrp installed for 5.0.3.1 ?
[Fire TV Android Development] andyman2000:
just upgraded to 5.0.5.0 and still same issue. samething with 5.0.4
[Fire TV Android Development] D-an-W:
You pushed _v6.zip but ran -v6.zip was that just a typo when writing the post?
[Fire TV Android Development] andyman2000:
THe filenames were just a typo from the cut and paste for this post. I was using auto complete on the shell so its not a typo problem.

Anyway I think I figured out the problem. Maybe I missed it but the bootloader looks for a particular file ramdisk-recovery.cpio.lzma in afew locations. /system/recovery ; the root of the microSD OR the root of USB. If this file is not in any of these locations you will NOT be prompted with a menu and you won't see the splash screen on bootup.

Once I got that working I was able to load a rooted ROM. I noticed that the rooted ROM's had /system/recovery files in place so I didn't have to leave the USB / microSD in place to see the boot menu's.

The only way I was able to make progress on any of these is with the A-A usb cable method while loading the TWRP. So there still seems to a problem geting this installed without the USB cable method. I'm no longer in a place I can test this but in the ned I got this working. Thanks for the hardwork.
[Fire TV Android Development] jpage4500:
'wipe cache and dalvik' hangs after update

Not sure if this is the same thing as I just saw - but I just installed the latest (5.2.4.0_r1) and then hit the 'wipe cache and dalvik' option which seemed to hang. I took a picture - here: http://pasteboard.co/fl1tPvXFW.png

I'll try the advanced method to do this next but wanted to report this as well before I forget
[Fire TV Android Development] Fruchttiger00x0:
It's maybe the same issue but to be sure you have to wait up to 30 minutes. For some reason it takes so long sometimes. Don't know whats behind that procedure. (Maybe drive is busy and the mount script wait for process to die)
[Fire TV Android Development] jpage4500:
>> to be sure you have to wait up to 30 minutes

I should have waited a little longer.. I think after 10 minutes or so I gave up and unplugged the FireTV.. at which point got stuck in a recovery boot loop.

The good news is - I was able to fix the problem by running the command listed in the first post via 'adb shell'.. the one that mounts the cache folder I think.
[Fire TV Android Development] Fruchttiger00x0:
[MENTION=3991724]rbox[/MENTION]

(Not that urgent thing but it would be nice to know finally)

Could you maybe bring some light into that? What takes so long to mount and create a simple filesystem? Is there a part where data needs to be encrypted? The final error seems to be a filesystem corruption but we don't see any debug informations.
[Fire TV Android Development] rbox:
No clue. Don't recall anyone else saying that.
[Fire TV Android Development] Fruchttiger00x0:
Ok, maybe I did something wrong in before.

Anyway... Thx for reply
[Fire TV Android Development] bird333:
Is it normal to have a weird looking prompt when in adb shell in recovery? Like this

C:\Users\GM>adb shell
~ # [6n

There is a special character that is between the '#' and the '[' that is not showing up in this post. Also note that is the entire prompt ending with the letter 'n'.
[Fire TV Android Development] rbox:
That looks like an escape character, so possibly. Would look normal if you had a real OS :)
[Fire TV Android Development] ldeveraux:
You need to get over your insane aversion to Windows. Most people use it over Linux, and fairly successfully at that! [emoji334]
[Fire TV Android Development] bird333:
Ok so it is normal then.
[Fire TV Android Development] andyman2000:
A friend of mine was so impressed with my firetv 2 he bought one and asked me to do the same to his newly purchased firetv2. I was able to root the device but installing TWRP was another story. I pushed the zip file to /sdcard via adb then I opened a shell via adb.

su

sh /sdcard/firetv2_recovery_v6.zip

The device does something (nothing on std out) then it reboots. I don't see any difference, no boot menu, and it just boots up like normal. This AFTV2 was purchased within the last week and is running 5.2.1.1. What else can I do?

I tried the USB A -A method but thats not supported in this version.
[Fire TV Android Development] xboxexpert:
Worked perfectly on mine, same version 5.2.1.1 I also got TWRP and then installed the rooted newer rom. Great device I hope you get it working.
[Fire TV Android Development] andyman2000:
Yup got it working. Was using Kingoroot but shoulda used kingroot v 5.0.2. working fine now.
[Fire TV Android Development] pwntrik:
[MENTION=3991724]rbox[/MENTION] : Is there any way to backup the boot configurations? The reason I ask is because each time I restore a DATA and SYSTEM backup made from a sloane-5.2.1.1-rooted r1.zip installation, I have to first install sloane-5.2.1.1-rooted r1.zip so it updates the boot partition (at least that's my guess why this is happening.) Thanks!
[Fire TV Android Development] maleclub:
Awesome work.thank u sir
[Fire TV Android Development] enderffx:
I am in the same boat. Please help, root is fine but i'd like the safety of TWRP to "come back" if i must.

Greetings,

Ender

---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------

------------------EDIT--------

BS, although there was this error TWRP installed fine, next stop: prerooted 5.2.4.1 :)

Ender
[Fire TV Android Development] pwntrik:
Exactly - sometimes you get errors even though it was fine. Looks like it worked, but keep in mind that next time you can always reboot and run the recovery zip until it exits successfully.
[Fire TV Android Development] enderffx:
Yup, everything worked, 5.2.4.1 is running rooted fine, KODI is running in 4k and i am basically a happy puppy :)

Ender
[Fire TV Android Development] ldeveraux:
I'm sure this has been asked, but I couldn't find it in the thread. Was this updated to the same 3.0.0-7 that we have for the FireTV 1, or is it an insignificant change?
[Fire TV Android Development] rbox:
The changes from 5 to 7 don't matter for sloane. In theory I should rebuild all 3 devices with the same version, but I haven't really had a need.
[Fire TV Android Development] andreizet96:
If I find a way to connect all the peripherals to a fireTVstick 2nd gen, would this work on such a device? Im desperately trying to root this stick and it is driving me nuts! Sorry if this has been already asked, I looked over the thread but couldn't find it.
[Fire TV Android Development] dave157:
[MENTION=3991724]rbox[/MENTION], I read somewhere that you were working on a small flashable file to be able to restore the stock recovery. I'm trying to return to full stock on my FTV 2 Sloane 5.2.6.9 prerooted.
[Fire TV Android Development] rbox:
If you follow the instructions in the post about my ROM that explains how to use manage_recovery, and use that to enable recovery. Then doing adb reboot recovery should take you to stock recovery. You might need to reboot normally once after using manage_recovery before trying to reboot into recovery. Then remove anything you have implemented to block updates. Then since you are on 5.2.6.9, doing a normal update at that point should cause it to download 5.2.7.0 and boot in to stock recovery. It'll probably fail once. But if you boot back and try it again, it should work.
[Fire TV Android Development] dave157:
[MENTION=3991724]rbox[/MENTION], Yeah, I did find the instructions to use manage_recovery and was able to enable the stock recovery and return to full stock. I forgot to update my post, lol. Thanks!
[Fire TV Android Development] mrchrister:
[MENTION=3991724]rbox[/MENTION] does manage_recovery work for Bueller as well?

I'd love to keep root but my Crave TV app (HBO in Canada) detects root and Hidemyroot isn't working anymore...
[Fire TV Android Development] _u2pop_:
Hi [MENTION=3991724]rbox[/MENTION] long time no see, we talked alot before in IRC bro im trying to unroot the firetv 2 so the first i did is factory setting method like enabling back the update ota using adb after i go to TWRP and wipe the art/cache/data/internal storage and rebooting for see if they will bootup to amazon OS didnt worked something is breaked still showing me recovery twrp and im trying to flash again the cureent prerooted.zip the latest version the problem is the damn recovery is not reading my MICROSD still 0MB and after i did a format data for see if they allow to read the external but not worked and i dont know what to do now please help me :(
[Fire TV Android Development] ForForkSake:
Try a different micro sd or plug ethernet in and adb sideoad it as per rbox first post
[Fire TV Android Development] _u2pop_:
Thx for the reply the stupid check mark in mount SYSTEM didnt was enabled so i already fixed it.
[Fire TV Android Development] Rortiz2:
Hi [MENTION=3991724]rbox[/MENTION],

I looked at 2ndinit at github and I have a question.

You are using some code from phh's SuperUser to disable SELinux of init, ueventd, recovery and the shell from recovery. My question is, can this code be applied to get a full SELinux Permissive at boot? Just wondering cause we are trying to boot custom ROM on it and well, locked bootloader has his limitations...

I was about to pick up a commit from ggow (netd binary that loads at boot from init.rc) that injects some code to netd to disable SELinux at boot but the commit is gone. Will your 2ndinit help to get a full permissive SELinux at boot? It can be a good option since it runs directly after mount the system (ext4_resize).

Cheers and sorry for the OT.
[Fire TV Android Development] rbox:
Possibly. You can try calling setenforce after you've disabled it for init.
[Fire TV Android Development] Rortiz2:
Yep, I tought that. I will give it a try. Another question (sorry xD). I replaced lineages ext4_resize by yours one and same for pppd. There's no more files to replace? I mounted your unbrick img and I can see a few libs in lib64 and linker64. They need to be replaced too?

Cheers!
[Fire TV Android Development] rbox:
Those should just be standard android stuff. The only things you should need are 2ndinitstub and 2ndinit.
[Fire TV Android Development] Rortiz2:
Yupp, thanks you :)

Finally got to work boot menu in Lineage. My issue was that I was using system/etc/recovery instead of system/recovery :p

Now going to play with the 2ndinit to try what you said before about setenforce:good:

Cheers!
[Fire TV Android Development] Rortiz2:
[MENTION=3991724]rbox[/MENTION]

Got working SELinux at boot ;)

Thanks you very much. We have bootanimation now!

This is what I added:

(2ndinit.c)

set_permissive("shell", &policydb);

(2ndinitstub.c)

execl("system/bin/setenforce/", "permissive", NULL);

Cheers.
[Fire TV Android Development] smumar143:
Any one Pls help me rooting my fire TV 2, Ios 5.2.7.2
[Fire TV Android Development] Rortiz2:
https://xdaforums.com/fire-tv/devel...i-rollback-t3986303/post80588511#post80588511

Regards.
[Fire TV Android Development] Rortiz2:
Hey all,

I'm facing a problem while wiping any partition in TWRP.

When I need to wipe data or cache I go (as usual) to the wipe option, I select them and I swipe to wipe.

The problem is, when I swipe, it stucks there with "Formatting cache/data using make_ext4fs..." (10 mins and more..)

Since it gets stuck on there, I tried running

killall recovery

(to "restart" TWRP as OP says) but that makes things worse as ADB stops working and the GUI freezes at the splash screen and I'm basically forced to unplug the power supply causing "damage" to the partitions I was wiping leaving them corrupted and in next boot seeing errors like "cannot mount /data" and so on...

As a "note", I'm able to wipe the partitions "manually" with adb shell using

make_ext4fs /dev/block/platform/mtk-msdc.0/by-name/partition_name

and that works just fine.

There's something I can do..? Or I just keep wiping the partitions manually with adb?

EDIT: Ignore all, fixed it.

Regards.
[Fire TV Android Development] wdcspurs:
Im searching for a way to remove twrp and go back fully stock. Im able to successfully download the latest OS OTA, but when it reboots to install it hits TWRP and then boots up into the launcher without installing. Ive tried the factory reset option. Still have TWRP. Any help appreciated.
[Fire TV Android Development] Bertonumber1:
Anyone know a way to get into twrp without using boot menu on 3.0.05 , I haven't got a keyboard that works and my mouse doesn't work on the usb port either so I always get kicked into system instead of recovery.
[Fire TV Android Development] Sus_i:
Yes, you're able to switch the bootmenu without a keyboard but with adb.

Easiest way, extract the force_recovery.img file out of the sloane amonet/bin zip folder, push it to your sd and then dd it to cache, then reboot...

If you're done playing with TWRP, wipe cache, in order to switch the boot menu back to system.
[Fire TV Android Development] Bertonumber1:
Hi [MENTION=5213625]Sus_i[/MENTION] thanks again for replying,

So in theory could I be able to put the spare force_recovery.img I have on my pc to /sdcard and dd it to cache mate or does it have to come from flashed bin folder?

chmod 777 /cache/force_recovery.img

I think I know that not sure if it's correct