FireTV 2 (sloane) Prerooted Stock Images [5.2.7.6_r1]
- Thread starter rbox
- Start date
Wow flashed the new firmware & then as it was flashing i noticed it had been pulled because of errors/problems, then when i booted it said updating dont touch anything! I almost died (HAHA), anyway ive reverted to the version before..... so now im on 5.0.5.r1 .
(& the update was for the remote control)
(& the update was for the remote control)
@AFTVnews.com
Yes I believe it is only 1080I. An older set from best buy Insignia brand. Best Buys store brand. What is strange is the 1080P (Westinghouse) capable tv could see the recovery ok but couldn't see the Amazon home screen after boot up. It would reboot ok from TWRP then go blank after the white amazon logo, but you could see there was still some signal being sensed by the tv, like the FTV was switching resolutions but the tv couldn't switch with it. I think I will try unplugging the Westinghouse so it "forgets" the connection later tonight when I am installing the new 5.0.5 update.
For some reason Multi-Quote is not working for me. Tried to quote two posts with this post. No dice.
edit: figured out the multi-Quote lol.
---------- Post added at 06:42 PM ---------- Previous post was at 06:26 PM ----------
Are both tvs 1080i? And the one does work for TWRP?
"tits up" lol sounds like a nice british description. I like that one. I might incorporate that in my repertoire. I see that a bit in the Kodi groups.
Last edited:
Forgot to disable updates after flashing the 5.0.4 pre-rooted ROM after doing a full wipe and today when I got home from work I was on 5.0.5 with no root anymore. :-/
Upgrade to 5.0.5 successful!!
Upgrade to 5.0.5 successful!!
I used the 1080p tv so I could see TWRP, flashed the rom, reboot same issue with the Amazon home screen being blank. Reboot, still the same. Unplug tv, reboot, same. Unplug tv swap hdmi ports, reboot, same. Used tv menu to change hdmi port input to a different device (cable box) and back to FTV.
BOOM now the tv displays the FTV Amazon home screen. Go figure. Not sure what actually is happening but at least I think I can get it to work on this tv if I want to. Actually this tv has a htpc hooked up to it so I won't need it for that. Now to try it in the kitchen, which is the tv I actually got this FTV for. Might wait till the hdmi switch I ordered from Amazon shows up, this tv only has 1 hdmi input, cable box hooked up to it now. If I get these all going as desired, I my goal is to eliminate the cable service. TOO expensive anymore and constantly raising prices. Five tvs in the household.
---------- Post added at 08:57 PM ---------- Previous post was at 08:48 PM ----------
When you say full wipe are you wiping the system and data partitions as you would with an android phone?
I only did the cache and dalvik. Could be wrong Not sure but I thought i saw that you don't wipe system or data on these.
Upgrade to 5.0.5 successful!!
I used the 1080p tv so I could see TWRP, flashed the rom, reboot same issue with the Amazon home screen being blank. Reboot, still the same. Unplug tv, reboot, same. Unplug tv swap hdmi ports, reboot, same. Used tv menu to change hdmi port input to a different device (cable box) and back to FTV.
BOOM now the tv displays the FTV Amazon home screen. Go figure. Not sure what actually is happening but at least I think I can get it to work on this tv if I want to. Actually this tv has a htpc hooked up to it so I won't need it for that. Now to try it in the kitchen, which is the tv I actually got this FTV for. Might wait till the hdmi switch I ordered from Amazon shows up, this tv only has 1 hdmi input, cable box hooked up to it now. If I get these all going as desired, I my goal is to eliminate the cable service. TOO expensive anymore and constantly raising prices. Five tvs in the household.
---------- Post added at 08:57 PM ---------- Previous post was at 08:48 PM ----------
When you say full wipe are you wiping the system and data partitions as you would with an android phone?
I only did the cache and dalvik. Could be wrong Not sure but I thought i saw that you don't wipe system or data on these.
Correct I did a full wipe of everything except the external SD card. I was following a guide on how to get play store to not error out. It wasn't successful in fixing play store and now I have to start over.
Previously I wasn't doing that full wipe only flashing over the existing rom with the new ones which worked fine. No need to clear cache either in the fire tv case.
I updated the OP with 5.0.5_r3. This will disable stock recovery, making it safer for people who forget to disable updates. Otherwise, there are no functional changes to 5.0.5_r1, although su is installed slightly differently, and it requires a newer 2ndinit that comes with the rom.
On none of the recent 5.0.5 releases - SuperSU can be launched . I'm fine with only ever getting in contact with it through its "grant me permissions" popups for now - but... managing applications root rights after the fact - actually should be considered "the basics".
I have read through this forum enough to know that this is a limitation that suddenly appeared with newer versions of the SuperSU app, but the suggestions on how to handle it are all over the place - so are the version numbers mentioned, and on top of it the .apk itself is nested in a folder structure that is new to me (system apks in folders?) and that I dont particularly want to mess with, not knowing what I am doing.
Please - look into it, if you find the time.
I have read through this forum enough to know that this is a limitation that suddenly appeared with newer versions of the SuperSU app, but the suggestions on how to handle it are all over the place - so are the version numbers mentioned, and on top of it the .apk itself is nested in a folder structure that is new to me (system apks in folders?) and that I dont particularly want to mess with, not knowing what I am doing.
Please - look into it, if you find the time.
Last edited:
I flashed v5.0.5-r1 yesterday, and I was gonna upgrade to v5.0.5-r3 today but I realized that the usb keyboard isn't working anymore at boot to be able to get into recovery. I tried 2 different keyboards and they don't respond until the fire tv boots all the way. Is there anything I can do to fix this? Thanks.
Flashed v5.0.5-r1 > v5.0.5-r2 > v5.0.5-r1 > v5.0.5-r3 in the past two days - never had a problem with my keyboard not being recognized. It shouldnt even be affected by you having "USB debugging" still turned on - but in any case, try turning it of - just in case.
Please read what rbox said here -
February 13, 2016 - 5.0.5_r3 (md5sum: 92d08a12d240cf9bf6d25005a65bd82d)
Starting with this update, stock recovery will be disabled to prevent stock updates from being flashed. Please refer to the instructions above for managing stock recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-3. Because this comes with a newer 2ndinit version, "do not flash an older recovery package". "Doing so will disable su."
I also have this problem. But my two keyboards had never worked. The keyboards are a wired and a wireless one.
I reflashed the recovery using:
Code:
sh /sdcard/firetv2_recovery_v4.zipUnfortunately that didn't help in my case, no reaction on right key press.
But: If I touch the file "/cache/bootmenu_recovery" (to force boot into recovery), then connect via ADB and execute "mouse" the keyboard presses are working, so I can use the recovery using mouse emulation?! Strange.
Any ideas? (Yes, USB debugging is off).
EDIT: Using v5.0.5-r1 and recovery v4 currently.
Last edited:
Dear rbox,
Is it possible to give via she'll a reboot command to flash directly the new zip firmware? I have no usb keyboard so I can't select twrp
Thx
So you can follow what @androidfux said to force it to boot in to recovery and use the mouse emulator.
Unfortunately, there is nothing I can do about this. It has never worked on FireTV, even on FireTV 1. I think it has something to do with something Amazon has done to Android.
I'm not quite sure why people are reporting keyboard problems. I did notice an intermittent problem at one point when I was testing the unbricking image, but I haven't had any problems with any of the 5.0.5 releases. Unfortunately if you try to flash v4 on 5.0.5_r3 it will break su. I will look in to what is different with 5.0.5_r1 and v4.
I just took a look at 5.0.5_r1 and v4. They both contain identical copies of 2ndinit and the recovery ramdisk. There is no reason one would work better than the other. The only suggestion I could give would be to flash 5.0.5_r3 and see if the problem goes away. Otherwise I could say try to physically unplug the power and plug it back in and see if that makes the keyboard work. But flashing v4 ontop of 5.0.5_r1 is definitely not going to change anything.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
78Here are prerooted stock images for use with my recovery. Note that these contain addon.d support, so any 3rd party things you install to /system need an addon.d script to be retained between flashes.
Managing Stock Recovery
Starting with 5.0.5_r3, stock recovery gets disabled. This means you cannot reboot in to stock recovery manually or automatically because of a system update. This will make it safer for people who forget to disable updates. You should still disable updates though. If for whatever reason, you want to reenable it, or verify it is disabled, you can use the manage_recovery program. Under normal circumstances, you should never need to use manage_recovery.
- Connect to adb and start a shell
- Switch to root with su
- Run manage_recovery (if you do not run su first, it will seem to run, but won't actually be able to do anything)
Code:manage_recovery
There are 3 different scenarios that manage_recovery will detect and prompt for.
The first is when stock recovery is disabled, it will look like this:
Code:Checking current stock recovery status... NOT STOCK Checking for reason... DISABLED Stock recovery is currently disabled, Would you like to enable it? Type 'yes' to enable it, anything else to quit.
The second is when a stock recovery is flashed that does not match the current system version:
Code:Checking current stock recovery status... NOT STOCK Checking for reason... WRONG VERSION Would you like to disable stock recovery? Type 'yes' to disable it, anything else to quit.
And finally, the third is when stock recovery is enabled and the correct version:
Code:Checking current stock recovery status... STOCK Would you like to disable stock recovery? Type 'yes' to disable it, anything else to quit.
After changing the recovery status, you can run the program again to verify it changed.
WARNING: DO NOT FLASH 5.0.5.1 OR EARLIER IF YOU STARTED WITH VERSION 5.2.1.0 OR LATER
NOTE: If you were at 5.2.6.6 or below, you MUST flash 5.2.6.7 before going to 5.2.6.8 or later.
Changelog and Downloads:
- December 26, 2020 - 5.2.7.6_r1 (md5sum: 01178aecf55cd895cbfdeb64d5a19e62)
- July 4, 2020 - 5.2.7.3_r1 (md5sum: 875436574974c3603aef179b898a4c60)
- December 7, 2019 - 5.2.7.2_r1 (md5sum: b91c6b596ef5daae085ddf08c1c504e5)
- September 21, 2019 - 5.2.7.1_r1 (md5sum: 0d72e930cee2652d324d2fceebdd4202)
- June 29, 2019 - 5.2.7.0_r1 (md5sum: 1e402185cefb91276d811f1321494863)
- March 30, 2019 - 5.2.6.9_r1 (md5sum: a3e23a7f337346a4638f8c8895632046)
- February 10, 2019 - 5.2.6.8_r1 (md5sum: bd0daa677635e04e368d1b2b235e03e9)
- December 2, 2018 - 5.2.6.7_r2 (md5sum: b50a1fddb3e01c18c353195c9f7f50cd)
- This ROM contains updated DRM firmware.
- November 27, 2018 - 5.2.6.7_r1 (md5sum: b0ee16b57b37a934778ca1436f29916a)
- This ROM contains updated DRM firmware.
- September 28, 2018 - 5.2.6.6_r1 (md5sum: 37ce0c6dda850fa2d462835496b68576)
- June 24, 2018 - 5.2.6.3_r1 (md5sum: 08982269022c01c9a1eac8ff94adf637)
- January 28, 2018 - 5.2.6.2_r1 (md5sum: 0967de2a707f173ca8715356a20ea88e)
- October 8, 2017 - 5.2.6.0_r1 (md5sum: 84eedbb2e9fd4b57679747ecb8fae797)
- July 27, 2017 - 5.2.4.2_r2 (md5sum: a96e73478cdbe8659f6758a5d27b4738)
- This includes updated firmware to fix Hulu and HBO.
- July 3, 2017 - 5.2.4.2_r1 (md5sum: 0719fde0db90702c2407461003217977)
- May 1, 2017 - 5.2.4.1_r1 (md5sum: 64915fceb4e7d1c0de9d1ef625db48e7)
- December 10, 2016 - 5.2.4.0_r1 (md5sum: 77af47d3c43fe79e82740d0cc0c4bce5)
- September 10, 2016 - 5.2.1.1_r1 (md5sum: fd7c06bce26d4aa611eef402ef156322)
- July 4, 2016 - 5.2.1.0_r2 (md5sum: a69981f6d4dce77cf1f9907f8a39b391)
- This is the same as the previous 5.2.1.0, just with the updated version that Amazon released.
- June 1, 2016 - 5.2.1.0_r1 (md5sum: 81693eae0ce3b497cf425691bc4ad041)
- This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
- April 8, 2016 - 5.0.5.1_r1 (md5sum: c6d8a11b7ca7a0b45a38af4f9f70cf2d)
- The updated TWRP in this version should disable auto flashing amazon updates.
- This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
- February 14, 2016 - 5.0.5_r4 (md5sum: 9145c8f6d52fda2c3cfdd1d091bcb331)
- The updated TWRP in this version should fix the issues certain keyboards were having.
- This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
- February 13, 2016 - 5.0.5_r3(md5sum: 92d08a12d240cf9bf6d25005a65bd82d)
- Starting with this update, stock recovery will be disabled to prevent stock updates from being flashed. Please refer to the instructions above for managing stock recovery.
- This includes 2ndinit version dee776 and TWRP version 3.0.0-3. Because this comes with a newer 2ndinit version, do not flash an older recovery package. Doing so will disable su.
February 12, 2016 - 5.0.5_r2
- OTA updates are permanently disabled, otherwise the same as r1.
- This breaks booting with a factory reset.
- February 12, 2016 - 5.0.5_r1(md5sum: 211a15f949e317b02c637b2927a7c8ba)
- This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
- February 8, 2016 - 5.0.4_r2(md5sum: ebcecf89e9b81c02f22ed2706fe5f796)
- This comes with TWRP 3.0.0-2
- This comes with the same 2ndinit version
- February 6, 2016 - 5.0.4_r1(md5sum: 87ce4f7802d21bd1f14c45d473783713)
- This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
- February 6, 2016 - 5.0.3.1_r1(md5sum: e38d66dce235c9c0122dfbde2db5a6b6)
- This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
15Awesome work!
For those who need a step-by-step guide with screenshots:
[GUIDE] How to Root a Fire TV 2 by installing rbox's Pre-Rooted Image
[VIDEO GUIDE]
