Related
A couple of questions:
- I've read that the SD based images of Froyo and HC actually put 4 partitions on the SD card. It was suggested that, since the 4 partitions likely won't use all the available space on the SD card, it's possible to expand the last partition to use the rest of the card. I downloaded EASUS partition manager and tried to do that but it appears that it's only seeing the first small partition. This is on Win7 64 bit. Is EASUS the right tool for this and, if so, how do I get it working.
- So far I've used win32diskimager for writing the images to SD and it's worked well. Since I've only got a couple of SD cards I wanted to make a backup of the contents of one so I could try a different build on it. When I read the card I only got a 100+k image instead of the 2G image I expected. I suspect that's the same first partition that EASUS seems to show. How do I create an image of a card?
hmm....that is kinda weird. I use EASUS myself and have Win 7 64 bit also. that said I just did the process to expand my bootbale HC sdcard to get all the sdcard storage space back after burning the bootable image to the sdcard. One thing I did notice tho is that if you have EASUS open prior to plugging the sdcard into the comp it doens't read correctly. So I reboot my comp leaving the sdcard plugged in. Once the comp came up I went into my comp to see what the size showed. The card was labeled a "boot" and the size was only about 120Mb. I then closed the window and fired up EASUS and it showed as Disk 2. Under that I have the small boot partition, along with an ext2 & ext3 partition each about 675Mb in size. Last partition was the sdcard and under that showed "unallocated space" of about 13Gb. I clicked ( ie highlighted ) sdcard and then was able to click the Resize button on the tool bat in the progrm. From there I grabbed the slider and slide it all the way to the right and it set the sdcard partition to just under 14Gb. Click okay and then last but not least just click the Apply button on the tool bar and it resized it.
As for your other question I can't comment at this time as I don't have my Nook or my sdcards with me to take a look at what they show up as for size when read. I'll try to take a look when I get home and report back on what I'm seeing.
Have you tried using the Win32diskImager read function?
I'm not near my computer, but I am pretty sure there was a read function in there..
Sent from my LogicPD Zoom2 using XDA App
Yes I did use the read function but the image file created was only 100-some k, way smaller than the original Froyo image that I wrote to the card.
I wonder if the SD slot on my laptop and/or the SD adapter that came with the card is funky, preventing a proper read of the card. I'll have to try the other adapters or an external card reader I have to see if I have better luck.
If I'm not mistaken the 100-some k partition is normal as it is only reading the boot partition IMG. My 8Gb bootable sdcard comes up showing as 119Mb when you look at it in My computer and check the properties. Reason being is Windows is not reading/seeing the other partitions. However in EASUS all the partitions ( 4 of them boot,ext2,ext3, and sdcard )should show up and that should allow you to resize the sdcard as that is the only thing you want to mess with anyways.
As I said earlier I will check this out tonight when I get home as I have at least 3 different bootable sdcards, and also a 16Gb sdcard that has HC flashed to it so I can run the OS off of it and still leave my CM7 setup on eMMC. One one darn day I don't bring it with me to work......lol, typical I tell ya.
I had tried to extend mine using windows DISKPART at first, and all of the partitions were listed, but they were all marked partition 0. EASUS did the job for me when I couldn't select the proper partition in diskpart (all of them being partition 0 confused it). Windows Disk Manager also saw all 4 partitions, but couldn't do anything with the last partition. Verify you've got 4 partitions using either diskpart or disk manager - if you don't see all 4 partitions in those programs, something went wrong with your image burn.
Unlikely that anything's wrong with the burn since Froyo boots and runs fine off the card.
I tried the card in the other adapter I have in the laptop slot and EASEUS still doesn't see the other partitions. Then I tired a cheap USB reader I have. EASEUS saw the partitions and allowed me to resize the fourth partition. Another hurdle cleared. Note to self use card reader from now on
Hey guys. I'm a noob to the nook. Got mine yesterday and flashed nookie froyo 0.6.8. Flashed auto nooter 3.0 before that (not sure that was necessary, but I did it anyway - Was it necessary?)
I digress... I'm confused about the sd card and from what I've read in the forum, it's still not clear to me. So here are my questions and I apologize if they were answered elsewhere. If someone could link a post that might be helpful that would be great!
1. Which roms run off the external sd card?
2. Is it better to run off the external sd card?
3. I'm using an 8 gig class 10 card, but only 1.78 is accessible and and less than 500 mb of open space is left.
4. NookcolorUMS is confusing. I've tried mounting all partitions and cant access the extra space. And yes I did format it after flashing so it's allocated using FAT32.
Any help or direction to helpful posts would be really greatly appreciated.
Thanks!
treylemkn said:
Hey guys. I'm a noob to the nook. Got mine yesterday and flashed nookie froyo 0.6.8. Flashed auto nooter 3.0 before that (not sure that was necessary, but I did it anyway - Was it necessary?)
I digress... I'm confused about the sd card and from what I've read in the forum, it's still not clear to me. So here are my questions and I apologize if they were answered elsewhere. If someone could link a post that might be helpful that would be great!
1. Which roms run off the external sd card?
2. Is it better to run off the external sd card?
3. I'm using an 8 gig class 10 card, but only 1.78 is accessible and and less than 500 mb of open space is left.
4. NookcolorUMS is confusing. I've tried mounting all partitions and cant access the extra space. And yes I did format it after flashing so it's allocated using FAT32.
Any help or direction to helpful posts would be really greatly appreciated.
Thanks!
Click to expand...
Click to collapse
1. I think CM7, NookieFroyo, and the HC build have all been made to run off the SD.
2. I don't think so; it does give you the nice "sandbox" feel that you can't screw anything up though. It is MUCH faster to run off the internal memory; and with the multi boot ability in my opinion there really is no reason to run off an SD card.
3. I'd look at the card in some type of partition manager; there may be some partitions that can not be seen otherwise. Have you already flashed a rom to the card?
4. Not sure.
themoe said:
1. I think CM7, NookieFroyo, and the HC build have all been made to run off the SD.
2. I don't think so; it does give you the nice "sandbox" feel that you can't screw anything up though. It is MUCH faster to run off the internal memory; and with the multi boot ability in my opinion there really is no reason to run off an SD card.
3. I'd look at the card in some type of partition manager; there may be some partitions that can not be seen otherwise. Have you already flashed a rom to the card?
4. Not sure.
Click to expand...
Click to collapse
I flashed the image to the external sd card. It put the boot image after flashing on the card. I just reformatted the card and can now see it in the nook.
New questions.
1. Is there a way to create a nandroid back up?
2. How do I get to clockwork recovery without using the image on the sd card?
Maybe more questions later.
Thanks!
themoe said:
1. I think CM7, NookieFroyo, and the HC build have all been made to run off the SD.
2. I don't think so; it does give you the nice "sandbox" feel that you can't screw anything up though. It is MUCH faster to run off the internal memory; and with the multi boot ability in my opinion there really is no reason to run off an SD card.
3. I'd look at the card in some type of partition manager; there may be some partitions that can not be seen otherwise. Have you already flashed a rom to the card?
4. Not sure.
Click to expand...
Click to collapse
Multi-boot ability? I still have so much to learn. Is it basically a matter of rearranging the partitions on the internal storage? Would the best link be http://forum.xda-developers.com/showthread.php?t=959461
?
Can the primary partition continue to boot stock unrooted Nook ROM?
* Go to the parallel Development Forum to find threads on:
- Multi-boot (very simple to install)
and
- SD card booting versions of CM7, Honeycomb and Froyo
* Within the thread of each of those three, you will find instructions for adjusting things (installing missing capabilities, partitions, etc).
* Download Free Easeus Partition Manager (sp?) to extend 4th partition while looking at SD card in Windows, this will give Android's /sdcard folder the rest of your card. Then Download Free Notepad++ (linux file format text editor) to edit a file as described in those threads. See threads for more details.
* Download Free Win 32 Disk Imager to backup SD card in Windows ("read" backs up card, "write" burns an image to card, the latter is how you create bootable ROM on SD card).
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.
Hi,
I just got myself a Nook Color with version 1.2 update and I am planning to root the device from a microSD Card with CM7 or Honeycomb. But before I start, I have two basic queries:
1. Which rooting will give a better and stable web browsing experience - CM7 (Gingerbread) or Honeycomb
2. Can I store and view my personal files (e.g, movies) from the microSD Card which will boot my Nook Color with CM7/Honeycomb? I am very concerned about this, as the Nook Color v1.2 comes with only 1 GB of free space for personal files storage and so I need to store my movies in mircoSD card. At the same time, I don't want to change the stock software thus violating warranty, so I have to root using a microSD card.
I am very new to this, so will appreciate your response very much. Thanks in advance.
Dazed378 said:
Hi,
I just got myself a Nook Color with version 1.2 update and I am planning to root the device from a microSD Card with CM7 or Honeycomb. But before I start, I have two basic queries:
1. Which rooting will give a better and stable web browsing experience - CM7 (Gingerbread) or Honeycomb
2. Can I store and view my personal files (e.g, movies) from the microSD Card which will boot my Nook Color with CM7/Honeycomb? I am very concerned about this, as the Nook Color v1.2 comes with only 1 GB of free space for personal files storage and so I need to store my movies in mircoSD card. At the same time, I don't want to change the stock software thus violating warranty, so I have to root using a microSD card.
I am very new to this, so will appreciate your response very much. Thanks in advance.
Click to expand...
Click to collapse
1. Without a doubt cm7. Honeycomb will unfortunately be forever buggy.
2. Yes you can use the left over storage on your SD card for files, music, videos, app etc.
And FYI you can root the internal memory and if you need to return for warranty then you can just return to stock and b&n will not know a thing but if you are going to run off the SD card make sure that it is a sandisk.
Sent from my NookColor using Tapatalk
The thing to remember if you want to access the 4th partitiion for storage is that you have to do it while the SD is in the NC. Win xp will only see the first partition which has only about 155 megs.
Thanks a ton! I have few more quick questions.
1. What is the most stable CM7 version for rooting 1.2 version Nook Color as of today?
2. Will the rooted nook be able to play AVI video files? What app I need to download for that?
3. I found that PDF page load is very slow in my Nook Color. What app do you suggest for a good reading experience?
Once again, thanks in anticipation.
1. 7.0.3 is the latest stable version of CM7, however, most people keeps up-to-day with nightly builds.
2. it should, if not, install Rock Player Lite, it plays virtually everthing
3. Either Adobe Reader or Alkido would do the job
Not able to copy files to uSD card which boots CM7
Hey thanks for your all your support. I was able to install CM7.0.3 on my 1 GB uSD card and also installed Adobe Reader and Moboplayer. Everything works fine, except when I connect my NC to my PC, and then turn on USB Mass Storage on NC, I can only explore my Nook Color (showing as F: drive) to copy files. I cannot open/explore my SD card, though the PC shows the uSD card as "Removable Disk (E. When I try open this E: drive, I get the message "Please insert a disk in E: drive".
Also, my NC does not seem to identify the SD card. When I go to Settings -> Storage, it shows total space unavailable under SD card. Even when I open Moboplayer, I get the message "There is no SD card, make sure it is usable". I could only play videos copied to my NC internal memory.
I was told that I can use the leftover space of the uSD card to copy personal files, but I have no success on that front yet :-(. Any idea/suggestions how to fix this issue?
More information:
In my NC Storage Settings, it shows:
1. SD card: Total space unavailable, Available space unavailable.
2. Internal storage: Total space 525 MB, Available space 449 MB
3. Additional storage (emmc): Total space 1 GB, Available space 63.51 MB
Wondering what is 2nd one (Internal storage)? Is that the data partition of my SD card? If yes, how can I copy personal files there?
Did you say you are using a 1GB uSD? IMO, that's way too small for what you want to do. I would recommend either a 4 or 8GB sandisk card to allow you enough space for files and the OS. Remember that this is also your boot disk and the cm7 files are taking up most of the available space on a 1GB card. Just sayin......
Sent from my NookColor using Tapatalk
I have ordered for a 16 GB class 4 SanDisk uSD card. I had a 1 GB uSD card at hand, so wanted to test with that first before I receive the 16 GB card. And as I said, I had no prob at all installing CM7.0.3 on the 1 GB card and if I am not wrong the card still has hunderds of MB memory free. My question is why can't I explore the SD card when I connect my NC to PC thru' the USB cable?
Dazed378 said:
I have ordered for a 16 GB class 4 SanDisk uSD card. I had a 1 GB uSD card at hand, so wanted to test with that first before I receive the 16 GB card. And as I said, I had no prob at all installing CM7.0.3 on the 1 GB card and if I am not wrong the card still has hunderds of MB memory free. My question is why can't I explore the SD card when I connect my NC to PC thru' the USB cable?
Click to expand...
Click to collapse
I don't recall the specific partition sizing of SASD but I would suspect there is no space available on the uSD after SASD creates the first 3 partitions... thus no partition 4 to be mounted as /sdcard.
Ok, thanks. As a mentioned in couple of posts back, any idea what is the "Internal Storage" of 525 MB total space that shows up in my storage settings? It is different from the emmc storage, because that shows up as the third storage option with 1 GB total space.
Ok - just found this thread and had to ask:
I'm running a stock 1.3 on the eMMC, and CM7.1 on a 16G micro-SD.
When I boot into the stock ROM, I see that my SD is mounted, but that the stock ROM mounted the /boot partition, rather than the /SD Card partition.
Is there a way to set the stock rom to boot /SD Card, or hide the other three from it?
Thanks!
traumadog said:
Ok - just found this thread and had to ask:
I'm running a stock 1.3 on the eMMC, and CM7.1 on a 16G micro-SD.
When I boot into the stock ROM, I see that my SD is mounted, but that the stock ROM mounted the /boot partition, rather than the /SD Card partition.
Is there a way to set the stock rom to boot /SD Card, or hide the other three from it?
Thanks!
Click to expand...
Click to collapse
To my knowledge, no, you cannot make the stock OS see any but the boot partition of the SD card. Both stock and your CM7 card can access eMMC storage, but stock can only see the first partition of your card. If you want a stock and a CM7 installation to share one /sdcard partition, you will have to set up a dual boot on internal storage (mine is linked in my sig).
If you just want to have some SD storage available to your stock install, you might be able to stretch the card's /boot partition and store some files in there, but I don't know if your SD install would remain stable. You could always back up your card as a disk image and try it out.
Taosaur said:
To my knowledge, no, you cannot make the stock OS see any but the boot partition of the SD card. Both stock and your CM7 card can access eMMC storage, but stock can only see the first partition of your card. If you want a stock and a CM7 installation to share one /sdcard partition, you will have to set up a dual boot on internal storage (mine is linked in my sig).
If you just want to have some SD storage available to your stock install, you might be able to stretch the card's /boot partition and store some files in there, but I don't know if your SD install would remain stable. You could always back up your card as a disk image and try it out.
Click to expand...
Click to collapse
I would also like to know the answer for how to make the /boot partition larger on various images to allow sufficient room when booted from eMMC. I tried doing this with EASEUS Partition Master but it will not let me resize the boot partition. Any other options to solve the issue? The only other options is to swap cards when you know you are booting off eMMC and that is a pain.
hikersc said:
I would also like to know the answer for how to make the /boot partition larger on various images to allow sufficient room when booted from eMMC. I tried doing this with EASEUS Partition Master but it will not let me resize the boot partition. Any other options to solve the issue? The only other options is to swap cards when you know you are booting off eMMC and that is a pain.
Click to expand...
Click to collapse
What are you trying to accomplish?
What is your running system?
Why do you want to expand the boot partition?
votinh said:
What are you trying to accomplish?
What is your running system?
Why do you want to expand the boot partition?
Click to expand...
Click to collapse
Sorry, I guess that I could have been more clear in what I am trying to do. I have a rooted nook color 1.1. I burned the image for the dualboot phiremod/Honeycomb that is approximately 3.5 Gb. I burned it to an 8 Gb card and then expanded the 7th (/sdcard) partition to use the space which is available when booted to phiremod. When I boot (with the card installed) to eMMC via J4mm3r's u-boot menu, my rooted 1.1 comes up but sees the /boot partition as the SD card. Since it is the /boot partition, it only has 80 Mb free which is not enough for Titanium Backup, etc. If I could make the /boot partition larger (say 2 Gb) then everything would work as desired.
1. I don't use dual boot option so can't help you
2. I don't use either Phiremod nor Honeycomb so can't help you but
a. I think the NC should still the left-over of the uSD card. if not
b. Try using MiniTool Partition wizard to expand the boot partition and see what happens. Not so sure if it allowed to do so.
hikersc said:
Sorry, I guess that I could have been more clear in what I am trying to do. I have a rooted nook color 1.1. I burned the image for the dualboot phiremod/Honeycomb that is approximately 3.5 Gb. I burned it to an 8 Gb card and then expanded the 7th (/sdcard) partition to use the space which is available when booted to phiremod. When I boot (with the card installed) to eMMC via J4mm3r's u-boot menu, my rooted 1.1 comes up but sees the /boot partition as the SD card. Since it is the /boot partition, it only has 80 Mb free which is not enough for Titanium Backup, etc. If I could make the /boot partition larger (say 2 Gb) then everything would work as desired.
Click to expand...
Click to collapse
Mmm, I think you maybe just need to make up your mind, or deal with the limitations--have your cake or eat it, because you can't do both. That said, I see no reason EASEUS wouldn't let you expand the boot partition, unless there's just no unallocated space, in which case you need to shrink your storage partition first. I don't know whether your card would boot properly with an expanded boot and random files in there, but you should be able to move the partitions around just fine.
Still, your better bet is to decide what's going to be your primary OS and stick with it. You can even dual-boot from eMMC and have two full OSes, but as long as you're using the SD as a boot drive, you're going to be trading off its ability to serve as storage for your interal OS.
Edit: sorry, didn't realize how old the thread was...was trying to find my info with the forum search. ^^;
In the original post the user asked if you could use the microSD for both booting/rooting and for storage -- when I tried this, I got a "SD Card must be formatted" error in my rooted Nook. I let it rty to format the card (then let Windows format it) and -then- I was able to store on the SD card.
But when I rebooted my Nook Color, it got stuck Infinite-looping the Nook Color splash screen. =\
I'm about to root it again, and I'd like to use the same SD card I use to root to have some storage space on it. I (had) a 4GB microSD card, but because the slot is in the worst place it could possibly be on the device...I've already managed to get it wedged inside the casing. =\ The drive still works but I'd rather not have to worry abotu swapping cards in and out and in and out; maybe I have fatter fingers than It hink, but that SD card slot is a pain in my arse.
What did I do wrong my first go 'round? I had a 4GB card, so I used the 4GB CWM image for it. Is it...really simple, and I need to format it into two partitions in windows; set 1GB aside for the CWM boot disc and the other 3GB would be available for file storage?
1. use SD formatter
2. if you used a 4GB CWM image, did you manually update it to the latest build? If not, just grab the 1GB image in the quote at the top of this thread: updated CWM. If you're planning to wipe it right after, it doesn't matter how big it is.
Also, regarding the OP and my response, I later found this link I'd saved about pointing stock to the storage partition of a CM7 SASD card: http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
I haven't tried it or seen anyone report back after trying it, but there it is if anyone wants to give it a go.
I am running CM7.1.0 on my nook color off the SD card. I used the YouTube tutorial by the Crash Tech Dummies. Now I notice that I am only allowed only 1GB of storage on the SD card. I used partition wizard to increase the space on the 4th partition like I was instructed. I would prefer to install the apps to the SD card so I have already burned through the space provided. Bellow I have listed what I see in partition magic. Should I move the free space in the 4th partition into the first? Or should I load the cm7 onto the HD of the nook? I am a bit of a noob but I have gotten this far.
My 16 GB card partitions read:
G:boot 30.32mb used 118.69mb unused
*: 179.55mb used 283.25mb unused
*: 367.34mb used 597.50mb unused
*: 6.68 gb used 6.61gb unused
Any suggestions would be great…I don’t know what else to do.
Help me XDA Developers you my only hope…
Steve da Noob
First of all, what is "1GB of storage on the SD card" you're talking about?
Secondly, the 4th partition has nothing to do with holding installed apps.
votinh said:
First of all, what is "1GB of storage on the SD card" you're talking about?
Secondly, the 4th partition has nothing to do with holding installed apps.
Click to expand...
Click to collapse
when i go into settings, apps, storage use, sd card it says 1.0 gb used 0.00 free...i was assuming this was referring to a section of the sd card. I also assumed that the 4th partition was being used by something do the fact that half of it has been used by something...
Steve
Quoting from VeryGreen's instructions
Partition layout for the SD cards depends on size:
Less than 600M - unsupported.
up to 1G cards gets: system of ~300M and data of the rest of space. No FAT partition
2G cards (more than 1G up to 1800M) gets: 300M system, 612M data, rest is FAT sdcard
more than 2G cards gets: 460M system, 975M data, rest is FAT for sdcard.
Your first partition is the boot, nothing else should go on here.
Your second partition is the system partition containing the OS and system applications
Your 3rd partition is the data partition used for downloaded apps. The space allocated is adequate for a decent number of downloaded apps but may get tight if you load lots of games. You can move apps to "SD" which is the 4th partition if you get tight on space.
Your 4th partition is the "SD" user data area. This can be used by apps for their working folders and is also where you put stuff like media (pictures, music, video). It is the partition that will normally get mounted as a drive on a PC when the USB is connected and USB disk storage is turned on via the notification panel.
You say the 4th partition has got 6.68GB data on already? That should start off fairly empty until you put stuff on there.
I do have music and pictures on the device that i uploaded so that's where the items on partition #4 came from.
When i try and move the applications to the sd card it tells me that there is not enough room on the card. Also when i plug in the nook to my computer without the sd card in it shows the applications on the internal hard drive. Should i try and move space from the 4th partition to the 3 and see if that helps?
Thanks,
Steve
WileECoyote79 said:
When i try and move the applications to the sd card it tells me that there is not enough room on the card. Also when i plug in the nook to my computer without the sd card in it shows the applications on the internal hard drive. Should i try and move space from the 4th partition to the 3 and see if that helps?
Click to expand...
Click to collapse
I'm a little surprised it says there is no room available to move an app if the partition still shows 6GB free. Have you tried using Apps2SD app. This will show space available and is a convenient way to move stuff around. Another possibility is that you are trying to do this whilst USB connected to the PC. That won't work as the Nook software can't access the SD partition while it is PC mounted.
Currently you said there was nearly 600MB free in your 3rd partition where new downloads go. If so I wouldn't bother with trying to move stuff until you get tight on space there.
If that happens and you just need to create some more app space in the 3rd partition then you can use a partition tool on the PC like minitools to reallocate some of the space from 4 to 3 to give yourself more app space.
I tried the apps2sd and i get the same error. It sends me to the same place as i discussed above and when i tell it to send it to the sd card i get the same error. "failed to move application, there is not enough storage space".
I am not trying to move anything while i have the nook attached to my computer. the only time i really used that function was to add music and some pictures.
This is really starting to get frustrating. I do appreciate all your help.
Is another option loading CM7 to the nook instead of the SD card?
I only used the SD CM7 method for a short while and I don't think I ever tried to move apps to the "SD" so maybe there is an issue trying to do this.
I think you have two choices.
If you stick with SD then increase the data partition to give yourself more room for apps.
If you never want to use the B&N OS then the internal memory is the best option. The SD card then becomes a single partition user space card and you can certainly move apps to it. If you do this then also consider using the zip that increases the internal data partition to 2GB to give yourself more internal room for apps anyway.
bobtidey said:
I only used the SD CM7 method for a short while and I don't think I ever tried to move apps to the "SD" so maybe there is an issue trying to do this.
I think you have two choices.
If you stick with SD then increase the data partition to give yourself more room for apps.
If you never want to use the B&N OS then the internal memory is the best option. The SD card then becomes a single partition user space card and you can certainly move apps to it. If you do this then also consider using the zip that increases the internal data partition to 2GB to give yourself more internal room for apps anyway.
Click to expand...
Click to collapse
I think ill try adjusting the partition and see if that helps. Like you said if it doesn't ill look into loading onto the internal memory. I am not to impressed with the B&N software and i use the kindle software for my e-reading.
Is there a method you could recommend for loading it onto the internal memory? A step by step tutorial would help out lots. I am not familiar with the zip you are referring to.
Thanks,
Steve
WileECoyote79 said:
I think ill try adjusting the partition and see if that helps. Like you said if it doesn't ill look into loading onto the internal memory. I am not to impressed with the B&N software and i use the kindle software for my e-reading.
Is there a method you could recommend for loading it onto the internal memory? A step by step tutorial would help out lots. I am not familiar with the zip you are referring to.
Thanks,
Steve
Click to expand...
Click to collapse
Yes. If you don't think you'll use the B&N then internal is the way to go. Especially if you use Amazon Kindle for your books.
The easiest method in my view is to use the Eyeballer Clockwork boot SD and use that then to flash the main ROM and gapps zips.
You can find the most straightforward instructions here but I would use the KANG MiRaGe ROM as the main OS.
http://rootzwiki.com/topic/8208-guide-install-cm71-clockworkmod-to-emmc-all-nooks-updated101111/
The 2GB partition zip can be found here
http://forum.xda-developers.com/showthread.php?t=1094371
This can actually be applied at same time as installing the OS and gapps. Put the repartition zip, the ROM zip and the gapps zip on the Eyeballer SD card then use the menus to flash repartition, ROM and then gapps.
If you also follow the advice to put ROM manager and flash clockwork to the internal as well then future updates become very easy and do not even involve removing the SD card.
Ive decided that the best solution is to install on the internal rather than the sd card. i think this will be less of a pain in the butt in the long run.
being new to android and coming over from apple (booooo) is there anyway to easy re-install the apps that i have already downloaded? I do have one that i did pay for.
Steve
easy way to re-install? hmmm, maybe not but I would suggest you make the backup for all of your apps first (meaning save all .apk files to somewhere else)
ok here goes nothing lol
Titanium backup would allow you to back up all your apps. If you save the Titanium back up folder (say onto a PC via USB) then after you have done the internal install then put the Titanium back up folder back onto the fresh SD card and you can restore the apps back from there.
everything seems to be working just fine...thank you all for the help and advice...
Steve