Database Develop

[01/06/11] ClockworkMod Recovery 3.2.0.0

ClockworkMod Recovery 3.2.0.0
Note:
Amend scripting (update-script) is no longer supported, was deprecated by Google in Android 1.5. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Current version: 3.2.0.0-(01.06)
Recovery_Optimus_2x_3.2.0.0-(01.06).zip
MD5: 1e97b2c8a0d4b84e11ec2f31e51f83ca
SHA-1: 2f7cd8cdf8e239886e31497dcffc9e5026606155
Installation:
Unzip the archive
Plug-in the USB cable and select enable the "debug mode"
Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
Done!
If you want to thank me, click the Thanks button.
Old versions:
Recovery_Optimus_2x_3.2.0.0.zip
Changelog: http://goo.gl/MAuLi (2011-05-30)
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!

All Ok with this version!! no /cache umount

Perfect ....
As always one step ahead....

When entering Recovery menu, device vibrates all time long. =/

Good to see you here. Gonna try tomorrow!
Sent from my LG-P990 using XDA App

Just installed. This version is perfect. Thanks.

how come i cant find it in rom manager?

Sorry for a noob question, but with previus version I cannot install CM7 #31.
Can I install this rom now?

ranrick said:
When entering Recovery menu, device vibrates all time long. =/
Click to expand...
Click to collapse
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!

initrd said:
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
Click to expand...
Click to collapse
Yeah, 3.0.2.8 didnt work either. Only 3.0.1.4 works without vibrations.

Works like a charm.
Anyway to add this aswell: http://forum.xda-developers.com/showthread.php?t=1098745
So you have 2 option.
Internal Sd and External Sd?
That would be awesome!

USB mount doesn't work. Is it me?

Recovery shows 3.2.0.0 but the app still reports it as 3.0.2.8 - is this for compatibility?

recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)

75markus said:
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
Click to expand...
Click to collapse
yep. same thing (like at 3.1.0.1)...

just made a nandroid restore and recovery can't mount /boot during restore.
It's probably why we can't ( for exemple ) flash a CM rom ( after nandroid stock rom ) play with it and if you want to return to stock rom using your backup you get a bootloop

Quite common (and annoying), that. Happens each time I've restored a CM NANDroid, have to restore, then reflash CM.

hi. just a noob question
can i use this recovery to flash all the roms for the optimus 2x. like modaco, cm7 and other modaco based custom roms. ?
i been reading the forums and there are so many recoveries. im kinda confused.

Yes you can.
There are only 2 types of recovery in reality, this type (external SD) and the one I built for internal SD use. If you're not sure what you need, pick the external one (unless you don't have an SD card).

bit of a noob..but cant seem to be able to install it. can someone give me a guide to install this with a mac thanks in advance

[RECOVERY][UNOFFICIAL] TWRP 2.8.1.0 for S4 Mini / I9195

Hello
This is TWRP v 2.8.1.0 for the S4 Mini. It works for the I9195 - I do not know if it works for similar devices.
The problem was that TWRP after version 2.7.1.0 did not boot up - the phone tried to enter recovery mode but eventually booted into android.
This is because of commit https://gerrit.omnirom.org/#/c/8471/ which does not seem to work nice with the S4 Mini.
DISCLAIMER : You apply this recovery at your own risk - if something breaks or bricks I am not responsible
IMPORTANT NOTE :
a) The attached file is NOT a flashable ZIP and I will not provide one. You have to unpack the attached file and use heimdall or dd. If someone wants to provide a flashable zip - I am fine with that.
b) There is no F2FS support.
c) I do not know if there are still problems with the recovery sometimes not booting up - I tried it a couple of times and it worked every time. Tell us if you experience booting problems.
d) I am no coder - so I cannot help with things like encryption, luks or similar wishes.
How to install:
a) Boot your phone to download mode
b) Connect phone to PC
c) Get root on your PC
d) Unzip attached ZIP file
e) Check md5sum
f) heimdall flash --RECOVERY recovery.img --no-reboot (dd should work as well - take care of the right partition)
Thanks goes to:
Teamwin
OliverG96
_that
Additional information:
If you want to build this by yourself from sources open file twrp-functions.cpp and search for line:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
You can change it like that:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
{
return 0;
std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;
This should fix the problem. According to one of the developers there should also be a flag for specifying a brightness file that one can probably set to /nobrightness.

It works great on my I9195 !
From your recovery, i created the Odin version and flashed it.
Thank you very much.
I attach the Odin version of your recovery (Instructions: unzip the .zip file, and flash the .tar.md5 file with Odin 3.09 into AP field)

Recovery flashable ZIP version of TWRP 2.8.1.0 attached.

Mounting both (Internal and External) doesnt work

mike_san said:
Mounting both (Internal and External) doesnt work
Click to expand...
Click to collapse
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.

thomson.aa said:
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
Click to expand...
Click to collapse
I confirm this.
I tried to mount and unmount System, Data and micro Sdcard... all ok.

Will it work with f4k kernel ?

lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.

Works great so far, noticed only one (minor) issue:
I need to use encryption for my phone and for its backups as well (I'm a sysadmin and my phone is fully equipped to access my datacenter). When using keyboard to type encryption/decryption passwords, somethimes I hit one key and completely another key gets pressed, can't be due to fat fingers because wrong key that gets pressed is usually very far from the original one. This was very iritating sometimes since I needed to type passwords for 3-4 times in a row for them to work. Figured out how to prevent this, I look at whole keyboard carefully on every keystroke and I'm usually able to see when it gets buggy and hits wrong key (keystroke animation is trigerred), but this isn't very fast or comfortable...
I think I had the same problem with early versions of TWRP 2.7 posted here but it has been resolved in newer ones. Otherwise, works as a charm, if someone added full F2FS support it would be totally perfect
PS If my memory serves me well, fix was build.prop related.

ericlnu said:
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Click to expand...
Click to collapse
works fine on aicp, Thanks

s.basketbuild.com/devs/F4k/twrp/serranoltexx
this one have F2FS

Install Help - [ROM] Evervolv | 6.0.0p1 [AOSP Marshmallow 6.0.1]

Hello,
I'm trying to install the new Marshmallow on my hp touchpad but running into below issue:
I've tried several combination of gapss, rom using Touchpad Toolbox v42 but keep geeting error (Incompatible GAPPS/ROM versions None/6.0)
Here's what I'm trying:
Recovery
2.8.3.0 TWRP recovery with MTP support.
ROM
ev_tenderloin-6.0.1-testing-2016.01.04
ev_tenderloin-6.0.1-nightly-2016.01.03
GAPPS
open_gapps-arm-6.0-nano-20160106
BaNkS-Dynamic-GApps-6.x.x-10-20-15
I also tried installing without gapp, but TPToolBox gives error saying Gapps file is missing (or found 0 gapp file).
Let me know if there is a combo of known files that works. - Thanks

tejtank said:
Hello,
I'm trying to install the new Marshmallow on my hp touchpad but running into below issue:
I've tried several combination of gapss, rom using Touchpad Toolbox v42 but keep geeting error (Incompatible GAPPS/ROM versions None/6.0)
Here's what I'm trying:
Recovery
2.8.3.0 TWRP recovery with MTP support.
ROM
ev_tenderloin-6.0.1-testing-2016.01.04
ev_tenderloin-6.0.1-nightly-2016.01.03
GAPPS
open_gapps-arm-6.0-nano-20160106
BaNkS-Dynamic-GApps-6.x.x-10-20-15
I also tried installing without gapp, but TPToolBox gives error saying Gapps file is missing (or found 0 gapp file).
Let me know if there is a combo of known files that works. - Thanks
Click to expand...
Click to collapse
Try using the gapps-601-base package from here:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
and one of the recoveries listed under "Compatible DataMedia (DM) recoveries" from the TPToolbox thread here:
http://forum.xda-developers.com/showpost.php?p=52765140&postcount=3

jcsullins said:
Try using the gapps-601-base package from here:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
and one of the recoveries listed under "Compatible DataMedia (DM) recoveries" from the TPToolbox thread here:
http://forum.xda-developers.com/showpost.php?p=52765140&postcount=3
Click to expand...
Click to collapse
Wow - Thank you!
That worked.
For anyone else in same situation, following worked for me:
ROM:
ev_tenderloin-6.0.1-nightly-2016.01.03
Recovery:
update-TWRP-jcs-dm-tenderloin-20140612b
GAPPS:
gapps-601-base-20160105-1-signed
Thanks again jcsullins

Same issue not resolved
Hello;
I am using TPToolbox-2015-01-08-v42 to try to install the following.
ROM:
ev_tenderloin-6.0.1-nightly-2016.01.17
Recovery:
update-TWRP-jcs-dm-tenderloin-20140612b
GAPPS:
gapps-601-base-20160105-1-signed
I keep getting an error that says that gapps-601-base-20160105-1-signed appears to be corrupt and the installation aborts. I have tried several times to re-download this file, I ave tried several times to wipe the data and start fully clean but still it shows the GAPPS file as corrupt. Any ideas?
Thanks

looks like the only difference from what I used is the ROM version.
I guess you can try the same Rom that I did and then later update to another nightly.
Others may have better ideas.

[RECOVERY] [NEW: CWM Graphics] CTR Recovery for Galaxy A5

CTR Recovery for Galaxy A5​
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.

Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.

Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work

oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support

you welcome brother

DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse

DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro

Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.

@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...

corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now

DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..

corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port

DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?

corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think

I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery

Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz

What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far

akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal

DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.

akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands

[Solved!] I want to update TWRP, but ...

Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format. Since the tablet is not rooted, I can't flash the newer version using Flashify or similar apps (as far as I can tell, that is) since they all require root access. And I can't flash an IMG file with v2.7.1.0, since that feature wasn't included until a later version (v2.8.5.0 I think). Therein lies the problem. I need a newer version to update, but I can't update until I have a newer version!
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
Thanks for your help ... and for not laughing at my possibly nutty idea

MaydayMalone said:
Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format.
Click to expand...
Click to collapse
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
...
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
...
Click to expand...
Click to collapse
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.

digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Thanks for your response. You told me exactly what I needed to know.
I have viewed D. Andrei Măceș dropbox in the past, but I neglected to check it for TWRP updates (my bad). I'll keep this in mind the next time I want to explore new possibilities for my HD+.
The idea of creating my own zip was a temptation that I couldn't resist (since I was now feeling confident that I wouldn't brick my tablet, blow up Pittsburgh, or be responsible for something equally catastrophic). So, instead of downloading a zip file from the dropbox, I used Linux Archive Manager (I switched to Linux Mint some time ago to escape the more-frequent-than-I-could-bear crashes with Windows), to delete the file named recovery.img in the v2.7.1.0 zip, then inserted a recovery.img file for TWRP v3.1.1.0 in it's place. It worked perfectly, and I feel like a genius (I'm very easily impressed)!
Thanks for letting me know that my idea wasn't as dumb as I feared it might be.

digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
I keep trying to install the zips from CWM Recovery but I cannot do it.
Is there any way for me to install TWRP from CWM?
Thank you

pnkye said:
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
Click to expand...
Click to collapse
Did you use one of the flashable TWRP zip files from https://www.mediafire.com/#6a4rivb8kkdfu?
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
Click to expand...
Click to collapse
Did you tried holding down the power button for 30+ sec?

Thank you for the answer.
1. The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
2. I tried all the options I could find online. If I let it be for 1 week (I use it for reading and sometimes youtube) it turns itself on at some point and the battery goes empty. And it is so hard to turn it on again. When I plug it for charging the battery and is completely empty, the led stays green - instead of orange - for a long time and is not responsive to anything I do until it reaches 80%+ , so I let it be for 2hrs while plugged.
3. What I try to do is actually root it for overclocking or make it a little bit faster because it lags in every thing I do with it. Although in some variants of the Android which I installed over the years it used to be more responsive.
Unfortunately I cannot root it because CWM doesn't recognize the install of SuperSU zip from Lineage website. Do you have any advice on that?
Thanks

pnkye said:
...
The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
Click to expand...
Click to collapse
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+

digixmax said:
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
Click to expand...
Click to collapse
Thank you very much! You really helped me with this one!
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Anyway my booting time is faster and so far (1min time) the turning on/off procedure works normal, as it should be.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Is there a proper way to root it? If so could you please share a solution when you have time?
Also any ideas on how to properly overclock (make the tablet a little snappier, besides the animation scale option from dev options)?
Cheers!

pnkye said:
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Click to expand...
Click to collapse
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
Click to expand...
Click to collapse
You should be able to disable auto-rotation in Settings->Display.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Click to expand...
Click to collapse
Try disabling and exit Settings->Developer Options, then come back and re-enable it.

digixmax said:
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
You should be able to disable auto-rotation in Settings->Display.
Click to expand...
Click to collapse
My device is with default landscape. If I disable it it stays in landscape and never goes to portrait.
digixmax said:
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
Click to expand...
Click to collapse
It still doesn't work.
Thanks for the overall guidance!