yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Ludacrisvp:
The service mentioned is a Linux OS thing, not a Mac OS X service.
[Fire TV Original Android Development] aboshi:
Nope, just use a windows VM or install bootcamp/windows.

Or just boot up a live linux usb and make your life easy ;)
[Fire TV Original Android Development] roligov:
In 5.0.5.1 there is good news and bad news.

Good news is the handshake still works in 5.0.5.1, so does writing to the nand.

Bad news is the existing firetv2_recovery_v5 and install_firetv2_recovery_v3 don't work. I took a chance and ran it, twice. It completes successfully, but upon booting with the USB drive plugged in, the FireTV boots normally with no sign of recovery menu.
[Fire TV Original Android Development] rbox:
I was afraid of that. They probably fixed the idiocy that I took advantage of in the kernel. How do you have a system with 5.0.5.1 and root?
[Fire TV Original Android Development] roligov:
This was a stock 5.0.5.1 rbox. Willing to sacrifice it since I have 3 others.
[Fire TV Original Android Development] rbox:
firetv2_recovery_v5 should have failed... Either way, good to know they still haven't patched the preloader. Once I finish firetv1 stuff, and I get the update package for 5.0.5.1 for firetv2, I'll take a look at how to attack the new kernel.
[Fire TV Original Android Development] roligov:
Sorry to be more precise, I extracted the files from firetv2_recovery_v5.zip into the same folder as install_firetv2_recovery_v3.zip. Then I ran install_firetv2_recovery.bat.

But I take that back, there was something dodge with my USB stick. Put the file on an SDCARD after flashing with the above and get taken to the stock "Amazon system recovery <3e>".

Same as this: http://imgur.com/xsPvta0
[Fire TV Original Android Development] rbox:
Well that's good. It means 2nd init is working, but the ramdisk didn't extract. Are you sure it's not corrupt?
[Fire TV Original Android Development] roligov:
I'm pretty sure but will test again tonight, anything is possible. It's 6am now and I'm off to work so can only test in about 12 hours time. For some reason I woke up at 3am this morning so I decided to tinker.
[Fire TV Original Android Development] roligov:
Yeah you called it. It was corrupt as well [MENTION=3991724]rbox[/MENTION]. Now managed to get into the recovery menu. Going to attempt a downgrade to sloane-5.0.5-rooted_r4.zip. If it bricks well then at least you don't need to risk your unit.

EDIT:

Rooting is still possible: [MENTION=5957312]AFTVnews.com[/MENTION]

- Download install_firetv2_recovery_v3.zip

- Download firetv2_recovery_v5.zip

- Extract both to same folder

- Run install_firetv2_recovery.bat

- Plug in power to AFTV2 and let it flash the recovery.

- When it's done copy ramdisk-recovery.cpio.lzma and sloane-5.0.5-rooted_r4.zip firmware to a NON corrupt usb or sdcard :D

- Reboot, choose recovery with a keyboard

- Install the 5.0.5.0 firmware

- Boot and bingo :good:

Great work again rbox!
[Fire TV Original Android Development] AFTVnews.com:
Awesome news! I'm updating a box to 5.0.5.1 right now to verify it myself.

UPDATE: Yup, I tried it myself on a 5.0.5.1 box and rooting with [MENTION=3991724]rbox[/MENTION]'s script via the A-to-A USB cable went smoothly. TWRP and the 5.0.5 pre-rooted ROM installed just fine. The only difference was a prompt within TWRP to "allow modifications" that appear when it booted for the first time, prior to going to the main menu. Not sure if that's something new in TWRP or a result of going from 5.0.5.1 to pre-rooted 5.0.5. It was asking for permission to switch to a read/write mount or stay read only. I allowed read/write and flashed the ROM just fine.
[Fire TV Original Android Development] roligov:
Yeah I got that screen aswell. Thought it was normal.
[Fire TV Original Android Development] thehackerwhohacksandroid:
Hey are u still working on some rom for fire tv stick and a custom recovery for fire tv stick. Love ur work by the way
[Fire TV Original Android Development] ldeveraux:
read the rules, dude...
[Fire TV Original Android Development] zroice:
Not sure if that happened to anyone else before - on a quick search it didnt come up:

I have four FireTV 4k, all with 5.0.3 and tried to install the recovery on them.

On all of them the injection process did not complete several times so I had to do it over and over again until it finally stuck. (also had to edit the script to inject files seperately so it wouldnt mess up if the 2ndinit went through but the second file did not.)

During the injection it would just stop randomly and hang at a certain %.

Eventually after up to 20 tries it went through, but it was pretty annoying to have to ctrl+c, restart the script and replug the firetvs that often.. =)

Anyone else had that problem?

Could be that it is computer related though - my flashing pc is an old pentium 4 single core.. but the mediatek_inject.exe did not take much cpu % though.
[Fire TV Original Android Development] Han-Droid:
Is it possible to install this custom recovery AND keep the existing ROM?

I am asking because my FireTV2 is preconfigured and I want to be on the safe side if anything fails. So I'd like to make a nandroid backup right after flashing TWRP.

or

does flashing this recovery kill the rom and I NEED TO install the pre-rooted ROM right after flashing the TWRP ?

TIA !
[Fire TV Original Android Development] Mat_london:
Absolutely can't get this or Roligovs combination to work

Hi All,

Really struggling here so may have missed something obvious. It's probably not helped by the fact that I don't really understand what the process is doing.

I've tried about 20+ combinations of install_firetv2_recoveryXXX & firetv2_recovery_YYY to no avail.

I've got Ubuntu and Windows 7 and have tried on both machines.

I'm getting the same symptoms as Romolac i.e "the error: source file is larger than target file!" message and overly short time to complete the process.

This happens with all the combinations of install_firetv2_recoveryXXX & firetv2_recovery_YYY that I've tried (including Roligov's suggested combo) except that is for Romolac's suggested combination firetv2_recovery_v3 & install_firetv2_recovery_v3.

Firetv2_recovery_v3 & install_firetv2_recovery_v3 appears to do everything it should no "the error: source file is larger than target file!" error and lots of writing going on over the course of several minutes.

I put the correct ramdisk-recovery.cpio from V3 on the SD (not another ramdisk-recovery.cpio.lzma ) and it still just boots straight through to FIreTV without recovery appearing.

Could someone let me know if I've got the post install procedure right?

Wait for install_firetv2_recovery.sh/bat to finish

Copy correct ramdisk-recovery.cpio or ramdisk-recovery.cpio.lzma to root directory of FAT 32 formatted micro SD

Unplug power from FireTV

Unplug AtoA USB from Fire TV

Give it 5 seconds

Insert SD Card and Hook up HDMI lead

Insert USB Keyboard

Insert FireTV Power and wait for Recovery to appear then take it from there

Could I also ask if anyone has got Recovery reinstalled even though they are getting the "the error: source file is larger than target file!" message.

I assume not

Many thanks

Mat
[Fire TV Original Android Development] rbox:
If you are getting source file is larger than target, that means your /system partition is corrupt and you'll need to use the unbrick image. I belive [MENTION=5957312]AFTVnews.com[/MENTION] has a guide for doing it as well.
[Fire TV Original Android Development] roligov:
Yip he does: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv
[Fire TV Original Android Development] Mat_london:
Excellent, that did the trick, although I had to use Ubuntu as Windows 7 was doing the same freezing while writing thing that it does with the recovery install
[Fire TV Original Android Development] Sylntnyt:
I've been trying to run this for the past two days on my Raspberry Pi and haven't had much luck. I'm not sure if it's because I'm using a Pi or if I'm just not executing it right or missing something. I've tried clicking the file and the terminal never shows up, so I just run the "sh" command and what I get is what's seen in the attachment below. Any help in getting this running would be greatly appreciated as I don't have a computer nor a laptop at the moment.
[Fire TV Original Android Development] zeroepoch:
It won't run on a raspberry pi because the binary is compiled for x86. Unfortunately there is no python version of the injector just the whole partition writer.
[Fire TV Original Android Development] jasonwhelan:
Please help

I have tried for the last 5 days to root my FireTV 2 using this method and I can't get it to work. Ive tried 2 windows 7 x64 PCs and Linux and the 2 windows PCs do the exact same thing (just sit there waiting for the preloader.)

I have definitely installed the drivers as needed in Windows on both machines and they show up in device manager but say they cannot start (which is supposed to be normal.)

In Linux the handshake script wont start because it cannot find the right device.

Any ideas???

I want to be able to set up samba shares so I can use Kodi with the files on my network, but I am beginning to think that I have an updated version of 5.0.5.1 that's blocking the rooting attempts.

Thanks!

Jason
[Fire TV Original Android Development] PhoenixMark:
I got a Mac guide and I've rooted this way several times. This is easy to do. Check it out if you got a Mac.

It just blows me away all the hoops windows people have to go through with drivers and what not, jeeze.
[Fire TV Original Android Development] jasonwhelan:
Mac

I tried on my Mac as well, same thing.

I finally decided to build my own cable and it still didn't work in OSX, but worked first try in Windows.

So I FINALLY got it rooted.

Thanks everyone!

Jason
[Fire TV Original Android Development] J2048b:
is there a mac guide for this? i sent u a pm as well if u don't mind? i just had my newish fire tv 2 take a turn for the worst out of now where and haven't the slightest clue about all this... didn't even see any zips to dn from the op's post....i guess u also have to be rooted in order to push any of this thru adbfire on a mac correct? so if i root it first will i be and to just use add fire and push the recovery thru?
[Fire TV Original Android Development] PhoenixMark:
It's here http://marksmods.com/Hack-the-Fire-...-and-Install-a-Pre-Rooted-ROM-with-a-Mac.html
[Fire TV Original Android Development] sharont1970:
pre loader /bat rec

Hi I was wondering if you have resolved pre loader issue which is not catching firetv into recovery. I'm having the same problem. bought usb hub and a-to-a usb. havent been able to get past pre loader stage and ideas would be great thx from james /;)uk.
[Fire TV Original Android Development] gazdaman.:
I followed this guide and got it to work:

http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
[Fire TV Original Android Development] flyerflar:
I have tried for days , to root my FireTv2 . Step 3 always remains standing . If it works , is not a boot menu from the USB stick . I have to stick reformatted or replaced. If the ram defect ? Have version 5.0.5.1 . and not root
[Fire TV Original Android Development] zeroepoch:
[MENTION=3991724]rbox[/MENTION], It might be a good idea to add a comment near the top that this installer only works for 5.0.x.y and NOT 5.2.1.0+.
[Fire TV Original Android Development] mrjoeyloke:
Is there a root process after 5.2.1.0? If so where does one find it?
[Fire TV Original Android Development] Stylz68:
Unfortunately I'm having an issue trying to install firetv2_recovery_v3.

I'm running windows 10 and have all the drivers installed. Also installed the drivers for the firetv from amazon as well.

It hangs at the following area once I plug the firetv back in.

Waiting for preloader…

Found port = COM7

Handshake complete!

Injecting 2ndinit…

Mediatek Inject, git version fa8d8f

Locating the partition…

Reading 000000200: 0%

Do you guys have any advice at all to get this to work? It's on 5.0.5.1.

Thanks!
[Fire TV Original Android Development] zeroepoch:
Sounds like it's hanging during the serial communication. It happens sometimes. If it doesn't work are a few reboots you might need another computer to try.
[Fire TV Original Android Development] Menchelke:
https://youtu.be/XYyR-kCW4aA?t=4m52s

At this point in the video, where you launch the bat file, and preload nothing ever shows up. And my fire TV light blinks orange constantly. I have restarted the script a dozen times, and replugged in the fire TV but I never see it working.﻿ Do I need to hunt down a Windows 7 or earlier machine?

I am running Windows 10. I believe everything is fine. I checked md5s, and all that. Thanks.
[Fire TV Original Android Development] Menchelke:
So, my Fire TV booted up fine, but kept flashing constantly, and it was making a popping noise out of the back of my monitor. I swapped out hdmi cables, and rebooted it, and now it's stuck on the "Amazon" logo, and it won't fully boot. I never did get the ROOT to go through.

Anyone that has had success willing to try and fix mine for me if I ship it to you, and how much? Thanks.
[Fire TV Original Android Development] playingbball20:
I'm on Win 10 x64 and getting that too!?! Any suggestions?
[Fire TV Original Android Development] zeroepoch:
Linux seems to work more reliably if you have that installed or try an Ubuntu live CD.
[Fire TV Original 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 Original Android Development] fdigl:
EDIT: resolved, forgot that my flash drive was partitioned in NTFS.
[Fire TV Original Android Development] Han-Droid:
general question:

I'd like to root and install this recovery. While doing so...is it possible to nandroid-backup my existing system? I'm asking because I bought a preconfigured FTV2 and...just in case ....and to be on the safe side, I'd like to "go back" if I want to. So...will rooting AND installing the recovery kill my existing system OR can I nandroid-backup the old system just after rooting/recovery installation?

TIA!
[Fire TV Original Android Development] xdanewbiedude:
When will there be a 64 bit version for the Fire TV?
[Fire TV Original Android Development] fregatte77:
Injecting stuck at 0%

I'm in the same boat.

Tried with different Computers and OS (Windows 7 / 10 / Mac OSX Captain).

My Fire TV was on 5.2.2.1 while testing and is now on 5.2.4.0.

Might it be that the rooting via USB does not work in general with this new firmware rel. ?
[Fire TV Original Android Development] rbox:
From the very first line in the OP...
[Fire TV Original Android Development] fregatte77:
Many thanks for clarification!!!!

So I need to wait and hope.
[Fire TV Original Android Development] Ludacrisvp:
I'm not sure if anyone is looking for another method.
[Fire TV Original Android Development] whodisname:
Anybody tried that factory cable on this?
[Fire TV Original Android Development] adam_ky:
bricked.. and did this..

went threw the first time no errors. i used an sdcard for the ramdisk.

but nothing happened.. it said finished press any key or such.. so i did.. sd card was in box.. and power cycled... went to amazon white logo and nothing.. wouldnt boot to recovery.

so i tried to install this again.... now i get an error

"source file is larger than target"

Waiting for preloader...
Found port = COM10
Handshake complete!
Injecting 2ndinit...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 100%
Reading 000000400: 100%
Opening the filesystem...
Reading 0058E0400: 100%
Reading 0058E0800: 100%
Locating the target file...
Reading 0058E8C00: 100%
Reading 0058E1000: 100%
Reading 0058E9000: 100%
Reading 0058E5000: 100%
Opening the target file...
error: source file is larger than target file!
Injecting 2ndinitstub...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 100%
Reading 000000400: 100%
Opening the filesystem...
Reading 0058E0400: 100%
Reading 0058E0800: 100%
Locating the target file...
Reading 0058E8C00: 100%
Reading 0058E1000: 100%
Reading 0058E9000: 100%
Reading 0058E5000: 100%
Opening the target file...
error: source file is larger than target file!
Press any key to continue . . .

any ideas?
[Fire TV Original Android Development] rbox:
Use the Unbrick Image
[Fire TV Original Android Development] zeroepoch:
It's saying the file the installer is trying to install is too large. You could try using the unbrick image method.
[Fire TV Original Android Development] adam_ky:
I tried both ramdisk and unbrick.img

I get the same thing.

The first time I did this (when it completed), I was using the unbrick.img option with the ramdisk on the micro SD card. It just never went to recovery after power cycle.

So I figured something didn't go right and tried it again. That's when I get the Target size error trying either method.
[Fire TV Original Android Development] jequetepeque:
Aramburu
[Fire TV Original Android Development] Servet83:
Could you solve this problem?
[Fire TV Original Android Development] adam_ky:
I unzipped the files into a fresh folder

Then I selected them all in Windows 10 and "take ownership"

Probably had no different effect..

I ended up using the method without the SD card and it worked.

So yes I did get it working just try it again.
[Fire TV Original Android Development] amtyazali88@gmail.com:
Firmware
[Fire TV Original Android Development] Bertonumber1:
Hello again people, how are you all? Great I hope, plodding along here. I managed to root, install twrp and Roms on firetv stick 1, tank, mantis and am about to buy a firetv 2nd gen if it's modifiable, im needing to obviously know if the latest software versions up to this day can still be worked around for root and installing twrp magisk/supersu etc. Any help or pointers greatly appreciated as always guys. Thank you

❤️❤️❤️?
[Fire TV Original Android Development] Sus_i:
Further bricks? ;)

If you mean the second gen fireTV with the sdcard slot, then yes, it's rootable with the shorting method here:

root thread

Works like the first gen stick with the prerooted roms / supersu (no magisk jet).
[Fire TV Original Android Development] speck1234:
Any luck with the rooting and custom rom stuff for people like me who are stuck on the Fire OS 5.2.9.4 in 2023 and cannot downgrade?
[Fire TV Original Android Development] Finnzz:
Do you have a FireTV2 box (Sloane)?

If so you probably want this thread
[Fire TV Original Android Development] Bertonumber1:
Once you unlock the sloane ( if you have one) there is no reason why you can't use any other firmware. Just don't jump to high or too low.

Eg flash 5.2.7.1 before you flash 5.2.7. 9 etc

Read the Op in unlock thread for more info.

I have two sloane both work perfect. One was on latest I unlocked and went back to 5.2. 7.4 and just updated webview and store apks.

All good

Regards a
[Fire TV Original Android Development] speck1234:
I do have the sloane I'm just stuck on 5.2.9.4 the latest. What is this "unlock" you speak of?
[Fire TV Original Android Development] Finnzz:
Unlocking the bootloader, meaning disabling signature verification so that you can flash TWRP & custom ROMs.

Read this guide, and direct your questions there. This method likely still works on 5.2.9.4
[Fire TV Original Android Development] speck1234:
That method requires Linux and I would like to do it using Windows
[Fire TV Original Android Development] Finnzz:
The only option is Linux.

You can make an Ubuntu bootable USB drive.
[G 2014 Android Development] MotoGUser69:
DELETED
[G 2014 Android Development] DepressedDead:
What's new in this release? 2.8.7.0 was released almost a week ago and both them look like they have the same features. Are in this version all twrp's 3.0 features, like MM decrypting and so on?
[G 2014 Android Development] CreasingMass Dev:
Twrp 2.8.7.0 was released almost 8 months ago lol

Look here: https://twrp.me/
[G 2014 Android Development] MotoGUser69:
2.8.7.0 wasn't released a week ago... And look at the changelog to see what changed...

Sent From My XT068 Powered By MinimalOS 5.1.1
[G 2014 Android Development] DepressedDead:
Luca uploaded a week ago an updated version (2.8.7.0, see screenshot below), feauturing MD, terminal features, etc... so I wonder if this and Luca's twrp aren't the same.
[G 2014 Android Development] Carlos Arriaga:
Delete

Enviado desde mi Moto G
[G 2014 Android Development] luca020400:
It's the same
[G 2014 Android Development] MotoGUser69:
No...

Sent From My XT068 Powered By MinimalOS 5.1.1
[G 2014 Android Development] MotoGUser69:
Il give ya credits

Sent From My XT068 Powered By MinimalOS 5.1.1
[G 2014 Android Development] luca020400:
My twrp is 3.0 without 3.0 label ...
[G 2014 Android Development] LuK1337:
Can you please take it down? This is TWRP for thea which is 2014 LTE model, it won't allow you to flash titan roms.
[G 2014 Android Development] luca020400:
"your" work

You just renamed official thea twrp to titan ....
[G 2014 Android Development] MotoGUser69:
Ok, didn't see it sorry

Sent From My XT068 Powered By MinimalOS 5.1.1
[G2 Q&A, Help & Troubleshooting] Jan Philipp:
Hello Forum!

I tested some Roms today and now after restoring my old System I encountered an italian App called mywind (its on Google Play). I didn't installed it and I can't uninstall it from within the drawer.

So I googled it and it seems to be part of any north american Provider Service or something.

Does anybody know where it comes from or how to get rid of it?

Greetings, Jan

PS: I'm on a debloated and modded G2 D802 with 5.0.2 Stock LL Dorimanx and I was testing the Google Edition 1.3 Rom.
[G2 Q&A, Help & Troubleshooting] Felipe_PS:
Use Root Uninstaller to get rid of it, you can find it on Play Store.
[G2 Q&A, Help & Troubleshooting] Jan Philipp:
Thanx for that, Felipe. It wasn't easy to remove. Had to erase single files via root explorer because the uninstaller only deleted the .apk.

Now its gone but theres still the Question: What exactly is it and where did it come from?
[G2 Q&A, Help & Troubleshooting] giannis_25:
i have the same problem.... witch other files did you delete? (i use root uninstaller to remove the app too). Thanks
[G2 Q&A, Help & Troubleshooting] ShadowEO:
I saw there was an unofficial application called myWind with the package ID it.wind.myWind and an official myWind application, do you know which one was installed? If it was the official myWind application (also available on the play store), it's possible that your carrier could have a thing similar to Sprint Zone/Boost Zone which downloads and installs carrier applications.
[G2 Q&A, Help & Troubleshooting] iubjaved:
It says in the app " MyWind is the app that lets you keep track of your Wind and Infostrada lines. "

It seems like a carrier app . Could be included in the rom you installed.
[Samsung Gear S2] Ysas:
When I receive a WhatsApp message, I can see the message and read it,

but I cant reply to it vwith the Gear S2, it only shows me the option "open on phone"

Does any one know if this is a bug or is it because I dont have a Samsung phone?
[Samsung Gear S2] OnnoJ:
It is not a bug. Even witch Samsung phone it is not straightforward.

Look at the app Chat Hub, it does allow you to answer WhatsApp and other social services. It is not free though...
[Samsung Gear S2] Ysas:
So the only way to get it work without a Samsung Smartphone is to download that App?
[Samsung Gear S2] bendez1985:
The most recent Whatsapp update did something to gear s2. Now I don't see the "read more" icon. Sigh..
[Samsung Gear S2] AlienBeans:
That's more than Handcent will do. If I get a message in handcent, the watch just displays a message to check phone. Doesn't show the message, or who its from or give us a way to reply to it. I've written to handcent and they have completely ignored me. I have since quit using handcent and went back to the stock messaging app.
[Samsung Gear S2] FGiuseppe:
I have the same problem, help please.