• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

FireTV 2 (sloane) Recovery [v6] - 3.0.0-5

Search This thread

aboshi

Senior Member
Apr 20, 2010
64
20
NY
Here is a script I whipped up and tested a few times.
I have made 2 scripts.
One for first time install of recovery.
The other for updating recovery when @rbox release's future updates.

To use the script(s) just upload the script to /sdcard/ along with all of the other files
When in adb shell:
Code:
su
cd /sdcard/
sh aftv2-recovery.sh

If updating:
Code:
su
cd /sdcard/
sh aftv2-recovery-update.sh

It doesn't get any easier :p
Again thanx to @rbox for another fine piece of work.
 

Attachments

  • recovery-scripts.zip
    2.1 KB · Views: 63
Last edited:
  • Like
Reactions: santamanga

BagiMT

Senior Member
Nov 30, 2015
71
21
The instructions in the OP work great. Took literally 1 minute on a rooted FTV with adb over WiFi. Thanks for the great work rbox!
 

zeroepoch

Senior Member
Dec 30, 2010
313
214
San Jose, CA
www.zeroepoch.com
Here is a script I whipped up and tested a few times.
I have made 2 scripts.
One for first time install of recovery.
The other for updating recovery when @rbox release's future updates.

To use the script(s) just upload the script to /sdcard/ along with all of the other files
When in adb shell:
Code:
su
cd /sdcard/
sh aftv2-recovery.sh

If updating:
Code:
su
cd /sdcard/
sh aftv2-recovery-update.sh

It doesn't get any easier :p
Again thanx to @rbox for another fine piece of work.

Not sure but you might need the chmod after copying from /sdcard to /system/recovery. I know on some devices you can't really change permissions on /sdcard. Maybe you already tested that, so again not sure if needed or not. Also for upgrades you would just boot into TWRP and sideload or otherwise apply the pre-rooted image and it would update for you. I guess your update script would be for new recovery releases on the same version.
 

aboshi

Senior Member
Apr 20, 2010
64
20
NY
Not sure but you might need the chmod after copying from /sdcard to /system/recovery. I know on some devices you can't really change permissions on /sdcard. Maybe you already tested that, so again not sure if needed or not. Also for upgrades you would just boot into TWRP and sideload or otherwise apply the pre-rooted image and it would update for you. I guess your update script would be for new recovery releases on the same version.

No chmod needed. I tested it and I am on a mac so I already changed the perms, they looked like they carried over after pushing it to the aftv as I had no issues running the script. I also forgot that its just as easy to go into recovery and update from there in the future ;)
I guess it will be for lazy people who don't feel like hooking up a keyboard.
Or for testing purposes.
 

deanr1977

Senior Member
Apr 17, 2011
1,000
316
lost somewhere.... Help
How do I get adb to find the directory? It says I have two devices connected? My ip & one starting with G070GV? Also when I press su it says not recognised as an internal or external command? I think I'm doing something wrong?

Sent from my SM-G900F using Tapatalk
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,603
How do I get adb to find the directory? It says I have two devices connected? My ip & one starting with G070GV? Also when I press su it says not recognised as an internal or external command? I think I'm doing something wrong?

Sent from my SM-G900F using Tapatalk

Are you connected with USB to the firetv and have usb debugging enabled and/or are you connected to another android device over USB? Disconnect it. If 'su' doesn't work... are you sure you are rooted?
 

deanr1977

Senior Member
Apr 17, 2011
1,000
316
lost somewhere.... Help
Are you connected with USB to the firetv and have usb debugging enabled and/or are you connected to another android device over USB? Disconnect it. If 'su' doesn't work... are you sure you are rooted?
Definitely rooted & running OS 5.0.3.1 i don't understand it? But I'm sure the command shouldn't say-

c:\Programe Files (x86)\Minimal ADB and Fastboot>

Shouldn't this be different?

Sent from my SM-G900F using Tapatalk
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,603
Thought I had android sdk tools on this laptop already? Must of done them on my compter before? I'm downloading that now, then will try again. Sorry rbox

Sent from my SM-G900F using Tapatalk

I'm working on a much easier method, if you can wait a little more. Still needs adb though.
 

dk1keith

Senior Member
Jul 26, 2012
476
49
ROM takes a few minutes.

Not real sure what I may have done. But SuperSu must not be working. When I tried to restore my backup from TWRP it said can't mount system. Also in adb shell when I type su it doesn't take me to root. I'm on pre-rooted 5.0.4. I did do a Factory Reset and installed rbox pre-rooted 5.0.3.1. that didn't fix my video playback issue so I decided to go back to pre-rooted 5.0.4. Is it possible I lost root?
 
Last edited:

rbox

Recognized Developer
Apr 22, 2011
1,776
2,603
Not real sure what I may have done. But SuperSu must not be working. When I tried to restore my backup from TWRP it said can't mount system. Also in adb shell when I type su it doesn't take me to root. I'm on pre-rooted 5.0.4.

I may not have tested backup/restore... oops. What happens with su? Did you maybe not accept the prompt on the screen?
 

dk1keith

Senior Member
Jul 26, 2012
476
49
I may not have tested backup/restore... oops. What happens with su? Did you maybe not accept the prompt on the screen?
didn't see a su prompt? when would that have come up? also, the fact that I can't get to root from adb shell by typing su gave me the impression that SuperSu wasn't working. Supersu is installed but there is no Launch tab to open it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 46
    It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.

    attachment.php

    As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.

    Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.

    Installation
    1. You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
    2. Copy the zip file to your destination.
    3. Connect adb
      Code:
      adb connect IPADDRESS
    4. Open an adb shell
      Code:
      adb shell
    5. Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
      Code:
      sh /sdcard/firetv2_recovery_vX.zip
    6. Reboot

    Upgrade
    You may repeat this to upgrade to a newer version, or you can install an updated pre-rooted rom, as I will be uploading new versions of those with every version of recovery.

    Notes
    This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. 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.

    DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.

    USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.

    You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.

    ROMs
    Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.

    Kernels
    The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.

    Installing zips
    You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.


    Stuck in a loop?
    If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
    If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
    Code:
    mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache


    Source Code
    You can find the source code here:
    https://github.com/androidrbox/sloane-2ndinit
    https://github.com/androidrbox/android_bootable_recovery

    WARNINGS

    • It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
      Code:
      killall recovery
      to restart it
    • It is also extremely important to never reboot after wiping /system.
    • If you wind up bricking, you must use the Unbrick Image to unbrick.


    Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.

    Changelog and Downloads:
    • April 8, 2016 - v6 (md5sum: 79c1a3efbac86618fa2cdbb4901fbd77)
      • This should prevent auto flashing amazon updates.
      • This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
    • February 14, 2016 - v5 (md5sum: 16c957c86f1f61160e14a55819610707)
      • This should fix the problems certain keyboard were having in recovery.
      • This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
    • February 12, 2016 - v4 (md5sum: 15c6d375607839cac4b186a2b68b8b0d)
      • This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
        • These are just changes related to the unbricking image. No other functional changes.
    • February 8, 2016 - v3 (md5sum: b39a4dbe0c19080a97f602f37fda63ec)
      • This includes an updated script. You can now just run the zip instead of needing the zip and the script.
      • This includes TWRP 3.0.0-2.
        • Added a reboot recovery option in addition to reboot system. Now reboot system will reboot straight in to Android. Reboot recovery will reboot to the bootmenu.
        • Fixed restoring backups.
      • This includes the same version of 2ndinit.
    • February 7, 2016 - v2 (md5sum: 762621104d158d7ce4010bea725f7181)
      • This includes an automated script.
      • This has the same versions of 2ndinit and recovery as v1.
    • February 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
      • This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
    6
    I just updated the OP with v6/3.0.0-5. This blocks TWRP from auto installing Amazon updates.
    3
    I added v3 to the OP. Now you only need to copy the zip file whole and just run it. Additionally, I updated TWRP to 3.0.0-2. The changes are listed in the OP.
    3
    Hi, @rbox - 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?

    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.
    3
    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?

    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.