Database Develop

Nook wont boot off Sdcard..Boots normally

no matter how many times i make the sdcard image, my nook refuses to boot off of it. Ive tried with Mac, WIndows, and Ubuntu and all failed. When i pop in the sdcard the nook just boots up normally...please someone help me. Ive been trying to get this to work since the second the first instructions were posted on nook devs

I had this problem as well. I ended up using a different USB MicroSD card reader and it worked. Try using a different MicroSD card, usually ones less than 2GB are safest, as they are not SDHC, and thus are compatible with more SD card readers...

hharte said:
I had this problem as well. I ended up using a different USB MicroSD card reader and it worked. Try using a different MicroSD card, usually ones less than 2GB are safest, as they are not SDHC, and thus are compatible with more SD card readers...
Click to expand...
Click to collapse
that might explain it lol..i've been using the 16gb that came with my galaxy s and using my phone as the sdreader
has one had success flashing the image through their phones or the nook itself?

Did you make the carding using winimage yet? For me, that was the method that worked the most consistently.
To check it, pop the card in your reader and see if there is a single ~40mb partition named nooter. That pretty much says the card is what it is supposed to be.
Unplug the nook, power it off by holding the power button until it turns off. put the card into the nook, plug it into your computer. In a little time, you should notice it saying about a new device connected, or some complaining about not being able to find the drivers. Let it go for about a minute after that and then remove the card and reboot the nook.
If it still boots normally with the card your just made, try using another card and see if that works. Also, if you have access to a mac, before you make the card with winimage (on the windows machine), use Disk utility to partition the card with 1 partition, free space.
It sounds kinda quirky, but it is how I got it to work.

I had to try 4 different computers before I found one that would work with either Winimage or Cygwin. Just keep trying different things and you'll eventually get it.

I originally tried using the Nook Color itself as the SD card reader, which did not work. Since the only USB card reader I had handy was not SDHC, I went down to a 2GB SD card, and it worked.

Help - Trouble w/Winimage
I'm using 64bit Vista and can open Winimage but when I try to install the 40Mb img file to the SD Card, all I get on the card is four files totaling about 11 Mb.
Could someone please post instruction for making an uSD image of Nooter 0.2
Thanks in advance

bobdude5 said:
that might explain it lol..i've been using the 16gb that came with my galaxy s and using my phone as the sdreader
has one had success flashing the image through their phones or the nook itself?
Click to expand...
Click to collapse
[mbm] initially had trouble as well since he was using his Nook as a card reader. Generally only dedicated card readers will reliably work. I'll go add that to the wiki page.

pokey9000 said:
[mbm] initially had trouble as well since he was using his Nook as a card reader. Generally only dedicated card readers will reliably work. I'll go add that to the wiki page.
Click to expand...
Click to collapse
did he end up using a card reader or did he get it to work?

My mistake was
Pokey9000 pointed out that I was making a simple mistake that stopped my card from working:
make sure your are writing to the whole disk, not a partition.
of = /dev/disk# (good)
of = /dev/disk#p# (bad)
I was adding the partition number to the end of my device string.

bobdude5 said:
did he end up using a card reader or did he get it to work?
Click to expand...
Click to collapse
IIRC he switched to his laptop's SD reader with an adapter and got it working.

pokey9000 said:
IIRC he switched to his laptop's SD reader with an adapter and got it working.
Click to expand...
Click to collapse
i just tried a 2gb sdcard..didnt work.. so its the reader. I hope a usb adapter will work

bobdude5 said:
i just tried a 2gb sdcard..didnt work.. so its the reader. I hope a usb adapter will work
Click to expand...
Click to collapse
via the laptop SDcard slot, the image doesn't work, and I used a USB SDcard reader, it worked.

+1 request for help
docfreed said:
I'm using 64bit Vista and can open Winimage but when I try to install the 40Mb img file to the SD Card, all I get on the card is four files totaling about 11 Mb.
Could someone please post instruction for making an uSD image of Nooter 0.2
Thanks in advance
Click to expand...
Click to collapse
+1 - despite searching and multiple efforts, I still am unable to get a useful microSD card to root the NC

docfreed said:
I'm using 64bit Vista and can open Winimage but when I try to install the 40Mb img file to the SD Card, all I get on the card is four files totaling about 11 Mb.
Could someone please post instruction for making an uSD image of Nooter 0.2
Thanks in advance
Click to expand...
Click to collapse
drbowden said:
+1 - despite searching and multiple efforts, I still am unable to get a useful microSD card to root the NC
Click to expand...
Click to collapse
That's OK!
After doing the winimage the microSD will have a 40MB partition with about 30MB free space and only about 7.5MB of files. It should work!

Finally Successful!
Finally got it done! Now on to loading useful apps and see how the NOOK holds up to work!

So excited to try and...
Grrr. both my sandisk and generic mini card readers suddenly all decide to fail/stop working and only found one of my 2gb sd cards after my move haha...
Murphy's law, such as life is..
-CC

Heya guys, Android n00b, but old time iphoney.
I to am having the same problem. I have been writing sd cards off multiple machines, bought more sd cards, etc.
Any help would be greatly appreciated! tx
Details:
Linux Mint 8 - Main
Windows 7 - tried and no success in results
Nook Color - Running firmware 1.0.1
8GB PNY HC uSD - image written sucessfully - Failed to boot in NC
2GB Sandisk uSD - image written sucessfully - Failed to boot in NC
1GB Kingston uSD - image written sucessfully - Failed to boot in NC
Latest nooter tried - auto-nooter-2.12.18.img - writes sucessfully - shows 2 partitions (NooterFiles,AutoNooter2)
Install notes:
I follow the directions to the letter. I have set up android sdk, and the other files needed from when this first became available. (I know they're not needed at the moment, but giving a history)
The image writes successfully. If I re-insert the card into my pc, then it reads as un-recognized. However, taking a leap of faith I put the card into the powered down NC. Plug in the usb cord, and it reboots just as normal.
Now after it boots. I swipe to open, and it goes into usb mode. Now my computer can see the 2 partitions listed through the nc.
Upon investigation I found that the partitions were not bootable. Aha! So I tried making them bootable. No success.
I'm at a loss, any help/points in the right direction would be greatly appreciated.

[Q] Honeycomb not booting from SD card.[1.1.0 issue?]

I have a 16 GB class 4 Sandisk card.
I ran the following command and successfully wrote the img to my SD Card
[email protected]:~$ umount /dev/sdg
[email protected]:~$ sudo dd if=nookhoney04.img of=/dev/sdg bs=1M
Click to expand...
Click to collapse
The SD Card now has a system, boot, data, and sdcard partiton. So I assume it was finished. I also received a confirmation message stating that it successfully wrote 3.7 GB to the card.
All appears well, but when resetting the nook, it almost immediately boots into stock instead of the sd card.
Am I missing something, or is this a card issue?

it might be the card, class 4 is really slow for honeycomb

Would "really slow" cause it to entirely skip the boot.
People claim to have got it working with a class 2, even if it is slow, it should still boot...

I appologize for bumping this, but I would really like a more definitive answer than "slow".

MXIIA said:
I have a 16 GB class 4 Sandisk card.
I ran the following command and successfully wrote the img to my SD Card
The SD Card now has a system, boot, data, and sdcard partiton. So I assume it was finished. I also received a confirmation message stating that it successfully wrote 3.7 GB to the card.
All appears well, but when resetting the nook, it almost immediately boots into stock instead of the sd card.
Am I missing something, or is this a card issue?
Click to expand...
Click to collapse
If they're in that order then somethings wrong. It should be Boot,System,Data,sdcard. Also a slow card shouldn't cause the boot sequence to be skipped but there could just be a compatability issue with your card
I suggest trying again to see if it works (btw I never use the BS=1M but that shouldn't cause any problems)

They're in the orter of boot, system, data, sdcard.
I used the bs=1M when I wrote autonooter, I guess I'll try it without that parameter since that's the only thing I can change.
It's kind of odd that the SD card would not boot... I've booted onto this SD card before when testing Froyo and doing some Clockwork recovery.
There are no buttons I have to hold to force a boot?
I am powering it on via plugging it into my computer, though I have tried a hard power on.

This maybe a card issue. So far all 16Gb cards I installed Froyo/Honeycomb booted successfully as long as you do not repartition the card with default head/sec/cyl (must be 255/63/the rest).
However at this moment neither Froyo nor Honeycomb work on any 16Gb card I tried. It installs fine, and boots ok, but after the first reboot the data partition gets corrupted almost immediately, and remounts read-only. If you eject the card, connect it to a Linux machine and run fsck.ext3 on /dev/sd?3 it will fix it, but it will be broken again during next reboot. Same images/files work fine on the same Nook on a 8Gb card.

No need to unmount the card. And normally your sd card is mmcblk0 or mmcblk1? Format your card, insert it into your computers sd card reader and in a terminal type "sudo fdisk -l" look for the device that is the same size as your card. Also, did you use your nook as the card reader for the computer? Most of the time, using the nook as your card reader when writing images doesnt work, you have to use the computers reader directly.
edit: Possible compatibility issues. 16gb's seem to have problems with corrupted partitions when writing sd images.

Hmm, that's interesting, is there any way to change the cyl-dead-sector data on linux?
If not, I guess I'll buy an 8GB class 6+ soon.
http://www.amazon.com/Transcend-microSDHC-Class-Memory-TS8GUSDHC6E/dp/B0026L7DG0
Would that card suffice?

Yes, that card seems to get really nice reviews as far as running HC goes. That or a Sandisk.

Well that card is under $20 dollars, so it works perfectly for me. Thank you for your feedback

I bought A-Data 8Gb class 10 microSD in Fry's, and it seem to work very well. $13.
Not sure how long it gonna last, but if it lasts a year, good enough for me.
The issue I mentioned, however, is not due to the card quality. 'badblocks' utility consistently showed all those cards having NO bad blocks, and I tested at least three different 16GB cards - Wintec, Patriot and A-Data.

RileyGrant said:
Yes, that card seems to get really nice reviews as far as running HC goes. That or a Sandisk.
Click to expand...
Click to collapse
Well, the card came in.... and no luck, same thing... I'm going to try it on Windows instead of Linux, see if that changes anything...

After I "upgraded" to 1.1.0 it jacked up my ability to boot from external SD card. Lots of random process failures and can no longer read my class 10 card at all. Going to revert to 1.0.1 I think... or else flash a CFW on instead. Seems like they added something nasty to the update.

Just to give some newcomers my experiences with the following two cards:
Lexar Class 10 32GB:
Stuck forever at the black screen with the message "android_" at the lower left. Tried both v3 and v4 of the honeycomb SD image. Neither worked.
Transcend Class 6 16GB:
Tried v4. Same pronlem as the Lexar. Stuck forever at the "android_" screen. Switched to v3. Bingo, it booted!
I should be receiving a Patriots 16GB tomorrow and will put it to test.

xdadidida said:
After I "upgraded" to 1.1.0 it jacked up my ability to boot from external SD card. Lots of random process failures and can no longer read my class 10 card at all. Going to revert to 1.0.1 I think... or else flash a CFW on instead. Seems like they added something nasty to the update.
Click to expand...
Click to collapse
Hmmm... that seems interesting... can anyone else confirm this?

I have two SD cards. One gives me the infamous encrypted file system error and the other just sits there looping on the android splash screen. Before updating, both ran honeycomb fine (CL4 and CL10).

Size-agnostic SD Card CM7 gets stuck while installing CM7

Hi,
I am unable to post in the dev forums. hence opening this thread.
I am facing a problem installing sd card bootable CM7.
I am refering to the folowing thread: [ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater: http://forum.xda-developers.com/showthread.php?t=1000957
I do the following:
1. Burn the 9M image (that would unpack into ~130M disk image)
2. Put the downloaded CM nightly build on the sdcard
3. Put the card in the nook color and boot
4. The nook boots to the installation process...penguin image in a corner and starts the process
However, it gets stuck at "Writing superblocks and filesystem accouting information".
I dunno if its stuck or not......because the cursor keeps on blinking.
Its been about 30 minutes and the screen stays in the above status only.
For information, I am using 16gb Kingmax Class 10 microsd card.
Any help will be greatly appreciated.......

acme2ajax said:
Hi,
I am unable to post in the dev forums. hence opening this thread.
I am facing a problem installing sd card bootable CM7.
I am refering to the folowing thread: [ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater: http://forum.xda-developers.com/showthread.php?t=1000957
I do the following:
1. Burn the 9M image (that would unpack into ~130M disk image)
2. Put the downloaded CM nightly build on the sdcard
3. Put the card in the nook color and boot
4. The nook boots to the installation process...penguin image in a corner and starts the process
However, it gets stuck at "Writing superblocks and filesystem accouting information".
I dunno if its stuck or not......because the cursor keeps on blinking.
Its been about 30 minutes and the screen stays in the above status only.
For information, I am using 16gb Kingmax Class 10 microsd card.
Any help will be greatly appreciated.......
Click to expand...
Click to collapse
Ummm... did you unpack the image prior to burning it to your Sdcard?
In addition it is not proven yet to work on 16gig cards, it has only been tested up to 8gig cards.
Edit: Others now have posted that 16gig cards do not work.

And Class 10 cards are known to have issue with Nook.
Search TITLES in this Forum only for "card" for threads on sd cards.

ADude said:
And Class 10 cards are known to have issue with Nook.
Search TITLES in this Forum only for "card" for threads on sd cards.
Click to expand...
Click to collapse
Hi Adude...Thanks for the update.
Have a small doubt...
I am able to install and run successfully, the sdcard bootable CM7 bt image...which is for 2gb card.
I, then, expand that partition to the rest of the card.
So is it the size of the card thats the issue?
Can this 'size agnostic' image be modified to write only to 2 or 4 gb and then we can expand the rest. I will like to ask this question to verygreen, but i still have some posts to go till I can paste in dev forums.
Thanks again for the info.......

Bumping an old thread, since I have the exact same problem, and can't post in the proper thread as well.
But I used a 2GB class 2 card( I think, it's a generic card that you get in the bundle when you buy a phone) instead, but got the same message.
Did I harm the card in anyway? Can I use it again for this procedure? Or do I have to reflash it in some way?

BrotherZero said:
Bumping an old thread, since I have the exact same problem, and can't post in the proper thread as well.
But I used a 2GB class 2 card( I think, it's a generic card that you get in the bundle when you buy a phone) instead, but got the same message.
Did I harm the card in anyway? Can I use it again for this procedure? Or do I have to reflash it in some way?
Click to expand...
Click to collapse
Generic Class 2 card. You answered your own question, it's probably too slow.

Pity, that's the only card I have lying around.
I'm very new to this so sorry for some very basic questions. But:
1. How do I restore the card to it's original state? I tried the HPUSBFW.EXE file that is in the link above(how to flash a bootable SD guide) but it says that I need admin rights even though I already am admin. Is there any other way to restore the card?
2. I have another generic 2GB from a Sony X10 mini pro, but no idea to try that then? What kind of SD-card should I buy? Since I saw that too fast SD cards have problem as well.

I also can't post in the dev thread and am having issues with this. I'm using an 8gb sandisk class 4 microsd card. I used win32imager to burn the agnostic iso file to the card. Then I clicked exit, unmounted the drive, and plugged it back in. Now the drive shows as a 115mb drive with 107mb free. In gparted it shows as 2 partitions, 1 as 115mb and another as unallocated with the rest of the 8gb. Windows can't see the unallocated one though.
So right now I'm stuck and can't copy the nightly cm7 build onto the drive. Anyone know why it formatted it like this and what I can do to fix it?
Here's an image of what I'm talking about:

107 MB is enough
gmanpie said:
I also can't post in the dev thread and am having issues with this. I'm using an 8gb sandisk class 4 microsd card. I used win32imager to burn the agnostic iso file to the card. Then I clicked exit, unmounted the drive, and plugged it back in. Now the drive shows as a 115mb drive with 107mb free. In gparted it shows as 2 partitions, 1 as 115mb and another as unallocated with the rest of the 8gb. Windows can't see the unallocated one though.
So right now I'm stuck and can't copy the nightly cm7 build onto the drive. Anyone know why it formatted it like this and what I can do to fix it?
Here's an image of what I'm talking about:
Click to expand...
Click to collapse
The nightly CM7 -87 file has around 91 MB (here: http://download.cyanogenmod.com/get/cm_encore_full-87.zip), so you should have enough space to copy it onto your sd card. Actually, that leaves more than 15 MB available, so I suggest you also put the gapps in your SD card (here: http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110307-signed.zip)
About the unallocated space, it will be partitioned by the installer accordingly once you boot the NC with your SD card in it.

Looks like it's working now. I fit the nightly build on there but couldn't fit gapps(144mb). I messed up my froyo install earlier trying to put cm7 on, so I was worried I'd be stuck with a half functional rom for my upcoming 14 hr flight :/
Ok, now for my next question. How do I install it to the emmc? I tried installing it through froyo, but when I deleted the system folder and reset it to factory settings it messed up the froyo install, so now the rom manager doesn't work.
[Edit:] going to try following this thread:
http://fineoils.blogspot.com/2011/04/nookcolor-with-cyanogen-mod-70-emmc.html

What? Gapps is ~5MB only. If you're trying to install with both at the same time verygreen's instructions say that you should flash CM7 and turn on wifi first, prior to flashing gapps.
To install to EMMC you need to burn a CWM SD card, plop the nightly zip on there, boot up with it, then install zip from SD card (select the nightly). Wipe caches/data. Remove CWM card, hit reboot option in CWM menu. You'll need to either have a fresh SD card or reformat the CWM card since CM7 on EMMC requires an SD card in. Instructions for doing this (step by step) are somewhere in General forum by eyeballer.
(Also of note: the info that 16GB cards do not work with this image is no longer true)

Could anybody use a 16Gb sd card so far? I bought one just for the nook and now I found out that its not working - damn! I can't give it back so what? pls help!

Earymgn said:
Could anybody use a 16Gb sd card so far? I bought one just for the nook and now I found out that its not working - damn! I can't give it back so what? pls help!
Click to expand...
Click to collapse
I used SanDisk 16Gb and everything worked like a charm.

stud_muffler said:
I used SanDisk 16Gb and everything worked like a charm.
Click to expand...
Click to collapse
I did too(both with issues and successfully), the only problem I had with my card is that with the size of cm7 and gapps you ahve to flash them separately, so do cm7 first, put the gapps on the boot partition then reboot into recovery.
if you don't do that you'll run out of space on the boot partition during installation.

I used verygreen's instructions to put CM& on a Sandisk 16 gig class 4. Worked the first time I tried. After CM7 I shut down, put gapps on, then rebooted into recovery.
I think the majority of the problems people are having is NOT READING the part in the verygreen instructions about using Sandisk cards.

Imbroglio said:
I used verygreen's instructions to put CM& on a Sandisk 16 gig class 4. Worked the first time I tried. After CM7 I shut down, put gapps on, then rebooted into recovery.
I think the majority of the problems people are having is NOT READING the part in the verygreen instructions about using Sandisk cards.
Click to expand...
Click to collapse
Sandisk is not required.. I've also used Transcend and Kingston. Class 4 and 6 between the three.
What is required is a card that's not crap, or works like crap in the Nook Color. An OS does a lot of small operations or uses a lot of small files, so even if the card is great at mass transfers but sucks at smaller ones, it's going to be a bad experience.
Sandisk is one way to avoid it. So if you're buying one, might as well make it Sandisk. Any others.... if it doesn't work right, try a different card. That easy.

Froyo "damaged SD card" error

I seen to be the only guy left with this problem. I have burned Nookie FROYO to an 8gb card. Using Mini tool partition wizard i then extend the last partition to cover the unused space. Then the Nook boots fine but gives me the 'damaged sd card' error. I tried the Vold method people used on older NF builds, but that seems just to ruin the image. If i don't resize the partition, everything runs fine and i can use the very limited free space on he card as normal. I wanted to try Easeus instead of minitool, thinking it might be something in the software, but i can't get Easeus to see the card at all after it is burned.
Can anyone help?

any advice on where to go here? I also asked at android central, and not getting any hits there either?
Thanks,
Brian

I've also tried deleting the sdcard partition and recreating it the right size. Since resizing didn't work, I thought this might. But it didn't. Still getting the 'Damaged SD card' error.
How is it that I'm the only one out there having this issue? Very frustrating.
-Brian

had same problem through the sd card in my fascinate and tried to format didn't work then plugged in my phone to my usb cable then unplugged went back and it auto formated for me so now i have my nook sd card all good just a little help

Well, I tried that as well. I plug the NC in, and it shows up as two different USB devices. E and F on my Win 7 machine. After quite some time waiting, I can actually open drive F in windows. Unfortunately, when I unplug my NC and try and remount the SD card, it doesn't do anything different. Still gives me the damaged SD card error.....
What else can I do here?
-Brian

[Q] Problem making Win32Imager image

I'd like to copy the contents on my CM7 on an 8G Transcend uSD card to a Sandisk 8G card using Win32DiskImager on my Win 7 64 bit laptop. I've verified with EASUS that the Transcend is using the full 8G but when I create an image file it's only 4G. If I to write that to the Sandisk the process finishes almost immediately and writes nothing to the card. I've rebooted and tried several different external card readers with the same result. I have successfully used these to create 8G backup images previously so am stumped why the process isn't working this time. Suggestions?

Are you running Win32DiskImager as "Administrator"?

azj said:
I'd like to copy the contents on my CM7 on an 8G Transcend uSD card to a Sandisk 8G card using Win32DiskImager on my Win 7 64 bit laptop. I've verified with EASUS that the Transcend is using the full 8G but when I create an image file it's only 4G. If I to write that to the Sandisk the process finishes almost immediately and writes nothing to the card. I've rebooted and tried several different external card readers with the same result. I have successfully used these to create 8G backup images previously so am stumped why the process isn't working this time. Suggestions?
Click to expand...
Click to collapse
Which version of win32diskimager?
I find version "RELEASE-0.2-r23" to work best... it still always reads to about 4gig... bit it writes the image correctly.

Definitely make sure you're running with elevated priviledges (administrator). These disk imaging programs have the annoying habit of providing very little feedback when they fail due to an accounts rights issue. Took me a long time to figure this out when I first tried to install Phiremod and then again a month later when I decided to try an OC kernel (by this time I'd forgotten about the problem).

dsf3g said:
Definitely make sure you're running with elevated priviledges (administrator). These disk imaging programs have the annoying habit of providing very little feedback when they fail due to an accounts rights issue. Took me a long time to figure this out when I first tried to install Phiremod and then again a month later when I decided to try an OC kernel (by this time I'd forgotten about the problem).
Click to expand...
Click to collapse
Ahhh... as I have disabled profile to prevent the priviledges issue in win7.... I forgot about that requirement.

Jimbo67 said:
Are you running Win32DiskImager as "Administrator"?
Click to expand...
Click to collapse
Yes I ran it on an administrator account. Will have to check the version when I get home.

I had a really old version of the program. Downloaded the current version. It still creates a 4G img file but when I write it back to the new card it's the full 8G image. The contents of the boot partition look correct but the Nook just skips the SD card when booting up.
Next, I'm going to use Easeus to reduce the total used on the card to 4G, image that, write to new card and see what happens.

i have encountered win32image problem before where it fails to write to disk with erorr but when i use earlier version 0.1 it works

Followed these steps and the new card boots correctly:
- Use EASEUS to reduce the last partition so the total used on the card is 4G or less
- Use Win32DiskImager to read old card and write new card
- Use EASEUS to increase the last partition to full size.
Of course this only works if you can do the first step.
As an aside: performance with the new Sandisk card is considerable faster than the old card.

for some reason the new version of windisk imager does not write the image to the card properly for me. i always get corrupt data. i use an older windisk and everything works great. i'm on windows 7 if that makes a difference.