yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Cor-master:
Hey i gotta ask, whats the deal with multi user? Or lack thereof i should say. A Google search reveals it was removed by the cm team but no indication as to why or when or if it's coming back. The nook color is my son's tablet now want to make a restricted access profile for him but can't because there's no multi user Support.
[Nook Color Android Development] pastordl:
Wondering if or when the hwcomposer nooverlay test info might be merged into the nightlies.
[Nook Color Android Development] frankusb:
It looks like they were merged late on April 21st. Nightly 20140422 has the changes.

Frank
[Nook Color Android Development] hwong96:
Take a look at my post here. Works for CM11 also.

If you flash a new nightly once the multiuser is set up, you will have to redo the build.prop modification.
[Nook Color Android Development] steven676:
Updated test CWM recovery (install-location-agnostic!)

EDIT: Please use the new and improved version posted downthread instead of this test build,

particularly

if you're installing to SD card. The new release will tell you up front whether it's managing an eMMC or SD card installation, and will not modify the eMMC even if you attempt to install an old ROM to SD card.

There's an updated ClockworkMod Recovery 6.0.4.8 attached to this post for you to test. There are two changes here that need looking at:

The handling of the home/volume/power keys has changed; there should be no functional difference, but I'd like to make sure that we haven't inadvertently broken anyone's device.

This recovery is fully install-location-agnostic: it'll install to either eMMC or external SD, and operate on whatever it's installed to! (In other words: if you install it to eMMC, the format and backup/restore options will touch the eMMC installation; if you install it to SD card, they'll operate on the SD card instead.) This is one of the last pieces of infrastructure we need in place for easier installs and single builds that install to both eMMC and SD without change. NOTE: do not attempt to install/update a full ROM package to SD card using this recovery; see below for details.

Please test and report your results. (Source: kernel (the current tip of the encore-omap3-3.0.y branch), device/bn/encore tree (the current tip of my personal cm-11.0-oneboot branch.) I'd particularly like to see the output of (# is your command prompt, not something you type)

# ls -l /dev/block/by-name

from adb shell in the recovery, for both eMMC and SD card installs.

Install instructions on eMMC: flash the ZIP as you normally would.

Install instructions on SD card: plug your SD card into your computer and open the ZIP there. Copy "kernel" to "uRecImg" on the first partition of the SD card, and "ramdisk-recovery.ub" to "uRecRam". (Make backup copies of those files first! If you currently have the SD card installer on the SD card, those are the boot files for the installer; if you move them to "uAltImg" and "uAltRam", respectively, you can then still access the installer by selecting "SD Card Alternate" from the Cyanoboot menu.)

Note that even with this new recovery, it is not (yet) safe to install a ROM OTA package to SD card from recovery -- attempting to do so will modify the eMMC instead! We need to make some changes to the default install scripts for the ROM first. (If you want to try this out, build your own ROM using my cm-11.0-oneboot device/bn/encore tree.)
[Nook Color Android Development] leapinlar:
Can this version of CWM be used on older zips that have the old version of update-binary or will they still fail with an assert failure?
[Nook Color Android Development] steven676:
I think there's now a workaround for that issue (which has something to do with the property service) in the CWM source upstream. You'd have to check to be sure, though.
[Nook Color Android Development] TACOMPUTER:
I am currently running 7.2 Mirage, using CWM 3.2.0.1 on sdcard. How do I upgrade to CM11?

Please guide from AZ, and the link to download the file.

And later, if the CM11 running slow, can i go back to 7.2 Mirage?

Thanks.
[Nook Color Android Development] pastordl:
Check out my "need help" link in my signature below. Look under install CM11 follow that link to get step by step instructions. Make sure and use CWM 6.0.4.7 or TWRP 2.6.3.0 to install. There is a link to the Cyanogenmod download age. And the link to get the Gapps for CM11. Don't forget to do a factory reset. Yes you can go back and install 7.2 as a new install, also in my help post. Just about any help you'll need you'll find the info or a link to what you'll looking for. Check out post #4 to help get the best from CM11. I doubt you'll want to go back, I sure don't.
[Nook Color Android Development] hliew88:
I had mentioned a week or two ago System UI is crashing... turns out it happens only when pulling down the notifications when the device is low on memory. The Quick Settings panel is fine - just the notifications. It also helps sometimes to hold my finger on the status bar for a while before swiping the notifications panel down.

After it crashes, it locks the screen and clears all my notifications, which is kind of annoying =/

Otherwise, CM11 is smoother than ever!
[Nook Color Android Development] bowguy:
Cannot connect via adb at all on an SD install. Using the show log command from the advanced menu I get:

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand. file not found...

I:Can't partition non-vfat: /storage/sdcard0 (vfat)

I:Can't partition non mmcblk device: /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1
[Nook Color Android Development] webyrd:
Sorry for tasking so long, installs fine on EMMC, dirty flash of CM11 nightly had no problems, dirty flash of my last CM10.2 installed and booted OK, lots of errors due to dirty flash. Dirty flash of an old MiRaGe ROM did not work, screen went black half way through flashing, had to hold power button for 10± seconds to re-boot. Then did factory reset and formatted system, MiRaGe did same thing, started installing but screen went black halfway through. Held power button to re-boot and did clean install of CM11 nightly - no problems, just did dirty flash of new CM11 nightly, no problems.

Cannot provide ADB list, no access to PC with ADB right now, sorry.
[Nook Color Android Development] deadbot1:
I have a strange issue for at least the last 10 nightlies...sometimes when I plug my NC in while the screen is off it just locks up. I have to hold power down to force shutdown and reboot. Don't have adb setup ATM but will install and try it with the laptop if needed.

Not sure if it's similar to the old SOD or not. It sometimes happens when the screen is on but almost always when the screen is off. The charge indicator on the cable usually stays lit green when this happens. If the cable is in when the Nook reboots, there are no issues and you can watch it cycle from green to orange. If it is freshly rebooted it doesn't seem to happen, only after sitting for a fairly long time(more than an hour). the time I remember it happening when the screen was on, the indicator had JUST switched to orange, then it locked up.
[Nook Color Android Development] hliew88:
I have a potentially similar bug to report - since about the 4/28 nightlies, my NC SODs only if I have some sort of lockscreen security enabled. If I disable the lockscreen, the tablet wakes just fine. I also noticed that in this SOD stage, the processor does seem to be running hot but I cannot confirm as the only way to revive is to hard reboot like you do. Ditto on the freshly rebooted thing - it only happens after I put it to sleep after 10 mins or so.

Do you have the lockscreen enabled? I haven't run into your problem simply because I have a habit of plugging it in with the screen on only, but I suspect these bugs are related. Try disabling the lockscreen and trying again?
[Nook Color Android Development] deadbot1:
Will do. Yes I have my lockscreen on. I'll get back after I get a chance to test.
[Nook Color Android Development] hliew88:
This morning my NC SOD'd even when I didn't have a lockscreen enabled, so maybe it's something else. I'm on the M6 Snapshot, BTW.
[Nook Color Android Development] deadbot1:
yeah, disabled it this morn when I got off work, rebooted, left it sit for 5 hours while charging and had the same issue as before. I did notice this time when I plugged in that I had an effect like there were multiple touches being registered and yahoo weather came up for a sec before lockup.
[Nook Color Android Development] webyrd:
I'm on the M6 Snapshot also, no problems, but I do not use a lockscreen
[Nook Color Android Development] hliew88:
The 5/7 nightly seems to have fixed the two bugs (notifications window and SOD), but I can't see what in the changelog could have done that, however.
[Nook Color Android Development] nicenice19:
Please, if anyone can help, I'd be very grateful. I am looking to root and install CM11 on my daughter's NC. I just inherited the NC and it is bone stock. I have been reading thru the instructions here and am totally confused. I ahve rooted my phones, tablet, etc.. but have never had so many problems trying to set something up. Does anyone have a step by step guid to take me from stock to CM11. I have a 16gb sd-card to use as well that I have tried following instrcutions here http://xdaforums.com/showthread.php?t=1030227 and here http://xdaforums.com/showthread.php?t=1941858 but the Nook never boots to the sd card it just boots normally. Any help would be greatly appreciated. Thanks in advance!
[Nook Color Android Development] webyrd:
Those are the best guides that I know of, are you trying to install to the SD card or to EMMC? SD install will leave the NC stock and only run CM if booted with the SD, EMMC install will wipe stock from the NC. Your first link is for EMMC the second is for SD
[Nook Color Android Development] nicenice19:
I really don't care either way. I guess I'd prefer EMMC and then use the SD for storage. Thanks for your help.
[Nook Color Android Development] gravitysandwich:
http://xdaforums.com/showthread.php?t=1941858

Use one of his guides and if anything, just flash a recovery on the SD card, then maybe flash the EMMC recovery or just flash the rom from the SD card recovery. I Think the SD card will write to EMMC if you flash the rom, or maybe it doesn't and I forgot.
[Nook Color Android Development] hliew88:
I had to flash CM11 when I got my replacement NC last week, so there are a few caveats to the guides that you linked. The one for installing to EMMC has the SD card images for older recoveries that won't install CM11.

I like TWRP, so what I did was get the TWRP 2.3.0.2 image from http://teamw.in/project/twrp2/43, image that onto my SD card, then replace the uRamdisk and uImage files with the 2.6.3.0 version here: http://techerrata.com/browse/twrp2/encore. I then downloaded CM11, GApps, and the EMMC TWRP 2.6.3.0 onto that SD card. Boot up the Nook from the SD card, then flash TWRP, then CM11, and finally GApps. Finally, turn your Nook off, take out your SD card (and format it), and then boot up your NC into your installed CM11.
[Nook Color Android Development] nicenice19:
Thank you for taking the time to help me with this. OK so I followed your directions to a T.First I formatted my Sdcard (Fat32). Then I copied the uRamdisk and uImage files which I believe were named "uRecImg" and "uRecRam" in 2.6.3.0 and renamed them to match the 2.3.0.2 naming of "uRamdisk" and "uImage". Then I copied over Cm11, Gapps, and TWRP 2.6.3.0. When I power on my Nook it just boots normally. Am I missing something here? I don't need to boot in a special method or anything (like power on and hold volume key or anything right?). My Sd works perfectly on the computer so I don't think there is anything wrong with it. I'm so frustrated!!!
[Nook Color Android Development] hliew88:
If you are using Windows, did you use win32diskimager to put the 2.3.0.2 image onto the SD card and make it bootable, before doing everything else? If not, your Nook will never boot off of your SD card.
[Nook Color Android Development] frankusb:
Do you have a 2GB or smaller card you can try?

Frank
[Nook Color Android Development] nicenice19:
I did do that :(

---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------

I may have one I can dig up. Will give that a shot next I guess.
[Nook Color Android Development] hwong96:
Look on the back of the nook. A lot of users mistake a nook tablet for a nook color. Here are the differences. Custom recoveries and roms are not interchangeable between the two.

Nook color (model BNVR200) has dark grey bezel and 8 gb ram.

Nook tablet (model BNT250) has a light silver bezel and 8 or 16 gb ram.

If you have the nook tablet head over to nook tablet forum.
[Nook Color Android Development] nicenice19:
Wow. That was it. Boy do I feel dumb. Thank you!
[Nook Color Android Development] steven676:
ClockworkMod Recovery 6.0.4.8 (required for new CM11 nightlies)

Here's a new ClockworkMod Recovery 6.0.4.8 build, including the changes required to install CM11 nightlies from May 16 or later.

This recovery is fully install-location-agnostic: it'll install to either eMMC or external SD, and operate on whatever it's installed to! (In other words: if you install it to eMMC, the format and backup/restore options will touch the eMMC installation; if you install it to SD card, they'll operate on the SD card instead.) The recovery will tell you on startup whether it's managing an eMMC or SD card install (look for the message at the bottom of the screen).

When used on eMMC, this recovery should be able to install any recent OTA package. When used on an SD card install, most recent addon packages (such as Google apps packages) should install, but only new eMMC/SD card location-agnostic ROM OTAs (such as CM11 nightlies from May 16 or later) will install successfully. (Unlike the test CWM 6.0.4.8, attempting to install an older ROM OTA package to SD card will not result in the eMMC being modified; the installation will appear to succeed, but nothing will be changed. We're still exploring ways to ensure that older OTAs fail outright.)

This is one of the last pieces of infrastructure we need in place for easier installs and single builds that install to both eMMC and SD without change.

Source: kernel (the current tip of the encore-omap3-3.0.y branch), device/bn/encore tree (the current tip of the cm-11.0 branch).

Install instructions on eMMC: flash the ZIP as you normally would.

Install instructions on SD card: first, either upgrade to a CM11 build from April 7 or later, or update the bootloader separately. Then, plug your SD card into your computer and open the ZIP there. Copy "kernel" to "uRecImg" on the first partition of the SD card, and "ramdisk-recovery.ub" to "uRecRam". (Make backup copies of those files first! If you currently have the SD card installer on the SD card, those are the boot files for the installer; if you move them to "uAltImg" and "uAltRam", respectively, you can then still access the installer by selecting "SD Card Alternate" from the Cyanoboot menu.)

Install instructions on SD card with CWM 6.0.4.8 or later already installed: just flash the ZIP from recovery.

EDIT: replaced -v2 with -v3 to fix automatic installation of OTA updates via the CM updater.
[Nook Color Android Development] steven676:
Recovery update required for nightlies beginning May 16

If you're running CM11 on eMMC, please note that nightly builds dated May 16 or later require an updated recovery to install (see the dev thread for details). The CWM 6.0.4.8 build posted above has the needed changes; hopefully eyeballer will be along soon to update TWRP (I'll update this post when that happens).

If you have CM11 installed on SD card, the traditional SD card installer is able to install the new builds. Still, it's suggested that you move to the new SD-card-capable recoveries when able, as those are what we will support going forward. (You will need to continue using the traditional SD card installer for installing older builds, though.)
[Nook Color Android Development] steven676:
We get this often enough that I've added it to the FAQ at the top of the thread.
[Nook Color Android Development] kozmo2k4:
Just tried to install (SD install) the 0515 nightly using the new CWM 6.0.4.8 from SD, following the instructions few posts above, but it fails with error Status 7 (set_metadata_recursive: some changes failed)...

However, the "original SD recovery", renamed as uAltImg installs the update just fine.

And the Reboot system boots into Nook by default, like it did with older

CWM, have to shut down and turn on to Boot from SD.

[Edit] Trying to restore fresh Nandroid created the new CWM gives md5 mismatch error....

Sent from my Mobile Communications Device
[Nook Color Android Development] volpo222:
I must be missing something.

Following the directions above I copied the new files to my NC and overwrote (but renaming as 'uAlt...') uRecImg & uRecRam. When I rebooted, holdng down the 'N' I ended up at the familiar "Universal Bootloader" screen, the boot menu. I selected "SD Card Recovery" and ended up at a menu I saw when I previously selected 'Alt Recovery'. Using the previous setup the update would have just started. I cannot select the zip because there is no way to see the (first) partition where I copied the update.

When I selected the "SD Card Alternative" the update installed as it did when I selected "SD Card Recovery" previous to copying the new files.

So what have I done wrong?

More: After moving the install file into a directory that I could navigate to I tried to install it and got the same error message etc. as referred to above.

(For SD Installs) In the original setup all that was needed was to select "SD Card Recovery" and the update started (with the update file in the root directory, partition 1). This new recovery boots into what was the "Alt" recovery style of the previous generation and makes necessary navigating to the recovery file. Will this become the new normal?

Also, previously after copying the update file to the root directory I could just select the "Reboot to Recovery" option of the reboot menu and it would just do it. Much easier.

Oh yah, one more thing. Why are the new files dated 'February 28, 2008'?

Thanks,

V
[Nook Color Android Development] pastordl:
Check third paragraph Steven676 post.

http://xdaforums.com/showpost.php?p=52672292&postcount=285

If I'm reading it correctly it is needed for 5-16 and later, and will not work with earlier nightlies for SD.

Go to my help post in signature below if you need to reinstall 6.0.4.7.
[Nook Color Android Development] pastordl:
Sounds like you named the new (6.0.4.8) files uAltImg and uAltRam. They should be uRecImg and uRecRam respectively. The old (6.0.4.7) files (uRecImg and uRecRam) were to be renamed to uAltImg and uAltRam. which would leave both versions available.

Kernel to uRecImg = regular image, to uAltImg = alternate image

ramdisk-recovery.ub to uRecRam = regular recovery, to uAltRam = alternate recovery

This applies to both eMMC and SD. I believe the SD must have an uRecImg and an uRecRam on it to recognize and install new zip. I'm not sure on this since it's been long time since I ran off a SD card.

Go to my help post in signature below if you need to reinstall 6.0.4.7. You can extract the files from the zip.
[Nook Color Android Development] steven676:
As pastordl points out, the May 15 nightly isn't SD-installable via this recovery. May 16 (which should be built and posted about six hours from now) is going to be the first nightly installable to SD using the new recovery.

Huh, I just tried this and it works fine here. Are you sure the backup completed successfully (and didn't run out of disk space or something)? A checksum mismatch suggests that part of the backup disappeared or was corrupted ...

OTA packages that are going to be hand-installed now need to be copied to /sdcard or /emmc instead of the boot partition. (You can also use adb sideload from a computer, if you like.) This is the way it's always worked with eMMC installations.

Yes, this is the new normal for hand-installing OTAs -- the process is the same as it would be for eMMC installs. That said, the CyanogenMod updater, ROM Manager, and similar tools for automatically installing updates should now work for SD card installs (someone should try them out, though, once suitable update packages are available). (That's one of the biggest advantages for going to standard tools for managing SD card installs.)

EDIT: Nope, the CM updater doesn't quite work ... we need the recovery's idea of /emmc and /sdcard to line up with the running system's. Fix incoming ...

EDIT 2: Updated recovery (-v3) posted above to fix that problem.

I think you'll have to ask Google -- that's the timestamp that comes out on any files unpacked from an OTA for some reason.

To be clear, the old SD card "recovery" was not CWM or another normal recovery, but a special installer system which only handled installing ROMs and Google apps to SD card. The current copy of that installer is found in leapinlar's thread.
[Nook Color Android Development] volpo222:
I'm sure I've named them correctly, I was quite careful because I thought I might make a mistake.The installation error confirms it I think because it is not possible to install any updates before 20140516 with the new installer to the SD card (as I've just read). It seems that I'll have to wait for the 2010516 or later nightly to install from the new installer onto an SD install.

Thanks to all who responded!

V
[Nook Color Android Development] kozmo2k4:
I guess I missed the part about the 5/16 nightly, didn't have enough caffeine yet...lol

Didn't see any errors while making a backup with the new CWM, and plenty of room left on this 16GB sdcard...

I ended up installing 5/15 using the "old installer", currently as uAltImg and all is good. Will try again tomorrow with the new nightly.

./b
[Nook Color Android Development] pastordl:
Installed new CWM, did backup, installed 5/16 on eMMC. Everything ran fine, smooth as silk. Just awesome what all the devs are doing with the Nook Color.

Is this also another step towards the repartition scheme that will have greater eMMC space?
[Nook Color Android Development] steven676:
I've updated the recovery posted above to fix a problem which was preventing fully automatic updates via the CM updater from completing successfully.

The new recovery is supposed to be the engine that drives the repartitioner, so in that sense, yes. (That said, it would have been possible -- though less convenient -- to implement the repartitioner using an older recovery.)
[Nook Color Android Development] polymath257:
Is the plan to have a fixed partition scheme, or will it be possible (possibly under an 'advanced' tab) for the user to determine it?
[Nook Color Android Development] volpo222:
New updater works well on my SD install.

Is there any way to change the update directory to SD card 1? The built in updater script is looking for the update on SD 0.

V

-----> Using the updated recovery this works fine now. Thanks steven676!