Related
I have my nook rooted through my memory card. When I check how much internal storage I have on it through the nook it shows only 900 mb. It shows the same when I have it hooked to my computer. I know its supposed to have 5 gigs. I havent downloaded anything so I dont know where all the 4 + gigs went. Can anyone help? Thanks.
Can anyone please help?
thegameksk said:
Can anyone please help?
Click to expand...
Click to collapse
Barnes & Noble repartitioned the newest Nook Colors. If you had done even a hint of research before starting yet another thread you would know that.....which is why no one answered you last night when you asked this question....C'mon man this isn't customer service, do a search before you post.
How bout I did research and everything that i've seen has said that 5 gigs should show not 900 mb. The nook has 8 gigs. 3 are used for the os/repair and 5 for downloading things.
Nope, you are wrong.
New models made in May or refurb units as of May are partitioned for 1 GB of space.
http://forum.xda-developers.com/showpost.php?p=13772065&postcount=4
http://forum.xda-developers.com/showthread.php?t=1083506
http://forum.xda-developers.com/showthread.php?t=1080445
http://forum.xda-developers.com/showthread.php?t=1077321
Thats bs. When I bought it I was told there were 5 gigs for storage of files from my computer. Lokks like im sending this back. Thanks. Sorry bout the tude before.
No worries...I didn't mean to jump on you either. Just gets frustrating seeing new posts with the same old questions. Makes it tough to stay on top of the most current stuff and gets a little frustrating.
YeA i had searched but everything that came back said 5 gigs. Based on my reading of the threads that were posted theres no way to reparation the nook?
thegameksk said:
YeA i had searched but everything that came back said 5 gigs. Based on my reading of the threads that were posted theres no way to reparation the nook?
Click to expand...
Click to collapse
It's being worked on by many, but as of yet has not been solved. Conventional methods have come up empty. I'm quite sure we're getting closer to a solution though.
I was doing some research and came across this:
Here's how to convert a new NC (or one where you don't care about anything in /data and /media that won't be automatically restored by B&N) with only a 1GB /media space, back to one with with 5GB media space:
Boot a rooted Android system in the external SD card slot:
Access the rooted OS command line prompt, using either ConnectBot or ADB.
Fire up "busybox fdisk /dev/block/mmcblk0"
Delete partition #8 (the /media partition).
Note the size of partition #7 (the cache partition), and delete it as well.
Delete partition #6 (the /data partition).
Recreate partition #6 (the /data partition), to the size you want (say 1GB).
Recreate partition #7 (the /cache partition), to the size noted in step #5.
Recreate partition #8 (the /media partition), to occupy the remainder of the space.
Remove the SDcard and reboot.
When the NC boots its native system, it will recreate (just like a factory reset), the contents of the resized partitions. Yes, you will have to reregister. Of course, the same process, but with a different number in step #7, can give you more app space.
This is easily scriptable as well, and I fully expect such scripts.
Do you think this could work? I dont know enough about modding to try it. lol
!! Important: Make a backup of your Nook device first !!
Resize partitions
1. Download Gparted LiveCD
2. Extract onto FAT / FAT32 USB memory stick or burn to CD-ROM
3. If on a USB memory stick, run \utils\win32\makeboot.bat from the memory stick.
Do NOT run makeboot from a hard disk!
4. Boot computer from USB device into Gparted
5. Connect your Nook running Noogie of a Micro USB card (this will make the partitions visible to Gparted).
6. Resize the last partition (nr 8) labelled "data" (= Barnes & Nobles content)
Make sure to move the partition to the far right.
7. Move the next-to-last partition (nr 7) labelled "cache" without resizing it.
8. Extend the next-to-next-to-last partition (nr 6) labelled "nook" (Side loaded content) to fill the gap.
9. Remove USB cord, Micro USB card and boot your Nook.
10. In Settings you can inspect the amount of storage space.
I received errors when the partitions were about to be moved on the disk.
I changed the partitioning resize to field where it says "Align to:" from "MiB" to "Cylinder". After a 2nd attempt and doing each partition individually all worked out well.
For those only with Windows, download Gparted LiveCD iso image and use virtualbox to boot from it. It still worked well.
Edit: I successfully repartitioned two of my Nook Simple Touch using the method above + virtualbox + Gparted LiveCD iso.
Surprisingly, the size of partitions in my two NST were slightly different, suggesting that the physical size and location of partitions don't matter as long as their order and type in the partition table are as expected and the size is big enough to hold files there. I resized and moved the last three partitions as I wanted several times and made sure they work well.
Factory reset, upgrade to 1.2.1 (this seems to require the cache partition to be big enough to hold the firmware update file: something like 128MB worked for me), rooting all worked well with resized partitions. I ended up shrinking the cache partition down to 32MB and the data partition to 128MB, reserving 1.11GB for the side-loaded contents. I'm sure the system partition can also be shrunken, but I didn't go that far.
Why a live cd? Does installing gparted to whatever linux flavor you're using not work?
I don't use linux on my PC... only on hacked router & nas.
Goggles2114 said:
Why a live cd? Does installing gparted to whatever linux flavor you're using not work?
Click to expand...
Click to collapse
So dump Noogie on a microsd card run noogie and while noogie's running plug nook into pc? Do you just plutg it in and it does everything auto, or does something in noogie need to be run? Does this work on a nook touch glow?
Sorry to sound so dense but rooted using NookManager.
Edit more to the point it's throwing up an error when trying to move sdb8 around. It shrank fine just won't move. Not sure why. Not getting any useful error messages. Just 'can't have overlapping partitions.'
Odd. I was able to move it twice and get it to behave. Yet do the same n one move and Nothing. Apologies for the rinning Log just. Meh. The rest of the partitions resized in one step. sdb8 was the one that needed two steps.
Aaaand Success. Showing up as having 913MB free as opposed to like 212 or whatever.
Edit: now I'm getting a constant 'low space' warning from nook (understandable.) And installing apps is hit/miss on if they'll actually install. Keeps claiming space issues.
Query. Do apps install to the BnN partition or where?
Good to hear another success story. In my case I squeezed all the way to 1.45GB for the side-loaded contents. boot/rom/system/cache/data partitions are shrunken, and factory partition is busted. I had to use fdisk instead of GPartED to completely recreate the partition table, though.
I think, apps are installed to the data partition (the 8th one) under /data/app. Before being installed it's downloaded to cache partition (the 7th one). In my case I gave 16M for cache and 128M for data. If you are low on the data partition and have some space left on the system partition, you can move apps from /data/app to /system/app.
Goggles2114 said:
So dump Noogie on a microsd card run noogie and while noogie's running plug nook into pc? Do you just plutg it in and it does everything auto, or does something in noogie need to be run? Does this work on a nook touch glow?
Sorry to sound so dense but rooted using NookManager.
Edit more to the point it's throwing up an error when trying to move sdb8 around. It shrank fine just won't move. Not sure why. Not getting any useful error messages. Just 'can't have overlapping partitions.'
Odd. I was able to move it twice and get it to behave. Yet do the same n one move and Nothing. Apologies for the rinning Log just. Meh. The rest of the partitions resized in one step. sdb8 was the one that needed two steps.
Aaaand Success. Showing up as having 913MB free as opposed to like 212 or whatever.
Edit: now I'm getting a constant 'low space' warning from nook (understandable.) And installing apps is hit/miss on if they'll actually install. Keeps claiming space issues.
Query. Do apps install to the BnN partition or where?
Click to expand...
Click to collapse
What's the point of doing all this?
You gave a list of instructions, but not the goal they achieve.
L_R_N said:
What's the point of doing all this?
You gave a list of instructions, but not the goal they achieve.
Click to expand...
Click to collapse
Which post are you referring to?
Troute said:
Which post are you referring to?
Click to expand...
Click to collapse
.c0.'s original post.
His instructions describe how to use gparted to resize the partitions on the NST to make full use of the memory available after you have rooted it. I've used gparted before so maybe they were clearer to me than to others but the thread title was the main clue.
Troute said:
His instructions describe how to use gparted to resize the partitions on the NST to make full use of the memory available after you have rooted it. I've used gparted before so maybe they were clearer to me than to others but the thread title was the main clue.
Click to expand...
Click to collapse
I kind of thought that Nook's internal 2GB flash is already sanely formatted (i.e. most space is dedicated to the partition that is mounted at /media). If that is not the case, then that should be noted in the first post. It would also be cool if it said exactly how much space each partition has (I think i saw these partitions back when i've used Noogie to make initial backup of my device, but i don't remember the details), and how much space you would gain, and on which partition (and where it is mounted).
L_R_N said:
I kind of thought that Nook's internal 2GB flash is already sanely formatted (i.e. most space is dedicated to the partition that is mounted at /media). If that is not the case, then that should be noted in the first post. It would also be cool if it said exactly how much space each partition has (I think i saw these partitions back when i've used Noogie to make initial backup of my device, but i don't remember the details), and how much space you would gain, and on which partition (and where it is mounted).
Click to expand...
Click to collapse
Thanks! i did the work 880MB for side loaded content now!!!
on one of my NST i had an issue resizing the FAT32 partition and i had to format it to make it work.
Other than that all went ok!
Thanks
How to maximize RAM available for apps
I found this easy to read table here.
I doubt that I will ever download books from B&N. I want to minimize the space for that. I infer that I should minimize partition 8 that gets mounted to \data. Is there a practical / actual minimum for this?
I see that anything I copy in from my PC over USB is going into media. 100MB should be more than I need. I could put in an SD card for this sort of thing if it grows.
My question is, which partition do I want to increase to make the maximum available to apps downloaded from the google marketplace?
If an application requires a minimum of 512 MB of RAM, which partition(s) do I need to set >= 512?
New additional question: Upon some further research, I see that you can use sd cards for swapfiles to increase system RAM up to a maximum of 4GB. Does anyone know if it is possible to use this built-in storage for the same purpose?
.c0. said:
!! Important: Make a backup of your Nook device first !!
Resize partitions
1. Download Gparted LiveCD
2. Extract onto FAT / FAT32 USB memory stick or burn to CD-ROM
3. If on a USB memory stick, run \utils\win32\makeboot.bat from the memory stick.
Do NOT run makeboot from a hard disk!
4. Boot computer from USB device into Gparted
5. Connect your Nook running Noogie of a Micro USB card (this will make the partitions visible to Gparted).
6. Resize the last partition (nr 8) labelled "data" (= Barnes & Nobles content)
Make sure to move the partition to the far right.
7. Move the next-to-last partition (nr 7) labelled "cache" without resizing it.
8. Extend the next-to-next-to-last partition (nr 6) labelled "nook" (Side loaded content) to fill the gap.
9. Remove USB cord, Micro USB card and boot your Nook.
10. In Settings you can inspect the amount of storage space.
I received errors when the partitions were about to be moved on the disk.
I changed the partitioning resize to field where it says "Align to:" from "MiB" to "Cylinder". After a 2nd attempt and doing each partition individually all worked out well.
Click to expand...
Click to collapse
I have a little (maybe big?) problem. Can't partition with Gparted Live, as gparted scans my /dev/sdb (nook) infinitely. If I plug out my nook, other partitions (in my case: /dev/sda) become visible and ready. Looks like my nook hangs gparted. Tried on 2 different PCs and no effect. Tried different version of Gparted Live (i486 & amd64) - still nothing.
Of course noogie is inside the nook unit, ready and steady. Already made a backup of (non-rooted) device, plus partitions are visible in Minitool Partition Wizard on Windows 7.
What to do in this situation? Is Linux the only safe way to repartition device? Or maybe Minitool would be as effective and safe?
If Linux is the only way to go, how to make nook visible to Gparted?
Please, experts.
DJ Athlon said:
I have a little (maybe big?) problem. Can't partition with Gparted Live, as gparted scans my /dev/sdb (nook) infinitely. If I plug out my nook, other partitions (in my case: /dev/sda) become visible and ready. Looks like my nook hangs gparted. Tried on 2 different PCs and no effect. Tried different version of Gparted Live (i486 & amd64) - still nothing.
Of course noogie is inside the nook unit, ready and steady. Already made a backup of (non-rooted) device, plus partitions are visible in Minitool Partition Wizard on Windows 7.
What to do in this situation? Is Linux the only safe way to repartition device? Or maybe Minitool would be as effective and safe?
If Linux is the only way to go, how to make nook visible to Gparted?
Please, experts.
Click to expand...
Click to collapse
If Gparted doesn't work for you, I'd highly recommend Minitool Partiton Wizard - it's what I used to partiton my Nook. Nice, easy UI, too.
Yeah, I often work with Minitool, but is it as safe as Gparted when it comes to nook?
DJ Athlon said:
Yeah, I often work with Minitool, but is it as safe as Gparted when it comes to nook?
Click to expand...
Click to collapse
Yeah, it is. Just make sure to make a Noogie backup before repartitoning.
Sorry for bugging you, but can't shrink userdata(ext3). What to do? Delete that partition and re-create it or...?
DJ Athlon said:
Sorry for bugging you, but can't shrink userdata(ext3). What to do? Delete that partition and re-create it or...?
Click to expand...
Click to collapse
Yes, delete and recreate is the way to go.
Please, people, help me
Write step to step guide for work with Minitool Partiton Wizard
I want to free the reserved space for B&N books of my NST ver. 1.2.1
The device is already rooted.
I installed Minitool Partiton Wizard on my PC, but after connecting it thru USB cable with my Nook, it only see "official" 240MBs.
Cannot find other around 750 MB reserved storage for B&N books ?
What to do
Explain to me, please
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...
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
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!