FireTV 2 (sloane) Prerooted Stock Images [5.2.4.1_r1]

1,592 posts

Thanks Meter: 1,982

By , Recognized Developer on 6th February 2016, 10:10 PM

Post Reply Email Thread

Page 1 of 40 1 2 3 11 Last

Here 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

Changelog and Downloads:

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

Quick Reply Reply

The Following 53 Users Say Thank You to rbox For This Useful Post: [ View ]

6th February 2016, 10:25 PM |#2

Senior Member

Thanks Meter: 330

Donate to Me

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

Quick Reply Reply

The Following 11 Users Say Thank You to AFTVnews.com For This Useful Post: [ View ] Gift AFTVnews.com Ad-Free

6th February 2016, 11:17 PM |#3

Junior Member

Thanks Meter: 0

Awesome! Thanks !

Quick Reply Reply

7th February 2016, 01:09 AM |#4

Senior Member

Thanks Meter: 36

Quote:

Originally Posted by wadisnake

Awesome! Thanks !

Awesome! Thanks for all your great work!

Quick Reply Reply

7th February 2016, 10:42 AM |#5

Member

Thanks Meter: 10

Donate to Me

Any one with Mac Guide Please help

Quick Reply Reply

8th February 2016, 03:23 AM |#6

Recognized Contributor

Phoenix

Thanks Meter: 4,543

Donate to Me

awesome sauce!

Quick Reply Reply

10th February 2016, 01:13 PM |#7

Junior Member

Thanks Meter: 2

Hi,
I ended up with following message during image installation:

Code:

[...]
Coping system image...
Updater process ended with signal: 7
Error installing zip file '/usb/sloane-5.0.4-rooted_r2.zip'
Updating partition details...
...done

And, no wonder... after power cycling (I had to do so, since recovery seemed to be frozen) it stuck in a bootloop.
But I still can access recovery!

Any ideas? Is there any way to get a more verbose output?
(Used recovery 3.0.0-2 and recovery_installer v3)

Edit:
Now there is no /system Partition mounted

Edit2:
I was able to mount /dev/block/mmcblk0p13 manually to /system but it seems that I can't mount it in rw mode.
If I do so, it switches back to ro when I there the folder. (I think, that could be the error during image installation)

What's strange is: If I enter /system/lib I can't execute any command (like "ls" "touch" etc. only cd is working) I get following output:

Code:

/system/lib # ls
CANNOT LINK EXECUTABLE DEPENDENCIES: "libc.so" is 32-bit instead of 64-bit
# echo $LD_LIBRARY_PATH
.:/sbin

File libc.so is existing, but I can't finde a way to get the file type data

Edit3:
More strange things:
I was wrong! I am able to write to /system till the point when I execute a "ls"

Than its back to ro.

Edit4:
I tried to reflash recovery and the following error:
Locating the target file...

Code:

[...]
Reading 05055F000: 100%
Opening the target file...
Reading 01D947000: 100%
error: source file is larger than target file!

No shure if that was there when I flashed it first.
Related to this post

Quick Reply Reply

10th February 2016, 07:48 PM |#8

Member

Leipzig

Thanks Meter: 1

re-rooted works fine !

its full Google Play Store Support possible ?

Quick Reply Reply

10th February 2016, 09:03 PM |#9

Recognized Contributor

Phoenix

Thanks Meter: 4,543

Donate to Me

Quote:

Originally Posted by Hoggels

its full Google Play Store Support possible ?

yes.. its been done already but some users are having issues

Quick Reply Reply

11th February 2016, 02:23 AM |#10

OP Recognized Developer

Thanks Meter: 1,982

Donate to Me

Quote:

Originally Posted by Takeoo111111

Hi,
I ended up with following message during image installation:

Code:

[...]
Coping system image...
Updater process ended with signal: 7
Error installing zip file '/usb/sloane-5.0.4-rooted_r2.zip'
Updating partition details...
...done

Code:

/system/lib # ls
CANNOT LINK EXECUTABLE DEPENDENCIES: "libc.so" is 32-bit instead of 64-bit
# echo $LD_LIBRARY_PATH
.:/sbin

File libc.so is existing, but I can't finde a way to get the file type data

Edit3:
More strange things:
I was wrong! I am able to write to /system till the point when I execute a "ls"

Than its back to ro.

Edit4:
I tried to reflash recovery and the following error:
Locating the target file...

Code:

[...]
Reading 05055F000: 100%
Opening the target file...
Reading 01D947000: 100%
error: source file is larger than target file!

No shure if that was there when I flashed it first.
Related to this post

If you reboot in the middle of flashing the ROM, you're /system is going to be corrupt. It's a miracle recovery is still working. The reason the installer is failing is because you can only use it for 100% stock roms. Once you start using recovery and flashing things, you cannot (and should not) use the installer. I will add a warning.

If recovery hangs again, you can run

Code:

killall recovery

from adb shell and it will restart. It is extremely important never to reboot if you have a failure. As for logs... /tmp/recovery.log has the full log. Have you verified the file transfer properly before trying to flash?

Quick Reply Reply

The Following User Says Thank You to rbox For This Useful Post: [ View ]

11th February 2016, 06:19 AM |#11

Member

Leipzig

Thanks Meter: 1

Google Playstore

Quote:

Originally Posted by elliwigy

yes.. its been done already but some users are having issues

Who can find it? Itsca zip to Flash with Recovery or gapps.org?
For gapps.org what for options i must select it? Thx

Quick Reply Reply

Post Reply

Page 1 of 40 1 2 3 11 Last

Guest Quick Reply (no urls or BBcode)
The following errors occurred with your submission

Okay
Message: Posting Quick Reply - Please Wait

Previous Thread Next Thread

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode