Database Users

[GUIDE] External2Internal Ultimate

I thought about this idea more than a month ago when i came to know that the partitions could freely be altered, but i could not put into practice until i got my 32 gb card yesterday.
so basically, after following my guide you will have:
* supersized data partition (12 gigs): no more move to sd needed unless for huge games (i'm thinking fifa12 and asphalt7) and then again the stock move to sd feature will work as expected (it will move data to the actual external sd card)
* external sd card mounted as internal sd card: nothing to say here, just does what is expected
* real internal sd (ums partition) shrinked to minimum (half gig) because it needs to stay present: used to mount a swap file (optional)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What you will need:
* g.lewarne hydracore 4.3b kernel: you don't need it for anything special, but it's the most amazing kernel, and gavin is the most devoted developer ive seen on the n7000. cheers gavin and keep up the good work :good:
* swapper2: if you want to use the swap file (see at the end)
so be warned, i'm no real specialist here, so i'm not aware of the no dos, i just got my guide to work through trial and error and getting information from other threads.
so if you follow my guide you're almost good, if not you may cause an atomic bomb to fall over your city, not my problem :silly:
enough chit chat for now let's head directly for the guide:
1. reboot to recovery, and connect your phone to your pc
2. run a command prompt and type the following (wait a little bit until the adb server starts on the phone, you can verify it by typing "adb devices" if you get a serie of digits then you're good to go.
Code:
adb shell
parted /dev/block/mmcblock0
you'll get into the parted interactive shell, this is where serious work done
Code:
did i remind you to backup your system,
this is your last stop before the no back point
so you just might wanna "move" all your internal sd stuff to the external sd,
and backup your system to the external sd also
(you just need to restore the data partition afterwards the rest of the system is safe but who knows :p)
ps: you can do your backup on cwm without leaving adb shell on the pc just like you will do the format later thanks to cwm
remove the partitions
Code:
rm 10
rm 11
make the new changed size partitions
Code:
unit b
mkpart primary 1174405120 14680064511
mkpart primary 14680064512 15216934911
name 10 DATAFS
name 11 UMS
now in cwm go to mounts and storage and select "format /emmc" and "format /data"
in parted type "print" and you should see this output
Code:
Number Start End Size File system Name Flags
1 4194304B 25165823B 20971520B ext4 EFS
2 25165824B 26476543B 1310720B SBL1
3 27262976B 28573695B 1310720B SBL2
4 29360128B 37748735B 8388608B PARAM
5 37748736B 46137343B 8388608B KERNEL
6 46137344B 54525951B 8388608B RECOVERY
7 54525952B 264241151B 209715200B ext4 CACHE
8 264241152B 281018367B 16777216B MODEM
9 281018368B 1174405119B 893386752B ext4 FACTORYFS
10 1174405120B 14680064511B 13505659392B ext4 DATAFS
11 14680064512B 15216934911B 536870400B fat32 UMS
12 15216934912B 15753805823B 536870912B ext4 HIDDEN
now the hardest part is over, restore your data partition and you will be able to boot you system normally. and you go to your storage information you will find that your app storage is now 13gigs and the usb storage is just 500 megs yay
to switch the sd with the internal you will have to modify vold.fstab file(thanks to ciphray for his guide on how to do so)
you can use the modified file from ciphray thread here which i didn't beacuse his file was smaller
so i just pulled the file to my pc
Code:
adb pull /etc/vold.fstab vold.fstab
modified it with notepad++ or any dev text editor (don't use windows notepad it will mess the file)
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
and push it back to phone + change permissions
Code:
adb push vold.fstab /etc/vold.fstab
chmod 644 /etc/vold.fstab
restart your phone and voila
as a final step you can use the now pretty useless internal space (500megs remember) as a swap sapce
download swapper2 from the play store here https://play.google.com/store/apps/details?id=lv.n3o.swapper2
run it and go to settings
set swap place as /sdcard/external_sd/swapfile.swp
set swap size to the max
set the swappiness to 20 ( you can rise the value a little but don't put a high value or the system will do much swapping all the time -value of 100 means any memory not used actively will be swapped- )
wait until the process finishes then reboot your phone
you can verify that swap is working by typing "free" in the shell if the line beginning with swap is not all zeros then you're swap is working.
hope my guide will be usefull, and don't hesitate to ask me any question

Awesome, thanks! Will try it out when I get some time

If you want more app space you can erase the hidden partition and get more space.
Sent from my GT-N7000 using Tapatalk 2

Okay, I've performed the whole thing, and just a few remarks on my experience
If you want to modify the vold.fstab straight from recovery without having to reboot first, you can simply mount the system partition, and retrieve the file from /system/etc/vold.fstab instead of /etc/fstab
More importantly, following your instructions, I ended up in a situation where my apps previously moved to the sd card weren't recognized. I've solved this by modifying my vold.fstab as follows:
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
That way, all my apps were properly recognized without issues. I'll probably be moving them back to phone now though.
Will be trying this setup over the next few days and see how it performs, but one caveat I missed is that you may not be able to install the whole of some apps on the data partition, as some the data will always be stored in the sdcard/Android folder, which would make the 12GB on /data less useful than I initially thought, unless I'm missing something of course

Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!

zongamin said:
Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!
Click to expand...
Click to collapse
here you are, look at the OP
i didn't realize the screenshot like was corrupt
if you read the op i mentioned the resulting sizes after the mod
sd storage will be mentioned as 500 megs (actually taken from the internal emmc) that i use for swap space

Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2

As far as I know, the HydraCore kernel doesn't allow swap, so it's unuseful to setup a swap file with swapper. Also, presently no Note kernel has swap enabled.
Carefully crafted on my Galaxy Note, for your eyes only

Hydracore 4.1 since has swap enabled in its kernel.
Sent from my GT-N7000 using Tapatalk 2

I'm sorry, I didn't know Gavin had listened to what I had asked oh so many times
Carefully crafted on my Galaxy Note, for your eyes only

travis82 said:
Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
i was fearing that the phone won't boot if the partition isn't available after a clean setup.
so i decided to leave the small size partition and make it useful for swap instead.
btw does anyone know how to use a bigger swap file with swapper2?

I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth

antique_sonic said:
I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth
Click to expand...
Click to collapse
just type print on the parted shell
and then you can recalculate new sizes for the data partitions, it should work like a charm

So... Im a USER, and there are part I am a bit confused about... BUT ill ask anyway!
It seems that if I wanted to resetup the partitions, I wouldnt need to mess with the pit files correct?
OR, because I want to totally KILL USB Storage, dedicate the entire internal memory to /data, and make /sdcard TRULY my sdcard, would I truly need to mess with the pit file?
Has anyone tried with killing off /ums completely?
Any help is appreciated. Also, I am using the i717 (AT&T GNote version), but my desire is the same so I figured Id post here...
EDIT: im not too worried about rom flashing, I normally slim down ROM's before I flash them, so Im not afraid of changes that have to be made (in txt files) in order to have them work properly on a UMS'less modded device. However, I do need to find out how to properly backup the pit file before I even THINK Of messing with it.

do i have to redo the whole procedure if i flashing nightly every time?

Anyone tried this on JB roms?

Hello?
Sent from my GT-N7000 using Tapatalk 2

jaguaralani said:
Anyone tried this on JB roms?
Click to expand...
Click to collapse
+1
I get 64 gb sandisk microsd card. I want to use this mod on jb stock LSC rom.
Can we use on jb roms?
GT-N7000 cihazımdan Tapatalk 2 ile gönderildi

Helpppppp
Envoyé depuis mon GT-N7000 avec Tapatalk

JB ready
I've tried it worked fine on Ultimate and Alliance ROM. Just edit vold.fstab in /etc after install new ROM. Replace 11 to auto and { } to { }. Now I need help if anyone have the original partition info, incase I wanted to restore.

TWRP 2.6.3.0 unable to mount esternal SDcard

[SOLVED: See last post]​
Hi everybody !
That's aLL... I just flashed a SBF, performed a factory reset from motorola's recovery, rooted my phone, installed 2ndinit 2.3, flashed TWRP 2.6.3.0 and then Quark's 2014 01 20 CM11 build.
Did I miss some step in order to get the card mounted in recovery ?
By the way I can easily access it plugging the USB cable on my Ubuntu Linux desktop and choosing MTP/PTP/USBstorage.
EDIT: it was previously formatted ( it's a 32GB class 10 U1 card ) as a fat32 partition on Windows7

Alka-Seltzer PLUS said:
Hi everybody !
That's aLL... I just flashed a SBF, performed a factory reset from motorola's recovery, rooted my phone, installed 2ndinit 2.3, flashed TWRP 2.6.3.0 and then Quark's 2014 01 20 CM11 build.
Did I miss some step in order to get the card mounted in recovery ?
By the way I can easily access it plugging the USB cable on my Ubuntu Linux desktop and choosing MTP/PTP/USBstorage.
EDIT: it was previously formatted ( it's a 32GB class 10 U1 card ) as a fat32 partition on Windows7
Click to expand...
Click to collapse
Your SDcard is visible from file manager?
If not than is better to format it in a ... compact camera or something like this.!

pgreed said:
Your SDcard is visible from file manager?
If not than is better to format it in a ... compact camera or something like this.!
Click to expand...
Click to collapse
Thanks for your answer !
Yes it is; I can mount it on my desktop too as I previously said.
This happened to me 2 times after having installed Quarx's CM11 with the steps described before
Plugging it on my desktop results in a mounted partition on the file explorer ( nautilus ) but as an unmounted on the partitioning app ( Gparted ) with a broken filesystem but I am able to copy files

Bump!

Alka-Seltzer PLUS said:
Bump!
Click to expand...
Click to collapse
As I said before something similar happened to me and the only solution was to re-format entire SDcard in a compact camera. I tried to format in a android tablet and in the phone but always it gave errors. After formatted in camera all work fine and no error.

pgreed said:
As I said before something similar happened to me and the only solution was to re-format entire SDcard in a compact camera. I tried to format in a android tablet and in the phone but always it gave errors. After formatted in camera all work fine and no error.
Click to expand...
Click to collapse
I should try but ... uhm ... my question is: why does the same card mount ever on every recovery ( TWRP 2.6.3.0 included ) but not any more after 2014 01 20 build ?
If I would restart from scratch without doing anything on the card( flashing a SBF, root, 2ndinit, TWRP 2.6.3.0, CM11 ) it should be mounted until the first CM11's boot: I did it 2 days ago. I just used the same card without formatting it: TWRP 2.6.3.0 does mount it only on the first shoot.
After the first CM11's boot it won't be mounted anymore.
sudo fdisk -l
Code:
Disk /dev/sdc: 32.1 GB, 32090619904 bytes
64 testine, 32 settori/tracce, 30604 cilindri, totale 62676992 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x70707573
Questa non sembra una tabella delle partizioni.
Probabilmente è stato scelto il dispositivo sbagliato.
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 ? 1701998450 3638285201 968143376 d Sconosciuto
/dev/sdc2 ? 1701995885 2246105740 272054928 a OS/2 Boot Manager
/dev/sdc3 ? 1769087090 3538458322 884685616+ 6f Sconosciuto
/dev/sdc4 ? 2885681152 2885734849 26849 a OS/2 Boot Manager
dmesg|tail
Code:
[16595.451780] sd 7:0:0:0: Attached scsi generic sg3 type 0
[16595.451862] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.451871] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.466630] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.466647] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.469344] sdc:
[16595.472449] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.472461] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.472471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[16595.775667] FAT-fs (sdc): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oh LoL: it mounts flawlessy and really on the fly and I can manage aLL files!
sudo dosfsck -w -r -l -a -v -t /dev/sdc
Code:
dosfsck 3.0.16 (01 Mar 2013)
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
Checking we can access the last sector of the filesystem
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
65536 bytes per cluster
540 reserved sectors
First FAT starts at byte 276480 (sector 540)
2 FATs, 32 bit entries
1958912 bytes per FAT (= 3826 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
489600 data clusters (32086425600 bytes)
63 sectors/track, 255 heads
0 hidden sectors
62676992 sectors total
...
...
...
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/sdc: 3703 files, 238236/489600 clusters
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Click to expand...
Click to collapse
uhm ... I'm just writing zeros to the entire drive:
Code:
sudo dd if=/dev/zero of=/dev/sdc
Let's see if it helps

SOLVED​
Okka roLLa !
So... trying to reformat the card via CM11 results in a random reboot; trying to wipe it on TWRP fails too.
I wrote zeros another 2 times in between and than i putted it into the defy, mounted it as USB Mass Storage in order to partition it with GParted creating 2 primary partitions ( 1024GB ext3 and aLL the other avaiable space FAT32 ) and now it is seen from recovery without mounting it :good:

I have the same problem: after installing any of the recent CM11 nightlies (since the autobot builds began), TWRP is unable to mount my sdcard. (It's a 16GB class 10 made by Topram.) I've tried fully formatting the card in my PC (as FAT32), also checked it for errors and bad sectors. So far as I can tell, there's nothing wrong with the card.
Earlier versions of CM11 (from pre-autobot builds, like the December 29th build) have no trouble mounting the card in recovery, and the latest builds of CM11 have no trouble reading from and writing to the card when the rom is fully booted; only TWRP is unable to mount it. Strangely, TWRP has no trouble mounting an older and slower 2GB card.
@Alka-Seltzer PLUS, I'd rather not use the workaround that you described above, because the last time I tried screwing around in TWRP trying to get it to mount the sdcard, I ended up hard-bricking my old defy.
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.

Proverbs2 said:
I have the same problem: after installing any of the recent CM11 nightlies (since the autobot builds began), TWRP is unable to mount my sdcard. (It's a 16GB class 10 made by Topram.) I've tried fully formatting the card in my PC (as FAT32), also checked it for errors and bad sectors. So far as I can tell, there's nothing wrong with the card.
Earlier versions of CM11 (from pre-autobot builds, like the December 29th build) have no trouble mounting the card in recovery, and the latest builds of CM11 have no trouble reading from and writing to the card when the rom is fully booted; only TWRP is unable to mount it. Strangely, TWRP has no trouble mounting an older and slower 2GB card.
@Alka-Seltzer PLUS, I'd rather not use the workaround that you described above, because the last time I tried screwing around in TWRP trying to get it to mount the sdcard, I ended up hard-bricking my old defy.
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.
Click to expand...
Click to collapse
Maybe there's a misunderstandig: the steps i described have been done with the microSD outside the phone; I did it with the card inserted in an adapter !

Alka-Seltzer PLUS said:
Maybe there's a misunderstandig: the steps i described have been done with the microSD outside the phone; I did it with the card inserted in an adapter !
Click to expand...
Click to collapse
Thanks for the reply. I'm still not sure that I understand your steps. Did you use gparted on your linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then put the sdcard back into the phone and now TWRP recognizes it? If so, which partition does TWRP recognize, the ext3 or the FAT32?
In any case, I'd rather not resort to such a workaround, since I don't trust the latest version of the TWRP recovery (which hard-bricked my old defy). I would prefer to downgrade the recovery to the version that was working fine on the earlier CM11 builds (e.g. the December 29th build). Does anyone know how to do that?
Thanks in advance!

That's right: I did use gparted on my linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then putted the sdcard back into the phone and now TWRP does recognize it.
The FAT32 is recognized, the ext3 i do not know because i did not look for it yet ^_^

Alka-Seltzer PLUS said:
That's right: I did use gparted on my linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then putted the sdcard back into the phone and now TWRP does recognize it.
The FAT32 is recognized, the ext3 i do not know because i did not look for it yet ^_^
Click to expand...
Click to collapse
Wow, that actually worked! I just used gparted to fix the partition table and reformat the entire sdcard as FAT32 (I only created one partition), and now the card is recognized in TWRP! :good:
Apparently there was something wrong with the partition tables on my sdcard, and even a full format in Windows 7 didn't fix it, nor did the Windows disk check utility detect the problem, but Linux saves the day again!

Alka-Seltzer PLUS said:
I should try but ... uhm ... my question is: why does the same card mount ever on every recovery ( TWRP 2.6.3.0 included ) but not any more after 2014 01 20 build ?
If I would restart from scratch without doing anything on the card( flashing a SBF, root, 2ndinit, TWRP 2.6.3.0, CM11 ) it should be mounted until the first CM11's boot: I did it 2 days ago. I just used the same card without formatting it: TWRP 2.6.3.0 does mount it only on the first shoot.
After the first CM11's boot it won't be mounted anymore.
sudo fdisk -l
Code:
Disk /dev/sdc: 32.1 GB, 32090619904 bytes
64 testine, 32 settori/tracce, 30604 cilindri, totale 62676992 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x70707573
Questa non sembra una tabella delle partizioni.
Probabilmente è stato scelto il dispositivo sbagliato.
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 ? 1701998450 3638285201 968143376 d Sconosciuto
/dev/sdc2 ? 1701995885 2246105740 272054928 a OS/2 Boot Manager
/dev/sdc3 ? 1769087090 3538458322 884685616+ 6f Sconosciuto
/dev/sdc4 ? 2885681152 2885734849 26849 a OS/2 Boot Manager
dmesg|tail
Code:
[16595.451780] sd 7:0:0:0: Attached scsi generic sg3 type 0
[16595.451862] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.451871] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.466630] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.466647] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.469344] sdc:
[16595.472449] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.472461] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.472471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[16595.775667] FAT-fs (sdc): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oh LoL: it mounts flawlessy and really on the fly and I can manage aLL files!
sudo dosfsck -w -r -l -a -v -t /dev/sdc
Code:
dosfsck 3.0.16 (01 Mar 2013)
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
Checking we can access the last sector of the filesystem
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
65536 bytes per cluster
540 reserved sectors
First FAT starts at byte 276480 (sector 540)
2 FATs, 32 bit entries
1958912 bytes per FAT (= 3826 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
489600 data clusters (32086425600 bytes)
63 sectors/track, 255 heads
0 hidden sectors
62676992 sectors total
...
...
...
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/sdc: 3703 files, 238236/489600 clusters
uhm ... I'm just writing zeros to the entire drive:
Code:
sudo dd if=/dev/zero of=/dev/sdc
Let's see if it helps
Click to expand...
Click to collapse
I think the problem here is that there is no partition table on your card, just a file system; you put a file system directly on the sd card, rather than creating a single partition spanning all of the card. Your file system would end up on /dev/block/mmcblk0 rather than /dev/block/mmcblk0p1, and twrp.fstab doesn't include an entry for that, so it doesn't get mounted.
This might be easy to fix, but testing the fix might also hard-brick the phone in question, as Proverbs2 discovered. It doesn't seem to be a hardware issue, and the overwhelming standard is for SD cards to have a partition table, so we're probably best off warning about such cards and not touching them at all. Whatever software you used to format your SD card initially needs to be fixed, though.

Proverbs2 said:
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.
Click to expand...
Click to collapse
I think there was a recent change to use separate kernels for recovery and normal 2nd-boot. You'd need to replace /system/bootmenu/2nd-boot/ramdisk-recovery with the old /system/bootmenu/2nd-boot/ramdisk-recovery and /system/bootmenu/2nd-boot/zImage-recovery with the old /system/bootmenu/2nd-boot/zImage (no "-recovery" suffix), I think, and I'd expect it to just work then. Don't touch the new /system/bootmenu/2nd-boot/ramdisk and /system/bootmenu/2nd-boot/zImage.

[PROBLEM SOLVED Time ago]
PhilipCetero said:
I think the problem here is that there is no partition table on your card, just a file system; you put a file system directly on the sd card, rather than creating a single partition spanning all of the card. Your file system would end up on /dev/block/mmcblk0 rather than /dev/block/mmcblk0p1, and twrp.fstab doesn't include an entry for that, so it doesn't get mounted.
This might be easy to fix, but testing the fix might also hard-brick the phone in question, as Proverbs2 discovered. It doesn't seem to be a hardware issue, and the overwhelming standard is for SD cards to have a partition table, so we're probably best off warning about such cards and not touching them at all. Whatever software you used to format your SD card initially needs to be fixed, though.
Click to expand...
Click to collapse
Alka-Seltzer PLUS said:
SOLVED​
Okka roLLa !
So... trying to reformat the card via CM11 results in a random reboot; trying to wipe it on TWRP fails too.
I wrote zeros another 2 times in between and than i putted it into the defy, mounted it as USB Mass Storage in order to partition it with GParted creating 2 primary partitions ( 1024GB ext3 and aLL the other avaiable space FAT32 ) and now it is seen from recovery without mounting it :good:
Click to expand...
Click to collapse
Thanks for your answer but I do not realize what was wrong doing it my way ( now the card gets mounted ) !
After having write zeros on the card i tried to partition it in 3 different ways:
1) Booting up CM11 and letting it ask to format the empty card ( I thought it was supposed to create a partition table with a FAT32 partition spanning all the space on the microSD ) but it always resulted in a random reboot and a not partitioned card.
2) Entering TWRP and letting it partition the SDcard using its menu: it returns that the recovery tries to mount any partition which is supposed to be created from an empty card Maybe the card should have had at least a partition table in order to be partitioned ? This question let go to this another one: isn't TWRP able to write a partition table on an empty microSD ?
3) My way: using Gparted whom prompts a window which says to create a partition table before partitioning the device.

Alka-Seltzer PLUS said:
Thanks for your answer but I do not realize what was wrong doing it my way ( now the card gets mounted ) !
Click to expand...
Click to collapse
There's nothing wrong with your way! I just thought an explanation of what went wrong would be helpful. To actually fix it, gparted is what I would use, too; and now you've used it everything should work flawlessly
Sorry for the confusion: I was talking about fixing TWRP to recognize such cards (which it should) and working with them (which it shouldn't, because of the risk it's a broken card and we end up Proverbsing the phone).

is there any new solution?
or can i mount(in twrp) /dev/block/mmcblk0 sdcard
and install my new rom and do away

[MOD][EMMC][I9070/P][8/16GB] Internal Memory Repartition

Internal Memory Repartition
Hey guys, after a very long time I show you the way to repartition your internal memory (EMMC).
You can modify partitions as you want, increase data partition to install more apps, increase internal storage for media files...
It's based on a little Linux binary called Parted, it's a part of CWM/TWRP recovery ramdisk.
This means that you can repartition in any recovery of any 4.2/4.3/4.4 ROM.
==========WARNING==========
Operations on EMMC partitions could be EXTREMELY DANGEROUS if you don't understand well what you do.
If you touch wrong partitions (CSPSA, EFS, SBLs...) you can lose your IMEI or hardbrick your device (in this case only JTAG can save you) so...
READ CAREFULLY!!!!!
Responsibility is all yours, but if you follow well this guide you will not risk anything.
Stock partition table is designed to be used in stock ROM, since it uses preload partition to store some system apps and needs bigger system (ROM is heavier than CM-based ones) and bigger cache partitions (more system apps=more dalvik-cache).
This mod is compatible with any ROM except stock and stock-based.
This is the stock partition table:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can touch ONLY:
Kernel2
SYSTEM
DATAFS
CACHEFS
HIDDEN
FOTA
UMS
Kernel2 is the backup of stock kernel, we don't need it.
SYSTEM is the /system partition (where the ROM is installed/stored).
DATAFS is /data partition (default 1.97 GB where are stored installed apps, Android settings, contacts, messages... User data).
CACHEFS is /cache partition (art/dalvik-cache is stored here, together with recovery logs/temporary files. In stock ROM here is stored also CSC. If you repartition to the minimum (at least 5 MB needed for recovery) you need to put dalvik.vm.dexopt.data-only=1 flag in system/build.prop
HIDDEN is /preload partition (some Samsung TouchWiz system apps are stored here and symlinked with /system/app. This is a swap partition on MIUI v5, CM10.2 and all CM11/Omni 4.4 builds (these 4.4 before 15 June), also every custom ROM based on Canjica device tree 4.3/4.4 (always before 15 June), resize it to the minimum (128 KB to format it as EXT2).
FOTA is Firmware Over The Air, so is needed to get OTA updates while on stock ROM, can be directly deleted.
UMS is the internal storage (3.96 GB one), you can repartition this to have less/more space, or repartition to the minimum (8 MB or less, you will need to swap internal/external storages).
Parted commands useful for us:
rm (to delete a partition)
mkpart primary (to make a partition)
format (to format a partition, only in ext2)
name (to rename a partition)
For an extended list/explanation of commands, type "help" without quotes
Let's go!
First make a nandroid backup of your current ROM, to be restored after repartition
If you touch UMS you will lose all the content of /sdcard (internal storage), so make a backup first!
You need a Linux distro or Windows with ADB configured.
Reboot device in recovery and connect to USB, then open ADB and write:
Code:
adb shell
parted /dev/block/mmcblk0
You can choose to display partitions as Gigabytes, Megabytes, Kilobytes (suggested), or Bytes by "unit **" command, where ** can be gb/mb/kb or b
Now type "print" to display partition table.
Parted create new partitions by following "Number", for example SYSTEM is 3, CACHEFS is 4 and DATAFS is 5 (for other partitions is the same), so when you create new partitions, you need to make them in order!! For example:
SYSTEM is 3 and its size is from 105906KB to 747635KB
CACHEFS is 4 and its size is from 2895118KB to 3215983KB
DATAFS is 5 and its size is from 747635KB to 2895118KB
The "end" of a partition is the "start" of the next partition
As you can see, DATAFS is between SYSTEM and CACHEFS. This means that after you create SYSTEM, you need to calculate new DATAFS size that you want and then first create CACHEFS (at the end of calculated DATAFS size) then create DATAFS from the end of SYSTEM to the start of CACHEFS.
To understand more:
We will resize now CACHEFS from 320864 KB to 5000 KB gaining 315864 KB for DATAFS:
Unmount /cache from recovery first!
Code:
rm 4 (to delete CACHEFS)
rm 5 (to delete DATAFS)
calculate now the new size of DATAFS, in this case add 315864 KB to DATAFS end: 2895118+315864=3210982 KB
calculate now the new end of CACHEFS, in this case add 5000 KB to 3210982 KB: 3210982+5000=3260982 KB
mkpart primary 3210982 (end of DATAFS and start of CACHEFS) 3260982 (end of CACHEFS, start of the next partition)
Now we made a new partition, its number is 4. Do: name 4 CACHEFS
It's time to make new DATAFS partition: from the end of SYSTEM to the start of CACHEFS
mkpart primary 747635 (end of SYSTEM and start of DATAFS) 3210982 (end of DATAFS and start of CACHEFS)
New partition has number 5, name it DATAFS by name 5 DATAFS
Basically the method is this, you can apply it to partitions listed above.
Remember to reboot recovery, go in Mounts and storage then (depending on what partitions you touched in Parted, excluding /preload) do the appropriate formats after repartition. Now you're ready to restore your nandroid backup (needs to have less size than new partitions) or install a ROM.
I suggest an useful program to check partition size on Android, Partition Table
If you touch HIDDEN partition and you are on 4.2 ROM or 4.4 builds after 15 June:
Code:
format
y
9
ext2
If you repartition UMS to the minimum, you will need to swap internal and external storages (MicroSD card will be the new internal storage):
On 4.2 open system/etc/vold.fstab and replace the content with this:
Code:
# MicroSD as internal storage
dev_mount sdcard0 /storage/sdcard0 auto /devices/sdi0/mmc_host/mmc1/mmc1
# UMS as external storage
dev_mount sdcard1 /storage/sdcard1 8 /devices/sdi2/mmc_host/mmc0/mmc0 nonremovable,encryptable
# usbdisk
dev_mount usbdisk0 /storage/usbdisk0 auto /devices/platform/msm_hsusb_host.0
On 4.3 ROMs open system/build.prop and add these lines at the end of the file:
Code:
persist.sys.vold.switchexternal=1
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
On 4.4 ROMs just open NovaThor Settings and enable "Swap Storages"
To restore original partition table flash stock ROM through Odin with "Repartition" enabled and correct PIT file for your model, in attachment (extract zip), soon CHN pits too
I know that it's difficult to understand well the first times, but think at me that I developed this method, a lot of testing and bricks on bricks
If you found this useful, you can support me at least by pressing "Thanks" or considering to offer me a beer, a coffee... Any kind of support will be very appreciated ​

Reserved for "The PIT Zone" (soon available!)

Reserved

Another reserved just in case!!

So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos

tasosf said:
So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos
Click to expand...
Click to collapse
All what you should know it's wrote in the OP.
You can make our way... rm anything after Kernel2, calculate datafs+1024MB more and make again all partitions, name and format them. Read again and well the OP for clarifications, it's all wrote there
Inviato dal mio GT-I9505

I didnt found any info about it in OP so i ask:
Every partition made using this guide will be formatted as ext2? Ext2 is worse than ext4 so probably it will affect performance, am i right about it?

Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later

ch3mn3y said:
Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later
Click to expand...
Click to collapse
Format didn't work for me either. I formatted everything through TWRP to ext4.
So, this method works! I now have 3GB for data so to have all the apps installed in the internal storage and not the internal sd card (ums). This way all apps are faster because ums is formatted as fat 32 in order to be recognised on Windows.
One tricky thing was that you have to mkpart from low numbers to high, regardless if you leave for a moment organ intermediate megabytes. The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Sent from my GT-I9070 using XDA Free mobile app

I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
tasosf said:
The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Click to expand...
Click to collapse
Yep, its important to not make mistakes, coz who wants to do something few times?

ch3mn3y said:
I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
Click to expand...
Click to collapse
How come you want to have bigger UMS? Not all apps can be installed there and DATAFS gets full very easily. Also, it's fat32 which creates some problems by itself.
Sent from my GT-I9070 using XDA Free mobile app

I just dont use this phone as my primary and as i have xplay for games i dont need to have lots of apps on it. Additionaly i have only 4gb sdcard for it, so my internal memory is now bigger than external
Sent using TF300T - CyanogenMod 11.0/GRIMLOCK (F2FS)

i'd really like to repartition my phone's memory but i fear i'm gonna screw everything up
i see a coming soon "pit zone" in the second post, does that mean that there is an automatic way to repartition the internal memory without directly using commands?

If u knows how to make pit file after repartitioning its probably possible to use odin to repartition
Sent using GT-i9070 - VanirAOSP

You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505

AntaresOne said:
You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps

TheSteve87 said:
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps
Click to expand...
Click to collapse
Completely agree mate. Also HIDDEN, you don't need it on CM/CM-based custom ROMs
Inviato dal mio GT-I9505

I really have to say this guide is just A-W-E-S-O-M-E
The process is not that easy but very well explained

A complicated by well explained method for partition........But i am a bit afraid to use .... Can u help out with the step for my issue...?
My Phone: S Advance
(Rooted with the help of http://forum.xda-developers.com/showthread.php?t=2087424)
RAM= 768 MB RAM,
ROM= 2 GB //*Note phone shows this as device storage, Pl correct if I am wrong*//
Internal=16 GB (user available=11.31 GB), //*Note phone shows this as USB storage, Pl correct if I am wrong*//
external micro SD card = Nil
I want to increase the RAM Or ROM so that my mobile should not lags/hangs
I feel that mobile is slow mainly due to less RAM......pl correct if I am wrong
I want to use the the 1GB/2GB/3GB/4GB out of Internal 16 GB to increase the size of ROM from 2GB to 3GB/4GB or RAM from 768 MB to 1GB/2GB/3GB/4GB more.....
Pl help me out with the specific steps.....
Thanks a lot @AntaresOne

@anil.xda
Yes, just 768 MB of RAM is one of the biggest performance limiting factors of this phone but sadly you can't just "increase it". You'll have to use something like a zRAM or a SWAP script. But this is just a workaround - and it too has some drawbacks I think.
Sent from my GT-I9070

[Repartitions] Expand Your Data Partition ! [U8800PRO]

Expand Your Data partition​
Hello dear friends! Welcome
I am happy to share with you a new trick for our lovely U8800PRO.
I am presenting to you a flashable zip tool that can be useful for who wants to customize their "/data" partition for more space without use of sdExt
So now the waiting is over now finally you can customize - expand your /data partition by shrinking your 1.5GB internal storage
so far you all know this trick is already available for U8800 but not work on U8800PRO.
thanks for genokolar who made expanding partition possible for U8800 and inspired me to make this available for U8800PRO. I modified that to work for U8800Pro
Nowadays we have Kitkat Available for our device. But for the great feel of that, Of course for ART run time, ~ 800 MB as /data partition not good
with this you can expand your /data partition at max ~2300 MB
so here you go --
1] Important ! make nandroid backup of your device. [ use latest Teamwin recovery ]
2] use 5irom App to make a backup of your imei [optional]
3] make sure you have backed up your internal storage as this method wipe your internal storage
4] Download one of attached Zip file to External SDcard and flash it from Teamwin recovery [make sure you have unmounted /data , /system , /emmc] !
5] reboot to RECOVERY
6] after booting in recovery go to "wipe" ==>> "Advanced Wipe" and make following from recovery [very important]
wipe /data
wipe /internal_sd
wipe /cache
7] restore your /data partition from nandroid [optional]
8] reboot device and Voila!!!!:cyclops:
this is permanent solution for /data partition, this will not change by changing roms.
tested working on Cm11 CrysisLtu Rom
probably work for any rom test it your self
if you facing problems,
post your partition table
Code:
su
fdisk /dev/block/mmcblk0
now when u see "Command (m for help)"
enter "p" for partition table
Code:
fdisk /dev/block/mmcblk0
Command (m for help): p
this is the safest method however i take no responsibility if you have done incorrectly to your device.
Enjoy!!
Don't Forget to hit Thanks !

Excellent work! I tried with "Data2300Mb-internal_200Mb" but it messed up my partitions.. I do not longer have mmcblk0p13 and it looks like internal storage is now in mmcblk1p2 with ext4 file system.. Restored a whole phone backup so everything ok now but you're sure the script works?

Thank you!
Hello! I also tested this, and as the previous poster, it broke my partition scheme. However, I used the commands found in your scripts to be able to make the system work again, and I now have space available on my data partition!
I am not sure what messed up my partitions, my block numbers matched yours perfectly. Upon running the script for the first time, it seems the script was somehow unable to create partitions 13 and 14. When running it again the next time, the script didn't even start correctly, since its first commands are to mount /data and /emmc. -So at this point, I copied your "partition" script, and put it on my SD-card to run manually. That worked well, and running the make_ext4fs and mkfs.vfat commands afterwards worked to recreate filesystems
Thanks again!

Lihis said:
Excellent work! I tried with "Data2300Mb-internal_200Mb" but it messed up my partitions.. I do not longer have mmcblk0p13 and it looks like internal storage is now in mmcblk1p2 with ext4 file system.. Restored a whole phone backup so everything ok now but you're sure the script works?
Click to expand...
Click to collapse
of course it works
tested with my own device [u8800pro]
please follow steps carefully
other wise if you still facing problems send me your partition table
Code:
su
fdisk /dev/block/mmcblk0
now when u see "Command (m for help)"
enter "p" for partition table :good:
Code:
fdisk /dev/block/mmcblk0
Command (m for help): p

mayank88288 said:
of course it works
tested with my own device [u8800pro]
please follow steps carefully
other wise if you still facing problems send me your partition table
Code:
su
fdisk /dev/block/mmcblk0
now when u see "Command (m for help)"
enter "p" for partition table :good:
Code:
fdisk /dev/block/mmcblk0
Command (m for help): p
Click to expand...
Click to collapse
Code:
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 32769 32831 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 32831 33206 3000 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 33206 483328 3600980 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 40961 42496 12288 59 Unknown
/dev/block/mmcblk0p6 49153 65792 133120 4c Unknown
/dev/block/mmcblk0p7 73729 73984 2048 5a Unknown
/dev/block/mmcblk0p8 81921 82304 3072 58 Unknown
/dev/block/mmcblk0p9 90113 90987 7000 50 Unknown
/dev/block/mmcblk0p10 98305 98688 3072 4a Unknown
/dev/block/mmcblk0p11 106497 106880 3072 4b Unknown
/dev/block/mmcblk0p12 114689 163840 393216 83 Linux
/dev/block/mmcblk0p13 163841 278528 917504 83 Linux
/dev/block/mmcblk0p14 278529 483328 1638400 69 Unknown
There you go.. I will make some test when I have time.

Deleted

Hi, I tried to flash the zip and my partitions disappeared. At least, I could recover the phone with the official ICS rom. Can anyone tell me how to expand the memory?? It would be very usefull, thanks.

How I got this working
This is a first draft of this guide!
Requirements:
- Recovery TWRP (or something similar), I have "twrp-v2860-260415-u8800pro.zip" (http://forum.xda-developers.com/ideos-x5/pro-development/5-1-cm-12-1-t3099390)
- ADB in Linux or Windows etc (http://developer.android.com/tools/help/adb.html)
- SD card
- One of the partition zip files above (depending on if you want to shrink or restore partitions)
- A rom to flash (restoring from nandroid backup didn't work for me, but by all means, do try )
Steps (READ ALL of this before you start):
1. Download and unzip a partition ZIP file from OP, "Data2300Mb-internal_200Mb.zip" for instrance.
2. Reboot mobile into recovery, TWRP (POWER + Vol up)
3. Do a backup, and manually copy the files from "Internal Storage" to somewhere. Remember to NOT backup TO internal storage!!
4. Unmount all partitions except SD Card!
5. Connect mobile to pc via USB cable
6. Start "adb shell" in the command line on your PC (Linux, Windows whatever)
7. In a text editor, open the "partition" file from your unzipped partition zip, "Data2300Mb-internal_200Mb.zip" in my case.
8. Begin with the command "cd /sbin" and run the commands in the file.
- BUT, skip the "<<EOF" text.
- Also skip the "t" part, line 14, 15 and 16 (not important, but not necessary either )
- Finish with the "w" at line 17 (Important! ).
- The ADB shell commands I ran:
Code:
cd /sbin
./fdisk /dev/block/mmcblk0
d
14
d
13
n
163842
278528
n
278530
483328
w
9. Run "exit" in the adb shell
10. Reboot the recovery
11. Open Wipe -> Advance Wipe -> Check "Data" -> Repair or Change File System -> Change File System -> ext4
12. Open Wipe -> Advance Wipe -> Check "Internal Storage" -> Repair or Change File System -> Change File System -> FAT
13. Reboot Recovery
14. Wipe all partitions except SD Card for good measure
15. Reinstall ROM or try and restore nandroid backup
My recovery is complaining about the "Android Secure" partition not being mounted, but installing a fresh ROM and booting works fine.
Restoring a nandroid backup not so much

Thank you very much!!! I have done it!! Now I have 2GB for apps!!
I am going to explain the easiest way. We can flash the zips by mayank, but at the end of the process is very important to do the steps 7 and 8 to recover our partitions with the new sizes working.
REMEMBER: I didn't backup because I wanted a new installation of a new rom. So, in my process I lost all my information. Save your photos and other important files before do that.
So, I am going to tell you exactly what I did and it works perfect:
1. Download the zip you prefer, I used "Data2200Mb-internal_300Mb.zip" and copy it to your SD Card.
2. Reboot mobile into recovery, TWRP (POWER + Vol up)
3. Unmount all partitions except SD Card
4. Connect mobile to pc via USB cable
5. Flash the zip Data2200Mb-internal_300Mb.zip or the one you prefer.
6. Reboot the recovery
7. Open Wipe -> Advance Wipe -> Check "Data" -> Repair or Change File System -> Change File System -> ext4
8. Open Wipe -> Advance Wipe -> Check "Internal Storage" -> Repair or Change File System -> Change File System -> FAT
9. Reboot Recovery
10. Wipe all partitions except SD Card for good measure
11. Install the new rom, in my case cyanogenmod 4.4
If you have any problem, you can recover your phone with the official rom ICS 4.0 ( U8800pro,Android 4.0,V100R001C00B928 ) . Just install it by the typical method of the folder "dload" in the SD card(POWER + VOL UP + VOL DOWN).
I am very happy with the result, my old u8800pro has a new life with 2gb for apps + kitkat 4.4 + nova launcher

Update (from memory):
I deleted partition 14 (its empty space atm), so now Spotify correctly saves the offline files to the SD card

[TUTO] Enable Adoptable Storage on MM

MM bring the ability to devices which support it to share SD card with system to install apps on SD card. But Sony disabled this on MM. Here is to Enable this functionality
(Be aware that your shared partition will be hidden on other devices)
You will need adb installed on your computer
If you doesn't have it :
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Then connect your phone with adb debugging enabled.
Type "adb shell"
Once you're connected to your device : "sm list-disks"
This will return the ID of your sd card.
Now, if you want the whole sd card to be shared type "sm partition disk:ID private"
If you want your sd to be partitionned type "sm partition disk:ID mixed:%"
(replace ID with your own card ID and % with the STANDARD stockage percent you want on your sd card)
You're done !
(Sizes of partitions are not reported as they should but it seems to work)
Before/After
Before :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After :
Source :
mocado.com
This is Mocado's work, not mine !

But they are testing it on S7 ........ anyone tried on our Sony?

@Elfeno
Is it possible to take and save screenshot after enabling adoptable storage and moved app with this way?
I couldn't access to internal storage in some apps when I enabled adoptable storage with other way (xposed)...

I have successfully done this and everything seems to work fine however when I migrate my data to the SD card so this becomes the default location for new apps and data, I get a memory error in the stock camera app. Is anyone else getting this issue? I haven't yet figured a way around it. This is the one and only issue but it would be a deal breaker

@AndroPlus Since this functionality is part of Android and the 2 memory become one It should not have this issue but will try @roland101 This issue happened to me also after upgrading to MM. Did a clean install wiping data resolved this issue

Hi @Elfeno. I tried a factory reset from the Backup and Restore menu but I still have the issue. How exactly did you do it? Did you already have the SD card private partitioned and data migrated when you did the factory reset? I did, but then my phone didn't recognize the SD card anyway so I had to re-apply the private partition via adoptable storage. I then check the camera, no error. I then migrated all data from internal to SD card from the storage section but after that and a reboot I still get the memory error in the camera app. What were your steps exactly? Thanks

Hello @roland101,
I met the same issue like you. But if your SD card is large enough (like 128GB), you can format it in mixed 25 (reserve 32GB standard storage, other some other value), and then you can use camera on that partition. But the new problem will be: Google Photos(if you use that for backup) cannot delete device copy on that partition (I dont't know why Google Photos didn't request external SD card permission).

@roland101 @fqj1994 Yes the partition created for apps cannot be use to store files. Mixed will create 1 partition for apps and 1 for files
About the Google Photos app I guess it store photos in app data and if we cannot write that partition it doesn't allow us to delete these files but should work using Google photo app since it's is own files. If Gphoto was baked with your rom maybe it have arlready the permision needed. You can also check in per apps permissions in settings Check if it delete the cloud backup when you delete local photo.

@Elfeno
Another problem is even get camera to work with a mixed partition. all apps externally calling camera to take photos are dead (like hangout/ telegram)

Elfeno said:
@roland101 @fqj1994 Yes the partition created for apps cannot be use to store files. Mixed will create 1 partition for apps and 1 for files
Click to expand...
Click to collapse
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.

Not sure it worked
fqj1994 said:
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.
Click to expand...
Click to collapse
Just tried this on a xperia z5 compact and the commands worked the sm partition returned in a few second, little too quick.
When I go into storage i just see a nagative number for both the internal and sd card.
a df from the adb shell shows the below
Filesystem Size Used Free Blksize
/dev 889.4M 96.0K 889.3M 4096
/sys/fs/cgroup 889.4M 0.0K 889.4M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt 889.4M 0.0K 889.4M 4096
/tmp 889.4M 4.0K 889.4M 4096
/system 4.9G 3.8G 1.1G 4096
/data 22.6G 5.0G 17.6G 4096
/oem 290.6M 117.6M 173.0M 4096
/cache 192.8M 260.0K 192.6M 4096
/persist 27.5M 804.0K 26.7M 4096
/firmware 80.0M 56.4M 23.5M 16384
/lta-label 11.7M 1.5M 10.2M 4096
/idd 14.0M 149.0K 13.8M 1024
/rca 8.4M 579.0K 7.8M 1024
/storage 889.4M 0.0K 889.4M 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 22.6G 5.0G 17.6G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
/mnt/expand/f9e6c33e-fc2c-45c4-ac57-c6f40d9360d3 117.2G 60.0M 117.1G 4096
is this right 22GB for /storage/emulated ? I would have though it should have been approx 160GB (32+128 - used space)

Actually it's right.
Adoptive storage does not merge two partitions. Or removing sd card will completely disable all installed application of your phone rather than a partial. It just provide ability to Store applications and application data to external storage without applications-aware. And the in the storage settings. You can use migrate data to point which storage to be used for data stored on /sdcard.

Hello,
It work perfectly, but because the function is not officially supported by Sony, displayed size informations are quite strange

fqj1994 said:
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.
Click to expand...
Click to collapse
I am now a little confused. I have a 64GB SD card and originally plan to use the entire SD card for Adoptable Storage.
Based on what's said above, does it make a difference if I choose to
1) partition the SD card to 32GB data+ 32GB for Adoptable Storage, or
2) use the entire SD card for Adoptable Storage?

Seems that it doesnt make any difference !

How I can return my phone to normal can not recognize other memories sd

For me it worked, no problem with stock camera.
Spotify did bug out a little (offline songs were stored to SD card), but a reinstall fixed it. Ii had nothing else set to SD card to begin with anyway.
Thanks for the tip! although I did have to use the whole SD card as private, using it partially would cause popups of new SD-card inserted constantly >> starting to use it would wipe the entire SD.
Using the following firmware:
KPN Mobile NL (32.1.A.1.185 / R3C)

It didn't work =/
Hi I did it all corecly, set the 64gb sd card full private... and started to install many apps... what happend is after it reached the full 16 gb(real internal storage) it would not let me instaling anything else it would just say memory full any one had this?
PS. didn't had any problem with the camera our any other app.

Also applicable on Z3?
Is this workaround also applicable on the z3 with marshmallow

Guys is it Z5c only or applicable on Z3 too?
please help.