[REF] I777 Partition Table & storage info.

cyril279

Senior Member
Jun 3, 2013
987
2,077
0
What many refer to as the "internal SD Card" is actually a partition of the internal memory module that is formatted FAT32 for cross-platform use, and dedicated to user storage (usb transfer, downloads, photos & videos, etc). Other partitions of the internal memory module use file system formats that are more specific to the linux-based operations of Android, kernels, bootloaders, etc.

The total size of the internal memory module of the SGH-i777 is 15.8 GB, and it is partitioned as shown in the table below.

Booted into Android: Settings > Storage, you should see reports for:
- "INTERNAL STORAGE" ~2GB
- "INTERNAL STORAGE" ~11.5GB
- IF you have an SD Card installed, you should see a third report named "SD CARD"

(Using the partition table as reference)
The first "internal storage", displays the status of the /data partition. This partition is populated by user-installed apps & data, as well as the user-specific data for /system apps.
The second "internal storage", displays the status of the user-storage partition.

Stock I777 Partition Table:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name       Flags
 1      4194kB  25.2MB  21.0MB  ext4         EFS
 2      25.2MB  26.5MB  1311kB               SBL1
 3      27.3MB  28.6MB  1311kB               SBL2
 4      29.4MB  37.7MB  8389kB               PARAM
 5      37.7MB  46.1MB  8389kB               KERNEL
 6      46.1MB  54.5MB  8389kB               RECOVERY
 7      54.5MB  317MB   262MB   ext4         CACHE
 8      317MB   333MB   16.8MB               MODEM
 9      333MB   870MB   537MB   ext4         FACTORYFS
10      870MB   3018MB  2147MB  ext4         DATAFS
11      3018MB  15.2GB  12.2GB  fat32        UMS
12      15.2GB  15.8GB  537MB   ext4         HIDDEN
 

cyril279

Senior Member
Jun 3, 2013
987
2,077
0
The path to user-storage (both internal and external) may vary from Android when booted into recovery.

Booted into Android
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/179:9 /mnt/media_rw/sdcard1 vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Booted into CWMR
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/block/vold/179:9 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
Booted into TWRP
internal & external user-storage are located at /emmc & /sdcard
These path names more appropriately represent the type of memory used. eMMC = embedded Multimedia Card
http://en.wikipedia.org/wiki/MultiMediaCard#eMMC
http://www.pcmag.com/encyclopedia/term/64404/emmc
The inconsistency with android's naming system can be an issue for apps that write OpenRecoveryScripts while booted into android, to be performed in recovery.
Code:
mount
/dev/block/mmcblk0p11 on /emmc type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk0p11 on /and-sec type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
Code:
	    TWRP	CWMR & AOSP	Device	Label	FileSys	size (MB)
mmcblk0					179:0			
mmcblk0p   /efs	     /efs		179:1	EFS	  ext4	20
mmcblk0p2				179:2	SBL1		1.2
mmcblk0p3				179:3	SBL2		1.2
mmcblk0p4				179:4	PARAM		8
mmcblk0p5  /boot     /boot		179:5	KERNEL		8
mmcblk0p6  /recovery /recovery		179:6	RECOVERY	8
mmcblk0p7  /cache    /cache		179:7	CACHE	  ext4	246
mmcblk0p8				259:0	MODEM		16
mmcblk0p9  /system   /system		259:1	FACTORYFS ext4	504
mmcblk0p10 /data     /data		259:2	DATAFS	  ext4	2016
mmcblk0p11 /emmc     /storage/sdcard0	259:3	UMS	  FAT32	11634
mmcblk0p12 /preload  /preload		259:4	HIDDEN	  ext4	504
						
mmcblk1					179:8			
mmcblk1p1  /sdcard   /storage/sdcard1	179:9	{whatevr} FAT32	{as purchased}
 
Last edited:

cyril279

Senior Member
Jun 3, 2013
987
2,077
0
This information above was helpful for me recently, and although these devices are well aged, I hope that the info. can be useful for someone else.

We have @SteveMurphy and @razen_kain to thank for encouraging me to compile and post this stuff.

From an ADB shell, or within a terminal emulator, "mount" will give you a report of the currently mounted devices, and their mount points, permissions and more.

The original partition table posted is reported from gparted, within an ADB shell

adb devices
^if it returns your device serial, then ADB can see your device
adb shell
^starts a shell session on the device
parted /dev/block/mmcblk0
^starts a gparted session on disk "mmcblk0", the internal memory module
print
^displays the partition table

If I have any of this information incorrect, or if there's more information that should be included, please let me know.
There's an entire world of fstab, device mapping, and volume daemons that I am NOT savvy with, so I chose not to run down that rabbit hole.
 
Last edited:

micallan_17

Senior Member
Sep 27, 2012
211
114
73
Santa Elena
so I wanted to try this but my android says:

Code:
C:\Users\Allan Romero>adb shell
[email protected]:/ $ parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
/system/bin/sh: parted: not found
127|[email protected]:/ $
is there a way to fix this, I wanted to compare the partition tables of my SGH-S959G to the SGH-I777, reason being was that when I go to download mode it says model S959G and I wanted to see if it can be changed to show the i777 under model.
 

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
so I wanted to try this but my android says:

Code:
C:\Users\Allan Romero>adb shell
[email protected]:/ $ parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
/system/bin/sh: parted: not found
127|[email protected]:/ $
is there a way to fix this, I wanted to compare the partition tables of my SGH-S959G to the SGH-I777, reason being was that when I go to download mode it says model S959G and I wanted to see if it can be changed to show the i777 under model.
Did you boot into recovery before you ran adb shell? First boot into recovery, next type adb shell and you will get a ~ # prompt, then type parted /dev/block/mmcblk0 followed by print.
 
Last edited:

micallan_17

Senior Member
Sep 27, 2012
211
114
73
Santa Elena
Did you boot into recovery before you ran adb shell? First boot into recovery, next type adb shell and you will get a ~ # prompt, then type parted /dev/block/mmcblk0 followed by print.
Oh I see, your tip fixed it, so I got this:

Code:
C:\Users\Allan Romero>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name       Flags
 1      4194kB  25.2MB  21.0MB  ext4         EFS
 2      25.2MB  26.5MB  1311kB               SBL1
 3      27.3MB  28.6MB  1311kB               SBL2
 4      29.4MB  37.7MB  8389kB               PARAM
 5      37.7MB  46.1MB  8389kB               KERNEL
 6      46.1MB  54.5MB  8389kB               RECOVERY
 7      54.5MB  317MB   262MB   ext4         CACHE
 8      317MB   333MB   16.8MB               MODEM
 9      333MB   870MB   537MB   ext4         FACTORYFS
10      870MB   3018MB  2147MB  ext4         DATAFS
11      3018MB  15.2GB  12.2GB  fat32        UMS
12      15.2GB  15.8GB  537MB   ext4         HIDDEN

(parted)

someone with more inside knowledge can let us know if there are any differences perhaps?
 

micallan_17

Senior Member
Sep 27, 2012
211
114
73
Santa Elena
so based on comparison by looks:

code from cyril279:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name       Flags
 1      4194kB  25.2MB  21.0MB  ext4         EFS
 2      25.2MB  26.5MB  1311kB               SBL1
 3      27.3MB  28.6MB  1311kB               SBL2
 4      29.4MB  37.7MB  8389kB               PARAM
 5      37.7MB  46.1MB  8389kB               KERNEL
 6      46.1MB  54.5MB  8389kB               RECOVERY
 7      54.5MB  317MB   262MB   ext4         CACHE
 8      317MB   333MB   16.8MB               MODEM
 9      333MB   870MB   537MB   ext4         FACTORYFS
10      870MB   3018MB  2147MB  ext4         DATAFS
11      3018MB  15.2GB  12.2GB  fat32        UMS
12      15.2GB  15.8GB  537MB   ext4         HIDDEN
code from mines:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name       Flags
 1      4194kB  25.2MB  21.0MB  ext4         EFS
 2      25.2MB  26.5MB  1311kB               SBL1
 3      27.3MB  28.6MB  1311kB               SBL2
 4      29.4MB  37.7MB  8389kB               PARAM
 5      37.7MB  46.1MB  8389kB               KERNEL
 6      46.1MB  54.5MB  8389kB               RECOVERY
 7      54.5MB  317MB   262MB   ext4         CACHE
 8      317MB   333MB   16.8MB               MODEM
 9      333MB   870MB   537MB   ext4         FACTORYFS
10      870MB   3018MB  2147MB  ext4         DATAFS
11      3018MB  15.2GB  12.2GB  fat32        UMS
12      15.2GB  15.8GB  537MB   ext4         HIDDEN
is it safe to say that flashing the i777 bootloader (odin screen one) to the SGH-S959G would basically convert it to an i777?
 

SteveMurphy

Recognized Contributor
Apr 22, 2012
1,656
2,702
153
Atlanta
is it safe to say that flashing the i777 bootloader (odin screen one) to the SGH-S959G would basically convert it to an i777?
I suppose, but what I don't get is why it matters? The devices are practically identical, excepting the 959 having the separate partition which is a great thing and something the i777/i9100 lacks.

So what I'm asking is because our two phones are almost the same and can flash the same roms/kernels/recovery, what does it matter if it says '959' or 'i777'?
 

micallan_17

Senior Member
Sep 27, 2012
211
114
73
Santa Elena
I suppose, but what I don't get is why it matters? The devices are practically identical, excepting the 959 having the separate partition which is a great thing and something the i777/i9100 lacks.

So what I'm asking is because our two phones are almost the same and can flash the same roms/kernels/recovery, what does it matter if it says '959' or 'i777'?
oh, I see I didn't know about the separate partition, I guess it doesn't really matter what it says on it, thanks for the reply :)

Cheers
 

david72262

Senior Member
Jul 3, 2013
1,951
1,781
143
Oregon
anyone fhave a new pit file for the s959g to increase system partition been searching for hours or would the one for the i777 work fine. I don't want to loose my separate recovery partition. I want to be able in install full slim gaaps

Created one don't need now.
 
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone