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

Search This thread

andyman2000

Member
Dec 28, 2016
5
0
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.
 

xboxexpert

Senior Member
Aug 1, 2007
1,008
1,185
41
www.thexboxexpert.com
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.

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.
 

pwntrik

Member
Apr 29, 2016
35
7
@rbox : 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!
 

enderffx

Senior Member
Sep 16, 2011
238
36
...

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.


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 ----------

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

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

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

Ender
 

pwntrik

Member
Apr 29, 2016
35
7
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

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.
 

enderffx

Senior Member
Sep 16, 2011
238
36
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.

Yup, everything worked, 5.2.4.1 is running rooted fine, KODI is running in 4k and i am basically a happy puppy :)

Ender
 

andreizet96

Member
Nov 16, 2013
10
0
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.

Sent from my Samsung Galaxy S8 using XDA Labs
 

dave157

Member
Jun 29, 2012
43
10
@rbox, 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.
 

rbox

Recognized Developer
Apr 22, 2011
1,776
2,612
@rbox, 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.

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.
 
  • Like
Reactions: dave157

dave157

Member
Jun 29, 2012
43
10
@rbox, 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!
 

mrchrister

Senior Member
Nov 28, 2009
241
59
@rbox 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...
 
Last edited:

_u2pop_

Senior Member
Jul 14, 2014
168
56
Hi @rbox 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 :(
 

Attachments

  • 20191022_232152.jpg
    20191022_232152.jpg
    247.8 KB · Views: 93
Last edited:
Hi @rbox 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 :(

Try a different micro sd or plug ethernet in and adb sideoad it as per rbox first post

Installation
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.
Copy the zip file to your destination.
Connect adb

adb connect IPADDRESS

adb shell

sh /sdcard/firetv2_recovery_vX.zip



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.

Reboot
 
Last edited:

Rortiz2

Senior Member
Hi @rbox,
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.
 

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.