Related
FIXED!
I took a stab in the dark after doing a pull of the partitions to my backup hard drive and formatted the last, and largest partition on the list. It calculated out to about what my internal storage was supposed to be, which made me fairly confident that it was the one.
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p28
I tossed that little command into the shell through adb and /emmc/ mounted right up.
Hey guys, I seem to have corrupted my mmcblk0 rather well. mmcblk0p1-4 have no bounds. (Edit 4: This sounds rather silly now that I know more of what I'm looking at. mmcblk0p4 contains all of the partitions after it. partitions 1 - 4 just don't fall on the cylinder lines like the file system expects it to) Anyway, I was wondering if anyone would be kind enough to either copy/paste a stock emmc partition table (/dev/block/mmcblk0), or toss together a CWM flashable that reformats it properly so I can get my internal storage back.
An example of what I'm talking about:
http://forum.xda-developers.com/showpost.php?p=25436995&postcount=2
Thanks!
What my partition table looks like...
Code:
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 92 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 1923584 15284271+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13313 13375 500 47 Unknown
/dev/block/mmcblk0p6 13825 14080 2048 45 Unknown
/dev/block/mmcblk0p7 14337 14649 2500 4c Unknown
/dev/block/mmcblk0p8 14849 16128 10240 48 Unknown
/dev/block/mmcblk0p9 16385 16447 500 46 Unknown
/dev/block/mmcblk0p10 16897 16959 500 5d Unknown
/dev/block/mmcblk0p11 17409 17471 500 91 Unknown
/dev/block/mmcblk0p12 17921 19200 10240 93 Unknown
/dev/block/mmcblk0p13 19457 32000 100352 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p14 32257 32640 3072 4a Unknown
/dev/block/mmcblk0p15 32769 33152 3072 4b Unknown
/dev/block/mmcblk0p16 33281 33664 3072 58 Unknown
/dev/block/mmcblk0p17 33793 46336 100352 8f Unknown
/dev/block/mmcblk0p18 46593 46976 3072 59 Unknown
/dev/block/mmcblk0p19 47105 47488 3072 5a Unknown
/dev/block/mmcblk0p20 47617 48000 3072 5b Unknown
/dev/block/mmcblk0p21 48129 49408 10240 ab Darwin boot
/dev/block/mmcblk0p22 49665 50944 10240 60 Unknown
/dev/block/mmcblk0p23 51201 52480 10240 94 Unknown
/dev/block/mmcblk0p24 52737 183808 1048576 a5 FreeBSD
/dev/block/mmcblk0p25 183809 446208 2099200 a6 OpenBSD
/dev/block/mmcblk0p26 446465 485120 309248 a8 Darwin UFS
/dev/block/mmcblk0p27 485377 501888 132096 a9 NetBSD
/dev/block/mmcblk0p28 502273 1923584 11370496 90 Unknown
Edit: I can tcp/ip adb into the device now. Still not sure what's up with my usb connectivity.
Both TWRP and CWM repartition. Have you tried them?
fprice02 said:
Both TWRP and CWM repartition. Have you tried them?
Click to expand...
Click to collapse
Yes, CWM. It can't mount /emmc/ which is why I'm trying to do it this way. I've spent most of the afternoon going through the steep learning curve that is android/linux file systems on a windows machine. Partition 4 actually contains all the partitions after it, which makes it more fun to figure out which one is the internal storage partition(s).
FIXED
So I fixed it. I took a stab in the dark after doing a pull of the partitions to my backup hard drive and formatted the last, and largest partition on the list. It calculated out to about what my internal storage was supposed to be, which made me fairly confident that it was the one.
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p28
I tossed that little command into the shell through adb and /emmc/ mounted right up.
MSDOS......classic on a linux platform.
As I posted previously about flashing issues and errors which came up with my device I've learned that my partitions were corrupted and nearly all were erased. With some help from developer Mev and other members I was able to get my device working with ADB shell yet the commands seemed to be far out of my lead.
I have an YP-G70 USA (8 Gigs) device.
From what I learned this is the partition to the device, yet the start/ending blocks aren't listed. Would that be a problem?
Code:
Device Size (KiB) Mount Name Notes
/dev/block/mmcblk0 7757824 Internal eMMC disk device
/dev/block/mmcblk0p1 1 Extended partition containing everything else
/dev/block/mmcblk0p5 256 boot.bin Initial+Primary Bootloaders
/dev/block/mmcblk0p6 256 YPG70_8G-0304.pit Partition Information Table
/dev/block/mmcblk0p7 1280 Sbl.bin Secondary Bootloader
/dev/block/mmcblk0p8 1280 Sbl.bin SBL backup
/dev/block/mmcblk0p9 5120 /mnt/.lfs param.lfs param.blk and boot logos - source of recovery loops
/dev/block/mmcblk0p10 10240 /efs efs.rfs WiFi and BT MAC addresses - causes missing lockscreen
/dev/block/mmcblk0p11 7680 zImage Kernel
/dev/block/mmcblk0p12 7680 zImage "Recovery" kernel that is never used
/dev/block/mmcblk0p13 296960 /system factoryfs.rfs System partition
/dev/block/mmcblk0p14 137216 /dbdata dbdata.rfs Various Android/app databases
/dev/block/mmcblk0p15 65536 /cache cache.rfs Cache partition
/dev/block/mmcblk0p16 1970176 /data datafs.rfs Data partition (apps and their data)
/dev/block/mmcblk0p17 5252096 /sdcard userfs_8G.rfs "Emmc" "Usb Storage" - where your media goes
/dev/block/mmcblk1 <varies> External SD Card disk device
/dev/block/mmcblk1p1 <varies> /sdcard/external_sd External SD Card partition
Next thing is, whenever I tried using
Code:
fdisk /dev/block/mmcblk0
and later on creating a prime partition within the settings that I try to use the "e" to extend (says nothing about "l" for logical) which I run out of sectors to create them with. And sadly the only ones that ever come up is mmcblk0p4 or mmcblk0p3.
Just looking for help to get my player back up and running .. it's all I have and use at work since I don't have a phone and really have been trying to get this to work but its difficult so im sorry for bothering..
I don't know what to do after this:
Jistropy said:
As I posted previously about flashing issues and errors which came up with my device I've learned that my partitions were corrupted and nearly all were erased. With some help from developer Mev and other members I was able to get my device working with ADB shell yet the commands seemed to be far out of my lead.
I have an YP-G70 USA (8 Gigs) device.
From what I learned this is the partition to the device, yet the start/ending blocks aren't listed. Would that be a problem?
Code:
Device Size (KiB) Mount Name Notes
/dev/block/mmcblk0 7757824 Internal eMMC disk device
/dev/block/mmcblk0p1 1 Extended partition containing everything else
/dev/block/mmcblk0p5 256 boot.bin Initial+Primary Bootloaders
/dev/block/mmcblk0p6 256 YPG70_8G-0304.pit Partition Information Table
/dev/block/mmcblk0p7 1280 Sbl.bin Secondary Bootloader
/dev/block/mmcblk0p8 1280 Sbl.bin SBL backup
/dev/block/mmcblk0p9 5120 /mnt/.lfs param.lfs param.blk and boot logos - source of recovery loops
/dev/block/mmcblk0p10 10240 /efs efs.rfs WiFi and BT MAC addresses - causes missing lockscreen
/dev/block/mmcblk0p11 7680 zImage Kernel
/dev/block/mmcblk0p12 7680 zImage "Recovery" kernel that is never used
/dev/block/mmcblk0p13 296960 /system factoryfs.rfs System partition
/dev/block/mmcblk0p14 137216 /dbdata dbdata.rfs Various Android/app databases
/dev/block/mmcblk0p15 65536 /cache cache.rfs Cache partition
/dev/block/mmcblk0p16 1970176 /data datafs.rfs Data partition (apps and their data)
/dev/block/mmcblk0p17 5252096 /sdcard userfs_8G.rfs "Emmc" "Usb Storage" - where your media goes
/dev/block/mmcblk1 <varies> External SD Card disk device
/dev/block/mmcblk1p1 <varies> /sdcard/external_sd External SD Card partition
Next thing is, whenever I tried using
Code:
fdisk /dev/block/mmcblk0
and later on creating a prime partition within the settings that I try to use the "e" to extend (says nothing about "l" for logical) which I run out of sectors to create them with. And sadly the only ones that ever come up is mmcblk0p4 or mmcblk0p3.
Just looking for help to get my player back up and running .. it's all I have and use at work since I don't have a phone and really have been trying to get this to work but its difficult so im sorry for bothering..
I don't know what to do after this:
Click to expand...
Click to collapse
You should have created that as an extended partition, not primary. Then go through and create new partitions "n"
I apologize for not giving you quite the right information. I know there's a table here with starting and ending blocks.
For illustration, here's an example of what to enter at the prompts. IGNORE THE BLOCK NUMBERS - it's just an illustration; just notice the extended/logical and the partition numbers.
Code:
[[email protected] ~]$ fdisk mmcblk0
Welcome to fdisk (util-linux 2.22.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table
Building a new DOS disklabel with disk identifier 0xab3ebd8d.
Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): e
Partition number (1-4, default 1):
Using default value 1
First sector (2048-102399, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-102399, default 102399):
Using default value 102399
Partition 1 of type Extended and of size 49 MiB is set
Command (m for help): p
Disk mmcblk0: 52 MB, 52428800 bytes, 102400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab3ebd8d
Device Boot Start End Blocks Id System
mmcblk0p1 2048 102399 50176 5 Extended
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 5
First sector (4096-102399, default 4096):
Using default value 4096
Last sector, +sectors or +size{K,M,G} (4096-102399, default 102399): 16383
Partition 5 of type Linux and of size 6 MiB is set
Command (m for help): p
Disk mmcblk0: 52 MB, 52428800 bytes, 102400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab3ebd8d
Device Boot Start End Blocks Id System
mmcblk0p1 2048 102399 50176 5 Extended
mmcblk0p5 4096 16383 6144 83 Linux
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 6
First sector (18432-102399, default 18432):
Using default value 18432
Last sector, +sectors or +size{K,M,G} (18432-102399, default 102399):
Using default value 102399
Partition 6 of type Linux and of size 41 MiB is set
Command (m for help): p
Disk mmcblk0: 52 MB, 52428800 bytes, 102400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab3ebd8d
Device Boot Start End Blocks Id System
mmcblk0p1 2048 102399 50176 5 Extended
mmcblk0p5 4096 16383 6144 83 Linux
mmcblk0p6 18432 102399 41984 83 Linux
Command (m for help): w
The partition table has been altered!
Syncing disks.
[[email protected] ~]$
Awe man thank you!! Going to try this out right now I felt bad for messaging you.
Give me like 15 minutes.
Those cover three of the partitions, how do I go about making the rest?
Jistropy said:
Awe man thank you!! Going to try this out right now I felt bad for messaging you.
Give me like 15 minutes.
Those cover three of the partitions, how do I go about making the rest?
Click to expand...
Click to collapse
Just keep going:
Code:
n (new)
l (logical)
<enter> (beginning)
+blocks (size)
and then
Code:
p (print)
to check your work, and
Code:
w (write)
to save changes and exit.
The Block sizes don't matter right?
Jistropy said:
The Block sizes don't matter right?
Click to expand...
Click to collapse
They matter very much. Use the ones from the device. The above was to illustrate the process. It has entirely wrong numbers.
I will have to repeat this process after doing the extended partition:
Code:
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
So what do I do with these?
Code:
First sector (18432-102399, default 18432):
Using default value 18432 (DONT FILL ?)
Last sector, +sectors or +size{K,M,G} (18432-102399, default 102399):
Using default value 102399 (DONT FILL ?)
Should I fill in those with this?
Code:
Device Size (KiB) Mount
/dev/block/mmcblk0 7757824
/dev/block/mmcblk0p1 1
/dev/block/mmcblk0p5 256
/dev/block/mmcblk0p6 256
/dev/block/mmcblk0p7 1280
/dev/block/mmcblk0p8 1280
/dev/block/mmcblk0p9 5120
/dev/block/mmcblk0p10 10240
/dev/block/mmcblk0p11 7680
/dev/block/mmcblk0p12 7680
/dev/block/mmcblk0p13 296960
/dev/block/mmcblk0p14 137216
/dev/block/mmcblk0p15 65536
/dev/block/mmcblk0p16 1970176
/dev/block/mmcblk0p17 5252096
/dev/block/mmcblk1 <varies>
/dev/block/mmcblk1p1 <varies>
Also, how do I do the last two? Just testing things I don't have the numbers so im randomly copying and pasting the number sets.
Jistropy said:
I will have to repeat this process after doing the extended partition:
Code:
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
So what do I do with these?
Code:
First sector (18432-102399, default 18432):
Using default value 18432 (DONT FILL ?)
Last sector, +sectors or +size{K,M,G} (18432-102399, default 102399):
Using default value 102399 (DONT FILL ?)
Should I fill in those with this?
Code:
Device Size (KiB) Mount
/dev/block/mmcblk0 7757824
/dev/block/mmcblk0p1 1
/dev/block/mmcblk0p5 256
/dev/block/mmcblk0p6 256
/dev/block/mmcblk0p7 1280
/dev/block/mmcblk0p8 1280
/dev/block/mmcblk0p9 5120
/dev/block/mmcblk0p10 10240
/dev/block/mmcblk0p11 7680
/dev/block/mmcblk0p12 7680
/dev/block/mmcblk0p13 296960
/dev/block/mmcblk0p14 137216
/dev/block/mmcblk0p15 65536
/dev/block/mmcblk0p16 1970176
/dev/block/mmcblk0p17 5252096
/dev/block/mmcblk1 <varies>
/dev/block/mmcblk1p1 <varies>
Also, how do I do the last two? Just testing things I don't have the numbers so im randomly copying and pasting the number sets.
Click to expand...
Click to collapse
PLEASE have a look around....
http://forum.xda-developers.com/showthread.php?t=1523682
the numbers you want are here within ^post n°8. (value is Kb) and in many other posts!
The last partition n°17, should and must have only some 5gb because your device is 8 gb. Take care to set fdisk with the proper set up between blocks and Bytes and in case of error don't panic, just trail again .
Good luck
sorry lolo9393
Jistropy said:
Okay, rude much?
Your no help, that's for: "CORRECT partition sizes (for 16GB model!):"
As I said above, I have a 8 GIG USA YP-G70.
If your gonna post, maybe you should read more clearly.
Click to expand...
Click to collapse
You follow the table until partition 17 that will show only some "5252096" kb remaining if entered numbers are correct, because you have a 8 Gb device.
I tried to help you with what I know, sorry for my bad english..
Jistropy said:
Okay, rude much?
Your no help, that's for: "CORRECT partition sizes (for 16GB model!):"
As I said above, I have a 8 GIG USA YP-G70.
If your gonna post, maybe you should read more clearly.
Click to expand...
Click to collapse
Please listen th his help. He knows more about it than I do.
i apologize but no matter how i insert those numbers they never come out close
I got up to block 16 but it says i over pass the cylendars
Code:
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
What do I set for 17 as well?
I can't get the tables to add up to what u got so i copied the start and ending for each.
Stuck on 16/17 need some help.
Edit --
I was able to flash stock! But i get a bunch of errors about opening cache and mounting.
rfs format failed on /dev/block/mmcblk0p15
Jistropy said:
I got up to block 16 but it says i over pass the cylendars
Code:
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
What do I set for 17 as well?
I can't get the tables to add up to what u got so i copied the start and ending for each.
Stuck on 16/17 need some help.
Edit --
I was able to flash stock! But i get a bunch of errors about opening cache and mounting.
rfs format failed on /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Yes, you were able to flash but your device is still useless because partition 16 and 17 are wrongly built.
may be you entered the right numbers but resulting in wrong recording , check your print (p) attached.
It is perfect until partition 16 beginning..
.Now just delete and rewrite 16 and 17th. (end n°17 by +k instruction will fill the gap and give you the right number or enter 242432 blocks as follow .
Vdev/block/mmcblk0p17 313401 242432 ........... result dotted should give some 5252096 kb.
Then write and print again in order to check your good work and at this point your next flashing will be good! (may be a wipe cache to be sure and avoid bootloop)
other suggestion is you come to my home tomorrow morning in order I arrange that for you!!!!
Cheers
It is perfect until partition 16 beginning..
.Now just delete and rewrite 16 and 17th. (end n°17 by +k instruction will fill the gap and give you the right number or enter 242432 blocks as follow .
Vdev/block/mmcblk0p17 313401 242432 ........... result dotted should give some 5252096 kb.
Then write and print again in order to check your good work and at this point your next flashing will be good! (may be a wipe cache to be sure and avoid bootloop)
Click to expand...
Click to collapse
What do I put for 0p16 then? Sorry I'm making sure i dont mess up
Tried following the same 16 and it went through however for block 17 the number value is too high
Jistropy said:
What do I put for 0p16 then? Sorry I'm making sure i dont mess up
Tried following the same 16 and it went through however for block 17 the number value is too high
Click to expand...
Click to collapse
Quick because it is lunch time here...
P16 is the same as in the 16gb table.
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
ok ,got it?
No risk you mess the device, only take care to verify what is done by (p) print instruction and check the written table.
it doesnt allow me to set that value.. im sorry
Jistropy said:
it doesnt allow me to set that value.. im sorry
Click to expand...
Click to collapse
Did you delete the partition before rewriting it?
Should work because you have enough numbers of blocks to fill as said.
If no success do as follow:
delete p16 and 17, then do a write and post the result you get.
here: (I dont have enough space for every 16, or 17)
but im glad you've gotten me this far.
Jistropy said:
here: (I dont have enough space for every 16, or 17)
but im glad you've gotten me this far.
Click to expand...
Click to collapse
Sorry i didn't check it first but you are 4 heads mode (read line 2 of your print) that explain wy your lack of blocks.
You shoud reset fdisk in secondary menu to 1 head like following example
1 heads, 16 sectors/track,
Units = cylinders of 16 * 512 = 8192 bytes
I have no means to open fdisk from here to guide you, but it is easy to find once understood.
I come back in 3 hours time and if you still have pb I'll check for more guidance.
OK?
ADD;
How to change heads number?
select (h) to change number of heads in expert menu (m)
(now you are the "expert") you should get some 970 000 cylinders to split.
For more details:
http://linux.omnipotent.net/article.php?article_id=6979
doing this will allow you to successfully complete your memory table. great!
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
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}
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.
This is fantastic stuff! I know you put a lot of work into it, so thanks for all the research you've accumulated and shared.
cyril279,
Very helpful info. Nice job on compiling and posting the info. Thanks for taking the time to do it and for continuing to help in this forum.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Great work man! We really appreciate you putting your time and effort into this. I am curious though what the 959g looks like. I know the recovery is on a different partition but that is the only difference Im aware of.
We would only know for sure if we analyze a 959 phone, but I'm going to guess that the partition table would be exactly the same. Notice that mmcblk0p6 is Recovery, and on the I777 that partition is not used.
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.
micallan_17 said:
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.
Click to expand...
Click to collapse
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.
creepyncrawly said:
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.
Click to expand...
Click to collapse
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?
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?
micallan_17 said:
is it safe to say that flashing the i777 bootloader (odin screen one) to the SGH-S959G would basically convert it to an i777?
Click to expand...
Click to collapse
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'?
SteveMurphy said:
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'?
Click to expand...
Click to collapse
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
Great info. Thanks fellas.
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.
i just got a Star/Ulefone n9002 mediatek based clone of a Samsung Galaxy Note 3. the phone is pretty nice... i'm liking it. specs on it are pretty good, but i am having an issue with the internal SD card. when i ordered it, it was suppose to come with an 8gb internal SD card. i got it, took it out of the box and checked, and the system specs said that it had a 16GB internal card. originally, i thought, "Bonus!!" but the more i thought about it, the more i realized that this is probably bogus or an issue with whatever rom is flashed on it. checking needrom.com there are 2 rom images out there for it and they both list the original specs for an 8gb internal card. when i started loading things on it, i suddenly started to get strange errors about running out of space. it didn't make much sense. anyway, i rooted it with mtk droid tools, installed the custom CWM, and what not, and started poking under the hood. fdisk is giving me errors and parted refuses to even work on it. (maybe i am running the wrong commands, but attached are outputs).
anyway, i already know there is an issue with the ROM cause MTK Droid tools reports that it has an mt6582 cpu even though the software on the phone reports and mt6589. all of the roms say it should be an mt6582 also. not a big deal in my opinion.
my question is this... is there anyway to non-destructively fix the partition table? i have read alot about editing the EBR files to change partition sizes, but there has got to be a better way. also, i'd like to truely verify the size of the built in storage without opening up the phone and reading the numbers off of the internal SD card.
should i just get the latest ROM off of needrom.com and flash it? i don't know if this would fix the partition table either.
here are the outputs:
fdisk output:
1|[email protected]_wet_v116_jb5:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 951232.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Command (m for help): v
v
Partition 2 does not end on cylinder boundary
Partition 2: sector 0 greater than maximum 16
Partition 3 does not end on cylinder boundary
Partition 3: sector 0 greater than maximum 16
Partition 4 does not end on cylinder boundary
Partition 4: sector 0 greater than maximum 16
Partition 5: sector 0 greater than maximum 16
Partition 6: sector 0 greater than maximum 16
Logical partition 5 not entirely in partition 1
Total allocated sectors 4290439170 greater than the maximum 15219712
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7792 MB, 7792492544 bytes
1 heads, 16 sectors/track, 951232 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1153 2432 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2433 3712 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 5313 6080 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8129 97728 716800 83 Linux
/dev/block/mmcblk0p6 376001 64 2144476159+ 83 Linux
Command (m for help):
Click to expand...
Click to collapse
gdisk output:
[email protected]_wet_v116_jb5:/system/xbin # gdisk
gdisk
GPT fdisk (gdisk) version 0.8.4
Type device filename, or press to exit: /dev/block/mmcblk0
/dev/block/mmcblk0
EBR signature for logical partition invalid; read 0x0000, but should be 0xAA55
Error reading logical partitions! List may be truncated!
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if
you don't want to convert your MBR partitions to GPT format!
***************************************************************
Command (? for help): v
v
No problems found. 13732797 free sectors (6.5 GiB) available in 4
segments, the largest of which is 13656031 (6.5 GiB) in size.
Click to expand...
Click to collapse
parted output:
1|[email protected]_wet_v116_jb5:/system/xbin # 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) check
check
check
Error: Can't have a partition outside the disk!
(parted) print devices
print devices
print devices
Error: Can't have a partition outside the disk!
(parted) print all
print all
print all
Error: Can't have a partition outside the disk!
(parted)
Click to expand...
Click to collapse
/proc/mounts:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 rw,relatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:8 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
/proc/partitons
major minor #blocks name
7 0 1254 loop0
7 1 11451 loop1
253 0 524288 zram0
179 0 7609856 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 716800 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 2097152 mmcblk0p7
179 8 4601856 mmcblk0p8
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 31166976 mmcblk1
179 97 31162880 mmcblk1p1
Click to expand...
Click to collapse
progress...
i take it by the deafening number of replys, no one has any idea whats up with my issue or any idea how to fix it. so i have been digging deeper myself and think i have come up with some solutions.
first of all, i was just planing on flashing one of the roms off of the NeedRom.com website, but i read a couple of posts on chinaphonearena.com and one in some german forum that listed a phone with my same baseband and ROM build, and when they flashed the new rom, it screwed up their touch screen. something about having an incompatible touch screen driver. i don't know if the person flashing the rom chose the correct rom, or incorrect rom, but it made me skidish to attempt this as a fix.
so i checked in on modifying the EBR files, which people have been doing on these mediatek phones for a while. i thought maybe one of mine was screwed up. i extracted the EBR1 and EBR2 file from my fine with MTKDroidTools and i pulled the files out of the rom update. i also took the scatter file generated by MTKDroidTools and the scatter file from the rom update. i compared them line for line. the EBR files are totally identical! as was the scatter file. address of where the partitions start and stop inside the phone are 100% the same. so flashing a new rom wouldn't have fixed the problem anyway.
i started googling around at the error that parted gives me: "Error: Can't have a partition outside the disk!" this is discussed elsewhere, but mostly on actual machines, not phones. there are some postings here on XDA, but none that address my specific issue. anyway, the ways it always suggests to fix it is to figure out which partition is oversized, used the sfdisk utility to dump the partiton table, fix it, and re-write the partition table to disk. simple enough, if you know what your partition table should look like.
back to fdisk, i reprint out a copy
1|[email protected]_wet_v116_jb5:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 951232.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Command (m for help): v
v
Partition 2 does not end on cylinder boundary
Partition 2: sector 0 greater than maximum 16
Partition 3 does not end on cylinder boundary
Partition 3: sector 0 greater than maximum 16
Partition 4 does not end on cylinder boundary
Partition 4: sector 0 greater than maximum 16
Partition 5: sector 0 greater than maximum 16
Partition 6: sector 0 greater than maximum 16
Logical partition 5 not entirely in partition 1
Total allocated sectors 4290439170 greater than the maximum 15219712
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7792 MB, 7792492544 bytes
1 heads, 16 sectors/track, 951232 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
/dev/block/mmcblk0p2 1153 2432 10240 83 Linux
/dev/block/mmcblk0p3 2433 3712 10240 83 Linux
/dev/block/mmcblk0p4 5313 6080 6144 83 Linux
/dev/block/mmcblk0p5 8129 97728 716800 83 Linux
/dev/block/mmcblk0p6 376001 64 2144476159+ 83 Linux
Click to expand...
Click to collapse
this does indeed tell me that the internal flash memory is about 8gb (Disk /dev/block/mmcblk0: 7792 MB, 7792492544 bytes) but it is not obvious to me which partition is screwed up.
anyway, i'd love for someone that has an mtk6582 based phone with 8gb of internal storage to provide me with a dump of their partition table, then i could just restore it over mine, and it should fix the issue!... the command is simple...
adb shell
su
sfdisk -d /dev/sdc > PT.txt
Click to expand...
Click to collapse
from what i see (i may be wrong here) but these phones run with something like 2 partition tables... there is the one that is physically connected to the first 512 bytes of the SD card. then they have the EBR's which map out all of the EMMC partitons. so there is just one big partition seen from the outside, but through software, we can map that big partition in to smaller ones by knowing start and end addresses inside that big partition. i tell you, it is confusing.
i'm sure if i use the spflash_tool and format my phone and re-install a rom, it would fix the problem, but i am nervous about doing that because so many people have had issues putting rom's on this phone. they report that even when going back to their original backup the touch screen issues persist.
anyone have any comments? any ideas? any mbr backup they could share with me?
I believe you read my thread in chinese forum, I have one here too, because my touch is not working well since the rom upgrade.
Anyway, I'm almost sure you have like me a STAR Ulefone N9002 MTK6582 (1.3GHz) with 8Gb total memory.
AnTuTu 17500 values are 6582, 13000 are 6589T.
The original ROM have 1Gb RAM, 2Gb Internal Memory, and 8Mpx camera.
The ROM you have, and the MARCH Rom Update of Needrom, make the fake values, and the ram and internal memory are not correct. The camera is updated to 13Mpx too.
If you want, here you could read the procedure to edit the MBR by yourself.
Or you could flash the JAN rom of needrom.
I'm not sure about what cause my touch to get screwed, I guess I will never know, but I will keep flashing my phones...
At the moment, I'm waiting for a new touch for replace.
Cheers and good luck.
PMoto.
So, trying to install LineageOS on a stock Sony Xperia T, I got to trying to unify the userdata and now I have a 2GB "Internal Storage" (on /sdcard) partition and no "Legacy SDCard" partition. So clearly I messed up. I looked at the source code of the unify_userdata-20170128.zip file and it looks like all it does is delete the old UserData and SDCard partitions and then creates a new partition using all the sectors that were previously divided between these two partitions.
My question is this: is this correct? Why did android have two partitions of ~2Gb for Internal Storage and ~10Gb for the Legacy SD Card? Does the unify_userdata script really just delete these two and make one partition from the freed space?
And also, how can I fix my phone? In adb shell, df reports that the userdata partition (number 14) is mounted at /sdcard and is 2GB, but fdisk says that partition 14 has the label Userdata and is 13Gb. So how can it be mounted and only show a size of 2Gb?
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 423.7M 16.0K 423.7M 0% /dev
tmpfs 423.7M 24.0K 423.7M 0% /tmp
/dev/block/mmcblk0p13 246.1M 4.2M 241.8M 2% /cache
/dev/block/mmcblk0p14 2.0G 35.0M 1.9G 2% /data
/dev/block/mmcblk0p14 2.0G 35.0M 1.9G 2% /sdcard
Code:
# fdisk -l /dev/block/mmcblk0
Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 7423 1536K 0700 Boot
3 7424 10495 1536K 0700 Boot2
4 12288 53247 20.0M 0700 Kernel
5 53248 55295 1024K 0700 TZ
6 57344 63487 3072K 0700 modemst1
7 65536 71679 3072K 0700 modemst2
8 73728 79871 3072K 0700 fsg
9 79872 90111 5120K 0700 ramdump
10 90112 106495 8192K 0700 apps_log
11 106496 139263 16.0M 0700 FOTAKernel
12 139264 2654207 1228M 0700 System
13 2654208 3166207 250M 0700 Cache
14 3166208 30535646 13.0G 0700 Userdata