Related
I have a 16Gb SandDisk class2 that I just bought, using verygreen's instructions for "ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards", and completing the first step for putting the image on the card, I now end up with an SD card that shows it is only 116MB and out of space!!! HELP!!! How do I undo this???
Edit: Relevant to emmc flashing technique only. Too tired to think yesterday.
babyfine24 said:
I have a 16Gb SandDisk class2 that I just bought, using verygreen's instructions for "ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards", and completing the first step for putting the image on the card, I now end up with an SD card that shows it is only 116MB and out of space!!! HELP!!! How do I undo this???
Click to expand...
Click to collapse
If you read the instructions you'd know that was normal... that is the "boot" partition you are seeing.
You can use something like EASEUS or MiniTools Partition managers to resize it prior to putting it in the nook and letting it set up the other partitions (keep it below 2GB... I recommend 1.75GB)
After you put it in the nook and let it set up... you cannot resize partition 1... but can resize partition 4 if it doesn't automatically set up to use the entire free space automatically.
I used EASUS partition manager. You can get it for free here: http://www.partition-tool.com/personal.htm
When you put the image on the card the software did not use all available space. Get EASUS and stretch out the last partition to the max and you will get full use of your card again.
I've been followed a lot of instructions but this particular "partition the uSD" always gives me problem. I bet I do not fully understand the process of using EASEUS or MiniTool to RESIZE PRIOR putting into the NC.
Can someone who has done this pls write up a detail instructions? Dizzy, pat, can you help?
Thing is: after creating a bootable uSD, the card becomes "boot" and only 110+ MB available like OP indicated, that's fine, we all understand that.
Next step is using EASEUS or MiniTool to resize.
Resize what?
As after creating the uSD, only "boot" partition showed as FAT32, the rest is UNallocated. Sine we haven't inserted the uSD in the NC yet, therefore no such ext4, ... created. So what are we resizing here? The "boot" partition?
votinh said:
Thing is: after creating a bootable uSD, the card becomes "boot" and only 110+ MB available like OP indicated, that's fine, we all understand that.
Next step is using EASEUS or MiniTool to resize.
Resize what?
Click to expand...
Click to collapse
You then resize the only partition that has been created on the drive... the 110MB partition.
votinh said:
As after creating the uSD, only "boot" partition showed as FAT32, the rest is UNallocated. Sine we haven't inserted the uSD in the NC yet, therefore no such ext4, ... created. So what are we resizing here? The "boot" partition?
Click to expand...
Click to collapse
After resizing only partition prior to running the uSD in the nook... you put it in nook...let it create the other partitions... after it is done... put it back in computer and resize the LAST partition on it.
What you're seeing is normal. The image copy sets things up, then the install step rearranges and populates the rest of the card. All that's happened is that an image of a tiny card has been copied onto a larger card, but that's not the final setup.
Unless you're unhappy with the final partitioning, you don't need to mess with it manually.
If you're feeling adventurous, Verygreen has posted that you can set up the partitions the way you want, then copy the files from the image (not the image itself) onto the first partition, and the installer will leave them that way.
Pretty slick, actually.
DizzyDen said:
You then resize the only partition that has been created on the drive... the 110MB partition.
Click to expand...
Click to collapse
So, you said we "resize" the "boot" partition, right?
If so, we resize it from 110+MB to 1.75GB like you recommended in previous post?
Should we say "supersize" it? expand it? increase it?
Put the word aside, let say I increase the boot partition to 1.75GB, what about the rest? Still UNallocated, I believe.
After resizing only partition prior to running the uSD in the nook... you put it in nook...let it create the other partitions... after it is done... put it back in computer and resize the LAST partition on it.
Click to expand...
Click to collapse
If I follow through, the first (boot) partition will still be seen as FAT32 and Windows will only see the very first FAT32 partition. What is the purpose of "resizing" the last partition?
Are you telling me that after resize the last partition, Windows will see it (as well as the first "boot" FAT32)?
votinh said:
So, you said we "resize" the "boot" partition, right?
If so, we resize it from 110+MB to 1.75GB like you recommended in previous post?
Should we say "supersize" it? expand it? increase it?
Put the word aside, let say I increase the boot partition to 1.75GB, what about the rest? Still UNallocated, I believe.
Click to expand...
Click to collapse
Just use the resize tool to make it max 1.75GB... the rest will still be unallocated until you let it do its thing by booting it in the nook.
votinh said:
If I follow through, the first (boot) partition will still be seen as FAT32 and Windows will only see the very first FAT32 partition. What is the purpose of "resizing" the last partition?
Are you telling me that after resize the last partition, Windows will see it (as well as the first "boot" FAT32)?
Click to expand...
Click to collapse
The purpose of resizing the last partition is to allow the nook to use the entire disk.... has nothing to do with windows seeing it.
DizzyDen said:
Just use the resize tool to make it max 1.75GB... the rest will still be unallocated until you let it do its thing by booting it in the nook.
Click to expand...
Click to collapse
Clear!
Big thanks
The purpose of resizing the last partition is to allow the nook to use the entire disk.... has nothing to do with windows seeing it.
Click to expand...
Click to collapse
I keep thinking that after the NC does the magic partition, it will automatically sees the rest.
Moreover, if the USB cable plugged in and tap to turn on USB Mass Storage, it's ready to use anyway.
I might miss that but I thought PC see the left over (via usb cable plugged) without "resizing" any partition.
I have to do it over again to be sure.
Just take the uSD out and load it in computer... start EASEUS or MiniTools partition manager and see if it shows the last partition taking the remaining space... or if there's still part unallocated.
I have scoured and tried to no avail, so I called my mom and told her I was special (as per your awesome noob video), or possibly illiterate. I rooted my nc last week via the instructions I found here (TY!!) it works so great that my memory is full, so I downloaded apps2sd and link2sd and neither will let me transfer to my 16gb PNY sdhc, link2sd says it needs 2 primary partitions, I downloaded easeus, paragon partition manager, and sdk manager, none will let me create a new partition, I can delete, and create 1 partition only, I have tried through windows disk manager as well. I am running Vista 32bit, also have a laptop with XP SP2. Sorry if this question is stupid, any help is greatly appreciated!!
You have to shrink the partition already on there and then make another from the unused space.
---
- Sent from my LG Optimus V using Tapatalk
ok I went back to windows disk management and shrink is greyed out, so I tried paragon and got this message when I tried to resize:
Basic MBR Hard Disk 1 (Lexar RW047SDHC Reader USB Device) - Removable
Wizard could not find any adjacent partitions to work with on this hard drive. Note, hard drive must contain at least a pair of partitions that are located next to each other (two primary and/or two logical) to perform resize between.
Thank You Again!
Try using Easeus.
---
- Sent from my LG Optimus V using Tapatalk
I just checked EaseUs and it seems to work. You can re-size the existing to a smaller one and then create a new one with what is left over.
Most definitely helpful. Thanks!
Sent from my HTC Incredible S using XDA Premium App
Sorry it took so long to get back,
Thank you for your replies, are you using the free version of easeus? on mine I have the re-size option for my hard drive but when i select the sd card it disappears
I think you have to right click the partition to see all the options. Is that what you are doing?
---
- Sent from my LG Optimus V using Tapatalk
I just tried right clicking and still no resize for my sd, I can (copy partition, change label, change drive letter, check-hide-format-explore partition, and view properties). I'm wondering if I perhaps messed up the sd card, it seems to be functional I can add/retrieve data from it and speed up my system. maybe the wrong file system? it is fat32 and says it has a 14.91 GB capacity. I'm generally pretty good with technology, rooting my nook was a breeze, but this is starting to make me feel pretty dumb!
Hmm, backup your sd card onto your pc abd then format the card in the nook and try again. Also make sure you are running easeus as admin.
---
- Sent from my LG Optimus V using Tapatalk
well looks like I'm about 50% there! using mini-tool partition wizard I managed to shrink the original partition down to 6.99 GB, but it wouldn't allow me to add another, it said I had to delete the first partition if I wanted to create multiple partitions, so I did but then when I tried to create the new partitions there was no option to create multiples so I ended up right where I started, so once again I shrank the partition and opened easeus and it keeps telling me I've successfully created the 2nd partitions but is still showing up as unallocated space and my nook wants to format it, won't let me do anything else with it, so I let it and tried again, but still nothing. Is it possible this cannot be done with a 16 GB card? I didn't think size really mattered with this kind of thing it should still be the same operation as a smaller card right?
Do you know of a program like link2sd or app2sd, that doesn't require a 2nd partition? I'm starting to think this is an unfixable user error!
This question probably belongs in the thread "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]", except that I can't post there yet.
I was able to create a working dual boot card per the instructions. However, I could not make a working card that made use of all 16 GB of my card, rather than just the <4GB size of the image file. The card still worked when I used fdisk on my Mac to increase the size of the last, 'sdcard', partition to fill up the available space. However, that did not increase the capacity of the FAT volume in that partition, leaving the extra space still unavailable.
After saving the files from that volume, I then used the Mac's Disk Utility to erase the partition and re-create it as a FAT partition using all the available space. Once I did that, unfortunately, the Nook would then not recognize anything on the SD card and would only boot into the Nook's own ROM.
As an alternative, I tried leaving the existing partitions alone and editing the MBR with fdisk to create a new partition using the available space, which I then formatted as a FAT partition with Disk Utility. Again, the Nook would no longer recognize the SD card and would only boot into its stock ROM.
I actually tried the above with two 16GB SD cards, a SanDisk Class 4 and a Samsung Class 10, and with two Nooks. Moreover, I tried a number of manipulations of the MBR, mostly to make it identical to the original one except for necessary size changes. Nothing worked to get a card that would boot and use the full 16 GB. I'll admit I haven't tried everything, such as trying to resize to something less than the full 16GB, but I've put so much time into this already that I don't want to do any more until I get some feedback.
aarons510 said:
This question probably belongs in the thread "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]", except that I can't post there yet.
I was able to create a working dual boot card per the instructions. However, I could not make a working card that made use of all 16 GB of my card, rather than just the <4GB size of the image file. The card still worked when I used fdisk on my Mac to increase the size of the last, 'sdcard', partition to fill up the available space. However, that did not increase the capacity of the FAT volume in that partition, leaving the extra space still unavailable.
After saving the files from that volume, I then used the Mac's Disk Utility to erase the partition and re-create it as a FAT partition using all the available space. Once I did that, unfortunately, the Nook would then not recognize anything on the SD card and would only boot into the Nook's own ROM.
As an alternative, I tried leaving the existing partitions alone and editing the MBR with fdisk to create a new partition using the available space, which I then formatted as a FAT partition with Disk Utility. Again, the Nook would no longer recognize the SD card and would only boot into its stock ROM.
I actually tried the above with two 16GB SD cards, a SanDisk Class 4 and a Samsung Class 10, and with two Nooks. Moreover, I tried a number of manipulations of the MBR, mostly to make it identical to the original one except for necessary size changes. Nothing worked to get a card that would boot and use the full 16 GB. I'll admit I haven't tried everything, such as trying to resize to something less than the full 16GB, but I've put so much time into this already that I don't want to do any more until I get some feedback.
Click to expand...
Click to collapse
Well you're missing just one step after fdisk. If Disk Utility is failing at it you could try terminal:
First you need to find out where your /sdcard is being mounted at. Use "diskutil list" to find out
Once you find out where it's being mounted (eg. /dev/disk4s7). You will then need to unmount the volumes before you can format it.
Code:
$ diskutil unmountDisk /dev/disk4s*
$ diskutil partitionDisk "/dev/disk*" 1 MBRFormat "MS-DOS FAT32" "sdcard" "*M"
Replace * with the actual values needed. You might need "sudo" to perform the format command. Make sure you're formatting the correct mount point or else you might end up wiping your system. But if you were able to use fdisk, I'm sure you have a good understanding of terminal.
Haven't tried it myself. But it should(might) work.
-Racks
Won't "diskutil partitionDisk ..." wipe out all volumes on disk?
racks11479 said:
[See previous post!]
Click to expand...
Click to collapse
When I type
Code:
diskutil partitionDisk
in Terminal to get usage info, I see, inter alia, the following:
Code:
(Re)Partition an existing disk. All volumes on this disk will be destroyed.
But that is clearly not what I want to do. Am I missing something?
Updated update:
I have tried, several times and on both SD cards and both Nooks, diskutil eraseVolume, a presumably more powerful version of the erase option in Disk Utility. I tried one or another of the commands:
Code:
diskutil eraseVolume MS-DOS sdcard /dev/disk4s7
diskutil eraseVolume 'MS-DOS FAT32' sdcard /dev/disk4s7
on cards that were booting, but with the small sdcard partition or the small volume on the enlarged partition. I also tried at least one of those commands on a card that was already not working after modification. In all cases, the commands ran without error but produced a non-booting card. Changing the 'ob' partition id back to 'oc' with fdisk didn't help, nor did any restoration of the original fdisk MBR info.
In sum, the only change that I have been able to make to a card as originally written from the image without making it unbootable was to enlarge the sdcard partition while leaving the sdcard volume untouched, and therefore not using most of the capacity of the partition.
Some more general but related questions.
Since I've got your attention, Racks, let me ask a few questions whose answers might help me and others understand what is going on here and what might go wrong with this and other Nook Color boot setups. Of course, also please point out where anything I think I know is, in fact, wrong.
1) I understand that the firmware boot code on the Nook first looks for something on an inserted SD card to boot from. It seems it looks for a file named u-boot.bin on the first partition of the inserted card to which to transfer control. Does it also check other things on the card before transferring control to u-boot.bin? Does it look at the file MLO? Does it look at the partition labeled sdcard, or at any other partition, before doing so?
2) Presuming that it does transfer control to u-boot.bin, what does the latter check before either booting from the (default) ROM on the card or, if the Home button is being held down, going to the interactive boot dialogue? My experience has been that, when using one of my 'non-working' cards, the Nook goes quickly to the ROM on internal memory without showing any visible signs of doing anything else first. In other words, it 'knows' that it can't boot from a ROM on the sdcard before actually trying to do so.
Though I'm fairly techy, I'm a complete newbie when it comes to rooting.
Last night, I bought a Sandisk 8g card from Radio Shack. It came with an adaptor and cost about $7. I'm not sure of the class.
I had to follow bits and pieces from various threads because most were either outdated or left out important info.
Anyhow, I popped the adaptor in my HP laptop and wrote the card image to disk. Then I downloaded the latest CM10 nightly from 12/22 and I had to use an older gapps file because the latest one made the keyboard disappear.
So far things are working well except I'm already running out of space.
What am I missing?
affirmwealth said:
Though I'm fairly techy, I'm a complete newbie when it comes to rooting.
Last night, I bought a Sandisk 8g card from Radio Shack. It came with an adaptor and cost about $7. I'm not sure of the class.
I had to follow bits and pieces from various threads because most were either outdated or left out important info.
Anyhow, I popped the adaptor in my HP laptop and wrote the card image to disk. Then I downloaded the latest CM10 nightly from 12/22 and I had to use an older gapps file because the latest one made the keyboard disappear.
So far things are working well except I'm already running out of space.
What am I missing?
Click to expand...
Click to collapse
Boot into recovery by holding the n button while powering up. Choose recovery from the menu. When the recovery menu comes up choose format SD card. Process should fix remaining space on the SD card so apps can use it. Reboot when done.
I tried what you suggested, but when it boots into recovery, it runs a few commands and then just shuts down.
It never gave me an option to format.
I tried it again and it still didn't work, but this time I looked at the commands closely when it was rebooting in recovery mode and it said something about "your sd card appears to be formatted correctly".
So maybe that's why it didn't ask.
I was going to try to follow some instructions I found online about partitioning using Mini-Tool Partition Wizard but the instructions kind of fell flat because I couldn't understand them well enough to follow them.
I did see the Fat32 partition, which is the 4th partition, and it is 5.8 GB, but 0 used.
There are actually two Fat32 partitions...the other one is the 1st partition, and it is 204 mb, all used. That is where everything is and why my phone thinks I'm out of space but I don't know how to fix it.
Any ideas?
affirmwealth said:
I tried it again and it still didn't work, but this time I looked at the commands closely when it was rebooting in recovery mode and it said something about "your sd card appears to be formatted correctly".
So maybe that's why it didn't ask.
I was going to try to follow some instructions I found online about partitioning using Mini-Tool Partition Wizard but the instructions kind of fell flat because I couldn't understand them well enough to follow them.
I did see the Fat32 partition, which is the 4th partition, and it is 5.8 GB, but 0 used.
There are actually two Fat32 partitions...the other one is the 1st partition, and it is 204 mb, all used. That is where everything is and why my phone thinks I'm out of space but I don't know how to fix it.
Any ideas?
Click to expand...
Click to collapse
in CWM recovery you did not see/select Advanced at the bottom of the first menu and Partition SD card in the second menu? Usually that fixes the fat32 partition for access.
In the CyanoBoot Universal Bootloader, the menu options are:
Internal eMMC Normal
Internal eMMC Recovery
Internal eMMC Alternate
SD Card Normal
SD Card Recovery
SD Card Alternate
When I select SD Card Recovery it says,
"Loading from SD Recovery"...
Then it goes into some Linux commands
Then it goes black.
The end.
Anyhow, I figured out how to expand the space in the first Fat32 partition using the Mini-Tool software...the only thing that bothers me is that all the instructions keep talking about the last partition but on mine the last partition is the second Fat32 section that has the 5.8Gb of space and you can't adjust it.
But I can adjust the first Fat32 partition and extend it out so that it takes up almost all of the 5.8gb.
affirmwealth said:
In the CyanoBoot Universal Bootloader, the menu options are:
Internal eMMC Normal
Internal eMMC Recovery
Internal eMMC Alternate
SD Card Normal
SD Card Recovery
SD Card Alternate
When I select SD Card Recovery it says,
"Loading from SD Recovery"...
Then it goes into some Linux commands
Then it goes black.
The end.
Anyhow, I figured out how to expand the space in the first Fat32 partition using the Mini-Tool software...the only thing that bothers me is that all the instructions keep talking about the last partition but on mine the last partition is the second Fat32 section that has the 5.8Gb of space and you can't adjust it.
But I can adjust the first Fat32 partition and extend it out so that it takes up almost all of the 5.8gb.
Click to expand...
Click to collapse
You are not on a dual boot SD, you are on a single boot SD. It has the partitions set up so one rom can run there. Go to my tips thread linked in my signature and look at section B. You will learn a lot about the card.
Sent from my HD+ rooted stock using Tapatalk
Using the Mini-Tool software to expand the first Fat32 partition to use up some of the unused space in the last partition was the answer.
I could have expanded it to take up almost all of the 5.8GB, but I left half of the space intact because I wasn't sure if it was needed for something or not.
I then clicked "Apply" and waited for it to process (reformat?) the sd card.
Then I also went ahead and updated to the next CM10 nightly while I was at it since the sd card was already open on my laptop.
After that I popped it back in to my Nook, booted in recovery mode, it went ahead and installed the newest nightly, and I'm off to the races.
Thanks for your help.
affirmwealth said:
Using the Mini-Tool software to expand the first Fat32 partition to use up some of the unused space in the last partition was the answer.
I could have expanded it to take up almost all of the 5.8GB, but I left half of the space intact because I wasn't sure if it was needed for something or not.
I then clicked "Apply" and waited for it to process (reformat?) the sd card.
Then I also went ahead and updated to the next CM10 nightly while I was at it since the sd card was already open on my laptop.
After that I popped it back in to my Nook, booted in recovery mode, it went ahead and installed the newest nightly, and I'm off to the races.
Thanks for your help.
Click to expand...
Click to collapse
When you burned the SD image, did you use the rev 5 image from my updated installation instructions thread also linked in my signature? You need to because CM10 will display the wrong partition as sdcard (partition one instead of 4) if you use an older image. That may be why you were complaining about running out of space.
Sent from my Nook HD+ Running CM10 on SD
Hi,
I have two Nook Color tablets that are running CM11 on SD. The SanDisk microSDs are 16GB each.
I have a constant problem that the space for Apps runs out. So I can't update apps or download any new. The only thing these NCs are used for are Apps. & web browsing. So I don't need alot of space for other tings like saving videos, music & files.
Is is possible to increase the size for the "volume" where the apps are saved?
Thanks in advance.
frav.se said:
Hi,
I have two Nook Color tablets that are running CM11 on SD. The SanDisk microSDs are 16GB each.
I have a constant problem that the space for Apps runs out. So I can't update apps or download any new. The only thing these NCs are used for are Apps. & web browsing. So I don't need alot of space for other tings like saving videos, music & files.
Is is possible to increase the size for the "volume" where the apps are saved?
Thanks in advance.
Click to expand...
Click to collapse
You must be running some very large apps because the space is already generous. But yes, you can use partitioning software to change the allocation. But you need to start over fresh. Make the SD and boot once before adding the CM rom zip. Use partitioning software like MiniTool and decrease the size of partition 4 (from the front of the partition), then expand partition 3 to fill the space. That gives you less for media and more for apps. Then install the CM zip and gapps.
Sent from my BN NookHD+ using XDA Premium HD app
Thank you for your information. I have now re-imaged (v1.3-largest-rev8c) the two 16GB SD-Cards with Win32diskimager, that i have for my two Nook Colors, installed "MiniTool Partition Wizard 9.0" & decreased the size of partition 4 [SDCARD(FAT32)] to 8.0GB. "Apply" on that & then start Resize partition 3 (Ext4) . But I can´t resize that one to use the unallocated space. Isen't it possible to resize an Ext4 partition?
Anyhow, My solution was to delete the third partition. Create a new Primary Ext4 partition. I diden't choose any Cluster size (1/2/4KB) more that let it be as "Default". This way I now have a 5.6GB third partition (for apps), instead of the default that had 1.9GB . I hope this helps me with my out of space problems. Installation of latest Nightly is running.
Unfortunately it looks like it diden't was successfull. The Cyanoboot only loops around now. It says "Loading..." then it gets black & after a while it start over again.
I suppose that the third partition wasen't empty. That't why it dosen't work for me.
Is it possible to re init that partition with data like the first run did? Or do we have another suggestion of partitioning program that can expand an existing Ext4 partition, in Windows, on a SD-Card?
I have now tried with "Paragon Partition Manager". Then it was possible to resize. But still the same problem with loop at boot after installing CM11.
Are there any limit of how large the third partition can be?
Hmmm... Now I have redone everything again, without any modifications to the partitions. But still the same problem, Cyanoboot just loops. Do we have a problem with the nightly? cm-11-20150405-NIGHTLY-encore.zip
The reason I told you to start over is an ext4 partition must be empty to be resized. And if you don't start really fresh your data will still be there. And by fresh I mean taking the card back to a full 16Gb and formatting it with a program like SDFormatter. Then you can reimage. And yes, you must not use new nightly on a new SD. You must start with CM11 CM11 or older. See my warning in the SD thread.
Sent from my SCH-i705 using XDA Premium HD app
Okay, so... is this a step by step procedure that would work?
SD Formatter to fully format the SD-card
Win32diskimager with "v1.3-largest-rev8c"
Boot once so partitions are created
Decrease the size of partition 4 (from the front of the partition), then expand partition 3 to fill the space
Add the CM zip and gapps to SD-Card
Install the CM zip and gapps
Then I have done a new try, based on below steps,
SD Card Formatter V4.0 , Full(OverWrite) Took almost an hour for 16GB
https://www.sdcard.org/downloads/formatter_4/index.html
Used "Win32DiskImager 0.9.5" to write "generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8c.img"
SD-Card mounted in NookColor, start it up to create partitions & filesystem.
SD-Card back into PC,
Resize partitions 3 & 4 with "Paragon Partition Manager™ 14 Free"
Insert SD-Card in NookColor & start, to make sure it still boots.
SD-Card back into PC,
Copy...
cm-11-20141008-SNAPSHOT-M11-encore.zip
gapps-kk-20140105-signed.zip
... to SD-Card
Insert SD-Card back into NookColor & start it up, installation started to run.
After that the installation is finnished & that the NC it powered off. Power it up again & the CM11 will boot!
Success!
After first boot & configuration. I will update to latest Nightly, cm-11-20150405-NIGHTLY-encore.zip
Thank you for all help!
frav.se said:
After first boot & configuration. I will update to latest Nightly, cm-11-20150405-NIGHTLY-encore.zip
Click to expand...
Click to collapse
When you install the nightly (or any zip after M11), you will get an error message during install but you can ignore it. It only causes a problem during the FIRST install to the card. That's why you need to begin with M11.