yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Taosaur:
If you look at the OP, you'll see a major update. I replaced all of the partitioning/moving files with new ones based on DeanGibson's, but altered to be compatible with CyanogenMod and the CM boot menu. I also implemented all of rajendra's updated 1.4.1 files.

Dean's scripts create one more partition than rookie1's prep-dualboot: 0p11, a copy of /cache. So, I would not expect the new BN/CM pri2alt zips to work on a dualboot build that was set up using prep-dualboot. BN/CM alt2pri may work, but I wouldn't count on it. If you're not looking to change your configuration (move CM to primary, have two CM installs) and are just running unrooted stock on alt (with most of your stuff backed up in B&N's cloud), you're probably better off leaving well enough alone.

If you want to migrate to the new partitioning and try to back up your existing build, I would:

back up the primary partition

attempt to run BNalt2pri

If it works (try booting into stock on primary to find out), then back up stock (I've never actually tried that, but I think I've seen others do it)

run remove-dualboot (under Old Resources in the OP)

run repartitionDual2GB

run formatData

restore whichever backup you want as the alternate

run the appropriate (BN/CM) pri2alt

do a fresh install of whatever you want on primary

if you want to restore your apps/settings, do an Advanced restore of /data only.

bootboot!

If BNalt2pri doesn't work, well at least you saved your primary partition, and you can set up your new dualboot any way you want and keep it backed up and updated.

I'm now rocking a MiRaGe CM7.2/Eyeballer CM9 dualboot :D

UPDATE: changed the restore to a /data only advanced restore, to avoid overwriting alt files on /boot.

ETA: I also meant to say, revert-dualboot could use some work. I added a line to the "clear" script in rookie1's remove-dualboot to delete 0p11, but I don't have time to puzzle out the script that rebuilds /media (/mnt/emmc) and I think it currently leaves that partition corrupted, or at least odd-sized. Whatever you had on primary will still work on the resulting single partition set, but I'm not sure if you can use /media at all without swinging by DG's partitioning thread (and wiping primary with any of those scripts). Most likely just one or two values need changed to eliminate that extra step, if anyone more script and/or partition table literate wants to take a look at it.
[Nook Color Android Development] -somebody-:
Thanks Taosaur, ive been hunting around trying to find a good way to dual boot the nc from internal instead of sdcard that was updated.
[Nook Color Android Development] skwalas:
So, question: If I want to be able to play with the CM9 nightlies and be ready to do the daily flash once CM officials come out, will I need to have CM9 on primary? I'd like to keep CM7.2 my daily driver for now, and would like to have CM9 on alternate, ideally, but am not sure how I'd do an update flash for CM9 if it was on alternate.

On the flip side, if I put my current CM7.2 on alternate instead, how do I back it up later on down the road?

(getting seriously jazzed about getting into the whole flashaholic mode again)

Edit: Hmm, never mind. In re-reading OP, it seems that i'll most likely have to put 7.2 on alternate and CM9 on primary, and move the 7.2 back to primary whenever i need to backup/update, which will (as I understand) wipe out the CM9 install (unless I choose to constantly make back ups). Not a biggie, since CM9 won't become my daily driver until it gets hardware acceleration anyway, so I'll just be futzing around with it.
[Nook Color Android Development] Taosaur:
Steps for backing up both partitions:

Boot into CWM

Backup and restore > backup

Install zip > choose zip > BN/CMalt2pri (whichever applies)

If desired, reboot to make sure everything went well

Backup and restore > backup

If you have an update, install it now

Install zip > choose zip > BN/CMalt2pri (whichever applies)

Backup and restore > restore > (choose the older backup)

Advanced > wipe Dalvik cache (doesn't hurt)

Reboot

Recommend resources to keep on your SD: BN+CMpri2alt, BN+CMalt2pri, 1 backup of each install

Optional: revert dual boot, repartitionDual2GB, 1 or more mono-boot partitioning zips (1/5GB, 2/4GB, 5/1GB), 1 update zip for each install (CM7.1/7.2/9, stock), gapps for each CM install, any favored mods (keysmod, flashable themes, kernels, etc)

You can actually keep as many different installs handy as you have room for backups (you might want to start renaming your backups to keep track of what's what). It's pretty trivial to back up whatever you have on primary and restore something different there temporarily, and even shuffle everything to whatever partition set you want.

Yeah, def sounds like you'll want to keep CM9 on primary. It's really not a big deal doing the 'backup shuffle,' especially if you're not updating or backing up alt that often--hell, it only takes 15-20 minutes to break a dual boot down to stock and rebuild it from scratch if you keep the files handy on your SD.
[Nook Color Android Development] YertletheTurtle:
CM9, CM7 dual boot assistance

I am attempting to set up a dual boot system with CM7.2 (mirage) on the alternate partition and CM9 on the primary partition.

Here are the steps I followed:

1. With CM7.2 loaded on a nonblue dot Nook, I ran repartitionDual2GB from CWM.

2. Ran CMpri2alt from CWM. Confirmed that CM7 ran properly from the alt partition using the boot menu. It loaded fine but showed a SD card error and the media partition was not accessible (/mnt/emmc). This was confirmed from CWM as well (unable to mount).

3. Wiped system, data, cache, Dalvik in CWM.

4. Successfully installed CM9 on the primary partition. However, it also was unable to access the media partition.

So in summary, I was able to successfully install and boot to both CM7 and CM9 but was unable to properly access the media partition. I tried several different combinations to no avail with returning to original 1/5 GB partitions in between.

Taosaur, you mentioned that you successfully are running CM9 and CM7. Do you mind showing what steps you utilized to achieve this? Thanks in advance.
[Nook Color Android Development] skwalas:
Cripes! I haven't seen this in a long time, but I managed to put myself in a CWM bootloop...

never got the alt boot to start up, so tried your revert file, and now I can't seem to get away from good ol' koush's wonderful little bowler hat.

Tried full wipe of everything, tried DG's repartitioning, tried installing 1.3 with CWM (which I already had).

dunno what the hell I did, but this is annoying. did I somehow replace the standard u-boot files with the rec-boot files maybe?

Where's the nuclear option?

Edit: Still had the old "remove cwr" zip, so I used that to remove CWM/CWR, used my CM9 SD card to re-install, and now it looks like my backup is booting up as expected.... and Bing! Back in business. Tao, you might want to get that revert zip fixed, since i wasn't having any problems till I tried using it (and you said you were already aware of issues with it). Now back to getting a proper dual-boot setup...
[Nook Color Android Development] Taosaur:
Yipes, guys--I'm sorry you are having these troubles, but thanks for reporting back so we can sort them.

@Yertle, Short answer: I've added a format of /emmc (aka /media) to the guide, and you may be able to do one now and be good to go--let us know.

Long answer: I've been rolling with this partitioning for a couple of weeks (w/only CM9 installed before I made the new files), but I can't say for sure that I ever had access to /emmc, because I rarely use it for anything. However, I did notice when I first tested revert-dualboot, but did not wipe CM9 off primary, that CM9 still worked fine except that I had no access to /emmc, like you describe. I attributed it to revert-dualboot, but I now suspect it was left over from repartiionDual2GB. DG does have us wipe /emmc (provides a zip for it, actually) when using his other repartitioning scripts, so it may be something inherent in his partitioning method.

I can confirm after doing another run through and formatting /emmc (I used DG's data/cache/media format zip from his repartition thread) that I do have access to /emmc from both systems. Unfortunately, I was already breaking things down before I had a chance to check if I'd had access before, but I suspect I did not.

Are you saying you do have access to CWM but can't get anywhere else, or you can only get CWM via SD? Sounds like the second, but I want to be sure I get what you're saying. When you say "1.3 with CWM," you mean you tried to install 1.3 from a CWM SD card, right?

Did you try the upgrade path from the old dual boot? I just discovered I left out an important step--the new dual boot script. I don't see how that could get you boot looping in CWM, but it would certainly explain why you couldn't get into alt.

If CWM is truly hosed, you can try:

DizzyDen's 1.4+CWM zip in the "1.2 Update" thread (I don't think any previous stock zips actually included CWM, they just left it alone).

pushing new urecImg and urecRam if you're comfortable with ADB

make a CM7 SD card (there's a link in my sig) and re-flash CWM from ROM Manager.

That last is the long way round, but would be the most appealing for some people (especially if you have the files sitting around).

Also, just to be clear--"full wipe of everything" did not inclulde /boot, right?

In this last run through, I just ran revert-db, then DG's "old 1GB /data" zip, then his format zip, then restored a backup to get back to mono-booting.
[Nook Color Android Development] jsirgey:
i started from scratch, when i got to

12. Choose the repartitionDual2GB file.

it says you have to reboot, i did this and when i tried to go back into 1.4.1 which was fine before this step, i now get a message that an error has occurred and the nook needs to restart, i restart and still get the error.

Any ideas?
[Nook Color Android Development] YertletheTurtle:
Success! As recommended, I ran from CWM reformatData-v1.zip after transferring CM7 to the alternate partition. At this time, I confirmed that it EMMC (media) was available (size 1.23 GB, down from 5 GB as expected). I then proceeded to install CM9 which also was successful and could see the EMMC partition as well.

One step that might need clarifying is after installing repartitionDual2GB, one needs to reboot back to recovery immediately before installing any alt2pri.zip. I discovered this the hard way (appears jsirgey also is learning the hard way).

Thanks again for developing this guide and software.
[Nook Color Android Development] jsirgey:
i take it the errors im getting are because i didnt go right back into recovery?

I'll start over and try that this time, thanks!

Edit - That fixed the issue, maybe a good addition to the walk through would be 12b) reboot right back into CWM otherwise you end up corrupting your install and have to start at the beginning.
[Nook Color Android Development] Taosaur:
Thanks for the feedback. I went ahead and added the reboot step--I didn't even think about it, because the instruction appears on-screen.

jsirgey, what method did you use to reboot into recovery? The rhythm method? I find that Advanced > Reboot Recovery simply reboots, without taking me back into recovery. With the CM boot menu it's easy, of course. I might look at a way to sneak that uboot in somewhere earlier in the guide to make the reboots easier for stock users. Some new stock zips (or smaller mods for the existing zips) might become available soon that would address the issue.

Order of operations might need a tweak, too--the repartitioning used to come before flashing stock, but that turned out to be unnecessary with prep-dualboot; the same may not true of repartitionDual2GB. If nothing else, you lose the empty folders on /emmc with the current order.
[Nook Color Android Development] skwalas:
Looks like y'all are getting to the same conclusions I was. The CMR bootloop I can't explain, but occurred while trying to fix the problems described above. Spent 5 solid hours on this last night and success/bed at 3 am. The wife was NOT amused:eek:

So my conclusions:

1) steps need to include reboot after repartitioning

2) repartitioning seemed to corrupt the primary: even though the partitions copied without errors, neither primary nor alternate boots worked. This was reproducible for me (and it was trying to fix this when I got stuck in cwr groundhog-day hell). And yes, this was occurring even after I learned to reboot to cwr after reparititioning, so for me its not just due to the missing reboot step.

3) as a result of 2), I had to change the order of operations to include the reinstallation of the intended alternative ROM after the repartitioning and before the pri2alt step (this was a restore of 7.2 in my case, and I wiped everything prior, just for good measure). After this, everything else worked fine.

On a separate note, at one point I accidently flashed cm9 directly over the 7.2 install without wiping anything and it seemed to work fine minus a few apps: I discovered cm9 to be setup identically to the 7.2 setup to my great surprise, including gapps icons. Now that I'm rocking the dualboot finally, I'm gonna play with this a bit and see if upgrading really can be that simple.
[Nook Color Android Development] Taosaur:
I'm glad you got it sorted, after however many headaches. I will look at moving the repartition up to the start of the process, though it will add steps for preserving an existing install (basically, back up and restore).

I did the same thing a while back, and all my apps automatically fetched their ICS versions. I found that Market would crash immediately upon opening, though. I have been contemplating setting up flashed-over-GB ICS and fresh ICS side-by-side. It'll quickly get to the point that I'm effectively quintuple-booting: two systems on board and three more in backups :cool:
[Nook Color Android Development] skwalas:
Well. Nice. so here's what I did after reading your reply: restored my 7.2 build (on primary ,natch), all personalized and everything, then flashed cm9 (samiam's build) directly over that, no wiping

anything

. Apps were updated upon startup, ADW EX laid out exactly as I had it in 7.2 (except the widgets I had didn't work, not unexpected). But GMail and Market kept closing no matter what I did. Went back to cwr, flashed samiams gapps and telephony-fix zips without doing any wipe (remember, it's now CM9 at this point). It did a little more "upgrading" on boot, I found that gmail worked fine, but market still kept closing. On a hunch i rebooted again and now market works, with the entire desktop set up exactly as I had it in 7.2, only ICS-flavored!

With a little tweaking to the above, it looks like we might be able to upgrade our CM7 installs directly to CM9 without having to deal with wiping data, titanium backup or any of that other stuff.... which is exactly what I'm hoping for!
[Nook Color Android Development] oppy:
Okay, probably a dumb question: is there any benefit to "upgrading" to the new partitioning? I'm using the latest MiRaGe KANG on primary and stock 1.4 on alternate, and it seems to work fine. The little experimentation I've done with CM9 so far has been limited to SD.
[Nook Color Android Development] skwalas:
My little experiment has nothing to do with dual boot generally. I was using dual boot as a way to play around with cm9 on primary while keeping my cm7 daily safe on alternate.

And in any case, my experiments ended up borking the alt boot somehow anyway, so i would advise not repeating my dumb mistakes.
[Nook Color Android Development] Taosaur:
The only benefit would be the ability to move your stock install over to primary to back up or upgrade it, but if you haven't rooted stock then chances are the majority of your stuff is backed up in B&N's cloud anyway, and we may well have reached the end of updates (and you have decent odds of getting an alt-flashable version of future updates).
[Nook Color Android Development] Taosaur:
You know, I considered making this method a new thread, or including both the old method and the new one in this thread... I may still do it. If you're only looking to get stock + CM, the old way was a little more streamlined, with fewer opportunities to screw something up.
[Nook Color Android Development] oppy:
Thanks, that's kinda what I was thinking. I actually don't have much B&N stuff, so backup isn't really an issue. I just like the stock reader.
[Nook Color Android Development] bdcrim:
Followed your guide and have CM7 on alternate and CM9 on primary with everything repartitioned correctly. Thanks for putting this together.
[Nook Color Android Development] tinpau60:
primary_update_NC_stock_1_4_1_keep_CWM.zip

Having a hard time getting primary_update_NC_stock_1_4_1_keep_CWM.zip to downlaod from Rapidshare. Is there another place to get it ?? Maybe a dropbox acct somewhere?? That is all I need to get this going ....

Thanx in advance

Tinpau
[Nook Color Android Development] Taosaur:
Here is the official B&N update (which will not work w/ CWM as-is, but should be a faster download) and here are instructions and resources for making it CWM-flashable and/or making other modifications.
[Nook Color Android Development] jdpdata:
I followed the steps listed with no issues until step #11. After I successfully connect to wifi, it wouldn't register. Says something about 'Problem registering...try later' only options were to shutdown or reset. I tried both many times, still can't register the nook. I had registered it before, tried using old username/password even created new username/password, none worked. Any ideas guys?
[Nook Color Android Development] tinpau60:
Followed instructions and worked first try!!

WOW !! ... Finally got the stock 1.4.1 to download from Rapidshare... and followed the guide for the dual boot. In less than 20 minutes or so I had it running first try. Brought my Titanium Backup folder back onto my NOOK from my previous single boot Mirage CM7 install and reinstalled my apps... Evertything works great !! Played with it a few hours and love it even more... Because I can use the stock Nook side for when I am at a B&N or want to read in a real nice format.

Thanx again to everyone who has worked on this ROM and all the others too.

Also thanx to the folks that create these great how-to instructions !!! You all are the best.

Tinpau
[Nook Color Android Development] -somebody-:
yay

this has been great for me too, the only problem is deciding on which roms to run side by side lol
[Nook Color Android Development] zires:
Went through all the steps and I think I messed something up. Default is cm7 mirage kang, alternate was supposed to be cm9. So was able to boot into default...all my apps were there from where I left off this morning. Emmc is now empty with a little more than 1.5gb in it. So cool. Tried to use the boot menu to boot into alternate and it hung. Did the both volume buttons and it booted okay but it's booting into a fresh install of cm7 mirage kang. How do I get cm9 into that partition?
[Nook Color Android Development] bdcrim:
I assume you went through all the steps. After moving the CM9 to alternate, how did you get your CM7 rom back on primary (default)? Did you do a fresh install or did you restore a backup?
[Nook Color Android Development] zires:
So started all over. Followed the directions to a point. Substituted keep stock with cm9. Also instead of using the bnint I used the cm one. Then continued. I'm not going to restore from data this time and see what happens. What I really need is a guide for cm7 and cm9. Upgrade guide too. Help!
[Nook Color Android Development] bdcrim:
If you have any more problems, send me a PM and I will help you go through the process. I just installed dual boot on mine with CM7 and CM9. I had to go back a couple of times before getting it right.
[Nook Color Android Development] zires:
Pm sent. Sorry but why not post here? It may benefit others like me.
[Nook Color Android Development] bdcrim:
7

Okay this will work. I did not want to come across as high jacking Taosaur's thread. Forgive me if I have. I assume you are wanting to set CM7 as your primary rom and CM9 as your alternate rom. Here is what I did following the guide and a little trial and error. After you add repartitionDual2GBdata, CMpri2alt, reformatData and Revert dual boot to your SD card:

1. Boot into recovery and backup the rom that you want to be primary, CM7 in your case.

2. I went ahead and Formatted System, Data and Cache and installed the repartitionDual2GBdata zip.

3. Power down the nook and reboot back into recovery.

4. Install the reformatData zip. Power down and reboot back into recovery.

5. Install the rom and gapps that you want to run as alternate. If you have a backup of that rom you can restore it now instead.

6. Install CMpri2alt zip from the SD card. This renames the kernel and ramdisk of the alternate rom so it triggers the boot and moves the rom to the alternate partitions.

7. Format system, data and cache in preparation for the primary rom.

8. Install the rom as you normally would any rom plus the gapps. If you have a backup that you want to restore, it is a little more tricky. If you restore the entire backup, the boot restore portion will overwrite the new changes to the dual boot partition and you will lose the ability to boot to the alternate rom. If you are restoring a backup, choose advanced in the backup/restore function and try restoring system and data only. The cache will be rebuilt after boot. Reboot and see if it will fully load. It did not for me and I had to power down and intall the original rom and gapps that I had backed up. I did not wipe anything at this point. Reboot and you should be able to use the primary rom.

9. You are probably aware that in order to get into the alternate rom with the newly added Cyanoboot, you have to go into the bootloader and then boot to alternate. The volume up/down buttons did not work for me.

I have CM9 on primary and CM7 on alternate, which nothing changes other than the rom choices, the process is the same. You may note that any future rom backups that you do to the primary rom should preserve the dual boot function. Restoring that rom should not overwrite the boot partition. Also if you have tried and failed, you can always install the revert dual boot zip and start from the top.Good luck.
[Nook Color Android Development] zires:
Thanks. I will try and report back.

Update: CM7 is freezing now at startup. Trying one more time, then I'm going to reformat and just put cm7 on my nook and wait for a stable cm9. Thanks for your help.

Edit again: So I had a couple of freezes. So tried again and did not restore system, but only restored data. All looks good now. Now I am backing up my rom again and I'm going to try CMpri2alt or CMpri2pri again. For the last three or four times that I have totally redone everything, whenever I run CMpri2alt or CMpri2pri, it reboots into CM7 but a fresh install with gapps and CM9 is gone. If I boot to alternate without running CMpri2alt or CMpri2pri it boots into CM9 but once I do CMpri2alt or CMpri2pri I get CM7 with gapps and the whole reset up. Confused? I sure am.

Edit again: So all seems well now. CM7 works and I can alternate boot into CM9. Couple of questions. So if I run CMpri2pri, it will not let CM9 boot as primary it is only for backups etc (within recovery)? What is the process to upgrade both and keep anything that I install?

Edit again: Just noticed that my media has shrunk down to less than 500mb. What gives?

Please reply someone!
[Nook Color Android Development] bdcrim:
Is that 500MB on both the primary and alternate roms? Also, I responded to your PM.
[Nook Color Android Development] zires:
I thought the emmc was shared?
[Nook Color Android Development] bdcrim:
No, the sd card is shared. Each Rom should have around 1.23 GB's of space on EMMC if things partitioned correctly.
[Nook Color Android Development] zires:
Tested created a new folder on the emmc of cm7 booted into cm9 and the folder was there.