yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] bdcrim:
I am not sure if the CM7 is cloned on both partitions or not. It sounds like you may be booting into primary still. If you haven't checked your boot partition, you can do it with an app called NookColor UMS by Samuel Halff. It is safe to use. Just connect the nook to your computer without toggling on usb mass storage. Mount the boot partition and look for the alternate kernel and ramdisk, which are labeled uAltImg and uAltRam. They need to be there in order for the nook to boot into alternate. The primary kernel and ramdisk should be labeled uImage and uRamdisk if I am not mistaken.
[Nook Color Android Development] bdcrim:
Found it for you.
[Nook Color Android Development] zeus_chingon:
Isn't the same as in mounting boot from recovery then:

adb shell

cd boot

ls?

Doing the above I don't see uAltRam.

This is the list of files on my boot partition:

charging.zip

mlo

romrestore.zip

u-boot.bin

uAltImg

uImage

uRamdisk

uRecImg

uRecRam

Since I'm missing uAltRam, would adb pulling the uRamdisk prior to CMpri2alt and then pushing it back as uAltRamDisk be adviceable?
[Nook Color Android Development] Taosaur:
Your CWM is out of date, which may be part of your problem. You want at least 3.2.0.1 (which I think is still what you'd get via ROM Manager). The main reason 3.2.0.1 was released is because 3.0.2.8 had fits dealing with any partition layout except the NC's original 1GB/5GB.

A couple of other things that came up:

Will recent CM9 nightlies install over a wiped /system? Yes, I just did it yesterday.

Does running CMpri2alt give you identical installs on both partition sets? Yes, it wipes anything that was on the Alt partitions and copies whatever's on Primary to them, but doesn't wipe Primary.

?

I'm not sure what you're saying. The ReformatData link is correct, and I link to DG's repartitioning thread in two different places.
[Nook Color Android Development] zeus_chingon:
Thanks for the pointers. I'll try it with an updated cwm and see how it goes. Right now i'm testing if pulling the uRamDisk and pushing it back as uAltRam method and see it this solves it.

---------- Post added at 12:13 AM ---------- Previous post was at 12:05 AM ----------

As for the CM9 nightlies flashing from a siped system. The link for the CM9 nightly thread provided on the OP doesn't work for me ( http://xdaforums.com/showthread.php?t=1444943 ).

The ones from this thread DOES work for me from a wiped system ( http://xdaforums.com/showthread.php?t=1526115 )
[Nook Color Android Development] zeus_chingon:
I finally managed to get dual boot setup working. The whole problem came down to an outdated CWM that failed in creating a uAltRam. Thanks everyone for the hints.
[Nook Color Android Development] IM0001:
Curious as I am not seeing what I have been looking for. But is there a chance I could get a 1.4.2-to-alt.zip from anybody? Apparently the auto install isn't working (does that have something to do with it being in the alt partition + CWR?) and I know flashing it raw would only botch up my primary partition.

No rush as I only use the stock partition when actually in a B&N (which has yet to happen lol. Too friggin busy to just sit and read.)
[Nook Color Android Development] Taosaur:
You know, I've been using Eyeballer's nightlies all along, but he didn't have a thread for them when last I edited. I went ahead and pointed to his thread. Glad you got your install sorted--wish I'd seen your post earlier, but life is crazy.

Sorry, haven't seen one. If you have any CWM-flashable 1.4.2, you could backup primary, run BNalt2pri, update, run BNpri2alt, then do a fresh install of whatever's on Primary and advanced restore /system and /data over it (don't just "restore" in CWM--it will undo any changes your stock update made to files in /boot, which could leave Alt unbootable).
[Nook Color Android Development] racks11479:
Hello Taosaur,

Just writing to see if you guys could/would use a tool that could convert any ROM to be flashed to alternate boot? Basically it will mod updater-script to flash to correct mountpoints as well as renaming uImage/uRamdisk to uAltImg/uAltRam and editing ramdisk mountpoints in init.

-Racks
[Nook Color Android Development] Taosaur:
ETA: to the person asking about 1.4.2 zips, there are DIY instructions for making B&N's updates CWM-flashable over here: http://xdaforums.com/showthread.php?p=22965301#post22965301

I'm conflicted :D On the one hand, such an app would be much quicker if you're flashing nightlies to both Primary and Alt. If you aren't updating Alt as often, though, you'll probably want to make a backup each time, which would mean moving the Alt install temporarily to Primary anyway, where you could use a regular update zip before moving it back.

I would think at least some people would use a tool like that, though. I would probably use it for flashing CM7.2 nightlies, and just do the full backup shuffle every 3rd or 4th time.
[Nook Color Android Development] Dhyneland:
Great guide OP! Thanks so much for posting this.

I dusted off my nook color and followed this guide without any issues.
[Nook Color Android Development] nickveldrin:
I for one would love a set of scripts that would do these functions like yours do but on these sets of partitions.
[Nook Color Android Development] jewnersey:
Ran through this tut and everything seemed to go smoothly, but I can't boot my alternate rom which is latest mirage Kang of cm7.

Can I flash something straight to alt without screwing up my primary?

decided to try again. updated to CWM 5.5.0.1, moved my primary (CM9) to alt, then flashed CM7 and now all is well

edit:

scratch that. booted into alternate after i moved it, but then after flashing cm7 it blank screens me at alt boot
[Nook Color Android Development] Taosaur:
Are you flashing a fresh install to primary, or restoring a backup? A full restore after you set up alt can hose your alt install because it overwrites /boot, erasing the alt boot files. You can still restore, but flash a fresh install first and then do an advanced restore of just /system and /data.

If you did a fresh install to primary, all I can say is try again. I had the same thing happen last time I overhauled my dual boot, getting the blank screen when trying to get to alt. IIRC I just ran through the steps again without doing anything differently (doesn't take too long if you have all the files and are familiar with the steps) and got the stable setup I've been using for a couple weeks, flashing CM9 nightlies on primary all the while.

My steps to try, try again were:

restore my old CM7 (also Mirage), update, and reboot to make sure it worked

move CM7 to alt (CMpri2alt)

reboot and check if you want, should see identical installs on both alt and primary

wipe /system /data and /cache

install CM9

advanced restore /system and /data (actually think I skipped this step and started fresh last time)

install gapps (I like to do this after the restore)

boot into everything one more time to check it out

Just make sure to give alt a couple tries and give both partitions plenty of time to boot the first time. I've seen first boots take 20 mins before (that one was a straight CM7 install, no dual boot). If it doesn't boot right up within a couple minutes, I leave it plugged in and walk away from it for awhile before I decide it's not working.
[Nook Color Android Development] jewnersey:
Doing all fresh installs followed by gapps.

Left my alt boot for a while with no change, butI think I can just stick with cm7 for a while. cm9 is prettier but there is nothng in their that I Cant do in cm7
[Nook Color Android Development] Taosaur:
Minor update to OP, turns out 1GB / 5GB partitioning is unnecessary with the current method. Jicama, who didn't have the post count to let us know here, just PMed me with confirmation that repartitionDual handles blue-dot NCs just fine.
[Nook Color Android Development] jicama:
I didn't find those instructions very specific. Here's what I did to make a CWM-flashable 1.4.2 that keeps CWM on the emmc:

1. Grab the stock image from Barnes & Noble.

2. Unzip it.

3. Make two changes to META-INF/com/google/android/updater-script :

3a. change line 1 as described here, to

assert(getprop("ro.product.device") == "zoom2" || getprop("ro.build.product") == "zoom2" || getprop("ro.product.overall.name") == "NOOKcolor" || getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore") ;

3b. From near the bottom of the file, delete the lines

package_extract_file("kernel-recovery", "/boot/uRecImg");

and

package_extract_file("ramdisk-recovery.img", "/boot/uRecRam");

4. Zip it all back up again.

And done.
[Nook Color Android Development] bluepen61:
Ok, I followed the instructions. But 'stock' B&N give me the error, Restart required, Your NC encountered a problem that requires a system restart.... " this is in alt.

So I did a restore again from cwm 3.0.2.8 and got the same issue.

Is there a work around? or should I start reflash 1.4.2, then install MN and the OC and then move it to alt and try again? (Then use Titanium backup to restore my apps.) ??

Btw, the procedure is really simple, almost fool proof.
[Nook Color Android Development] bdcrim:
Update your CWM to 3.2.0.1 and try again.
[Nook Color Android Development] bluepen61:
Worked! Thank you for your suggestion! :cool:

To clean up the mess I made, I un-partitioned, and re-partitioned the NC back to stock partitions. Then, I did the 7 failed start method to revert the NC OS back to stock OS; booted to the signup screen and then powered it down. To check for a good CWM backup, I then booted to CWM 3.2.0.1 and restored the prior setup from the backup. Worked perfect, and with the expected partition size for B&N and other data. I then followed the OP using CWM 3.2.0.1.

I kind of kicked myself for not upgrading CWM earlier, since I read posts that older versions were not compatible. Maybe I like the exercise of doing these processes more than once.
[Nook Color Android Development] bluepen61:
I reverted to stock so I could update to 1.4.3. And here are some observations:

1.4.3 rooted MN seemed to work for a time in alternate, but I lost access to PlayStore, MyApps; and I lost Shop and management of Settings\Social.

So I reverted back to stock and updated just to 1.4.3, unrooted with CM7 primary. 1.4.3 in alternate lost wifi.
[Nook Color Android Development] bluepen61:
Ok, just disregard my comments above concerning problems with upgrading to 1.4.3/MN 5.2.19 to dual boot, alternate partition. I broke rule #1: be patient while the NC is upgrading. And rule #2, be more patient while the NC is upgrading, let it sit, while either B&N or MN/Play Store updates behind the scenes. Go for a walk or down a couple of pints while

each

process is working. It seems that just downloading all the B&N apps, book, mags, etc or just letting Market to update to Play Store is not enough. It continues to do more work which one does not observe.

Oh, the good news is that 1.4.3/mn 5.2.19 seems to be working well, all aspects. One other thing I did was to minimize the restoring of apps using Titanium to those apps whose data was not on uSD card.

Sometimes I wish there was a message delete button....
[Nook Color Android Development] k8108:
I wanted to try ICS again, but didn't want to lose my MiRage Rom, so this set up seemed perfect. I got everything loaded and set up, only to find out that each rom only had about 300 MB for apps. Is that right? No way do-able for me. Is there someway to expand to have more room for apps?
[Nook Color Android Development] bluepen61:
That happened to me, did this to fix to my NC:

In the Original Post (OP) under

Other Resources

do this:

Apply Revert dual boot, twice

Then partition back to stock, I used 1b in that thread's process.

Then restore to stock 1.4.2 (or MiRage Rom in your case).

Then follow the install process in the OP again, using the CMpri2alt instead of BNpri2alt to move MiRage Rom to alternate partitions.

That might work.
[Nook Color Android Development] k8108:
I have reverted back to my single boot Mirage rom. I did use CMpri2alt in my original dual boot configuration, but can't figure out why the data images were so small if the 2 roms were supposed to be sharing 2gb.
[Nook Color Android Development] harryzee:
Help!!!

I have your dual boot setup with 7.2.2-RC3-Kang on eMMc normal and 1.4.2.keep-CWM on eMMc alternate.

This is by far the most satisfying iterartion (of many) I have used on my original NC...Thanks!

However, I cannot for the life of me find the path to the folders where my Kindle and Nook books are kept for their respective apps on the Normal/7.2.0-RC3 side.

I have used both the Root Explorer and File manager apps to no avail.

The files for my 1.4.2 Nook books are clearly on the sdcard.

In the eMMC sections I can examaine, both the Nook and Kindle files are empty even though I clearly have books in both.

Uploading to BN and then d/l to the app is not an option for several titles I want on the "apps" side.

Thanks in advance.

Also: Is there a 1.4.3-keep-CWM in the offing???
[Nook Color Android Development] harryzee:
Found the Nook folder but the Kindel folder and its two subfolders are empty and I clearly have books on my device.
[Nook Color Android Development] mbarry55:
Can I use this guide to do an AOKP/stock emmc dual boot? Or does it have to be CM?
[Nook Color Android Development] Taosaur:
I suspect AOKP uses the same conventions as CM, so the tools for moving CM ought to work fine with AOKP, but we won't know until someone tries it and reports back :D
[Nook Color Android Development] pastordl:
Thank you, Taosaur and all the others who worked to make this dual boot setup possible and do-able. I'm in my late fifties and very limited due to constant, moderate to severe pain throughout my body. Three years ago I was blessed with a Nook Color. Very soon after getting it I wanted it to do more than the stock ROM would allow. CM and Xda became my go to sites and enabled me to flash to CM7. Since the work on ICS (CM9) has been going on I have tried an install of it on SD. Liked the ROM but having it on a separate SD card and not having access to my 32gSD was a drag. A little research and Yep XDA has a dual boot solution. I now have CM7 on Primary and CM9 on alternate. More to help the day go by and enjoy my Nook even more than before. My Nook goes with my every I go and I love to show off to others what this little "tablet" can really do. Have even flashed others over to CM7.

Thanks again from the the bottom of my heart.
[Nook Color Android Development] tambourineman86:
Great work on this guide, very easy to understand! Exactly the solution I was looking for.
[Nook Color Android Development] -somebody-:
thank you for this, ive been pulling my hair out trying to find a stock 1.4.2 for this damn thing, 1.4.1 leaves me with no touch screen functionality for some reason.
[Nook Color Android Development] echoedge:
Last time I tried to revert to nook it disabled my access because it wasn't synced to their servers (I'd forgotten my B&N account).. will this help?
[Nook Color Android Development] pastordl:
The dropbox address comes up with a 404 error. Please correct so I can download.

Thank you
[Nook Color Android Development] -somebody-:
uploaded, lemme know if any problems. the uploads should be fine though
[Nook Color Android Development] -somebody-:
manualnooter 5-8-20. basic block updates: https://dl.dropbox.com/u/14932133/NookColor/manualnooter-5.08.20.basic.block_updates.zip

manualnooter 5-8-20. incremental block updates: https://dl.dropbox.com/u/14932133/NookColor/manualnooter-5.08.20.incremental.block_updates.zip

nook color 1.2 stock keep cwm: https://dl.dropbox.com/u/14932133/NookColor/update-nc-stock-1.2-keepcwm-signed.zip

nook color stock 1.2: https://dl.dropbox.com/u/14932133/NookColor/update-nc-stock-1.2-signed.zip

B&N nook color 1.4.1 stock: https://dl.dropbox.com/u/14932133/NookColor/nookcolor_1_4_1_signed.zip (im pretty sure with this i got pissed off and disabled signature check in recovery and just flashed it then upgraded with the others like normal then ran the manualnooter)

B&N nook color 1.4.2 stock: https://dl.dropbox.com/u/14932133/NookColor/nookcolor_1_4_2_update.zip

B&N nook color 1.4.3 stock: https://dl.dropbox.com/u/14932133/NookColor/nookcolor_1_4_3_update.zip

all i did was hunt some of these down and reupload them, the props/thanks goes to the ones who put them together and B&N
[Nook Color Android Development] oppy:
Okay, probably a dumb question: I set this up about a year ago using the "original" method. I haven't booted into stock in months, so it's time to get rid of it. Should I still use the method under "Old Resources" from the first post, or is there a better way?
[Nook Color Android Development] -somebody-:
just redo everything the newest way all in one shot and get it over with
[Nook Color Android Development] oppy:
Sorry, should have been more specific. I actually want to get rid of the dual boot because I no longer need it.

So, my question was really asking if I should use the "old resources" method to uninstall the dual boot so I can reflash.

Thanks for the help!
[Nook Color Android Development] -somebody-:
id use the revertdual zip and restore partition sizes zip in the other resources section. read and try the other resources section

and

http://xdaforums.com/showthread.php?t=1094371
[Nook Color Android Development] oppy:
Okay, I actually used the "Remove dual boot" file listed under Old Resources and it worked fine, no additional repartitioning needed. Just reflashed MiRaGe KANG and I'm good to go.

Keep in mind I installed dual boot using the original method, so this may or may not work for you.
[Nook Color Android Development] bluepen61:
I cannot boot to alternate anymore. Is there a fix? Here is the background:

I have been running dual boot with CM 7.2 primary, and B&N 1.4.3/ManualNooter Alternate for several months and really like it.

Now that CM 10 came along, I wiped primary and installed CM 10 betas and that worked fine and I could boot to alternate.

That is until I tried the nightlies today. Opps. Apparently the nightlies did not install because recovery was not on the emmc. Ok, I tried to installed TWRP from GooManager within CM10 and that did the same thing. Then I downloaded CWM and installed through my CWM uSD card and that worked. I can boot to CWM recovery, and install the nightly.

Then try to boot to alternate, my NC just hangs with the words "Booting into alternate..." with the cyanoboot logo above.

Also, in the cyanoboot boot menu, the "Internal eMMC Alternate" is grayed out.

It would be nice to boot back to alternate.
[Nook Color Android Development] Taosaur:
Hmm, it sounds like something got corrupted in boot with all that flashing back and forth, but I don't see any reason the alt partitions should have been touched. The only thing I could suggest, if you used the current method in the OP, is to back up your CM10 and use the BNalt2primary script to try to shuffle your alt onto primary and see if it will boot from there. If so, you can send it back to alt and restore CM10 /system and /data to primary. Otherwise, I'd say partition back to stock and start from scratch w/ the dualboot.

For what it's worth, I just double checked and CM7.2 is doing fine on my alt partition set, and I'm also running CM10 nightlies on Primary. I know the very first CM10 nightly after the betas was a dud that would not boot, which is probably what started you down this road. I went from Beta 4 to the second nightly.
[Nook Color Android Development] bluepen61:
Something corrupted that partition.

Edit (add): I ran fix permissions from ROM Manager in CM10, maybe that affected the alternate partition(s).

I decided to go back to single boot to CM 10. Found out that it is important to do the reformat zip :)

I will return to dual boot during the holiday when I have more time.

Thank you for the advice!
[Nook Color Android Development] bluepen61:
Edit: see my next post.

Sent from my xda premium
[Nook Color Android Development] bluepen61:
Back to dual boot by following your suggestion to start from scratch. Thanks!

I do note that on boot, I cannot enter the boot menu. It is the cyan colored Cyanogenmod boot with CWM 3.2.0.1 on emmc.
[Nook Color Android Development] lowsnamebrand:
Anyway to install cm and cm10 with this method? I tried searching the thread but the couldn't find a strait andwer
[Nook Color Android Development] bluepen61:
Yes. In the op, install CM 7.x to primary, then use the cmpri2alt.zip (in Other Resources section) to move CM 7.x to alt and then install CM 10 to primary. I am not sure if CMpri2alt.zip works with CM 10.
[Nook Color Android Development] lowsnamebrand:
Thank you I appreciate it. does it matter how my nooks emmc is formatted currently?
[Nook Color Android Development] lekofraggle:
I used this method to get my current setup.

Here is what I have...

Cm10 as primary

Autonootered OEM install on alt.

OEM recovery

Sd card: twrp.

I used this method to move autonooter to alt

Then I installed cm9 then cm10 through twrp.

In order to install twrp on sd, I made a bootble sd card (using one of the images on this forum), then followed the twrp directions for updating (renaming and replacing uboot and urecram)

It works like a charm.

As for the partition scheme, I think this modifies your existing partition scheme. Because of this, know the oem recovery will fail unless you revert your partition scheme first.

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] Taosaur:
It's cool to see people getting creative with these tools. Part of my motivation in assembling this thread was to publish (partly for my own reference) my NC toolbox, most of which just happen to be required to get a dual boot EMMC setup. As a result, more capable modders popped their heads in with new tools and advice on tweaking what I had to get results that weren't possible before this thread existed.

My NC days are numbered now, as I picked up the HD+ (which is frigging gorgeous). I'll be setting up my NC for my sister, probably as a single CM10 system, though I may go CM7 if I can't get decent browser performance on CM10. I might even try rooted stock, or setting up and then unrooting stock, to make it harder for my sister to get into trouble ;)
[Nook Color Android Development] odj1041:
Is it possible to do all this but with TWRP because the volume rocker is broken on my nook
[Nook Color Android Development] Taosaur:
Yep, I'm using TWRP myself. If you have access to at least one working CM install, just grab TWRP via Goo Manager.
[Nook Color Android Development] bluepen61:
Leapinlar,

Here is what I can and cannot do with the dual boot. (Note both CM 10 and B&N Stock rooted with MN 5.8.20 are on emmc not uSD.)

From CM 10's power down Tablet options, I can select Reboot, then select Recovery and it will reboot into recovery CWM 3.2.0.1.

From CM 10 or B&N Stock rooted with MN 5.8.20, I can power-off, then boot normally to either CM 10 or hold the volume +- buttons to enter B&N Stock rooted with MN 5.8.20.

What I cannot do:

When booting from a power-off state, I cannot enter the

Boot Menu

in the Cyanoboot universal bootloader. The bootloader displays, hold N to enter boot menu, and after holding down the button, the option disappears and Boot Menu (words) appear in cyan color on the display. The screen display will forever stay that way until I hold the power button to force the NC off.

The problem is not getting to alternate, I can do that holding the volume -+ keys. The problem is getting access to the Boot Menu in Cyanoboot universal bootloader.
[Nook Color Android Development] mitaiwan:
Internal memory in alt partition

Thanks for such a detailed guide for dual boot. It works.

I followed the steps with these combinations:

CM10 pri /w CM9 alt

CM9 pri /w CM10 alt

CM10 pri /w CM7 alt

and all works fine. but I found that the internal memory on alt partition are just 34x mb in all these three cases.

Any idea?
[Nook Color Android Development] jdaudlin:
Can't download primary_update_NC_stock_1_4_1_keep_CWM.zip from rapidshare

Can't download the file primary_update_NC_stock_1_4_1_keep_CWM.zip from rapidshare. Anyone have this file for download?