Database Develop

[Q] replace TWRP by CWM

hi guys after having issu with TWRP ( after a flash via goo manager impossible to boot on it and it always boot on twrp after each restart...), i am wondering how can i replace it by cmw recovery again.
thanks

thi3um said:
hi guys after having issu with TWRP ( after a flash via goo manager impossible to boot on it and it always boot on twrp after each restart...), i am wondering how can i replace it by cmw recovery again.
thanks
Click to expand...
Click to collapse
What did you flash?

What I flash is not the problem
update cm9 aokp webos style to final buid =ok, but fc with Google play so clear data app but still have fc, so I decide to flash gapps again via goo manager but when I select flash rom goo manager tell me that I don't have a recovery script...
so I update twrp via goo manager =ok and finally I select my gapps zip with wipe cache and dalvik, it reboot and stuck in moboot loading twrp img. And then impossible to boot nothing, after many reboot, restart, pushing all the button it finally boot.
Now it work normally except if I boot on twrp.
Voilà
I want to go back to cwm, that's all.

thi3um said:
What I flash is not the problem
update cm9 aokp webos style to final buid =ok, but fc with Google play so clear data app but still have fc, so I decide to flash gapps again via goo manager but when I select flash rom goo manager tell me that I don't have a recovery script...
so I update twrp via goo manager =ok and finally I select my gapps zip with wipe cache and dalvik, it reboot and stuck in moboot loading twrp img. And then impossible to boot nothing, after many reboot, restart, pushing all the button it finally boot.
Now it work normally except if I boot on twrp.
Voilà
I want to go back to cwm, that's all.
Click to expand...
Click to collapse
DL CWM here http://goo.im/devs/jcsullins/cmtouchpad/testing/uImage.CWM6_tenderloin_20121204 . Then with an app like Rom toolbox lite copy and paste it into your boot folder , then delete the TWRP ulimage and edit your default recovery , and you should be good to go.

sstar said:
DL CWM here http://goo.im/devs/jcsullins/cmtouchpad/testing/uImage.CWM6_tenderloin_20121204 . Then with an app like Rom toolbox lite copy and paste it into your boot folder , then delete the TWRP ulimage and edit your default recovery , and you should be good to go.
Click to expand...
Click to collapse
ok, thanks buddy
what do you mean by edit your defaut recovery, i guess it's a text file to mod.

Yes below are 2 screenshots 1 with ES File explorer and the other with Rom Toolbox when you tap to open select open as Text and edit/change with RB text editor this is assuming you have Rom Toolbox lite or another text editor with root privileges.
Hope this helps.
Sent from my cm_tenderloin using Tapatalk 2

Yep found it with root explorer.

Ulmage
sstar said:
Yes below are 2 screenshots 1 with ES File explorer and the other with Rom Toolbox when you tap to open select open as Text and edit/change with RB text editor this is assuming you have Rom Toolbox lite or another text editor with root privileges.
Hope this helps.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When I went to boot drive I saw several ulmage files. Am I to delete all and replace with the one posted in this thread? Is this how I will delete TWRP?

horaceb said:
When I went to boot drive I saw several ulmage files. Am I to delete all and replace with the one posted in this thread? Is this how I will delete TWRP?
Click to expand...
Click to collapse
NO just delete the TWRP ulimage AFTER you have successfully copied/ placed your CWM their . Then edit the Android. default. recovery file .
I hope this makes it clearer.
If you have any other questions post or PM me.
Good luck.
The images shown are after I deleted TWRP and copied CWM

thi3um said:
hi guys after having issu with TWRP ( after a flash via goo manager impossible to boot on it and it always boot on twrp after each restart...), i am wondering how can i replace it by cmw recovery again.
thanks
Click to expand...
Click to collapse
funny , I have the exact same problem since yesterday and I cant get rid of TWRP in the boot menu even after using acmeuninstaller + webOS doctor.
Advice to everyone, do not install TWRP twice on this device. Goo manager is too lame to see its already there and for some reason, it messes up the boot manager.

[Q] Installing multiple recoveries

Installed CWM 6.03.6-datamedia recovery to install CM11 (Milaq) 12/24 CM11 ROM build. And then did a nandroid backup and backed up apps and system data with TiBU.
Now I wish to install several other new Kit Kat experimental ROMs (Evervolv and invisiblek) to test how the updated Kernel upgrades are coming along.
To prepare for the Evervolv ROM I installed open-recovery TWRP 2.6.3.0 (Sep12-2013). Was very easy to install TWRP by renaming as uImage.TWRP and copying to /boot. (thanks for the info from nevertells)
But not sure how to install Invisiblek CWM update which supports SE Linux as required by invisiblek ROM.
cwm_selinux_6.0.5.4_datamedia.uImage
I renamed the new recovery as "uImage.cwm_selinux_6.0.5.4_dm" and moved to /boot. And indeed it appears in the moboot menu. But when I select it I observe the following error:
Loading '/boot/uImage.cwm_selinux_6.0.5.4_dm' ... OK
Checking uImage... Invalid Size
I've re-downloaded and re-installed twice and the issue repeats itself.
I do not wish to destroy my existing CWM 6.0.3.6 (non selinux) recovery install.
So is it possible to install the newer CWM recovery so both CWM recovery tools can coexist and be accessible via the moboot menu at the same time?

woodytrain said:
Installed CWM 6.03.6-datamedia recovery to install CM11 (Milaq) 12/24 CM11 ROM build. And then did a nandroid backup and backed up apps and system data with TiBU.
Now I wish to install several other new Kit Kat experimental ROMs (Evervolv and invisiblek) to test how the updated Kernel upgrades are coming along.
To prepare for the Evervolv ROM I installed open-recovery TWRP 2.6.3.0 (Sep12-2013). Was very easy to install TWRP by renaming as uImage.TWRP and copying to /boot. (thanks for the info from nevertells)
But not sure how to install Invisiblek CWM update which supports SE Linux as required by invisiblek ROM.
cwm_selinux_6.0.5.4_datamedia.uImage
I renamed the new recovery as "uImage.cwm_selinux_6.0.5.4_dm" and moved to /boot. And indeed it appears in the moboot menu. But when I select it I observe the following error:
Loading '/boot/uImage.cwm_selinux_6.0.5.4_dm' ... OK
Checking uImage... Invalid Size
I've re-downloaded and re-installed twice and the issue repeats itself.
I do not wish to destroy my existing CWM 6.0.3.6 (non selinux) recovery install.
So is it possible to install the newer CWM recovery so both CWM recovery tools can coexist and be accessible via the moboot menu at the same time?
Click to expand...
Click to collapse
Your /boot partition does not have enough space for cwm_selinux_6.0.5.4_datamedia.ulmage, and you will need to clean up your /boot partition to make room for it.

goog888 said:
Your /boot partition does not have enough space for cwm_selinux_6.0.5.4_datamedia.ulmage, and you will need to clean up your /boot partition to make room for it.
Click to expand...
Click to collapse
I tried "cwm_selinux_6.0.5.4_datamedia.uImage", but it does not work with uImage.CyanogenMod. It caused this error "Checking uImage. Invalid Size", and I had to restore the backup to fix the issue.
However, I found out that Flemmard's "openrecovery-twrp-2.6.3.0-tenderloin-selinux.zip" can work very well with Invisblek's "cm-11-20131227-UNOFFICIAL-tenderloin.zip".
1. You should be able to flash Invisbleh's ROM over Milag's build to get 3.4 kernel.
2. The known black box issue has been fixed.
3. Playing video on YouTube could cause system reboot occasionally.

I have decided to go back to 10.2.
I am waiting for a cm11 release which includes a more stable 3.4 kernel.

Actually "cwm_selinux_6.0.5.4_datamedia.uImage" is functional, after I cleaned up my /boot folder.
And because it supports datamedia, it can restore my cm10.2 backup without any issue.

goog888 said:
Actually "cwm_selinux_6.0.5.4_datamedia.uImage" is functional, after I cleaned up my /boot folder.
And because it supports datamedia, it can restore my cm10.2 backup without any issue.
Click to expand...
Click to collapse
How did u clean it up?

Moody66 said:
How did u clean it up?
Click to expand...
Click to collapse
My /boot folder didn't have enough space for two different CWM.
You will need to download the free application "Rom Toolbox Lite" from the Store.
First I backed up and removed the original uImage.ClockworkMod (rev 6.0.3.6) from the /boot folder to save 5.8MB.
Then Invisiblek's "cwm_selinux_6.0.5.4_datamedia.uImage" (7.1MB) is renamed to uImage.ClockworkMod and "moved" to /boot folder.

Thanks. Recovery is driving me nuts. So many roms. Each wanting a different recovery. I try to help by testing rooms but I guess I will just stick to one as its to difficult to keep up with them all. Had to Webos doctor several times this week. Back to mom data media for me. Thanks again!

[Q] Updated CWM and resized partition, now CWM can't find my folder structure

I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM10:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
Rebooted into webos:
resized my system partition from 400 to 600 mb.
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
CM10 still boots fine and my files show up in /sdcard0/. There is no sign of a folder called /sdcard/. Same story if I explore the device with a computer.
I should mention that I also moved my nandroid backup to my computer, off the touchpad to save space before I resized my partitions. I then moved it back into the folder. I wouldn't be opposed to wiping the thing and starting over to get 4.4 working.
Any ideas?

kspanks04 said:
I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
Click to expand...
Click to collapse
First, this issue that you observe has been discussed ad nauseam in various CM11 ROM development threads.
Second, you did not post which specific CM11 ROM you are planning to employ. So I assume it is Milaq's CM11 ROM (kernel 3.0+).
At any rate, what you are observing in an inability to directly access the /external_sd partition (on the TouchPad), which is accessible in previous CM builds, but is no longer directly accessible in Milaq's recent CM11 builds (Kernel 3.0.101) or in his recent CWM recoveries.
http://forum.xda-developers.com/showpost.php?p=49216229
• Milaq and others have suggested you can use ADB to mount the partition manually (sorry no instructions).
• Some have posted you can use Invisiblek's recovery (CWM 6.0.5.4 selinux datamedia) to flash Milaq's recent CM11 (Kernel 3.0+) ROM's
• You may be able to find a version of TWRP that can access the /external_sd partition.
On a related note, the new DataMedia storage paradigm which is the future of Android, has been designed into the newer CM11 and other KitKat ROM and recovery builds. Thus you need to increase the size of your /data partition.
You can use the Tailor app within WebOS to reduce the size of /media partition, then increase the /data partition size. And there are some scripts available that do similarly.
Best to read the specific ROM thread (including the OP) for more info on how DataMedia applies to the ROM build you are employing, and then be sure to read later posts in the thread regarding the inaccessibility of /external_sd: http://forum.xda-developers.com/showthread.php?t=2542353
It is possible that future builds of the CM11 ROM (kernel 3.0+) might provide access to /external_sd once again. Will see. Fingers crossed.

I tried invisiblek's cwm recovery and it did not provide access to /external_sd
(and there is confusion on the recoveries specific version number)
http://forum.xda-developers.com/showpost.php?p=49423381
There is another recovery on invisiblek's site: openrecovery-twrp-2.6.3.0-tenderloin.zip
Anyone have experience with that recovery version, ability to access /external_sd or "compatibility" with Milaq's newer CM11 ROM builds?

Yes sorry, Milaqs rom that you linked is the one I was working from. I don't have ten posts so that's why I'm posting here. I read through most of that forum and tried searching for my issue with no luck.
I went back and saw a couple posts that matched my problem with the following solution:
http://forum.xda-developers.com/showpost.php?p=49154585&postcount=471
When I get home I will try this although I didn't remember seeing that folder when I explored my device on Windows.
Thank you for the reply and sorry for the redundancy!

Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now

kspanks04 said:
Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now
Click to expand...
Click to collapse
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck

Here is another trick that worked for me. Recover a previous stored ROM that supported both sd1 and sd0. Use file manager to copy the files you want from sd1 to sd0. Then go back to the new ROM and you will have access to your files on sd0.

Merfy said:
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck
Click to expand...
Click to collapse
Ahhh thank you. I had tried this with a different file explorer in root. Es did the trick.

Now I need figure out how to fix these black screens that lock up after a good amount of inactivity.

Greeting HP Touchpad Expert: I need help.
I didn't mean to post this thread but I have same issue.. only I have this..
I also updated my CWM to http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.7-tenderloin.zip
in preparation for upgrading my CM09 to CM11 (Milanq 4.4 Kitkat). Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM9:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
I have not yet resize system partition.
Now, when I want reboot to CWM install the 4.4 rom all my folders were missing.
All I can see is
/sdcard/
-0/
-clockworkmod/
-clockworkmod/backup
Yes I have tried to ES File Explorer (R+W root) and following gabhroo123's notes above
I do not have
/data/media nor /data/media/0 folder
only empty /data folder.... I am able to write to copy older recovery-clockwork to /data but not "/" ...
When reboot to CWM 6.0.4.7 I still don't see any zip file.. (No files found message show).
Can someone at least point me the right URL or discussion xda-developers.com thread so I can read them.
I am not sure what I did wrong...
What extra steps I suppose to do ...because I have HP Touchpad with CWM 5.x.x + Android 4.0.1.x + CM 9 + mobo 0.35 ?
My planning steps were
#1) upgrade CWM to 6.0.4.7
#2) upgrade CM 11
#3) upgrade Gapps
Reference http://forum.xda-developers.com/showthread.php?t=2542353
([ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel])
I do see /sdcard/clockworkmod/backup/backupfolder.. in CM 9 and I did put CM 11 and Gapps in several place in
/media , /sdcard/media, /sdcard/cminstall etc.. but nothing.. kept saying file not found..
Should I downgrade CWM back to 5.x.x ? I do not see any install zip file at all ...how?
HELP!
Thank you

[UB]FOTA TWRP/PhilZ installer APK and Flashable ZIP recovery

F2FS improves the benchmark score in most (if not all) devices by around 20%..
For testing:
I have modified an APK containing Aroma Installer to flash recoveries to fotakernel for our ZR's. This is an initial release..
It contains 2 recoveries.
PhilZ Touch and TWRP with f2fs (TWRP) support which has been tested and working in both Resurrection and Validus builds/ports and should work in all cm11 and CM12/CM12.1 with f2fs working in cm12 after march this year
Install the apk and flash either Philz or Twrp through the app in the drawer..
And no, this is not Xperia Recovery manager.
The recoveries are both contained in the app so making it 22MB to download.
The TWRP 2.8.7.0 has new graphics and f2fs support
PhilZ is stock 6.57.9 cwm v6.0.5.1 shared by @uncomment
Download APP here (contains the 2 recoveries mentioned above): Removed because of bugs.. will fix and upload to new link..
TWRP 2.8.7.0 f2fs with updated graphics flashable zip: https://drive.google.com/file/d/0B3slVcYWwXQ-RjNKUDhWWk5OemM/view?usp=sharing
(This is the latest recovery from TeamWin with their new blue theme.. I personally didn't like all that blue so I changed the images.. See screenshot below)
Philz Touch 6.57.9 flashable zip:https://drive.google.com/file/d/0B3slVcYWwXQ-MEd4TU1vb0NYcmc/view?usp=sharing
Flashable ZIP stock TWRP 2.8.7.0 with f2fs:
Put the zip in you sd card and flash through recovery.. This will push the twrp 2.8.7.0 f2fs to your fota kernel, reboot recovery after flash...
Download: https://drive.google.com/file/d/0B3slVcYWwXQ-YTB6V1N0eEx5SU0/view?usp=sharing
Please test (recovery.img)
UPDATED TO TWRP 2.8.7.0
Download here: https://drive.google.com/file/d/0B3slVcYWwXQ-SjJRRjdyZ2pzeXc/view?usp=sharing
Instructions are the same as below...
This is TWRP 2.8.6.0
Download here:
https://drive.google.com/file/d/0B3slVcYWwXQ-Q0pEYzlFSjhPNFk/view?usp=sharing
Place the recovery.img (it is named twrp.img when you download but rename to recovery.img) to you internal storage and use adb or emulator (download Android Terminal Emulator free from Store) commands to install to your Fota:
su (enter and grant root access if using Emulator)
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel (enter)
If you use Xperia Recovery Manager app by @championswimmer, rename the recovery.img to twrp.img and put in the TWRPXperia folder on your sd-card and flash to Fota through the app. Confirmed working.
If the image doesn't install correctly, please flash this hack:
http://forum.xda-developers.com/show...51&postcount=2
Only cache and data/ ext-sdcard is convertible for now, if you try to convert system, you will brick your phone..
Use the following method to convert:
Convert to f2fs by pressing Wipe > Advanced Wipe > select the desired partition > Repair or change filesystem > Change filesystem > f2fs
Some added info by @nostupidthing
with f2fs twrp installed, i've changed /cache and /data into f2fs without wiping. you just have to backup /data, then format it as f2fs, click "use rm-rf instead for format" in twrp settings, then restore /data.
If any one is looking for a theme for twrp recovery, i found an excellent theme here: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
(Download resolution 720x1280 for ZR)
As an added service I am willing to personalize the splash screen at recovery start-up should you have any request ie your name, flag etc but i will insist that "TeamWin" will be present somewhere on your personalized splash.. After all, we all benefit from their hard work.. Do not expect your request to be done within the hour but periodically check and i will upload and link as and when you request is done..
Massive thanks to @uncomment and @o-l-a-v and @Olivier and @blastagator and @qsnc including @nostupidthing for testing and for making this possible. @SdtBarbarossa for the app!!

the "now changing the microsd to f2fs" is not necessary for /data & /cache. you may or may not like to do it, and i ended up not doing it because copying my several gbs of files out of the microsd takes so much time and i just gave up..
but if anyone wants to do it, basically you just copy the files to your PC, then format the microsd to f2fs, then copy the files back there.

nostupidthing said:
the "now changing the microsd to f2fs" is not necessary for /data & /cache. you may or may not like to do it, and i ended up not doing it because copying my several gbs of files out of the microsd takes so much time and i just gave up..
but if anyone wants to do it, basically you just copy the files to your PC, then format the microsd to f2fs, then copy the files back there.
Click to expand...
Click to collapse
I agree with you.. I have formatted my ext sd card but like you said, took ages to copy the content to pc and back again.. In my opinion not worth doing if anyone, like me, use the ext_sd card for storage of music and downloads etc.. Cache and data absolutely worth doing tho.. A great many thanks for your comments and help doing this..
sent from Paul's phone

one more thing. backing up /data via twrp will not back up your "internal sd" files, like camera photos if you store them internally instead of on the microsd, so you have to copy those yourself as well.

Added flashable zip to op... Should make things easier..

the 2.8.7 flashable zip works, bro. thx.

hey, any chance that you make an insaller version ?

Ilko said:
hey, any chance that you make an insaller version ?
Click to expand...
Click to collapse
I'll look in to it..

hagar006 said:
I'll look in to it..
Click to expand...
Click to collapse
Great
BTW, I would suggest you to set TWRP's file manager to open SDCARD1 by default instead of SDCARD0, if possible, or even both to let users choose. I'm not sure if this is ROM or Recovery dependent because it worked this way through the latest Validus ROM. I'd bet on the recovery side though.

Ilko said:
Great
BTW, I would suggest you to set TWRP's file manager to open SDCARD1 by default instead of SDCARD0, if possible, or even both to let users choose. I'm not sure if this is ROM or Recovery dependent because it worked this way through the latest Validus ROM. I'd bet on the recovery side though.
Click to expand...
Click to collapse
It's party of the recovery but a few spaces down from the top in file manager is external_SD and a few spaces lower is SD_card so should be easy enough to find the way around..
BTW I've made new images and things for twrp which makes it a little easier to see but I'm waiting for permission from someone as I used their ui.xml to make that.. Will be added as soon as
Sent from my ZR

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