If I use gparted to shrink the p4 partition to 6gb (so the whole cards
partitions are < 8gb and dd the updated card to a file, then back to
to an 8gb card that should work, right? I know the restore will run
out of card to write to but the actual image is only ~8gb so it fits.
If I can successfully access the p4 vfat (/sdcard) it worked, right?
I'm hopeful the boot block / partition table will then reflect a real
size of ~8gb.
Sounds like it's worth trying. If it won't boot you can try to get to the individual partitions. fdisk -ul will tell you where they're at in sectors.
[Solved]
Ended up rebuilding up from the provided 2gb card image.
It seems down sizing doesn't work, but upsizing does .
I also did the build.prop change to support the netflix app.
Everything is working as expected.
Related
I'm using Paragon Partition Manager (9.0 special edition) and an 8GB MicroSD card, and would like to make two partitions, one with the android files, and the other one so that I can put all my other stuff in. Is there a way that I can see my second partition in windows once I connect my phone to my computer, and what type of partition should I make? I can choose between FAT32, NTFS, and Linux ext2 and ext3.
Thanks in advance.
Ideally you are supposed to make 3 partitions:
First partition is the biggest partition (Fat32)
Second partition should be around 256MB
Third partition should also be around 256MB
I also have an 8GB card. However 8GB is really 7.61GB
If i remember correctly what i did was i shrank the sd card from 7.61GB to about 7.10GB...........which created approximately a second partition of 516MB or so.
Then i split that 516 in half so i had 2 partitions of 258MB.
Then i formatted the two 256MB partitions to ext2
***Important***
The fat32 partition (7.10GB) should be the first partition (must be on the left)
Then the other 2 partitions should come after the fat32 partition.
Failure to do this may cause the sd card to not be recognized in windows computer (i think)
Well I got it working with Paragon Partition Manager. I created two ext3 but I had to modify cluster size to 4.
Link2SD wouldn't recognize 2 cluster ext3 and it couldn't mount 8 cluster ext3.
I'm having some problems with partitioning my new 16GB microSD card for use with apps2SD. The problem seems to be that any partition past the first fat32 partition comes out inevitably messed up.
What I did first is use dd on a ubuntu system to image my old 8GB SD card and write the image to the new one. I figured I could maybe resize the FAT32 partition and move the ext2 and swap ones up (I'm not really sure whether or not the swap partition is useful, but that's irrelevant). Problem is, gparted did not seem to recognize the two partitions past the fat32 one. This meant that I couldn't do anything with them. For the record, the partitions on the 8GB card work fine and even mount automagically on the same system.
So what I did next is try to partition the card with gparted, with one huge fat32 partition, one ext2 the same size as the one on my old card, and the swap. This resulted in a similar situation to that I encountered earlier - gparted had no idea what the last two partitions were. The phone seemed to think that the card was blank (I do not recall the exact notification text right now but it was something to that effect). I even tried imaging the old partition 2 and writing it directly over the new partition 2. Pretty sure that wouldn't have worked anyway and so it didn't.
I tried writing zeros to the entire card to be damn sure. I booted the phone into recovery (I'm running Amon_RA's recovery 1.6.2), and ran parted on the phone. I did mklabel msdos, then tried mkpartfs. The first partition went up ok, but once I tried making the ext2 one, my parted crashed. It spat out "Error: Invalid superblock. Are you sure this is an ext2 file system?" followed by lengthy text along the lines of "You found a bug in Parted here's how you report it," followed by "Error: SEGV_MAPERR (Address not mapped to object). Aborted."
So, I'm pretty sure my card is a dud. I'm posting this here in case I'm missing something obvious and someone can point that out. Also, I'm running CM 5.0.7.
the problem is that you have a fake sd card
I tried to create an image backup and the file stopped at 4gb,
(both for 8gb and 32gb cards). I was able to boot a Linux
OS and use DD to image both cards successfully. Windows
refused to NTFS format a 16gb flash drive, I had to use
Linux to create it .
It seemed like the maximum file size win32imager.exe
could create was 4gb, (like it was stuck with fat32
rules , even though it was outputting to an NTFS
disk).
Thanks
EDIT: Sorry, didn't realize you meant you wanted to do an image backup (unless you mean from within CWM, then my post stands).
I just do what I need to do with disk imager, and when I'm done, format within Android to give it the full 16gb back. I've read some threads where CM7 didn't format the SD card correctly and wound up formatting the boot partition instead, so I formatted in my phone instead to be safe.
A couple noteworthy bugs...
4GB limit:
https://bugs.launchpad.net/win32-image-writer/+bug/724102
Incorrect device size (potentially truncated images even < 4GB):
https://bugs.launchpad.net/win32-image-writer/+bug/786060
Yes exactly my issue
win32imager.exe can't image > 4gb cards.
I guess I'll have to boot to Linux to image
the big cards, unless there is a working
win32 tool?
If you have enough space on the card so that you can use EASEUS to reduce the size of the last partition so that 4G or less is used on the card you can then make the image file. I did this to copy a CM7 install to a faster Sandisk card.
how?
I am trying to back up 8gb card
last 4.3 gb are unallocated
dd still fails "file too large"
I used verygreen's size-agnostic installer with my 8GB SD card, and put CM7-107 nightly on it.
I ended up with the boot partition of about 100MB, two android partitions (one 450MB, the other 1GB), and the rest being "sdcard", around 6GB as FAT32.
I'd really like to take the 1GB android partition (my system stuff, and where apps are installed) and kick it up a bit in size, taking space away from the SDCARD partition. That way i have more room for app installs, etc.
I tried using EASUS Partition Manager, and while it'll let me take space away from the SDCARD/FAT32 partition, it's not letting me give it to any of the "other" (linux/android) partitions - doesn't give me an option to resize it, once I have unallocated space available on the SD card.
Any ideas? This is Windows 7 64bit, btw.
Hi! Successfully rooted my Nook ST using Nook Manager, except I used a 32 GB micro SD card to do the rooting. After rooting, I ended up with two partitions on the SD card, Nook (239 MB) and Nook Manager (62.9 MB). I was wondering what I need to do to be able to utilize the rest of the space on the card? The reason I bought a 32 GB card was so I could store all my sideloaded books there, and now I find I'm just limited to the space/partitions showing up when I connect the nook via USB.
You need to repartition your card.
Partition Magic can do that.
If you want to use multiple partitions on the SD card (like 2 x 16 GB) you might want to look at:
http://forum.xda-developers.com/showthread.php?t=2184495
Renate NST said:
You need to repartition your card.
Partition Magic can do that.
If you want to use multiple partitions on the SD card (like 2 x 16 GB) you might want to look at:
http://forum.xda-developers.com/showthread.php?t=2184495
Click to expand...
Click to collapse
Thanks, will download a copy of Partition Magic later. I really am completely clueless when it comes to programming though. In fact, I'm only here because the folks at mobileread told me I'd probably have better luck having my question/s answered here than there. So just to confirm, I can repartition the drive using partition magic so I'll have one extra partition for the books I want to sideload, and I'm good to go already when I re-insert the SD card into the Nook? Or do I have to attempt the code that you gave in the thread you linked?
If you want to have a single FAT partition on your SD card you can do that without much change.
It comes down to whether you want to be able to pull the SD card and plug it into random desktops and things.
If you want to have multiple partitions or ext3 partitions you will have to use the new vold in the link above.
if used windows 7,8. Insert a memory card into the card reader. Go to cmd(administrator mode) and run command:
Diskpart
List Disk
Select Disk 1 (#select sdcard)
clean (#clean partition sdcard)
create partition primary
active
format fs=fat32 quick
assign (#run command if not view sdcard in mycomputer )
Renate, I tried to repartition my SD card, but got a "disk is not formatted, do you want to format it now?" message. So I had no choice but to do a data recovery using EaseUs Partition Master first, then went ahead and clicked format now. Then I tried using Minitool Partition Wizard (couldn't find a free version of Partition Magic) to create new partitions in the formatted SD card so that the NookManager partition would be larger (27 GB) while the NookBackup partition would be 2 GB. Except that I can't seem to create any new partitions at all. And I also have no idea how to restore the data I'd backed up earlier either.
Sorry, I missed seeing this come up when you posted it.
When your Nook asks you if you want to format you should say "No!".
It could be that it misidentified the situation.
In any case, you want to look closer before formatting anything.
Here's a gotcha.
If you are using ext3 and the internal clock has reset itself then the last mount will be in the future.
That makes things angry. Check that the date/time on the Nook is correct.
You can use gparted to give the card the partition layout you need (i.e. first NookManager partition is big, second NookBackup partition is only large enough to hold a backup), then write the first partition from NookManager.img into first partition of the card (you need to do something roughly similar to this. Then you can use gparted to set the "boot" flag on the first partition and use the card to backup&root your Nook. Then remove the "boot" flag, and keep using the card for storage (it's a bit messy to have both user&app files AND NookManager boot files in the same place, but if you only have one card, then this is inevitable - i haven't found a way to mount the second or the third partitions from the card). The card will act as normal storage device when flag is not set, and as NookManager bootable card when flag is set.