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
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
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]
Awesome! Thanks !
wadisnake said:
Awesome! Thanks !
Click to expand...
Click to collapse
Awesome! Thanks for all your great work!
Any one with Mac Guide Please help
awesome sauce!
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
re-rooted works fine !
its full Google Play Store Support possible ?
Hoggels said:
its full Google Play Store Support possible ?
Click to expand...
Click to collapse
yes.. its been done already but some users are having issues
Takeoo111111 said:
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
Click to expand...
Click to collapse
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?
Google Playstore
elliwigy said:
yes.. its been done already but some users are having issues
Click to expand...
Click to collapse
Who can find it? Itsca zip to Flash with Recovery or gapps.org?
For gapps.org what for options i must select it? Thx
Hoggels said:
Who can find it? Itsca zip to Flash with Recovery or gapps.org?
For gapps.org what for options i must select it? Thx
Click to expand...
Click to collapse
Read this tread: http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
bula1ca said:
Read this tread: http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
Click to expand...
Click to collapse
haha thx for posting the link..
amazing how much tunnel vision exists as theres threads for most anything but somehow some fail to find them lol
elliwigy said:
haha thx for posting the link..
amazing how much tunnel vision exists as theres threads for most anything but somehow some fail to find them lol
Click to expand...
Click to collapse
LOL
Success!! I have the issue with the recovery screen being scrambled. Switched to another tv got through recovery and installed rom, then the screen would be blank when booting to system. After 2 hours of reading and trying.... Went back to the original tv , the tv recognizes the home screen display. Apparently whatever the issue with the recovery screen is prevented the home screen from being visible on the second tv. anyway all good now!
TorqueWrench001 said:
Success!! I have the issue with the recovery screen being scrambled. Switched to another tv got through recovery and installed rom, then the screen would be blank when booting to system. After 2 hours of reading and trying.... Went back to the original tv , the tv recognizes the home screen display. Apparently whatever the issue with the recovery screen is prevented the home screen from being visible on the second tv. anyway all good now!
Click to expand...
Click to collapse
i think someone else had the same issue and i think it was the tv lol
what do you have the fire tv set to in the display settings? If you had it set to a certain setting such as 1080p but the tv is in a different setting could be the issue.. or something like that lol
5.0.5_r1 installed perfectly
krawhitham said:
5.0.5_r1 installed perfectly
Click to expand...
Click to collapse
how did you install....did you update recovery first then flash 5.05_r1?
thanks
TorqueWrench001 said:
Success!! I have the issue with the recovery screen being scrambled. Switched to another tv got through recovery and installed rom, then the screen would be blank when booting to system. After 2 hours of reading and trying.... Went back to the original tv , the tv recognizes the home screen display. Apparently whatever the issue with the recovery screen is prevented the home screen from being visible on the second tv. anyway all good now!
Click to expand...
Click to collapse
elliwigy said:
i think someone else had the same issue and i think it was the tv lol
what do you have the fire tv set to in the display settings? If you had it set to a certain setting such as 1080p but the tv is in a different setting could be the issue.. or something like that lol
Click to expand...
Click to collapse
Someone in the comments of my guide said the scrambled screen issue was due to incompatibility with 1080i TVs. I'm curious @TorqueWrench001 is your scrambled TV a 1080i set that's not capable of 1080p ?
AFTVnews.com said:
Someone in the comments of my guide said the scrambled screen issue was due to incompatibility with 1080i TVs. I'm curious @TorqueWrench001 is your scrambled TV a 1080i set that's not capable of 1080p ?
Click to expand...
Click to collapse
Mine is a 1080i tv. Old sony bravia. Great picture and sound though. The display is most definitely tits up on twrp. However, I have a broken tiny cheap wall mounted 1080i flatscreen, with no sound, which is now my dedicated 2nd aftv monitor, just for twrp purposes. It even fits snug under my living room tv unit out of sight.
I am awaiting funds for a new samsung curved 55inch beast. But, I think it will have to wait until the sony bravia dies on me! lol
Related
BETA WARNING:
This version of CWM is now in beta testing.
I need user reports of what zips are compatable/not-compatable.
I will remove the beta tag once I have a fair idea of what update zips are/arnt compatable with CWM 6.0.
For any developers: I will be providing instructions/binaries to work with CWM 6.0 soon.
They will likely not be compatable with streakmod.
Once CWM is out of beta, I would strongly recommend everyone migrating off of streakmod.
Click to expand...
Click to collapse
How to use fastboot:
Setting up fastboot for Windows -XDA wiki
Installing a recovery - XDA wiki
Click to expand...
Click to collapse
Requirements:
Ability to enter fastboot mode
Basic understanding of the command line
Click to expand...
Click to collapse
Install instructions:
Download Clockwork mod recovery.img
streak5
streak5ex (link TBA)
streak5sd8 (link TBA)
Turn device off
Hold down Power and Camera Down
Flash the recovery with "fastboot flash recovery <path to recovery.img>"
Click to expand...
Click to collapse
What works:
Clearing caches
Factory resetting
Nandroid
Update zip flashing
USB mounting
Click to expand...
Click to collapse
Notice:
What to do if your nandroid freezes at /cache, /data, /datadata:
Flash update-CWMfixer-1.zip as an update zip and try again.
OR: Factory reset and manually restore data (Not recommended)
This is portrait only, unless someone is willing to give me code to rotate it 270 degrees it will remain as so
Removing the battery door while recovery is active will cause it to exit (this is intentional, it is also part of the stock 407 kernal)
Streakmod nandroids are not compatable with CWM. You may be able to get it to work by copying the contents of "rom_backup" to "clockworkmod", but this is not supported
If you get errors about not being able to mount your SD card, power the device off and remove the battery for a moment, then try again
Notes about sd-ext:
If you get the error message while nandroid: "sd-ext.img not found. Skipping restore of /sd-ext." This is normal, as sd-ext is an optional partition.
If you get the error message while formatting: "E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p2", same as above
Click to expand...
Click to collapse
Controls:
Vol Up: Scroll up
Vol Down: Scroll down
Camera: Select item
Back: Go back
Click to expand...
Click to collapse
Changelog:
Sep 09 2012: Updated to 6.0.1.2
Aug 21 2012: Removed beta tag, added workaround for nandroid issues
Aug 07 2012: Updated to 6.0.1.1
Jul 21 2012: Updated to 6.0.1.0 - entered beta phase
Jul 20 2012: Updated to 6.0.0.9
Jul 18 2012: Initial release
Click to expand...
Click to collapse
2char
glad to hear this
i am trying
So is this the touch version?
it displays nothing when moving up (or down)
and show back when moving for the second time
not just display ，
if you want to select the 2nd (4th ，6th ... ）item
you must moving up and down till it shows "BACK menu button enabled" or "BACK menu button disabled"
and is there anying new in CWM6007?
i had posted CWM5027 chinese version
most functions are working well
what about change it back to english version?
and i had seen a special version of CWM4010
it has a new function “advanced backup”
i think it's very useful
http://bbs.anzhi.com/thread-3182311-1-1.html
the Attach File is for ZTE X876
it is NOT for streak
Crinos512 said:
So is this the touch version?
Click to expand...
Click to collapse
no
If by advanced backup you mean selective backing up of partitions.
I had considered that many months ago, but I didnt add it because it wouldnt matter. (I never had a fully working CWM previously)
CWM never liked booting on the S5 for whatever reasons.
Adding in selective backups shouldnt be terribly difficult, but I'm not really interestested in modding CWM, (excluding the S5) all my devices have working CWM 6.0.0.x and the source code is available for anyone interested.
I'm trying to modify CWM as little as possible to make it easier for future changes. CWM 6.0 was only released a couple days ago and we're already at 6.0.0.7+
The biggest change in 6.0 is "dedupe" where nandroids are base + delta so if you constantly nandroid, the deltas become very small.
Besides the screen I would assume everything works and it would be ready to replace streakmod, but the screen issue is very annoying.
Also to note: I will attempt to port TWRP later, as it DOES support RGB_565 displays still, and since we have an ICS kernel, it might just work.
somewhere from CWM 5.5 -> 6.0 RGB_565 displays took a back seat to RGBX_8888/BGRA_8888 displays and I guess wasnt really fixed.
Edit: The other major feature is that I dont have to make multiple versions of every update zip.
Currently it's S5/V and S7 and nothing for the S10.
Streakmod doesnt have much in /sbin, CWM has busybox, and a bunch of filesystem utils.
so instead of needing:
Code:
mount("MTD", "system", "/system"); (for the S5/V)
mount("ext4", "/dev/block/mmcblk3p3", "/system"); (for the S7)
mount("ext4", "/dev/block/mmcblk0p3", "/system"); (for the S10)
Or make a new one for each specific device I'm gonna support
I can do
Code:
run_program("/sbin/busybox", "mount", "/system");
and that will work with any device with any device with a recent enough recovery
Edit2:
If and when I get CWM 6.0 working on the S5, I will be making all future update zips "generic" as in they should be able to install on any device (assuming they're relevent for that device)
Examples of such are: Superuser.zip, Gapps
Edit3:
After doing a test zip, I can in fact use the same mount script on all 4 devices instead of needing 3 seperate ones.
Unfortunately like previously mentioned they simply dont work on streakmod as it doesnt have busybox.
Edit4:
I will be internally using CM6.0 now, regardless of if I can fix the framebuffer issue.
Any future S5-specific update zips will be deemed "legacy update" zips
I will be updating to CWM 6.0.0.9 as soon as it's available.
Also: I have no idea of older update zips (from whoever) will work on CWM 6.0, there's many changes to the scripting from 1.8 -> 6.0 (streakmod is based on a very old CWM) and even edify based update.zips may not work if they're using an old enough binary.
Updated to 6.0.0.9 now,
there's no changes specific to the S5 though, so everything prevous still applies
TheManii said:
Updated to 6.0.0.9 now,
there's no changes specific to the S5 though, so everything prevous still applies
Click to expand...
Click to collapse
maybe this will help people to test new recovery without PC
just flash it in recovery as ROMs
2 files?
I assume recovery6009a.zip is the CWM recovery...what is the other one?
The other one is likely streakmod from the version number
I think I got it
Edit: I am in the middle of testing it, but I think I will be able to release a full version soon
CWM 6.0.1.0 is now released an in the beta phase!
What I need tester reports of:
flashing recent roms
flashing random (things you would normally expect to flash in streakmod) zips
fac resetting
I believe nandroids are already reliable, but any reports to re-confirm/deny would be welcomed.
USB mounting works fine
I will be migrating all my utilities to be CWM compatable and marking streakmod-compatable versions as "legacy"
ALL HAIL TheManii!!!
Dude, you are god! THANK YOU!
what are the odds of a flashable Zip version? Can't wait to try this out too!
Crinos512 said:
2 files?
I assume recovery6009a.zip is the CWM recovery...what is the other one?
Click to expand...
Click to collapse
these two could be used to flash recovery to clockwork mod recovery 6.0.0.9 or to streakmod 0.3.2.8these are zip flash ,without PC
Controls:
•Vol Up: Scroll up
•Vol Down: Scroll down
•Power: Select item
•Back: Go back
Click to expand...
Click to collapse
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
manics said:
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
Click to expand...
Click to collapse
Is this the flashable zip via streakmod recovery?
manics said:
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
Click to expand...
Click to collapse
i dont like using the touch key for CWM coz sometime it thinks u pressed it twise, like a double tap.. it gets very annoying
sinan33 said:
Is this the flashable zip via streakmod recovery?
Click to expand...
Click to collapse
yes,
not only streakmod but also clockwork mod
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.
If you are currently on FireOS3 and CWM you MUST install TWRP recovery from the link above before using these.
Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it.
Changelog and Downloads:
July 4, 2020 - 5.2.7.3_r1 (md5sum: 92824186b5eec7e86792897bfb9593b7)
December 7, 2019 - 5.2.7.2_r1 (md5sum: 8dd08a41900a75794f28c455e173141f)
June 29, 2019 - 5.2.7.0_r1 (md5sum: 97b9ffef275d7dffcae085b2325aa9cc)
March 30, 2019 - 5.2.6.9_r1 (md5sum: 2f00ee478118ccf034b70236357ee0a3)
November 27, 2018 - 5.2.6.7_r1 (md5sum: cc455830d78f2d545760f1705dbe4f63)
October 7, 2018 - 5.2.6.6_r1 (md5sum: de48df30cadf9f88865698d3a3e514ef)
June 24, 2018 - 5.2.6.3_r1 (md5sum: c4fcecc0d3dda3f5c58ba9bbc1fddbdc)
January 28, 2018 - 5.2.6.2_r1 (md5sum: facfcc900ac21e70023b6fbf7259b5b0)
October 8, 2017 - 5.2.6.0_r1 (md5sum: 126fffd4f2384a483792b336b0c89b83
July 3, 2017 - 5.2.4.1_r2 (md5sum: ee25fe57cce08dce6c5962871916c7e3
May 1, 2017 - 5.2.4.1_r1 (md5sum: 64451a8f88cb5a3fff53f14c80ba2267)
January 31, 2017 - 5.2.1.2_r1 (md5sum: 4a01e9a4e6bdcb98da97d2438bf5066d)
September 3, 2016 - 5.2.1.1_r1 (md5sum: 4c4cc2b9dc01cf8397905712b8c91ae3)
July 4, 2016
5.2.1.0_r1 (md5sum: c465bbbddaf3254f805bddbf2d162637)
5.0.5_r2 (md5sum: 32c869fff5e39a5c0d2f5f48b3a10ef5)
This includes the same 2ndinit as before and TWRP version 3.0.0-7. This version of TWRP has support for 720p and fixes the crashing/looping.
May 20, 2016 - 5.0.5.1_r1 (md5sum: 5398851cb37ecd6c5df80abe1cc85447)
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - 5.0.5_r1 (md5sum: 924dadb59d73083704844bb27f189449)
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
Everything below here is FireOS3.
September 7, 2015 - Added 51.1.6.3_516012020 (md5sum: fcf1a8ddf2f3bc93280af03dcf408ac8)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
August 20, 2015 - Added 51.1.6.2_516011120 (md5sum: 3fd1cc67fdd3351b470d09cff586fbf8)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
July 21, 2015 - Added 51.1.6.1_516010220 (md5sum: 61ae1e646c970faf137e9a31d64a1316)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
July 9, 2015 - Added 51.1.6.0_516009820 (md5sum: a1b550d1a7b21a348ca6bd0d7127427c)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
May 24, 2015 - Added 51.1.5.3_515040320 (md5sum: a12852edbe6dc24146533f43e0ae4a05)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Apr 15, 2015 - Added 51.1.5.0_515030720 (md5sum: de2ab7f2d3072e10d3e592b73ca52750)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Mar 26, 2015 - Added 51.1.5.0_515020820 (md5sum: b7005dd3cc0b6a15dae21b0170aeae85)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Nov 21, 2014 - Added 51.1.4.1_514013920+fixed (md5sum: 4429327daeed0df852731d81fa9b1f54)
Starting with this update, this requires FireTV Boot Menu.
You also must ensure you have already flashed 51.1.4.0.
Nov 19, 2014 - Added 51.1.4.1_514013920 (md5sum: 348c8b23d785177f7dfd45cc2ef19626)
Oct 30, 2014 - Added 51.1.4.0_514006420+updated (md5sum: b1b48348cb56c0b83a3affc9fd06e07e)
This fixes the Netflix problem from the original 51.1.4.0. After flashing and rebooting, you might get a hung black screen. If that is the case, just pull the power and plug it back in. Also, Netflix might be broken for International people using DNS unblocking. Please let me know if it works/doesn't work for you when using DNS unblocking.
Oct 29, 2014 - Added 51.1.4.0_514006420[/URL] (md5sum: 98074ae3dead5c12ce77d735c2126b80)
Oct 02, 2014 - Added 51.1.3.0_513011820 (md5sum: 8a7b02691760abf11db4c1c583c20d8f)
Sep 20, 2014 - Added 51.1.3.0_513011520 (md5sum: 2dbd022eacbad0b001753d7519f0ad1b)
Sep 19, 2014 - Added 51.1.1.0_511070220 (md5sum: f98fe5b7de4acb5d2dfa4d8586179b98)
Here are some guides with step by step instructions:
How to install ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to update ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-update-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to remotely control ClockworkMod on the Amazon Fire TV using ADB
http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/
How to install a Custom ROM Image on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
How to update a Rooted Amazon Fire TV to the Latest Version Without Losing Root
http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/
How to Revert back to Stock Recovery and Stock Software
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
..
@rbox when flashing the pre-rooted image, does it also rebuild/replace the recovery?
I'm just curious how these work, and if CWR would then need to be 'dd' again. I did a quick compare between the pre-rooted image and the stock, and the only differences I see are su binary, superuser.apk, and the removal of every file from the root of the zip but:
boot.img
NON-HLOS.bin
prod_cert_swap.sed
sed
Luxferro said:
@rbox when flashing the pre-rooted image, does it also rebuild/replace the recovery?
I'm just curious how these work, and if CWR would then need to be 'dd' again. I did a quick compare between the pre-rooted image and the stock, and the only differences I see are su binary, superuser.apk, and the removal of every file from the root of the zip but:
boot.img
NON-HLOS.bin
prod_cert_swap.sed
sed
Click to expand...
Click to collapse
No. It doesn't touch the recovery. These images are basically just the regular image with the bootloader and nonessential images pulled out. And as you can see, it comes with su.
rbox said:
No. It doesn't touch the recovery. These images are basically just the regular image with the bootloader and nonessential images pulled out. And as you can see, it comes with su.
Click to expand...
Click to collapse
Doesn't android typically rebuild & flash the recovery partition from boot.img and /system/etc/recovery-resource.dat when it detects it's been changed? I was just curious when that normally would occur on a stock FireTV, and what prevents this from happening on your pre-rooted images. I haven't used any prerooted images. Already had root and just dd'd your cwr_recovery.img. CWR asks you if you want to disable the stock recovery process. As a test I picked no, and CWR didn't get replaced. So should I assume that Amazon doesn't run any scripts at boot that check the recovery and rebuild/flash it?
To make a long story short. I was just curious if your pre-rooted images disabled the recovery replacement, since I still saw the recovery-resource.dat used to build them in the zip. But I guess FireOS doesn't do that at boot
edit: I guess that may have been disabled by towelroot, since the install-recovery.sh is being used to start the /system/xbin/daemonsu --auto-daemon &
Luxferro said:
Doesn't android typically rebuild & flash the recovery partition from boot.img and /system/etc/recovery-resource.dat when it detects it's been changed? I was just curious when that normally would occur on a stock FireTV, and what prevents this from happening on your pre-rooted images. I haven't used any prerooted images. Already had root and just dd'd your cwr_recovery.img. CWR asks you if you want to disable the stock recovery process. As a test I picked no, and CWR didn't get replaced. So should I assume that Amazon doesn't run any scripts at boot that check the recovery and rebuild/flash it?
To make a long story short. I was just curious if your pre-rooted images disabled the recovery replacement, since I still saw the recovery-resource.dat used to build them in the zip. But I guess FireOS doesn't do that at boot
Click to expand...
Click to collapse
51.1.3.0 was actually the first version to include an updated recovery. If you look in the stock 51.1.3.0 image, you'll see a recovery directory with recovery-from-boot.p and install-recovery.sh. I removed that from my image. The install-recovery.sh is the one that updates the recovery.
I'm not quire sure why it asked you about disabling stock. I'm guessing you booted into it, did nothing, and then rebooted. The only thing I can guess is whatever you had installed already had a /system/etc/install-recovery.sh script there. That doesn't seem to be included in the stock update images. Maybe the stock recovery writes it if it doesn't exist... Either way, I think people have said the install-recovery.sh script that came with stock didn't do anything. And then when you install one of my updates, it definitely doesn't come with it.
Also, I just uploaded 51.1.3.0.
rbox said:
51.1.3.0 was actually the first version to include an updated recovery. If you look in the stock 51.1.3.0 image, you'll see a recovery directory with recovery-from-boot.p and install-recovery.sh. I removed that from my image. The install-recovery.sh is the one that updates the recovery.
I'm not quire sure why it asked you about disabling stock. I'm guessing you booted into it, did nothing, and then rebooted. The only thing I can guess is whatever you had installed already had a /system/etc/install-recovery.sh script there. That doesn't seem to be included in the stock update images. Maybe the stock recovery writes it if it doesn't exist... Either way, I think people have said the install-recovery.sh script that came with stock didn't do anything. And then when you install one of my updates, it definitely doesn't come with it.
Click to expand...
Click to collapse
The contents of my install-recovery.sh had to do with the su daemon. So i assume it was from towelroot. edit: actually probably one of the variations of superuser?
Basically I was curious what changes you were making so the stock recovery wasn't being flashed back, just in case I wanted to mess around with later revisions that aren't rootable and might flash the stock recovery back and leave me w/ an unrootable system. Like 51.1.3.0. But I see that you just created a pre-rooted 51.1.3.0 Anyway, it was more of a curiosity than me wanting to have the latest version.
Upgrading to Pre-Rooted 51.1.3.0_513011520
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
imtiajmeah said:
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
Click to expand...
Click to collapse
As the post says... the prerooted images are only for use with my recovery. So yes, you have to downgrade and install it.
Read Again
imtiajmeah said:
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
Click to expand...
Click to collapse
Regarding these images, the OP states clearly: "These will not work with the stock recovery". You will not be able to update to them without first installing CWM.
rbox said:
As the post says... the prerooted images are only for use with my recovery. So yes, you have to downgrade and install it.
Click to expand...
Click to collapse
For the sake of clarity and semantics, is the "Pre-Rooted Stock Software" the same as "Pre-Rooted Stock Images"? The word Images is throwing off my understanding.
Hi there,
Just one question i didn't find an answere.
Can i use this stock images on German fire TV?
Thx. For a quick reply
Zetup-EXE said:
Hi there,
Just one question i didn't find an answere.
Can i use this stock images on German fire TV?
Thx. For a quick reply
Click to expand...
Click to collapse
I wasn't aware that anyone had gotten the German Fire TV, so... I'll just whip out my crystal ball...
All signs point to it coming with 51.1.3.0, which is unrootable. So... no.
Awesome work rbox!
I´m on pre-rooted 51.1.3.0 by now. As soon as i can i´ll keep donating to you! This is exactly why i bought my FTV!
Thanks!
mjbxx said:
For the sake of clarity and semantics, is the "Pre-Rooted Stock Software" the same as "Pre-Rooted Stock Images"? The word Images is throwing off my understanding.
Click to expand...
Click to collapse
Yes, they are the same.
Stock Image, Stock Software, Stock ROM, Stock OS, and Stock Package all mean the same thing. The only important distinction to remember is that there is a difference between a Recovery image and the rest of the software that runs on the Fire TV.
"Pre-Rooted Stock Images" do not include the recovery image within them, whereas the official 51.1.3.0_user_513011520 update from Amazon does include a recovery image. rbox has stripped out the recovery image from the official update because if he didn't, installing his pre-rooted version would overwrite ClockworkMod recovery.
I assumed this was done, but I wasn't 100% sure so I verified that the updating mechanism has been blocked on these prerooted images.
Code:
[email protected]:/ # pm list packages -d
pm list packages -d
package:com.amazon.dcp
[email protected]:/ #
mastermind278 said:
I assumed this was done, but I wasn't 100% sure so I verified that the updating mechanism has been blocked on these prerooted images.
Code:
[email protected]:/ # pm list packages -d
pm list packages -d
package:com.amazon.dcp
[email protected]:/ #
Click to expand...
Click to collapse
i was just about to ask the same thing, thanks. now im just wondering if i can install cwm from 51.1.0.1 as i've been blocking updates since day one or if i should just update to 51.1.0.2 and then install cwm.
nhumber said:
i was just about to ask the same thing, thanks. now im just wondering if i can install cwm from 51.1.0.1 as i've been blocking updates since day one or if i should just update to 51.1.0.2 and then install cwm.
Click to expand...
Click to collapse
I am wondering the same thing.
Sent from my SCH-I545 using Tapatalk
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Sent from my Nexus 6P using XDA-Developers mobile app
Hmm, seems to be working ok for me on the 7.1.1 DP2 release.
Sent from my Pixel XL using Tapatalk
PearsonDKA said:
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Click to expand...
Click to collapse
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
CaptShaft said:
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
Click to expand...
Click to collapse
You need to flash either Root or a modified boot image for it to stay
jaytv said:
You need to flash either Root or a modified boot image for it to stay
Click to expand...
Click to collapse
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
CaptShaft said:
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
Click to expand...
Click to collapse
Sounds like time for you to do some reading as to what root and boot images are. Search works great. I suggest the threads on SuperSU (a form of root) and also looking at the many wonderful custom boot images and Roms that are floating around in this forum.
The simple answer is flash Super Su or find a modified boot image for the current release and flash that.
Also, Heisenberg's excellent beginner's thread in Nexus 6p general is a great place to start.
Enjoy!
Just what I was looking for.
I was in TWRP loop forever and couldn't figure it out till this thread. No issues now
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
shadowstep said:
TWRP versions 3.0.2-1 and above work with Android Nougat 7.0's encryption, TWRP 3.0.2-0 and below don't. Also, both versions 3.0.2-1 and 3.0.2-2 are buggy at the moment, but none of those bugs are along the lines of encryption. Read the end of this post for more information.
(Replies snipped)
EFS partition is never needed to be restored under any general circumstance. It is the partition where the phone stores its IMEI information, MAC address, product code, etc. and will never be needed to be modified or changed in any way. Even if you're flashing a stock factory image (be it of 6.0.1 or 7.0, whenever it is out), it would never touch this partition. You should just backup it once, store it away for emergency purposes and never backup or restore it again.
Okay now moving onto important notes and the bugs:
1. TWRP 3.0.2-0: Is stable and has no known bugs. However, it has not been updated to handle Android Nougat 7.0's encryption. Hence, if you're on 7.0 and you're encrypted, it will keep asking for an encryption password even if you don't have one or if you have one and are inputting it correctly, it will refuse to accept it. If you're on 7.0 and you're unencrypted, then this version should be fine.
2. TWRP 3.0.2-1: Is not stable and has a known bug. The bug would affect those who are restoring their EFS partition using this version of TWRP. The EFS partition has two subparts to it, i.e. /efs1 and /efs2. So, when you check EFS at the backup option menu in TWRP, it backups /efs1 to efs1.emmc.win and /efs2 to efs2.emmc.win, which is fine. However, while restoring (and here is when the bug comes in), it restores efs1.emmc.win to /efs1 but restores the same backup of efs1.emmc.win to /efs2 as well (which it shouldn't be doing and instead it should be restoring the corresponding efs2emmc.win to /efs2). This can brick your phone. Hence, the fatal bug.
This version, however, supports Android Nougat 7.0's encryption. Therefore, as long as you don't backup/restore EFS with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
3. TWRP 3.0.2-2: Is not stable and has a known bug (with the EFS bug most likely fixed in this version, but this is unconfirmed since there is no changelog available yet). The bug would affect those who are backing up their data using this version. TWRP creates the backups of your selected partitions as tar files. The bug that is present in this version would give you an error (most likely the one that @stankyou got) as it is unable to write the second tar file after processing approximately 1 GB of data and would cancel the backup. Hence, the bug.
This version, however, also supports Android Nougat 7.0's encryption. Therefore, as long as you don't create backups with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
4. @jcadduono has created unofficial builds (versions 3.0.2-3) for the Nexus 6P (Angler) and Nexus 5X (Bullhead) without the broken patches. They are up-to-date, but have the adb backup patches rebased out until the bugs are solved. These builds are untested, and he recommends sticking with 3.0.2-0 instead for the time being.
Click to expand...
Click to collapse
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
vibranze said:
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
Click to expand...
Click to collapse
I had a few failures with it in TWRP, yes.
Until fixed, you'll have to do ADB push instead and then load from TWRP install.
Alternately, you can do fastboot flash commands while in the bootloader.
Grospolina said:
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
Click to expand...
Click to collapse
I noticed that bug yesterday restoring a backup. TWRP appeared to hang whilst restoring, I left it a further five minutes, then hard reset the power button. When the phone loaded up, I found it had restored correctly.
3.0.2-4 twrp ?
Anybody have the capabilities to roll the 3.0.2-3 version in with The Flash's 3.0.2-0_F2FS version lol; and make a version compatible with Nougat encryption as well as F2FS (and without EMS restore problem, nor backup error issue) ?
I know I sure don't, and now that I'm on christmas break I am just sitting around - in fact if anybody could point me to a resource, I have the time and I'm sure I could pick it up quick, I could try and compile it! I've been wanting to give back to this great community since I joined; maybe now that I've done a couple years of engineering school and been searching thru the forums, I can help throw this together.
I'm going to assume that I look up those two builds sources on GitHub, then use Parallels Windows to use a Linux distro (because I'm on a Macbook Pro) to combine the sources and make a build? Honestly, if I could get any advice, I'd love to jump on it.
3.0.3.0 is out. Anyone know the changelog ?
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
ariefabuzaky said:
3.0.3.0 is out. Anyone know the changelog ?
Click to expand...
Click to collapse
Unfortunately, the answer is here. I did not expect to see a nag screen after making a backup!
bkkzak said:
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
Click to expand...
Click to collapse
You can always look at their repository
Since 2016-09-01:
- Change version to 3.0.3 to support the app release - 27 hours ago
- Update Ukraine language translation (via jemmini) - 27 hours ago
- Add TWRP app install via TWRP recovery - 29 hours ago
- TWRP Language Update - 7 days ago
- Change handling of /cache due to AB devices not having cache - 7 days ago
- Support backup/restore of FBE policies - 8 days ago
- Support File Based Encryption - 10 days ago
- Add boot slot support - 12 days ago
- Support new AB OTA zips - 12 days ago
- Copy Kernel Logs - 5 months ago
- Improve backup & wipe exclusion handling - 2 weeks ago
- Fix adb shell in 7.0 tree - 6 weeks ago
- Check if mount point is dir during startup - 6 weeks ago
- MD5 verification sanity - 8 weeks ago
- Fix image flashing: attempt 2 - 8 weeks ago
- Fix image flashing - 3 months ago
- Update to android-7.1 - 4 weeks ago
- Fix libcrypto dependency in 6.0 trees - 3 months ago
- Clean up PartitionSettings - 3 months ago
- Fix compressed backups with split archives - 3 months ago
- Fix restore of subpartitions - 4 months ago
Unfortunately for me, I still have issues decrypting an encrypted phone on TWRP 3.0.2-3 and 3.0.3-0. TWRP prompts for a password and won't take my PIN.
Running the latest ResurrectionRemix (CM-based), which enables device encryption. I'm still searching around to see what I need to do about this.
Edit: Update: Huh, weird, got it to mount.
I rebooted back into Android, went in to Security and set a device encryption password with "Change encryption password".
I hadn't set one before. It requests my screen lock PIN then to enter an alphanumeric encryption password.
Attempted to remove it again immediately (it doesn't show any feedback when I tap "Replace encryption password" then enter my screen lock PIN), and rebooted into recovery.
TWRP prompted again for an encryption password but now accepts my device lock PIN and it mounts!
Rebooted again, and now the phone requests a PIN unlock during boot >.<
Went back in to Security and went straight to "Replace encryption password", entered my PIN, and saw no feedback again. Rebooted back into Recovery.
TWRP prompts again but accepts my PIN. Rebooting to Android again, I am prompted again on boot to enter my screen PIN to finish the boot process. Sooo now I guess I have to figure out how to disable the device encryption PIN, or something. Oh well. I'll update if I make progress.
The end goal is to reach a point where TWRP will mount (even if it's manually with an entered PIN), and to not have a phone that requires a PIN unlock during boot. But I guess that's still safer and I can live with it. It's just different from how the ROM originally behaved, is all.
Edit: Update again!
Disabled my PIN/security altogether, rebooted into recovery. TWRP mounts without any prompts. Nice. Reboot int system, it boots fine. Also nice.
Set a new screen lock PIN, do not select to use it on bootup, and set my fingerprints again. Apps work immediately fine after, I did not have to reset them to use that auth method. Woot, nice.
Restart into TWRP, no prompt, good. Restart into System again, no prompt during boot.
So I guess in the end you have to disable and re-enable device screen locking security if you hit this issue in TWRP on a 6P? It could be my ROM as well.
CaptShaft said:
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Click to expand...
Click to collapse
tu 2: is that recovery image the same as under point one? and where is the ADB /fastbootfolder? these not exist
Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 6P
osm0sis said:
Guys.. bad news.. my Nexus 5X just got hit with the BLOD.
Good news for everyone is I spent a bit of time tonight to first patch TWRP 3.2.1-0-FBE (File-Based Encryption support) image to be 4core, then made an AnyKernel2 zip which will patch the existing boot and recovery partitions on-device to add all the 4core fixes from @XCnathan32.
Should work over any ROM, any custom kernel, recovery, etc., can be added in queue after ROM, root zip + custom kernel to patch it from TWRP or FlashFire (so good for OTAs), and simplifies the initial process greatly since you can now fastboot boot any 4core recovery.img and then adb sideload my AK3 zip to fix the likely newer recovery you already had on your device.
Click to expand...
Click to collapse
Original thread posts: Nexus 5X, Nexus 6P
Now updated to an AnyKernel3 zip to support the SAR (system-as-root) and 2SI (2 stage init) ROMs that have popped up for Pie and Android 10+!
General Information
If you've found this thread then I'm sure you probably already know what the Bootloop of Death is - separation of the performance (perf) CPU cores - and that the only way to recover from it is to unlock your bootloader and patch to disable the faulty cluster. If you have not enabled unlocking your bootloader yet, the known methods to get it to boot long enough so you can go to System, then Developer Options and toggle "OEM unlocking" are:
super cooling the device in a freezer in a ziplock bag to keep out moisture,
super heating around the camera, and
letting the battery run all the way down before trying to boot.
For further details on these methods check out the original threads by @XCnathan32, linked in the "Thanks" section.
Some important notes before going any further:
Freezing at the Google logo likely points to it being perf cluster separation, but this could also be caused by other components separating.
Freezing at the boot animation suggests ROM/ROM data problem or could also potentially be a BLOD with other components now beginning to separate and that's what people have reported when the 4core mods suddenly stop working with no configuration changes - if you've tried the default boot.img for your ROM, patched with the BLOD AK3 and it still doesn't work, sorry but your device is a brick.
If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick.
I haven't seen anyone say their devices only worked using a "1core" modification who had tried a proper 4core patched setup; 4core makes sense because it's the separate perf cores cluster becoming unsoldered, but if the 4 low power cores cluster also starts to come unsoldered logically not even a single core would work.. I think that's where the "Green Screen Of Death" comes into it.
DemiGod = Green Screen Of Death; unfortunately this (more components separating given more time - maybe the flash memory chip?) is why many call the 4core workaround only temporary.. there's not much that can be done after that from what I've read.
EX Kernel does not support FBE on these devices because the EX zip patches the fstab forcefdeorfbe flag to encryptable.
Android 10 does not appear to support FBE on these devices but the 4core FBE TWRP build can be used to BLOD patch the latest TWRP (see instructions in next post).
On Oreo, I was personally on stock ROM still, FBE enabled, rooted with SuperSU v2.82 SR5 + suhide and the latest Franco Kernel on my 5X. Then I bumped up the min freq on the low perf cores and it's working great - totally fine for general use, just anything creating a bit of heat like games maxing the low power cores for awhile, or charging, will make it pretty painfully laggy and risk further solder deterioration.
Even though SuperSU development is ostensibly dead, I still strongly recommend it on BLOD-affected devices using stock ROM for reasons I'll explain below.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Step-By-Step Installation Instructions
Any quoted commands should be entered without quotes
1) Download and unzip platform-tools for your PC from https://developer.android.com/studio/releases/platform-tools.html
2) Navigate to https://androidfilehost.com/?w=files&flid=312881 (also mirrored below) and download N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip to your platform-tools folder as well as
2a) twrp-3.2.1-0-fbe-4core-bullhead.img (Nexus 5X), or2b) twrp-3.2.1-0-fbe-4core-angler.img (Nexus 6P)3) Hold Shift + right-click on your platform-tools folder and
3a) Open a command window here (Windows <10), or3b) Open a PowerShell window here, then enter "cmd" at the Windows PowerShell prompt (Windows 10+)4) Reboot your phone to bootloader and connect it to your PC with a USB cable
5) Enter "fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img" into the cmd prompt
6) Reboot your phone to recovery and tap Advanced, then ADB Sideload
7) Enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip" into the cmd prompt
8) Reboot and cross your fingers that it works
For information how to seamlessly update to stock and custom ROM OTAs, see the following post
Source Code: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
Status: No Longer Updated
Thanks:
- @XCnathan32 for researching and developing the 4core workarounds for both the Nexus 5X and Nexus 6P
- chetgurevitch (GitHub) for the original FBE supporting TWRP builds
- @Aukaminator for the original step-by-step write-up
Update Flashing Instructions
Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
The correct manual order for a clean flash is: ROM -> root -> custom kernel -> BLOD AK3
Always flash the BLOD AK3 zip last!
Reflashing the BLOD AK3 zip will likely be required after anything that could modify the boot.img or recovery.img, including (but not limited to): ROM updates, custom kernel updates, custom recovery updates.
ROMs:
On custom ROMs with built-in Flash After Update (i.e. OmniROM-based), place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/OpenDelta/FlashAfterUpdate/ ensuring the BLOD AK3 is last in the directory listing so that they will be flashed after each update.
On custom ROMs that do not have built-in Flash After Update (i.e. LineageOS-based), you may add my FlashAfterUpdate addon.d script to /system/addon.d/ and then place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/FlashAfterUpdate/ ensuring the BLOD AK3 is last for the same effect: flashed after every OTA.
On stock ROM rooted with SuperSU (SuperSU v2.82-SR5 recommended) instead of tapping "Reboot & Install" once the OTA is downloaded you should use @Chainfire's excellent FlashFire app to queue the OTA from /data/ota_package/update_s.zip then queue the SuperSU zip, custom kernel and BLOD AK3 zip, ensuring the BLOD AK3 is last. This is how I have mine set up, since this is by far the most seamless. Be sure to disable EverRoot since SuperSU v2.82-SR5 is newer than the SuperSU included in FlashFire.
On stock ROM rooted with Magisk you must uninstall Magisk from within Magisk Manager to restore your stock boot.img, reboot the ROM to restore your stock recovery partition, tap "Reboot & Install" once the OTA is downloaded, then go through the steps above to flash the 4core TWRP and BLOD AK3 zip again. I definitely recommend SuperSU on this device to avoid the hassle of unrooting and/or messing with factory images.
Kernels:
Custom kernels can be flashed from an app like Franco Kernel Manager & Updater, which can be set to flash without reboot for Franco Kernel updates, or "Flash only" can be chosen in the manual flasher. The FK app supports all types of AnyKernel3 zip so the BLOD AK3 zip may then be flashed after the custom kernel zip to repatch the new kernel's ramdisk.
For other kernel managers that don't support AK3 zips, simply reboot to recovery and flash the BLOD AK3 zip from there to repatch before attempting to boot the ROM again. Also see above under "stock ROM rooted with SuperSU", since FlashFire also works perfectly for this use-case, queuing the custom kernel zip and then the BLOD AK3 zip, with FlashFire's EverRoot option disabled since the device is already rooted.
Recoveries:
Download the updated custom recovery .img and, without flashing it, reboot to recovery, use TWRP's flash image feature to flash the new recovery.img, then without rebooting immediately flash the BLOD AK3 zip to patch it. You can then dump/backup the recovery partition if you want it as a recovery.img. Custom recovery updates can also be done from FlashFire, queuing the BLOD AK3 zip afterward, but the "Preserve recovery" feature must be disabled.
If you prefer to stay on stock recovery for some reason, you can still use TWRP to do the above without flashing TWRP to the device by using "fastboot boot twrp-3.2.1-0-fbe-4core-angler.img".
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Changelog
2018-01-15 - Original post in other BLOD threads.
2018-07-21 - Update AK2 Core+Backend files to latest, add searching of all init.*.rc files for problematic cpuset commands which were popularized by Franco Kernel and are now used by multiple custom kernels. (6758 downloads)
2019-10-30 - Update to AnyKernel3, add support for SAR and 2SI Treblized ROMs. (1720 downloads)
2020-01-16 - Update AK3 Core+Backend files to latest to fix AVBv1 signing in recovery on Android 10, update boot_signer-dexed.jar. (570 downloads)
2020-02-17 - Update AK3 Core+Backend files to latest to fix SAR mount support in fragmented TWRP and Lineage 16+17 Recovery. (1412 downloads)
2020-05-25 - Update AK3 Core+Backend files to latest to improve SAR mount support in Lineage 17 Recovery and AVBv1 signing. (1789 downloads)
2021-07-21 - Update AK3 Core+Backend files to latest to support Lineage 18.1 recovery and Android 11 ROMs.
Good luck and enjoy!
Glad to see this exclusive thread... just came here to report that I've been using your fix since Jan this year ( https://forum.xda-developers.com/ne...-6p-bootloop-death-blod-t3640279/post75220708 ) and yeah my phone's still alive and running fine. Kudos to your work... Great job you did there... saving hundreds of bucks... Really appreciated!
Thanks again.
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
SH15 said:
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
Click to expand...
Click to collapse
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
osm0sis said:
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
Click to expand...
Click to collapse
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
SH15 said:
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
Click to expand...
Click to collapse
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
FlameSting said:
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
Click to expand...
Click to collapse
Please read the OP. It works over any ROM, any custom kernel, any recovery.
osm0sis said:
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Click to expand...
Click to collapse
Thank you very much! I flashed the newest factory image for Oreo and then re-flashed the BLOD AK2 zip and it worked. Thank you for your help! :good:
Idk if I'm in the right place.
I recently replaced my battery (2nd time this week, first one was bad) and everything was working fine. Then my phone started randomly rebooting. Googled it and apparently it's one of the first signs of BLOD. Followed this and the phone stopped shutting down randomly. Now the phone only works if plugged into a power source. Idk if I did something wrong or the battery is trash (even though it was working fine all day)
I'd appreciate an guidance [emoji24]
Sent from my [device_name] using XDA-Developers Legacy app
This saved my day! Thanks everyone! Got my 6P booted up again... and it's not even rooted
I want just only to thanks @osm0sis and it's genial solution!
Thanlks i recover my phone and saved a lot of money.
I understand it could be a temporary solution but thanks!!!
gabriele
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
godd said:
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
Click to expand...
Click to collapse
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
I had my phone hang on the google logo a couple times, but rebooting it fixed it. Is this an early sign of this problem? Just replaced battery and so far it seems fine.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
I am in this same boat... RIP N6P, this is my 2nd N6P Google replaced the first one due to the BLOD and now the replacement is dead.
Thanks for all the efforts and help.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
Same as the guy above. Sites down need mirrors or something?
jbjcurly said:
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
Click to expand...
Click to collapse
CavyS said:
Same as the guy above. Sites down need mirrors or something?
Click to expand...
Click to collapse
Mirrored in the OP. Thanks!
Edit: And BasketBuild is also back! :good:
Hi all.
I updated to the latest version last night, but I lost my root in the process.
I tired to re-root my GP6 yet unsuccessful. Anybody manage to do it?
Thanks.
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Jaitsu said:
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Click to expand...
Click to collapse
Have the same Problem, no root on latest Beta,
although following the above steps ( used them in the pasta for wach beta)
Anyone with root on newest Beta?
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Jaitsu said:
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Click to expand...
Click to collapse
Yes, same thing happened to me this morning after doing the common steps to retain root after applying an OTA. I then proceeded to patch the boot image using adb but stil no root access.
Edit. It appears that no one is able to root on T2B1, as someone said in the official guide rooting pixel 6 here on XDA
Same issue, tried with PixelFlasher, manual commands, diffrent Magisk versions, but still can't get it work
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Jaitsu said:
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Click to expand...
Click to collapse
I've already posted on Reddit r\Magisk [Help] Flashed magisk pathed pathed boot image T2B1.221118.006 don't works, but maybe submitting bug would be better. Yea, TWRP would be best but still nothing for A13 (and A12 I think). I remember that there was similar issue in older updates, but Canary made it work, but... not this time
Tried all the possible ways to root the phone, either using fastboot or Pixel Flasher, but no avail. Perhaps someone could successfully do it and tell all of us how
Same issue in Pixel 6a
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
BAlex9601 said:
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
Click to expand...
Click to collapse
Yea, everything else stays the same. Just after upgrade, instead of patching Pixel 6 boot.img, patch the one from Pixel 7 and flash it.
I've used Pixel Flasher for factory update and then in Magisk app I've patched image and then flashed it with fastboot flash boot <patched_boot.img>.
https://twitter.com/i/web/status/1602774339224367104
Yup broken.. should have read the thread.
m_pastuszek said:
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
Click to expand...
Click to collapse
Is this true? I'm downloading it now to test it. Will update later.
UPDATE:
Apparently, flashing Pixel 7 boot.img into Pixel 6 worked like a charm. I get the root back. Thanks guy!
Thanks for the hint regarding boot.img
I'm facing aslo this issue while updating
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.2-9152140'.
Update requires 'slider-1.2-9228550'.
Actually I'm on T1B3.221003.008
Any idea? -> flashed bootloader manually -> solved