Related
NOOOOOOO! My cousin tried to partition my sd card for me and said he knew what he was doing. Next thing I know, everything is missing from my sd card including nandroid backups, PLUS it cut my memory down from 16gb to 13gb. Is this normal or what? He did it through the boot menu and did 512 for the swap and 512 for the other. Not sure what that means, but I'm pretty sure I got ****ed here. Any help would be appreciated. thanks in advance.
Sounds like he formated as NTFS or something with huge Allocation Units or something.
MuzikJay said:
NOOOOOOO! My cousin tried to partition my sd card for me and said he knew what he was doing. Next thing I know, everything is missing from my sd card including nandroid backups, PLUS it cut my memory down from 16gb to 13gb. Is this normal or what? He did it through the boot menu and did 512 for the swap and 512 for the other. Not sure what that means, but I'm pretty sure I got ****ed here. Any help would be appreciated. thanks in advance.
Click to expand...
Click to collapse
When you partition your card it also formats it.
The reason the capacity dropped is because it has been partitioned so that only the partition that you see, is only 13gb.
You have never made a backup of your SD card? You could tell your cousin to not touch your things.
A good piece of advice:
Always make backups of backups, on different media. Hopefully you have some nandroids saved to your desktop/laptop.
Sorry about that. Might be better in the future to do it yourself and follow guides on here. They are pretty straight forward and usually indicate when backups should be made. Sorry but those files are gone.
Partitioning a drive or card erases its contents.
You are F'd in the A! I feel your pain, I accidentally partitioned without saving all the stuff on my SD card first. Sorry for your loss.
damn. looks like it was my mistake then. well did he at least partition it right? so I don't have to again? lol. Im currently going through different file recovery programs in hope lol
Keep in mind, you can use a partition manager such as paragon partition manager to partition without formatting. Thats how I did it.
You should have lost 1 gig, not 3 if he formatted it correctly. Also, 512 swap is probably not a good idea.
Like the poster above recommended, use a partitioning program to sort your card out.. and yes it will format it again.
Get Test Disk (Opensource Disk Recovery) It will likely be able to recover everything no problem.
danknee said:
You should have lost 1 gig, not 3 if he formatted it correctly. Also, 512 swap is probably not a good idea.
Like the poster above recommended, use a partitioning program to sort your card out.. and yes it will format it again.
Click to expand...
Click to collapse
damn, so should i partition it again? and lower the swap to 512 or will that just take even more space away from the 13gb?
MuzikJay said:
damn, so should i partition it again? and lower the swap to 512 or will that just take even more space away from the 13gb?
Click to expand...
Click to collapse
Not through recovery, sounds like you have several ext partitions already. I use Paragon Partition Manager and you will have to load the card in a card reader outside of the phone.
Personally I don't use swap at all, the heavy read/write cycles kill sd cards at a much faster rate than even a2sd. Most guys that run a swap use 32 or 64 megabytes and 512 is fine for a2sd.
If your card really decreased 3 gigs in size then you will probably find that you have 3 swap partitions, 3 ext partitions and one 13gb fat32 partition. It would literally take 5 minutes to delete the extra partitions and restore the card with a partitioning program.
data recovery
If you add files or data to the card it will be very hard or impossible to recover. Run data recovery software on the disk immediately and it should find most of your data.
http://www.snapfiles.com/get/restoration.HTML
connect the card as a removable disk to a pc and try that software, you should be able to restore most of the stuff
Droidish said:
Get Test Disk (Opensource Disk Recovery) It will likely be able to recover everything no problem.
Click to expand...
Click to collapse
worked great! thanks!
So if i go to boot menu and choose, "Wipe SD:ext partition" will that get me back to 16gb or can I never get back that extra space?
MuzikJay said:
So if i go to boot menu and choose, "Wipe SD:ext partition" will that get me back to 16gb or can I never get back that extra space?
Click to expand...
Click to collapse
No, but if you simply select the option to 'partition with ext', it should recover most of your space other than that used for the ext (a2sd) partition.
MuzikJay said:
So if i go to boot menu and choose, "Wipe SD:ext partition" will that get me back to 16gb or can I never get back that extra space?
Click to expand...
Click to collapse
If you don't want to use a2sd you can get all of it back with a partition program.
Otherwise do what the last poster suggested and reformat your card with 32 or 0 swap and 512-1gb ext3 from Recovery.
thank you both so much
Don't forget, most companies sell cards in increments of 1,000, where a computer would read them in increments of 1024. So it's very likely your 16GB card would be read at about 14.5 to 15GB under normal circumstances.
hahaha "my cousin"
So I'm thinking of finally installing CWR on my phone but my question is - how do I partition my SD card for ROM's that use Apps2SD/Data2SD? Also, I see that different ROM's use different size CWR's, how do I change that? Probably noob questions.
haven't done it myself, but to partition read the FAQ about partition in hyperdroid:
http://forum.xda-developers.com/showthread.php?t=918899
for the different roms with different CWM, simply usb flash -> flash required CWM and you are ready to go.
cheers.
Skellyyy said:
So I'm thinking of finally installing CWR on my phone but my question is - how do I partition my SD card for ROM's that use Apps2SD/Data2SD? Also, I see that different ROM's use different size CWR's, how do I change that? Probably noob questions.
Click to expand...
Click to collapse
[HOW-TO] Make Ext4 from Recovery Without Losing FAT32 Data
I wrote a guide just for such occasions. =] Good luck.
Its actually really simple, it just looks confusing. CWM has 3 partition sizes for your phone memory, 150 250 and 400. These are the sizes your ROM can be with the respective types of CWM. I use 250. Now to partition your sd card its extremely simple. (NOTE: This is for windows only) Download Minitool partition wizard, load it up with your sdcard connected to your computer, now you should see the sdcard will be one partition formatted as FAT32. Now, if you right click on that and select move/resize then drag it to how big you want your A2SD partition to be. (THIS IS EXTREMELY IMPORTANT Drag it from the right so that the grey box is on the right of the FAT32 section. Dont make it larger than 1024 MB, however mine is 512MB and it is more than enough) Right, so now right click on the unallocated part of your sdcard and select create. Make it primary, not logical. The file type should be either EXT2,3 or 4. (I use 3 as it seems to be the most compatible) and there you go, done
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 was just gifted an NSTGL and have found that the backup size seems to differ from the original NST.
Before I proceed, can anybody else confirm a disk image of 1,953,792KB/2,000,683,008 bytes/1.86GB?
image for NSTG
my image size for NSTGL is 245,744kb
ladykayaker said:
my image size for NSTGL is 245,744kb
Click to expand...
Click to collapse
I don't mean compressed. I dunno how you're doing backups? But I first take a full backup of the raw disk and then compress with 7z. when I compress, my filesize is around there.
If we are talking about exact sizes of things, it's best to not talk in kB, MB, GB, but in bytes.
The Touch and the Glow are partitioned the same.
The first cylinder and the 7 partitions add up to exactly 1,944,059,904 bytes.
This all fits in a "2 GB" flash memory.
A "2 GB" could actually be about any size.
Mine happens to be 1,958,739,968 bytes.
What you have depends on what chips they swept off the factory floor that day.
When you make a full backup it copies the entire physical device.
This includes some stuff at the end which is not even in a partition.
Renate NST said:
If we are talking about exact sizes of things, it's best to not talk in kB, MB, GB, but in bytes.
The Touch and the Glow are partitioned the same.
The first cylinder and the 7 partitions add up to exactly 1,944,059,904 bytes.
This all fits in a "2 GB" flash memory.
A "2 GB" could actually be about any size.
Mine happens to be 1,958,739,968 bytes.
What you have depends on what chips they swept off the factory floor that day.
When you make a full backup it copies the entire physical device.
This includes some stuff at the end which is not even in a partition.
Click to expand...
Click to collapse
I think I did provide a byte number up there, but anyway thanks for the detailed response!
-e
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
I3ig Al said:
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
Click to expand...
Click to collapse
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
I like this. The only "issue" is that if more space were ever to be reallocated to /system or /cache, it'd require wiping /data obviously. Small price to pay. 500MB isn't too small a chunk for 8GB users.
75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
Actually it does. System data cache and boot, plus like 30 other ones, same as any other phone with no micro SD card
Sent from my Nexus 7 @1.60 GHz on Stock 4.2.2
I3ig Al said:
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
Click to expand...
Click to collapse
i think N4 uses FUSE (Filesystem in Userspace) file system
noobdeagle said:
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
Click to expand...
Click to collapse
That is for the sdcard.
The other partitions such as /system still have fixed amounts of space allocated
Sent from my Nexus 4 using xda app-developers app