yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] maltydog:
A friend of my has a Nook Color which I rooted and put

on Cyanogenmod a while ago. It is currently on 10.2

(20140107 Nightly). I offered to update it the Cyanogenmod 11.

I have it for a few days to do the update. The recovery

was TWRP. I think it was 2.1, but I am not sure. Anyway,

I tried upgrading to 11, and I forgot that I needed to update

the recovery first, and of course that didn't work. Luckily,

I had done a nandroid backup first, and was able to get

restore it. So I tried to install a later version of TWRP.

I found 2 later versions; 2.3.1.0 and and 2.6.3.0. I tried

installing them from within TWRP, but they both failed

to install. Not sure why. I installed Goomanager

and tried installing the latest TWRP with that, but the

program said there was no recovery for my device.

So then I downloaded a later version of CWM, 6.0.48,

which I was able to install from the older TWRP recovery.

So I was all set to install CM11, but now I am running

into another issue. The volume rocker buttons do not

seem to be responding at all. I hit them up and down

and the cursor in the recovery does not move at all.

So of course I cannot make any selections in recovery

except to reboot the phone.

Even when the tablet is on, the volume buttons seem

to have no effect on the sound so it may be hardware

issue with them; I'm not sure, as I said it's not my tablet,

and I contacted my friend who owns this and she said

she was not sure if the volume buttons were working

as she rarely listens to music on the device.

So this puts me in a quandary. My original plan was

to give this tablet back to my friend tomorrow with

CM11 installed, but I'm not sure what the best step

would be to get this done.

Any help from the knowledgeable folks on this

forum would be appreciated!
[Nook Color Android Development] hwong96:
Check out the touch cwm recovery in pastodl's thread

http://xdaforums.com/showthread.php?p=50438687&nocache=1
[Nook Color Android Development] maltydog:
I assume that is one of these:

File Type: zip	cwm-touch-6.0.4.7-Mar28-encore.zip - [Click for QR Code] (28.1 KB, 35 views)

File Type: zip	cwm-touch-6.0.4.7-Mar28-encore-ALT.zip - [Click for QR Code] (28.2 KB, 12 views)

Which would I use the regular or the ALT?

Also, maybe this is a really stupid question, but how can I install this zip in recovery when I can't

get the volume bars to work in the recovery I currently have? I seem to remember that there was

a rooted app that would reboot and install recovery files, but I can't for the life of me remember what

it was.

Edit: The app I was thinking of was Flashify. Does anyone know if that works on this device?
[Nook Color Android Development] hwong96:
The first zip is the right one to use if you indeed have a nook color. Please read post #3 to determine if you are in the right forum. Specifically FAQ "I can't get any roms or recoveries for Nook Color to boot".
[Nook Color Android Development] steven676:
Given the time constraint, I think the quickest fix would be to install a nightly older than May 16 -- that said, we need to restore a touch-enabled recovery to the device first. I think the fastest way to do that is from within CM10.2 itself. First, on the tablet, via either adb shell or Terminal Emulator ($ and # represent command prompts, not something you type):

$ su
# umask 022
# mount -o remount,rw /
# mkdir /boot
# mount -t vfat -o uid=2000 /dev/block/mmcblk0p1 /boot

Now grab the recovery ZIP and unpack it; you'll find files called "kernel" and "ramdisk-recovery.ub" inside. To install the recovery, copy "kernel" to /boot/uRecImg and "ramdisk-recovery.ub" to /boot/uRecRam (you can use the CM File Manager, adb push from a computer, or the shell).

With that done, you can flash any CM11 build from May 15 or earlier using the recovery.
[Nook Color Android Development] maltydog:
Thanks for your helpful suggestions. I have to admit, however, I am a bit confused.

When you say grab the recovery ZIP and unpack it, you mean the file mentioned earlier,

the zip cwm-touch-6.0.4.7-Mar28-encore.zip, right? I tried unzipping it, and I do not see any

files called "kernel" or "ramdisk-recovery.ub". Is that the wrong file?
[Nook Color Android Development] steven676:
Do you instead have files called "uRecImg" and "uRecRam"? If so, copy those to /boot.
[Nook Color Android Development] hwong96:
You could try TWRP 2.63 encore signed zip also. I think the cwm touch zip is just the touch overlay for cwm 6.0.4.7 encore zip. I dont 't use cwm touch so I may be wrong.
[Nook Color Android Development] maltydog:
Yes, they are both there. I'll give it a try I guess.

So, terminal emulator, type those commands,

move the files, and then what, reboot into recovery?

That it?

Update: Worked, thanks a lot, I have the touch CWM on now.
[Nook Color Android Development] bowguy:
Just finished the upgrade on an SD install. Worked like a charm. New recovery installed 5/16 zip from Cyandelta directly to SD card. Faster install as it only updated apps from zip instead of all. Very nice.
[Nook Color Android Development] volpo222:
I used the automatic updater for the first time (on my SD install) after I updated the recovery.

Nice!

Thanks to everyone working on this!

A day later: Tried CyanDelta, works great too!
[Nook Color Android Development] pastordl:
Great job developers

Ever since the trebuchet update I have noticed a decrease in stability. Particularly when using browsers, Dolphin or stock, with multiple tabs, or the YouTube app. Anything more than three tabs would likely crash. YouTube in HQ would also crash after several minutes. Had even reduced the clock to 800mhz.

I installed 5/17 this AM. Wow, can't make it crash. 20 tabs open no problem, either browser. YouTube no problem. Knew you would work out the bugs.

And you sure did. Smooth, fast, back at 1100mhz and better than ever.

Thanks again. :highfive: :o :good: :laugh: :angel:

Edit: And with nightly 5/22 the disappearing wallpaper choice on cold boot has been fixed. Another thanks!
[Nook Color Android Development] pastordl:
Cm11 twrp blues

[MENTION=2687009]eyeballer[/MENTION]

CM11 without a usable TWRP recovery.

:crying::fingers-crossed::confused::eek:

CM11 with a usable TWRP recovery.

:laugh::highfive::good::):victory::cool:

Trying to patiently wait for the updated TWRP,

("YAH, RIGHT")

If you could use a beta tester to check it out, mark me as a volunteer.
[Nook Color Android Development] bigbob23:
I miss TWRP but have found CWM to work fine for updating with Cyandelta. I haven't tried it for anything else, however.
[Nook Color Android Development] steven676:
Having gotten no feedback on this either way, I've gone ahead and merged a change to start reporting a GPS and microphone again. As noted above, the Market appears to do some kind of server-side caching for app compatibility, so even after you upgrade your ROM, it'll take a couple of days before Market will notice the changes. In any event, if you've upgraded to a nightly from May 27 or later, waited a few days, and are still not seeing an app that you used to see on Market before the hardware features changes, grab a copy of the APK, use aapt to get the hardware features the app needs, and post the output.
[Nook Color Android Development] hliew88:
It took until today for all the apps to reappear! I don't seem to be missing any - thanks =D

I'm still getting SOD, however. If I flash a new nightly on battery power, it SODs immediately, but if I flash a new nightly while charging, it takes about half to a whole day for it to start SOD-ing again. When it starts SOD-ing doesn't seem to coincide with using any particular app - it just starts doing it at random. Anything I can do to try to pinpoint the source?
[Nook Color Android Development] EAK128:
No SODs for me, running the June 1st nightly.
[Nook Color Android Development] viskon:
Looks like is been updated to 4.4.3 without any fanfare.

Is it going to be called CM 11.1 ?
[Nook Color Android Development] polymath257:
So far 4.4.3 is working well for me. I did a dirty flash from cm11-M6.
[Nook Color Android Development] pastordl:
4.4.3 running great on mine and my wife's Nook. Wow less than a week from the release date too.

Thank you developers for all your hard work.
[Nook Color Android Development] viskon:
Same sentiments here. My Nook is running much better than it has in the last few years. Thank you all , that made this possible.
[Nook Color Android Development] CSouthwick:
Physical Volume buttons broken - ideas on flashing

Hello,

I have CWM 6.048 installed however the physical volume buttons on my nook are unresponsive. TWRP doesn't work for the latest CM 11. GooManager reboots, but then CWM doesn't flash the rom, it just hangs.

Any ideas for flashing CM 11 updates?

Thanks either way
[Nook Color Android Development] pastordl:
problem with 6-11 nightly

I have tried twice installing the 6-11 nightly. Did check the MD5 and tried a fresh download on the second install attempt. The install goes ok, but if any reboot is used except full power off the wallpaper is reset to the default with the big "O". Any attempt to change the wallpaper causes a reboot to some point after the boot loader. Which then causes the media provider to go into its chronic shut down mode. Clearing it's data cache and doing a power off and restart will fix this till the next reboot is used ie: NSR, Xposed, or reboot to recovery to do a backup. This is similar but worse than it was before 5/17 nightly. Will revert back to the M-7 snapshot for now which had no problems. I am using the Nova Launcher but was running fine with it from 5-17 up to the M7. I know before 5-17 the disappearing wallpaper choice started with the modified trebuchet launcher. and yes I do have the new themer frozen per recommendation on Nova.
[Nook Color Android Development] ericjmcpherson:
This has probably been mentioned, but be sure to use the 'Micro' gapps, as the others won't fit on the system partition.
[Nook Color Android Development] bowguy:
Strange. I had the identical android.process.media behavior with the 6/7 nightly. It eventually calmed down after a day. I installed the 6/11 nightly and had no issues. Note Gmail just updated around this time too.
[Nook Color Android Development] volpo222:
I'm having trouble with 6/11 as well. I get repeated trebuchet has stopped errors. This also happened before, could have been 6/7 but it stopped after a re-start.

I have an image of my NC from 4/3 that works fine. I guess I'll try m7 and see what happens.
[Nook Color Android Development] pastordl:
Ok, I defrosted Gmail, it updated. Then tried the 6-11 nightly. Wiz bang it works, even with Gmail frozen. Lucy, you got some splainin' to do. What would Gmail have to do with choosing wallpaper?

Thank you bowguy, didn't make sense but it does work????

:confused::rolleyes::D
[Nook Color Android Development] bowguy:
I agree. I just know the process.media would constantly pop up and you hit ok and move on. However when it popped up during Gmail and you hit OK it would FC Gmail every time. No issues now in days.

Edit: Found this: http://www.techzilo.com/fix-android-process-media-has-stopped-force-close-crash/

Edit2: FYI What finally worked for me was removing all the updates to Play Store and revert back to factory version. This is mentioned as well in the post above
[Nook Color Android Development] bigbob23:
While I would like to see a TWRP update, CWM has been working well with CyanDelta for my updates. What I like about CyanDelta is that it only needs to download a "diff" file instead of the full ~170 MB each time. I don't need to touch the volume buttons to do this.
[Nook Color Android Development] CSouthwick:
Thank you very much. I was about to give essentially up my nook color. With a volume widget I have my tablet back.
[Nook Color Android Development] webyrd:
I think this is probably the best way to go. I had contacted 8 app devs about this, two replied:

One basically said that they did not plan to support tablets;

the other tried to get me to clear chache, data resets, etc to get the app to load - did not really seem to understand the issue.

All the apps that I use that are "not compatible" with the NC run fine when side-loaded.

The M7 snapshot seems to be running very well on my NC.

On a side note, I got a Nexus7 for my birthday, am going to let the grandkids use the NC, probably will not check in here as often - [MENTION=4353291]steven676[/MENTION] - if you need something tested on the hardware/firmware version that I have, let me know by PM - I will "borrow" it back.
[Nook Color Android Development] pastordl:
Status bar clock problem

Have noticed a problem with the status bar clock that started after 7-11 nightly. The problem is the placement of the clock. After any reboot or start up the clock comes up in center. It appears that other choices aren't saved. I have had it hidden since I use another clock app. I have tried disabling the clock app, no change, setting the status bar setting to default, etc with no results,. This is not a major problem but is a pain. Every start up requires a trip to setting, change to center and then to hidden to get rid of the sb clock.

Did notice in the change logs for 15th & 17th changes were made dealing with centering the SB clock. Hopefully someone can gind and fix the problem.
[Nook Color Android Development] hwong96:
I haven't come across the clock issue. I have been flashing the nightlies regularly. Attached screen print shows clock at default. If I choose center it moves to center. When I choose default it moves to the right again.
[Nook Color Android Development] pastordl:
Try setting to "hidden" then rebooting or power off and restart. That is when it comes up with clock at the center. The hidden setting is not surviving shut down or reboot, it did with 7-11 and prior.
[Nook Color Android Development] hwong96:
You are correct. I set it to hidden,rebooted, clock shows up in center AND default position.

See attached screen print. Definitely a flaw.
[Nook Color Android Development] pastordl:
You got it. With my SB app it over rides the default placement. With it off I get both also. Glad to know it's not just me.
[Nook Color Android Development] dweaton:
I am having a problem trying to install the CM11 nightly using the information in post #1 of this thread.

Background information that might be helpful:

- previously had CM10 installed

- used leaplinar (sp?) script to clear and reformat the partitions

- created a bootable SD card

- copied the zip file for cwm 6.0.4.8 as noted on the right hand side of the top of this thread

- put the SD card in the Nook Color and powered it up

- This may make a difference - I don't know: it comes up with the cyanogen boot loader and then eventually boots the SD card from that

- installed cwm 6.0.4.8 and rebooted - it still goes to cyanogen boot loader if that makes any difference

- tried to load the 07202014 nightly - it aborts almost immediately saying the file is in error. md5sum was checked from the actual SD card and is ok

- tried to load the 20140716 nightly - get the same errors

What do I actually have to do to install CM11? This is the only How-To or tutorial I have found anywhere. I've tried with a version of twrp - but apparently it is at too low of a version to install CM11 - wanted md5sum files so I created those and it starts, then aborts. I thought this cwm 6.0.4.8 was supposed to allow me to do it.

Right now I'm frustrated with myself because I have spent many, many, many hours trying to do this and can't get it to work. Also, when I click on the nightly link it doesn't go back as far a May - it's only showing July.

Any help, any straight forward "push this button" kind of instructions would be greatly appreciated. I really don't want to go to the trouble of installing cm10 again and want to just get this working. I'm at the point of feeling pretty stupid and inept.

Thanks in advance!

Dave ;)
[Nook Color Android Development] pastordl:
Boot up holding the "n" button w/o the sdcard in. Insert sdcard. Choose emmc recovery in bootloader. Make sure you are in 6.0.4.8 (will be listed on top}. Then install from sdcard1. Make sure you install with the 6/6 gapps.
[Nook Color Android Development] dweaton:
Thanks for the reply. Here's the state of things:

(1) booted using the internal emmc. It shows "CWM-based Recovery v6.0.4.8. It also show some errors right away if they make any differenc of not:

- E:Can't mount /cache/recovery/command

- Managing an eMMC installation

- E:Can't mount /cache/recovery/log

- E:Can't open /cache/recovery/log

- E:Can't mount /cache/recovery/last_log

- E:Can't open /cache/recovery/last_log

- E:Can't mount /cache/recovery/last_install

- E:Can't mount /cache/recovery/last_install

(2) I then chose "install zip"

(3) I put the cm11 zip and the gapps zip on a already formatted SD card that has my file from previous install on it, so I selected "choose zip from /storage/sdcard1

(4) scrolled down and selected "cm-11-20140608-SNAPSHOT-M7-encore.zip"

(5) scrolled down and selected the gappz zip file

AND.......

IT WORKED!!

Thank you SO MUCH!!

Dave ;)
[Nook Color Android Development] dweaton:
I guess I spoke a little too early. Both files installed fine, but on reboot it appears "stuck" in the cyangenmod startup. I get the "evil looking" droid face with the arrow circling it at various speeds, but it never stops and goes to a desktop. I waited 15 minutes the first time, then powered it off. On power up again it's been like that for over an hour.

Perhaps I did this somehow? I had tried the newer cm11 nightlies with no luck, so for this attempt I had used the 06/08 M7 snapshot. I read something online about the "M" nightlies but honestly don't understand a thing they are talking about. Perhaps I should go back and clear the partitions again, install 6.0.4.8 and then use the latest nightly again?
[Nook Color Android Development] leapinlar:
No need to clear partitions. Just boot to CWM and factory reset.
[Nook Color Android Development] dweaton:
Thanks for the quick response! I have done the factory reset and installed the 7/20 nightly and gapps (didn't know if I had to do the gapps again or not). At any rate, rebooted and it stayed on that screen for a while but finally came up!

Thanks!

---------- Post added at 08:45 PM ---------- Previous post was at 08:38 PM ----------

I think I did something wrong again - I don't see Google Play or what the Google store is called now. Can someone point me to what I did wrong and how to correct that?

Thanks in advance!

Dave
[Nook Color Android Development] pastordl:
Try reinstalling gapps. Make sure it is the 6/6 gapps from

http://wiki.cyanogenmod.org/w/Gapps.

Any other {earlier} won't work.
[Nook Color Android Development] dweaton:
That's what I've been using, but I went ahead and downloaded it again and verified the md5sum. Copied to microSD, booted internal emmc, installed the zip file, rebooted, and still no store. I've got gmai, google+, maps, people, play games, play movies & TV, play music, play newstand, but no store. I must be missing something along the way. This isn't one of those intermediate gapps where Google wasn't allowing access is it?
[Nook Color Android Development] steven676:
Could you open up Terminal Emulator, type in "df" (without the quotes), press enter, and provide the output?
[Nook Color Android Development] dweaton:
That list is a little difficult to re-type. If there is a specific mount point you are looking for please let me know. In the mean time, I may have an idea of why it's not working: I never got my google account defined to cmod11. Do I need to go back and re-do everything? I looked under settings/accounts but don't see a way to enter in my existing google account.

---------- Post added at 10:54 PM ---------- Previous post was at 10:41 PM ----------

Also just found the following:

trying to access any of the "Play" apps results in it saying that google play is not supported on my device. huh?
[Nook Color Android Development] dweaton:
Cleared the partitions using leapinlar's (sp?) zip file, installed 10.2 and appropriate gapps. On reboot, the setup asked for my google account. That never happended when I was trying to load cm11. So, I assume I did something wrong. I noticed in 10.2 it comes up and says I have some updates available - 3 for cm11. Should I try just doing one of those updates?
[Nook Color Android Development] freonchill:
first of all, thanks to all of the developers who keep pounding away on this updates for this hardware. it my first android device and has worked well since cm7 to 10.x...

i have read several topics here regarding upgrading to cm11. i am currently running cm10 on my emmc. i upgraded cwm to 6.0.4.8 so that i could install cm11 on it and noticed a comment about using the mini-gapps rather than the normal. i started researching and found issues with not enough space for the gapps causing problems. i have an early nook color (not nook tablet or later/newer nook models) and of the top of my head cante remember what the current partition sizes are (1/5 or 5/1), but cant find a definite answer of what they should be for cm11.

i come at this from recently upgrading my touchpad from cm10 to cm11 and remember reading how on that device (and perhaps all cm11) merged data/media partitions.

i hope that bringing this up does not confuse anyone, i am just looking for the correct partition sizes for cm11 on emmc, not sd.

note: and it does seem the most of the comments i have been reading say that i should use an older than cwm 6.0.4.8 to use the re-partition recover zip files and it looks like the most effective way to do that is to re-create a bootable sd card and install a previous version of cwm to use as a re-partition device. re-partition, install cm11 and put in a blank sdcard for /media, right?

can someone please direct me to the post and or advise what size partitions are ideal for cm11 / emmc install?

thanks
[Nook Color Android Development] steven676:
Long-press on the terminal to get a context menu, from where you can copy the text. Alternately, do "df > /sdcard/output.txt" and copy output.txt from your SD card.
[Nook Color Android Development] leapinlar:
The issue with partition size on the NC is with the small size of /system. None of the repartition zips change that. They only affect /data and /media so don't bother, just use the smaller gapps.

And the merged /data and /media is for other devices. The NC stays the same.
[Nook Color Android Development] dweaton:
I don't know why I didn't just pipe the output in the first place - I guess i was just to frazzled at the time. I also tried blkid but I don't know if Android does things differently from linux or what, but there was no output from that.

Filesystem Size Used Free Blksize

/dev 224.0M 64.0K 223.9M 4096

/mnt/secure 224.0M 0.0K 224.0M 4096

/mnt/asec 224.0M 0.0K 224.0M 4096

/mnt/obb 224.0M 0.0K 224.0M 4096

/mnt/fuse 224.0M 0.0K 224.0M 4096

/system 447.8M 405.2M 42.6M 4096

/data 941.9M 195.6M 746.3M 4096

/cache 347.4M 103.3M 244.1M 4096

/rom 69.5M 311.5K 69.2M 512

/storage/sdcard1 297.4M 272.3M 25.2M 4096

/mnt/secure/asec 297.4M 272.3M 25.2M 4096

The sdcard I 'm using is a bootable TWRP. Please note I had to overwrite it to install 10.2 so I could do this again. Something tells me you'd prefer the output from cm11 ;) I'll try to reload it a post that data back as well.

EDIT: Here's the output when cm11 from 7/20/2014 is installed. Still no GooglePlay store.

Output of df:

Filesystem Size Used Free Blksize

/dev 223.1M 136.0K 223.0M 4096

/sys/fs/cgroup 223.1M 0.0K 223.1M 4096

/mnt/asec 223.1M 0.0K 223.1M 4096

/mnt/obb 223.1M 0.0K 223.1M 4096

/mnt/fuse 223.1M 0.0K 223.1M 4096

/system 447.8M 447.8M 8.0K 4096

/data 941.9M 140.3M 801.5M 4096

/cache 347.4M 16.3M 331.1M 4096

/rom 69.5M 311.5K 69.2M 512

/mnt/media_rw/sdcard1 1.9G 327.3M 1.5G 4096

/mnt/secure/asec 1.9G 327.3M 1.5G 4096

/storage/sdcard1 1.9G 327.3M 1.5G 4096

---------------------

Output of ls /storage/sdcard1:

Alarms

Android

DCIM

Download

LOST.DIR

Movies

Music

Notifications

Pictures

Podcasts

Ringtones

cm-11-20140720-NIGHTLY-encore.zip

dwe.txt

gapps-kk-20140606-signed.zip

----------------------