Database Info

[REF][INFO] SCH-I535 Partition Table

Google found this for me somewhere...
So I thought I'll share it with you. Not sure if this has been posted before, but I didn't find it in any search here.
I believe it's for the US SGS3 (SCH-I535), but I am not 100%, only ~85% sure.
{
"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"
}
@mods: Not sure this is the right place to post this, please move to appropriate place if necessary.
If you're looking for the 32 GB PIT file, you can look in this thread.
If you're looking for the GT-I9300 partition table, look in the thread:
"[REF] GT-I9300 PIT and Flash Analysis [WIP]"

E:V:A said:
Google found this for me somewhere...
So I thought I'll share it with you. Not sure if this has been posted before, but I didn't find it in any search here.
I believe it's for the US SGS3 (SCH-I535), but I am not 100%, only ~85% sure.
@mods: Not sure this is the right place to post this, please move to appropriate place if necessary.
If you're looking for the 32 GB PIT file, you can look in this thread.
Click to expand...
Click to collapse
Thank you for the table dude!
Sent from my SCH-I535 using xda app-developers app

Hey,
Is there a way to extract this kind of informations on a working device ? (i'm interested in HEX values for sectors)

vache said:
Hey,
Is there a way to extract this kind of informations on a working device ? (i'm interested in HEX values for sectors)
Click to expand...
Click to collapse
Check here: http://forum.xda-developers.com/showpost.php?p=30618458&postcount=57
You should be able to convert those bite sizes to hex (also, the table above has a column for hex and the number of sectors in each partition...)
I that what you're looking for?

In fact i want to find fist sector number for each partition to be able to write on it and try to restore my phone. (A bit off topic cause it's not a Samsung phone, but also using MSM8960)

For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!

E:V:A said:
For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!
Click to expand...
Click to collapse
You, sir, are big pimpin'. Thanks
Sent from my SCH-I535 using xda app-developers app

E:V:A said:
For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!
Click to expand...
Click to collapse
You're missing a few mmc blocks for the SCA-I535 (d2vzw). Here they are, but I hve no idea what they do:
Code:
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk1p1
/dev/block/mmcblk1p2
The latter two blocks suggest a second eMMC chip with its own NAND storage.
I working on a tool that backs up the SCH-I535 directly to your computer using adb. You can find it HERE. For now, Its only setup for partitions and data that one might use in recovery like CWM or TWRP or even ODIN. I haven't iterated out all the blocks into backup code yet, but I am working on it. I hope to have this list:
Code:
## BLOCK_LIST ##
# Conventions for the list o block are as follows
# [VAR_NAME]="/dev/blockmmcblk#p##" #-> [Known As] ([FS], [mount point if visible], [description]) == [odin img file]
MOD_BLK="/dev/block/mmcblk0p1" #-> CDMA Modem (vfat, mounts at /firmware, its the CDMA modem) == NON-HLOS.bin
SB1_BLK="/dev/block/mmcblk0p2" #-> sbl1 (samsung proprietary fs, sammys odd way of booting part1) == sbl1.mbn
SB2_BLK="/dev/block/mmcblk0p3" #-> sbl2 (samsung proprietary fs, sammys odd way of booting part2) == sbl2.mbn
SB3_BLK="/dev/block/mmcblk0p4" #-> sbl3 (samsung proprietary fs, sammys odd way of booting part3) == sbl3.mbn
ABT_BLK="/dev/block/mmcblk0p5" #-> aboot (unknown fs, this is the bootloader) == aboot.mbn
RPM_BLK="/dev/block/mmcblk0p6" #-> rpm (unknown fs, something to do with the radio) == rpm.mbn
BOT_BLK="/dev/block/mmcblk0p7" #-> boot (yaffs2, boot image contains the kernel) == boot.img
STZ_BLK="/dev/block/mmcblk0p8" #-> tz (porbably samsung proprietary fs, samsungs "Trust Zone" referenced in the sbl boot process) == tz.mbn
PAD_BLK="/dev/block/mmcblk0p9" #-> pad (unknown fs, aka PIT )
PRM_BLK="/dev/block/mmcblk0p10" #-> param (unknown fs, pretty much empty exept for one octet)
EFS_BLK="/dev/block/mmcblk0p11" #-> /efs (ext4, mounts at /efs, has device info like IMEI and MEID)
LT1_BLK="/dev/block/mmcblk0p12" #-> modemst1 (unknown fs, LTE modem 1)
LT2_BLK="/dev/block/mmcblk0p13" #-> modemst2 (unknown fs, LTE modem 2)
SYS_BLK="/dev/block/mmcblk0p14" #-> /system (ext4, everything under /system) == system.img.ext4
DAT_BLK="/dev/block/mmcblk0p15" #-> userdata (ext4. mounts at /data, contains internal sdcard as well at /data/media)
PST_BLK="/dev/block/mmcblk0p16" #-> /persist && /tombstones (ext4, contains very little data) == persist.img.ext4
CHE_BLK="/dev/block/mmcblk0p17" #-> /cache (ext4, its the cache baby) == cache.img.ext4
REC_BLK="/dev/block/mmcblk0p18" #-> recovery (ext4??, recovery image like CWM and TWRP?) == recovery.img
OTA_BLK="/dev/block/mmcblk0p19" #-> fota (ext4, found at /cache/fota, its where OTA updates are stored)
BAK_BLK="/dev/block/mmcblk0p20" #-> backup (unknown fs, where factory reset images are stored?)
FSG_BLK="/dev/block/mmcblk0p21" #-> fsg (unknown fs, may contain files used in factory wipe, somehow linked to the grow partition)
SSD_BLK="/dev/block/mmcblk0p22" #-> ssd (unknown fs maybe ramfs, "Secure Software Download" don't know what its used for)
GRW_BLK="/dev/block/mmcblk0p23" #-> grow (unknown fs, i think this has something to do with ext4 sparse images)
# WTF!?!?!?!?!?!!???
DK1_BLK="/dev/block/mmcblk0boot0" #-> may have something to do with booting (duh, but what)
DK2_BLK="/dev/block/mmcblk0boot1" #-> may have something to do with booting (duh, but what)
DK3_BLK="/dev/block/mmcblk1p1" #-> no idea
DK4_BLK="/dev/block/mmcblk1p2" #-> no idea
# NOTES:
# samsung seems to refer to 4 types of file systems; cgroup, ecryptfs, ext4, fuse
# could ecryptfs be the same as samsungs proprietary file system?
## END_BLOCK_LIST ##
Included in the tool, as options to backup. So far I have working code for System, Data (makes a tar and skips /data/media), Recovery, Userdata (HUGE), Modemst1, Modemst2, CDMA modem, Cache and Boot. But I do want to have all mmc blocks as options because I need a disaster recovery plan as well.
There's still alot of work to be done on it, but for now I use it to back up my device before flashing a rom. Saves on internal storage.
I'll try and convert my block list to you format used in the EL GRANDE Partition Table Reference as soon as possible. I dunno if you'll need it though. I do have alot of knowledge on GPT (GUID Partition Table) formatted storage as well as how EFI vs MBR can work withing such a table. But I can discuss that on the other thread.
I've read what you have so far in that thread and its very helpful.
Ta,
ALQI

Could you follow the instructions in post #2, of the thread I posted above, to obtain an output of parted and fdisk , for both mmcblk0 and mmcblk1?

E:V:A said:
Could you follow the instructions in post #2, of the thread I posted above, to obtain an output of parted and fdisk , for both mmcblk0 and mmcblk1?
Click to expand...
Click to collapse
Not a problem mate. I hope this fits your format.
Device info:
Code:
General Device Name: Samsung Galaxy S3
Manufacturer Product Name: SCH-I535
Processor: Snapdragon S4plus
AOS version: Android JB 4.1.1
Radio FW version: I535VRLHD
System FW version: I535VZWBLI5
Service Provider/ Branding: Verizon
Country: USA
ROM: Almost Stock JellyBean I535VRBLI5 (my own cooking from dsixda's andoid kitchen, added bash binary, nano, busybox and root)
fidsk output for mmcblk0:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 58.2M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61059087
Number Start (sector) End (sector) Size Code Name
1 8192 131071 120K 0700 modem
2 131072 131327 256 0700 sbl1
3 131328 131839 512 0700 sbl2
4 131840 132863 1024 0700 sbl3
5 132864 136959 4096 0700 aboot
6 136960 137983 1024 0700 rpm
7 137984 158463 20480 0700 boot
8 158464 159487 1024 0700 tz
9 159488 160511 1024 0700 pad
10 160512 180991 20480 0700 param
11 180992 208895 27904 0700 efs
12 208896 215039 6144 0700 modemst1
13 215040 221183 6144 0700 modemst2
14 221184 3293183 3000K 0700 system
15 3293184 59252735 53.3M 0700 userdata
16 59252736 59269119 16384 0700 persist
17 59269120 60989439 1680K 0700 cache
18 60989440 61009919 20480 0700 recovery
19 61009920 61030399 20480 0700 fota
20 61030400 61042687 12288 0700 backup
21 61042688 61048831 6144 0700 fsg
22 61048832 61048847 16 0700 ssd
23 61048848 61059087 10240 0700 grow
fdisk for those odd mmcblk0boot# devs:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk0boot0
Disk /dev/block/mmcblk0boot0: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0boot0 doesn't contain a valid partition table
sh-4.2# fdisk -l /dev/block/mmcblk0boot1
Disk /dev/block/mmcblk0boot1: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0boot1 doesn't contain a valid partition table
NOTE: I'm still not sure what these mmcblk0boot# blocks are, but they are there in the file system under /dev/block/ as well as /dev/block/platform/by-name.
fdisk output mmcblk1:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 1872 15032320 b Win95 FAT32
/dev/block/mmcblk1p2 1872 1937 524288 82 Linux swap
NOTE: mmcblk1 is the external sdcard (i'm dumb cause I thought it was a seperate eMMC chip, but its just plain old MMC) THat little swap space is left over from when I had the OG Droid.
parted output for mmcblk0:
Code:
sh-4.2# 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) p
p
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? Ignore
Ignore
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 12239 blocks) or
continue with the current setting?
Fix/Ignore? Ignore
Ignore
Model: MMC MBG8FB (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 30.3GB 28.7GB ext4 userdata
16 30.3GB 30.3GB 8389kB ext4 persist
17 30.3GB 31.2GB 881MB ext4 cache
18 31.2GB 31.2GB 10.5MB recovery
19 31.2GB 31.2GB 10.5MB fota
20 31.2GB 31.3GB 6291kB backup
21 31.3GB 31.3GB 3146kB fsg
22 31.3GB 31.3GB 8192B ssd
23 31.3GB 31.3GB 5243kB grow
(parted)
NOTE: The second warning with parted, is because the device uses a hybrid MBR/GPT table (gdisk shows us this). This is kinda like dual booting a Mac with Windows and Mac OS X. Also, the "backup" error is because the gpt table backup is in "pad" (aka PIT).
WARNING: Be careful with parted, make sure you tell it to "Ignore" and errors it might find. Also you have to type "quit" to get it to exit from interactive mode.
parted output for mmcblk0boot0
Code:
sh-4.2# parted /dev/block/mmcblk0boot0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0boot0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Error: /dev/block/mmcblk0boot0: unrecognised disk label
(parted)
NOTE: No need to run parted on mmcblk1 (cause its the external sdcard) nor mmcblk0boot# cause its not part of the gpt. Same goes for gdisk.
gdisk output for mmcblk0
Code:
sh-4.2# gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61059087
Partitions will be aligned on 16-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 131071 60.0 MiB 0700 modem
2 131072 131327 128.0 KiB FFFF sbl1
3 131328 131839 256.0 KiB FFFF sbl2
4 131840 132863 512.0 KiB FFFF sbl3
5 132864 136959 2.0 MiB FFFF aboot
6 136960 137983 512.0 KiB FFFF rpm
7 137984 158463 10.0 MiB FFFF boot
8 158464 159487 512.0 KiB FFFF tz
9 159488 160511 512.0 KiB FFFF pad
10 160512 180991 10.0 MiB 8300 param
11 180992 208895 13.6 MiB 8300 efs
12 208896 215039 3.0 MiB FFFF modemst1
13 215040 221183 3.0 MiB FFFF modemst2
14 221184 3293183 1.5 GiB 8300 system
15 3293184 59252735 26.7 GiB 8300 userdata
16 59252736 59269119 8.0 MiB 8300 persist
17 59269120 60989439 840.0 MiB 8300 cache
18 60989440 61009919 10.0 MiB FFFF recovery
19 61009920 61030399 10.0 MiB FFFF fota
20 61030400 61042687 6.0 MiB 8300 backup
21 61042688 61048831 3.0 MiB FFFF fsg
22 61048832 61048847 8.0 KiB FFFF ssd
23 61048848 61059087 5.0 MiB 8300 grow
Again, be very careful when running these disk utilities because they are not meant to handle a hybrid boot. Samsung's odd way of booting makes this kind of analysis difficult because of the prorieray fs they use for sbl1 through sbl3.
Click to expand...
Click to collapse
Wow that's alot of formatting.
Ta,
ALQI

Thanks a lot! In particular to remind people of the "warnings". I'll add that to the other thread.

Hey guys,
I have a I535 S3 that was hard bricked because of a bad flash, I want to try and repair it with JTAG but I don't have the necessary partition boot files...and it's not a supported version either.
Does anybody have a backup of the first 10 partitions from Modem to Param in .bin format?
I know it's possible to do such a backup with adb. or can somebody point me in the right direction?
Thank you!

Sure, I'll dd those for you tomorrow and pm you a Dropbox link.
For the first 10 partitions it shouldn't matter, but do you have a 16GB or 32Gb?
Sent from my SCH-I535 using xda app-developers app

It's the 16Gb version.
Thank you very much... You're a life savor!
Sent from my SGH-I897 using Tapatalk 2

PM sent.

Thank you!
Got them.. Hopefully it works!
Sent from my SGH-I897 using Tapatalk 2

E:V:A said:
Thanks a lot! In particular to remind people of the "warnings". I'll add that to the other thread.
Click to expand...
Click to collapse
As this is GTP parition it uses differing handles for the partition type
here is a example snip of the qualcomm partition.xml for a gtp partition
Code:
<partition label="modem" size_in_kb="65536" type="EBD0A0A2-B9E5-4433-87C0-68B6B72699C7" bootable="false" readonly="true" filename="NON-HLOS.bin"/>
<partition label="sbl1" size_in_kb="128" type="[COLOR="Red"][B]DEA0BA2C-CBDD-4805-B4F9-F428251C3E98[/B][/COLOR]" bootable="false" readonly="false" filename="sbl1.mbn"/>
<partition label="sbl2" size_in_kb="256" type="8C6B52AD-8A9E-4398-AD09-AE916E53AE2D" bootable="false" readonly="false" filename="sbl2.mbn"/>
<partition label="sbl3" size_in_kb="512" type="05E044DF-92F1-4325-B69E-374A82E97D6E" bootable="false" readonly="false" filename="sbl3.mbn"/>
<partition label="aboot" size_in_kb="512" type="400FFDCD-22E0-47E7-9A23-F16ED9382388" bootable="false" readonly="false" filename="emmc_appsboot.mbn"/>
<partition label="rpm" size_in_kb="512" type="098DF793-D712-413D-9D4E-89D711772228" bootable="false" readonly="false" filename="rpm.mbn"/>
<partition label="boot" size_in_kb="10240" type="20117f86-E985-4357-B9EE-374BC1D8487D" bootable="false" readonly="true" filename="boot.img" />
<partition label="tz" size_in_kb="512" type="A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4" bootable="false" readonly="false" filename="tz.mbn"/>
<partition label="pad" size_in_kb="1" type="004A6838-062A-44DF-8152-4F340C05225D" bootable="false" readonly="false" filename="" />
<partition label="modemst1" size_in_kb="3072" type="2013373E-1AC4-4131-B0F8-9158F9654F4F" bootable="false" readonly="false" filename="" />
<partition label="modemst2" size_in_kb="3072" type="2013373E-1AC4-4131-B0F8-9158F9654F4F" bootable="false" readonly="false" filename="" />
<partition label="system" size_in_kb="262144" type="0FC63DAF-8483-4772-8E79-3D69D8477DE4" bootable="false" readonly="true" filename="system.img.ext4" sparse="true"/>
Click to expand...
Click to collapse
could we see if my compiled binaries for gtp partitions return the UUID for type ?
Original Post http://forum.xda-developers.com/showpost.php?p=36019312&postcount=13
Binaries
http://www.sendspace.com/file/5b3jdc
Example output from partx ( non gtp partition, i dont have gtp partition)
Code:
[email protected]:/ # /data/test/partx
Usage:
partx [-a|-d|-s] [--nr <n:m> | <partition>] <disk>
Options:
-a, --add add specified partitions or all of them
-d, --delete delete specified partitions or all of them
-l, --list list partitions (DEPRECATED)
-s, --show list partitions
-b, --bytes print SIZE in bytes rather than in human readable format
-g, --noheadings don't print headings for --show
-n, --nr <n:m> specify the range of partitions (e.g. --nr 2:4)
-o, --output <type> define which output columns to use
-P, --pairs use key="value" output format
-r, --raw use raw output format
-t, --type <type> specify the partition type (dos, bsd, solaris, etc.)
-v, --verbose verbose mode
-h, --help display this help and exit
-V, --version output version information and exit
Available columns (for --show, --raw or --pairs):
NR partition number
START start of the partition in sectors
END end of the partition in sectors
SECTORS number of sectors
SIZE human readable size
NAME partition name
UUID partition UUID
TYPE partition type hex or uuid
FLAGS partition flags
SCHEME partition table type (dos, gpt, ...)
For more details see partx(8).
1|[email protected]:/ # /data/test/partx -l /dev/block/mmcblk0
# 1: 1- 204800 ( 204800 sectors, 104 MB)
# 2: 204801- 205800 ( 1000 sectors, 0 MB)
# 3: 205801- 208800 ( 3000 sectors, 1 MB)
# 4: 208801- 30777343 ( 30568543 sectors, 15651 MB)
# 5: 212992- 213991 ( 1000 sectors, 0 MB)
# 6: 221184- 225279 ( 4096 sectors, 2 MB)
# 7: 229376- 234375 ( 5000 sectors, 2 MB)
# 8: 237568- 258047 ( 20480 sectors, 10 MB)
# 9: 262144- 263143 ( 1000 sectors, 0 MB)
#10: 270336- 271335 ( 1000 sectors, 0 MB)
#11: 278528- 279527 ( 1000 sectors, 0 MB)
#12: 286720- 307199 ( 20480 sectors, 10 MB)
#13: 311296- 511999 ( 200704 sectors, 102 MB)
#14: 516096- 522239 ( 6144 sectors, 3 MB)
#15: 524288- 530431 ( 6144 sectors, 3 MB)
#16: 532480- 538623 ( 6144 sectors, 3 MB)
#17: 540672- 741375 ( 200704 sectors, 102 MB)
#18: 745472- 751615 ( 6144 sectors, 3 MB)
#19: 753664- 759807 ( 6144 sectors, 3 MB)
#20: 761856- 767999 ( 6144 sectors, 3 MB)
#21: 770048- 790527 ( 20480 sectors, 10 MB)
#22: 794624- 815103 ( 20480 sectors, 10 MB)
#23: 819200- 839679 ( 20480 sectors, 10 MB)
#24: 843776- 3911679 ( 3067904 sectors, 1570 MB)
#25: 3915776- 8114175 ( 4198400 sectors, 2149 MB)
#26: 8118272- 8736767 ( 618496 sectors, 316 MB)
#27: 8740864- 9005055 ( 264192 sectors, 135 MB)
#28: 9011200- 10035199 ( 1024000 sectors, 524 MB)
#29: 10035200- 30777343 ( 20742144 sectors, 10619 MB)
[email protected]:/ #
lsblk output
Code:
[email protected]:/ # /data/test/lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 2.1M 0 loop
`-278cb90965c39ee2acfea003ec39e4f5 (dm-0)
254:0 0 2.1M 0 dm /mnt/asec/com.androirc-1
loop1 7:1 0 5.1M 0 loop
`-ce28924bd3284f292fdd7955925746bc (dm-1)
254:1 0 5.1M 0 dm /mnt/asec/com.quoord.tapatalkxda.activity-
loop2 7:2 0 16.3M 0 loop
`-2ef6fb57bc43988a90c9add8bc514237 (dm-2)
254:2 0 16.3M 0 dm /mnt/asec/com.loumasoft.amiga500musiccolle
mmcblk0 179:0 0 14.7G 0 disk
|-mmcblk0p1 179:1 0 100M 0 disk
|-mmcblk0p2 179:2 0 500K 0 disk
|-mmcblk0p3 179:3 0 1.5M 0 disk
|-mmcblk0p4 179:4 0 1K 0 disk
|-mmcblk0p5 179:5 0 500K 0 disk
|-mmcblk0p6 179:6 0 2M 0 disk
|-mmcblk0p7 179:7 0 2.5M 0 disk
|-mmcblk0p8 179:8 0 10M 0 disk
|-mmcblk0p9 179:9 0 500K 0 disk
|-mmcblk0p10 179:10 0 500K 0 disk
|-mmcblk0p11 179:11 0 500K 0 disk
|-mmcblk0p12 179:12 0 10M 0 disk
|-mmcblk0p13 179:13 0 98M 0 disk
|-mmcblk0p14 179:14 0 3M 0 disk
|-mmcblk0p15 179:15 0 3M 0 disk
|-mmcblk0p16 179:16 0 3M 0 disk
|-mmcblk0p17 179:17 0 98M 0 disk
|-mmcblk0p18 179:18 0 3M 0 disk
|-mmcblk0p19 179:19 0 3M 0 disk
|-mmcblk0p20 179:20 0 3M 0 disk
|-mmcblk0p21 179:21 0 10M 0 disk
|-mmcblk0p22 179:22 0 10M 0 disk
|-mmcblk0p23 179:23 0 10M 0 disk
|-mmcblk0p24 179:24 0 1.5G 0 disk
|-mmcblk0p25 179:25 0 2G 0 disk
|-mmcblk0p26 179:26 0 302M 0 disk
|-mmcblk0p27 179:27 0 129M 0 disk
|-mmcblk0p28 179:28 0 500M 0 disk
`-mmcblk0p29 179:29 0 9.9G 0 disk
mmcblk1 179:32 0 14.4G 0 disk
`-mmcblk1p1 179:33 0 14.4G 0 disk
[email protected]:/ #
sample output from blkid
Code:
blkid from util-linux 2.22 (libblkid 2.22.0, 04-Sep-2012)
Usage:
blkid -L <label> | -U <uuid>
blkid [-c <file>] [-ghlLv] [-o <format>] [-s <tag>]
[-t <token>] [<dev> ...]
blkid -p [-s <tag>] [-O <offset>] [-S <size>]
[-o <format>] <dev> ...
blkid -i [-s <tag>] [-o <format>] <dev> ...
Options:
-c <file> read from <file> instead of reading from the default
cache file (-c /dev/null means no cache)
-d don't encode non-printing characters
-h print this usage message and exit
-g garbage collect the blkid cache
-o <format> output format; can be one of:
value, device, export or full; (default: full)
-k list all known filesystems/RAIDs and exit
-s <tag> show specified tag(s) (default show all tags)
-t <token> find device with a specific token (NAME=value pair)
-l look up only first device with token specified by -t
-L <label> convert LABEL to device name
-U <uuid> convert UUID to device name
-v print version and exit
<dev> specify device(s) to probe (default: all devices)
Low-level probing options:
-p low-level superblocks probing (bypass cache)
-i gather information about I/O limits
-S <size> overwrite device size
-O <offset> probe at the given offset
-u <list> filter by "usage" (e.g. -u filesystem,raid)
-n <list> filter by filesystem type (e.g. -n vfat,ext3)
4|[email protected]:/ # /data/test/blkid
/dev/block/mmcblk0: PTTYPE="dos"
/dev/block/mmcblk0p13: SEC_TYPE="msdos" UUID="7365-DAB3" TYPE="vfat"
/dev/block/mmcblk0p17: SEC_TYPE="msdos" UUID="29B2-ACBF" TYPE="vfat"
/dev/block/mmcblk0p21: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p24: UUID="c63c0c30-700c-4874-9acd-fd507d02000a" TYPE="ext4"
/dev/block/mmcblk0p25: UUID="36caf8ff-15bf-4c24-92e0-0c84a21f3b0c" TYPE="ext4"
/dev/block/mmcblk0p26: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p27: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p28: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p29: UUID="887F-1DF5" TYPE="vfat"
/dev/block/mmcblk1: PTTYPE="dos"
/dev/block/mmcblk1p1: UUID="64A1-1B57" TYPE="vfat"
[email protected]:/ #
most will use sgdisk/partx on gtp based partitions. sgdisk also supports the partition info cloning like sfdisk does.
See sfdisk in util-linux sources for more info
darkspr1te

letinsh said:
PM sent.
Click to expand...
Click to collapse
By the way.. Those partitions worked great for jtag.
Thanks again!
Sent from my I897 AoCP CP 4.6

spagman72 said:
Hey guys,
I have a I535 S3 that was hard bricked because of a bad flash, I want to try and repair it with JTAG but I don't have the necessary partition boot files...and it's not a supported version either.
Does anybody have a backup of the first 10 partitions from Modem to Param in .bin format?
I know it's possible to do such a backup with adb. or can somebody point me in the right direction?
Thank you!
Click to expand...
Click to collapse
Hey, I have the sch-i535 Verizon. Do you want me to give it to you?

Israelleite said:
Hey, I have the sch-i535 Verizon. Do you want me to give it to you?
Click to expand...
Click to collapse
spagman72 said:
By the way.. Those partitions worked great for jtag.
Thanks again!
Sent from my I897 AoCP CP 4.6
Click to expand...
Click to collapse
already got him taken care of

[Q] How to restore damaged Internal SD card partition layout? Tried everything.

I have Samsung S 3 mini.
I did something really bad to my INTERNAL SD CARD partition layout, so now I have
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 3866624 mmcblk1
179 97 3862528 mmcblk1p1
Code:
~ # ls -la /dev/block/mmcblk*
brw------- 1 root root 179, 0 Jan 1 10:30 /dev/block/mmcblk0
brw------- 1 root root 179, 32 Jan 1 09:28 /dev/block/mmcblk0boot0
brw------- 1 root root 179, 64 Jan 1 09:28 /dev/block/mmcblk0boot1
-rw-rw-rw- 1 root root 16777216 Jan 1 10:07 /dev/block/mmcblk0p20
-rw-r--r-- 1 root root 0 Jan 1 10:07 /dev/block/mmcblk0p22
brw------- 1 root root 179, 96 Jan 1 09:28 /dev/block/mmcblk1
brw------- 1 root root 179, 97 Jan 1 09:28 /dev/block/mmcblk1p1
Code:
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 411756 16452 395304 4% /dev
/dev/block/mmcblk1p1 3858432 1473472 2384960 38% /external_sd
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Code:
~ # tail ./etc/recovery.fstab
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25 length=-16384
/efs ext4 /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
/modem ext4 /dev/block/mmcblk0p12
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
Code:
~ # tail ./etc/fstab
/dev/block/mmcblk0p23 /cache ext4 rw
/dev/block/mmcblk0p25 /data ext4 rw
/dev/block/mmcblk0p22 /system ext4 rw
/dev/null /sdcard datamedia rw
Code:
~ # 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
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No?
My ClockWorkMod recovery tool can't mount anything (/cache, /system, nothing). This is what kind of stuff I get in CWM:
Code:
-- Wiping cache...
Formatting /cache...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p23
Cache wipe complete.
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
W:Can't unlink /cache/recovery/command
Formatting /data...
warning: get_file_size: Computed filesystem size less than 0
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error formatting /data!
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
As you can see, there is no partitions for /system, /cache and other stuff, that should be there. (but /system, and /cache folders are present in dir listing)
I really did everything I could. I tried: restore from backup (I have one, made with recovery tool), install new ROM (With recovery tool), install stock firmware and stock kernel in ODIN mode. I even tried some PIT file: nothing did absolutely nothing to my status.
Frankly I miss some important part in understanding of filesystem, partitions, images, what is ROM, what is stock kernel, how does those 22, 23 25 partitions are created etc ...
What should I do? Please, help.

How did you mess it up
Sent from my Nexus 4 using xda app-developers app

mattoaida said:
How did you mess it up
Click to expand...
Click to collapse
As I remember correctly, I tried to repartition my External SD card with fdisk right on Android via 'adb shell'. And I delete existed (there was only one as I recall) partition on mmcblk0 (which is appeared to be not an External, but Internal =\
I tried to create fat and ext partitions on mmcblk0, but only now I thought, that I didn't format it .. and maybe ext should be made as ext3 or ext4. Don't know exactly how to do it.

Oh, looks like I have everything in console buffer (full history of distraction actions)
In the beginning I had this:
Code:
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 3872256 mmcblk1
179 97 3868160 mmcblk1p1
254 0 2110 dm-0
Code:
/ $ df
Filesystem Size Used Free Blksize
/dev 402.1M 84K 402M 4096
/mnt/asec 402.1M 0K 402.1M 4096
/mnt/obb 402.1M 0K 402.1M 4096
/dev/shm 402.1M 0K 402.1M 4096
/system 1.2G 414.5M 766.6M 4096
/modemfs 15.7M 4.3M 11.4M 4096
/cache 826.8M 84.8M 742M 4096
/efs 15.7M 4.5M 11.2M 4096
/preload 315M 64.2M 250.8M 4096
/data 4.6G 4G 699.2M 4096
/mnt/.lfs: Function not implemented
/storage/sdcard0 4.6G 4G 699.2M 4096
/mnt/asec/com.spruds.transport.pro.tallin-1 2M 888K 1.1M 4096
/storage/sdcard1 3.7G 905.7M 2.8G 32768
Even before everything went wrong I tried to use parted command and get an error
Code:
~ # 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) list
list
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
.....
.....
copyright information of GNU Parted
(parted) print
print
Error: Unable to satisfy all constraints on the partition.
This is fdisk print before disaster
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
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)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
And then I deleted it
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
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)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Command (m for help): d
Selected partition 1
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy

sensation XE make_extf4fs failed on /dev/block/mmc/...

Hi, I know that there are lots of topics like that but I didn't find any of those helpful.
I was just doing some basic changes to the settings of the phone, and then suddenly it rebooted to recovery mode, and it doesn't boot anymore.
I get this error when I want to format the data partition:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p23
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p23
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p24
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p24
formating /sdcard/.android_secure...
Data wipe complete.
And I also get the same error when I want to format the system partition, except this time the blk0p22 block causes error.
The phone's s-off, with 4ext recovery touch, hboot 1.27.1111, and it was running viperS 5.3.0 when this happened.
what do I have to do?
thanks. :good:

Now I got to the /dev/block/mmc/ via the adb shell, the following files are in the directory:
Code:
ls
loop0 loop7 mmcblk0p14 mmcblk0p20 mmcblk0p27 mmcblk0p4 mmcblk1p
1
loop1 mmcblk0 mmcblk0p15 mmcblk0p21 mmcblk0p28 mmcblk0p5 platform
loop2 mmcblk0p1 mmcblk0p16 mmcblk0p22 mmcblk0p29 mmcblk0p6
loop3 mmcblk0p10 mmcblk0p17 mmcblk0p23 mmcblk0p3 mmcblk0p7
loop4 mmcblk0p11 mmcblk0p18 mmcblk0p24 mmcblk0p30 mmcblk0p8
loop5 mmcblk0p12 mmcblk0p19 mmcblk0p25 mmcblk0p31 mmcblk0p9
loop6 mmcblk0p13 mmcblk0p2 mmcblk0p26 mmcblk0p32 mmcblk1
As written in this link, I have put parted to the sbin directory, now when I try to format the directory I get this error:
Code:
~ # parted /dev/block/mmc/ mkfs ext4
parted /dev/block/mmc/ mkfs ext4
Error: Could not stat device /dev/block/mmc/ - No such file or directory.
Retry/Cancel?
what should I do now? am I doing the right thing?
thanks.

the system/data partitions are not even mounting:
Code:
mount -a
mount: mounting /dev/block/mmcblk0p23 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p22 on /system failed: Invalid argument
and when I try to mount the cache partition:
Code:
mount cache
mount: mounting /dev/block/mmcblk0p24 on /cache failed: Device or resource busy
Is there anyway that I can change the internal memory chip without changing the whole motherboard?
thanks.
edit:
I get this when I run the parted and then I send mkfs 1 ext3 or ext4:
Code:
(parted) mkfs 1 ext4
mkfs 1 ext4
mkfs 1 ext4
Error: /dev/block/mmcblk0: unrecognised disk label
(parted) mkfs 1 ext3
mkfs 1 ext3
mkfs 1 ext3
Error: /dev/block/mmcblk0: unrecognised disk label

any solution?

[Q] Problems with partition table

I have a Prestigio 5044 Duo (PAP5044) with MTK6589. Basically, what I was trying to do was to resize /data partition, beacause it was only about 950Mb, by shrinking Internal SD card (/emmc) partition. For that I used Meteos MTK6589 Apllication.
After going all the steps I found out that Android OS was hanging during boot (like half-way to boot up, and it freezed with no error messages). Though, recovery (I have CWM) boots well.
After doing some research I found out, that partition table of the device was messed up after /cache partition. So, all system and recovery partititons are fine.
Here is fdisk output:
Code:
~ # fdisk -lu /dev/block/mmcblk0
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Disk /dev/block/mmcblk0: 3853 MB, 3853516800 bytes
1 heads, 16 sectors/track, 470400 cylinders, total 7526400 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 1022 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26624 47103 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 47104 67583 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 93184 105471 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 134144 1465343 665600 83 Linux
/dev/block/mmcblk0p6 7556096 1022 2143706111+ 83 Linux
And here are /proc/partitions and fstab:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 3763200 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 665600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 2901504 mmcblk0p7
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 31338496 mmcblk1
179 97 31334400 mmcblk1p1
~ # cat /etc/fstab
/dev/block/mmcblk0p6 /cache ext4 rw
/dev/block/mmcblk0p7 /data ext4 rw
/dev/block/mmcblk0p8 /emmc vfat rw
/dev/block/mmcblk0p5 /system ext4 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
So, on mmcblk0 there must be 10 partitions, and now there are only 6, according to fdisk.
I have two ideas how it is possible to restore partitions: 1) manually with fdisk, though it doesn't seem like a very good idea 2) I've found some info about scatter file for MTK-based devices, seems like it contains all the partitioning info; I have no idea how to get and use that file, though.
What should I do to recover my device?

How to recover a recovery partition and how to restore / create / inspect EMMC

Hi guys,
I could probably make a thread outside TF700 forums as my questions are more generic but as I don't know what place would suit it better and as my device is TF700T, I'm doing it here.
Some time ago I was messing around with my TF700T which at that moment was already unlocked and rooted. I had TWRP (not sure what version exactly it was but probably something close to 2.8.x) and CyanogenMod 11-20160815-NIGHTLY-tf700t installed and working properly. As I wanted to install Gentoo on it, I replaced TWRP with something else (don't remember what was that) and finally somehow screwed recovery. As I don't fully remember what has happened back then, I can tell how it is now.
So the tablet is working without problems but recovery is not accessible. Whenever I try to boot into recovery choosing the RCK icon in a boot menu the tablet is hanging.
But as both adb and fastboot can see the tablet, I decided to dig it a bit more.
Code:
# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
015d2a50865c1a07 device
# adb reboot bootloader
# fastboot devices
015d2a50865c1a07 fastboot
# fastboot -i 0x0B05 flash recovery twrp-3.2.1-0-tf700t.img
sending 'recovery' (7414 KB)...
As this process seems to be endless I decide to interrupt it using the power button on the tablet. As result I get a message:
Code:
FAILED (data transfer failure (Cannot send after transport endpoint shutdown))
finished. total time: 337.278s
Then I decide to inspect how partitions look like using the adb shell but first I inspect fstab to see what supposed to be mounted:
Code:
# adb shell
[email protected]:/ $ su
[email protected]:/ # cat fstab.cardhu
# INIT mount points
/dev/block/mmcblk0p1 /system ext4 noatime,noauto_da_alloc,nodiratime,barrier=0,ro wait
/dev/block/mmcblk0p2 /cache ext4 noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,errors=panic wait
/dev/block/mmcblk0p8 /data ext4 noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,errors=panic wait,encryptable=footer
# VOLD mount points
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1.2 auto auto defaults voldmanaged=usbdisk0:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1.2 auto auto defaults voldmanaged=usbdisk0:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1.1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1.1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1:1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1:1 auto auto defaults voldmanaged=usbdisk1:auto
/devices/platform/tegra-ehci.2/usb1/1-1/1-1.3 auto auto defaults voldmanaged=sdcard2:auto
/devices/platform/tegra-ehci.2/usb2/2-1/2-1.3 auto auto defaults voldmanaged=sdcard2:auto
# Recovery only
/dev/block/mmcblk1p1 /external_sd auto defaults recoveryonly
/dev/block/mmcblk0p3 /misc emmc defaults recoveryonly
/dev/block/mmcblk0p4 /staging ext3 defaults recoveryonly
/dev/block/mmcblk0p9 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p10 /boot emmc defaults recoveryonly
Then I check what partitions I have (I thought maybe recovery partition has been deleted somehow):
Code:
# cat /proc/partitions
major minor #blocks name
179 0 62087168 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 59976192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 15622144 mmcblk1
179 49 15618048 mmcblk1p1
And finally check if parted can give me any info about these partitions. I don't care about mmcblk1 as it is an external SD card:
Code:
# parted /dev/block/mmcblk0p1
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 805MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 805MB 805MB ext4
# parted /dev/block/mmcblk0p2
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p2: 449MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 449MB 449MB ext4
# parted /dev/block/mmcblk0p3
Error: /dev/block/mmcblk0p3: unrecognised disk label
# parted /dev/block/mmcblk0p4
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p4: 856MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 856MB 856MB ext3
# parted /dev/block/mmcblk0p5
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p5: 5243kB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
# parted /dev/block/mmcblk0p6
Error: /dev/block/mmcblk0p6: unrecognised disk label
# parted /dev/block/mmcblk0p7
Error: /dev/block/mmcblk0p7: unrecognised disk label
# parted /dev/block/mmcblk0p8
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p8: 61.4GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 61.4GB 61.4GB ext4
# parted /dev/block/mmcblk0p9
Error: /dev/block/mmcblk0p9: unrecognised disk label
# parted /dev/block/mmcblk0p10
Error: /dev/block/mmcblk0p10: unrecognised disk label
# parted /dev/block/mmcblk0boot0
Error: /dev/block/mmcblk0boot0: unrecognised disk label
# parted /dev/block/mmcblk0boot1
Error: /dev/block/mmcblk0boot1: unrecognised disk label
As we can see partitions 3, 6, 7, 9, 10 and boot0, boot1 have unrecognised disk label. I can't also mount them to inspect their contents (can mount others and their contents looks good to me).
I don't see partitions 6, 7 in fstab but anyhow it does look like all unrecognised partitions have type emmc.
And recovery partition should be mmcblk0p9. The question now is: how do I mount emmc partition then in order to be able to check if it's okay or dead? How do I manage it (delete / create / resize)?
For now I would like to make recovery work. Any ideas?