Here's my contribution,
A Friend has a TP that I 'keep upto date' for him, He wanted to get to 4.3, so I've done that, however resizing partitions in HP world just seems a pain. So here's some flashable ZIP's to do the hard lifting for you.
4 versions I'm uploading (shout if you want a different sizing).
First add's 8gb to the data size (ontop of what you have already, just look in the storage system setting option for that info) the second adds 12gb, then 16gb and finally 24gb.
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
Just pick the one that matches what you want (obviously don't try the 16 / 24 on the 16gb device! and make sure you have enough 'clean' space before you start)
What I recommend doing is moving everything you can off the old 'SDCard' partition, using Recovery in the tether mode (int the storage menu), once you have removed as much as you can (remember the 'hidden' .???? folders and don't go deleting anything that's WebOs based!)
Then just flash the ZIP you think meets your requirements.
UPDATE - Uploaded the revert scripts, I've not tested them but they should be fine.
Hope that helps.
Two way trip
Edit: To revert these changes users can do a full uninstall using the ACMEUinstaller2. This will remove all partition changes and files added when installing Android:
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
In addition Gradular The Ape have created flashable zips that can reverse the partition changes the previous Android state . Find these in the above post and in Gradular's second post in his thread here: How to guide for changing your system, data, and cache partition sizes to whatever you want.
RolandDeschain79 said:
This is great thank you! A few people have run into problems when moving around data with the tailor, this should totally get around that:good:
I've got to ask, would it be possible to create a reverse of these files? The problem with this setup is that it's a one way trip. If users don't like, or have problems, they'd have to go through the pain of using tailor to rearrange their space again. Being able to add and remove the space with a zip would be a lot more convenient and give users a round trip pass for changing the partition sizes.
Cheers:highfive:
Click to expand...
Click to collapse
Shouldn't be an issue, I've obviously not got a TP to play with here, so can't test, and I don't like to put stuff out there that I've not at least done a once over of.
I'll have a look at it tomorrow when I've got access to the device and post a few ZIP's. I'll just do an 'inverse' of the four I've already done so you can undo a change.
the_ape said:
Here's my contribution,
A Friend has a TP that I 'keep upto date' for him, He wanted to get to 4.3, so I've done that, however resizing partitions in HP world just seems a pain. So here's some flashable ZIP's to do the hard lifting for you.
4 versions I'm uploading (shout if you want a different sizing).
First add's 8gb to the data size (ontop of what you have already, just look in the storage system setting option for that info) the second adds 12gb, then 16gb and finally 24gb.
Just pick the one that matches what you want (obviously don't try the 16 / 24 on the 16gb device! and make sure you have enough 'clean' space before you start)
What I recommend doing is moving everything you can off the old 'SDCard' partition, using Recovery in the tether mode (int the storage menu), once you have removed as much as you can (remember the 'hidden' .???? folders and don't go deleting anything that's WebOs based!)
Then just flash the ZIP you think meets your requirements.
Hope that helps.
Click to expand...
Click to collapse
the_ape said:
Shouldn't be an issue, I've obviously not got a TP to play with here, so can't test, and I don't like to put stuff out there that I've not at least done a once over of.
I'll have a look at it tomorrow when I've got access to the device and post a few ZIP's. I'll just do an 'inverse' of the four I've already done so you can undo a change.
Click to expand...
Click to collapse
Great... Guess it would reverse to the ACMEInstaller3 default partitions... If u'r flash resizes the (system) to 512 MiB... I would leave that one alone instead of making it go back to 400 MiB...
What is the breakdown for a 32GB TP using the data_plus_24576mb-signed... Is this about right ???
USB (media) - Depends what size TouchPad u have... (Decreases 112 MiB to be added to the Android (system) partition & Decreases about 23076 to be added to the 1.5 GiB already in the (data) partition)
Android (system) - 512 MiB (Increase of 112 MiB from ACMEInstaller3 400 MiB size OR do u leave it at the 400 MiB size ??? OR does it assume we used the update-cm-tenderloin-system_resize_512-0.4 already ???)
Android (cache) - 200 MiB (Stays at ACMEInstaller3 size)
Android (data) - 24576 MiB
Plan to so some testing how ACMEInstaller3 would handle an update-data_plus_24576mb-signed thru the CMInstall when reconfiguring or coming from a stock TP (before Android & any Recovery is install on the TP)... Any thoughts on this ??? Doesn't work from ACMEInstaller3... Although I did see it run... It didn't change the size of the default partitions that ACMEInstaller3 creates...
Update: Was able to play with the 24576 file... This was the break down of the partitions now..
USB (media) - 1.539 GiB
Android (system) - 400 MiB
Android (cache) - 200 MiB
Android (data) - 25.5 GiB
Unused Space - 16 MiB
So we will need to increase the (system) partition separate using the update-cm-tenderloin-system_resize_512-0.4 file if u'r still @ 400 MiB...
Y314K said:
Great... Guess it would reverse to the ACMEInstaller3 default partitions... If u'r flash resizes the (system) to 512 MiB... I would leave that one alone instead of making it go back to 400 MiB...
What is the breakdown for a 32GB TP using the data_plus_24576mb-signed... Is this about right ???
USB (media) - Depends what size TouchPad u have... (Decreases 112 MiB to be added to the Android (system) partition & Decreases about 23076 to be added to the 1.5 GiB already in the (data) partition)
Android (system) - 512 MiB (Increase of 112 MiB from ACMEInstaller3 400 MiB size OR do u leave it at the 400 MiB size ??? OR does it assume we used the update-cm-tenderloin-system_resize_512-0.4 already ???)
Android (cache) - 200 MiB (Stays at ACMEInstaller3 size)
Android (data) - 24576 MiB
Plan to so some testing how ACMEInstaller3 would handle an update-data_plus_24576mb-signed thru the CMInstall when reconfiguring or coming from a stock TP (before Android & any Recovery is install on the TP)... Any thoughts on this ??? Doesn't work from ACMEInstaller3... Although I did see it run... It didn't change the size of the default partitions that ACMEInstaller3 creates...
Update: Was able to play with the 24576 file... This was the break down of the partitions now..
USB (media) - 1.539 GiB
Android (system) - 400 MiB
Android (cache) - 200 MiB
Android (data) - 25.5 GiB
Unused Space - 16 MiB
So we will need to increase the (system) partition separate using the update-cm-tenderloin-system_resize_512-0.4 file if u'r still @ 400 MiB...
Click to expand...
Click to collapse
I've only tested it using cwm 6, and no, my zips dont touch the system size. Forgive my ignorance, but what is ACMEInstaller?
the_ape said:
I've only tested it using cwm 6, and no, my zips dont touch the system size. Forgive my ignorance, but what is ACMEInstaller?
Click to expand...
Click to collapse
Using CWM6_tenderloin-20121215 here...
We've all used ACMEInstaller @ the initial setup of Android... It creates the Android partitions & it installs moboot, recovery & rom & gapps... It was the double penguin screen that installed them.. Most of u have not used it since then... You just use the recovery to change things... I've been reconfiguring my TP lately so I've been using it a few times.... More of the exception & not the norm...
U'r flash files only increase size right... It doesn't format anything... Can u do a version of the 24576 file that also changes the (system) partition to 512 MiB... I can test it if u like.. Thanks.. :good:
Y314K said:
Using CWM6_tenderloin-20121215 here...
We've all used ACMEInstaller @ the initial setup of Android... It creates the Android partitions & it installs moboot, recovery & rom & gapps... It was the double penguin screen that installed them.. Most of u have not used it since then... You just use the recovery to change things... I've been reconfiguring my TP lately so I've been using it a few times.... More of the exception & not the norm...
U'r flash files only increase size right... It doesn't format anything... Can u do a version of the 24576 file that also changes the (system) partition to 512 MiB... I can test it if u like.. Thanks.. :good:
Click to expand...
Click to collapse
I'll put some that do system together in the morning, I didn't bother as it was already done that way on my friends. And no, it doesn't delete anything, just shunts partitions around.
Oh and yes I do remember ACME now, back in he early days was all done via scripts and terminal, so never played with it as such, think used it once for cm9. But doubt my scripts will run under that as they make use of a lot more than just pure recovery, hats why I recommend at least cwm6
the_ape said:
I'll put some that do system together in the morning, I didn't bother as it was already done that way on my friends. And no, it doesn't delete anything, just shunts partitions around.
Click to expand...
Click to collapse
Great... Thanks.. Should help for when some CM9 or CM10 folks upgrade to the 4.3 options... Or for those still with just 400 MiB (system)... I myself feel comfortable with Tailor... Which lets u squeeze out every bit of space out of our TP's...
Y314K said:
Great... Thanks.. Should help for when some CM9 or CM10 folks upgrade to the 4.3 options... Or for those still with just 400 MiB (system)... I myself feel comfortable with Tailor... Which lets u squeeze out every bit of space out of our TP's...
Click to expand...
Click to collapse
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Thanks... Gonna try the two largest one's right now... I am guessing if we ever need a special size... We can just manually change the data_plus_24576mb-signed/update/update_script.sh for the data & data_plus_24576mb-signed/update/system_script.sh for the system...
Code:
CHANGE_SIZE=24576
EXTPART="cm-data"
Code:
CHANGE_SIZE=512
EXTPART="cm-system"
Looking good!
the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Thank you for these very helpful packages, great work! This will help a lot of people change their partitions easily. I will test them out once you also post the reverse files so I can try the round trip experience cheers:good:
the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Think I found something... Or maybe not...
I had already used the data_plus_24576mb-signed yesterday...
I tried to use the sys_512mb_data_plus_24576mb-signed patch just to resize the (system) partition... I thought it would recognize that the (data) partition was already 24576 MiB or that the (media) partition didn't have 24576 to give again...
Got the following:
DO NOT DO ANYTHING ELSE!
REBOOT NOW!!!
Resizing the Data Partition ...
=== Reallocating 24576MB from media to cm-data
Preparing tools...
Checking media...
media:1464=>23112 cm-data:26112=>50688
media_fs tot=1575 sz=628 free=947
cannot resize media
>>FAILED<<
Lets tidy up ...
All Done ...
Click the thanks button
if you found this useful
The_Ape
Install from sdcard complete.
Click to expand...
Click to collapse
Guess the FAIL part of it is the safety check...
Went back to WebOS... And Tailor is telling me my new partition break down is as follow...
USB (media) - 1.539 GiB => 1.43 GiB
Android (system) - 400 MiB => 512 MiB
Android (cache) - 200 MiB => 200 MiB
Android (data) - 25.5 GiB => 25.5 GiB (This includes the 24576MB + 1.5GiB that ACMEInstaller3 created the (data) partition with)
Unused Space - 16 MiB => 16 MiB
So everything worked fine... Wonder if the FAIL message can be specific enough when it's due to not having enough space in (media) to move over or if it's due to (data) already being the requested size... The part that said cm-data:26112=>50688 made me think it was forcing the mod... Also the media:1464=>23112 looks weird to me... Like it's shifting space from (data) to (system) to send back to (data)..
Y314K said:
Thanks... Gonna try the two largest one's right now... I am guessing if we ever need a special size... We can just manually change the data_plus_24576mb-signed/update/update_script.sh for the data & data_plus_24576mb-signed/update/system_script.sh for the system...
Code:
CHANGE_SIZE=24576
EXTPART="cm-data"
Code:
CHANGE_SIZE=512
EXTPART="cm-system"
Click to expand...
Click to collapse
Yup, that's the one, you can change the other partitions that way too if you wanted too, but the sizes here should be pretty close for most people.
However if your a bit more confident with what your doing then help yourself, after all, your device, you should know best what sizes are right for you.
Y314K said:
Think I found something... Or maybe not...
I had already used the data_plus_24576mb-signed yesterday...
I tried to use the sys_512mb_data_plus_24576mb-signed patch just to resize the (system) partition... I thought it would recognize that the (data) partition was already 24576 MiB or that the (media) partition didn't have 24576 to give again...
Got the following:
Guess the FAIL part of it is the safety check...
Went back to WebOS... And Tailor is telling me my new partition break down is as follow...
USB (media) - 1.539 GiB => 1.43 GiB
Android (system) - 400 MiB => 512 MiB
Android (cache) - 200 MiB => 200 MiB
Android (data) - 25.5 GiB => 25.5 GiB (This includes the 24576MB + 1.5GiB that ACMEInstaller3 created the (data) partition with)
Unused Space - 16 MiB => 16 MiB
So everything worked fine... Wonder if the FAIL message can be specific enough when it's due to not having enough space in (media) to move over or if it's due to (data) already being the requested size... The part that said cm-data:26112=>50688 made me think it was forcing the mod... Also the media:1464=>23112 looks weird to me... Like it's shifting space from (data) to (system) to send back to (data)..
Click to expand...
Click to collapse
There is very little error checking/reporting built in, it 'shouldnt' cause any issues if your sizes are not able to be changed, but the output has not been friendlied up, after all I knocked it up so I didnt have to use WebOS, it does however have a quick look to see if it's possible to do the command it's meant to be doing before it tries (as you can see)
RolandDeschain79 said:
Thank you for these very helpful packages, great work! This will help a lot of people change their partitions easily. I will test them out once you also post the reverse files so I can try the round trip experience cheers:good:
Click to expand...
Click to collapse
Damn! I forgot all about the revert ones, could anyone let me know what the 'original standard' partition sizes are for the 32gb and the 16gb and I'll knock a zip for each together.
the_ape said:
Damn! I forgot all about the revert ones, could anyone let me know what the 'original standard' partition sizes are for the 32gb and the 16gb and I'll knock a zip for each together.
Click to expand...
Click to collapse
Neve mind about WebOS partition sizes since most won't want to have to rerun ACMEInstaller3..
My 32GB after a reconfig & without any Android part install shows...
USB (media): 27.663 MiB (Partition Size 28296 MiB)
Unused Space: 8 MiB
My 32GB after a reconfig & first Android Installation shows..
USB (media): 25.539 GiB (Partition Size: 26152 MiB)
Android (system): 400 MiB
Android (cache): 200 MiB
Android (data): 1.5 GiB
Unused Space: 16 MiB
U would want a reverse flash that would only shift the 24576 MB back from (data) to (media)... Keeping the (system) @ 512 MB seems like a must thing to do now.. RolandDeschain79 probably has a better idea of what would be best for most...
Not sure about 16GB models...
That's the info I would need. What would be best for the 16GB models?
can we resize the partition from windows ?
HashTagHell said:
That's the info I would need. What would be best for the 16GB models?
Click to expand...
Click to collapse
:good: I want to try it also
the_ape said:
As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
Click to expand...
Click to collapse
Thansk for your work. Now, pardon my newbines on the touchpad, but here it goes.
I have my TP with CM7, very old and unstable.
1) Can I use your ZIPs to repartition before moving to CM9 or CM10?
2) Can I just boot to recovery and flash this no matter what I have today?
3) I have a 32GB TP. If I use for example, sys_512mb_data_plus_16384mb-signed.zip I would have used about half meg for system, and 16GB for data, what happens with the remaining 15.5 GB?
Thanks!
Related
I'have flashed a lot of roms already but i'am still wondering how the memory works.
My favorites are the roms with Sense from DungPHP.
Now i'am running Coredroid that gives a load of manual options but also crashed unexpectedly.
Why this questions:
Every rom crashes somewhile. To understand how the memory works can help to find the rootcause. That can be application related, or configuration for the partitions, core etc.. Now only the developers know this (should know )
My Phone:
The Phone HD2 HTC LEO (EU) has 512 Mb memory
EXT4 partition of 2 gb
SWAP 256 mb
SD card of 16 Gb, 4mb speed
[*]What kind of memory's are there?
[*]and where are they used for?
To install the Rom we have to give the correct configuration like:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 175M
cache ya 5M
userdata ya|asize|hr allsize
So when i have 512mb - 1 - 5 - 175 - 5 = 313 mb left over
[*]Where is the left 313 mb used for?
[*]What is installed on the EXT4 partition?
[*]How much do you need to keep for good performance?
This are a lot of questions and i hope someone can help me to figure it out so we have a usefull tutorial page left over.
[*]Where is the left 313 mb used for?
[*]What is installed on the EXT4 partition?
[*]How much do you need to keep for good performance?
Click to expand...
Click to collapse
1 - 313 would be the userdata partition (allsize). This is the only nand partition which counts towards total internal storage.
2 - depends on the rom, some put user installed apps there, some put apps and dalvik cache, some put the whole data partition there.
3 - doesn't matter, you are talking about rom, not ram,, free rom has no effect on performance.( well, perhaps if every tiny scrap of space is full, but you sound like you meant ram)
You are right RAM has effect on performance.
The problem for me is that i understand lots of fragments of the theory but it is not complete.
Like today i have installed a backup, and later a full installation of a rom on my phone. And this rom was working fine in the past and now the battery lacks and streaming video is not working. Why??
I did a cleanup to factory, and cache and dalvic cache, but it looks like something stayes and is not formatted.
Back to runny. Video works fine now. But the sense is stopping very often due to lack of memory.
Is there a way to improve this?
I removed almost all widgets from main screen but after opening an application it is stooped and needs to be reloaded.
Sent from my HTC Runnymede using xda premium
Flash marc 0.1.9 kernel and then add a zram (100mb) script to increase virtual memory size.
I already improved the phone by changing the config from 5/170/5 to 10/180/10. Especially cash was the problem what I think. Till now it worked fine.
Sent from my HTC Runnymede using xda premium
Hello guys i have a T-Mobile HD2. And i know its has 1 gb rom.But the toolkit for hd2 supports only 450 mb max partition. How can i make it 1 gb? Thanks,,
no one knows :/
that 450 is the system partition only, if you made a 1gb system partition, you wouldn't be able to install anything, and you would waste a heap of space. when you setup the partition layout, anything left over becomes the data partition. so a 450 meg partition layout would leave about 550meg as the data partition for your user data, apps and such like..
Also, there's no point making the partition bigger than you need, ,if you flash a 200meg rom to a 450meg layout, you will lose the 250meg difference, it wont be used by the data partition, it will be wasted space.
engineerr said:
Hello guys i have a T-Mobile HD2. And i know its has 1 gb rom.But the toolkit for hd2 supports only 450 mb max partition. How can i make it 1 gb? Thanks,,
Click to expand...
Click to collapse
You can use clk1.5 to increase the system partition to that size in settings>repartition.
samsamuel said:
that 450 is the system partition only, if you made a 1gb system partition, you wouldn't be able to install anything, and you would waste a heap of space. when you setup the partition layout, anything left over becomes the data partition. so a 450 meg partition layout would leave about 550meg as the data partition for your user data, apps and such like..
Also, there's no point making the partition bigger than you need, ,if you flash a 200meg rom to a 450meg layout, you will lose the 250meg difference, it wont be used by the data partition, it will be wasted space.
Click to expand...
Click to collapse
Oh i see so if i put 200 mb rom then the rest 800 mb i will be able to use
hengsheng120 said:
You can use clk1.5 to increase the system partition to that size in settings>repartition.
Click to expand...
Click to collapse
Thanks i will try
engineerr said:
Oh i see so if i put 200 mb rom then the rest 800 mb i will be able to use
Click to expand...
Click to collapse
Correct.
I'm looking for some input into what you fine folks think is the best partition scheme for the Kindle Fire. Share yours, constructively criticize others; this is a battle royale in which the winner will get my KF partitioned under his or her scheme.
6/7GB and then the rest for the OS. Only because yesterday I tried to transfer all my Amazon MP3 bought stuff using doubleTwist and 5GB wasn't enough and didn't give me room for anything else. :silly: 1GB is enough for the OS.
Jessical said:
6/7GB and then the rest for the OS. Only because yesterday I tried to transfer all my Amazon MP3 bought stuff using doubleTwist and 5GB wasn't enough and didn't give me room for anything else. :silly: 1GB is enough for the OS.
Click to expand...
Click to collapse
Isn't this the default?
moore.bryan said:
Isn't this the default?
Click to expand...
Click to collapse
I think that's his point.
Sent from my DROID3 using xda app-developers app
No, it's 5GB.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So, it seems, the forum has answered one of two options:
the ROM's native partition is fine or
increase the sdcard partition by 1GB.
About right?
Jessical said:
No, it's 5GB.
Click to expand...
Click to collapse
It looks like I misunderstand the Fire's memory partitioning..
When I look at the partitioning my Fire running CM9 nightly's from Hashcode, I see its got 528mb for System ROM (281 free), 1.17Gb Internal (975 mb free) and 5.36Gb for the SDcard partition. I thought that layout was standard. That's more than 5Gb for the SDCard though, right ?
Adding that up I get only about 7Gb accounted for, so I am for sure missing something. Recovery partition for TWRP maybe ?
I got these numbers from Titanium Backup Pro, so maybe its not telling me stuff I don't need to know about.
You are saying you can increase the SDCard partition from 5.36Gb to 6Gb by reducing the size of the Internal partition ?
If so, would that limit the number and size of the programs you could install on your Fire, but give you more room for music and stuff ?
Thanks,
Glenn
glennj99 said:
It looks like I misunderstand the Fire's memory partitioning..
When I look at the partitioning my my Fire running CM9 nightly's from Hashcode, I see its got 528mb for System ROM (281 free), 1.17Gb Internal (975 mb free) and 5.36Gb for the SDcard partition. I thought that layout was standard. That's more than 5Gb for the SDCard though, right ?
Adding that up I get only about 7Gb accounted for, so I am for sure missing something. Recovery partition for TWRP maybe ?
I got these numbers from Titanium Backup Pro, so maybe its not telling me stuff I don't need to know about.
You are saying you can increase the SDCard partition from 5.36Gb to 6Gb by reducing the size of the Internal partition ?
If so, would that limit the number and size of the programs you could install on your Fire, but give you more room for music and stuff ?
Thanks,
Glenn
Click to expand...
Click to collapse
I'm running Jelly Bean and it says my internal is 1.09GB, and then my internal SD is 5GB. I'm getting that from the Settings page...
It wouldn't limits the number of programs, but you'd probably have to push them to the SD card for storage (some apps already do that though). But yeah, it'd give you more space for media too.
Are you using this Jelly build?
moore.bryan said:
Are you using this Jelly build?
Click to expand...
Click to collapse
Yep.
Jessical said:
Yep.
Click to expand...
Click to collapse
I tried it, briefly, and jumped ship because it didn't auto-rotate from landscape to portrait. I check the thread, also briefly, but didn't see anyone reporting the same. Am I missing something?
Code:
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 525kB 512B
4 525kB 525kB 512B
5 525kB 16.9MB 16.4MB recovery
6 16.9MB 16.9MB 512B
7 16.9MB 25.1MB 8191kB boot
8 25.1MB 25.1MB 512B
9 25.1MB 537MB 512MB ext4 system
10 537MB 1561MB 1024MB ext4 userdata
11 1561MB 1817MB 256MB ext4 cache
12 1817MB 2841MB 1024MB fat32 media msftres
13 2841MB 7818MB 4977MB ext4 linux
Of course I have nearly 5gb dedicated to linux, but that space can be used for media.
/thread
What makes you think this is the best way? Not being difficult, just trying to understand the inner workings...
I recently had my 1 tb hdd on my sony laptop replaced with a 180 gig ssd. I let best buy do the switch because it was free and I figured why not. When I got it back with a clean install on the ssd there is only 95 gigs free. The c drive says 95 free out of 129 total. I knew I wouldn't get the whole 180 but why only 129? Just wondered if this is normal or not as this is my first ssd.
It's a matter of multiplication. 2 to the 10th power is 1024, so numerically you get a so-called 180 (or what not) but since the OS reads storage in terms of powers of 2, you get a different number.
Now, on the other hand, 130 seems way too low. I would say to go to disc management and see if there's another partition. Since this is a laptop, it likely has a recovery partition (unless you know your old drive didn't have one).
Sent from my LG-P999 using xda premium
Recovery partition is indeed the most likely reason. Disk Management will show you what the full size of the storage device (SSD in your case) is, as well as what volumes ("drives") it contains, and whether there's any unpartitioned space. It will also let you delete and resize partitions.
The easiest way to launch it on Win8 is to right-click the Start button (or hit [Win]+x) and select Disk Management from the menu, although you can also type "disk" into Start search and go to Settings, or type "diskmgmt.msc" and hit [Enter] immediately.
Thanks for the replies. I will check into the disc management.
Sent from my Galaxy Nexus using xda premium
Thanks guys I found the disc management and I see that there are 4 other partitions besides my c drive. Would anyone know what ones are safe to delete if any?
OEM : 260 mb
Recovery: 1.44 GB
EFI System: 260 mb
Recovery: 36 GB
Im assuming I should probably keep the OEM and EFI partitions but what about the two recoveries. I have a recovery flash drive which is how the os got flashed to this ssd in the first place.
Thanks again if anyone has time to help me out.
ROORnNUGZ said:
Thanks guys I found the disc management and I see that there are 4 other partitions besides my c drive. Would anyone know what ones are safe to delete if any?
OEM : 260 mb
Recovery: 1.44 GB
EFI System: 260 mb
Recovery: 36 GB
Im assuming I should probably keep the OEM and EFI partitions but what about the two recoveries. I have a recovery flash drive which is how the os got flashed to this ssd in the first place.
Thanks again if anyone has time to help me out.
Click to expand...
Click to collapse
Both of the recoveries should be safe to delete, yea, though you'll have to resize the main partition (not hard, but not really for novices either) to get it back on there.
ROORnNUGZ said:
Thanks guys I found the disc management and I see that there are 4 other partitions besides my c drive. Would anyone know what ones are safe to delete if any?
OEM : 260 mb
Recovery: 1.44 GB
EFI System: 260 mb
Recovery: 36 GB
Im assuming I should probably keep the OEM and EFI partitions but what about the two recoveries. I have a recovery flash drive which is how the os got flashed to this ssd in the first place.
Thanks again if anyone has time to help me out.
Click to expand...
Click to collapse
For the amount you gain I would suggest only deleting the 36 Mb partition. Do you really need the extra space?
One expands a partition by deleting the partitions that are not desired and then increasing the size of the active partition. It is not hard to do from the control panel. The only consideration is that to expand a partition, I believe the space has to be adjacent to the existing partition. This means that you may be limited as to which partitions can be retained and still provide a single space for your active partition.
Ok cool I think I will be safe to delete the 36 gig recovery since I have a recovery flash drive. I will look up some more info on deleting and expanding partitions. I'm no expert but I can handle following instructions so I should be able to figure it out. Thanks again.
Expanding a partition is trivial, although (as @stevedebi said) it has to be adjacent (specifically, it must be located directly before) a block of free space. Deleting a partition that is right after your C drive will easily let you expand the C drive. Just right-click the drive (in Disk Management) and select Extend (might be Expand, something like that; it'll be obvious). It will default to using the maximum available size; confirm that dialog and a few seconds late you will have a newly enlarged drive.
The recovery was located right after the c drive so I was able to expand the c drive but first I had to delete the recovery through the command line. I found some you tube instructions and it was easy.
Sent from my Galaxy Nexus using xda premium
This is win8 right? Deleting the recovery partition means you can't boot into the recovery environment. Though I was under the impression the recovery partition needed to be only a GB at most, since the actual recovery tools are stored on the main partition.
Sent from my 820 using Board Express
link68759 said:
This is win8 right? Deleting the recovery partition means you can't boot into the recovery environment. Though I was under the impression the recovery partition needed to be only a GB at most, since the actual recovery tools are stored on the main partition.
Sent from my 820 using Board Express
Click to expand...
Click to collapse
Not sure about other systems, but my Toshiba has the option to make recovery media.
Sent from my IdeaTabA2109A using xda premium
I had already made a recovery flash drive using the sony software. This is what was used to install windows 8 on the ssd when it was put in. So I assumed that is as good as a recovery partition. Hopefully that is correct. I probably just can't use the refresh pc options anymore and would have to do a clean install with the flash drive. There is also still a 1.44 gig recovery partition that I left. So maybe that smaller one is made by windows and the larger one I deleted was from sony.
Well, I have the Cube i10 Android/Windows Tablet. Nice thing, except maybe the space for the Android OS being a bit too small.
I managed to upgrade my Windows 10 to 10586 and with seperate language pack, it back in my language.
Now i looked around the internet, if I could change the predefined space for either System. (It is possible to increase the partition size of the Andorid OS, but it requires a re-flashing, which I don't neccessarily want. In windows disc-management i saw all the partitions given for android etc, but did not dare to touch something as it was shown in RAW-format. Now i installed a "real" partitioning program (Paragon Partition Manager 15) and it shows me the "real" informations.
Total disk: 28.9 gb (which sums up to ~32gb advertised)
- then a lot of small (5x 16 and 3x 64 and 1x 32mb) GTP partitions, no label, all hidden (i expect these to be android Dalvik, recovery and cache partitions)
- then 4x Linux ext4 partitions (16mb, partially full, 1gb, hardly full, 256mb, half full another almost full 1gb partition) don't know what these are, also all hidden
- then a 3GB Linux ext4 partition (which surely represents the ROM from the Android part, with exact taken/free space data from android)
- then - my problem - a 128mb GPT-Volume, which i can't move
- then the 22.7gb Windows Partition (is resizeable)
- and last, a 450mb hidden backup/windows recovery partition
my problem is, that i can't move the 128mb GPT-Volume. So even if i can split ~2-3gb off the Windows partition, it stays after the GPT volume but it has to be before that to be merged with the android 3gb to make it bigger. I read around that you can delete the GPT-partitions, but don't want to risk it. I "could" merge my 3gb Linux partition with any of the 4 other partitions, but as all of those are not empty, i expect them to be some system recovery backup or whatever. Any information?
I'm afraid that you have to do repartitioning with android flasher and then reinstall Windows too.
Sent from Nexus 6P using Tapatalk
sad, i was afraid that it would be able by editing the partition.tbl file in the rom. Well then i have to stay with the few space i got.