Related
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.
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).
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.
well i followed the instructions here http://forum.xda-developers.com/showthread.php?t=1000957 and the penguin came up and the program did its thing. but after it shuts down, i reboot and it stays on the loading screen. i have a sandisk 2 gb card. what could be my issue?
thanks in advance for any help
bootloop, bootloop and bootloop. Let me out!
Me too!
Do I need to root first? Read something about "clearing the cache"? Does it works? How to do it?
I tried installer 1.3 and CM7 nightly -87, then installer 1.2.1 and stable 7.0.3 and 7.0.2. The latter froze during installation!
Also tried recovery after bootloop.
Even left for hours booting. Nothing.
I am using a Sony 4g SD card Class 4 which I formatted using my Laptop and my Nook. Neither way worked.
I am using Win32 disk imager. The Nook simply won´t start if I use Winimage to mount the SD.
Oh yeah! My NC soft is 1.2.0 and the model (I think) BNVR20.
System partition might be corrupted on the SD card. Make sure you always remove the sdcard SAFELY from your PC.
I've never had a problem just removing the SD card but it is wise to "eject" the drive from My Computer on Windows systems to make sure it closes the files and isn't doing a delayed write.
The microSDHC disk may have something to do with it.
Try to use a SanDisk 8GB class 4 microSDHC disk
(you can get one from Amazon for about $11.00 including shipping).
Either one of these builds should work:
-- system #1 running @925MHz max.
----- generic-sdcard-v1.3.img
----- gapps-gb-20110307-signed
----- update-cm-7.0.3-encore-signed
-- system #2 running @1300MHz max.
----- generic-sdcard-v1.3.img
----- update-cm-phiremod-nook-6.3
Hope that helps and good luck.
Hi,
does it loop the android man and spinning wheel over and over again, or really hangs? Mine was looping the "spinning wheel" - what helped was removing \data\system\batterystats.bin file via ADB.
Regards,
Maciej
Hey Matchay,
In my case it loops the android man and spinning wheel over and over again.
But I don´t know the first thing about ADB. Where can I get it? And what command line should I use?
Thnx.
The thing is, if you didn't have the "USB Debugging" enabled in settings, the effort to install ADB might be in vain. I do not know any more, what the default setting in a fresh CM7 installation is. For instructions, look here http://forum.xda-developers.com/showthread.php?t=910008. If all works, you'll only need to execute "adb shell" and then "rm \data\system\batterystats.bin" afterwards.
I believe the second option could be to use a fake Hitachi Microdrive driver to trick out the USB Card Reader driver and then reach the /data partition of the SD card directly from Windows. Instructions here: http://www.1src.com/forums/showpost.php?p=1010117&postcount=1
Edit: the second option won't work. Windows doesn't know how to access ext2/3 partitions, even if they can be seen in the Disk Manager after installing the fake microdrive driver.
CM7 running now
Okay, so I got it running.
Guess what I did...
come on...
Yes... I changed the SD card.
New SD card. No more problem.
The first SD card I used was a Sony 4g Class 4. I tested it with H2test2 and the writing speed was around 5-6 MB/s (thus a Class 4) but the reading speed was only 11-12 MB/s (baaad Sony, bad!). Then, I tested a older card I had, a Toshiba 2g Class 2, the writing speed was around 2-3 MB/s (thus a Class 2) but the reading speed was 18-19 MB/s (see Sony!).
So I used the Toshiba SD card and everything is running smooth now.
Now, what have we learned from this?
GET A FREAKING SANDISK CLASS 4 before you even start!!
Hi, i used win32diskimager to burn my 16 gig microsd card. Now it reads 300 mb and even when i reformat it, it won't go back to the 16gb. I was wondering how i can fix this and get my sd card back to it's real size
mastermind1234321 said:
Hi, i used win32diskimager to burn my 16 gig microsd card. Now it reads 300 mb and even when i reformat it, it won't go back to the 16gb. I was wondering how i can fix this and get my sd card back to it's real size
Click to expand...
Click to collapse
use easeus partition master.
ShutterPeep said:
use easeus partition master.
Click to expand...
Click to collapse
Well, yes. Specifically, use EASEUS to delete all partitions except the storage partition (the largest) then drag that partition to fill all the unallocated space. Windows only recognizes the first partition on any flash storage.
If you are running off SD card - and left the stock NC in tact on the EMMC - you can use settings to reformat your card. It'll have a couple folders you will have to delete afterwards - but it should free up the memory to original state.
mastermind1234321 said:
Hi, i used win32diskimager to burn my 16 gig microsd card. Now it reads 300 mb and even when i reformat it, it won't go back to the 16gb. I was wondering how i can fix this and get my sd card back to it's real size
Click to expand...
Click to collapse
If you are doing this in Windows you probably will have to go to Disk Management and delete the first partition and then format.
Right click "My Computer"
Select "Manage"
Select "Disk Management" (you need Administrative privileges)
Be very careful to pick the correct drive letter!
Right click the area where the drive letter appears and select "Delete partition"
Create a new primary partition and format
What I did to restore my micro SD card completely to a formatted state was put it in a SD adapter and put it in my digital camera and formatted the card. It removed all partitions and files. Works everytime.
Sent from my MB860
SD card 16 go to 74mo partition
Taosaur said:
Well, yes. Specifically, use EASEUS to delete all partitions except the storage partition (the largest) then drag that partition to fill all the unallocated space. Windows only recognizes the first partition on any flash storage.
Click to expand...
Click to collapse
You made my day ! Thanks for this information! After set up debian for arm on my 16 go sd card I just had a 74mo partition I got my full space back with your advice thanks
I am using this card for Raspberry Pi and I set up debian for arm with Win32DiskImager. It is at this moment the problem happened
The simpler solution now is probably to use SD Formatter for Windows. It should wipe all partitions and get you back to a 'default' state.
Use SD Formatter
Another simple way is to look for a program called SD Formatter (free) on the internet.
and format the SD card (make sure it is correct drive letter) using NOT the default setting but i believe it is a pulldown call (erase all zeros)
Great program, if you play with SD cards you should get it.
Everett1954
Not Enough Disk Space Error using Win32diskmanager
I have been working at this for hours and can't seem to figure it out.......I have an 8 gb empty (formatted fat32) micro sd which I am trying to write the clockworkmod 8gb file using win32diskimager. Every time I try to write it I get an Error Message "Not Enough Disk Space".......does anyone know what I should do??
djfury said:
I have been working at this for hours and can't seem to figure it out.......I have an 8 gb empty (formatted fat32) micro sd which I am trying to write the clockworkmod 8gb file using win32diskimager. Every time I try to write it I get an Error Message "Not Enough Disk Space".......does anyone know what I should do??
Click to expand...
Click to collapse
Just find and write a smaller image file to the card. Then use a partition manager program like Mini-Tool Partition Wizard (free) to expand the partition to fill the card. I have 200MB version in my tips thread linked in my signature. It has CWM 5.5.0.4 on it.
Use the 4 GB CWM image... then use minitools partition manager or eausus to resize to full capacity.
Not Enough Disk Space Error using Win32diskmanager
DizzyDen said:
Use the 4 GB CWM image... then use minitools partition manager or eausus to resize to full capacity.
Click to expand...
Click to collapse
First time to post. Hope I'm in the right thread. Have read many of the threads here regarding Nook Color, CM7, CM9 et al. I really enjoy learning from all the information posted. I currently have an unrooted NC running CM9 on a micro SD and love it.
My problem: like djfury, I have tried to write an image file of a given size - in my case 16GB - to a new 16GB microSD card and always get a message that the file is too large for the card. What I have done is to make an image of my current CM9 installation on the microSD card using win32diskimager. Then I try to write that image to a new 16GB microSD card. But, alas, the image is suddenly to large for the card.
I want to keep this exact same image as it contains various apps and data that I have installed to my CM9 card.
Is there any way to "resize" the created image to make it about 2MB smaller so it will fit on the card?
Any help would be greatly appreciated.
madavis77 said:
First time to post. Hope I'm in the right thread. Have read many of the threads here regarding Nook Color, CM7, CM9 et al. I really enjoy learning from all the information posted. I currently have an unrooted NC running CM9 on a micro SD and love it.
My problem: like djfury, I have tried to write an image file of a given size - in my case 16GB - to a new 16GB microSD card and always get a message that the file is too large for the card. What I have done is to make an image of my current CM9 installation on the microSD card using win32diskimager. Then I try to write that image to a new 16GB microSD card. But, alas, the image is suddenly to large for the card.
I want to keep this exact same image as it contains various apps and data that I have installed to my CM9 card.
Is there any way to "resize" the created image to make it about 2MB smaller so it will fit on the card?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Yes, use a partition software program like Mini-Tool Partition Wizard to make your partition 4 a little smaller (take it off the end). Then use win32diskimager to make an image of the card. Then burn that to your new card.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
I'm a little concerned about what version number of CWM people are getting in these size-specific images. Anything earlier than 3.2.0.1 (the last stable release) has a good chance of causing you problems down the road, depending on what you try to do with it, and I'm not aware of any 3.2.0.1 images bouncing around except for eyeballer's 1GB image over here (quoted text near the top).
Leapinlar's 5.5.x.x image should be fine, too, but if you have 3.0.2.8 or earlier it can be finicky about dealing with the partition tables on NCs released after July 2011 or NCs with modified partitions, which can result in boot loops and other shenanigans.
As detailed earlier in the thread, you can expand the partitions from the smaller images later if you want to continue using the card for backups, or if you're just using it one time to root or flash something, you don't need the space anyway.
Another thing that causes confusion and issues is manufacturer's selection of how to report size... some use the 1024 standard... some use the 1000 standard... If you read from a 16 GB card using the 1024 standard and try to write it to a 16 GB card using the 1000 standard... it will be approx 16 MB too large...
That being said... you are best if you can resize the last partition on a card approx 20 MB (to be safe) make the image... then write image to a new card and resize the last partition to consume the remainder of the card.
DizzyDen said:
Another thing that causes confusion and issues is manufacturer's selection of how to report size... some use the 1024 standard... some use the 1000 standard... If you read from a 16 GB card using the 1024 standard and try to write it to a 16 GB card using the 1000 standard... it will be approx 16 MB too large...
That being said... you are best if you can resize the last partition on a card approx 20 MB (to be safe) make the image... then write image to a new card and resize the last partition to consume the remainder of the card.
Click to expand...
Click to collapse
Sorry about the delay in offering thanks to those who replied. THANKS.
I also found the best solution for me was to use Mini Tool Partition Wizard and the Copy Disk Wizard. This process took a mirror image of my micro SD card then allowed me to write it ot a larger or smaller card. In my case from a 16GB to another 16GB, then from the 16GB to a 32GB. The last partition was automatically resized to fit the selected card size.
I'm happy now and can use one card for experimentation and still have a backup for restore purposes.
Thanks again for the advice offered.
---------- Post added at 03:40 PM ---------- Previous post was at 03:24 PM ----------
DizzyDen said:
Another thing that causes confusion and issues is manufacturer's selection of how to report size... some use the 1024 standard... some use the 1000 standard... If you read from a 16 GB card using the 1024 standard and try to write it to a 16 GB card using the 1000 standard... it will be approx 16 MB too large...
That being said... you are best if you can resize the last partition on a card approx 20 MB (to be safe) make the image... then write image to a new card and resize the last partition to consume the remainder of the card.
Click to expand...
Click to collapse
Sorry about the delay in offering thanks to those who replied. THANKS.
I also found the best solution for me was to use Mini Tool Partition Wizard and the Copy Disk Wizard. This process took a mirror image of my micro SD card then allowed me to write it ot a larger or smaller card. In my case from a 16GB to another 16GB, then from the 16GB to a 32GB. The last partition was automatically resized to fit the selected card size.
I'm happy now and can use one card for experimentation and still have a backup for restore purposes.
Thanks again for the advice offered.