Database Develop

[Q] CM 10.1.3 RC Question

According to this post,
cyanogenmod [dot] org/blog/cyanogenmod-10-1-3-rc1

edfcmc said:
According to this post,
cyanogenmod [dot] org/blog/cyanogenmod-10-1-3-rc1
CM just announced one update to the CM 10.1 branch of code. I tried posting this in the other CM 10.1 thread, but I cannot due to my newbiness. Anyway, does anybody know if 10.1.3 RC1 will get ported to the Nook HD Ovation? Can somebody ask everygreen the awesome guy who has been doing all this stuff? I really havent made the switch to 10.2 and probably wont for quite a while. I currently run 10.1 the last one from 8/13. I wonder of 10.1.3RC has anybody better. Oh well. I hope this makes sense.
Click to expand...
Click to collapse
I missed the boat on 10.1.3RC1, but RC2 and eventually 10.1.3 stable should be made for our devices too.

Where should we watch for updates about when this is available? Seems all of the chatter over in the dev forum is only about CM10.2.

mr72 said:
Where should we watch for updates about when this is available? Seems all of the chatter over in the dev forum is only about CM10.2.
Click to expand...
Click to collapse
It's up now.
HD (hummingbird) http://download.cyanogenmod.org/?type=RC&device=hummingbird
HD+ (ovation) http://download.cyanogenmod.org/?type=RC&device=ovation

Update
NookE said:
It's up now.
Click to expand...
Click to collapse
Would installing this new 10.1 RC from the updated in CM be wise?
Still very new to this. Just got CM put on my Nook this weekend and would hate to have to start fresh again.

I would suggest installing any RC version. They are supposed to be pretty stable and have bug fixes that you'll want (not to say that they won't have bugs of their own).

artesea said:
I would suggest installing any RC version. They are supposed to be pretty stable and have bug fixes that you'll want (not to say that they won't have bugs of their own).
Click to expand...
Click to collapse
I think he's asking about updating from the CM menu. I received a notification today that RC 2 was available, will I lose all my apps and data if I update from there?

Mugby said:
I think he's asking about updating from the CM menu. I received a notification today that RC 2 was available, will I lose all my apps and data if I update from there?
Click to expand...
Click to collapse
No.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
No.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the help!
I updated it with the internal CM updated but it kept hanging on boot and restarting so I just went ahead and did a manual install.
My Nook runs much smoother now! Hopefully it won't keep rebooting and hanging on boot as much as before.

[Q] Introduction and a question about nightly builds

Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:

Fanarkle said:
Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:
Click to expand...
Click to collapse
Nightly builds are just that, builds that are made nightly. They are the most up to date. Snapshots/M(*insert number here*) releases are generally more stable, but we got knocked out of being eligible for them after the release of M8 (thanks kk bootloader). CM has made a msm8960 jb bl section, which you did find. This might get us up and running for a M10 next month if they choose to do that, but then again, msm8960 did not get a M9. Nightly's are for everyone. CM makes a few tweaks to their code and pushes it to each nightly. Some tweaks make it better, some tweaks make it worse. If you are satisfied with the release that you currently are running, you don't need to flash the update if you don't want to. Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Sent from my MB886 using XDA Free mobile app

palmbeach05 said:
Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Click to expand...
Click to collapse
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.

Fanarkle said:
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.
Click to expand...
Click to collapse
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.

Dr. Orange said:
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.
Click to expand...
Click to collapse
When you say "clear cache", do you mean "wipe cache partition," "format /cache," or "wipe delvik cache?" So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.

Yes. Wipe cache. It will format automagically. You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.

Fanarkle said:
So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.
Click to expand...
Click to collapse
Dr. Orange said:
You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.
Click to expand...
Click to collapse
The method of flashing over-top of an existing ROM is referred to as "dirty flashing". The issue isn't so much that it's not recommended or that it develops problems, but it could potentially develop problems, because there's always a chance that the new build relies on some random file that should have been deleted, changed, etc.
So, in summary, it's perfectly fine to dirty flash a CM nightly over your existing version, especially if it works fine for you. HOWEVER, if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."

quasihellfish said:
if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."
Click to expand...
Click to collapse
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?

Fanarkle said:
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?
Click to expand...
Click to collapse
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.

quasihellfish said:
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.
Click to expand...
Click to collapse
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?

Fanarkle said:
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?
Click to expand...
Click to collapse
Well, then I just recommend sticking with XDA. If one of the real CM devs/maintainers then recognizes a bug, someone will report it. Or re-ask this question over there, and they can help you.

Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app

RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Click to expand...
Click to collapse
Did I do something wrong? I am creating a backup and "dirty" flashing the latest nightly right now. I was going to post how it went after I finished just so other people would have the info if they were looking for it.

Success! I rebooted into recovery and, after creating a backup, performed "wipe cache partition" and "wipe delvik cache" before installing cm-11-20140811-NIGHTLY-moto_msm8960_jbbl.zip on top of the build I was running. I rebooted and everything is as it was, except that my custom boot animation was reverted back to CM default (which was expected, no big deal) and the new version I flashed is correctly shown on the "About phone" screen. If I encounter any issues going forward, I will post in the appropriate thread.

Fanarkle said:
Did I do something wrong?
Click to expand...
Click to collapse
No.

RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Why did you post here if you had nothing constructive to say?
I'm glad you got it to work fanarkle[emoji4]

update bootloader

Im running an mb886 using the CM11 and Carbon nightlys. ive been using the CM11 JBBL nightlys and was wondering if there is any reason to jump up to a KKBL. and if so is there a guide. alas the search feature did nothing for me.

disregard i found it.
disappointing that i cant move to the KKBL.
currently I have carbonrom on my phone. do the CM11 nightlys for JBBL mirror the other ones or are they behind?

oscar the grouch said:
currently I have carbonrom on my phone. do the CM11 nightlys for JBBL mirror the other ones or are they behind?
Click to expand...
Click to collapse
CM11 nightlies are based on the same build for both JBBL and KKBL bootloaders. The build server runs every night and uses the same code base for both of them.
p.s. If you're ever in doubt, you can always check the changelogs for both the JBBL and KKBL builds.

Thank you.
I tired the aospb build rom earlier. For some reason it kept giving me unfortunately blah blah quit. Apparently my itialian input method. (Not Italian) kept shutting off. And everything I tried from my titanium backup and the playstore crashed every time I opened it. Can't ask inthe rom thread so I sent back to carbon. Any thoughts

oscar the grouch said:
Thank you.
I tired the aospb build rom earlier. For some reason it kept giving me unfortunately blah blah quit. Apparently my itialian input method. (Not Italian) kept shutting off. And everything I tried from my titanium backup and the playstore crashed every time I opened it. Can't ask inthe rom thread so I sent back to carbon. Any thoughts
Click to expand...
Click to collapse
Sorry, but I have no idea what you're trying to say. I've used both Carbon and CM11 on my phone without issue (currently on CM11 nightly).
If I had to take a wild guess about your issue with Playstore crashing, you probably need a newer/more compatible version of the Google Apps installed. Not sure what you installed, but the PA Gapps are always up to date. Start with the Mini or Micro packages and work from there.
Or ask a new question in the Q&A forum.

I was using the pa micro. Still am. Something about the aospb rom didn't like me. I flashed it with out gapps and it still.crashed every non system app. It was better when not running the app data on a partition but still not good. Currentlyrunning the carbon nightly with zero issues

oscar the grouch said:
I was using the pa micro. Still am. Something about the aospb rom didn't like me. I flashed it with out gapps and it still.crashed every non system app. It was better when not running the app data on a partition but still not good. Currentlyrunning the carbon nightly with zero issues
Click to expand...
Click to collapse
With some ROMs, I was having an issue with the dialler whereby I would need to press the # key three times in a row to get the keypad to appear. Have you ever experienced this issue?

audit13 said:
With some ROMs, I was having an issue with the dialler whereby I would need to press the # key three times in a row to get the keypad to appear. Have you ever experienced this issue?
Click to expand...
Click to collapse
have not. that is weird. how do you get a #key with out a dial pad tho?

[Q&A] CM11 based on 4.4.2 OTA

Q&A for CM11 based on 4.4.2 OTA
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Thanks!
JackpotClavin said:
K I'm back on my CM11 builds. New build will be released tomorrow if I have time!
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
This is a really nice ROM. I bought a VS980 (for cash, even) and was disappointed that Cyanogenmod didn't seem to be maintaining the build for it anymore. Battery life is so good I thought the battery meter was broken at first. I'm seeing 75% full at the end of a typical day of calls and texts and apps.
Thanks a lot for making this!

Is the OCT 13th build using 26a binaries, drivers and kernel?
Sent from my VS980 4G

I'm on 24a on paranoid android. Can I just go ahead and flash this like I do any other ROM or do I need to follow all the steps on the front page?
Sent from my LG-VS980 using XDA Free mobile app

babygetoboy said:
I'm on 24a on paranoid android. Can I just go ahead and flash this like I do any other ROM or do I need to follow all the steps on the front page?
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Just flash it is fine.

Curious what those on CM and CM based Roms are using for SMS..the stock app only sends compressed pictures that look like garbage. How are you all sending uncompressed? Personally I've been using Textra, but would prefer to mod stock SMS if possible...anyone?

What's the point of this thread? I don't understand what to ask here instead of in the original thread.

CaptainElwood said:
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
Click to expand...
Click to collapse
Kinda wondering the same thing. I guess it's good for people who don't have enough posts to use the development thread, on the other hand it splits conversations about the rom to two different places. I could understand if the developer specifically asked for all Q & A to go here but I don't think that's the case is it?

CaptainElwood said:
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
Click to expand...
Click to collapse
Based on the OP and the name of the poster, I'm guessing this is automated by XDA.
I think threads like these could be useful. For instance the question I posed above in no way contributes to the development of a ROM, it's features, or is a bug that needs sorting out.
Lately I've noticed mods pointing those who ask questions in a development thread to Q&A threads like this..I can only guess that XDA prefers things in this direction now.

Hope this isn't too dumb a question.
So I've been reading a LOT of this thread and I just need to clarify a few things.
First, I have the 26A build and cannot flash the regular CM11 (I get stuck in the LG boot loop) so this is how I found this thread. Now, is this thread specifically for a special build of CM that gets around this problem? The last 20 pages or so are more about bugs and things within this build so I'm getting a little confused on if this is actually the thread and build I need.
Second thing: If this IS the zip I need for my boot loop problem, can I simply flash it in recovery or do I need to go through the steps in the OP? I saw someone ask this question a few pages back but didn't really understand the answer. If it's as simple as a flash of the zip, whey would the long string of instructions still be in the OP? Thank you for clarifying.
Third thing is: If I flash this build and the official CM builds later somehow work with the 26A firmware, can I simply flash the new, official CM build(s) or will I need to wipe and install the official build clean?
Thank you for answering these annoying questions. I've literally spend the last 3 days trying to root and boot and finally found this thread and spent the last day reading up on it.

blue duck butter said:
So I've been reading a LOT of this thread and I just need to clarify a few things.
First, I have the 26A build and cannot flash the regular CM11 (I get stuck in the LG boot loop) so this is how I found this thread. Now, is this thread specifically for a special build of CM that gets around this problem? The last 20 pages or so are more about bugs and things within this build so I'm getting a little confused on if this is actually the thread and build I need.
Second thing: If this IS the zip I need for my boot loop problem, can I simply flash it in recovery or do I need to go through the steps in the OP? I saw someone ask this question a few pages back but didn't really understand the answer. If it's as simple as a flash of the zip, whey would the long string of instructions still be in the OP? Thank you for clarifying.
Third thing is: If I flash this build and the official CM builds later somehow work with the 26A firmware, can I simply flash the new, official CM build(s) or will I need to wipe and install the official build clean?
Thank you for answering these annoying questions. I've literally spend the last 3 days trying to root and boot and finally found this thread and spent the last day reading up on it.
Click to expand...
Click to collapse
1.Official CM is still using 4.2 sources.
2. Yes, just wipe and flash this then gapps. Ignore all the complicated instructions, they're outdated.
3. I'd recommend a clean flash, but, yes, when/if CM finally updates to true kitkat sources.

jesssiii said:
1.Official CM is still using 4.2 sources.
2. Yes, just wipe and flash this then gapps. Ignore all the complicated instructions, they're outdated.
3. I'd recommend a clean flash, but, yes, when/if CM finally updates to true kitkat sources.
Click to expand...
Click to collapse
Great! Thanks for clarifying. Is the CM team slow at updating the sources? I was under the impression that CM worked fairly quickly. From what I gather, the VS98026A build has been around for about a month, correct? Also, does that mean 26A is the first firmware from LG built on 4.4?

blue duck butter said:
Great! Thanks for clarifying. Is the CM team slow at updating the sources? I was under the impression that CM worked fairly quickly. From what I gather, the VS98026A build has been around for about a month, correct? Also, does that mean 26A is the first firmware from LG built on 4.4?
Click to expand...
Click to collapse
24A was first, then 2nd, then 26A. Not all were official. As far as CM goes, I don't know.

Getting same error message as other user
I have fewer than 10 posts so I can't post in the forum but I'm getting the same error message that user AO4EVER was getting. Here is his post:
"Same error message with the new build
Can't install this package on top of incompatible data. Please try another package or run a factory reset. E: Error executing updater binary in zip's '/data/media/0/sideload.zip'
Anyone else is getting this? [Don't think it is due to build, something is off the device itself]" - AO4EVER
He was confused because nobody else was getting that error message. Well, that's the message I get when I try to flash JPC's build of CM11. I am rooted on stock 26A.
Does anyone know why this is happening? The user said he ended up deleting some of the verification code to get it to finally work. Can anyone explain how I would go about doing this? I don't know a ton but I feel comfortable enough in terminal/command prompt to make changes if I know what changes to make.
*EDIT* I deleted the part of the verification code that was preventing me from flashing JPC's CM11 build and have successfully flashed it now.

Just updated to 20141026, GPS is broke (was broke on an earlier Oct build). I see others confirming GPS working, how do I test to make sure I don't have bad hardware?

laf gets overwritten
The aboot and boot replacement works fine. The md5sums match over many reboots. However, something keeps overwriting the laf file. I tried replacing mmcblk0p24 directly, and the md5sum for that and the laf symlink in by-name are correct, but when the phone reboots something has overwritten it. I also made a copy of mmcblk0p24 in the block folder, and strangely that gets deleted on reboot as well. But aboot and boot keep the changes. Weird. Do you know what could be causing this?

updating
If i followed this guide to install the cm 11 m11 build and i want to update to m12 how do i do that

boggsmicah said:
If i followed this guide to install the cm 11 m11 build and i want to update to m12 how do i do that
Click to expand...
Click to collapse
Wipe and flash rom and gapps as usual.
LG G2 VS980

I have the same problem with screen off during call after screen timeout has elapsed, did u manage to get it fixed? im on 26A and im using 2014 11 02 nightly build, M12 gave me call drop so i opted for the nightly

CM 11 (M12) vs980 Camera w Flash problem
Hello all,
So, i've been running the latest builds of CM 11 4.4.4 through the help of JackpotCalvin's write up and kernel exploit.
I figure I should ask if anyone else has had some issues with the camera and taking pictures with flash enabled?
for whatever reason the white balance is faulty with flash enabled and the pictures come out whitewashed. It didn't used to do this with previous updates (before the M12 stapshot).
maybe something is bogging down performance and i dont realize it. Anyway, thanks for any feedback.
-Mike M

Need a little help with my new Nook HD+. Overwhelmed with Roms and such.

Hi, so I have here a now totally stock Nook HD+. I previously installed Cm-10.2.1 Official Stable and it was anything but.
So I have a bootable SDcard with CWM 6.0.4.6 and my question is what Custom Android rom and Gapps combination is stable that someone could recommend? Can you point me in the right direction? I did follow the five easy steps tutorial but I kept getting an error 7 when trying to install the ROM.
I am a total noob but I am kind of getting the hang of CWM as I managed to restore it back to stock.

Get TWRP and look around a bit. There really aren't a lot of current ROMs out there for the Nook HD+.
CM 10.1.3 was probably the most stable but #AMACES is doing great things with CM 12.1 and CM 13.
Sent from my XT1060 using Tapatalk

FirePsych said:
Get TWRP and look around a bit. There really aren't a lot of current ROMs out there for the Nook HD+.
CM 10.1.3 was probably the most stable but #AMACES is doing great things with CM 12.1 and CM 13.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I will check that out thanks.

Zeig3r said:
Hi, so I have here a now totally stock Nook HD+. I previously installed Cm-10.2.1 Official Stable and it was anything but.
So I have a bootable SDcard with CWM 6.0.4.6 and my question is what Custom Android rom and Gapps combination is stable that someone could recommend? Can you point me in the right direction? I did follow the five easy steps tutorial but I kept getting an error 7 when trying to install the ROM.
I am a total noob but I am kind of getting the hang of CWM as I managed to restore it back to stock.
Click to expand...
Click to collapse
If you prefer a stable ROM, I'd suggest a recent CM11 nightly build from http://download.cyanogenmod.org/?device=ovation and a nano or pico GApps ARM-4.4 package from http://opengapps.org/#. And unless you plan to use CM12 or CM13, CWM 6.0.4.6 is a perfectly fine choice for both SD and EMMC recovery.