[Nook Color Android Development] nadafinger:
So you can adb even if the device isn't fully booted? This is where I am this morning as well. I could never resolve my wifi issues with the nookie-froyo3.img image...and got bored/frustrated. There were a TON of FC's while the wifi wasn't working. The system was stable (kernel) other than app FC's/wifi issue. I went back and tried the first image from the OP and it booted, and then hung on the 2nd attempt to boot up (after running the makepart.sh script). Do you think it's trying to drop to a FSCK or such during the boot process? As it's not "looping" I'm pretty sure it's hung waiting on some input. This is further supported by the fact that kurtA was able to get the boot to complete after running the mount command for /data manually. Today I'm going back to the newer image, as I have nothing better to try. I'm still thinking this is something to do with the larger cards, as most folks who have posted about this are running 16GB. Since I forgot my dang charger cable and I have ~25% battery I have nothing better to do with it than hack around with adb anyway. I'll reload, try to get it stable, and then attempt to clear dalvik cache as a workaround for the intermittent issues.

Question: Is there a way to disable the boot-wrapper image file so that I can actually watch the boot sequence? although dmesg isn't turning much up that I can see, it would be interesting to confirm what's hanging on the boot (seems like mounts).

Also, I'm gonna head up to Microcenter and get an 8GB card for further testing. I need one for my Incredible anyway. Would it help if I took an image of my 16GB card after it starts to hang and uploaded it somewhere for you brianf21?

UPDATE: I have imaged the card, booted, allowed 15 minutes to normalize. Then I did all the steps in the makepart.sh script manually via adb and rebooted. Held breathe, worked. So an interesting observation is this: You mentioned that the formatpart.sh script was necessary a few posts ago, and from kurtA's output it looks like for him it was. BUT, I have not run that and here is my current status:

# df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 244.3M 12.0K 244.3M 0% /dev

tmpfs 244.3M 0 244.3M 0% /mnt/asec

/dev/block/mmcblk0p2 69.5M 43.5K 69.5M 0% /rom

/dev/block/mmcblk1p2 144.3M 101.4M 35.4M 74% /system

/dev/block/mmcblk1p3 687.1M 85.1M 567.2M 13% /data

/dev/block/mmcblk0p7 341.8M 10.1M 328.2M 3% /mnt/cache

/dev/block/vold/179:20

14.5G 192.0K 14.5G 0% /mnt/sdcard

/dev/block/vold/179:20

14.5G 192.0K 14.5G 0% /mnt/secure/asec

which is what his looked like only after running the 2nd script. Not sure how to explain that. I went into the /mnt/sdcard filesystem to touch a file for testing and there were already directories there that had been auto-created by the Android system and Nook apps.

Currently I am rebooting a few times to see if it hangs up, and then will update.

UPDATE2: So I violated the first rule of IT, and made two changes at once. The question is which, if either, is the culprit. So I rebooted 3-4 times with absolutely NO problems. Then I turned on wifi, which was a little strange acting. It saw my AP, and I told it to connect, and it went into this loop of connecting, disconnecting, connecting, disconnecting. I had that happen yesterday too. I have found if you touch the AP again, and tell it to connect again, it will. Once I had it connected, I fired up Dolphin, and made sure I was online...check. Then I tried to add my google account. At that point the thing went nuts, FC's of all the google apps, but also FC's of softkeys as well, and basically became unusable. I let it sit, and it just kept incrementing FC's of basically every running app. so I rebooted...and it came up. I get very hopeful at this point, but as soon as I unlock the screen a few things happen: 1) it is asking me to select my default home button action. Since I have never loaded a new app or anything that was a bit concerning. 2) I got FC's on every google app, and a few others as well (I'm thinking essentially everything). 3) when I selected "softkeys" and made it default it started looping through and throwing a FC on softkeys about every 2 seconds. I couldn't ADB to the system during all of this, so I was stuck with one choice, and rebooted. Now it hung up like before, and a quick check shows that /data is not mounted. There have been two posts about /data earlier in the thread, the first about /data being corrupted on a completely stable system, and the poster was wondering if overclocking caused it. The poster in that case mounted the card in a linux machine and fsck'd it, and found the corruption that way. He didn't mention if that was corrected via the FSCK or allowed him to boot after that. presumably the same thing is happening to myself and kurtA, which is why it's not mounting on boot (probably it's asking or recommending a fsck but we just can't see it). I do not have a *nix machine with an SDreader, so I can't try this myself...and the busybox fsck errors out looking for an /etc/fstab file. I'm pretty sure something along the way is corrupting /data. Enabling wifi? Google apps? Unrelated coincidence? So I can either 1)Burn again, and try a reboot after wifi enabled to see if it's wifi, then try google apps. or 2). try to fix the corruption of /data with an fsck, then try reloading the gapps. decisions,decisions.