yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mkhopper:
If I had 6 thumbs, they'd all be way up! :D

Simple as cake install and it's running great.

One question though... Is there any danger of the device calling home and pulling out an update that might break root?

I was running stock+root only for months since I bought the device in May ('11) and when the auto-update occurred in August (? I forget when it happened), it ended up breaking root and for whatever reason I had a really hard time getting it rooted again. Is there something that needs to be turned off to prevent the device from receiving any auto updates?
[Nook Color Android Development] Taosaur:
Flashing CWM to internal recovery should block all OTA updates. Just go into the ROM Manager app in CM7 (or Phiremod) and "Flash ClockworkMod Recovery." It will also block 8-failed-boots restore.
[Nook Color Android Development] hawkwolf223:
Yes, made sure to follow tht. Originally set it to 2GB/4GB, then went back and repartitioned to 1GB/5GB. Still no joy.

At this point, with the price drop and announcement of the Tablet, I think I will restore to stock everything, and see if I am within the 30 day return time. If so, I will wait on the Tablet. If not, running from SD isn't as fast as I would like, but it does run...

Thanks.
[Nook Color Android Development] Taosaur:
Hey, re-reading your original post it's not clear: you did re-download the 1.3 zip between attempts, right? A corrupt file probably just wouldn't install, but it might cause you the problems you saw.

Understandable if you don't want to bother - if I were in a position to upgrade to the new tablet, I'd be all over it (assuming it gets root in a timely fashion). I didn't expect to be tempted, but the hardware improvements they made in a slightly slimmer but otherwise identical package... I could hit that.
[Nook Color Android Development] sryan1983:
Boot Loop

First and foremost, thank you for this guide. It seems though that I am having a problem when booting into the alternate partition (stock rooted). I keep getting stuck in boot loop. After some research, I believe I am boot looping for the same that people are in this thread (Adobe Flash/Air). I downloaded the link from that thread and installed it via CWM. However, I am still in boot loop.

I believe that the zip is installing to the primary partition and not the secondary partition though. How can I fix this so that I can install the Adobe Flash/Air fix to the alternate partition? Any help would be greatly appreciated as I have not been able to boot into stock rooted since the first time. The primary partition of CM7 boots with no problems. Thanks again for your help.
[Nook Color Android Development] sryan1983:
I hate to quote my own quote but I think I have some new information. It looks like I would need to modify the updater-script from the zip file in the link from the quote.

The current updater-script looks like this:

ui_print("::Flash and AIR Fix::");

ui_print("Mounting partitions...");
mount("ext2", "/dev/block/mmcblk0p5", "/system");
mount("ext3", "/dev/block/mmcblk0p6", "/data");

delete_recursive("/data/data/com.adobe.flashplayer");
delete("/system/app/FlashPlayer.apk","/data/app/com.adobe.flashplayer-1.apk","/data/dalvik-cache/system@app@FlashPlayer.apk@classes.dex","/data/dalvik-cache/data@app@com.adobe.flashplayer-1.apk@classes.dex");

delete_recursive("/data/data/com.adobe.air");
delete("/system/app/AirRuntime.apk","/data/app/com.adobe.air-1.apk","/data/dalvik-cache/system@app@AirRuntime.apk@classes.dex","/data/dalvik-cache/data@app@com.adobe.air-1.apk@classes.dex");

ui_print("Flash Player and AIR Fix...");
package_extract_dir("data/app", "/data/app");
ui_print("Chmodding installed apks...");
# /data/app is system:system, rwxrwxr-x
# subfiles are system:system
set_perm(1000, 1000, 0775, "/data/app");

unmount("/system");
unmount("/data");

ui_print("All done!");

That being said, it looks like I would have to just change the mount points and paths to the alternate partition. Does anyone smarter than myself have the information on this? Or can anyone modify the updater-script for me? Thanks again.

Edit: Problem solved. As soon as I get permission from the author, I will post a link.

Edit 2: Here is the link for those that may need it.
[Nook Color Android Development] Taosaur:
I added your link to the OP, sryan. Glad you got it figured out.
[Nook Color Android Development] stwallman:
THANKS!!

Just wanted to say a big THANK YOU for this!! Love being able to dual-boot from emmc and have the best of both worlds.
[Nook Color Android Development] vrman:
Thanks,

This guide worked perfect for me. I started with 1.3 rooted and added CM7.1.
[Nook Color Android Development] Shortyred:
Ok I have read thru this but still just a little confused. I have cm7.03 on emmc I want to go back to stock 1.3 and sideload. This if I understand will put both on the emmc? Is that right?
[Nook Color Android Development] Taosaur:
Correct. If all you want is stock 1.3, make a CWM card (link's in the OP) and flash one of the 1.3 zips (also in the OP), or use CWM on your device if you already have it. If you want CM7.1, too, you can follow this guide, or there's a link in my sig for SD install instructions using verygreen's SASD method.
[Nook Color Android Development] jasoraso:
For what is worth, I took the 1.3_dual update, and put in the new 1.4.1 files > so here is a 1.4.1_dual update that can be flashed. This will flash the new B&N 1.4.1 update to the second partition.

http://www.mediafire.com/?9xaqc6qe7cbdb82
[Nook Color Android Development] traumadog:
Hey - have to see how things go since I reflashed stock with the 1.4 update, but one weird issue I had with the stock 1.3/CM7 dual-boot setup was that the stock 1.3 apps didn't install at all - is that because all the room for those apps were taken by the dual-boot? If so, is there a way to tweak the settings to allow stock apps some room?
[Nook Color Android Development] jdaudlin:
Just to be clear, this update will only remove root from my alt partition not my CM7 partition correct!
[Nook Color Android Development] Taosaur:
Hmm, that I don't know. You should have at least some room for B&N apps. I never spent much time on the B&N side, and now I've actually reverted to straight CM7 (no dual boot). Pretty much the only use I ever had for stock was answering other people's questions ;)

Correct, it won't affect CM7.
[Nook Color Android Development] Shortyred:
Hi I installed b&n 1.3 from SD card and when I reboot I just hang at the colored b&n screen. I can still boot to cm7 on SD card. I figure I did something wrong.
[Nook Color Android Development] Taosaur:
The sense-making you not are do.

Did you use this guide? Are you saying you used a CWM SD card and you're stuck at step 9, but have a separate SD with CM7 that still works?

I have no clue if it's relevant to your situation, but you might have a look at the boot-loop fix under Other Resources in the OP.

Otherwise, I would say try, try again, possibly using the other 1.3 zip (if you're using a CWM SD, it doesn't matter if you use the keep-CWM zip or the full restore).
[Nook Color Android Development] Shortyred:
Ok sorry I know I didn't say it right, I'll try again. I made the 4gig boot disk from the open instructions. I put B&N 1.3 keep cm7 zip on the SD. I also put cm7.1 on the SD card. I booted with the SD card and installed 1.3 then reboot without the card mounted. I get the keep reading screen and then the Barnes & Noble screen and that's it. I have a dual boot SD card that I can sideload with. Hope that's a better explanation.
[Nook Color Android Development] Taosaur:
Soooo...

Yes or no?
[Nook Color Android Development] Shortyred:
Yes.
[Nook Color Android Development] Taosaur:
Well, I would just start again from step 5.

The only red flag I see is that you say you made a 4GB "boot disk" (I assume you mean CWM); did you use CWM 3.2.0.1, the current version? Because there's no 4GB image for that version in the thread linked in the OP, only a 1GB image. If you have an older version, you can update the card with these instructions.
[Nook Color Android Development] cyberkhan:
Followed the guide and the whole process was like a breeze!

Installed as advised and updated with 1.4 (link provided on P-9 and OP).

Working perfect. Thanks.
[Nook Color Android Development] SCrid2000:
Just in case anyone is wondering, this guide works great for dual booting 1.4.1 and the ICS alpha found in http://xdaforums.com/showthread.php?t=1370873
[Nook Color Android Development] Shortyred:
Got it installed. Ran into the loop got that handled too!! 8)
[Nook Color Android Development] Taosaur:
Glad to hear it :)

I'm not brave enough (or maybe I'm too lazy) to load ICS yet, but it looks like it's coming along nicely. Still, unless the devs are just lowering our expectations, it doesn't look like CM9 will have many advantages over CM7--no new hardware acceleration, in particular.
[Nook Color Android Development] traumadog:
I dunno - I ran the current ICS version on an SD card install, and it seemed just as smooth as CM7 on the EMMC - but did have the added bonus of the improved ICS interface.

As for my other post - I now have (from scratch) dual-booted 1.4.1 and CM7 on EMMC - and I still can't load apps on the stock ROM. Now I get a pop-up message saying I can't load the app, and that there might be insufficient memory... which is odd as the stock ROM still reads plenty of available space.

Edit: added the relevant screenshots.
[Nook Color Android Development] jasoraso:
Hmm. If you havent tried yet, I would suggest if you reflash back to stock (there is an old dualboot thread that has a .zip to undo the dualboot partitions.)

Then, I would flash the 1gb/5gb partition .zip to make sure your partitions are the way that bn shipped originally, not the partition layout that bn switched to later on. (I think you need a reboot and reformat here, too.)

Then flash the 1.2/1.3/1.4 to the stock partition, and follow the steps to flash the dualboot prep etc.
[Nook Color Android Development] traumadog:
Actually, that's how I wound up doing it this time - starting from a stock 1.4 install, and swapping for the non-blue-dot partitioning. I had wiped the stock rom cache/data to the point that I actually had to re-install the apps that were already there. Of course, that now gives me the error you see. Not a huge deal, as I can get those apps in CM7, though having something like Evernote would have been nice.
[Nook Color Android Development] mkm1126:
Thanks for the great guide! I am running BN 1.3 with a cm build and all is well. One question...I want to use the 1.4 update found in the OP. I see the latest MN works with this, but how do I root it in this situation? Do I have to return to stock partition, then root and move it back over, or is there another way? Thanks!
[Nook Color Android Development] Taosaur:
I just did a fresh run-through of this guide to set up the CM9 preview alongside B&N 1.4, and like others I wasn't able to download apps from the B&N market. I don't know how it would affect books and magazines. For apps at least, it's looking like you'll either want to stick with 1.3 on secondary, or install them all before you move stock.

I also discovered, as one person had reported in rajendra's thread, that his 1.3-full-restore zip is actually 1.2. I'm guessing he just renamed and uploaded the wrong file when he was modding nemith's zips, but I went ahead and changed the info in the OP to direct to nemith's. I just used B&N's file to update stock to 1.4 before I moved it.

If you want to re-root, yes, you'll have to start over with stock on primary, though see above about the issues with the B&N market on secondary in 1.4.
[Nook Color Android Development] traumadog:
Just to clarify: books download and install ok on the stock partition. I was able to download and start reading a book where I left off. AFAIK, only apps do not. Not sure about magazines, though. That's what was making me think this was a partition use issue... just like how the stock ROM on EMMC would only see the first partition of the external SD card.
[Nook Color Android Development] Taosaur:
Weelll, I've been messing around a bit more, and I now have 1.4 on secondary with apps installing.

I flashed 1.3-keep-CWM, tried installing some free apps with no problem, moved it to secondary, and while I didn't get error messages, apps just stayed at "downloading" indefinitely. Just to check that it worked, I flashed jasoraso's update, and when I booted into it and tried downloading apps, I had no problems at all.

Sooo I'm thinking maybe you want to move 1.3 to secondary and then update, rather than update on primary and then move like I did yesterday. Or, maybe it's just a fluke :S

Feedback is welcomed.
[Nook Color Android Development] rajendra82:
The zip that moves primary boot to secondary partitions had one error in the script tools/copyboot.sh. On one line after unpacking the ramdisk it looks for the line "chmod 771 cache" in init.rc, but that line apparently changed between Eclair and Froyo versions to "chmod 770 cache". Since it does not find that line, the sed command does not correctly substitute it with the replacement lines. I believe this is the cause of the B&N Shop not working properly after moving to secondary issue, because I have used the corrected script in my 1.3 updater and now my 1.4.1 updater files. Neither one has had these B&N shop issues.

The corrected CWM zip is attached.
[Nook Color Android Development] Taosaur:
rajendra82 is attributing the B&N market errors to a problem in the froyo-to-dualboot script, and has made a revised version, but I don't think I'll have a chance to test it before the holiday. If anyone is up for testing, it's linked in this post: http://xdaforums.com/showpost.php?p=20522956&postcount=53

Again, running jasoraso's alt-partition 1.4 update on a 1.3 install seemed to resolve the issue for me. It's possible flashing it over an existing 1.4 install that's getting market errors may do the trick, too.

ETA: ninja'd by raj :D
[Nook Color Android Development] rajendra82:
Jasoraso's update also appears to be using the correct version of the copyboot.sh script when applying the B&N update. If you flash it (or my 1.4.1 secondary update zip) over an already moved 1.4.1, it will fix the ramdisk by rerunning the updated script. You will lose root on secondary though, as those files apply the full 1.4.1 update to secondary /system.

Let me provide a zip that simply overwrites the affected secondary ramdisk that was moved using the buggy script with a fresh copy of B&N 1.4.1 ramdisk, and runs it again through the corrected script. This should keep everything else on your secondary partition intact, and should resolve the B&N Shop issues without losing any settings, root, apps, books, or data.

Of course there is no way for me to test this file on my wife's Nook Color, as it doesn't have that issue, but give it a shot. I could try to break her B&N Shop, and then fix it using this, but on second thoughts, I won't do it. I like my nuts attached, thank you very much.
[Nook Color Android Development] mkm1126:
+1 this worked for me as well. Thanks!
[Nook Color Android Development] traumadog:
Ok - update:

Doing both the jasoraso and rajendra updates seemed to do the trick.

Thanks guys!
[Nook Color Android Development] jimhorner5405:
dual boot

OK..i gave my wife a NC for Xmas. I want to create a SD card that it will boot from so i can get on the market. I am not sure how to go about it. I have rooted all of my phones but i am nervous about this one. does anyone have a video showing how to do this? Sorry..im a visual learner. any help would be appreciated.

thanks
[Nook Color Android Development] jmocherman:
second partition freezes

I have phiremod on the primary partition and stock 1.4.1 on the secondary partition.

Everything is working as it should, but freezes on the stock lock screen. It boots normally into the secondary partition, but as soon as I see the stock nook lock screen, it freezes up and I have to do a reset.

Any ideas?

I have tried reflashing, redownloading, rerunning the dual boot directions multiple times. Has anyone else had this issue? If so, how can I fix this?
[Nook Color Android Development] rajendra82:
To create the bootable SD card, all you need is a spare microSD card that you don't need for storage, a card reader, and download the shareware program to write the bootable image to the card. You won't need to make any changes to the Nook Color. It's very similar to writing a bootable Linux LiveCD on a Windows machine and then booting with it in the drive but not installing it on the hard drive. There is absolutely nothing to be nervous about, as no permanent changes will be made to anything. If you somehow mess up creation of the card, the Nook Color just won't boot with it inserted, but will do it just fine without it in the slot. Just take it out, reformat the card, and try again if you want to.
[Nook Color Android Development] Taosaur:
I updated the OP with a link to ManualNooter 5.12.20, which is somewhat buried in the MN thread.
[Nook Color Android Development] atulb:
root BN 1.4

Is there a way to root the alt-partition without going through the whole process again?
[Nook Color Android Development] Taosaur:
Short answer: no. Honestly, though, once you've done this process once or twice, another run-through is fairly quick and easy. And you wouldn't have to go through the *whole* process again, just install clean stock to primary, root it, move it, and install CM7.

If stock is set up just how you like it (which I doubt if you haven't rooted yet), you could use DeanGibson's Alt2Pri file here to move it back to Primary, where it can be rooted. That method will wipe CM7, but you can always restore it from a back-up later.
[Nook Color Android Development] deanerh:
Total noob question......how do I flash the two zip fix files? Can I use ROM Manager when I'm booted into CM7?
[Nook Color Android Development] Taosaur:
I really don't think you could have completed the process described in this thread and still need to ask that question.

All the zip files in this thread would be flashed with CMW. You only need to flash one to fix the problem. If you didn't set up an internal dual boot per the OP, these zips will not fix your problem.
[Nook Color Android Development] deanerh:
The Catch-22 here is that the contributors to this forum, including yourself, do such a great job of outlining the steps needed to accomplish some amazing things that people like myself are able to follow those steps without always completely following what's going on under the hood, so to speak. So yes, I did get my NC partitioned and working. My question was based on the fact that I was pretty sure I understood what needed to happen but wanted to be 100% so that I wouldnt screw things up

I truly appreciate your efforts on this project as well as your response. It would have been nice if you could have managed to leave off the somewhat demeaning opening.
[Nook Color Android Development] Taosaur:
Sorry if I was a bit of a jerk--I really did see about 65% odds you'd wandered into the wrong thread, what with all the zip-flashing involved in the OP. I just noticed that I left something out of the OP, from my blog post:
[Nook Color Android Development] deanerh:
No prob. Thanks again for all your work.
[Nook Color Android Development] ChrisFSU:
nevermind - figured it out

Thanks!
[Nook Color Android Development] CrackedTech:
I've had the same thing happen to me three times now. I've gone through the setup and gotten it going with no problems. I use it for a few days both using the stock partition for reading and the CM7 partition for everything else. At some point though I boot into stock and when I go to boot back into CM7 it just boot loops at the spinning circle animation and never changes. I can still boot into the stock partition just fine though.

The first time this happened I wiped completely and started from scratch. The second time I spent a lot of time trying various things. Wiped cache and Dalvik, and various other things, tried just reloading over the top and eventually just started from scratch again.

That brings me to now with the same problem for the third time. I've again tried re-flashing just CM7 and wiping cache and Dalvik with no luck. I have no problem starting from scratch as between setting this up for friends and fixing my own I can do it pretty quickly but I'd really like to know what's going on. I searched this thread but couldn't find anyone else with this problem. If anyone can help me out I would very much appreciate it.
[Nook Color Android Development] danootz:
Other Resources:

Remove dual boot: returns partitioning to stock (1GB/5GB, non-blue-dot)

----

I have Nook Stock install in the alternate partition. Will running the above zip in the OP delete the Nook Stock install and restore the partitioning to the way it was originally?

Will I basically just have CM7 and the drive space back to normal?
[Nook Color Android Development] Taosaur:
I don't *think* RDB will leave you a working CM7 install, but you can just make a backup of CM7 and restore it after running RDB.
[Nook Color Android Development] lekofraggle:
Hello,

There has not been much action here in a while, so perhaps I am messing something up. I have read and tried all I can think of.

I have cm9 and manual nootered 1.4.1 on a non blue dot nook color.

My primary partition works great, but when I move the manual nootered partition I get the install error. This happens even when I try to install an app lready on my sd card, or I try to download from the Market.

I tried moving by flashing the updated froyo to dual boot script, and have the same error.

I tried flashing the just fix the ualtram file, but my nook hangs at the N.

If I use the update 1.4.1, it fixes the issue, but I loose root and Market.

If I move it back to primary and use manual nooter, Everything works fine until I move it back.

So, is there any way I can do both? Or do I have to pick and choose? I have a large sd card, but the install is too laggy.

Note, I am running clockwork mod off an sd card.

Thank you again for all your help.

~Leko
[Nook Color Android Development] Taosaur:
Sorry, leko, but I've never rooted stock myself or heard of someone else having your issue. I know there was some weird stuff going on w/ MN to get the market working after the 1.4.1 update, but I imagine you've read up on it more than I have. If you can't find a workaround, I'd say get stock set up the best you can with the apps you want before running the 1.4.1-to-alt update and/or start looking at ways to satisfy your root needs in CM7/9.
[Nook Color Android Development] Taosaur:
CM7/CM9 dual boot is go! With a little advice from Racks11479 (actual advice was over PM, but this got the ball rolling) I was able to edit DeanGibson's two-way scripts (Pri2Alt/Alt2Pri) to work w/ CM builds. I only tested each one until I got them working, but they worked for me:

EDIT: below scripts are probably not compatible with the old dualboot method; see next post /EDIT

CMpri2alt.zip Moves either CM7 or CM9 to secondary partition.

CMalt2pri.zip Moves either CM7 or CM9 from secondary back to the primary partition.

No need to wipe system/data/cache before running these zips--they do it for you, and obviously you can't wipe the secondaries direct from CWM, anyway.

These files will not work for stock; DeanGibson's zips a few posts back should. Between his set for stock and my set for CyanogenMod, everyone should have pretty much total flexibility now. If I get a chance, I'll edit and rename his zips to be more consistent with the rest of the guide (they currently include a different boot menu that doesn't seem CM compatible--easily fixed by swapping in any recent CM uboot.bin) and dump everything in the OP.

I know there's some cleanup to be done in the OP, and I'll add these links in when I have the time and spare brain cycles to whip the whole thing into shape--my plate's pretty full just now.