Related
By example of this thread, I thought it would be convenient to also create a separate thread for our L5. I will update this first post with relevant information and links when needed.
Info
CyanogenMod's site: http://www.cyanogenmod.org/
Announcement on Google+ by CM: link
Screenshots by luKi13223: link
Screenshots by Sirrocco with dpi lowered to 130 and theme applied: link
Requirements
Properly unlocked boot loader (here, a guide on top of first post)
Root/working CWM
Ability to read and common sense
Downloads
Nightlies started building. You can get the latest build from http://get.cm/?device=e610 OR http://10.cmxlog.com/?device=e610
CWM Recovery by Ricardo Cerqueira (CyanogenMod): Direct download. Alternatively you can download the flashable zip provided in the attachment, it's the same, but easier to install if you already had a recovery installed.
Google Apps (GAPPS) for Jelly Bean/CM10: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Short Installations guide
Make sure you meet the requirements
Download needed files (see above) and place them on your internal sd card
Update your ClockWorkMod Recovery to v6.0.2.8 (you can do this by using terminal, adb (guide) or use the flashable zip I've attached
This will avoid status(7) error messages and prevent issues with ROM Manager.
Flash "cm-10-build date-NIGHTLY-e610.zip" from your internal sd card with CWM (or if you prefer with ROM Manager)
[*]Optional: Flash custom kernel by PinkFlozd: link to thread WARNING: Don't install this kernel with builds created on 21 april 2013 or later (at least not untill someone updates the kernel)
Optional: Flash "gapps-jb-20121011-signed.zip"
After first boot see if your receiving any signal (provided your normally have any signal on that spot). If not, don't worry, a simple reboot might fix it.
Enjoy
Bugs:
Considering these are the very first nightly builds of CM10 for our device, the dev did a pretty great job. Almost everything is working. Thanks to him :highfive:
Network / data is not working after 1st boot. A simple reboot after a few minutes might fix this
Multi-touch not fully working (dual touch works)?
SD card is full error, while there is still room left (up to at least 300 MB). I haven't experienced this bug in a while, it may be fixed, but I'm not sure.
Accelerometer
Small mods/Fixes
Wake with Home key
Pinkflozd's custom kernel[/COLOR]. Supports multi-touch and allows for overclocking. His kernel doesn't work with builds after April 14th
Overclocked kernel for builds made after April 14th
Workaround to make accelerometer work
:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Ianuz1320 said:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
same here...
Will the developer look here for bugs? Or is there some other way to report CM10 bugs?
Anyway, I noticed that it drains battery much faster than the stock rom too.
Tonight it drained 20% of battery just by standby.
Ianuz1320 said:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
First install the recovery provide by CM. This will fix this problem. You will need to copy your flashables zips and back ups to the internal SD-card, because this version only mounts internal SD (instead of only the external)
E.jr said:
Will the developer look here for bugs? Or is there some other way to report CM10 bugs?
Anyway, I noticed that it drains battery much faster than the stock rom too.
Tonight it drained 20% of battery just by standby.
Click to expand...
Click to collapse
I don't know if he will look here. We could inform him about it, when we have more clarity about the bugs.
My main purpose was to concentrate talk about CM10 in one place, because in the other thread also other subjects were discussed and it got messy. And we might help each other here with CM10 related problems.
ldeleeuw said:
First install the recovery provide by CM. This will fix this problem. You will need to copy your flashables zips and back ups to the internal SD-card, because this version only mounts internal SD (instead of only the external)
Click to expand...
Click to collapse
thank you buddy..but where can we get recovery provide by CM?
For Instalation aborted :
Open downloaded zip by winrar or 7zip.
Open Meta-inf>google>android>updater-script
Open updater-script by notepad++
Delete first lane in updater-script
Save and rebuild archive (automaticly)
Copy your package to sd card and instal via cwm
Kisloo said:
For Instalation aborted :
Open downloaded zip by winrar or 7zip.
Open Meta-inf>google>android>updater-script
Open updater-script by notepad++
Delete first lane in updater-script
Save and rebuild archive (automaticly)
Copy your package to sd card and instal via cwm
Click to expand...
Click to collapse
it's not working buddy.
delete this lane :
assert(getprop("ro.product.device") == "e610" || getprop("ro.build.product") == "e610");
Click to expand...
Click to collapse
and it will work
Thanks buddy.. it worked on my phone!! but first boot took so long..i was stuck on CyanogenMod boot logo!! untill now!
Ianuz1320 said:
thank you buddy..but where can we get recovery provide by CM?
Click to expand...
Click to collapse
check first post
The new nightly does seem to lag a little as opposed to the original one.
The first one was smoother I've noticed.
E617
Has anyone tried CM10 for the E617 version of the L5? I'm to much of a newb to try it myself, I wouldn't be able to find my way back if I screwed-up my phone.
Bootlop
Im on cm bootloop about 20 minutes WHEN THIS WILL BOOT UP
I noticed that this cm10 for e610 has a kind of problem with multitouch,I have played shadow gun,modern combat 3 and modern combat 4 and six guns and in all these 4 games, I noticed that I can't move at the same time that I shoot,I wait that they solve this problem in next updates ;p
Sent from my LG-E610 using xda premium
Kisloo said:
delete this lane :
and it will work
Click to expand...
Click to collapse
thanks a lot mate!
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
DodoKoce said:
Im on cm bootloop about 20 minutes WHEN THIS WILL BOOT UP
Click to expand...
Click to collapse
E: I found out why there is a bootloop, we didn't took the right bootloader, see here my tutorial: http://forum.xda-developers.com/showthread.php?t=2186161 - if you do everything like i did, everything will work properly
Use older build, idk - new is more bugged :/ Old working smarter than new.
OK, I've got it installed (nightly 20130310), first I installed the provided CWM (6.0.2.8), had to do that manually though, because for some reason Rom Manager destroyed the 6.0.2.5 version I had when I tried to install CWM through Rom Manager.
It's running smoothly, although I also see a little graining in the screen. I had no data issues.
Also, booting didn't take that long.
One strange phenomenon:
I had FreeL5 running before CM10. Before flashing CM10 I did a factory reset from CWM, cleaned cache and Dalvik cache. After booting CM10 for the first time, my WiFi settings were still there... hadn't expected that, but since I'm on a corporate WiFi connection which needs a username and password to connect, it was nice not to have to retype it :victory:
---
Previous devices:
HTC Desire - MIUI
HTC Desire HD - MIUI
Sony XPeria S - FreeXPeria JB
Current devices:
Samsung Galaxy Tab 2 7.0 - Stock JB (because my girlfriend doesn't want me 'messing' with it)
LG Optimus L5 (E610) - CM10 nightly
Bootloop too, any way to solve?
This is a patch to install a second system with BMM in unused partitions without using virtual slots and in this way we will save a lot of space in our internal or external memory.
With this patch BMM will install the System_2 in these unused partitions:
- /system_2 in /preinstall
- /data_2 in /webtop
- sharing /cache with /system_1
How to install:
- Install BMM
- Copy the .zip file to the external memory or memory card
- Reboot your phone and enter on BMM
- From the Install menu select the .zip file and instal on System_1
I personally tested installing every rom for the droid 4 with bmm in System_1(that is the stock rom system) and System_2 without any problem.
To install the official version of the cm11 with bmm avoiding the status 6 error you have to simply replace in the .zip the updater-script at this path:
HTML:
.zip\META-INF\com\google\android\updater-script
with the updater-script here attached and then you can install the modded .zip with bmm.
The patch is available here.
Hello Mentor! So, I have to select, in recovery, system_1 and flash this .zip, no? After that, if I want to install a second rom in my droid 4, what I have to do? Tnx in advance
Inviato dal mio DROID4 utilizzando Tapatalk
You have to activate the System_2, then you can switch in it and you can install a rom.
The first version of this patch was not working. I manually edited my configuration and i did not test the patch.
Sorry!!!
Now I have updated the patch with version 2.1 and I've tried the patch and it is working properly.
xt912
is it working on xt912?
whats the difference with normal system2?
This is only for xt894.
Does this patch mean that only one set of app data is shared between the two, or is it just using the space of webtop?
Sent from my XT894 using Tapatalk
With this patch you will use the unused partitions to install a second rom, in /preinstall will be installed the system and in /webtop will be stored the data.
I could make a patch to share /userdata between system1 and system2 to share the user data and app but i think that this will make unstable both systems if you will use two different rom.
Gotcha, thanks for the info!
Sent from my XT894 using Tapatalk
With BMM I successfully tested in System_1 and System_2 all the roms that with safestrap should be installed only on slot 1.
Mentor.37 said:
With BMM I successfully tested in System_1 and System_2 all the roms that with safestrap should be installed only on slot 1.
Click to expand...
Click to collapse
hmm I do not understand what you mean
I want to have stockrom in slot1 and cm1x in slot2
whether such a combination is possible?
I just installed CM10.2 in slot 2,
BMM nicely named him, but as I try to bootup with this slot, BMM booting [email protected]
--------
EDIT
--------
all OK!!
switching system is not so cute like in safestrap, but it works
You can choice the rom to boot at startup and you can set your preferred rom in the bmm app.
For me it is a lot better than safestrap.
Looks like BMM can't install the latest CyanogenMod nightlies which is a shame as it did look bloody useful.
I did, however, use it to wipe the cdrom partition which means that even when booting the stock ROM, the cdrom no-longer automounts, no more having my phone attempt to install Motocast when I plug it into someone else's PC!
I wonder if there's any way to use those partitions as additional user data on the stock slot, some kind of JBOD type setup?
I also couldn't get BMM to install from the Play Store, says it's incompatible with my device, so used this little website to pull it directly from google to my PC and sideload it: http://apps.evozi.com/apk-downloader/?id=com.projectlense.bootmenu.manager
To install the cm11 with bmm you have to edit the .zip with this file.
With the locked bootloader we can't use these partitions in other way.
About the download of bmm from the play store I have not had any problems.
Mentor.37 said:
To install the cm11 with bmm you have to edit the .zip with this file.
With the locked bootloader we can't use these partitions in other way.
About the download of bmm from the play store I have not had any problems.
Click to expand...
Click to collapse
The download works from CM11, but not from the Stock Verizon ROM. Unfortunately under CM11 it won't install, complaining of the wrong busybox.
Going to make a new rom slot and flash a stock-based rom, just to install BMM, *sigh* I guess it's probably not wise to install BMM from CM11 on the stock slot anyways.
Ended up flashing back to stock, install BMM and your patch, attempting to install CM11 nightly with the updater-script replaced with yours...
-- Installing: /ext/D4_ROMs/CM11/cm-11-20140521-NIGHTLY-maserati.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
No error message or anything.
I guess it's back to safestrap
I have never tried installing bmm with pure stock rom, my main system is the stock rom updated with my rom.
If you want install the cm11 in System_1 with bmm and to avoid the wrong busybox error you have to install the stock rom, then you have to install bmm, then you can format the System_1 and finally you can install the cm11 in the System_1 but you can't re-install the bmm app in the cm11. Everything will work correctly the same.
Honestly I installed my rom in System_1 and the cm11 with my patch gsm and with my gapps in System_2 to try the ART.
#Postedit
If you do not know how to recompile the .zip you can install these versions that should work with bmm.
##Postedit
You do not have to recompile the .zip, you can simply open it and you only have to replace the updater-script.
Hi!
You will be in the future, wrote a patch for Android Lollipop? update-scripts does not work properly with the new Android (installed, but the Android has bootloop [I wait only few minutes and nothing happened])
I do not know if it's possible (the special version of Safestrap was created for Lollipop)
Fervi
I'm sorry but i think that bmm will never be available for L.
This sounds awesome, but would it be at all possible to make a script that sets up the partitions for just ONE ROM in the stock slot and reclaims all of the other space to make it available to that system? I do not use any other ROM slots, and have CM11 installed into my Stock Slot, but sadly am limited by a 3GB Data partition out of the 16GB internal space that could be more available. i realize this is not what your patch does, as it just gives extra space to Slot 1, but I would love to be able to just have one ROM in Stock Slot and utilize the space otherwise reserved for other slots.
Earlier today I saw a CyanogenMod 11 nightly so I decided to update from cyanogenmod 10.2 through cmupdater but it showed a status 7 error now I bricked my nook. Every time I try to boot it up it goes to cwm but I cannot select anything. Can someone please help me. :crying:
GianniAraujo said:
Earlier today I saw a CyanogenMod 11 nightly so I decided to update from cyanogenmod 10.2 through cmupdater but it showed a status 7 error now I bricked my nook. Every time I try to boot it up it goes to cwm but I cannot select anything. Can someone please help me. :crying:
Click to expand...
Click to collapse
In order to flash the CM11 zip you need to update your CWM to 6045.
Make a new CWM SD from verygreen's CM11 thread.
Sent from my SCH-i705 using XDA Premium 4 mobile app
leapinlar said:
In order to flash the CM11 zip you need to update your CWM to 6045.
Make a new CWM SD from verygreen's CM11 thread.
Sent from my SCH-i705 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey thanks man, I'll try it after I finish school.
**Update**
It works! on CWM 6.0.4.6, thanks for your help
TWRP 2.6.3.0 works also fine here, also the last CM11-20140113 update worked using TWRP
GianniAraujo said:
Hey thanks man, I'll try it after I finish school.
**Update**
It works! on CWM 6.0.4.6, thanks for your help
Click to expand...
Click to collapse
Hi there! I did what you did (use cmupdater to update and got the status 7 error). I followed verygreen's upgrade (not new install) instruction and updated to CWM 6.0.4.5, but when I flashed CM11 I still get the status 7 error. Did you install as New Install or Upgrade from CM10.x?
I then use the New Installs instruction, unzip the initial SD image, unzipped and wrote the 5 files with winimage to a SD card. But when I went to choose zip from /sdcard or /external_sd, it didn't see the files. And if I just save the initial SD img file to the SD, it will see it, but then gives me the status 7 error.
Also, there are two files there "for completeness"... what does that mean? Should I use those instead?
What did I do wrong? Many thanks to save my nook (HD+)!
koalajoe said:
Hi there! I did what you did (use cmupdater to update and got the status 7 error). I followed verygreen's upgrade (not new install) instruction and updated to CWM 6.0.4.5, but when I flashed CM11 I still get the status 7 error. Did you install as New Install or Upgrade from CM10.x?
I then use the New Installs instruction, unzip the initial SD image, unzipped and wrote the 5 files with winimage to a SD card. But when I went to choose zip from /sdcard or /external_sd, it didn't see the files. And if I just save the initial SD img file to the SD, it will see it, but then gives me the status 7 error.
Also, there are two files there "for completeness"... what does that mean? Should I use those instead?
What did I do wrong? Many thanks to save my nook (HD+)!
Click to expand...
Click to collapse
Sorry for the late reply, don't know if you still have this issue but anyway... First I didn't use winimage i used win32 disk imager (maybe that's the problem), I also used CWM 6.0.4.6 from verygreen and I used the latest CM11 official nightly. I did a clean install but you could try installing over your current cm update but I can't guarantee anything. Hope this helps!
Links
http://sourceforge.net/projects/win32diskimager/
http://forum.xda-developers.com/showthread.php?t=2600572
http://download.cyanogenmod.com/?device=ovation
GianniAraujo said:
Sorry for the late reply, don't know if you still have this issue but anyway... First I didn't use winimage i used win32 disk imager (maybe that's the problem), I also used CWM 6.0.4.6 from verygreen and I used the latest CM11 official nightly. I did a clean install but you could try installing over your current cm update but I can't guarantee anything. Hope this helps!
Links
http://sourceforge.net/projects/win32diskimager/
http://forum.xda-developers.com/showthread.php?t=2600572
http://download.cyanogenmod.com/?device=ovation
Click to expand...
Click to collapse
Thank you for the reply I finally did successfully bringing it back to 10.1.3. I messed up one step Thank you!
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Edit : on ES Explorer you have to activate root access to see /data/media/0
Bristow69 said:
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Click to expand...
Click to collapse
Welcome to the world of DataMedia.
In CM10.1 use a Root Browser app (e.g. ROM Toolbox lite) or a file manager app with root permissions (e.g. ES File Explorer or X-Plore) to move your CM11 ROM zip to a directory accessible to your new CWM recovery.
Myself I store all my ROM and recovery zips in the Download directory, where Chrome and Firefox also download files to.
e.g.
/storage/sdcard0/Download
/data/media/0/Download
Thanks woodytrain for your quick reply.
I tried to put my ROM /storage/sdcard0/Download but it's the same, i don't see this folder.
In /data, i've no folder
I tried to find obb/ with ES Explorer and it found it on /mnt/, is it normal ?
Last thing, i gone in WebOS in order to use Tailor and found this partition layout, i think it's not ok to flash KitKat :
USB (media) = 25.43 Gib
Android (system) = 408 Mib
Android (cache) = 200 Mib
Android (data) = 1.5 Gib
Unused Space = 8 Mib
I don't knom how to install KK on my touchpad. I don't understand because i don't thing to be a newbie, i flashed i9000 on CM 10.2, Touchpad on CM10.1, but KK made me crazy !
Thanks for your help !
You need to change your partition sizes. At the very least need to increase /system
And if you want to install a DataMedia (DM) ROM, you need to make additional adjustments.
Right now there are three (or four) KitKat (4.4.2) ROM's for the TouchPad (tenderloin) to choose from:
CM11 - 3.0 kernel (Milaq) - DM
CM11 - 3.4 kernel (invisiblek) - DM
Evervolv - AOSP - 3.4 kernel (flintman) - (two version:- one DM and one not)
If you want to install KitKat on your TouchPad will need to do some reading. Keep in mind all these KK 3.x kernel based ROMs are in development (experimental and/or for testing). Each has its own pros and cons, and various TouchPad features are not yet working, features you might have observed working in previous JB 2.6 kernel ROMs.
If you want to stay with JB, until KK is better baked for the TouchPad you may want to try out the new JB 3.x kernel ROM just released from jcscullins (01-25-14). It is NOT a DM ROM, whereas Milaq's CM10.2 (JB) is a DM ROM.
http://forum.xda-developers.com/showthread.php?t=1811480
Suggestions:
1. For each ROM you are interested in thoroughly read the OP. And suggest reading, at the minimum the last five pages of each thread.
2. Then visit [ROM GUIDE] How to Update/Install Android 4.2, 4.3 and 4.4 Builds on the HP TouchPad
http://forum.xda-developers.com/showthread.php?t=2321397
3. Be sure to read the info on how to update your partition for DM support. If you decide to go with a DM ROM, I would suggest using Tailor to change your partitions since you have Tailor installed on your device already.
4. Backup your device before proceeding. Generate a nandroid backup in your recovery as well as back up your app/data with Titanium Backup
5. A "full wipe" in your recovery (factory reset, including clearing caches, formatting /system) is generally recommended when doing major upgrades (not just a nightly flash of the same ROM).
Once you have chosen a ROM to install, and have downloaded the zips for both the matching ROM and Recovery zips (note each ROM has it's own specific recovery version matched to the ROM), then you should be ready to upgrade.
If you have questions before upgrading post your SPECIFIC questions/issues, identifying the ROM version you are coming from and going to.
Thanks woodytrain for your help.
I understood what i missed : root explorer button on Es Explorer
So, now, i can see my files with clockwork Recovery, yes ! I put them in /data/media/0/Download.
After that, i'm gone on Tailor to resize my partitions.
Now, i have :
600 Mb for system
200 Mb for cache
15 Go for media
and ~ 6 Go for data, it's not enough but don't care now...
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Bristow69 said:
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Click to expand...
Click to collapse
Not sure what is meant by "15 Go for media". Recommend you follow the partition instructions as listed in the OP of Milaq's CM11 ROM thread. At any rate...
Before you started the process did you do a nandroid, and backup your apps and data with TiBu or helium?
Then when you did the wipe, did you clear Dalvick cache as well?
And then did you flash the CWM recovery version listed in the OP of Milaq's CM11 ROM thread (CWM 6.0.4.6)? You MUST use that version.
http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.6-tenderloin.zip
You might want to redo the process and hold off installing gapps until you have booted into CM11. Then go back to recovery and install the gapps listed in the OP. Or install one of the PA-gapps packages.
With a few more posts you receive the right to post to the ROM dev thread. Joy!
I reply only to increase my posts and because i made a big big mistake after this post, i formated all partitions on clockworkmod (6.0.4.6 ). So i will create an other thread on forum...
Mad and Confused
I was duped into updating to 4.4 evervolv when i was on their 4.3.1 rom and im not understanding the layout of my sd-card now. i know all my info is still there but unsure how to reformat so i can use all my space. 32gb touchpad. i will use root explore app to get all my data but can i use onboard storage app to format? Really pissed im in this situation at all. Stupid to be on a 4.3.1 rom and update only to find out it's now a 4.4 rom and my sd-card is different. Thanks much
Nevermind, got it sorted. Good excuse to repartition and reformat everything. Still want nothing from evervolv but there 16mb Gapps package, mwahaha
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!