yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] jpiermarini:
Let me rephrase what i have said in my original post. i put the sd card into my laptop that has a built in sd card slot. i tried to burn the image with win32diskimager but it gave me an error saying the sd card didn't have enough space. according to angomy's post a couple posts down i'm probably getting that error because i'm using the built in sd reader.

after failing at win32diskimager i then booted into ubuntu and burned the image with the dd command. after burning the image with that command the sd card doesn't come up in ubuntu although i can see it with fdisk -l and when i try it in windows it pops up as needing to be formatted.

i'll go ahead and use gparted to get the sd card back to normal and maybe try to find an sd card reader here at work.
[Nook Color Android Development] japzone:
That's probably best.

____________________________________________________

Sent from NookColor CM7 uSD using Tapatalk
[Nook Color Android Development] TabletConnect:
My wife got a Nook Color and I just want to confirm that doing creating this CM7 installer on the SD card will basically allow her to dual boot (stock Nook & CM7). The NC will run CM7 if the SD card is installed. If it is not, regular stock Nook will boot. Am I correct in understanding this?

If not, where can I find information on setting up a bootable SD card with CM7?

thank you all
[Nook Color Android Development] cameraz:
You're in the right thread, and your assumptions are correct. Your wife's Nook Color will run CM7 with the SD card installed, and will revert back to stock if she powers off, removes the card and then reboots.

It's the best of both worlds!
[Nook Color Android Development] angomy:
This will allow you to create a CM7 install on SD card.

(Oops I misread your post, running on 4 hours of sleep today) -- feel free to ignore below if you don't care about multi booting :)

If you want dual boot functionality you will need to get either of the two multi-boots offered here and install it after finishing the agnostic card setup:

rookie1's multi-boot - no menu, depending on how you write the boot order file it will let you boot normally into SD, into EMMC (regular Nook stock) when you hold down N button, and recovery mode when you hold down both volume keys. You can switch the priority boot order by creating and editing a file.

http://xdaforums.com/showthread.php?t=947698&highlight=multi-boot

j4mm3r's multi-boot has a menu. When you boot up you have 5 seconds to hit a key to manually select what to boot from (sd vs mmc vs recovery). If left alone it will boot to w/e default you have it set (see his instructions in:)

http://xdaforums.com/showthread.php?t=962708&highlight=multi-boot

Alternatively, you can do the 2GB expandable sd install w/ j4mm3r's multi-boot menu already incorporated -- but if you're using a 16GB+ card be forewarned that some have had issues (works fine 8GB under).

http://xdaforums.com/showthread.php?t=1022786

I'm using the size-agnostic image with CM7 and nookie1's multi boot on a 16GB Sandisk, it's working fantastic.
[Nook Color Android Development] TabletConnect:
Do I need to be rooted before doing this? Thanks
[Nook Color Android Development] Taosaur:
As angomy said, you should probably ignore the things he posted because they don't apply to your situation. You do not need to root or otherwise disturb the operating system on your NC; if you follow the instructions in the OP of this thread, you will have CM7 running entirely from an SD card. You may want to consult this thread about an appropriate card to use:

http://xdaforums.com/showthread.php?p=13567695

If you have any trouble, this blog post includes more step-by-step instructions as well as a five-part video of the process:

http://www.anamardoll.com/2011/04/ereader-running-cm7-firmware-on-nook.html

All the paragraphs leading up to "Here is a list of all the things you will need" are a rambling introduction you can probably skip, as is the first video, but from there on it's quite helpful.
[Nook Color Android Development] angomy:
Edit: (If you mean CM7 + Nookie1's multiboot, or the 2GB expandable w/ multiboot install) - No, but it requires that you fiddle with files instead of just running the installers :) My install is entirely on the card, nothing's been done to touch the stock OS on the Nook's native drive.
[Nook Color Android Development] paschott:
Is there an easy way to see the large partition of the SD card when dual-booting into the default Nook OS? It sees the card, but seems to only see the "boot" partition from the Nook OS. I'd love to be able to use the whole card if possible. Any ideas on ways to do that without rooting my Nook? Every suggestion I've seen implies that I need to root first and I really don't have a desire to do that right now.

Thanks.
[Nook Color Android Development] GTT1:
FROM OP

""How to update to a new build:

put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)

Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.

The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.

""

I have tried and tried and cannot get this to update my SD. I know the CM7.0.3 file is good because I tested it on another card.

I guess I need to start from scratch unless someone has a thought on what I may be doing wrong.
[Nook Color Android Development] Taosaur:
Based on the thread, I'll assume by "dual-booting" you mean you're running CM7 from SD and the stock OS 1.2 from eMMC. If that's the case, are you aware that CM7 running off the SD does recognize the 5GB storage partition on eMMC? If there are files you want shared between the two OSes, you do have that much space available. If you need more space for magazines or kids books from B&N, you could always get a second card and swap.
[Nook Color Android Development] Techienana:
I was thinking of something you could try but I don't think I know enough about your problem to put my thought out here. Can you give a little more detail?
[Nook Color Android Development] Taosaur:
It took a couple tries, but I just got 7.0.3 installed myself. Like Techienana said, it's hard to know if you're doing anything wrong without knowing what you've actually done. The steps are:

1. Place the update .zip file in the SD card's boot partition. If you are using a Windows machine, the boot partition will be the only one recognized. You cannot place this file in the boot partition from within CM7*

2. Return the SD card to your NC and boot into recovery by holding p+n for 3-4 seconds after the Touch the Future of Reading screen appears and then releasing (if the NC shuts off again, you held them too long).

3. A little penguin should appear in the upper left corner (landscape) followed by some text saying it's looking for update packages. If it finds one, you will see many many lines of text as it installs all the elements of the new ROM.

4. When the penguin says "safe to power off" or when the screen goes blank, power off then power back on. Things won't look any different, but go to Settings>CyanogenMod Settings>System and you should see you're running 7.0.3.

Did you definitely get the .zip into the boot partition? Did you successfully boot to the update/recovery screen with the penguin? If so, what did it say?

If the penguin detects your update package but does not install it successfully (as happened to me on round 1), you have to start at step 1, because it will erase the file.

*Except--and I can't confirm because I screwed up this time around--if you have automatic updates enabled, CM7 will download the update automatically, and offer to "reboot and install" WHICH DOES NOT WORK. However, none of the automatic "boot to recovery" options within CM7 work for me, so I'm guessing if I'd picked up at step 2 with a manual recovery boot, it would have installed.

Instead, I dl'ed the file in Windows, mounted the SD card, and tried to copy it over. The update...zip file wasn't visible on the SD, but Windows prompted me to Copy and Replace, then failed to do so, which I'm guessing corrupted the file. When I tried to boot, the penguin found the file but failed to install it, so I started over at step 1 and succeeded.
[Nook Color Android Development] GTT1:
Finally got it to work after different times releasing. For others it is just before the words go off the screen.

Might just start over again and reload everything clean including apps.
[Nook Color Android Development] Awats:
I got it work. Nice Taosaur!

I did notice the first time it didn't update and just went into the old build. I rebooted again and held the buttons down as long as I could stand it while the opening screen was up ("Touch the Future or Reading" .. yeah, touch this.

It's a bit of a game of chicken ... or penguin ... around how long you have to hold the buttons. Who's going to flinch first! I count to 5 after the TtFoR comes up.

Voila!

Edit: I have discovered that the success of this stuff is heavily dependent on the speed/quality of the SD card. I started with some 4GB Class 4 Patriots and had continual problems with things locking up, Forced Close, big delays, etc.

I got a Sandisk Class 4 2GB and things starting working. Especially when overclocked. I then got a Sandisk 16GB and things still worked fine. For fun, I tried the 4 GB Patriots again just to see if my lack of experience was the problem.

Nope, they just don't work right. I would assume it's related to the legendary 4kb block write performance. What works on the Sandisk won't work (or is at least very flaky) on the Patriots.

Maybe things are even better flashing to the internal emmc, but for now SD is how I roll.

I wonder if I can go backwards on builds (in case one doesn't work ...) Hmm....
[Nook Color Android Development] paschott:
Actually, I was hoping to use more of the storage on the SD card for actual books and such. In general, I plan to use the NC as intended, as an e-reader. I don't have major issues with the software and so far performance for my Android on SD card has been pretty bad (haven't had/taken the time to investigate). I'd just like the option to use Android as desired by booting into that, but also have a lot of space for my books. I have a 16GB uSD, but when in the Nook boot, can only see the boot partition. Wondering if there's a way to change that so I can see more partitions or if I just need to find a way to resize that partition to make it more usable when I'm using the stock Nook ROM.

Thanks.
[Nook Color Android Development] Moritzio:
Great build and wonderful instructions. Worked without a hitch. Thanks very much for making the Nook Color more useful.
[Nook Color Android Development] Taosaur:
Recovery boot behavior seems really inconsistent to me. Verygreen was mentioning a few days ago about some new behavior he observed:

I did get this behavior, ONCE, while booting to recovery on the eMMC. I held down n, pressed and released power, and as long as I held n, it stayed on "Read Forever," then when I released, it booted into CWM (which I flashed over the stock recovery on my eMMC). Booting to recovery on the SD, I had to hold both buttons as I described a couple posts back, and attempting to boot into recovery on eMMC, I was getting all kinds of results, sometimes with the NC shutting back off after only two seconds holding power, sometimes booting into stock OS instead of recovery, and that one time holding at Read Forever until I released n.

I don't want to test it too much, because the NC was intended more as an 'always on' device, and I don't want to wear it out with all these power cycles, but it's odd.
[Nook Color Android Development] Taosaur:
Hmm, I hadn't been able to get the stock OS to recognize my CM7 card as anything but "ready to remove" previously, but I inserted it before stock OS was fully loaded and it does see the boot partition. In theory, I don't see why you couldn't use something like EASUS or gparted to make the boot partition 14GB, but I'm not so knowledgeable on rearranging partitions. It might be worth backing up your SD card and giving it a try. Worst case scenario, you reformat and start from scratch.

ETA: Some apps that default to SD storage may give you trouble.
[Nook Color Android Development] jpiermarini:
incase anyone has having the same issue as me, i connected the sd card through usb rather than the sd card reader on my laptop and was able to burn the image using win32diskimager. i am now able to use cm7 on my nook and it is pretty slick.
[Nook Color Android Development] japzone:
Stock will only look for the First Partition on the SD card. If you want to see the "sdcard" 4th partition your stock will have to be Rooted.

PM me if you have more questions.

____________________________________________________

Sent from NookColor CM7 uSD using Tapatalk
[Nook Color Android Development] paschott:
I was afraid of that. Oh well - not really looking to root anything right now. I may look at resizing the partitions to increase the size of the boot partition. It's not highly critical - was just hoping to have both a usable portion of the SD card for Nook usage and an SD to boot into Android if desired. (Besides - one of the PDF readers for Nook only reads from SD cards and it's supposedly tons better than the stock reader.)

Thanks for the answer.
[Nook Color Android Development] DizzyDen:
Burn the image to the SD card... BEFORE booting it up... use easeus or mintools and resize the only partition at that point to what you want (I have only been able to get up to slightly below 4GB to work).... THEN put it in nook and let it create the remaining partitions... load ROM and whatever....

After this... you have a larger "boot" partition that can be used by stock as well for booting... Can also do a dual boot and not have to take it out to boot stock when wanted.
[Nook Color Android Development] paschott:
I'll give that a try. I'm not so far in that I'm committed to what's on the current card. I got everything installed, but then was having extremely slow performance downloading apps to the tablet. I can definitely reformat and 3-4GB is quite a bit when it comes to eBooks. I don't plan to carry my entire collection on the card, just want to use better PDF tools and not root the device yet.

I appreciate the suggestion. Sounds like that will do what I need.
[Nook Color Android Development] swoozle:
racks--->verygreen

This is a simple, obvious question that I can't believe hasn't been asked, but i DID look, so either my search skills suck monkey butt or the answer is obvious without asking. Take your pick...

So having suitably basted myself in derpitude before the cranky-gods:

If I was to want to switch from the Racks CWM for Flashing Roms to SDcard Method to the Size Agnostic Verygreen Method, would I just do this part of the verygreen method and charge onward?

How to update if you already installed using v1 of the installer and don't want to reinstall (understandably):

* Get u-boot.zip file from attachment in this post: http://xdaforums.com/show...&postcount=153

* Unpack the u-boot.bin file and put it onto parttion 1 of the SD card instead of the one there.

* Rename file named uRecImage on the first partition to uRecImg (doh!)

* Get this uRamdisk file, rename it to uRecRam and then put the result to the 1st partition on the uSD card instead of the file with the same name there​

Thank you for your patience, assistance and general air of intelligence and wit...

And by the way, that new haircut really does look good on you.
[Nook Color Android Development] racks11479:
No need to root your stock nook. If you have a CM7 sdcard, root explorer or file expert(free from market), and a terminal emulator app. Which you should have with cm7. Try the following steps.

-using root explorer or file expert. Mount system as R/W

-open up a terminal emulator and run the following commands

$ su
# mkdir /mnt/nooksys
# mount /dev/block/mmcblk0p5 /mnt/nooksys

-now exit out of terminal emulator

-open up root explorer/file expert

-navigate to /mnt/nooksys

-you should now be able to see the stock nook system partition

-open up the /etc directory

-long press the vold.fstab file.

-it should give you an option to open with text editor

-change the line where it mounts the /sdcard from auto to 4

-exit out of root explorer

-reboot to stock

-it should now mount the 4th partition of your sdcard

-Racks
[Nook Color Android Development] Taosaur:
Awesome info for us linux-illiterate folks, Racks :)

On a related note, my explorations in response to paschott's dilemma game me an alternate, perhaps simpler solution to my original problem of installing gapps (and/or updates) without a card reader. While inserting my SD card after the stock OS loads only gets me "SD card safe to remove," inserting it before the stock OS has loaded (for instance, on the blinding white "Nook Color" splash screen) does give me access to the SD boot partition, at which point I can mount it over USB in my PC :cool:
[Nook Color Android Development] TabletConnect:
dumb question but am I suppose to rename the generic-sdcard-v1.1.img.gz by deleting the ".gz"? Win32diskimager cannot detect the file with the .gz extension.

However by deleting the .gz extension, win32diskimager appears to burn the image. I unmount the SD card. Plug it in again to my computer but get messages that I need to format the card. It does appear that the image is being burnt. I tried this multiple times. I formatted with both FAT and FAT32 and I get the same message that I need to format the card. I am using a 2GB microSD.

Help.
[Nook Color Android Development] dzigns:
You need to extract (or unzip) the file using a program such as 7-Zip - there are other programs that will do the job (just make sure they support the .gz extension), however 7-Zip is the program I use.
[Nook Color Android Development] Taosaur:
Yes, .gz is a compressed archive like .rar or .zip. If you right click the file, you'll probably find you already have software installed that can extract it, and there will be an "extract" option. If not, install something like 7-zip or winrar.
[Nook Color Android Development] lschroeder:
Installed ClockworkMod 3.0.2.8. Can not get update-cm-7.1.0-RC0-encore-2.6.32-beta2.zip to bootup with this installer. Use to work with 3.0.1.0 in emmc.

Next I tried to install update-cm-7.1.0-RC0-encore-2.6.32-signed.zip which had previously installed when I had 3.0.1.0. In both cases it would not go into boot recovery.

Not sure if 3.0.2.8 causing problems or something else. Any suggestions? I know this has its own installer. Maybe partition/card too full, md5 checksum error?
[Nook Color Android Development] TheTodFather:
Can't get OC Kernel 4-24 1.3ghz loaded on this

How do you get this to load? I've downloaded the Sd version of the kernel and changed the ext3 to ext4 and still no go on the nightly 69. I even tried 7.03 but i knew that was going to be the same problem but tried anyway. It just hangs like i'm in the wrong ext. Anyone have any suggestions?
[Nook Color Android Development] TheTodFather:
Ok went to the nookcolor irc and now i hear i need to push more then just uimage over to the boot drive. I was told to push system over as well. I'm on a win machine so it's not letting me look at the partitons and folders like if i was on my linux machine. So...gonna put the sd card back to stock boot into it and see if i can find this allusive "system folder" then push the system folder from the kernel into it and try again.

Ok I apparently I don't know what the hell i'm talking about!

EverGreen could you make some kind of update in the OP cause totally lost this 2.3.4 is killing me...
[Nook Color Android Development] Awats:
I finally gave up on installing the OC kernel from the zip file and do this:

1. Unzip the build and Overclock zip files (I use 4/24) to their own directories (WinRAR 3.80 is perfect since an extraction will create the folder in the same location at the original zip file.)

2 Copy the overclock "uImage" file to "kernel" (I copy and then rename it)

3. Copy the "kernel" file and "system" folder to the build folder (replacing the ones in build)

4. Re-zipping the build back up (don't forget to check/select ZIP!)

5. Copy that new zip file over to the SD card (I add -OC to the end of the file name)

6. Put the card back into the nook, face north and ...

A quick reboot, let it expand and load and I was updated with the OC on any new build I want.

Credit goes to the people that fingered this simple process out! ;)
[Nook Color Android Development] gregh77:
can u post that image file so we dont have trouble with it working?
[Nook Color Android Development] TheTodFather:
I'm doing this with windows and i'm limited on what it sees in that drive.
[Nook Color Android Development] TabletConnect:
Thanks. I got it working except now I am having trouble with installing the Gapps. I cannot get into the Recovery mode. I tried holding N and power button together but the bootloader message never appears. Any ideas?
[Nook Color Android Development] TheTodFather:
Yeah an image would be awesome. I don't see anywhere in the "H" drive called BOot where it says kernel....just urecram uimage mlo uboot.bin urecimg. I don't see kernel. I just assumed you swap the uimage.
[Nook Color Android Development] danvee:
If you load the gapps .zip and the build .zip to the SD card at the same time, the installer will handle all of it at once....
[Nook Color Android Development] DizzyDen:
Part of the CM7 install script extracts the file called kernel in the package to uImage on the device.... that's why I had told people to copy the OC uImage file and rename it kernel.... then add the contents of system folder from kernel zip to the CM7 image.... don't even have to extract the CM7 to do it... just add it to the zip with update option.
[Nook Color Android Development] TabletConnect:
I didn't do that. I did the build first and now I am trying to install the gapps. But I can't get into recovery mode. Do I need to install cwr?
[Nook Color Android Development] rhester72:
1. Power off

2. Hold down the n/home button

3. Also hold down the power button

4. While holding both, wait until you see the white-on-black first Nook boot screen (i.e. u-boot)

5. Count one-one thousand, two-one thousand, three and release the power button (keeping the N/home button depressed)

6. Count one-one thousand, two-one thousand, three and release the n button

7. Wait a moment, pray, and hopefully you'll be in recovery mode

The above works for me about 85% of the time.

Rodney
[Nook Color Android Development] tutech:
Are there any plans to update this installer to work off the 1.2 u-boot ("Read Forever") instead of the 1.1 u-boot ("The Future of Reading") ?
[Nook Color Android Development] khaytsus:
It's simply timing.... Personally what works for me is this:

Power off

Hold the N key

Hold the power button and count exactly 8 seconds

Release the Power key

DO NOT release the N key, keep holding it.

Works every time for me.
[Nook Color Android Development] TheTodFather:
Copy the "kernel" file and "system" folder to the build folder (replacing the ones in build)

OK i got as far as renaming the uimage from the OC file to kernel but the part that I don't seem to grasp is where this system folder goes. I understand it goes to the one in the build that is already on the SD card but my question is, am I suppose to be seeing a folder on the Nook's Sd called system. Because like I said earlier i Just see only the basic image files only, like urecram, uimage.

then add the contents of system folder from kernel zip to the CM7 image. Ok and by system folder you just mean the folder in the OC kernel named system and not to copy over the Meta folder?

just add it to the zip with update option ok so do i take just the uimage , rename it kernel, just add in only the system folder and put them into an update.zip? lol