yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] ajrty33:
Attached is a flashable, updated cwm 6.0.4.5 recovery zip... since no one has posted one yet.
[Nook Color Android Development] ajrty33:
These two patches can now be cherry picked...

http://review.cyanogenmod.org/#/c/54609/

http://review.cyanogenmod.org/#/c/54610/
[Nook Color Android Development] gbeardmore:
So.... before I go flashing willie-nillie, I want to understand.

I'm on TWRP 2.3.1.0. If I want to change to CWM, I boot into TWRP and flash this CWM zip. Restart and I'll now have CWM, the next time I go into Recovery?

Thanks!
[Nook Color Android Development] pastordl:
That's it

I just did the same.
[Nook Color Android Development] unibroker:
I just tried flashing your zip while in TWRP 2.3.1 and I get

E:Error in /sdcard/encore-cwm-6.0.4.5.zip (Status 2)

I'll be hunting down what Status 2 means but thought I would let you know.
[Nook Color Android Development] leapinlar:
That usually means whoever made the zip used an old update-binary and TWRP 2.3 and above will refuse to flash them.
[Nook Color Android Development] weldawadyathink:
Anyone have an off-center boot animation? I have had it on two different builds I did.
[Nook Color Android Development] aperezdc:
In my builds I have no boot animation. I didn't look into it, probably some silly thing I did while trying to cherry-pick some commits from CM to AOSP... :silly:
[Nook Color Android Development] unibroker:
CM11 flash with TWRP 2.4.1.0 fails

I did manage to find a version 2.4.1.0 of TWRP from eyeballer's thread but got a Status 7 Error while trying to flash my 11/25 build. Leapinlar?
[Nook Color Android Development] :
In case anyone wants to build a TWRP recovery for CM11

http://xdaforums.com/showthread.php?p=32965365
[Nook Color Android Development] leapinlar:
I don't know anything about that version of TWRP. Is it supposed to work on CM11?
[Nook Color Android Development] unibroker:
Dunno. I thought I might try as it was the closest thing to 2.6 that I have found. Warning: I did a restore from TWRP after the fail; it completed (I thought) because the reboot system button appeared which I then hit. Result is I have a "dead" NC for the time being. I have been reviewing your signature. Thought before I tried I'd drop in another card that had been working previously but to no avail. I think that tells me that your solutions in the Tips section won't work either. BTW; my battery was at 86% when this happened.

Update: I think what might have happened is the TWRP restore process didn't complete even though the reboot button appeared. When I hit that it started to load an incomplete backup and the reboot failed.
[Nook Color Android Development] dparrothead1:
Everything I have read on other boards indicate CM11 works better with CWM. I am running 4.4 roms on my Infuse, Captivate and Note 1 and installed using CWM on all three.
[Nook Color Android Development] :
As long as you have an updated TWRP recovery KitKat works great. I flashed slimKat on my Note 2 using TWRP and have had zero issues.
[Nook Color Android Development] drmarble:
Boot animation fix

To fix the boot animation you can add the following lines to encore.mk:

# Fix boot animation
PRODUCT_COPY_FILES += \
vendor/cm/prebuilt/common/bootanimation/600.zip:system/media/bootanimation.zip

This change also fixes the animation on cm-10.2.

It is unclear to me why this isn't automatically set correctly for the new boot animations but it isn't. We seem to be using the tablet default of 800.zip. I would submit this as a fix to gerrit but I think that it should be fixed upstream somewhere in vendor/cm/config/*.mk.

Anyway, this change will fix the boot animation. Good enough for non-official builds.
[Nook Color Android Development] fattire:
Can you submit via gerrit for 10.2 and 11.0?
[Nook Color Android Development] drmarble:
FatTire:

I can submit it but it will break next time they change bootanimation names. I guess we can always revert it later. Time to repo start....
[Nook Color Android Development] weldawadyathink:
So I built a new version of TWRP for the nook, but it seems that you need a new theme and so it's all wonkey. I'll check to see if I can find one now.
[Nook Color Android Development] drmarble:
Boot animation patch submitted.

Re: Boot animation patch.

I submitted a patch to gerrit for cm-10.2 and a pull request to NookieDevs for cm-11.0. I think that was my first pull request so be kind if I messed up.

I still think that there is something wrong in how cm assigns boot animations. The tablet make (800) overwrites the main make that looks at screen size.
[Nook Color Android Development] leapinlar:
Rather than clutter up this CM11 thread with help to revive your seemingly dead nook, let's move this discussion to my NC Tips thread linked in my signature.
[Nook Color Android Development] tdm:
Here is another sdcard solution...

https://github.com/pacerom/system_vold/commit/4527947586bff311a0d8ef9dbd46295bac64fe38
[Nook Color Android Development] pastordl:
Problem with CWM 6.0.4.5 recovery zip

I tried this recovery. It flashed fine but defaults to sdcard0 mounted. Workable manually by umounting card 0 and mounting card1 but will not work with Rom manager, or other managers. This makes it useless to me since I update nightlies and use Rom manager to save steps and let the nook do the work and return to a rebooted, backed up and updated nook with out my further attention. Yes I am still on CM 10.2 but wanted to be prepared for CM 11 when available. I would anticipate the same problem whit CM 11 then.

Is it possible to get a 6.0.4.5 zip that defaults to SDcard1 mounted?
[Nook Color Android Development] Arbelzapf:
Could anyone shed some light on what to do to enable OC to 1200mhz in the kernel? (Or is that a bad idea at the moment? I never had a single issue with the cm10.2 test kernel, so I'd like to have it back)

I was able to build myself, but I know next to nothing about cherrypicking specific commits and so on. Could someone let me in?
[Nook Color Android Development] kcls:
Hey guys, sorry to intrude. I'm trying to build, and the breakfast encore command isn't working. Any suggestions? Here's what it gives me.

including vendor/cm/vendorsetup.sh
ls: cannot access device/*/encore/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_encore". Stop.
Device encore not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_bn_encore
Default revision: cm-11.0
Checking branch info
Default revision cm-11.0 not found in android_device_bn_encore. Bailing.
Branches found:
cm-10.1
cm-10.1-staging
cm-10.2
gb-release-7.2
gingerbread
gingerbread-release
jellybean
cm-10.2-M1
cm-10.1.3-RC2
cm-10.1.3-RC1
cm-10.1.3
cm-10.1.2
cm-10.1.1
cm-10.1.0-RC5
cm-10.1.0-RC4
cm-10.1.0-RC3
cm-10.1.0-RC2
cm-10.1.0-RC1
cm-10.1.0
cm-7.1.0
cm-7.0.3
cm-7.0.2.1
cm-7.0.1
cm-7.0.0
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
ls: cannot access device/*/encore/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_encore". Stop.

** Don't have a product spec for: 'cm_encore'
** Do you have the right repo manifest?
[Nook Color Android Development] Arbelzapf:
You seem to be missing the NookieDevs repository in your local manifest.

http://xdaforums.com/showpost.php?p=47765270&postcount=3572
[Nook Color Android Development] kcls:
Thanks, just tried that and I'm still getting the same error :/

Edit: I'm getting the same error as the guy on that page, not the original one I was getting. But that had changed already after I did another repo sync.
[Nook Color Android Development] anapospastos:
I'm extremely interested in cherry picking commits too. I googled enough but I couldn't find a comprehensive guide. It would be great if someone could point us to something useful.
[Nook Color Android Development] Arbelzapf:
You need to repo init again after changing your manifest

Then repo sync and try again
[Nook Color Android Development] kcls:
Did that too. Still getting the same error. Ugh lol

I'm back to the original error though. I have the roomservice.xml in /android/system/.repo/local_manifest, I did everything from "Initialize the CyanogenMod source repository" in the cyanogenmod wiki. Still getting that original error.
[Nook Color Android Development] Arbelzapf:
I'm no expert (only recently did my first build as well) but this definetely looks like a local_manifest related problem to me.

It cannot find any device-specific code, because it wasn't told to fetch it, defaults to looking in the official CM repos and since there's no official Kitkat branch there, it throws an error.

Can you post your roomservice.xml?

---------- Post added at 06:38 PM ---------- Previous post was at 06:00 PM ----------

Here's what I could find:

Gerrit:

http://http://xdaforums.com/showpost.php?p=23527685&postcount=29

Github

http://stackoverflow.com/questions/1405030/using-git-how-can-i-selectively-pull-merge-changes-from-anothers-fork

Now I need to dig up the commits that add 1200 oc :/

EDIT: Oh wait, this was only in a test kernel right? Is there even something to pick on NookieDevs? How do others do it?
[Nook Color Android Development] fattire:
See here.
[Nook Color Android Development] kcls:
It's a file in ~/android/system/.repo/manifests called "roomservice.xml" and it contains this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_bn_encore" path="kernel/bn/encore" remote="github" revision="encore-omap3-3.0.y" />
</manifest>
[Nook Color Android Development] Arbelzapf:
Hm, shouldn't it be in "local_manifests"?

http://wiki.cyanogenmod.org/w/Doc:_Using_local_manifests

Maybe your file isn't being picked up at all

EDIT: Can you guys build? After syncing, I get the following:

target Strip: libexif_jni (/home/biont/android/system/out/target/product/encore/obj/lib/libexif_jni.so)
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:299: error: undefined reference to 'wpa_ft_mic'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:34: error: undefined reference to 'wpa_derive_pmk_r0'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:41: error: undefined reference to 'wpa_derive_pmk_r1'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:46: error: undefined reference to 'wpa_pmk_r1_to_ptk'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:70: error: undefined reference to 'wpa_ft_parse_ies'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:410: error: undefined reference to 'wpa_ft_parse_ies'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:471: error: undefined reference to 'wpa_derive_pmk_r1'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:479: error: undefined reference to 'wpa_pmk_r1_to_ptk'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:688: error: undefined reference to 'wpa_ft_parse_ies'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa_ft.c:769: error: undefined reference to 'wpa_ft_mic'
external/wpa_supplicant_8/wpa_supplicant/src/rsn_supp/wpa.c:300: error: undefined reference to 'wpa_insert_pmkid'
collect2: error: ld returned 1 exit status
make: *** [/home/biont/android/system/out/target/product/encore/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant] Error 1
[Nook Color Android Development] unibroker:
Am I applying this patch to my AndroidManifest.xml file at this location? Assuming I am I can apply this patch at the end as long as it is before the final

</manifest>

?
[Nook Color Android Development] weldawadyathink:
You never modify any manifest file except roomservice.xml. Period. Ever. Unless you are going to change the official cyanogenmod manifest and you go through Gerrit. You only modify the room service file
[Nook Color Android Development] unibroker:
I have navigated per drmarble to

:~/android/system/packages/providers/MediaProvider

ls -a gives me

. .. AndroidManifest.xml Android.mk CleanSpec.mk .git MODULE_LICENSE_APACHE2 NOTICE res src tools

Where do I paste the code in his post to my build?

I am following these directions here through a link provided by one of the board sages.
[Nook Color Android Development] kcls:
Oops, sorry, yeah it is in local_manifests. Still not being picked up by a repo init and sync.
[Nook Color Android Development] weldawadyathink:
For everyone who is not in the loop, here is what the room service file should be:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_bn_encore" path="kernel/bn/encore" remote="github" revision="encore-omap3-3.0.y" />
</manifest>
[Nook Color Android Development] bowguy:
CM11 touchscreen driver?

arch/arm/mach-omap2/board-encore-peripherals.c looks like the ft5x06 driver stuff is there but there is nothing about it in Makefile or Kconfig.in the CM-11.0 repo.

Could this be the issue I am having?
[Nook Color Android Development] unibroker:
I built last night and the boot animation is fixed but the

android.process.media has stopped

still persists.
[Nook Color Android Development] steven676:
Strange, but no, I don't think so -- the kernel is identical to the one we're using for CM10.2 nightlies at the moment.

The patches quoted above for this issue were rejected by CM because (among other things) they break mounting of non-FAT filesystems. You'll need to apply them to your build yourself, or (better yet) fix/reimplement the patches so that they can be merged upstream.
[Nook Color Android Development] tdm:
Yeah that patch won't be merged as is. But I'm sure there will be a solution soon. I'll work on it Monday if nothing shows up by then.
[Nook Color Android Development] weldawadyathink:
Room service is essentially the same thing as local manifest. To mount /boot, you have to be in recovery and then push with adb. You can name them uAltImg and uAltRam and then boot them from cyanoboot by selecting alternative, if you want to keep your current recovery.
[Nook Color Android Development] moocow1452:
Ok, was afraid of that. Dropping that text into an otherwise empty file at ~/android/system/.repo/local_manifests/roomservice.xml doesn't do jack squat when I tell it to breakfast encore. Should I try and manually git the code, put it into the directory tree and see if I can resume builds after that, or is there a more involved fix?
[Nook Color Android Development] Zippy Dufus:
I am using Clockworkmod Recovery v.3.2.0.1 and my laptop is Fedora 19 Linux x64 using adb from the Fedora repositories (android-tools-20130123git98d0789-1.fc19.x86_64) and I don't see a device when my Nook is plugged in the USB.

I perform the following:

boot into recovery

navigate to "mounts and storage"

mount /boot

plug the usb cable into my Nook

on laptop "# adb devices -l" and see no attached devices

adb works fine when I have cm10.2 running with adb debugging turned on.

So I am still stuck.
[Nook Color Android Development] weldawadyathink:
Somebody earlier in the thread made a flash able zip for the new recovery, have you tried that? And you only need to do the alternative thing I posted if you don't like cwm and rather have twrp as the main recovery.

For the guy two posts up, did you repo sync after adding that file? If not, try that and then brunch. If you still get an error, pm me.

We really need to make a build guide to help alleviate problems like these. I may do that when I get the chance.
[Nook Color Android Development] Zippy Dufus:
Looks like I'm too late. The attachment on this post is gone.
[Nook Color Android Development] unibroker:
It generated an error when I tried to use it.
[Nook Color Android Development] Zippy Dufus:
DANGER! ... Amateur recovery

I figured out how to build a flashable recovery and, surprisingly, it worked for me. My very first zip, wow!

It is available here: http://www.mirrorcreator.com/files/0YJOTSMN/cm11-encore-recovery.zip_links

USE AT YOUR OWN RISK!!

Enjoy!

== edit ==

Another user has reported issues 2 posts down - beware!. Here are the checksums:

$ sha1sum cm11-encore-recovery.zip
5367b3cdb11afb75e26901aca7d6c330d2aa6b40 cm11-encore-recovery.zip
$ sum cm11-encore-recovery.zip
50418 6430
[Nook Color Android Development] steven676:
Plug the USB cable in, unplug it, then plug it in again. This is a known bug in the 2.6.32 kernel used by CM7 and many of the older recoveries.
[Nook Color Android Development] pastordl:
Tried the zip and it failed failed to install. CWM. returned that the zip could not be open and zip was bad.

edit: thanks for the checksum. It was a bad download. Installed fine. Does default to sdcard0 being mounted though. Works fine manually but doesn't function with Rom manager to backup and update unattended.
[Nook Color Android Development] Zippy Dufus:
Sorry to hear that. All I can suggest is that you inspect the checksums of the file you downloaded. I downloaded it and compared to what I actually flashed and they are the same. (Sorry about the obnoxious file-sharing site that I used, too!)

Otherwise, I have no idea why it doesn't work for you.

$ sha1sum cm11-encore-recovery.zip
5367b3cdb11afb75e26901aca7d6c330d2aa6b40 cm11-encore-recovery.zip
$ sum cm11-encore-recovery.zip
50418 6430

== // ==

Meanwhile, I managed to install my cm-11-20131201-UNOFFICIAL-encore.zip ROM.

It's not ready for prime time yet:

It often get "Unfortunately, the process android.process.media has stopped". It appears to hate my 16GB sdcard.

I cannot change wallpapers: "Unfortunately, launcher3 has stopped" yet it appears to have retained my jellybean theme wallpaper despite a clean flash. The image itself is really poor. (I used titanium to restored my apps and system data only - the system part may be a problem.)

S - L - O - W to boot up.

Good news is that all my favourite apps appear to be working fine: Tuneit, corporate email and calendar, various newspaper and magazine apps, the stock browser (except incognito mode which is a known issue).

I am going to try reflashing the ROM and play with it before I restore anything.

Cheers
[Nook Color Android Development] aperezdc:
The MediaProvider needs patching. For the moment we have patches which solve the issue in the thread. As mentioned, as soon as a generic solution that does not break other partition types is posted to CM, this will be solved for everybody.

Changing wallpapers does work in my plain AOSP builds. You may want to try wiping and doing a clean install, then changing the wallpaper before restoring any system data using Titanium Backup and see whether that works.

Here it is indeed very slow to boot up, but mostly the first boot (or the first boot after switching runtimes). Then the system is still sluggish for some moments until the Dalvik (or ART) cache is filled up for the applications and services which are run at bootup. Considering the specs of the Nook Color, it looks amazing to me that it is running current Android versions. Certainly I would not call it a blocker for release that first boots are slow in such hardware :)
[Nook Color Android Development] Zippy Dufus:
Thanks, it is good to know that the media provider is not my issue.

I just went through my entire reflashing procedure, including reflashing my recovery zip, and all worked fine. I performed a factory reset, clear cache and clear Dalvik cache from both the old and new recoveries. I still have problems setting the wallpaper for both launchers although Launcher reported a "Google search" error but I just noticed that it is automatically updating g+.

The device is now in a pristine state as all I have done was to add my Google account. I'm letting it charge up, then unplug, leave it alone, and watch its battery usage for the next day.

Probably in a week or so, I will do another build. I have built a cm11 ROM for my old Samsung Galaxy phone and I'm hugely impressed by its performance so I am hopeful that cm11 will bring new life to the Nook Color!

Cheers.
[Nook Color Android Development] Arbelzapf:
I believe this went largely unnoticed. It's still stopping me from building. Can anyone help me please?
[Nook Color Android Development] kcls:
I'm having a problem where the nook isn't recognized by ADB, so I can't pull the proprietary files. Typing adb devices in a windows command prompt gives be the ID and the device, but typing adb devices in the ubuntu server shell gives nothing under "List of Devices Attached:"

Any pointers? ADB is in my path of execution.

Edit: Got it, but now it's showing ??????????? no permissions when I type adb devices.
[Nook Color Android Development] Zippy Dufus:
I always pull the proprietary files from a ROM like the one I am trying to build. I unzip the ROM and tweak the extract script.
[Nook Color Android Development] fattire:
Did you try repo syncing and doing it again? I think there were some supplicant errors that went away a few days ago...
[Nook Color Android Development] tdm:
Yes I had the same problem. I just reverted to a working point temporarily.
[Nook Color Android Development] unibroker:
When I've gotten that I unplug and plug in again (making sure the NC screen is on) and adb devices then has the correct output.
[Nook Color Android Development] Arbelzapf:
Just before I posted again, yes. Will try again soon. I don't come near my desktop during the week :)
[Nook Color Android Development] polymath257:
Which OS are you using? You may need to have a udev rule for the Nook Color. Also, starting adb as root (using sudo, for example)

can help the permissions problem.
[Nook Color Android Development] polymath257:
After some issues with manifests, roomservice, and having the wrong version of java, I was finally able to get cm-11.0 to compile. I put it on a verygreen SD card and it appeared to install fully. Now it is stuck on the boot animation. Hearing about the slow boot, I waited about 20 minutes and was still on the animation. When I tried to use twrp 2.3.1 to install the zip file to emmc, I got an error and it would not install.

Any recommendations?
[Nook Color Android Development] :
You need to update your emmc recovery for you to flash 4.4.
[Nook Color Android Development] polymath257:
Is there any way to make this into a SD card install?
[Nook Color Android Development] leapinlar:
Not currently. Once development gets further along I might be able to modify the SD image so it works with CM11. Right now I don't understand what is different so that I can do that. And obviously something is very different to require a new recovery to install to emmc.
[Nook Color Android Development] polymath257:
I realize I am but an egg in this, but is there any way I can help out? I would like to learn how to do more than I can currently do and this seems like an interesting place to start. Or would you suggest another project?
[Nook Color Android Development] leapinlar:
If you could post your build somewhere private and send me the link via PM, I could look at the code to see what I can find. All that really has to be done is understand the partition mounting so I can modify the SD image. The script in the SD image dynamically changes those mount points so that it works on SD.

Edit: Bowguy just sent me his so you don't need to. Thanks bowguy. I will take a look at it.
[Nook Color Android Development] leapinlar:
Ok, I found the issue. There is a new command (set_metadata_recursive) in the updater-script in the CM11 zip that replaces the old command (set_perm_recursive) for setting file permissions. This new command is why you must use a new CWM to flash the zip. The old CWM cannot interpret that command.

So my challenge is to figure out how to get the installer script in the SD image to interpret that command. May take a while.