Database Info

[Q] going crazy trying to figure out how to partition!

hi all, i have a rooted htc aria running froyo 2.2.ive got a new 16g card coming. i would like to partition. ive read way too much info on doing this, that im now totally confused! i cant figure out what steps this should be done in. ive got everything backed up. im not sure what program to use for the partitioning. have read not to use rom manager. im not sure about how many partitions i should have. after i copy my card contents to pc, where do they go when i copy them back? i just really need someone kind enough to walk me thru this. i have adhd and need specific instructions......thanx

chowceal said:
hi all, i have a rooted htc aria running froyo 2.2.ive got a new 16g card coming. i would like to partition. ive read way too much info on doing this, that im now totally confused! i cant figure out what steps this should be done in. ive got everything backed up. im not sure what program to use for the partitioning. have read not to use rom manager. im not sure about how many partitions i should have. after i copy my card contents to pc, where do they go when i copy them back? i just really need someone kind enough to walk me thru this. i have adhd and need specific instructions......thanx
Click to expand...
Click to collapse
Why do you need to partition buddy? Do you want multiple internal storages, or another reason? I may be able to help here with just a little more info.

i would like to partition the micro card.ive read that its better to have it partitioned?

chowceal said:
i would like to partition the micro card.ive read that its better to have it partitioned?
Click to expand...
Click to collapse
In some cases, putting a separate partition on your SD card and formatting to etx3 can be beneficial, especially with the Galaxy S devices. In day-to-day use with others phones though, you'll benefit far more from the extra storage than having multiple partitions. Do you have a Galaxy S mate?

i have a htc aria.

chowceal said:
i have a htc aria.
Click to expand...
Click to collapse
I found this for you, from the Aria forum:
To Enable A2SD:
Backup your applications
Backup your sdcard
Partition your sdcard with ROM Manager with an ext partition option. (ROM manager is in Market)
This should start a special mode of clockwork recovery, which will partition the sdcard.
That's the only reason you'd want to partition your card, so that if you're running out of memory you can move some of your apps to the SD card. ROM Manager is very easy to use, but I'll be here if you need me Good luck!

juzz86 said:
I found this for you, from the Aria forum:
To Enable A2SD:
Backup your applications
Backup your sdcard
Partition your sdcard with ROM Manager with an ext partition option. (ROM manager is in Market)
This should start a special mode of clockwork recovery, which will partition the sdcard.
That's the only reason you'd want to partition your card, so that if you're running out of memory you can move some of your apps to the SD card. ROM Manager is very easy to use, but I'll be here if you need me Good luck!
Click to expand...
Click to collapse
To follow onto this question. 1st time droid user, limited linux knowledge. I am running 2.2 on a brand new optimus t(mobile). I plan on rooting using z4root and flashing ROM (maybe megatron). Sdcard new (unused) only thing I have done with the phone is install a bunch of apps (which I can replace) and load my contact/gmail account.
I notice that my phone indicates 143kb internal available, so I assume I will have space limitations soon. It is my understanding that one of the benefits or rooting and putting on custom rom is the ability to have your phone recognize portions of the sd card as internal memory and, thus, "create" more internal space.
Considering my phone and my desire, can I go through the process of 1) rooting (z4root) 2) backup (custom recovery) 3) flash new rom/kernal 4) dump back up from sdcard onto PC via card reader 5) Use your above method to partition card?
Any suggestions/advice would be greatly appreciated, including partition types/sizes, process, procedure....or just tell me if I am an idiot and am way off base.
Thanks a lot

[GUIDE] Prep for App2SD and why do a "Wipe data / factory reset"

I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
These are the steps you should take before loading a new ROM:
1) Download your new ROM and relevant supporting or needed files like modem, alternate kernel, etc., and place them on your internal SD.
2) Backup your applications, settings, messages, etc., with a backup tool like Titanium Backup, image specific backup tool, etc.
3) Boot into recovery and run a “wipe data/factory reset"
4) Follow the developers ROM loading instructions.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
Nothing else on your SD card (internal or external) outside of these directories is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them. Your external SD card and SIM do not need to be removed. The goal here is load a new or updated ROM in as much a clean environment that you can. Files left behind in these, especially cache and davlik-cache can cause some of the strangest problems. The kind that nobody can really resolve.
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The sd-ext partition is an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have APP2SD or data2ext enabled. It is popularly used on devices that have little memory allotted to the /data partition. A misfortune that in my experience, Captivate does not partake in. Still, users who want to install more programs than the internal memory allows can take advantage of this partition and use it with a ROM supporting this feature.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Disclaimer! I am not responsible for any damage you may cause to your phone or SD Card if you try to enable/use sd-ext.
To enable sd-ext in ClockWork Mod (ROM Manager):
Boot into CWM
Go to Advanced
Then to "Partition SD Card"
Choose an sd-ext size
Then choose a swap size, or not. Swap is just like windows' virtual memory. The system will use it when you're running low on RAM and use it as temporary RAM storage. This is where you'll probably see an increase in speed.
Just for fun I put sd-ext at 512MB and Swap at 64MB which is probably more than plenty for the swap. The swap will assist a little with memory and with the extra space I can move my apps over to it with a program like App2SD or in most custom ROMs nowadays just use the "move to USB" option in "Manage Applications". Titanium Backup will also move apps to SD for you and I'm sure you can find plenty more in the market.
You can also use a tool like Minitool Partition Wizard:
1. Open Minitool Partition Wizard
2. Delete Existing Partition from SDCard (Backup data first!!)
3. Create Fat32 Partition
Note: Set all partitions to PRIMARY (Steps 3 - 6)
4. Create EXT2 Partition (System) about 150MB-200MB depend on ROM
5. Create EXT2 Partition (Data) about 150MB-250MB
6. Create EXT2 Partition (Cache) about 50MB
Personally I don't see a need to do any of this on either of my Captivate phones though I have played with it on my DEV phone.
And since it does play a big role and needs to be cleared at times...
Davlik-Cache - dalvik cache is a program cache area for the program "Dalvik". Dalvik is a java based virtual machine that is the base for running your (.apk) programs. In order to make access times faster (there wasn't a JIT compiler installed by default until Android 2.2), the dalvik-cache is the result of dalvik doing a optimization of the running program/s. This optimization is kept so that it is then re-used every time you use your application/s. By default, davlik-cache is located in your /data partition.
No, I'm not looking for donations. Just trying to clarify things for some.

Great info, but a "guide" assists you in doing something, this is just straight info.

While I initially intended on writing it to guide flashers into the benefits of a wipe data / factory reset, and avoiding the myriad of strange issues experienced, I can see now where it can more construed as informational. Hmmm... maybe I'll add more to it or ask a mod to change the title topic for me.
Regardless, my hope is that some people get some benefit out of it otherwise I've only wasted my time.

Thanks, I've been wondering for a while what that actually did.

Great start for a guide that should clear the boards up a bit. I vote it to be stickied after adding a bit more info on backing up, partitioning the sd card, dalvik cache, etc.
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.

Cozmo1 said:
I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Nothing else on your SD card (internal or external) is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them.
If you plan on trying several different ROM's and/or updating your favorite ROM every time a new version is released you need to invest in an application like Titanium Backup or one that comes with your ROM if it's supplied with one. MIUI includes one that works extremely well. Performing a “wipe data/factory reset" after loading your new ROM and before booting into it should provide you with a smoother transition to your newly chosen or upgraded ROM. Having a standard backup and restoral process should help you enjoy it quicker too.
Click to expand...
Click to collapse
Here is something I keep in a word file to help answer what you are also trying to answer. It is a bit shorter and simplified but it may help to polish your thread for us simpletons.
Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them. It does this when you make a major change like replace the kernel/modem. Clearing the Dalvik cache will force Android OS to recompile the apps for the the new kernel/modem. This can take time on the first boot after clearing the Dalvik cache.
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons. You want to clear this out so it doesn't re-use the old cached data.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.

snowake said:
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.
Click to expand...
Click to collapse
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!

Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
do u have more info about "format your SD card, or partition a part of it as a ext file system" or how to do that.
i have read someone format part of the sdcard (class 10)to ext 2 or 4,to make the write n read faster.is that what you mean.can u guide me to the right direction.thank in advance.
? ? ? about this......(However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.)

Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
I struggled with all of this my first first few flashes.

xpakage said:
...Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them.
...
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.[/I]
Click to expand...
Click to collapse
That is much more boiled down. I looked back at the "how to flash" threads and a couple good explanations on custom roms. None explain this that I found.
Cosmo, here are some more thoughts on misunderstandings I have had and seen posted. Like post above I pasted from my notes, so may be incorrect.
Bootloaders: Same for Froyo/Eclaire in both i897 and i9000 roms. GB requires new bootloaders, but i897 are apparently cross-compatible. However, issues seem to pop up on i9000 roms with GB i897 bootloaders. If flashing back to Froyo, use the full jf6 stock, not cezar's stock eclaire without bootloaders.
Using Tibu: If no useful data (i.e. Bookmarks on dolphin) then simply click data only when restoring user apps. Typically no issues when restoring user apps after switching Android versions. However, system apps should not be restored because of the rom customizations. Especially when switching to GB because it uses different directory structure. I do not seem to have issues when staying on same version and restoring foreground (user accessible) apps with data only or restoring green text color sys apps with Tibu as icon (i.e. Accounts).
Rom manager: really only need the app if flash to stock and need to flash rom directly from cwm. If so, then flash cwm (top button in menu) and choose phone. This places update.zip in /sd, which is opened after selecting "reinstall update" in stock recovery. Usually have to select it twice for it to work. This will replace ATT stock 2e recovery (blue text) with cwm 2.5 (froyo).
Voodoo color, lagfix, sound: must either be included in kernel. Lagfix simply allows user to format sd as ext4 (linux). Color balances display so less blue iodes are used and color is more realistic. Sound allows clearer sound through headphones through tweaks enabled in voodoo app. If sound is not in kernel then purchase voodoo pro in market and it will install it into the kernel (if rooted, even if stock).

Thanks for clearing that up!
- Aaron

Updated with more details.

Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!

Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?

snowake said:
Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?
Click to expand...
Click to collapse
That is probably the safest way to do it within the phone itself. An alternate way would be to mount it to your computer:
In Windows right click the drive that was assigned to your internal SD card and then click on format. By default it'll most likely set you to Fat32 and if you click format it'll say its complete, but nothing will be deleted. Android being a Linux OS doesn't use fat. You can format it by choosing exFat, but by doing this...
!!!WARNING!!! be aware that you will lose everything on your internal SD card AND your external SD card.
Emphasis placed mainly for others that read this and might not know.
Safer and easier to do it within the phone.

snowake said:
Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!
Click to expand...
Click to collapse
This one is from MiniTool, though I wouldn't be surprised if Easus owned them. I didn't investigate to confirm. You can get the free home edition of MiniTool Partition Wizard here.

Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).

Any decent update(r)-script will do this for you.
Sent from my Infuse 4G

littlewierdo said:
Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).
Click to expand...
Click to collapse
I can run some tests on Odin's master clear to confirm what it does. Initially I would believe it does the same as a "wipe data / factory reset", but testing should let us know for sure. I'll test it this weekend. Maybe sooner.
Awesome to hear that I'm not the only advocate for SpinRite and I still use it a lot though not every 6 months like you do. It's definitely worth having and using.

MikeyMike01 said:
Any decent update(r)-script will do this for you.
Sent from my Infuse 4G
Click to expand...
Click to collapse
I totally 100% agree with you, MikeyMike01. Unfortunately, not all update scripts are created equally Asides from teaching people how to script themselves or parse through it, a task I do not have the time or patience to tackle, this it probably the easiest and best way to have users try to avoid the many and strange issues posted that possibly / most likely could've been avoided by using the tools at their disposal.
On a side note... I didn't notice you got yourself an Infuse 4G. Congrats! How do you like it? I've been out of contract for almost a year now and wouldn't mind upgrading (my wife is in contract), but I haven't seen anything really worth upgrading to or that does something I really need/want that the Captivate cannot, atm. I haven't looked up any specs and reviews on the Infuse yet tho.

Firerats + Data2ext Complete Installation Guide: Now works with Sense roms!

This thread serves as a guide to install both firerats and data2ext mods on a single rom and have them work simultaneously.
I do not take any credit for the creation of any files mentioned or attached, nor methods for the installation of each individual mod, nor roms, gapps, or otherwise mentioned content. All credit goes to those who created each mod, rom, gapps, and the methods for installing each individually. I only claim responsibility for my own research and the order and hierarchy of steps below that combine these incredible feats of development into a working system of internal storage expansion and space management.
Even though it is impossible to brick your phone using the guide below, I am not responsible if you break your device, because you have willfully chosen on your own to void your warranty by rooting your phone and installing the mods mentioned below.​
To make firerats work with data2ext simultaneously, follow these over-detailed instructions EXACTLY. This is written so that anyone who has never held a smartphone in their lives can understand and do this right the first time, so those of you that know what you're doing, sorry about the length, but it should be pretty easy for you.
Note: I've uploaded some pertinent files from the following steps and added all links to all files needed so you don't have to go find them yourself. I did not include any roms, gapps, or the freespace app from the Play Store(just download from your phone, or from the link in step 6d). Links for all necessary files are in their respective steps below. The only links to a rom or gapps are for ICS. Otherwise you'll have to find and use your own downloaded roms and the correct gapps for your rom. If you would rather use the links below to download the files instead of using the ones I provided, be my guest.
I've updated this guide to make installation much easier and work with Sense roms!​
Now on to the good stuff!!
Steps 1 through 7a are written for you to collect the files necessary, and to prepare your phone, sd card, and recovery for the correct method of installation of the collected files.
Steps 8 through 10 are to install the mods.
Preparation
1. Be sure to start from scratch!!! This means an UNPARTITIONED, FULLY WIPED sd card, fully wiped and rooted phone, and fully wiped recovery. Fresh file downloads for roms, gapps, and other mods you like wouldn't hurt either. If your phone is not rooted, go here, it's the best and easiest root method I've found.
1a. If you already have a partitioned sd card, insert it into your computer via a microsd adapter or other means(you cannot use your phone for this; it will not recognize that it's partitioned), delete the partitions and wipe the card using partition management software on your computer. I recommend EASEUS Partition Manager 9.1.1 Home Edition(Windows users only). If you use this program, after you delete partitions on your sd card, you will be left with unallocated space. Create a partition that takes up the entire unallocated space and set it as a Primary and FAT32 file system(remember, only do this to your sd card, NOT THE C: DRIVE!!!!).
2. Boot to recovery(hold down home, press and release power, then release home once recovery shows up)
2a. Be sure you have a recovery that supports flashing unsigned .zip files. If your recovery does not support flashing unsigned .zip files, flash a rom and then the corresponding gapps that are signed(cyanogenmod roms and gapps are the easiest way to go), boot into rom, sign in, download rom manager from Market/Play Store, open rom manager, flash clockworkmod recovery, and boot to recovery.
3. Make sure you are using latest 5.5.0.4 recovery, found here.
3a. If you are not already using the 5.5.0.4, flash the 5.5.0.4.zip in your current recovery(or follow the instructions from step 2a if you cannot flash unsigned .zip files) and reboot back into recovery.
4. In your new recovery, make sure you wipe everything, and go to advanced>partition SD card. Choose whatever size you want to have as internal storage(the 'M' means Megabyte, if you didn't already know...). I use 1024M or 2048M(i.e. 1Gb or 2Gb), depending on what mood I'm in, but it works with any of them. Then choose 0M swap size and wait for it to process.
5. Wipe everything once again(just to be safe), including sd-ext, and place your rom and preferred gapps on sd card, along with any other flashable modifications you like to use(I use the sd card speed boost, which can be found here. 2048Kb works best for my card, a 16Gb Class 4).
Note: For ICS users only! I use official, larger ICS gapps, found here(download the one next to 4.0.X, the link will be: '20120429'). The smaller gapps, as well as the current best ICS rom, can be found in whoshotjr2006's thread, here.
6. Make sure you have the latest firerats(1.5.8), which can be found here.
6a. Don't use any of the alphas or betas. Just 1.5.8. Download only the recovery-v1.5.8-CustomMTD_S.zip and boot-v1.5.8-CustomMTD_S.zip and place on sd card. Create a .txt file named 'mtdpartmap' and type 'mtd XXX XX'. These X's represent the size in numbers that you want your /system and /cache partition sizes to be, and therefore will not actually be used. See step 6b or 6c, depending on what rom you'll be using, for information on how to determine the correct partition sizes/numbers to use. DON'T KEEP THE X's IN THE FILE! REPLACE THEM WITH THE NUMBERS YOU WILL USE AFTER YOU DETERMINE WHAT YOUR /SYSTEM AND /CACHE SIZES SHOULD BE!
6b. For ICS users: If you are using the official, larger gapps, type 'mtd 190 60' into the text file and save to sd card. If you are using smaller gapps, type 'mtd 190 30'. Proceed to step 7.
6c. For Non-ICS users: To find out what numbers to replace the X's with in your mtdpartmap.txt, first wipe everything and install only the rom and gapps you'll be using this mod with. Then boot into rom, sign in, and follow step 6d. After you do this, however, you will need to repeat steps 5 and 6a, then proceed to step 7.
6d. You can download 'freespace' from the Play Store, which needs root access, and will show you the total size and space remaining for each of the /system, /data, /cache, /sdcard, and /ext partitions, so you can change the numbers in your mtdpartmap file to what you want the /system and /cache to be that best suits the rom you want to flash. The first number after 'mtd' is for the /system partition, the second number is for /cache. You can't change the /data, because it is dependent on what you set the system and cache sizes to, and will be set to what you partitioned the sd card to anyways. Also, keep at least a 5Mb allowance over what you need for both /system and /cache partitions as you will run into force closing problems if there is no breathing room, especially for the /cache partition.
7. The data2ext thread and .zip file can be found here.
7a. Download the unCoRrUpTeD_data2extV2.2.zip at the bottom of the post and place on sd card. DO NOT FLASH!!!
Summary of what should be accomplished after following steps 1 through 7a: You should now be using CWM Recovery 5.5.0.4, have a partitioned sd card, wiped everything, and placed the boot-v1.5.8-CustomMTD_S.zip, recovery-v1.5.8-CustomMTD_S.zip, unCoRrUpTeD_data2extV2.2.zip, mtdpartmap.txt, the rom and correct gapps, as well as any other mods you want to use onto your sd card. If all of this is true, move to step 8. If not, go back and find what you missed.
The Installation Process
8. Flash recovery-v1.5.8-CustomMTD_S.zip, then under mounts and storage, wipe /system, /cache, and /data in that order.
8a. Reboot to recovery(go to advanced>reboot recovery).
9. Flash rom, gapps, and whatever other mods you have or like, then flash boot-v1.5.8-CustomMTD_S.zip, then unCoRrUpTeD_data2extV2.2.zip, and reboot.
Note: the firerats installation thread for the HeroCDMA says to flash boot-v1.5.8-CustomMTD_S.zip after anything that changes the kernel specifications, but the unCoRrUpTeD_data2extV2.2.zip does not change these. The thread also says that adb is necessary to reboot; it's not. After wiping /system, /cache, and /data, just go to advanced>reboot recovery. It will work just fine, I promise. Newer recoveries don't need to use adb for this step.
10. Reboot immediately after signing in for data2ext to take effect.
That's it! You're all done! Set up your phone the way you want and start installing apps!
Summary of steps 1 through 10: By now, you should be using 5.5.0.4 recovery, have a partitioned sd card, have placed all necessary files, your rom, gapps, and other mods onto your sd card, flashed the correct files in the correct order and rebooted, signed in, and rebooted after signing in. You should now be looking at the home screen(or lockscreen) of your rom, and if you check storage from settings, you should see internal storage showing the size you partitioned the sd card to be in step 4.
Hopefully this wasn't too confusing...good luck!
If you have any questions, don't hesitate to post in this thread!

Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...

Hammerfest said:
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Click to expand...
Click to collapse
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.

goliath714 said:
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
Click to expand...
Click to collapse
I think 1.59 alpha... after a system crash a few months ago, i havent had the need to re-bookmark the firerats mediafire folder... I really should, and seeing as most file share hosts are closing down or restricting free access to files I really should re-download and archive them... god knows how many things I have lost because of the MAFIAA fiasco's...

Yeah that might be a good idea. Personally I've never used any alphas or betas so I really don't have any input for them lol
Sent from my HeroC using XDA

Bumping my own thread...lets get some more views for this thing! If you haven't tried it yet, or have questions about it, or simply don't know what it does, send me a message or post on this thread! It's really a very useful mod for those of you that use or like installing lots of apps...

Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?

I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE

Hmoobphajej said:
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
Click to expand...
Click to collapse
You have to unmout the partition first.
#Root-Hack_Mod*Always\=LTE

App2sd
Yea, I got that too, is it not working for you.
If not, add "/system/etc/init.d/40data2ext --enable" That made it work for me. Don't add "".
after reboot and the memory still hasn't change then go back in to terminal manager and add the above line and then reboot, should work then, never got firerats to play nice with the script, so i just use data2sd

laie1472 said:
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.

goliath714 said:
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
Click to expand...
Click to collapse
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE

In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?

fforward72 said:
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
Click to expand...
Click to collapse
You can install from the market
Sent from my HERO200 using xda app-developers app

ajrty33 said:
You can install from the market
Sent from my HERO200 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot!

laie1472 said:
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
How? The firerats mod allows you to change the /system and /cache partition sizes, but from what I can find, data2ext only applies the /ext partition to the /data partition to make the phone utilize the /ext partition as /data, and doesn't allow for modification of the /system and /cache partitions.

Updated
Edit: Updated again to fix minor wording issues and make links much prettier!

Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Sent from my HERO200

So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed".
Any ideas?

dankdank11 said:
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Click to expand...
Click to collapse
Firerats has nothing to do with recovery. It's about resizing partitions. Recovery functions on a level above, so whatever you do with firerats won't affect it. TWRP is a great recovery program.
Tux2609 said:
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed". Any ideas?
Click to expand...
Click to collapse
Try again. Go through the instructions verbatim, as outlined. I wouldn't deviate in any way.

SD Card partitioning on MTD ROMs

Hi There
Can someone explain what he\she did to partition SD card, and make all apps get installed on it.
Please note :
1. I don't want to use Titanium backup for this usage. I don't have the paid version and I'm tired of doing this one app at a time.
2. I saw some guides on the net, but they were all for GB.
(partition the microSD on PC using minitool) -can we use ext4 on our MTD ROMs ? What is the 1st partition for ? and the 2nd ?
(install busybox and super user) - Is it still needed ? (MIUI for example has LBE as su).
(install Link2SD) - Is it always in memory ?
(reboot and put partitioned SD card)
(Define Link2SD)
3. I also saw swapper instructions but I can manage with 170MB free RAM memory I get after removing all unnecessary system apps, and I remember ppl saying then that it kills the SDCard very quickly.
If someone has a clear guide or instructions that he knows work, that will be nice.
Thanks in advance.

Step 1. Partition your SD card to have a sd-ext partition. This can definitely be ext2 or FAT16. Anything else depends on your kernel. Most of them do support ext3 and 4, but... start with something fairly basic.
Regarding recoveries:
TWRP has always failed for me on this, so I'd avoid that.
This may be doable in CWM. I've seen reference to that newer versions of CWM removed the partition option, so you might need to flash an ICS ROM with an older kernel, repartition, and then flash back to the one you want.
Also note that if you use CWM to repartition, your SD-card will be wiped. So do a backup first.
Step 2. Install Mounts2SD. Either from XDA or the Play Store. Even if you do take it from the Play Store to get update notifications, I highly suggest grabbing the recovery script from the XDA thread so that you can get back your shifted applications without needing to re-download and install M2SD, since it likes to be on internal which means... shifted off.
Step 3. Open Mounts2SD. Grant SU rights at whatever point it asks for it during step 3. Hit the menu button. Go to Application Settings. Install the Startup Script. Tell it to use the built-in busybox as well, so that you don't need to install anything or worry about it failing. Back out of the Application Settings.
Step 4. Press on the Wrench to go into the actual specific settings. I currently have forced Cache, 1% Storage Threshold, Applications are the only bit moved, the File System Check is on and using the Ext4 Driver, 128KB Deadline for Internal and 4096 with Deadline for External, and Safe Mode is disabled. But decide on what you want yourself, set it, go back to the Eye to see your current info.
Step 5. Reboot.
Step 6. Wait 1-30 minutes for it to finish moving all your stuff around.
Step 7. Unlock your phone, open Mounts2SD, and make sure everything looks pretty on that first 'Eye' info tab. If you like it then close Mounts2SD and keep going on your merry way. If you don't like it or you've done something like offload your data and now your phone is wretchedly slow, go to the Wrench, change your settings, go back to the Eye, and reboot again. Repeat until satisfied.

I thought it would be simplier.
A few more questions:
1. If I partition SD on PC, then I don't need any partitioning on recovery so it should work fine even on TWRP or advanced CWMs. Am I right?
2. Why do I need scripts for? Isn't the app enough?
3. Why should/could it possibly slow down my device? TB 'move to SD' for all doesn't slow my device what so ever.
4. How and where do I see what partition is used for what?
5. How much RAM does the app take?
6. Have you tried other apps link2sd or something CM has built in I think.?
Thanks.
sent from me

New answers to new questions.
1. Skip step 1 if you've done it on your PC. I just suggested recovery as that's easy... if you've made your sd-ext partition on the PC, step 1 is done.
2. No clue on Link2SD. I use Mounts2SD instead since it lets me set things. It probably does the same thing though and sets a init.d script that gets run during startup.
3. True. For some reason though having all your data moved to sd-ext makes our phone go to a crawl. Same if you move off the dalvik.
4. That's in Mounts2SD. No clue how you can see if you're using Link2SD.
5. For Mounts2SD, none while it's being used, since it just runs as a startup script. The app is just to control the script.
6. Not successfully. I had tried 5 or 6 different apps back a year ago or so when I first started playing with sd-ext and Mounts2SD was the best and free, so... never looked back after that. Now you can also do some system-flag tweaking if you want to donate, but the sd-ext stuff is all free.

I was able to successfully partition SD and use mount2sd on 4.3 SlimBean.
however, it was rather slow.
CM 10.1 and CM10.2 by DJL. did not allow me to partition nor did they recognize SlimBean's partition even if I replaced them kernel (to NilTMT).
I'm currently using CM10.1 which is stable as a daily driver and manually swapping apps with TB, I hate it, but this is the best combination I've come so far.
I sold my wife's SGS4G and upgraded her to SGS3 and hopefully in a year I will do the same. it had its moments, but on the bottom line it's a pretty ****ty phone with its lack of internal mem...but hey, it drove so many of us to go deeper and deeper trying to understand and made us more tecnolgical and solution oriented.

Mounts2SD worked for me on CM10.1, so not sure why it failed for you. Ah well.

A few things I have found...
Yes, you can partition on Windows, but you're really asking for trouble. It's not too bad download Ubuntu or the like and you can boot off a USB stick without touching your Windows install.
The TeamAcid kernels that I know of handle ext2/3/4 file systems. All kinds of arguments as to which are better. I personally use ext4 and don't find it obviously "slow" for the way I use my phone.
That said, what the boot scripts (which are part of a flashed "kernel" for the SGS4G) actually do with a "special" partition is another story. In some cases the first stages of booting will look for special partitions and mount them in pre-configured places. For example, the second partition of the removable card might be mounted on /sd-ext/ in many CyanogenMod ROMs. Many (most?) SGS4G ROMs don't have these "special" mount rules defined.
Moving an app to SD using the "native" approach just moves the app and none of its data to the SD card. It won't for example, move 25 MB of mail from /data/data to your microSD
Moving an app to SD (or anywhere else) doesn't keep it from generating its classes in /data/dalvik-cache -- It isn't "free" to have an app on SD as far as internal storage goes, even if it doesn't write any data.
Moving an app to SD will absolutely slow down your boot time. It does it by creating a file that contains a file system that then gets read and mounted at boot time. You can watch the parade of them getting mounted using adb logcat. It can take a minute or two to mount them all. Once mounted, that double layer of file systems shouldn't slow you down too much, since it is basically a read-only kind of thing.
Scripts are required since you need to be able to "fake out" the operating system as to where things are stored for anything (except if you just use the native app to SD method). In most cases you need new partitions mounted before the Android part of the OS starts running.
Some scripts are more robust than others.
TitaniumBackup (paid version) has a way to move data to an external partition. It works like a charm for me (64 GB Sandisk UHS-1 / Class 10 microSD). It was very tweaky for me to get it to recognize the ext4 partition the first time. It can bulk-move app data to the partition. I don't know which, if any, of the other scripts move the data to an external partition.
On my phone, an ext4 file system can be significantly faster than the internal yaffs, especially for write. Alas, it usually seems to be read that is a killer for most things in an well-written app. On my phone, yaffs can be faster than ext4 for short reads. Who knows how this would play out in real-world usage.
Other things that TitaniumBackup can do that help free up internal storage, at least in the paid version, are:
Dalvik cache cleanup
Integrate system Dalvik cache into ROM
Integrate update into ROM
Convert to system app

I can confirm Link2SD works where Mount2SD fails, which is an ext3 partitioned sd-ext on AOKP. it doesn't get any simpler than that.
sent from me

[Q] C2305 insufficient disk space - to mod / root / cry?

Hi there
I've got a Sony Xperia C (C2305) and it's got a constant problem with disk space. I have installed a 32GB microSD but many of the app's insist on remaining on the 1GB partition (Device Memory) which now means app's are starting to bloat, etc. and I can't even run updates on app's like Whatsapp or Google+ because it says there's insufficient disk space for the download.
I am optimistic and hopeful that if I root / custom ROM the device I can get some life out of the phone.
When I did the Sony Unlock Bootloader check, my phone says under Service Info / Configuration "Rooting Status: Bootloader unlock allowed: No" which I think means I cannot use the Sony Developer tool to unlock the bootloader but I don't know if this also means it is a hopeless cause entirely.
I'd appreciate any insight into whether it is advisable to root / custom ROM my phone (and if it's even possible, given the above information) and whether or not this will enable me a greater deal of flexibility with installing app's on the SD card? 1GB internal is apparently not enough but if I can (with a custom ROM) move Gmail etc. to the SD card then I don't see any long-term challenges with this fix...
Thanks in advance

Brattex said:
Hi there
I've got a Sony Xperia C (C2305) and it's got a constant problem with disk space. I have installed a 32GB microSD but many of the app's insist on remaining on the 1GB partition (Device Memory) which now means app's are starting to bloat, etc. and I can't even run updates on app's like Whatsapp or Google+ because it says there's insufficient disk space for the download.
I am optimistic and hopeful that if I root / custom ROM the device I can get some life out of the phone.
When I did the Sony Unlock Bootloader check, my phone says under Service Info / Configuration "Rooting Status: Bootloader unlock allowed: No" which I think means I cannot use the Sony Developer tool to unlock the bootloader but I don't know if this also means it is a hopeless cause entirely.
I'd appreciate any insight into whether it is advisable to root / custom ROM my phone (and if it's even possible, given the above information) and whether or not this will enable me a greater deal of flexibility with installing app's on the SD card? 1GB internal is apparently not enough but if I can (with a custom ROM) move Gmail etc. to the SD card then I don't see any long-term challenges with this fix...
Thanks in advance
Click to expand...
Click to collapse
Root your device using this guide : CLICK HERE
To solve your Memory problem.
Step 1 : Root Your Device
Step 2 : Install "Link2SD" fom playstore
Step 3 : Open the app (Link2SD) and move all apps from Internal Storage to SD card and the apps that show "updated", long press on them and select "integrate update into system"
Step 4 : Select default application installation directory as SD Card using Link2SD.

iSiddharth said:
Root your device using this guide : CLICK HERE
To solve your Memory problem.
Step 1 : Root Your Device
Step 2 : Install "Link2SD" fom playstore
Step 3 : Open the app (Link2SD) and move all apps from Internal Storage to SD card and the apps that show "updated", long press on them and select "integrate update into system"
Step 4 : Select default application installation directory as SD Card using Link2SD.
Click to expand...
Click to collapse
Firstly, I hit the "thanks" button.
Secondly, I just followed this thread http://forum.xda-developers.com/showpost.php?p=59153643&postcount=171 to root and custom ROM my phone - timing was a little off because I'd have preferred to keep my original Sony ROM and run your fix. I may still need to do it now that I've done the new ROM because some app's still refuse to move to SD on their own.
The title of the app implies it creates a link, rather than moves the app - I will look into it though.
Many thanks!

Brattex said:
Firstly, I hit the "thanks" button.
Secondly, I just followed this thread http://forum.xda-developers.com/showpost.php?p=59153643&postcount=171 to root and custom ROM my phone - timing was a little off because I'd have preferred to keep my original Sony ROM and run your fix. I may still need to do it now that I've done the new ROM because some app's still refuse to move to SD on their own.
The title of the app implies it creates a link, rather than moves the app - I will look into it though.
Many thanks!
Click to expand...
Click to collapse
The same of app sounds like linking but I use this app and many other people also use this app. It moves any App permanently from your desired location to your desired location.

Just flash this by cwm and your internal memory would become 2gb.
LINK: https://drive.google.com/file/d/0BzJt7pK7xZYzMnJyeWxiTHJvcWM/view?usp=sharing&pli=1

iSiddharth said:
Root your device using this guide : CLICK HERE
To solve your Memory problem.
Step 1 : Root Your Device
Step 2 : Install "Link2SD" fom playstore
Step 3 : Open the app (Link2SD) and move all apps from Internal Storage to SD card and the apps that show "updated", long press on them and select "integrate update into system"
Step 4 : Select default application installation directory as SD Card using Link2SD.
Click to expand...
Click to collapse
Hi again - sorry for the late response; moved home and had no internet access for ages!!
I find Link2SD cannot move all apps from Internal Storage to SD card... for example:
Google+ tries to move for a while, then it says:
"Failure
pkg: /data/app/
com.google.android.apps.plus-1.apk
Failure
[INSTALL_FAILED_INVALID_INSTALL_LOCATION]"
I find there are several apps (mostly Google apps) that seem to not be able to move to SD Card?
Another example is with Gmail:
If I hit "Link to SD card" it says
Second partition not found
/dev/block/: device not found
Make sure you have two partitions on your SD card and both are primary.
I'm guessing that means I need to partition my SD card but I'm not sure how I should do that for Android (or can I do something silly like use Windows DIsk Management for this) ?
Is it true that some applications just won't allow you to move them to SD card? I find the limited device memory on the Xperia C crippling. I keep running out of memory and can't even install a 16k app and I hardly have anything on there - the major app's like Gmail and Inbox are using up a large chunk of space.

Rsameer said:
Just flash this by cwm and your internal memory would become 2gb.
Click to expand...
Click to collapse
Thanks, that sounds like a dream - but forgive me, how is it possible that the internal memory will become 2gb with this flash? You're a junior poster so how can I be sure this is safe to use? Can anyone vouch for this?
I've done some google hunting and it seems legit. but I would just like to be sure

Brattex said:
Hi again - sorry for the late response; moved home and had no internet access for ages!!
I find Link2SD cannot move all apps from Internal Storage to SD card... for example:
Google+ tries to move for a while, then it says:
"Failure
pkg: /data/app/
com.google.android.apps.plus-1.apk
Failure
[INSTALL_FAILED_INVALID_INSTALL_LOCATION]"
I find there are several apps (mostly Google apps) that seem to not be able to move to SD Card?
Another example is with Gmail:
If I hit "Link to SD card" it says
Second partition not found
/dev/block/: device not found
Make sure you have two partitions on your SD card and both are primary.
I'm guessing that means I need to partition my SD card but I'm not sure how I should do that for Android (or can I do something silly like use Windows DIsk Management for this) ?
Is it true that some applications just won't allow you to move them to SD card? I find the limited device memory on the Xperia C crippling. I keep running out of memory and can't even install a 16k app and I hardly have anything on there - the major app's like Gmail and Inbox are using up a large chunk of space.
Click to expand...
Click to collapse
Actually, I may have answered my own question by fiddling a bit with Link2SD - there's an option to convert an app (e.g. Google+) to a user app. I am still learning Android but it seems AFAIK that a system app is read-only and in /system/app and that's why it cannot be moved.
So by first following your original advice (@iSiddharth) and selecting the option "Integrate update into system", I think I am now removing the rollback feature of a system app (i.e. it is now a single app instead of a system app plus a separate update). Next, if I convert it to a user app, I can then - after a device reboot - move the app to the SD card (since it is now considered a user app instead of a system app).
At least, I hope my understanding is more or less correct and I'm not messing up my apps!!! I'm leaving all mission critical apps that are in /system where they are in case removing read-only for them could run me into trouble later.
And if I follow this for all of the apps that I need to, I can free up internal memory - AND if that patch / flash from @Rsameer
is legit, I can also get more local memory (+1GB).

maybe this will help you
http://www.informationlord.com/increase-apps-storage-space-of-xperia-c/

Brattex said:
Thanks, that sounds like a dream - but forgive me, how is it possible that the internal memory will become 2gb with this flash? You're a junior poster so how can I be sure this is safe to use? Can anyone vouch for this?
I've done some google hunting and it seems legit. but I would just like to be sure
Click to expand...
Click to collapse
Bro it's safe. Don't worry. I do not post something that I haven't tried myself. And here's a screenshot from my xc.
And also anyone whose posts are gr8r than 100 becomes senior member. I don't use xda quite often and post few messages.

Magdy Yassen said:
maybe this will help you
http://www.informationlord.com/increase-apps-storage-space-of-xperia-c/
Click to expand...
Click to collapse
Bro informationLord requires surveys nowadays. I am not sure but I think we can't post links with surveys on this site.

Rsameer said:
Bro informationLord requires surveys nowadays. I am not sure but I think we can't post links with surveys on this site.
Click to expand...
Click to collapse
I'm trying to help :-/

Flashed but now can't restore
Magdy Yassen said:
I'm trying to help :-/
Click to expand...
Click to collapse
Rsameer said:
Just flash this by cwm and your internal memory would become 2gb.
LINK: https://drive.google.com/file/d/0BzJt7pK7xZYzMnJyeWxiTHJvcWM/view?usp=sharing&pli=1
Click to expand...
Click to collapse
Magdy Yassen said:
maybe this will help you
http://www.informationlord.com/increase-apps-storage-space-of-xperia-c/
Click to expand...
Click to collapse
Hey guys!
Once again sorry for late reply; just had a baby addition into our new home so I've been kinda busy
@Rsameer @Magdy Yassen I have followed the steps and flashed it but now the new ROM hasn't got Google Account Manager, Settings UI, or CWM any more so I can't figure out how to restore my backup? I'm sitting with the new image but I am stuck?
The steps say
"Once Xperia C starts, then simply turn off the phone and again boot into recovery and restore the backup you created earlier using CWM. By this you will restore all the data you had earlier."
but how do I boot into recovery now?

Brattex said:
Hey guys!
Once again sorry for late reply; just had a baby addition into our new home so I've been kinda busy
@Rsameer @Magdy Yassen I have followed the steps and flashed it but now the new ROM hasn't got Google Account Manager, Settings UI, or CWM any more so I can't figure out how to restore my backup? I'm sitting with the new image but I am stuck?
The steps say
"Once Xperia C starts, then simply turn off the phone and again boot into recovery and restore the backup you created earlier using CWM. By this you will restore all the data you had earlier."
but how do I boot into recovery now?
Click to expand...
Click to collapse
Alright, I've worked it out - perhaps a little too hasty in my reply ... the instructions I had said press power and UP button but that wasn't working. I eventually decided to try Power and DOWN button and it worked! I've restored my backup and I am back in business!
Thanks guys - I have successfully merged /sdcard1 and /data together

theres a method
Brattex said:
Hi there
I've got a Sony Xperia C (C2305) and it's got a constant problem with disk space. I have installed a 32GB microSD but many of the app's insist on remaining on the 1GB partition (Device Memory) which now means app's are starting to bloat, etc. and I can't even run updates on app's like Whatsapp or Google+ because it says there's insufficient disk space for the download.
I am optimistic and hopeful that if I root / custom ROM the device I can get some life out of the phone.
When I did the Sony Unlock Bootloader check, my phone says under Service Info / Configuration "Rooting Status: Bootloader unlock allowed: No" which I think means I cannot use the Sony Developer tool to unlock the bootloader but I don't know if this also means it is a hopeless cause entirely.
I'd appreciate any insight into whether it is advisable to root / custom ROM my phone (and if it's even possible, given the above information) and whether or not this will enable me a greater deal of flexibility with installing app's on the SD card? 1GB internal is apparently not enough but if I can (with a custom ROM) move Gmail etc. to the SD card then I don't see any long-term challenges with this fix...
Thanks in advance
Click to expand...
Click to collapse
theres a method to increase internal mem of xc
google Increase Internal mem XC